Re: Package Scope Recommendations for File_Ogg
| From: | David Grant | Date: | Thu, 14 Aug 2003 13:12:06 +0000 |
| Subject: | Re: Package Scope Recommendations for File_Ogg | ||
| References: | 1 2 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-19727@lists.php.net to get a copy of this message | ||
Hi Stefan
>> > What files do you think exist "in the wild life"? Okay I could think
>> > of an ogg-file that contains some audiostreams following each other
>> > ... maybe if they switch bitrate inbetween or so. But I don't think
>> > this occurs very often. And if you have a look at mp3, mp3-players
>> > etc. you will see (as one example) that most programs don't handle
>> > intermediate bitrate-changes (if its not marked as vbr) correctly.
>> > It too hard to detect things like this correctly, to parse
>> > everything (if its a huge file) etc.
>>
>> I intend to have a chat with some of the Ogg developers (if I can find
>> them on an IRC channel) to see if they can point out "unusual"
>> physical streams, such as a mixture of Vorbis and Speex, for example.
>> Personally I can't really see the point of concurrant streams unless
>> it forms part of a audio or video stream.
>
> Have a try via irc to irc.xiph.org for a chat.
That was my intended port of call. :)
> Well I could imagine having one video and let's say 2 audio-streams -
> maybe German / English or something. Also there might be features
> like on a DVD:
> Audio-channel 1: Sound (e.g. from sports)
> Audio-channel 2: Sounds + comments
> Audio-channel 3: Just plain comments
>
> Or whatever. If that exists that often in real life depends. But
> afaik it CAN be.
There's no dispute that it can be done. According to the Ogg
specification, that is. The real world example is the one to track down,
though. :)
>> > Using libvorbis etc. directly via a pecl-interface, as proposed by
>> > Patrick, doesn't seem a good solution for me. Okay, it would save
>> > you reinventing the wheel. But if it's possible to solve this
>> > problem in "clean" php (and without taking too much amount of memory
>> > and time for parsing) I would favor a php-pear- and not a
>> > pecl-class. With a pecl-solution you are dependent on libvorbis etc.
>>
>> I've pointed out that both solutions could be offered. Since I've no
>> experience in C, I suggest someone else might like to take a look at
>> it.
>
> How do you intend to do that?
I don't. I'll do the PEAR implementation, and someone else can do the
PECL one. :)
> Take it eeeassssyyyyy *g*
Not a problem!
Regards,
David