v3 Beta Feedback And Discussion (Bugs, Features, Suggestions)

[BluGenes]

Nice change to chord selector, however.. you lose the ability to change notation style if you add more scales..

[BluGenes]

found a phrase inspector bug and will have to show it in my next "what's new" video.. just a heads up..

[sj1]

Hi,

On Windows, got a crash when I unchecked the new 'Use Smaller Chord Buttons' for the Chord List.

RC - Use Smaller Chord Buttons.jpg

[sj1]

I just realized something that would be amazingly helpful for composing. I'm not sure if it is currently possible or not. If so, could someone please advise me how to do it? If not, I really think this would be a powerful feature.

Constrain Chord Progression Generation by Note Filter

IOW, very similarly to how the Note Filter can be used to limit the displayed chord choices to only those chords which contain the notes in the filter (e.g. notes D and E, as below)

RC - Notes Filter 01.jpg

let the user auto-generate a progression where all the chords in the progression have the same constraint.

One step better than that would be to allow individual chords to be locked (kept) while the auto-generation is re-invoked to get rid of the ones the composer does not want to use at the moment.

This would allow very quick convergence on nice progressions that share a "character" (sound, texture) of having the specified notes in common.

[sj1]

don't forget custom chords for chord rules!

RC give us a huge library of chords to work with, but of course it is effectively impossible to pre-categorize and database every conceivable chord (combination of notes considered together). Hence composers have the desire to be able to define their own custom chords even in the presence of a very large chord library.

Isn't the real need for custom chords themselves? What I mean is that if RC provided a UI which allowed the user to create his custom chords as desired, represented and databased just exactly as the RC built-in chords are (but presumably in a separate parallel user custom chord database that functions as an addendum to the built-in chord database), then the use of the custom chords in rule definitions, or anywhere else in the program, would fall into place almost automatically.

What I'm suggesting is that it's not a new rule thing (UI, or capability) which is necessary, but a new Custom Chord thing (UI, and capability).

Does that make sense?

[BluGenes]

don't forget custom chords for chord rules!

RC give us a huge library of chords to work with, but of course it is effectively impossible to pre-categorize and database every conceivable chord (combination of notes considered together). Hence composers have the desire to be able to define their own custom chords even in the presence of a very large chord library.

Isn't the real need for custom chords themselves? What I mean is that if RC provided a UI which allowed the user to create his custom chords as desired, represented and databased just exactly as the RC built-in chords are (but presumably in a separate parallel user custom chord database that functions as an addendum to the built-in chord database), then the use of the custom chords in rule definitions, or anywhere else in the program, would fall into place almost automatically.

What I'm suggesting is that it's not a new rule thing (UI, or capability) which is necessary, but a new Custom Chord thing (UI, and capability).

Does that make sense?

yes, makes sense, but, there is the chord builder for that already. With the chord builder there are also some "presets" as well.. Look at at the chord selector/ builder tab.. Once used, they are marked "Custom" in the progression.

You can't auto generate those custom chords because they are not able to be added to the rules.

[sj1]

yes, makes sense, but, there is the chord builder for that already. With the chord builder there are also some "presets" as well.. Look at at the chord selector/ builder tab.. Once used, they are marked "Custom" in the progression.

You can't auto generate those custom chords because they are not able to be added to the rules.

Thanks, I think I track that.

So a custom chord as made like this:

RC - Custom Chord for Chord Progression 01.jpg

is instantiated in the composition in which it is created, but not added to any permanent database and thus not available to other areas of the program in the way that the built-in chords are. (?)

If I'm understanding correctly, then I see two possibilities -

1. Coding to make such custom chords known only in the composition they were created in (incl. being available to rules built in that composition)

2. Coding to database such custom chords and thus make them permanently known to RC always and anywhere (incl. rule construction in any composition thereafter).

[sj1]

I could also see utility in letting the user assign a custom name to custom chords.

[sj1]

I could also imagine it would be quite cool if users could export and post their custom chord libraries for others to import ala the way we can post phrases, progressions, and so forth.

[BluGenes]

Actually, once the chord is in the progression, just add it to the progression browser..(your data base).. You can add multiple chords, or just a single chord.

And while I was working on this response, I actually found a way to add custom chords to chord rules. I will have to watch a video I did a while back to see how I got the error preventing this to be sure though.. stay tuned.. lol

edit: naw, I was wrong.. The reason you can't add a custom chord to the rules, is, it has to have a standard notion style name, for now..

[sj1]

Actually, once the chord is in the progression, just add it to the progression browser..(your data base).. You can add multiple chords, or just a single chord.

Interesting! When I use the Drag! from any of the sub-tabs of Chord Selector - > For Chord Progression then the drag drags all of the chords , regardless of their selection (highlighted) status.

So to "add ... just a single chord" I have to have a one-chord progression?

It would be helpfully flexible when following your tip to be able to select a subset (e.g. just one, the custom one) for dragging as a singleton into my own Progression database. If not arbitrary subsets, then perhaps just making single chords directly draggable into the Progression database could be done at a future point.

I will still note though that while having single chords available as progressions can arguably cover most (if not all) common use cases, its not the same thing as ultimately incorporating custom chords into the program "just exactly like" the built-in chords. Certainly though the existing ability to work via the Progressions database as described makes this non-urgent. Thanks for pointing it out in this context!

[BluGenes]

I edited my previous post when you posted.. so, look for the edit..

for a single chord, I was incorrect.. minimum two chords via the master track inspector...

[musicdevelopments]

Hi Steve,

This is annoying. I could not make it crash. Can you reproduce it? Does it always crash, or it happened just once? I checked everything carefully, I cannot see how it could crash

Thanks,
Attila

Hi,

On Windows, got a crash when I unchecked the new 'Use Smaller Chord Buttons' for the Chord List.

[musicdevelopments]

I am following your discussion about custom chords with great interest

Nothing prevents you to define your own chords:



Caveats:
(1) you can use the same note multiple times (like in a complex voicing) but at the moment the root must be the lowest in the chord, so you cannot go under the root. I could fix this for v4.0.
(2) it would be great if the UI would allow you to use/define/save/preview custom chords from basically anywhere
(3) there is an artificial limit of addressing 7 chord notes (e.g. chord generator can display 7 notes) but this can be easily increased

[BluGenes]

Ya, forgot about that as pictured above.. What ever it takes to get those into the chord rules... I am basing this on the what chord rules define as a requirement to be in the rules, traditional naming.. would that count, e.g. "sw"? If so, problem solved..