RapidComposer v4 beta feedback and discussion (locked)

[lulukom]

This is so, but we are glad that the new moves us forward and satisfies just human curiosity! ))))))

[sj1]

Q: Is the new official RC 4.2.3 ahead of, equal to, or not as advanced as the last beta?

[milliondabeat]

is there i can solo/mute the left or right hand in the piano chord pattern generator?
i wanted to only use the left hand notes, ive been having to use the limit note range variation to get this to work

[BluGenes]

Q: Is the new official RC 4.2.3 ahead of, equal to, or not as advanced as the last beta?

Hey, just wanted to point out an issue that happens when beta testing RC.. Atilla doesn't name the VST's as a beta version, so, when you install one or the other, (beta or production), which ever is installed last, uses those VST's .. VST's as you know, install in a specific VST folder.

You can, and should be, installing the beta in it's own folder. The beta and production do share the same DB folder and data.

So, depending how you want to work, depends in which order to do the install. For my production "work" I prefer the stable release, so, I install that after the beta. When a new beta comes out and I install it, I re-install the production. (unless the new beta stuff is VST specific, that is)

But, to answer your question, hard to say, unless he tells us about it.. Sometimes, he doesn't, though. I suppose you should just keep a keen eye on the posts and all.

As an example, not all bugs are reported here, but, people just send them via the support in the software.. many times I have found bug fixes that were not reported here.

I am hoping he can further answer your question..

[BluGenes]

Hey, was wondering.. (we may have discussed this before, but, don't remember)....

Is there any reason that we can't have access to the chord builder/circle of fifths, etc., from the chord rules editor?

EDIT: As opposed to having the chord pallet already open from the composition.. Also, from the chord selector, could you add a right click pop up menu to copy the chord name to be pasted into the chord rules editor? (when you select the chord in the pallet..)

I am kind of remembering talking about this, and I know you added something to add to the rules, but, forgot what it was..

EDIT: Ok, found it.. the button on the chord selector -> progressions tab -> Add to rules.. and RC crashed..

need someone else to verify the crash..

[DLate]

Confirm crash.
Windows 10, RC 4.2.3

[BluGenes]

@Dlate ..Hey Thanks

Atilla,..

This probably should be changed for consistency...

The Master Track Inspector's settings for chord rules is not carried over to the Master Track Inspector's settings to generate a progression ..







The blues rules is from a test..

Maybe also possibly, lol, add a setting to enable/disable loading the last edited chord rules to the chord rules editor and maybe consider checks to see if that is the correct rules set in settings, etc., (for a friendly reminder popup to that effect).

Currently, I think, that is the only thing not re-loaded when you enable load last session on startup..
(generally my preference as a work flow, loading the last session.., so, I have that setting on all the time..)

[musicdevelopments]

Thanks, BluGenes and DLate, this bug is fixed now.
Please re-download v4.2.3.

Another strange bug was fixed when using Windows HiDPI scaling (e.g. 150%) in the plug-ins but dragging phrases were drawn using an offset.

Thanks,
Attila

Confirm crash.
Windows 10, RC 4.2.3

[musicdevelopments]

Hi BluGenes,

I'll think what can be done about this, but at the moment the chord rule set for the composition and the rule selected in the inspector has no relation to each other. They are independent, which lets you make a chord progression using another rule than the one used in the composition.

Thanks,
Attila

This probably should be changed for consistency...

The Master Track Inspector's settings for chord rules is not carried over to the Master Track Inspector's settings to generate a progression ..

[musicdevelopments]

Good point, and sorry for the confusion.
While it is easy to install the beta standalone in a separate folder, the plug-ins go to the same folder with the same name. It would be complicated for me to rename the beta plug-ins, so I recommend not to install (uncheck) the beta plug-ins, unless it includes a fix that you need. Or always install the beta plug-ins, keeping in mind which beta or production plug-ins you use. Sorry again!

Thanks,
Attila

Hey, just wanted to point out an issue that happens when beta testing RC.. Atilla doesn't name the VST's as a beta version, so, when you install one or the other, (beta or production), which ever is installed last, uses those VST's .. VST's as you know, install in a specific VST folder.

[musicdevelopments]

The latest fixes are in the the official v4.2.3 version.
I'll do my best to build a new beta version soon.

Thanks,
Attila

Q: Is the new official RC 4.2.3 ahead of, equal to, or not as advanced as the last beta?

[lulukom]

It became more or less clear why the beta is not a version with the latest fixes. Although it's strange to me)))))

[musicdevelopments]

Hold on, I'll build the beta version now.

[lulukom]

[musicdevelopments]

RapidComposer v4.3b6 is available!

You'll find the latest bug fixes in this update.

• 'Phrase lock' should not affect locked notes (e.g. key-switch notes)
• Fixed chord rule selection from menu when magnet was 'off'
• Fixed a crash when clicking on "Add To Rules" for an empty chord progression
• Fixed a crash when removing chord progression from the Idea Tool progression list
• Melody Editor: crashing issue when resizing the last chord fixed
• Melody Editor: chords track length issues fixes (when adding/removing motives)
• Melody Editor: playback option to play the chords track together with the melody