Okay I load a plug in.
result = FMOD_System_LoadPlugin(system, "C:\Program Files\Steinberg\VstPlugins\Final Master.dll", FMOD_PLUGINTYPE_DSP, 1)
result = FMOD_System_CreateDSPByIndex(system, 1, vstEffect)
result = FMOD_System_AddDSP(system, vstEffect)
result = FMOD_DSP_SetActive(vstEffect, True)
I know that this loads the plug in, because if I use one that came with Cubase SX (ie Reverb A.dll) I get a dialog box with an error (Sorry This PlugIn Requires Cubase SX). Fair Enuff (although Why can’t FMOD open an SX plugin?).
Now, why am I not hearing this plug-in when I play a stream (it is set to FMOD_SOFTWARE). What am I missing in thtat code to route sound through this plugin?
- jayDC asked 10 years ago
seems like plugins created with synthmaker are working normally. Which is good. Now we need to get the rest of the plugins working.
Can someone from FMOD take a look at these yamaha plugins to see why they do not work correctly with FMOD? They have Trial versions on the site.
I think the issue maybe with vst2.0 plugins and fmod.
My testbed was basically based on the dsppluginviewer example that comes with the FMOD SDK.
If you can the small sample testapp you had along with a description of what the problem is to firstname.lastname@example.org I’ll take a look at it as soon as I can.
result = FMOD_DSP_GetInfo(vstEffect, n, v, c, cw, ch)
Why does n always return 86 for a VST plugin? How do I pull the plugin name?
Also, cw and ch are not correct. The results differ from plugin to plugin. so sometimes the form is too big, and sometimes its correct. what gives?
[quote="jayDC":1h57n5l3]Okay by adding this bit of code:
result = FMOD_DSP_ShowConfigDialog(vstEffect, Hwnd, True)
it will show the VST Effects Config Dialog. IT looks really nice sitting there in the form. Major Problem is that the graphic do not update unless I’m touching one of the sliders or buttons (MOUSE DOWN). If I leave it alone the VU meters do not update. They are blank. How can I fix this.
EDIT: Also noticed that when you are holding mouse down on a control of a VST, the Clock from the play stream example stops.
So while the VST is graphically updating the other forms stop updating.[/quote:1h57n5l3]
I really need help with this one. I can provide the sample I’m working with.
jayDC – these guys on these forums have been helpful before with my VB questions. It seems throughout your posts you have answered your own questions. The issue with the VU meters not updating could be that the PAINT event may not be getting triggered. This would make sense that as you change a control within the form a PAINT event is called. Anyways you could try to subclass the window handle you pass in order to manually fire off the PAINT event? At the root of all of this may be the VST itself. And as far as FMOD not being able to open CuBase VST plugins – I thought these plugins where written in such a way they could check where they were called from and look for the hardware dongle for CuBase. This may be an issue with those VST plugins and not FMOD. This is why when you purchase plugins with CuBase you have to update your dongle.
- cxvjeff answered 10 years ago
The cubase plugin shipped with cubase, they are not the ones you purchase after, which I believe you need the dongle update for.
I’m not worried about them working, I want to catch the error before the awful dialog box appears. That way you don’t see the dialog fire off 100 times while scanning the VST plugins directory to populate a list of available plugins.
I’m going to look into the PAINT event. thx!!!
Apologies for not taking a look at this last week. I hade some high priority tasks and wasn’t able to get to it.
Is it just this particular plugin that doesn’t load? What sort of problem are you having when trying to load the plugin?
I was able to load the plugin in my own testapp. It did take some head scratching though. I think the plugin has some type of anti-hacking security in it. I wasn’t able to load the plugin if I was running my app through the debugger (it would simply just close the whole app whenever the plugin was queried). However, it loaded okay outside of the ide/debugger.
had an idea.
result = FMOD_DSP_GetNumParameters(vstEffect, numparam)
Using the plugin final master.dll numparam = 45
okay cool the plugin has 45 parameters. Maybe there is one that refreshes the plugin.
So I use this bit of code to get the parameter info
result = FMOD_DSP_GetParameterInfo(vstEffect, 1, name, Lbl, des, desLen, min, max)
Now a bigger problem arises I get en error "Run Time Error ‘458’. Variable uses Automation type not supported in Visual Basic".
EDIT: Wierd this error only happens when running it, if you compile it no errors, but the data never changes.
I think there some sort of bug, or that FMOD really doesn’t support VST in VB even though it says it does. Could someone look into this? I can provide the sample I’m working with.
it’s not just with this plugin. I just used that plugin as an example.
The only plugins that update the screen are the plugin created with a program called synthmaker. Steinberg, TC works, Waldorf, Yamaha, Native Instrument Plugins load, but the screen does not update unless you are manipulating the controls. CVJeff and myself have not been able to find a way to force this screen update.
Please login first to submit.