Jump to content

Erik Rönnqvist

Member
  • Posts

    108
  • Joined

  • Last visited

1 Follower

Profile Information

  • Gender
    Not Telling

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Erik Rönnqvist's Achievements

(3/3)

  1. I just tested with a 14000x2000 Hap movie, and that works just fine, but 12000x12000 does not work. My best guess is still that you hit some kind of limit in the GPU. /Erik
  2. It is possible to play Hap files in very high resolutions in Watchout. I just encoded an 10000x10000 Hap (30 fps) and it plays ok. 12000x12000 will not work on the computer I am using, so my best guess is that I reached the capabilities of the graphics board. While there is no hard limit in Watchout for Hap resolutions, you will sooner or later hit the wall of what the GPU is able to handle. /Erik
  3. As few chunks as possible while still getting smooth playback is the general rule. There is never any point in using more chunks than there are cores in the CPU. Chunking adds a slight overhead in the form of less compression, but the difference is very small. If a movie needs 4 chunks for smooth playback, and you decide to pre split it into 4 presplit movies, I would try with no chunking (=1 chunk) for the individual presplits. /Erik
  4. Hi, I realize Trax and (probably) the Touchdown device aren't currently supported products, but I'm trying to get a Touchdown working for a personal project and I'm wondering if the old Showroom Forum posts re archived somewhere that I can sort though? My main issue is it seems like once the built-in batteries die, The unit will not function. I have two units I purchased second-hand, one which currently powers up, and one that did for a short time, but now doesn't for longer than 10 seconds. Both have touchscreens that don't work. Any info you could provide would be awesome. Thanks, Bryan

  5. From the info above it looks like it's avc high profile without chroma subsampling (4:4:4), which is not supported by watchout. You have to stick to 4:2:0 chroma subsampling. Another important aspect when encoding h264 is to NOT use B-frames. B-frames are great when you are trying to get maximum compression, but they have a very negative impact on playback performance. If you are worried about the quality when not using B-frames, just bump up the bitrate by 10%. This will have much less impact on performance than sticking to the lower bitrate and using B-frames. For encoding with constant bitrate I would use: ffmpeg -i input.mov -vcodec h264 -pix_fmt yuv420p -bf 0 -g 30 -b:v 10000k -minrate 10000k -maxrate 10000k output.mp4 You'll have to change the bitrate to your preferences of course. Another option would be to encode with constant quality: ffmpeg -i input.mov -vcodec h264 -pix_fmt yuv420p -g 30 -bf 0 -crf 18 output.mov -crf 18 means visually lossless. By increasing that number by 6, the file size (and of course bitrate) will be about half, and the quality will decrease. You will have to experiment yourself to strike a good balance between quality, file size and playback performance. Valid range for the crf parameter is 0 to 51 /Erik
  6. Hello! I am curious about your statement above that there is a limit of two streams for receiving NDI into Watchout, where does it come from? There is no limitation of the number of streams in Watchout, but of course, sooner or later you will hit the wall either due to network bandwidth issues or an overloaded CPU on the display computer. During testing we have successfully run 64 unique 1920x1080 streams in 30 fps on a 10 gigabit network. This test setup was running for days without any issues. We do not currently support NDI output from Watchout. /Erik
  7. Hello! The Hap decoder is natively built in into Watchout (both display and production software), so there is no need to install any hap codec. In fact, installing additional codecs will in many cases just make things work worse, which is what is happening here. To fix the problems you are seeing, uninstall any codecs you have installed on both display and production computer. You might also need to empty the cache folders. Then it should work properly. I would also advice against installing quicktime on the display computers. It is not needed there. Quicktime is only needed if you use the Export function in the production software. Another issue with installing external Hap decoders is that the decoding will take place on the CPU, but when using Watchout's internal Hap codec, most of the decoding will take place on the GPU, thus giving much better performance. /Erik
  8. A lot (if not all) AMD drivers from 2018 have had performance issues of various sorts. I would advice you to test with the drivers from 2017 q4.1 and see if that makes a difference. /Erik
  9. Proxy is lowest quality, really intended for preview purposes only. LT is better, Standard even better, and HD best quality (of the 4:2:2 formats, that is). For editing, you should really use the highest quality, but for playback purposes Standard should be good enough in almost all cases. I doubt there are many people that would be able to spot a difference between Standard and HD in a playback blind test, given that the videos are encoded using the same encoder, and that the screens are identical. /Erik
  10. Hello! Unfortunately there is currently no way of seeing this from the production software. You will get a warning in the message window when the disk is full on a display computer, and I can agree that a warning before the disk is actually full would be more useful. /Erik
  11. Using the low-latency mode increases the risk of stuttering. By using this mode, Watchout will always display the latest frame received from the NDI source. By selecting balanced or smooth, Watchout will keep an internal queue of a few frames, which decreases the risk of stuttering, but also increases the latency somewhat. So if low latency is important in this case, balanced or smooth may not be the best options. Streaming video over Wifi in public places is problematic, since there are so many things that can disturb the stream. /Erik
  12. Most likely, you will have to install the NDI | HX driver, which is available for download on NewTek's web. The reason you are seeing the stream on the production computer is that the Watchout production software use a separate low-bandwidth stream for the preview, to preserve network bandwidth. The preview stream is usually not sent using the NDI | HX protocol. /Erik
  13. Currently there is no way of doing this in Watchout. But it is an interesting idea. It is possible though to specify an alternate source in the NDI media's settings. If the primary source goes down, Watchout will automatically switch to the alternate source. As soon as the primary source is back online, Watchout will switch back to the primary source. I don't know if this would help you in any way, but I figured I would just mention it in case you find it useful. /Erik
  14. Hi Eric!

    My name is Tim Musin, I'm from INTmedia, premium parthner from Russia!

    Please, could you comment my topic (private or in topic, as you prefer) :

    It's very important to us. 

     

  15. The hap codec is built into Watchout, so there is no need to install it. In fact, installing codecs on a computer running Watchout is generally not recommended. You don't mention which Watchout release you are running, but if it is 6.2.1, there is a bug that in many cases makes hap files with embedded audio show up as audio only. The workaround is to extract the audio from the video file, and run audio and video as separate files/cues. However, the bug is fixed, and will be included in an upcoming bug fix release of Watchout. /Erik
×
×
  • Create New...