By utty
Sun Jun 25, 2006 11:23 am
Please report bugs using mpc1000 OS 3 beta.
************
nym's compilation so far
bugs -
A - ENDLESS LIST LOOP in PROGRAM MODE
1 - load preexisting project
2 - sample new sound
3 - trim new sound
4 - attempt to assign new sample in program mode
5 - note the "endless loop" of preexisting samples that occurs.
6 - note that samples appear in trim mode
replication is hit or miss. other users have complained of this as well.
B - SAMPLE LOAD
1 - Load multiple samples from hd or mem card
2 - return to program screen
3 - samples appear not to be loaded
4 - note that in replication, i checked in "record mode" the remaining time available and saw that something was indeed loaded - simply not showing up in Program mode.
*** NOTE ON A AND B - due to the nature of these issues, it's my guess that they are the same bug, or at least caused by the same issue.
b
C - MODE 11 SCALE BUG
1 - load multiple preexisting samples
2 - enter mode/11
3 - change scaling w/ F4 and F5
4 - crash occurred twice to user "LONE DIPLOMAT" in same screen
C(a) - MODE 11 SCALE BUG ADDITIONAL
1) Press Mode, then pad 11
2) Press F6 'Whole'
3) Hold both F4 AND F5 and turn the data wheel.
4) The cursor will not return to the part of the screen that allows you to edit pad data; The MPC doesn't freeze, but Mode-Pad11 is stuck in this funny state until you reboot the MPC.
D - TRACKS 61-64 RECORDING INSERTS SILENCE IN BEGINNING OF SAMPLE
1. Turn Machine On
2. Go to track 61
3. Record by pressing rec+play( or play start) or overdub+play (or play start)
4. record track in sync to metronome or to other tracks already sequenced.
5. playback (this is now out of sync with the metronome most of the time, approx. 1/2 sec. late, enough to completely throw it off)
6. go to track 62-64
7. record track(s) using method in step 3&4
8. playback (this will also be out of sync with metronome and other track)
***** SUMMARIZED NOTES FROM USER "BigMan" - I laid a beat down and played a bass guitar over it on Track 61. The first time it sync'd and repeated perfectly. I went to track 62 to make another track--playback was not even close to how I put it down. I erased this track and sample. Next, i tried to find out what the problem was by recording on different tracks and resetting the time to 1.01.00 between takes. Trim mode also shows this offset.
E - DELETE FUNCTION IN GRID MODE
1 - Go to grid mode (Mode + Pad15)
2 - Move the cursor over an occupied cell of the grid, and press the 'window' button. This brings up a list of events in that cell, with the usual step edit details (velocity, duration, etc.)
3 - Select an event from the list, and press delete (F5). I've found that the display does not update accurately. Either nothing happens, and it looks like the event is still there, or the event pad changes. However, the event is deleted from the grid properly. It just looks kind of confusing.
F - DISPLAY PROBLEM IN GRID MODE
1) Start with a sequence that has multiple events on multiple pads.
2) Use the Tap Tempo key and the data wheel/cursor keys to select a region containing multiple events.
3) Press the Window key and the Events window opens. If the region selected contains more than 5 events then the list of events overwrites the bottom frame of the Events window and you are not able to scroll through the list of events.
G - SAVE BUGS
1. place a memory card in the unit which has samples.
2. load a sample into the MPC
3. save this same sample back to the memory card
4. the cancel/rename/replace screen comes up (good), however when you press replace, it deletes the original samlpe from the card instead of overwriting it (bad). You have to repeat this process a second time (save/do it/replace) in order to write the revised sample back to the memory card.
This save screen is a bit buggy in general, one time the bottom half of this screen went wacky and all letters appeared jumbled and broken up (I could not recreate this) It also does not always list all of the samples in the internal memory when you go to save. As this system is not one hundred percent stable, it does seem that the save screen should be fixed early so people can save their work before it freezes up.
H - SLICES TRANSIENTS ONLY
1 - this is not a bug--rather a request. OS 2.1 allowed "slicing," while 3.0 offers "transient detection." 3.0's slice technique is good -- as an option. however, we would love to have the option of either 3.0's slice technique or 2.1's slice technique. we need both as some samples have no transients. This has been brought up by many of your future customers.
=======>
end bug reports.
THANK YOU.
nym
************
nym's compilation so far
bugs -
A - ENDLESS LIST LOOP in PROGRAM MODE
1 - load preexisting project
2 - sample new sound
3 - trim new sound
4 - attempt to assign new sample in program mode
5 - note the "endless loop" of preexisting samples that occurs.
6 - note that samples appear in trim mode
replication is hit or miss. other users have complained of this as well.
B - SAMPLE LOAD
1 - Load multiple samples from hd or mem card
2 - return to program screen
3 - samples appear not to be loaded
4 - note that in replication, i checked in "record mode" the remaining time available and saw that something was indeed loaded - simply not showing up in Program mode.
*** NOTE ON A AND B - due to the nature of these issues, it's my guess that they are the same bug, or at least caused by the same issue.
b
C - MODE 11 SCALE BUG
1 - load multiple preexisting samples
2 - enter mode/11
3 - change scaling w/ F4 and F5
4 - crash occurred twice to user "LONE DIPLOMAT" in same screen
C(a) - MODE 11 SCALE BUG ADDITIONAL
1) Press Mode, then pad 11
2) Press F6 'Whole'
3) Hold both F4 AND F5 and turn the data wheel.
4) The cursor will not return to the part of the screen that allows you to edit pad data; The MPC doesn't freeze, but Mode-Pad11 is stuck in this funny state until you reboot the MPC.
D - TRACKS 61-64 RECORDING INSERTS SILENCE IN BEGINNING OF SAMPLE
1. Turn Machine On
2. Go to track 61
3. Record by pressing rec+play( or play start) or overdub+play (or play start)
4. record track in sync to metronome or to other tracks already sequenced.
5. playback (this is now out of sync with the metronome most of the time, approx. 1/2 sec. late, enough to completely throw it off)
6. go to track 62-64
7. record track(s) using method in step 3&4
8. playback (this will also be out of sync with metronome and other track)
***** SUMMARIZED NOTES FROM USER "BigMan" - I laid a beat down and played a bass guitar over it on Track 61. The first time it sync'd and repeated perfectly. I went to track 62 to make another track--playback was not even close to how I put it down. I erased this track and sample. Next, i tried to find out what the problem was by recording on different tracks and resetting the time to 1.01.00 between takes. Trim mode also shows this offset.
E - DELETE FUNCTION IN GRID MODE
1 - Go to grid mode (Mode + Pad15)
2 - Move the cursor over an occupied cell of the grid, and press the 'window' button. This brings up a list of events in that cell, with the usual step edit details (velocity, duration, etc.)
3 - Select an event from the list, and press delete (F5). I've found that the display does not update accurately. Either nothing happens, and it looks like the event is still there, or the event pad changes. However, the event is deleted from the grid properly. It just looks kind of confusing.
F - DISPLAY PROBLEM IN GRID MODE
1) Start with a sequence that has multiple events on multiple pads.
2) Use the Tap Tempo key and the data wheel/cursor keys to select a region containing multiple events.
3) Press the Window key and the Events window opens. If the region selected contains more than 5 events then the list of events overwrites the bottom frame of the Events window and you are not able to scroll through the list of events.
G - SAVE BUGS
1. place a memory card in the unit which has samples.
2. load a sample into the MPC
3. save this same sample back to the memory card
4. the cancel/rename/replace screen comes up (good), however when you press replace, it deletes the original samlpe from the card instead of overwriting it (bad). You have to repeat this process a second time (save/do it/replace) in order to write the revised sample back to the memory card.
This save screen is a bit buggy in general, one time the bottom half of this screen went wacky and all letters appeared jumbled and broken up (I could not recreate this) It also does not always list all of the samples in the internal memory when you go to save. As this system is not one hundred percent stable, it does seem that the save screen should be fixed early so people can save their work before it freezes up.
H - SLICES TRANSIENTS ONLY
1 - this is not a bug--rather a request. OS 2.1 allowed "slicing," while 3.0 offers "transient detection." 3.0's slice technique is good -- as an option. however, we would love to have the option of either 3.0's slice technique or 2.1's slice technique. we need both as some samples have no transients. This has been brought up by many of your future customers.
=======>
end bug reports.
THANK YOU.
nym
[/quote]