Re: File_Vorbis Latest...
| From: | Stefan Neufeind | Date: | Tue, 12 Aug 2003 22:48:34 +0000 |
| Subject: | Re: File_Vorbis Latest... | ||
| References: | 1 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-19608@lists.php.net to get a copy of this message | ||
I wouldn't call myself "too experienced" with pear yet. But if you
might be interested in my 2 cents anyway:
Refering to
http://www.vorbis.com/faq.psp#names
"Ogg is the name of Xiph.org's container format for audio, video, and
metadata.".
So wouldn't, refering to meta-data, it be a File_Ogg-package? But
since we're also talking about Vorbis-specific details (e.g.
Bitrates) okay. Just thought off Ogg Theora or even Speex which also
use an Ogg container. Wouldn't abstracting a general ogg-part for
meta-data make sense? If you have a look at the ogginfo-output it
says that there was a "vorbis stream" found. Maybe think of
multichannel-audio (English/German/...) or audio/video and similar.
Then having a File_Ogg to handle all streams inside the file would
make sense.
Back to your File_Vorbis:
Would it be possible to also display the length or the stream and
maybe the "total data length" (see ogg info) for that stream?
Looking at the source without going into too much technical detail
looks fine for me. Didn't find a necessity to criticise anything.
Generally I'd love to see a package to handle ogg/vorbis-files. But
maybe give it a thought about abstracting the ogg-container in
general and also aming to support Theora, Speex and similar in the
future. This would mean a future-wise and extensible setup without
braking BC or reinventing the wheel.
Stefan
On 13 Aug 2003 at 1:21, David Grant wrote:
> Having read the recent (and probably ongoing) thread on the proposal
> of new packages, can someone experienced please comment whether or not
> it is worth continuing to code a File_Vorbis package? Is it
> considered of value to the majority of PHP (or rather, PEAR) users?
>
> Latest sources are here:
>
> http://jalapeno.dyndns.org/File_Vorbis/
>
> If it is deemed that development should continue, does anyone have any
> pointers regarding style, consistency with PEAR, etc.?