Available now: Tone2 Icarus v3.2

[Examigan]

Maybe I’m not understanding, but you mean opening Mac projects, but on a PC? Wouldn’t it be looking for the versions of plugins that were originally used on the Mac?

[zvenx]

the same version is on both...
I exchange projects between and mac and pc and vice versa all the time..
I only buy plugins that are on both platforms..
I create project on one and open it and do additional work on the other.

With rare exception (like Tal J8 had an issue once that they quickly corrected, Addictive Drums 2 I think also had the issue once, where they accidentally put different plug in id on mac vs pc) but they fixed those..
I am not aware of any other plugin that has this issue.
rsp

The XLN issue:

https://support.xlnaudio.com/hc/en-us/a ... -XLN-Audio

The Tal Issue:

[Tone2 Synthesizers]

These files are cross platform (PC/Mac) and can be exchanged:
- All patches in fxp format (saved from the synth's interafce)
- All arp templates
- All effect templates
- Samples and wavetables in wav format
- Anything else that was saved from within the synth

These files most likely are cross platform can be exchanged:
- Songs that use the VST2 version (depends on the DAW)

These files may be cross platform and possibly can be exchancged:
- Songs that use the VST3 version (for some, but not all plugins; depends also on the DAW)

These files are not cross platform can not be exchanged:
- Songs that use the AU version (there exists no AudioUnit format on PC)

Why is there not always possible to have cross platform compatibility?
- We need to keep downward compatibility with old versions
- We need to deal with technical restrictions of the platforms
- Over the years we've added support for new plugin formats and CPUs (VST3, AUv2, M1 native, 64 bit Intel, 32bit Intel)

Why can the plugin IDs not be changed easily?
- This would break old song projects of hunderts of other customers

[zvenx]

Two Things..
"These files may be cross platform and possibly can be exchanged:
- Songs that use the VST3 version (for some, but not all plugins; depends also on the DAW)"
I sent you guys a demo project.. none of your vst3's are cross platformed in Cubendo...
yes I understand the difficulty of changing the plugin ID now,
but I think it can be done with https://steinbergmedia.github.io/vst3_d ... -interface and do both. I can ask SB for assistance for you if you wish.

You are the only developer that i have that isn't cross platformed in vst3 (your vst2 is afaik).
rsp

[zvenx]

I am curious for which DAWS the vst3 is cross platformed for any of your plugins.
rsp

[zvenx]

I imagine most of your customers use windows, so leave the plugin ID of the windows alone and maybe provide alternate optional mac plugins with the same plugin ID as the windows...
rsp

[Tone2 Synthesizers]

There is no need to spam your demands here as I've already given you a detailed answer.
Please do also note that we do not have a support forum on kvr.
If you have further questions use our company forum or send an email: support[a t]tone2[do t]com

We can build a special Mac version for you with a different plugin ID. But in this case you'll need to pay us for the work as there are only two people[edit] who requested this during the last decade.

[zvenx]

I did contact support, and Troels said there was one other person who had the issue.
I myself was not aware of the issue for a few years because i haven't been using my pc much beyond beta testing.

I am pretty sure your first vst3 didn't come out a decade ago. As I said I didn't have that issue when you were just vst2.

That you think it is a special request to have your plugin work as it should, like almost every other plugin does, speaks volumes.
No I won't be paying for this, i will find another solution.
Tal had a similar issue, they fixed it no fuss.
Xln did too. Also no fuss.
rsp

[Tone2 Synthesizers]

Sorry, I assumed you were the one who had written to Troels. I edited my above post. So now we have two persons who requested cross-platform compatibility for VST3 on PC-Mac.

Sorry, but in this case we can not just change the plugin ID of the VST3 version on the Mac.
It is a very bad idea as this would break existing songs of several hundret other people.

Workarounds:
- use the VST2 version
- dump the track
- Stick to PC *or* Mac in your studio productions

[starflakeprj]

Just so a third person would understand. This discussion is about any musical project you start on one system (MAC) wouldn't be able to transfer to another system (PC) if the project contain Tone2 VST3 instruments? I didn't know this either, since I didn't care before (was using only PC). But out of laziness (I disassembled my PC 3 years ago to upgrade it, but was too lazy to re-build it) I bought a Mac Mini M4 Pro when they were released last year.

It's good to at least know any projects I have started, and will start, using Tone2 VST plugins, won't load when (if ever) I go back to my PC

Edit: Without some hands-on, of course.

[zvenx]

Assuming of course you are using tone2 vst3... vst2's are fine last time I checked... and it may also depend on your host..
(I think Reaper allows you to substitute one plugin from another painlessly from a list you create (I don't use reaper, so I am using memory of what I think I have assimilated from others saying so over the years, forgive me if I am misremembering))

Whilst I imagine I am one of the few who uses both platforms, I am surprised people who collaborate with others on projects haven't bumped into this before.
rsp

[starflakeprj]

I'm primarily a Studio One user, but I also own licenses for Cubase, Bitwig, Logic (which doesn't apply here), Reason (which I run only with Rack Extensions anyway), FL Studio (installed but almost never used), Reaper (licenses until v6 I believe, which is also my least liked DAW), Renoise and Waveform (the latter two rarely get used either).

I assume that you could load the project created in Studio One for Mac on a PC and manually add the Tone2 synth (VST3), just making sure you have saved the preset from the Tone2 synth on the Mac and loaded it on the PC?

I aim to re-build my PC again, and I have taken the decision to not use VST2 anymore, so I hope at least the manual part, mentioned above, is a workaround. I must say I'm also a bit surprised others haven't bumped in to this before either, but I'm no professional, so what would I know

[zvenx]

I assume that you could load the project created in Studio One for Mac on a PC and manually add the Tone2 synth (VST3), just making sure you have saved the preset from the Tone2 synth on the Mac and loaded it on the PC?

yes the manual part works fine. Assuming you don't have automation etc

rsp

[Markus Krause]

You can also dump the audio track of the plugin before you migrate.
This works also when a plugin or plugin format is not available on a new platform.

Also make sure that you use the same version number of the DAW. An older version might fail to load songs created with a newer version.

Further point of failure may be filenames. Especially wav files come to my mind here. Mac/Linux is case sensitive while PC is not. (This issue does not affect our plugins as they store sample data within the patches).

[Hanz Meyzer]

the same version is on both...
I exchange projects between and mac and pc and vice versa all the time..
I only buy plugins that are on both platforms..
I create project on one and open it and do additional work on the other.

Maybe you could hexedit-patch the cubase project file, but only if there is no checksum mechanism or so...

Save a .vstpreset on each of your system. So then you can find out the vst3 plugin identifier. Here how it looks in a vstpreset file saved with ZebraHZ:

Bildschirmfoto 2025-08-08 um 22.12.25.png

So it's this string for ZebraHZ: D39D5B69D6AF42FA12345678534D485A
Will be always on the same position and length in a .vstpreset file.

You could then try to search within your cubase song file with a hex editor, searching for that string (not as hex values!). And then replace all occurences with the other id. No idea if that works... Of course make a copy of your song file first.