JJ OS Bug Reports (ARCHIVE)

That's good to hear. Thanks for all you efforts. I'm looking forward to working more with this feature when the new version is out.

distortedtekno wrote:That's good to hear. Thanks for all you efforts. I'm looking forward to working more with this feature when the new version is out.

JJ said:
I'm sorry.
Although correction of this bug was tried, since a noise arises in a knot, it is uncorrectable

hello
I want you to know (users interested) this anomaly to those who still do not know this error (bug), and the response gives JJ.
http://emepece.mundoforo.com/image-vp6913.html#6913

The bug was checked.
However, correction of this bug is not easy.
Time is required or correction may be difficulty.

Thank you.

He didn't say it was uncorrectable no?

warning OS2 User



fatal bug!!

http://www.youtube.com/watch?v=oVbcMyTR35w

FROZEN

Freaky bug

le rat wrote:

The bug was checked.
However, correction of this bug is not easy.
Time is required or correction may be difficulty.

Thank you.

He didn't say it was uncorrectable no?

when I was a child in school,
taught me and I'll always remember:



+ X + = +
- X - = +
and
+ X - = -

do the math.

strange bug. i'd try it for fun, but i'm running os2xl and don't feel like re-adjusting all my parameters again.
thanks for sharing.

Jandpoint wrote:

fatal bug!!

http://www.youtube.com/watch?v=oVbcMyTR35w

JJ said:

This bug was corrected by Ver1.26.
Please download Ver1.26.

Thank you.
____________________

but ...
my question is:
correction has been made from which version?
I imagine that the last (1.25).

long before I test the 1.26 update ....

I fear that this correction has been implemented, and on the other side also has re-cut / removed other features, which usually does JJ.
I know I have a problem (or perhaps I certainly have many!), is that for example, I had been using 1.22, for me, is and was, the most stable, having tested 1.23, 1.24 and 1.25 with bigger problems than with 1.22. (Also I have tested all updates xl )

then I will not have the direct benefit of this version / update, (I was, who reported this bug!!!!)
JJ should correct all the updates,
I have a understanding that each user chooses which handles update best for your workflow.
is not it?

Of course, I appreciate the attention and effort that makes JJ, but the benefit is for future users .
thanks for your speed >>>>>>>>> JJ !!!!

_________________________________________________________

OS-XL Ver1.47 is a schedule of upload in December:

we have between 9 and 40 days to see it!
especially, if it contains some bugs...

if, free of payment!!! see it!!


Greetings....

When I load a project saved as "save entire memory" it doesn't load the audio files in audio tracks even tho this audio tracks are stored in the folder where I saved the entire memory. I´m using the latest update 1.46

Another issue:

My sample loops is getting a gap in the transition from one sequence to another (in song mode) with the sample in the audio track. Even when I convert a song to a sequence, the loop get´s cut very slightly but very audible between one bar that was a sequence to another bar that was another sequence. When I loop the sequence itself (the original sequence, not converted from song to sequence) it loops perfectly.

The gap appears in song mode even when I solo the drums, between one sequence to another. When I convert the song to a sequence, the drum track transition are smooth, but the audio track still don´t loop right.

I
when looping pads with the "pad bank" + PAD method the volume changes dont take effect,
the volume only changes when the pad ist triggered again.

this makes it hard to adjust the volume while looping.

to avoid a crash in jjos2xl 1.45 (1000) and 1.46 (2500),
avoid doing this:

1- creating a midi track, then
2- setting qlink REALTIME TUNE, then
3- recording a performance, then
4- entering STEP EDIT and finally
5- changing a value (velocity, for example).

this causes a crash.

crothers wrote:to avoid a crash in jjos2xl 1.45 (1000) and 1.46 (2500),
avoid doing this:

1- creating a midi track, then
2- setting qlink REALTIME TUNE, then
3- recording a performance, then
4- entering STEP EDIT and finally
5- changing a value (velocity, for example).

this causes a crash.

honestly, i've had my 2500 freeze and crash running 0s2xl1.44 and 1.45. haven't even used 1.46 yet as i switched back to 1.43, which runs fine. All crashes have been within hours or a day of using a particular os, and, it seems to have somrthing to do with q'link settings.

anyone else have this happen?

try it now. i'm not gonna lie, that bug was fcking HARD to track down.
load up the newest business and give it a whirl on something unimportant.
in os 1.45, this was the only crash i could find (i don't use pattern mode, so no comment there)
and otherwise, aside from another hard-to-pin-down lagging cursor bug in midi grid edit, 1.45 was pretty clean.
but yeah this above bug did **** me up twice.