[Mjpeg-users] Re: [Mjpeg-developer] New release (0.9.4) of unified Zoran driver

2003-03-26 Thread Martin Samuelsson
On Thursday 27 March 2003 00:21, Ronald Bultje wrote:
> Hey all,
>
> A new release of your all-time favourite driver (well, the WLAN drivers
> are cooler, but still ;-) ) is available! This time, we (me) have
> decided unanymously to call this release 0.9.4!

My compliments to all the chefs!

As I couldn't sleep, I've done some tests on this new release and the Buz, and 
what can I say? It seems rock solid, on par with the driver before the 
rewrite. Good work!

By jiggling around with the video connector, it's still possible to cause 
field inversion (it's my understanding that the field order isn't really 
detectable while capturing, just when beginning the capture), and I did 
manage to make it lose sync completely. I don't think the chip was designed 
for that kind of abuse anyway.

However, in more normal circumstances, it seem very hard to make the driver 
croak, either from slow disks or missing syncs. (In most cases, it just goes 
on capturing if the video signal is lost.)

/Sam



---
This SF.net email is sponsored by:
The Definitive IT and Networking Event. Be There!
NetWorld+Interop Las Vegas 2003 -- Register today!
http://ads.sourceforge.net/cgi-bin/redirect.pl?keyn0001en
___
Mjpeg-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/mjpeg-users


Re: [Mjpeg-users] New release (0.9.4) of unified Zoran driver

2003-03-26 Thread Karl and Tanya Pizzolatto
-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.


- -- 
Improve a mechanical device and you may double productivity. But improve man, 
you gain a thousandfold.
- -Khan Noonian Singh
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE+gl1UTHYRdwouzJMRApd8AJ4gHrv33uX5jkjTaszJV/xk7bBaqACglfVj
L4jIc6CzM/bWHa/SFxhrDP0=
=/VOy
-END PGP SIGNATURE-



---
This SF.net email is sponsored by:
The Definitive IT and Networking Event. Be There!
NetWorld+Interop Las Vegas 2003 -- Register today!
http://ads.sourceforge.net/cgi-bin/redirect.pl?keyn0001en
___
Mjpeg-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/mjpeg-users


[Mjpeg-users] New release (0.9.4) of unified Zoran driver

2003-03-26 Thread Ronald Bultje
Hey all,

A new release of your all-time favourite driver (well, the WLAN drivers
are cooler, but still ;-) ) is available! This time, we (me) have
decided unanymously to call this release 0.9.4!

Changes since our last episode:
* Add YUY2 overlay (fullscreen/hardware-scaled)
* use __stringify() for array insmod options
* fix stupid flaw in open() logic (could result in oops)
* fix 2.5.x build
* remove lots of 'dead' includes from zoran_driver.c
* remove DataErr from the zr36060 IRQMask, this autoresets the chip when
it loses sync, which means we don't get a timeout. Much better than
all the manual restart handling (which only worked partly).
* introduce workaround for kfree-in-munmap-handler oops
* implement support for bitmaps rather than clips for overlay
* use try_module_get()/module_put() instead of MOD_INC/DEC_USE_COUNT
in 2.5.x... Also implement i2c_driver->owner for all i2c clients

This means, in short, that it shouldn't timeout anymore, it shouldn't
oops anymore, and it should use 'true' fullscreen now (hardware-scaled)
on Xv-capable videocards. Also, it should now work under 2.5.x
(compilation is tested). I've had one report that the field order is
sometimes spontaneously switched after a signal glitch. If anyone
encounters it, I'd be interested in knowning what conditions trigger it
(of course, it shouldn't do this).

A tarball can be downloaded from the usual spot on sourceforge:
https://sourceforge.net/project/showfiles.php?group_id=5776&release_id=149014. Same as 
for latest releases - it this one works well, it'll go into 2.5.x. Bugreports can be 
send to me, Laurent or to this mailinglist (preferred).

Please test and let me know the results!

Ronald

-- 
Ronald Bultje <[EMAIL PROTECTED]>



---
This SF.net email is sponsored by:
The Definitive IT and Networking Event. Be There!
NetWorld+Interop Las Vegas 2003 -- Register today!
http://ads.sourceforge.net/cgi-bin/redirect.pl?keyn0001en
___
Mjpeg-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/mjpeg-users


Re: [Mjpeg-users] difference -f 5 -f 8

2003-03-26 Thread Andrew Stevens
Hi Al,

> So the difference you see, is:
> -q -4 2 -2 3
>
> I use different -q values with different sources. But does it make
> sense to use  -4 2 -2 3 for encoding DVDs from dv-camera-sources?

The -4 and -2 flags just control how exhaustively the motion estimator
searches for good motion compensation.  Basically, the lower the number
the fewer unlikely Candidates are discarded without detailed examination.

The gains in compression from cranking -4 and -2 right down are pretty 
marginal for most material.   More a case of "I don't care if it compresses
overnight, so which not".  If encoding time matters to you don't bother
winding them down low.

Andrew



---
This SF.net email is sponsored by:
The Definitive IT and Networking Event. Be There!
NetWorld+Interop Las Vegas 2003 -- Register today!
http://ads.sourceforge.net/cgi-bin/redirect.pl?keyn0001en
___
Mjpeg-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/mjpeg-users


[Mjpeg-users] [Solved]: driver-zoran-0.9.3 - DC10+ & SB pci128 OOPS

2003-03-26 Thread Ríkharður Egilsson

I found the problem, the card was just making crackle and pops 
when I tried to record with another (home made) program, so I moved
the card to a different PCI slot.

That solved the problem.


- Ríkharður


On Tue, Mar 25, 2003 at 10:26:31AM +0100, Ríkharður Egilsson wrote:
> What a card, the DC10+ I'm realy impressed with the image quality,
> By the way, what is the difference between the DC10 and the DC10+ ?
> 
> My hardware:
>   Motherboard: Abit BP6 (Dual Celeron [EMAIL PROTECTED])
>   DC10+ video capture card.
>   Sound Blaster pci128
>   All the Hard disks are connected to the HighPoint
>   UDMA controller.
> 
> Recording video only (i.e. no sound) works without any problem.
> I can also use lavplay to play the recording back to the TV in
> broadcast quality. (*Super*)
> 
> >>"No sound" Recording :
> >>>
> [EMAIL PROTECTED] root]# lavrec -fa -is -a0 -d2 -q30 -t 5 -v1 Snap.avi
>INFO: [lavrec] Recording parameters:
>INFO: [lavrec] Output format:  AVI
>INFO: [lavrec] Input Source:   Composite SECAM
> 
>INFO: [lavrec] Decimation: 2
>INFO: [lavrec] Quality:30
>INFO: [lavrec] Recording time: 5 sec
>INFO: [lavrec]  
>INFO: [lavrec] MJPEG buffer size:  256 KB
>INFO: [lavrec] # of MJPEG buffers: 64
>INFO: [lavrec] Audio disabled
>INFO: [lavrec] Auto detecting input and norm ...
>INFO: [lavrec] Image size will be 384x288, 1 field(s) per buffer
>INFO: [lavrec] Got 32 buffers of size 256 KB
>INFO: [lavrec] Opening output file Snap.avi
>INFO: [lavrec] Recording time reached, stoppingtd1=0.000 td2=0.000
> 
> Recording time  :  0.00.05:00
> Lost frames : 000
> A/V sync ins/del: 000/000
> Audio errors: 000
> 
> 
> >>> syslog:
> >>>
> Mar 24 18:51:07 CandyBox kernel: i2c: initialized
> Mar 24 18:51:07 CandyBox kernel: Linux video capture interface: v1.00
> Mar 24 18:51:07 CandyBox kernel: Zoran ZR36060 + ZR36057/67 MJPEG board driver 
> version 0.7
> Mar 24 18:51:07 CandyBox kernel: MJPEG[0]: Zoran ZR36067 (rev 2) irq: 19, memory: 
> 0xee00
> Mar 24 18:51:07 CandyBox kernel: MJPEG[0]: subsystem vendor=0x1031 id=0x7efe
> Mar 24 18:51:07 CandyBox kernel: MJPEG[0]: Initializing i2c bus...
> Mar 24 18:51:07 CandyBox kernel: MJPEG[0]: Card not supported
> Mar 24 18:51:07 CandyBox kernel: No known MJPEG cards found.
> Mar 24 18:51:07 CandyBox kernel: Linux video codec intermediate layer: v0.2
> Mar 24 18:51:07 CandyBox kernel: i2c-core.o: i2c core module
> Mar 24 18:51:07 CandyBox kernel: i2c-algo-bit.o: i2c bit algorithm module
> Mar 24 18:51:07 CandyBox kernel: Zoran MJPEG board driver version 0.9.3
> Mar 24 18:51:07 CandyBox kernel: MJPEG[0]: Zoran ZR36067 (rev 2) irq: 19, memory: 
> 0xee00
> Mar 24 18:51:07 CandyBox kernel: MJPEG[0]: subsystem vendor=0x1031 id=0x7efe
> Mar 24 18:51:07 CandyBox kernel: i2c-core.o: driver saa7110 registered.
> Mar 24 18:51:07 CandyBox kernel: i2c-core.o: driver adv717x registered.
> Mar 24 18:51:07 CandyBox kernel: i2c-core.o: client [saa7110[0]] registered to 
> adapter [DC10plus[0]](pos. 0).
> Mar 24 18:51:07 CandyBox kernel: i2c-core.o: client [adv7176[0]] registered to 
> adapter [DC10plus[0]](pos. 1).
> Mar 24 18:51:07 CandyBox kernel: i2c-core.o: adapter DC10plus[0] registered as 
> adapter 0.
> Mar 24 18:51:07 CandyBox kernel: ZORAN: 1 card(s) found
> Mar 24 18:51:07 CandyBox kernel: DC10plus[0]: zr36057_init() - initializing card[0], 
> zr=d9487ac0
> Mar 24 18:51:08 CandyBox kernel: DC10plus[0]: zoran_open(lavrec, pid=[716]), 
> users(-)=0
> Mar 24 18:51:14 CandyBox kernel: DC10plus[0]: zoran_close(lavrec, pid=[716])
> 
> 
> But when I try to record with sound, the recording process
> hangs between  0.6  and 6 seconds (I have never managed to
> record 10 seconds with sound).
> 
> >>> Demo recording With Sound (1 second).
> 
> [EMAIL PROTECTED] root]# lavrec -fa -is  -d2 -q30 -t 1 -v1 Snap.avi
>INFO: [lavrec] Recording parameters:
>INFO: [lavrec] Output format:  AVI
>INFO: [lavrec] Input Source:   Composite SECAM
> 
>INFO: [lavrec] Decimation: 2
>INFO: [lavrec] Quality:30
>INFO: [lavrec] Recording time: 1 sec
>INFO: [lavrec]
>INFO: [lavrec] MJPEG buffer size:  256 KB
>INFO: [lavrec] # of MJPEG buffers: 64
>INFO: [lavrec] Audio parameters:
>INFO: [lavrec] Audio sample size:   16 bit
>INFO: [lavrec] Audio sampling rate: 44100 Hz
>INFO: [lavrec] Audio is MONO
>INFO: [lavrec] Audio input recording level: Use mixer setting
>INFO: [lavrec] Level of correction for Audio/Video synchronization:
>INFO: [lavrec] Lost frame compensation and frame drop/insert
>INFO: [lavrec] Using mmap(2) system call for capture
>INFO: [lavrec] Auto detecting input and norm ...
>INFO: [lavrec] Image size will be 384x288, 1 field(s) per buffer
>INFO: [lavrec] Got 32 buffers of size 256 KB
>INFO: [la