O2 dmrecord error

Video, software tools and techniques on SGI systems.
Forum rules
Any posts concerning pirated software or offering to buy/sell/trade commercial software are subject to removal.
jmc
Posts: 135
Joined: Thu Feb 14, 2008 1:23 pm
Location: Germany

Re: O2 dmrecord error

Unread postby jmc » Wed Jul 22, 2009 8:18 am

Hi!

I will try the tests later.

The 1st error looks like the system disk is full.
Well I have about 63GB free space on that drive. :?

Thanks,
jmc
:Onyx2:

User avatar
cadmo
Posts: 40
Joined: Tue Dec 12, 2006 2:11 am
Location: Italy

Re: O2 dmrecord error

Unread postby cadmo » Wed Aug 12, 2009 11:24 am

Got the same error!
Error in dmedia library : dmlICReceive failed: Compress failed : hw timeout
After YEARS of no errors!
Have you solved this problem?
Marco
Italy

rooprob
Posts: 75
Joined: Wed Sep 01, 2010 7:20 am

Re: O2 dmrecord error

Unread postby rooprob » Sun Feb 05, 2012 9:35 am

Temperamental indeed.

I find myself with this problem - after several successful records of many minutes of footage, the next and subsequent invocations just will not capture. A reboot fixes the problem.

OK so something less invasive: reset the video system, sudo ml unld mvp driver, as suggested in the man O2Video. We see the slight pause on the next invocation as the kernel modules are reloaded, but we still cannot capture.

I did try recording as root and my system froze immediately. Pah! That was with logging as my user and using sudo. I tried logging in as root instead, and successfully recorded a few times until a total freeze on invocation. I the initiated reader would immediately point to h/w failure, like memory, but I'm not convinced.

Lets go back to just being a normal user and using dmrecord.

So what's going on ? top, par and gr_osview are my current observation points. In normal "working" operation we can see some, but not excessive CPU user and sys percentage, but mostly idle, as we'd expect as the video is being processed by ICE. In borked operation, we see a hugely increased amount of sys, which is kernel sys call activity. There are no other background tasks stealing cpu.

Why would this be? I'm still trying to find out. dmrecord or mediarecorder both fork a child to do the recording, and it's the combined CPU time consumed by the pair that breaches what the system can do, introduces the hiccup and as I'm cancelling the capture on a drop, dropping the session. In my par output of mediarecorder I have gazillions of select and ioctl calls, but my skills in this area make the system a bit opaque. Oddly I cannot get par and dmrecord to give me any data on the child process (FIX you have to run par as root).

You might thing par has something to do with it too, but when we're in a working state, I have enough headroom to have par collect stats.

oo@mapleleaf:~/MovieTest dmrecord -C -v -p video -p audio dmrec0.mv
Options:
Audio channels: 2
Video device: mvp
Input port: 'Camera Video Input' (1)
Compression scheme: jpeg
Compression engine: ice
Quality: 75
Audio rate: 44100hz
Image (field) height: 240
Image width: 640
video timing = VL_TIMING_525_SQ_PIX
DM_IMAGE_PIXEL_ASPECT = 1.000000

Hit the Enter key to begin recording...
Hit <ctrl>-c to stop recording...

Expecting buffer 11 from video, got buffer 23 instead


Warning: Expecting buffer 11 from compressor, got buffer 23 instead

Error capturing image frame 5
Post-processing output file 'dmrec0.mv' ...
Timing information:
5 image frames = 0.17 seconds of video captured.

Compression information:
Average compressed frame size: 20062.4 bytes
Average compression ratio: 30.6 : 1
Bit rate achieved: 4810161.0 bits/sec

Tried a few things: sudo ml unload the mvp and ice modules and retry - no joy. Tried systune mvpearly_frontiemsc = 0 (was 1) no change.
The only thing that reliably works is a full reboot. Then I can get 4 successful captures, then no more.
Actually sometimes it fixes itself and I can get a few more, but it's not reliable.

And then - just like that, the time it took me to write this out, it's working. Argh!

oo@mapleleaf:~/MovieTest sudo par -e ioctl -e select -i -o dmrec.par dmrecord -t 30.0 -C -v -p video -p audio dmrec0.mv
Options:
Audio channels: 2
Video device: mvp
Input port: 'Camera Video Input' (1)
Compression scheme: jpeg
Compression engine: ice
Quality: 75
Audio rate: 44100hz
Image (field) height: 240
Image width: 640
video timing = VL_TIMING_525_SQ_PIX
DM_IMAGE_PIXEL_ASPECT = 1.000000

Hit the Enter key to begin recording...

Recording was done in real time successfully.
Post-processing output file 'dmrec0.mv' ...
Timing information:
899 image frames = 30.00 seconds of video captured.

Compression information:
Average compressed frame size: 19717.6 bytes
Average compression ratio: 31.2 : 1
Bit rate achieved: 4727497.5 bits/sec

and it works...

oo@mapleleaf:~/MovieTest time dmrecord -t 30.0 -C -v -p video -p audio dmrec0.mv
Options:
Audio channels: 2
Video device: mvp
Input port: 'Camera Video Input' (1)
Compression scheme: jpeg
Compression engine: ice
Quality: 75
Audio rate: 44100hz
Image (field) height: 240
Image width: 640
video timing = VL_TIMING_525_SQ_PIX
DM_IMAGE_PIXEL_ASPECT = 1.000000

Hit the Enter key to begin recording...
Recording was done in real time successfully.
Post-processing output file 'dmrec0.mv' ...
Timing information:
899 image frames = 30.00 seconds of video captured.

Compression information:
Average compressed frame size: 17976.1 bytes
Average compression ratio: 34.2 : 1
Bit rate achieved: 4309947.1 bits/sec
0.698u 3.677s 0:32.16 13.5% 0+0k 2+4io 1pf+0w

and it doesn't work... meh :( It sucks being an SGI aficionado...

oo@mapleleaf:~/MovieTest time dmrecord -t 30.0 -C -v -p video -p audio dmrec0.mv
Options:
Audio channels: 2
Video device: mvp
Input port: 'Camera Video Input' (1)
Compression scheme: jpeg
Compression engine: ice
Quality: 75
Audio rate: 44100hz
Image (field) height: 240
Image width: 640
video timing = VL_TIMING_525_SQ_PIX
DM_IMAGE_PIXEL_ASPECT = 1.000000

Hit the Enter key to begin recording...

Expecting buffer 11 from video, got buffer 13 instead


Expecting buffer 15 from video, got buffer 17 instead


Warning: Expecting buffer 11 from compressor, got buffer 13 instead

Error capturing image frame 5
Post-processing output file 'dmrec0.mv' ...
Timing information:
5 image frames = 0.17 seconds of video captured.

Compression information:
Average compressed frame size: 17068.8 bytes
Average compression ratio: 36.0 : 1
Bit rate achieved: 4092415.5 bits/sec
0.027u 0.272s 0:01.94 14.9% 0+0k 2+5io 1pf+0w

CPU: MIPS R12000 Processor Chip Revision: 2.3
FPU: MIPS R12010 Floating Point Chip Revision: 0.0
1 300 MHZ IP32 Processor
Main memory size: 768 Mbytes
Secondary unified instruction/data cache size: 1 Mbyte on Processor 0
Instruction cache size: 32 Kbytes
Data cache size: 32 Kbytes
FLASH PROM version 4.18
Integral SCSI controller 0: Version ADAPTEC 7880
Disk drive: unit 2 on SCSI controller 0
CDROM: unit 4 on SCSI controller 0
Integral SCSI controller 1: Version ADAPTEC 7880
On-board serial ports: tty1
On-board serial ports: tty2
On-board EPP/ECP parallel port
CRM graphics installed
Integral Ethernet: ec0, version 1
Iris Audio Processor: version A3 revision 3
Video: MVP unit 0 version 1.4
AV: AV1 Card version 1, O2Cam type 1 version 0 connected.
Vice: TRE

oo@mapleleaf:~/MovieTest /sbin/uname -R
6.5 6.5.26m
:O2: r12 400 mapleleaf :Indigo2IMP: r10 195 IRIS :Cube: NeXT
New Zealand

rooprob
Posts: 75
Joined: Wed Sep 01, 2010 7:20 am

Re: O2 dmrecord error

Unread postby rooprob » Sun Feb 05, 2012 10:09 am

rooprob wrote:And then - just like that, the time it took me to write this out, it's working. Argh!


... and after *five minutes* it works....

Interesting that IRIX has a unload delay of 5 minutes for many of it's modules....
I did say I tried unloading both mvp and vice myself, and it didn't cleanup the problem for me. However leaving the machine idle for 5 minutes and returning to the test, we see a successful recording...

Now how' to script this.... Wait another 5 minutes and see what modules are still loaded.

oo@mapleleaf:~/MovieTest sudo ml list

Loaded Modules:
Id: 6 Character device driver: prefix plp, major 38, unload delay 5 minutes, filename /var/sysgen/boot/ecplp.o
Id: 4020 File system: filename /usr/vice/etc/sgiload/libafs.IP32.nonfs.o
Id: 6000 Symbol Table module: unload delay 5 minutes, filename /unix


Registered Modules:
Id: 2 Character device driver: prefix pciba_, unload delay 5 minutes, filename /var/sysgen/boot/pciba.o
Id: 1013 Streams module: prefix kbd, fmodsw name kbd, unload delay 5 minutes, filename /var/sysgen/boot/kbd.o
Id: 3 Character/Block device driver: prefix smfd, unload delay 5 minutes, filename /var/sysgen/boot/smfd.o
Id: 4 Character device driver: prefix ts_, unload delay 5 minutes, filename /var/sysgen/boot/ts.o
Id: 5 Character device driver: prefix tpsc, unload delay 5 minutes, filename /var/sysgen/boot/tpsc.o
Id: 1014 Streams module: prefix ptrmap, fmodsw name ptrmap, unload delay 5 minutes, filename /var/sysgen/boot/ptrmap.o
Id: 1015 Streams module: prefix wacom, fmodsw name wacom, unload delay 5 minutes, filename /var/sysgen/boot/wacom.o
Id: 1016 Streams module: prefix magellan, fmodsw name magellan, unload delay 5 minutes, filename /var/sysgen/boot/magellan.o
Id: 1017 Streams module: prefix imp, fmodsw name imp, unload delay 5 minutes, filename /var/sysgen/boot/imp.o
Id: 1018 Streams module: prefix hitachi, fmodsw name hitachi, unload delay 5 minutes, filename /var/sysgen/boot/hitachi.o
Id: 1019 Streams module: prefix calcomp, fmodsw name calcomp, unload delay 5 minutes, filename /var/sysgen/boot/calcomp.o
Id: 1020 Streams module: prefix tablet, fmodsw name tablet, unload delay 5 minutes, filename /var/sysgen/boot/tablet.o
Id: 1021 Streams module: prefix sball, fmodsw name sball, unload delay 5 minutes, filename /var/sysgen/boot/sball.o
Id: 1022 Streams module: prefix dialbox, fmodsw name dialbox, unload delay 5 minutes, filename /var/sysgen/boot/dialbox.o
Id: 1023 Streams module: prefix dial, fmodsw name dial, unload delay 5 minutes, filename /var/sysgen/boot/dial.o


Registered and Currently Loaded Modules:
Id: 0 Character device driver: prefix vice, major 17, unload delay 5 minutes, filename /var/sysgen/boot/vice.o
Id: 1 Character device driver: prefix mvp, major 9, unload delay 5 minutes, filename /var/sysgen/boot/mvp.o
:O2: r12 400 mapleleaf :Indigo2IMP: r10 195 IRIS :Cube: NeXT
New Zealand

rooprob
Posts: 75
Joined: Wed Sep 01, 2010 7:20 am

Re: O2 dmrecord error

Unread postby rooprob » Sun Feb 05, 2012 11:08 am

This isn't it either. Left system for 30 mins, first two tries failed, the next worked.

This smells more like some kind of software bug in either the mvp kernel module or the dm library interaction in these tools. Time to battle with the dm code directly....
:O2: r12 400 mapleleaf :Indigo2IMP: r10 195 IRIS :Cube: NeXT
New Zealand

rooprob
Posts: 75
Joined: Wed Sep 01, 2010 7:20 am

Re: O2 dmrecord error

Unread postby rooprob » Sun Feb 05, 2012 12:59 pm

Would be interested in any fellow O2 user with an O2cam, if they wouldn't mind wasting a couple of minutes:

With mediarecorder, select Tasks -> Movie -> Video Production JPEG and try and record more than 6 individual 20second clips one after another without it dropping a frame. I get to the 6th and they it wont record anymore without resorting to waiting for more than 5 minutes or rebooting.

Tell me what OS rev you are, and the CPU type.
Thanks a bunch,
:O2: r12 400 mapleleaf :Indigo2IMP: r10 195 IRIS :Cube: NeXT
New Zealand

rooprob
Posts: 75
Joined: Wed Sep 01, 2010 7:20 am

Re: O2 dmrecord error

Unread postby rooprob » Tue Feb 07, 2012 10:36 am

Tried 6.5.30m. Basically the same results at recording. Didn't fix this sys storm.

Removed all the RAM, started reinstalling in pairs. I have two pairs of 128 and two pairs or 64.

Observation. It's ok with 256MB ram, seems to record reliably all the time. Doesn't matter whether it's 2x 128 or 4x64. So discounting the slots or the sticks.

Put in 384 (256 +128) and it's records and fails to record in even amounts. When it fails to record, it often only does twice

Found out about timex -p

Good:
18:08:34 vflt/s dfill/s cache/s pgswp/s pgfil/s pflt/s cpyw/s steal/s rclm/s
18:10:13 8.86 3.01 5.80 0.00 0.01 0.76 0.59 3.18 0.00
18:08:34 physmem kernel user fsctl fsdelwr fsdata freedat empty
18:10:13 98304 13870 12881 863 1691 13969 1117 53913

Bad:
17:54:59 vflt/s dfill/s cache/s pgswp/s pgfil/s pflt/s cpyw/s steal/s rclm/s
17:55:03 182.26 32.90 148.33 0.00 2.83 19.28 15.17 37.02 0.00
17:54:59 physmem kernel user fsctl fsdelwr fsdata freedat empty
17:55:03 98304 12919 12504 356 28 1716 464 70317

More faults (vflts/s) and less pages of free memory that may be reclaimable (freedat), this is the %sys activity that kills it. So what's all this about? what's the relationship between this and the installed ram, and is it more a systune? I know MIPS uses two memory segments for kernel data structures.

man sar(1)
-p Report paging activities:
vflt/s - address translation page faults (valid page not in memory);
dfill/s - address translation fault on demand fill or demand zero
page;
cache/s - address translation fault page reclaimed from page cache;
pgswp/s - address translation fault page reclaimed from swap space;
pgfil/s - address translation fault page reclaimed from filesystem;
pflt/s - (hardware) protection faults -- including illegal access to
page and writes to (software) writable pages;
cpyw/s - protection fault on shared copy-on-write page;
steal/s - protection fault on unshared writable page;
rclm/s - pages reclaimed by paging daemon.

Posting for my own amusement. I'm not expecting anyone to be able to fix this, or there to be any IRIX virtual memory authors haunting this list. Live in hope.
:O2: r12 400 mapleleaf :Indigo2IMP: r10 195 IRIS :Cube: NeXT
New Zealand

User avatar
recondas
Moderator
Moderator
Posts: 5441
Joined: Sun Jun 06, 2004 5:55 pm
Location: NC - USA

Re: O2 dmrecord error

Unread postby recondas » Tue Feb 07, 2012 12:58 pm

rooprob wrote:Observation. It's ok with 256MB ram, seems to record reliably all the time. Doesn't matter whether it's 2x 128 or 4x64. So discounting the slots or the sticks. Put in 384 (256 +128) and it's records and fails to record in even amounts. When it fails to record, it often only does twice
Early on there was an issue with O2s that had more than 256MB of memory installed, but afaik *only* IRIX 6.3 was affected.
***********************************************************************
Welcome to ARMLand - 0/0x0d00
running...(sherwood-root 0607201829)
* InfiniteReality/Reality Software, IRIX 6.5 Release *
***********************************************************************

rooprob
Posts: 75
Joined: Wed Sep 01, 2010 7:20 am

Re: O2 dmrecord error

Unread postby rooprob » Tue Feb 07, 2012 2:46 pm

Yeah I'm on 6.5.30.

So I've read this, particularly the section Checking for Excessive Paging and Swapping.
http://techpubs.sgi.com/library/tpl/cgi ... /ch10.html

Particularly

Code: Select all

-p vflt/s       

Frequency with which a process accessed a page that was not in memory. Compare this number between times of good and bad performance. If the onset of poor performance is associated with a sharp increase of vflt/s, swap I/O may be a problem even if %vswp is low or 0.


I have developed a little test harness to gather par and sar output and tested as root with different RAM configurations.

Code: Select all

mapleleaf 8# cat /usr/people/oo/bin/dm1.par_sched
#!/bin/sh
set -e
# http://techpubs.sgi.com/library/tpl/cgi-bin/getdoc.cgi/0650/bks/SGI_Admin/books/IA_ConfigOps/sgi_html/ch10.html
date=`date '+%Y-%m-%d_%H%M'`

if [ -z "$1" -o -z "$2" ]; then
        echo "usage: $0 <tag> <duration>s"
        exit 0;
fi
tag=$1
duration=$2
script=`basename $0`

export TMPDIR=/var/tmp/$USER/$tag/$script/$date
[ ! -d $TMPDIR ] && mkdir -p $TMPDIR
tmpfile=`mktemp -p $TMPDIR XXXXXXXX`

echo "dm1: output to $TMPDIR"

/usr/lib/sa/sadc 1 1 $tmpfile.sa.out
par -rQQ > $tmpfile.$script.out dmrecord -B auto -t $duration -C -v -2 -p video -p audio $tmpfile.mv || \
        {
                rc=$?
                echo "error: failed $!"
        }

/usr/lib/sa/sadc 1 1 $tmpfile.sa.out
echo "sar report"
echo "=========="
sar -A -f $tmpfile.sa.out
echo "files"
echo "====="
echo $TMPDIR
ls -al $TMPDIR


I am seeing increased vflt/s - page faults (valid page not in memory)

Tested with 256MB, all good. 171 vflt/s (this is a common average result of a few goes)

Code: Select all

mapleleaf 11# sar -p -f /var/tmp/root/256/dm1.par_sched/2012-02-07_2112/gWYG2417.sa.out

IRIX mapleleaf 6.5 07202013 IP32    02/07/12

21:12:33  vflt/s dfill/s cache/s pgswp/s pgfil/s  pflt/s  cpyw/s steal/s rclm/s
21:12:44  171.87   69.49  102.03    0.00    0.09   16.93   11.29   75.13   0.00


Test with 384 MB (results from when it fails to record 10s of video, after several successful attempts)

Code: Select all

mapleleaf 15# sar -p -f /var/tmp/root/384/dm1.par_sched/2012-02-07_2126/wkII1425.sa.out

IRIX mapleleaf 6.5 07202013 IP32    02/07/12

21:26:28  vflt/s dfill/s cache/s pgswp/s pgfil/s  pflt/s  cpyw/s steal/s rclm/s
21:26:30  933.17  374.52  556.73    0.00    0.48   87.02   62.02  399.52   0.00
mapleleaf 16#

mapleleaf 16# sar -p -f /var/tmp/root/384/dm1.par_sched/2012-02-07_2126/ZlPq1410.sa.out

IRIX mapleleaf 6.5 07202013 IP32    02/07/12

21:26:21  vflt/s dfill/s cache/s pgswp/s pgfil/s  pflt/s  cpyw/s steal/s rclm/s
21:26:23 1353.85  544.06  806.99    0.00    0.70  128.67   89.51  583.22   0.00



Very much higher vflt/s, but zero pgswp and pgfil, which are pages retreived from disk.

So what I have is a "non-disk page fault" condition when I *add* more RAM to the box. And it doesn't seem to matter what arrangement of RAM is added (64MB or 128MB sticks) just that it goes wrong above 256MB of RAM.

So something is getting too big for something. Could just be a poorly written dmrecord. It came from 6.3 and the age of 256MB of RAM. People have talked about it being crappy - perhaps it's failing to localize it's resources effectively once RAM gets to the crazy heights of 384 MB and beyond. You can watch RAM deplete the longer you run it, and since it's spooling to disk through ICE it shouldn't be really consuming anything more than a static pool- not actually consuming RAM indefinitely. I'm going to write my own.
:O2: r12 400 mapleleaf :Indigo2IMP: r10 195 IRIS :Cube: NeXT
New Zealand

User avatar
mapesdhs
Posts: 2516
Joined: Mon Nov 10, 2003 4:17 pm
Location: Edinburgh, Scotland
Contact:

Re: O2 dmrecord error

Unread postby mapesdhs » Tue Feb 07, 2012 5:58 pm

If you write your own, and it works, you'll be famous. I'd build a statue. 8)

Ian.
I'm working on a charitable PC build for the Learn Engineering YouTube channel. Please PM/email/call if you'd like to contribute!
Donations of any kind of item I can sell to provide funds are also most welcome.
mapesdhs@yahoo.com
+44 (0)7434 635 121

rooprob
Posts: 75
Joined: Wed Sep 01, 2010 7:20 am

Re: O2 dmrecord error

Unread postby rooprob » Sun Feb 12, 2012 3:21 pm

I like bronze :)

Played around with the systunes, even setting them all the way to 256MB ram settings and nada - cannot stop the vm paging from saturating the capture and preventing from working.

So plan B. Poured over the man pages and lurkers guide while the wife has been doing coursework. I have a prototype in C. Uses the "cross platform" (meaning 6.x) 6.5 dmedia libraries. Architecturally it's using the event model on the vlPath which triggers callbacks - instead of forking/select polling. That much works. It could still go either way as I'm doing something wrong - it's running at something like 4 frames per second. And it doesn't actually save anything yet. Not fully understanding something about dmbuffers and the dmIC. The point of O2 is that only data pointers are passed and devices can all see the same RAM thanks to the UMA design. Perhaps the call overhead in the event model when handling video is too high - the docs says it's really supposed to be for application events. Don't know yet.

Who knows. Anyway, more later in the week.
:O2: r12 400 mapleleaf :Indigo2IMP: r10 195 IRIS :Cube: NeXT
New Zealand

rooprob
Posts: 75
Joined: Wed Sep 01, 2010 7:20 am

Re: O2 dmrecord error

Unread postby rooprob » Thu Feb 16, 2012 4:17 pm

May as well complete this thread.

I found the reason in the source for dmrecord.dmic (/usr/share/src/dmedia), which it seems to share behaviour of the stock utility /usr/sbin/dmrecord.

capture.c
DC(dmBufferSetPoolDefaults(p,options.outbufs,video.xferbytes,DM_TRUE,DM_TRUE));

The establishment of the buffer for the video -> compressor sets both cacheable and mapped to TRUE. This is actually a cache coherency overhead when passing data between the two pools which seems to drive the system into a problem state. When I set to FALSE, I observe consistent realtime compression without any issues over and over.

That was a bit of a rat hole. Learned about the dmedia libraries, written three different versions of dmrecord (forking and event driven), a par parser, some graphviz transformations of the call trace data. Pretty pictures too :)

Educational, but it was finding jrecvid.c on ftp.sgi.com (amazingly still functional) and on a hunch that led me to the apparent fix. Learning is fun.

I'm transitioning jobs at the moment which is why I have a stupid amount of free time right now to expend on this puzzle. (I'm not allowed to touch much at my current job, just hang around to answer questions until the end of the month). I may consider learning motif to make a little UI for my doings.
:O2: r12 400 mapleleaf :Indigo2IMP: r10 195 IRIS :Cube: NeXT
New Zealand

User avatar
mapesdhs
Posts: 2516
Joined: Mon Nov 10, 2003 4:17 pm
Location: Edinburgh, Scotland
Contact:

Re: O2 dmrecord error

Unread postby mapesdhs » Thu Feb 16, 2012 7:15 pm

rooprob wrote:... I may consider learning motif to make a little UI for my doings.


A reliable capture app?? Time to plan that statue... 8)

Ian.

robespierre
Posts: 1578
Joined: Mon Sep 12, 2011 2:28 pm
Location: Boston

Re: O2 dmrecord error

Unread postby robespierre » Sun Feb 19, 2012 4:14 pm

noticed that the O2 docs mention a 256MB limit for direct kernel access to memory.

Code: Select all

For system memory, the full 1GByte memory space is directly accessible to the CPU, but the first 256 MBytes are aliased to KSEG0 so that operating system structures may be mapped without using TLB entries. To access the full 1GByte memory configuration, translation buffer entries are required.


The R5000 has only 48 TLB entries, so there may be more pressure on this resource when capturing in a >128 MB system.
:PI: :O2: :Indigo2IMP: :Indigo2IMP:

User avatar
mapesdhs
Posts: 2516
Joined: Mon Nov 10, 2003 4:17 pm
Location: Edinburgh, Scotland
Contact:

Re: O2 dmrecord error

Unread postby mapesdhs » Sun Feb 19, 2012 4:46 pm

Would it be any different for an R10K/R12K system?

Ian.


Return to “SGI: Video”

Who is online

Users browsing this forum: No registered users and 1 guest