Interesting concept questions for X1

Hi guys,
 
So I'm talking to a bud of mine on the phone tonight that recently purchased X1. We were going through all the cool options it has that 8.5 doesn't and he asks me a question which I had never heard of, but wanted to throw at you guys...especially if the bakers are reading or a few of you programmer types are reading.
 
He asked if there was a program or something that could literally analyze all the tracks in your project, and have it present you with a chart of what instrument is on what track as well as how they are all panned. I thought that would be a pretty cool thing to see. Like for example...
 
You run Sonar and you click this extra tool, it checks out your mix and gives you a pan field line or something and lists all your instruments and where they are panned so you can just look at this thing and see it all in front of you. Each time you add a track or whatever, it auto-updates when you open it again. Have any of you heard of anything like this that may be a plugin or a program of sorts? Would be cool to be in Sonar...especially for those that have huge track counts. I'd love to see Sonar have something like this as a part of the program. I make my own sheets for this and have a nice template, but I always have to manually fill the pan field numbers in. Would be nice to click and it knows what the deal is and shows it to me.
 
One other thing since I have you here....I'm sure some of you have thought of this and talked about it, but do you think we'll ever have the capability to freeze busses? Is it even possible? I would think something like this would be useful as quite a few of us have as many busses as we do tracks these days. You have to have a pretty killer system to run loads of them, ya know? What are your thoughts about this? Anyone have pros or cons about it...and if any of the Bakers are reading, any chance of us seeing this if it's possible?
 
-Danny

I guess I need to jump in that request thing with you and get all my buds to join in as well, John. Maybe they need a few of us nagging at them. Sounds like your idea is the complete one...good thinking there! ;)

How about the freeze busses thing, John? Would you have a use for that...is it even possible?

-Danny

The project summery idea is one that I think would be useful to many. I know some of my old projects are a little complicated and I have to take some time to figure out just what I did. Also it could be useful for diagnosing problems.

I've been wishing for reporting options since the first week I started using SONAR.

Wouldn't it be great to get a report that graphically displays the whole routing scheme, with effect names, panning and volume/trim values?

If CW were to just publish their project file structure, or even better, create an API to work with it, third-party developers would quickly fill the void. A DAW with an open architecture would, I think, have a huge competitive advantage in the marketplace.

FastBikerBoy


I like the 'grand view' concept.

Wouldn't freezing busses though quickly become impractical? It would mean freezing all the tracks going through that buss wouldn't it? If not as soon as you made a change to a track feeding it the resulting output from the buss should change which if it was frozen it couldn't.

Thats in line with how I view buses. I tried to give the same idea above but you did a much better job of explaining it. Thats what was meant by buses being dynamic.

A flow chart is something so basic. Once that door is opened, the possibilities beome almost limitless.

I have made many referrences to my desire for this over the years.  And it should  not only show every connection by name and it's place in the tree,  it should also be printable.
 
All effects should be in a patchable rack that could be patched from anywhere to anywhere by snipping or cutting  a signal "cord" anywhere in the flow diagram.

Oh my, how retro.

>> If CW were to just publish their project file structure, or even better, create an API to work with it, third-party developers would quickly fill the void. <<.. .. this