0
0

Okay I load a plug in.
[code:hjebe8vf]
result = FMOD_System_LoadPlugin(system, "C:\Program Files\Steinberg\VstPlugins\Final Master.dll", FMOD_PLUGINTYPE_DSP, 1)
ERRCHECK (result)

result = FMOD_System_CreateDSPByIndex(system, 1, vstEffect)
ERRCHECK (result)
result = FMOD_System_AddDSP(system, vstEffect)
ERRCHECK (result)
result = FMOD_DSP_SetActive(vstEffect, True)
[/code:hjebe8vf]
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?

  • You must to post comments
0
0

anything?.

  • You must to post comments
0
0

Cool. I’ll pm you as soon as I pack up the code :)

  • You must to post comments
0
0

any word yet? :(

  • You must to post comments
0
0

This seems to work.

[code:3mzcuce4]
result = FMOD_System_LoadPlugin(system, "C:\Program Files\Steinberg\VstPlugins\Final Master.dll", FMOD_PLUGINTYPE_DSP, vstEffect) ‘Load plugin
ERRCHECK (result)
‘Create Plugin and add it to System
result = FMOD_System_CreateDSPByType(system, FMOD_DSP_TYPE_VSTPLUGIN, vstEffect)
ERRCHECK (result)
result = FMOD_System_AddDSP(system, vstEffect)
ERRCHECK (result)
result = FMOD_DSP_SetActive(vstEffect, True)
ERRCHECK (result)
‘Check to see if the Plugin is Active
result = FMOD_DSP_GetActive(vstEffect, Act)
ERRCHECK (result)
If Act = 1 Then
Label1.Caption = "True"
Else
Label1.Caption = "False"
End If
[/code:3mzcuce4]
Cool. That plugin loads and effects the system.

Still not sure why a plugin that shipped with SX would not work with FMOD.

Would there be a way to catch that "Sorry This PlugIn Requires Cubase SX" error, before it’s displayed?

That way I can code a function that checks which plugins will not be populated into the list of available plugins.

  • You must to post comments
0
0

Still nothing on this.. Any FMOD guys going to jump in?

  • You must to post comments
0
0

Chenpo,

care to share your test app?

  • You must to post comments
0
0

Okay by adding this bit of code:

[code:1v6wxbna]
result = FMOD_DSP_ShowConfigDialog(vstEffect, Hwnd, True)
ERRCHECK (result)
[/code:1v6wxbna]

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.

  • You must to post comments
0
0

seems like plugins created with synthmaker are working normally. Which is good. Now we need to get the rest of the plugins working.

http://www.yamahasynth.com/download/finalmaster.html
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.

  • You must to post comments
0
0

Hi,

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 support@fmod.org I’ll take a look at it as soon as I can.

  • You must to post comments
0
0

[code:1clabbh0]
result = FMOD_DSP_GetInfo(vstEffect, n, v, c, cw, ch)
ERRCHECK(result)
[/code:1clabbh0]

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?

  • You must to post comments
0
0

still nothing?… 😥

  • You must to post comments
0
0

sure thing.

  • You must to post comments
0
0

[quote="jayDC":1h57n5l3]Okay by adding this bit of code:

[code:1h57n5l3]
result = FMOD_DSP_ShowConfigDialog(vstEffect, Hwnd, True)
ERRCHECK (result)
[/code:1h57n5l3]

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.

  • You must to post comments
0
0

I’ll try and take a look at this by the end of the week.

  • You must to post comments
0
0

chenpo,
any chance that you’ve taken a look?

  • You must to post comments
0
0

any ideas? hint, anything!.. If it’s not an fmod problem, and a VB problem tell me what to research.

Ah maybe, Multi threading?

  • You must to post comments
0
0

Awesome Chenpo!… Thx.. If you’d like the example code I wrote, I can PM you a link.

  • You must to post comments
0
0

Hi Jay,

Apologies for the delays in resolving this.

Thanks for the repro. I’ve found the problem and there will be a fix for it in our next release which should be next Thursday.

  • You must to post comments
0
0

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.

  • You must to post comments
0
0

Get a chance to take a look, chenpo?

  • You must to post comments
Showing 1 - 20 of 28 results
Your Answer

Please first to submit.