similar to: Flac multi channel

Don't overlook the FLAC in Ogg container solution. That's established as a standard for some time now, as far as I know, and would probably be better than a new, proprietary multi mono bundle. I haven't used it myself, but people have been talking about it for a while, and I believe that some "FLAC" users are actually working with FLAC in Ogg container files. Brian

This could make sense indeed. I suppose this is not a libFlac feature and that I should end up using libogg and or adding myself basic ogg support in order to support that ? Thanks ! 2017-01-28 7:37 GMT+01:00 Brian Willoughby <brianw at audiobanshee.com>: > Don't overlook the FLAC in Ogg container solution. That's established as a > standard for some time now, as far as I

I see :( That what I would call a good struct size optimisation. Please tell me there was another reason behind this being only 3 instead of 8 or 16 bits, right ? 2017-01-25 18:30 GMT+01:00 Tor-Einar Jarnbjo <tor-einar at jarnbjo.name>: > Hello Olivier, > > the limitation is in the file format itself, as the number of channels is > encoded in a 3 bit field in the streaminfo

Thanks everybody for their answer. This is quite unfortunate for me, but hey, that's life. I will probably end up doing some multi mono bundle similar to what Protools did back in the days with its .L .R files ++ Le 26/01/2017 à 18:58, Martin Leese a écrit : > Federico Miyara wrote: > ... >> The file format allows some unused fields for future use, such as the >> padding

e deleflie <edeleflie at gmail.com> ... > ok, I do realise that the extending the maximum channel count may be > difficult ... there's gotta be a way to do it though. Perhaps a comparison of the FLAC structure with that of Vorbis will help. Within a FLAC stream the audio is split into blocks which are grouped (interleaved). But within each block the eight channels are chained

Hi Guys, I know that FLAC format is currently limited to 8 channels but I was wondering if this hard limitation of the format or if it can be easily circumvented if the flac library is compiled with other settings and/or the software using it don't mind it Thanks ! -- Olivier Tristan Research & Development www.uvi.net

Brian Willoughby <brianw at sounds.wa.com> > Isn't there a standard option to place FLAC data within an Ogg > container? I don't use it myself, but I understand that it is quite > popular. Would it be possible to interleave multiple FLAC blocks > this way? In other words, can Ogg suffice as the second level of > grouping that you refer to? Etienne was asking for

Op 03-12-14 om 16:48 schreef Olivier Tristan: > Looks like I've missed the talk about this regression introduced in 1.3.1.

Per https://xiph.org/flac/faq.html#general__channels currently FLAC supports 1 through 8 channels. This is fine for 5.1 surround sound (6 channels). But some of the newer surround sound systems can handle many more channels. Is it still convenient to have all of the audio channels in one file for, say, a 16 channel audio track? I don't know much about the history of FLAC. How did this

lvqcl wrote: > Martin Leese wrote: >> Why place restrictions on which speaker a >> user can use? ... >> Finally to answer your question, for a >> single-channel file, FLAC should accept any >> one of the three masks 0x00000001 (FL), >> 0x00000002 (FR), 0x00000004 (FC), plus any >> one of the 15 other single-bit masks, plus zero. Please note that the

lvqcl wrote: > Martin Leese wrote: >> Note that the channel order may not be defined. > > IMHO it doesn't matter in this place of documentation (which describes > default channel assignments for FLAC). Your proposed wording was: 0000-0111 : (number of independent channels)-1. The channel order follows SMPTE/ITU-R recommendations. The assignments are as follows: The

Early this past week, Miroslav Lichvar suggested for me: > Ok, you need 0.04% improvement, that should not be a problem. Try > flac --lax -e -p -l 32 -r 10 --no-padding Thank you again, Miroslav. I tried that, and it took almost two full days (surprisingly, Windows ME stayed up that long without crashing) to re-encode the entire set on my 266-MHz machine. After all, in the help file

On 6/4/12, Benjamin M. Schwartz wrote: > On 06/04/2012 04:08 PM, Martin Leese wrote: ... >> The optimal solution is described at: >> https://wiki.xiph.org/XMLEmbedding > > As that page says, "This page is for development of a specification for > embedding XML streams in Ogg.". "XML streams" are not simply XML > documents. They are _temporally

It's certainly best to honor what the specification says. My assumption is that a "stream" could also be a continuous broadcast, not just a file. With a hypothetical server streaming FLAC bitstreams, I would assume that the most recent STREAMINFO is valid until another one comes along. If you're writing a file player, then perhaps you can trust the spec and assume

Brian Willoughby <brianw at sounds.wa.com> wrote: > Hello all, > > Is anyone here potentially up to the task of adding support for CAF > (the CoreAudio Format) into the flac command-line? ... > I've already made some recordings > that are so long that they cannot be uncompressed from FLAC to WAV or > AIFF because they would exceed 4 GB - the maximum file size for

If processing time is not a big factor -- say, I could put up with four to six times the duration of compressing at -8 -- what command-line settings could one use to get even more compression? I have a case where the FLACs encoded at -8 are about 653.3 MB, but the set comes with artwork whose jpegs are 50.5 MB (I tried zipping the jpegs, realizing it would do very little, and the zip file

"Benjamin M. Schwartz" wrote: > On 06/04/2012 10:50 AM, Oleksij Rempel wrote: ... >> XMP fits to our needs, but it >> looks like there is still no ready documentation about muxing XML to ogg. > > Well then you've already solved the problem. Just store the XMP in a > VorbisComment field named "XMP" (or whatever name you like). This suggestion falls

More specifically, about this patch: http://git.xiph.org/?p=flac.git;a=commitdiff;h=70b078cfd5f9d4b0692c33f018cac3c652b14f90 I downloaded the latest code from git (flac-70b078c), disabled all SSE optimizations in the code and compiled it (GCC 4.8.2). This patch doesn't change FLAC output. Either gcc is too smart and optimizes this new code back to the old, or this fix is MSVS-specific. Or

This patch removes FLAC__lpc_restore_signal_16_intrin_sse2(). It's faster than C code, but not faster than MMX-accelerated ASM functions. It's also slower than the new SSE4.1 functions that were added by the previous patch. So this function wasn't very useful before, and now it's even less useful. I don't see a reason to keep it. -------------- next part -------------- A

Hi, I have posted this three times to the flac-dev, vorbis-dev, and ogg-dev mailing lists. I wanted to see what code there was currently to support Ambisonics. So I downloaded the code from the xiph download page for libogg-1.1.3, libvorbis-1.1.2, vorbis-tools-1.1.1 and flac-1.1.4, but wasn't able to find anything. If it exists then I missed it, so could somebody please point me to it.