beta 16 bugs - please copy old

These two bugs I posted and wrote to JJ about from beta15 still remain:

I
The Track 61-64 bug only exists using the analog or digital inputs. This problem does not happen using Main Out.

Example

1 power sources ON→ (unused) selecting the sequence
2 cursor to TR and select track 61-64
3 set recording preferences (to analog or digital, stereo or mono l/r input) using the window button
4 record a take (counting into microphone 1,2,3,4,5,6,7,8)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.

look in the Trim Mode (Mode+Pad6) to see the sample has extra time recorded to the Left and(or) Right side. You can see exactly how much when zooming in to the first peak, because the beginning is dead silence (no signal).


II
Different track 61-64 bug

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
5 press stop to stop recording
6 go to song mode (Mode+Pad16)
7 in Song Mode, cursor to Sequence and select sequence(s) that have direct record takes on them
8 (bug) all tracks EXCEPT tracks 61-64 will play back while in Song Mode

I have been messing with direct record for a while since writing these and I am starting to think that the direct record tracks are not supposed to show up in song mode. What is giving me this notion is how the direct record tracks behave with sequences.

For instance, say that you have a two bar drum loop that you want to direct record some lyrics over. You can go to track 61 and use overdub+rec and do your thing for as long as you want, since the loop keeps going in the background. When you press stop, the MPC asks if you would like change the amount of bars to match the length of the new recording. If you choose "yes" the amount of bars in the sequence are greater but the drum loop only plays for the first two bars.

At this point in beta16, bug (I) which is listed above comes into play. This is where to make the track sync you must cut a bit of time off of the front of your new sample "Take x". You can see exactly where to trim to, because the extra time consists of dead silence before any signal comes in.

Once that is done, your new sample "Take x" is in sync, but your drums still only play for two bars. To make them work, first cursor to bars on the main screen and set this to 2, when you are prompted say yes. Then go to seq edit (mode+bad13) and tab to bars (F2). Select the last bar as 2 and the amount of copies to equally suit the length of whatever your Direct record sample (take x) was.

Notice the length is where it was when the take was recorded. Now when you play back the drums play through the whole sequence and the Direct record take plays all the way through. This because the direct record takes do NOT get changed with any sequence editing. They just play at 1.00.000 and start again if loop is on whenever the time hits 1.00.000.

This is what leads me to beleive that the direct record tracks are not supposed to show up in song mode. As it might be meant for linking sequences into a song and then transferring back to a long sequence so the direct record tracks can play over all of your changes. You can also then go into the sequence and edit breaks, program changes, etc. throughout the song.

If you do want these tracks to loop with the sequence wherever you edit. Reassign the take to a program/pad with note on. Add an event in step edit at 1.00.000 to trigger the take and change decay (D:) to 9999. Now your direct record track will be freed up, your take will start whenever triggered (and stop abruptly when sequence stops), also you can use filters@lfo's, chop, etc..

I have not had time to read all the new bugs on here in detail, but good job to everyone finding them.

One more new bug before I go.

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
5 press stop to stop recording
6 playback track
(bug)while playing back press (mode+trim) and sequence goes temporarily out of whack.
(bug)while playing back in Trim mode, press (Main) and Direct record tracks stop playing until 1.00.000 repeats.

bigman wrote:These two bugs I posted and wrote to JJ about from beta15 still remain

yep, the JJ stated that these bugs were pending (= he is working on it).
check here: http://www7a.biglobe.ne.jp/~mpc1000/bug.htm

and by the way, i submitted to the JJ the bugs i found. hopefully they were concise enough to be understandable in english.

Here is how it was stated on the report:

------------------------------------------------------------------------------------------
Pending Bugs:
------------------------------------------------------------------------------------------
Direct recoding(tr61-64)
1. [PLAY] or [START]
and
[REC]or[DUB]+ [START] or[PLAY]
this case not record.

2. [SEQ EDIT] [GRID] etc.
　track61-64 problem

These are actually two seperate direct record problems from my submissions, which I didn't know about until I read the notes again and tried 'em out.


1. Occurs when the sequence is playing and you hit rec/overdub+play/playstart to record on the fly. The screen pops up that shows a take recording, but when you stop it says "?take x" in (Tr:)where your new take should be and the new sample is also not in the sample list.

2. Refers to someone elses problem that is in the same realm as the Song mode problem. I talked about why I think this might be intentional in my earlier post, because the direct record tracks are not linked to the sequence, which would make things like grid, step and seq edit not effect them. Instead, the direct record tracks 61-64 work independently, which means that they only re-start at 1.00.000 and play straight through to the end.


I don't know if he is still working on the added pre-silence bug (I) or not. In beta15's notes, he did a test of the main out recording the click and it played back correctly. I tried this too and it worked perfectly on main out. The problem is with the digital and analog in's, you still get the added pre-silence. I might re-sub (pre-silence on analog/digital in's), along with the new one (going in/out of trim mode wabbles/stops 61-64 playback) for beta 16 so he doesn't forget.

Menthal wrote:The trim sample bug L+R--->>to mono is still there...
when u convert a sample to mono and you try to turn the data wheel t show another sample, it crashes...

confirmed.

MODE > TRIM
Convert stereo to mono
back to TRIM > select another sample = CPU crash

anyone else having trouble with triple-quantisized recordings? every time i record with 32 (3), 16 (3) or 8 (3) quanti, some of the notes i play are recorded correctly, but some move to the very start of the sequence.
ie. if i record 4 bars, i have some notes correctly recorded and 10 or more samples playing altogether at 1.00.00. i have to record it manually in step edit then... this sucks!

YES

just had that problem yesterday, commander. triple recording bug confirmed. it was driving me crazy.

Ok so I finally had some time to install OS 3.0 today. And every time I load the "trim" menu, it crashes and gives me the same message:
CPU Address Error with a whole bunch of numbers.

I downloaded the file again and reinstalled it 3 times. Same thing every time. Has this happend to anyone else?

nope, not me. trim mode works fine.

Here are a few more problems I have found with direct recording in beta16.

When you are re-taking (deleting and redoing takes), some of the time the new take is not recorded and a "?Take x" is shown in the Tr: field. I believe it is random, since I use the same method every time and record only while in the Main screen.

Also when recording using overdub+record, the rest of the sequenced tracks mess up at 1.00.000 to about 1.02.000. This might be another part of the same old added start time bug. This does not happen when it loops 1.00.000, but only when the sequence starts recording.

after several hours of use yesterday my mpc shifted recorded sequences just after recording them: in a 4 bar sequence, the sequence data for the first bar was in the 3rd bar and vice versa. anyone else had that?

Doppelhorst, i've never gotten that but it sounds frustrating. If you can recreate it, then please write down the steps to be submitted to JJ.

As for the trim screen crashing bug, are some of you getting crashes after samples are loaded, or just when the sample list is blank? If you are getting the crash when samples are loaded then it is a new bug and should be written up.

(this excludes the l+r=Mono bug, since that has already been confirmed)


Nym, are you or anyone else keeping track of the new and existing bugs in beta16 listed in this thread that have, or have not been officially bug reported to JJ? If not, I think it would be nice to have an ongoing list of bugs found here that have their status (new, existing, confirmed, fixed, etc..) next to them. I know the author has an updated list like this with every release, but it isn't in clear english and doesn't cover everything we find on here.

bigman,
strange, but i could not recreate it today (maybe i didn´t leave it on for long enough???).

this has probly been mentioned before but i didnt find anything about it
so when i grab a sample and just wanna chop it 8 times when i press to chop it chops up 62 times nomatter how man times i wanna chop i tried diff numbers and same **** anybody else with this bug

sorry for bad english

joeybells wrote:I think when you hit MODE 11 it should go staight to the program that you had selected in the MAIN screen.. rather than pressing F1 and having to scroll thru every time...anybody?

This does seem like a bug, but i dunno

of course

the new o.s is dope but its some things abuot it that im not really feelin like for example

loading up prgrams..its sayin file not found...that shyt is drivin me up the wall