4.83

Bug fixes

-------------------------------------------------------
Bug fixes & Addition & Delete: New OS Ver4.83 29-Aug-2007
-------------------------------------------------------
1. [MAIN]
??[Simult sequence]
??Example:
??Sq: Sequence1<- 10bars (Audio track used)
??SS: Sequence2<- 2bars (LOOP ON)
??The sound of the audio track of MAIN stops in the end of simult sequence.

2. [MAIN]
??When the START point of a stereo sample is not 0,
??the sound by the side of R is strange.

3. [GRID]
??[Duration: AS PLAYED]
??It does not work in 16PAD screen.

4. [TEMPO]
??[Q-link - > tempo change.]
??Resolution is rude when a range is narrow.

5. [Q-LINK]
??[NOTE ON]
??Q-Link - > Sample End
??The sample of Loop ON is strange.

6. [LOAD]
??A short sample is not one shot play when the PLAY/START button performs audition.

7. [NEXT SEQ]
??[IMMEDITALY PLAY]
??When a sequence changes and the sample of “PLAY MODE=NOTE ON” breaks OFF.

8. [GRID]
??-----------------------------------------------------------------
??[OTHER] page
??F2 [MISC.]
??Mute/stop of one-shot sample: IMMEDIATE<-- <<<< IMMEDIATE >>>>
-------------------------------------------------------------------
??At the time of this setup STEP SOUND is not muted.

< Addition >
1. [Record setups Window] (Audio track window)
??Monitor: ON/OFF

< Delete >
?The following functions were deleted in order to secure OS memory for bug correction.
?
1. [PROGRAM]
??[PARAMS]
??F6 [EDIT] <--- <<<< Delete >>>>
??The same function as this It is in [TRIM] - >F6 [EDIT].

----------------------------------------------------------------------------------

Just reported a bug today and he fixed it! Thats darn good service!

2. [MAIN]
??When the START point of a stereo sample is not 0,
??the sound by the side of R is strange.

I never had this problem, but then again, i'm still on 4.75.. Maybe it's time for an update.

lag time is GONE! thank god. no more pauses on boot or switching between modes!!! that shit was getting on my nerves so bad. my normal work flow is back. maybe i got lost in translation but i didn't see this in his list of fixes and such.

edit:

Q: If recording a sequence and you trigger a sample that is longer than the sequence itself, the sample will be muted when the sequence 　　　loops back to 001.01.00
　　 For instance:
　1. 4 bar sequence
　2. Trigger a loop at 004.04.48
　3. Sample gets muted before it can finish playing

"Immediate" is getting useless for me, as it now stops samples at the end of the loop and even mutes sample-mute-groups if they're on a different track and the track is muted. too much muting! i can't even play a nice beat on the pads because everytime it loops and i push the first kick a little bit to early, it gets muted, too, leaving only a nasty click-sound. why did he hanged that, everything was fine before.


Q: 1. in program mode, go to mute/simult pad
　 2. push the pad you want to mute/simult (ie: a03)
　 3. now switch to a different bank (ie: b)
　bug: the selected pad changes from bank a to bank b (ie: a03 to b03).

A: It is not a bug but specification.

i don't understand the benefit of this either... now i have to use the jogwheel to scoll to the pad i want to simult/mute if its on an other bank instead of just pushing it.

looks like i spoke to soon. i can only avoid the lag time by powering on with a cf in the drive. still get the pauses when moving to/from the load/save screen while using the hdd.

Sounds like your HDD is taking a while to spin up.

Balls wrote:

2. [MAIN]
??When the START point of a stereo sample is not 0,
??the sound by the side of R is strange.

I never had this problem, but then again, i'm still on 4.75.. Maybe it's time for an update.

perharps it is the random pan bug

Wow, thats a big changelog right there! Some thing I don't understand, but it'll probably all be cool if I check them out on the working machine.

mkl... wrote:

Balls wrote:

2. [MAIN]
??When the START point of a stereo sample is not 0,
??the sound by the side of R is strange.

I never had this problem, but then again, i'm still on 4.75.. Maybe it's time for an update.

perharps it is the random pan bug

I think so

OMFG The lag time is gone!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!



Except when I am moving from mode - load to the main screen when I am accessing the HDD, that must have to do with the hard drive spinning.


Just when I had lost faith in JJ, he came back and proved me wrong. Best 30 bucks I ever spent. better than that questionable hooker in Tijuana at least...

< Delete >
?The following functions were deleted in order to secure OS memory for bug correction.
?
1. [PROGRAM]
??[PARAMS]
??F6 [EDIT] <--- <<<< Delete >>>>
??The same function as this It is in [TRIM] - >F6 [EDIT].

redundancy is deleted.

a parody:

< Delete >
the following function can be deleted in order to secure OS memory for further jenius:

1 - Mode+pad 07: [PROGRAM]

??The same function as this It is in [Global Program Edit]

folks here's something interesting:

4.82 = 896KB
4.83 = 892KB

by just thinning out that delete function in OPE, the programmer freed up 4 kb of code - and that's AFTER the addition and many bug fixes in 4.83.

i imagine how much code is currently occupied by OPM.

remember that bit convert and ring mod both were inserted into the os when it was about 894 kb. that's a lot of power in just a couple kb of space...

salute! down with redundancy, up with jenius!!!

random panning bug still here.

Antonym wrote:folks here's something interesting:

4.82 = 896KB
4.83 = 892KB

by just thinning out that delete function in OPE, the programmer freed up 4 kb of code - and that's AFTER the addition and many bug fixes in 4.83.

i imagine how much code is currently occupied by OPM.

remember that bit convert and ring mod both were inserted into the os when it was about 894 kb. that's a lot of power in just a couple kb of space...

salute! down with redundancy, up with jenius!!!

What about being able to layer sounds in old program mode? Would you just have to trigger multiple pads at once then?

CommanderRobot wrote:Q: If recording a sequence and you trigger a sample that is longer than the sequence itself, the sample will be muted when the sequence 　　　loops back to 001.01.00
　　 For instance:
　1. 4 bar sequence
　2. Trigger a loop at 004.04.48
　3. Sample gets muted before it can finish playing

"Immediate" is getting useless for me, as it now stops samples at the end of the loop and even mutes sample-mute-groups if they're on a different track and the track is muted. too much muting! i can't even play a nice beat on the pads because everytime it loops and i push the first kick a little bit to early, it gets muted, too, leaving only a nasty click-sound. why did he hanged that, everything was fine before.


Q: 1. in program mode, go to mute/simult pad
　 2. push the pad you want to mute/simult (ie: a03)
　 3. now switch to a different bank (ie: b)
　bug: the selected pad changes from bank a to bank b (ie: a03 to b03).

A: It is not a bug but specification.

i don't understand the benefit of this either... now i have to use the jogwheel to scoll to the pad i want to simult/mute if its on an other bank instead of just pushing it.

so considering all of this which is the best os to use?