From: Don Resnik <don.resnik@wrench.io>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] Question about ffmpeg support of sph files with embedded-shorten-v2.00 coding
Date: Tue, 29 Aug 2023 17:40:17 -0400
Message-ID: <CA+aEaaCh5n9yaE4JU7qTmYFgcUHXnLvyQ+KpoNbe8T0Q91OHqQ@mail.gmail.com> (raw)
In-Reply-To: <ZO5VV5i+p+DCtJhY@e7558a32d3568eef279faaec59470a4a>
Peter,
Thanks for your response. I mentioned that I am using ffmpeg 6.0, isn't
that the latest version?
I will submit on the bug tracker side. After doing some research, I think
the issue is that in
https://github.com/FFmpeg/FFmpeg/blob/master/libavformat/nistspheredec.c#L73
The only embedded-shorten condition that is handled is this one
} else if (!av_strncasecmp(coding, "pcm,embedded-shorten", 20))
{
There is no accounting for my coding condition 'ulaw,embedded-shorten-v2.00'
I will submit it as a bug, but I may also try to make a patch to test that
if I include my coding in the conditional that it will work.
Thanks,
Don R
On Tue, Aug 29, 2023 at 4:30 PM Peter Ross <pross@xvid.org> wrote:
> On Tue, Aug 29, 2023 at 12:45:57PM -0400, Don Resnik wrote: > ffmpeg,
> >
> > I have a sph file that ffmpeg will not process. I am using ffmpeg 6.0,
> > which I believe is the latest version. I am actually running ffprobe on
> > the file.
> >
> > Here is the file header:
>
> ...
>
> > and here is the output:
> > [nistsphere @ 0x29f1ac0] coding ulaw,embedded-shorten-v2.00 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.
> >
> > Before I go through sending a sample file, I would just like to confirm
> > that ffmpeg should be able to process audio files with:
> >
> > 'sample_coding -s27 ulaw,embedded-shorten-v2.00'
> >
> > I was hoping there was a setting for configuration I could try that I
> have
> > not discovered yet to make this work.
>
> Follow the instructions: *Update your FFmpeg version to the newest one
> from Git.*
>
> If you do not know how to update FFmpeg from git, I suggest using an
> automatic build: https://github.com/BtbN/FFmpeg-Builds/releases
>
> If problem still exists report it on the bug tracker:
> https://trac.ffmpeg.org/ . Attach sample file to bug report.
>
> -- Peter
> (A907 E02F A6E5 0CD2 34CD 20D2 6760 79C5 AC40 DD6B)
> _______________________________________________
> 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".
>
_______________________________________________
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".
prev parent reply other threads:[~2023-08-29 21:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-29 16:45 Don Resnik
2023-08-29 20:30 ` Peter Ross
2023-08-29 21:40 ` Don Resnik [this message]
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+aEaaCh5n9yaE4JU7qTmYFgcUHXnLvyQ+KpoNbe8T0Q91OHqQ@mail.gmail.com \
--to=don.resnik@wrench.io \
--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