I suspect that if I edited each clip independently and differently then the project may have grow even larger.
given that it has 24 smart clips each with a full 2 hours of data (albeit mostly hidden). Vii) I’m surprised that the inactive/closed size of the 3.2.1 project does not get above 5GB.
Vi) 3.2.1 step 4 active size was surprisingly large V) 3.2.1 step 2 WAL size seems unexpected Iv) compaction in 3.x cab be both time-consuming and tiresome - but necessary due to the use of the SQLite database Iii) performance appears to not be an issue Ii) The on-disk size of a 3.2.x project can be much larger due to the temporary WAL file I) yes the 3.2.x smart clips result in a larger project size the the 2.4.2 simple clips (in this use case double the size when closed 1min 10secs (twice as long as the effects took) I did some tests comparing 3.2.1 and 2.4.2 …īetween each of the Steps I noted the active size of the project closed Audacity and noted the inactive project size and then relaunched.Īt Step 1-2 the active and closed size was 2.4GBįor steps 3-5 the active size was 4.8GB, the inactive closed size was 2.4GBĪt Step 1 the active size was 5GB (AUP3 and WAL both 2.5GB)B - the closed size was 2.5GBĪt Step 2 the active size was 2.5GB AUP3, WAL 1.7MB - the closed size was 2.5GBĪt Step 3 the active size was 5GB (AUP3 and WAL both 2.5GB) - the closed size was 5GBĪt Step 4 the active size was 10.1GB (AUP3 7.6GB and WAL 2.5GB) - the closed size was 5GBĪt Step 5 the active size was 7.5GB (AUP3 5GB and WAL 2.5GB) - the closed size was 5GBįor both the processing time for the generate and the effects is broadly similar with both versions.ģ.2.x carries the extra burden of Compaction on closure which took c. Nevertheless, it’s true that projects made in Audacity 3.1 and later can be much bigger than in earlier versions. It’s when the audio data is modified that a copy has to be made. … Audio data may be shared between multiple audio clips.
0 kommentar(er)
