Forum Replies Created
-
Posts
-
Guys, please let’s take one step back, and talk about what it is you want to do / achieve. As of now you can CPY/PST individual steps, once you mark them selected using the SEL button. But this is likely not what you are looking for. Lars explained a bit, but I am not sure still..
I was just realtime recording on chained tracks (1 and 2). It happened twice after recording just a few notes. But I tried again now, and I can not reproduce it…
The one mechanism that is provided is PLAY. However, it is more a "remember and restore" rather than an "undo" mechanism.
Hi guys, the record on step 1 issue is older I guess and while I have identified the cause, it appears like a significant effort to remove. I was hoping we can live with it for just a bit longer, until we have other little buggers out of the way.
But now Lars, you say you were able to crash. Whether that has the same cause is not clear, but more (any!) information on how you did it would be invaluable! Any specifics will help to track down the crashing behaviour and get a fix quickly.
If we find that the step one recording is the cause, priority is obviously going to shift significantly.
I could not reproduce this.
However while trying to do so the Octopus crashed (froze) twice. I have never had the Octo crash before, so there is something fishy here.Ok, one other issue is that CPY and PST also operate mute for track 1 and O. But I just think that the mute light should have priority: We will not see the orange CPY/PST lights if we have track 1/O muted. Apart from that I dont think there is any problem: If only CPY is pressed, track 1 mute is toggled, and if a step button is held while pressing CPY it will copy the step.
Strangely enough pressing play to undo recording has not bothered me.
But I must admit that I sometimes miss a more general undo. There are things that you can do accidently that can mess up your stuff pretty badly. You could argue though, that undo is for sissies:laugh:
Seriously, I think it would be damn nice to be able to undo your latest action. E.g today I accidently hit track RMX, and I just had to live with the result:SSo, *if* we at some time get a general undo command, this could also work as undo recording.
Quote:Let’s not talk about trading esoteric functions right away, maybe the UI space is already there. I mean, I *like* that stuff!Well, most of the time somebody says: "I would give my right arm for…" they don´t really mean it, do they?
Anyway I will try to be a little constructive about it tomorrow.
But thinking about it now (not at the Octo) it seems simple enough. What is interesting is what happens the moment you touch a step button. In the normal page state, step buttons toggle the step state. But we are already accustomed to the behavior when you grab a step and tweaking an attribute knob (PIT, LEN whatever): The step is in this case NOT toggled because you imediately performed an action.
So perhaps copy/paste could work in exactly the same way: You grab a step, and if CPY or PST is pressed very shortly after, there is no toggling but instead the chosen command.In EDIT state you should have the same, but following the model of this state, the step you grab will be played in realtime as you grab it for copying it. What you additionally could do here is also make the note you paste play in realtime.
Interesting thought. However the two effects of AMT in what you propose would be mixed, but at the same time semantically unrelated. Technically no problem, but probably not a good fit into the master model.
I do have an idea of how to add rests to the chord pool, will let you know how that goes as soon as I get my hands on a prototype.
Step GRV is already in use, but nothing against a refinement, as always
Actually I must admit that with all the great input you guys are providing you are not making my life necessarily easier, but I am so grateful for that!
robert wrote:
Quote:I don’t think the page length property and track retrigger mode should be linked this way, because the result would be that pages with a page length less than 16 steps can no longer have tracks larger than that same amount of steps.Let me explain. Image a page with two tracks, one 8-step track with drums, and a 24-step track with some ambient space stuff on it. The drum track is what I call the ‘dominant’ track, I don’t want the page to be cut off in the middle of that track. To guarantee this, I set page lenght to 8 steps, so I know the page will always run full 8-step cycles before the page is switched.
Suppose my page is put in a cluster, and I want it to repeat 3 times. That’s 3 x 8 = 24 steps before the next page in the cluster is selected. During those 24 steps I want my 21-step track of course to run it’s full cycle.
However, this proposal cuts off all tracks to 8 steps (in this example), because when page length is set to a value less than 16, all tracks will be automatically retriggered when the page cycles, which is at 8 steps in this example. My beautiful 21-step track is butchered down to the first 8 steps. Arrrrggghhh!
That is, I *think* this would happen.
<br /><br />PHow about using step skips to adjust your drum track to 8 steps of length and then set the page length to 24? Wouldn’t that work?
Been working with it now. And now I understand why it works as is does (my questions 1. and 3. are cleared up.)
I like the beta version. For me it has only one quirk, but the workaround is simple. If I have a 16 step page that I want to loop at a 20 step lenght, I have to copy the page and make a two page cluster. Then it works as I want.
I like it, but the question is if other guys are missing something now.Quote:So that would mean a note press in the circle would do this:1. On, octave #1.
2. On, octave #2.
3. On, octave #3.
4. On, musical rest (mute). (blinking LED).
5. Off. (LED off).Yup, that is precisely what I meant.
I already used it on drums (as explained earlier) and it is really good for making that hit that only comes once in a while. Plus you may choose to have a random pick between several sounds that may come with the chosen probability.
The most current beta can now be downloaded in the service area.
Post edited by: admin, at: 2008/05/06 09:57
Quote:I suddenly realise what this feature can do from drum tracks. For instance, have slightly different hihat sounds randomly triggered, or different snare sounds. Very cool…It is cool. I played with the beta today and I did exactly the above thing. But it is even cooler, because with sound sources like a drum kit with a limited range (such as my 808 and my DRM-1) you even have a built-in step probability: You just add notes to the chord pool and octave switch them out of the range of the reciever.
This is suuuper cool.However, this additional feature does not work for instruments with a normal (wide) range.
BUT: How about this: In the beta version every chord note can have one of three colours representing the three different octaves (you cycle through them). What about adding a muted state (a blinking LED) to the chord notes. Thus a muted chord note will not play at all, but it will still be in the chord pool. Result: By adding muted notes to a step chord in "random pool" mode, you will have created a variable probability effect! One note in the pool and two muted notes will be 33% chance that the one note will play etc.
Voila! What do you say?
