Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Don Resnik <don.resnik@wrench.io>
To: ffmpeg-devel@ffmpeg.org
Subject: [FFmpeg-devel] Question about ffmpeg support of sph files with embedded-shorten-v2.00 coding
Date: Tue, 29 Aug 2023 12:45:57 -0400
Message-ID: <CA+aEaaBS6Q=SEBtAK8Q2Y-xHPEdyvo+Jnz1ZL+dVMVa6oUqDoQ@mail.gmail.com> (raw)

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:

NIST_1A
   1024
sample_count -i 10612160
sample_n_bytes -i 1
channel_count -i 2
sample_byte_format -s1 1
sample_rate -i 8000
sample_coding -s27 ulaw,embedded-shorten-v2.00
database_id -s8 CALLHOME
pin -s6 509115
sample_checksum -i 12165
end_head

Here is the command:
>ffprobe -i input-file.sph

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.

Thank you for your help resolving this issue.

Don R.
_______________________________________________
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:[~2023-08-29 16:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-29 16:45 Don Resnik [this message]
2023-08-29 20:30 ` Peter Ross
2023-08-29 21:40   ` Don Resnik

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+aEaaBS6Q=SEBtAK8Q2Y-xHPEdyvo+Jnz1ZL+dVMVa6oUqDoQ@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