Log in
Register
Home
Forums
New posts
Search forums
What's new
Featured content
New posts
New profile posts
Latest activity
News
Members
Current visitors
New profile posts
Search profile posts
Features
Log in
Register
What's new
Search
Search titles only
By:
Search titles only
By:
New posts
Search forums
Menu
Install the app
Install
Reply to thread
Home
Forums
Pro Audio
Junior Varsity
X32 Discussion
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Message
<blockquote data-quote="Dan Mortensen" data-source="post: 120834" data-attributes="member: 2826"><p>Re: V2 final</p><p></p><p></p><p></p><p>Since Jan posted this there has been some back and forth there, and here is what I think is almost the final word on this subject for now. </p><p></p><p>The below is reposted from that thread, in which many people were confused if not outraged (including me) that loading a scene or sequence of scenes and having the console reboot before the autosave did its thing (up to 2 minutes after the last change) resulted in something appearing that was NOT the exact thing when power was lost. </p><p><span style="color: #000000"><span style="font-family: 'Verdana'"></span></span></p><p><span style="color: #000000"><span style="font-family: 'Verdana'">Short version: Sometimes it was the last </span></span>[FONT=Verdana, Helvetica, sans-serif]<span style="color: #000000">scene you loaded minus any changes made within 2 minutes, sometimes a previous scene, sometimes a random combination of elements of several scenes. Other consoles were alleged to be better at that, although recent posts name some that perform no better than the X32. The implication was that 2.02 was a change in this performance than we previously experienced.</span>[/FONT]</p><p></p><p><span style="color: #000000"><span style="font-family: 'Verdana'">Today I finally got to do something I've wanted to for a while regarding this question.</span></span></p><p></p><p><span style="color: #000000"><span style="font-family: 'Verdana'">Set up a console with 1.15 on it which had never had 2.anything on it. Compared how each performed when loading scenes, not waiting long enough for auto-save, and then rebooting and seeing what came up. </span></span></p><p></p><p><span style="color: #000000"><span style="font-family: 'Verdana'">Short answer is that whatever the console is doing in 2.02 it was also doing in 1.15.</span></span></p><p></p><p><span style="color: #000000"><span style="font-family: 'Verdana'">Both consoles behaved the same no matter what I did to them, and I did it in unison simultaneously (if those mean slightly different things to somebody).</span></span></p><p></p><p><span style="color: #000000"><span style="font-family: 'Verdana'">Another data point is that manually saving settings to a scene and then rebooting has no effect on the settings when it reboots. It will go to its random combinations of settings upon reboot.</span></span></p><p></p><p><span style="color: #000000"><span style="font-family: 'Verdana'">There is a clear difference between manual save and auto-save, and auto-save is the only one that counts in this discussion.</span></span></p><p></p><p><span style="color: #000000"><span style="font-family: 'Verdana'">So, again, as with several other things on the console, unless they are able to make the thing autosave more often or upon any parameter change or to make manual save the same as autosave (which still wouldn't solve the problem, because an unplanned power down is not going to let you save your settings by definition), we are left with "WTF do you expect from a console this complex which costs this much?"</span></span></p><p></p><p><span style="color: #000000"><span style="font-family: 'Verdana'">At this point I feel like we've identified its behavior under surprise power loss conditions, and can plan accordingly.</span></span></p><p></p><p><span style="color: #000000"><span style="font-family: 'Verdana'">In case of total power loss, bring the console up first and get your correct cue/scene loaded (and you need to affirmatively load it, not just assume that because it SAYS it's the right one that it is), and then power up your amps and speakers.</span></span></p><p></p><p><span style="color: #000000"><span style="font-family: 'Verdana'">If only the console goes off, either mute all your amps or disconnect the input cables unless you are positive that no combination of wrong inputs will be embarrassing.</span></span></p><p></p><p><span style="color: #000000"><span style="font-family: 'Verdana'">I'm personally happy we went off on this goose chase because now we know more about my favorite console.</span></span></p></blockquote><p></p>
[QUOTE="Dan Mortensen, post: 120834, member: 2826"] Re: V2 final Since Jan posted this there has been some back and forth there, and here is what I think is almost the final word on this subject for now. The below is reposted from that thread, in which many people were confused if not outraged (including me) that loading a scene or sequence of scenes and having the console reboot before the autosave did its thing (up to 2 minutes after the last change) resulted in something appearing that was NOT the exact thing when power was lost. [COLOR=#000000][FONT=Verdana] Short version: Sometimes it was the last [/FONT][/COLOR][FONT=Verdana, Helvetica, sans-serif][COLOR=#000000]scene you loaded minus any changes made within 2 minutes, sometimes a previous scene, sometimes a random combination of elements of several scenes. Other consoles were alleged to be better at that, although recent posts name some that perform no better than the X32. The implication was that 2.02 was a change in this performance than we previously experienced.[/COLOR][/FONT] [COLOR=#000000][FONT=Verdana]Today I finally got to do something I've wanted to for a while regarding this question.[/FONT][/COLOR] [COLOR=#000000][FONT=Verdana]Set up a console with 1.15 on it which had never had 2.anything on it. Compared how each performed when loading scenes, not waiting long enough for auto-save, and then rebooting and seeing what came up. [/FONT][/COLOR] [COLOR=#000000][FONT=Verdana]Short answer is that whatever the console is doing in 2.02 it was also doing in 1.15.[/FONT][/COLOR] [COLOR=#000000][FONT=Verdana]Both consoles behaved the same no matter what I did to them, and I did it in unison simultaneously (if those mean slightly different things to somebody).[/FONT][/COLOR] [COLOR=#000000][FONT=Verdana]Another data point is that manually saving settings to a scene and then rebooting has no effect on the settings when it reboots. It will go to its random combinations of settings upon reboot.[/FONT][/COLOR] [COLOR=#000000][FONT=Verdana]There is a clear difference between manual save and auto-save, and auto-save is the only one that counts in this discussion.[/FONT][/COLOR] [COLOR=#000000][FONT=Verdana]So, again, as with several other things on the console, unless they are able to make the thing autosave more often or upon any parameter change or to make manual save the same as autosave (which still wouldn't solve the problem, because an unplanned power down is not going to let you save your settings by definition), we are left with "WTF do you expect from a console this complex which costs this much?"[/FONT][/COLOR] [COLOR=#000000][FONT=Verdana]At this point I feel like we've identified its behavior under surprise power loss conditions, and can plan accordingly.[/FONT][/COLOR] [COLOR=#000000][FONT=Verdana]In case of total power loss, bring the console up first and get your correct cue/scene loaded (and you need to affirmatively load it, not just assume that because it SAYS it's the right one that it is), and then power up your amps and speakers.[/FONT][/COLOR] [COLOR=#000000][FONT=Verdana]If only the console goes off, either mute all your amps or disconnect the input cables unless you are positive that no combination of wrong inputs will be embarrassing.[/FONT][/COLOR] [COLOR=#000000][FONT=Verdana]I'm personally happy we went off on this goose chase because now we know more about my favorite console.[/FONT][/COLOR] [/QUOTE]
Insert quotes…
Verification
Post reply
Home
Forums
Pro Audio
Junior Varsity
X32 Discussion
Top
Bottom
Sign-up
or
log in
to join the discussion today!
