Mega bug with Busses PT10.01

[Robsab]

Hi
I just bump into a serious bug. Further than the 32 default busses, I have created 32 stereo and some mono busses in I/O. Have named them and assigned. Saved the session.

When I reopen the session most of the new busses are all wrong. IN the SENDS the busses are incorrect and in the AUX input tracks some have also its input incorrectly as well.

I fixed manually the busses several times and saved the sessions trying both enabling and not enabling "Sessions overwrite current I/O", but when the session reopens the problems always persist.

Anyone found a solution for this bug?

thanks!

[Robsab]

Beside all the above problems, I have just noticed that Protools even allows me to create a new bus taking the name of an already existing bus. This is a nonsense. It should advise that this name is already taken by another bus!.

[jjamesbomb]

There's def something weird going on right now w I/O assignment. Sometimes when I add a new track other ones stop playing and I have to reboot...

[crizdee]

Originally Posted by Robsab

Hi
I just bump into a serious bug. Further than the 32 default busses, I have created 32 stereo and some mono busses in I/O. Have named them and assigned. Saved the session.

When I reopen the session most of the new busses are all wrong. IN the SENDS the busses are incorrect and in the AUX input tracks some have also its input incorrectly as well.

I fixed manually the busses several times and saved the sessions trying both enabling and not enabling "Sessions overwrite current I/O", but when the session reopens the problems always persist.

Anyone found a solution for this

thanks!

Hi,

In the I/o setup page have you got a tick for... Session overwrites current I/o setup?

Chris

[DJ Hellfire]

Originally Posted by Robsab

Hi
I just bump into a serious bug. Further than the 32 default busses, I have created 32 stereo and some mono busses in I/O. Have named them and assigned. Saved the session.

When I reopen the session most of the new busses are all wrong. IN the SENDS the busses are incorrect and in the AUX input tracks some have also its input incorrectly as well.

I fixed manually the busses several times and saved the sessions trying both enabling and not enabling "Sessions overwrite current I/O", but when the session reopens the problems always persist.

Anyone found a solution for this bug?

thanks!

It's not 10.0.1. It's 10 period. I've had this problem since 10.0. Really aggravating.

Also, some times when I used "bus to new track", Pro Tools creates a new track with the new bus inactive and you can't make it active. The problem is Pro Tools assigns the new bus with a Mapped Output (which is confusing in itself) and you have to go into the i/o menu and uncheck the new bus' Mapped Output in order to make the bus active. I don't know why it does this but it pisses me off!

[DJ Hellfire]

Originally Posted by crizdee

Hi,

In the I/o setup page have you got a tick for... Session overwrites current I/o setup?

Chris

Yes, I do!

[Robsab]

Originally Posted by crizdee

Hi,

In the I/o setup page have you got a tick for... Session overwrites current I/o setup?

Chris

Hi

Yes I did try several times but nothing got solved.

I found a workaround that for the time being is working. I just deleted from I/O "delete path" those busses that were causing problems (that actually were always the same). Then I created new ones with different names and problem solved.

I think the bug appears when most of the default busses are renamed and more busses are created in I/O, then the new Bus 1-2, bus 3-4 are mistaken by those original busses that have been renamed. At least is what the bug did to me.

Please AVID provide us with a fix for this.

[NewdestinyX]

Originally Posted by DJ Hellfire

It's not 10.0.1. It's 10 period. I've had this problem since 10.0. Really aggravating.

Also, some times when I used "bus to new track", Pro Tools creates a new track with the new bus inactive and you can't make it active. The problem is Pro Tools assigns the new bus with a Mapped Output (which is confusing in itself) and you have to go into the i/o menu and uncheck the new bus' Mapped Output in order to make the bus active. I don't know why it does this but it pisses me off!

+1. Totally frustrating bug! Agreed -- since 10.0.0 too. The whole 'mapping' a bus to an output thing is a huge mystery to me too. Does anyone know the underpinnings of why the bus window had to change to accommodate this functionality as of PT9 anyway? It worked PERFECTLY the old way. Busses were busses, Ins were Ins and Outs were outs. So simple... oy... *sigh*

[gives]

Originally Posted by Robsab

Hi

Yes I did try several times but nothing got solved.

I found a workaround that for the time being is working. I just deleted from I/O "delete path" those busses that were causing problems (that actually were always the same). Then I created new ones with different names and problem solved.

I think the bug appears when most of the default busses are renamed and more busses are created in I/O, then the new Bus 1-2, bus 3-4 are mistaken by those original busses that have been renamed. At least is what the bug did to me.

Please AVID provide us with a fix for this.

YUP.. I think that is when I have had problems too! I am going back to the old "Standard" bus names. G

[thierryd]

Originally Posted by NewdestinyX

+1. Totally frustrating bug! Agreed -- since 10.0.0 too. The whole 'mapping' a bus to an output thing is a huge mystery to me too. Does anyone know the underpinnings of why the bus window had to change to accommodate this functionality as of PT9 anyway? It worked PERFECTLY the old way. Busses were busses, Ins were Ins and Outs were outs. So simple... oy... *sigh*

FWIW it wasn't "perfect" either before PT9. The changes were introduced in PT9 for the new interfaces (suchs as Omni) and they do make sense (plus there was the benefit that the busses went up from 128 to 256 which was a much needed change). Also it's good that PT searches for free buss paths by itself, compared to the old way.
The unfortunate thing is that it is still buggy. Basically I don't thrust things that PT does "automatically". I don't use ADC, nor DSP cache because of this. The new I/O structure can't be bypassed so I learned to work around the buggy behavior which basically means that you should build the session or template till it has everything you need (busses, tracks, sends etc.) and then quit PT and restart. I found that with PT10 adding tracks or changing the I/O while mixing, will almost guarantee a crash sometime after the change. If you don't change the structure of the PT session, PT will be fairly stable. This is especially so if you work agains the dsp and native limits of the system (which I do a lot)

Greetings,

Thierry