similar to: Ogg as container format

I'm forwarding this to the vorbis list FYI. I'll also forward the reply. Marshall -------- Original Message -------- Subject: Re: File formats (RE: MP4 Player Available for Download) Date: Thu, 15 Mar 2001 10:29:20 -0500 From: Marshall Eubanks <tme@21rst-century.com> Reply-To: tme@21rst-century.com Organization: Multicast Technologies To: philippe.gentric@philips.com CC:

>RFC822 is HISTORIC: please refer to RFC2822 instead. > >While UTC is sufficient for human beings, but not necessarily accurate >for machines, because of the leap year adjustment. TAI is the You mean leap seconds, not leap years. Since 1972, UTC == TAI modulo some number of seconds. Leap Seconds are announced officially by the IERS http://www.iers.org/iers/products/eop/leap.html

I recall reading that all MPEG AAC software has different and incompatible file formats , because this is a condition set by the MPEG AAC technology licensing authority. Some kind of yet-another-anti-piracy-measure, the idea probably being that users of different software can not swap their files. I picked up this a while ago when following AAC software development, but can't remember exactly

>http://www.m4if.org/resources.html > See also http://www.mpeg4ip.net/ which has a lot of open source and available MPEG-4 code available. The licensing issue is still a mess, although they hope to make it at least coherent "real soon now". Use at your own risk. BTW, there is no MP4. The equivalent audio codec is the Dolby AAC. Regards Marshall Eubanks >appears it's

Here in the uk, to get a patent on anything, you have to prove that the patent is not obvious and that there is no prior art. If there is prior art, then a patent cannot be given, this is why people patenting stuff have to keep it a secret until they actually have the patent, otherwise it is considered to have been released into the public domain. Once something is in the public domain, nobody

David Jagu (1): meson: fix typo in libdrm_intel Geert Uytterhoeven (18): util: improve SMPTE color LUT accuracy util: factor out and optimize C8 SMPTE color LUT util: add support for DRM_FORMAT_C[124] util: store number of colors for indexed formats util: add SMPTE pattern support for C4 format util: add SMPTE pattern support for C1 format util: add

On 7/16/15, Martin Leese <martin.leese at stanfordalumni.org> wrote: > Martijn van Beurden wrote: >> I would propose: 0000-0111 : (number of independent channels)-1. >> The channel order is defined through the >> WAVEFORMATEXTENSIBLE_CHANNEL_MASK vorbis comment, if defined. If >> no WAVEFORMATEXTENSIBLE_CHANNEL_MASK is present, the channel >> order follows

I've been encoding my CD collection with mostely great results. However, there is the oddball that doesn't sound as it should (mostely I get flanging effects on high-frequency sounds like cymbals). I've seen people upload samples and post it here so that the developers might have a look at them. Now I don't have any online space. Is there an ftp site or something I can upload

(hello all, this is my first writing. so please bear with me if I'm wrong anywhere.) orry to break too lately, but how is the RTP payload submission is going? could we see the new payload at March IETF? I agree that it would be fairy straightforward to make an RTP payload for ogg vorbis, assuming raw packets, AFAIK. using physical bitstream is, in this case, not adequate by the reasons in

There is some time now that I reported this issue on the bugtracker: https://roundup.ffmpeg.org/roundup/ffmpeg/issue1325 And this guy, jbr, kindly created a patch that solved the problem. What is needed now for the patch to be included in the SVN? About his patch, there is a remap table that maps the channel order from SMPTE order to Vorbis order. What is this SMPTE order? Vorbis specification

lvqcl wrote: ... > From FLAC 1.2.1 documentation: > > 0000-0111 : (number of independent channels)-1. Where defined, the channel > order follows SMPTE/ITU-R recommendations. The assignments are as follows: > 1 channel: mono > 2 channels: left, right > 3 channels: left, right, center > 4 channels: left, right, back left, back right > 5 channels: left, right, center,

Hey, all. I'm looking -- if possible -- for a decent, multi-platform soft-phone. Specifically, Linux and Windows; that way, I'll go through the same issues my end users do. I've noticed a couple (e.g., minisip, which seems abandoned, and sip-communicator, which, honestly, is probably a great IM client, but has a confusing interface for actual phone calls). So I'm wondering if

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

Dear All I'm having problem with some script which worked a few months ago (on a different computer that might well have had a different version of R installed, so perhaps it has to do with the old version of R?): library(reshape) Loading required package: plyr > tble.data <- melt.array(interp, varnames=c("tme","lon","lat")) > > allyrs.interp <-

Martin Leese wrote: > 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 channel order might not follow SMPTE/ITU-R > recommendations, so this proposed wording > seems misleading to me. But this text describes only those 4 bits in frame header. IMHO

alpha. (that about sums it up) Will encode and play back via an sdp file and multicast on one computer (over the net if you transfer the sdp file over by hand). rc/rtenc3 and src/rtdec3 are in the style of encoder/decoder_example ...so this means you MUST edit it them to suit your system. For example, I specify my rtenc3 to multicast just on eth1 (to avoid pissing off my cable supplier on

Sorry for starting another topic, this is actually a reply to Segher's post on Sun Oct 22 on the 'mdct question' topic. I wasn't subscribed properly and so I didn't get email confirmation and thus can't add to that thread. So Segher, if the equation is indeed what you say it is, then replacing mdct_backward with this version should work, but it doesn't. Am I applying

HOgg 0.3.0 Released ------------------- The HOgg package provides a commandline tool for manipulating Ogg files, and a corresponding Haskell library. HOgg is in hackage, or on the web at: http://www.kfish.org/~conrad/software/hogg/ This is the second public release. The focus is on correctness of Ogg parsing, production and editing. The capabilities of the hogg commandline tool are roughly on

HOgg 0.3.0 Released ------------------- The HOgg package provides a commandline tool for manipulating Ogg files, and a corresponding Haskell library. HOgg is in hackage, or on the web at: http://www.kfish.org/~conrad/software/hogg/ This is the second public release. The focus is on correctness of Ogg parsing, production and editing. The capabilities of the hogg commandline tool are roughly on

I'm a mathematician and programmer working on experimental surround sound techniques. Some of the ideas I'm working on require dozens of channels. These channels are often highly correlated and are very well suited to compression. I'm new to Vorbis. Does it attempt to address such issues? Thanks, --Richard --- >8 ---- List archives: http://www.xiph.org/archives/ Ogg project