JJ OS Bug Reports (ARCHIVE)

here is a bug which exists for a long time, pre jj.

SEQ EDIT COPY TRACK bug

1 - load project.
2 - in MAIN screen, move cursor to used, named TRACK
3 - hit WINDOW
4 - hit COPY
5 - COPY to unused TRACK
NOTE: NAME and PROGRAM are transferred. MIDI OUT and MIDI/DRUM is transferred too.
6 - enter SEQ EDIT.
7 - copy used, named TRACK to a track on another sequence.
BUG: NAME and PROGRAM, MIDI OUT and MIDI/DRUM is not transferred. Details must be manually entered before/after copy.

summary: inconsistent copying behavior between COPY in MAIN SCREEN and COPY in SEQ EDIT.

who still reports bugs? meaning in the last two weeks.

I got one. Its a midi bug but I'm not quite sure how to word it to JJ. And I gotta try to recreate it. Well, I got 2 if you count the Note Repeat bug.

bugs are kind of endangered these days.

ok,
1:
i have a external midi synth playing into the MPC audio inputs with 'input thru'=ON,Analog, Mode=ST,Level=100,OUT=ST, with the MPC triggering its midi from a sequence01 - playing/looping....

2:
i set up a couple of fx, delay#1, reverb#2, compressor on the main fx.

3:
then i set the (input thru) out to FX=1, [oddly enough many of these type of parameters are locked if the seq is running, but not this fx param]....

so, last nite i was messing around with this - sending to either 1 or 2 fx bus here, and all was fine, but after a while, (or as in this mornings case - straight away), it freezes the mpc up, although the sequencers still running and the thru's still active plus FX, but no buttons work, i cant stop the mpc.....only the pad ABCD buttons lite up if pressed.

at least i go tto record the results on my daw, before i switched it off, but i lost brand new (and unsaved! :0) material....and it happened again to day.

oh yeah, os 487, but hasnt happened all day since i posted, hah , typical.

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.

how are things looking on the pan-bug??

if i have '16levels' on (eg: velocity)
slider 1 or 2 :note on: decay, tune, doesnt work.

is this a bug or an undesired operation with no work around?
JJ ta.

rB)

arebee wrote:if i have '16levels' on (eg: velocity)
slider 1 or 2 :note on: decay, tune, doesnt work.

confirmed.

report it to JJ.

in a similar vein,

1: normally - when i start a sequence, the qlink sliders' current values are overridden by any data thats in the sequence - cool, cos i want any qlink data in the sequence to be the dominant data.

2: of course pressing the 'after' buttons is intended to then override any qlink data in the sequence right? it ONLY works if u press the 'after' button after the sequence has already started - ie:when u start a sequence and have the 'after' buttons active before u started, they DONT override the qlink data in the sequence. that seems wrong.

ALSO 3: if i have the faders off zero (ie not in the reset position) and press either 'after 1' or 'after 2' buttons, the qlink slider of BOTH sliders gets used, not just the 'after' button i pressed. whats going on? i know this has been like this for sometime, but its really vugging me off now.

CAN WE HAVE A FIX? JJ

occurs only when both sequence and simult sequences use the same program:

when used in a simult seq, any samples that are 'oneshot' (play mode) & 'mono' (voice mode) - the sample does not behave as normal......so a note played does not cut off previous note. (and plays like its 'poly')

and

when used in a simult seq, any samples that are 'note on' (play mode) & 'mono' (voice mode) - the sample does not behave as normal.....so a note played is at minimum decay (as if chopped off by note on at each same events)

this is difficult to explain, but it appears to have something to do with the active tracks in both sequence & simult sequence, when tracks are muted the same in each seq & simult seq. (eg: when tracks# in seq, and the same tracks# in simult sequence are active = the active tracks' events in the main seq cuts off events in the active track in the simult seq........and if the track# is muted in the main seq = the same track# in simult seq goes from 'mono' to 'poly' )

i hope u can unravel this description,let me know if this gets u too...
rB)

bit of a weird one this.

just recorded a bass line. played it back and it plays the bass line back at a lower pitch. it's very slight, but definitely there. if i play along with the sequence, i can distinctly hear the difference.

anyone else had this?

Mr modnaR wrote:bit of a weird one this.

just recorded a bass line. played it back and it plays the bass line back at a lower pitch. it's very slight, but definitely there. if i play along with the sequence, i can distinctly hear the difference.

anyone else had this?

Have this sometimes cos my keyboards pitchbend is kinda messed up.

rinseout wrote:

Mr modnaR wrote:bit of a weird one this.

just recorded a bass line. played it back and it plays the bass line back at a lower pitch. it's very slight, but definitely there. if i play along with the sequence, i can distinctly hear the difference.

anyone else had this?

Have this sometimes cos my keyboards pitchbend is kinda messed up.

i recorded this on the pads. mpc only.