record to playbacks not working

[quote=bradpepe]The more information you can provide the better.. can someone provide exact keystroke steps from starting a show to get this to occur?

We want to fix this, but without a repro it is difficult.

hi brad,

if i understand correctly, keystrokes are not a cause for the system to enter this state; this state has already been entered by the time the desktop process has finished initiailzing.

i myself have never encountered this during normal 3.0.0.2417 use.

but this so strikingly resembles something i've seen ever since 1.4.0.1112, that i can't help but think that the two are directly related.
[LIST=1]
Launch launcher, without arguments
Pause/Break, Ctrl+O+Backspace, to open the Launched Processes window
New Show (or, existing empty show)
in the Launched Processes window, right-click the desktop process and choose "Restart desktop" from the context menu
the Wholehog Screens and dummy front panel will close and restart
the Wholehog Screens and dummy front panel will re-open
the dummy front panel will not have any of its Choose buttons lit
recording to master ??? happens
moving to master 4294967295 happens
(looks to me like another sign bit bug, as UInt32 4294967295 would be SInt32 -1, the more likely mistaken result. type schmafety. either way, it should be Assert'd)
always recording to cue 2, when a page is populated, happensagain, i can't provide a way to get a system into this state during normal use and without restarting the desktop process. but even so, i think it's a great place to begin whiteboxing.


i hope this is helpful; i expect it might already be well-known, but your asking for keystrokes and for clarification of the symptoms prompted me to post, just in case.


attached are three supporting files, recounting:
[LIST=1]
the launch of an existing but empty show
recording (nothing) to choose button 1
restarting the desktop process
recording (nothing) to choose button 1DbgPrint.log : a log of standard DbgPrint output

new desktop process begins with event 66
notably missing is a FirstFaderID received event, similar to event 65eventlog.txt : 3PC Event Monitor > Dump Log results

the restarted desktop process initializes with 19929754 through 19930791
the eventlog.txt seems to have an XML header, and also suffers from the Unicode byte-order-mark bug; the attached file has been modified at the byte level to compensate. it should be opened in Visual Studio with its XML editor, as it's not pretty in notepad. a screenshot of this has also been attached.event monitor dump.jpg: screenshot of eventlog.txt

[quote=bradpepe]The more information you can provide the better.. can someone provide exact keystroke steps from starting a show to get this to occur?

We want to fix this, but without a repro it is difficult.

hi brad,

if i understand correctly, keystrokes are not a cause for the system to enter this state; this state has already been entered by the time the desktop process has finished initiailzing.

i myself have never encountered this during normal 3.0.0.2417 use.

but this so strikingly resembles something i've seen ever since 1.4.0.1112, that i can't help but think that the two are directly related.
[LIST=1]
Launch launcher, without arguments
Pause/Break, Ctrl+O+Backspace, to open the Launched Processes window
New Show (or, existing empty show)
in the Launched Processes window, right-click the desktop process and choose "Restart desktop" from the context menu
the Wholehog Screens and dummy front panel will close and restart
the Wholehog Screens and dummy front panel will re-open
the dummy front panel will not have any of its Choose buttons lit
recording to master ??? happens
moving to master 4294967295 happens
(looks to me like another sign bit bug, as UInt32 4294967295 would be SInt32 -1, the more likely mistaken result. type schmafety. either way, it should be Assert'd)
always recording to cue 2, when a page is populated, happensagain, i can't provide a way to get a system into this state during normal use and without restarting the desktop process. but even so, i think it's a great place to begin whiteboxing.


i hope this is helpful; i expect it might already be well-known, but your asking for keystrokes and for clarification of the symptoms prompted me to post, just in case.


attached are three supporting files, recounting:
[LIST=1]
the launch of an existing but empty show
recording (nothing) to choose button 1
restarting the desktop process
recording (nothing) to choose button 1DbgPrint.log : a log of standard DbgPrint output

new desktop process begins with event 66
notably missing is a FirstFaderID received event, similar to event 65eventlog.txt : 3PC Event Monitor > Dump Log results

the restarted desktop process initializes with 19929754 through 19930791
the eventlog.txt seems to have an XML header, and also suffers from the Unicode byte-order-mark bug; the attached file has been modified at the byte level to compensate. it should be opened in Visual Studio with its XML editor, as it's not pretty in notepad. a screenshot of this has also been attached.event monitor dump.jpg: screenshot of eventlog.txt