Official release notes for OS 1.70

http://www.akaipro.co.jp/jp/datalib/dow ... _v170e.pdf


Adrian
FWTX

Some of the bugs on the list in that PDF are quite frightning!!!!!

Do Akai Unprofessional Inc have ANY kind of systematic software test regime in place?!?!!?



"On entering the EFFECTS pages, "NO EFFECT" could be shown instead of the correct effect. This only happened when coming from PROGRAM or SAMPLE monitor mode" -
I reported this bug nice to have it fixed.

Yeah,

It's good to see that AKAI have fixed some of the issues that we have been reporting. I reported these two:

Fixed crash when recording in Step Edit and a "MIDI Panic Reset" is
received on MIDI-in-I and MIDI-in-II simultaneously.

If a long sysex message (9 bytes or more) was recorded in step edit mode, incorrect data was recorded.

Especially the first one was dangerous, causing my MPC to crash completely (the fatal error screen) when I switched my AMT8 midi-interface from computermode to patchmode and vice versa, but it only happened after recording something in STEP EDIT mode strangely enough. I have lost a lot of work due to that, more than once. I know, I know, should save my stuff periodically, but somehow I keep forgetting that when I am in a flow . Finally I don't have to worry about switching my AMT8 anymore... maybe NOW I'll make some good music

bleepfreak wrote:
If a long sysex message (9 bytes or more) was recorded in step edit mode, incorrect data was recorded.

its good to see all those bugs fixed - some i haven't even been really aware of ... the sysex one for example ... and i got a question to it ...

a few month back i been doin a complete backup of my virus - total sysex dump to store everythin i did on the virus on the 4k to feel saver - its quite a long sysexdump - ... i never been aware of the above bug - and i never yet sended that sysex total dump back to virus. meanwhile most of the patches are overwritten at the virus - so question: .... you d say that basically the backup i did a few month back contains fukked up data?? if so i guess i just lost 1-2 years of virus patches ... and will do a backup right again (is the shit workin now? anyone tried already? - if it worx now i could backup whaz new and test my older backups) - on regular dumps such as single dumps, arrangement dumps ... i never got a problem ...

damn - any insight on thisone is greatly appreciated coz it qui5te pisses me off atm ... and currently i dont rreally feel like sendin those sysex backups there to test it coz i did quite a few new patches meanwhile ... and i wanna keep at least those ...

btw: i encountered a thing dunno whether i should call it a bug or its the bug described above regarding sysex ... just asking whether anyone encountered the same ...

i dump my patches (arrangement) from the virus to the 4k and save it as a single sequence to backup just the sounds on the virus on my harddisc (i usually save it on seq. 127 which contains my virusdumps) - i wanted to upload that sequence to use the same virus sounds on a song i m workin on .... whenever i uploaded that seq to seq 127 on my new song in the new track my 4k crashed (black screen) ... did it 3 times in a row one week back ... uploading normal sequence data just in the same way was never a problem and never caused my 4k to crash ... anyone encoutered thisone? you think its the bug sorted out with new os? or should i report it to akai? ... thanx

Altopiano wrote:

bleepfreak wrote:
If a long sysex message (9 bytes or more) was recorded in step edit mode, incorrect data was recorded.

its good to see all those bugs fixed - some i haven't even been really aware of ... the sysex one for example ... and i got a question to it ...

a few month back i been doin a complete backup of my virus - total sysex dump to store everythin i did on the virus on the 4k to feel saver - its quite a long sysexdump - ... i never been aware of the above bug - and i never yet sended that sysex total dump back to virus. meanwhile most of the patches are overwritten at the virus - so question: .... you d say that basically the backup i did a few month back contains fukked up data?? if so i guess i just lost 1-2 years of virus patches ... and will do a backup right again (is the **** workin now? anyone tried already? - if it worx now i could backup whaz new and test my older backups) - on regular dumps such as single dumps, arrangement dumps ... i never got a problem ...

damn - any insight on thisone is greatly appreciated coz it qui5te pisses me off atm ... and currently i dont rreally feel like sendin those sysex backups there to test it coz i did quite a few new patches meanwhile ... and i wanna keep at least those ...

According to the Release Notes, this bug only happened if you recorded the Sysex data
via Step Edit. I'm guessing if you did a complete back up of the Virus sounds, that you
recorded the dump in real time and not in step edit mode?



I record sysex data all the time in Step Edit mode, I'll have to check how long the Sysex strings were. What I like to do is, since I myself, use quite a bit of outboard synths
rather then just my MPC. So when I am done with a song, what I like to do , is go ahead
and take a sysex dump of the patch that the synth is playing and put that into a blank
track.

Then when I load up my song again and play it, the MPC sends the SYSEX strings to the
respective synth and programs them with the patches that I use in that song. That
way I don't have to keep track of whether I used this patch in that song or not. At
any time I can wipe the sounds on my synth and know that when I reload up that song again
that My sysex data will reprogram the synth with the proper sound. I've tested this on
all of my synths, so I'm guessing my sysex strings were shorter then this bug.

Mr Bleepfreek,
by "MIDI Panic Reset",
do you mean the MIDI System Common "FF hex" byte ?
Or sthg else?

(cos I didn't think the MPC4000 responded to the FF byte at all - its own MIDI implementation chart says it doesn't anyways.

Altopiano wrote:btw: i encountered a thing dunno whether i should call it a bug or its the bug described above regarding sysex ... just asking whether anyone encountered the same ...

i dump my patches (arrangement) from the virus to the 4k and save it as a single sequence to backup just the sounds on the virus on my harddisc (i usually save it on seq. 127 which contains my virusdumps) - i wanted to upload that sequence to use the same virus sounds on a song i m workin on .... whenever i uploaded that seq to seq 127 on my new song in the new track my 4k crashed (black screen) ... did it 3 times in a row one week back ... uploading normal sequence data just in the same way was never a problem and never caused my 4k to crash ... anyone encoutered thisone? you think its the bug sorted out with new os? or should i report it to akai? ... thanx

I have a problem when I do a sys. ex. dump from the triton to the mpc. It works fine when I dump it to the mpc and dump it back to the triton, where I have the problem is after I save the sys. ex. info onto the mpc and turn it off when I turn it back on and load the sys. ex. info into the mpc and try to play it back to my triton I get a "buffer full" message on the mpc. I called akai and they couldn't help me out, I noticed that this new os does the same thing.

thanx renegade ... yeah i did it realtime so hhopefully its all good for the total sysex dump.

maybe i was panicing coz i had those problems last week on some sysex dumps ... i encountered it in 1.60 - its only when i loadup the independently saved sequence containing the arrangement dump (guess its 16 +1 syssex messages). i dump my arrangements or patches all the time, the 4k even displays them in step edit, i save them with the songs and i never encountered a similar problem with those sysex dumps before - if i loadup an all file (which contains the same sysex dumps on sequence 127) and send it back to virus everything plays back as it always did ... however if i save the seq 127 indepentently i m not able to upload it again (ie to use same patches on a different song) coz my 4k (even with empty memory) crashed 3 times in a row last week just by attempting to upload that seq 127 containg the arrangement dump for the virus ...

jonspnices .... the midi buffer full thing at my 4k just happened when i sended sysex messages to virus at somewhere over 100 bpm ... dont think that thats your problem but if ya didn't already turn bpm down to 30 and see if that sorts it out ...

jonspnices .... the midi buffer full thing at my 4k just happened when i sended sysex messages to virus at somewhere over 100 bpm ... dont think that thats your problem but if ya didn't already turn bpm down to 30 and see if that sorts it out ...

It does the same thing no matter what the bpm is set at. It only happens after I save the sequence. I wonder if something, like some type of compression, is done to the sequence when you save it.

I think it might be a bug with this brand of hard drive that comes with the mpc, because I saved the sys. ex. data onto a cd and every thing worked fine.

jonespnice wrote:I think it might be a bug with this brand of hard drive that comes with the mpc, because I saved the sys. ex. data onto a cd and every thing worked fine.

Correction, it doesn't work when saved on a cd either.

To Feline:

// By "MIDI Panic Reset", do you mean the MIDI System Common "FF hex" byte ? //

No, Simply all notes, on all channels turned off and maybe a reset of all controllers on all channels too. When you switch an Emagic AMT8 or Unitor8 from patch mode to computer mode it sends out these note-offs to avoid hanging notes after switching. I use the amt as a midi patchbay and have both the MPC input ports connected to it. When it received these note offs on both ports the MPC crashed, but only when I recorded something in step edit first...

When I work on my computer and run an application that uses MIDI, the amt automatically switches to computermode. I Crashed my MPC more than once by starting Nuendo. At first I thought it was the usb connection but it also happened with the cable unplugged.

Saves me a lot of hair since it's fixed now
________________________________


To Altopiano

The sysex bug only occured in step edit when the sequencer was not running. Strange things happened like note data from track 1 appeared in the exclusive list on track 2. I don't think you should worry too much about your backup.

By the way, the method Renegadebliss describes would be a much better sollution for backing up your sounds. I use it all the time to make sure every song contains it's own set of sounds backed up in the sequence itself. You never have to worry about overwriting any memory slot in any synth again because the sounds are always right there where you need them, in the song. Of course it is also handy to keep some of the sounds stored in the virus to be able to use them more often...
Also if you have a gig and for some reason you can't use your own Virus and you need to borrow or rent a Virus, or something like that, you can plug it in and press play and the song will start with the original sound right away.

....

nicone - thanx bleepfreak and renegadebliss for your hints with dumpin and backin up. hints like that are always welcome and much appreciated coz my backup strategy is not really the maximum - i know .... however i m quite happy as it is coz there was worse... at least this way everythin gets saved within an all file ... but what to save where best seems to be an ever lasting issue here

anyways thanx - i ll backup on tracks next time i switch my 4k on ... maybe with the new play start function i ll even insert a few bars at the beginnin of seq 1 - dump virus in there- and switch play start to loop and go like that ...

... and if my kb where to die i d cry and get the ti ... with no virus around here i guess i couldn't resist in pickin up a polar ... still quite sure to keep the kb for some more time ...