1

Hi,

i´m new to my octatrack.

What does the message mean: ERROR: UNSUPPORTED ENCODING

I´ve created a new empty project, cleared the ram, renamed the samples into 8+3 format (e.g. “dumdum1.wav”), renamed the folders into 8+3 format (e.g. “drums1”) etc., but the Octa will not load the samples. Not into flex- and not into static-slots.

Is it a card or a sample-format problem or something like this?

My cf-card is a 16gb kingston ultimate 266+

Is there a difference between formating the card in the octatrack (card tools -> format card) or in the pc (windows explorer -> format fat32) ?

Any suggestions?

Thanks a lot and greetings from Germany :slight_smile:

2

A wild guess: it’s got something to do with the endianness of your audio files? If they are AIFF files, try saving them into WAV?

http://wiki.audacityteam.org/wiki/WAV

3

Check out page 29 in the manual. Use the file browser to look for the :slight_smile: for your sample.

You might have a file with a sample rate that is too high, or you have the wrong file format. It must be a .wav file, I believe.

4

… problem not solved, but thanks :slight_smile:

5

It’s not like dos, you don’t need to rename 8.3, plus make sure the files are actually wav and at the correct encoding for OT and ensure they are not actually named sample.wav.wav (some OS will hide the extension) download a random wav from music radar and try just that on a card formatted in the machine

6

A lot of samples are loaded without any problems, but some samples will not (ERROR: UNSUPPORTED ENCODING). Some samples are furthermore loaded with pitch-problems (“mickey mouse effect”).

Hmmmm.

I found out, that all samples with problems are “old samples” from sample-cds of the 90´s. Maybe the old *wav-format is the problem. Maybe OT can´t load the old encoded *.wav-files?

Hmmmm.

That seems to be the problem. With “actual encoded” samples there are no problems.

Thanks :slight_smile:

7

You could load them into a DAW like cubase or logic and re-export them as wavs.
Maybe search google for old wav file compatibility. There might be some free utility to bring them up to scratch.

8

The only time I had a similar issue was when I was dragging samples from Ableton’s library into the OT. I didn’t realise that these samples had additional encoding to them - or something along those lines - which meant I couldnt use them directly without faffing around and recording into a fresh clip (or direct to the OT).

So, like others, I’m guessing there is a sample rate issue here or something along those lines. Where did you source your samples?

9

I’m guessing the pitch problem is a sample rate problem. Check your files’ sample rates in Audacity or something.
No problem :joy:

10

Try batch audio converter:

WIN

OSX
https://public.msli.com/lcs/audiomove/

I use AudioMove on mac and it’s awesome

[EDIT]
there’s actually AudioMove for Windows as well on that page

Hope it helps

11

You are all right:

The PITCH-PROBLEM (“mickey mouse effect”) is a sample rate problem (44,1 khz/48 khz, 16 bit/24/96 bit etc.): No problems with standard 44,1 khz/16bit and 44,1 khz/24bit samples, but pitch-problems with 48 khz samples.

The UNSUPPORTED ENCODING ERROR is a problem with old *wav-samples from old sample-cds. The old samples will not loaded into OT directly. It seems to be an encoding-format problem. I haven´t tried to convert the old samles yet.

Thanks !

1 Like
12

I don’t think that this was solved before…

So maybe this helps with future ones struggling with this: ffmpeg command line util can fix these broken wavs. ffmpeg -i bad.wav good.wav

Btw, my broken wav came out of Adobe Audition, I made it myself. Otherwise Audition is perfectly capable of producing Octatrack-compliant wav files, so I am not sure what went wrong in this case.

13

Sorry, but your simple example …

… won’t work when the “bad.wav” isn’t already in an encoding the OT supports. It doesn’t auto-magically select the narrow range of formats the OT supports (16 or 24 bit/44.1 kHz wav/aiff files, either in mono or stereo).

When you feed ffmpeg with, for example a 48kHz wav file the output wav file will also be 48kHz.

Just a side note about AIFF: aiff files can be copy-protected (like most of the files coming with Ableton).

14

yes sure, this is for cases when there are no trivial problems with wav file, like described above

15

I just encountered a whole bunch of Unsupported Format Encoding errors with WAV files.

The thing is i can’t load/read them on a static machine but i’m able to load/read them on a Flex machine.

Weird isn’t it?

1 Like