4.68

http://www7a.biglobe.ne.jp/%7Empc1000/

-------------------------------------
Bug Fixes: New OS Ver4.68 7-Jun-2007
-------------------------------------
1. [SEQ EDIT]
　　[COPY/MOVE]
　Setting conditions
　1.From Sq bars < To Sq bars
　2.Copy Start Bar > From Sq bars
　 It dose not work.

2. [SONG]
　　When play reaches the end of song the long sample sound also gets cut.
　---------
　[OTHER]
F2:[MISC.]
Mute/Stop of one-shot sample:THROUGH
Irrespective of the above-mentioned setup.
---------

3. [TRIM]
　　F5:[CHOP]
　　F3:[SLICE]
　　Numeric key dose not work.

I had a feeling we would have an update by the end of the week.

Still 220 samples infront of every slice when chopping?

balls, none of my chops all day have this silence before the sample plays...and i've choppedd roughly 220 samples today

mind uploading a sample?

Why does the version say 4.68 but the bin download says mpc1000_nv467.bin?

I got that also. But when you turn on 1k it then says 4.68.

Balls wrote:Still 220 samples infront of every slice when chopping?

I've never noticed that problem whne I slice.

However, I have noted that when you slice you should ensure that you don't edit the start point of the first slice. The bug is there, if anywhere, if you move the start point of the first slice anywhere up from 0, the slice job moves everything left with same amount, resulting in inaccurate slice points.
try it and see if that solves your problem.

wudsiba wrote:I got that also. But when you turn on 1k it then says 4.68.

That text portion of the site hasn't been updated. You'll notice that on the english translation. But the original Japanese homepage does have 4.68 available, despite the info reading 4.67.

I downloaded 4.68 from the japenese sight, but when I went to load the new version into 1k, when the machine searches the CF card, it says it found version 4.67. I went ahead and loaded that, knowing that the only version I had on the card was the 4.68 that I had just downloaded. I thought it was odd, but when I turned 1k off and then on again, it showed up as version4.68. That's what I thought the other post was refering to. Peace.

^^^ I've seen that happen in previous versions as well.

freezerman wrote:

Balls wrote:However, I have noted that when you slice you should ensure that you don't edit the start point of the first slice. The bug is there, if anywhere, if you move the start point of the first slice anywhere up from 0, the slice job moves everything left with same amount, resulting in inaccurate slice points.
try it and see if that solves your problem.

nice find. did you report it? sounds like JJ could easily fix that.

also, balls, are you using auto slice without actually going and adjusting all the start and end points?

cuz autoslice leaves silence in front of transients, a lot like recycle does.

that's (another reason) why i don't use autoslice - "divide and conquer" works even more accurately and just as quickly.

truvc wrote:

freezerman wrote:

Balls wrote:However, I have noted that when you slice you should ensure that you don't edit the start point of the first slice. The bug is there, if anywhere, if you move the start point of the first slice anywhere up from 0, the slice job moves everything left with same amount, resulting in inaccurate slice points.
try it and see if that solves your problem.

nice find. did you report it? sounds like JJ could easily fix that.

I didn't bother reporting that since it is not a serious bug, it just requires not editing the start point in slice mode, i.e. first edit the start and end as appropriate in TRIM mode, then get in slice mode. Excuse my laziness...

i take it he has not fixed my bug then, cause its starting to piss me off and its impacting on my workflow as i need to stop both cubase and the mpc, locate the mpc back to the start point then re sync.

not good!!