Support and General Use > Recording

WARNING: current CVS recording code not stable [ NOW FIXED! ]

<< < (11/11)

petur:

--- Quote from: jhMikeS on May 08, 2007, 12:02:05 PM ---Petur: Was going to mention before you ran out of IRC that I do know of trouble spots in the scheduler itself...I suppose I shouldn't delay repairs there and I'll give each bit of the threading a thorough exam. It's likely the cause of the blocking violations and perhaps this one as well.

--- End quote ---

Ah... ok... and sorry for running away just like that, things are getting a bit hectic at work...


--- Quote from: jhMikeS on May 08, 2007, 01:40:00 PM ---Both iRivers have backlight fading? This has caused the scheduler to get borked on my H120 recording and must be due to the known scheduler issue.
--- End quote ---
of the irivers, only the h1x0 has fading, the h3x0 uses a different type of backlight control that has less steps.

perjak:

--- Quote from: jhMikeS on May 08, 2007, 01:33:08 PM ---Warning: 0x00000001 -> PCM buffer overflow
Warning: 0x00000002 -> Encoder buffer overflow
Warning: 0x00000003 -> Both of those

Flashed over the time display.


--- End quote ---

For some seconds or will warning(s) be visible when the show is over and I take the iRiver out of my pocket? I usually do stealth recordings and when gain is set I park the iRiver in my pocket.

I only check it again if soundlevel at venue increases dangerously  :D

Per in Denmark

jhMikeS:
The warnings stick until:

1) You leave the recording screen :)
2) You press stop and then start a new recording.

jhMikeS:
Petur, here's an old flyspray task you might be interested in that strongly suggests the corruption on full disk is not a part of the recording code at all and is not new.

Reported 9 days before the introduction of codec based recording:

265 days old: Running out of space corrupts recorded file
http://www.rockbox.org/tracker/5852

petur:

--- Quote from: jhMikeS on May 11, 2007, 08:21:52 PM ---Petur, here's an old flyspray task you might be interested in that strongly suggests the corruption on full disk is not a part of the recording code at all and is not new.

Reported 9 days before the introduction of codec based recording:

265 days old: Running out of space corrupts recorded file
http://www.rockbox.org/tracker/5852

--- End quote ---
Thanks... I'll try to find some time to dive into that code (but most of coming week is already booked by real life)

Navigation

[0] Message Index

[*] Previous page

Go to full version