When I was using version 2.1, I was very happy that the rendering time was fast and the previous speed issues had been fixed. However, version 4.1 seems to have changed the rendering and now takes 5-7 hours to render 4 minutes of music that would have taken maybe 15-20 minutes on the previous version on the exact same settings.
I don't really have time for that if that's how rendering will be from now on. Unfortunately, I'm also not able to use version 2.1 anymore because the trial period expired on it. Here's the last video I made with version 2.1: https://www.youtube.com/watch?v=43ZX_x7hILA - It's a good testament of version 2.1's fast rendering because that song came out just five hours before my video was out. In fact, I'd say that version 2.1's rendering only took about half the time that my editing software took to render the final product, which is impressive.
Ok. Since I'm not able to consistently replicate it, it'll be very difficult for me to completely guarantee the elimination of the problem. But I'll try one change that might prevent it. Please keep me posted if you still see the problem consistently after the 5.1 update that gets posted tonight or tomorrow. Thank you again!
Well, after getting the issue on the first try, now I can't replicate it at all - everything is working perfectly. Just so I know, what percentage of the time is this happening for you?
Ok, I'm able to replicate it - it was triggered by rendering on 60 FPS for me on Windows.
Will get to fixing it...
It said that it would take 27 minutes to render this at 30 FPS. Then when I restarted the app, it took 3 minutes. https://www.youtube.com/watch?v=9MWyjPQrbxA
It seems to be going faster only temperamentally. Often, it will give me a long time estimate. Then if I close the app and restart it, it will render at the correct speed. I'm not sure why that is. It does that with every MIDI I've used since downloading version 4.2.
Hmm... it should take twice as long to render a 60 FPS video, since there are twice as many frames. Is it taking more than twice as long as the same video at 30 FPS?
Also, if that specific MIDI you mentioned is still causing an issue - please do send it over so that I can see if there's an issue there.
Yes, the rendering seems to be fixed now. It took about 10 minutes to render this at 30 FPS: https://www.youtube.com/watch?v=99kBzUNcA6o
However, it seems that it still taking abnormally long to render that at 60 FPS. I tested it with another 4 minute MIDI file and that other one was rendering at the correct speed, so I don't know why the first one was rendering so slowly. I'll let you know if it keeps being slow.
Ok - after about 9 hours of more debugging, I think I've finally got the stalling issue on rendering fixed permanently.
- Version 4.2 is now up - could you give it a try at your earliest convenience and let me know if it's now back to rendering fast (and correctly)?
Just in case you're interested why all this went down - This is a complicated issue - there are 3 different videos playing in the scene with the different video textures the app uses, and it's very complicated for a computer to be sure that it's loaded the correct video frame for each frame of the render. The app can potentially hang if it doesn't get a notification back that the videos correctly updated, but if it rushes ahead too soon, it can skip video frames (which is what is was doing occasionally back in Version 2.1). Now it should be working correctly, fingers crossed... (I've tested on both Mac and Windows).
- Thanks for the heads up about the second issue as well, another user posted about this and I'll get to fixing it later tonight.
Here's a video of me rendering. There's also a glitch where the render dialog box says you're rendering some classical piece regardless of what the MIDI is called. https://drive.google.com/file/d/1bmE4trE7ycshpdvPJQwpgWHW2BDNxLEm/view?usp=sharing
Thanks very much for letting me know. The issue is coming from an adjustment to the way that the app handles the video layers. This definitely needs to (and will be) fixed.
Update: I'm able to replicate the issue on Windows. Will see if I can figure out a fix tonight.