BrainModular

Hello, I just started to discover the world of Usine and i have another question. I hope it wasn´t discussed in the past, otherwise sorry but I didn´t found it. I want to ask you how I can do parallel processing in Usine without that annoying phasing effect? Example: I have some recorded audio as input, and I patch it to some VST effect like some compressor AND patch dry signal straight to output in same time. The result is phasing effect. So is there any solution? Is this missing feature or normal behaviour of modular system? Thank you very much!

i was wondering so too,
It must be very hard to calculate adc with complex patch, I guess the workaround is to slightly delay the dry signal, maybe check with an invert phase and adjust the delay till you get no sound...then revert the phase back..no the best also..and this would only work with a "constant" latency., or maybe there is a way to track latency of signal processing? then it would allow to use that info to compensate on a delay fader....but I think the count ms would not be precise enough, it must be a slight number of samples...
brainstorm

hi,

technically, it's possible, in Usine, to delay the dry signal, but the question is now...

how to quantify the necessary delay for the dry signal ? (depending on the VST used)

maybe putting two synchronized wave display (one withe dry, one thru VST) with a tick sound can let you see the approximate the delay time needed...

Hope it help

23fx23 wrote:i was wondering so too,
It must be very hard to calculate adc with complex patch, I guess the workaround is to slightly delay the dry signal, maybe check with an invert phase and adjust the delay till you get no sound...then revert the phase back..no the best also..and this would only work with a "constant" latency., or maybe there is a way to track latency of signal processing? then it would allow to use that info to compensate on a delay fader....but I think the count ms would not be precise enough, it must be a slight number of samples...
brainstorm

Something like Line-Up would probably be more practical than the delay module.

thanks bsork for the line up link, ( for me i don't have the pb for now as I entertain myself via wiring only midi and data for now),
but the question was interesting me, i might check the audio side soon.. usine is great, i managed to make a clip matrix with scroller that react to incoming data in a few hours with the few advices you provided to someone else in another thread, that rocks..im really happy.

"Clip matrix with scroller" What's that? Something to share as an add-on?

martignasse wrote:hi,

technically, it's possible, in Usine, to delay the dry signal, but the question is now...

how to quantify the necessary delay for the dry signal ? (depending on the VST used)

maybe putting two synchronized wave display (one withe dry, one thru VST) with a tick sound can let you see the approximate the delay time needed...

Hope it help

I never had to deal with this in Usine (everything working well for me) but I know that there are other hosts (eg Cubase; Reaper) that show the exact delay time that every plugin is introducing.
Shouldn't be too hard to calculate the correct cumultative delay time for the Vst chain with this info I think.

Just an idea though...

VST's should report their delay and the host can then adjust. You don't have to calculate it your self, there is a plugin callback (apparently) called getInitialDelay(). But I think that needs to be done at the host level rather than user level.

As gregh said. The problem is that (as I readed) some plugins did´t report their delay correctly... But I believe most of them did. Could you gregh please explain what is that getInitialDelay()? Thank you!

bsork wrote:"Clip matrix with scroller" What's that? Something to share as an add-on?

hehe have to finish and adjust a few thingz, and for now it's too much made for my self purposes (trigger/get infos of ableton live clips in the session view), but as soon as I finished it I ll try to make a "more universal" version of it and post in the add-ons..
basically it's a column of 5 buttons labelled from 1 to 5, and two arrows button to scroll. each time you scroll the buttons caption updates from 0 to userchoose max and let you see what number will be send and wich one is actually playing(surrounded by a bg usine panel lighted up). this is quite simple but can be usefull for lot's of thing (choose fx, launch clips ect) ... maybe i should post this simple but open patch now and then the more specific for live when it ll be finished (with interesting visuall feedback like clip is armed, clip is playing, clip duration in bars, processing lock...had lot's of fun putting the infos I wanted in lighted led/panels blinking with rvb values (thx senso): red :it'ss not cool, green it's cool ect)..maybe soon I ll use it to lauch usine clips/loops and no more ableton, but for now too many habits...but definitively a cool way to discover usine, Im really loving it!!!..
bsork/senso I think I ll be asking you a few q during next years hehe (like I start to undestand the math tip to optimize, search the needed pin, cool). I first try hard to test myself, but I ll have so many questions to ask to "masterZ".
cheers

I am no expert and have now seen that the call is setInitialDelay() - but my understanding is that the VST has to report the latency to the host, which means the VST must be written to give out that information correctly. setinitialDelay() is found within the VST code, so you can't see how it is used unless you have the actual code for the VST you are interested in.

I have not found a VST that can test a plugin and give the latency, but Christian Budde has a standalone VST testing suite.
http://www.savioursofsoul.de/Christian/?page_id=106

Maybe someone on KVR in the DSP forum will know of something. Some info here
http://www.kvraudio.com/forum/viewtopic ... ay&start=0