RapidComposer v5 beta feedback and discussion

[lulukom]

Hello Attila. Thank you very much for the shortcut (collecting scales). There is one subtlety.. When I select a scale for my monophonic phrase, I always need to find a euphonious transposition by scale step.. but at this moment, when I start adjusting the transposition slider in the track head, the menu (collect scales) closes ((Please make it possible working with the open menu (collecting scales) and adjusting the sliders in the track head. This is important. Thank you.

[BluGenes]

Missed saying in email Atilla, add a 10 second timer on shutdown, see if that works..

[BluGenes]

[deleted]

[sj1]

Improvements:

Keyboard shortcuts added for forward/rewind

A minor point of terminology consistency -

Since the keyboard shortcuts for these, as implemented, are found by a search on the words"forward" and "rewind", then those words should appear in the tooltip pop-up help for those buttons.

The idea is that a user can read the tooltip help text and derive keywords to search on in order to find any shortcut that exists.

Thanks very much for adding the feature, it will help my life every time I open the program!

[musicdevelopments]

RapidComposer v5.2b2 is available!

BluGenes found a nasty bug when loading compositions with VST3 plug-ins (thanks! ). This update has the fix.

Improvements:

• "Modify existing phrase by AI" added to Phrase Editor
• Fixed hanging when loading another composition with plug-ins

[BluGenes]

Ahh, thanks Atilla, was an easy spot.. anyways..

If you could, maybe fix this when you get a chance... The scale choices don't quite match the master track compared to the AI Chord rules.. If you could add the missing scales to the AI pop up, that would be so cool.. if not, no problem.. kind of trivial really..

Master Track view



AI View

[sj1]

About Roman Numeral (RN) notation -

I seem to be observing that RN is calculated locally.

IOW, regardless of the key/scale we have set for the composition as a whole, if the scale in effect at some measure is different then the RN calculation for that measure follows this local scale rather the key of the piece.

Possibly some users may want this, but to me it is usually problematic. I typically want RN to be consistent (to a single key) for the whole piece. That is somewhat the point of it, IMO.

I did not really notice this before in my own work which typically did not change scales across a piece, but now with AI progression generation, where different Scales are sometimes inserted at points in the piece by the AI, I notice that RN no longer is "anchored" to the key of piece and this messes up my ability to follow it as I am used to.

So, to me, in the Key of E, a D7 = bVII7. With E mixolydian scale in effect, RC is reporting D7 = VII7.

Granted, we may have different scales in effect at different points in a piece in order to guide automated generation and relative-to-absolute instantiation. This is certainly an important feature.

But should the RN representation be a constantly moving target? I don't think so. (What do others think?)

To me, in "E", a chord built on "D" is built on "bVII".

IOW, the RNs are really meant to be just relative to the root itself, like so:

I bII II bIII III IV bV V bVI VI bVII VII I

I could put any scale in effect at any point for generation purposes, but if the piece is in E, I want to see the RNs as above.

This post is getting kinda long. My goal is not to start an argument or mess up anyone else, so I suppose this is a request for an optional setting that will anchor Roman Numeral notation to the root note of the key of piece as opposed to the local scale-of-the-moment.

Thanks.

[sj1]

Visual example for reference:

RC - Incorrect Roman 01.jpg

RC - Incorrect Roman 03.jpg

[BluGenes]

Hey Steve, just for the fun of it, use a chord rules and make sure of that they evaluate to that example. I'll try that myself soon.. that might be all that is needed, the correct rules to follow..

[musicdevelopments]

If you could, maybe fix this when you get a chance... The scale choices don't quite match the master track compared to the AI Chord rules.. If you could add the missing scales to the AI pop up, that would be so cool.. if not, no problem.. kind of trivial really..

I omitted those scales deliberately; I don't think AI can make chord rules for Major Set, etc. Some additional explanation would be needed to be sent with the prompt, e.g. listing the possible scale notes.

Thanks,
Attila

[lulukom]

Hello Attila. When I install a shortcut (in particular, “collect scales”), the shortcut is not saved after restarting the program. Thank you .

[musicdevelopments]

About Roman Numeral (RN) notation -

I seem to be observing that RN is calculated locally.

I understand what you mean. Yes, it would be a good feature.
For evaluating a roman numeral (or universal) notation chord, the 'current' scale is used. For this feature not just a 'current' but also a 'root' scale must be used. This is no small internal change.

In version 5.0 the scale representation was reworked and became amazingly flexible. Other than specifying the scale notes, there are other settings too:



One of them is how to name the scale notes. You can set a different scale or notes for naming them. For example this lets you use the major scale to name minor chords as: Im, IIdim, bIII, IVm, Vm, bVI, bVII

As a workaround, you can change this in the scales you use in the scale browser (right-click on a scale). I can add a setting for this for users who always want to use the major scale as the reference for naming notes, if there is demand for this.

Thanks,
Attila

[musicdevelopments]

Hello Attila. When I install a shortcut (in particular, “collect scales”), the shortcut is not saved after restarting the program. Thank you .

I don't know, it works here on macOS and Windows too.
I assigned key 'D', exited the program. When I started it next time, 'D' was assigned to 'collect scales'.

Are the settings correctly saved, e.g. when you change something else?

[lulukom]

Doesn't save for me. Maybe I don't know about the existence of saving settings?

[lulukom]

Maybe this has something to do with unexpected terminations of the program?