Just replace the definitions of 'device' and 'engine' with 'ice' instead of 'impact' and it shouldwork ok on O2.

It could be that without specifying the parameters fully, it's defaulting to something unwise,like single-frame capture and fixed a percentage quality factor (MJPEG on O2 works betterwith 2-field capture and fixed bitrate).

Hmm, my O2 is off atm. I'll check later, make sure the above is correct.

There are some other example commands on the page, and aliases to make things easier. See theman page for dmrecord on your O2 for more info and other settings specific to O2. Note that thecomment on my IMPACT page about playing to the screen with audio is not relevant to O2.

Btw, I'd want more than 128MB RAM for doing video stuff on an O2. 256MB minimum is best IMO.

The one good thing though is that at least you are trying to use dmrecord. Very wise, as it's morereliable than MediaRecorder; just a somewhat steeper learning curve. Worth the effort though. Andassuming you have a recent enough OS version, O2 can capture as AVI aswell, which makes iteasier to port files to a PC (convert to other formats for free with the MidVid JPEG codec, oruse the PIC codec which costs $99 but is 20% faster than MidVid; use VirtualDUB, AVIdemux orother application to convert to DivX).

Cheers!

Ian.

Last edited by mapesdhs on Sat May 23, 2009 6:57 am, edited 1 time in total.

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 items I can sell to provide funds are also welcome.mapesdhs@yahoo.com+44 (0)131 476 0796+44 (0)7434 635 121

It works for around 8 seconds usually and then stops capturing. Without an audio track I was able to capture for minutes without a problem...

Is this related to the limited RAM (128MB) I have?

I also tried capturing using media tools -> movie recorder but after capturing it has to process the movie for ages... I mean, if the O2 does the jpeg compression in hardware it shouldn't have to do that right?!

And even using movie recorder it gave me buffer errors once or twice...

It works for around 8 seconds usually> and then stops capturing. Without an audio track I was able to capture for minutes without a problem...

Odd... perhaps the audio is not being dealt with properly.

> Is this related to the limited RAM (128MB) I have?

Hard to say, I've never done video stuff on an O2 with that little RAM.

> I also tried capturing using media tools -> movie recorder but after capturing it has to process the movie for ages... > I mean, if the O2 does the jpeg compression in hardware it shouldn't have to do that right?!

That will happen if you select single-frame instead of 2-field for the compression format.

It works for around 8 seconds usually and then stops capturing. Without an audio track I was able to capture for minutes without a problem...

Is this related to the limited RAM (128MB) I have?

I also tried capturing using media tools -> movie recorder but after capturing it has to process the movie for ages... I mean, if the O2 does the jpeg compression in hardware it shouldn't have to do that right?!

And even using movie recorder it gave me buffer errors once or twice...

jmc

Hi, I have this command(found similiar version on Ian's pages) modified in aliases:dmrecord -a -v -p audio -p video,comp=jpeg,quality=98 output.mv

Only limitation on my system is disk speed so I cant write fast enough video with quality=100. My disks are old SGI/IBM 9gb 7200rpm and capabe of ~7-9mb/s writes in classic use (big files copying). But this is done with 100% system load (checked trough top, copying done with neko_mc). It is normal?

Also you must have on mind that as disk becomes more filled, it SLOWS down writes. Not even talking about this alert window:

1-2 seconds before this happends O2 becomes like kicked to the head. After displaying alert window everything becomes normal again.

My sugestion is start with low quality parameters eg. 75 and then go higher.Also don't run anything system demanding on background. Check it trough top maybe you will be surprised how many cpu power is wasted on something that do nothing - like neko_xmms on my system it draws 3% of cpu - when idling (not playing anything and is displayed on other desktop) Seamonkey & etc are mutch worst on this.

If you don't solve this problem I can strip my sytem to minimal ram config (64) and try to record some video we will see...

That command is specifying constant quality. O2's ICE system works better with a constant bitrate.

Constant quality means the size of each compressed frame can vary enormously, giving an uneven flow intothe compression engine. The microcode was optimised for constant bitrate, ie. a more even flow. Thus, insteadof quality=98, try brate=25000000. That should work better.

> Only limitation on my system is disk speed so I cant write fast enough video with quality=100. My disks are old SGI/IBM> 9gb 7200rpm and capabe of ~7-9mb/s writes in classic use (big files copying). But this is done with 100% system load> (checked trough top, copying done with neko_mc). It is normal?

For reference, if it's of any help, I have 73GB 1.6" SCA 10K disks normally for 35 UKP each, but make it 30 for any Nekomember (lots available, suitable as external drives, 60 day warranty). I also have R7K/600 CPU modules available, ready to use.

No, use lower bitrates, like 20M, and go higher. Assuming the disk can take it, 30Mbit gives good quality, no need to goany higher than that.

> Also don't run anything system demanding on background. Check it trough top maybe you will be surprised how many> cpu power is wasted on something that do nothing - like neko_xmms on my system it draws 3% of cpu - when idling> (not playing anything and is displayed on other desktop) Seamonkey & etc are mutch worst on this.

My IMPCOM advice page has some suggestions on this. Turn off all unnecessary background daemons (except XLVif you need it) and shut down mediad/httpd, and anything else not needed:

And: It worked I tried capturing sevaral movie files ranging from a few seconds to a few minutes and had no problem (yet)

I was wondering what the difference was to last time and the only thing I can think of is that I changed from NTSC to PAL in the mediarecord settings. Something I did not do when capturing with dmrecord the first time because the videoin signal was ok... at least on screen. Was this really it?! I will do another session and see if I get any errors... "touch wood"

This line keeps repeating with different buffer values and the recording is stopped.

When using mediarecorder sometimes it workes to capture as two-field full res Pal using JPEG compression... and the next time it won't work. Then the video input freezes every few seconds when capturing. When I stopped the recording I even got a completely frozen system and had to pull the plug...