similar to: Testing 24-bit full-scale deflection streams fails

On 2007-09-15, Josh wrote: > --- Daniel Aleksandersen <aleksandersen+xiphlists@runbox.com> wrote: > > Hi list, > > > > I am trying to compile and install flac 1.2. I $ ./configure(d) and $ > > > > make(d) without any errors or warnings. However I get the following > > error > > > > when $ make check(ing): > > > Testing 24-bit

--- Daniel Aleksandersen <aleksandersen+xiphlists@runbox.com> wrote: > Hi list, > > I am trying to compile and install flac 1.2. I $ ./configure(d) and $ > > make(d) without any errors or warnings. However I get the following > error > when $ make check(ing): > > > Testing 24-bit full-scale deflection streams... > > fsd24-01 (--channels=1 --bps=24 -0

On 19/09/2007, Daniel Aleksandersen <aleksandersen+xiphlists@runbox.com> wrote: > On Wednesday 19. September 2007 19:02:06 Ian Malone wrote: > > Daniel Aleksandersen wrote: > > > Attached is a much improved version of yesterday's draft. Introducing > > > the audio:collection:artwork element to deal with album cover graphics > > > and such. > >

Running the basic (--disable-thorough-tests) test suite, I get these failures round-trip test (rt-1-24-111.raw) encode... Segmentation fault (core dumped) ERROR FAIL: ./test_flac.sh fsd24-01 (--channels=1 --bps=24 -0 -l 16 --lax -m -e -p): encode...ERROR during encode of fsd24-01 FAIL: ./test_streams.sh on alpha and amd64. By contrast, i386 is fine. (All OpenBSD/4.2.) Could be a generic LP64

Hi list, I have been trying to get the new file extension for Ogg FLAC (.oga) to work with Amarok. But it does not look to be possible due to limitations in the xine and gstreamer engines. Maybe the move to .oga was prematurely? I have done some testing with other players?including Banshee, Quod Libet, and others?but have not had any success with playing the .oga files. Only player I have

The biggest problem with Vorbis comments are too loose specifications and too little standardisation. Another problem is attribution of involved parties. Currently only the ARTIST field name is supported in software. More standardised field names need to be worked out for organisations and persons involved in the production of the recording. See:

Hi list, I would really like to see support for .cda as input files. The cda format is the one used on regular audio CDs. Support for this format would make it even easier to encode to FLAC from CDs -- Daniel Aleksandersen

On 2007-09-13, Brian wrote: > On Sep 13, 2007, at 12:08, Daniel Aleksandersen wrote: >> I would really like to see support for .cda as input files. The cda >> format >> is the one used on regular audio CDs. >> >> Support for this format would make it even easier to encode to FLAC >> from CDs > > You are mistaken, Daniel. Regular audio CDs do not use

On Tuesday 18. September 2007 14:32:45 Ian Malone wrote: > On 11/09/2007, Ian Malone <ibmalone@gmail.com> wrote: > > On 11/09/2007, Daniel Aleksandersen <aleksandersen+xiphlists@runbox.com> wrote: > > > On Tuesday 11. September 2007 01:34:35 Ian Malone wrote: > > > > I'd be interested which ones. DC is a bit nebulous, but that gives > > >

Daniel Aleksandersen <aleksandersen+xiphlists@runbox.com> wrote: ... > Since the URI attribute can describe locations (URLs), the format could work > as a RDF document; being an external resource describing external content. > But of course the metadata would be in the Ogg stream-container-thingy > (...somehow. help. input?) in the case of the Ogg format. As this would be XML, I

On 10/09/2007, Daniel Aleksandersen <aleksandersen+xiphlists@runbox.com> wrote: > On Monday 10. September 2007 23:39:50 Silvia Pfeiffer wrote: > > 2) we need a XML annotation format for audio - in particular for music > > - that is more structured than vorbiscomment (and this probably > > applies to video, too) > > It would have to apply to any kind of media. >

Daniel Aleksandersen wrote: > Hi again list, > > Attached is a much improved version of yesterday's draft. Introducing the > audio:collection:artwork element to deal with album cover graphics and > such. > > Hi, One thing still missing is a subject/synopsis description. This would have little value for pop music, but for tracks from opera, tv programmes and films it

On 11/09/2007, Daniel Aleksandersen <aleksandersen+xiphlists@runbox.com> wrote: > On Tuesday 11. September 2007 01:34:35 Ian Malone wrote: > > Daniel Aleksandersen wrote: > > > By the way, I have bee discussing Dublin Core ('DC') with the > > > developers of the Atom 1.0 specification. It seams the reason they > > > created atom:rights instead of

Hi again Ivo and the Xiph ogg-dev emailing list, This email is meant to present two blockers for continued development of the XML based Multimedia Metadata Format (M3F) (MDMF page in the wiki). This format is intended to replace comments as a way of including descriptions of metadata contained in the Ogg container format. For instance title, production year, actors, producers, and so on for

On Saturday 08. September 2007 16:12:08 Ivo Emanuel Gon?alves wrote: > Thanks a lot for taking an interest and trying to work with metadata > in Ogg. There have been efforts before, but they have seemly gone > nowhere. I've heard there's a need for a serious metadata framework > in Ogg, albeit me personally would find no use for it. Then again, > the Web's moving to a

Hi ogg-dev list, I have improved the format formally known as Media Description and Metadata (MDMF) for the Ogg Container Format. Please have a look at the M3F page in the wiki http://wiki.xiph.org/M3F The format have been simplified and designed primarily with audio and movie recordings in mind. The old version focused on providing separate tools for each media type, were the new version

Hi ogg-dev list, After discussing the [lack of] metadata standards on the irc://irc.freenode.net/#Vorbis channel yesterday I figured I had to contribute to this process. Attached is a sample XML formatted metadata sheet describing a song; and shows off other media type elements as well. How this is to be embedded in the OGG container is not my field. I have only spent a couple of hours

What I've gotten out of this discussion so far: 1) we need to introduce a means in which to do captions; this could be done through adding a "caption" element to CMML, or in another time-continuous annotation format; so far I am not sure which would be the better way 2) we need a XML annotation format for audio - in particular for music - that is more structured than vorbiscomment

Daniel Aleksandersen wrote: > By the way, I have bee discussing Dublin Core (?DC?) with the developers of > the Atom 1.0 specification. It seams the reason they created atom:rights > instead of using dc:rights were just about what I thought it was: They > though DC was too loosely defined. Their own atom:rights element were > designed to more clearly define what the element

Hi again list, I have given the matter of supporting .cda as input format some more thought. What I wanted was an easier way to do drag 'n' drop music files from CDs onto the local system and then have those files encoded with FLAC. As of now most operating systems displays files on CDs as .cda. (Which has later been clarified not to even be a format.) I think that what I actually