AAX patch and VST3 patch not the same when loaded

[MattLeschuck]

I work primarily in Pro Tools but got an itch to fire up Reason as it had been a long time. I noticed when loading one of my patches that is my default Dune 3 preset, the AAX version (which is the correct version) was different than when i loaded the same patch in Reason. You can see in the video the OSC wavetable position is different (may be other things too).

Im on a M1 Mac studio, latest version of Sonoma. Latest version of Pro Tools, and Reason 12. Any info is appreciated here. Makes me a bit reluctant to start a session in Reason using my patches.

https://drive.google.com/file/d/1XP2Ftd ... sp=sharing

[Marcin]

At first glance it looks that patch loaded from template/session in ProTools may not be the same as loaded from patches popup list in Reason. Please check something to be sure. In the ProTools (when the patch is the correct one) please save the patch to a file (DUNE 3's monitor -> PATCH -> "Save Patch As...") and then load it in DUNE 3 in Reason (DUNE 3's monitor -> PATCH -> "Load Patch..."). Is it different then as well?
Also please check if the patch loaded from patches popup list in ProTools is the same as loaded from session/project.

[MattLeschuck]

At first glance it looks that patch loaded from template/session in ProTools may not be the same as loaded from patches popup list in Reason. Please check something to be sure. In the ProTools (when the patch is the correct one) please save the patch to a file (DUNE 3's monitor -> PATCH -> "Save Patch As...") and then load it in DUNE 3 in Reason (DUNE 3's monitor -> PATCH -> "Load Patch..."). Is it different then as well?
Also please check if the patch loaded from patches popup list in ProTools is the same as loaded from session/project.

Marcin,

I just did this and am getting the same problem. I saved the correct patch to my desktop, initialized Dune in Pro Tools, then loaded the patch from my desktop into Pro Tools and Reason. I may install the VST version and see if i still get that issue in Reason. I also tested in Bitwig, and the VST3 is loading the correct settings, so it must be something with Reason. See new video to confirm.

https://drive.google.com/file/d/1PWpoiV ... sp=sharing

[Marcin]

Could you please post here the patch from your Desktop then? Also, if possible, please make some wav sample how it sounds properly for you. We'll check it.

Ah, and one important check more. Please click on the "SYNAPSE DUNE 3" text in the monitor and check the DUNE 3 version you open (in ProTools and in Reason). Thanks!

[MattLeschuck]

Could you please post here the patch from your Desktop then? Also, if possible, please make some wav sample how it sounds properly for you. We'll check it.

Ah, and one important check more. Please click on the "SYNAPSE DUNE 3" text in the monitor and check the DUNE 3 version you open (in ProTools and in Reason). Thanks!

Marcin,

Here is the patch, and i recorded a simple midi pattern from both Pro Tools and Reason. Pro Tools version sounds correct. The Reason one sounds off.

Im using the latest version of Dune 3.620.

Dune.zip

[MattLeschuck]

Actually i may have caught something! The VST3 version is actually Dune 3.610 where as Pro Tools is 3.620. Im going to update and retest. Ill report back.

Edit: Just updated the VST3 version to the latest, and the same problem exists

[Marcin]

Ok, indeed there is some issue with VST 3 in Reason with your patch - though VST 3 in Cubase or Live the patch loads perfectly fine. Something happens in Reason here. We will check this and write back as soon as we figoure it out. Thanks for the report!

[MattLeschuck]

Right on, thanks for being so prompt with everything Marcin!

[Marcin]

Please check PM. A couple of additional questions sent.

[Marcin]

The issue (Reason-only issue) was related to the mishmash of parameter notifications in very rare cases after the program change and will be fixed in the next update. Thank you Matt for your time and checking this!