4.79

its up! Get it while its hot boys!

http://www7a.biglobe.ne.jp/~mpc1000/index.html

--------------------------------------
Bug fix: New OS Ver4.79 03-Aug-2007
--------------------------------------
[GRID]
F2 [Q-REAL] Q-LINK real time data edit mode.
1. A display is strange at the time of TC=OFF.
2. RESO12, RESO1, RESO2 and is not +-50

About the following bug

Q: http://youtube.com/watch?v=vp8TIfvP0bo

A: Isn't “Q-Link REALTIME LEVEL” recorded by the sequence?

Q: Tap tempo does not work in its usual manner

A: [MO0DE] +PAD10 (OTHER) =>F2 (MISC.)
?
?Is Tap average OFF?
?Please set the setup here to 2-4.?
-----------------------------------------------------

[GRID]
F2 [Q-REAL] Q-LINK [riarutaimudetaedeitomodo]
At the time of 1.TC=OFF, indication is strange.
2.RESO12, RESO1 and RESO2, is not +-50

woooh hooh

i don't get it, can someone translate it?

I think what JJ is trying to say is, that it seems to him that the guy of the youtube video (djspair), somehow may have recorded some track automation using the q link realtime feature for volume. You know, like recordable track mutes, but with volume attached to the Q-Link instead. That's what I am reading out of this "answer"

Anyway, why all of a sudden I see like three different threads discussing three different and more important: old / outdated os versions here? Development could improve if we'd all update on the regular to have a broader usergroup for testing, I guess.

Just a thought... of course everybody can use the system they want to and choose the topics what they want to talk about, but in terms of bug fixing / documentation it's not very efficient

stan steez wrote:Development could improve if we'd all update on the regular to have a broader usergroup for testing

COOOO
SIIIIGN

stay current so the rest of us don't have to carry dead weight! be an active participant!

I'm still at 4.75 because I don't want to downgrade the size of the waveform in TRIM MODE... and i can't really see any progress in fixes that will speed up my workflow. Am I missing something out?

yeah im still at 4.75 too..

no reason for me to upgrade as of yet - but i have no issues or complaints with 4.75

i'll probably update when they add something new, or when i get bored

es-k wrote:yeah im still at 4.75 too..

no reason for me to upgrade as of yet - but i have no issues or complaints with 4.75

i'll probably update when they add something new, or when i get bored

I think he has added something new since then that is important at least to me. While trimming you can hold down a pad and move the start data with the wheel and listen to it scroll throught the sample. makes placement easier and more efficient. also with the end side.

i have been enjoying that new trim addition a lot, makes for fast trim
the downside is that still, when you are trying to vertically zoom, this happens:

1 - load sample
2 - adjust start point
3 - attempt to vertical zoom by hitting UP:
4 - up key takes you to "SAMPLE LIST"
5 - hit up again to zoom vertical
6 - hit down to go back to start point to edit based on zoom
7 - WORKFLOW BUG: extra keystroke to get to vertical zoom when editing start point.

this is the only criticism i have of new trim, and it's ONLY applicable on START POINT, not on END POINT. example:

1 - load sample
2 - adjust end point
3 - hit UP: zoom vertical
4 - hit DOWN: un-zoom vertical
5 - NOTE: no extra keystroke needed to zoom UP.

Yeah, i find it disturbing too! Somebody already suggested to use [SHIFT] to jump in the sample field, I believe. Using [TAP TEMPO] or [STOP] for this would also make sense to me... I hope he does something about it.

good to see someone else notice that, i was beginning to worry i was the only one

I noticed it ever since it first appered in 4.76.
See: http://www.mpc-forums.com/viewtopic.php ... light=4+76

But what you wanna do though? By now I am too lazy to explain to JJ what the problemo is... maybe the next man isn't, hopefully!

PEACE

stan steez wrote:Yeah, i find it disturbing too! Somebody already suggested to use [SHIFT] to jump in the sample field, I believe. Using [TAP TEMPO] or [STOP] for this would also make sense to me... I hope he does something about it.

perhaps [shift] (or [note repeat] or [stop]) + turn the data wheel to change the sample? may be quicker, plus the cursor wouldn't have to move from the start/loop/end row.

Mr modnaR wrote:perhaps [shift] (or [note repeat] or [stop]) + turn the data wheel to change the sample? may be quicker, plus the cursor wouldn't have to move from the start/loop/end row.

Team JJ wrote:About the affair, I also asked change of operation of the programmer.
However, a programmer does not change.
The programmer is thinking unification of operation as important

oh well.