slide module - so how it works

[tester]

I'm trying to figure out how the "slide" module works, but it looks that I'm missing something.

I'd like to set a constant slide time per step, to make it smoother with dezippers on blue side, so I'm manipulating the step size. So the formula is:

steps = slidetime x 1000/steptime
stepsize = input/steps = steptime/1000 x input/slidetime

But getting weird slide times.
What did I miss?
Somewhat I doubt that windows timing is so bad, rather my math.

[tester]

I found your module Trog.
What can I remove from it, to make it smaller?
Could you clean it a little bit?

[RJHollins]

tagging on tho this thread regarding an issue with the 'Slide' primitive.

I don't know what the problem is, but I've placed a 'Slide' prim into one of my circuits and everything works fine inside of FS.

Now, when I export the module as a VST ... everything works EXCEPT the bit with the Slide primitive

What could possibly change just doing an VST export ????

[tester]

Green motion prims will not work in render mode in DAWs, you need streamy modules there instead. Use dezipper.

[RJHollins]

This is for a midi project, no audio.

Basically need a fader or knob value to glide
up/down to target value.

I wonder if RUBY would be a choice?

[tester]

Extract that part of your schematic, check how it works alone, and if doesn't works - post it here.

[RJHollins]

Hi tester,

I can extract that part of the schematic, but it may be a bit to test it out as its 'input' is only MIDI data.

Secondly, as mentioned, it works fine when run from FS ... stops working as exported VST. Your mention of green 'motion' prims not working in DAWs is a bit troubling to read.

I've looked into using the DeZipper. It seems an M2F is the only prim I find to get back to a float. The problem there is that it needs an audio stream to function. Maybe that won't be such a problem in the end. I'm working on something new for me, and still learning.

Anyway ... this is a fairly simple schematic.

Data arrives at the MIDI IN port. There is a MIDI Channel filter to isolate a single channel. This is then 'split' off to have D2 as a value that will control a Knob connected to dual VCA's. Basically, MIDI data control audio output level. All else is eye candy info.

My goal is to do a form of 'damping' to changes in the data to ease dramatic level changes ... thus the idea to 'slide' into the new level. I'm also needing to address an issue when a MIDI patch change AND level change are sent. I need to figure a way to smooth audio levels during that time [audio cuts out during the patch change ... nothing I can do about that, so I need to work something out]. The problem has been when I export this, the 'Slide' no longer works, so any testing can't be done

Here's the basic schematic ... do you see if I'm just doing stupid somewhere here

capture 1.jpg (65.91 KiB) Viewed 19155 times

Slide prim issue-1.fsm

Slide prim issue with VST export

(142.01 KiB) Downloaded 1022 times

Again ... works fine in FS ... not after VST export.

Thanks everyone for any ideas to this!

[MyCo]

Try this

Don't know if this is addresses the problem you have, but there was a threading problem with Midi, that's why there was a de-threader module in SynthMaker. It isn't included in the FS Toolbox, may be it's not necessary anymore.

[RJHollins]

Try this

Don't know if this is addresses the problem you have, but there was a threading problem with Midi, that's why there was a de-threader module in SynthMaker. It isn't included in the FS Toolbox, may be it's not necessary anymore.

Once again ... MyCo, you have 'Saved The Day' !

It WORKS ... even in the VST export ! Thank-you !

If I may impose a bit further, please ....

Is there any links to details that identify what this issue is, and when, where, we should apply the de-thread module ??

You were also correct that this 'de-thread' module is not in FS [best I know]. I would have never figured this out on my own. If this is, indeed, a bug ... is this being addressed in an update ? Would the 'de-thread' module cause problems when MIDI is fixed ???

In the meantime, any info, links that could help educate me on this 'issue' would be most welcomed, as I'm now relying on MIDI within many aspects of my new projects.

Once again, thanks for spotting this thread and providing a solution MyCo ! I've been following other threads [FFT] stuff that you've posted ... but mostly for me, with 'glazed over eyes' Fascinating stuff.

Also, I've just started using Your multi-tabbed GUI in my 2nd project. [I think the latest one posted]. So far, it seems I'm able to integrate without any problems. This is so brilliant what you've put together, and now allows me to do some sophisticated designs. My planned 3rd project will start with this tabbed GUI module, and should help me to design with this feature already in mind.

THANK-YOU !

[MyCo]

The Midi-problem is not a Bug... it's kind of a known misbehaviour. The background is: The Midi stuff runs in a separate thread (not the GUI Thread that the green trigger system uses). Here is the original description from Malc:
http://www.synthmaker.co.uk/forum/viewtopic.php?t=3673