TheaterTek

[Trioxide]

Having problems with TheaterTek now. On CQC 3.4.1 now and TheaterTek DVD 2.0. Has been working fine but now getting errors when starting. If I reboot the server then works fine for awhile and then back to the error when trying to run from the IV.

11/26 16:56:38-cqc, CQCServer, CIDOrbSrvWorkThread_4
{
CIDSock, CIDSock_StreamSocket.cpp.1126, Failed/Not Ready, Error: 5025/0/0
The socket is not yet connected.

Here is my command to run.

Devices::FieldWrite
P1=TheaterTek-noneIP.Power
P2=True
P3=True

Devices::FieldWrite
P1=Variables.%(StdRTV:HostName)-SelectedMovie
P2=%(GVar:Title)
P3=True

Devices::FieldWrite
P1=USBUIRT.Invoke
P2=Yamaha AV Receiver.Power On:3
P3=True

Devices::FieldWrite
P1=USBUIRT.Invoke
P2=Yamaha AV Receiver.Input-Switch
P3=True

Devices::FieldWrite
P1=USBUIRT.Invoke
P2=Impact Acoustics AV Switch.1 Green:3
P3=True

If Not Devices:riverIsReady
P1=TheaterTek

System:ause
P1=4000

End
Devices::FieldWrite
P1=TheaterTek.PlayMedia
P2=$(Variables.SelectedVideo)
P3=True

IntfViewer::Exit

[Dean Roddey]

What is the status of the driver in the Host Admin dialog box? Is it online or in error? If in error, put it into verbose and bring up the Log Monitor and see what it's complaining about.

[Trioxide]

Both drivers are online - TheaterTek (TheaterTekIP ver1.1 used to play movie and control) and TheaterTek-noneIP (TheaterTek ver2.0 Deprecated used to start TheaterTek). When I run the command listed above TheaterTek does start but then nothing. So I close it and that is when I see the error from CQC. Changed verbose to high but nothing new listed in the log file.
Looking in the TheaterTek driver and the movie info is not being passed to it, just seeing an older movie picked and not the current one.

[Dean Roddey]

If TheaterTek isn't running, you would see that error. So that makes sense. You should check the current status (via the app control driver) before starting any playback and if it's false, then power up TheaterTek and wait for the power field to go to true before continuing.

As to why it's not responding to commands when it is running, I'm not sure. I assume you are writing to its PlayMedia field?

[Trioxide]

Been playing with it and it has to be this command as I removed everything else except this and it gives the same error.
Devices::FieldWrite
P1=TheaterTek.PlayMedia
P2=$(Variables.SelectedVideo)
P3=True

So somehow it is not seeing TheaterTek the program so can not pass along the information???

Variables.SelectedVideo=%(MediaRTV:ColCookie)

Like I said works fine when I reboot: starts TheaterTek and plays the movie. When I am done I close TheaterTek so I can see CQC again. Later, I don't know how long, I get this problem.

[Trioxide]

If TheaterTek isn't running, you would see that error. So that makes sense. You should check the current status (via the app control driver) before starting any playback and if it's false, then power up TheaterTek and wait for the power field to go to true before continuing.

Tried that and when TheaterTek is running it says Running. When I close TheaterTek it says Stopped under status. Have tried to manually start TheaterTek and then run the TheaterTek.PlayMedia command but same error.

[Trioxide]

Been doing some more troubleshooting. If I reboot it works fine UNTIL I close TT. If I leave it running then I can start another movie BUT if I close it then when I start another movie TT-NoneIP starts TT and App Control Server says it is running but TT driver I guess does not see it and that is where I am getting the error. Have tried other transport commands and same problem. So how I see it when TT the program is closed and then started again it does something so TT the driver does not know it is running.

Is there a different way to start TT besides the TheaterTek ver2.0 Deprecated driver way? Is there not an option from the newer ver1.1 IP driver?

[Dean Roddey]

So you are starting up TT when a new select is made? Are you giving it time to actually get up and running? Generally you'd want to do something like, check the power field. If false, start TT up, then do a WaitDriverReady before you proceed, to give TT time to start and the driver time to connect to it and get ready.

[Trioxide]

You see in the commands above that there is a if driverisready command, if not then it does a pause. I have manually tried and waited minutes and still nothing. The commands are the same everytime so I don't see how that would make a difference as stated before it works fine when computer is rebooted. Just when TT the program is shut down after using then it does not work the next time.

[Dean Roddey]

Is the (IP) driver seeing that it has closed? And it connects again ok after TT comes back up, right?