Finishing the multi stage modulation envelope

[infuzion]

Allthough I have always wanted all sustain points to move vertically in sync with a key pressed or similar. eg. shift+click&drag.

There is a right-click menu to do that for the start & end points. Feel free to [CTRL]+click to select multiple points to drag all at once.

[aliasant]

Allthough I have always wanted all sustain points to move vertically in sync with a key pressed or similar. eg. shift+click&drag.

There is a right-click menu to do that for the start & end points. Feel free to [CTRL]+click to select multiple points to drag all at once.

I will the day I actually start putting that synth together.
Estimated release date is Jan 1 2046.

[infuzion]

Allthough I have always wanted all sustain points to move vertically in sync with a key pressed or similar. eg. shift+click&drag.

There is a right-click menu to do that for the start & end points. Feel free to [CTRL]+click to select multiple points to drag all at once.

I will the day I actually start putting that synth together. Estimated release date is Jan 1 2046.

Most of the modules you need are already inside the OSM; Presets/* Array/Advanced Float Array/VST Param/Locked Move. And you will have to go inside LeftClick Drag, create a new array if a qualifier key is presed if "Click on Point?". I'd do it, but I'm already busy. Good idea though!

[infuzion]

I forgot to report this but before, but:
1) Properties:MAX ENV POINTS is pre-set set to 64, but could & should be changed as needs arise (most envelopes IMHO could & should be set to 16, 32 max; smaller arrays in SM, the better. However, if you want to use the MSME for song-long modulation like you find in DAWs, one can use more points)
2) Shape routines (Save,Load,Copy,Paste) are hard-coded to 64 points (see Parse and Split module), & there is no markup or "Variables" info to set how long the points-array should be as I can tell.

I would like the .VCS (saved array) file & copy/paste to hold the vector length size, so the MSME can load different sizes, & just truncate if the .VCS is too long.
Exo or whoever added the shape routines, is there a spec-sheet on all the items used in the "Variables" please?

I added in my current GUI bug-list.

[infuzion]

Is it a bug or a feature? The sustain is only looping the end point? When I set the start to full and the end to zero it drops silent, and when I set the start to zero and the end full, it swells up as it should, but doesn't repeat and keeps sustaining at full volume.

Confirmed. Can't be a feature or?

OK, I isolated the behavior: seems the sustain-loop is forgetting an end point. You can test this by having a 3 point sustain-loop (including the Start & End), playing, then deleting the middle point, play a few times, then re-adding the middle point. Happens at least to V1.9.8.0, so it happened before the MSE-MSME Code re-merge. Not sure if the bug is something in the non-audio routines (point calculations) or audio Code. Might be something I did, or not. I'll have to look into the GUI part in a day or 3.

Other changes: I've found that the Zoom had no VST Parameter (important; I've added), but the Scroll does (drop this?)? I fixed that, & have a few more changes in an internal beta.

[stw]

Though i can't confirm the sustain loop bug (seems to work as expected) i remember that i had that kind of "misleaded sustain points". However i can't reproduce right know. Maybe i've to test further.
But i found some other issues:

If two points fall to the same position the levels are corrupted. Test this with a simple saw. As soon as the 0 point and the 1 point are at the same place the level is reduced. Maybe the levels are summed or something like that. This happens to every "double".

When I added the snap function to grid the grid changed to the selected resolution if not in "auto" mode. In auto mode it worked the other way round. Snap snapped on the graphical resolution set by the zoom factor. Both functions are broken.

[infuzion]

Though i can't confirm the sustain loop bug (seems to work as expected) i remember that i had that kind of "misleaded sustain points". However i can't reproduce right know. Maybe i've to test further.

Sorry I should have attached an example file. I would just post some .VCS shapes, but since I've made other changes, here is the entire OSM:

Multi Stage Modulation Envelope V1.9.8.3~infuzion_snapButtons.osm

1.9.8.3: fixed VST Parameter Zoom amount support, moved Snap buttons (still broken?), + scale button

(89.46 KiB) Downloaded 130 times

The patch Loop:HighEnd is obvious; volume swells loud to the Sustain-loop End, & stays loud. Insert a new point between the Start & End & hear what happens.

If two points fall to the same position the levels are corrupted. Test this with a simple saw. As soon as the 0 point and the 1 point are at the same place the level is reduced. Maybe the levels are summed or something like that. This happens to every "double".

Can you save an .VCS file or 2 & upload to this thread please?

When I added the snap function to grid the grid changed to the selected resolution if not in "auto" mode. In auto mode it worked the other way round. Snap snapped on the graphical resolution set by the zoom factor. Both functions are broken.

Try this version. I didn't change any logic, but perhaps I fixed by accident. It is buggy though; the values are hard-coded, assuming a 4/4 measure?

I would like the .VCS (saved array) file & copy/paste to hold the vector length size, so the MSME can load different sizes, & just truncate if the .VCS is too long.
Exo or whoever added the shape routines, is there a spec-sheet on all the items used in the "Variables" please?

I still need this info. TIA

[exonerate]

Exo or whoever added the shape routines, is there a spec-sheet on all the items used in the "Variables" please?

Will this do?

0 = sustain start
1 = sustain end
2 = number of points for arrays
3 = sustain on/off
4 = zoom

They are the only ones used.

Cheers

Exo

[stw]

Can you save an .VCS file or 2 & upload to this thread please?

I will if i'm back at my DAW. But you can esay try yourself by following my description.

Try this version. I didn't change any logic, but perhaps I fixed by accident. It is buggy though; the values are hard-coded, assuming a 4/4 measure?

No! The whole thing was killed with the new background grid drawing modules. So i took these simplified and deleted a lot of modules and rewrote the Grid snap thing. I fine tuned the limits for auto grid changes a bit too.
Another side effect is that dotted and triplet measures are available again. I didn't test it but visually it seems to be fine.

[infuzion]

Exo or whoever added the shape routines, is there a spec-sheet on all the items used in the "Variables" please?

Will this do?

0 = sustain start
1 = sustain end
2 = number of points for arrays
3 = sustain on/off
4 = zoom

Yes, thank you.

Can you save an .VCS file or 2 & upload to this thread please?

I will if I'm back at my DAW. But you can easily try yourself by following my description.

I'm half-way brain-dead due to lack of sleep; thus I need to see with eyes & not mind.

No! The whole thing was killed with the new background grid drawing modules. So i took these simplified and deleted a lot of modules and rewrote the Grid snap thing. I fine tuned the limits for auto grid changes a bit too.
Another side effect is that dotted and triplet measures are available again. I didn't test it but visually it seems to be fine.

Thanks for your hard work stw! Visually it seems to work well here also. We'll have to re-add the beat & maybe half/quarter markers; too hard to get lost. Or maybe make the markers dotted or dashed to be lighter. If someone can test an VST export with an weird time measure (eg 3/2), that would be helpful. But I still think that part is broken?

[stw]

I'm half-way brain-dead due to lack of sleep; thus I need to see with eyes & not mind.

It's in the actual attachment. The amps have the same levels but one is louder than the other. The louder and correct peak comes from the point (susatin end) which is preceded by a point on another position. The wrong lower value comes from the peak which is preceded by a point on the same position.

We'll have to re-add the beat & maybe half/quarter markers; too hard to get lost. Or maybe make the markers dotted or dashed to be lighter. If someone can test an VST export with an weird time measure (eg 3/2), that would be helpful. But I still think that part is broken?

Changes in .5
I added a 1/4 and a bar line module. The settings are in the property panel (which is partially a mess ). Maybe the enableing should go into the right click menue.
Added a broken recalc link for host tempo changes. (I tested the MSME in Cubase and everything seems to work fine.)
The snap window now shows the actual grid resolution when in auto mode and not just "Auto". That's how it was before.

Some minor fixes

[infuzion]

I'm half-way brain-dead due to lack of sleep; thus I need to see with eyes & not mind.

It's in the actual attachment. The amps have the same levels but one is louder than the other. The louder and correct peak comes from the point (susatin end) which is preceded by a point on another position. The wrong lower value comes from the peak which is preceded by a point on the same position.

OK, this proves why I'll never chase a bug without the reporter's file. Your curve preset has the following characters:
1) The point before the End (last 0 point) is not vertically aligned; you can tell visually by the time of the points & can drag it more to the right.
2) The first curve point is not set to 0. This seems to be the real cause for some reason.
If you fix these 2 things, then each decay will sound the same. You made a good bug find though; strange that the curve makes such a big difference, but I think there may be line-sampling issue that makes the very top tip being missed (not enough resolution?), or that is how it is. Compared to other MSEs/MSMEs?

Thanks for adding the visual grid stw!

Changes in .6
+ The visual-"Grid" now has a switch
f Screen will redraw when snap & Grid are switched
+ moved the "Speed" (horizontally squishes & stretches the env) to a slider inside the MSME, so all envelope controlls are in one place & the pref/paste info is all in once place. Speed may be externally adjusted via the stream-in still.

[stw]

Changes in .6
+ The visual-"Grid" now has a switch

I can't find that

Changes v.7

f Screen will redraw when snap & Grid are switched

Fixed a redraw trigger when snap is set to auto.

-included a "stretch reset" button right beside the slider (GUI could be improved ). When pushed the actual stretch value is calculated into the times array and stretch is reset to factor 1.
- "snapped stretch mode": When snap is activated the stretch also works in steps. For now i hardcoded that to a stepsize of 1/32 based on a point on the first 1/4. Which means with every step that point moves one 1/32 on the grid.

[infuzion]

Changes in .6
+ The visual-"Grid" now has a switch

I can't find that

I saved it to my Recovery folder, & then uploaded the last version from my SM/exonerate folder
Sorry, your Stretch did not give the same values as the older version. Please merge your .7 changes into my .8, although that reset button isn't needed since I already had a right-click reset in the real .6 version.

Changes in .8
+ The visual-"Grid" now has a switch, for real this time
f Screen will redraw when snap & Grid are switched (should also redraw when snap is set to auto)
+ moved the "Speed"/Stretch (horizontally squishes & stretches the env) to a slider inside the MSME, so all envelope controls are in one place & the pref/paste info is all in once place. Speed may be externally adjusted via the stream-in still.
+ Stretch has % readout
+ right-clicking inside Stretch bar resets to 100%

[aliasant]

Guys.

A question.
Is it possible to get a trig/gate output from each point in the envelope?

As an example, that would then be used to retrigger another envelope controlling a filter.....

Or am I just to tired?