Jump to content
Dataton Forum
warwolf

bug - refused to play timeline

Recommended Posts

Hi,

I had a show with multiple clips in the timeline. It played perfectly for 2 days. The computers been rebooted between those 2 days. At the end of day 2. Arrowhead is position before the cue. 

I remember that I triple, quadruple check that I was clicked on the main timeline and that I was online and that I was not on standby mode

friday april 12 at 20h35

  • - I Press space bar - Nothing
  • press again, maybe I didnt fully press - nothing
  • I think, maybe the keyboard stopped working, I click with the mouse on the green arrow at the bottom of the main timeline - Nothing
  • I move the arrowhead else where, it moves but no files play on the production computer and on the display computer.
  • press space bar again multiple times. 
  • Try ctrl-D
  • try going offline (I can see the status window going from online to offline) then online (I can see the status window going from offline to onine)
  • nothing happens
  • try offline-online again. still does play
  • quit the application, reopen, everything works.

Missed the first 25% of the show( a 4min show) My client was unhappy, and the client of my client even more. I can't even reproduce the bug. It seems very random to me. 

never saw any error message.

The log show the same message error mxhscroll or something like that. See attachment

watchout version 6.2.2

Let me know if there is something I could provide to help you help me thank you

 

warwolf-logfile-noresponcetospacebar.zip

Share this post


Link to post
Share on other sites

I've been able to make the watchout production computer crash easily by preloading (pressing stop) aout 16 tasks. Is that a normal behavior?

CPU was way under 50%
memory was also under 50%

However, I can't reproduce the not playing main timeline thing

Share this post


Link to post
Share on other sites

It looks a bit like a fault on your production computer. Has it been tweaked (basic tweaks)? Which OS are you running?What sort of graphic card are you using on the production computer?

Pre-loading 12 timelines can put some work on the production computer since it needs to render all the content of the stage window at the same time while usually the graphic power of notebooks is not the highest.

If you have a lot of displays and maybe even more than one display computer, the display engine in WATCHMAKER has to do the work of the complete cluster to render the content.

A good way to handle this is to switch the stage window to show thumbnails only instead of videos in highest possible quality. Once the show is programmed it is usually not necessary to see the videos running in the stage window. This reduces the load on the production computer quite a lot.

The log files do not seem to show any information about the crash on April 12th. 

You could maybe check the events of the Windows log files. Maybe you'll find some hint in there.

 

Share this post


Link to post
Share on other sites

Thank you for your answer. The stage preview was in high quality for programming. that must be why. It's unfortunate that w-o cannot handle this error and just crash instead of maybe not allowing to get there. I only found this behavior while trying to reproduce the "not responding to play" issue(Which I was not able to reproduce).

windows 7, service pack1. The basic tweeks had been done. The show is done now, I don't have access the graphics card.

Now about the real issue. The playback not responding. I wish I still had access to the computer to get the event log of windows. I'll see if I can find a way to get it. Anything else I should be looking for that could be helpful finding the problem?

Thank you

Share this post


Link to post
Share on other sites

I've not seen WATCHOUT production crashing when too many videos had to be rendered. It usually slows down a lot and working with cues gets lagging. But the Windows protocols could show more information about the cause of your issues. Alex is pointing to an issue which usually happens when more than one NIC is active. In this case the production software will roll the timeline but the display computer will not react. In your case, the gui of the production software was blocked, wasn't it?

Share this post


Link to post
Share on other sites

Hi, I missed Alex answer. 

There are 2 network port and each computer (production and displays). Only one port on each computer had a network cable plugged in.

In my case, the production computer refused to roll any timeline. It was stuck at stop. I would click on the play button at the bottom of the timeline and I would see the button being pushed down, but it would return to a non-pressed state immediatly after the release of the mouse click / space bar.

 

thank you for your time

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×