-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I have successfully compiled and installed libquicktime (cvs), but mjpegtools
does not find it.
Can anybody tell me what the configure looks for? I have looked through the
log and the config files, but I don't understand them.
It looks like libq
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Friday 09 January 2004 10:35 pm, Steven M. Schultz wrote:
> On Fri, 9 Jan 2004, Karl and Tanya Pizzolatto wrote:
> > latest versions of everything:
>
> Including the documentation and mailing list archive search? :-)
>
Y
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
latest versions of everything:
libmovtar-0.1.3
mjpegtools-1.6.1.92
I built libmovtar, installed it, and then built and installed mjpegtools.
I test
lavrec -fm -iN -t5 /tmp/test.avi
But there is no longer a -fm option to record in movtar format.
Us
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
There isn't a list for linuxvideostudio, so I thought I'd post here rather than
emailing the developer(s) directly.
Anyhow, I just got mjpegtools & the zoran driver working with my buz. Hasn't blown up
yet; thanks for your hand-holding, Ronald!
I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> modprobe then. Also, remember that modules.conf is called modprobe.conf
> in 2.6.x.
BINGO!
I did not know that.
Thank you very much.
BTW, you mentioned 1.8M as the avi file size. I somehow got the impression
(wrong, it seems), that lavrec 1.6.1
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thursday 09 October 2003 04:18 am, Ronald Bultje wrote:
> Hi Karl,
>
> On Thu, 2003-10-09 at 05:57, Karl and Tanya Pizzolatto wrote:
> > -BEGIN PGP SIGNED MESSAGE-
> > CC [M] /mnt/archive/library/compu
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I saw a bug earlier that was not observed in the 2.6 kernel, so...
I suspect I'm missing something obvious here, but I think I covered all the bases...
I built the 2.6 kernel with modular zoran support
Video For Linux
Zoran ZR36057/36067 Video For
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
For giggles, I updated the kernel modules--
/usr/lib/[asm, asm-i386, asm-generic, linux, etc...]
from 2.4.22 to 2.6.0-test6--just in case that was the problem.
No help; make of driver-zoran from cvs still yields
...
...
...
Making Unified Zoran (zr36
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Testing out the 0.9.5 (cvs) version of driver-zoran in slackware-9.1 (actually
slackware-current as of Oct 10, 2003, but the changes are mostly security
patches to ssl)
kernel, motherboard, and capture card:
2.4.22-smp, dual pIII, iomega buz
dow
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I am getting a kernel oops in 0.9.4. I got this before, with 0.9.3 and
submitted bug reports. 0.9.4 worked fine for a while until I upgraded my
system.
kernel is 2.4.22-SMP; distro is slackware-9.1; machine is dual PIII
I would like to try the cv
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hmmm...
I recorded about 47 minutes of AV with lavrec into 2 avi files, then tried to
merge them:
$ avimerge -o reallybig.avi -i big01.avi big02.avi
where big01.avi is 1995M and big02.avi is 1869M
fails after reallybig.avi is about ~1500M
Why does
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
FYI:
It locked up the machine again! But only did it once; maybe it's a fluke. At
any rate, it's performing *much* better than 0.9.3.
I'll submit a proper bug report if I see it again and can repeat it.
Thanks,
Karl Pizzolatto
- --
Improve a me
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I'm trying to record a 1-hour show, and my file size exceeds 2G.
I read (in the MJpeg docs) that the avi file size limit is 2G. But I've also
read (in mplayer docs) that it's 4G.
What is the maximum file size for an avi file?
Is this a limit of MJ
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> * fix stupid flaw in open() logic (could result in oops)
> Please test and let me know the results!
>
> Ronald
It Works!
Yippee
Oh, yeah--I did the test that reproduces the "Oops on the second time you run
lavrec." That's what works.
- --
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thursday 20 March 2003 03:17 am, Ronald Bultje wrote:
> Hey,
>
> On Thu, 2003-03-20 at 04:03, Karl and Tanya Pizzolatto wrote:
> > This weekend, I will build a 2.4.20 kernel with no patches and no
> > i2c-2.7.0. Then rebuild
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tuesday 18 March 2003 03:16 am, Ronald Bultje wrote:
> Hey Karl,
>
> On Tue, 2003-03-18 at 02:54, Karl and Tanya Pizzolatto wrote:
> > I didn't find anything. What I wrote down follows below. Keep in mind
> > this repo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Followup to my crash report a few hours ago
>Tell me if there's any more info I can provide you.
Oh, yeah. It's an iomega buz. That might help. Sorry!
Karl Pizzolatto
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.1 (GNU/Linux)
iD8DBQE+dwvDTH
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
driver-zoran-0.9.3 crashes on the second try at recording video.
as a user (not root), I issued the command:
$ lavrec -in -fa -t5 test1.avi
then for the second try
$ lavrec -in -fa -t5 test2.avi
The second time, lavrec ran for about 3-4s, and then cr
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
>> Once I have used the video encoding or decoding functions of my iomega buz
>> card, I cannot use the card again. If I do, the computer stops responding
>> to keyboard and mouse input. I don't have another machine to try
>> telnetting via a serial
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thursday 13 February 2003 10:23 am, you wrote:
> Hey,
>
> On Thu, 2003-02-13 at 14:48, Karl and Tanya Pizzolatto wrote:
> > Make fails with a complaint "lav_common.c:425:too many arguments to
> > function '3v_decod
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thursday 13 February 2003 10:23 am, you wrote:
> Hey,
>
> On Thu, 2003-02-13 at 14:48, Karl and Tanya Pizzolatto wrote:
> > Make fails with a complaint "lav_common.c:425:too many arguments to
> > function '3v_decod
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Make fails with a complaint "lav_common.c:425:too many arguments to function
'3v_decoder_free'":
I have tried MJpegTools 1.6.0 and 1.6.1 and gotten the same error. After
make, I did make again and captured just the error output.
Has anybody seen t
22 matches
Mail list logo
