Put All Audio Questions Here

You repeat yourself...

The Gameshark does nothing more than to modify memory location, either manipulating game code or game data (or both, as we know that a lot of N64 catridges do run-time code transformation).

If you have read the link I gave you, you now know that the N64 has no standard way of playing back SFX and music data, that's the main reason why it's so hard to rip music.

Should be clear by now why no universal memory hack exists for disable SFX playback. You would have to figure out (by disassembling and tracing) for each game which part of the gamecode generates SFX and passes it to the DSP of the N64. Then you patch that part of the code and make a diff, resulting in your gameshark code.
That's not easier than creating a USF.

Originally Posted by LiquidAcid

You repeat yourself...

The Gameshark does nothing more than to modify memory location, either manipulating game code or game data (or both, as we know that a lot of N64 catridges do run-time code transformation).

If you have read the link I gave you, you now know that the N64 has no standard way of playing back SFX and music data, that's the main reason why it's so hard to rip music.

Should be clear by now why no universal memory hack exists for disable SFX playback. You would have to figure out (by disassembling and tracing) for each game which part of the gamecode generates SFX and passes it to the DSP of the N64. Then you patch that part of the code and make a diff, resulting in your gameshark code.
That's not easier than creating a USF.

Oh...I see the connection now. Thanks. Yeah, I did read the link you posted, but I didn't see how that answered my question until you explained it just now. (I repeated myself because I wasn't sure if your post was directed at me to begin with. )

Recording net radio: HOW TO?

I've begun working on my first .GBS conversion, and I have a few questions.

First off, I saw that this was covered briefly earlier in this thread, but when applying replaygain info to tracks, is there any way to prevent native clipping from a .GBS file? (I guess that would be the best way to describe it.) I did a replaygain scan with Foobar2000 v0.9.4.2 and noticed all tracks are above the ideal 1.00 dB track gain value, not to mention one of the tracks being at 11.15 dB... So, I guess my question is, since I can't apply replaygain to the .GBS file itself (to my knowledge) after converting the tracks to .FLAC (.WAV can't store replaygain info, AFAIK), can I still apply replaygain? Or, would it not make a difference at all?

Second, are there are any recommended freeware audio editing programs you would suggest?

Finally, I've never really done any audio editing before, so any suggested guides/instructions/tips for the audio editing process would be appreciated. Thanks.

Edit: I'm using Audacity to do some experimental editing. I've ripped/encoded a sample track, if anyone wants to critique it and give me any suggestions. Thanks, again.

Kaeru.mp3

What is the best program to edit audio tags?

MEGAUPLOAD - The leading online storage and file delivery service

This track contains artifacts at 1:03, 3:13 and a ripper at 4:35, more at 6:32 and 6:35, as well as skipping at 5:29. But are they rip/handling related or is it a problem with the mastering? The disc's part of a 7CD set that arrived last week, and the others are totally flawless. There's only the barest scuffing on the problem disc.

I've reripped it twice, presuming hardware hiccups, but every time EAC error correction didn't detect anything amiss.

If it's a mastering issue, is there any possiblity for correction? If it's (somehow) physical damage, what else is there to do?

Sometimes using burst-mode in EAC helps with badly scratched discs. If there're no scratches then it's probalby a mastering issue.

You could edit the wave file and cut the erroneous frames out.

Or enable C2 with secure mode (usually most guides advice you to disable it), if the drive logic correctly implements C2 error reporting and there are any (which can't be detected through C1), then EAC should provide a more precise report of possible error positions.

@sup!: I would advice against cutting out frames, which results in audible dropouts. Filtering the frames plus surrounding frames should be better.

It isn't badly scratched though, but regardless I'll try burst then fiddle with C2 reporting.