On Mon, Jun 12, 2006 at 09:58:52PM +0200, Mark Washeim wrote: > Well, I wound up solving this problem by checking out the source and > compiling afresh. The above problem seems to be solved in the most > recent release published to sourceforge. (...) > Anyway, it appears that I should close the bug with a note, but that > seems silly if the maintainer isn't on it? Since he wrote most of the > fixes, I'm not sure what the procedure is?
I'd like to see this issue fixed, but without maintainer feedback I'm reluctant to introduce a new upstream version as long as we don't have handle on what the problem actually is. Therefore, if it's still possible for you, sending in a small sample file for debugging would be great. I failed to reproduce the bug so far, but that's possibly due to me not having access to a DV source. I got some .movs out of dvgrab using raw DV input and the --stdin switch, but those were all NTSC. I guess yours are PAL? Regards, Daniel. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
