Anyway, I am afraid to report that all three versions of the new beta respond the same way. One difference is, when the editor is first launched in Cubase, it shows that Editor window saying “The Editor cannot connect to the hardware. Please connect…” but you just hit continue because it is connected. This is something new that wasn’t happening before and it doesn’t happen every time. Again, it’s connected but the message randomly pops up when first launched.
The latest midi drivers (3.30.0.0) are installed as well as the latest firmware and software. Here is a screen of the settings:
let me know if there is anything I can do or test.
Thanks for your work on the new editor, I am sure we can get this thing working smoothly.
I didn’t realize you had emailed a new version (2.0.0b2) until a few minutes ago I am happy to say that automation is working like it should in Cubase now!
Yes! Good times
Appreciate all the hard work on this one. I will do some more testing this weekend to see if I run into anymore issues.
As of that post I wasn’t but today I installed b2 and it seems to be working ok. Used it for about 15 minutes and no errors came up (with error reporting turned back on in the prefs.)
So one of the things I have noticed that I am not sure if you would classify as a bug or maybe a feature request is that when opening a saved song in Cubase (possibly other DAWS too?), the last sound created on the SPHE isn’t being recalled when the song is opened. It seems to work if I create a preset right before closing Cubase and then save.
Not sure if the SPHE has a way to call/load a sysex message when opening a song so that all the controls reflect the way it was saved? Basically the way any standard vsti works.
When you are working on a track inside a DAW, you want to just be able to save the song with the current settings being recalled the way you last had it. At least in my opinion. Maybe some other users can chime in here with their comments/ideas.
It should keep the SPHE settings as they were by the time the project was saved, and recall both the settings and sound when reloading it. I will check into this, thanks!
Create a new Cubase project and add a Sub Phatty track. Select a patch, create a midi pattern, then change the patch settings so that it’s quite a bit different than the original patch. Save the song.
Open up the SPHE standalone outside your DAW. Select another preset, doesn’t matter which one so long as it’s something different. Close out of the SPHE
Open Cubase and reopen the track you created. Hit play. The patch that plays is the last patch I selected in the stand alone editor even though the SHPE is showing the correct patch with the adjusted settings you made before saving the song.
For me the vst effect and instrument have this issue.
So I just tried 2.0.0b3 and it did fix the issue of the above problem but I am still experiencing a fairly major Cubase issue.
Start a new track using either the SP effect or instrument
Load up any preset, in this example we will use factory 1-1
Arm the track for recording and read/writing automation
Start recording a midi track, start tweaking knobs, really messing with the preset while you are playing, go pretty crazy.
Stop the recording.
The SP won’t start back from the preset at which it began. For some reason, some of the controls (Filter Cutoff, EG Amount, etc.) will be completely turned counter clockwise.
I tried this with a few different presets with the same results.