HAPQ files look great in VLC and QuickTime but look horrible in WatchOUT.

[Brian]

Hello. I am seeing an issue with HAPQ files where they look very good in VLC and QuickTime but in WatchOUT they are washed out.

Sometimes I am seeing thumbnails in WatchOUT and when I do they look fine but video placed on a timeline is washed out.

Sometimes I am not seeing any thumbnails in WatchOUT and I am getting a symbol that looks like this ">>>>>>".

I have tried two different workflows for rendering HAPQ.

First - ProRes source, Resolve edit, output to h264, use QuickTime Pro to encode to HAPQ.

Second - ProRes souce, Resolve edit, output to uncompressed yuv422 10 bit avi, use Adobe Media Encoder to encode to HAPQ.

Both pipelines have ended with the same result on multiple WatchOUT servers.

Conference requested HAPQ but they're having the same issues with the files that I am.

Any ideas? Thanks!

[daniel carino]

I've not seen any issues with HAP, HAPQ, or HAPA aside from some limitations on the final output and gradients, but that's unrelated to WO.

 
Usually for HAP I would look into how many cores you have available. I personally go about half that many as my chunk size. 
My workflow however is just directly from after effects/premiere and export as HAP from Media Encoder and no converting from other codecs if possible.
I usually use 5-6 chunks and seem to have no playback issues.

This plugin from GitHub hasn't given me any issue for Media Encoder, but now and then on ME updates I'll uninstall and reinstall it.

But I personally try and export the first export as any of the version of HAP I'm using with no converting in between

[Leonard]

Try using FFmpeg to encode HAP, HAPQ, HAP ALPHA, it always work perfectly with WATCHOUT.

https://knowledge.dataton.com/knowledge/what-tools-can-i-use-to-encode-decode-and-transcode

[Ventmedia]

I’ve been batching out a lot HapQ content from After effects, Premiere and Media encoder over the last year using Aftercodecs plugin and it’s been really solid. The only issue I’ve seen is if I attempt to replace the video files from within watchout using the browse option, it create a nasty yellowing. Bringing in video files freshly then replacing them on the timeline sorts this out.

[Brian]

On 9/8/2021 at 11:13 AM, daniel carino said:

I've not seen any issues with HAP, HAPQ, or HAPA aside from some limitations on the final output and gradients, but that's unrelated to WO.

 
Usually for HAP I would look into how many cores you have available. I personally go about half that many as my chunk size. 
My workflow however is just directly from after effects/premiere and export as HAP from Media Encoder and no converting from other codecs if possible.
I usually use 5-6 chunks and seem to have no playback issues.

This plugin from GitHub hasn't given me any issue for Media Encoder, but now and then on ME updates I'll uninstall and reinstall it.

But I personally try and export the first export as any of the version of HAP I'm using with no converting in between

I'm not new to HAP but thank you.

 

I appreciate all the replies but this is all too basic. I've been encoding/using HAP for years and this is the first time I've seen this behavior.

 

I don't use FFMPEG to encode HAP because the quality is poor. Doesn't matter what I do I can't match what AE+disguise render plug in create.

 

I refuse to touch After Codecs.

 

Still trying to figure out what happened. I re-encoded all the videos as HAP and the issue went away.

 

I've also seen this recently with a HAP non-Q file. That was on v6.2.2. Turning off hardware acceleration fixed it.

 

99% of the time, like every time except this one show HAP has been rock solid. Still trying to figure out what happened!

 

[Morgan Wong]

Maybe 10bit cause the problem?

share us some sample video,
so we can have a look on the codec/video details?

Maybe a basic video(detail) compare/check between working "encoding/using HAP for years" Hap file and "the first time I've seen this behavior" Hap file
can tell the different?