Quick question: I installed an iLive t112-idr48 back in July with then (then) latest firmware/etc.
Everything is peachy, but one continual complaint I get from the customer is the 1-2 second delay when switching scenes. I’ve verified the delay myself, and it’s a pain!
The venue has three stages, and each song is a stage change, so you can imagine the frustration when there’s this awkward pause.
Scenes are slow if they have everything stored in them (store all). They will change much quicker if you only have say fader levels and mutes so if you can edit your scenes to only have what is actually changing between scenes you will find them much more responsive. Do a “store all” at important scene locations or at the start of the show.
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.
Maybe this could be something for a future update: the ability to preset a specific scene store profile… the other issue with doing the selective store on the fly is the chance that you’ll miss something important.
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!
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).
I also work with ligthing desks and they have the “tracking” option. In short, when you press store they only store what is changed. Everything else, the channels that weren’t changed, stay just the way they were. Would be great on an ilive, you don’t have to worry if you have forgotten something!
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!
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
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…
Saving scenes as deltas from the previous settings would be great for speed, but would only be useful to me if the software has the capability to reconcile all the changes when scenes are reordered. This would slow down the reordering a bit, but is not an unsolvable problem. I essentially need to create scenes for musical sets that can be changed.
There are a couple of ways this could be solved from an algorithm standpoint. The simplest is probably a function to walk the scenes and fill in all the missing gaps. Then after reorder, another function to walk the list and remove redundant information and leave the deltas in place. This could offer the both of best worlds without too much problem programically.
I could go something like this: entering reorder mode fill in the scenes with all settings; exiting reorder mode eliminate all but the differences. Restoring scenes out of order would be slightly more complicated but solving this problem would eliminate the need to do the conversions as often.
And this probably doesn’t apply to your situation, but with a idr32 you can have duplicates of all channels in the mixer. In other words inputs 1-32 go first to channels 1-32 and then again to channels 33-64. This doesn’t get them out of the mixer, but gives you the option of having two versions of the same channel. If you needed 32 outputs you could also add 2 xdr-16’s and that would give you 32 available outputs. Just some thoughts.
T112/48, MacBook Pro, Mac Mini, and trying to patiently wait on Dante.
Looking into purchasing ilive for music and theatre. During the scene switch does the current scene continue playing until next scene is recalled or is there quiet time?
Looking into purchasing ilive for music and theatre. During the scene switch does the current scene continue playing until next scene is recalled or is there quiet time?
There is no “quiet” time between scenes…audio keeps going through…