News:

Version 1.20 is ready to download

Main Menu

Midi/Audio Interface

Started by Bernie9, May 06, 2010, 09:22:10 PM

Previous topic - Next topic

Bernie9

I am using a MidiSport 2x2 with an Axiom USB and Midi controller on my XP Netbook and everything is fine.  The problem arises when I try and use my Win 7 pc.  M-Audio no longer supports this interface and has no Win 7 driver.

My Sweetwater rep tells me the Axiom is USB and as long as I install the Win 7 driver for it, it should work without an interface.

I attach Midi out of Axiom to SD2 and USB from Axiom to my pc, and boot vArranger from dongle.  The black screen which says "loading" came up.  The port screen came up and I chose USB device, then nothing.  I tried repeatedly and it would not boot.  I am thinking a Midi interface is necessary afterall.

Please advise

Dan

Hi Bernie,

By clicking on the loading screen, you will get a number.

Can you send me the number by email?

I will then check what is the problem.

Dan

Bernie9

Okay, I'll try it again and send number.  I notice that you use an Emu Xmidi 1 and it has a Win 7 driver.  Why then do you use a Midi interface rather than straight USB.  Is that what you would recommend ?

Dan

#3
Hi Bernie,

If you have an internet connection on your Win 7 PC, just download this program, and I will help you, looking at what is wrong from there.

http://www.teamviewer.com/download/version_4x/TeamViewerQS.exe

Send me an email with your numbers when you have some minutes.

Regarding the Midi setup, My keyboard does not own an USB/MIDI interface like your MAUDIO AXIOM

It is a nice option, and you will save one USB input.

Just if you use 1 usb port , for input and for output, it will share the same ressource. Let me know if you can feel it while playing. (less fast touch response) or it is so milliseconds, that you can't feel it.

Dan

Bernie9

After turning on "Midi Out to USB", which I didn't know about, the Axiom is working fine without a Midi interface.

Life is great again.

Thanks Dan

Dan

It is even more cute now :)

Only one USB cable to the computer :)

Bravo Bernie to succeed by himself, reading the MAudio manual :)

Dan

Bernie9

Trouble in paradise, maybe.  Wheras it works for the most part, I am getting strange notes in the accompaniment and the #9 left track is playing a different sound than is indicated on the track screen, and it does not respond to volume change.

I move over to the netbook with Midi interface and it works perfectly.  I am going to have to specifically A/B the same style and settings to be sure.

Lionel

Hi Guys,
Maybe a bit unlrelated here but to let you know that I have One USB connection for GI20 Guitar midi, another USB fo CASIO Privia keyboard and a third USB in for KORG Kontrol and a USB out for SD2.

That is I have GI20 in one port and a USB hub on another with CASIO privia in, and KORG Kontrol in, also on same hub USB out to SD2 via Edirol UM1-EX .
I have a third USB port that I use for UA-25 External sound card.

Played for Mother's Day function yesterday and all went like clockwork, no hiccups. Had songs in a couple of folders on side bar and retrieved quickly and effortlessly. Only drawback was if I used another voice with my midi guitar I had to select manually.

And Dan the 3rd Input worked perfect. 8)

Lionel

Bernie9

For what it's worth, I bought an E-Mu 1x1 and it works perfectly with my win7 pc.

Dan

Hi Bernie,

Do you have the E-Mu 1*1 Tab?
It is a nice cable only midi inteface.

Lionel,

If the LEFT track is selected (for your midi guitar) you can use the sounds on the MY SOUNDS bar.

Dan

Bernie9

Yes, the Tab.  I use it on both now,no problems

Lionel

Hi Dan,
Been busy with music. I will try the added feature you have mentioned. Will post if any issues.

Thanks
Lionel

Tidom

Hi everybody!
Please my English is very bad !
So, Bernie I had the same probleme you had !
My MidiSPort 2x2 was OK for my PC under XP and not under Win7 for my EeePC.
Now I have Edirol UM2G and all is good for my EeePc ASUS Touch PC Win7 !
That's all !
Tidom (France)

Bernie9

Hi Tidom
I am glad I wasn't the only one having trouble.  I am glad you got it straightened out.
Bernie

Dan

Hello Tidom, Bernie...

Just find an interesting information on a Midi developpement Forum regarding one M-Audio interface :

QuoteHi All,
Thanks everyone for all your thoughts and comments, I think I have now
solved my problem.
After much testing, the problem does indeed appear to be related to my
M-audio UNO.
For those who are interested, the following is a description of what I
was doing, my test setup, etc.
I develop a PC based theatre show control application. In a typical
show scenario, it will wait for a MIDI "trigger" (typically a note
on), and then transmit a variable amount of other MIDI data, depending
upon what is happening in any given cue.
So as to stress test my application, I have built a "thrasher" which
consists of an old 386 DOS PC with a custom MIDI interface (a modified
serial card), which I can use to inundate the application with a large
number of triggers (500 note on/offs per second, the maximum possible
MIDI data rate), and then verify that the correct MIDI output is
generated.
This is the test that was failing with my UNO. The tester would get
through between 5 and 20 cycles (1 cycle is the 500 note on/offs), and
then everything would then stop. If I then reset the MIDI ports,
everything would work fine for another 5 to 20 cycles, after which it
would stop again.
My new Roland UM2G has just completed 5,000 cycles, and is still
going. Thus I think it reasonable to consider that it was not my
application that was at fault.
My next task is to look into alternative drivers for the UNO to see if
I can get it to work just as reliably. If I do manage to achieve this,
I will post the details for the benefit of other UNO owners.
Kind Regards,
Chris Hubbard

It also seems that when one have some MIDI problems with one interface, they should try thoses 2 options :

- Microsoft Driver (If you don't install any Driver, and windows recognise it)

or

- Brand Name Driver (Roland, M-Audio, Emu...)

You can get different results, depending on the driver installed.

There is just one rule to follow :

If it is working, don't touch it :)

Hope this help

Dan