Eyetoy- anybody got any news on it?

2006-01-16
2013-05-09
  • i'll volenteer to test if anybodys got a driver for it.

     
    • Harald
      Harald
      2006-01-18

      OK, try the new cvs-build and let me know what happens!

      http://prdownloads.sourceforge.net/webcam-osx/cvs-build-2006-01-17.zip?download

      hxr

       
      • I did what it said to do, but to no avail. "Status: USB Connection Problem" is all that came up. Do i just move the component into Library/Quicktime and start Macam?

         
        • patrick mcevoy
          patrick mcevoy
          2006-03-27

          Yep, same here, this one doesn't work. USB connection problem (mac mini OSX 10.4.5).

           
    • french-man
      french-man
      2006-01-20

      hello,
      i have test you new macam archive with my webcam maxell

      maxcam plus (is the same chipset of eyetoy).

      but macam see "problem to connect with usb webcam"

      ps:
      chipset ov519
      vendor  id 0x05A9    
      product id 0x8519

      thank a lot for your work to add webcam in macam.

       
    • blademelbourne
      blademelbourne
      2006-02-01

      Hi Guys,

      I have a Dick Smith Electronics camera with the same chipset as the Eye Toy. It's a DSE Internet Camera & Microphone (OV519) OV7648 built-in microphone.

      System Profiler reports:
      Version:        1.00
      Bus Power (mA): 500
      Speed:          Up to 12 Mb/sec
      Manufacturer:   OmniVision Technologies, Inc.
      Product ID:     0x8519
      Vendor ID:      0x05a9

      I downloaded the CVS zip file above (2006-01-17).
      Moved macam.app to /Applications
      Moved macam.component to /Library/QuickTime
      Plugged in camera and ran macam.
      Status bar reports: "Status: USB communication problem"

      I have a Mac Mini running OS X 10.4.4 (fully updated) with QuickTime 7.0.4. The camera was plugged into the back of the Mini (no external hub).

      If there is any way I can enable debug info (or download a version that outputs useful information) and report it back, please let me know.

      Thanks :-)

       
    • HansH
      HansH
      2006-02-12

      Same Problem hier on my Powerbook runnig Mac Os X 10.4.4. The Status Bar says "USB communication problem". Die Run Log of Xcode provides the following output:

      2006-02-12 12:06:58.517 macam[283] OV511:regWrite:usbWriteCmdWithBRequest error
      usbCmdWithBRequestType: Error: kIOReturnNotResponding - device not responding

      Hope this is of any help. I'm also willing to donate my eyetoy camera if required. Would be great if the camera works :)

       
    • WietseB1989
      WietseB1989
      2006-03-07

      Yep, same problem here. "USB communication problem". Any news Harald?

       
    • blademelbourne
      blademelbourne
      2006-03-15

      FYI...

      cvs-build-2006-03-04.zip reports "Status: USB communication problem" too.

       
    • blademelbourne
      blademelbourne
      2006-03-25

      The same message is reported with cvs-build-2006-03-23.zip

       
    • Jarrod
      Jarrod
      2006-06-07

      I would love to help get this cam working.  I have some limited programming background, but I am very comfortable editing source and compiling.  I have compiled from CVS (even though the OV519 driver has not been updated since the last release)  And I get the same USB communication error.

      The run log in Xcode gives this "2006-06-06 19:54:11.356 macam[14646] GenericDriver: grab aborted because of invalid data stream (too long without a frame, 1049 invalid frames, 0 invalid chunks)"

      Dunno if this is helpful, but I am gonna poke around in the source, let me know what I can do, if anything to help along development.

       
      • Harald
        Harald
        2006-06-07

        Get the latest source from CVS (it sounds like you did).
        Use the "Debug" configuration, it gives the most messages.

        The ov511 Linux driver project
        http://alpha.dyndns.org/ov511/
        has source code that work with a lot of different
        ov511 variants, including the ov519. Be warned,
        this is messy, but the code is your best documentation.

        You will probably have to make some changes depending
        on your sensor. Otherwise, it should be pretty close.

        I don't know if the JPEG decoding is set up properly,
        you may have to fiddle with that too. Vincenzo (who
        didi the 519 driver) has not replied as to whether it is
        working now. His driver linked the libjpeg library; I
        changed  it to use code already included, but I could
        not test it. You can also change the "JpgDecompress.c"
        file and link with libjpeg if you desire.

        Let me know how it turns out,
        hxr

         
    • katastro
      katastro
      2006-06-09

      Hello,
      I hope this will help the developpers of this project. Thanks for your work.
      I have OS X Version 10.3.9 on a PPC. QuickTime Player 7.0.1.

      When I start cvs-build-2006-06-02 with the eye toy connected.
      The screen is black and the message is «Status: Connected to Sony Eye Toy (2) ».

      This is the console.log text:
      The sensor is  0 0
      The sensor is unknown things may or may not work! Please report!

      Camera Regs

           00=C0 01=00 02=A8 03=00 04=00 05=00 06=00 07=00 08=1D 09=00 0A=00 0B=05 0C=00 0D=00 0E=00 0F=00
           10=28 11=3C 12=00 13=00 14=00 15=00 16=00 17=40 18=00 19=00 1A=00 1B=44 1C=00 1D=00 1E=00 1F=00
           20=10 21=08 22=98 23=FF 24=00 25=03 26=00 27=00 28=22 29=01 2A=49 2B=00 2C=01 2D=00 2E=00 2F=00
           30=FF 31=FF 32=FF 33=FF 34=50 35=51 36=52 37=00 38=00 39=00 3A=00 3B=00 3C=00 3D=00 3E=00 3F=00
           40=00 41=43 42=0B 43=0B 44=0B 45=00 46=00 47=2C 48=3B 49=00 4A=00 4B=00 4C=00 4D=00 4E=00 4F=00
           50=00 51=0F 52=00 53=9B 54=0F 55=02 56=00 57=21 58=00 59=04 5A=6D 5B=0E 5C=00 5D=03 5E=00 5F=11
           60=00 61=21 62=0F 63=00 64=00 65=00 66=00 67=00 68=05 69=04 6A=01 6B=00 6C=00 6D=00 6E=00 6F=00
           70=B4 71=00 72=FF 73=00 74=FF 75=00 76=00 77=FF 78=03 79=03 7A=FC 7B=00 7C=FF 7D=00 7E=00 7F=FF
           80=00 81=00 82=FF 83=00 84=FF 85=00 86=00 87=FF 88=00 89=00 8A=00 8B=00 8C=7F 8D=00 8E=00 8F=00
           90=00 91=00 92=00 93=00 94=00 95=00 96=00 97=00 98=00 99=00 9A=00 9B=00 9C=00 9D=00 9E=00 9F=00
           A0=33 A1=04 A2=40 A3=40 A4=0C A5=3F A6=76 A7=00 A8=00 A9=20 AA=00 AB=00 AC=00 AD=00 AE=00 AF=00
           B0=00 B1=0A B2=0F B3=1E B4=2D B5=FF B6=00 B7=FF B8=00 B9=FF BA=00 BB=00 BC=00 BD=00 BE=00 BF=00
           C0=00 C1=01 C2=02 C3=03 C4=00 C5=05 C6=02 C7=07 C8=00 C9=09 CA=02 CB=0B CC=00 CD=0D CE=02 CF=0F
           D0=00 D1=11 D2=02 D3=13 D4=00 D5=15 D6=02 D7=17 D8=00 D9=19 DA=02 DB=1B DC=00 DD=1D DE=02 DF=1F
           E0=50 E1=64 E2=82 E3=96 E4=82 E5=81 E6=00 E7=01 E8=02 E9=00 EA=10 EB=00 EC=00 ED=00 EE=00 EF=00

      I2C Regs

           00=00 01=00 02=00 03=00 04=00 05=00 06=00 07=00 08=00 09=00 0A=00 0B=00 0C=00 0D=00 0E=00 0F=00
           10=00 11=00 12=00 13=00 14=00 15=00 16=00 17=00 18=00 19=00 1A=00 1B=00 1C=00 1D=00 1E=00 1F=00
           20=00 21=00 22=00 23=00 24=00 25=00 26=00 27=00 28=00 29=00 2A=00 2B=00 2C=00 2D=00 2E=00 2F=00
           30=00 31=00 32=00 33=00 34=00 35=00 36=00 37=00 38=00 39=00 3A=00 3B=00 3C=00 3D=00 3E=00 3F=00
           40=00 41=00 42=00 43=00 44=00 45=00 46=00 47=00 48=00 49=00 4A=00 4B=00 4C=00 4D=00 4E=00 4F=00
           50=00 51=00 52=00 53=00 54=00 55=00 56=00 57=00 58=00 59=00 5A=00 5B=00 5C=00 5D=00 5E=00 5F=00
           60=00 61=00 62=00 63=00 64=00 65=00 66=00 67=00 68=00 69=00 6A=00 6B=00 6C=00 6D=00 6E=00 6F=00
           70=00 71=00 72=00 73=00 74=00 75=00 76=00 77=00 78=00 79=00 7A=00 7B=00 7C=00 7D=00 7E=00 7F=00

      Then I push on the play botton and this is the message «Etat: problème de communication sur USB ». In english probably « USB communication error ».

      This is the console.log text:
      2006-06-09 16:09:10.127 macam[450] GenericDriver: grab aborted because of invalid data stream (too long without a frame, 1049 invalid frames, 0 invalid chunks)

      Nothing is written in the console. Log when I start macam.0.8.6 with the eye toy connected.
      The screen is black and the message is «Status: Connected to Sony Eye Toy (2) ».
      Then I push on the play botton and this is the message «Etat: problème de communication sur USB ». In english probably « USB communication error »

      The console.log:
      2006-06-09 16:22:46.047 macam[336] GenericDriver: grab aborted because of invalid data stream (too long without a frame, 1049 invalid frames, 0 invalid chunks)

      Info from USB Prober:
      Full Speed device @ 2 (0x3B100000): .............................................   Composite device: "EyeToy USB camera Namtai"
          Device Descriptor  
              Descriptor Version Number:   0x0110
              Device Class:   0   (Composite)
              Device Subclass:   0
              Device Protocol:   0
              Device MaxPacketSize:   8
              Device VendorID/ProductID:   0x054C/0x0155   (Sony Corporation)
              Device Version Number:   0x0100
              Number of Configurations:   1
              Manufacturer String:   1 "Sony corporation"
              Product String:   2 "EyeToy USB camera Namtai"
              Serial Number String:   0 (none)
          Configuration Descriptor  
              Total Length of Descriptor:   180
              Number of Interfaces:   3
              Configuration Value:   1
              Attributes:   0x80 (bus-powered)
              MaxPower:   500 ma
              Interface #0 - Vendor-specific  
                  Alternate Setting   0
                  Number of Endpoints   1
                  Interface Class:   255   (Vendor-specific)
                  Interface Subclass;   0   (Vendor-specific)
                  Interface Protocol   0
                  Endpoint 0x81 - Isochronous Input  
                      Attributes:   0x81  (IN)
                      Attributes:   0x01  (Isochronous)
                      Max Packet Size:   0
                      Polling Interval:   1 ms
              Interface #0 - Vendor-specific (#1)  
                  Alternate Setting   1
                  Number of Endpoints   1
                  Interface Class:   255   (Vendor-specific)
                  Interface Subclass;   0   (Vendor-specific)
                  Interface Protocol   0
                  Endpoint 0x81 - Isochronous Input  
                      Attributes:   0x81  (IN)
                      Attributes:   0x01  (Isochronous)
                      Max Packet Size:   384
                      Polling Interval:   1 ms
              Interface #0 - Vendor-specific (#2)  
                  Alternate Setting   2
                  Number of Endpoints   1
                  Interface Class:   255   (Vendor-specific)
                  Interface Subclass;   0   (Vendor-specific)
                  Interface Protocol   0
                  Endpoint 0x81 - Isochronous Input  
                      Attributes:   0x81  (IN)
                      Attributes:   0x01  (Isochronous)
                      Max Packet Size:   512
                      Polling Interval:   1 ms
              Interface #0 - Vendor-specific (#3)  
                  Alternate Setting   3
                  Number of Endpoints   1
                  Interface Class:   255   (Vendor-specific)
                  Interface Subclass;   0   (Vendor-specific)
                  Interface Protocol   0
                  Endpoint 0x81 - Isochronous Input  
                      Attributes:   0x81  (IN)
                      Attributes:   0x01  (Isochronous)
                      Max Packet Size:   768
                      Polling Interval:   1 ms
              Interface #0 - Vendor-specific (#4)  
                  Alternate Setting   4
                  Number of Endpoints   1
                  Interface Class:   255   (Vendor-specific)
                  Interface Subclass;   0   (Vendor-specific)
                  Interface Protocol   0
                  Endpoint 0x81 - Isochronous Input  
                      Attributes:   0x81  (IN)
                      Attributes:   0x01  (Isochronous)
                      Max Packet Size:   896
                      Polling Interval:   1 ms
              Interface #1 - Audio/Audio Control  
                  Alternate Setting   0
                  Number of Endpoints   0
                  Interface Class:   1   (Audio)
                  Interface Subclass;   1   (Audio Control)
                  Interface Protocol   0
                  Audio Control Class Specific Header  
                      Descriptor Version Number:   01.00
                      Class Specific Size:   30
                      Number of Audio Interfaces:   1
                      Audio Interface Number:   2
                  Audio Class Specific Input Terminal  
                      Terminal ID:   1
                      Input Terminal Type:   0x201 (Microphone)
                      OutTerminal ID:   0 [NONE]
                      Number of Channels:   1
                      Spatial config of channels:   0000000000000000
                      String index for first logical channel:   0
                      Terminal Name String Index:   0 [NONE]
                  Audio Class Specific Ouput Terminal  
                      Terminal ID:   2
                      Output Terminal Type:   0x101 (USB Isochronous Stream)
                      InTerminal ID:   0 [NONE]
                      Source ID:   1
                      Terminal Name String Index:   0 [NONE]
              Interface #2 - Audio/Audio Streaming  
                  Alternate Setting   0
                  Number of Endpoints   0
                  Interface Class:   1   (Audio)
                  Interface Subclass;   2   (Audio Streaming)
                  Interface Protocol   0
              Interface #2 - Audio/Audio Streaming (#1)  
                  Alternate Setting   1
                  Number of Endpoints   1
                  Interface Class:   1   (Audio)
                  Interface Subclass;   2   (Audio Streaming)
                  Interface Protocol   0
                  Audio Control Class Specific Header  
                      Audio Stream General  
                          Endpoint Terminal ID:   2
                          Delay:   1 frames    
                          Format Tag:   0x0001 (PCM)
                  Audio Class Specific Audio Data Format  
                      Audio Stream Format Type Desc.  
                          Format Type:   1 PCM
                          Number Of Channels:   1 MONO
                          Sub Frame Size:   2
                          Bit Resolution:   16
                          Sample Frequency Type:   0x01 (Discrete)
                          Sample Frequency:   16000 Hz
                  Endpoint 0x82 - Isochronous Input  
                      Attributes:   0x82  (IN)
                      Attributes:   0x05  (Isochronous)
                      Max Packet Size:   40
                      Polling Interval:   1 ms
                  Class-Specific AS Audio EndPoint - Control output  
                      Attributes:   0x00   
                      bLockDelayUnits:   0x00  (UNDEFINED)
                      wLockDelay:   0   

       
    • blademelbourne
      blademelbourne
      2006-06-11

      CVS build from 9th June 2006...

      I plug in my Dick Smith camera with the ov519 chipset.

      Macam status bar reports:
      "Status: Connected to OV519-based camera (2)"

      When I press the play icon, the status bar reports:
      "Status: Playing"
      The window turns from black to a grey with little dots spaced about 10px apart.

      After a couple of minutes, the status bar changes to "Status: USB communication problem"

      Looks like it's getting closer :-)

       
    • french-man
      french-man
      2006-06-17

      hello

      no news to decompress the jpeg format.

      thanks

       
    • blademelbourne
      blademelbourne
      2006-07-27

      Hi Everyone,

      Good news! I have tested every CVS build for 7 months, and macam-cvs-build-2006-07-26.zip is a winner!

      It's grainy, but it's no different on Windows. The softness slider control would be perfect if it was enabled. I realise this camera outputs JPEG though, so this may not be easy.

      For proof:
      http://www.mikeskinner.net/images/macam_20060727.png

      Thank you to Hxr and the other developers who got it working. I tip my "pimp" hat to you ;-)

       
    • WietseB1989
      WietseB1989
      2006-08-27

      The USB communication problem is gone, so I'm pretty sure progress has been made, but I still can't see anything.

      Macam tells me my webcam's playing, while I don't think it really is. My 'screen' is just black. Any idea what this could be?

      I'm using the latest build.

       
      • Harald
        Harald
        2006-08-30

        Hi ,

        The Eyetoy seems to work on 10.4.x but not on 10.3.x.
        (using the cvs-build, of course)
        Must have something to do with the JPEG decoding.

        Does this correspond with the experience of other?
        Please respond if it does *not*!

        Thanks,
        Harald

         
    • WietseB1989
      WietseB1989
      2006-09-28

      Okay, checked on 10.4.7 - works! Did not work on the 10.3.x.

      Still very blurry, unsure of what this is. Does anyone have a similar problem?