Support and General Use > Recording
Recording Enhancements Pack
redwood:
--- Quote from: NorTheBear on April 19, 2007, 01:49:18 PM ---Hello everybody,
*snip*
Colorized peak meters, e.g.
black = no recording at the moment ||||||||||||
red = recording is running at the moment |||||||||||||||||
yellow = recoding is on hold (i.e. recording is interrupted) |||||||
--- End quote ---
If it were to happen, colorization of the peak meters should be tied in with background and foreground colors because some people don't use the defaults. I for example use a black backgound with blue text, which would render the no recording mode invisble to me.
Personally I think there are better ways to indicate recording status other than meter color or the small indicators in the status bar, but this has been discussed before.
jp
TaperChuck:
I got the:
warning: 000000001
again last night.
I was recording optical in from a Grace v3.
Maybe my hard drive is going bad? My other recorder, iHP-140, was fine. No problems.
TaperChuck:
Could a bad (cracked) optical cable be causing this? Or, is it hard disc or software related? It's frustrating, because I tested for eight hours + last weekend with no problems... Â ???
Is there a version of the REP that is approved, so I can start using that, to see if that's the problem?
Davide-NYC:
--- Quote from: redwood on April 21, 2007, 10:44:07 AM ---
--- Quote from: NorTheBear on April 19, 2007, 01:49:18 PM ---Hello everybody,
*snip*
Colorized peak meters, e.g.
black = no recording at the moment ||||||||||||
red = recording is running at the moment |||||||||||||||||
yellow = recoding is on hold (i.e. recording is interrupted) |||||||
--- End quote ---
Personally I think there are better ways to indicate recording status other than meter color or the small indicators in the status bar, but this has been discussed before.
jp
--- End quote ---
I feel this is a good time to resurrect the BIG STATUS ICON idea.
Also adding a line to the REP that states which input is currently being used would be huge.
[attachment deleted by admin for age]
jhMikeS:
--- Quote from: TaperChuck on April 21, 2007, 01:44:35 PM ---Could a bad (cracked) optical cable be causing this? Or, is it hard disc or software related? It's frustrating, because I tested for eight hours + last weekend with no problems... Â ???
Is there a version of the REP that is approved, so I can start using that, to see if that's the problem?
--- End quote ---
It could I imagine though I'd hope the CPU would properly detect the errors and not flood out the buffers if that's what really happened. I think pulling the connector half way out would give similar problems to that but if the equipment you're using did something bad when trying to keep sync or if the coldfire CPU doesn't report all errors correctly, I'm not sure rockbox can do anything about it.
Despite my idiocy the other day, :) I did notice not every flag is being checked (for real, they're not) and that could possibly be it though I'll have to do some reading and make sure the other flags are at all relevant to detecting stream errors.
So this is either outside the software pervue or else there's some creepy little obscure bug hiding out in the REP or in SVN that messes with digital in. Due to the fact there was a PCM buffer overflow when it really should not even be possible, that's what my gut tells me.
So, I'll just shut my trap now and I'll check my recording debug screen soon. I'd love to have that in SVN so the buffers can be watched but the recording screen isn't modular enough to keep functioning correctly while showing it. That's something I plan to change in the near future.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version