Support and General Use > Recording

Recording Enhancements Pack

<< < (9/189) > >>

renho3k:
rogain = hair rejuvenating forumula *wink*

i tried to patch your recordingenhancementspack.patch with daily build 02/07/06 and i got a HUNK #2 failed error. this is my first time patching. i put the patch file in the root of the source. did i do something wrong or is the patch not compatible w/build 20060207?

$ patch --binary -p0 < recordingenhancementspack.patch

patching file apps/menu.c
patching file apps/menu.h
patching file apps/settings.c
Hunk #4 succeeded at 516 with fuzz 2 (offset -22 lines).
patching file apps/settings.h
Hunk #1 succeeded at 216 (offset -1 lines).
Hunk #2 succeeded at 233 (offset -1 lines).
patching file apps/sound_menu.c
Hunk #1 succeeded at 51 (offset -1 lines).
Hunk #2 succeeded at 241 (offset -1 lines).
Hunk #3 succeeded at 255 (offset -1 lines).
Hunk #4 succeeded at 338 (offset -1 lines).
Hunk #5 succeeded at 782 (offset -2 lines).
Hunk #6 succeeded at 794 (offset -2 lines).
Hunk #7 succeeded at 804 (offset -2 lines).
patching file apps/gui/gwps-common.c
patching file apps/lang/english.lang
Hunk #2 FAILED at 3701.
1 out of 2 hunks FAILED -- saving rejects to file apps/lang/english.lang.rej
patching file apps/recorder/peakmeter.c
patching file apps/recorder/peakmeter.h
patching file apps/recorder/radio.c
patching file apps/recorder/recording.c
patching file firmware/sound.c
patching file firmware/drivers/uda1380.c
patching file firmware/export/audio.h
patching file firmware/export/sound.h

Mmmm:
Don't worry the build you are trying to patch is too old! it's nothing you have done! You should use the bleeding edge build.
or you could have a look in the patch and at english. lang, you should be able to input the changes manually, english.lang is fairly easy! :-)

renho3k:
wow. i posted at 04:51:48pm and got a reply by 4:58:30pm. now that's service with a smile!

k, now i got the bleeding edge built and successfully patched it (just the enhancement pack, not the font changing one). everything more or less fits in the remote now as compared to thomas's patch that i was using before. the clip light also works fine. however, question about functionality of the clip light. once it clips, it turns on (duh) and stays on. what determines when the clip light turns off? is it just timed?

mlind:
When clip indicator in peak meter goes off the light goes off.
You adjust this time in the settings for peak meter.

whatboutbob:

--- Quote from: mlind on February 07, 2006, 07:01:57 PM ---When clip indicator in peak meter goes off the light goes off.
You adjust this time in the settings for peak meter.

--- End quote ---

When stealthing I set it to like 5 mins so that i just have a peek at the remote @ the end of particularly loud songs, and if the light ain't on, I'm laughing.

Something worth mentioning on the clipping indicator though...its not an exact tool...hence neither is the cliplight.  It is possible to clip without triggering the indicator.  The issues are at least twofold...but I'm running off memory here, which is unreliable at best.  I believe clipping needs to exist over two samples before its triggered (eg one loud clap won't trigger it).  Apparently it can also get false positives, and just not fire other times.  In other words, don't put complete faith in it.  Is that fair Mmmm?

Navigation

[0] Message Index

[#] Next page

[*] Previous page