Delete unused Busses

[lode]

http://protools.ideascale.com/a/dtd/...tup/91252-3779

Can we get some votes on this?

It is ridiculous how many irrelevant buses I have to search through at times when something is routed incorrectly. And most of them are not used and haven´t been used in years.

[Craig F]

but is a bus unused or just not used right now, auto delete would not know the difference

I have extra Rev, Dly, & Cue Bus names in my I/Os

[lode]

Of course. It is not something you would use without being sure beforehand. But it would be very useful for some situations.

And it shouldn´t be that hard to implement.

[Craig F]

maybe Select All Unused Buses would be better

[Frank Kruse]

The whole bussing I/O assignment system PT needs a serious remodeling. Of course they can go on taping band-aids across the little things but the whole system needs to be worked over. With 700+ tracks running on HDX3 the current spaghetti routing system simulating patch-bays from an old console doesn't make sense anymore.

http://protools.ideascale.com/a/dtd/...er/118803-3779

Frank.

P.S.: Having said that, deleting unused busses would be a good thing of course.

[smurfyou]

Originally Posted by Frank Kruse

The whole bussing I/O assignment system PT needs a serious remodeling. Of course they can go on taping band-aids across the little things but the whole system needs to be worked over. With 700+ tracks running on HDX3 the current spaghetti routing system simulating patch-bays from an old console doesn't make sense anymore.

http://protools.ideascale.com/a/dtd/...er/118803-3779

Frank.

P.S.: Having said that, deleting unused busses would be a good thing of course.

Yes, a matrix would be great. PT's routing is flexible but cumbersome. Still waiting on automatable routing too

Although I could see it throwing the music guys off if they change it.

[reichman]

Although I could see it throwing the music guys off if they change it.

Maybe the music guys would actually start using it if they changed it! Ha.

Yes, we desperately need a visual matrix or something clever. The current system works, but when you have dozens of busses multed to various outputs and the only way to see it is with a drop-down menu, it's crazy.

[lode]

I absolutely agree that it is in dire need of a makeover. The flexibility is awesome, but leads to a lot of cumbersome problems. Not sure I need automatable routing though. Seems that one could really easily get lost in routing-hell (tm) if it wasn´t static, and some one else is supposed to take over the session.

[reichman]

Still waiting on automatable routing too

smurfyou:

This scares me, but I'm willing to keep an open mind. Can you explain a workflow situation where automatable routing would benefit the mix? I guess I could imagine running out of sends and using that function...

[smurfyou]

Originally Posted by reichman

smurfyou:

This scares me, but I'm willing to keep an open mind. Can you explain a workflow situation where automatable routing would benefit the mix? I guess I could imagine running out of sends and using that function...

Yes mainly to avoid using sends. Although frankly I don't think I would ever need it nowadays. But when working with other consoles it was nice to reassign say a dialogue track if I had a certain NR chain to use. But with PT it seems totally unnecessary.

What I do actually want is automatable Pre/Post send control. And a matrix.