MMultibandDelay dotted problem

[operator]

Au contraire. It should be fixed with a note in the Release Notes explaining that users using these plug-ins in projects will need to make a change to the dotted value. From, for example, "dotted 1/4" to "Dotted 1/8".

I need to agree...

How far did we come with norms and conventions:
- In Europe we don´t need to change the Train when we go to other countries becasue they normed the distance of the rails so all Trains can ride all tracks.
- We all know how big a DIN-A4 Paper is... (think of the chaos at the beginning of the schoolyear if everybody had a different size of school-book. This could even affect objective grading!)
- Writing the adress on a Letter in the right convention is also very important otherwise the letter may never arive.
- EBU R 128, so we can all listen to the Radio without changing the Volume after every program.

So we see the reason for a convention or a norm is always to generalize and eliminate borders/barrieres. This furthers a common base for a discussion and keeps the focus on the relevant subject.

SAME WITH NOTE NAMES AND LENGHTS! (BTW this is a much older convention than the ones I have listed above.)

For the sake of global and professional communication we should change it to the "right!" values.

[operator]

Maybe we should rather display it in a Multiplier Value than Dot, Trip, etc... (seems more meldaish to me anyway) This way it could be avoided that wrong values are shown intentionally AND it would stay backward compatible.

A true 1/8 dotted Delay would become ---> 1/4 | 0.6667 (or 66.67%)
[U-he Hive Manual: For triplets, set 75% or 150%, for dotted times set 66.67% or 133.33%.]

In U-he Hive`s Sequencer it is also only possible to dial in dotted or tripplet via percentage. And the new Timeless3 from FabFilter also has a percentage offset... (but also has classic dot, trip, etc...) So there would be other software out there who already uses this convention too. Therfore it wouldn´t be something completly new... like the current solution.

[Held]

Au contraire. It should be fixed with a note in the Release Notes explaining that users using these plug-ins in projects will need to make a change to the dotted value. From, for example, "dotted 1/4" to "Dotted 1/8".

I meant it's a bigger project to program and test those changes. And MTurboDelay has a lot of devices that would have to be reworked.

Maybe we should rather display it in a Multiplier Value than Dot, Trip, etc... (seems more meldaish to me anyway) This way it could be avoided that wrong values are shown intentionally AND it would stay backward compatible.

Having a multiplier instead of fixed values could be nice. And then a popup menu that helps you select a multiplier for dotted, triplets, etc like we have at the moment for frequencies where you can select notes. I agree that would be much more Melda like than the current system.

[stearine]

I meant it's a bigger project to program and test those changes. And MTurboDelay has a lot of devices that would have to be reworked.

Is it really?

Not sure if this makes any sense as I can't find MMultibandDelay to see for myself, but why not just change the symbol representing the value, instead of the value behind the symbol. Like renaming a pointer. Then mention it in release notes that there has been a cosmetic change.

[Held]

Is it really?

It's not just MDelayMB, it's also MTurboDelay, MSpectralDelay, and everything else that can get synced to tempo like envelopes, modulators, delay and feedback modules inside MXXX etc.

I hope no one is suggesting to only change MDelayMB while leaving everything else as it is.

[DarkStar]

Of course not. I'll guess that the dotted-code is in the Kernels anyway. If a lot of devices need to be reworked, then Vojtech would need to come up with some sort of batch utility to convert those devices. Or make the change and introduce some meta-data to indicate whether the original or new dotted standard is being used.

[Held]

The more I think about it, the more I like the idea of a length multiplier instead of the fixed options triplet, dotted, tuplet (which should be duplet, by the way. Tuplet is the generic term for duplet, triplet, quadruplet etc.)

The options "Modify" and "Count" which I don't find intuitive at all could all be condensed into a single multiplier value simplifying the whole thing.