Open Carlsans opened 1 year ago
It's really the Audio reference tab that make it that slow. Tried Chrome with the same issues. Using Audacity for now and lock keyframes to seconds.
Thanks for the report! Totally agree Parseq becomes clunky with more than a few thousand frames or a few mins of audio. I hope to address this soon. One promising line of investigation is upgrading WaveSurfer 6->7 (7 has some perf improvements). It's not a trivial upgrade but hope to get there soon. Beyond that there's plenty of scope for optimisation within Parseq itself: there's almost certainly a bunch of unnecessary React re-renders that can be optimised out.
So bear with me, this'll be improved eventually! :) Meanwhile, an approach many people take is to work in chunks with Parseq and combine sections in post.
Using Firefox, I closed all the windows (by the way they should be closed by default or one button to close them all) except for keyframe grid and audio reference. I try to set up keyframes for a 7 minute song that totalize 5700 frame. The latency when I push for example the play button is about 1 second. That make it difficult to adequately place the keyframes. I really like parseq but the optimization issues are a big problem that render the whole project much less interesting. Is there any way I could speed that up ? Thanks.