[SPHE] Editor v1.1.0 fails under Cakewalk Sonar Platinum

Hi all,
I am having issues with the latest version of Sub Phatty Editor ‘VI’ (v1.1.0) under SONAR Platinum. The earlier version VI used loads under SONAR, but the new versions fail to load or fail the VST Scan. I would love to use 1.1.0 with the fixed ‘Midi Channel other 1’ bugs because I prefer to use Channel 4 for me SP.

More details…

Sub Phatty Editor Release 1.0.3

Sub Phatty Editor-VI(x64).dll - Working in Sonar, but automation only works when SP set to Midi Channel 1

Sub Phatty Editor(x64).dll - Working in Sonar, but automation only works when SP set to Midi Channel 1
MIDI forwarding does not work - when ‘MIDI Out’ of the plugin is enabled in
Sonar, playing keys on SP do not appear to be received by Sonar.

Sub Phatty Editor-VI(x86).dll - Working in Sonar, but automation not supported (VST Bridge Limitation)

Sub Phatty Editor(x86) - Working in Sonar, but automation not supported (VST Bridge Limitation)



Sub Phatty Editor Release 1.1.0

Sub Phatty Editor-VI(x64).dll - Will not load in Sonar. The plugin manager tries to scan it, but something fails.

Sub Phatty Editor(x64).dll - Working in Sonar. Automation works whatever Midi Channel the SP is set to.
MIDI forwarding does not work - when ‘MIDI Out’ of the plugin is enabled in
Sonar, playing keys on SP do not appeart to be received by Sonar.

Sub Phatty Editor-VI(x86).dll - Will not load in Sonar. The plugin manager tries to scan it, but something fails.

Sub Phatty Editor(x86) - Working in Sonar, but automation not supported (VST Bridge Limitation)

So it appears there is something broken in newer VI from the previous VI.

Regards,
Chris

Thanks for the information. I’ve added this to our list of current bugs.

PS. At the end I mentioned an 2nd ‘mini’ issue with the SPE in plugin mode where Sonar Platinum didn’t want to send midi notes to the SPE via its ‘VST midi input’. This mini issue has been resolved. I don’t know if it was the upgrade to Firmware 2.1.9, the new mutli-mode driver or just a bug in Sonar where a reload of the project fixed it. I suspect the later, as it seems unlikely the firmware or USB driver could have influenced this.
Cheers,
Chris

Thanks for the update.