RapidComposer v4 beta feedback and discussion (locked)

[musicdevelopments]

Hi Attila. I think, after all, quantization of midi controllers does not work.

Hi lulukom,

I don't know, it works when I tried. I prepared a GIF about the same configuration:



Can you send the file to me in e-mail so that I can check what is wrong?

Thanks,
Attila

[musicdevelopments]

I recently purchased the full version of RapidComposer. How can I participant int he beta?

Hi Ebony,

Welcome to this forum!
I am going to send you the beta links in a few minutes, as well as additional resources for RapidComposer.

Thanks,
Attila

[musicdevelopments]

RapidComposer v4.7b3 is available!

So that we all have the latest update, with bug fixes that went into v4.6.1.

Improvements:

• New experimental feature: "Sync to DAW" in the Phrase Editor. Enable it under Settings / Miscellaneous. When enabled, right-click on the PLAY button in the Phrase Editor to find the "Sync to DAW" check-box
• [Plug-ins] Fixed hanging notes during phrase preview when selecting a phrase
• (in v4.6.1) Fixed: 2/4 grid lines disappeared when zooming
• (in v4.6.1) Fixed: VST3 plug-in resizing to a bigger size resulted in black areas
• (in v4.6.1) Fixed a bug when auto-harmonizing many phrases at once

[ebbownee]

I recently purchased the full version of RapidComposer. How can I participant int he beta?

Hi Ebony,

Welcome to this forum!
I am going to send you the beta links in a few minutes, as well as additional resources for RapidComposer.

Thanks,
Attila

Thank you. mI've had classmates (Full Sail University) tell me about RapidComposer. They use it on PC and MACs. I'm on a MAC and It continues to crash Studio One 6, constantly. I've tried using it in standalone mode as well and not a VST, same ordeal. I was hoping the beta would fix the crash issues. I reached out to my friends that use RC and with updated windows and MAC systems, their RC works without any issues. It's odd to say the least, 200 dollars US on software that crashes is no bueno.

[BluGenes]

Quantize was working for a minute, and unfortunately, it stopped. I missed what I did to make it stop working..

[lulukom]

Hi Attila. I'm sending you a composition with one ) phrase and in beta 7.3 where midi controller quantize variations don't work (as in your GIF).

[BluGenes]

Ok, so, yea, it is working for me. I think it depends on the phrase itself. If the phrase is already on the mark, sort of speaking, then there is no need to quantize, it seems. What I did was drop a melody generator down, added some modulation in the phrase editor, then applied, it would not quantize. However, when I edited the phrase and move some notes off a bit, it did quantize with the CC's.

[lulukom]

Thank you BluGenes, I think you are right. Other phrases work.

[lulukom]

Crashes are sometimes present.

[sj1]

Hi.

I'm noticing that a left-click on the Master Track will give me dice if two (or more) chords are selected.

RC - Two Chord Dice 01.jpg

but dice will not be available if only one chord is selected.

RC - One Chord No Dice 01.jpg

Is there a compelling reason for this?

If there is not, I would find it helpful (and consistent) if dice were available in all cases, including the single-chord case (which of course already includes all the other (6 icons) single-chord selection capabilities.

[BluGenes]

That's for generating a random chord progression. You of course, need more than one chord for a progression. That is part of the quick suggestions for chords.. for a single chord, try the mystery button, as I call it.. lol, the question mark.

[sj1]

This all-cases use of the dice request also has a relation to separating timeline selection from loop selection.

( viewtopic.php?p=8611118&hilit=loop#p8611118 )

It's a workflow thing, relating to quickly finding and auditioning chord progressions for song sections with RC.

Consider this example:

RC - 4 Chord Context for One or Two Chord Search 01.jpg

The first two chords (VIm7 II7) have been vetted and are as-desired.

The next two chords are TBD.

In order to determine them, they need to be heard in context.

IOW, all 4 measures need to be a playback loop for auditioning, while the trailing two measures (or perhaps ultimately just the 4th measure) need to be the "timeline selection" used for regeneration/randomization (i.e. dice, in this example).

I think these two suggestions implemented together will enable a superior discovery workflow that is quite desirable and not possible today.

[sj1]

That's for generating a random chord progression. You of course, need more than one chord for a progression. That is part of the quick suggestions for chords.. for a single chord, try the mystery button, as I call it.. lol, the question mark.

The question mark pops up the Quick Suggestions:

RC - Quick Suggestions 01.jpg

which is great, but not the same thing as the instant generation provided by the dice.

Interestingly, if we go one level deeper by clicking on 'More Suggestions ...' we get dice!

RC - More Suggestions 01.jpg

I know I would find it both consistent and rapid to be able to just use the dice in the first place (when desired), operating on the same level in all cases without having to drill down for the special case of the semantic distinction between "chord" (singular) and "chord progression" (more than one).

[sj1]

BTW, it seems there is a failure to sync-up (visually? generatively? both?) when the user chooses to change (by clicking on it) the rule set initially presented in the drill-down.

RC - Rules Mismatch 01.jpg

Under current conditions, I can't tell what rule set is actually going to used when those dice are pressed.

Fixing this sync-up would be good (and I support that if this layout remains), but being able to invoke the dice for a single chord from the very top (while using the current rule set) would successfully avoid the whole issue.

[sj1]

Here is a future wish:

Add a wizard that would analyze whatever chords are in the Master Track and generate a new Chord Rules Set (CRS). The user could then further edit the CRS to expand it out.

One contemplated use would be to type or drag in chords from any desired source (e.g. a known tune), generate a CRS, try out using that CRS and then add to it to expand it (either manually, or with another merged import) until it is working well. At that point you have a new, cool custom CRS derived from a specific genealogy. Rinse and repeat, growing your CRS library.

This would work especially quickly in combination with MusicXML chord import.

Ah, well, it seems like yet another case where RC is already there and my working knowledge of what's available is trailing behind!!

RC - Add Chords to Progression Rules 01.jpg

Love this program!

The part about how slick it would be to add chord importing via MusicXML still applies <g>.