Beta 13 Bugs?

im stoked on this new version.. mainly the direct recording (tr 61-64)
any bugs for this genious to fix?

thanks, epc.

i got this message from the jj and co via Murahachibu

"Beta 13 was uploaded today but the slice function in slated to be included in the version after this. Also, in this coming version a feature will be added where by using AFTER + QLINK you will be able to select parameters, and numbers can be entered using the numeric keys and the pads. The next version is scheduled for release on the 8th or 9th.

Also, Antonym, in response to your comment "shift + data wheel no longer changes increments", this can be done in beta 10 using tap tempo and the data wheel."

apparently we still can't use the qlink to trim - but we can in fact change increments to trim with the data wheel using tap tempo instead of the data wheel. that'll take some getting used to but it's closer to the screen/finger anyway, so no complaints here.

i'm excited. will resume bug testing tonight - apparently a good number have been cleared up. could someone please go the .jp and copy what bugs have been fixed? my internet's being incredibly slow.

antonym :

Beta version number 13
---------------------------------------------------------------------------------------------------
Bug fixes:
---------------------------------------------------------------------------------------------------
1. [TRIM] page
Sequnce play & [EDIT] crash.
2. [TRIM] page
Can't select sample list after xxx.PRJ file Load.
3. [MAIN] page
Track61 cursor ON Fx and F3 [Tr -] hangs.
4. [MAIN] page
Track61-64 Recording with COUNT-IN.
exisit silence in beginnig sample.
---------------------------------------------------------------------------------------------------
New features/Changes:
---------------------------------------------------------------------------------------------------
1. [TRIM] page
SHIFT+CURSOR-L - > ZOOM OUT
SHIFT+CURSOR-R - > ZOOM IN
---------------------------------------------------------------------------------------------------
Under construction:
---------------------------------------------------------------------------------------------------
1. [TRIM] page F5 [SLICE]
---------------------------------------------------------------------------------------------------

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

A quick update on the bugs that were either fixed or carried over from beta 12. (the ones that were okay in 12 i'm not going to cover since they were fixed earlier)

1. L+R =>Mono bug- Fixed in beta 13

2. Directory Error when trying to save entire memory over previous project file- Still there in Beta 13

3. individual outputs not included in Propellant Actuated Device screen (Mode+Pad11)- Still there in Beta 13

4. Trim mode not being able to edit properly- This has been improved a lot in beta 13, you can now use shift+cursor <or> to zoom in or out as requested. Also the tap tempo+jog wheel makes you scan faster, but since trim is now calculated in samples it can't really select more or less incriments as an exact amount, since that changes depending on the level of zoom and length of your sample (but scanning faster with tap+wheel is fine for me).

5. Direct Record 61-64- This has not been fixed, but returned to the previous state it was at in beta 6 and before. This is where the Samples recorded on these tracks have an extra bit of time at the beginning. The last two or three versions had this little beginning bit plus the entire count in recorded, but now it's back to just the little bit. On the upside, you can correct this as you could in beta 6- (due to improvements in the trim screen in beta 13), but instead of using the 00.11.700 method since it doesn't read like that anymore, you must edit with your eyes by cutting out the silence before the signal. It's not as precise or easy as it should be, but now it's at least useable.

The other improvement I never noticed before, but was contested in the beta 12 post as missing (I don't know if it was there or not), is that when you press the window button in Load mode (Mode+Pad2) you now get the option of turning assignment of samples to the program on or off. Also, when this is turned on, the screen that shows what pads have which samples before you place your new one, which is very nice.

I am going to write JJ tonight about the Directory Error, Direct Record and Individual outs not being in (Mode+Pad11). If you have any suggestions on these, post them so I can edit these reports properly.

Also, what do you guys think of the new trim/loop mode since it has been and is still being improved? Is it better or worse workwise for you than the old Trim/loop Mode?

bigman wrote:Also, what do you guys think of the new trim/loop mode since it has been and is still being improved? Is it better or worse workwise for you than the old Trim/loop Mode?

its alright. i can work with it.. but the q link would be sweet

bigman wrote:Also, what do you guys think of the new trim/loop mode since it has been and is still being improved? Is it better or worse workwise for you than the old Trim/loop Mode?

I think it is much better and faster.

I just submitted the remaining bugs in beta 13 I knew about. If someone already submitted some of these for beta 13, sorry to be redundant. I just wanted to get them in on time, since the new beta comes out on the 8th or 9th. Here is a copy of how they were written up and submitted for reference.

I
1 power sources ON→ (unused) selecting the sequence
2 cursor to TR and select track 61-64
3 set recording preferences using the window button
4 record a take in time with metronome
5 press stop to stop recording
6 (bug) press play or play start to replay the newly recorded sample(take) and it is late.
This is still due to small bit of silence being added at the beginning of each recorded sample when using track 61-64.

I wrote reports for this bug before during Betas 6 and 12. Beta 6 and earlier had the same sync problems as it has now. Beta 12 tried to fix this, but had the count in as well as the extra bit in the beginning of the sample. This was again said to be fixed in Beta 13, but has the original bug from Beta 6 and earlier instead.

II.
1 power sources ON→ (unused) selecting the sequence
2 go to Load Mode (Mode+Pad2)
3 Select a folder with an existing Project File
4 Load Project File in folder
5 go to Save Mode (Mode+Pad3)
6 Scroll to "Save Entire Memory" and select original folder from which you loaded the project.
7 Press Save and leave Project name the same
8 Press Do It (F5)
9 When "File Exists!!!" prompt comes up, select Replac(F2)
(bug) you will get a message in center of screen that says "Directory Error!!!" and be returned to the save screen. I do not know if the project was replaced or not due to this error.

III
1 power sources ON→ (unused) selecting the sequence
2 go to (Mode+Pad11)
3 Scroll to "OUT" column
(bug) user cannot select individual outputs 1,2,3,4 here. Only St,12,34 pairs are shown
(bug) Individual outs 1,2,3,4 already set in Mixer (Mode+Pad8) are not labeled correctly in (Mode+Pad11) column "OUT".

IV
1 power sources ON→ (unused) selecting the sequence
2 go to Save mode (Mode+Pad3)
3 in menu "Save:", Scroll to "Entier Memory"
(bug) this is misspelled, should read "Entire Memory"

Keep hunting these bugs out and i'll try to do as much as I can to help.

bigman, you are doing a very great work

ok i did a bit of searching and i found the following bugs. Cyklops, i was unable to replicate your grid/step bug, i have completed a whole song using step edit heavily and i cannot say that i've had any problem with step edit or grid edit, yet.

meanwhile, here's a WEIRD TRIM BUG

1 - Load a phrase sample, like a break or w/e
2 - zoom in w/ F3 while trimming (great and fast selection)
3 - start your selection after something discernable (like a kick drum) so that everything but the first sound is selected
4 - zoom all the way out.
5 - the entire sample appears to be selected, rather than what you selected. note that the numbers in the upper right hand corner show that something IS in fact selected. note also that "PLAY TO" and "PLAY FROM" both play as they should. it's only the display that is showing incorrect data.
6 - Note that scrolling the data wheel left sends the start parameter directly to 0.

SAME OL' EMPTY TRIM CRASH

1 - boot your mpc with nothing loaded (no project, no samples)
2 - go directly to Trim. you crash with

CPU Address Error

PC(8847a544) SE(40001060) TEA(fcc95f00)
--------Stack Dump (sp=884ffed0)

883bfb80 00000000 00ffffff 00000100
ffffffff 0000008 7d527900 00000076
891ac73b 82082085 7e64af00 00000000



more later, hopefully.

I am beginning to think that some of these bugs might be different on one mpc1k to the next. For instance, on the track 61-64 bug I've been reporting, I keep getting conflicting messages from people (and the author's notes) saying that it does in fact work properly. Now after reading the post directly above this one from Nym, I cannot replicate either of the bugs he just listed on my Mpc with beta 13. Nor could I replicate the "same 'ol empty trim crash" on my machine with the earlier betas, although multiple people reported this problem with their machines.

So, if those reading could try to recreate some of these posted errors in beta 13+ on your machines and post the results, that might help sort this matter out.

Racking my brain, the only differences in all of our MPC1k's I could think of (other than casing) would be the ram, cf card, or harddrive. Ram I guess being a more logical cause, since the machine constantly uses it and there are many different manufacturer's Ram chips that people here have been using with the MPC1k. But that is just a guess.

i tend to not think it's an issue with ram - i think it's purely os. if anything, it may be that we're going about our mechanisms a different way.

bigman - when you go to trim after booting your machine empty, what do you see? it happens each and every time for me.

i'm gonna go try your direct recording bug again.

the quantize in beta 13 is still screwed up. if u set it to 1/32t it quantizes in 1/16t. if u set it to any other timing it corrects everything to 1/8. can anyone confirm this so i know that its not my machine. i reinstalled 2.10 and everything is peachy so it has to be the os, but nobody seems to have this problem

bigman wrote:I am beginning to think that some of these bugs might be different on one mpc1k to the next.

hum, sounds like the "blank screen" bug, which only some of us got after updating to os 2.10

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

strength wrote:the quantize in beta 13 is still screwed up. if u set it to 1/32t it quantizes in 1/16t. if u set it to any other timing it corrects everything to 1/8. can anyone confirm this so i know that its not my machine. i reinstalled 2.10 and everything is peachy so it has to be the os, but nobody seems to have this problem

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)