Finishing the multi stage modulation envelope

[exonerate]

Ok so this is the project from Here.

I'm moving it to this fresh thread to get this thing finished, it's been going on to long now.

So I would appreciated any bug reports, or if you know how to fix a certain issue and have the time, just upload the fix

The most current version will always be at the bottom of this first post.....

[exonerate]

changes in 1.9.7.7:

fixed beat fraction times to work with different time sigs
rewrote the background grid, now works with different time sigs
Made the env view a bit longer
Added a button in properties to set the current shape to the default shape
when sustain is off and hold is on the env now plays all the way through

Cheers

Exo

[stw]

changes in 1.9.7.7:

fixed beat fraction times to work with different time sigs
rewrote the background grid, now works with different time sigs
Made the env view a bit longer
Added a button in properties to set the current shape to the default shape
when sustain is off and hold is on the env now plays all the way through

Cheers

Exo

Well done exo. Thanks for your efforts! The sync seems to work perfectly well now!
Was that "only" a hop issue? That would worry me a bit because that should not happen.
I'll try to contribute if i can.

[Large]

Thanks for the update
However:
In the "Voices" module in FLSM, when setting "Use a new voice when triggering an old note that is already playing" is set to TRUE, there are loud pops, when playing fast notes.
I attached an example.

[exonerate]

Well done exo. Thanks for your efforts! The sync seems to work perfectly well now!
Was that "only" a hop issue? That would worry me a bit because that should not happen.
I'll try to contribute if i can.

This issue with the hop was that the section number could not increase until 128 samples had passed. With no sustain loop it wasn't a noticeable problem because it was a 128 sample latency overall, each and every section started 128 samples late.

With the sustain loop this latency was accumulating, so with each and every loop it goes an extra 128 samples out of sync.

The reason for the latency was simply because when a section has finished a trigger is sent back to the section manager to increase the section number for the next sample, with the hop the next sample was actually 128 samples in the future. So therefore the section number could not increase until 128 samples had passed.

I do think there is something weird going on in this env though, for instance I've had to set the minimum section length to two samples, where as before it was set to one. This was because if two points are at the exact same area on the X axis the section cannot progress to the next, so it's seems to need two samples to increase the section number in this case. Not sure if that would cause any sync issues but it doesn't seem to from the simple tests I've done.

Cheers

Exo

[exonerate]

Thanks for the update
However:
In the "Voices" module in FLSM, when setting "Use a new voice when triggering an old note that is already playing" is set to TRUE, there are loud pops, when playing fast notes.
I attached an example.

Yep this is the next big issue I'm going to attempt to fix, be playing around with solutions but I've not come up with anything "proper" as of yet.

Cheers

Exo

[exonerate]

Ok so I think I've pretty much got the fastRelease thing (popping) solved.

changes in 1.9.7.8:

Fixed a graphical glitch when setting sustain to zero through the point menu.
Rewrote the fastRelease, works now without popping clicking ect-
Needs good testing though to make sure it is ok.

I was testing with a sine wave as this is the best one to use because the pops show up much clearer. Seems to be fine now.

Cheers

Exo

[Large]

The popping is a little more muffled, but still there. Did you test it in the previous OSM I posted?
I'm suspecting FL Studio may have something to do with this, as I couldn't play your OSM unless I reloaded the envelope into the default FL Studio template.


But a lot of other things were fixed, which is good

[exonerate]

Ok here we go...

changes in 1.9.7.8b:

Rewrote the fastRelease again, sounds much better to my ears
The "unlock/lock sustain points" option from the point menu now only shows up
when the sustain loop is on.

In the last version there was still a noticeable popping but muffled. I guess I didn't have my speakers loud enough to hear it properly.

This version *should* be much better.....

Cheers

Exo

[Large]

It must be my computer or FL Studio, as there is still muffled click-popping.

But I tested MyCo's envelope and it also does that.

If you say you don't hear any click-popping then it has to be my computer or FL Studio.

Thanks for your work on this though

We need more testers. Does anyone else hear the click-popping?

[aliasant]

I tested it earlier today and couldnt ear any strange popping.

Im using a good quality Firewire ASIO soundcard. Are you using real ASIO?
Internal or external soundcard?
What Latency are you running?
Have you tried using maybe 512 or even 1024 and see if that removes the popping?

If I go to low ( say under 128) on my card I get some weird clicks but they are related to sync problems I guess.
That is only on a PC and not using a Mac.

What Im trying to say is that there might be other things in your setup causing this.

Maybe give us a soundbite with the clicks using Exos osm?

[Large]

Not sure what my exact config is, I'll have to check. All other programs work fine though.

Exo, I noticed you fixed other bugs also... the disappering points on reload, and the resetting of envelope shape after copying... Arrrgh! Good job killing those bugs.

However I found another. There's that "hanging note" thing happening again. You'll be playing some notes and then one or two will keep playing non-stop until you cut the poly stream.

This happens on average every 15 minutes or so of playing notes.

[Large]

Not to be confused with "CPU Hanging". It doesn't do that. Just notes that won't turn off.

[exonerate]

Not to be confused with "CPU Hanging". It doesn't do that. Just notes that won't turn off.

I'll be able to take a proper look at this on the weekend. Is this a new problem with the lastest releases? if so which version did it start with?

Cheers

Exo

[Large]

It always has been the case. It happens more so on CPU-demaning schematics, so test it on the biggest baddest schematic you might have