Forum Replies Created
-
Posts
-
Hmm, have you tried the recording undo function?
You record your take, but if you want another go, you just push ">" (while still in record) and what you just recorded is erased, but you are still in record mode. That is what I do all the time.Quote:Maybe we should clarify that "overwrite" means that as the step indicator passes over a step it is erased and overwritten, so that means if you hit stop while the indicator is at step 10, then anything on steps 11-16 is not overwritten.I think we still need a distiction between notes that was on the track before the recording in contrast to notes recorded in the previous round of the same recording process. I am still unclear if you mean overwrite whatever is on the track or just the new stuff.
OK, need your help on this one.
Traditionally, to compose a chord on a step you hold down any of the chord buttons and enter your notes. Then you release the chord button and you are done. The chord block serves as a cardinality indicator (number of notes in the chord), but the buttons are not different in function. So far.
I have introduced a new twist, called chord size (working name). Chord size is different from chord cardinality in that it is independent and user definable between 1 and 7, you guessed it, using the chord block buttons.
When chord size and cardinality are the same you have the old model. Step plays a chord as expected.
Btw, size is shown in green, cardinality in red. When they overlap it’s orange, and we have the old model in place.When chord size differs from the cardinality.. what do you think should happen?
Chord size is nice in (and originates from) the random pool pick scenario because it easily gives you access to "rests", when size is greater than cardinality. But I have a feeling we can do a bit more with it in the cases where we don’t do pool picking.Now I need your thoughts..
I think I may have mentioned it a while ago that on my sketch pad right now the keyboard legend at the top and the row numbers play a central role in the note assignments to the page for page triggers.
Yes, you will not be able to trigger all 144 pages, but I tend to agree with Lars that this is not necessarily the point. Intuitive access to the function is the key and I think that is a good way forward.Quote:but only having access to 127 values makes it a bit ugly.Do you expect to trigger more than 127 tracks/pages in a setup?
The concept of my proposal comes from: Ok I want to trigger this page so I assign it to this note. And then I assign this track to the next note.
Very different from: Ok, to trigger this particular page I have to *reads the manual* play a g#5 on midichannel 14 at velocity 78.
I am not trying to be able to trigger everything there is to trigger at anytime. I just want something that is musical and intuitive.Can you make an example of track triggering that justifies it compared to page triggering? I am just thinking that if I had a track that I wanted to trigger, I would copy it to its own page and then trigger that.
Track triggering would be cool, but I am just trying to picture strong argument for it.I think using midi notes for triggering has huge benefits over anything else (vel, cc, whatever). First of all they are playable. Secondly they are mutatable in so many ways because the midi notes are the "meat and potatoes" of a seqencer.
But IF we say "yes we want track triggering" I think I would suggest taking my plan for "midi note page triggering" and say "you can also link midi notes to tracks the same way as you can link them to pages."
Quote:1. record-loop-overdub.
2. record-loop-overwrite.
3. record-oneshot-overwrite.
4. record-oneshot-overdub (while we’re on it, heh).
5. record-oneshot-overwrite-trigger.
6. record-oneshot-overdub-trigger (while we’re on it, again).
7. etc.The way I understand Ripe, #3 & 5 does not make sense to me. Are we not agreeing that the only thing that is overwritten is stuff that has been recorded earlier in the same take? So if you have "one-shot" there will be nothing to overwrite.
If you by "overwrite" mean that whatever is on the track when you begin the recording is erased, I dont see the point. For this you just use track CLR before record.Regarding loop-overwrite:
What is it (exactly) that you want to accomplish.
I try to picture myself using it: Drum beat is playing, and I am recording a bass searching for the perfect bassline. So everytime I come to the end of the bar, I have to take a split second decision if that was the right take, because if I dont, it is being erased right away. No, sorry, I fail miserably at trying to picture a use for it.The trigger modes: Well, I can see that they would have a function that is new, and as long as the mode would not complicate what we have, I won´t object, (but I would never use it.)
This feature would take care of that (and more!):
http://genoqs.net/index.php?option=com_joomlaboard&Itemid=50&func=view&id=375&catid=3Ok, is works only on page level, but it covers a lot of ground IMHO.
Post edited by: LDT, at: 2008/05/08 21:41
That’s a nice one! I still need to validate how and that it works technically. Do like it though..
By the way – the recording undo now works in MIDI slave mode as well.
Post edited by: gseher, at: 2008/05/12 23:06
Ok, now I see why I thought this was not working at all: Typicly I copy a step into an empty space, and that does NOT work. But yes, In the way you describe, you can copy one step to an already active step, but isn´t that a bit amputated?
And further: Now that I found out how it is intended to work, I thought: Ok, an advantage of using the SEL button here could be that you easily can select several steps across tracks, and then copy them, but no, it is only possible to copy one step at a time.
So my thought is:
Either fix the current behavior so you can paste into non-active steps AND add multistep copy. Or: Make step copy work without the use of SEL (and forget multistep copy).Ok, now I see why I thought this was not working at all: Typicly I copy a step into an empty space, and that does NOT work. But yes, In the way you describe, you can copy one step to an already active step, but isn´t that a bit amputated?
And further: Now that I found out how it is intended to work, I thought: Ok, an advantage of using the SEL button here could be that you easily can select several steps across tracks, and then copy them, but no, it is only possible to copy one step at a time.
So my thought is:
Either fix the current behavior so you can paste into non-active steps AND add multistep copy. Or: Make step copy work without the use of SEL (and forget multistep copy).Quote:If PLAY were automatic you would not be able to recall more than just back to the last move.Yes I know, but even one level of undo can be a lifesaver.
This just occured to me:
The normal operation could always have one level of undo available. (This undo could be performed by e.g. a doubleclick on PLAY (not > ). The PLAY function as we know it, we don´t change at all.
So if you decide to use PLAY, you dont have the normal one level undo, but off course instead you have the PLAY function.Post edited by: LDT, at: 2008/05/08 11:05
The way it works in page is not as fast as grid, but still.. Hold SEL and press the step you want to copy (it has to be toggled on). Press CPY.
Select the destination step in the same manner and press PST. This should move your step across.Quote: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.Well it might be what I am looking for, but I dont really know what you are talking about now, haha.
Are you saying that in page mode you can copy/paste individual steps? I did not know that. I just went through the Page chapter of the manual (also searched in other chapters) but I can´t find any info. Please tell…
Anyway to point out what I am looking for:
You know, in Grid mode you grab a page, press CPY, grab a destination, press PST, and you just copied a page.
I am looking for exactly the same in Page mode. The same intuitive imidiateness to step copying.
As it is, I have gone into Step mode every time I wanted to copy a step, but it sounds like there is something I may have overlooked?If PLAY were automatic you would not be able to recall more than just back to the last move. Unless you would throw significant amounts of memory at it, which is better used otherwise
Using two modes of PLAY however could be an option, in theory at least. I would have to evaluate if it is feasible in practice though.
