Recherche avancée

Sur d’autres sites (14671)

• Connection randomly closes wihtout data while running a FFMPEG PHP script

  23 octobre 2022, par Victor Marinov

  I'm building a simple back-end solution for a client that allows them to upload any video in mo4 or mov format of up to about 500MB in size to a PHP back-end, which then takes the material, downsizes and compresses the it using the PHP library FFMPEG available here https://github.com/PHP-FFMpeg/PHP-FFMpeg.

  


  While the video is being processed the connection to the front-end stays open, awaiting the compression result.

  


  This may normally take up to 3-5 minutes depending on the size and duration of the video.

  


  Overall it functions as intended, but with some videos I get random resets of the connection while the video is being processed.

  


  I've added numerous error_log() lines in my script which show that the script continues running even after the connection is reset and the actual processing and compression of the video completes correctly and the file is saved in the DB and in storage.

  


  Below is a small excerpt from the code in question :

  


                          //THEN COMPRESS VIDEO THUMBNAIL
                        $format = new FFMpeg\Format\Video\X264();
                        $format->setKiloBitrate(3200);
                        error_log("BEFORE COMPRESS! ", 0);

                        //PREVENT ANY ECHO's
                        ob_start();
                        error_log("DURING COMPRESS... ", 0);
                        $video->save($format, $export_path);
                        error_log("JUST AFTER... ", 0);
                        $compress_output = ob_get_clean();

                        $resp['video_compression_result'] = 'success';
                        error_log("COMPRESS SUCCESS! ", 0);


  


  I would just like to know if any of you would have an idea why the connection might be reset on some files and not on others ? I've even tried wrapping the the $video->save() function in an output buffer to prevent any possible output which might trigger an premature output.

  


  I have increased the PHP settings for max_memory to 2G and upload_max_filze and post_max size to 500M.

  


  max_execution_time and max_input_time are both set to 1200 sec. The random reset usually comes at 1.7 or 5.4 minutes into the request and seem to depend on the file selected.

  


  I've successfully processed smaller files from the same source without issues. The only variable here appears to be the duration and size of the video. What is most puzzling to me is that the remaining code continues to run fine even after the connection is reset.

  


  If you have any clues, please let me know as this is driving me crazy for a second day in a row now and spoiling an otherwise perfectly functional solution for the client !

  


• Decoding RIMM streaming file format

  10 septembre 2011, par Thomas

  I want to decode the video (visual) frames within a Blackberry RIMM file. So far I have a parser, and some corresponding container documentation from RIM. 

  The video codec is H264 and is explicitly set on the device using one of the video.encodings properties. However, FFMPEG is not able to decode the frames and this is driving me nuts.

  Edit 1 : The issues seems to be lack of SPS and PPS in the frames, and artificially inserting them have proven unsuccessful so far (all grey image). Blackberry 9700 sends

  0x00 0x00 0x ?? 0x ?? 0xType

  where Type is according to table 7-1 in the H264 spec (I and P frames). We believe the 0x ?? 0x ?? represent the size of the frame, however the size does not always correspond to the size found by the parser (the parser seems to be working correctly).

  I have a windows decoder codec from blackberry, called mc_demux_mp2_ds.ax, and can play some MPEG-4 files captured the same way, but it is a binary for windows. And the H264 files will not play either way. I am aware of previous attempts. The capture url for javax.microedition.media.Manager is

  encoding=video-3gpp_width=176_height=144_video_codec=H264_audio_codec=AAC

  and I am writing to an output stream. Some example files here.

  Edit 2 :Turns out that about 3-4 of the 12-15 available video capture modes are flat out failing and refusing to output data, even in the simplest of test applications. So any working solution should implement MPEG-4, H264 and H263 in both AMR and AAC, in so getting fallback alternatives when one sound codec and/or resolution fails. Reboots, hangs and what not litters the Blackberry video implementation and vary from firmware to firmware ; total suckage.

• Error with RTSP Stream in Node.js : Could not find codec parameters for stream 0 (Video : h264, none)

  7 août 2023, par theplaceofburak

  I have a Node.js application that uses the node-rtsp-stream package to stream an RTSP video from an IP camera. However, when I run the application, I encounter the following errors in the console after a few minutes :

  


  [rtsp @ 000002402795dd80] Could not find codec parameters for stream 0 (Video: h264, none): unspecified size
Consider increasing the value for the 'analyzeduration' (0) and 'probesize' (5000000) options
Input #0, rtsp, from 'rtsp://fake_test:jksdfhskhdfsomethingfake@111.111.11.1111:50213/cam/realmonitor?channel=1&subtype=1'(fake rtsp link used for privacy)':
  Metadata:
    title           : Media Server
  Duration: N/A, bitrate: N/A
  Stream #0:0: Video: h264, none, 90k tbr, 90k tbn
Output #0, mpegts, to 'pipe:':
[out#0/mpegts @ 0000024027987b80] Output file does not contain any stream
Error opening output file -.
Error opening output files: Invalid argument
RTSP stream exited with error


  


  I am certain that the RTSP stream from the camera is in H.264 - MPEG-4 AVC format, and I can play it in VLC without any issues. However, when I try to stream it using the node-rtsp-stream package, I encounter these errors.

  


  Here is my Node.js code :

  


  const express = require('express');
const Stream = require('node-rtsp-stream');

const app = express();
const port = 4000;


const stream = new Stream({
  name: 'rtsp_server_name',
  streamUrl: 'rtsp://fake_test:jksdfhskhdfsomethingfake@111.111.11.1111:50213/cam/realmonitor?channel=1&subtype=1'(fake rtsp link used for privacy),
  wsPort: 9999,
  ffmpegOptions: {
    '-stats': '', // an option with no necessary value uses a blank string
    '-r': 30, // options with required values specify the value after the key
  },
});

// Middleware to log each request
app.use((req, res, next) => {
  console.log(`${req.method} ${req.url}`);
  next();
});

app.get('/', (req, res) => {
  res.send('Hello World');
});

app.listen(port, () => {
  console.log(`Server running at http://localhost:${port}/`);
});

// Event listener to check if the RTSP stream is ready
stream.on('data', (data) => {
  if (data.includes('frame=')) {
    console.log('RTSP stream is ready and streaming.');
  }
});


  


  I have tried increasing the values for 'analyzeduration' and 'probesize' options, but the errors persist. How can I resolve these errors and successfully stream the RTSP video in H.264 format using the node-rtsp-stream package ? Any help or guidance would be appreciated. Thank you !