From: Jason J. <j...@po...> - 2004-08-30 03:57:12
|
Hello all.... Please excuse the frustration, but I've been working with Muse trying to get it right now for at least a month. I'm a "do-it-yourself" kind of guy, so.... this is my last hope. I'm trying to do something that is evidently super simple, but I must be missing something cause it ain't working. Here's my situation: I've got a Roland RS-9 keyboard (GS) and a Soundblaster Audigy Pro EX sound card. I've got my MIDI OUT on my keyboard plugged into my break-out panel's MIDI IN and the MIDI OUT on my keyboard plugged into the MIDI IN on the panel. I've read the manual and all the tutorials I could find on how to record MIDI data from my keyboard with MusE. Nothing too hard, right? Yeah, I thought so too. I know my ports (at least the output port) is set correctly because I can control my keyboard with MusE (I.E. changing the program in the MusE program correctly changes the program in my keyboard. When I want a flute, I change the program to flute in MusE and my keyboard reflects those changes just fine.) I assume this means the keyboard / MusE MIDI setup is at least communicating. My problem, however, doesn't have to do with the OUTPUT. I cannot, for the life of me, get MusE to recognize any input from the keyboard. I mean.. When I play my keyboard - MusE just sits there with a dumb smile on its face like its waiting for me to do something. I hit record and play - the tracker (not sure of the proper terminology) bar moves along the tracks window like it should... But when I play something... that vertical tracker bar just keeps on trotting along the tracks window as if it were waiting for something. Nothing (and I mean nothing) is recorded. When I hit stop, it stops and rewinds itself to the beginning as if nothing had been recorded. I hit play, and it won't move because there isn't anything in the track. Also.... the midi-thru function of MusE has problems. When I turn local control off on my keyboard - I can't hear anything through my computer. I can hear my keyboard just fine when it's on - but nothing when it's off. Oh... I tried turning on / meddling with the metronome, and lo-and-behold, I heard the metronome! And it was being played through my keyboard! When I turned down the volume on my keyboard, the metonome reflected it! Not sure what that means, but... I thought it'd help anyone understand a bit more of my problem. I've tried switching the MIDI In/Out cables, to make sure it wasn't a faulty cable, and nothing changed - so... no faulty cables. There's got to be some little thing I'm missing, and it's driving me nuts. If anyone has any clue as to something I'm not doing, or missing, or doing wrong... Please help. I'll be more than happy to answer any questions regarding this problem... I'm sure it's just some little thing I'm missing due to my ignorance. Thanks for your patience. frustrated, Jason PS - I used this same setup in windows to record with Cubase VST and it worked wonderfully.... So, I know it can be done with this setup. |
From: Crispin C. <cc...@oh...> - 2004-08-30 09:56:02
|
Jason, Try checking that midi input is happening at all. Type cat /dev/midi00 into a terminal, play some notes on the keyboard, see if any characters appear on screen. Let us know what happens. Assuming it is, try launching kaconnect or the midi patchbay inside qjackctl and see if muse is connected to the midi input. Also (though I assume migrating from cubase you wouldn't make this mistake, but forgive me for suggesting!) - check you have armed a track for recording in the sequencer. If on the other hand cat /dev/midi00 shows nothing, try all the other midi devices in /dev and get back to the mailing list... -- Crispin |
From: Jason J. <j...@po...> - 2004-08-30 15:01:44
|
Thank you so much for your prompt reply, Crispin. I tried cat'ing my MIDI nodes, but I don't have a /dev/midi00 node. What I do have is: /dev/midi /dev/snd/midiC0D0 /dev/snd/midiC0D1 /dev/snd/midiC0D2 /dev/admmidi /dev/dmmidi /dev/amidi I cat'ed all of em' yesterday and didn't get a thing while pressing keys. I guess that means the problem goes beyond MusE eh'? Maybe there's something I'm not doing right in my kernel? Maybe MusE can't find the right MIDI port? Is there any way to see what MIDI node MusE is looking for its input? Another FYI that might help is.. I've got like.... 6 MIDI ports to choose from in the midi port configuration inside MusE. MPU 401 MPU 401 #2 EMUK101 #1 EMUK101 #2 EMUK101 #3 EMUK101 #4 and the one from qjackctl The one from MPU401 #2 is the one that allows the computer to control the keyboard (same with Cubase). I've tried through all of em' with no success in inputting. and yeah.. I made sure I had all tracks armed to record when I try. ;-) Always good to check, though. --Jason Crispin Cooper wrote: >Jason, > >Try checking that midi input is happening at all. Type cat /dev/midi00 into >a terminal, play some notes on the keyboard, see if any characters appear on >screen. Let us know what happens. > >Assuming it is, try launching kaconnect or the midi patchbay inside qjackctl >and see if muse is connected to the midi input. Also (though I assume >migrating from cubase you wouldn't make this mistake, but forgive me for >suggesting!) - check you have armed a track for recording in the sequencer. > >If on the other hand cat /dev/midi00 shows nothing, try all the other midi >devices in /dev and get back to the mailing list... > >-- >Crispin > > > >------------------------------------------------------- >This SF.Net email is sponsored by BEA Weblogic Workshop >FREE Java Enterprise J2EE developer tools! >Get your free copy of BEA WebLogic Workshop 8.1 today. >http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click >_______________________________________________ >Lmuse-user mailing list >Lmu...@li... >https://lists.sourceforge.net/lists/listinfo/lmuse-user > > > > |
From: Robert J. <rj...@sp...> - 2004-08-30 15:32:25
|
On Monday 30 August 2004 18.01, Jason Jones wrote: > Thank you so much for your prompt reply, Crispin. > > I tried cat'ing my MIDI nodes, but I don't have a /dev/midi00 node. > What I do have is: > > /dev/midi > /dev/snd/midiC0D0 > /dev/snd/midiC0D1 > /dev/snd/midiC0D2 > /dev/admmidi > /dev/dmmidi > /dev/amidi > > I cat'ed all of em' yesterday and didn't get a thing while pressing > keys. I guess that means the problem goes beyond MusE eh'? Maybe > there's something I'm not doing right in my kernel? Maybe MusE can't > find the right MIDI port? Is there any way to see what MIDI node MusE > is looking for its input? > > Another FYI that might help is.. I've got like.... 6 MIDI ports to > choose from in the midi port configuration inside MusE. > > MPU 401 > MPU 401 #2 > EMUK101 #1 > EMUK101 #2 > EMUK101 #3 > EMUK101 #4 > > and the one from > > qjackctl > > The one from MPU401 #2 is the one that allows the computer to control > the keyboard (same with Cubase). I've tried through all of em' with no > success in inputting. > > and yeah.. I made sure I had all tracks armed to record when I try. > ;-) Always good to check, though. Hi Jason, I'd agree that the audigy is the most probable cause at the moment. I had an audigy a while ago and I had problems with the break-out box too. No doubt support has improved, but still you might need to do something "extra". If possible I suggest you try to connect the keyboard on the back of the card instead (Should be MPU #1 then), should give definitive proof. One other thing to check, that's a bit easier ;), Is to check in synth configuration dialog that the [I] column is properly selected for the keyboard (MPU #2 according to your info). Regards, Robert > > --Jason > > Crispin Cooper wrote: > >Jason, > > > >Try checking that midi input is happening at all. Type cat /dev/midi00 > > into a terminal, play some notes on the keyboard, see if any characters > > appear on screen. Let us know what happens. > > > >Assuming it is, try launching kaconnect or the midi patchbay inside > > qjackctl and see if muse is connected to the midi input. Also (though I > > assume migrating from cubase you wouldn't make this mistake, but forgive > > me for suggesting!) - check you have armed a track for recording in the > > sequencer. > > > >If on the other hand cat /dev/midi00 shows nothing, try all the other midi > >devices in /dev and get back to the mailing list... > > > >-- > >Crispin > > > > > > > >------------------------------------------------------- > >This SF.Net email is sponsored by BEA Weblogic Workshop > >FREE Java Enterprise J2EE developer tools! > >Get your free copy of BEA WebLogic Workshop 8.1 today. > >http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click > >_______________________________________________ > >Lmuse-user mailing list > >Lmu...@li... > >https://lists.sourceforge.net/lists/listinfo/lmuse-user > > ------------------------------------------------------- > This SF.Net email is sponsored by BEA Weblogic Workshop > FREE Java Enterprise J2EE developer tools! > Get your free copy of BEA WebLogic Workshop 8.1 today. > http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click > _______________________________________________ > Lmuse-user mailing list > Lmu...@li... > https://lists.sourceforge.net/lists/listinfo/lmuse-user -- http://spamatica.se/music/ |
From: Jason J. <j...@po...> - 2004-08-30 15:59:42
|
Robert Jonsson wrote: >On Monday 30 August 2004 18.01, Jason Jones wrote: > > >>Thank you so much for your prompt reply, Crispin. >> >>I tried cat'ing my MIDI nodes, but I don't have a /dev/midi00 node. >>What I do have is: >> >>/dev/midi >>/dev/snd/midiC0D0 >>/dev/snd/midiC0D1 >>/dev/snd/midiC0D2 >>/dev/admmidi >>/dev/dmmidi >>/dev/amidi >> >>I cat'ed all of em' yesterday and didn't get a thing while pressing >>keys. I guess that means the problem goes beyond MusE eh'? Maybe >>there's something I'm not doing right in my kernel? Maybe MusE can't >>find the right MIDI port? Is there any way to see what MIDI node MusE >>is looking for its input? >> >>Another FYI that might help is.. I've got like.... 6 MIDI ports to >>choose from in the midi port configuration inside MusE. >> >>MPU 401 >>MPU 401 #2 >>EMUK101 #1 >>EMUK101 #2 >>EMUK101 #3 >>EMUK101 #4 >> >>and the one from >> >>qjackctl >> >>The one from MPU401 #2 is the one that allows the computer to control >>the keyboard (same with Cubase). I've tried through all of em' with no >>success in inputting. >> >>and yeah.. I made sure I had all tracks armed to record when I try. >>;-) Always good to check, though. >> >> > >Hi Jason, > >I'd agree that the audigy is the most probable cause at the moment. I had an >audigy a while ago and I had problems with the break-out box too. No doubt >support has improved, but still you might need to do something "extra". > >If possible I suggest you try to connect the keyboard on the back of the card >instead (Should be MPU #1 then), should give definitive proof. > >One other thing to check, that's a bit easier ;), Is to check in synth >configuration dialog that the [I] column is properly selected for the >keyboard (MPU #2 according to your info). > >Regards, >Robert > > Hey Robert. Thanks for the advice. Right now I don't have the correct cables to connect my first midi port up, although I'll look around and see what I can find. And about the synth configuration dialog... I'm not sure what you mean, but if you mean to make sure the track I'm recording on has the correct port activated - it does. Crud... Looks like I'm just a victim of insufficient driver support. I'm SO close to recording MIDI in Linux... I feel like I'm drowning under a centimeter of water. So close - yet still dead in the water. If anyone can think of any patches or anything I can do to test or upgrade ALSA's MIDI support for the SB Audigy Pro EX, I'd be most grateful. Thanks again! --Jason |
From: Crispin <cc...@oh...> - 2004-08-30 15:33:26
|
> I tried cat'ing my MIDI nodes, but I don't have a /dev/midi00 node. =20 Ah. I'm afraid I'm no expert on what's happening then, but: 1. Maybe the soundcard is not properly configured? There's a useful = page on this here http://ccrma.stanford.edu/planetccrma/software/installkernelandsound.html= 2. If that doesn't help, and nobody on this list replies, try the planet ccrma list (linked from that site) or maybe the ALSA project has one. > MPU 401 > MPU 401 #2 > EMUK101 #1 > EMUK101 #2 > EMUK101 #3 > EMUK101 #4 FYI - I think these are all outputs - the first two are your external = ones (also inputs though), the next 4 are the soundblaster built-in synth (if = you get a program called sfxload, you can load soundfonts into this and use = it. Not bad if you don't have a sampler.) --=20 Crispin |
From: Jason J. <j...@po...> - 2004-08-30 15:53:24
|
Hmmm.... I think my soundcard is configured alright. I don't have problems listening to music or recording / playing audio in ardour... It might be a MIDI misconfiguration (which I know nothing about, or how to fix it) or it might just be bad drivers for the MIDI input.... Weird... I also gotta tell ya... about 6 months ago (when I was going through all of this before), I had been trying and failing hundreds of times, like now - but once - I turned on my computer and my keyboard, hooked it all up, and it worked just fine... Just about blew me over. I'm pretty sure I didn't configure anyting differently - I think it may have just been a transistor that decided to fire correctly or something. Anyway... I could record MIDI just fine that one time - but then I turned my computer off. I couldn't get it to work again - ever. Weird stuff. Anyway... Thanks for your help. I'll keep tryin'. --Jason PS - thanks for the tip on loading soundfonts. I'll keep that in mind. Crispin wrote: >>I tried cat'ing my MIDI nodes, but I don't have a /dev/midi00 node. >> >> > >Ah. I'm afraid I'm no expert on what's happening then, but: > >1. Maybe the soundcard is not properly configured? There's a useful page on >this here >http://ccrma.stanford.edu/planetccrma/software/installkernelandsound.html > >2. If that doesn't help, and nobody on this list replies, try the planet >ccrma list (linked from that site) or maybe the ALSA project has one. > > > >>MPU 401 >>MPU 401 #2 >>EMUK101 #1 >>EMUK101 #2 >>EMUK101 #3 >>EMUK101 #4 >> >> > >FYI - I think these are all outputs - the first two are your external ones >(also inputs though), the next 4 are the soundblaster built-in synth (if you >get a program called sfxload, you can load soundfonts into this and use it. >Not bad if you don't have a sampler.) > > > |
From: Frank N. <bea...@we...> - 2004-09-11 01:59:00
|
Hi list, this is already some days ago, but I thought I should comment.. Jason Jones <j...@po...> wrote: > Thank you so much for your prompt reply, Crispin. > > I tried cat'ing my MIDI nodes, but I don't have a /dev/midi00 node. > What I do have is: > > /dev/midi > /dev/snd/midiC0D0 > /dev/snd/midiC0D1 > /dev/snd/midiC0D2 > /dev/admmidi > /dev/dmmidi > /dev/amidi > > I cat'ed all of em' yesterday and didn't get a thing while pressing > keys. I guess that means the problem goes beyond MusE eh'? Maybe > there's something I'm not doing right in my kernel? Maybe MusE can't > find the right MIDI port? Is there any way to see what MIDI node MusE > is looking for its input? The correct MIDI device you'll want to try is one of the /dev/snd/... entries, and here a simple "cat" might not echo anything because you get back binary data which some terminal programs cannot handle correctly. What you should instead do is something like $ cat /dev/snd/midiC0D0 | xxd xxd is a hex dumper, and using the above line (and then playing something on the keyboard), hex data is printed out in chunks (not immediately after each NoteOn/NoteOff event, but that is xxd's internal line-by-line buffering). Just press different keys for some seconds, and you should see something. The fact that your MIDI out seems to work would let me guess that the ALSA MIDI driver for your soundcard is fine. Greetings, Frank (catching up with some old mail) > Another FYI that might help is.. I've got like.... 6 MIDI ports to > choose from in the midi port configuration inside MusE. > > MPU 401 > MPU 401 #2 > EMUK101 #1 > EMUK101 #2 > EMUK101 #3 > EMUK101 #4 > > and the one from > > qjackctl > > The one from MPU401 #2 is the one that allows the computer to control > the keyboard (same with Cubase). I've tried through all of em' with no > success in inputting. > > and yeah.. I made sure I had all tracks armed to record when I try. > ;-) Always good to check, though. > > --Jason > > Crispin Cooper wrote: > > >Jason, > > > >Try checking that midi input is happening at all. Type cat /dev/midi00 into > >a terminal, play some notes on the keyboard, see if any characters appear on > >screen. Let us know what happens. > > > >Assuming it is, try launching kaconnect or the midi patchbay inside qjackctl > >and see if muse is connected to the midi input. Also (though I assume > >migrating from cubase you wouldn't make this mistake, but forgive me for > >suggesting!) - check you have armed a track for recording in the sequencer. > > > >If on the other hand cat /dev/midi00 shows nothing, try all the other midi > >devices in /dev and get back to the mailing list... > > > >-- |