Open PC Project on Mac No Zebra 2.5?
-
- KVRist
- 89 posts since 5 Aug, 2010
Ok, i just installed my OSX machine and transfered a Pro Tools PC project and opened it.
The horror the horror!
I cant open my Zebra instances on the OSX machine, this has to do with the VST wrapper on the PC?
I have to solve this by installing the VST to RTAS wrapper on the OSX machine?
Or is there another way?
The horror the horror!
I cant open my Zebra instances on the OSX machine, this has to do with the VST wrapper on the PC?
I have to solve this by installing the VST to RTAS wrapper on the OSX machine?
Or is there another way?
-
- KVRist
- Topic Starter
- 89 posts since 5 Aug, 2010
i installed the wrapper, but Zebra does not show up under the Wrapped files folder, zrev and zebrify does, and i can find both the original RTAS and the wrapped file in the pluginsfolder.
Still the plugin does not load.
Any ideas?
Still the plugin does not load.
Any ideas?
- KVRAF
- 4197 posts since 23 May, 2004 from Bad Vilbel, Germany
-
- KVRist
- Topic Starter
- 89 posts since 5 Aug, 2010
Yes it works, but that's not the issue here.
I have about 200-250 projects made with zebra 2.5 on my PC.
The PC uses the VST to RTAS wrapper to utilize Zebra and shows up in protools under wrapped devices in the plugins menu.
When i transfered one of my projects to the OSX machine and opened it, i got a message from ProTools that Zebra 2.5 could not be opened and i have about 5 channels that have nothing on them now.
So i tried to install the VST to RTAS wrapper on the OSX machine and i opened the project, but this time i get the same message.
I see the wrapped version of Zebra as well as the RTAS version in the plugins list, they are there and working. But pro tools does not recognize the plugin because it is in a different part of the plugins list now. Instead of in the "wrapped plugins" directory it now lies under u-he directory.
So now i have about 200 projects that i cannot edit on my OSX machine without loosing all the automation because i have to load another version of the Zebra.
This means that i have to save all my settings as presets in the zebra folder.
Copy all the automation manually and open a new version of zebra in ALL of the projects = sucks big time.
Unless there is a way to tell Pro Tools that the wrapped version on the mac is the same as the one i use on PC.
Hope this clarifies my problem.
/Christer
I have about 200-250 projects made with zebra 2.5 on my PC.
The PC uses the VST to RTAS wrapper to utilize Zebra and shows up in protools under wrapped devices in the plugins menu.
When i transfered one of my projects to the OSX machine and opened it, i got a message from ProTools that Zebra 2.5 could not be opened and i have about 5 channels that have nothing on them now.
So i tried to install the VST to RTAS wrapper on the OSX machine and i opened the project, but this time i get the same message.
I see the wrapped version of Zebra as well as the RTAS version in the plugins list, they are there and working. But pro tools does not recognize the plugin because it is in a different part of the plugins list now. Instead of in the "wrapped plugins" directory it now lies under u-he directory.
So now i have about 200 projects that i cannot edit on my OSX machine without loosing all the automation because i have to load another version of the Zebra.
This means that i have to save all my settings as presets in the zebra folder.
Copy all the automation manually and open a new version of zebra in ALL of the projects = sucks big time.
Unless there is a way to tell Pro Tools that the wrapped version on the mac is the same as the one i use on PC.
Hope this clarifies my problem.
/Christer
- KVRAF
- 4197 posts since 23 May, 2004 from Bad Vilbel, Germany
OK gotcha... I sent Urs a link to this thread (although he's incredibly busy right now).
- u-he
- 30217 posts since 8 Aug, 2002 from Berlin
Hmmm... that sounds like a serious f*up.
The RTAS wrapper probably can not use my company identifier ("UHfX") that I registered with Avid to tell PT that it actually is Zebra. Hence I don't think the "real" Zebra RTAS on Mac will ever be used.
However, why the wrapped one isn't recognised remains a mystery to me. I suggest to ask Angus/FXpansion about this. Maybe you need to remove the "real" Zebra?
One thing that I never got my head around is why Angus' wrapper doesn't give my stuff mouse events since VST 2.4. The world would be much easier if it did (Angus mentioned that there was a solution, but then he never told me what it was)
Arrgh.
The RTAS wrapper probably can not use my company identifier ("UHfX") that I registered with Avid to tell PT that it actually is Zebra. Hence I don't think the "real" Zebra RTAS on Mac will ever be used.
However, why the wrapped one isn't recognised remains a mystery to me. I suggest to ask Angus/FXpansion about this. Maybe you need to remove the "real" Zebra?
One thing that I never got my head around is why Angus' wrapper doesn't give my stuff mouse events since VST 2.4. The world would be much easier if it did (Angus mentioned that there was a solution, but then he never told me what it was)
Arrgh.
-
- KVRist
- Topic Starter
- 89 posts since 5 Aug, 2010
I tried to remove the original zebra2.dpm from the plugins folder, but it didnt work.
And i also came to think about that ive been using the 64bit beta since it came out (32bit version)
So i tried to install this one, but i couldnt figure out what the problem was, the original install was named zebra2.vst and i got zebra2.dll in the downloader. Are they the same versions or is the beta from 20 decem er still a different version?
Anyways, it feels like there is a small issue here, and it must be easy for someone to test by mqking a zebra instrument channel on pc via the wrapper and then open the pro tools project on a mac, shouldnt take more than 5 mins to do.
And i also came to think about that ive been using the 64bit beta since it came out (32bit version)
So i tried to install this one, but i couldnt figure out what the problem was, the original install was named zebra2.vst and i got zebra2.dll in the downloader. Are they the same versions or is the beta from 20 decem er still a different version?
Anyways, it feels like there is a small issue here, and it must be easy for someone to test by mqking a zebra instrument channel on pc via the wrapper and then open the pro tools project on a mac, shouldnt take more than 5 mins to do.
-
- KVRist
- Topic Starter
- 89 posts since 5 Aug, 2010
I am very surprised with the RTAS version of Zebra for mac.
So far, everything seems to work very well technically, but the GUI is f**ked up. I get all kinds of strange behaviour when fiddeling around with the different knobs.
If i turn the VCF cutoff, the Tune knob suddenly shows that it is turned 75%
And it cant even turn that much when i do it manually. I have had some visual "error" where the entire OSC knob turned into a square. It seems as it shows the background in some way.
Nothing happens to the sound when i doubleclick the knob and it turns back to normal but it looks like Amiga 500 graphics, very annoying.
I am on a Mac Pro 6 core 2010 and OS 10.6
So far, everything seems to work very well technically, but the GUI is f**ked up. I get all kinds of strange behaviour when fiddeling around with the different knobs.
If i turn the VCF cutoff, the Tune knob suddenly shows that it is turned 75%
And it cant even turn that much when i do it manually. I have had some visual "error" where the entire OSC knob turned into a square. It seems as it shows the background in some way.
Nothing happens to the sound when i doubleclick the knob and it turns back to normal but it looks like Amiga 500 graphics, very annoying.
I am on a Mac Pro 6 core 2010 and OS 10.6
- u-he
- 30217 posts since 8 Aug, 2002 from Berlin
Yeah, we definately need to get on top of that. I think something went ballistic because we're still using the RTAS 7.3 SDK. Seems like updating to a newer one is mandatory, but I have no clue how backward compatibility works with Avid...
