Open Lykdraft opened 7 years ago
I think there's two suggestions here:
Would this make it simpler to use the sequencer?
On Mon, Dec 19, 2016 at 12:08 AM, Lykdraft notifications@github.com wrote:
Hey there,
I have a hard time finding the right words here, I try to explain as good as I can...
First, a typical example how my blocks look when I split the usual pre-Sequencer "one block/all instruments" approach into groups tied to the specific instrument/data group to take advantage of the new sequencer:
As a result, I have something like this: 20 different Drum Blocks 5 Different Synth Blocks 5 different Bass Blocks, 10 different Fx/Fills Blocks and 20 different Automation Blocks.
Combined this makes 60 entries in the playlist... If these are not created properly in an orderly fashion, things tend to get pretty chaotic. Again, this need preplanning to stay organized, but you can't really plan ahead that far when making music. And 60 Blocks in one list is pretty heavy to handle anyways, even with tight project management.
I would propose something to lock a specific selection of blocks to a specific sequencer track. Or some other way, so that on inserting/replacing a block, we only see the blocks that belong to the specific group of instruments/block/data we want to work with.
(Think of multiple playlists or multiple block pools. For example: If we want to change a block which includes notes for a synth-line and we want to replace it with a variation of that synth-line, we only see blocks associated with that specific synth block. )
Maybe this could be at least be made easier via a text-entry mask. I enter "Synth" and I only see blocks with the name synth in them. The text mask could also be configured in a way that the last text entry is still there when re-opened, so that we don't have to enter synth all the time again when searching for the best variation for that specific time/place in the song arrangement.
This issue is personally the biggest problem for me right now with the sequencer. (That's actually why I still don't use it and prefer working the "old" way. More organized.)
Think about this: When comparing Radiums new Sequencer with one that is using a similar restriction-free but more traditional approach a la Ableton this issue is the main difference.
In Ableton (or similar applications), the clip/part management is done by having all clips in the associated track in the Session view. Thus easy to find and to work with. So that's why you don't get confused there.
In Radium that's a different story at the moment because essentially you have all "Clips" ( = Blocks) in one big "Track" (= Old Playlist).
I hope you can understand what I am talking about. I can't articulate exactly what's in my head. :)
Best, tL.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/kmatheussen/radium/issues/780, or mute the thread https://github.com/notifications/unsubscribe-auth/ABF9p6JPFRUT0x0_cDzUoS4dVTLvJJpUks5rJb0KgaJpZM4LQQ0Q .
Absolutely. These are exact the two things I had in mind. Text search for block insert and grouping specific blocks to tie them to a specific sequencer track.
Would make it much easier, because more controlled and organised block pools.
Best, tL.
Hey there,
I have a hard time finding the right words here, I try to explain as good as I can...
First, a typical example how my blocks look when I split the usual pre-Sequencer "one block/all instruments" approach into groups tied to the specific instrument/data group to take advantage of the new sequencer:
As a result, I have something like this: 20 different Drum Blocks 5 Different Synth Blocks 5 different Bass Blocks, 10 different Fx/Fills Blocks and 20 different Automation Blocks.
Combined this makes 60 entries in the playlist... If these are not created properly in an orderly fashion, things tend to get pretty chaotic. Again, this need preplanning to stay organized, but you can't really plan ahead that far when making music. And 60 Blocks in one list is pretty heavy to handle anyways, even with tight project management.
I would propose something to lock a specific selection of blocks to a specific sequencer track. Or some other way, so that on inserting/replacing a block, we only see the blocks that belong to the specific group of instruments/block/data we want to work with.
(Think of multiple playlists or multiple block pools. For example: If we want to change a block which includes notes for a synth-line and we want to replace it with a variation of that synth-line, we only see blocks associated with that specific synth block. )
Maybe this could be at least be made easier via a text-entry mask. I enter "Synth" and I only see blocks with the name synth in them. The text mask could also be configured in a way that the last text entry is still there when re-opened, so that we don't have to enter synth all the time again when searching for the best variation for that specific time/place in the song arrangement.
This issue is personally the biggest problem for me right now with the sequencer. (That's actually why I still don't use it and prefer working the "old" way. More organized.)
Think about this: When comparing Radiums new Sequencer with one that is using a similar restriction-free but more traditional approach a la Ableton this issue is the main difference.
In Ableton (or similar applications), the clip/part management is done by having all clips in the associated track in the Session view. Thus easy to find and to work with. So that's why you don't get confused there.
In Radium that's a different story at the moment because essentially you have all "Clips" ( = Blocks) in one big "Track" (= Old Playlist).
I hope you can understand what I am talking about. I can't articulate exactly what's in my head. :)
Best, tL.