Definitely not a MINOR oversight. MDelay

[zuhizuhi]

If you set 1/4 straight, you get 1/4 straight. If you set 1/4 dotted, you get 1/8 (!!!) dotted, not 1/4. The same goes with any other note lengths. One would assume if you set the dotted type one would get this DOT added to the selected length, not shrunk one step down with a dot, that's only logical.

[_al_]

And what's even weirder...
If you switch off tempo sync and double click the rate knob, alongside being able to type in a rate, you can also choose "synced" rate. (For example 1/4, 1/4D etc)
If you select 1/4 D from that menu, you'll find it plays the proper dotted time.
So clearly Vojtech knows how a Dotted should sound.

Been like that for ages (years, I think?). I think the problem is that it was left unreported for so long, he wouldn't be able to fix it without breaking everyone's project.

I guess that was due to the fact, his plugins were so complex, and his user base was so small, he didn't have enough beta testers to catch weirdness like this.
And if I'm honest, I didn't notice it it either. If I wanted a dotted sound, I would just turn the dial until it was at the speed I needed. I mean, I knew 1/4D should be next to 1/4 Straight, but I didn't really think about whether it should be to the left or to the right. Maybe everyone else was the same, hehe.

But yeah, it does look kinda amatuer.

Pretty sure it was reported one time.

But hey, just double click the rate and select 1/4D from there, for correct timing, if that helps.

[zuhizuhi]

And what's even weirder...
If you switch off tempo sync and double click the rate knob, alongside being able to type in a rate, you can also choose "synced" rate. (For example 1/4, 1/4D etc)
If you select 1/4 D from that menu, you'll find it plays the proper dotted time.
So clearly Vojtech knows how a Dotted should sound.

Been like that for ages (years, I think?). I think the problem is that it was left unreported for so long, he wouldn't be able to fix it without breaking everyone's project.

I guess that was due to the fact, his plugins were so complex, and his user base was so small, he didn't have enough beta testers to catch weirdness like this.
And if I'm honest, I didn't notice it it either. If I wanted a dotted sound, I would just turn the dial until it was at the speed I needed. I mean, I knew 1/4D should be next to 1/4 Straight, but I didn't really think about whether it should be to the left or to the right. Maybe everyone else was the same, hehe.

But yeah, it does look kinda amatuer.

Pretty sure it was reported one time.

But hey, just double click the rate and select 1/4D from there, for correct timing, if that helps.

No doubt the developers do know how Dotted should sound They just missed it out. And yes, selecting length via freerate it's another whole story, moreover, many other plugins have this right (soundfactory, oscillators, rhythmizer), so yes, it's just an oversight. But still needs to be fixed I think...

[_al_]

Yeah, honestly, I would rather he fixed it and broke my projects, rather than just leave it.
Was definitely reported on the forums. I remember it.
Maybe email him, if it really bothers you?
I always got very fast and helpful responses when emailing.

[mabian]

Yeah, honestly, I would rather he fixed it and broke my projects, rather than just leave it.
Was definitely reported on the forums. I remember it.
Maybe email him, if it really bothers you?
I always got very fast and helpful responses when emailing.

I hope they are able to fix the behavior and detect if settings were saved by an older version of the plugin and, if the case, adjust so that the delay actual length stays the same while the parameter value is the new (correct) one for that length.
Example: loading settings with 1/4 dotted (which actually sounds 1/8 dotted) from a bugged version? Ok, set the delay to 1/8 dotted in the GUI reflecting the actual parameter value.
From then on no further adjustment needed (and yes if you go back to previous version it breaks).

- Mario

[vanerio]

Some time ago I reported that the MSoundFactory tremolo had the phase reversed. Vojtech replied that it was better to leave it that way due to backward compatibility.
Honestly, I'd rather, as _al_ said, have the bugs fixed than keep backward compatibility for things that do not work correctly.
It is strange and, in my opinion, wrong, to adapt your thinking and the way you work with plugins to malfunction.
I vote for solving it!

[Held]

Installing a new version, and suddenly have different delays in all my projects would be a nightmare. So I appreciate a focus on backwards compatibility. That being said, this is a labeling issue and could be changed without changing the sound of any existing projects.

The only ways to clean up other mistakes, that do affect the sound, would be a clean break and introduce MeldaProduction 2.0 with consolidated versions of all EQs and other multi-version plugins. Maybe get a talented UI/UX designer and finally put all the GUI complaints to rest

Maybe with the MixingRevolution or something.

[FTsounds]

My vote is for backward compatibility. A label is just something the producer sees, but a sound is something everyone experiences.

Out of curiosity, it's the same with MTurboDelay too?

[Hexspa]

I was one of the people who requested that the delay values be corrected, and yes BC was the answer. A good reason to fix it is that sometimes you use multiple delays, and you know in your head what you want, especially if you have internalized rhythmic values. It's less convenient to turn the delay up and listen to each one to remember which is which. So, I still think it's worth labelling things correctly.

[mabian]

If somebody can read my previous post, BC can be preserved as well as the behaviour can be fixed. In reaper adjustments like this have been done various times. Of course the plugin must be able to detect the version that was used to save settings in order to adjust accordingly. And once fixed you can't go back. But if you see Melda version notes they broke BC several times, for example with automation, as plugins went under major updates. Or, they could just release a V2 delay with the right labelling. There are options.

[Xichael]

Looks like this is the case in other pugins too. Just noticed it in MVibrato. Honestly makes me a bit warry to use their plugins. What other inconsistencies are hiding throughout?