RC v6 and we want to know what you want to see in V6!

[musicdevelopments]

Is it possible to add another entry to this dropdown for 'Bar.Beats.16ths' only please.?

Also is it possible when using both Bar Position + Timecode displays to keep the top, primary in 'large' format (like above picture), instead of reducing both to the same point size (below pic).?

Dear thebutler,

thanks for posting! Today I improved the timecode display. Not just "Bar.Beat.16ths" and "Beat.16ths" were added, but now it is possible to adjust the timecode font size and color, as on this picture:

PS:- Also I'm sorry, but I have to say, this whole area seems to just visually merge into one similar 'blob' of information, with little to separate/distinguish each from another - especially when choosing to display both primary and secondary options here... Something to think about - or see if others/newcomers are that bothered by this like me...

I am not sure if the above improves the situation, but I am all ears, if anyone has an idea to reduce the clutter...

Thanks,
Attila

[musicdevelopments]

Instead, could RC contain a (very simple) HTTP server for a REST API, which would allow each named entry in the "Keyboard Shortcuts" list to be invoked by name. E.g. The Stream Deck button would send URL http://localhost:NNNN/key/Cut+track and RC would do the "Cut track" action as though triggered by a keystroke.

This is a very interesting idea!
Thanks, Brian!

[musicdevelopments]

* Wasn't sure if this topic superceded Feature Requests so I've put in both.
Hope this is ok.

Hi Mike,

of course! Unfortunately recently I do not have much time to read the forum.

Hi Attila.
Is this Possible?

When using the neural network to create / continue a song, can there be a dropdown: "Absolute", "Chord Relative", "Scale Relative" that automatically adds the pipeline for right clicking the phrase after creation and converting to relative forms (If not set to Absolute). Absolute being the default unless a global preference can be set by the user.

You are right, this is badly needed. It was planned, but did not fit into the new v6 version. I want to implement this for v6.1. I'll do my best to upload a beta version before the end of year, because a few features have already been added.

Thanks!
Attila

[Mykyndryd_]

You are right, this is badly needed. It was planned, but did not fit into the new v6 version. I want to implement this for v6.1. I'll do my best to upload a beta version before the end of year, because a few features have already been added.

Thanks!
Attila

Brilliant. Thanks Attila. look forward to it.

[thebutler]

Dear thebutler,

thanks for posting! Today I improved the timecode display. Not just "Bar.Beat.16ths" and "Beat.16ths" were added, but now it is possible to adjust the timecode font size and color,

Wow.! That's really great Attila - thank you; you've done even more than I was hoping for.!

As regards improving visual 'clutter', what you've done here does look like it will help, but for me, more change is needed in this overall 'area' of RC's main UI. I will have to think on (and see what others say too).

I'm no visual artist or photoshop expert - but I'll see if I can put together some cut-n-paste mock-up pictures, to help the conversation along.

(PS:- I'll wait until an update with this latest improvement is included - I can play with sizes, colours. layouts of the Timecode display, to see how that affects/changes things).

[shiningstarswwsj]

Hey Attila,

I got one more idea related to chords.
It would be really useful to be able to non-destructively stretch/extend the selected chords to a target bar range (for example, stretch the highlighted chords to fill up to bar 16), and also the reverse (compress them back to bar 4).

It will function similar to time-stretching, but it should work on or just for the chord blocks or just on the harmonic timeline, but it shouldn't rewrite or re-generate the chords while doing so, just visually and musically extending them. This would make experimenting with structure and pacing much faster, especially when trying different section lengths of chords. Maybe holding down the Shift key while dragging could enable this mode. That way it feels fast and can also be edited intentionally.

Chords Stretching Idea.png

Thank you so much!
Shiningstarswwsj

[lulukom]

+1

[thebutler]

I got one more idea related to chords.

Yes.! I like your idea(s) for the chord track too...

Presumably, this would mean notes on all other tracks adjusting accordingly (with the stretch/compress).?

Maybe you would have to choose carefully when in your process you perform this type of experimenting. I can imagine very short notes on an ostinato string track for example, could become 'crippled' quite quickly during this action... But acting on only one track of 'chord' notes, not a problem...

(or perhaps I've misunderstood the request a little.?)

thebutler
(Bob)

[shiningstarswwsj]

Presumably, this would mean notes on all other tracks adjusting accordingly (with the stretch/compress).?

Hi thebutler,

Yes, this is exactly what I was thinking. This should be the main use case, notes on the other tracks should adjust accordingly when the chords are stretched or compressed, so everything stays in sync with the harmonic timeline.

Maybe you would have to choose carefully when in your process you perform this type of experimenting. I can imagine very short notes on an ostinato string track for example, could become 'crippled' quite quickly during this action... But acting on only one track of 'chord' notes, not a problem...

That said, I also really like your second point that if there were an option to limit the action to just the chord track (or choose between “chord-only” vs “affect all tracks”), this option would definitely be a big plus as it can be used with the master track versions to great effect. It would also give users a lot more control over the arrangements and make it safer/ non-destructive to use in different stages of their workflow. I think if this can be implemented as an option, things like short ostinato notes, fast runs, or rhythmic details on other tracks wont get mangled or “crippled,” as you nicely put it. The chords would simply occupy more (or less) time, and the rest of the arrangement could then respond to that as needed (regeneration, follow-chords logic, manual tweaks, etc.).

I totally agree that this is something you’d have to use thoughtfully and at the right stage in the process of structuring the arrangement, as its more for experimentation with structure and pacing than a always-on operation feature.

Thank you for thinking about it and for giving meaningful feedback. I really appreciate the discussion!

Thanks,
Shiningstarswwsj

[shiningstarswwsj]

Hey Attila,

I got another quick workflow idea...
Would it be possible to make the blue automation icon always be visible on the tracks, even when there’s no CC or automation data present yet?

Right now, we have to first add CC data in the MIDI CC's variations lane just to make the icon appear, and then if that CC data is later removed, the icon disappears again, and then we have to go back to the MIDI CC lane, add modulation (or any CC) again just to bring the icon back.

Automation Icon.png

If the icon is always present on all the tracks, it will really speed things up when adding or editing CC/automation events, simplifying expression work. The automation lanes can be hidden but can be easily accessed with this button like the functions in a DAW.

Thanks!
Shiningstarswwsj

[thebutler]

... if there were an option to limit the action to just the chord track (or choose between “chord-only” vs “affect all tracks”), this option would definitely be a big plus as it can be used with the master track versions to great effect. It would also give users a lot more control over the arrangements and make it safer/ non-destructive to use in different stages of their workflow. I think if this can be implemented as an option, things like short ostinato notes, fast runs, or rhythmic details on other tracks wont get mangled or “crippled,” as you nicely put it. The chords would simply occupy more (or less) time, and the rest of the arrangement could then respond to that as needed (regeneration, follow-chords logic, manual tweaks, etc.).

I totally agree that this is something you’d have to use thoughtfully and at the right stage in the process of structuring the arrangement, as its more for experimentation with structure and pacing than a always-on operation feature.

Thank you for thinking about it and for giving meaningful feedback. I really appreciate the discussion!

Ok... now I think we're really getting somewhere.!

I have more thoughts, but I'm tempted to leave it there, allowing/leaving room for others to join in... and of course, to let Attila himself bring in his thoughts (as to how easy/difficult/wise this whole concept is to implement).!

I know he doesn't get time to read the posts in here that regularly, so we may need to leave it a few days (maybe into the new year), before furthering the discussion.

But, very good topic.! And you're right, that creative possibilities could open up quite quickly through this...

Happy festivities.!
Bob

[shiningstarswwsj]

Hey Attila,

I had a small feature request that would really improve the MIDI import workflow.

Would it be possible to add the ability to recognize and save custom chord voicings when importing MIDI files?

Right now, RapidComposer does a great job at identifying the chords, but it doesn’t retain or recognise the actual voicings used when importing midi files. It would be incredibly useful if RC could detect and preserve those voicings as well.

This would help a ton when bringing in ideas from other DAW's or projects, and would save a lot of time recreating the original feel manually.

Please consider looking into this, as I think this could be a really powerful addition.

Thanks again, Attila!

[lulukom]

+1. Yes, that would be great. To see the chord exactly as it was played!