Beta 13 Bugs?

i still haven't been having this issue, but it did seem weird for a split second there when i recorded w/ note repeat a 1/32 triplet machine gun hat and then tried to quantise it to 1/16 triplet. for a while it sounded exactly the same. but when i recorded the same thing in 1/16 triplet, it sounded considerably slower. which makes me think that there is some kind of bug in the time correction, which is strange because i doubt that they even touched that.

can you give us an exact set of steps to replicate your problem?

I went back and tried these again to make sure and here's what I got:

When I boot up and go directly to trim (Mode+pad6) I get the trim screen which is empty (not a blank screen or anything, just without samples). I can then cursor around to (L/R), start and end without any problems and go to main or any other mode without crashing. Something funny in this empty trim screen is that when I select start or end and move the jog wheel, it moves the cursor(or line on screen) going one direction and highlights the empty space going the other. I've tried this about five times to be sure I wasn't mistaken and I get no problems every time.

As for the new trim bug you posted, I retried my approach a couple of times and I actually did get this exact error on my third attempt. On this third attempt, I loaded a long phrase sample and entered Trim mode. I then zoomed in enough to set the start time at the start of the second beat of the second bar of this 8 bar sample. I then zoomed out and the sample did show as completely highlighted as you said (this is only at the farthest zoom out view, one zoom earlier is still okay). The jog wheel at the farthest zoom brought me to 00000000 at one click left as well.

Also, here's what happened on the Second attempt (which is actually a different effect of the same bug). For this attempt, I used a phrase that was only one bar and zoomed in to select the beginning of the second beat. When I fully zoomed out, the picture of the sample misrepresented that there was more highlighted area than there actually was supposed to be. Only this time the sample was not fully highlighted due to it being shorter in length. Instead, it showed the highlited area start only a little while sooner than I had set (during the beginning of the release of the first beat) and the start wheel was not taking me directly to zero on one turn when fully zoomed out.

as ant said, people might do things slightly differently. maybe you could post the exact steps which leads to the bug, for others to reproduce it.
(steps from "power on", press key, do that etc... until the bug)

its like: power on, load folder , assign sounds to pads, set tempo, set time correct to 1/16t , hit record , tap in a two bar loop, when it loops and plays back all the sounds (kick,hihat,snare)are quantized to 1/8 notes (dead on 1st,2nt 3rd and 4th beat of the meassure),set the quantize to 1/32t and it quantizes to 1/16t.

i just tried all the different quantize settings and here goes: when set to 1/32t it quantizes to 1/16t, when set to 1/16t it corrects it to 1/8t. 1/8,1/16,and 1/32 timing plays back right. i think it has something to do with the tempo , cause while i was messing with it , the tempo switched on its own to half of what i set it (from 86 to 43) , and the nature of the bug is it quantizes it to half the timing u set it to. holla back fellas . other then that i like the new os a lot especially the way the trim function is set up with the tap tempo button, the shift ,left click thing in the previous os's was kinda akward and the q link slider wasnt precise enough


http://www.myspace.com/strengthofwillakalittleboyblue

truvc wrote:maybe it would help to reset the mpc after every new os update. (or before...)
can't remember how to reset it though.

I belive that you hold down shift while powering on the MPC. I think that bypasses the OS 1.3 bootblock and restores OS 1.3.

I'm using beta 13 and still have problems direct recording to tracks 61+ if I'm recording the outputs of my DAW and I hit play on my sequencer which is controlling the playback of Sonar. The time window that pops up displays erratic numbering. Anyone getting this?

Saul

But with my Proteus X, think it is more of a MTC or lack of issue though and not an OS.3 ISSUE

TBonus76 wrote:

truvc wrote:maybe it would help to reset the mpc after every new os update. (or before...)
can't remember how to reset it though.

I belive that you hold down shift while powering on the MPC. I think that bypasses the OS 1.3 bootblock and restores OS 1.3.

I never tied shift + power on.

in fact i was thinking of [erase] + power on

same as here:
http://www.mpc-forums.com/viewtopic.php ... ank+screen

truvc wrote:

TBonus76 wrote:I belive that you hold down shift while powering on the MPC. I think that bypasses the OS 1.3 bootblock and restores OS 1.3.

I never tied shift + power on.

in fact i was thinking of [erase] + power on

same as here:
http://www.mpc-forums.com/viewtopic.php ... ank+screen

Lol... Ooops yeah, that's what I was thinking of.

..after recording a take, it would be nice to be able to assign the new sound to a pad.

also i notice that the INPUT THRU function turns itself off ( no input thru sound) i have to go back to (mode - mixer - input thru OFF then back on)
before i hear the sound again.

I made a PGM in Recycle. 18 chops.
set all pads to Note Off.(in recycle)
loaded to Mpc via Usb
went to the folder Opened up my new PGM.

now the bug.
all of the sounds come from OUTPUT 1/2 even tho it's set to ST

then i went to the Mixer page. too see whats up?

when i set sound to OUT 1/2 it comes out 3/4
when i set sound to OUT 3/4 it comes out ST
when i set sound to OUT ST it comes out 1/2
when i set sound to OUT 1 it comes out 4
when i set sound to OUT 2 it comes out 3
when i set sound to OUT 3 it comes out Stereo RIGHT
when i set sound to OUT 4 it comes out Stereo LEFT

OK then i decided to Power Off mpc to see if that was it..
Turned it back on ..loaded my new PGM. and they all come out the proper outputs 1 comes out 1 ,2 comes out 2 ,St comes out ST ETC.

hm. thats wierd.

ALSO.. any Pgm i make in Recycle..
when i hit the pads... the sound level is at 156 for every pad.
i have to go to Mode Program and hit each sound while turning the jog wheel to the right. it resets the levels back to 100 for some reason ....

anybody else use recycle and notice this?

cyklops wrote:In GRID i want to move a note 2 ticks say from 001.04.72 - 001.04.80 , it does not allow this if your grid is set to 1/16 or 1/8 , it keeps pushing to the default range, so basically i cannot move notes in between.

Also if i check that note in STEP EDIT it show a completely different value , i moved my note in GRID to .80 and in GRID it shows the note value as .72 still but in STEP EDIT it shows that note as .90

can someone else confirm this happening ?

forgot to add that if i move the note to 0.80 in STEP it moves fine but in GRID it still shows as .72

Yes, I have experienced something very similar, MOVE function and TC act rather funny, for sure.