Jump to content

Claude.Rivet

Member
  • Posts

    52
  • Joined

  • Last visited

Everything posted by Claude.Rivet

  1. Hello JFK, In this case it would be 6.3.1 and 6.2, the problem happens with still images or videos. However, we think we found the culprit and will be testing further tomorow to confirm but it looks like it's a license key issue, the hardware dongle itself. Changing it seems to have solve the problems but we barely tested at the end of our troubleshooting day. I will post the confirmation after the tests. Thanks for helping!
  2. Hello guys, We are currently installing a new display computer and are stumbling upon issues and while we are still testing and hunting for solutions I would like to dive in the collective minds for solutions. x299 (MSI raider) i7 8 cores w9100 32GB ram (4channel of 8GB) on board network adapter (1Gbps) Win10 pro (we are trying win10 entreprise LTSB atm) win10 tweak list applied Problems: -1- some medias just do not show up on the display computer, we tried solid and a jpeg. The same media that was not showing can start showing after a reboot and a new media was affected. The reason we haven't tried other media is number -2- -2- file transfer do not complete, it either freezes on a file and gives us a caching error. Solutions tried and current troubleshoot: -1- ran memtest86, RAM is fine -2- ran iPerf3, network is fine -3- tried different disk and different storage tech (ssd, nvme, HDD), no difference -4- tried the same sessions on a different display machine which was then working flawlessly -5- tried to install win7 pro. It doesn't work as x299 and the new i7 are not supported and external drivers won't install -6- we are currently trying win10 entreprise LTSB with the tweak list, will update post with result Considerations With win7 phased out and with new hardware being unsuported anyways we are entering a phase of uncertainty with Watchout where we will embark on multi day testing not knowing if it's our hardware, the driver versions, a faulty component, a tweak, an addon that causes the problem. I guess it was always the case but not at this level, troubleshoot will always take place but having a media server that doesn't officialy and rigorously support the current OS in place is tricky at best. For years we had the win7pro fallback, it doesn't apply anymore and win10 obviously has issues, for many users. It would greatly help to be able to rule out the OS as the possible culprit when having problems. Does Dataton has any OS plan for the upcomming year? Do you guys ever plan on moving to linux and skip all the windows nonsense? Do you plan on releasing a fully win10 compliant Watchout? Thank you for the upcomming help and for the great product, it might give us headaches recently but it's still our favorite one regards
  3. Hello, A few things to consider: -Update win7 to the latest service pack (sp3 I think) -If given the choice pick faster clock over number of cores, Watchout uses 2 cores mainly, it is a 32bit app also. Capture cards and external control can lead to more than 2 cores being used but at a fraction of the first 2. Since you work with HAP speed, not concurrent processing, is important, the GPU works, not the CPU. -Update your BIOS, M.2 drives are constantly getting performance boost and stability improvement trough those, they are recent and still being tweaked by BIOS vendors. -If you have the W9100 you need the S400 sync board or else you do not framelock, which leads to your problem of having only two computer in a cluster performing badly, if you were framelocked they would ALL perform badly (or not) the exact same way on the exact same frame. just having an S400 board and connecting it is not enough, you need to configure it if the AMD graphic card advanced settings. First you define a master and lock each of the card output on that timing master for each computer in your cluster, for the master computer it means choosing input 1 as the sync source for example and then slaving each other output to the output 1 and then setting the RJ45 connections to that master, then in each other computer you set the receiving RJ45 as the master and slave your outputs and the outputing RJ45 (for the daisy chain) to it. You also need to identify in Watchout which output is the sync chain master. That being said I encountered the same issues you are having. If the payback is choppy under the same circumstances every playback it is usually because of your file bandwidth (or some other bottleneck). HAP bandwidth is variable, very variable, so some frame might require 800MB/s while other demand 1.4GB/s. After some testing we came to the conclusion that smal gradients where the issue; fire, smoke, fancy light bubbles, HAP has a hard time encoding those or rather keeping the bandwidth low. Noise, if not blurred, doesn't display this issue, it is always as soon as small gradients are found (a sky is not an issue, it is a gradient but it is big). The only way to reduce the bandwidth is by reducing the file size (resolution), the only painful way I found to figure out by what exact amount is by encoding the file with FFmpeg and watching the cmd line output as it encodes to spot the highest bandwith peak, if I peak at 1.8GB/s and my storage is giving out 900MB/s max then I know I have to reduce the size by 50% so HAP encodes it within my hardware spec. I am currently writing an encoder, an FFmpeg interface actually, that amongst other tracks your HAP bandwith trough the encode process and auto resize the file in a second pass if the first one leads to frames encoded at a superior bandwidth that the system can take. Other than that I don't know of any way to manage it in an automated manner. A note about encoding in chunks, if you plan on playing back concurent files do not encode in chunk as it allows bigger files to be played back, yes, but at the expense of limiting the amount of concurrent files that can be played back. If I encode in chunks I can play 4 HD files before stuttering happens, without chunks I can play 56 HD files before it does. The difference is huge. However I can play back larger files when encoding in chunk than without, it is a tradeoff. As a general rule of thumb you want to encode in a number of chunks equal to half the number of cores on the playback computer so that you have no issue crossfading between files. That's what I see for now, hope it helps.
  4. Use virtual displays, you lose the warping, which is a shame, I'd really like to warp the show as a whole rather than by screen but otherwise it would do the trick. Other than that you basically seem to be referring to what Watchout calls task, which are timelines you can start and stop independently of one another, each task can be layered according to the rule it is set to (always above, according to list order...).
  5. Until Watchout supports generative and procedural content and input processing these tracking things will remain tricky to play with, high interactivity does require much work when working with playbacks. Other than that Watchout has no input processing whatsoever, so damping and prediction must be done before the input is sent to whatchout and Watchout doesn't give feedback; positions, orientation, rotation, all manipulated parameters or coordinate must be tracked in the external software as you cannot query Watchout for the infos (as far as I know, would be happy to be wrong). That being said, there are many packages out there that could manage your interactivity and digest the input before sending them to Watchout. Then, color changes, rotations, media follow, position based playback triggers, are all doable. I am not sure I should list them here as some are from competitors but a quick search on google should give you a few results. One last thing, Watchout doesn't latch, it starts, stops or pause, and it doesn't auto generate channels in case you trigger the same timeline twice (at best you will restart the video) playing back a video for as long as a note is pressed for example is not possible, latency and lack of enveloppes amongst other make it unaesthetic. Watchout is a superb software but as far as interactivity goes it is pretty limited right now. You might also consider a VRPN server for easy interfacing with Watchout. https://github.com/vrpn/vrpn/wiki Also, Blacktrax uses Optitracks technology which is now available for everyone and quite impressive. Here is their VR application page (you feed a screen rather than an helmet but it's the same package): http://optitrack.com/motion-capture-virtual-reality/
  6. First things first: Select wireframe preview, try Still crashing? First possible culprit is the medias, Watchout can deal with a great variety of format, just not all at the same time, general rules of thumb: -HD = HAP or .m2v (mpeg2 video stream, no audio) or .m4v (mpeg4 video stream, no audio) -Non-Standard resolution under HD = HAP or .m4v -Non-Standard resolution above HD = HAP -Transparency = Hap_Alpha -Images = png -images transparency = png 32bit -audio should be .wav -HAP, each side must be divisible by 4 -.m2v, each side must be divisible by 16 -.m4v, each side must be divisible by 2 (Watchout will still try to play back the file if it doesn't respect those divisible but problems will arise) -Separate audio and video, they should play back from 2 tracks Still crashing? Depending on the medias you might tax some part of your computer, storage is usually the main culprit, you are playing back from HD or SSD? You are entering computer specific issues, in the manual there is a whole section on how to configure Windows for Watchout, go trough and do. Do not use Watchout like you would use Word for example, it doesn't play well with software loaded and feature enabled computers, the simpler the system the better. Go on the forum posts about win10, I think there is a sticky about it, read and do. Start with that and come back
  7. M.2 drives are actually the way to go in display computers but there are a few things to keep in mind 1- Number of lanes: PCIe bus have 1GB per lane of bandwidth (roughly), it is important that you do your bandwidth calculation before building your computer and it is important you manage those lanes appropriately else you will have less performance from M.2 drives than from a normal SSD. Some slot share their bandwidth with the M.2 slot, if you install your graphic card in slot 1 for example and your M.2 drive in M.2 slot 1 they will compete for bandwidth and dramatically reduce your performance. Your motherboard documentation should layout how lanes are distributed. That also brings us to RAID1 M.2 drives, it's a very bad idea on most motherboard for the reason stated, however some PCIe card can fit more than 1 M.2 drives and raid them, this is the way to go, this way you have dedicated lanes for your storage because you aren't using shared lane slots. That also means you will have to reduce overall bandwidth usage for your machine, distributing your lanes appropriately becomes very important. 2- M.2 drives are NVMe SSDs, the one with insane performances at least, which mean they are not secure or stable and it means the performances will degrade with time, after 3years I get about 2/3 of my original bandwidth on my Samsung 950pro. It is important you have a backup system in place, personally I use an internal hidden drive and using one scripted keyboard key I backup my M.2s on this drive whenever my show reach a milestone in programming. SSD fails, they will, it's not a matter of "if" it's a matter of "when", be prepared. 3- Do NOT use an M.2 drives for your system, the CPU overhead is not worth it and in my experience it is far less stable, don't ask me why I still haven't figured that out but IF the motherboard can boot from M.2 corruption is more likely to occur on system drives than data ones. 4- HAP is ultimately limited by your drive bandwidth but you have to make sure there is still bandwidth available for the exchange between the graphic card (HAP is decoded by your GPU) and your drive and the system memory, so 5GBps becomes 20GBps because you use your lanes to read from drive, send to the card and read from the card in main memory where Watchout renders the scene for example, if your source is an input card count 4GB per HD input (according to Datapath documentation). That's about what I can think of right now but basically using M.2 is not a simple switch like going from HDD to SSD, your need to manage ressources. hope this helps
  8. Hello guys, I posted the issue on Github and they answered saying it was a Watchout issue and to contact Dataton. So it IS a known issue, and it IS in the hands of Dataton, this is almost good news as it means we will soon see a dramatic increase in playback performance as soon as this is fixed. Thanks for the help looking forward to the fix regards
  9. Still haven't got any reply from Dataton so I guess I won't get to test that. So basically Hap seems to be decoded in the CPU embeded GPU rather than on the AMD W9100 which only reserves the amount of memory needed for the frame buffers (or whatever it is named). If I used two output it goes from 302-304MB to 600ish and at 6 outputs the amount of reserved memory is around 1.8GB, so GPU-Z does report some stuff correctly now maybe some usage is not monitored and my assumptions are wrong but it does look like WO only takes ram on the GPU for it's output and decodes HAP elsewhere. My guess is if that get fixed (I will post on hap forums in case the problem is in the decoder) we will see a dramatic increase in playback performance as we will now use to pro card with 16GB of ram availlable for HAP decoding. Anyways, thanks for the help, hope to see some fix at some point. regards
  10. 50+files simultaneously, introduced one by one with 1second gap between. I will ask support, thank for the tip!
  11. Yes, this is a recipe for disaster, from experience. However, why not use a dual boot system, one for watchout, clean, and one for other stuff. A local clonezilla with two images accessible at boot via an F key is also a solution if the switch from Watchout to other stuff is rare.
  12. Here is the screenshot, long story short HD007 and HD008 are the 55th and 56th files added, usually is starts at around 51st and 52nd. http://imgur.com/a/FZUY4
  13. Is it possible HAP files are decoded with the intel GPU rather than the amd pcie card? It would explain getting identical results from an 8GB and 16GB machine and the GPU-Z reading.
  14. It keeps teasing me with it's cheap 6x outputs, I wouldn't run shows on them but I could see a small system for museum driving 6 output from one cheap computer playing back one HD stream per output (2x HD per output max when crossfading between content), facilitating management and saving space. Would be nice to know what results you guys got with it. Thanks, regards
  15. Good day, I am in the process of building new stations, I will post results and testing procedures when I am done as requested in another thread when I am done. However while testing HAP playback I stumbled upon an issue where my production computer was running out of video memory (as stated in the message panel). At 8GB I was not so surprised as I was playing 50x HD files however when playing those same files on my display computers I got the same message even though I have 16GB of video memory available. My production preview was set to video as thumbnail. Surprised I ran GPU-Z on my display and production computer while playing back those same files. I also ran AMD system monitor and Windows ressource monitor to get a bigger picture of what was happening. I logged to file when possible. GPU-Z reports a maximum of 304MB used on card... memory clock was topping and so was core clock but memory didn't seem to be even remotely used, telling me either GPU-Z was badly reporting or only the output frame buffer is reserved (HD 249MB) plus a little overhead and therefore GPU ram was indeed not used at all as all compositing was done prior. So why the video memory issue then? So I am getting this error where Watchout runs out of video memory even though all tells me there is still much memory left. Even if all meters are wrong (which is a possibility after all) there is still the odd result of running out of memory with the very same amount of data on both an 8GB card and 16GB one. Somehow I have a feeling I have a lot of unused power there . side NOTE: encoding HAP in chunk is not always a good idea btw, it helps to play back huge files but also greatly limit the amount of files you can play back simultaneously, in my production computer as soon as I play back 2 HD files encoded in 4 to 8 chunks (8cores processor) the playback as issues, with no chunks I reach 50x HD files. So be carefull about chunks, it helps, but only for huge files and only if you play back a minimum of file at the same time also, it is not the solution to my issue, it has been tested.
  16. There are many benchmark that need to be used if you want to properly benchmark your machine but there is not a single benchmarking tool aimed at Watchout specifically. I use many synthetic benchmark when testing components but in the end the only real measure of performance will be shown using a show I built specifically for the purpose, it is HUGE but it precisely measure the performance under many common situation in real world usage. Here is how it works: -I have 60 HD files, same content, different name, a sherrif star spinning on sand, hard to compress, obvious if there is a lag or latency issue, loop hiccup or anything. Alternatively I use to have a file containing fractal noise and a diagonal bar going up and down (easier to see jerk, stutters and the like on diagonal movement than horizontal or vertical one). Same thing, hard to compress obvious is there are issues. -I have 20 4k files, same content, the sherrif star on sand, same reason. -I have 10 10240x1080 files, noise and diagonal movement with color bars throughout in movement. All files are availlable in HAP, HAPQ, HAP Alpha, MP4 and when possible MP2, I also have several copies of the same movie (24x HD, 8x 4k, 4x 10240x1080) in image sequence, BMP, PNG and JPEG. That's a total of 456 discrete files. I then built a main timeline where it reads one HD file then after 3sec in starts another and so on and so forth until I reach my max or I see any artifact, jerks, tears, stutter, lag, anything. I note the number. I then jump in the timeline to another set of HD files but in another format. Take note when it displays issues. Then for the 4k files and finaly the large files (10240x1080). Then I do the same but with files playing back in aux timelines being triggered by cues, and then finally in composition playing back in virtual displays applied to 3D objects. ALL test are done with the full 6 output active with edid emulation and frame lock engaged. Then when I know the real limit of my machine for various situation and format I use my live inputs and 720p and 1080p and run the test again to see the limit when using live inputs on both the content and the live input lag/latency and fluidity of fades. At last I program controls for opacity, keying and scale and run the test while playing with my faders. It takes me 1-2 day to benchmark my machines but at least I truly know the limit in relevant circumstances. Currently I can play back 56x HD files, 16x 4k or 7x 10240x1080 concurently, in aux timelines in comps in virtual displays applied to a 3d object. These are my 4 year old machines I am building new ones this very month optimized for a live update workflow and remote management, I'm like a kid waiting for his new toys .
  17. I have been working in HDSDI for quite some time now and here are my observations: 1-BMD and typical video suite brand are cheap but they break easily, have flimsy power supplies and rarely do 1920x1080 60p, the BMD ones even when rated 3G are a good example. They are not easy to stack and secure cables in. 2-Theatrix X-Vision are currently the best show ready converters there are, reclocking on loop out, clear leds diagnostic (you know if the cables are in, if there is HDCP, if the signal reach, etc.), rock solid, seriously, rock solid, thread for installing c-clamps to rig on trusses, magnetized top and bottom for easy solid stacking, daisy-chainable powercons, screw on HDMI ports. Using RG7 cables we are doing solid 1920x1080 60p over 300', and using an xvision we can extend it another 300' because it reclocks and do it well. I have tried many many tools and these are the best converters, bar none and they are barely more expensive than BMDs. 3- Many video mixers work in i not p and many do not support 60Hz, they support 59,94. This is a problem with computers and projectors as they natively are 60Hz, as such make sure you use 60p mixers, they exist and are not necessarily more expensive. 4-Frame locking or at the very least genlocking becomes very important as slight timing differences will lead to tearing in your blends, no converters to date include frame locking so making sure you are locked before getting in make sure only the converters could add slight delays, in my experience they don't. 5-Time your signal, many people assume HDSDI is digital and do not need timing but it is a wrong assumption, often top or left raster lines do not appear, most of the time a simple auto-setup or auto-centering depending on how it's called is required on the projector, if it doesn't solve the issue it is a sure sign you are at the very limit of your transport, lower you resolution, go in i or use lower refresh rate. If you use live inputs (cameras) DO NOT use any converters that include scalers (DAC70 and the like), you will delay your signal unevenly accross unit and have tears in your blend, huge delay in IMAG. Use the dumbest signal converters, as soon as you process you delay, as soon as you delay you have issues. That being said, HDSDI is the way to go for cheap and long transport, it is solid and will let you use video gear rather than multiformat mixers and when 12G arrives we will be very happy we went that route.
  18. mitreklov Sure, I basically use veranoe FFMPEG for windows. Then I write batch files in windows to encode to HAP, I make sure the size is divisible by 4 and pad accordingly, I make sure audio is discarded or rendered to a separate file if appropriate, I also use 8 chunks since I have an 8 core (16 thread) processor, I append -WO to the filename before the extension and wrap it in a .mov container. I then use the registry to attach the batch file to the right click menu of the explorer. When I subsequently right click a file I am offered the option to "Convert for Watchout" (the name of my script) which opens a command windows showing the progress and stats of the encode as it is encoding, the resulting file sits beside the other one in the folder with a name like "final file-WO.mov". I can deal with up to 15 simultaneous files (8cores/16 thread). Super easy and very powerful, here is a link to help you attach the batch file to the right click menu: http://fluorware.tumblr.com/post/12786344562/integrate-ffmpeg-in-right-click-menu-to-convert I am not beside my stations right now but I guess I can post the batch file content when I will be able to copy it so we can all make it better and end up with a superb encoder for Watchout. I could also post an installer but I am not sure how the license works for ffmpeg and I don't want to get in trouble.
  19. Hello Mindopera, I use both system extensively amongst others, I have been using Watchout since version 2 and Pandora's box since version 4. I build workstations and solutions using both system. I mapped planes, buildings, hard sets and made ultra large projection for the past 20years using both system, well, Pandora's Box got in the mix the last 5 years actually. I program Coolux Widget Designer also and will get into Watchnet as soon as my schedule gets less crazy. In short: Watchout is a real-time interactive compositing software, think after effect in realtime. It was conceived and evolved with a video workflow in mind. It does 444 and uses various compositing technique which makes it far more advanced than Pandora's box as far as image quality goes, on the other hand it used to be slower and far less responsive than PB, that changed with version6, PB still has the edge in interactivity especially when tracking is involved but it is not as clear cut as it used to be. Watchout use the progressively complex approach, means that when opening the app everything is super simple and it will get as complex as you want it when you want it, but it starts simple. Watchout is almost all contained in the Production app, Watchnet, the dynamic image server and iOS apps are part of the ecosystem but aren't needed for normal operations. Pandora's box is a media server, think videos used as lighting devices. It was built with a lighting workflow in mind. It is very responsive, extensively programmable and quite stable and versatile, in my opinion way more versatile than Watchout. It used to be the only package out of both to do 3D mapping. However it is at most 422 therefore keying and blend effects are rough, display aliaising and overall lack the finish watchout has. Also it is a layer based license, so you will have to choose how many video layers you will need when buying the product, a faster machine does NOT translate into more layers. It is either non-linear or very linear, basically you either program with a lighting console or with the included timeline tools which are very limited because of the license method. So for example if you have a sequence using layer 1 and 2, your other sequence cannot use these layers or the content won't be shown if present at the same time, greatly limiting non linear shows using the provided tools. Compositing works in a very weird way, you have access to blend effects for example but it can resize other layers, or obfuscate some, it will treat all layers under the effect and not only those you wish. No folder tracks, no groups, just basically the most advanced playback machine there is, not compositing, even though it does a few compositing tricks. Pandora's Box uses the versatile approach which means that every options are there and are in your face, nothing is really hidden, it makes the software quite hard to learn at first but it gets quite powerful as soon as you get it, you have to make it simpler on purpose but the Widget Designer makes it very easy to do so once you learned it. Pandora's Box is an ecosytem, you have the manager to manage servers, players, medias and timelines, the warper to warp content, Widget Designer to program interactivity or user interfaces, an app to monitor and start servers and players, and a floating menu to access various options like resolutions and others. That said the biggest difference in the end as a user between both platform is service. Watchout has outstanding service, forums are monitored and people will easily get help here. When communicating with the people at Dataton they receive criticism and suggestion and consider them genuinely. It used to be different back in version 2 with their awful email forums but it changed a lot and now are an example of how to do stuff and consider your customers. Coolux on the other hand are very proud and easily offended. Their distributor here suggested I write to them and exposes the problems I had with the solution initially so I could get help on how to do stuff or at least know what's up. I received an awful letter of complaint where my distributor was being asked to talk to me because how dare I question their product and say it's not optimal. seriously, I am not joking, I was treated like a child by overproud support and have been reprimanded. After that I still kept using their product and even went as far as going to Germany to receive private teaching with my colleague for 4 days. I had a great time and they were very nice and helpful but my initial contact with them was just plain awful. After that visit we had to call support because of some serious issues where their warper kept loosing and corrupting our warp files but they don't work past 17:00 in Germany so screw us. When we finally got to them they told us completely unhelpful stuff and were basically of no help. Now that they have been bought by Christie things are just... not so alive, they released version 5.9 and version6 is told to be a fantastic upgrade went it will come but other than a patch and rumors things don't move much. If you need more info, PM me I will be glad to provide assistance.
  20. ffmpeg for the win, I just love this package, so many possibilities and you can then attach your scripts to the right click menu in windows to convert in place with no config or GUI.
  21. Thanks JFK, I knew about this however but I was hoping trough the GUI, a toggle switch or menu option.
  22. Superb answers, thanks much guys, will look into it!
  23. Good day, I have been working much with Watchout6 and I love it, what a fantastic upgrade however when you use a product a lot you tend to wish for a few things, here are mine: Virtual displays: -Warp, seriously warping the virtual display is at the very top of my wishlist. I would use the warp at the output to correct the projection (geometry, linearity, blend, basically get a perfect grid on the surface) and then use a virtual display to Warp and correct the content itself, whatever content I send to the virtual display, I could even have different warp settings and crossfade between them. I would also let us warp intelligently after camera placement when working in 3D, rather then correcting a camera we would correct the texture itself. -Nesting seems to cause issues also and I do use it a lot. For example I will have a virtual display as the target of all my "PiP" so that if I move/fade the PiP I don't have to move/fade all the content and plan the move. I then place this VD in another VD that covers all my surface so I can fade the whole show for example or create a preview/program workflow in live update mode. Basically nesting lower performance and playback becomes less predictable, especially more than two nest. Warping: -Please give us an on-surface indicator we can toggle on or off when we select point so we can see where in the real world that point is located. Live update -Playback stops when adding medias in a live update workflow, I understand it will affect performance but it would be nice to still be able to update without playback stopping, to have some room. -We need to have an indicator on live update, in the screen list for example that clearly indicates which computers are currently updating and where they are in the process. This is a big issue when working in 3D has we have no way of knowing if the display is busy updating or if it crashed/hung. Watchout logo: -I would be nice to update without seeing the logo or progress bars on the displays, bonus if we could have a custom image/video loop when updating. I understand the whole branding issue but all it achieves is showing everyone which system crashed during their shows, client, spectators, everyone is now aware Watchout is the problem even if it's not. Because let's not fool ourselves, this is the only moment your logo is reaching someone not using the software. I bought it, no need to sell me the package, so showing me the logo when I work is pointless, the only other time an update/startup happens is during the rehearsals and during the event when things go wrong, not really a winner way to present your brand. Maybe during rehearsals when changes are requested you then reach a few people in the room, producers, graphic artist and techs that could be unaware of your existence but that's it. Thanks for your time reading this and thanks Dataton for a great product, hope this make sense and will be supported by the community.
  24. Hi everyone, I stumbled upon issues using HAP I wanted to share, System: HAP 12 Watchout 6.1.2 storage bandwith: 2.5GBs VRAM: 16GB CPU: 8cores 3.1GHz I noticed two limits using HAP: 11Megapixel and/or 500Mbps per stream My system is able to concurently play 7x 10240x1080 with no issue, barely above 11 megapixel The same system has serious stutter with 1x 5400x2160, 11.6 megapixel If I take the same movie and squeeze it to 5400x1900, 10.2 megapixel, it plays fine Same goes for HAP files with more than 500Mbps bitrate, exact same result; barely under is fine, barely above is enough to cause issues. The problem is I haven't found an efficient way to deal how to control the bitrate when encoding HAP, the only workaround seem to resize prior to the encode and wish it will be enough to reduce the bitrate. For example, another 5800x2160 movie was unplayable, squeezed to 5400x1900 it was still unplayable, to obtain the correct bitrate I had to resize to 5800x1080 prior to the encode. Hope this helps those with HAP issues!
  25. I know we are in 2016 and the thread is from 2015 but I am having the same problem with 4518X1920 files. They play in quicktime player but not in watchout. I have 6.0.2. I noticed 6.1 is out but as I am currently on a show I am not sure I want to update however if the fix for hap size is in 6.1 I will gladly install it, what should I do?
×
×
  • Create New...