Recherche avancée

Sur d’autres sites (7571)

• Copied .ass Subtitle Has Font Size Changed

  7 novembre 2022, par Rapta

  This is happening when doing an mkv to mkv conversion, with a simple -c:s copy, and whilst the font style, and position are the same, the size ends up being bigger. I'm also playing it with VLC ,if that matters.

  


  Here're the sub settings :
[Script Info]
 ; Script generated by Aegisub r8942
 ; http://www.aegisub.org/
Title : Default Aegisub file
ScriptType : v4.00+
PlayDepth : 0
YCbCr Matrix : TV.601
PlayResX : 708
PlayResY : 480
WrapStyle : 0
ScaledBorderAndShadow : yes

  


  [Aegisub Project Garbage]
Last Style Storage : Default
Video AR Mode : 4
Video AR Value : 1.333333
Video Zoom Percent : 1.000000
Video Position : 35410

  


  [V4+ Styles]
Format : Name, Fontname, Fontsize, PrimaryColour, SecondaryColour, OutlineColour, BackColour, Bold, Italic, Underline, StrikeOut, ScaleX, ScaleY, Spacing, Angle, BorderStyle, Outline, Shadow, Alignment, MarginL, MarginR, MarginV, Encoding
Style : Default,Funimitation,28,&H00FFFFFF,&H0300FFFF,&H00000000,&H02000000,-1,0,0,0,100,100,1,0,1,2,0,2,40,40,25,1
Style : Lyrics JPN,Faxfont Tone,40,&H00FFFFFF,&H000000FF,&H00000000,&H501D0032,0,0,0,0,100,100,0,0,1,0,0,8,0,0,10,0
Style : Lyrics ENG,Faxfont Tone,36,&H00FFFFFF,&H000000FF,&H00000000,&H501D0032,0,0,0,0,100,100,0,0,1,0,0,2,0,0,6,0
Style : Title,Faxfont Tone,55,&H00FFFFFF,&H000000FF,&H28616161,&H28E0E0E0,-1,0,0,0,100,100,0,0,1,0.5,0.1,2,10,10,20,1
Style : Credits ENG,Faxfont Tone,42,&H00FFFFFF,&H000000FF,&H00000000,&H501D0032,0,0,0,0,100,100,0,0,1,0,0,8,0,0,0,0

  


  And here's a sub example :
[Events]
Format : Layer, Start, End, Style, Name, MarginL, MarginR, MarginV, Effect, Text
Dialogue : 0,0:00:17.95,0:00:20.79,Credits ENG,,0,0,0,,\blur0.6\c&HFFF3ED&\fscx60\fscy76\pos(102.882,73)Planning

  


  If I export the sub from the converted file, all of the settings are the same.

  


  Is there any way to stop the size from changing ?

  


  Thanks

  


  Tried : -c:s copy
Expected : Complete copy.
Resulted : Not a complete copy — the font size was bigger.

  


• FFmpeg streaming stuck few minutes after start [closed]

  19 février, par josue ramirez

  Sorry for my english ! :D

  


  I'm trying to make a live video stream from my webcam with ffmpeg using Node.

  


  I get the images or frames from ffmpeg via pipe1 on the stdout event and send them via a socket-io client to my angular app to play the stream.

  


  So far the stream starts fine and my angular app can play it fine, but after a certain time (8 minutes or so) ffmpeg stops sending data and the stream in my angular app stops and if I want to start the webcam again it's not possible anymore because it's apparently occupied by another process. I've been trying to figure out what's going on and what I've noticed is that the ffmpeg process just stops and the process is no longer visible with the top command (ubuntu), but the child process in node still shows a ffmpeg process as if it were a zombie process.

  


  I've tried running ffmpeg from the terminal to save an mp4 file with the stream and in that case there is no problem, the recording doesn't stop even using pipe1. Only when I run ffmpeg from my Node app, the error occurs.

  


  Does anyone have any idea what could be going on ?

  


  This command is the one that is executed to send the data through pipe1 both from node and from the terminal but it only stops in Node

  


  ffmpeg -f v4l2 -input_format mjpeg -video_size 800x600 -i /dev/video0 -q:v 4 -f image2pipe pipe1


  


  The same thing happens when saving an mp4 video only in Node it fails

  


  ffmpeg -f v4l2 -input_format mjpeg -video_size 800x600 -i /dev/video0 -q:v 4 video.mp4


  


  This is my function that starts the streaming

  


  export const startCamera = () => {
    logger.info('Starting camera ', cameraName);

    const inputFormat = process.platform === 'win32' ? 'dshow' : 'v4l2';

    const ffmpegArgs = [
        '-f', inputFormat, // Formato de entrada según la plataforma
    ];

    if (process.platform === 'linux') {
        ffmpegArgs.push(
            '-input_format', 'mjpeg',  // Especificar el formato antes de video_size
            '-video_size', '800x600',  // Tamaño de la imagen
        );
    }
    
    ffmpegArgs.push(
        '-i', cameraName,    // Dispositivo de entrada
        '-vf', 'fps=15',     // Fotogramas por segundo
        '-q:v', '10',        // Calidad de video
        '-f', 'image2pipe',  // Formato de salida
        'pipe:1'             // Salida por stdout
    );

    try {
        logger.info('FFmpeg command: ffmpeg', ffmpegArgs.join(' '));
        ffmpeg = spawn('ffmpeg', ffmpegArgs);
        let cameraOpen = false;
        // Enviar los datos del fotograma a través del WebSocket
        ffmpeg.stdout.on('data', (chunk) => {
            logger.debug(`Sending chunk of ${chunk.length} bytes`);
            if (!cameraOpen) {
                cameraOpen = true;
                serialConnection.connect();
                logger.info('Camera started!!');
            }

            if (streamWS.isActive()) {
                streamWS.send(chunk);
            }
        });
        // Manejo de errores
        ffmpeg.stderr.on('error', (data) => {
            logger.error('FFmpeg Error:', data.toString());
        });

        ffmpeg.on('close', async () => {
            logger.info('Camera closed....', cameraName);
            if (!cameraOpen) {
                await commandWS.send(
                    {
                        command: COMMANDS.START_STREAM,
                        isError: true,
                        response: `Error al intentar iniciar la camara ${cameraName}, verificar que la camara se encuentre bien conectada.`,
                    },
                    COMMANDS_EVENTS.ROBOT_RESPONSE
                );
            }
            cameraOpen = false;
            await serialConnection.close();
            stopCamera();
            await streamWS.disconnectWS();
        });
    } catch (e) {
        logger.error('Error tryng to start the camera...', e);
    }
};


  


• (ffmpeg) : Failed to read frame size : Could not seek to 1026

  24 mai 2021, par UserUNP

  I was trying to convert Midi files to Mp3 files using timidity and ffmpeg
using this command

  


  python -m timidity play.mid -Ow -o - | ffmpeg -i - -acodec libmp3lame -ab 64k play.mp3


  


  so I can use it in my Discord bot, but whenever I execute the command, it always returns this error that I couldn't understand

  


  [mp3 @ 0x56226d7e0440] Format mp3 detected only with low score of 1, misdetection possible!
[mp3 @ 0x56226d7e0440] Failed to read frame size: Could not seek to 1026.
play.mp3: Invalid argument


  


  If you have any idea to what this means or how can I fix it then please give me an Answer, thanks !