Daniel Kobras wrote:
tag 359863 + moreinfo
thanks
On Wed, Mar 29, 2006 at 02:46:46AM -0700, Mark Washeim wrote:
I've been testing for the past 3 months and... dv 1394 captured material
(dvgrab 1.7 and 1.8) where quicktime is the format written but not able
to be read. Kino, for instance reports the file is not readable.
Similarly,
lqt_transcode reports:
quicktime_open: error in header
Can you please send a mail with a (preferably small) sample file
attached to this bug report? (I know Steve has already asked for it
before, and probably gotten a sample from you, but it wasn't public.)
Also, what's the output of 'file sample.mov' on one of the failing
quicktime movies?
Regards,
Daniel.
Hi Daniel,
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.
However, it simply reveals a bunch of others, not entirely
libquicktime's problem, but...
I've tried to contact Gerd Knorr (who I believe recently changed his
name) since he's upstream and debian maintainer. In any case, he also
lives in berlin as I do. No dice in the past months.
What I discovered after studying the source, is that packages like pdp
(pure data's video processing library) are actually broken. I've done
the 'minimal' fixes required for pdp and pidip to function, but only
basic reading and writing. The api's changed enough and the authors (Tom
Schouten and Yves Degoyan) seem to be unwilling to update. I'm not sure
I see their point, since the api refactoring was cleanly done and it's
been developing for over 2 years. Perhaps it's a communication issue?
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 wish I had the time, I'd take over. Sadly, I finally solved the bounty
issue by doing the prototyping with max and jitter on a bloody mac. Very
humiliating, but I didn't have the time to refactor all the code I needed.
Let me know what I should do.
Thanks and regards
Mark
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
