Posts: 64
Threads: 10
Joined: Jul 2018
Reputation:
0
Hi,
Just tried converting a folder of samples from 32 bit stereo to 16 bit mono and when I put them in the Nerdseq they sound terrible, low quality and much longer.
Don’t know what I’m doing wrong? They’re wavs, I used switch converter for Mac.
Help?
Posts: 3.644
Threads: 123
Joined: Jul 2017
Reputation:
215
I suggest you use another conversion tool. Also 16bit mono is not too common anyways. Try to go with normal 16bit, Stereo 44.1khz waves or make them 8bit mono or convert them to 8 bit unsigned raw directly. And the chances are there that your tool adds additional information in the wave file itself which the nerdseq probably can't handle, then it maybe doesn't matter how your set it. Then you definitely got to switch to another tool.
PLEASE use the search function if something have been asked or discussed before.
Every (unnessesary) forum support means less time to develop! But of course, i am here to help!
Posts: 64
Threads: 10
Joined: Jul 2018
Reputation:
0
I’ve tried 8 bit and nothing works.
Same issues.
Anyone???
Posts: 20
Threads: 7
Joined: Dec 2019
Reputation:
0
Hello all,
I too started to experiment with samples today. I had the same issue but I manged it to work.
I'm using Audacity latest version. I think it is a problem with header as Thomas already mentioned in some other topic.
Make sure you select
format: Other uncopressed files
header: Wav(Microsoft)
encoding: Signed 16-bit PCM
For me it's working very well.
Posts: 19
Threads: 4
Joined: Nov 2019
Reputation:
1
Yeah I had to convert all my samples to 8 bit mono unsigned raw before everything worked as expected. I had signed raw for a while, and it still distorts like crazy.
"unsigned raw" sounds cooler too
Posts: 3.644
Threads: 123
Joined: Jul 2017
Reputation:
215
I can confirm that all sample types mentioned in the manual: wave 8/16 bit mono or stereo and 8bit raw unsigned work...
But some softwares use wavefiles with loads of metadata and extra information which the NerdSEQ can’t simply decode. Mostly because it has an easy wave file decoder and assumes the standard simple implementation that you can find everywhere but not specials that are added.
Implementing a full stack would be probably as big as the NerdSEQ code itself, if not bigger.
They are many tools out there to either convert or write your wavefiles in all kinds (except 24/32 bit) which work perfectly with the NerdSEQ. Also some batch conversion tools are available and have been posted here.
PLEASE use the search function if something have been asked or discussed before.
Every (unnessesary) forum support means less time to develop! But of course, i am here to help!