Beta 15 bUGS.

nym: in that pic of you and your cousin above, have you changed the paint job on your mpc? looks good either way. i take back all i said.

yeah it's the same paint job, it just gets gnarlier. there's rust forming - i love it!!!!

OK, I just installed beta 15. No funny Flash ROM messages.
Nice.
But wonder why i didn't and you did nym?

Antonym wrote:yeah it's the same paint job, it just gets gnarlier. there's rust forming - i love it!!!!

hahaaaa your mpc's turning ginger! more ridicule material! great stuff.

***space reserved for nym's mpc***

SELECTION BUG:

1. Zoom in on your sample
2. Go to St. and select start point
3. Go to End and select end point
4. When you go back to St. now your End point will slightly be off


anybody noticed this?

do the numbers change, or just the display? if it's just the display, it's the same thing that i've been talking about w/ the trim selection being off

yes nym its just the display the numbers stay the same. do you think this is just an optical thing or not?


p.s. my mpc doesnt freeze in the trim window without any samples loaded

Alright, first off I have to agree that this beta is really starting to show the huge improvements that 3.0 brings to the extent that there is no going back without suffering a severe handicap. This is especially true for the vastly improved chop(formerly slice) feature. I am wondering what "Auto" does in chop too, I think it is supposed to automatically detect the amount of regions to create. If anyone knows for sure what it is, let me know.

Also, prior to os 3.0 Mode+Pad11/Pad15 made a nice flesh hitting rubber sound but nothing else.

As for bugs, I read through this post and tried some of these to see if I could recreate them, since the results have been different for different people on some of these.

1. Start MPC with no samples and go to trim mode causes crash- still doesn't crash my machine, but new to this beta I now cannot cursor around parts of this screen when no samples are loaded.

2. While playing sequence, go to Mode+A11 and try to change programs by holding F1 and turning jog wheel causes crash- I tried this, but when sequence was playing and I went to Mode+A11, held F1 and tried to turn the jog wheel, it wouldn't change until the sequence was stopped. It did not crash on my machine though.

3. Incorrect displayed selection of start time in trim when fully zoomed out- I'm still getting this as well.

4. OS flash rom error- I also got this error/crash when machine was freshly turned on and empty as well as after a project was loaded.

5. Directory Error when trying to save entire mem over existing project file using replace- For the first time when doing this, I did not get the Directory Error in this beta.

Another bug that I just came across testing these was that in beta 15, when you press (Mode+Pad2) to get to load mode, it takes a couple of seconds to come up and the mode light stays solid green during this time. This only happens some of the time though and only to Load mode.

As for the track 61-64 bug, the author made a big writeup in the beta15 bugfix report about how he could not replicate this. However I am getting the exact same extra beginning of sample bug in beta 15 as I did in beta 12, 6 and prior. Also at the very beginning of the extra portion there is a spike you can see clearly in trim mode.

Nym, you said you are getting this 50% of the time, what method are you going about when it works/vs does not work?

Sorry if this next part is redundant.

If anyone reading wants to test this without going too far into it, try this.
1. start mpc
2. go to track 61, leave tempo and bars alone
3. set recording inputs to what you need
4. press overdub+playstart
5. after count in play a simple instrument or vocal line to metronome
6. press stop at end of recording
7. go to click menu (main then F2)
8. turn "in play" to "yes", and close (F4)
9. press playstart to playback track and it will start late and in not sync with the metronome.
10. go to trim mode (mode+pad6) and select newly recorded take
11. look at the beginning of the sample where you will see a spike and a bit of dead silence before the signal comes in.

Please post your results to see if this is a common problem or not.

Thanks for reading my long and kind of boring post.

i have a problem with version 15 ...i dont know how to zoom in on the end point of a slice, because it doesnt work automically.

anybody noticed this?

Good catch Chulukinat, I couldn't do this as well in the new Chop mode. A workaround that works on all but the last slice is going to the next slice over and adjusting and zooming the start time. (example: Slice 3 start time and zoom would effect Slice 2's end time and zoom level).

yes i know but it should be fixed anyway.

but i think all hell just broke loose! i tried to covert a sample from stereo to mono and i get a CPU ADDRESS ERROR (read) ---------------------------------
----------------------------------------------------------------------------------------
PC(8847a90c) SR(blablablablabla.........................................
------------------stack dump (sp=884ffeec)---------------------------
984dkjhkdj8784 849874987kjhffjh
989898dkjhkjhk 48748kjhdkjhdk
798479487uhdf djkhkj8u8ruiend

SOMETHING LIKE SHOWN ABOVE

HELP!

well i already rebooted it and lost my beautiful work ( "the struggles of a beta tester" i can hear yall thinkin )

but i have another problem. when you load a sample from your hard drive she wont ask if you would like to assign your sample to one of her pads. i think she's having hoogmoedswaan!

I just tried to replicate that by converting a stereo sample to mono using Stereo L+R=>Mono and Stereo L-R=>Mono and the both worked without crashing my machine or having any other error.

What steps did you take, how long was the sample and how much of it was selected when this error happened?

Chulukinat, in Load mode press the window button at any time and the Option dialog comes up that lets you select: Sample assign to pad window: (Off or On). When this is turned on, a much improved pad assignment window comes up that shows what samples are located on which pad and where you would like to put the new one.

I don't want to ask for more new features since the original set is still being worked on, but the choice to assign a sample to a layer in the Assign to Pad window rather than always replacing the existing sample would be nice.

(All the edits are because I keep mixing up words like program and pad.)

Hey, just wanna thank everyone that's been keeping us posted on everything. This beta is really coming along well, thanks to 1k fam and JJ of course.

Much respect.

This made my day.