
Recherche avancée
Médias (1)
-
Rennes Emotion Map 2010-11
19 octobre 2011, par
Mis à jour : Juillet 2013
Langue : français
Type : Texte
Autres articles (57)
-
Use, discuss, criticize
13 avril 2011, parTalk to people directly involved in MediaSPIP’s development, or to people around you who could use MediaSPIP to share, enhance or develop their creative projects.
The bigger the community, the more MediaSPIP’s potential will be explored and the faster the software will evolve.
A discussion list is available for all exchanges between users. -
MediaSPIP Player : problèmes potentiels
22 février 2011, parLe lecteur ne fonctionne pas sur Internet Explorer
Sur Internet Explorer (8 et 7 au moins), le plugin utilise le lecteur Flash flowplayer pour lire vidéos et son. Si le lecteur ne semble pas fonctionner, cela peut venir de la configuration du mod_deflate d’Apache.
Si dans la configuration de ce module Apache vous avez une ligne qui ressemble à la suivante, essayez de la supprimer ou de la commenter pour voir si le lecteur fonctionne correctement : /** * GeSHi (C) 2004 - 2007 Nigel McNie, (...) -
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 (8779)
-
can't stream rtsp with ffmpeg
7 novembre 2017, par xswxw222I want to stream rtsp with ffmpeg and ffserver
I use on this config
<feed>
File /tmp/feed1.ffm
FileMaxSize 200K
# You could specify
# ReadOnlyFile /saved/specialvideo.ffm
# This marks the file as readonly and it will not be deleted or updated.
# Specify launch in order to start ffmpeg automatically.
# First ffmpeg must be defined with an appropriate path if needed,
# after that options can follow, but avoid adding the http:// field
#Launch ffmpeg
# Only allow connections from localhost to the feed.
ACL allow 127.0.0.1
</feed>
#<stream>
#Format rtp
#Feed feed1.ffm
#VideoCodec libx264
#VideoFrameRate 24
#VideoBitRate 100
#VideoSize 480x272
#AVPresetVideo default
#AVPresetVideo baseline
#AVOptionVideo flags +global_header
#
#AudioCodec libfaac
#AudioBitRate 32
#AudioChannels 2
#AudioSampleRate 22050
#AVOptionAudio flags +global_header
#</stream>and run ffserver.
Now i run the ffmpeg likeffmpeg -i input.mp4 http://x.x.x.x:8090/out.h264
.When i tried to watch on this url with ffplayer i got 2 error :
1 : On ffplay terminal I see
stream ends prematurely al 0 should be (SOME NUMBER)
.2 : On ffserver terminal I see
max packet size 0 too low Error writing output header for stream live.h264
I tried to add -packetsize 9999 but it stil show me those errors
What can I do to fix that ?
-
FFMPEG bash > folder processing > AI upscale - script ERROR ">" [closed]
13 novembre 2022, par Jason Paul MichaelsTrying to port a single file manual command from Topaz AI so I can run it as a part of a simple script allowing me to run multiple sessions from terminal. I am running MacOS with BASH 5.2 and when I run the script I get dumped to ">" instead of command prompt and no error message is displayed.


This is my command -


for f in *.mp4; do
 /Applications/Topaz\ Video\ AI.app/Contents/MacOS/ffmpeg \
 -hide_banner \
 -nostdin \
 -y \
 -nostats \
 -i “$f” \
 -vsync 0 \
 -avoid_negative_ts 1 \
 -sws_flags spline+accurate_rnd+full_chroma_int \
 -color_trc 1 \
 -colorspace 1 \
 -color_primaries 1 \
 -filter_complex veai_up=model=prob-3:scale=0:w=1920:h=1080:preblur=0:noise=0:details=0:halo=0:blur=0:compression=0:estimate=20:device=0:vram=1:instances=1,scale=w=1920:h=1080:flags=lanczos:threads=0,scale=out_color_matrix=bt709 \
 -c:v prores_videotoolbox \
 -profile:v lt \
 -pix_fmt p210le \
 -allow_sw 1 \
 -map_metadata 0 \
 -movflags frag_keyframe+empty_moov+delay_moov+use_metadata_tags+write_colr \
 -map_metadata:s:v 0:s:v \
 -map_metadata:s:a 0:s:a \
 -c:a aac \
 "encoded/${f%.*}.mp4”;
done



I have a feeling it's something really simple I'm missing but I've gone through it a dozen times and can't seem to modify in any way to success.


Thank you !


Getting dumped back to ">" terminal prompt.


-
How do you run ffmpeg from Java, without crashing ?
30 juin 2024, par WinnieTheDampoehI try running ffmpeg from Java, and for a couple of moments everything is working fine. I want ffmpeg to record my screen, and split the recording into small clips. The command is working fine from the terminal, but when I run it from Java I get at most 3 clips. Ffmpeg doesn't write anything to the InputStream, so I have no idea what's going wrong.


public static void execute(int frameRate, int width, int height, String windowTitle) {
 String[] args = new String[]{
 path,
 "-hide_banner",
 "-f", "gdigrab",
 "-thread_queue_size", "1024",
 "-rtbufsize", "256M",
 "-framerate", "" + frameRate,
 "-offset_x", "0",
 "-offset_y", "0",
 "-video_size", "" + width + "x" + height,
 "-draw_mouse", "1",
 "-i", "title=" + windowTitle,
 "-c:v", "libx264",
 "-r", "" + frameRate,
 "-preset", "ultrafast",
 "-tune", "zerolatency",
 "-crf", "28",
 "-pix_fmt", "yuv420p",
 "-movflags", "+faststart",
 "-y",
 "-f", "segment",
 "-reset_timestamps", "1",
 "-segment_time", "1",
 "output%06d.mp4"
 };

 try {
 Process p = Runtime.getRuntime().exec(args);
 Thread thread = new Thread(() -> {
 String line;
 BufferedReader input = new BufferedReader(new InputStreamReader(p.getInputStream()));

 System.out.println("TEST");
 try {
 while ((line = input.readLine()) != null)
 System.out.println(line);

 System.out.println("Stopping with reading");
 input.close();
 } catch (IOException e) {
 e.printStackTrace();
 }
 });
 int exitCode = p.waitFor();
 thread.start();
 thread.join();
 if (exitCode != 0) {
 throw new RuntimeException("FFmpeg exited with code " + exitCode);
 }
 } catch (IOException | InterruptedException e) {
 throw new RuntimeException(e);
 }
 }



I've run the same command in the terminal. That worked fine. I ran the code above, but that resulted in ffmpeg stopping after 3 clips. It kept showing as working from the task manager. As said before, ffmpeg doesn't write anything to the InputStream, even though it normally does write a lot in the terminal. The weird thing is, when I stop my Java program, but accidentally keep ffmpeg running, it suddenly does everything I wanted it to. It didn't capture the things between stopping and closing Java, but after that it continues like it should have.