I use Octachain to create sliced samples, importing chains of 64 drum hits as separate slices.
Usually it works fine but sometimes the sample sounds distorted/unrecognisable (which I’m guessing is a problem with the sample rate) or has a little glitch/click in it (I’m not sure what’s causing this).
I know that the Octa needs 16bit 44.1khz but can anyone let me know:
- How do you check the bit/sample rate on Windows? I’m never sure where to look and can’t find how to show it in Explorer or in media players. Something that was free and can show this in a list would be great.
- Any nice tools for bulk converting samples with the wrong rates? Preferably free again (I know, I spent all my cash on Elektron gear…)
- Any idea what is causing the odd ‘click’ glitch in an otherwise nice sounding sample/slice. Seems fine otherwise but it affects every one in a sample ‘set’ I take it from.
- Any tips for using Octachain or another tool to create samples? Do you use the normalise function. Why does it have 48k/24bit options if the Octa can’t take them? Sorry for all the questions!
I would guess when splicing together individual hits that some of the start/end of a few of the samples zero crossing doesn’t line up, one has + polarity the other -.
I haven’t experienced any noticable strangeness from using a 48k sample except the " : |" face
Think on the properties tab on Win will tell you the sample rate but not bit depth.
I use Audacity to convert and eyeball for strange assymetries in waveforms that may show up in OT. The only other clicks would be when sample loops. Don’t think Windows media player would be a good final place to audition stuff.
I tend not to use normalize and go by ear, since you can manually zoom in and amp sections of the waveform, some may peak by just having sub or low end energy.
Thanks for the reply. I don’t think that’s the cause of the click, it happens halfway through the sample and the start/end points seem fine, sounds like it might be overloading. I’ll see if I can upload an example when I get back to my Octatrack.
Can you tell the bit depth in in Audacity? Shame to have to load up one though as I usually use a ton. Maybe I’ll have to admit it’s a bit more of a painstaking process or be more selective with my slices…
Yes I would stick with 44k, the conversion in OT may be the issue. Audacity you can check it or convert as needed.
I’ve checked the waveforms and zoomed in (never really use the audio editor on the Octa, always do that stuff on PC) and it looks like it’s overloading. Waveform bigger than the top of the screen and the couple that sound ok are quieter and look fine on the Octa editing screen.
Ok I’ll check again and see, the waveforms look fine on PC so not sure how they got overloaded. Maybe the normalise setting on Octachain? I’ll do some experimenting.
ps. Turns out Resonic audio player is really handy for displaying sample/bit rates.
Sounds like those samples are clipping. I don‘t use Octachainer, so can‘t help you with the settings there.
Ah fair enough. With the name I just assumed it only worked on the Octatrack.
With 1.3 version 1 or 2 modes were added for AR/DT…
And concerning 24bit, OT also use it!
1 Like
Turns out it was the ‘Normalise slices’ setting in Octachainer that did it. Disabled normalising and all was fine 
1 Like