Forum Replies Created
-
Posts
-
you using a mac? this is the setting I always forget, & which gives an "unknown image" response like the one you’re quoting.
d.
I took my delay box out of the circuit after installing the tweaked o/s.
current rig, which ought to make life difficult for the sort of tight sync we all want:
octopus is slaved, & merged through motu usb express into sequentix P3, then goes into a variety of midi modules. master clock is another sequentix sequencer, not a P3. not even sure I should mention that here….
this is also merged with the octopus into the P3.if I programme some drum sounds on the octopus & some on the new sequentix device, the timing is so close as to be causing that phasing sound on longer decays.
so… good.
if however I now introduce the P3 into the mix, the notes from both the octopus & the new sequencer are a bit early. so…. yes.
more experiments required.
d.
regarding the absence of gabriel & marcel from this discussion, & the way we’ve managed to describe, diagnose & fix the problem ourselves, I’m now wondering if this little o/s time-bomb was a test of the viability of making the hardware run on open-source code…. see if the users can support it themselves.
or else they’ve just got bored with it.
d.Post edited by: duncandisorderly, at: 2010/10/24 20:02
the official "elf-loader" instructions are in the software downloads section of this site (i.e. not with the other documentation but with the O/S files).
I had to use them about six months ago, & provided you follow them to the letter, they work very well. however, if you are using a mac & zterm, there is that one line missing about files>transfer convert I mentioned….
it is a weird experience talking to the octopus over a serial link…
d.
he’s fixed it! he’s fixed it! he’s fixed it! he’s fixed it! he’s fixed it! he’s fixed it! he’s fixed it! he’s fixed it! he’s fixed it! he’s fixed it! he’s fixed it! he’s fixed it! he’s fixed it! he’s fixed it! he’s fixed it! he’s fixed it! he’s fixed it! he’s fixed it! he’s fixed it! he’s fixed it! he’s fixed it! he’s fixed it! he’s fixed it! he’s fixed it! he’s fixed it! he’s fixed it! he’s fixed it! he’s fixed it! he’s fixed it! he’s fixed it! he’s fixed it!
I’m sat here with a colin-fraser-midi’d tb303 as my master clock & the octopus is staying perfectly in time with it from 50bpm to around 160bpm…. I’m really too tired to be more scientific about this right now, but "early results are encouraging". there’s also a P3 in the rig, & all three are locked together fine now. I reading the bpm from the front of a line-6 echo pro.
BY THE WAY- I forgot this, & wasted half-an-hour, because the genoqs "elf loader" doc hasn’t been adjusted… if you’re using zterm on a mac, you need to go to the files>transfer convert menu & change it to ordinary binary or you’ll get an unknown image response from the octopus.
erm…. anyone want to buy some delay boxes?
duncan. very happy.
he’s fixed it! he’s fixed it! he’s fixed it! he’s fixed it! he’s fixed it! he’s fixed it! he’s fixed it! he’s fixed it! he’s fixed it! he’s fixed it! he’s fixed it! he’s fixed it! he’s fixed it! he’s fixed it! he’s fixed it! he’s fixed it! he’s fixed it! he’s fixed it! he’s fixed it! he’s fixed it! he’s fixed it! he’s fixed it! he’s fixed it! he’s fixed it! he’s fixed it! he’s fixed it! he’s fixed it! he’s fixed it! he’s fixed it! he’s fixed it! he’s fixed it!
I’m sat here with a colin-fraser-midi’d tb303 as my master clock & the octopus is staying perfectly in time with it from 50bpm to around 160bpm…. I’m really too tired to be more scientific about this right now, but "early results are encouraging". there’s also a P3 in the rig, & all three are locked together fine now. I reading the bpm from the front of a line-6 echo pro.
BY THE WAY- I forgot this, & wasted half-an-hour, because the genoqs "elf loader" doc hasn’t been adjusted… if you’re using zterm on a mac, you need to go to the files>transfer convert menu & change it to ordinary binary or you’ll get an unknown image response from the octopus.
erm…. anyone want to buy some delay boxes?
duncan. very happy.
chris- excellent work. I wish I had the understanding of the source code & the ability to recompile it myself; this is plainly where the problem lies, & agrees broadly with what colin "P3" fraser suggested a few weeks ago.
I think there are a couple of other forum members- one at least- who have created their own versions of the o/s. maybe this solution should be cross-posted to make sure they see it, & then they can incorporate it in the custom builds.
meanwhile, where are gabriel & marcel?duncan.
sounds like the same thing I found, then. like I say, I’ve cracked it for now with this delay unit…. but it’s a nuisance having to tweak the thing whenever I change tempo.
din-sync, very sensibly, was a dedicated stream of pulses (24 or 48 ppqn, depending whether you were roland or korg, but otherwise compatible) with the start/stop carried on a separate wire.
midi tries to get everything down a single wire (the other active connection is a steady 5V reference, while the ground wire is usually connected only at one end), which means 16 channels-worth of note-on/off, continuous controllers, patch changes, sys-ex & all the rest, fighting for space at 32.5 kbaud. somewhere in amongst that is the realtime clock data & commands. they’re supposed to be prioritised, but how does that happen in practise? it doesn’t.
besides that, as I have been told, midi "start" & clock bytes are supposed to be separate, & it appears that they are not, in the octopus’ current implementation.might try an email to genoqs, since they don’t appear to be watching this thread..
d.
I’d be interested to see the results, when you have time. I should have mentioned, my octopus is running v1.6-something, the latest version. using the delay box means I can get on with using it in the studio at least, & provided I keep the peavey somewhere handy, I can always adjust the delay.
still, it would be nice to hear from the genoqs lads about this….duncan.
I mentioned this experiment to colin (P3) fraser, who replied with a theory that they might be treating the "start" byte as the first tick of the midi clock. I’m not sure what that means, but CF knows his stuff. he continues:
>>Well, 60 seconds divided by 50 bpm = 1.2s per beat
1.2s divided by 24 ticks per beat = 50ms
150bpm = 16.6ms per tick, so not too far off – allowing for a few milliseconds latency to reduce the timing advance.<<gabriel, marcel, you still there? what do you make of this? I can live with it for now, but only if I keep the PC1600 & this delay box handy…
d.
as I recall, when you choose a midi channel for a track, you can turn the LEDs red instead of green, & that’s the other port. I think.
d.
