From: Adolfo Rodrigues <adolfotregosa@gmail.com> To: ffmpeg-devel@ffmpeg.org Subject: [FFmpeg-devel] Fix for [ffmpeg] spdif: Unusual frame timing 40 samples/frame is not implemented. Date: Sun, 21 Apr 2024 00:22:28 +0100 Message-ID: <CA+gx7UrvjU6W+V0hRCKCkp7PQETWwY=0VCHA8bMKzAYkroefXQ@mail.gmail.com> (raw) Hello. I'm new at this so please bare with me. I have created a sample file that produces an audio drop at the same time it produces the following message: [ffmpeg] spdif: Unusual frame timing: 10248 => 12042, 40 samples/frame is not implemented. Update your FFmpeg version to the newest one from Git. If the problem still occurs, it means that your file has a feature which has not been implemented. sample file -> https://tregosacloud.duckdns.org/s/HRWxz7oX7HCSSpD The same message shows up when I seek but with the added side effect of audio rarely recovering, becoming silent. I found out that by editing the file spdifenc.c and commenting out: /* sanity check */ //if (padding_remaining < 0 || padding_remaining >= MAT_FRAME_SIZE / 2) { // avpriv_request_sample(s, "Unusual frame timing: %"PRIu16" => %"PRIu16", %d samples/frame", // ctx->truehd_prev_time, input_timing, ctx->truehd_samples_per_frame); // padding_remaining = 0; // } All my issues went away. I have opened a ffmpeg trac ticket: https://trac.ffmpeg.org/ticket/10948 I'm no developer, my knowledge is very limited but I since I have yet to find any negative symptom of my change I'm leaving here my findings. Thank you for your time. Adolfo _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".
reply other threads:[~2024-04-20 23:22 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to='CA+gx7UrvjU6W+V0hRCKCkp7PQETWwY=0VCHA8bMKzAYkroefXQ@mail.gmail.com' \ --to=adolfotregosa@gmail.com \ --cc=ffmpeg-devel@ffmpeg.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel This inbox may be cloned and mirrored by anyone: git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \ ffmpegdev@gitmailbox.com public-inbox-index ffmpegdev Example config snippet for mirrors. AGPL code for this site: git clone https://public-inbox.org/public-inbox.git