Deprecated: mysql_connect(): The mysql extension is deprecated and will be removed in the future: use mysqli or PDO instead in /storage/content/49/145849/famitracker.com/public_html/forum/classes/dbHandler.php on line 29
i've recorded my own kick and snare samples that i've been able to get down to 4KB .WAV files (bounced in Pro Tools at an 8-Bit Resolution and 8kHz Sample Rate). when i click Import at the "DPCM Samples" window, i select one of the files and click "Preview", but it only makes a clicking sound. i've tried adjusting the Quality, etc. but it still just ends up being a click or a high pitched frequency. i feel like there's a problem here and it's not just the result of the editor trying to compress the file to 1KB. is there a possible issue with how i've prepared the files? (although the FamiTracker help file says sample rate, etc. doesn't matter.) i've attached the snare sample in case anyone's willing to see if they can get it to work.
thanks. i've read the FamiTracker help file, the wiki, every thread with "DPCM" in the title, and i've searched Google and YouTube, so any additional input would be greatly appreciated.
I don't know what is the exact thing that failed, but I'm certain that FamiTracker crashes while attempting to import this WAV file. However, I was able to convert it from Audacity into a new WAV file and it seems to work. It also sounds almost the same. I hope this helps you.
EDIT: Audacity said something like this:
[quote=Audacity]Name: _snare
8000 Hz
32-bit float[/quote]
I changed the 32-bit float into 16-bit PCM and exported it. It now works fine in FamiTracker, but I can't really tell if this was the exact problem.
yeah, there must be some setting i'm not accounting for in Pro Tools when i'm creating the .WAV files. i just exported a new copy of the file using Quicktime and everything is working fine when i import it into FamiTracker. if i can't figure out what the deal is with Pro Tools i'll look into using Audacity for making these samples. thanks!
i have one more (hopefully quick) question. i've recreated the WAV files at 8kHz and a 16-bit rate. when importing to FamiTracker i can now hear the sample (as opposed to the original click i was getting) but it is overpowered by white noise. am i missing something or is this the normal downgrade you get when converting the files (in which case i'll just have to figure out how to make better samples)? the same thing happens when i import the "snare2.wav" file that Mr_Master created.
i realized i had re-converted the same files between so many different formats that the integrity was lost. i started again with the original 44.1kHz 24-bit samples and the background noise in the final DMC files is at a minimum.
thanks again for all of your input...10 hours and a few colorful cursing sessions later i have some decent samples.
Some people seem to think converting samples to 33144Hz to approximately match the maximum playback rate of the hardware will improve the quality of samples a bit, but I've never noticed any significant difference, personally. I feel it's worth mentioning if you want to try it, though.
When using the internal FT converter, I find the samples turn out the best from +7 db to +9 db.
Additionally, if you highlight the imported sample in question and click the 'Edit' button, you can remove some of the excess noise at the end (see attachment).
There are no straight lines or smooth curves in DPCM, only up (1), or down (0), so if your sample reaches a point where it's practically a straight line, the poor delta wave has no choice but to bounce back-and-forth in an attempt to walk the straight and narrow path it's given.
_______________________
The only things certain in life are death and uncertainty.
I'd put the .wav into 44khz/16-bit as the DPCM's highest sample rate is 33khz - by making it 8khz you might lose some of the sound even on DPCM (minimally though).
[quote=Necrophageon]Some people seem to think converting samples to 33144Hz to approximately match the maximum playback rate of the hardware will improve the quality of samples a bit, but I've never noticed any significant difference, personally.[/quote]
And effectively, you should not, because now the resampling process is very accurate--aliases are much more quieter than the signal itself (depending on the frequency, 40dB to 60dB attenuation).