WebM support

[stopsatgreen]

Now that WebM is in FFmpeg 0.6, can we look forward to seeing it in
the next release of Perian? I think it's a good opportunity as Apple
have announced no plans to include it in Safari, to provide the option
for people who want it. That's what I think Perian is great for.

Note: there's an earlier thread on this subject, but it appears to be
locked.

[Christopher Forsythe]

I don't think threads get locked..

Anyhow, so do you have an actual need for webm support? 

Chris

--
You received this message because you are subscribed to the Google Groups "perian discussion" group.
To post to this group, send email to perian-...@googlegroups.com.
To unsubscribe from this group, send email to perian-discus...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/perian-discuss?hl=en.

[Alexander Strange]

WebM is implemented in SVN, though I can't remember if all the test
vectors pass. I'm worried about files that use altref frames in VP8
too.

On Aug 24, 12:30 pm, Christopher Forsythe <ch...@growl.info> wrote:
> I don't think threads get locked..
>
> Anyhow, so do you have an actual need for webm support?
>
> Chris
>
>
>
> On Tue, Aug 24, 2010 at 11:24 AM, stopsatgreen <pgass...@gmail.com> wrote:
> > Now that WebM is in FFmpeg 0.6, can we look forward to seeing it in
> > the next release of Perian? I think it's a good opportunity as Apple
> > have announced no plans to include it in Safari, to provide the option
> > for people who want it. That's what I think Perian is great for.
>
> > Note: there's an earlier thread on this subject, but it appears to be
> > locked.
>
> > --
> > You received this message because you are subscribed to the Google Groups
> > "perian discussion" group.
> > To post to this group, send email to perian-...@googlegroups.com.
> > To unsubscribe from this group, send email to

> > perian-discus...@googlegroups.com<perian-discuss%2Bunsubscribe@go oglegroups.com>
> > .

[Ryan Thompson]

Have you been able to watch a webm video yet with perian? As you
know webm is a subset of matroska. After reading your FAQ, I'm
interested to know also if you saw similar slowness in webm as you saw
with matroska?

[Chris Forsythe]

I'm interested in finding out if anyone actually needs webm, or if it's just a curiosity. We've seen a lot of attention on this one, with very little substance from what I can tell.

We need to find someone actually using it to address Alexander's and your concerns. I'd assume that you do not actually use webm, since you'd already know the answer to your question.

Chris

> To unsubscribe from this group, send email to perian-discus...@googlegroups.com.

[Ryan Thompson]

Hi Chris,

On Sep 25, 10:59 pm, Chris Forsythe <ch...@growl.info> wrote:
> I'm interested in finding out if anyone actually needs webm, or if it's just a curiosity. We've seen a lot of attention on this one, with very little substance from what I can tell.

Well, I use WebM (though my situation may be unique). It's a younger
technology, so it being less prevalent than say flv or avi doesn't
mean its not in use.

> We need to find someone actually using it to address Alexander's and your concerns. I'd assume that you do not actually use webm, since you'd already know the answer to your question.

As for knowing the answer to my question... not really, that's why I
asked it. It seems that the claim was the Matroska files need to be
parsed completely, which seems to me as though the implementation is
not done correctly. Location of key frames needed for seeking should
be made available in the cues element. According to your FAQ,
Quicktime needs to know the location of every frame, something smells
wrong about that. I'm really interested to know, why does the entire
file need to be parse before playback can happen?

[Alexander Strange]

On Sep 27, 9:21 am, Ryan Thompson <ryanthomp...@google.com> wrote:
>  According to your FAQ,
> Quicktime needs to know the location of every frame, something smells
> wrong about that.

I wrote that answer, I'm sorry you apparently don't believe it. That's
how QT7 works.

[C.W. Betts]

QTX not need to know about each and every frame, but there currently is no plug-in API for QuickTime X (it uses a QuickTime 7 wrapper to access QuickTime 7 codecs like Perian).