disc mode / file system problem?

Knightshift · Post by **Knightshift** » Thu Jul 07, 2011 11:13 am

Hi, I had a strange experience regarding long filenames and special charactes 'ä' 'ö' 'ü'. I wanted to import a wave file with a long filename (about 40 characters including special characters) into a sequence. At the end of the importing process, the kronos froze at 100%. the touchscreen didnt react although I could play on the keyboard. The only thing I could do was a restart. After renaming the file the import worked without problems.

The second problem I had was in disc mode. I created a folder with 17 characters in itd name, added anothet folder with 7 characters and there wanted to 'save all' to a file named '2011_07_06'. I received an error 'unable to save' or something (cant remember exactly) and only the .pcg was saved.
When trying to save all in the root folder, everything worked fine.

Are there any known issues regarding long filenames or special characters?
Thx

Mystic38 · Post by **Mystic38** » Thu Jul 07, 2011 12:17 pm

Given your experience I would say "probably"...

One simple way to check on filenames would be to see the number and type of characters that the K allows when saving a recorded sample.

Knightshift · Post by **Knightshift** » Sat Jul 09, 2011 11:08 am

Here another problem when trying to "save all" overwriting existing files: the .pcg and .sng file will be overwritten, after then the message "file already exists" appears (pressing "ok") then the .kge file is overwritten. However, the .kgs and the subfolder with the sample data is NOT overwritten and new sample data is NOT saved.

Because of this I lost some hours of creating samples since I thought "save all" would really save everything even in the case already existing data is overwritten.

Anybody else experiencing this or is it a malfunction of my machine? Any other information regarding my first issue?

sani · Post by **sani** » Sat Jul 09, 2011 11:22 am

You have to be careful with the cumbersome file handling when it comes to overwriting samples. It's obvious that Korg didn't changed it since the Triton Classic. You cannot overwrite a sampling folder. Whenever you add new samples/multisamples to your list and create new ksc scripts (for loading them into the proper places) you have first to delete the old one and then you can create/save the new extended sample folder. This is of course valid only if you choose to save it under the same name.

EvilDragon · Post by **EvilDragon** » Sat Jul 09, 2011 12:10 pm

I would enforce the idea of using simple filenaming on any hardware workstation, just as a common sense. Windows and OSX spoiled us all.

So, keep it below 10 characters and use only the regular ASCII characters, no checks, no dashes, no acutes, no dots, circles or umlauts. Keep it simple and stupid.

Megakazbek · Post by **Megakazbek** » Sat Jul 09, 2011 4:46 pm

EvilDragon, your idea does not make any sense at all to me

yawnthepost · Post by **yawnthepost** » Thu Aug 02, 2012 3:47 pm

I'm using a Korg Kronos 88 with what I think is one of the earliest operating systems: 1.0.7 - I think there is a significant problem with long file names - I've had audio files disappear, files not save or load, and it's taken me this long to realise what it could be - if it wasn't for coming across your post, knightshift, I wouldn't have realised this was a possibility - and nor did the Korg technical helpdesk (who are really helpful otherwise). Thanks!

danatkorg · Post by **danatkorg** » Thu Aug 02, 2012 3:58 pm

My guess is that the file paths exceeded 76 characters.

The Operation Guide and on-board Help system include a section titled "Error and confirmation messages." This can be pretty helpful to find out both the potential causes and remedies for any message you see on the KRONOS. "File/path not found" and "Unable to save file" errors may be caused by exceeding the path length, and solved by reducing the total number of characters in the path:

"Rename the file and/or directories so that the file path fits within 76 characters. This includes the file name and the names of all parent directories up to the root level of the disk."

Hope this helps,

Dan

yawnthepost · Post by **yawnthepost** » Thu Aug 02, 2012 4:04 pm

The longest filename I used had 53 characters - the shortest I had a problem with had 19 - but all three had more than two spaces between words - I am certain that this was causing some sort of file error. (including audio files disappearing and save failures). Many thanks for your response. Andrew.

danatkorg · Post by **danatkorg** » Thu Aug 02, 2012 4:11 pm

yawnthepost wrote:The longest filename I used had 53 characters - the shortest I had a problem with had 19 - but all three had more than two spaces between words - I am certain that this was causing some sort of file error. (including audio files disappearing and save failures). Many thanks for your response. Andrew.

Please note that the length limitation is for the entire file path, which includes the names of all enclosing directories as well as the file name itself:

"Rename the file and/or directories so that the file path fits within 76 characters. This includes the file name and the names of all parent directories up to the root level of the disk."

- Dan

yawnthepost · Post by **yawnthepost** » Thu Aug 02, 2012 4:14 pm

Ah! Sorry, I missed that. Makes sense completely. Thanks for your help.

mcv · Post by **mcv** » Sun Feb 09, 2014 5:22 pm

danatkorg wrote:Please note that the length limitation is for the entire file path, which includes the names of all enclosing directories as well as the file name itself:

What's the reason for this limitation? Can it be fixed in future versions? Linux certainly doesn't have a limit of 76 characters per path, and ext3 actually allows 255 characters per _file name_.

Saxifraga · Post by **Saxifraga** » Sun Feb 09, 2014 6:12 pm

EvilDragon wrote:Windows and OSX spoiled

That's a wicked thing to say! lol

Saxifraga · Post by **Saxifraga** » Sun Feb 09, 2014 10:50 pm

mcv wrote:
danatkorg wrote:Please note that the length limitation is for the entire file path, which includes the names of all enclosing directories as well as the file name itself:
What's the reason for this limitation? Can it be fixed in future versions? Linux certainly doesn't have a limit of 76 characters per path, and ext3 actually allows 255 characters per _file name_.

I was angry about that a year ago. Sadly Roland is not better in that department, but at least they have no functions that ignore their own limitations without warning and leave the user with some errors in the dark.
(Korgs motto: If you can not do it right, write an error message and document it! This they do since 1995: Not get it right.)
All major Synth producer are years behind the IT standard.
Korg, Roland and Yamaha etc. may be good at programing DSPs but theri UI(Korg) and OS(Korg/Roland/Yamaha) is s**t.

@Dan: Isn´t it tiresome to have people always fall over the same OS bugs, which you obviously have to sell as well documented features?

I bet every Korg user has fallen about this one and lost some of his work.
It´s time to catch up and use that linux features.

danatkorg · Post by **danatkorg** » Mon Feb 10, 2014 9:16 am

Saxifraga wrote:@Dan: Isn´t it tiresome to have people always fall over the same OS bugs, which you obviously have to sell as well documented features?

Any reasonable observer will see that I'm not trying to "sell this" as a feature. Instead, I responded to a user who was having a difficulty, explained what was happening, and told them how to solve the problem - along with pointing them to a resource that might help them to solve future problems. Pretty much the sort of thing that nice people do on forums: helping someone out.

In contrast, you are just crashing the thread with your usual tiresome attempts at insults. Since you no longer own the product, there is only one reason for you to continue to do this. Like "tiresome" it also starts with a "t."