UNIFY DOES NOT RETAIN KEY IN STUDIO ONE 4.6 (WINDOWS 10 64-BIT)
When re-opening a song within Studio One, the instantiation(s) of UNIFY within the song load properly with the correct patches, but the key of the song is not retained, leaving the patches to incorrectly play in a different key. I have to open the UNIFY browser, click on a different patch and then click on the desired patch to make it play in the key of the song.
Is there something I can do to correct this issue?
Are you running Unify v1.0.12?
Does this happen with every patch, or just certain patches? Please specify one patch that does this.
When it does happen, can you please check the global transpose setting, which appears at the very bottom right corner of the ShowMIDI view. ( https://pluginguru.net/unify/manual/doku.php?id=showmidi ) and let me know if it's not coming up set to "0".
Thanks for the prompt response!
Yes, I am running the latest available version (1.0.12) and the patches I am using are of the BPM category:
chord dance 2a
chord dance 2b
Also, Always Dreaming... from the BELL category
Lastly, yes the global transpose setting is coming up set to "0"
Does it seem to you that Unify is coming up with a non-zero global transpose amount, even though it shows as zero?
If so, is the transpose amount always the same, or does it come up differently each time?
This could be a result of the interim version of BlueARP we shipped with 1.0.12.
Please download the latest from http://graywolf2004.net/wp/?page_id=35 , and put the file BlueARP.x64.dll in C:\Program Files\PlugInGuru\Unify\VST, overwriting the existing version, and try again.
Sadly, the latest version of BlueARP did not resolve the issue and yes, the transpose amount is always the same when loaded. It's always displayed as zero.
Also, I noticed that though the patches load properly but are not in the same key, I lose any edits I've made because I have to open the browser, select another patch, and then select the desired patch which now loads in its default state and not as the edited version. This makes sense because I select a different patch prior to selecting the desired patch, but I wanted to bring the issue to light.
I am very sorry to hear that you're having this problem. I can only fix it once I understand exactly what is happening, and ideally, if I can reproduce it.
Could you possibly create a very simple Studio One project, using only the Unify factory patches you mentioned, which has this issue, then zip it and post it here? If I can manifest the issue on my own system, I can analyze what's happening.