Please fix the Saving Issues

please someone fix the saving bugs.

please

please

please


Man, I know theres been threads on all this shit, but everyday I try something differant and I think Im doing the best possible way and to my surprise, i gotta redo my shit.

So Im official just straight up saying please!


please!

I remember having problems until i started saving everything to a new folder. Honestly, I haven't had any other problems since.

episode wrote:I remember having problems until i started saving everything to a new folder. Honestly, I haven't had any other problems since.

Just so I understand this correctly... You create a new folder for every sequence or every project? Can you please elaborate because I'm sitting thinking how crazy it would be to have to have a new folder for every sequence one saves ie 200 sequences grouped at 123bpm saved in one folder called 123bpm vs one folder called sequences with 200 folders each titled the name of the saving sequence.

Why wouldn't you just name your songs and save them in individual folders by saving entire memory. Works fine for me. I have never had an issue since.

Memphlow wrote:Why wouldn't you just name your songs and save them in individual folders by saving entire memory. Works fine for me. I have never had an issue since.

when I do that, everything saves, but when you go to reload, it doesnt load the samples, it will load the seq and the pgm, but no samples.

ive tried saving to new folder, saving all pgms, saving entire memory and the same thing happens no matter how I do it.

I dont believe its my memory card because before I went to 1.22 this didnt happen.

cyrus wrote:

Memphlow wrote:Why wouldn't you just name your songs and save them in individual folders by saving entire memory. Works fine for me. I have never had an issue since.

when I do that, everything saves, but when you go to reload, it doesnt load the samples, it will load the seq and the pgm, but no samples.

ive tried saving to new folder, saving all pgms, saving entire memory and the same thing happens no matter how I do it.

I dont believe its my memory card because before I went to 1.22 this didnt happen.

I get the same thing as well. I went between 1.22 & 1.21 & still get the same thing. I have read over the posts about how to save & I'm doing it the same as everybody else but it still happens.

I'm with you on this one, it needs to be fixed. There shouldn't be this big of a problem trying to save your work on a $1700.00 machine. I know there will be problems when a new product comes out but the 2500 has been out for a while now, it's time to get it right.

CYRUS. In the meantime I have been tracking all of my beats to pro tools before I save & shut it off. I don't know if you have it or anyother recording software but you might want to try that too. I know it takes up time but at least you know it will be there when you turn the machine back on.

This big is just lame. I'm still on 1.1 and I guess I am staying there.

saving bugs for the 2500 will soon be gone, if you get my drift

Antonym wrote:saving bugs for the 2500 will soon be gone, if you get my drift

their is no saving bugs in the mpc2500 if you get my drift.....put each beat in a seprate named folder.....and when u save "save entire memory" to the folder ....your beat will load up for sure if not your cf card or card reader or hd what ever u save to is **** up

savilion wrote:

Antonym wrote:saving bugs for the 2500 will soon be gone, if you get my drift

their is no saving bugs in the mpc2500 if you get my drift.....put each beat in a seprate named folder.....and when u save "save entire memory" to the folder ....your beat will load up for sure if not your cf card or card reader or hd what ever u save to is **** up

no way man. First of all, I have done this. Secondly my cf card is fine.

thirdly, what ever happened to shit working the way it is suppose to. So we have to save entire memory for every thing we do, including minor edits? Thats bullshit.

thirdly, what ever happened to **** working the way it is suppose to.

hahah my bet is that akai cut all its funding to os development and started paying its coders with monopoly money

I have never had a problem saving that way and neither has others....... it takes like 20 seconds tops to save entire memory or replace whats their..... if you can reproduce this bug on your machien but I cant then its oviously a hardware issue , all day i v been saving with no problems ... I even saved the programs and the sequences sepratly...and still everything loaded up fine.....so....not sure what the problem is ...anyone else with this problem?

savilion wrote:I have never had a problem saving that way and neither has others....... it takes like 20 seconds tops to save entire memory or replace whats their..... if you can reproduce this bug on your machien but I cant then its oviously a hardware issue , all day i v been saving with no problems ... I even saved the programs and the sequences sepratly...and still everything loaded up fine.....so....not sure what the problem is ...anyone else with this problem?

Only save entire memory is the sure shot, saving individual programs and sequences works for a while and then it corrupts. There is a saving issue or there would not be as much talk as there is. One should be able to save how they want instead of entire memory. One thing is certain as long as I have been saving entire memory to a folder I have not had a problem even when I resave a project no problem replacing files or whatever.

this issue is bvllshyt and needs to be fixed but of course AKAI ignorance is more important than its consumers. Same with the midi issues.

it is bullshit. Think about it, the 2xl has no saving issues and how old is it?

i've been saving the entire memory. whenever i make changes, i save the entire memory to new folder. i've tried to save the entire memory to the same folder i had previously saved to, of course with replacing existing files, and it didn't save all of the changes i made.

it was obvious too, i made a beat on one day, the next day i loaded it up, decided that the kick pattern was all wrong and redid it. i saved the entire memory to the same folder replacing existing files thinking nothing of it. the next day when i loaded it up, the sequence had the original kick pattern, not the new one that i had changed it to.