Forum Replies Created
-
Posts
-
You could maybe look for a second hand Sequentix P3 to run alongside your genoQs gear. The P3’s aux events cover tempo/timebase changes (as well as a host of other stuff) and you can automate them, use accumulators to progressively change or morph them etc. etc.
I imagine lots of us have more than one synth so owning more than one sequencer can also be a good thing.
I tried switching between clusters with different repeat cycles and didn’t see any inconsistency.
We could use the unused buttons from the grid track live mode to switch clusters. In Nemo it’s rows 5 to 16, in Octopus it would be less, probably 11 to 16.
The mutes dealing the the currently playing page also annoys me, it’s great, but when mixed with clusters, it becomes annoying because, suppose you’re playing a 2 page cluster with no repeat and you mute one or more tracks, then the page changes. You have no way to unmute the track(s) you previously muted before the first page plays again.
Making the grid track live mode mutes affect all tracks in all pages so you can always control what’s muted would be interesting, but that would be the easy way out.
Here’s the hard way:
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 hope this makes sense.
Guillaume
Guillaume wrote:
Quote:Each cluster group could be represented by a single slot in grid track mode, regardless of the number of pages in the group.This way you could switch between different cluster groups, as well as have access to muting tracks all from the same mode.
Yes this is also something that bothers me, the mutes only deal with the currently playing page. My suggestion was to override the mute state for all tracks based on current page when entering grid track mode, but i think this boils down to the same thing.
But how would you switch cluster-groups here?
Post edited by: chaosmoon, at: 2009/02/12 00:31
Guillaume wrote:
Quote:OK, I knew I missed something.I finally found that you can have multiple clusters per track by separating them by blank pages, this gives me about 90% of what I was looking for.
Could you try setting the pages in these clusters to repeat more than once and see what happens if you jump from cluster to cluster after each cycle? I was getting inconsistant repeat numbers last time i tried.
Wolfram tones is very cool…
I thought along the same lines when I saw the Octopus grid and put two and two together…
Big interest of mine also…
OK, I knew I missed something.
I finally found that you can have multiple clusters per track by separating them by blank pages, this gives me about 90% of what I was looking for.
I’m happy to hear someone else would like multiple clusters per bank.
I think I cut some corners in my initial explanation, so here’s the long version.
If you could make multiple clusters per bank, each group of clusters could include a different number of pages.
How would you see which pages are part of which cluster group and select which group is playing?
We would need a way to identify different groups in grid mode. Possibly using different colors for the first page of a group, for example a 2 page cluster would have a green page and an orange page, orange indicating it is the second page of a cluster.
This way you could switch between different cluster groups by selecting the first page of a cluster group. We could also switch group by selecting another page than the first one, but we need to see which page is first.
Now the grid track thing.
Each cluster group could be represented by a single slot in grid track mode, regardless of the number of pages in the group.
This way you could switch between different cluster groups, as well as have access to muting tracks all from the same mode.
I hope this makes more sense.
Guillaume
hmmm..post got lost when trying to upload a 9Mb file.
to recap:
The Nemo is getting 0xFB (continue) messages from logic if started elsewhere than 1111, as apposed to 0xFA (start) when started from 1111.This results in the Nemo not resetting to step 1 and thus running offbeat.
Until i find an option in Logic to remedy this i’ve made a standalone in Max that sends 0xFA to Nemo when 0xFB is received.
You can find it here
I believe this is a Logic thing as this happened also together with my MPC 2000XL.
Somewhere in your Logic there should be a setting that solves this problem.
Post edited by: Prime NL, at: 2009/02/04 15:22
You have to hold down the ESC button when you turn on your Nemo.
In the first row you should see (f.i.) the first six leds lit and the 10Xled lit.
And on the second row the 3rd number of the OS f.i. the first led in row2 is orange which will read as OS 1.6.11
