2.8 beta2 crashing Studio One 3 with tracks created with 2.7

[Marc2109]

Well there it is, 2.8 crashes Studio One when attempting to load and play tracks made with Zebra 2.7. I didn't test to see if the reverse was true. Tracks will either not play the synth, further fiddling around just locks up studio one. It does not CTD. Anything further I can do to help with resolving this issue?

Windows 10 X64
Studio One 3 latest build
Presonus AudioBox i2

[redplum]

I had a similar experience yesterday. I pulled up an old (drunken) song fragment, made a couple of years ago, because I wanted to see which preset Zebra had been using. I couldn't get Zebra's UI to appear, yet it would play the track that had been recorded. Also, when the song opened I got a message from Studio One about some "missing devices", including Zebra, which I thought was weird since I don't consider VSTs to be devices. And further fiddling crashed Studio One.

It's not a big deal; I mention it because it might be related.

[tasmaniandevil]

Anything further I can do to help with resolving this issue?

Hmm, loading old projects with the new Zebra2.8 works over here, so it should not be a general problem.
Maybe it's just some installation hiccup.
Could you please send a mail to support at u-he dot com?
I am sure we can figure out where the problem lies.

[tasmaniandevil]

Also, when the song opened I got a message from Studio One about some "missing devices", including Zebra

This sounds like it also might be a problem with the update installation, maybe just something connected to installing multiple plugin formats.
If one had installed both, VST2 and VST3 of the previous Zebra2 version, and during the update, only one of the formats was selected for updating, then there might be problems arising. Similarly, if during the update, you decide to install the data portion to a new location, there might also be problems if you still have the old data folder installed elsewhere.

[redplum]

Well, Tasmanian, this is interesting. I couldn't remember which plugin formats I'd selected when installing Zebra 2.7, so I reinstalled 2.8 (over the previous) with all formats, including AAX (Where does it put those? I can't find them.).

The old song opened with a similar message about missing devices (a closer inspection of this message revealed that it couldn't find any of my controllers except the one used on the first track, which wasn't a Zebra track). But everything worked normally. I could bring up any of the VSTs' UIs, edit anything, play anything after reassigning each track/vst to a controller. No crashes (yet).

I saved the song under a new name, quit Studio One, then relaunched it and loaded the newly saved version without any problems at all.

I should mention that yesterday, in a feeble troubleshooting attempt, I opened a new song, loaded Zebra 2.8 and set its default skin back to original. That made no difference to the problem in the old song.

Anyway, I was able to see the name of the preset Zebra had been using, which is why I opened that old song in the first place. An surprisingly, that drunken creation doesn't sound as bad as I remembered. I might work on it some more...

[tasmaniandevil]

The AAX plugins can be found here on Windows:
C:\Program Files\Common Files\Avid\Audio\Plug-Ins\
C:\Program Files(x86)\Common Files\Avid\Audio\Plug-Ins\

That issue with the 'missing devices' message sounds very weird indeed.
Sounds like it could not find the controller assigned to those tracks.
But the plugin has nothing to do with which controllers are assigned to the track, that's all saved in the Studio One project, our plugins can't have any influence on that.

Actually it sounds like an issue with the controller (pure speculation).
Sometimes I get warnings from Studio One on startup that my device setup has changed (or something similar), although it hasn't. And I have to go into the options and set up the controller again.
Did you have a look at the Studio One options, if all the external devices are still set up correctly?
Or maybe the driver for that controller had been updated since you last saved that old project, and that's why it couldn't find the device anymore?
Or did you have a totally different controller installed when you initially created the old project, and meanwhile replaced that controller with a different one? (just poking around in the dark)

I'll go and scratch my head for a little while, see if I can find another lightbulb to shed some light on this.

[redplum]

Please don't scratch your head too hard; I'm good.

I didn't change any controllers, but I did replace the interface, from a Presonus audiobox to the Behringer (with a new driver), and I'm pretty sure this happened sometime after the last time I had that song open. That might explain why my main controller (which uses midi via the interface) wasn't seen, but I also sometimes use a little Akai mini, which is USB, and this was also identified as missing.

However, this Akai, mostly used for drumming, gets moved between DAW computers sometimes. Generally, Studio One's startup screen flags the fact that it's not connected, and the configuration in Options/External Devices remains intact.

I might, out of curiosity, go to my secondary DAW computer (which is similar to my main one) and try to open this song. This secondary computer doesn't have much connected to it: it uses Windows audio, so no interface, and it's main controller is a cheap USB Casio. It does have Zebra 2.8 on it. If I do this, I will post the results in this thread.

Until then, thank you for your help.