Well I’m using VB, but I guess it would all work under C#.
All I did was something like:
You may also need
[code:1hz342uz]FMOD_DSP_ShowConfigDialog(dsp, Me.hwnd, 0)[/code:1hz342uz]to configure the plugin.
Hmm, the previous FMODEx version was working fine for me, but now when I use this version, I can’t hear anything in DirectSound mode.
I can’t hear anything in all of the examples that use Direct Sound, or in my application.
Using Auto-Detect chooses Direct sound and I still can’t hear anything.
I have an SBLive! Value card.
WinMM mode works fine.
Don’t think this is a bug report, more of an observation or a question.
Previous betas have worked under VB (don’t know about other languages) without setting cbsize in a FMOD_CREATESOUNDEXINFO passed to FMOD_System_CreateSound. Beta-32 however needs cbsize set to 72 otherwise you get FMOD_ERR_INVALID_PARAM returned. I worked this out by comparing my own code to the examples.
I was just wondering why cbsize needs to be set now, and whether anyone knows of a way to calculate it in VB instead of hardcoding it?
[quote="brett":10kk82so]Its pretty damn annoying (even stupid) that VB cant pass a null value as a parameter.[/quote:10kk82so] Couldn’t agree more! 😀 Thanks for taking the problem with exinfo in-hand!
Also, just noticed that FMOD_DSP_TYPE_WINAMPPLUGIN is missing from the FMOD_DSP_TYPE enum in the VB API files. I’ve just had a fun 20mins trying all sorts of different Winamp DSP plugins with my own software though. Very cool! 8)
Damn these sound card drivers 😡
Ok this time i’m ditching WAVEFORMATEXTENSIBLE all together if the format is plain 8 or 16bit, mono or stereo, the extensible stuff that uses the channel mask is only used if the sound or output is greater than stereo, or 24,32,floating point audio data.
FMOD is doing everything by the book, its the stupid drivers that screw it up constantly :([/quote:3qt4muhf]
Will you be updating this version, or should I wait for the next version for the working DirectSound output?
[quote="andrewboothman":14lg4bpu][quote="brett":14lg4bpu]Its pretty damn annoying (even stupid) that VB cant pass a null value as a parameter.[/quote:14lg4bpu] Couldn’t agree more! 😀 Thanks for taking the problem with exinfo in-hand![/quote:14lg4bpu]VB can pass a null value as a parameter as long as the parameter is defined as [b:14lg4bpu]As Any[/b:14lg4bpu] instead of a struct. If you tell it you’re passing a struct, you have to pass a struct – period. Null isn’t a struct.
When I try to load a VST Plugin with FmodEx 32, the plugin is not loaded.
This following error is returned by System::loadPlugin :
[code:11wrt9dg]FMOD error! (23) Unsupported file or audio format[/code:11wrt9dg]
This error is returned for all VST plugin I have. With FmodEx 31, the plugin is well loaded and works well.
[quote="chenpo":2l6vypwa]We’ve tried defining the parameter As Any and passing in a null. I’m not sure what type a null is in vb, however when it is passed into c, it points to a random part of memory instead of being null.[/quote:2l6vypwa]Are you passing vbNull, ByVal 0, or just 0? You have to pass ByVal 0, I believe, or perhaps ByVal vbNull (the default in all BASICs that I know of except VB.net is ByRef.)
[b:3m0p86bv]Linux64[/b:3m0p86bv] – coming soon[/quote:3m0p86bv]
This will be the last beta! Next friday will see the final release. To be added are just channel groups, a cross platform reverb dsp effect, and any outstanding issues.[/quote:3m0p86bv]
will the linux64 version be there next friday? excited
- chilli answered 12 years ago
Please login first to submit.