Jump to content
Dataton Forum

PierreLucB

Member
  • Content Count

    33
  • Joined

  • Last visited

About PierreLucB

  • Rank

Profile Information

  • Gender
    Male

Recent Profile Visitors

595 profile views
  1. It yes plays in sync when not triggered from external TC. Also when there was a sync different because we were using TC, the moment I would stop the TC the watchout displays would jump catch up to where they were supposed to. In the end I did not have time to test whether the problem came from the sample rate setting of the sound card or not, there were other priorities for the show. This will have to be tested at another time.
  2. Hi there JFK, Sorry was out of internet for a while. We are using 25 fps TC and yes we are specifying it in the production computer. This problem (or very similar) has also happened to me on 30 fps and possibly 29.97 (but can't remember if it was drop or non-drop) Watchout v6.6.2
  3. Hi there, I believe this maybe the 3rd time I'm experiencing this issue and it's a bad one! Sometimes with LTC incoming to the Prod computer, the display computers will play the content slower than it should (or out of sync) resulting in videos being out of sync with the rest of the show. Here is a video showing this issue. You will the see the the image in the Prod computer and in the Projections do not match and that the timeline position and the TC being projected also do not match. (But they should!) Note, external TC readers (Mif4s) and Prod computer TC match but the Displays
  4. That is a tragic and shocking news. Such an active member indeed. Rest in peace Thomas.
  5. Hi guys, Every time I try to import a FBX 3D object Watchout gives me an "Not recognized as a media file" error. I've joined 2 fbx exported differently to see if you can try them. .OBJ work but from C4D in obj, C4D always exports the whole scene. With FBX I can export only a selection which I need to do. Any ideas what could be blocking it? Thanks. J1-plb-1.fbx j1.fbx
  6. Hi Jochri, The filenames vary in length but I even get these errors when I am renaming a simple play or pause cue. I doubt it's the network's fault. I've got 2 switches. One a the control booth and one with the display computers backstage. Here is my show file. https://www.dropbox.com/s/yxexqprfzg6iqen/Fame.watch?dl=0
  7. Hi everyone, Does anyone have an exemple of the string to send to trigger a ControlCue of an Aux timeline? I cannot figure it out. I can get other commands to work but not this one. I'm sending the commands over UDP at the moment. Thanks.
  8. Hi Callum that's good to know. So for you it only happens with a specific show file? @Benoit Turning off UDP inputs did not help, I'm still getting a lot of those errors. Often when moving 2 or 3 clips to a different later or even editing tween tracks. I think my original show file was created in an earlier version. Maybe 6.1.? And I'm now running 6.2.2. Any more thoughts on this? I'm also getting problems with the 3D projector View tab and Mask tab not always showing their views but just showing black.
  9. Hi Benoit, That's good to know. On the network there are: -2 Production computers -4 Display computers -8 Barco HDF-W30 projectors (which I send TCP shutter cues to) -1 Lightware Matrix 16 DVI -There was 1 but will be 2 QLab computers which Watchout will trigger and receive Timecode from. -4 network switches -1 or 2 laptops (windows and mac) I had the UDP incoming trigger turned on and I wonder if it could come from there... I'll play with this and see how it behaves.
  10. Thanks Brecht, I might give this a try. Steve, with my setup using Nvidia Quadros (K5000 I believe) the numbers in the windows panel are the same as the numbers in the Nvidia panel but they do not match the ones from Watchout.
  11. Hi guys, I have a Watchout 6.2.2 system running on Windows 7 pro 64bits service pack 1 and I'm getting a Lot of "runtime error" coming up with I do most operations such as add a tween track, change it, move content. As well the Live update doesn't work well. I have to run manual updates quite a bit. See picture here: https://photos.app.goo.gl/4Gufj60n48JPz0Ns2 I have 2 displays each with 4 outputs and 2 backup display computers which are just in stand by right now. Any ideas how to fix this? Thanks.
  12. Hi guys, Where does Watchout get its video output number for the display computer? Are they suppose to match with the Nvidia graphics card output number for instance? What is the correlation? I'm trying to figure out the order. Thanks.
  13. Haaaa! I didn't know this. All good. Merci Benoit.
  14. Hi guys, I'm running some tests offline for an upcoming production and when I scale up a virtual display media I get a very low quality result. When I scale an actual media, the quality is fine. Is this just a preview issue? A bug? Normal? I tried to attach screenshots but the forum keeps on giving me error. PNG or JPEG... Thanks.
  15. This same thing is happening to me right now running Watchout 5.5.2 and Windows 7 64bits. When timecode is running and I go to the Watchout Production computers' preferences and I uncheck the "Timecode control of Main Timeline" the watchout production software just disappears (quits) without any error message. I have to re-open watchout afterwards.
×
×
  • Create New...