Same row property reset when pasting multiparameters into MXXX ?

[al808]

Hi, hopefully someone can enlighten me as to if I'm doing something wrong.

When I add an instance , let's say of MSpectralDynamics to MXXX, and then using the manager from the multiparameter menu, paste into MXXX a whole bunch of multiparameters I'd previously set up in MSpectralDynamics, it works all fine except for the need reset again the values for the "same row" GUI properties, that don't seem to be carried on from what I had setup in MSpectralDynamics.

Is this the expected behavior, or is there a setting I'm overlooking somewhere ?
I'm on a mac mini M1 using rosetta , Logic and V15.

Thanks any help, cheers Al.

[MeldaProduction]

Hi Al, well, I just tried and it seems to copy everything. Perhaps a screen video? (update to the newest version too of course)

[al808]

Hi Vojtech and thanks for your time.

Basically, I might setup some personalized multi parameters for different plugins, and at some stage possibly combine some of them into an instance of MXXX. With the help of the multi parameter manager, I'll then copy the settings from the individual plugins and paste them into MXXX , which might require some minimal additional editing depending on how the MXXX is structured, but certainly saves a lot of time compared to having to redo all the settings from scratch.

As far as I can tell, the "same row" setting defaults to on, regardless of the adjustments I had pasted in from my initial plugin-level multi parameter values, which admittedly is no show-stopper.

I get this on a mac mini M1 and also on a boot-camped windows 10 partition I briefly tested, which says to me that this is by design, and that my understanding of the Melda eco-system is still incomplete at this stage.

As suggested I uploaded one riveting video, where I open up a customized instance of MSpectralDynamics, copy it's multi-parameters, open the same preset in MXXX, paste the said multi-parameters, flick to the easy screen, and shock-horror, all the multi-parameters are perfectly aligned. I then proceed to open a few multi-parameter windows, revealing some of the offending same-row settings .Finally, and not wanting to part on such an inharmonious note, one is then presented with a previously re-worked version of the MXXX , where the original same row attributes have returned, and peace and harmony now restored.

Cheers Al.

[al808]

Hi Vojtech,
So, do you have the same behavior on your machine ?
Thanks Al.

[MeldaProduction]

Aaaaha, now I understand. Indeed there seems to be something fishy with pasting to MXXX from a different plugin. I'll check!

[MeldaProduction]

Bad news! The default value for this option is inversed for MXXX, some backwards compatibility reason, so I'm afraid I won't be able to fix this one. Copying MPs from plugins to MXXX will just leave the Same row switch incorrect.

[al808]

Hi Vojtech,
Thanks for looking into this. I think I managed to copy the multiparameters of MDynamicsMB correctly with the proper Same Row data into MXXX by using a text editor. If it's of any interest:
If I understand correctly, MdynamicsMB uses Same Row =1 whereas MXXX uses Same Row =0, so :

1 - mark the same row =1 that we'll get rid of later :
search for ( " GUISameRow="1" Index ) and replace with an arbitrary value ( tindex )

2 - find the spots where there was no Same Row data and insert the Same Row=0 that MXXX wants:
find (" Index) and replace with (" GUISameRow=“0” Index)

3 - finally get rid of the temporary arbitrary value marking the deleted Same Row =1 from step 1:
search for (tindex) and replace with ( " Index)

Yay !

[Held]

That's a great workaround, but this could also be automated if MXXX simply inverted the same row value when copying and pasting.

That way, the copied format would be consistent while MXXX could keep its backward system for backwards compatibility.

[MeldaProduction]

Hehe good job

I could certainly mark it always, but the problem is, I'm trying to keep the settings size as small as possible. But I'll think about it, it's a bit unfortunate this one.

[Held]

I could certainly mark it always, but the problem is, I'm trying to keep the settings size as small as possible. But I'll think about it, it's a bit unfortunate this one.

Would that really need to be a setting? I doubt anyone actually wants the current behavior. I don't know how exactly you've implemented the copy and paste functionality, but wouldn't a special case for MXXX that flips the GUISameRow bit/string before serialization and after de-serialization be enough?

[MeldaProduction]

No no, the stored settings. I'm pretty sure you want the plugins to remember the "Same row" state . Let's just say if the plugins would store everything, the projects using them would become huge and would take quite a long time to load. So only "nondefault" stuff is stored.

[Held]

I see. That makes sense. But still, the representation of the "same row" state in the save wouldn't have to change if you only change the representation in the clipboard and leave everything else as is. Or maybe I'm missing something here.

You know your code best, and I hope you'll figure something out