Replies: 1 comment 1 reply
-
Yes, that should be safe. Any songs saved with community will not load on official however.
If you can, uploading a .zip with the "collect all" (so song.xml and samples in the folder that collect all creates, see the official manual for how to do this) would be helpful. That way, we can try to narrow down where the sound has changed and why. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello,
I just tried community version 1.2.0 and I suspect number of my tracks sound somewhat differently than on official 4.1.3.
There are definitely lot more of cut off notes than previously - so obviously polyphony with community version is reduced significantly, what I can understand as more features require more resources from CPU, but it also seems there are also some notable changes in sound balance in some tracks - perhaps it is because my tracks are 100% midi (I don't use audio) and I use saturation a lot, which I guess can introduce instability - I noticed this already with official fw that changing saturation by 1 could drastically change the sound.
So my question is -
• is it safe to revert to official firmware, by just replacing fw bin file and rebooting with shift+power on?
and also
• is there some safe mode in community version settings or guidelines allowing to sustain sound compatibility with official firmware?
Beta Was this translation helpful? Give feedback.
All reactions