Page 3 of 4

Re: Firewire Video via DM10 and Apple iSight FW

Posted: Wed May 15, 2013 7:58 pm
by guardian452
I thought everybody knew about that... :/ of course without the camera all you get is the indian head test pattern...

Re: Firewire Video via DM10 and Apple iSight FW

Posted: Thu May 16, 2013 2:27 am
by smj
recondas wrote:Please Note: Because of the relative age of IRIX, take a close look at your security before enabling or using Outbox.

Sure, that's a good idea regardless of Outbox. The guidelines in the IRIX Installation and Customization wiki page have some excellent suggestions on that front.

Better still, do those things and keep the IRIX box behind the firewall and have it push the image out to a webserver running a more modern OS...

Re: Firewire Video via DM10 and Apple iSight FW

Posted: Thu May 16, 2013 5:25 am
by recondas
guardian452 wrote:I thought everybody knew about that.
First time SGI owners become involved in nekochan all the time, so it really wasn't aimed at anybody already fully qualified for the been-there-done-that merit badge.

Re: Firewire Video via DM10 and Apple iSight FW

Posted: Fri May 17, 2013 5:24 am
by guardian452
Sorry, didn't mean to be condescending.. it's good to know that it works with these devices, and not just (i.e. indycam and O2cam).

All I've ever gotten to see is: :oops:
Screen shot 2013-05-17 at 8.23.49 AM.png


Still it is a very cool default setup ;)

Re: Firewire Video via DM10 and Apple iSight FW

Posted: Mon Nov 25, 2013 9:16 am
by recondas
Had the opportunity to try the DM10 IIDC camera setup connected through a Firewire hub.

Did initial testing using the Tezro and ADS Pyro 1394 IIDC camera described earlier in this thread. The hub used is a Belkin FU526-APL-S 6-port Firewire hub. During this test the ADS Pyro 1394 was connected to the FW hub rather than directly to the DM10 (for those not already familiar with the DM10, no rare $GI hardware is needed - a generic PCI firewire HBA can be used).

The booting the system with the FU526 FW hub attached (added the ADS Pyro later) produced an 'businfo read' alert message in the syslog:

Code: Select all

Scanning FireWire bus /hw/module/001c01/IXbrick/xtalk/15/pci-x/1/2/ohci/0 (2 nodes)
FireWire Node [0]: <6>OXFORD SEMICONDUCTOR LTD., OXFORD IDE Device   
ALERT: Can't do businfo read to id 1, adr = 0xfffff0000408, status = 0x7
Scanning FireWire bus /hw/module/001c01/IXbrick/xtalk/15/pci-x/1/2/ohci/0 (0 nodes)
Just to make the test a little more challenging, after IRIX booted the ADS Pryo camera was hot-plugged into the FW hub. Syslog again produced a businfo read alert:

Code: Select all

Scanning FireWire bus /hw/module/001c01/IXbrick/xtalk/15/pci-x/1/2/ohci/0 (3 nodes)
FireWire Node [0]: <6>OXFORD SEMICONDUCTOR LTD., OXFORD IDE Device   
FireWire Node [1]: <6>ADS TECHNOLOGIES, INC., PYRO WEBCAM
ALERT: Can't do businfo read to id 2, adr = 0xfffff0000408, status = 0x7
Scanning FireWire bus /hw/module/001c01/IXbrick/xtalk/15/pci-x/1/2/ohci/0 (0 nodes)
In spite of the businfo alerts, the ADS Pyro worked without issue when connected to the FW hub, as did a MicroTech Firewire Compact Flash card reader.

Haven't had the opportunity to test it yet, but don't expect the FW iSight will behave much differently.

Re: Firewire Video via DM10 and Apple iSight FW

Posted: Mon Nov 25, 2013 5:25 pm
by hamei
recondas wrote:Haven't had the opportunity to test it yet, but don't expect the FW iSight will behave much differently.

Have you been able to get an iSight to work directly attached ? I remember that a few people tried to use an iSight before but had problems with it.

Re: Firewire Video via DM10 and Apple iSight FW

Posted: Mon Nov 25, 2013 7:42 pm
by recondas
hamei wrote:Have you been able to get an iSight to work directly attached ? I remember that a few people tried to use an iSight before but had problems with it.
Yep, It works.

Out late last night showin' up the whippersnappers?

in the second post in this very thread, hamei wrote:Another small step for Man ! Congratulations :D

I remember that neko got almost to that point but his iSight would not work. Maybe this means that the supported Canopus ADVC device could one day be persuaded to function ?

Super news, thank you !
viewtopic.php?f=3&t=16727655#p7359565

Re: Firewire Video via DM10 and Apple iSight FW

Posted: Mon Nov 25, 2013 8:41 pm
by ClassicHasClass
My FW iSight works fine with the Fuel too.

Re: Firewire Video via DM10 and Apple iSight FW

Posted: Mon Nov 25, 2013 10:45 pm
by hamei
recondas wrote:Out late last night showin' up the whippersnappers?

No, I just turned off that portion of the brain to save on electricity. Trying to cut down on the carbon footprint ... :oops:

Re: Firewire Video via DM10 and Apple iSight FW

Posted: Sun Feb 02, 2014 4:43 am
by hamei
Amends for brainfade, can add another camera known to work ...
snap.jpg

Code: Select all

fool 14% fwprobe
Probing DM10 cards...
Number of cards: 1
Card Info
=========
Card #: 0
Name  : DM10
ID    : 0x0
Ports : 3
Speed : 400 / 400

3 devices attached
Device 0: 0x0
  Vendor: Silicon Graphics, Inc.
   Model: DMediaPro DM10
   Proto: HBA
Device 1: 0xD016010000182F
  Vendor: SCM MICROSYSTEMS, INC.
   Model: FireWire CameraMate
   Proto: SBP2
Device 2: 0x800286000018B3E
  Vendor: Texas Instruments
   Model: TI
   Proto: IIDC

The name printed on top is "BlackHawk IEEE1394 Digital Camera" but it looks exactly like the iRez Stealthfire. The DuoConnect didn't seem to like it. Tezro and O350 don't seem to like the DuoConnect, so maybe that's fair ... Had to use recondas' excellent writeup to discover that the TIMING on this camera was the glitch,

Code: Select all

    "available timings:            available samplings:\n"
    "    NTSC                         444\n"
    "   0375p                         422\n"
    "   0750p                         411\n"
    "     15p\n"
    "     30p\n"
    ;

so tried ...

Code: Select all

fool 15% /usr/share/src/dmedia/video/iidc/iidc_vidtogfx -d iidc-camera -t NTSC -D

which brought it to life. Not bad. Focus is sharp, motion is decent, looks as good as Facetime even in fairly low-light conditions, pretty good for a webcam. Looks like the basics of getting an IIDC camera to work have been solved :D

Re: Firewire Video via DM10 and Apple iSight FW

Posted: Sun Feb 02, 2014 6:16 am
by recondas
hamei wrote:can add another camera known to work ...

Thanks for the write up, the Blackhawk IEEE1394 Digital Camera has been added to the list in the Fuel IP35 Hardware Aggregator.

Re: Firewire Video via DM10 and Apple iSight FW

Posted: Sun Feb 02, 2014 7:46 am
by hamei
recondas wrote: the Blackhawk IEEE1394 Digital Camera has been added to the list.

Cool, thank you. I'm pretty sure (99.9%) that this is an iRez Stealthfire so that guy could probably go itno the Approved category too. Found a couple photos, they look identical.

But the helpful part is, I actually discovered a step you missed :P Me, too, but when I did < man iidc > it came up with this :

Run the mlquery -d first to get the correct device name (most likely going to be iidc-camera but never hurts to make sure) then

Code: Select all

fool 35% mlquery -d iidc-camera -v all

          PARAM: ML_DEVICE_STATE_INT32
         parent: SDSerialDigitalInput
           type: int32
           enum: ML_DEVICE_STATE_TRANSFERRING,
                 ML_DEVICE_STATE_WAITING,
                 ML_DEVICE_STATE_ABORTING,
                 ML_DEVICE_STATE_FINISHING,
                 ML_DEVICE_STATE_READY
          usage: get/setControls

          PARAM: ML_QUEUE_SEND_COUNT_INT32
         parent: SDSerialDigitalInput
           type: int32
          usage: getControls (but not during a transfer)

          PARAM: ML_QUEUE_RECEIVE_COUNT_INT32
         parent: SDSerialDigitalInput
           type: int32
          usage: getControls (but not during a transfer)

          PARAM: ML_QUEUE_SEND_WAITABLE_INT32
         parent: SDSerialDigitalInput
           type: int32
          usage: getControls (but not during a transfer)

          PARAM: ML_QUEUE_RECEIVE_WAITABLE_INT32
         parent: SDSerialDigitalInput
           type: int32
          usage: getControls (but not during a transfer)

          PARAM: ML_IMAGE_COMPRESSION_INT32
         parent: SDSerialDigitalInput
           type: int32
           enum: ML_COMPRESSION_UNCOMPRESSED
          usage: get/setControls (but not during a transfer)

          PARAM: ML_IMAGE_COLORSPACE_INT32
         parent: SDSerialDigitalInput
           type: int32
           enum: ML_COLORSPACE_RGB_601_FULL,
                 ML_COLORSPACE_CbYCr_601_FULL
          usage: get/setControls (but not during a transfer)

          PARAM: ML_IMAGE_PACKING_INT32
         parent: SDSerialDigitalInput
           type: int32
           enum: ML_PACKING_8
          usage: get/setControls (but not during a transfer)

          PARAM: ML_IMAGE_SAMPLING_INT32
         parent: SDSerialDigitalInput
           type: int32
           enum: ML_SAMPLING_411,
                 ML_SAMPLING_422,
                 ML_SAMPLING_444
          usage: get/setControls (but not during a transfer)

          PARAM: ML_IMAGE_WIDTH_INT32
         parent: SDSerialDigitalInput
           type: int32
          usage: get/setControls (but not during a transfer)

          PARAM: ML_IMAGE_HEIGHT_1_INT32
         parent: SDSerialDigitalInput
           type: int32
          usage: get/setControls (but not during a transfer)

          PARAM: ML_IMAGE_HEIGHT_2_INT32
         parent: SDSerialDigitalInput
           type: int32
          usage: get/setControls (but not during a transfer)

          PARAM: ML_IMAGE_INTERLEAVE_MODE_INT32
         parent: SDSerialDigitalInput
           type: int32
           enum: ML_INTERLEAVE_MODE_SINGLE_FIELD
          usage: get/setControls (but not during a transfer)

          PARAM: ML_IMAGE_SKIP_ROWS_INT32
         parent: SDSerialDigitalInput
           type: int32
        min-max: [0 - 0]
          usage: get/setControls (but not during a transfer)

          PARAM: ML_IMAGE_SKIP_PIXELS_INT32
         parent: SDSerialDigitalInput
           type: int32
        min-max: [0 - 0]
          usage: get/setControls (but not during a transfer)

          PARAM: ML_IMAGE_ROW_BYTES_INT32
         parent: SDSerialDigitalInput
           type: int32
        min-max: [0 - 0]
          usage: get/setControls (but not during a transfer)

          PARAM: ML_VIDEO_TIMING_INT32
         parent: SDSerialDigitalInput
           type: int32
           enum: ML_TIMING_525
          usage: get/setControls (but not during a transfer)

          PARAM: IIDC_VIDEO_TIMING_INT32
         parent: SDSerialDigitalInput
           type: int32
           enum: IIDC_TIMING_525_0375p,
                 IIDC_TIMING_525_0750p,
                 IIDC_TIMING_525_15p,
                 IIDC_TIMING_525_30p
          usage: get/setControls (but not during a transfer)

          PARAM: ML_VIDEO_SIGNAL_PRESENT_INT32
         parent: SDSerialDigitalInput
           type: int32
           enum: ML_TIMING_NONE,
                 ML_TIMING_UNKNOWN
          usage: getControls

and mlquery will get all the device's advertised capabilities :D Trial and error is more my style but this is pretty handy ...

Re: Firewire Video via DM10 and Apple iSight FW

Posted: Fri Mar 04, 2016 12:01 pm
by uunix
Today arrived a firewire capable of reaching my AJA loLA & loLD so I was able to start my video in testing. I presumed the AJA would output a stream of video, but had to get over the bridge of it being recognized first. I also connected a Panasic Mini DV camera.

I shutdown the machine, connected it all up and all seemed good.

Code: Select all

Mar  4 18:43:52 6A:fuel01 unix: IRIX Release 6.5 IP35 Version 07202013 System V - 64 Bit
Mar  4 18:43:52 2A:fuel01 unix: Copyright 1987-2006 Silicon Graphics, Inc.
Mar  4 18:43:52 2A:fuel01 unix: All Rights Reserved.
Mar  4 18:43:52 2A:fuel01 unix:
Mar  4 18:43:52 5A:fuel01 unix: NOTICE: Initialising Guaranteed Rate I/O v2 (Jul 20 2006 18:47:01)
Mar  4 18:43:52 6A:fuel01 unix: Scanning FireWire bus /hw/module/001c01/Ibrick/xtalk/14/pci/1/ohci/0 (2 nodes)
Mar  4 18:43:52 6A:fuel01 unix: FireWire Node [0]: <6>AJA Video Systems Inc, IoLD   
Mar  4 18:43:52 6A:fuel01 unix: Scanning FireWire bus /hw/module/001c01/Ibrick/xtalk/14/pci/1/ohci/0 (2 nodes)
Mar  4 18:43:52 6A:fuel01 unix: FireWire Node [0]: <6>AJA Video Systems Inc, IoLD   
Mar  4 18:43:52 6A:fuel01 unix: FireWire Node [2]: <6>MATSUSHITA ELECTRIC IND. CO, NV-GS17


So next step, fwprobe

Code: Select all

fuel01 35# fwprobe
Probing DM10 cards...
Number of cards: 1
Card Info
=========
Card #: 0
Name  : DM10
ID    : 0x309500A001EE5A
Ports : 3
Speed : 400 / 400

3 devices attached
Device 0: 0x309500A001EE5A
  Vendor: Silicon Graphics, Inc.
   Model: Unknown
   Proto: Unknown
Device 1: 0xC170000000AEA
  Vendor: AJA Video Systems Inc
   Model: IoLD   
   Proto: Unknown
Device 2: 0x804580C1465854
  Vendor: MATSUSHITA ELECTRIC IND. CO
   Model: NV-GS17
   Proto: AV/C


OK So far so good, I then compiled all the dmedia tools. To run though I needed the location.. so mlquery -d all

Code: Select all

fuel01 36# mlquery -d all

         DEVICE: nullXcode
         parent: fuel01.
          index: 0
        version: 1.0
       location: Software Null Xcode Device
         xcodes: nullXcodeMemoryToMemoryCopy,
                 nullXcodeMemoryClear

Nothing.. OK so, I could sort of see why the AJA may have a problem, but the MiniDV ?

I have restarted mldaemon a few times times, plus a complete shutdown when I change device.

Any ideas?

[Edit] running mlquery on its own indicates it no installed devices

mlquery on my Octane2 shows
xt-digvid:1
nullXcode:0

Whereas on the Fuel just shows nullXcode.

I have installed 6.5.21_dmediapro_dm10_1.0.1 (DMediaPro DM10 Execution Environment 1.0.1 for IRIX) is there a later version?

Re: Firewire Video via DM10 and Apple iSight FW

Posted: Fri Mar 04, 2016 9:31 pm
by ClassicHasClass
You probably need the DMedia 1.1 beta drivers, see rec's post here: viewtopic.php?f=14&t=16724415#p7333432

The Matsushita camera should work, at least.

Re: Firewire Video via DM10 and Apple iSight FW

Posted: Sat Mar 05, 2016 11:09 am
by uunix
ClassicHasClass wrote:You probably need the DMedia 1.1 beta drivers, see rec's post here: viewtopic.php?f=14&t=16724415#p7333432

The Matsushita camera should work, at least.

Nice one Mr Classic, I missed that snippet and thought I was indeed installing the latest..

So I have better news, it is indeed picking up something (I'm guessing at the moment it's the Panasonic/Matsushita).

Code: Select all

fuel01 1# mlquery -d all

         DEVICE: nullXcode
         parent: fuel01.
          index: 0
        version: 1.0
       location: Software Null Xcode Device
         xcodes: nullXcodeMemoryToMemoryCopy,
                 nullXcodeMemoryClear

         DEVICE: dv-deck
         parent: fuel01.
          index: 0
        version: 1
       location: /hw/firewire/0/avc/avc0
          jacks: VideoInputJack,
                 VideoOutputJack
          paths: AnalogInput,
                 AnalogOutput