More than one multidock?

+1 

for what reason??

OK, I'm stumped.  I can't come up with a scenario where more than one multidock would be useful.   Multidock is just the function of parking views in various places - why/how would a second multidock be possible or needed--?

Randy B.

I personally don't like multidock with my current monitor. I think I'd like it more if I had a bigger one with a higher resolution. As it is now, I only have a tiny space in between the top/bottom of my screen where I can move things without them docking.

Well I Would put smaller footprint and horizontal-centric windows in the bottom-docked multidock and larger ones and vertical-centric ones in the larger-sized floating dock.

Or VST UIs in one and the PRV stuff in the other, it's not hard to find uses for multiple docks.

I think that would defeat the purpose of the multidock, which seems to be a tabbed view for easy switching of whatever feature you are working on.  If you want different multidock views (ie. one stretched across teh bottom and another big on your second screen), that is what screensets are for.  Otherwise you are just cluttering up the worksurface with everything there and stepping on one another.  Or that is how I believe Cake thinks it should work.  But flexiblity should rule, so put in a request.

@

I wonder if you could dock the second multidock into the first one...Hmmm...

I keep the multidock on the second monitor and open any views I need inside it and keep the trackview on the other. Works great for me.

Yeah ... I was thinking about getting all the plugin GUI tidy out of the way - sorta like a tabbed view ehancement of the old synthrack..

I did like the tabbed view where you could dock ideas in sonar 8... but find it very inflexible due to location and in number.

the other dock could be used for PRV / Staff  views / console...

+1 for Multiple MultiDocks. it's a great idea.

With dual monitors you can have a lot of use for 2 multidocks.
for example I wish I could have one multidock where the regular multidock is for console and piano roll and another multidock which will be like a tabbed browser for all the VSTs and FXs.

Bub
 I personally don't like multidock with my current monitor. I think I'd like it more if I had a bigger one with a higher resolution. As it is now, I only have a tiny space in between the top/bottom of my screen where I can move things without them docking.

I recently came across a cool trick to overcome this: hold down Alt whilst moving.

Of course multiple docks would require some tweaks to keyboard navigation. 

I'm so-so about it. If it existed I'm sure I'd use it. After all Adobe apps and Vegas and the like have an almost infinite amount of palette dockability with each other. 

And even with the Multidock, I often break plugs out so I can keep them "always up" in a corner while I work. 

Screensets and me are still dubiously circling each other. I get large pauses when switching..sometimes it even hangs. I think I'd actually prefer assigning individual plugs to the num keys so you could pop a specific plugin to the front with one keystroke. 

I think I'd actually prefer assigning individual plugs to the num keys so you could pop a specific plugin to the front with one keystroke. 

Thats Not a Bad Idea..  

 I think every launched window/module/button/fader/switch ect should have the ability for a midi learn. A: this will allow for us to build a custom console/controller with no programming knowledge needed , A simple learn and save. no more MMC mode or mackie mode no more throwing out old midi controllers if its midi hardware it can be used on any feature in Sonar. That would hold same for touch screen to.. 

Wow, it's weird reading things I wrote so long ago!
That said, I truly miss SAW+. It had the most dirt-simple "screenset" implementation evar. SHIFT+F-key saved a layout, F-key recalled it. No lag, no crashing. And it instantly allowed 12 layouts of EVERY THING. Screensets now, even like I wrote all those months ago, are buggy as heck. They lag, they hang, they are just a total pain. Plus the weird "you don't have to save" BUT "you have to be IN the new screenset when you edit" is completely backwards. 
 
All that said, the obvious definition is: plugin UIs in one tabbable window, different editing views in the other. It's extremely obvious, even WITH inline PRV (never use btw), console view (also never use, get over it, it's a dead medium for folk who can't let go of physical hardware...and I say that having learned on them), and all the other views. One last thing: MAKE THE PRV ABLE TO ROTATE 90 DEGREES! Studio One can do it, and it makes ALL the difference learning parts since a piano keyboard goes left to right, not bottom to top. 

Yah, though I wouldn't be surprised if it was easier to acclimate to than you think.
 
But, I don't play through projects in the PRV anyway, I edit there. I'll play little bits over and over. one of the major streamer programs IIRC goes top-bottom instead of left-right.
 
I like the idea because it makes it way easier for me to figure out parts. I suspect younger folk will like it because Rock Band and all those games work in a similar fashion.