Recherche avancée

Sur d’autres sites (10526)

• Application Crashes With No Exception

  24 octobre 2017, par Frank Natoli

  Have a relatively complex C# Windows Forms application that makes use of C++ bridge DLL to call FFmpeg DLLS to concurrently write multiple MP4 files directly from imagery downloaded from real time cameras using a separate thread for each camera.

  On my Windows 7 development laptop, Toshiba Tecra with i7 vPro eight core CPU and 16GB RAM, and on customer laptop, application runs fine.
  But on customer desktop, configuration unknown, when the application finishes recording and begins downloading imagery from the real time cameras and thus begins calling FFmpeg DLLs, the application disappears without a trace, no exception message, no "program has stopped working", nothing. Normal program exit writes an "application exiting" message to a log file which is NOT happening, so I am reasonably certain the program is not normally exiting.
  What might result in a C# Windows Forms application crash with no exception report from Windows ?

• Red5 Streaming in flv Or h.264 [closed]

  23 février 2013, par alex

  How do i mux a h.264 video into an flv container. This is for high quality streaming in red5. With video on demand service people can upload a video it ghets saved to streams directory of red5 and streamed and played from flash.

• FFmpeg starting manually but not with Systemd on boot

  23 juin 2021, par eKrajnak

  On Raspberry Pi 4 B 4GB with official Debian 10 image, I have /home/pi/run.sh script with following :

  


  #!/bin/bash
ffmpeg -nostdin -framerate 15 -video_size 1280x720 -input_format yuyv422  -i /dev/video0 -f alsa -i hw:Device \
    -af acompressor=threshold=-14dB:ratio=9:attack=10:release=1000 -c:a aac -ac 2 -ar 48000 -ab 160k \
    -c:v libx264 -pix_fmt yuv420p -b:v 3M -bf 1 -g 20 -flags +ilme+ildct -preset ultrafast \
    -streamid 0:0x101 -streamid 1:0x100 -mpegts_pmt_start_pid 4096 -mpegts_start_pid 0x259 -metadata:s:a:0 language="" -mpegts_service_id 131 -mpegts_transport_stream_id 9217 -metadata provider_name="Doesnt matter" -metadata service_name="Doesnt matter" \
    -minrate 3500 -maxrate 3500k -bufsize 4500k -muxrate 4000k  -f mpegts "udp://@239.1.67.13:1234?pkt_size=1316&bitrate=4000000&dscp=34" -loglevel debug < /dev/null > /tmp/ff3.log 2>&1


  


  Script is starting from console without problems. It takes audio from USB sound card and video from USB camera and creates UDP stream to IPTV. Then I created Systemd service :

  


  [Unit]
Description=Streamer
After=multi-user.target sound.target network.target

[Service]
ExecStart=/home/pi/run.sh
KillMode=control-group
Restart=on-failure
TimeoutSec=1

[Install]
WantedBy=multi-user.target
Alias=streaming.service


  


  After restarting Raspberry, script has started, but FFmpeg hangs on error failures in log :

  


  cur_dts is invalid st:0 (257) [init:1 i_done:0 finish:0] (this is harmless if it occurs once at the start per stream)
cur_dts is invalid st:1 (256) [init:1 i_done:0 finish:0] (this is harmless if it occurs once at the start per stream)
cur_dts is invalid st:0 (257) [init:1 i_done:0 finish:0] (this is harmless if it occurs once at the start per stream)
cur_dts is invalid st:1 (256) [init:1 i_done:0 finish:0] (this is harmless if it occurs once at the start per stream)
cur_dts is invalid st:0 (257) [init:1 i_done:0 finish:0] (this is harmless if it occurs once at the start per stream)
cur_dts is invalid st:1 (256) [init:1 i_done:0 finish:0] (this is harmless if it occurs once at the start per stream)
cur_dts is invalid st:0 (257) [init:1 i_done:0 finish:0] (this is harmless if it occurs once at the start per stream)
cur_dts is invalid st:1 (256) [init:1 i_done:0 finish:0] (this is harmless if it occurs once at the start per stream)


  


  and will not start streaming to UDP target. But, if I manually login to SSH and issue systemctl stop streaming and then systemctl start streaming Ffmpeg starts successfully. What's different with service auto-start on boot ?

  


  Setting the "sleep timeout" at script begginging will not help. However, removing audio stream from FFmpeg config looks to solve auto-start on boot.