SeeMusic fps very low

Got it.

1. I can see that you're rendering out in the most recent test at 4K resolution, Best quality, 60 FPS. This is an extremely high resolution, and the speed that you're seeing in the render is actually normal for that setting. Decreasing the resolution to 1080p or 720p will drastically increase the render speed. Changing to 30 FPS will cut the render time in half. If you really need 4K, 60 FPS, you should first do a lower resolution render to check everything, then only render out at 4K 60 FPS when you are ok with leaving the render an hour or two to complete.

2. I've just done more testing on Windows, and am completely unable to replicate a performance difference between the earlier versions and the 4.0 versions - the performance on my computers is identical. I'm not saying that there isn't possibly something happening on your computer - just that it's highly unlikely I'm going to be able to identify or help with what is happening. If something is happening, it is most likely related to something that changed in Unity relating to your specific computer hardware. I unfortunately have absolutely no control over the changes that Unity makes to its framework.

I wish I could be of more help, but unfortunately this is likely all the assistance I can offer at this time. You're welcome to use one of the earlier versions, and I'm always happy to refund and cancel a subscription at any time.

Thank you

It looks like the newest version of Unity has resolved the bugs that prevented me from using the newest release in Version 4.0 previously.

Could you please give this newest build a try, and let me know if it resolves the issue at all?

https://www.dropbox.com/s/gsnyq8yabzvwhke/SeeMusic%20Windows%204.0.6.zip?dl=1

Thank you

Got it, yes I see that now.

This is likely due to a Unity issue then. Recent versions of Unity have been plagued by issues. I'm hoping there will be a stable version that I can update the app with soon. I will continue to look into this and update this thread when there is an update.

Thanks for your assistance.

Thank you.

It would be very helpful if you could do a comparison video like the one you did, showing the difference in rendering time between just 3.8.3 and 4.0.5, with ALL of the effects disabled, especially Particles and Saber.

If it turns out there is no slowdown / difference in rendering out a video with all effects disabled, please try slowing reenabling each effect one by one, especially Particles and Saber, to see if you can isolate which effect is causing the slowdown.

This will help me understand if the issue here is changes made by Unity in the Unity framework, or a change made on my end to a specific effect. Often this kind of performance issue on a specific computer is related to a Unity issue.

Thank you

What version of Windows are you running? Can you please send a screenshot of your system specifications?

Thank you

Trying to help you with this - here are a few points from further investigation:

- I'm unable to replicate the performance difference between 3.6.2 and 4.0.5 with the basic visuals on the Windows system I have available for testing. I'm not saying there isn't one on your computer - just that I'm unable to easily replicate it, which is why this wasn't an issue I have noticed before releasing a version.

- There were absolutely no code changes that could have resulted in a performance shift between versions 3.6.2 and 3.8. I'm not saying something didn't happen - just that there were no code changes that could be responsible for it. There were certainly bigger code changes that could have affected performance with the Version 4.0 release. However, they almost entirely relate to advanced effects that can be disabled.

1. Could you please try Version 3.8, and verify specifically what is happening, with total certainty, between Versions 3.6.2 and 3.8?

https://www.dropbox.com/s/1fpvr4v8nygwzp0/SeeMusic%20Windows%203.8.3.zip?dl=1

2. The rendering time issue in Version 4.0.5 seems very strange. Is this with a piece with no video and effects? Can you please post a video capture showing a short preview of the piece, and then your attempt to render it in 4.0.5?

Even better, if you can post a video of an attempt to render in 3.6.2, then cancel and close, reopen in 4.0.5, and reattempt to render, that would be the most helpful.

Thank you for your assistance, I'll do my best to help.

Please try running Version 3.6.2 and send a video of exactly the same process as this video, showing the difference in performance -

https://www.dropbox.com/s/u4skv9zf60v9ssg/SeeMusic%20Windows%203.6.2.zip?dl=1

Thank you

Logs would not be useful here. Please explore the recommendations I provided in the previous response - Thank you!

Ok - screen capturing with OBS is going to require a LOT more processing power. The slowdown is almost certainly not related to the app update.

- The single feature that would be most likely to cause lag would be the Particle Rays. Particle Rays should only be used to render out videos, not for realtime streaming. Please make sure Particle Rays is disabled in Particle Settings.

- In general, if you want to reduce lag, try disabling some or all of these effects in Effect Settings:

- Texture

- Glow

- Saber

- Particles

Initialize engine version: 2019.4.22f1 (9fdda2fe27ad)
[Subsystems] Discovering subsystems at path C:/Users/xxx/Downloads/SeeMusic/SeeMusic_Data/UnitySubsystems
GfxDevice: creating device client; threaded=1
Direct3D:
    Version:  Direct3D 11.0 [level 11.1]
    Renderer: NVIDIA GeForce RTX 3070 (ID=0x2484)
    Vendor:   
    VRAM:     8043 MB
    Driver:   27.21.14.6627
WARNING: Shader Unsupported: 'Hidden/Universal Render Pipeline/ScreenSpaceShadows' - All passes removed
WARNING: Shader Did you use #pragma only_renderers and omit this platform?
D3D11 device created for Microsoft Media Foundation video decoding.

I'm guessing this is the relevant error from the player.log too >.<

My bad, didn't realise OBS wasn't recording the video