Jump to content

Problems when playing Video through Browsers. GPU (H.264 (AVC))) - Hardware Encoder.


Santrex

Recommended Posts

Добрый день.
Я являюсь Интегратором в Крупной Российской Телевизионной компании VGTRK.COM
На сегодняшней день мы уже имеет Emby Premiere для нашего пилотного проекта по разворачиванию Корпоративной системы на базе продукта Emby для внутренних нужд компании.
Мы уже развернули и используем несколько серверов Emby для Удаленной работы наших сотрудников и хотели бы расширить докупив новые лицензии (порядка 200+ и развитие).
Но мы столкнулись с рядом проблем, которые критически важны для масштабной интеграции данного решения. Без этого мы не сможем продолжать и запросить деньги для проекта.

Мы хотели бы услышать, как мы можем обойти данную проблему.

Основной контент “Видео” — это “Большие” форматы для Телевидения. У нас 95% это MXF файлы.
MXFEmby.thumb.png.73b69b73f7aaae666539ebb16d057ab5.png
У нас были куплены карточки Nvidia Quadro P4000 чтобы разгрузить CPU наших серверов и увеличить плотность пользователей на нем.
Все видео находятся на “Больших” файловых серверах под
Windows. Это 100 TB+. Видео за 30+ лет работы ТВ-Компании.
Мы настроили Аппаратные Энкодеры на работу с NVENC Quadro P4000 - H.264 (AVC) .

TranscodingEmby.thumb.png.c3ae3ccb0d6dc2ac8048372ae3ea1f3c.png
И мы делали тесты на базе Google Chrome (и любые браузеры на Core Chromium) и Аппаратная поддержка полностью работает. (мы смотрим графики нагрузок).
Но, когда мы попытались это сделать на
Firefox/MS EDGE/Opera во всех случаях мы потерпели поражение.
Я прикреплю пару логов с “Не удачных” воспроизведений. Мы хотели бы понять в чем проблема.
И почему только
Google Chrome может показать нам эти видео работая через GPU.

P.S. один лог с EDGE и один с FireFox. 

embyserver.txt ffmpeg-transcode-aa487ff0-b528-4ad4-9acd-cb6f8ef9e783_1.txt ffmpeg-transcode-7ada270a-0a6c-4089-a4fa-51535a5dc9c3_1.txt

hardware_detection-63738745508.txt

Edited by Santrex
Link to comment
Share on other sites

Хотел так же обратить внимания на баг в Энкодаре при попытках Воспроизвести файлы формата .Mov
Они обходят GPU с ошибкой в логе и переходят на Software конвертор.
Выдержка из лога:
 

18:26:25.223 [scale_cuda@f3 @ 000001be5be97e40] Unsupported input format: yuv444p16le
18:26:25.223 [scale_cuda@f3 @ 000001be5be97e40] Failed to configure output pad on scale_cuda@f3
18:26:25.263 Error reinitializing filters!
18:26:25.263 Failed to inject frame into filter network: Function not implemented
18:26:25.263 Error while processing the decoded data for stream #0:0
18:26:25.271 [libmp3lame @ 000001be5be91800] 3 frames left in the queue on closing
18:26:25.309 Conversion failed!


Конфигурация сервера и GPU аналогично посту: 

 

ffmpeg-transcode-bac77663-8b78-4dc8-af00-d35880e7049b_1.txt

Link to comment
Share on other sites

4 hours ago, Luke said:

Hi there, did you follow our hardware acceleration setup guide?

https://support.emby.media/support/solutions/articles/44001160148-hardware-acceleration-overview

Oh sure. We went through all your guides at once. And as I pointed out, this works in a number of cases. But not always. We are looking for a cross-platform solution. Since the clients are different people with different OS and browsers.
MXF was able to work with NVENC only in Google Chrome. In other browsers it doesn't show anything. Black picture or eternal loading when we activated GPU Encoding.

We tried to download the FFMPEG from the official site. And substitute for yours. But that doesn't work either.

Link to comment
Share on other sites

The video which is failing is of a very special format (yuv422p10) which the P4000 is unable to handle. I can handle yuv420p10 and yuv422 but not yuv422p10.

Link to comment
Share on other sites

8 hours ago, softworkz said:

The video which is failing is of a very special format (yuv422p10) which the P4000 is unable to handle. I can handle yuv420p10 and yuv422 but not yuv422p10.

Okay. It's about .mov
Now it is clear that neither is so. And why isn't it GPU encoded.

I still have a question about .MXF. Judging by the log, it is yuv422p. And it works under the supervision of the Emby Theather Client and through Google Chrome. I have attached Sreenshot.
But when I try to view it from Firefox / MS EDGE / Opera, I just don't get anything. There is nothing ... black screen at the exit .... I wonder why it works in some clients, while others cannot show the picture?
I am trying to find solutions for this.
EDGE - Bad
BadEdge.thumb.png.c08c0dc6ff809f6f5677ed316c4cf340.png
FireFofx - Bad
BlackWindowFF.thumb.png.e178a67237691239b5744f6551e6adba.png

Good for Google Chrome
GoodChrome.thumb.png.0e5b793e90eedd242b08b01d3ff1c6b7.png
We have many resources and testing capabilities. And we have already been doing this for several weeks. And until they came to success. 
SEE LOGS!

[bad-Edge]-ffmpeg-transcode-c4399e63-4b62-4e9d-aec4-20ff6be32f7e_1.txt [bad-FireFox]-ffmpeg-transcode-afc4674e-0621-4258-89b4-e261d6e4c584_1.txt [good-Chrome]-ffmpeg-transcode-19ba597b-5827-4024-88b8-1e8eea312796_1.txt

Link to comment
Share on other sites

 

I decided to look through the console built into FireFox. And I immediately found an error when trying to play.
image.thumb.png.a129a328470c0943343cd38ccafe1f8f.png

Не удалось декодировать медиаресурс blob:http://rtrecomedia2.res.vgtrk:8096/0b429cee-a383-4ba6-bcee-6a771fe2082f. index.html
Не удалось декодировать медиаресурс blob:http://rtrecomedia2.res.vgtrk:8096/0b429cee-a383-4ba6-bcee-6a771fe2082f. index.html
Не удалось декодировать медиаресурс blob:http://rtrecomedia2.res.vgtrk:8096/0b429cee-a383-4ba6-bcee-6a771fe2082f, ошибка: Error Code: NS_ERROR_DOM_MEDIA_FATAL_ERR (0x806e0005)
Details: auto __cdecl mozilla::SupportChecker::AddMediaFormatChecker(const mozilla::TrackInfo &)::(anonymous class)::operator()(void) const: Decoder may not have the capability to handle the requested video format with YUV444 chroma subsampling.

 

Link to comment
Share on other sites

1 minute ago, softworkz said:

I think I found the reason...please give me a while to investigate.

Thanks.

Oh sure. Thanks! Will wait...

Link to comment
Share on other sites

8 minutes ago, softworkz said:

Would you be able to provide a short video clip of that same format?

I will try to request to "cut" a piece of video with the logs that I sent. And put it on the cloud
 

  • Like 1
Link to comment
Share on other sites

I already have a fix but it is still unverified.

As an alternative, if you would be willing to try a beta version, you could also wait for the next beta and try that.

Link to comment
Share on other sites

1 hour ago, softworkz said:

I already have a fix but it is still unverified.

As an alternative, if you would be willing to try a beta version, you could also wait for the next beta and try that.

I'll wait for the Beta update. But would you like a time frame? We are using Emby in Production and need GPU tests until more people come.

Link to comment
Share on other sites

17 hours ago, softworkz said:

I already have a fix but it is still unverified.

As an alternative, if you would be willing to try a beta version, you could also wait for the next beta and try that.

did you download it?

Link to comment
Share on other sites

gdeyoung

I can confirm I have the same issue.  Will not transcode my 4k x265 content played back in browser.  If I play the same content in emby theatre on win10 it transcodes just fine.

Link to comment
Share on other sites

7 minutes ago, gdeyoung said:

I can confirm I have the same issue.  Will not transcode my 4k x265 content played back in browser.  If I play the same content in emby theatre on win10 it transcodes just fine.

This is neither about 4k nor about H.265. Please create a new topic and include log files.

Thanks.

Edited by softworkz
Link to comment
Share on other sites

9 hours ago, Santrex said:

There is success on our issue?

Yes, it's all fixed now:

  1. Hardware decoders will no longer be chosen for mpeg2video with profile 4:2:2 
    (none of them supports this)
    It is not longer necessary to disable the MP2 hardware decoder
    .
  2. Video color format will always be converted to YUV420 (= nv12) in hardware
    (second red arrow below)
    Encoding H.264 with YUV422 is legal, but browser support for this varies, that's why it had been working in some cases for you but not always.

image.thumb.png.dc05a5599c5f116d0afdabfe26a2d283.png

 

The fix will be included in the next beta version.

Thanks for reporting!

  • Thanks 1
Link to comment
Share on other sites

12 minutes ago, softworkz said:

Yes, it's all fixed now:

  1. Hardware decoders will no longer be chosen for mpeg2video with profile 4:2:2 
    (none of them supports this)
    It is not longer necessary to disable the MP2 hardware decoder
    .
  2. Video color format will always be converted to YUV420 (= nv12) in hardware
    (second red arrow below)
    Encoding H.264 with YUV422 is legal, but browser support for this varies, that's why it had been working in some cases for you but not always.

image.thumb.png.dc05a5599c5f116d0afdabfe26a2d283.png

 

The fix will be included in the next beta version.

Thanks for reporting!

Excellent. Thanks, we'll wait.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...