SGI: Video

Octane Impact Compression

So, it seems there's an at least an occasional issue with using an Octane compression board on a system with more than a certain amount a RAM (one GB?); the system it's installed in currently has 2 GB. (Though sometimes it works, sometimes it just stops everything.)

Since it's not possible to just turn off banks o' DIMMs (per viewtopic.php?f=3&t=16728287 ), is it possible to constrain how much ram is available to a command (dmrecord &c.) invoked from the shell? Or does this just not matter?

(Why not just physically remove the RAM? It's a pain. And I really have nowhere safe to put it. And I think I really need to squeeze all of the toys into one single physical box, simplify my life into that, and call it good. Right now, I've got capabilities spread between basically two boxes, and I'd like to consolidate. If possible.)
Scott Elyard cgfx.us
:Octane2: Sarcosuchus_imperator :Octane: Liopleurodon :Indigo2: Carcharodon :Indy: Helicoprion :Indigo: Paradoxides
How are you using dmrecord? What command line options? Like, if you're recording 30 seconds of video you should be able to easily see how much RAM it's grabbing by running top in a terminal window, at a fast refresh rate. Make sure top is only showing processes running under your user ID to make it easier to see what dmrecord is doing.
Project:
Temporarily lost at sea...
Plan:
World domination! Or something...
scottE wrote: So, it seems there's an at least an occasional issue with using an Octane compression board on a system with more than a certain amount a RAM (one GB?); the system it's installed in currently has 2 GB. (Though sometimes it works, sometimes it just stops everything.)
From the information in this thread it sounded like the issue with the OCO and RAM came down to the size, type or brand of memory installed.
In that thread bigD wrote: I finally got around to playing with this more, and this morning I gave it a workout using dmrecord. It *generally* works just fine, but still seemingly crashes at random intervals. I'll play a clip back perfectly one time, but the system will go down if I immediately try to play it again.

All I had installed were two 1GB Dataram sticks, so I removed those and took my system down to 1.25GB using the various 256MB and 128MB sticks I still have laying around. And lo and behold, I can't get the system to crash anymore. I've recorded gigs of video, played it back over and over again, tried different compression settings and methods, and everything just works. ::knock on wood::

So it appears that at least in my case, the compression option doesn't like the 1GB sticks of Dataram memory. Perhaps it just doesn't like higher capacity memory at all - I dunno. That might be what lead people to think that it wouldn't work with more than 2GB installed - you'd need 1GB or 512MB sticks to accomplish that (I don't have any 512MB modules to test with).
***********************************************************************
Welcome to ARMLand - 0/0x0d00
running...(sherwood-root 0607201829)
* InfiniteReality/Reality Software, IRIX 6.5 Release *
***********************************************************************
I'd nearly to completely forgotten about that thread (and I was a participant! awkward); I'll have to check both boxes when I get back. It really would be nice to get back to dubbing laserdiscs again, even if it is a pain to have to replace a bunch of RAM. (Also on the list of hardware needs: a player. The old one died a while back.)

I suppose if push comes to shove, I could just rely on the O2 ( Pholidosaur ) for dub work.
Scott Elyard cgfx.us
:Octane2: Sarcosuchus_imperator :Octane: Liopleurodon :Indigo2: Carcharodon :Indy: Helicoprion :Indigo: Paradoxides