Forum to discuss all matters relating to the MPC1000 and MPC2500 operating systems created by 'JJ' (all versions).
User avatar
By t_bias Fri Nov 16, 2007 12:57 am
morning all,

been having a few issues with this of late.

everytime i update i try to play projects made on earlier versions of JJOS
(pre 4.5x) and any q-link automation turns to jibberish.

i.e. a simple filter sweep becomes an irreversible silencing of all programs.

is there any work around apart from deleting all old q-link data and
re-entering it? and of course continually jumping between OS versions?


cheeeeers gents...
User avatar
By arebee Fri Nov 16, 2007 1:39 am
t_bias wrote:morning all,

been having a few issues with this of late.

everytime i update i try to play projects made on earlier versions of JJOS
(pre 4.5x) and any q-link automation turns to jibberish.

i.e. a simple filter sweep becomes an irreversible silencing of all programs.

is there any work around apart from deleting all old q-link data and
re-entering it? and of course continually jumping between OS versions?


cheeeeers gents...


not sure if its a compatability issue, just that i seem to remember one os being buggy with the qlink recording for a spell, it got fixed, but could ot be that u were using that buggy os at the time you did that older stuff?

check their bug list, date, and os version, it might show something
but mostly just a hunch all this, cos a similar thing happened to me way back..

good luck
User avatar
By t_bias Sat Nov 17, 2007 12:26 am
arebee wrote:
t_bias wrote:morning all,

been having a few issues with this of late.

everytime i update i try to play projects made on earlier versions of JJOS
(pre 4.5x) and any q-link automation turns to jibberish.

i.e. a simple filter sweep becomes an irreversible silencing of all programs.

is there any work around apart from deleting all old q-link data and
re-entering it? and of course continually jumping between OS versions?


cheeeeers gents...


not sure if its a compatability issue, just that i seem to remember one os being buggy with the qlink recording for a spell, it got fixed, but could ot be that u were using that buggy os at the time you did that older stuff?

check their bug list, date, and os version, it might show something
but mostly just a hunch all this, cos a similar thing happened to me way back..

good luck


very possible. probably the most likely explanation...

kinda spewin... i got way into so much automation at the time that those
tracks are pretty much dead to me now! haven't been able to reverse
the problem, despite deleting pretty much all data besides notes....


bummer.

thanks anyway amigo
User avatar

By t_bias Mon Nov 19, 2007 1:15 am
yo - anyone else had this problem?

the old tracks I was makin on 4.51 are now pretty much useless on every
other version of JJ.

any volume/level automation is now read by every pad. even after deleting the q-real info!

i can't reverse this! it's totally f*%ked! lost heaps of good material.


if anyone has any ideas i'd be real greatful.
User avatar

By t_bias Mon Nov 19, 2007 1:39 am
yo think i gots it sussed....

have to re-load the buggy os 4.51, delete all q-link data. re-save.
then load up new 4.9x and re-automate all old data.

oh-so-sh!thouse.


ahh well. least all is not completely lost.
User avatar

By arebee Mon Nov 19, 2007 10:21 am
glad u just about made it through the thorns!

these things do happen, jj os is awesome, but any new os needs a bit of a tryout - especially in areas u use / depend on a lot, before u commit to starting any major projects on it.

also mbe stick to the os u know works well in these areas before rushing to upgrade...just because sometimes, something big n bad gets fixed, but behind the scenes there's a minor bug elswhere as a result of that fix....its tricky - being a beta tester (essentially what we are now).....and if u are trying to run a studio thats functional, this is where u can get into a mess.

its ironic tho' because i tend to rush into upgrades to chase that new code, then get something really fresh going, but subsequently it can get lost as there's a bug introduced that screws it up (in terms of using the mad-freewheeling-off the cuff stuff i just did) and cant be used in quite the same way in other os versions = exactly what u have just dealt with here.

but for any brand new upgrade its best to just jam,tweak,tryout, but most of all, expect not to be able to save!! - just as a worst case scenario - then u wont get stung by this ever evolving plateau!

: )
User avatar

By t_bias Tue Nov 20, 2007 2:40 am
yes...
the irony being that I stuck with 4.51 believing it to be more stable than the
others...

d'oh!

cheers mate