RapidComposer v4 beta feedback and discussion (locked)

[musicdevelopments]

I am not sure what is going on, because I was able to scan the last entry in the log file, Korg WAVESTATION.vst3. I suspect that the loaded plug-ins somehow remain in memory and that causes the crashes. I am doing further tests.

Yes, there is no blacklisting but it should not be necessary.

Apart from scanning issues, normal VST3 usage works well, right?

Thanks,
Attila

Here's another log of VST3 scans. This one got further.

Offhand, the problem does not seem to be that a specific plugin(s) is causing RC to quit.

[musicdevelopments]

Yes, in the next beta version.

As requested, the 'lightning' button is added to the top toolbar, when the Idea Tool was already used

Great! This is in the upcoming b6?

[lovemusic15]

Thanks for the video! Please keep it available as I will need to watch it again and make notes.

I know OpenAI somewhat (I am a ChatGPT user, thanks to BluGenes) but they have models pre-trained on a vast amount of text from the internet, so that is not usable for music.

Thanks,
Attila

I second that Mike anything to do with midi learn is 100% the next step for RC.
I put a video together to demonstrate some of the features that could be beneficial from anyone wanting to work with their own midi phrases.

No problem I will leave it up there for as long as you need it.

Just saw something about the idea tool
No big rush for this as I know you're busy but would it be possible to have the option of applying rhythm to all phrases, that way you get the same rhythm with the Bassline chords and Melody. Would be a great time Saver.
So basically if you only drop rhythms in the bass section any other phrase with follow that same rhythm.

Also in the phrase list is it possible that once it's played one of your custom phrases that it automatically removes itself from the list, so that way you don't use it again when hitting regenerate.

Thanks

[sj1]

Hi.

Here is a video showing the small lightnings in the Idea Tool failing to generate.

https://www.screencast.com/t/ra4Dg3pc

I've attached my file, in case that helps.

BTW, these problems persist in 4.6b6.

[musicdevelopments]

Hello sammlin1122,

welcome to this forum!
I am not sure I can answer your question because I am not really a composer, but if you have a motive, that means you can use it with any chords, apply non-destructive variations on it, like changing its rhythm, inserting connecting notes, simplifying it, freely transposing or stretching it, or slicing it and rearranging the slices.
I recommend studying the available variations that you can use. Since variations are non-destructive, you can disable them anytime without changing the original motive.

Thanks,
Attila

Hello everyone, I am new here and got a few motifs or themes for my violin concerto, and wonder if this RapidComposer would help develop the motifs and themes to a longer section with logical melody development or at least help create more options for music/melody development. Thank you.

[musicdevelopments]

I am wondering if anyone still uses 32-bit executables or plug-ins on Windows. I am thinking of dropping support for 32-bit in a few months.

Thanks,
Attila

[musicdevelopments]

RapidComposer v4.6b6 is available!

In this update VST3 plug-in scanning became faster and more reliable, because plug-ins are not fully instantiated during scanning, but only to an extent that allows requesting some vital information about them.

Improvements:

• Searchable lists for plug-ins, settings, keyboard shortcuts, UI colors
• Faster and more reliable VST3 plug-in scanning
• Plug-in list offers multiple selection so that you can remove multiple plug-ins at once
• Idea Tool 'generate' button is always displayed after using the Idea Tool
• Fixed occasional duplicated items in the plug-in list

[sj1]

re 4.6b5:

[*]. Added a button for timeline selection in the structure inspector

Super. In the context of the Structure Browser, this is perfect IMO.

[sj1]

Back in the context of the Primary Composition, I suggest making use of right-click and shift-right-click for timeline selection of Line and Part areas.

RC - Timeline Selection Suggestion 01.jpg

I think this would partner very well with the new Big Lightning availability for the most rapid possible selection and regeneration of specific portions of the composition.

I know we can double-click into the zoomed view and operate there, and I do! I just also think that being able to stay and operate in the highest context while looking at it is desirable to have.

[sj1]

I hope the single-track lightnings and lightbulbs can be fixed soon, that's the main stumbler right now for me.

When/while attention is on that, I recommend adding shift-click on a lightbulb to act as a solo function toggle for lightbulbs (with an exit from lightbulb solo returning us to the prior pre-solo state).

[sj1]

RC 4.6b6 - VST3 plugin scan completed successfully. Yay!

I see that all plugins listed from scan create with the Multi-timbral Plugin indicator checked. This is opposite from the default I would prefer. (I realize others may like it.) Could we get a button to uncheck all of them at once, rather than having to do it one-by-one after any/every scan?

[sj1]

Also, could we get a remove all button? If we want to "start from scratch" we currently have to remove one-by-one pages and pages (in my case!) of plugins.

[sj1]

I'm also noticing a fair amount of double-entries.

I'm not sure if this is because some were already there and then the comprehensive scan re-detected and duplicated them, or if the comprehensive scan produced doubles on it's own.

Figuring this out and cleaning it up is one reason "start from scratch" can sometimes be desired.

[sj1]

BTW, if we do use a plugin in a Multi-timbral way, where do we set the MIDI channel upon which RC will send for a given track?

[musicdevelopments]

Wow, if scan completes successfully, that is great!
In this update multiple selection is possible in the plug-ins list, so use Shift-click to select all and click on the Remove button to start from scratch.

The reason for duplicate entries is because the VST3 SDK returns pathnames with forward slash on Windows. In this update all path names are converted to use backslash.
Collecting plug-in paths is built into the VST3 SDK, which is very useful.

Thanks,
Attila

Also, could we get a remove all button? If we want to "start from scratch" we currently have to remove one-by-one pages and pages (in my case!) of plugins.