I agree that storing less information into a scene would make it more quickly to recall. However, if the time for scene creation is limited then store all is single option as store some takes much more time and thinking.

ddff
T112+iDR48

Yes – a user scene store library /Profile/Template – call it what you want has been requested before! The way I work around it (for Theatre shows anyway) is to store a scene with just the parameters needed, copy that edited scene to many new unused locations, then when programming start the first scene with a Store ALL, and for the next scenes just hit update. You can also still decide to hit Store All if you know there are other changes that need storing. Works fine for Theatre type shows but not for multiple band/artist changeovers!

Cheers

Richard Howey
Audio Dynamite Ltd
IDR48/IDR16/T112/R72

I would also like the option to store the parameters that I changed since my last scene recall on top of the parameters defined is the template.

That way, I could store fader levels by default, and let’s say, store a specific change in EQ for a specific channel on top of the fader levels just by executing that change and then choosing save scene according to template and with changed parameters. Ideally the system could show me the list of things I changed since the last scene recall (up to a certain number of changes of course).

Wouter
My prayers have been heard, Dante is coming!

quote:

---

Originally posted by Gijsbert

I also work with ligthing desks and they have the “tracking” option.
Gijsbert

---

And they also have scene fading… that’s still on top of my wish list!

greetings from Belgium,
Wouter

Any one know any more on this problem being fixed?

I am demoing ilive t112 with a IDR-64, loving it, but slow load and no fade time on scene loads is a pain. fine for a band, but running a theatre show, when I press go it needs to go!

Going to give stix way ago tomorrow.

Jacob
LifeLike

I’ve also found if you need to be quick in creating the scenes – say in the tech run for a musical, hit store all throughout, then later use a computer editor to remove parts of the scene you dont need, or if I’ve had the forethought/setup time, i do as stix suggests and create a heap of copy/pastes with just Mutes Levels Assignments and Strip Assignments, then re-add any singular items back to scenes that might need them, such as a IP Name change.

Then hitting update stores just the parts you need.

That being said, im gonna +1 the request for tracking what has changed, and a +1 for choosing templates

quote:

---

Originally posted by kentlowt

I would not want to choose from a predesigned template but, I would like to create a template.

112T/IDR48/IDR16

---

FWIW, on a usb key I have created a show called Scene Templates and in there I have scene “types” I use most often as well as “patch only” scenes depending on whether I am touring with different systems or at home in our theatre in a fixed install…all I have to do is determine which type of show it is and import these scenes to the editor within any given show file ,then it’s just a matter of copying and pasting at the appropriate scene # ….that way you can also filter/block/allow what gets imported…..

RayS

R-72/iDR32/iPS10