SGI: Hardware

Firewire Video via DM10 and Apple iSight FW - Page 3

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 .
***********************************************************************
Welcome to ARMLand - 0/0x0d00
running...(sherwood-root 0607201829)
* InfiniteReality/Reality Software, IRIX 6.5 Release *
***********************************************************************
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 ...
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?
-----------------------------------------------------------------------
Hey Ho! Pip & Dandy!
MyDungeon() << :Fuel: :Octane2: :Octane2: :Octane2: :Octane: :Indy: MyLoft() << :540: :Octane: MyWork() << :Indy: :Indy: :O2: :O2: :O2: :Indigo: :Indigo:
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.
smit happens.

:Fuel: bigred , 900MHz R16K, 4GB RAM, V12 DCD, 6.5.30
:Indy: indy , 150MHz R4400SC, 256MB RAM, XL24, 6.5.10
:Indigo2IMP: purplehaze , 175MHz R10000, Solid IMPACT
probably posted from Image bruce , Quad 2.5GHz PowerPC 970MP, 16GB RAM, Mac OS X 10.4.11
plus IBM POWER6 p520 * Apple Network Server 500 * HP C8000 * BeBox * Solbourne S3000 * Commodore 128 * many more...
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
-----------------------------------------------------------------------
Hey Ho! Pip & Dandy!
MyDungeon() << :Fuel: :Octane2: :Octane2: :Octane2: :Octane: :Indy: MyLoft() << :540: :Octane: MyWork() << :Indy: :Indy: :O2: :O2: :O2: :Indigo: :Indigo:
That would be my guess. If you go back earlier in the thread, you can see where I capture .dv (I called it MTS at the time but rec found it it was a regular DV stream) off my ADVC-300 and that should work for your camera. If that works, you've joined the FireWire club. :)
smit happens.

:Fuel: bigred , 900MHz R16K, 4GB RAM, V12 DCD, 6.5.30
:Indy: indy , 150MHz R4400SC, 256MB RAM, XL24, 6.5.10
:Indigo2IMP: purplehaze , 175MHz R10000, Solid IMPACT
probably posted from Image bruce , Quad 2.5GHz PowerPC 970MP, 16GB RAM, Mac OS X 10.4.11
plus IBM POWER6 p520 * Apple Network Server 500 * HP C8000 * BeBox * Solbourne S3000 * Commodore 128 * many more...