Forum Replies Created
-
Posts
-
What about chord recognition as in ordinary arranger keyboards? This is were all stepsequencers fail. Once you’ve created a fantastic pattern you’re stuck with it. No way to improvise (meaning changing scale) on the fly other then a simple key transpose or a non-musical thing like hitting a button to change scale. If you guys can do this, then you’ve have really something.
Post edited by: bronswerk, at: 2008/04/11 20:28
Post edited by: bronswerk, at: 2008/04/11 20:29
gseher wrote:
Quote:You are right in that there is no way to do a direct jump from let’s say F# Major to G Major, and that would not be a big issue to implement, maybe using the main encoder.. is that what sort of what you meant?Yep that’s what I was after.
I haven’t yet figured out a workflow where you can freely improvise with scales and key, but the scale transpose would add something to that.Cheers, /R
Great! And yes it even makes some logical senseB)
Where the current behaviour of POS change in chains has the "I am feeling lucky" factor, actually there is indeed an element of happy accident to the new mode too, although it was thought out for seeking "normality":
Lets say you have two melodic tracks going on different midi channels (to be really conservative we could call them bass and lead:P ). Then you chain them and put them in "Follow head" mode and shift POS ,say, 8 steps and then unchain. Now half of the bassline has moved to the lead track and vice versa. Chaos at your fingertips!
Hello zinoff,
just a few quick notes.
When in MOD you can adjust the base of the scale and build "on top" of it.From the default (chromatic with a base of C), you would select F# as the base and press Maj, and you should get F# Major.
When in CAD, the scale composition will get translated to changes in pitch of your tracks, so you can actually use MOD to influence the page sounds altogether.
You are right in that there is no way to do a direct jump from let’s say F# Major to G Major, and that would not be a big issue to implement, maybe using the main encoder.. is that what sort of what you meant?
Cheers,
Gabriel
Well, increasing the resolution of the sequencer could be achieved in at least two ways I can think of now, but one of them (the more promising one) is something I would really need to build a experiment for. The other one bases on the current model and seems very CPU heavy, but still worth validating.
What needs to be rewritten in the way the sequencer events are generated and put into the sequencer queue, and the way the sequencer queue is then played back.
There is a component of latency that I need to investigate an experiment. The OS values in the specs are good, but I need to see it running, and hear it play. Realistically, that looks more like a summer project rather than a quick fix.Ok, some years the summer comes earlier, especially in these days.. so will keep you posted on any progress / realization I manage to achieve at that front.
Cheers,
GabrielSounds like you got a Black Sea too, not?
Welcome to the party, I also just joined.
Let´s rock,n,rooo , – ahem, lets make some wierd sh*t and have fun!Great, thanks for clearing up my questions.
It could be that I accidently had created an event. I havent looked into events yet. Looking forward to that.
Do you mean I should learn hot wo use scales in the first place? :whistle:
(heavily edited)
If I use the preset major scale it’s specified on C Major, from there if I want to do the C/Am/F/G chord progression I have to go to the grid, or select all tracks and twiddle with the pitch.
This is my question:
How do I get let’s say the F# Major scale from the presets? (my idea was to transpose the scale)On the side, my other questions are:
what is MOD suppose to do?
why CAD on my machines sets the track pitch to something almost always to 1.5 tones down [e.g. base track in C, enabling CAD and hitting C on the pitch ring the track is transposed to A, when I hit G it transposes to E]Dunno, let me know, it was probably a silly idea to start with. Cheers.
Post edited by: zinoff, at: 2008/04/08 21:39
Hi Lars,
first off, many thanks for the nice background, as to why this is desirable, and I must say that I can fully follow. Yet another great discussion, alongside with the one we have had on chords.Before going from my end into the ways to solve it, let me give you the cold sight of the programmer on this. Octopus has an internal resolution of 1/192 of a note. That translates to 12 possible positions between two steps of 1/16th. Why GRV can get up to 16 is a separate question for now, let’s focus on the 12 segments.
That is the current setup as of right now and I need to reflect a bit on how your proposed solutions may be mapped. Any thoughts in the meantime are welcome!
Cheers, Gabriel
Hi Lars, here some quick shots..
A step will be orange (again, in the traditional color scheme) in one of two cases: a) the step holds an event, or
b) the step holds a chord.In the a) case the step may have a note trigger or not. But the event is always active regardless of the note trigger status so it is shown "in the foreground".
Also, you cannot turn the event off by pressing the step, so the orange light stays.In the b) case the step will trigger a chord but only as long as it has a note trigger with it. So you can toggle the step as you normally would.
In the case of skipped steps, it is a question of preference if you want an event step that is skipped to show red or orange. Consistency says it should be red, since it is skipped. In practice I found it useful to know that there is an event, and where, such as to activate it directly as soon as it is needed. But glad to discuss
Stop does not work in step mode, indeed. The reason is that the play doesn’t work either. What?? Well, the play buttons (one, two and three triangles) in step mode have the function of multiplying the step length. So the idea is that letting you stop the machine but not restart it is kinda mean..
ESC is used to always bring you back to page mode. It is not used to take you one level up, but always to page mode of the last visited page, since that is where we accuse you of spending most of your time. As always, ymmv.
I have also an Octopus nearly from the beginning on and actually with OS 1.40. I had never such breakdowns / freezes and I think the reason could caused by a midi problem comes in from an external connected device or from a inadequate OS setup. Did you try to install the OS 1.40 new again? Perhaps that could help. Please read before the OS installation procedure carefully!
