Jump to content
Dataton Forum

Erik Rönnqvist

  • Content count

  • Joined

  • Last visited

About Erik Rönnqvist

  • Rank

Profile Information

  • Gender
    Not Telling
  1. Direct URL Images in 6.2

    This is not a deliberate change. It is a recently discovered bug that was introduced in 6.2 when we added the possibility to presplit still images. My guess is that an older show imported into 6.2 should work, but I have not tested it. The bug is fixed and will be included in an upcoming bug fix release of Watchout. /Erik
  2. Problem audio loop 6.2.1

    Hello! Yes, there is an issue with looping video files with embedded audio in Watchout 6.2.1. We are looking into a solution for this. The problem is that audio (AAC for example) is compressed in chunks of a few milliseconds each, which in almost all cases makes the audio track slightly longer than the video track. The audio chunks are fixed in size, and you cannot have half a chunk or something like that. Usually the last part of the last audio chunk in the file is silent, just to fill up the last chunk so you get all of the audio encoded, rather than making the audio track slightly shorter, thus truncating the audio track. This makes the timing incorrect when looping. I assume you are running compressed audio. If possible, try to use uncompressed audio (PCM) instead. This will make the file larger, but since there is no compression in chunks involved, the audio track should be exactly as long (or very very very close) as the video track, which should make the problem disappear. As always, keeping the audio in a separate file usually works best, which could also serve as a workaround (or a permanent solution). /Erik
  3. HAP Encode / QT / Etc

    There are some issues with Hap files with embedded audio in 6.2.1, but as long as there is no audio in the files, you should be fine. The issues have been resolved, and will be included in an upcoming service release of Watchout. That said, the general recommendations still stand: Use separate audio and video files whenever possible, and do not install any codec pack, encoding software etc on machines running Watchout. /Erik
  4. HAP,New Codecs and more...

    I usually download the zeranoe builds for ffmpeg, available at https://ffmpeg.zeranoe.com/ A simple example for encoding a HapQ movie and removing the audio from the file: ffmpeg -i InputMovie.mov -an -vcodec hap -format hap_q HapQMovie.mov -i specifies the input file, which can be just about any format -an tells ffmpeg to remove any audio tracks -vcodec (or -c:v) specifies which codec to use -format specifies which hap flavour to use (hap, hap_alpha or hap_q) The last argument is the name of the reencoded file. For very large movies (high resolution, that is) it makes sense to use the -chunks n argument to enable multithreaded decoding, where n is the number of chunks to use. It never makes sense to use more chunks than there are cores in the target (display) computer. As each additional chunks adds a (very) slight overhead in the form of decreased decoding speed and larger files, it is generally a good idea to keep the number of chunks as low as possible. For a list of codes supported by ffmpeg: ffmpeg -codecs For help about a specific codec: ffmpeg -h encoder=x, where you would replace x by the name of the codec as listed by the ffmpeg -codecs command. /Erik
  5. HAP,New Codecs and more...

    If you can live with the command line interface (which I personally like better and better the more I use it), ffmpeg would be my recommendation. Since Hap files tend to be large, a fast disk is probably one of the most important aspects when encoding Hap movies. It is also quite easy to do batch encoding in ffmpeg by just using a regular .bat file (when running on windows). /Erik
  6. NDI on WatchPax

    Hello! The NDI HX driver should be automatically installed on the display watchpaxes when upgrading by going online in the production software. However, this assumes that the NDI HX driver checkbox in the Watchout installer was checked when installing/upgrading Watchout on the production computer. When trying to display NDI HX content (from the Spark) on the Watchpax display computer, what did you get? Just a black screen or a screen saying that you need to install the NDI HX driver with a link to NewTek? /Erik
  7. NDI on WatchPax

    Which Watchpax and Watchout version are you using? The NewTek spark sends NDI|HX which is quite different from the NDI streams sent from the Scan Converter (and similar tools). NDI|HX is more highly compressed, and is not all I-frames as regular NDI is. NDI|HX needs a driver to be installed on the display computer, which is done as part of the upgrade process i Watchpax. (When installing on other computers the NDI|HX driver install is optional). Watchout 6.2.1 contains an updated NDI|HX drivers, that solves some issues with the driver supplied with WO 6.2. Is the Spark configured to sent Multicast? If so, I would recommend turning Multicast off and see if that makes any difference. /Erik
  8. Windows HAP without QuickTime?

    Watchout only uses Quicktime when exporting a movie, so it would make little sense to install Quicktime on a display computer. If you want to use the export function in Watchout, Quicktime is required on the production computer. That said, if you want to encode to Hap using a Quicktime-enabled application, you might need to install Quicktime and the Hap codec for Quicktime. Another option would be to encode Hap files using ffmpeg, using the following command line: ffmpeg -i inputfile.mov -vcodec hap -format hap_q -chunks 4 outputfile.mov Change hap_q to hap or hap_alpha if you want standard hap or hap with alpha. The chunks argument enables multithreaded decoding, but higher numbers give slightly more overhead, both in space and decoding time, so this number should be kept as low as possible. For a 1920x1080 video, one chunk is sufficient on most hardware. Higher resolutions and/or slower hardware might require a larger number. It never makes sense to use a larger number than the number of cores in the CPU. /Erik
  9. Are the files video only or video+audio? There is an issue with hap files containing audio in 6.2 and 6.2.1 I have received a few reports about pink color in HapQ videos in the production software, but never in the display software, but I have not been able to successfully reproduce the issue here. I don't think the files can be tagged to use a certain brand of the decoder. Uninstalling Quicktime would probably make no difference, except that Watchout would not be able to play the files at all, instead of using the wrong decoder. That said, it could at least be worth testing. /Erik
  10. HAP Version

    Any version is fine, and I would recommend using the latest version, since it contains the latest bug fixes and performance improvements. But you will have to stick to Hap, HapAlpha or HapQ. HapQ+alpha is not yet supported in Watchout. /Erik
  11. WATCHOUT 6.2 Bugs

    There seems to be an issue with Hap files containing audio in Watchout 6.2.1, as it is many cases will get recognised as audio only. The solution in the meantime is to use separate video and audio files. Additionally, installing codec packs, or software that in their turn install codec packs, on the production computer can cause issues like this. /Erik
  12. Is there anything else besides video in the Hap file (audio track(s) for example)? I have managed to reproduced similar issues with Hap files containing audio in Watchout 6.2.1. Is the Hap movie stored in a .mov-file or something else? What happens in your case is probably that Watchout fails to play the Hap file using the normal playback mechanism, and when this fails, it reverts to trying to play the file through Quicktime instead. Regarding the pink colors for HapQ, have you ever seen it on a display computer, or is it only in the production software? Do you see the pink colors when displaying the actual movie (Best Quality preview) or only when you have selected "Video as thumbnails"? One last reason I can think of is if you are trying to play a HapQ+alpha files, which is currently not supported in Watchout. As of now, Watchout supports Hap, HapAlpha and HapQ. /Erik
  13. WATCHOUT 6.2 Bugs

    Regarding the Hap and audio issue, where Watchout does not recognise the embedded audio: Have you installed any codec packs or similar on the computer? Haali media splitter is included both here and there, in encoding applications for example, and may cause issues like this. /Erik
  14. WATCHOUT 6.2 Bugs

    Are you somehow trying to export to a Hap file, or are you trying to export a show containing hap file(s), and in that case which format are you trying to export to? /Erik
  15. Update lag

    Yes, going online may take quite a while if you have very long timelines, where at least some parts of it contain a continuously changing tween parameter. The reason is that Watchout needs to sample the timeline(s) at quite short intervals to determine which media is visible on which display server(s). Only media that is actually visible at some point during the show on a certain server will be transfered to that server. The reasoning behind this is to shorten the time it takes to transfer media as well as to preserve disk space on the display servers. That said, if you turn on live update, the process will be faster, since in that case all media used in the show will always be transfered to all display servers, thus eliminating the need to sample the timeline(s). /Erik