Besides my own projects, I wanted to make a compilation of some mp3 songs from the 90's with CDA and remaster them.
So on each track I put an Ozone plugin with different settings.
And what is very strange is that the more tracks I have in the project, the more it takes on CPU to play a track (render to file and burn too).
With only one track in the project, my CPU meter (Windows Task Manager) show between 30-40 %.
With 7 tracks on the project, the CPU meter is on 100 % and it is so hard on the CPU than the playing stops periodically (same effect than when on Sound forge the plugin meter shows >100%). I tried to change the audio buffer size but it has no effect as the project is very hard on CPU.
The creation of the temporary file is crazily long (it shows 80-70 min when it starts... my CPU is a XP 1800+).
Is there anything I can do ? Is that a bug or is there somekind of explanation ?
So on each track I put an Ozone plugin with different settings.
And what is very strange is that the more tracks I have in the project, the more it takes on CPU to play a track (render to file and burn too).
With only one track in the project, my CPU meter (Windows Task Manager) show between 30-40 %.
With 7 tracks on the project, the CPU meter is on 100 % and it is so hard on the CPU than the playing stops periodically (same effect than when on Sound forge the plugin meter shows >100%). I tried to change the audio buffer size but it has no effect as the project is very hard on CPU.
The creation of the temporary file is crazily long (it shows 80-70 min when it starts... my CPU is a XP 1800+).
Is there anything I can do ? Is that a bug or is there somekind of explanation ?