Forum Replies Created
-
AuthorPosts
-
gseherKeymaster
OT:
Hi Lars, just curious (and solely based on your first name) if you may be from anywhere near my part of the world: Cph, Denmark?gseherKeymasterHi Lars, glad you solved the Speed problem. To see the version of the OS start your machine with the ESC button pressed down. The number readout should reveal the OS version number.
Cheers, GabrielgseherKeymasterGabriel, that was the fix, thank you. Is there a reference manual availale, in addition to the Navigation Guide? Finding specific user info is quite difficult. Love my Nemo, though.
Cheers,
Lars:)gseherKeymasterTahnks for your response, Gabriel posted the answer and it worked. How do I see the OS version currently installed on the Nemo?
Tanks,
LarsgseherKeymasterYes, you will possibly lose some mute configurations in pages within a cluster, but i think its worth it for the benefits of having a mute master for clusters.
Nothing else major for now. i’d like to suggest that empty pages automatically become active(but not playing) if you enter them from the grid. At the moment, if you exit a page without adding a step, they stay not activated. I think the fact that you entered an empty page means your most probably going to use it, so it might as well be activated (red led in grid).
I also noticed that STA values less than 8(?) on the first step result in it not playing. I have no suggestions on how to solve this because of all the chaining and clustering possibilities (if its a straight 16 step sequence you could move the data to the 16th step), but was wondering if anyone had any bright ideas.
Post edited by: chaosmoon, at: 2009/03/17 15:51
gseherKeymasterAdvansys, make sure that while in track mode you see the Track Value LED lit up orange (in Row 3). If it is not orange, click on it once and Speed should light up together with some other options for actual values as opposed to factors.
Let us know if this solved it.
Cheers, GabrielgseherKeymasterAbout the bug you mention above, Guillaume, there is a fix for it that will be part of the next OS release.
What chaosmoon suggests just above would work in principle: the last sentence I am not fully clear about though: you mean the mutestate of the currently playing page of a cluster will have carried over to all pages in the cluster, and hence becomes the "master" for the cluster (rhyme not intended). That means you lose any mute configurations you may have in some pages, right?
In principle this can be good or bad – you just have to make sure you arrange your material accordingly, or things out of your control will happen.. any other ideas?
gseherKeymasterWhich OS are you using on your Nemo…?
Post edited by: Prime NL, at: 2009/03/17 09:52
gseherKeymasteri’ve captured this on video..
I’m using chained tracks, page-repeats and clusters. The clustered pages are repeating inconsistently.
its a .3gp file made with my phone. Lo-fi, but good enough to see whats going on:
Post edited by: chaosmoon, at: 2009/03/17 02:00
gseherKeymasterHow about a mix of both?
If GT is entered on a single page, it effects in the same way as now implemented, not effecting any other pages.
If GT is entered on a cluster, the mutes states in the currently playing page within the cluster are immediately -and irreversibly- applied to all pages within that cluster.
Exiting GT mode wouldn’t change anything this way. right?
Post edited by: chaosmoon, at: 2009/03/16 23:55
gseherKeymasterHi,
The place where the current muting system is annoying is exclusively when page clusters are enabled and you are in gridtrack mode.
This new muting system should only come into effect for pages which have clustering enabled.
When clustering is enabled, send the mute/unmute to all pages in the cluster.
If you cluster 2 pages with different tracks muted, they would play as they are, but if you use gridtrack to set/unset a mute for a track, it would apply to all clustered pages.
This way, what you see in page mode would match what you see in gridtrack mode.
I hope this makes sense.
BTW, I found a related bug, in gridtrack mode, you cannot mute/unmute 2 tracks simultaneously, you must do it one at a time. In page mode, you can mute 2 tracks simultaneously.
Guillaume
gseherKeymasterQuote:I think I was just being an idiot.I know that feeling:whistle: .
Everytime we add one more piece of gear to the chain, the complexity increases and surely the risk of "what the f**k is going on now?" increases as well.
But this is a good excuse for using our complex setup every day!Post edited by: LDT, at: 2009/03/16 13:14
gseherKeymasterHi Gabriel,
I think I was just being an idiot.
I have the Octopus driving a CV/Gate rig
and I think I miskeyed my settings.When tuning, I set the A440 on the System 100
relative to a note pressed on a MIDI keyboard,
which should be an A3.This can also be offsset by the Sequencer 104
and so I need to tune that as well.Then when I was sending Midi note A 440 from the
Octopus, I had mistakenly first transposed my
MIDI controller, so it was offset by that amount.After I realised what I had done, I recalibrated and
tuned everything and setup a basic page on the Octopus
with the correct defaults, but it took me a long
time and frustration!There are so many places to offset the MIDI notes,
I just got caught up in it all!rachel
gseherKeymasterTo stick with your good example, when you use Pause in page mode without a track selected, it works so that it re-starts on the next 16th. When you use pause with a track selection it continues to play the rest of the 16th it was playing when you paused it initially. Hope this helps.
Cheers, GabrielgseherKeymasterI have played a bit with making GRIDTRACK mutes act across page boundaries.
While cool in some cases there are a few issues related to usability.
The most important is that now you have two places on the machine where you control the mutestate inside a page. In the worst case, and not so uncommon, a track will not play and you have to check two places to see if its muted. Not good.Even if we de-couple the modes in the sense that when in GRIDTRACK the mute patterns of GRIDTRACK are applied, and the "normal" mutepattern is applied for the rest, it is awkward as soon as you have switch out of GRIDTRACK, since your composition changes. Not good either.
Another option could be to make track mutes act on the bank, and not on the page level. But I can see how that can lead to problems as well, although for the moment it seems to be the more harmless of the above.
Let me know your thoughts.
Cheers,
Gabriel -
AuthorPosts