Jump to content

keitht

Member
  • Posts

    70
  • Joined

  • Last visited

Everything posted by keitht

  1. What version of Watchout are you using? And you have a NVidia card in that production PC, correct? And the videos are MP4's? I had this same problem a while back. This problem was fixed. It got created with a certain version of NVidia drivers. I cannot remember exactly which version had the problem and which version fixed it. But I know for sure if it's the same problem I had, upgrading to WO 6.7.x will fix. -KT
  2. In each layer there is option for Normal, Stand by, or both. This is exactly the reason they added the BOTH option. So the layer with your virtual display on it can work for both normal and stand by. -kt
  3. I am using Jokyo in AME and at times directly out of AE Render. Works well. Disguise plugin also worked well, but Jokyo has more setting options and more reliable installation.
  4. Hello. I am the one user Jim quoted above to have “solved.” I did not just add an additional NIC. I added 10G NICs to both the production and the servers (and of course 10G switches). Not exactly the cheapest solution, but it did seem to solve. I had previously spent months and months troubleshooting and work-arounds. I remain sure that there are some settings, somewhere, in either the prod or server NIC that would solve, but I was unable to track it down. Before I took the 10G leap, my workaround was to use the 2nd NIC in both to create a 2nd network in a different range with sharing enabled. That worked for transfer speed, but sometimes causes communications problems as WO still cannot give us the ability to manually choose the NIC for use in communications. I hope this helps. -kt
  5. Hi Benoit, At this stage I use the Disguise-built AME plugin. I have used everything in the past, and had multiple topics of conversation with both the HAP developers as well as FFMPEG (which give very poor results). Hap does a fine job for footage. But anything that is graphically created with any sort of gradients has banding, often really bad. I have tested every which way I can think of for better results. Strange thing is generally for gradients, you get better results with HAP than you do with HAPQ. https://github.com/Vidvox/hap-qt-codec/issues/16
  6. I have made this request directly to support, might as well add it here publicly. This needs to be the highest priority need. HAP does NOT look good.
  7. Not sure how long this has been the case, but for a while now, you can type numbers only, leaving out the ":" and watchout will insert the colons. So, <ctrl>-J | 0510.00 - will jump you to 5:10.00
  8. I would vote for fixing this sooner vs. later. It is very bothersome and was better when it worked the other way (jumping to the proper frame or last frame of video).
  9. Oh I see Matt already linked to the same link. Sorry for the repeat!
  10. Hi Richard, Although I haven't tried this in a few years, last time I needed such a feature - I was able to do it in Photoshop with Native Define Variable features. Here is a nice tutorial on how to accomplish. https://helpx.adobe.com/photoshop/using/creating-data-driven-graphics.html
  11. Hi all, Reviving this old thread to let you all know that for a limited time we are offering Perpetual (non-subscription) licenses for purchase. There is also a free trial available for download. https://www.corpimaging.com/piw
  12. I would NOT recommend using FFMPEG to make HAP files. The image quality is not as good as other methods. If you can install AME 12.0.1 and the normal HAP QT plugin, use AME Here is a link to alpha versions for AME plugin for versions greater than 12.0.1: https://github.com/disguise-one/hap-encoder-adobe-cc/releases
  13. I have had good success making 4K MPG2 in FF. HAP is great - and the performance is unworldly, but sometimes I need either smaller files sizes or better image quality (yes, I find MPG2 quality better than HAP for many types of media). I find MPG2 performance vs quality far superior to MPG4. Here are my FF settings: -c:v mpeg2video -g 15 -bf 0 -pix_fmt yuv422p -b:v 80000k -minrate 80000k -maxrate 80000k -bufsize 80000k
  14. All very interesting. I usually tend to batch/multi-processor render from AE to uncompressed first anyways, so - for me - the AME plugin is a fine (even preferred) solution. I hope to test the Disguise Plugin further this coming week.
  15. Good info WatchDog. I had not tried Render Garden, because it uses FF. Gonna have to look into it and see if they are using different switches than I am or a different build that uses different encoding. I was able to try the Disguise plugin. I have bee on site, so remoting in to office machine so as not to mess anything up on site. Therefore although I was able to test the process, I am unable to adequately rate the quality/performance of the result yet. However - I WAS able to get it installed in CC 2019. And I DID have AE (que to AME) make a HAP file - then reimported into AE. Seems to work!! Also, I have contributed a few messages to their development Git hub and: 1. They are very active, this is going to get better, fast I think. 2. They also see the difference between quality of FFMEG... but also the same big speed improvement you mentioned. I would love to see if you can show a difference in quality running the same footage through FF direct and RenderGarden. Lastly in regards to your playback issues... they are not an issue. Although QT and VLC can read the HAP files, they do not use the GPU for decoding, therefore cannot playback in real-time (depending on the size of the media of course). What trouble did you have getting the Disguise plugin to work? Perhaps what I did was different. -Keith
  16. Hey JJ. Sorry - for some reason I was didn’t get a notification on the reply to this thread - I am just seeing it now. It has been a year or so since I have done real world testing on this. I am not sure if anything has changed. My finding were that encoding to HAP with FFMPEG resulted in worse quality than if encoded with AME. The differences are in banding, color depth and artifacts (blocky compression). It was by no means unacceptable quality, but definitely worse for computer generated content. I am not sure I understand what you are saying. Playback performance is fine. Of course playback performance in QT player or AE is not real-time. Quality in WO seemed to match quality in AE. Meaning I notice a difference when playing the 2 files side by side in WO, and when I compared Frame-by-frame, zooming in in AE the exact differences are easier to pinpoint, but I think are the same I see in WO. For this reason, I have stayed on AME 12.0.1 and have been making HAPs there will good results. FYI - AfterCodecs just uses FFMPEG and others have noticed the difference too: Here is my original report and confirmation that different encoding software WILL yield different results: https://github.com/Vidvox/hap-qt-codec/issues/39 I am sure we are all tracing what is happening with HAP and Adobe products very closely these days. Here are a few relevant links I have been tracking. Many I have not yet tested - so maybe all could chime in there findings and other possible solutions until this mess settles down: The D3 guys have written a plugin for Premiere (that should work in AME). I haven’t personally tested yet. https://github.com/disguise-one/hap-encoder-adobe-cc/releases Apparently Adobe is at least listening. I will try to test next week. The comments below do not sound as though it is working, but this thread claims that the newest AE will at least be able to use HAP footage. https://adobe-video.uservoice.com/forums/911311-after-effects/suggestions/33853372-support-the-hap-codec What about using HAP AVI (rather than QT). Will this work in WO? I am guessing not, but perhaps this is the area Dataton should be moving to?? https://support.troikatronix.com/support/solutions/articles/13000044970-create-windows-native-hap-avi-video-files http://renderheads.com/product/hap-for-directshow/ Does anyone have any newer/better information to add here? Keith Tromer Corporate Imaging
  17. I know this has been a while... but we have finally had the time to make a release out of this product. Photoshop Import for Watchout is now available for purchase. Automatically import all Photoshop layers into Watchout. Trimmed, in position, with anchors centered! It even supports blend modes and making each PSD into a composition. Have a look at the video tutorial here: http://www.corpimaging.com/piw/ Thanks for all the positive feedback on this over the last few years. Keith Tromer
  18. I dont understand? We are talking about HAP encoding here. Not ProRes. The ProRes in this case is the source and look good. -kt
  19. That's an interesting thought. I'll test to be sure... but since the same input file gets excellent results with FFMPEG for 4K MPG2 I would say that decoding is not the issue. I'll run the test anyways. -kt
  20. No, I have not tried coming from image sequences (that's what you mean, right?) - but that should not make a difference on encode quality I would think. In any case, my situation makes it not possible for me to input sequences anyways. FYI - What I have learned from the HAP forum is that AME (and AE etc...) use the quicktime codec written by hap to encode. FFMPEG does NOT... and wrote their own encoder. I, for one, am not happy with the FFMPEG encoding. Anyone else? -kt
  21. I'm trying to understand why I am getting substantially worse results while encoding to HAP using FFMPEG vs. Adobe Media Encoder. My problem is I need to do Chuncks encoding (which cannot be set using AME) but the results from FFMPEG are not up to quality. See results here: https://www.dropbox.com/s/4fakivsytefl60c/HAP%20Test.tif?dl=0 Has anyone else seen these issues? Here is my FF command line: ffmpeg.exe -i "H:\_Render\test.mov" -vcodec hap -format hap_q "H:\_Render\output.mov" AME is set to HAP Q, Quality=100, Render at Max Depth (not that any of those settings makes a difference if my understanding is correct). Any ideas on how I can get the matching quality from FFMPEG or how ELSE I can do HAP encoding with Chunks ON WINDOWS? -kt
  22. Hmmm. The only thing you mention that I have not personally tried is Hap v12 (I think I am using v10). Erik - have you tested HAP renders with v12 encoding? Keith
  23. As Erik said above, all files in same format - including the preview file. I was having some issues with the preview file being H264 (seems like a logical thing to do), but that was screwing up the presplits sometime. I think there may also have been an issue that I was using a utility I wrote to generate the PreSplit via making a clipboard to paste in. The original source of the clipboard was a presplit from a previous version, and that caused a problem. Try creating a brand new pre-split - ensure all files are same codec (Q or notQ) - with no preview file. -Keith
  24. I can confirm the issues I was having with HAP Pre-Splits above have been solved in 6.1+. Keith
×
×
  • Create New...