Recording Enhancements Pack

[amoergosum]

There is a setting that starts up straight into the recording screen. Then I think it's only a matter of pressing one button?

This topic refers:

http://forums.rockbox.org/index.php?topic=8793.msg68096#msg68096

yes...but it would be great if you had the choice of having to
press that button or not...

[amoergosum]

Hi,
I’ve noticed that there’s a lot more hiss with RB when recording somebody who's speaking  for  example. There’s less hiss with the Iriver firmware.
How’s that possible?
Ben

[Davide-NYC]

It's not.

This is probably a function of AGC. Turn it off or play with the settings.

 

[amoergosum]

It's not.

This is probably a function of AGC. Turn it off or play with the settings.

 

no....it doesn't have anything to do with that...
I always turn off AGC.
/Ben

[Llorean]

What format are you recording in?

[petur]

and which gain levels. Anything above +15dB will give audible hiss. Get an external pre-amp if you need more amplification

[amoergosum]

I just recorded two test files.
Both were recorded with maximum gain in order to hear the difference.
One with the Iriver firmware, the other with RB.
When I listen to the two files they seem to be equal in volume.
What I noticed was that there’s much (!) more hiss with the RB version.
How’s that possible?

[petur]

you have no idea what gain settings the original firmware uses so you can't compare them.
Using max gain will give you A LOT of hiss. As the whole gain and ADC thing is done by a hardware chip, I don't see how noise levels can be different...

As stated, keep gain well below +15dB (in rockbox) and you'll be fine.

This is a table somebody once made, don't know how accurate it is:

orig fw setting     rockbox
                          adc     decrementer
line in ~             -6    +   0  ()
ext mic 0            18   +   0
ext mic 5 ~         24   +  0
ext mic 20 ~       24   +  24

[petur]

Mmmm: I think it's worth rebuilding your REP as jhMikeS committed some important recording changes which should guarantee more stability (ie no missing samples).

[Mmmm]

I'm just waiting until JDGordon moves the recording settings menu really! or I'll just have to go and do it all again in a week or so!

[Rincewind]

just a note for Mmmm: it is very likely that I make a new record button patch at the end of next week.

[Mmmm]

Well, after saying all that I went ahead and did it anyway seeing as I had a bit of spare time. So post#1 has the new patch and my new build. (So, Rincewind, when you're updating, you may want a look in here for the new settings and menu code for your patch).  

 (I haven't updated the extra patches that are usually in my build so for now there is no left to wps and click insert and whatever else is usually in there. So my build is purely REP at the moment).

[Peter200lx]

I was just wondering how much longer until this is updated? Has the new menu progressed far enough yet for a new version of the REP?

[Mmmm]

I was just wondering how much longer until this is updated? Has the new menu progressed far enough yet for a new version of the REP?

??What do you mean?? look at the post above yours, I updated it on 17th Feb!

(Whenever I do an update I modify post#1 so that the modified date of post#1 should be the version date)

(and I've just updated it again today..... )

[x1jmp]

There's missing an adjustment in apps/gui/statusbar.c on which breaks compiling on RTC targets

Code: [Select]

---  apps/gui/statusbar.c      2007-02-27 14:27:24.412249030 +0100
+++ apps/gui/statusbar.c        2007-02-27 14:23:54.851257558 +0100
@@ -155,7 +155,7 @@
 static void gui_statusbar_timer(struct screen * display, int dy, int hr, int mn, int sc);
 #endif
 #ifdef CONFIG_RTC
-static void gui_statusbar_time(struct screen * display, int hour, int minute);
+static void gui_statusbar_time(struct screen * display, int hour, int minute, bool timer_display);
 #endif
 #endif