Re: Re:Gigging with the Nemo

OS_CE Forums Nemo General Gigging with the Nemo Re: Re:Gigging with the Nemo


Received the Nemo yesterday, and…IT’S ABSOLUTELY BRILLIANT!!! Repeating what I just wrote on the VSE webiste: "Sterling craftsmanship, extremely ergonomic, creatively inspiring and most important of all-EASY as hell to use, despite its remarkably deep capabilities. The intuitive nature of the interface makes it an absolutely joy. Before I bought it, I was concerned about the lack of any LED/LCD alphanumeric display, but oddly the machine forces you to be more creative because of this. The clever arrangement of its reassuringly tactile ball bearing buttons combined with the multi-color LED chase lights and the 4-tracks-at-a-glance page setup brings out a natural mathematical workflow that I’ve not utilized with any other sequencer."

As far as the machine state save capabilities for your purposes, monobass, I suspect that you’d be able to find a way to work within the 64 pattern-at-a-time capacity, particularly if you’re focusing mostly on live tweaking and then returning to the saved "snapshot." But, I guess that all depends on how long your pieces are. I originally voiced your very same concerns to Noisebug, and they forwarded me the following response from Gabriel of Genoqs:

"This is an interesting point and was not aware that this is actually
such a concern.
It seems to be perceived as a shortcoming, and in fact I am making the
case that it is actually state of the art.
Apparently we (genoQs) need to change the way we position this
message, as it appears
confuse the customers as to what is really available to them
functionality wise at that end. Here my thoughts:

An Octopus page is immensely powerful by itself, it includes several
program change commands, CCs, and
sequence information, etc, so in the end it can be considered
analogous to a patch on a synthesizer.
Remember that what people know to be a "step sequence", is what we
call a "track" on the Octopus/Nemo,
and a page holds 10 / 4 of those.

On synths you create multis, for more complex structures, and so can
you do on Octopus, by grouping pages
together either visually (all over the matrix, as you fancy) or
formally using the 16 page group slots available.

You also have a global state, i.e. parameters that apply to everything
in the machine, and this again is separate.

So now – saving one full machine state to flash means that every
single page, plus the global
settings are stored to flash, so you can pick up work where you left
it off the next time you
turn on the machine. Until now we chose to pack this all up into one
single operation, simply for ease of use.

Furthermore, you can use the MIDI SYSEX route to save pages externally
and load them back, as you would
with synth patches too. Or you save banks of pages (up to 16 pages at
once), of which we have 9 concurrently
in the memory, the global machine setting, or of course the full
machine state.

So in the end, my point is that functionality wise the save operation
is only different by context (sequencer as
opposed to synth) from what people know already. They may just not
realize that.
And they may also not realize that you will seldomly need to use a
majority of the available sequencing space
for just one application (i.e. session, track, jam, etc.).

These are just my thoughts, and please let me know if this story makes
sense to you.
If it does not, we’ll talk again. If it does, I’ll try to adjust our
own messaging along these same lines, to correct
this glitch in the image of the machine.



PS- to answer your question about saving more states in the flash –
there are technical barriers that prevent us
from doing that."

Monobass-hopefully that helps (although I didn’t completely comprehend some of what Gabriel was talking about).

P.S.-Gabriel, if you read this, I hope it was OK to reprint your e-mail; if not, you could delete the post.