Do you mix in track or console view?

Console view is great. If you have lots of tracks console view can make it easy to make adjustments to both the track strip and any plug ins. 
But beware, console view can add to the CPU strain.

mike_mccue


Whats a console view?

:-)

I guess depending who you are, it can either be this neat little gray box on a computer screen or a Neve 8078.

I've always mixed in track view and haven't thought of any reason to try other views.

track view.  I'll track (pun intended) down problems in the console view, esp. buses, but mainly use the track view.

@

I use both..... but mostly track view. I can see my envelopes and I can also see what's coming. Most volume and panning adjustments are done here.

Console view is good for seeing the entire project at once.... to watch the meters to be sure nothing clips. It's also easier to see that everything is going where it's supposed to go....tracks to busses, and then to master.  I hide the midi source tracks and use narrow view if I have a large number of tracks. ( not very common)

I start out in Track View, to insert markers, apply fades and crossfades, general track cleaning and clip gain envelopes, and then I switch to Console View for track and bus volume adjustments, panning, eq and applying effects.

Bob

Yeah, same as the above 2.

Track view for tracking, organisation, automation etc, console view for everything else.

Console for mixing, track for editing.

Easier for me to see in console. I guess it's a verticle, horizontal thing.

Track View all the way....

I track in track view, do all editing etc, then, I mix in console view. I guess it is because I'm used to mixing on a real console. Some things are just hard to let go of.

This is the first time I've heard that the Console View uses more CPU. I'll have to do a little comparison to see the difference. What makes the Console View so CPU intensive?

I use both..........as stated before.....
Track, edit, envlope,automation, basic mixing and some other type things...but then go over to console view for a more refined mixing.

Cliff

I too work a lot like Bob. I use a Mackie Control Universal Pro and I have the Console and Track views set up as user buttons, so I switch back and forth a lot during mixing and tracking.

Can anyone confirm that the Console View uses more CPU?

Console view for mixing, track view for tracking & editing.

I guess my quick answer is both. I use Sonic Core Scope so I generally mix through a Sonic Core mixer (the 4896 version for those who know about such things) on monitor 2. If I didn't have Scope I'd have the Sonar mixer up and running constantly on monitor 2 just because it makes sense to do so.
 
But generally speaking, I do most of my work in the track pane. It just makes more sense for me to do it there. I'm not moving my eyes back and forth so much I guess. I find it a tad distracting to dart my eyes from monitor to monitor. I prefer to do what I can on monitor one and since it seems you can do almost everything right there in the track pane anyway, why not. Sonar facilitates working like that quite well. Samplitude is a different matter. In Sam world, you need to be able to bounce back and forth since some important features are only available in the mixer window.