Miro
-
Posts
144 -
Joined
-
Last visited
Posts posted by Miro
-
-
Are you using a managed switch, router or unmanaged/dumb switch? Seems like the UDP packages are lost somewhere on the way. Do you use any firewalls?
0 -
Hi, there is a problem with the X99 chipset and most professional graphics adapters. This is not a bug in WATCHOUT and appears in any other applications as well. Playing sounds through the graphics card's audio interface works but playback through all other interfaces results in various sound errors.
Which motherboard are you using?
0 -
Hi, I managed to reproduce this issue on one of our computers and we will have a fix for it in WATCHOUT 6.1.1.
0 -
Can you post some specs on your system (like OS, motherboard, GPU, etc..), capture card model and capture card drivers?
Best regards,
Miroslav
0 -
Which capture device are you using? We need some more info about your system. Does WATCHOUT 6.0.2 work with live inputs on the same computer? Or are you running mixed versions of WATCHOUT on your system?
0 -
The MPEG-2 codec doesn't allow dimensions to be multiples of 4096. FFmpeg throws the following warning while decoding your file: "Invalid horizontal or vertical size value". If you try to encode you probably get this error: "Width or Height are not allowed to be multiples of 4096
add '-strict -1' if you want to use them anyway.".However, VLC and FFmpeg/FFplay are using libAV for decoding and can play the file anyway (even with warnings). I will have a look if it's possible to force the mainconcept's decoder (the one used in WATCHOUT) to play files like this.As a workaround you can pad your video to 4100x656 and it will play in WATCHOUT. Simply add -vf "pad=width=4100:height=656:x=2:y=0:color=black" to your FFmpeg command line and it will do the trick. If needed you can crop those extra pixels in WATCHOUT using a crop tween track.0 -
WATCHNET 1.2.1 is released and available for download.
This version contains the following fixes:
- A bug has been fixed in the WOB file distribution to a WATCHOUT cluster where Image Sequences were not distributed.
- Sliders are now rendered correctly and title text-orientation adjusted in vertical mode.
- Titles of Panel Items are now correctly clipped if they are too large for the item.
- Panel Sliders can now correctly deal with any value ranges.
- Media uploading for Panel Items has been greatly enchanced.
- Resolved a licence key bug which prevented the server to run using a V5 key.
- Cluster input names with white spaces are now correctly handled.
Let me know if you have any questions.
0 -
If you can convert a small sample (use -t option in ffmpeg) of just a few seconds and upload somewhere we can have a look at it.
0 -
Quim, yes you can mix different displays and EDIDs. Make sure you can run the same refresh frequency on all displays to prevent sync issues.
0 -
Quim, we will investigate this. What sound card are you using? Does the same sound card work in windows 7 with WO 6 Production?
0 -
WATCHOUT 6.1 and WATCHNET 1.2 are now available for download. For brief description of what has changed please read the release notes below. A Mac OS X installer for WATCHNET 1.2 will be available for download in a few days.
0 -
At the moment WATCHOUT doesn't work in Windows 10. We are working on a solution and will release an update as soon as possible. This issue has our highest priority and we expect to have a solution in March-April. Until then we recommend Windows 7 Professional. We apologize for any inconvenience!
Best regards,
Miroslav Andel
Chief Software Developer
0
Live Video "Micro Stuttering"
in WATCHOUT FORUM
Posted
Hi, do you have the possibility to measure the time between the micro-glitches?
If the device generating the live video is not genlocked with the display computer then some microscopic glitches will occur due to the difference in refresh rates. Say that the captured device is generating images at 59.94Hz and WATCHOUT renders at 60.00Hz then WATCHOUT will insert a double frame every 16-17th second. In a very smooth animation this will look like a microscopic glitch.
Frame blending should smooth out this kind of frequency mismatches but if you don't want this feature then genlocking is the only way to go. Otherwise you will always get this issue since the source device is not perfectly synced with WATCHOUT (they use separate clocks). In your case the camera might actually output images at 49.995 Hz while WATCHOUT renders in 50.005Hz which will generate a glitch every 100th second (1.67th minute).
Best regards,
Miro