OLD OS 3 beta bug list - SEE NEW

I submitted a couple of bugs at the beginning of this beta testing to the author, when I recently looked at the list http://www7a.biglobe.ne.jp/~mpc1000/bug.htm I saw one of the bugs I wrote about. Under it it said "I can't see this bug", so I tested it out again with beta 6 and it is still there. Hopefully someone here can recreate this as well so we can better explain it and get it fixed.

Anyhow, I wrote about this bug a few pages back in this post, but here is a quick recap so you don't have to search. When recording to track 61-64, the recorded takes do not play back in sync and you need to trim a bit off of the front of each sample to make them play back right. I don't know the exact amount of time (i've been cutting 0.011.700 off the start and it's close, but not perfect) but you must subtract the same amount from each take for them to play correctly together.

Here's an example, say you have a beat (or not) laid down on the first few tracks. Scroll to track 61 and set your recording preferences (in Track press Window). Press overdub+record (this will count in and play your other tracks as well as the metronome). Play whatever "instrument/vox/etc.." to the click or beat and press stop when you are done. Now play back this track and it will be a bit late to start every time.

I don't think this is due to the positioning of the sample in the sequencer, since looking in trim mode you can see that there is extra time at the start of the sample itself. I think this is because during the recording of the sample on track 61-64, the recorder kicks in somewhere during the count in instead of 1.00.000.

This same error happens every time to me in all of the beta versions. So, whomever tries to test this, please post your results so I know I am not going crazy.

Hi Bigman,

I've seen something similar to this, but only sometimes. I'll try to spend some time digging in a bit further this weekend and see if I can recreate both the way it worked OK, and the way that I got the delay (I'll also check my delayed samples to see if it has the same added time you mention).

Antonym wrote:has anyone caused 3.0 to crash other than utty's tsig/grid bug?

we should concentrate on that problem first.

i'm gonna try to reproduce that when i get home and i'll get back to ya.

New info from JJ's site. Basically from the way it's written the person/people running the site are different from the actual programmer of the new OS. I'm not sure of their relationship, but the person running the site has sent a list of all of the feature requests which people have sent to the site to the programmer. Apparently there have been a number of requests for additional features and there's a limit to what the programmer will be able to feasibly implement. There are no specifics, so I don't know what this refers to.

I didn't have time to translate the bug list before I went to Tokyo, so I sent it in English and wrote a note in Japanese letting them know that I could translate the list if they have questions. In reponse to that, they told me they didn't understand some of the bugs so they wanted me to translate it. They are also looking into using Paypal when the official OS is released.

I'll try to get the bug list out as soon as I can.

List of bugs translated and sent out....

nice work. this is going so well. these guys are on the ball.

Since a couple of features have recently been taken out and/or dramatically changed, I thought this thread would be the best place for this even though it's not technically a bug.

I've noticed that in beta version 10 the trim/loop screen has changed in layout as well as the ways to navigate it. In this new layout the zoom functions are right in the main trim screen which is nice and the up down cursors can make the waveform look larger or smaller which is also a good thing. However, a couple useful ways of adjusting values are absent from this screen now, which are: qlink control of start and end time and numeric entry for start and end time. This leaves you only with the jog wheel, where increment control is now completely tied to the zoom level and sample length as explained below.

For example, a sample that is 00683909 long (<- this is the new sample time readout in trim/loop) will jump in these increments: 00002885, 00005771, 00008657, etc.. when fully zoomed out, which is the default in trim/loop view. While another sample that is say 00345178 long will jump in increments of 00001456, 00002912, 00004369, etc. Zooming in decreases these increments based on how long the sample is, and zooming all the way in is now the only way to be able to scroll one increment at a time.

Since the qlink and numeric entry are gone and jogging has changed, you must zoom in and out and really use your eyes to scroll to the precise spot to make an edit. Then you must zoom out to get to your next edit point which can get time consuming when doing specific tasks like extracting or fixing the track 61-64 problem.

With this being said, there is a good side to this new trim/loop mode. For one, the way the waveform now moves while the start/end point remains stationary (only on the screen of course) feels good in comparison to the opposite way it was before. Also, the new look and feel of the trim/loop screen is generally much smoother, faster and overall nicer than before. It looks almost as if the new trim/loop mode layout is meant to resemble certain computer based DAW's ways of sample editing, which is a step in the right direction.

So, to fix the control problems I mentioned but still keep the updated parts of the new trim/loop mode, I think these changes would work.

1. Put back qlink control of start/end points if possible
2. Put back numeric entry of start/end points if possible
3. Since (Shift+Cursor <&>) are now unused in this screen, the Zoom In and Out controls would fit nicely in these spots and speed up trimming. (Since zooming is now manditory to edit precisely and the buttons to do this are only on F3 and F4, it makes it inconvienient to constantly go back and forth from while editing.)

Let me know what you guys think since this is a big change for anyone who edits samples in the MPC.

i found a bug on beta 10:
1) go to trim page
2) edit sample: L+R=mono
3)Convert sample
4)Turn data wheel
5)the MPC frezees and give some strange cpu error...i tried 3 times.all of three happened.

LMFAO, Beta 10 within about 10 days and Akai can't release one within a few months!

Akai, step your fukkin game up...

Spirez wrote:LMFAO, Beta 10 within about 10 days and Akai can't release one within a few months!

Akai, step your fukkin game up...

co-sign

1.Turn on mpc

2.Load a sample from the HDD

3.Load a second sample from the HDD

4.The second sample will not appear in the program mode when you scroll the wheel, but when you go to trim mode the sample is there.

Tried the same file after restarting my mpc and it worked. Any one had this?

When in Grid sometimes pressing MAIN won't take me back to main.
I have to press STOP then MAIN

Then when I go back into Grid and try it again it works. Random

This has happened several times.

Oh yeah, anyone noticed when you press Window when an event is selected in Grid, the edit options have disappeared, "this section under development" or something! I hope that means he's working on it, hopefully giving us more options!

Since a couple of features have recently been taken out and/or dramatically changed, I thought this thread would be the best place for this even though it's not technically a bug.

I've noticed that in beta version 10 the trim/loop screen has changed in layout as well as the ways to navigate it. In this new layout the zoom functions are right in the main trim screen which is nice and the up down cursors can make the waveform look larger or smaller which is also a good thing. However, a couple useful ways of adjusting values are absent from this screen now, which are: qlink control of start and end time and numeric entry for start and end time. This leaves you only with the jog wheel, where increment control is now completely tied to the zoom level and sample length as explained below.

For example, a sample that is 00683909 long (<- this is the new sample time readout in trim/loop) will jump in these increments: 00002885, 00005771, 00008657, etc.. when fully zoomed out, which is the default in trim/loop view. While another sample that is say 00345178 long will jump in increments of 00001456, 00002912, 00004369, etc. Zooming in decreases these increments based on how long the sample is, and zooming all the way in is now the only way to be able to scroll one increment at a time.

Since the qlink and numeric entry are gone and jogging has changed, you must zoom in and out and really use your eyes to scroll to the precise spot to make an edit. Then you must zoom out to get to your next edit point which can get time consuming when doing specific tasks like extracting or fixing the track 61-64 problem.

With this being said, there is a good side to this new trim/loop mode. For one, the way the waveform now moves while the start/end point remains stationary (only on the screen of course) feels good in comparison to the opposite way it was before. Also, the new look and feel of the trim/loop screen is generally much smoother, faster and overall nicer than before. It looks almost as if the new trim/loop mode layout is meant to resemble certain computer based DAW's ways of sample editing, which is a step in the right direction.

So, to fix the control problems I mentioned but still keep the updated parts of the new trim/loop mode, I think these changes would work.

1. Put back qlink control of start/end points if possible
2. Put back numeric entry of start/end points if possible
3. Since (Shift+Cursor <&>) are now unused in this screen, the Zoom In and Out controls would fit nicely in these spots and speed up trimming. (Since zooming is now manditory to edit precisely and the buttons to do this are only on F3 and F4, it makes it inconvienient to constantly go back and forth from while editing.)

bigman - YES. could you trim this down and submit it? PLEASE? i havent upgraded to the newest yet but i couldn't live with this.

No problem, ill make it more in the bug report format and send it in. Beta 10 is not as useable for sample editing as prior versions due to this change as well as the "under construction" message you get when you press slice.

Also, I noticed in the authors notes for this release that the track 61-64 sample bug I submitted and wrote about earlier here is now a pending fix. Of all of the new features of os 3.0, I think that direct recording is the most powerful and underrated one. It will be great to have this working properly, since it can change the mpc from just a sampler/sequencer to that and a multitrack recorder (or a really easy to use phrase sampler).

bigman wrote:No problem, ill make it more in the bug report format and send it in. Beta 10 is not as useable for sample editing as prior versions due to this change as well as the "under construction" message you get when you press slice.

Also, I noticed in the authors notes for this release that the track 61-64 sample bug I submitted and wrote about earlier here is now a pending fix. Of all of the new features of os 3.0, I think that direct recording is the most powerful and underrated one. It will be great to have this working properly, since it can change the mpc from just a sampler/sequencer to that and a multitrack recorder (or a really easy to use phrase sampler).

yes i know there are dj's out there who wish the 1k could do that, for live set use.