Chris PresnellWhen I add EZD3 to a Reaper project in Windows, the plugin can not be opened when I switch into MacOS. If I add EZD3 to a Reaper project while in MacOS, the plugin is not openable when I switch to Windows. So the plugin instance can only be opened when on the same platform it was instanced on (windows to windows, mac to mac). I’m using Windows 10 and 11, MacOS Big Sur and Reaper 6.70 along with EZD3, latest version as of this moment.
When I try the same thing using Pro Tools 2022.10 with the AAX version of EZD3, no problems. I can open the plugin from either Windows or MacOS and it doesn’t matter what I was running when I added the instance to the test session.
Is it a VST3 issue or is it specific to Reaper? I don’t have Cubase installed on Windows (no hard drive space left) so I can’t check the VST3 of EZD3 in Cubase.
When I add EZD3 to a Reaper project in Windows, the plugin can not be opened when I switch into MacOS. If I add EZD3 to a Reaper project while in MacOS, the plugin is not openable when I switch to Windows. So the plugin instance can only be opened when on the same platform it was instanced on (windows to windows, mac to mac). I’m using Windows 10 and 11, MacOS Big Sur and Reaper 6.70 along with EZD3, latest version as of this moment.
When I try the same thing using Pro Tools 2022.10 with the AAX version of EZD3, no problems. I can open the plugin from either Windows or MacOS and it doesn’t matter what I was running when I added the instance to the test session.
Is it a VST3 issue or is it specific to Reaper? I don’t have Cubase installed on Windows (no hard drive space left) so I can’t check the VST3 of EZD3 in Cubase.
IhundaIs there an update on this? I am having the same issue with Ableton Live between mac and PC.
I was fed up of paying for apple hardware prices so I built a windows pc for my studio but I still collaborate with Mac users. Out of dozens of plugins, only EZDrummer 3 cannot load on a different platform it was saved with. That’s a big BUG in my opinion and should get a workaround ASAP…
Maybe another optional plugin with a compatible name on the Windows or Mac side?
AnindoHi! Seems like this issue has been around for a while and now I am stuck with a project that needs me to switch between my Studio Windows 11 machine and my rehearsal machine on the M2 Macbookpro. DAW – Cubase 12 on both machines.
Dear Coders, PLEASE help us out! Is there any id tag or renaming option or something possible to work around this? Saving presets and reopening them along with the vst instrument track settings every time is going to be a nightmare!
Thank you in advance for looking into this!
Glenn Stantonthe plugins in Mac and Windows are wholly different code… so you wouldn’t be opening a Windows plugin on a Mac and vice versa… and running emulations of OSes is often a recipe for problems…
but if the issue is project file compatibility, that is something the dev team should look into as (imho) the project files should be OS/DAW agnostic.
Glenn
www.runnel.com
www.reverbnation.com/fossile
Paul MorganIF you check back previous posts in this thread you’ll see that this is a problem with EZD3. You can in fact open a project file from Reaper or other DAW’s between windows & macos as long as the vst3 of the said plugin is installed on both systems. For instance my cubase projects with Kontakt & other vst3 plugins do open as expected on my PC & macbook. This wouldn’t be the case if your running Reaper on both windows & mac but only have the AU versions of the plugins installed on your mac & none of the vst3 versions.
For some reason toontrack have decided not to make EZD3 & some other of their plugins cross platform like a lot of other plugins are as mentioned here:
Unfortunately, we would not be able to fix this without breaking all user projects on one of the platforms. 🙁
“Only” EZD3 and EZbass have this issue, not SD3 and Audio Sender.
We are considering an opt-in solution for this issue for a future update of EZD3 (and EZbass).
1
Thanked by: Brad
ProsectorHaving the same problem with Reaper and EZ Drummer 3: track managed on Mac can’t be opened on Windows. It’s a really annoying problem for me, would be grateful for a fix or workaround.
SZimmiePlease define what this ‘opt-in solution’ might look like?
SZimmieI hope this helps someone else save some time and frustration.
This works in Studio One:
1) Save the EZD preset on the PC, and copy it to the Mac.
2) Open the newly copied PC project/song in Mac, and ignore the ‘missing device’ error.
3) Create a new instrument track, and drag EZD3 to it.
4) Copy the midi from the old EZD track to the new.
5) Restore/load the EZD preset on the new track.
6) Add the multi-channel tracks for the drums on the new EZD track.
7) Now you can copy and paste the channel settings from the now defunct drum tracks to the new tracks.
Glenn Stantonor just export the drum track MIDI and load it into the other OS project? or are the Reaper files not compatible across OS?
Glenn
www.runnel.com
www.reverbnation.com/fossile
SZimmieFor me it was more than just a midi issue. I use the multi-channel option on EZD and bring in individual tracks for the kick, snare, hh, overheads, etc. each track is different and eq’d with compression, saturation, etc. I probably spent way too much time them, but they sound perfect for each song.
ShidoStrifeAre there any updates regarding this issue? If there are opt-ins, I definitely would love to. I switch back and forth between Windows at home and Mac at work and need it to be editable seamlessly whenever I sit down on both computers. Exporting WAVs or MIDI is NOT a solution.
Chris PresnellNo, there aren’t any updates. Seems like Toontrack screwed up and used a different plugin ID code on Windows and Mac for EZD3. So if they changed that ID on one platform, that would break it for all existing sessions/project on that platform. Only solution I can see is to wait for EZD4 and hope they don’t repeat that same critical mistake.
I posted the workaround earlier in this thread. Just be sure you save your EZD3 settings along with your DAW session/project file. Then once you open the file on the other computer platform, insert another EZD3 instance on the same track (so it will share all MIDI data, FX and track routing) and load that EZD3 settings file you saved while booted in the other computer platform. So in the end, you’ll have a disabled instance of EZD3 inserted while booted in the other operating system plus one instance that works fine. When you switch back to the other platform, the instances will be reversed as far as which one is disabled but it should continue to work fine. If you make any changes to EZD3 settings, be sure to re-save the settings and re-load them when you get back to the other operating system.
Yes, it’s a few extra steps. Yes, it’s not seamless. Yes, it works.
2
Thanked by: ShidoStrife and Glenn StantonChris PresnellThere is one other way to get around this issue but you probably won’t like it… the AAX version of EZD3 doesn’t have this issue so if you use Pro Tools, cross-platform sessions work FLAWLESSLY.
For me, that’s fine when I’m working with other studios but the local musicians where I live are using less expensive DAW’s and that means I still deal with the VST issue.
Another way that I get around this issue is I’m running a 2018 mac mini with BootCamp so I can boot into either macOS or Windows 10. I’ve got all my software installed in both partitions so I can simply reboot to open a file made on the other platform. It is a major pain to have to switch OS during a work day, then back again since I prefer to be in macOS for running DAW’s, Windows for 3d design.
1
Thanked by: ShidoStrifeShidoStrifeNo, there aren’t any updates. Seems like Toontrack screwed up and used a different plugin ID code on Windows and Mac for EZD3. So if they changed that ID on one platform, that would break it for all existing sessions/project on that platform. Only solution I can see is to wait for EZD4 and hope they don’t repeat that same critical mistake.
I posted the workaround earlier in this thread. Just be sure you save your EZD3 settings along with your DAW session/project file. Then once you open the file on the other computer platform, insert another EZD3 instance on the same track (so it will share all MIDI data, FX and track routing) and load that EZD3 settings file you saved while booted in the other computer platform. So in the end, you’ll have a disabled instance of EZD3 inserted while booted in the other operating system plus one instance that works fine. When you switch back to the other platform, the instances will be reversed as far as which one is disabled but it should continue to work fine. If you make any changes to EZD3 settings, be sure to re-save the settings and re-load them when you get back to the other operating system.
Yes, it’s a few extra steps. Yes, it’s not seamless. Yes, it works.
EZdrummer version: 3.0.6
Yeah, this is what I have been doing. Basically keep both Mac and Win instances in the DAW project and switch the midi back and forth, saving and transferring the EZD projects if there are changes there. Not perfect, but works.
There is one other way to get around this issue but you probably won’t like it… the AAX version of EZD3 doesn’t have this issue so if you use Pro Tools, cross-platform sessions work FLAWLESSLY.
For me, that’s fine when I’m working with other studios but the local musicians where I live are using less expensive DAW’s and that means I still deal with the VST issue.
Another way that I get around this issue is I’m running a 2018 mac mini with BootCamp so I can boot into either macOS or Windows 10. I’ve got all my software installed in both partitions so I can simply reboot to open a file made on the other platform. It is a major pain to have to switch OS during a work day, then back again since I prefer to be in macOS for running DAW’s, Windows for 3d design.
EZdrummer version: 3.0.6
Unfortunately I don’t use Pro Tools and probably never will 🙁 virtual machine would be too much of a hassle for little gain. It’s not a dealbreaker, just some minor but unnecessary inconvenience.
janodinI’m having the same exact issue. Trying to open a Cubase Pro project that was created in Windows on a Mac, the only plugins that are not recognized out of quite a lot of them are Guitar Rig 6 (due to the fact it wasn’t available anymore in Native Access and had to use GR7 on the mac) and EZ Drummer 3. Fixing the VST Instrument assignment completely wipes out all the multi-channel tracks that were created. Unfortunately I don’t have the ability to do a workaround to save the settings on these projects from the Windows side.
If the opt-in solution is basically to give an option for the plugin to use the same ID as Windows or visa-versa and basically make EZD3 completely cross-platform I’d definitely do it that if it was in the installer, I don’t have any projects started on this Mac to worry about that problem but loading projects created from Windows is a big deal for me.
In thinking about it, it sounds like if you did do the opt-in, then opening a project created on another Mac that didn’t choose to opt-in or upgrade EZD3 yet would break. I’m guessing this would be a very specific use case opt-in? I can definitely empathize with the problem of fixing this for the long term breaking a lot of things right now.
janodinI just thought of an idea, why not just give the option in a patch to install two versions of the VST, one that is a continuation of the existing platform GUID, and one that is for cross-platform compatibility. Obviously the one that is cross-platform compatible would depend on which platform you’re installing on. That way everything will work fine. Seems like a sensible option in the installer. As long as both plugin binaries could share the same purchased EZX and MIDI packs seems sound. I’m sure something in there would be easier said than done, but at least it wouldn’t break anything.
No products in the cart.