OCTATRACK: ERROR Invalid Filetype

Elektron Gear Octatrack
#1

Hello,

I’m new to Octatrack but have been dedicating it lots of time to learn how to use it properly. I have and issue when saving samples and loading them to tracks. So here’s my case: I sample a track from midi track 1 into track 2 with R2 assign to it. I hit T2+Bank and I see the recording. I can hear and see it’s perfect. I go to File, Save and Assign, Assign to Flex, and it say Assigned to Flex X, as usual. But then when I want to load the sample into one of the tracks, it says ERROR: INVALID FILETYPE R2.trackname.

Why?

I’ve done this several times before (sampling both midi and my plugged guitar) and it was working well. Now it’s happening this way and I can’t find an answer.

I would be so thankful for any help. This is making me crazy XD

Thanks!

#2

Having same issue but with a common file that I use to play a lot in static machine. It shows the massage: ERROR Couldn’t load STATIC[90] with ‘…/AUDIO/filename.wav’ (‘INVALID FILETYPE’)

#4

Corrupted file maybe. Do you have another copy of that file?

#5

I’ve just reload the sample in to the slot and start to work again… hope it keeps playing

1 Like
#6

I was having issues like this a couple years ago, not much with audio but with bank files being corrupted and also even more strangely sometimes I would save a project and reopen it and it wouldn’t give me an error but some of the parameters would be changed in really weird ways (record parameters for track 1 moving to track 5 was a common one, as was the record source being changed from whatever it had been before saving and reloading to SRC3 - Track 7, once or twice track trigs would move from one pattern to another and IIRC I had one instance where a track that had been center panned ended up hard panned to one side; once this happened to a project it would persist - it was an actual problem with the files on the card).

It started after I had to make a two hour drive with the OT in the drunk of a car during the worst cold snap in a decade, and what ended up fixing it was doing a low level reformat of the CF card on a computer with a dedicated CF formatting program. Reformatting on the OT didn’t work and reformatting with the OSes own reformat function didn’t work. I honestly can’ remember what program I used, I tried a few and only one of them would complete the format (which took about 20 minutes) without locking up near the end. Been using the same card since then and it never happened again after the reformat, as far as I can figure the project files were being corrupted but the OT was still able to read them, it was just reading incorrect values for some things.

This is the post where I described what I did in more detail, maybe it will help you.

EDIT: also, ever since that drive encoder A has been jsut a bit jittery if I run it slow (but responds like normal when I turn it fast) - not bad enough to replace it but enough that I notice it compared to how it was before and how all the other encoders still are. The moral here is don’t let your OT get too cold!

1 Like