So before the dual workspace, no way to change wkp between tunes on stage...
Another big drawback for me using a wkp per tune, is having to copy/paste every change I make in all the other wkp. That's why I suggested Olivier to implement a grid playlist : changing grid instead of wkp between tunes.
Statistics: Posted by La Tenaille — 01 Dec 2015, 10:51
]]>
Statistics: Posted by Vincent — 01 Dec 2015, 00:16
]]>
Statistics: Posted by La Tenaille — 30 Nov 2015, 20:28
]]>
Well, it seems you have build a two-legged workspace!
I also use arrays to minimize the number of links and busses, I don't know if it's a good idea, but it's clear and clean.
About the popup windows, do you use floating windows?
What do you mean by default workspace?
Statistics: Posted by Vincent — 30 Nov 2015, 18:59
]]>
I communicate between the wkp with arrays and comma text multi modules, it allows one bus per patch instead of one per value.
An interesting thing is you can use popup windows to display a wkp element from another, using keyboard shortcuts.
I still have to learn how to work that way, and change my habits (once again
)Statistics: Posted by La Tenaille — 30 Nov 2015, 14:53
]]>
Since the two workspaces run the same instance of usine (same instance of audio engine), loading wkp sometimes cracks or dop out the sound. And I'm not sure which wkp is saved when I make a Ctrl+S. And, as you say, I cannot show two workspaces at the same time.
I've finally decided to work with two instances of usine (two different installation folders). One for my main workspaces (A), with one wkp per song, the other instance (B) is only for transitions while workspaces are loaded in the main instance (it can be long), with only one wkp for the whole stuff, and pretty simple. Instance A loads instance B if it's not, and then B loads it's own wkp.
I don't see on screen that second instance B but it's possible to rearrange the windows. All the controls are in the first one A. In every WKP of instance A, I have a rack that sends MIDI messages to instance B via LoopBe1 for levels and other stuffs. This is not very optimal, I wish I use OSC instead. I did that many years ago, but I don't remember how I did!
It's very stable and I have no more cracks when loading heavy workspaces. Also, whatever happen, I can make some noise!
Not sure i'll use the additional workspace but I think it's a good idea.
Olivier is right: put your main heavy VSTi in the additional (if you use one), no need to reload it each time, and use some midi busses to play it from the main WKP and audio busses to retrieve and process the sound. Not so many busses infact. It really depends on the structure of your workspaces, in fact.
Well, I just have now to remember how to use OSC to communicate between the to instances.
cheers
V
Statistics: Posted by Vincent — 30 Nov 2015, 02:11
]]>
I'm looking for a way to manage my tunes without loading a wkp per tune, and Olivier suggested the additional workspace for that use :
http://www.sensomusic.org/forums/viewtopic.php?id=4965
I thought about using one grid workspace to change tune, and another grid workspace for changes inside tunes, but it means tons of buses to link the racks...put every common racks in the additional wkp and big changes in your main wkp
Statistics: Posted by La Tenaille — 24 Nov 2015, 09:25
]]>
Say you have a performance, and also have a singer or guitar player that utilizes EFX from Usine.
Using the additional workspace you could provide these additional AUX channels, but still have a workspace say for a direct synth performance or sampling, etc...
As far as I know I think you are right in regards to connection.
-s
Statistics: Posted by sephult — 23 Nov 2015, 23:10
]]>
What I understand is the 2 workspaces are sharing the same master audio engine, sync, and devices.
Appart from that, the wkp are completely independant : racks, grid, IB. That's it ?
So if I want to build connections between them, I have to use buses ?
And I can't display the 2 IB on the same screen ?
Statistics: Posted by La Tenaille — 23 Nov 2015, 21:57
]]>