[gseher]

Check for a midiloop.
That’s a common cause for freezes in midi gear.

[gseher]

Thanks all for your thoughts.

I am running 1.40 although this is an assumption as I purchased just before musikmesse I guess fresh octo’s come with 1.40 ready. The midi input and output is handled by an xstation interface routing is configured such that a midi loop would not occur
keyboard source is a moog LP. As I say it has caught me out mid flow and I have not been paying special attention to my exact orientation with regard to the exact source of the problem. I will keep a careful lookout and when it happens again I can identify whether it is human error (probable :blink: ) or otherwise. I honestly hope for the former.
I’ll reread the manual…can’t hurt

Many thanks

Wilson

Post edited by: pushtin_cat, at: 2008/04/02 12:53

[gseher]

Octopus as a centerpiece

I do the same with Octopus as Master and a Slave Mac with Live (incl. Plug ln`s in different Midi Channel), a Polar and a Monomachine plus Spectralis.

But this is not possible with Logic because Logic Pro to not accept Midi Clock In and it allways works in Track Mode (that means that the Octopus can only trigger one selected track at a time.:evil:

Post edited by: Dayflight, at: 2008/04/01 23:44

[gseher]

this sounds highly unusual… i’ve never had anything even slightly resembling a crash in 2 years since i got my octopus and i’ve got all sorts of stuff going on… perhaps there’s some sort of midi loop or something that’s been accidently created… or perhaps just try putting the os on again… otherwise i guess it must be some sort of hardware problem?

[gseher]

Hi Wilson,
I must say, this is rather uncommon from what we have seen so far.
My questions would be the same as already asked by tonewrecker.
Any detail you can give could be of great help.
Thanks,
Gabriel

[gseher]

Are you running the 1.40 OS?
What is feeding into the Midi In ports on the machine?
What state is the Octopus in when it locks up? Grid/Page/Track?

Are you using the USB Lamp?
I bought a new lamp for mine and the machine goes out when I plug it in and turn it on. Haven’t figured that one out yet.

[gseher]

Thanks for the reply!

The Octopus is the first piece of new gear on my list!
I’m thinking of buying one next month..

I saw on a video on sonicstate that the Octopus is also availible with black colored side panels?

That’s nice tough the Black sea is sold out..

Sinosphere

[gseher]

Does MidiOX show something funky in the output of the Repeater? I usually run my machines through that freebie program to see what might be causing trouble. It really is a workhorse.

[gseher]

Yeah yeah yeah.
Drum programming on the Octopus is great.
It’s like when you’d see the grid for some of the digital gear Roland had such as the R8 or the 707 and you had the visual relation of where all the hits were falling, except now you can grab them all and move them without having to move around between edit screens.

Even the 909 16 step grid which is fun and fast seems archaic after you start using all the multiple tracks on the octopus at the same time and have different lengths running. I think you’ll like working with more velocity levels too rather than the couple accents provided.

I have a machinedrum myself and still use the internal sequencer in that because the step lock parameters work so well internally and I like the single step copy to multiple step pasting you can do on it once you’ve heard something you like on a step.

I will agree that you want the Octopus as the master clock..you’ll feel like you’re flying the spaceship around.

[gseher]

Hi Sinosphere,

what a wonderful setup (imo)!
In a quite similar setup I would probably setup an Octopus as the master clock and control the TR909 (one MIDI channel) and the MD (another MIDI channel) directly via MIDI.
The SH101, the AKS and the ARP2600 can be controlled via the Kenton interface, while I assume that the TB303 will run on its own sequencer (unless it is hooked up to the Kenton as well).
In terms of the actual routing, you have two outs on Octopus. So one out could go to the emagic box which will provide the signal for the TR909, MD, and the Kenton interface, and possibly interface to the soft synths.
Then you still have an out on the Octopus to go to some other, further MIDI target.
In any event, it seems that you will still have lots of resources on the Octopus to add further equipment down the road.
The bandwidth is similarly available on Nemo, but if you want your sequencing all in one place (i.e. no "delegation" to the TR909 and MD sequencers) Octopus is probably the better choice. If you do "distributed" sequencing, then Nemo may be the nicer machine.
Hope this helps.
Cheers,

Gabriel

Post edited by: gseher, at: 2008/03/21 19:03

[gseher]

Hi Gabriel,

My setup includes a tr-909, tb-303, sh-101, machinedrum uw, ems synthi aks, arp 2600 and some soft synths.

Sinosphere

[gseher]

Hello Sinosphere,
would you mind giving us a bit more specifics/detail about your setup?
In general you can use Octopus and Nemo to address 32 MIDI channels, including all controllers (CC) on each of the channels.
I understand that you would like to make Octopus something like the centerpiece of your setup, but to give you an opinion, I need to understand better what you have in mind.
Cheers,
Gabriel

[gseher]

droolmaster0 wrote:

Quote:

…. But how could I ever justify buying another Octopus.

Well now you can justify it, sort of… you can get a Nemo with the excuse that it’s portable.

[gseher]

Looks great guys can wait to see what it can do…

[gseher]

Seems to be quite a little fiend of a machine. Can’t wait to see the specs.
Will it fit in my backpack to carry on the plane to gigs?

[Author]

Posts