[MickMad]

Thank you Olaf

I really hope this is something that you both can resolve easily!

[MickMad]

Hi there,

 

I am having quite similar issues as described here; I got the latest EZMix 2 version as well as the latest Reason 10 version, and there’s plenty of issues with the parameters handling, whenever I’m loading a preset, copying an instance or closing and reopening a project with EZMix in it.

 

I opened a ticket with Propellerheads but the issue persists and they said that I should have contacted you too to check on both sides; here’s the issues description that I sent to Propellerheads too:

 

<p dir=”auto”>Now, the first issue happens when selecting presets: if I click on a preset, most of the times the output knob will jump to an arbitrary value that is not the one of the preset; this is confirmed by the asterisk appearing near the name of the preset, and because if I click on the preset multiple times, the output knob will jump back and forth between the preset value and the arbitrary one. Sometimes, the preset will stick to its original values when selecting it.</p>
<p dir=”auto”>Second issue is with ctrl-click on knobs to set them to the default preset value: sometimes it works, sometime it doesn’t, and the knob jumps around as in the previous issue.</p>
<p dir=”auto”>Third issue (as explained originally in ticket): if I copy-paste an instance of EZMix 2, the parameters set in the pasted instance will be set to default values (0dB for input/output knobs, 50% for the 2 other parameters), rather than to the values set on the original instance. As for the previous issues, this is also random; as you can see in the video, when I copy-paste EZMix only half of the parameters got copied correctly, rather than all of them.</p>
<p dir=”auto”>Fourth issue: if I put one parameter to 0%, then save a project, and open it back, sometimes the GUI will show 0% on that parameter but the engine will treat it as if it’s set to 100%. I discovered this while mixing a track: I set an EZMix patch on a track of Tom-toms, they were a bit loud, so I set one of the EZMix parameters to 0% and it sounded good; I then went on, saved, the project, and when I came back to it the drums were very loud, and I found out that indeed the parameter I set was still shown as 0% but it would be treated as if it was at 100%.</p>

Here’s also a video I made that I sent them to further explain the issues: https://www.youtube.com/watch?v=O9CMfCSiEx0

This is their answer on the matter:

Thanks for getting in touch with us!

I’m afraid I don’t have access to EZMix, but generally speaking, there are no user settings in Reason that would change how parameters are handled when loading/pasting/opening a VST instance.
Have you been in touch with Toontrack? Are there any settings that can be made in the plug that would affect how parameters are loaded or reset?

If there is a problem with how EZMix interacts with the Reason VTS integration, they are weolcome to get in touch with our developers and work on how to solve this issue.

Sorry I couldn’t be of any help!

Can you please do something about this? I basically live with EZMix and this issue is quite annoying.

[Author]

Replies