Page 1 of 1
Posted: 28 Apr 2008, 20:32
by nofish
My conductor currently has about 40 snapshots and growing, each snapshot basically representing a "song" for the live gigs with my band.
For every gig, I change the order of the snapshots representing our actual setlist.
So I think it would be nice if I could save the conductor (snapshot order) seperately from the workspace. So if the band says "for this gig we use setlist X" I just load it into conductor and keep going.
More economical than saving/loading the whole workspace everytime I think.
Posted: 29 Apr 2008, 08:44
by damstraversaz
nice idea !
Posted: 29 Apr 2008, 16:24
by nofish
Thanks.
But if I think about it more closely I`m wondering what would happen if I load the conductor in a workspace that "doesn't fit", meaning it has totally different patches than the snapshots saved in the conductor.
Maybe Senso has an idea?
Posted: 29 Apr 2008, 18:00
by senso
I can think about a 'save /load conductor' menu, probably not so difficult to implement.
But if you load a conductor which was not originally made for the wkp: nothing will happen (recalls are ignored).
Posted: 29 Apr 2008, 18:50
by nofish
That would be really nice and save me some work.
Oh and I certainly don't want to sound unthankfull or too demanding, but maybe while you are at reworking the conductor, there's the other idea about implementing scrollbars for the conductor.
http://www.sensomusic.com/forums/viewtopic.php?id=756
Posted: 29 Apr 2008, 20:53
by senso
this suggestion is not dead!
but as you have noticed, there is no scrollbar in Usine.
So I need time to create a totally new interface design for Usine (skins).
This will be done after the finalization of the vst version and a small set of high priority implementation.
Posted: 30 Apr 2008, 13:45
by moody33
I think it's a good idea but :
-It means that we will have to save a conductor file for each workspace !
- What about a special function like a bank of preset for the conductor , stored with the workspace ? In this case, no confusion will be possible with loading/saving conductor.
No?
Posted: 30 Apr 2008, 15:26
by senso
let me think about it.
Posted: 01 May 2008, 04:01
by nofish
moody33 wrote:I think it's a good idea but :
-It means that we will have to save a conductor file for each workspace !
- What about a special function like a bank of preset for the conductor , stored with the workspace ? In this case, no confusion will be possible with loading/saving conductor.
No?
This sounds also like a good idea to me.
Posted: 18 May 2008, 10:40
by senso
the multi-bank conductor storage is implemented.
next release