Re: ov_open_callbacks takes so much time to open 210 MB OGG file
Pavel Nikitenko <[email protected]> Mon, 10 Dec 2012 16:05:22 +0100
| Newsgroups | gmane.comp.multimedia.ogg.vorbis.general |
|---|---|
| Message-ID | <[email protected]> |
Thanks for the info. I will try to reproduce the bug with use of: libvorbis-1.3.3\examples\vorbisfile_example.c . > ogginfo complained that streams were not being terminated (no EOS > page). That makes the streams invalid, but should not trigger that > behavior in vorbisfile. ogginfo also complained about 'garbage > between pages' at one point, but I've not verified yet that report is > correct. This, also, should not trigger the behavior you're seeing. I am not sure what that means. I just try to append new OGG file to existing OGG file. Do you think, there is a bug, that the new OGG file is not appended into existing OGG file correctly? At correct position? Pavel On 10.12.2012 14:04, [email protected] wrote: > On Mon, Dec 10, 2012 at 6:22 AM, Pavel Nikitenko <[email protected]> wrote: >> Should I user rather Opusfile or Oggz library? >> >> >>> Well— files with a lot of chaining fundamentally take a bit longer to >>> open. >> Quite long time to open. In minutes. Around 15 minutes. > Goodness gracious. That's absolutely wrong :-) > > I grabbed the file and looked at it; 52 links which is a lot, but not > 15 minutes a lot. Should be maybe 150ms at worst. I've not had time > to look at what is happening beyond a quick run through the various > inspection tools. > > ogginfo complained that streams were not being terminated (no EOS > page). That makes the streams invalid, but should not trigger that > behavior in vorbisfile. ogginfo also complained about 'garbage > between pages' at one point, but I've not verified yet that report is > correct. This, also, should not trigger the behavior you're seeing. > > So... no news quite yet. I do plan to have a more detailed look at it. > > Monty