MPC 1k, OS2XL v. 1.11 DIRECTORY ERROR, the RETURN OF!!!!!!!!

I just tried to get the same error you guys did using 1.11 and saving the entire memory. It didn't give me an error. All I did was load up 3 drum samples, made a program, a sequence, and saved the entire memory. I could load the folder and the project file just fine.

Just FYI. Hopefully JJ can ensure that everyone's is working.

try it with some files with spaces in the names

yep i do, but im not riding with XL, dont think ill even buy it.

theres really no reason not to buy it. that x-fade loop is really some cool shiit

Hope this is only a one off, have too many akai mares about directory errors, I always save entire memory to new folder, if working on the same project I will save to that folder with a diff project name , just the date mainly and overwrite all the samples again. Using OS2 1.22 the only time I've had the directory errors have been with imprpper file names and 24 bit samples

no such error here. this likely stems from not having reformated after installing jjos over the original akai os - lingering effects from the original bug.

Also, are your sound files 16 bit or 32 bit? MPC won't read 32 bit files.

when u connect it to a mac (leopard) it leaves behind a few files for the macOS filesystem, 2 hidden folders
Trashes & Spolight, on FAt formatted storage,

i know fuk all about it, and i could be off the mark but it's worth investigating, if this is isolated to mac's and usb connect with an mpc1000,.

like someone said its prolly the sample names with spaces in them cause when i changed that it didnt do it anymore.

btw nym by lingering effects... you must mean some common code... thats the only thing that could be possible as far as 'lingering effects'

nah i mean having had an akai os/mid-2006 "new" jj os touch your hd could have lingering effects on the drive itself

ie, if you saved even once using an os with the saving bug, it could cause problems even for an os in which the saving bug has been fixed - even if that is way on down the line. this is why there's this page:

http://www7a.biglobe.ne.jp/~mpc1000/important.htm

furthermore:

Notes: When it writes in by returning os to the version not more than Version3.05,
please format by jj os Version3.08 or jj os1 Version4.xx again.

that means that if you ever went back to the akai os EVER and saved something, you need to backup and reformat.

oh you mean if you dont reformat. well i reformatted using xl 1.11 and it still happened until i took the spaces out of the file names like someone suggested.

btw im curious what you did with your data wheel... can you comment on my thread in the mpc 1000 forum and post a pic maybe? thanks

rich_biatch wrote:like someone said its prolly the sample names with spaces in them cause when i changed that it didnt do it anymore.

btw nym by lingering effects... you must mean some common code... thats the only thing that could be possible as far as 'lingering effects'

The spaces in the names thing only takes affect, if the sample names are mor then 11 characters long. As long as you got underscore_in_it_the_file_name_can_be_very_very_long_like_255_characters_i_think. I did some investigation and some testing on this. Read the FAQ for more info on this!

jackymurda wrote:bumbleclot!

we got 4 pages onna friggin RTFM question like "where's the swing duh?" and nobody really cares about this ?? does anybody else here use the 'save entire memory' or just me and like 4 other people?

WORD!!!!!!! I just went back to regular OS 2, loaded the project, I created in XL and just works fine... XL can get my XL Bozack, until this thing runs rock solid.

I rported both (the Folder Error and the Seq/All loading problem to JJ), so hopefully we see a new build soon...

PEACE

PS: had to delete some smilies "Your message contains too many smilies. The maximum number of smilies allowed is 3."

i found a workaround: you gotta load up each program individually after loading the project file- only the first program loads with project...dunno , guessi'll try reformatting..

This is a OSXL only exception. It won't disappear by re-formatting, because I had reformatted my disk right before that! So don't waste your time!