Support and General Use > Recording

Warning 0000002 (split from Re: Internal noise of HDD-based recorders)

(1/3) > >>

sullen:
I saw that warning 0000002 message tonght recording.  This was my third time with the build I am on, not sure it's late here, and somehow the AGC got turned on for the max of 48db.  I haven't checked the recording yet, just freaked me out with the warning flashing oppoiste the time recorded.  

petur:

--- Quote from: sullen on October 24, 2007, 01:07:58 AM ---I saw that warning 0000002 message tonght recording.  This was my third time with the build I am on, not sure it's late here, and somehow the AGC got turned on for the max of 48db.  I haven't checked the recording yet, just freaked me out with the warning flashing oppoiste the time recorded.
--- End quote ---

1) don't hijack threads, start a new one

2) get in touch with jhMikeS on IRC about the warning issue

jhMikeS:
A few things:


* This build has no patches of any sort?
* It's the latest SVN (post kernel improvements)? Locking used in the disk writing could lag before.
* Was the recording missing even one small bit of data? Warning 00000002 should invariably mean at least one encoded chunk needed to be dumped. If the recording was fine, something else could be clobbering the warnings variable. The AGC thing makes me wonder.
* Disk has sufficient free space and wasn't heavily fragmented?

jhMikeS:
We'll move this to somthing more appropriate of course if discussion continues.

AlexP:
I've split this from the original thread.

Navigation

[0] Message Index

[#] Next page