Best Format For Uploading HDR10 Content To Youtube

I would appreciate any suggestions for what is the best output format to use when creating 10- bit (or 12 bit), HDR 4:2:2, or 4:4:4 content for Youtube?

At the moment, I'm waiting to see what happens to a short 4K QuickTime DNxHR HQX 10-bit file I uploaded this morning. It's only 24 seconds long (an experiment), but after almost 2 hours since it uploaded , it's still saying "HD Processing HD version." It's been in the processing stage much longer than I would have expected, so I'm wondering if there is a problem.

I followed the instructions about HDR uploading from Youtube, which indicated that this codec should be working.

I would appreciate any suggestions for what is the best output format to use when creating 10- bit (or 12 bit), HDR 4:2:2, or 4:4:4 content for Youtube?

At the moment, I'm waiting to see what happens to a short 4K QuickTime DNxHR HQX 10-bit file I uploaded this morning. It's only 24 seconds long (an experiment), but after almost 2 hours since it uploaded , it's still saying "HD Processing HD version." It's been in the processing stage much longer than I would have expected, so I'm wondering if there is a problem.

I followed the instructions about HDR uploading from Youtube, which indicated that this codec should be working.

That’s nothing unusual. Whether uploading HEVC or ProRes 422, YT can take forever to finish processing. A fifteen minute video of mine once took 24 hours! And it’s not just HDR videos either. There’s a hack on the German website Slashcam to get YT to finish processing quickly but unfortunately it doesn’t work with HDR videos.
https://www.slashcam.de/artikel/Tips/Yo ... ler--.html

I would appreciate any suggestions for what is the best output format to use when creating 10- bit (or 12 bit), HDR 4:2:2, or 4:4:4 content for Youtube?

At the moment, I'm waiting to see what happens to a short 4K QuickTime DNxHR HQX 10-bit file I uploaded this morning. It's only 24 seconds long (an experiment), but after almost 2 hours since it uploaded , it's still saying "HD Processing HD version." It's been in the processing stage much longer than I would have expected, so I'm wondering if there is a problem.

I followed the instructions about HDR uploading from Youtube, which indicated that this codec should be working.

Think how many people upload files daily to YT.
Take into account that YT has to convert them to most demanding codecs out there (h264/5/VP9). They also need to create many profiles for smooth steaming and also in different codecs for different browsers (also SDR for HDR sources!). This is many files for your single source. Even with scaling to many machines it's still very demanding task, which uses huge amount of energy

Yep,
Definitely sounds like the new norm! No problem, I've got nothing but patience, now that I know.

I would appreciate any suggestions for what is the best output format to use when creating 10- bit (or 12 bit), HDR 4:2:2, or 4:4:4 content for Youtube?

At the moment, I'm waiting to see what happens to a short 4K QuickTime DNxHR HQX 10-bit file I uploaded this morning. It's only 24 seconds long (an experiment), but after almost 2 hours since it uploaded , it's still saying "HD Processing HD version." It's been in the processing stage much longer than I would have expected, so I'm wondering if there is a problem.

I followed the instructions about HDR uploading from Youtube, which indicated that this codec should be working.

Think how many people upload files daily to YT.
Take into account that YT has to convert them to most demanding codecs out there (h264/5/VP9). They also need to create many profiles for smooth steaming and also in different codecs for different browsers (also SDR for HDR sources!). This is many files for your single source. Even with scaling to many machines it's still very demanding task, which uses huge amount of energy

The fact that using the hack can reduce processing time from hours to just a couple of minutes indicates that there is a different reason. In fact, YT acknowledged it was a known issue but has failed to fix it.

For me hack is simple.
When you upload file to YT it lands in the global queue.
When you do "fake" editing most likely your file is triggers immediate encode, so you are "1st" in the queue.
There is no way YT will ever have enough processing power to do all encodes within minutes. Cost would be huge.
Vimeo is the same. Want to be on top of the queue pay for premium profile, so they can spin dedicated machine for your source