Steve Fogal wrote:...at least in your experience Ok, I know that 16 midi channels is the 'maximum' ... but I'm talking 'reliably'.
Until the other day, the most midi channels I've send down a single cable has been maybe 5 tops! And that figure wasn't met until a couple/few months back.
As of last night, I think I had about 13 or 14 midi tracks all sending on a corresponding channel. So far so good..though my machine froze and had to be restarted..but that's happened with far less too, so not sure if a lot of midi tracks & high channel count was the issue.
But I read the other night, that in order to relieve midi conjestion of a single cable & midi port...multiple ports are sometimes used with more midi cables...each carrying a limited number of midi channels.
I'm in the proccess of putting this to the test..that is piling up the midi channels...I just ran out of time to get a few more or so midi tracks to the full 16. Me, I'm not using many midi messages (not that I know anyway). The only thing I'm use is Velocity..no other intentional perameters.
But maybe if other things in the way of midi automations etc, would limit a full 16 channels??
Steve Fogal wrote:Elektro, I guess it sounds like 'it all depends' with this stuff. At least I'm gathering some information here now on what things can be done when the time comes that my midi is scewing me
Steve Fogal wrote:I've never used or needed any kind clock on midi before. Actually, even on digital audio I've not been able to perceive any difference with clock or no clock.
Steve Fogal wrote:
So... with that said, the question is; How important is Word Clock & Midi Clock?
This, as opposed to the common syncing of different devices, running in their own PLAY mode
Steve Fogal wrote:Ok, steering back to the original topic... if running the full 16 midi channels going through a single 5-pin midi cable is too much, or not. For which the replies I got indicated that it can depend on how much controller event information is also being fed through along with it. Since I'm not exactly sure of what's being sent along with my midi test tracks - which are very simple parts that I've not 'purposely' added controller messages too - And so I procceed...
Well I'll be a monkeys uncle.... just last night I added more midi tracks for my testing. I had 13 midi channels before (not 14) going through the one midi cable. I've now reached the full 16 channels... so far, absolutely no problems running them for over an hour (not straight).
While these 16 midi channels were playing, on I was having a look at my resources on both quad computers. But 1st I eliminated my main DAW's original few loaded VSTi's when setting the test project up. I just wanted to see those little bit of resources drop! (there's no audio in this midi test tune).
On the midi receiving machine, surprisingly, I had fairly low CPU resources being sucked up.., except for ram was at 1st up to 90+ %. While the midi sending machine with only midi tracks & no VSTi's loaded showed extremly minimal resource usage ... I couldn't even see the yellow memory graph & the VSTi meter was almost nothing.
I was continuing to check things...closed the projects...reopened & very oddly, the receiving computers ram usage that
showed over 90% just before, was now showing almost nothing, and still playing fine... this cannot be
Maybe before I had a ram spike for some unknown problem going on. I'm actually going to do more testing now. It's either that the midi receiving VSTi computer is maxed, or it's not...but it's certainly not stuttering, crackling/popping or
anything yet. On just my main DAW, far less VSTi's - though had lots of audio & FX's did a bucking bronco number on
For another test; I'll be sending this same midi test tune with 16 channels to an outboard midi sound module to see if they cave in
Steve Fogal wrote:...just because I'm nuts!
Indiana Jones wrote:"...it ain't the years, it's the mileage, baby..."
Users browsing this forum: swamptone and 5 guests