SynthMaker

Pb with my VST

Archive · 2007 15 old posts

From the original SynthMaker forum (2004–2014), with its members’ names and dates.

sonata31 ·

Hello,

Excuse my poor english

I begin with Synthmaker, and I am working on a "Switcher-Splitter" Its schematic : http://dialou.fr/temp/Switcher_Splitter.osm

In Synthmaker it's ok except : the blue rectangle is below

the blue rectangle is above

In Console I get :

When I click on the buttons the horizontal slider moves, but the label does not change (wave,tuner,aux,phono)

When I move the horizontal slider, it comes back at its original position

sonata31 ·

I have resolved the first problem, new schematic :

http://dialou.fr/temp/Switch4Split2.osm

But always the problem with the host (Console)

rl ·

You shouldn't use the Index selector module. AFAIK it's made to be used in property panels

sonata31 ·

rl wrote: You shouldn't use the Index selector module. AFAIK it's made to be used in property panels

??

sonata31 ·

Help

exonerate ·

i've had a little look, i'm not sure exactly what your problem is, but the only thing i can see that could be causing a problem is that you are dividing the input to the vst param by 3, when i think you should be just connecting it to straight to the vst param, as far as i can see there is no reason to divide to value,

so just try connecting your input index straight to the vst param, it doesn't matter that the value is an integer and the input to the vst param is a float, SM will just change you integer to a float.

anyway let me know if this make's a difference

cheers

sonata31 ·

exonerate wrote: i've had a little look, i'm not sure exactly what your problem is, but the only thing i can see that could be causing a problem is that you are dividing the input to the vst param by 3, when i think you should be just connecting it to straight to the vst param, as far as i can see there is no reason to divide to value,

so just try connecting your input index straight to the vst param, it doesn't matter that the value is an integer and the input to the vst param is a float, SM will just change you integer to a float.

anyway let me know if this make's a difference

cheers

Component reference.pdf page 259 :

The VST preset parameter system requires values to be floats in the range 0 to 1. You must make sure that you transform any values you want to store into this range before passing them to the VST Parameter component. If you want the host to display something other than the 0-1 float value you can create a section of schematic that processes the float output of the VST Parameter component and connect it to the Disp input. Examples 1. You could have switch that you want to show On for 1.0 and Off for 0. 2. You might have a multiplier that you want to show as Level 1, Level 2 or Level 3. You�d convert the input value to 0-1 by calculating (value-1)/2. This would give you 0,0.5 and 1. When the preset changes you�d process the result back to a number in the range 1-3, append it onto �Level � and pass the result to the Disp input.

exonerate ·

ok stupid me i know next to nothing about presets.

i thinki though that you might need to put a vst param inside each of the button's you have because the one's your using dont have them in, one thing i've noticed is every control needs it's own vst param for presets to work and they all need there own name, so basicly you've got a single vst param for all the control's, i think it might work if you gave each button it's own vst param,

the buttons only have two states 0 and 1, so that would work with the vst param without the need to divide, and as long as you use a different preset name for each button i should think that it would work fine. because at the moment i don't think that the vst param is able to send a value to your index selector because it would need to be before it, so if you have it inside the buttons then it would be able to.

i hope this helps, let me know how you get on

cheers

sonata31 ·

exonerate wrote: ok stupid me i know next to nothing about presets.

i thinki though that you might need to put a vst param inside each of the button's you have because the one's your using dont have them in, one thing i've noticed is every control needs it's own vst param for presets to work and they all need there own name, so basicly you've got a single vst param for all the control's, i think it might work if you gave each button it's own vst param,

the buttons only have two states 0 and 1, so that would work with the vst param without the need to divide, and as long as you use a different preset name for each button i should think that it would work fine. because at the moment i don't think that the vst param is able to send a value to your index selector because it would need to be before it, so if you have it inside the buttons then it would be able to.

i hope this helps, let me know how you get on

cheers

I don't understand : this is only one parameter (input) with different values (wave,tuner,aux,phono) corresponding at each button One parameter = one VST parameter ??

exonerate ·

'm sorry but i'm sure that i'm not understanding what the problem is that your having.

if i am getting you right this time you are using midi to change between switches and you want the name on the display to change with the midi?

well if this is the case then you would just need to set up your buttons using selectors instead of the index selector because it can't take an index value it's self which would be needed when using midi, so when you send it a midi value the selectors change to output the name to the vst param, the way your doing it now you can't do that, i think you need to replace the index selector for normal selector's. it would mean a total rethink of how you have your buttons set up now, i don't think that the index selector was designed for the way your using it

exonerate ·

thinking about this again you could probally still use the index selector, but you would have to use a midi splitter, and then use int equals which ever numbers you want, so if the midi number was one then the int equals component would output a boolean true, connect this to the boolean input of a string select with the name you want, so when the midi number was say 3 then the int equals, which contains the value 3 would output a true to the corrosponding string select containing the name you want, then this name would go to the index select and switch it, changing the name.

i would knock you up a quick example but i'm about to go out,

hope this helps

sonata31 ·

My plugin is ok when I test it with synthmaker :

With Console :

The slider is ok (with midi also) The pb is with the label : its value does not change

exonerate ·

yes i uderstand what you mean now, i'm not sure how to sort this out, and i can't even test it to see if anything i do works, cos i've exported it form synthmaker and tried to load it in to my DAW(i use sonar 6) but it will not load. i get a process replace error or something. i can export as exe, but with the exe i haven't got a clue how to find out if it's working. i'm not sure what your using to host it.

anyway maybe someone else can test it as well cos without being able to load it into my DAW, i don't know how to find out if it's working or not

you might have to wait for someone else with more experianced in this area.

cheers

sonata31 ·

exonerate wrote: yes i uderstand what you mean now, i'm not sure how to sort this out, and i can't even test it to see if anything i do works, cos i've exported it form synthmaker and tried to load it in to my DAW(i use sonar 6) but it will not load. i get a process replace error or something. i can export as exe, but with the exe i haven't got a clue how to find out if it's working. i'm not sure what your using to host it.

anyway maybe someone else can test it as well cos without being able to load it into my DAW, i don't know how to find out if it's working or not

you might have to wait for someone else with more experianced in this area.

cheers

I use Console for host

Thank you for your responses

sonata31 ·

Nobody for my problem ?

Wrote something here? To have a post removed or your name hidden, write to [email protected].

Before your first post

A few rules keep this a friendly place. You agree to them once.

Shown next to what you post, here and in the app. It doesn’t have to be your real name: 3–24 lower-case letters, digits or _ (capitals become lower case, spaces become _).

    Then your post goes up straight away.

    Delete this reply?

    Open it in SynthMaker?

    It goes on the track you’re editing there, in place of that track’s sound, and into My sounds. Your other tracks stay as they are.

    Want to keep that track’s sound? Start a new song in SynthMaker first (Song › New song), then open this.

    Report this reply?

    Only the developer reads reports. The person isn’t told who reported them.

    What’s wrong with it?

    Block this person?

    You won’t see their posts and replies here any more. They aren’t told, and you can unblock them at any time.

    People you’ve blocked

    Their posts and replies are hidden from you. Unblock someone to see them again.

    The community rules

    A few rules keep this a friendly place. Everyone agrees to them once, before their first post.