similar to: Support for CAF in flac command-line?

On Sat, Nov 29, 2008 at 2:20 PM, Josh Coalson <xflac at yahoo.com> wrote: > --- Martin Leese <martin.leese at stanfordalumni.org> wrote: >> Erik de Castro Lopo <mle+la at mega-nerd.com> wrote: >> ... >> > Whats more, the sndfile-convert program can also convert >> > from FLAC to the following file formats that support 63 bit >> > file

Hello all, Is anyone here potentially up to the task of adding support for CAF (the CoreAudio Format) into the flac command-line? This would present minimal difficulty under OSX, due to the presence of the CoreAudio API, but the real challenge would be to support CAF on Unix and Windows - everywhere that flac is now available. Although the format is rather unknown, there are some very

RF64 support sure would be nice, but it wouldn't really help to do this "instead of" CAF. For one thing, Logic Studio Pro does not seem to support RF64, because the manual states that WAVE and BWF are limited to 4 GB. CAF may be a format which lacks universal support, but RF64 is also very limited in usefulness. Treating either one as a substitute for the other is not

On Oct 12, 2008, at 22:32, Paul Davis wrote: > On Sun, 2008-10-12 at 19:26 -0700, Brian Willoughby wrote: >> Is anyone here potentially up to the task of adding support for CAF >> (the CoreAudio Format) into the flac command-line? This would >> present minimal difficulty under OSX, due to the presence of the >> CoreAudio API, but the real challenge would be to support

Thanks for the interest, Michael. I don't use Ogg, so I'm a little wary that standard FLAC would be left out of any Ogg Frog implementation. But I say that mostly out of ignorance. I have noticed that there seem to be two worlds for FLAC, inside Ogg and outside. It's important to be aware of the fact that many hardware devices support the FLAC format directly, without the

Do you have a source on the CoreAudio quality thing? I'd be very interested in reading more about that. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.xiph.org/pipermail/flac-dev/attachments/20150719/f37ce5e8/attachment.htm

Hi all, Here are two patches, one for flac.git and one for flac-website.git, which 'merges' them. This is mainly some cleanup work I did earlier on the website that were copied to the html docs, and documentation on new features (like Wave64 and RF64 support, --preserve-modtime etc.) that were copied the other way. *flac.git patch*

Using FFmpeg, I can stream to a file on disk okay: c:\apps\ffmpeg\bin\ffmpeg.exe -f dshow -i audio="Line In (Realtek High Definition Audio)" -c:a libopus -ac 1 -b:a 32000 live.caf But, if I add Icey metadata, FFmpeg throws errors: c:\apps\ffmpeg\bin\ffmpeg.exe -f dshow -i audio="Line In (Realtek High Definition Audio)" -c:a libopus -ac 1 -b:a 32000^ -ice_name

I upgraded to Leopard (version 10.5 of OS X) a few weeks ago. Although I was a bit disappointed, but not surprised, to see that FLAC support isn't built natively into the OS, I was very happy to notice recently that Apple ships source code for a FLAC encoder and decoder codec component in /Developer/Examples/CoreAudio/AudioCodecs/ FLAC.xcodeproj. All that is necessary to build the

--- man/flac.1 | 25 +++++++++++++++++++++---- man/flac.sgml | 2 ++ 2 files changed, 23 insertions(+), 4 deletions(-) diff --git a/man/flac.1 b/man/flac.1 index fef4ded..3d7bd50 100644 --- a/man/flac.1 +++ b/man/flac.1 @@ -68,6 +68,9 @@ Prefix each output file name with the given string. This can be useful for enco \fB--delete-input-file \fR Automatically delete the input file after

On Sun, Oct 12, 2008 at 7:26 PM, Brian Willoughby <brianw at sounds.wa.com> wrote: > Is anyone here potentially up to the task of adding support for CAF > (the CoreAudio Format) into the flac command-line? This would > present minimal difficulty under OSX, due to the presence of the > CoreAudio API, but the real challenge would be to support CAF on Unix > and Windows -

Lots of comments throughout this one... On Jan 7, 2011, at 15:28, Declan Kelly wrote: > On Fri, Jan 07, 2011 at 02:22:51PM -0800, brianw at sounds.wa.com wrote: >> However, you should be aware that many modern producers use software >> to create their music, and when the software stores sound clips in >> MP3 format, what you end up with is music that sometimes looks like

Erik de Castro Lopo <mle+xiph@mega-nerd.com> wrote: > Martin Leese wrote: > > So what is "OggPCM"? I started this thread > > because I was puzzled why someone was > > changing a draft instead of the document > > itself. > > The original OggPCM was started by a person who really didn't > lnow what they were doing and wouldn't listen to

I have been tidying up the VorbisComment page in the XiphWiki. The problem with it was that it was a mixture of proposals and discussion of those proposals. This made it difficult for implementers to see what to implement. The problem section is: http://wiki.xiph.org/index.php/VorbisComment#New_ENCODER_field_name_proposal This is a mess, and all I could do was add attributions to the

Brendan Bolles wrote: > Hey everyone, according to Wikipedia's 4-year-old information, there is no > standard for putting metadata into an Ogg file. True. > That metadata must be > included in the codec. More generally, in a stream in the Ogg file. Codecs are streams, but so are things like Ogg Skeleton. Information about Metadata has been collected together in the Xiph Wiki

On 10/25/18, Rodger Combs wrote: > >> On Oct 25, 2018, at 12:47, Martin Leese <martin.leese at stanfordalumni.org> >> wrote: ... >> An alternative approach is to only define >> popular layouts. For more obscure layouts, >> such as 2.1 and Mid/Side, assume that the >> person doing the encoding knew what they >> put in, and so knows what will come

"Kurosawa, Taku" wrote: > Hi Martijn, > > Sorry for the late reply again, > The application we are preparing this time is not exactly similar to > Replaygain. > > Replaygain as we understand is something which normalize the loudness at > content provider side, but our application takes different approach. It is > designed to normalize the loudness at player

On 7/23/13, Silvia Pfeiffer <silviapfeiffer1 at gmail.com> wrote: > On 23 Jul 2013 15:17, "Martin Leese" <martin.leese at stanfordalumni.org> > wrote: ... >> Information about Metadata >> has been collected together in the Xiph Wiki >> at: >> https://wiki.xiph.org/Metadata > > That page is a bit outdated. It has CMML in it which we

Rodger Combs wrote: > I've run into some issues using Opus with source files in channel layouts > other than the default 8. For instance, 2.1 isn't supported, so I have to > either downconvert to 2.0 or upconvert to 5.1 (which usually involves adding > empty channels, which prevents the playback device from upconverting to the > native layout). > To address this,

I have been tidying up bits of the Wiki. This one is not clear cut, so I decided to seek advice. Also, I wasn't sure where to post this question, so defaulted to ogg-dev. Should Speex and CMML be removed from the Wiki Sidebar at: https://wiki.xiph.org/MediaWiki:Sidebar ? Many thanks, Martin -- Martin J Leese E-mail: martin.leese stanfordalumni.org Web: