Support and General Use > Recording
WARNING: current CVS recording code not stable [ NOW FIXED! ]
petur:
Mike, I get a bit worried when I read
http://taperssection.com/index.php/topic,83004.msg1117129.html#msg1117129 and
http://taperssection.com/index.php/topic,84121.msg1117466.html#msg1117466
It seems like the person who recently had a warning displayed on his display was using a svn version of 7 March 2007, not the REP..... (confirmation pending)
So far all _my_ recordings have been fine.
jhMikeS:
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.
perjak:
--- Quote ---I can only join jhMikeS: update....
--- End quote ---
Done yesterday!
--- Quote ---Stability was verified for that in the field and in buffer checks.
--- End quote ---
What can I do to test? Just record and listen closely afterwards? Are there any messages on the screen if troubles occur?
How can I check buffer?
Thanks for all your struggle 8-)
Per in Denmark
jhMikeS:
Warning: 0x00000001 -> PCM buffer overflow
Warning: 0x00000002 -> Encoder buffer overflow
Warning: 0x00000003 -> Both of those
Flashed over the time display.
jhMikeS:
petur: also, I myself am confusing the two warnings...when I'm just not awake yet. :o Well, no matter, Semayat had an encoder buffer overflow which could still be caused by that. 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. Well, I'm on that one since a solid base for everything must be in place since corrupting the scheduler with IRQ posts can kill threads permanently. That would also explain the inability to shut down since pcmrec must work for shutdown to proceed.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version