beta 12 bug list (ONLY POST IF YOU KNOW YOUR SHIT)

^^^ on a sidenote, i wish i could take the day off from work, so i can do some beta testing and relax. but unfortunately my co-worker is sick and i gotta cover for him.

hahahaha you must lay tile in fredericksburg virginia with a conservative christian and his cokehead brother, too

Antonym wrote:hahahaha you must lay tile in fredericksburg virginia with a conservative christian and his cokehead brother, too

LMAO
that's hilarious!

i gotta get going. i'm running late.

anybody get a directory error when saving entire mem overtop a preexisting project folder in 12?

i got it yesterday on 3 and i doubt JJ and co has worked on it

obvious bug that nobody seemed to have mentioned. no matter what timing u set the quantize to, it quantizes to 1/8 notes unless u set it to 1/32t then quantizes to 1/16t. am i the only one that this happened to. also when loading samples from flash it doesnt let u assign em to pads, just loade em into memory, and u gotta go to program and assign.

this is a bug report for os 12
which you don't seem to have, as 12 does allow you to assign samples via loading.
as for the first problem, i couldn't replicate it.

download 12. b

Here's one that causes a crash on my machine:

1) Power on with NO samples loaded
2) Go to trim mode
3) I get a crash

If I have any samples in memory, this doesn't happen, nor does it happen if I load a sample, then clear the sample memory and go back to Trim mode. This suggests that it's a power on/initialization issue.

^ ^ confirmed

1). Turn Power On.
2.) Go to a load a folder
3.) Go to main screen and now the sequence name is named after the program and MIDI set to 1A bars is set to 1.

I've just tried doing it several times and I only seem to notice it on programs with 16 or less samples assigned to it.

strength wrote:obvious bug that nobody seemed to have mentioned. no matter what timing u set the quantize to, it quantizes to 1/8 notes unless u set it to 1/32t then quantizes to 1/16t. am i the only one that this happened to. also when loading samples from flash it doesnt let u assign em to pads, just loade em into memory, and u gotta go to program and assign.

i agree... when loading samples... i like to assign to pads... not have to go to (mode pad a11) or somethin

Antonym wrote:this is a bug report for os 12
which you don't seem to have, as 12 does allow you to assign samples via loading.
as for the first problem, i couldn't replicate it.

download 12. b

how? i load a sample.. and thats it. no assign screen?

am i not doing sumthing

I've also been trying to replicate some of these posted bugs in beta 12 and here's what I got.

1. Problem of not being able to change res, pan, filt in new prog (or propellant actuated device) screen. I found this still to be true in beta 12, where no paramaters can be adjusted in this screen while the sequence is playing (but I think that is how it is supposed to be)

2. Problem of footswitch- I don't own one, so I don't know about this problem, or if it was solved in the new beta.

3. The L+R=Mono sample conversion bug- I tried this in version 12 and it is a bad one. After converting, when you scroll through the samples in trim mode the screen starts to corrupt and then machine has a CPU Address error (read) ,does a stack dump and the machine crashes.

4. Nym already did the 4 layer bug test to report it in working order and it is working for me too.

5. Directory Error when saving a project file over an existing one- I did this in beta 12 and got the same message.

6. 1/8 or 1/32t note quantize bug- I also couldn't replicate this in beta 12.

7. Power on with NO samples and go to trim mode causes crash- I did this in beta 12 twice to make sure I was doing it right and did not get a crash (but I did find that the start and end markers still highlight parts of the screen with the jog wheel)

8. Power on, load folder (im guessing with a program and samples in it) and sequence name is now program name and the bars are set to 1. - I did not get this error in beta 12. I first tried loading a folder with only one program that had eight samples (since it was said that it only happened with 16 or less samples) and it still worked okay. I then loaded a folder with a couple of sequences and a program with less than 16 samples and it still worked okay.

Here's a new bug I noticed while trying to replicate these bugs. I am getting random clicks as my sequences replay (ones made with short samples only and not direct record takes). I looked at the level to see if it was occasionally clipping, but it was okay. I also looked at the samples used in the sequence to check for clicks and make sure they started and ended at zero crossings and they did. The clicks happen at random intervals during the sequence. The one I used to find it on was a two bar loop which played fine sometimes but had loud clicks every once in a while at different times in the sequence, but not every time through.

I don't want to write the last one (clicking) up yet as a bug until someone can replicate it, since there are other things in my signal chain/cpu that might be causing this.

Load a Pgm.
Go to Mode (mixer) pad a8
assign 6 samples to different outputs. 1 2 3 4 1/2 3/4
It works Fine.. all sounds go to different outputs (btw i Love the mono outs)

Now
Go to Mode (pad A11)
OUT 1 says OFF
OUT 2 says ..nothing its blank
OUT 3 says 1
OUT 4 says X2
OUT 1/2 says 1/2
OUT 3/4 says 3/4

Just Wierd.. Right?

ALSO: would be nice to use the WHOLE button (f6) to change all outs to 1,2,3,4,1/2,3/4 but instead it only gives the option of 1/2 , 3/4 , and ST


i thought id say something cuz id like to see that fixered


www.riseproductions.com/mp3player.swf

Bigman ! thanks for testing those bugs & potential bugs.. good stuff!!

Here's another from Beta 12:

1) Power on
2) go to program mode [PAD7], select the 'OFF' program
3) go to [PAD11], and press any pad other than PAD1
4) MPC freezes

(as an alternative to step 2, you can go to the program field in the Main window and select 'OFF" there).