Please see the screenshot below for my system specs. The Player.log file has since been overwritten during subsequent rendering attempts, so I don't have the original log to submit. However, I did see the original log, and the crash message at the end seemed to indicate about 6-7 GB of RAM was in use, and Task Manager also showed 6-7 GB of RAM being utilized during a later render attempt. I cancelled all the other render attempts because they were quite slow, so I haven't been able to reproduce the crash message.
The renders were all done with the audio turned off. After I downloaded version 1.26 today, I saw the same rendering behavior. However, when I enabled the audio, the render completed successfully (the first pass for the audio sounded like it was done in real time and took around 3 minutes; the second pass for the video took approximately 2 minutes and 50 seconds). The video was 2 minutes and 48 seconds long. The RAM usage was much lower this time as well (only around 630 MB; see second screenshot below). I should note that the audio in the rendered video contained a lot of glitches.
Another message on this forum indicated SeeMusic Version 1.13 also renders quickly (though it doesn't have the newest particle effects). Could you send me a link to V1.13 to try, please? My email is esdennis85@gmail.com
Please let me know if you need any other information. Thanks!!
Hello,
Luckily I think I found the issue, and it is an easy but important fix.
Please give this version a try:
https://www.dropbox.com/s/gdoa55syf65vdc0/SeeMusic%20Windows%201.28.zip?dl=1
Let me know if it's fixed now, or if you are still having issues rendering?
I'm still having this issue with version 4.2.1. It renders at snail pace unless I turn off saber and texture but I'd like to use those features. How can I make it work?
I just tried the new version and it rendered on the first attempt without crashing! There were some audio glitches (particularly on the louder, faster passages), but the video itself rendered beautifully! It took only 11 minutes to render at 1080p resolution (60 FPS). Thanks for resolving the slow render and crash issue so quickly--keep up the awesome work 😎
Here is the link to Version 1.13: https://www.dropbox.com/s/cx0dkq9yylfpkjg/SeeMusic%20Windows%201.13.zip?dl=1
Please also send:
A screenshot of Visual Settings
A screenshot of Player Settings
If using a video file, a screenshot of Video Settings
The files you used to make the render, including MIDI, Audio and Video files
The logs would be very helpful as well.
The 0.04x rendering speed is almost certainly due to the Unity VideoPlayer failing to advance video frames during the render. The VideoPlayer is used for the Video Texture inside the notes, the Saber effect, and of course if you are using a Video File.
If you could test a render in the new version by disabling:
Video Texture in Note Settings
Saber in Visual Settings
Video in Visual Settings
I would expect it should then work perfectly - it would be good to know if it does not.
I am planning on eventually replacing Unity's built-in Video Player with the more player AVPro framework, and I could potentially make that a higher priority if it's clear that the Unity Video Player is causing serious render issues.
Thank you!