Parse error, brand new octatrack

I’ll update for sure.

2 Likes

Any update? I just got this error today on my Mkii :frowning:

1 Like

What is your card ?
Do you have it / use it since a long time ?

Think it’s the original one. Yeah I’ve had it for a year and bought the OT used. Its been fine.

I deleted the project that wouldn’t load. Loaded my template file. Saved as new. Renamed it and powered off. I powered on and everything seems to be working. The new project loaded fine.

Maybe the old name - july22222 messed it up? I had not loaded any samples yet or anything.

Also meant to ask if there is a recommended cf card replacement.

Doesn’t seem to be with strange characters…

I had this PARSE ERROR with my original card (MKI, Kingston 16GB), but my card was almost full, used since maybe 5 years, with a lot of projects.

Then I had a card crash, almost all projects deleted. I think it’s because I turned off OT just after power on, during card files loading. Backup important files ! (I didn’t).

Seemed to work correctly after formating. But now I’ll use it as backup card.

IIRC some writing errors can concern only certain banks, so you can recover some banks copying them in a new project, or with a Save As New procedure (if you can).

Some users, including me, chose a Sandisk Extreme (gold) 64 GB, or 32 GB.

Max is 64 GB.

Great thanks! Maybe I should get one to be safe. Is this the card you are talking about?

Yep.

1 Like

Here’s what was sent to me via email: What most likely has happened is that some of the files on your CF card have become corrupted, and are causing the Project to load erroneously. Could you try if saving the project as new in the Octatrack makes any difference?

Are any other projects affected or does it only happen in that specific project? Could you also send a picture of the back of the CF card that was shipped with your Octatrack? Have you been moving the project files around to and from a computer? Or have you edited them outside of the Octatrack?

Parse Errors are not indicative of a hardware issue. It could potentially be a problem with the CF card though.

I haven’t had any issues since then, but I plan on switching to the better cf card linked above at some point.

2 Likes

Thats awesome. Thanks. Yeah I deleted the corrupt project and my template project loaded fine. Made a new one and I’ll see if it loads up tonight.

I did put some samples on my ot before this happened via usb so maybe that caused it. Im buying a new card to be safe.

If it happens again, try Save As New. IIRC it solved this problem for me, and it seems recommended by Elektron :

1 Like

I had a PARSE ERROR today !
A bank was blinking red (MKI).

SAVE TO NEW solved it.

1 Like

That’s a “not so friendly” reminder about making a backup again, isn’t it? :wink:

2 Likes

Yes, but I’ve nothing essential to backup anyway…

I had a parse error yesterday, after the arrangement refused to mute a thru track.

Saved the project to new, but the new project also seems corrupted.

I read that you have to do a empty reset if this is the case, but what is the correct order in this proces?

What is corrupted ? A bank ?

I don’t think so. PARSE ERROR is on the card.

I got this message with the old project and the new project that I saved to new. (not at home, nicked a picture from the internet)

parse

When I press NO the project seems to have been loaded and works fine. But when I save it to a new project the message comes up again when reloading.

Check if there is a faulty bank (IIRC after Bank button press you can see a blinking red bank on OT MKI, which is not the selected bank).
You can try to save and reload the bank, or delete it if it doesn’t work.

@Hooger sorry I wrote something wrong with YES. So check above, I edited.

If you delete a bank, there is a message error, but a new bank is created after loading

I have bought a new card and stopped using the elektron supplied card. Since replacing I haven’t had this issue.

1 Like