Forum Replies Created
-
Posts
-
Same for me.
I tried going from 160 to 162 using the sysex last night and it never switched back on afterwards.
USB upgrade worked first time though from windows XP and all my data seems to be intact, although I did back it up via sysex first.
Right, where were we?
Oxix52 wrote:
Quote:Finally fixed my Octopus! I had to use a windows machine to get the transfer to work. I downloaded the 1.62 OS without problems using the USB connection. Now my Octopus is living again!:laugh:Thank you very much.
Barry
So did you just follow the USB update pdf word for word on windows and it worked Barry?
Gabriel I have the latest beta version. Am I safe to upgrade to the new version?
LDT which version did you upgrade from??
Cheers!
matt
Ah sorry Gabriel I didn’t see this thread before – this is the problem I emailed you about with cluster pages repeating too many times.
Cheers
Matt
No doesn’t sound right. I can’t check to see what mine does at the moment in this case but certainly I’m having other problem with clusters not repeating pages the correct number of times. Will try to check this a bit later on…
ah right yeah very simple. i wonder what would happen if you had it pitch down instead of up? would it sound moodier?!
actually i thought it might choose the nearest one. i guess that’s a bit more processor intensive though is it?
okay i’ll try to draw something up over the weekend when i get a sec
cheers!!
the more i think about this feature the more i want it!!
also, what would be really cool from an experimental point of view would be a user definable tempo ‘slew’ rate.
ie. if you’re changing from 190BPM to 57BPM or some other nonsense then you wouldn’t necessarily want it to instantly jump so you should be able to set the time somehow. in fact, this damping factor would probably help stabilise the clock frequency too, when making drastic changes. could get a bit chaotic otherwise.
any thoughts guys? i guess it’s a bit like a modification to the synch to external midi clock routine?
cheers
m
Yeah I reckon it’ll be really useful actually. Gabriel can you describe how the current force to scale works algorithmically? eg. if the scale your forcing notes to contains none of the notes in the actual sequence, how does the mapping work? makes sense to use the same system, at least initially so it’s easy to implement!
cheers
matt
My vampire doesn’t seem to attract too much grease really to be honest, but I’m over the fondling stage now – i generally only touch the silver bits. I generally wash my paws before using it too. Haven’t had to wipe it down yet and still looks utterly awesome.
Get one, and just be careful you don’t dribble too much…
Looking at page 119 in my manual on External Scale Editing we could just use a similar process for the global (grid) scale.
Arming for external scale edit:
Hold GRID and press REC then enter scale mode by pressing SCALE SELEditing current scale:
Current scale is determined by incoming midi ‘chords’.eg if you press C3, F2, A4, all notes generated (that aren’t fixed by specific page scales) will be C, F and A in their respective octaves (their respective programmed ones, not the keyed ones – perhaps we have the first key of the ‘chord’ determining the base octave of the transposition relative to octave 3 eg C3 would give no base octave transposition but C4 would shift everything up an octave etc)
Letting go of all keys in the ‘chord’ essentially fixes the current scale. Any new key presses will start a new scale and instantly clear the previous one.
Disarming:
Press REC again or SCALE SEL againWhat do you think Garbiel? I could generate some example tables of what I mean if you like when i get chance?
Cheers!
Matt
gseher wrote:
Quote:One problem I see here is that you will in most cases alter the pitch of the bottom rows, but changing the pitch of the top rows will require a lot of fingers
Would it not be better to work with force to scale and have the keys influence the scale rather than the track pitches directly?i think this makes more intuitive sense to me…
