Please see the actual release version as Editor v0.9.54 and Firmware v1.1.28.
We have put some real effort recently to make this version as tight as possible, and we actually think it’s good enough for release.
In 1-2 days we will compile the final Editor v1.0.0 and Firmware v1.2.0 and will post again, so you can all give it last verification before publishing.
Fixes in this version:
Fixed #642: Import automatically reloads although it’s been canceled
Fixed #640: A few issues regarding librarian folder focus
Fixed #623: Brown background may appear in Librarian under wrong circumstances
Fixed #645: Preset name changes according to SAVE AS file name
Restore selection in browser
Check sysex BANK size before triggering IMPORT progress bar and GET
Fixed font size for italicized text on librarian right pane
Recalls italicized lines on boot (store in preferences)
Renaming from top menu and hardware presets now makes its row italicized if AUTOSYNC is OFF
Fixed orange ‘active preset’ turning normal grey in center panel after switching pages
I see 2 minor visual glitches that I haven’t noticed before on previous releases. I was playing around with trying to blow up the size of the editor as large as I could make it and noticed them. Not a big deal, but it would also seem easy to fix prior to release.
Yes, this is exactly what I see as well. It’s an old item which has been suspended for this release. The font size should be higher than default and the Editor window should be set to a specific size for this to appear.
I know Reaper is not going to be one of the first DAW supported by the Editor when the final version will be released but I made an interesting discovery to avoid the jumping values issue after automation and consists in bypass the automation lane. This way you can use the Editor without remove it.
I hope this can help some Reaper users in the forum.
I noticed something with this release that i didn’t have before. All the knobs and buttons are working but it seems if i were pushing the envelop latch button we will say i would have to push it 3 times in order for the HW to respond. The synth section and editor would respond and the button would turn on and off in the editor correctly but the HW button wouldn’t reflect the status correctly. And once I would get response from that section it would work fine.
Yes this behavior happened during my whole session last night. Even after a restart and dropping an new instance of the editor in. I was running a 0.9.53 from salvator and i don’t recall it happening in that build. It seem to function correctly until i would let the synth sit a bit then when i would move to a different section in the synth the buttons would react the same way.
I am on OSX
All Local control turned off and all midi filters on (7 bit) for reference
Didn’t happen on synth not connected (USB)
Didn’t happen on standalone
Happens on AU ( didn’t test VST)
So I reinstalled 1.1.28 FW to be sure. Reinstalled the 0.9.53 editor. Seems to happen on this version too. It seems that the editor and the actual “synth” section responds to the buttons but the hardware isn’t getting the midi messages back to turn on the light for the button maybe idk?
Not exactly mine only happens when running with the editor and the buttons reflect status sometimes. In the above mentioned post he said it was happening not connected at all basically. It seems to happen to almost any button at random, the arp sync, latch or arp on too. It happens when connected USB, AU editor running and i can get the problem more frequently if the arp is running and i have the LFO assigned and working so idk it is a midi stream issue or what.
