Volume shaper /Line editor causing extra harmonics, noise ?

[Spogg]

You'll often get clicks with too fast an attack or decay time. Especially so if your signal is non-zero when the attack starts. A minimum attack time of about 1-5 mS should work.
This was especially true for older real analogue synths where the oscillators were free-running, so you never knew the phase of the waveform when the envelope opened. Also your envelope should always start at zero when triggered.

Cheers

Spogg

[pshannon]

You'll often get clicks with too fast an attack or decay time. Especially so if your signal is non-zero when the attack starts. A minimum attack time of about 1-5 mS should work.
This was especially true for older real analogue synths where the oscillators were free-running, so you never knew the phase of the waveform when the envelope opened. Also your envelope should always start at zero when triggered.

Cheers

Spogg

Thanks for the info Spogg, I didn't know that and yes I have experienced this many times thinking something else was wrong.

QuadBIT

[lalalandsynth]

@Theom

I noticed this in the interpolator code "// remember to change memin size when changing
// line editor size or resolution" I might want to change the size , How would I change the memin size to correspond to a change in the line editor size ?

I have figured out why the knobs were not saved in the preset manager,
BUT :The knobs still do not report to the daw for undo purposes or saving in the daw ?


Then there is figuring out how to get higher resolution cc output , I will start by removing the CC scaling and see what that does.

[Spogg]

I found you have to be a bit careful with MIDI cc in combination with green processing. Green is slow and is processed with much lower priority than the stream stuff and can be a bit unpredictable. For example, I had a knob driven by the Modwheel so you could use either the knob and/or the Modwheel. Due to the triggers and redraws I got a big CPU hit when I operated the Modwheel, due to the knob workings. So in that case I disabled the knob as a “display” for the Modwheel.

The other thing I’ve found is it’s a good idea to test the functions in a VST plugin export because it seems the green issues are generally less apparent.

This is all about real-world experience rather than in-depth knowledge of the processes.

Good luck with your project!


Spogg

[lalalandsynth]

OK, thanks , that is good to know .

I am constantly exporting into Reaper and testing , I agree , that is probably the way best to see what is going on.
As for the "green" , The values from the envelope have now been interpolated and are fast enough to run audio through.
I am taking that output into a signal to CC so I would assume that its fast enough ?

It is quite essential for this thing to be able to output CC, I guess I am kind of stuck with not knowing if the interpolated output from the envelope is sufficient or not , and if not , obviously looking for another way .

This is also one thing where my skills and knowledge are sorely lacking , I am so used to being able to put a scope or tester anywhere , like in Multisim . Is there anything equivalent in FS for monitoring resolution of "streams" ? Not sure if I am using the right terminology. Or any tools you would suggest that are essential for building ?

[TheOm]

I noticed this in the interpolator code "// remember to change memin size when changing
// line editor size or resolution" I might want to change the size , How would I change the memin size to correspond to a change in the line editor size ?.

Just make sure that the number in the brackets of the memin is at least as big as the size of the array that comes out of the line editor.

[lalalandsynth]

Just make sure that the number in the brackets of the memin is at least as big as the size of the array that comes out of the line editor.

I see , and its double the size now at 256 . Cool, thanks.