Recherche avancée

Sur d’autres sites (13765)

• Getting ffmpeg error ‘Ignoring unsupported var reason rtmp :// : I/O error’

  6 septembre 2022, par Lectos Lacious

  Same setting worked normally for months, suddenly start to receive ffmpeg errors about ‘unsupported var’ related to rtmp and streaming stop working. Is this error about unavailable server or bad url ? Can someone enlighten me about meaning of unsupported var ?

  


  NOTE : replaced actual url with ‘someurl’

  


  LOG :
Input #0, rtsp, from 'rtsp ://192.168.40.44:554/1' :
  
Metadata :
  
title : 10
  
Duration : N/A, start : 0.000000, bitrate : N/A
  
Stream #0:0 : Video : h264, yuvj420p(pc, bt709), 1280x720, 15 tbr, 90k tbn, 180k tbc
  
Stream #0:1 : Audio : aac, 48000 Hz, stereo, fltp
  
[rtmp @ 0x7f9fdd58c5e0] Ignoring unsupported var reason
  
rtmp ://someurl : I/O error
  
Exiting normally, received signal 2.
  
Input #0, rtsp, from 'rtsp ://192.168.40.44:554/1' :
  
Metadata :
  
title : 10
  
Duration : N/A, start : 0.000000, bitrate : N/A
  
Stream #0:0 : Video : h264, yuvj420p(pc, bt709), 1280x720, 15 fps, 15 tbr, 90k tbn, 180k tbc
  
Stream #0:1 : Audio : aac, 48000 Hz, stereo, fltp
  
[rtmp @ 0x7f62a5869b20] Ignoring unsupported var reason
  
rtmp ://someurl : I/O error
  
Exiting normally, received signal 2.
  
[rtsp @ 0x7f0b4add32a0] max delay reached. need to consume packet
  
[rtsp @ 0x7f0b4add32a0] RTP : missed 2 packets
  
Input #0, rtsp, from 'rtsp ://192.168.40.44:554/1' :
  
Metadata :
  
title : 10
  
Duration : N/A, start : 0.000000, bitrate : N/A
  
Stream #0:0 : Video : h264, yuvj420p(pc, bt709), 1280x720, 15 fps, 15 tbr, 90k tbn, 180k tbc
  
Stream #0:1 : Audio : aac, 48000 Hz, stereo, fltp
  
[rtmp @ 0x7f0b4af13840] Ignoring unsupported var reason
  
rtmp ://someurl : I/O error
  
Exiting normally, received signal 2.
  
Input #0, rtsp, from 'rtsp ://192.168.40.44:554/1' :
  
Metadata :
  
title : 10
  
Duration : N/A, start : 0.000000, bitrate : N/A
  
Stream #0:0 : Video : h264, yuvj420p(pc, bt709), 1280x720, 15 fps, 15 tbr, 90k tbn, 180k tbc
  
Stream #0:1 : Audio : aac, 48000 Hz, stereo, fltp
  
[rtmp @ 0x7fc61ef8b880] Ignoring unsupported var reason

  


• Rails 5 - Concurrent large Video uploads using Carrierwave eats up the server memory/space

  22 mars 2020, par Milind

  I have a working Rails 5 apps using Reactjs for frontend and React dropzone uploader to upload video files using carrierwave.

  So far, what is working great is listed below -

  1. User can upload videos and videos are encoded based on the selection made by user - HLS or MPEG-DASH for online streaming.
  2. Once the video is uploaded on the server, it starts streaming it by :-
     • FIRST,copying video on /tmp folder.
     • Running a bash script that uses ffmpeg to transcode uploaded video using predefined commands to produce new fragments of videos inside /tmp folder.
     • Once the background job is done, all the videos are uploaded on AWS S3, which is how the default carrierwave works
  3. So, when multiple videos are uploaded, they are all copied in /tmp folder and then transcoded and eventually uploaded to S3.

  My questions, where i am looking some help are listed below -

  1- The above process is good for small videos, BUT what if there are many concurrent users uploading 2GB of videos ? I know this will kill my server as my /tmp folder will keep on increasing and consume all the memory, making it to die hard.How can I allow concurrent videos to upload videos without effecting my server’s memory consumption ?

  2- Is there a way where I can directly upload the videos on AWS-S3 first, and then use one more proxy server/child application to encode videos from S3, download it to the child server, convert it and again upload it to the destination ? but this is almost the same but doing it on cloud, where memory consumption can be on-demand but will be not cost-effective.

  3- Is there some easy and cost-effective way by which I can upload large videos, transcode them and upload it to AWS S3, without effecting my server memory. Am i missing some technical architecture here.

  4- How Youtube/Netflix works, I know they do the same thing in a smart way but can someone help me to improve this ?

  Thanks in advance.

• Rails 5 - Video streaming using Carrierwave uploaded video size constraint on the server

  21 mars 2020, par Milind

  I have a working Rails 5 apps using Reactjs for frontend and React dropzone uploader to upload video files using carrierwave.

  So far, what is working great is listed below -

  1. User can upload videos and videos are encoded based on the selection made by user - HLS or MPEG-DASH for online streaming.
  2. Once the video is uploaded on the server, it starts streaming it by :-
     • FIRST,copying video on /tmp folder.
     • Running a bash script that uses ffmpeg to transcode uploaded video using predefined commands to produce new fragments of videos inside /tmp folder.
     • Once the background job is done, all the videos are uploaded on AWS S3, which is how the default carrierwave works
  3. So, when multiple videos are uploaded, they are all copied in /tmp folder and then transcoded and eventually uploaded to S3.

  My questions, where i am looking some help are listed below -

  1- The above process is good for small videos, BUT what if there are many concurrent users uploading 2GB of videos ? I know this will kill my server as my /tmp folder will keep on increasing and consume all the memory, making it to die hard.How can I allow concurrent videos to upload videos without effecting my server’s memory consumption ?

  2- Is there a way where I can directly upload the videos on AWS-S3 first, and then use one more proxy server/child application to encode videos from S3, download it to the child server, convert it and again upload it to the destination ? but this is almost the same but doing it on cloud, where memory consumption can be on-demand but will be not cost-effective.

  3- Is there some easy and cost-effective way by which I can upload large videos, transcode them and upload it to AWS S3, without effecting my server memory. Am i missing some technical architecture here.

  4- How Youtube/Netflix works, I know they do the same thing in a smart way but can someone help me to improve this ?

  Thanks in advance.