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

[lulukom]

Thanks Attila!
I would ask you to pay attention to dragging midi files along with the controllers. There are probably problems here ..

[BluGenes]

vst3 still crashes.. on open and close phrase browser..

[musicdevelopments]

Hi BluGenes,
IIRC you like to open the browsers in a separate window. I am using the VST3 with Reaper on Windows10 so far I could not make it crash. What shall I do?
Thanks,
Attila

[BluGenes]

k, lemme check something..

[BluGenes]

This is my settings currently for RC... (the browsers, etc..)

To make it crash.. add the vst, then open the phrase browser.. Close the phrase browser, then close the FX window containing RC.. re-open FX window then click phrase browser..

[sj1]

Hi,

Trying out the RapidComposer 3.9b19 new {chord} track names and MIDI export, I am experiencing these issues:

1. {chord} track name uses all the chords, ignoring the timeline selection. This "too long" name propagated thru to the exported filename. However, the actual MIDI notes in the exported file seem correct, and limited to the timeline selection range.

RC Selection Ignored 01.jpg

RC Notes in Bitwig.jpg

2. RC 3.9b19 crashes loading a file that used to load OK.

SJ_Summertime_01b.zip

[sj1]

BTW, if it is possible to set the Forum here to allow files with the .rcCOMP extension to be uploaded, that would be a minor convenience. <g>

[sj1]

Also, FWIW, considering the name format of the exported MIDI files, we currently have:

"RapidComposer-Dm7 - A7 - Dm7 - G7 - Abdim - F6 - Dm7 - Em7b5 - A7 - Dm7 - Em7 - A7.mid"

I would suggest the example above become:

"RapidComposer_(Dm7 A7 Dm7 G7 Abdim F6 Dm7 Em7b5 A7 Dm7 Em7 A7).mid"

or even just (perhaps optionally as a preference):

"(Dm7 A7 Dm7 G7 Abdim F6 Dm7 Em7b5 A7 Dm7 Em7 A7).mid"

Reasons:

a) the shortest, readable filename is generally to be desired at the ultimate import destination, where real-estate matters

b) if it's possible to avoid needing subsequent filename editing after the export, that's desirable

c) if/when the user does need subsequent filename editing after the export, being able to automate same is very desirable (i.e. with RenameMaster). This requires consistent patterns for different parts of the name.

d) marking the left and right sides of the chords themselves with the parens assists with c).

e) using a single space between the chords (and nowhere else) is consistent with a), and allows c).

Tweaky as heck, right? But I hope you follow the motivations here ...

Thanks!

[musicdevelopments]

1. {chord} track name uses all the chords, ignoring the timeline selection.

Ouch, I did not know that only the selection should be used. I corrected the behaviour.

2. RC 3.9b19 crashes loading a file that used to load OK.

Thank you, based on the uploaded file, I could fix this quickly.

Thanks,
Attila

[BluGenes]

sent pm..

[musicdevelopments]

OK, I removed the "RapidComposer-" prefix from the dragged filename. The track name is enough.
If you want parenthesis around the list, you write ({chords}).
I try to add a setting for the preferred chord list format.

Also, FWIW, considering the name format of the exported MIDI files, we currently have:

"RapidComposer-Dm7 - A7 - Dm7 - G7 - Abdim - F6 - Dm7 - Em7b5 - A7 - Dm7 - Em7 - A7.mid"

I would suggest the example above become:

"RapidComposer_(Dm7 A7 Dm7 G7 Abdim F6 Dm7 Em7b5 A7 Dm7 Em7 A7).mid"

or even just (perhaps optionally as a preference):

"(Dm7 A7 Dm7 G7 Abdim F6 Dm7 Em7b5 A7 Dm7 Em7 A7).mid"

[lulukom]

or even just (perhaps optionally as a preference):

"(Dm7 A7 Dm7 G7 Abdim F6 Dm7 Em7b5 A7 Dm7 Em7 A7).mid"

+1

[musicdevelopments]

In the next update you'll be able to specify what to use for separators between chords.
Selections are:
<space>-<space>
<space>
,<space>

This is also used for displaying chord progressions.

[lovemusic15]

Hi Attila.
just downloaded the new beta update, can you please fix it so I can use more than one instance inside Ableton.
I never use RC as standalone, all of my projects open with at least three instances of RC but now can't use any because of this new RC.

I want to be able to use this with all of my effects and filters that I have in my Ableton projects.
I would even be happy to go back to using the old RC if they had the new modern rhythms inside the generators.

Thanks

[musicdevelopments]

Hi Dam,

I'll do that, but it is not a simple fix.
If you want to use 3 plug-in instances because you need 48 MIDI channels, you need to wait until it is implemented.
Otherwise please check Mike O'Connor's videos about setting up RC in Ableton:
viewtopic.php?f=285&t=503538

Thanks,
Attila