Recherche avancée

Sur d’autres sites (7105)

• Untiy VideoPlayer error - The byte stream type of the given URL is unsupported

  24 avril 2018, par Nika Kasradze

  I’m on Unity 2018.1.0b13 trying to play a video from a local server.
  I’ve transcoded the video myself with ffmpeg. This is the encoding of the streams (by running ffmpeg -i v1.mp4) :

  Stream #0:0(eng) : Video : h264 (Constrained Baseline) (avc1 / 0x31637661), yu v420p, 960x540, 1244 kb/s, 25 fps, 25 tbr, 12800 tbn, 50 tbc (default)

  Stream #0:1(eng) : Audio : aac (LC) (mp4a / 0x6134706D), 48000 Hz, stereo, fltp, 317 kb/s (default)

  In the folder of my v1.mp4 file I’m running http-server so that the file is available at http://127.0.0.1:8080/v1.mp4

  In unity I’m trying to play the video via this URL but I keep getting this same error, no matter what codec I try for encoding :

  WindowsVideoMedia error 0xc00d36c4 while reading http://127.0.0.1:8080/v1.mp4

  Context : MFCreateSourceReaderFromURL

  Error details : The byte stream type of the given URL is unsupported.

  Track types :

  The same video plays ok on Android so I’m guessing it’s just Media Foundation that’s messing me up, not Unity. Any suggestions on how can I make this work in Unity ?

  Thanks !

• How to get your Matomo plugin ready for GDPR

  24 avril 2018, par Matomo Core Team

  Are you developing a plugin for your self-hosted Matomo ? Have you maybe published a plugin on the Matomo Marketplace ? Then we highly recommend you read this article.

  On 25th May 2018, new privacy regulations become effective called GDPR (General Data Protection Regulation) which applies to businesses worldwide. It is also known under different wordings in other countries, for example to RGPD in French and Datenschutz-Grundverordnung, DS-GVO in German.

  If your plugin is storing any personal information or tracks or imports any data, we highly recommend you give the GDPR guide a read. You may also want to read our blog as we are releasing new content about GDPR regularly.

  In Matomo 3.5.0, we will introduce new features for GDPR and we implemented it in a way that most – but not all – plugins will support these features out of the box without having to do anything.

  Nevertheless, we recommend every plugin developer to check out our developer guide on how to make your plugin GDPR compliant to see what you need to do. A beta version of Matomo 3.5.0 is already available so you can test these new features. You can find them by logging in to your Matomo and going to “Administration => Privacy”.

  Please note that any version of Piwik will not be GDPR compliant, so it is recommended that your plugin supports the latest version of Matomo (3.5.0+).

  The post How to get your Matomo plugin ready for GDPR appeared first on Analytics Platform - Matomo.

• FFMPEG [h264_nvenc @ 0x56151389fe00] Cannot get the preset configuration : invalid version (15)

  22 avril 2018, par Netheme

  i have issue with ffmpeg as usual :D. I have FFMPEG compiled (version N-90807-g00099ef0d0) with NVIDIA support (latest CUDA and latest NV Headers) :

  ffmpeg version N-90807-g00099ef0d0 Copyright (c) 2000-2018 the FFmpeg developers
  
    built with gcc 6.3.0 (Debian 6.3.0-18+deb9u1) 20170516
  
    configuration: --enable-libnpp --enable-cuda --enable-cuvid --enable-nvenc --extra-cflags=-I/usr/local/cuda/include --extra-ldflags=-L/usr/local/cuda/lib64 --enable-gpl --enable-libx264 --disable-x86asm --enable-libx265 --enable-libfdk-aac --enable-nonfree --enable-x86asm
  
    libavutil      56. 15.100 / 56. 15.100
  
    libavcodec     58. 19.100 / 58. 19.100
  
    libavformat    58. 13.100 / 58. 13.100
  
    libavdevice    58.  4.100 / 58.  4.100
  
    libavfilter     7. 19.100 /  7. 19.100
  
    libswscale      5.  2.100 /  5.  2.100
  
    libswresample   3.  2.100 /  3.  2.100
  
    libpostproc    55.  2.100 / 55.  2.100
  
  Hyper fast Audio and Video encoder
  
  usage: ffmpeg [options] [[infile options] -i infile]... {[outfile options] outfile}...
  
  
  
  Use -h to get full help or, even better, run 'man ffmpeg'

  When I try to run basic transcoding on GPU using command :

  ffmpeg -i 'udp://@239.100.0.1:331?fifo_size=‎100000000' -map i:0x100 -g 20 -vcodec  h264_nvenc -map i:0x101 -ab 128k -ar 48k -acodec aac -f mpegts udp://@239.0.0.1:1234?overrun_nonfatal_optin=

  I got this error :

      Input #0, mpegts, from 'udp://@239.100.0.1:331?fifo_size=‎100000000':
  
    Duration: N/A, start: 106.414400, bitrate: N/A
  
    Program 1 
  
      Metadata:
  
        service_name    : Service01
  
        service_provider: FFmpeg
  
      Stream #0:0[0x100]: Video: h264 (High) ([27][0][0][0] / 0x001B), yuv420p(progressive), 1920x1080, 23.98 fps, 23.98 tbr, 90k tbn, 47.95 tbc
  
      Stream #0:1[0x101](eng): Audio: aac (LC) ([15][0][0][0] / 0x000F), 44100 Hz, stereo, fltp, 64 kb/s
  
  Stream mapping:
  
    Stream #0:0 -> #0:0 (h264 (native) -> h264 (h264_nvenc))
  
    Stream #0:1 -> #0:1 (aac (native) -> aac (native))
  
  Press [q] to stop, [?] for help
  
  [h264 @ 0x55a5edc45880] co located POCs unavailable
  
  [h264_nvenc @ 0x55a5edc45380] Cannot get the preset configuration: invalid version (15)
  
  Error initializing output stream 0:0 -- Error while opening encoder for output stream #0:0 - maybe incorrect parameters such as bit_rate, rate, width or height
  
  [aac @ 0x55a5edc46d40] Qavg: 227.785
  
  [aac @ 0x55a5edc46d40] 2 frames left in the queue on closing

  I have same version of FFMPEG compiled by the same way on another testing machine and there it is working. I tried to recompile/reinstall ffmpeg with the latest version, but result is the same.

  Does someone know what could be wrong on my instance ?
  Thanks.