quote:

---

Originally posted by papromike

You are probably hitting the “store all” button to save scenes, what you really should do is

Store all your master setup, then just use the “update” on each subsequent scene change.. that way it only stores the updates on each scene.

when you hit the store all, its re-storing everything, IP address settings, buss configs, user preferences, etc. there really is no need to do that and reloading all that stuff takes a bit of time.

If you just do “updates” on each scene, it will snapshot instantaneously.

Vice President of Sales
Allen & Heath USA

---

Hi Vice,

That’s the problem I have been complaining about – it’s not intuitive and everyone encounters the same problem … and the work around is clumsy. I have just supplied an iLive for a school musical production and they had problems with the scene management…. Again!

For the part of the market the iLive seems most suited, such as schools and armature theatre, where you use scenes quite a bit, you need 3 levels of scene management.

1) A master scene save all, which is the current save all.

2) A scene save that only saves levels and mutes as the default. To this you can add other functions such as EQ, Gates, Compressors, pre amp gain etc if needed.

3) A show save, which is saves all the files associated with that particular performance.

In addition, you still need scene safe functions.

Best Regards

Peter

Peter

quote:

---

Originally posted by tk2k

Hi everyone,

Been using our new iLive for about a week now, got a few questions for the masses.

I know there are a lot of topics on scene management, how to do it, etc, and this is one of those, but with a few caveats.

I support everything from live bands to orchestras to theater shows, all of my theater programing experience is digico or yamaha. In both of those cases, I’ve never really had to worry about ‘recall time’ its just fairly instantaneous.

on the iLive, it seems to take more time? Is this accurite? at the very least the touchscreen seems occupied while the ‘system busy’ dialogue displays, but does that actually ‘lock up’ the whole console, or just the touch screen?

---

To add to what was said already, unfortunately when the screen is showing “system busy” messages your console is “locked up” in its last state, that is you have audio going thru but no control, care must be taken as fader moves or others during that time will eventually be acted upon after the “system busy” message disappears…..

To properly use the scenes as implemented on the iLive, you should store a “first scene with a “store all” that will restore at boot up ( socket assignments console layout) etc… this will be stored with your show.for subsequent scenes, only store what you need in it, by using the “edit” button in the scene management window, you might want to copy basic scenes and again on a scene to scene basis only add elements that are needed…..once you’ve made changes to a scene use “update” that way only the elements included in the scene will be memorized.

quote:

---

Originally posted by tk2k

Is there an equivalent of tracking, where I can tell the iLive not to recall a setting unless its changed?
for example, I have an actor who puts on a large hat at one point which changes the characteristics of their mic, so I have a different EQ on them. Obviously there’s no point in recalling the same exact EQ for the 30+ scenes before I need that EQ, but I can’t remove the EQ from programing entirely as I do need it to change for one scene.

Thanks

---

Save a scene that reflect the EQ you want with no hat for that particular channel or group of channels, in subsequent scenes you can either remove the EQ from the scene recall (edit in scene window) but, because now your scene content has been trimmed down and you are recalling fewer elements, you could leave it in. without affecting scene recall speed ……at the scene where the hat is worn add the new EQ if you had removed it from that scene or just click “update” if you left it in…and so on.

Hope that helps

Ray

Thanks for the video link – somehow I didn’t know A&H has a youtube channel.

Short off-topic, if you don’t mind – what is the basic difference between IDR Mixrack Socket and Direct Out of the channel when choosing signal source for recording ?

ddff

Hi all,

One thing I have suggested in the past is:

– Scenes should be able to recall library items. For example let’s say you have a PEQ store in the library for your lead vocal. During sound check, you need to make a change to that PEQ setting for whatever reason. By simply updating this change in the library, the change should be reflected by all the scene recalls which use this library entry. (Change once, apply to many)

So, using the actor with the hat changing mic characteristics example, lets say the actor puts the hat on and takes it off more than once during the show. With two EQ settings stored in you library, one for hat on and one for hat off, it would be nice if you could have a scene recall the EQ setting from your library. This way, if you need to change let’s say the hat on EQ for some reason, you would make your EQ change and update your previous hat on EQ in your library. You wouldn’t have to update any of the scenes. Otherwise, you have to first recall each scene making use of this hat on EQ one at a time, make your EQ change, and update the scene. Why? Simply because you may have other settings common to those scenes but set differently that you don’t want updated. That would be disastrous. An UNDO would be good too.

Just a thought!

Paul