0
0

Hi,

In FModEx 4.01.00 I could list out the ASIO drivers. Now, no matter what I try I get an error in C# when listing the ASIO devices installed on the system after upgrading to 4.01.02. Even using the older version doesnt seem to work.

In the latest C# useplugins sample if I add:

[code:24usy1nn]
private void outputList_SelectedIndexChanged(object sender, System.EventArgs e)
{
int num = 0;

        StringBuilder name = new StringBuilder(2560);
        FMOD.RESULT     result;

        result = system.setOutputByPlugin(outputList.SelectedIndex);
        ERRCHECK(result);

        result = system.getRecordNumDrivers(ref num);
        MessageBox.Show("Driver count = " + num.ToString());
        ERRCHECK(result);

        if (num == 0)
        {
            MessageBox.Show("No devices found.");
        } 
        else 
        {
            for (int count = 0; count < num; count++)
            {
                result = system.getRecordDriverName(count, name, name.Capacity);
                ERRCHECK(result);

                MessageBox.Show(name.ToString());
            }
        }

[/code:24usy1nn]

I get the following exception:
[code:24usy1nn]
System.NullReferenceException: Object reference not set to an instance of an object.
at FMOD.System.FMOD_System_GetRecordDriverName(IntPtr system, Int32 id, StringBuilder name, Int32 namelen)
at FMOD.System.getRecordDriverName(Int32 id, StringBuilder name, Int32 namelen) in c:\dev\fmod programmers api 40102\examples_csharp\useplugins\fmodp.cs:line 2074
at useplugins.Form1.outputList_SelectedIndexChanged(Object sender, EventArgs e) in c:\dev\fmod programmers api 40102\examples_csharp\useplugins\useplugins.cs:line 438
at System.Windows.Forms.ListBox.OnSelectedIndexChanged(EventArgs e)
at System.Windows.Forms.ListBox.WmReflectCommand(Message& m)
at System.Windows.Forms.ListBox.WndProc(Message& m)
at System.Windows.Forms.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
[/code:24usy1nn]

I am using the latest api. Also, it says I have 1 driver in ASIO despite the fact I have 4 installed on my system. Asioconfig.exe reads the number of drivers fine. Does fmodex read the registry to enumerate the ASIO drivers? My registry is intact as other applications can enumerate the drivers without problems. Are there any known ASIO drivers which cause problems with fmod?

When I use the ASIO SDK I can access and initialise all of the drivers but I need FModEx to work with ASIO.

Thanks for reading. I’m desperate to get to the bottom of this.

  • You must to post comments
0
0

help… anyone??

  • You must to post comments
0
0

Sorry to hassle you Brett but Im pretty desperate and I need to know whether or not this issue can be resolved or at least reproduced.

Thanks

  • You must to post comments
0
0

Hi,

I tested it with the latest release and still I get this error. Have you been able to reproduce it yet?

Cheers

Mark

  • You must to post comments
0
0

Hi markt,

Thanks for reporting this.

Sorry for the delay, we’ve found the problem and the fix will be in the next release :)

  • You must to post comments
Showing 4 results
Your Answer

Please first to submit.