
Recherche avancée
Autres articles (106)
-
MediaSPIP 0.1 Beta version
25 avril 2011, parMediaSPIP 0.1 beta is the first version of MediaSPIP proclaimed as "usable".
The zip file provided here only contains the sources of MediaSPIP in its standalone version.
To get a working installation, you must manually install all-software dependencies on the server.
If you want to use this archive for an installation in "farm mode", you will also need to proceed to other manual (...) -
Les autorisations surchargées par les plugins
27 avril 2010, parMediaspip core
autoriser_auteur_modifier() afin que les visiteurs soient capables de modifier leurs informations sur la page d’auteurs -
Publier sur MédiaSpip
13 juin 2013Puis-je poster des contenus à partir d’une tablette Ipad ?
Oui, si votre Médiaspip installé est à la version 0.2 ou supérieure. Contacter au besoin l’administrateur de votre MédiaSpip pour le savoir
Sur d’autres sites (15819)
-
I am phasing a issue of " ffmpeg attribute 'error'" in my project which is a voice command assistant using GPT 3.5 Turbo and BING API [closed]
2 mai 2023, par Rudraksh Singh BhadauriaI ma working on a pyhton project as want to make a program which can work as fluent as GPT and can also adapt latest news through BING API but after trying a lot I am stuck with a issue where "Error transcribing audio : module 'ffmpeg' has no attribute 'Error'" I have tried installing these ffmpeg files again and again in the way already mentioned in stack overflow but for me its not working.


I have tried using :
installing ffmpeg-pyhton in my terminal and also ffmpeg module and also I have reinstalled the whole files and also have put them in my environment variables.
If anyone could help me to sort this problem out then it will be great help.


-
Converting a rtsp stream to hls but got error "Non-monotonous DTS in output stream 0:0"
8 mai 2023, par DeviI'm converting a rtsp live camera stream to hls using ffmpeg, it is all good the first few hours, each segment file sizes around
1.1M
, which match the setting ofsegment_time
of 5 seconds. However, when I check back a few days later, the size of each segment file became20G
, and I found that some error are logged.

My current implementation is like this :


ffmpeg -fflags nobuffer \
 -rtsp_transport tcp \
 -i rtsp://abc.com/live.sdp \
 -fps_mode 0 \
 -copyts \
 -c copy \
 -movflags frag_keyframe+empty_moov \
 -hls_flags delete_segments+append_list \
 -f segment \
 -segment_list_flags live \
 -segment_time 5 \
 -segment_list_size 3 \
 -segment_format mpegts \
 -segment_list /app/mount/test/live.m3u8 \
 -segment_list_type m3u8 \
 -segment_wrap 10 \
 /app/mount/test/%04d.ts \
 2>&1 



Here's the logged error :


[segment @ 0x7fe5123101c0] Non-monotonous DTS in output stream 0:0; previous: 14179898636, current: 11332822107; changing to 14179898637. This may result in incorrect timestamps in the output file.
[segment @ 0x7fe5123101c0] stream:0 start_pts_time:157550 pts:14179898637 pts_time:157554 dts:14179898637 dts_time:157554 -> pts:14179898637 pts_time:157554 dts:14179898637 dts_time:157554
[NULL @ 0x7fe510744880] unknown SEI type 229
[segment @ 0x7fe5123101c0] Non-monotonous DTS in output stream 0:0; previous: 14179898637, current: 11332823907; changing to 14179898638. This may result in incorrect timestamps in the output file.
[segment @ 0x7fe5123101c0] stream:0 start_pts_time:157550 pts:14179898638 pts_time:157554 dts:14179898638 dts_time:157554 -> pts:14179898638 pts_time:157554 dts:14179898638 dts_time:157554
[segment @ 0x7fe5123101c0] Non-monotonous DTS in output stream 0:0; previous: 14179898638, current: 11332825707; changing to 14179898639. This may result in incorrect timestamps in the output file.
[segment @ 0x7fe5123101c0] stream:0 start_pts_time:157550 pts:14179898639 pts_time:157554 dts:14179898639 dts_time:157554 -> pts:14179898639 pts_time:157554 dts:14179898639 dts_time:157554



I've tried :


- 

- Changing the option
-fps_mode
withpassthrough
,vfr
,drop
. - Changing the option
-c
with-c copy
,-c:a copy -c:v libx264
.






None of the above works for me.


- Changing the option
-
Trying to stream a video loop using FFMPEG. However, I keep getting the error "Cannot Write the Headers Server returned 400 Bad Request" [closed]
8 mai 2023, par lokit khemkaI am using
mediamtx
for starting RTSP server. The command that I am using for ffmpeg is as follows :

ffmpeg -re -stream_loop -1 -i ./clouds.mp4 -f rtsp -rtsp_transport tcp rtsp://localhost:8554


The tried various different options but not luck. I am not getting the ffmpeg to stream the video.


The file details are as follows :


Input #0, mov,mp4,m4a,3gp,3g2,mj2, from './clouds.mp4':
 Metadata:
 major_brand : mp42
 minor_version : 0
 compatible_brands: mp42isomavc1
 creation_time : 2023-01-12T20:44:34.000000Z
 Duration: 00:00:56.34, start: 0.000000, bitrate: 2952 kb/s
 Stream #0:0[0x1](und): Video: h264 (High) (avc1 / 0x31637661), yuv420p(tv, bt709, progressive), 1920x1080, 2758 kb/s, 29.97 fps, 29.97 tbr, 30k tbn (default)
 Metadata:
 creation_time : 2023-01-12T20:44:34.000000Z
 handler_name : Vimeo Artax Video Handler
 vendor_id : [0][0][0][0]
 encoder : AVC Coding
 Stream #0:1[0x2](und): Audio: aac (LC) (mp4a / 0x6134706D), 48000 Hz, stereo, fltp, 189 kb/s (default)
 Metadata:
 creation_time : 2023-01-12T20:44:34.000000Z
 handler_name : Vimeo Artax Audio Handler
 vendor_id : [0][0][0][0]
Stream mapping:
 Stream #0:0 -> #0:0 (h264 (native) -> mpeg4 (native))
 Stream #0:1 -> #0:1 (aac (native) -> aac (native))



The error on
mediamtx
terminal window is :

2023/05/08 17:30:43 INF [RTSP] [session 298895e1] created by 127.0.0.1:38024
2023/05/08 17:30:43 INF [RTSP] [conn 127.0.0.1:38024] closed (invalid path)