Topic: USB Midi driver problem

Viewing 15 posts - 1 through 15 (of 20 total)
1 2
  • June 13, 2007 at 21:12 #1320
    MoodyB
    Participant

    Hi,

    I have just recently changed to a Emu XMidi USB interface for connecting my 2 synths to Podium, but I’ve come across an annoying issue that I’m not sure if it’s an Emu driver problem or something in Podium.

    Every time I start up Podium, I get the following message :

    If I then enable the interfaces in the audio/midi prefs in Podium they seem to work fine.

    I’ve disabled the powersaving features on all the usb hubs shown in Windows device manager as I though this might be the cause but it hasn’t helped. Tested the interface with MidiOX and MiniHost and both work with no problems. Also tested the interface in CubaseSX and the in/out ports show up as ‘ emulated ‘ for whatever reason.

    I’m tempted to say its a Emu driver prob as it hasn’t been updated since 2005, but I’d like to make sure before I return it for an alternative like Edirol or M-Audio.

    Any help would be appreciated.

    June 13, 2007 at 23:15 #10126
    NeoDavinci
    Participant

    Is this a matter of saving a template? (Sorry that isn’t more helpful, but I’d like to know the answer to your problem too)

    June 14, 2007 at 10:19 #10127
    Conquistador
    Participant

    @MoodyB wrote:

    I’m tempted to say its a Emu driver prob as it hasn’t been updated since 2005, but I’d like to make sure before I return it for an alternative like Edirol or M-Audio.

    Any help would be appreciated.

    Hi,

    If I then enable the interfaces in the audio/midi prefs in Podium they seem to work fine.

    I would have thought that was a set and forget option, perhaps you really do have another application running in the background that is using your device?

    Not sure how much this might help but…have you tried downloading and installing the very latest drivers for your EMU USB interface?

    Or did you mean the EMU drivers have not been updated by EMU since 2005?

    Is your device always powered on first before starting Podium?

    I wish I could offer more help but I have not come across that kind of error before. 🙁

    I just had a quick look on EMU’s site they do have 2007 drivers for the xmidi 2×2 and 1×1 products.

    http://www.emu.com/support/files/download2.asp?Centric=1009&Legacy=&Platform=1

    That might solve your problem or at least narrow down the cause hopefully. 😉

    HTH

    June 14, 2007 at 10:53 #10130
    MoodyB
    Participant

    Thanks for the replys guys.

    Downloaded the drivers from Emu’s website, but the installer says I already have the latest version installed ( v5.12.1.2 – 19/07/05 ) so I guess the only changes were adding Vista compatability.

    Tried starting Windows with the interface disconnected then plugging it in. Still the same problems.

    Tested the midi ports in Bars&Pipes through the WinUAE emulator and they’re working fine.

    If I run DXDiag, the XMidi ports are shown as [emulated] in the Music tab, although they still playback the midi test properly.

    Tried different USB ports with no joy either. I do have a PCI USB card sitting here unused, so I’ll install it and see if it makes any difference.

    June 14, 2007 at 13:48 #10131
    Zynewave
    Keymaster

    You’re not the first to report problems with EMU MIDI drivers. I’ve added extra MIDI error logging in the 1.89 release, which is going up later today. When you try this, go to the report page and tell me the MIDI error shown in the report.

    June 14, 2007 at 15:14 #10132
    MoodyB
    Participant

    Thanks Frits.

    I’m going to see if I can return the Emu interface and get an Edirol one instead tomorrow.

    June 14, 2007 at 15:37 #10135
    Zynewave
    Keymaster

    @MoodyB wrote:

    Thanks Frits.

    I’m going to see if I can return the Emu interface and get an Edirol one instead tomorrow.

    If you have time, please try the EMU interface with release 1.89. I’m curious to know what error message is logged for the EMU.

    June 14, 2007 at 16:00 #10136
    MoodyB
    Participant

    Just tried 1.89. I no longer get the error message, but the midi inputs / outputs are still inactive every time Podium is opened. Here’s the contents of the report.txt :

    Podium audio manager status report
    Log period: 14/06/2007 16:55:14 – 14/06/2007 16:55:49

    ASIO device: Creative ASIO
    – Supported clock sources: Internal
    – Current clock source: Internal
    – Supported sample rates: 44100, 48000, 88200, 96000
    – Current sample rate: 44100
    – Input channels: 22 (0000000000110000000000)
    – Output channels: 18 (111111000000000000)
    – Input/Output latency, buffer size: 188/88, 88
    – PerformanceCounter: 3579545 Hz
    – ASIO sample types: 18, 18

    Audio stream buffer errors:
    – Output buffer skip count: 93

    End of report

    For some reason, 1.89 would crash on startup until I deleted my podium.ini file for v1.87 from ‘ Application DataZynewavePodium ‘

    June 14, 2007 at 16:02 #10137
    Zynewave
    Keymaster

    If you select the EMU MIDI interfaces, exit Podium and restart Podium, doesn’t the error message appear then?

    June 14, 2007 at 16:14 #10138
    MoodyB
    Participant

    No, I don’t get the error message anymore. Midi ports are still inactie upon restart though.

    Maybe it had something to do with deleting my old podium.ini file ? I still have the v1.87 ini file if you want to see if anything in that could have been causing the error message to appear ?

    June 14, 2007 at 16:28 #10139
    Zynewave
    Keymaster

    Yes, please send the 1.87 ini file.

    Are you saying that if you select the EMU interfaces, exit and restart, then the interfaces are no longer selected in the interfaces dialog?

    If so, that is very strange. It suggests that the Podium.ini file is not saved properly when Podium exits.

    June 14, 2007 at 17:14 #10144
    MoodyB
    Participant

    @Zynewave wrote:

    Yes, please send the 1.87 ini file.

    I’ve rar’d up the 1.87 ini and 1.89 ini files here :

    http://www.savefile.com/files/809302

    Are you saying that if you select the EMU interfaces, exit and restart, then the interfaces are no longer selected in the interfaces dialog?

    Yes

    If so, that is very strange. It suggests that the Podium.ini file is not saved properly when Podium exits.

    It seems to be saving the .ini file as it remembered my colour prefs, etc, it just doesn’t activate the midi ports even though they are listed in the .ini file properly.

    June 14, 2007 at 19:43 #10148
    Conquistador
    Participant

    I have now had this exact same error with Podium 1.89. 😯 I am using an Edirol UA25. The interface works properly in Sonar but Podium keeps giving me the same error message that Moody B has been getting.

    I am having this problem on Windows xp.

    June 14, 2007 at 20:42 #10150
    MoodyB
    Participant

    Try doing what I did and delete the prodium.ini file ( make a backup first though 🙂 ), the restart v1.89 so it writes out a new one.

    I’m almost 100% certain that’s what stopped the error messages for me, but I’m just about to check something else to be sure.

    June 14, 2007 at 22:22 #10153
    Zynewave
    Keymaster

    It seems to be saving the .ini file as it remembered my colour prefs, etc, it just doesn’t activate the midi ports even though they are listed in the .ini file properly.

    I think I have an answer to that. I looked at your ini files, and it seems that the EMU interface names have a space at the end. This space is saved in the ini file, but when the Windows API function loads the string from the file, this space is removed. Thus the device name comparison no longer matches.

    To make this work I need to remove the trailing spaces from the device names before doing any comparisons. I’ll fix that for 1.90.

Viewing 15 posts - 1 through 15 (of 20 total)
1 2
  • You must be logged in to reply to this topic.