beta 16 bugs - please copy old

bigman i know you just posted a bunch in the 15 bug list, could you copy the applicable ones?

thanks
nym

hahaha look, they photoshopped it to look like 16. that's hilarious.

keepin it (un) real.
these guyz are lo-key

i finally installed os3. looks really good indeed! and I have not found big bugs so far.

MOVE: in step edit.
after several moves i manage to have one event moved sort of before 01:00:00. it displayed it with lots of zeros after the pad number (in the step edit screen). could not reproduce it though... (and not a big deal as it did not crash the mpc, and i could delete the event easily).

i was also trying the SAVE and LOAD screens. could not get the directory error so far (good!).
but when i save entire memory to overwrite one folder, it first slowly deletes all the samples one by one, and then save all the stuff. but the delete process takes quite a long time.
but if i save to autoload while using the F keys, then it empty the autoload very fast (in 2 secs, display "please wait...").
is there a way to overwrite/save quickly for normal folders folders ?
i remember in os 1.07, it was fast if the folder was hilighted, and slow if i was already inside the folder.
any thoughts ?

hey nym ; by just looking at that starting screen picture, wouldn't it be awesome to make some sort of asci art for the mpc(uhmm.. imma bit stoned tho) .. nice gimmick for in the future perhaps

i found a few:

1_ push [mode] + [pad 9] -> midi sync
2_ soft thru: select OMNI-AB.
3_ error = no midi thru.

1_ push [play start] -> mpc + midi synced starts from beginning
2_ push [play start] mpc restarts from beginning
3_ error = midi gear synced to midi clock does not restart.

1_ push [play start]
2_ push [note repeat] (with or without holding [shift]) + push any pad
3_ puch [F2 8/3] or [F4 16/3] or [F6 32/3] (triplets)
4_ error : repeat too slow (internal sounds or external midi gear)

i am doing some more testing now, so will be adding more later.
I have not submitted them yet to the programmer, so let me know if a bug does not make sense or has been posted already or you cannot reproduce.
cheers
edit: removed a bug which wasn't one

in OS 3.00 beta 16 i found like i said a sound difference between load screen and sequnce screen. try and play a sample in load screen and then the same sample in sequence screen.

confirmed, see below.

1 push [mode] + [pad 2] -> LOAD
2 "memory card" selected
3 push [->] -> select a folder
4 push [->] -> go inside the folder
5 push [arrow down] -> select any sample
6 push [F5 play] -> play sample
7 error: sample play incorrectly.

last one for today:

1 push [mode] + [pad 10] -> other
2 push [F3 FOOTSW]
3 footswitch 1 or 2, select "REC/PUNCH"
4 MPC is not playing
5 press Footswitch -> MPC starts playing
6 error: external midi gear, synced to midi clock, did not start playing

anyone experienced this :

1/ Highlight event in grid-edit
2/ sample is assigned to sample bank B, C or D
3/ Press window to bring up note info, but it is not there, you have to go to step edit to see the details.

Sample bank A works correctly in grid-edit.

Over

This is not a bug, but i think it should be corrected:
1) You go in to the Trim page and you select to slice a sample
2) When you go to set the "sample end" in a zone and you "zoom in" to do so more accurately, you can not see the "sample end" anymore, but the sample end value keeps on changing if you move the data wheel...
i think it would be better if the screen follows the sample end point..

truvc wrote:MOVE: in step edit.
after several moves i manage to have one event moved sort of before 01:00:00. it displayed it with lots of zeros after the pad number (in the step edit screen). could not reproduce it though... (and not a big deal as it did not crash the mpc, and i could delete the event easily).

That also happaens in 2.1, it´s not a OS 3 specific bug.

ryssen wrote:

truvc wrote:MOVE: in step edit.
after several moves i manage to have one event moved sort of before 01:00:00. it displayed it with lots of zeros after the pad number (in the step edit screen). could not reproduce it though... (and not a big deal as it did not crash the mpc, and i could delete the event easily).

That also happaens in 2.1, it´s not a OS 3 specific bug.

ok. maybe if you know the pattern to reproduce it we could post it to the bug report.

wavemartian wrote:anyone experienced this :

1/ Highlight event in grid-edit
2/ sample is assigned to sample bank B, C or D
3/ Press window to bring up note info, but it is not there, you have to go to step edit to see the details.

Sample bank A works correctly in grid-edit.

Over

I had this also. but i had the feeling that it had been reported already. not sure...

Also the move bug in GRID is still there,

1. move a note in GRID EDIT from 001.04.72 to 001.04.78
2. play the sequence for a few bars them go back to that note (click move in grid)and its value (on mine) is now something like 001.04.60
3. it still shows original value in GRID EDIT 00.1.04.72 BUT but plays accrding to the random value it created in STEP EDIT
4.UNDO does not take it back to defult value either also just some random value

Seems moving values in between normal TC is not possible in GRID EDIT

cyklops wrote:Also the move bug in GRID is still there,

1. move a note in GRID EDIT from 001.04.72 to 001.04.78
2. play the sequence for a few bars them go back to that note (click move in grid)and its value (on mine) is now something like 001.04.60
3. it still shows original value in GRID EDIT 00.1.04.72 BUT but plays accrding to the random value it created in STEP EDIT
4.UNDO does not take it back to defult value either also just some random value

Seems moving values in between normal TC is not possible in GRID EDIT

cyclop, did you submit this bug already ?

i think would help a lot much if the japanese programmer could leave on the website the complete list of submitted bugs, with the one fixed and the one still open.
i might request that. what do you guys think ?