quote:

---

Originally posted by Stix
Hi Wouter – You have made the assumption that a “scene” is kept in the IDR memory – but it is really just the current mixer state that is kept

---

Hi Richard,

As far as my experience goes, the entire scenelist is really stored in the IDR’s memory. Otherwise I could not do what I’m doing now: create all the scenes for my show with the editor, then deconnect the editor and just recall all those scenes by MIDI program change.

That means that the scene list is indeed stored in the IDR, BUT the scene NAMES do not show up on other machines then the machine where the scene list was created, and that is such a pity!! I mean, if I rename a channel we all think it’s logical that anyone sees that same channel name. It also works that way, but not with the scenes. I think somehow this was overlooked and I can only hope that it’s already on the wishlist.

The indication of the last recalled scene was indeed also discussed in other threads and yes, this too needs to be fixed.

greetz,
Wouter

quote:

---

Originally posted by antonyja
I hope that helps…

Antony Jackson
Software Manager
Allen & Heath Limited

---

Hello Antony, yes this explanation helps a lot. But I’d really like to propose these things:

1 Please, please, please, please, put the scene names in the IDR.

2. The option of separating strip assignment from the scene system and put it, at least for the editor, in a “mixer layout” file or something. OR have them stored centrally but not as scenes.

In my case I’d propose this structure:

SHOW
> SCENES
> SCENE PLAYLISTS
>> SCENE PLAYLIST 1
>> SCENE PLAYLIST 2
>> SCENE PLAYLIST 3
>> etc
> MIXER LAYOUTS
>> T80
>>> Wouters FOH layout
>>> My monitor tech’s monitor layout
>>> Etc
>> EDITOR
>>> Drummer’s own monitor control layout
>>> Wouter’s FOH Layout
>>> My monitor tech’s monitor layout

Is it known if a lot of users are really using strip assignment in scene, to change the strip assignment DURING a show? I would never do that I think…

But if so, why not have every surface identify itself and using that strip assignment for the update and still store it centrally? To me, it seems it would be good to leave the route of storing things on several places and go entirely forcentral storage. I can see that there might be some advantages to not doing this but to me the advantages are more important.

An example: I do a show with both T112 surface and editor connected.
I’d like to be able to store the entire show on my laptop’s editor session on HD and STILL be sure that that show file also covers the setting on my T112 for instance.

Suppose I’m a rental company and I decide to take another T112 to the show next time. I would like to be able to load the show using the editor, to start ringing out monitors and STORING THOSE NEW SETTINGS IN SOME SCENES (while my T112 is still used on another job for instance. Then later connect the T112 and be able to choose to use all settings for the T112 that are present in the show that’s already loaded in the IDR, WITHOUT HAVING TO LOAD A SHOW FILE WITH SCENES THAT ARE ALREADY OUTDATED BY NOW!!!

This is actually a lot more important for my musicians that like to adjust their in-ears. I have a replacement drummer and want him to use the mixer layout that was already created by the previous drummer on his own laptop. I tell him to install the editor on his laptop, then open the program, connect to the IDR, and the system would ask him, if he want to connect as a certain surface, or as a new surface but starting with some mixer layout that’s stored in the show. I’d tell him: or to go ahead and use the

---

“SHOW> MIXER LAYOUT> EDITOR> DRUMMER” mixer layout (or machine ID for strip assigment update DURING the show) and work with that during the show, OR (if I suppose that he might do some thing that the other drummer won’t like) to create a new layout BASED on the “DRUMMER” layout and call himself “DRUMMER2” for instance…

Still need to do some more thinking though. These are some basic ideas. I hope this can help too

Wouter
My prayers have been heard, Dante is coming!

This is a very interesting topic indeed, especially when thinking about multiple mix racks.

My experience though is that it may get confusing for the user. I mean, it really feels weird that one needs to save and restore a show when connecting a surface, whereas I always considered the show to host the basic settings of the mixer.
It’s also very confusing that it makes a difference on which controller you restore a show. I feel it’s a bit limiting always to have to restore a show, whereas actually I just need my controller to identify itself to the mixrack.
If I understand you correctly you can make some changes concerning the controller in the show via the editor but then you have to save the show on a USB stick, take that USB stick to the controller and recall the show on that controller?
As I see it, I’d rather have the Mixrack ask every controller to identify itself (with a physical controller, that’s still easy at the moment as it’s only one, but that will change if I understand correctly) or in case of the virtual controllers (editors) to indicate what controller settings they want to affect/be affected by.

Thus far, I do understand that info concerning a controller always needs to be transferred via USB stick, and moreover, not a single saved show will 100% sure contains ALL the info of that show (if people start using personal editors for in ear monitoring their strip settings are only stored on their personal machines, they might, no they will get lost, that I know upfront, they are, well we are musicians in the end, not computer scientists)

Concerning performance, the controller could sync it’s settings with the IDR rack so that controller specific scene info is also kept in local memory as a cache memory. However when saving a show it would be so nice to know that you have ALL info concerning your show in one file, and not in several files depending on the number of controllers that you are using.
Maybe it could be like a website/cookie system, where most of the users info is stored in the central user database of the website, but the identification goes fast as at the webclient side the basic “login” info is kept. In such a case, a user could ID himself to the Mixrack as “Wouter Tilkin laptop” and get those settings IF if in the current show there is a “Wouter Tilkin laptop” known as a used controller (just like R72, T80, T112 and so on) if not the controller will need to login using another “account” or create a new subscription to the show. On the local machine, I’d store the settings… showID–>account USED

This even has some advantages as I could start preparing custom strips for my colleagues. I could make a “DRUMMER” custom strip assignment by logging on using a (new) “DRUMMER” account.

Dreaming now (but seriously, I already ran into this story a couple of times!)
Then when we start rehearsing and the drummer asks me “where the f*ck is this channel?”, I even don’t have to run to the stage, I just change account to DRUMMER (or using a delegate system ) ) (if I’m allowed to, I won’t let the DRUMMER touch my settings for instance) and make the change in the strip assignment, and change the editor account back to my “Wouter Tilkin laptop” account…

Then at the end of the day I save the entire show on my laptop and on the internet storage (I don’t like using sticks all the time ) and I’m sure that if the drummer forgets his own laptop tomorrow and needs to use the laptop of our scene manager….. (it DOES happen ) he will still be able to get his custom strip assignment that we stored yesterday…

So my plead remains… please please, more central storage in the IDR… please? Make the Mix rack also the Show server
If that’s out of the question then I’d plead at least the scene names to be stored centrally and offer the possibility to store a fixed custom strip assignment as a seperate file.

The thinking goes on

PS: In fact when working with dual mix racks i would find it logical to see that one of them is the master where all info is kept, and the other one is just a slave.

Wouter
My prayers have been heard, Dante is coming!