> Finally verified. Misbehaviour confirmed. It cannot be fixed easily (read:
> not without doing terryfing hacks or without rewriting almost all related
> code). The "solution" that I'll adopt for 1.1.0 is to emit a warning
> when -C is used with uncompatible files like vobs.
> Maybe a _BYTE_-based range support will be added, that's feasible right now,
> but I'm doubtful on it's utility for users.
Damn, that's bad news. :-(
I was under the impression (possibly mistaken) that it used to work
properly a while ago. Is that the truth or am I wrong?
-C used to work (and it's supposed to never stop working) for some containers,
mosto notably AVIs. The key point is that transcode, so tcextract, can detect
easily frame boundaries when dealing with AVIs, but not yet with MPEGs/VOBs.
Any suggestions on how to work around this issue? (and still use transcode)
Dunno yet, I'm sorry. I've some ideas[1] on this topic, the problem is -as usual- time. :(
Maybe a libavformat-powered tcextract in 1.1.0 could help? I'm not shore.
Is there a bugzilla site where I can submit a bug report?
Not yet :)
It would be really nice. Maybe opening a project on berlios or something... We'll see.
[1]: Shortly: revamp mpeglib (http://fromani.exit1.org ), extending it to
support frame extraction (isn't that hard, it's matter of buffering and MPEG
packet payload inspection), integrate it into tc :)
Best regards,
--
Francesco Romani
