>>It seems that some of the changing and optimising of code I've done has introduced a few oddities. I've uploaded tonights build, which fixes these.<< aye, that's done the trick. also, the midi-clock-only output on this machine (#1003) is working as advertised too, ta. I have quite a complex little set-up here now (this is in the studio, though the live rig has a few things in common). & because of this, I'm getting some false clock-starts (F8, is it?) here's what's going on: the clock-only output of the p3 goes to a doepfer pocket controller, which does things to the maq & whatever it's talking to. this goes to a midi through-box, & then to my oldest, most knackered, but up-to-date software-wise maq. the maq's output is merged with another output of the through-box & with my novation x-station controller keyboard. (this last bit of merging happens inside the keyboard). the whole lot then goes back into the p3, while everything else (repeater, supernova, samplers, proteus boxes, ms6's & so forth) is fed from the p3. what's happening is that the repeater &/or the maq will suddenly start up on their own... I have to start & then stop the p3 to stop them, & then they do it again a few seconds later. while the maq & the repeater are having their moments of madness, the tempo control on the p3 is locked out, almost as if it's receiving an external clock. which it is, I suppose what I can't figure out is where the spurious F8's are coming from. a normal clock-loop would just chase itself- this is running at the right speed, it's just not starting & stopping when I want it to. I think I either need to use the maq as the master clock (ugh...) or use something else as the master clock. in the live-rig, this would probably be the korg es-1 anyway. but everything else is fine.... :-) duncan.
Message
Re: erm.... ah..... er......
2005-10-22 by ferrograph632
Attachments
- No local attachments were found for this message.