Recherche avancée

Sur d’autres sites (3307)

• Convert H.264 Annex B to MPEG-TS

  24 octobre 2019, par Lane

  SO...

  I have RAW H.264 video data captured via RTSP in a local file and I am attempting to playback the video in a Java FX application. In order to do this, I need to use Http Live Streaming.

  I have successfully prototyped a Java FX architecture that can play a video via HLS with a local server using a local folder containing a .m3u8 (HLS index) file and collection of .ts (MPEG-TS) files. The last piece for me is to replace the .ts files with .264 / .h264 files and in the local server, perform the conversion / wrapping of the H.264 Annex B data into MPEG-TS.

  I am having trouble figuring out what is required to get H.264 Annex B into MPEG-TS. I have found the following information...

  "Annex B is commonly used in live and streaming formats such as
  transport streams..."

  szatmary.org/blog/25

  "Annex B of of the document specifies one such format, which wraps NAL
  units in a format resembling a traditional MPEG video elementary
  stream, thus making it suitable for use with containers like MPEG
  PS/TS unable to provide the required framing..."

  wiki.multimedia.cx/ ?title=H.264

  "Java FX supports a number of different media types. A media type is
  considered to be the combination of a container format and one or more
  encodings. In some cases the container format might simply be an
  elementary stream containing the encoded data."

  docs.oracle.com/javafx/2/api/javafx/scene/media/package-summary.html

  "Use the CODECS attribute of the EXT-X-STREAM-INF tag. When this
  attribute is present, it must include all codecs and profiles required
  to play back the stream..."

  developer.apple.com/library/ios/documentation/networkinginternet/conceptual/streamingmediaguide/FrequentlyAskedQuestions/FrequentlyAskedQuestions.html

  It seems like I am missing something simple around Elementary and Transport Streams. I have used ffmpeg to convert my H.264 file into a TS file and try to understand the differences. I have an idea of the approximate format differences, but I am still lacking on the details to do it. Does anyone have a link showcasing this or know something simple about how to serve H.264 Annex B data over MPEG-TS ?

  I am not looking to use a tool, I need to have a custom file format locally where I parse out the H.264 Annex B data and perform the format change in memory, on the fly. I know of a way to use ffmpeg with pipes to accomplish this, but I do not want to have any dependencies and performance is important.

• When adding a new module to nginx, an error occurred in the configuration assembly

  16 octobre 2019, par Ambasador

  On Centos 6, I am rebuilding nginx to add the module "nginx-rtmp-module-master"

  ./configure --prefix=/etc/nginx --sbin-path=/usr/sbin/nginx
  
  --conf-path=/etc/nginx/nginx.conf
  
  --error-log-path=/var/log/nginx/error.log
  
  --http-log-path=/var/log/nginx/access.log --pid-path=/var/run/nginx.pid
  
  --lock-path=/var/run/nginx.lock
  
  --http-client-body-temp-path=/var/cache/nginx/client_temp
  
  --http-proxy-temp-path=/var/cache/nginx/proxy_temp
  
  --http-fastcgi-temp-path=/var/cache/nginx/fastcgi_temp
  
  --http-uwsgi-temp-path=/var/cache/nginx/uwsgi_temp
  
  --http-scgi-temp-path=/var/cache/nginx/scgi_temp --user=nginx
  
  --group=nginx
  
  --with-openssl=/builddir/build/BUILD/bx-nginx-1.16.1/openssl-1.1.1c
  
  --with-openssl-opt=enable-tls1_3 --with-http_ssl_module
  
  --with-http_realip_module --with-http_addition_module
  
  --with-http_sub_module --with-http_dav_module --with-http_flv_module
  
  --with-http_mp4_module --with-http_gunzip_module
  
  --with-http_gzip_static_module --with-http_random_index_module
  
  --with-http_secure_link_module --with-http_stub_status_module
  
  --with-http_auth_request_module --with-http_v2_module --with-mail
  
  --with-mail_ssl_module --with-file-aio --with-ipv6
  
  --add-module=../nginx-rtmp-module-master

  After the configuration is completed in the console, the following :

  ....
  
  configuring additional modules
  
  adding module in ../nginx-rtmp-module-master
  
  + ngx_rtmp_module was configured
  
  checking for PCRE library ... found
  
  checking for PCRE JIT support ... not found
  
  checking for zlib library ... found
  
  creating objs/Makefile
  
  
  
  Configuration summary
  
  + using system PCRE library
  
  + using OpenSSL library:
  
  /builddir/build/BUILD/bx-nginx-1.16.1/openssl-1.1.1c
  
  + using system zlib library
  
  
  
  nginx path prefix: "/etc/nginx"
  
  nginx binary file: "/usr/sbin/nginx"
  
  nginx modules path: "/etc/nginx/modules"
  
  nginx configuration prefix: "/etc/nginx"
  
  nginx configuration file: "/etc/nginx/nginx.conf"
  
  nginx pid file: "/var/run/nginx.pid"
  
  nginx error log file: "/var/log/nginx/error.log"
  
  nginx http access log file: "/var/log/nginx/access.log"
  
  nginx http client request body temporary files:
  
  "/var/cache/nginx/client_temp"
  
  nginx http proxy temporary files: "/var/cache/nginx/proxy_temp"
  
  nginx http fastcgi temporary files: "/var/cache/nginx/fastcgi_temp"
  
  nginx http uwsgi temporary files: "/var/cache/nginx/uwsgi_temp"
  
  nginx http scgi temporary files: "/var/cache/nginx/scgi_temp"
  
  
  
  ./configure: warning: the "--with-ipv6" option is deprecated

  After trying to build using the make command, I get an error :

  [root@216501 nginx-1.16.1]# make
  
  make -f objs/Makefile
  
  make[1]: Entering directory `/root/nginx-1.16.1'
  
  cd /builddir/build/BUILD/bx-nginx-1.16.1/openssl-1.1.1c \
  
  && if [ -f Makefile ]; then make clean; fi \
  
  && ./config
  
  --prefix=/builddir/build/BUILD/bx-nginx-1.16.1/openssl-1.1.1c/.openssl
  
  no-shared no-threads enable-tls1_3 \
  
  && make \
  
  && make install_sw LIBDIR=lib
  
  /bin/sh: line 0: cd:
  
  /builddir/build/BUILD/bx-nginx-1.16.1/openssl-1.1.1c: No such file or
  
  directory
  
  make[1]: ***
  
  [/builddir/build/BUILD/bx-nginx-1.16.1/openssl-1.1.1c/.openssl/include/openssl/ssl.h]
  
  Error 1
  
  make[1]: Leaving directory `/root/nginx-1.16.1'
  
  make: *** [build] Error 2

  How to fix the error to correctly install the module I need ?

• ClickOnce Deployment looking for manifest signature on an nuget sourced .exe (FFMPEG #) as if it is a .csproj output. Deployment fails

  9 octobre 2019, par M_Ryce

  I have a C# forms app which utilizes the nuget package "FFMPEG Sharp" (Nuget Github) to generate video from a sequence of images.

  Unlike most nuget packages which simply pull in a .dll, installing FFMPEG Sharp places an "FFMPEG" folder into the .csproj root directory, in addition to bringing the appropriate .dll into "packages"

  Inside this folder are a few FFMPEG artifacts and a /bin folder containing FFMPEG executables. According to the project’s Github readme, this /bin directory needs to be specified in the app.config.

  From Github Readme example :

  <appsettings>
  
    <add key="ffmpegRoot" value="C:\ffmpeg\bin\"></add>
  
  </appsettings>`

  Adjusting the above to work in alignment with the default location Nuget placed the dependency artifacts :

  <appsettings>
  
    <add key="ffmpegRoot" value="..\..\FFMPEG\bin"></add>
  
  </appsettings>`

  Everything related to this dev effort has been smooth sailing, until I tried to utilize the existing Clickonce deployment for the app. The FFMPEG folder in my .csproj root wasn’t making it to the build output and therefore the application’s call to the FFMPEG .exe was throwing a null reference error. Understandable result, given that I had not set up any method of ensuring the FFMPEG artifacts made it to the build output with the same folder structure as existed on my local dev box.

  To counter this, I set a POST-build command to XCOPY....

  XCOPY "$(SolutionDir)MyApp\FFMPEG" "$(TargetDir)FFMPEG" /S /Y /I

  ...the nuget-provisioned FFMPEG artifacts into the build output root, and adjusted the config setting accordingly (see below)

  <appsettings>
  
    <add key="ffmpegRoot" value=".\FFMPEG\bin"></add>
  
  </appsettings>`

  This worked like a dream when building/running locally. The XCOPY succeeded in placing FFMPEG folder contents into the compiled solution’s Debug/Release bin and the updated config referenced them. No errors.

  Attempting to deploy with the .NET ClickOnce tool has created a rather befuddling error though.

  (Apologies for formatting ugliness below. I tried but didn’t succeed. The important parts are in bold)

  ERROR SUMMARY
  Below is a summary of the errors, details of these errors are listed later in the log.
  Activation of https://MySite/MyApp/Install/MyApp.application resulted in exception. Following failure messages were detected :
  + Downloading https://MySite/MyApp/Install/Application Files/MyApp/FFMPEG/bin/x86/ffmpeg.exe.deploy did not succeed.
  + The remote server returned an error : (404) Not Found.
  COMPONENT STORE TRANSACTION FAILURE SUMMARY
  No transaction error was detected.
  WARNINGS
  The manifest for this application does not have a signature. Signature validation will be ignored.
  * The manifest for this application does not have a signature. Signature validation will be ignored.
  OPERATION PROGRESS STATUS
  * [10/8/2019 2:03:37 PM] : Activation of https://MySite/MyApp/Install/MyApp.application has started.
  * [10/8/2019 2:03:37 PM] : Processing of deployment manifest has successfully completed.
  * [10/8/2019 2:03:37 PM] : Installation of the application has started.
  * [10/8/2019 2:03:37 PM] : Processing of application manifest has successfully completed.
  * [10/8/2019 2:03:40 PM] : Found compatible runtime version 4.0.30319.
  * [10/8/2019 2:03:40 PM] : Request of trust and detection of platform is complete.
  ERROR DETAILS
  Following errors were detected during this operation.
  * [10/8/2019 2:03:40 PM] System.Deployment.Application.DeploymentDownloadException (Unknown subtype)
  - Downloading https://MySite/MyApp/Install/Application Files/MyApp/FFMPEG/bin/x86/ffmpeg.exe.deploy did not succeed.*

  ...

  My interpretation of this is that the ClickOnce deployment is treating the Nuget-sourced .exe’s as if they are compiled code from this very project, and checking for a signed manifest.

  This ClickOnce deployment was not set up by me, and had not needed to account for such external artifacts existing in the output previously. I do not believe turning off signed assemblies is an option for me, for security reasons.

  Is there a way to make ClickOnce deployments ignore a specific .exe when checking for signed manifests ? I think the "correct" intended usage is for FFMPEG to be pre-installed on the machine as a stand-alone application, but This is not an option for me at this time. I will need FFMPEG to be brought in by the ClickOnce.