[sdiy] [Polluriel détecté] Re: Reliable MIDI recording app for PC.. Or my Sonar X3 Pro DAW is not set correctly..

[jpdesroc at oricom.ca]

My program only outputs the following MIDI datas:

NOTE ON (paper hole detected)

NOTE OFF (paper hole finished)

ALL NOTES OFF (when rewinding my paper rolls only. Never else)

 

So there is no ‘big’ MIDI traffic involved here to the Sonar MIDI input.

But the number of voices can go up to around 20 in some parts
of songs but rarely. Mostly around 10-15 notes played at the same time.

 

Mike Briant asked:

>> What else is on the USB connectors of the PC ?   Anything else taking lots of bandwidth (a USB3->HDMI display for example ?)

I use a 5 pins DIN MIDI connector to my Focusrite Scarlett 2i4 USB device.

No other USB devices used on my PC during MIDI recordings.

 

I tried using only Notes and remove System Exclusive from the
‘authorized’ record datas.

It improved the recorded datas but still some lags inserted
here and there..

 

 

De : Synth-diy <synth-diy-bounces at synth-diy.org> De la part de John Speth via Synth-diy
Envoyé : 30 octobre 2025 11:03
À : SYNTH DIY <synth-diy at synth-diy.org>
Objet : Re: [sdiy] [Polluriel détecté] Re: Reliable MIDI recording app for PC.. Or my Sonar X3 Pro DAW is not set correctly..

 

>> Do the hesitations happen in the same way each time when you start playback?  

Yes. Same way, same places. The lags are recorded on the MIDI track.

"The lags are recorded on the MIDI track."???  Does that mean the gaps are in your recorded event list?  If so, that's not a playback problem. That's a recording problem. Your filter is set to record note on/off and sysex. Does your event list only contain note on/off and sysex? If you change your filter to not record sysex, do you still have valid test conditions for you to see the problem?  IOW, if you don't record sysex, will playback be silent because sysex was needed? Disable sysex recording as a test. There's no lasting harm in doing so I assume.

I think the next step is to monitor MIDI data with a MIDI monitor during recording. There might be some sort of MIDI data clogging up the MIDI stream. MIDI is capacity limited. So, for example, if sysex is constantly being pumped along with note on/off, you could plausibly see hesitations. Monitor in both directions (if you're using both directions).

I recently had a Cakewalk experience that showed a bug regarding .MID files. I took an interest in the "Situation" by Yazoo MIDI file. When I loaded it into free Sonar, I had many problems running it (problems I don't remember). I tried two other .MID files and never had the same problems. I concluded that the Yazoo .MID file contained something that corrupted Cakewalk. I tried the same exercise with Bandlab and noted the same problem. I concluded that there is some sort of bug associated with some .MID files in Cakewalk and that the this mysterious bug has been around for a while. I would try a different sequencer. You should be able to find at least a few free ones, including online sequencers. The bottom line is: CW has bugs and it probably always will.

If you haven't done so yet, install and use MIDI-OX. It's a swiss army knife tool for MIDI. It has a MIDI monitor and will let you confirm your MIDI data that you record has no hesitations by taking Sonar out of the picture.

JJS

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://synth-diy.org/pipermail/synth-diy/attachments/20251030/96166ecc/attachment.htm>