Francesco Romani wrote:
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?
Any suggestions on how to work around this issue? (and still use transcode)
Is there a bugzilla site where I can submit a bug report?
Thanks,
--
Florin Andrei
http://florin.myip.org/
