Chrome built FFMPEG avformat_open_input PROTOCOL NOT FOUND

412 views
Skip to first unread message

Michael IV

unread,
Nov 8, 2017, 12:22:03 PM11/8/17
to Chromium-dev
Hi people.
I built WebRTC repo with CHROME ffmpeg.

Here  are my args:

--args="ffmpeg_branding=\"Chrome\" rtc_initialize_ffmpeg=true  rtc_use_h264=true  proprietary_codecs=true is_debug=true target_cpu=\"x64\" symbol_level=2 use_rtti=true msvc_use_absolute_paths=true is_win_fastlink=true enable_nacl=false disable_libfuzzer=true"


Now,the thing is that I am trying to use avformat_open_input  and it always gives me "Protocol not found" error:

Here is the code
       avcodec_register_all();
       av_register_all();
       avformat_network_init();
         AVDictionary *d = NULL;
av_dict_set(&d, "protocol_whitelist","file,udp,tcp,rtp,rtsp", 0);
       int ret = avformat_open_input(&pFormatCtx, in_f_name , NULL, &d);

So  do init all the codecs and formats correctly. I also tried to leave only one of those prtocols in the
dictionary- same issue. All those protocols are supported by ffmpeg.

Do I miss some build arg to enable this stuff ? 

Thanks.



Dale Curtis

unread,
Nov 8, 2017, 1:14:10 PM11/8/17
to explo...@gmail.com, Chromium-dev
Chrome's ffmpeg does not allow any of those protocols, if you want to enable them you'll have to rebuild and reconfigure Chrome's copy of ffmpeg.

- dale

--
--
Chromium Developers mailing list: chromi...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev
---
You received this message because you are subscribed to the Google Groups "Chromium-dev" group.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-dev/643d9c2f-f6e9-485d-9c0f-4f1cb091a403%40chromium.org.

Michael IV

unread,
Nov 8, 2017, 1:16:45 PM11/8/17
to Dale Curtis, Chromium-dev
That's exactly what I need  .How do I define those features via cmd or some build script file?  

Dale Curtis

unread,
Nov 8, 2017, 1:23:45 PM11/8/17
to Michael IV, Chromium-dev
You'll have to figure out how to generate them using ffmpeg's ./configure (for all the platforms you're targeting) then run ./chromium/scripts/copy_config and ./chromium/scripts/generate_gn -- if you're lucky this will just work, but you'll then likely have a bunch of issues to fix with BUILD.gn. Good luck.

- dale

Michael IV

unread,
Nov 8, 2017, 6:30:00 PM11/8/17
to Dale Curtis, Chromium-dev
Thanks for the tip. It was a nightmare but now I got the full FFMPEG working :_)
Reply all
Reply to author
Forward
0 new messages