Submit bug reports and feature requests for the JJOS-XL and 2XL
User avatar

By Nebulou5 Tue Jan 08, 2008 3:58 am
JJOS1: Midi bug where if note is recorded at the start of a sequence the first time through it does not play the note.
By briancares Tue Jan 08, 2008 4:47 pm
OS 4.98


in trackmute window in play you can not jump between sequences
when there is a blank sequence between the sequences.

1- SEQ 1
2- SEQ 2
3- unused
4- SEQ 3

you can jump from SEQ1 to SEQ2
you can not jump from SEQ2 to SEQ3
User avatar
By arebee Tue Jan 08, 2008 4:52 pm
briancares wrote:OS 4.98


in trackmute window in play you can not jump between sequences
when there is a blank sequence between the sequences.

1- SEQ 1
2- SEQ 2
3- unused
4- SEQ 3

you can jump from SEQ1 to SEQ2
you can not jump from SEQ2 to SEQ3


i get it a bit different,

[with 'end of seq' selected] - i can move up through seq's with an unused in between the current and next selected, but can't move back down through them

[with immediate play or start] - it cannot move past unused seq's up or down.

By briancares Tue Jan 08, 2008 5:00 pm
"i get it a bit different, i can move up through seq's with an unused in between the current and next selected, but can't move back down through them"

its about positivity!
there´s only one direction: FORWARD! ;-)

seriously. yeah. could be that way.
just checked back to 4.96 to see if i missed an option.
also loaded older projects. 4.96 is ok.

DONT DELETE YOUR OLD OS UNTIL YOU ARE SURE THE NEW ONE WORKS FINE!
User avatar

By arebee Tue Jan 08, 2008 5:09 pm
briancares wrote:"i get it a bit different, i can move up through seq's with an unused in between the current and next selected, but can't move back down through them"

its about positivity!
there´s only one direction: FORWARD! ;-)

seriously. yeah. could be that way.
just checked back to 4.96 to see if i missed an option.
also loaded older projects. 4.96 is ok.

DONT DELETE YOUR OLD OS UNTIL YOU ARE SURE THE NEW ONE WORKS FINE!


but which os was the one with the newly added next seq options for the 3 (track mute/main/next seq] pages?

i suspect its at that update point where the code got buggered.

yoyo - i dont ever delete an os!, i keep an archive of each one, cos sometimes back one step is not enough.
User avatar

By Antonym Tue Jan 08, 2008 5:32 pm
.80 bugs, so far so good.

__________________________________________________

bug - it is impossible to edit/change MIDI NOTE in midi tracks

1 - load sample
2 - chop sample to NEW DRUM PGM
3 - enter GPE, f2 AMP, window over NOTE, select [35-98] note assign to straight.
4 - turn track to MIDI, record performance. preview performance.
5 - enter midi grid edit, navigate to a recorded note.
6 - hit f5, EDIT. change the recorded midi note (example: from 35b_0 to 43g-1)
7 - preview performance. NOTE: note is unchanged. Note appears to be changed, but triggers original pad.
8 - this happens in STEP EDIT also. enter step edit, attempt to change a note. preview performance - note: note is unchanged.

__________________________________________________

bug - cannot delete single item in midi grid edit/main screen grid edit.

1 - load program (example: one inst program)
2 - enter MIDI GRID EDIT or MAIN screen
3 - record 3 notes on 1.01.00 (example: a chord)
4 - attempt to delete lowest note in chord.
5 - BUG: all 3 recorded notes at 1.01.00 are deleted. it is impossible to delete 1 note only.
6 - NOTE: hit UNDO or record new notes on 1.01.00. enter 6 or 16 pad grid edit
7 - NOTE: attempt to delete lowest note in chord.
8 - NOTE: in 16/6 pad grid edit, it is possible to delete 1 note only.

By briancares Tue Jan 08, 2008 11:58 pm
but which os was the one with the newly added next seq options for the 3 (track mute/main/next seq] pages?

i suspect its at that update point where the code got buggered.

its 4.97 or 4.97b.

i did not update that one when i read about the next seq option problem.
when i tried it in 4.96 the result of next seq immediately seemed
to be way more tight as now in 4.98 (as a result of my wobbly timing probably :)
now in 4.98 it sounds weird.. i did not manage to create these fast & tight
headbanging seq. changes in the middle of a bar.

4.96 is ok for me atm. but i am looking forward to receive my os 2 pass
anyway. so i can work on both os and choose the best solution for my needs.
User avatar

By arebee Wed Jan 09, 2008 12:06 am
briancares wrote:but which os was the one with the newly added next seq options for the 3 (track mute/main/next seq] pages?

i suspect its at that update point where the code got buggered.

its 4.97 or 4.97b.

i did not update that one when i read about the next seq option problem.
when i tried it in 4.96 the result of next seq immediately seemed
to be way more tight as now in 4.98 (as a result of my wobbly timing probably :)
now in 4.98 it sounds weird.. i did not manage to create these fast & tight
headbanging seq. changes in the middle of a bar.

4.96 is ok for me atm. but i am looking forward to receive my os 2 pass
anyway. so i can work on both os and choose the best solution for my needs.


i cant imagine it should be any different in behavior, the 'immediate start' is the mental headbanger i think - any quick flicks through seq's with the right data in them sounds awesome.....has allways been fun to spin this one in a 'free death jazz implosion' set,

but i mostly use 'end of..' to be on beat exactly seq to seq in a song arrangement way,

but my favorite "havanna cigar" = 'special occasions only' one is 'immediate play' that does change anywhere in a sequence, and the next sequence is in the same place where switched....super deluxe!

but if u r sure theres a difference in the behavior between os's for the same function - let me know for sure cos it should be put right, to whichever is better i guess

By briancares Wed Jan 09, 2008 12:18 am
i think i got i now.
my "mental banger" is the immediate play, as you stay exactly within
your bar measuring and not jump to the beginning of the next seq.
which sounds strange to me.

with immmediate play you just can flip in the piano line shortly on a dry beat and will always stay in the right position.

so immediate start might have caused that strange behaviour i mentioned.
my fault. anyways i have to get back and wait for the next update as the trackmute bug is unacceptable to me and my needs.
User avatar

By arebee Wed Jan 09, 2008 12:25 am
briancares wrote:i think i got i now.
my "mental banger" is the immediate play, as you stay exactly within
your bar measuring and not jump to the beginning of the next seq.
which sounds strange to me.

with immmediate play you just can flip in the piano line shortly on a dry beat and will always stay in the right position.

so immediate start might have caused that strange behaviour i mentioned.
my fault. anyways i have to get back and wait for the next update as the trackmute bug is unacceptable to me and my needs.


right now i guess u could work around by re ordering your seq's into the required order and go forwards! hahah

or, just create one blank (no events, just a new name will 'create' a blank seq) for every old unused seq...... and u could then go through them no?

By briancares Wed Jan 09, 2008 12:41 am
right now i guess u could work around by re ordering your seq's into the required order and go forwards! hahah

you mean this thing... ahh. wait. aaa ARRANGING!
nope. i do not arrange atm. just like to flip around and track the flips.
and for live its cool to get back to a previously played part sometimes.

or, just create one blank (no events, just a new name will 'create' a blank seq) for every old unused seq...... and u could then go through them no?[/quote]

but in the heat of the night i might end up on a blank sequence.
and then i had to explain: "yeah you know i´m sorry. but there is this new
operating system for my mpc. you know what a mpc is..? don´t you?
ok let me explain... "

that´d be actually a nice feature for a live show.
like a comedy interlude..
User avatar

By arebee Wed Jan 09, 2008 12:46 am
briancares wrote:right now i guess u could work around by re ordering your seq's into the required order and go forwards! hahah

you mean this thing... ahh. wait. aaa ARRANGING!
nope. i do not arrange atm. just like to flip around and track the flips.
and for live its cool to get back to a previously played part sometimes.

or, just create one blank (no events, just a new name will 'create' a blank seq) for every old unused seq...... and u could then go through them no?


but in the heat of the night i might end up on a blank sequence.
and then i had to explain: "yeah you know i´m sorry. but there is this new
operating system for my mpc. you know what a mpc is..? don´t you?
ok let me explain... "

that´d be actually a nice feature for a live show.
like a comedy interlude..[/quote]

well there u go - i bet you didnt expect to find a whole new creative avenue here! you'll be famous as the guy who makes excuses in intervals of tracks for a living!, hheheh

but what i meant by arranging, was that you could put all your used sequences next to each other - no unused ones nearby. all the used ones at say #1------64, then unused from 64-------99. etc? no good?
User avatar

By kuniklo Thu Jan 10, 2008 3:50 am
0.80

Nothing comes up in my autoload.

When I do manually load the autoload or any other project, all tracks come up with PGM: OFF. Nothing plays when I hit start.

Switching to the track mute screen and then back to main, the programs are visible and play properly.
User avatar

By kuniklo Fri Jan 11, 2008 8:52 pm
0.80

Crash when playing midi notes through the MPC to an external sound module. When playing my Virus through a track on the MPC via an external keyboard I get consistent crashes. Sometimes it takes a while for it to happen but it's happened three times now.

This is the error message:

Illegal general instruction exception
PC(a5007164) SR(40000106b) TEA(00000000)
....
User avatar

By Antonym Mon Jan 14, 2008 7:19 pm
kuniklo - always try to grab all the numbers and submit them to jj. those are helpful in solving the bugs. getting a crash screen like that sucks, but at the same time it's really good because if you submit that data, chances are almost positive that it'll be fixed in the next version. in my experience at least.