[gseher]

I’m not sure why exactly you’re mentioning osc – Kyma at this point does not respond to osc. I have a feeling that this will come sooner rather than later, but there has been no announcement. I just received my Pacarana last week – sold my old system a couple of years ago, but always intended to get one again when they updated the hardware.

Of course, you can use the osculator program to convert osc to midi signals for the kyma, but there is no direct osc support.

[gseher]

OK, one issue with pressing MUT first then the step(s) to skip is that if you have some tracks muted, it un-mutes all the tracks!

So, back to plan A – select step(s) then click MUT.

I’m clearly missing something here. It can’t be right that you have to mute steps before skipping them.

Apols if I sound negative – I’m not. I really like the Nemo. I am just finding this whole skip implementation very bizarre.

[gseher]

Hi. Another observation on this.

I note the manual says to hold the step(s) then press MUT. Holding a step that is green turns it off of course. Then the MUT turns it red.

There is also the (undocumented?) way which is to click and hold MUT first, then press the step(s). This turns them red instantly. Hence is a better way to skip.

However, in both cases, clicking them to turn them on reverts them to off, not to green. It takes an extra click to switch them on, by which time often the step has triggered with an unwanted gap.

I really hope there is a way round this.

Post edited by: skip2thebeat, at: 2009/03/01 15:01

[gseher]

It is technically a no-biggie to swap them. The current implementation is based on consistency considerations – in other parts of the UI you use the sigle click to command low values and double click to enter high value (as tens, etc.).

Otoh this is a theoretical approach, and practical experience may be different. So I am very open to hear what other users think about this proposal.

Cheers, Gabriel

[gseher]

Thanks – I just upgraded to the latest 1.60 OS – and it all works as expected now, and even with a few minutes use I’ve noticed improvements in workflow, and the new phrase thing sounds cool aswell

[gseher]

You can override the number of notes in your chord – limiting it to 1 note will produce the random selection effect you describe so I guess that’s what’s inadvertantly happened.
It’s in the manual, sorry I don’t have it to hand but hopefully you can find it under "chords" (oh for an index eh?) – a jolly useful feature.
best regards

[gseher]

Quote:

In grid track live mode, starting with the fact that the mutes would affect all tracks in a cluster. Assuming we have the cluster switching option, you could use edit mode, where you could select clusters, but it would not cue them for playback, and see the mutes for that cluster and change mutes before that cluster plays.

i think i’m following, and it sounds good, but global mutes for tracks in clustered pages would be a great first step.

So thats -not surprisingly- a yes from me too.

[gseher]

I would say yes to this.

[gseher]

Hello. If I remember correct the virtual midi channels was still working under 1.42. To go back from 1.60 to 1.42 involves the USB port.

Read this:
http://genoqs.net/downloads/OCT_USB_Update.pdf

It’s not an easy task to execute…in my opinion of course

/Bo

Post edited by: Sbay, at: 2009/02/18 19:09

[gseher]

So is the general opinion that the gridtrack mutes should be de-coupled from the pages, and act universally? I personally am in favor of it to.. seems to simplify the workflow in a lot of cases.. But I thought I’d ask before breaking anything
Cheers,
Gabriel

[gseher]

OK, so you mean have some user defined scales be ready to be called directly, after you have composed them, right? Indeed, this is working nicely on the Nemo, so no reason to not carry it over! Will look into it.
Cheers,
Gabriel

[gseher]

Well, I think we should be able to introduce the aleatoric elements by other means, so I definitely would categorize it as a bug. I have confirmed it is not doing what it should, so it is on the fix list.
Cheers,

Gabriel

[gseher]

Hello,
just some thoughts to the very good points you bring up.

Pendulum with skipped steps seems to go wrong after some time. I have technically understood the issue now and it is on the list to get fixed in a next OS update.

Skipping more than one step should work by holding the step buttons pressed, and then pressing the MUT button.

Default after-clear track values cannot be changed right now. The values that are assigned after a reset are the ones that you have saved previously. So a workaround may be once invest the time and save the values as you need them.
Alternatively you can do this for a single page for example, and use a copy of that page each time you need that particular configuration.

Direction maps are on the agenda – however it takes longer than expected because the model used in Octopus will not carry over and we are looking to simplify it anyway.

Hope this is helpful.
Cheers,

Gabriel

[gseher]

Mine does this too. It’s using OS 1.60.27 (I think).
It’s a weird bug/feature because if I have a page repeat
in there and the page has a chained track, it really
starts to become almost self composing or aleatoric
when it shifts through the chained cycle.

In any case, I like the feature, but I also want
my pages to play the way I arrange them!

rachel

[gseher]

Hello

It’s first time to post my messerge here.
I’m Japanese and live in Tokyo, so my description in English may be confusing.
My Vampire(OS 1.60) has arrived a few days ago, and I feel happy to be with this incredible machine. 😆 I’m sure Octpus is the most revolutionary sequencer in the history.

By the way, I have a trouble similar to LDT’s problem.
I can’t make it return to the head of chainings in page clusters.
I always want to make it return from the head of the chain,
but it always returns to start from the last row which it has played.

For example, in the case the track chain of row 9 through 6 from page 1 to 2,
the first playing is no problem, it plays row 9,8,7,6 of page 1 and then row 9,8,7,6 of page 2.
But it returns to play row 6,9,8,7 of page 1 to page 2.
In the third time playing of loops, it repeat from 7,6,9,8 each page.
Likewise it repeat from 8,7,6,9 each page in the forth time.
It does the same things when it’s played both using page repeat and page length.
This problem occurs in grid live mode as well.
Though the first loop plays as I expected,
it plays from the last row whenever I toggle pages intentionally.

Thanks,
Mitsu.

[Author]

Posts