Bug#359863: BOUNTY: files created by libquicktime0 not opened with same
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]
Bug#359863: BOUNTY: files created by libquicktime0 not opened with same
tag 359863 + patch
thanks
On Tue, Jun 13, 2006 at 01:49:59PM +0200, Daniel Kobras wrote:
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?
Scratch that. I do see what's going wrong here. The generated .movs are
perfectly valid, but the Debian package of libquicktime currently ships
without decoding support for DV: Nowadays, the libdv plugin is only used
for encoding. DV decoding is supposed to be handled by ffmpeg, but this
plugin isn't built in Debian so far. The attached patch adds the
necessary bits and pieces.
Gerd, unless you object, I'd like to upload these changes within the
next days.
Regards,
Daniel.
diff -u libquicktime-0.9.7/configure libquicktime-0.9.7/configure
--- libquicktime-0.9.7/configure
+++ libquicktime-0.9.7/configure
@@ -25678,13 +25678,18 @@
#include ffmpeg/avcodec.h
#include stdio.h
+#ifndef STRINGIFY
+# define STRINGIFY(x)STRINGIFY1(x)
+# define STRINGIFY1(x) #x
+#endif
+
int main()
{
FILE * output;
if(LIBAVCODEC_BUILD $AVCODEC_BUILD )
return -1;
output=fopen(avcodec_version, w);
-fprintf(output, LIBAVCODEC_VERSION);
+fprintf(output, STRINGIFY(LIBAVCODEC_VERSION));
fclose(output);
return 0;
}
@@ -25858,13 +25863,18 @@
#include ffmpeg/avcodec.h
#include stdio.h
+#ifndef STRINGIFY
+# define STRINGIFY(x)STRINGIFY1(x)
+# define STRINGIFY1(x) #x
+#endif
+
int main()
{
FILE * output;
if(LIBAVCODEC_BUILD $AVCODEC_BUILD )
return -1;
output=fopen(avcodec_version, w);
-fprintf(output, LIBAVCODEC_VERSION);
+fprintf(output, STRINGIFY(LIBAVCODEC_VERSION));
fclose(output);
return 0;
}
@@ -25943,13 +25953,18 @@
#include ffmpeg/avcodec.h
#include stdio.h
+#ifndef STRINGIFY
+# define STRINGIFY(x)STRINGIFY1(x)
+# define STRINGIFY1(x) #x
+#endif
+
int main()
{
FILE * output;
if(LIBAVCODEC_BUILD $AVCODEC_BUILD )
return -1;
output=fopen(avcodec_version, w);
-fprintf(output, LIBAVCODEC_VERSION);
+fprintf(output, STRINGIFY(LIBAVCODEC_VERSION));
fclose(output);
return 0;
}
diff -u libquicktime-0.9.7/debian/changelog libquicktime-0.9.7/debian/changelog
--- libquicktime-0.9.7/debian/changelog
+++ libquicktime-0.9.7/debian/changelog
@@ -1,3 +1,12 @@
+libquicktime (1:0.9.7-0.5) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * acinclude.m4, configure: Fix compile error in ffmpeg test program.
+ * debian/control: Build-depend on libavcodec-dev to reinstate DV
+decoding support. Closes: #359863
+
+ -- Daniel Kobras [EMAIL PROTECTED] Tue, 13 Jun 2006 15:36:59 +0200
+
libquicktime (1:0.9.7-0.4) unstable; urgency=medium
* Non-maintainer upload.
diff -u libquicktime-0.9.7/debian/control libquicktime-0.9.7/debian/control
--- libquicktime-0.9.7/debian/control
+++ libquicktime-0.9.7/debian/control
@@ -3,7 +3,7 @@
Priority: optional
Maintainer: Gerd Knorr [EMAIL PROTECTED]
Standards-Version: 3.6.2
-Build-Depends: debhelper (= 3.0), libgtk2.0-dev ( 2.4.0), libpng12-0-dev |
libpng-dev, libjpeg-dev, libraw1394-dev, libavc1394-dev, libvorbis-dev
(=1.0.1-1), libxaw7-dev, libsdl1.2-dev, libpopt-dev, libdv4-dev, libxv-dev
+Build-Depends: debhelper (= 3.0), libgtk2.0-dev ( 2.4.0), libpng12-0-dev |
libpng-dev, libjpeg-dev, libraw1394-dev, libavc1394-dev, libvorbis-dev
(=1.0.1-1), libxaw7-dev, libsdl1.2-dev, libpopt-dev, libdv4-dev, libxv-dev,
libavcodec-dev
Package: libquicktime0
Architecture: any
only in patch2:
unchanged:
--- libquicktime-0.9.7.orig/acinclude.m4
+++ libquicktime-0.9.7/acinclude.m4
@@ -381,13 +381,17 @@
AC_TRY_RUN([
#include ffmpeg/avcodec.h
#include stdio.h
+#ifndef STRINGIFY
+# define STRINGIFY(x)STRINGIFY1(x)
+# define STRINGIFY1(x) #x
+#endif
int main()
{
FILE * output;
if(LIBAVCODEC_BUILD $1)
return -1;
output=fopen(avcodec_version, w);
-fprintf(output, LIBAVCODEC_VERSION);
+fprintf(output, STRINGIFY(LIBAVCODEC_VERSION));
Bug#359863: BOUNTY: files created by libquicktime0 not opened with same
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. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#359863: BOUNTY: files created by libquicktime0 not opened with same
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]
Bug#359863: BOUNTY: files created by libquicktime0 not opened with same
Package: libquicktime0 Version: 1:0.9.7-0.4 Severity: grave Justification: renders package unusable *** Please type your report below this line *** Hello, 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 pure data's PDP library reports: pdp_qt: ERROR: not a quicktime file I've only been able to get transcoded files to open, for instance mencoder test.mov -o other.mov -oac pcm -fafmttag 0x736f7774 -ovc lavc -lavcopts vcodec=mjpeg -ffourcc jpeg Will be read fine. I must be able to read dv streams and would be willing to pay 500 Euro to solve this one in the next short (how about week) while. I've tried to locate the header writing (src for AMD 64) and realized that even getting it fixed would still leave me with a considerable maintenance problem. Mark Washeim, [EMAIL PROTECTED] -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.15-1-amd64-k8-smp Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Versions of packages libquicktime0 depends on: ii libavc1394-0 0.5.1-1control IEEE 1394 audio/video devi ii libc6 2.3.6-3GNU C Library: Shared libraries an ii libdv40.104-1software library for DV format dig ii libjpeg62 6b-12 The Independent JPEG Group's JPEG ii libpng12-01.2.8rel-5 PNG library - runtime ii libraw1394-5 0.10.1-1.1 library for direct access to IEEE ii libvorbis0a 1.1.2-1The Vorbis General Audio Compressi ii libvorbisenc2 1.1.2-1The Vorbis General Audio Compressi ii libvorbisfile31.1.2-1The Vorbis General Audio Compressi ii zlib1g1:1.2.3-11 compression library - runtime libquicktime0 recommends no packages. -- no debconf information A -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#359863: BOUNTY: files created by libquicktime0 not opened with same
Hi Mark, On Wed, Mar 29, 2006 at 02:46:46AM -0700, Mark Washeim wrote: *** Please type your report below this line *** Hello, 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 Do you have a small sample file you could forward to the bug report which exhibit this problem? I've tried to locate the header writing (src for AMD 64) and realized that even getting it fixed would still leave me with a considerable maintenance problem. Does this mean you believe the problem is amd64-specific? Has it been confirmed that these files can be read correctly by libquicktime0 on i386? Cheers, -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ signature.asc Description: Digital signature
