Cue stack on desk not following RFR of iRFR

What console are you using?   Not sure I understand where you are seeing that the cue label is incorrect.  We haven't been able to reproduce any issue with incorrect labels here.

Using the iRFR, you playback some cues using the Playback display or the Virtual RFR display?  Then the cue label above the which {Go} button is showing the incorrect label?

We've got an Eos.

We went into cue 0.1 via the console. Then, at the half hour call using the RFR, went first into cue 0.2 then into cue 0.3 then cue 0.5 which was the preset.

when the operator went up to the desk the monitor showing the playback screen showed the desk as being in cue 0.5 and the actual output was following this.

In the small window above the load button for the main playback that shows the active and next cue number, it was still showing cue 0.1 as active and cue 0.2 as the next. It also showed this at the bottom of the main playback monitor where this is mirrored. This can just be made out in the second picture below.

When the GO button was pushed on the output of  the console jumped back into cue 0.2

We have been using the RFR and iRFR to go into our presets since we have had the desk and they have always followed each other.

Sadly at the moment our desk is not in use in the control room so we have not had a chance since then to investigate it any further here.

Michael,

I am having a hard time making out the detail but it appears the playback status screen is following cue list one which is being triggered. However the main playback button (small screen) has cue list two loaded. So it makes sense this display would not follow as nothing is being triggered in this cue list.

the last pic is the best. there i think i can see that the PSD has cuelist 1 and shows 0.5 active, but the master section at the bottom, which shows list 1 as well, says 0.1 -> 0.2. the small screen area above the master playback section would show the same as the bottom section of the PSD.

so i don't think there are two cuelists involved?

What we thought was the issue and wrote up, is not the same now that we have this additional information. 

Try doing a deep clear and see that clears things up.  Steps:  Save your show.  Exit to Shell, Click on Settings>Maintenance>Deep Clear and click {OK}.  Press {OK} again, then {Accept} and {Primary}.  Finally open the show file and run the set of cues in the same manner that you do for performances.

Let us know if that fixes it.

I was guessing that your console is the Master.  Do you have any clients or backups?  If so, what console is the iRFR connect to?

So, have managed to reinstate my desk today.

No backups just the main console.

Tried to re create the same problem with the same show file and it did exactly the same.

Tried the deep Clear but still no change.

Loaded an old show file from a different show and all worked correctly.

Created a new show file and that worked fine too.

So, I guess there is something odd with that show file. I've looked around in the settings but cant find anything that would stop it from working.

Also, the show we had in was doing two different plays and had two different show files so, I tried loading the other one and, it wouldn't let me use the Go button on my remote at all, but would let me use Goto cue which was followed correctly on the desk! All very bizarre.

Would be able to send in the logs with the show file loaded that isn't working correctly and the show file?  I would like to see what the logs might show us and see if there is something in the file that I can look see as a trigger.

Please send them to eos (at) etcconnect (dot) com with attention Steven Peterson and reference this forum post.

Logs are collected by going to the shell>Settings>Maintenance>Save Logs.

Thanks.

Would be able to send in the logs with the show file loaded that isn't working correctly and the show file?  I would like to see what the logs might show us and see if there is something in the file that I can look see as a trigger.

Please send them to eos (at) etcconnect (dot) com with attention Steven Peterson and reference this forum post.

Logs are collected by going to the shell>Settings>Maintenance>Save Logs.

Thanks.

I got your email and will get back to you shortly.