Topic: midi recording problem on UC

hi, I've nbeen using my new fireface UC with windows xp Sp3 and sonar x1 expanded.
as this interface replaced my motu 828 (no midi i/o) my fastlane midi interface (that was working just fine) was replaced by the UC midi i/o.
Since then, though I have no problems recording and playing back audio (UC works just great), I do have this midi recording issue:

every time I record, once in a while (every 10 or 20 notes recorded) there's one midi note that sticks "on" as if there's no "midi note off" message recorded. So I get my performance with a bunch of very long notes ringing on for the whole length of the recording.

I'm using a Microkorg for input midi notes, as mentioned it worked perfectly with fastlane.
the notes that "remain ON" are random, is not always the same note.

Any idea if this is an incompatibility issue or if there's some tweaking (settings) to di to solve this??

THANKS A LOT, best

dd

Re: midi recording problem on UC

I experienced this with my old FF800. Since I have the UC, I have no problem anymore. FF800 was used with Sonar 8.5.3/Windows XP x32 SP3 and FF UC is used with Sonar X1c x64/Windows 7 x64 using the same midi controller (an e-drum).

Re: midi recording problem on UC

Manolo wrote:

I experienced this with my old FF800. Since I have the UC, I have no problem anymore. FF800 was used with Sonar 8.5.3/Windows XP x32 SP3 and FF UC is used with Sonar X1c x64/Windows 7 x64 using the same midi controller (an e-drum).

so you don't have an idea about why this happens? you couldn't find a solution under XP?
I'm using X1e 32 with XP SP3 32bit.

Thanks for your post! best
dd

Re: midi recording problem on UC

Nope, I think it was a problem with my FF800. I made a post about this years ago but I can't find it anymore. It's exactly what you describe.

I don't think it's a problem with Windows version cause nobody, even in RME found an answer when I asked for this.

Re: midi recording problem on UC

It's probably a case of midi control messages. Some messages are not received (take for instance volume vs. expression - volume is 7 and expression is 11) and may be a thing like that. If "notes off" messages are not being received all the time, perhaps you should look to the numbers being used for the output between your equipment, and what messages are to work. I know in older versions of Sonar, that you have to mark what midi messages will be looked at in Sonar. One such example again is "Aftertouch". Some keyboards do not give that message and although you can mark it as wanting to be received in Sonar, if the keyboard does not transmit such a message then it can not be received. Although in that case, nothing will happen, check Sonar to see what is going on with the midi messages in the program and between both the keyboard or unit transmitting midi messages and what is being received. Although "notes off" should be the same message in any unit transmitting midi message, perhaps the midi control message may not be. That is all I can think of, so I stopped using midi, and record only wave files now.

Re: midi recording problem on UC

spacealf, it doesn't come from Sonar I'm sure. I tried instead of my FF 800 the MIDI IN of my Aardvard 24/96 and it worked perfectly (same DAW, same midi controller). dede said its fastlane midi interface works well too.

Re: midi recording problem on UC

Manolo wrote:

spacealf, it doesn't come from Sonar I'm sure. I tried instead of my FF 800 the MIDI IN of my Aardvard 24/96 and it worked perfectly (same DAW, same midi controller). dede said its fastlane midi interface works well too.

indeed, fastlane worked ok with different versions of (Sonar including X1) for 8 straight years, no problem;
From the moment I installed FF UC this problem started with midi recording. first thing I tried was reducing the input information available for recording (aftertouch, sysex, etc, everything except notes), but I have the same problem, notes remain on....

Re: midi recording problem on UC

I have the exact same problem with a UC. My Yamaha S08 synth works flawlessly with my silly little hunk-of-plastic Edirol midi interface. The UC, though, creates hanging notes regularly. Logic shows the on and off messages as I play, but the notes ring regardless. I spent days thinking it was a problem with port matching, etc. I reset the keyboard to the original factory setting. Nothing worked. RME support was of no help. For the moment I'm using the UC just for audio and have gone back to the Edirol for midi. It does strike me as a bit of a joke, though, that I spent some big bucks for this box as an audio and midi interface, only the audio half works properly.

Jim

iMac, OS 10.6.8, Logic 9.1.4

Fireface UC, iMac i7 quad core, Logic 9.1.4, Yamaha S08 synth

Re: midi recording problem on UC

This may or may not apply to the OP, but my synth's LED screen showed an error message "!MIDIDATA!" This, according to the manual, indicates that the keyboard is receiving "invalid midi information." I was never able to sort out what that meant. Again, though, I've never received any such message when using the $29 Edirol plastic box.

Jim

Fireface UC, iMac i7 quad core, Logic 9.1.4, Yamaha S08 synth

Re: midi recording problem on UC

Studio162A wrote:

I have the exact same problem with a UC. My Yamaha S08 synth works flawlessly with my silly little hunk-of-plastic Edirol midi interface. The UC, though, creates hanging notes regularly. Logic shows the on and off messages as I play, but the notes ring regardless. I spent days thinking it was a problem with port matching, etc. I reset the keyboard to the original factory setting. Nothing worked. RME support was of no help. For the moment I'm using the UC just for audio and have gone back to the Edirol for midi. It does strike me as a bit of a joke, though, that I spent some big bucks for this box as an audio and midi interface, only the audio half works properly.

Jim

iMac, OS 10.6.8, Logic 9.1.4

I share you feelings about this, my 8 years old FastLane always worked flawlessly, spending these bucks on a new generation UC was supposed to be an upgrade, and dealing with midi data is not big deal in 2011, they should be able to fix this quite fast, but got no response from RME whatsoever.
Audio works great though.

cheers

dd