From the original SynthMaker forum (2004–2014), with its members’ names and dates.
Atnoz ·
Ok guys, im in trouble...
Im trying to take the L and R channel from a vsti synth output and pass through another vst, this one
will apply a math formula at L and a different math formula at R channel but im checking the result
with blue cat scope and isnt working. No changes in graph or sound of synth. Sometimes it stay mute.
Im confused.
Prolly im missing some basic concept. Someone can put some light in this question?
Or post a silly example to clear my dumb mind?
Silly example:
VSTi Synth L OUT -> L MyPluging IN -> (2*L input) -> MyPlugin out L -> scope -> speaker
VSTi Synth R OUT -> R MyPlugin IN -> (R input/3) -> MyPlugin out R -> scope -> speaker
Thanks in advance.
trogluddite ·
Welcome to the forum Atnoz,
Need to make sure I am understanding the problem - it sounds like your problem is when using the exported VST inside a host? Or is this problem purely inside the SM software?
If possible posting the SM .osm file or a screenshot will help to find the problem (you may not have permission, sometimes it is slow to be enabled).
Atnoz ·
Ok. Thank you.
Here is 2 screens:
First show the synth connected to the testplugin and this one to the output of vsthost.
Second show the project. It has 2 input box to insert the conversion numbers, one for the
L and another for the R. Each with a simple formula (x and /). And has 4 readout boxes.
1 to report the data before and 1 for after conversion for each channel.
The result of test is:
i play the A3 note (440hz) - in true any keyboard note is mute.
everything is mute.
no data is reported.
I expected (pure sine out from the synth - A3): report1=440, report2=880, report3=440, report4=88
For sure im doing some gross mistake. Thank you for your patience.
kirkagur ·
hi there.
in order to open the poly signal you need to have midi to poly and hold one note open with the env module so the poly signal will stay open.
cant send an osm right now but maybe later i will upload a solution.
MichaelBenjamin ·
ok, yes as kirkagur said, the white stuff is only processed when connected with a midi to voice upon playing a note.
just delete that mono2poly and the combiner and make everything blue (always running). but since you process audio here, the conversion to hz as in a pitch stream does not make directly sense. watch your speakers, or better always use a stereo clip module before output.
Atnoz ·
Humm.... *scratch her head*
I made some changes like you guys said.
Now i hear the sound and see the floating numbers but... the behaviour of L and R at
scope isnt what i expected. Changing the input values the waves moves up and down (Y scale)...
and i need them moving to left or right at X scale. And some human readable numbers at
report gui.
So if the synth sends to the pluging 440hz, the peak of L will moves to the right at 880hz and
the peak of R will move to the left at 88hz (if the inputs are 0.5 and 0.2).
Here is the new screens:
MichaelBenjamin ·
i guess the synth doesnt output 440hz, that would be a constant value, instead it outputs the waveform cycling between -1 and 1 at the frequency of eg 440hz. i dont know what you want to do, but if its changing the pitch you cant do that afterwards with a simple number conversion. maybe look at the example synth that comes with sm and use some readouts to understand what kind of numbers get through the specific parts of a synth.
Atnoz ·
Yeah...
Studying the synth example.osm i can see only the note frequency at midi to poly output... *sad*
after that the whole thing become -1 ~ +1 at any part of project. And i guess there is no way
to compose the float numbers back to some human readable number. Well guys...
Im not a scientist or sound engineer. Prolly i will give up. I thought was be easy to move the whole
wave of some chanel (no mutation) to up/down and left/right at Y X axys of scope by math formulas
with one or two variables. Will read some articles and try a bit more. Any sugestions?
Wrote something here? To have a post removed or your name hidden, write to [email protected].