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

By the_raider Thu Dec 27, 2007 10:41 pm
in jj os2. in grid edit when you try to overdub something. the notes are not recorded. this also happens with record and overdub with playstart.
User avatar

By Antonym Fri Dec 28, 2007 5:19 am
yup that's a one liner

16 pad grid edit: BUG: notes are not recorded.

1 - load project
2 - record performance in 16 grid
3 - BUG: performed notes are not recorded.
User avatar

By the_raider Fri Dec 28, 2007 7:41 am
if on the main screen in os2. hit main again takes you to grid edit. i don't know if this is supposed to be like this but, i doubt it.
User avatar

By Antonym Fri Dec 28, 2007 5:08 pm
yeah main in main takes you to grid edit. just a shortcut.
User avatar

By the_raider Fri Dec 28, 2007 5:19 pm
well i guess its a short cut but when the grid edit doesn't function really unless he fixed that in the transition from .71 to .72 i am not really using it except to delete large pharses.
User avatar

By Antonym Fri Dec 28, 2007 5:26 pm
haha yeah. remember, since os2 is really in the middle of development there are gonna be these issues. you're right, as of now it's a shortcut to a bug, kind of a bridge to nowhere. but in the future it will be a nice shortcut.
User avatar

By the_raider Fri Dec 28, 2007 5:28 pm
yeah most definitely, i wish there was a short cut to the intrument program screen thing. i think that is called GPE. cause literally i am putting all my sounds through that now.
User avatar

By Antonym Fri Dec 28, 2007 5:48 pm
yeah, GPE is accessed via mode/pad 7 or 11 right now
but this might come close for single pad program edits: NPE, new program edit, is accessed from the main screen with a press of the MODE button if you position your cursor above the program name in the main screen.

this is great for INST programs, since they operate on more of a "1 param fits all pads" type of deal. for drum programs, it's a little more limited than gpe (kind of like what OPM was for os1, a quick and easy way to edit 1 pad rather than edit them all in bulk)

man, have you checked out the layer 1-2 crossfade function yet?????? it's amazing...i have never seen anything like it before.
User avatar

By the_raider Fri Dec 28, 2007 5:55 pm
dude i'm not gonna lie i got to study up on this cause i'm quite confused by what you just said. And yeah i read about the layer cross fade. i was thinking you could make like a flam sound with two snares or a snare and a bass. i have thought about a lot of this stuff but i haven't applied it yet to my work.
User avatar

By the_raider Fri Dec 28, 2007 5:58 pm
new one: when doing 16 pads, when hitting the pad to decide which pad is used it doesn't play the sound assigned to that pad. once in 16 pads mode everything is ok, just the set up screen doesn't function properly. if that made sense. :D
User avatar

By the_raider Sat Dec 29, 2007 8:24 pm
OS2: I had a beat that was sequenced out, not a loop and i had one bar in the middle of 7/8 time signature which then went back to 4/4. This through the click track off and then played this weird like double pattern that wasn't anything like it should be playing. Hope that made sense.

By Seasinz Sun Dec 30, 2007 2:11 am
OS2 0.72.

here's something I just found thats kind of annoying while chopping.

1. load sample
2. enter TRIM mode with CHOP=ON
3. max zoom, horizontal and vertical.
4. adjust end point
5. BUG - waveform redraws when selecting end point and nearly becomes a new waveform.
6. move endpoint backwards and waveform changes back to original.

edit... seems this only happens on a couple of the samples I have, most seem to work alright.
User avatar

By Antonym Tue Jan 01, 2008 2:48 am
seasinz, i was unable to reproduce that one.
briancares, in .72, it appears that that one is solved.

By Seasinz Tue Jan 01, 2008 8:36 pm
yah it only pops up on every once in awhile for me, it must be an issue with the samples themselves.
its weird that it happens on some and not others because they're all ripped the same way.
User avatar
By arebee Wed Jan 02, 2008 11:52 am
happy nuyear to y'all

> FX clicks in master eq when "auto load fx" event used

ive been using fx#load commands inserted into the event list in sequences to get each sequence to have its own discreet set of fx, but when the seq's are looped (fx not being changed), the fx# 'load' causes a click at each 'load' event, even while the fx hasnt changed any params, and in a sense should be identical.

ive traced it to be the master 'eq' block, only when the master eq is 'off' or when all the values are set to +00 (ie: no eq gains) the clicks stop happening.

i know this might not be a priority to some users, but i was thinking, that in theory if the fx is re-loading the same eq each seq loop, then no clicks should occur.....but i know with digital gear sometimes there can be tiny dropouts when params get deleted to rewrite even the same values...
anyone got a view/solution.....i might still chase jj about it tho'

rB)