Hi Dwaine,
thank you for testing the driver and thank you for the link. But I'm
sorry, that the input values didn't match with your device. Now let's
fix the Problem. Can you please tell me some details of your camera:
What is the exact name of your device?
It's the X10 camera. The vendor ID and product ID are all ready in the
code.
Is there an saa7111a chip in your device?
Yep... I crack the usb cable open and read the info right off the chip.
Wednesday I will try to use a NTSC video source with my HAUPPAUGE
device. The signal will come from a pattern generator, but I hope it
will match your TV norm.
It will be interesting to see the results of your test.
Yes. The maximum now is 320x240 to prevent overrunning of the
nt1003-FIFO. Maybe you can use a bigger
size when changing the value of BUF_THR (reg 0x30) on nt1003. It is set
in usbvision__set_compress_params.
I hadn't yet time to test it.
Is there a way to get the information from the usb device and adjust the
allocated BUG_THR
on the fly?
> The image was in Black and white.
Maybe the video mode bits on the saa7111a isn't set right. I did some
changes in usbvision_muxsel to have correct S-Video input on my
WINTV-USB FM. There you will find a line:
Maybe there should be a flag for the connections. My USB Vision device has
both S-Video and Composite connections. It would also be nice to probe and
identify which port is being used.
int mode[] = {0, 1, 7}; //modes of saa7111 fix me (this is only for
Hauppauge WinTV)
Prior the 7 was a 2. If a 2 gives colored pictures to you, than we must
add an device depending if-clause.
aaaaaaaaaaarrrrrrrrrrrrrrrggggggggghhhhhhhhhhhhhh!
I hate using device depending if-clauses. hehehehaha....
I'll try changing the values to see if I can get colour to spit out.
I was thinking it was a change to the saa7111-new.c. I did have alot of time
to really investigate it. I let you know of the results.
> The frame still has multiple sections.
I can see the picture on your site.
I think the value[2]=0x20 and value[3]=0x01 (number of videolines) in
usbvision_set_input are wrong.
Try value[2]=0xF2 and value[3]=0x00 or similar. Then you have to shift
in horizontal direction by changing
value[4] and value[5]. Maybe changing 0x51 to 0x60 is ok.
I'll make those changes and report back with the output. Is there
a way for the NT1003 or 1004 to report on these parameters? It would be a lot
better to have the device report on the input size.
Also, the windows driver reports that the number of lines of video
are 740 in NTSC mode. I tried this number and the output looked like a room
with funny mirrors.
>
> It weird.... I can't see anything in the code that would suggest a black and
> white image. I'm going to check the code again tonight.
>
> I love the speed improvements. I also tried sending the output through
> xawtv off the screen. Hehehehe.....
>
> Where did you get the input values for the video format PAL? I'm thinking
(Pssst!) Don't tell it to anyone: I have a Windows PC and an USB
analyser.
I was using the information from the software package that X10 ships with
their wireless camera. Trying to grab information on the output and input
size. It listed
on one tab the number of lines of video.
The NT1003 and NT1004 are really neat devices. I have learned alot about video
from these devices. You
can hook a lot of devices to the usb cables.
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
http://lists.sourceforge.net/lists/listinfo/linux-usb-devel
