v4.94

-------------------------------------------------
Bug Fixes & Addition: Ver4.94 26-Nov-2007
------------------------------------------------
1.[GROBAL PROGRAM EDIT]
The cursor position may be strange at MIDI-IN note.

2.[OTHER]
F4[PAD]
Curve:B <--- B
It does not turn on in a light touch.

3.[OTHER]
[F2[MISC.]
Tap tempo:TAP TEMPO Average:2 Note no.x <-Tap tempo MIDI-IN note number.
Tap tempo by MIDI-IN note is added.


http://www7a.biglobe.ne.jp/~mpc1000/

CommanderRobot wrote:-------------------------------------------------
Bug Fixes & Addition: Ver4.94 26-Nov-2007
------------------------------------------------
1.[GROBAL PROGRAM EDIT]
The cursor position may be strange at MIDI-IN note.

2.[OTHER]
F4[PAD]
Curve:B <--- B
It does not turn on in a light touch.

3.[OTHER]
[F2[MISC.]
Tap tempo:TAP TEMPO Average:2 Note no.x <-Tap tempo MIDI-IN note number.
Tap tempo by MIDI-IN note is added.


http://www7a.biglobe.ne.jp/~mpc1000/

heyhey - tap tempo from midi note in is clever, yeah, now any time im jammin with a live drummer or mental maxpatch, it can be in sync.....yep thats good.

ive a feeling there may be another update soon tho', cos theyre just right now investigating a possibly serious bug.

arebee wrote:

CommanderRobot wrote:-------------------------------------------------
Bug Fixes & Addition: Ver4.94 26-Nov-2007
------------------------------------------------
1.[GROBAL PROGRAM EDIT]
The cursor position may be strange at MIDI-IN note.

2.[OTHER]
F4[PAD]
Curve:B <--- B
It does not turn on in a light touch.

3.[OTHER]
[F2[MISC.]
Tap tempo:TAP TEMPO Average:2 Note no.x <-Tap tempo MIDI-IN note number.
Tap tempo by MIDI-IN note is added.


http://www7a.biglobe.ne.jp/~mpc1000/

heyhey - tap tempo from midi note in is clever, yeah, now any time im jammin with a live drummer or mental maxpatch, it can be in sync.....yep thats good.

ive a feeling there may be another update soon tho', cos theyre just right now investigating a possibly serious bug.

What bug is that? the midi bug?

hereo wrote:I've noticed that when I play chords on my midi piano (that triggers my sound modules) and record into my MPC as a sequencer, that within the first bar the MPC shortens my chords or single notes, or melodies.
I've noticed this a while back, but I couldn't think how to explain it. I might have to do a lil vid and post it cause I still don't think I'm explaining it well enough for you guys to understand. But if you do, please holla back. I need to send it to JJ, but maybe you can word it better.

Is this the midi bug you are referring to?

hereo wrote:

arebee wrote:

CommanderRobot wrote:-------------------------------------------------
Bug Fixes & Addition: Ver4.94 26-Nov-2007
------------------------------------------------
1.[GROBAL PROGRAM EDIT]
The cursor position may be strange at MIDI-IN note.

2.[OTHER]
F4[PAD]
Curve:B <--- B
It does not turn on in a light touch.

3.[OTHER]
[F2[MISC.]
Tap tempo:TAP TEMPO Average:2 Note no.x <-Tap tempo MIDI-IN note number.
Tap tempo by MIDI-IN note is added.


http://www7a.biglobe.ne.jp/~mpc1000/

heyhey - tap tempo from midi note in is clever, yeah, now any time im jammin with a live drummer or mental maxpatch, it can be in sync.....yep thats good.

ive a feeling there may be another update soon tho', cos theyre just right now investigating a possibly serious bug.

What bug is that? the midi bug?

oh. its not so bad as first expected, but involves qreal events that are the same being too close (2 ticks etc) - then if this stuff is in a track and the track is copied, the rest of ALL the sequence doesn't play from after that part....

i reported a bug the other day where i just copied a track off a 4bar seq to an 8 bar seq, (seq edit:copy) track13 > track13 / replace / 2 copies , and from the end of bar 4, the second half of the seq (bars 5 through 8 ) didnt play any events anymore - like they were erased! (they hadn't been erased - i could still see 'em in the event list)..... i tracked it down to 2 qreal events (cutoff+50) very close at 004:04:92 and :94... (ok in a 4bar loop) that somehow when copied and followed by another same qreal event (cutoff+50) at 005:01:00 (in an 8bar loop) caused the seq not to play anymore events in all tracks! from that point on.....not sure if that should be ok for the mpc or not, but all other events were fine - just these after they got copied went wrong, so i expect its a bug of sorts.

rinseout wrote:

hereo wrote:I've noticed that when I play chords on my midi piano (that triggers my sound modules) and record into my MPC as a sequencer, that within the first bar the MPC shortens my chords or single notes, or melodies.
I've noticed this a while back, but I couldn't think how to explain it. I might have to do a lil vid and post it cause I still don't think I'm explaining it well enough for you guys to understand. But if you do, please holla back. I need to send it to JJ, but maybe you can word it better.

Is this the midi bug you are referring to?

Yessir.

I got this problem only if the program of the module is selected on the main screen (mpc). Kinda switches the program and forgets the note length of the notes on 1:00:00. Maybe that helps.

rinseout wrote:I got this problem only if the program of the module is selected on the main screen (mpc). Kinda switches the program and forgets the note length of the notes on 1:00:00. Maybe that helps.

forgive me if im not following u here - but...

if u need program changes or set patch numbers, i find its way better to nest them into the start of a sequence track set up for playing the patch and then use "PC:seq:xx" in the main screen,

mainly 'cos i use say 4 separate outboard midi channels, and each has its own patch settings (all on a NordModG2 ch:1-4), yet i only needed them to trigger when THAT particular track was unmuted, if a track IS unmuted when i switch seq's the voice remains what it was/is, even if i've tweaked it with my midi controller, BUT if i had the patch (PC: xx) in the track settings (not - PC:seq:xx) then the patch would reset each time the seq looped.

the PC:seq:xx way is perfect for live too, because u get to control when a patch gets updated by unmuting that track only.

arebee wrote:... BUT if i had the patch (PC: xx) in the track settings (not - PC:seq:xx) then the patch would reset each time the seq looped.

Theres no p.c. event sent everytime the seq loops, only on "play start" or if you switch to the seq.

hereo wrote:

rinseout wrote:

hereo wrote:I've noticed that when I play chords on my midi piano (that triggers my sound modules) and record into my MPC as a sequencer, that within the first bar the MPC shortens my chords or single notes, or melodies.
I've noticed this a while back, but I couldn't think how to explain it. I might have to do a lil vid and post it cause I still don't think I'm explaining it well enough for you guys to understand. But if you do, please holla back. I need to send it to JJ, but maybe you can word it better.

Is this the midi bug you are referring to?

Yessir.

I have had that same problem as well and it is annoying as ****!

Nebulou5 wrote:

hereo wrote:

rinseout wrote:

hereo wrote:I've noticed that when I play chords on my midi piano (that triggers my sound modules) and record into my MPC as a sequencer, that within the first bar the MPC shortens my chords or single notes, or melodies.
I've noticed this a while back, but I couldn't think how to explain it. I might have to do a lil vid and post it cause I still don't think I'm explaining it well enough for you guys to understand. But if you do, please holla back. I need to send it to JJ, but maybe you can word it better.

Is this the midi bug you are referring to?

Yessir.

I have had that same problem as well and it is annoying as ****!

Me too, only have the problem when PLAY START is used. Its like it sends a reset or PC to the synth and reloads the patch.

One of us should type up the bug in very good detail and then email it to the rest of us and we'll send him the same email. That puts extra emphasis on the fact that many people are having this bug. He'll fix it then.

I thought this has been well documented. I think a bunch of folks have experienced this.

Yeah i have the same midi note cutoff problem too.I don't know if it is module specific or what but I get it real bad when sequencing my Orbit....
One thing that helps me a little is i turn up the release up on the patch in the modules envelope.It sustains the sound a bit to cover up some of the note drops but its not perfect...

juxstaman wrote:Yeah i have the same midi note cutoff problem too.I don't know if it is module specific or what but I get it real bad when sequencing my Orbit....
One thing that helps me a little is i turn up the release up on the patch in the modules envelope.It sustains the sound a bit to cover up some of the note drops but its not perfect...

I have the problem with my Korg R3. But it doesn't cutoff notes when I set the MPC to midi sync out as MASTER (either MIDI CLOCK or MTC). I have no idea why setting MPC to master stops the note cutoffs. Try it out and tell me if its the same behavior for you.