IO Limits? Changes in 2020?

[59.9hz]

Bit of a red herring, or a cruel April fools joke, i guess. It still only passes audio up to the 32nd input.


I also tested if removing all other inputs would allow passing audio past 32, but nope.


I feel like Charlie Brown when Lucy pulls away the football.


As I stated in my opening post, this is a deal killer for me, as I have more than 32 I/O. Even though I don't track with more than 32 I/O at the same time I use the extra I/O to configure sends, utility signals, and just smart cable numbering. The only way I can manage the "first 32" is by using another software patch-bay, as Pro-Tools limits to only the >first< 32 inputs.


If there was a change to still restrict to 32 inputs but allow channel numbers past 32 where I could choose which 32 are enabled, that would solve my issue.


This must be a bug.

[JFreak]

Sounds like a bug, but ... just but ... maybe they are giving this a thought? First step would be seeing all i/o, right? Then using all of it would be a bliss.

Until now you need to manage that first 32 i/o outside of PT

[59.9hz]

I gave up making predictions about PT back when 32bit was king.


It's really the tiered pricing model that keeps me from going to HD. I use PT mostly for session transfers these days.



I've adopted esssone... haven't had a crash since.

[BScout]

Not a bug.

Same as Dante DVS appears
Same as a lot of Apollos (with extended channel count) appear

It's been this way for a long time now. Doubt this is "giving thought" or anything. Just representing what CoreAudio gives it. There was a point where you had to limit what was visible/available (>32 channels) for an audio interface or Pro Tools would crash. A lot of developers (well Universal Audio and RME for two) wrote special driver modes which would only show 32 channels to Pro Tools to keep it from crashing. That was a bandage by audio interface makers.
Avid's fix, in the end, was to allow all channels to show -- just nothing over 32 would work. It was the simplest solution. And it's been this way for a long time now.

[smurfyou]

Originally Posted by JFreak

Very good question. Also would want to see screenshot that shows more than 32 i/o and proves it is not Ultimate

FWIW it wouldn't matter if it's Ultimate or not. You still only get 32 if you're running native.

[Emi]

Originally Posted by 59.9hz

Bit of a red herring, or a cruel April fools joke, i guess. It still only passes audio up to the 32nd input.


I also tested if removing all other inputs would allow passing audio past 32, but nope.


I feel like Charlie Brown when Lucy pulls away the football.


As I stated in my opening post, this is a deal killer for me, as I have more than 32 I/O. Even though I don't track with more than 32 I/O at the same time I use the extra I/O to configure sends, utility signals, and just smart cable numbering. The only way I can manage the "first 32" is by using another software patch-bay, as Pro-Tools limits to only the >first< 32 inputs.


If there was a change to still restrict to 32 inputs but allow channel numbers past 32 where I could choose which 32 are enabled, that would solve my issue.


This must be a bug.

What, it doesn’t pass audio??!!?????! I can’t believe it?

[JFreak]

Originally Posted by smurfyou

FWIW it wouldn't matter if it's Ultimate or not. You still only get 32 if you're running native.

Yes, but a pic of IO setup does not tell if you are running native or dsp. If this was April Fools, that pic could have been done with HDX system. Just trying to make sure it is what it is supposed to be...

[Emi]

Just tried to see if it passes audio, and No it doesn’t. So only first 32 I/O passes audio.

What a Joke...I think Pro tools Native it the only “pro” Daw that has a Limit on I/O. I should of thought we talk about Avid here....

[[email protected]]

Pro Fools 2020.3 ....

[59.9hz]

smurfyou: Thanks for the info, I did not know Ultimate native also only allowed 32 channels. No way am I forking out the cash for HDX to get higher I/O counts.


However, if they allowed addressing more than 32, but only allowed 32 active at one time, that would be helpful because it would eliminate the additional patch-bay required to move channels around to #32 and below.