RapidComposer v5 beta feedback and discussion

[musicdevelopments]

Hello Attila. Let's do everything in order.. User Fonts don't work for me. Pictures as proof (of course I did, I rebooted after changing fonts ))

I am afraid you have to enter the full path to the font file, and it will work.

Thanks,
Attila

[musicdevelopments]

Food for thought.

https://www.kvraudio.com/news/bitwig-an ... rmat-58830

Yes, I have seen this. I want to support this format, because it is indeed a good idea.

[musicdevelopments]

Think I'll have to get in touch with the developer of this plug in and complain that it won't load into RC.. lol it was black listed.

[musicdevelopments]

RapidComposer v5.0b12 is available!

As I see RC v5 is in good shape now.

Improvements:

• Rhythm editing improvements: velocity is displayed in notes as a velocity bar (optional, see settings under Miscellaneous / Rhythm Editing)
• Rhythm editing improvements: immediate velocity setting when resizing or moving a note (optional, see settings under Miscellaneous / Rhythm Editing)
• Slightly improved color scheme for displaying note velocity
• Plug-in scanning and blacklisting options menu added to the plug-ins page. You can skip found and/or blacklisted plug-ins
• Fixed bug with blacklisting: when RC crashed, the blacklist was not saved, so it contained a single entry
• Fixed preview instruments when soundfonts were used
• Fixed: custom rhythms folder was set to FactoryRhythms
• 'Regenerate' was changed to 'Set generator length' for clarity in the Phrase Inspector

[BluGenes]

working pretty good.. had crashes on 2 VST's, they were black listed and skipped.. so, that is working..

But, I think you need to figure out a way to catch the crash instead of passing the crash off to the OS. I got the now getting old to me Windows close program dialog. I would think something needs to be added in your main.cpp in the lines of a "try.. catch", then exit to the OS gracefully.

It will always have a crash problem there in the scan, so, I would try to polish that turd as best as possible. lol

You will always get complaints in support there every time from new users, so, really needs to be addressed now while it's fresh.

[musicdevelopments]

Yes, you are right and you see things right with the try...catch, which was used in old versions, but C++ exceptions are turned off now in the whole project. I think it is possible to enable exceptions in just one compilation unit as long as I handle the exception in it, so I'll try that.

[sj1]

On b12 now.

Definitely moving forward scan-wise!

Here is one observed situation, probably rather rare:

RC - entry point not found 01.jpg

The scan reports a Warning with the Amplitube3.dll plugin, but interestingly the scan does not stop.

However, clicking on 'OK" does not dismiss the dialog box. And, the dialog box as originally presented, completely covers up the blue box which is reporting on the scan progress. (Unlike the picture shown, where I have fortuitously dragged the Warning dialog away.)

Now, as it happens, I have a newer version of Amplitube, so I went ahead and deleted my old version and for me this exact problem is now moot.

FWIW though, in this situation (or similar), having the 'OK' button work to dismiss the Warning dialog would be desirable, as would not having the Warning dialog completely cover the scan progress box.

Cheers!

[lulukom]

Hello Attila. Thanks for the tip, custom fonts work. )))
Now it is quite inconvenient to try to play phrases with different scales without changing the master track chords and provided that these scales correspond to the selected chord and, for example, the scales change for each chord. I think the most convenient and simple solution is to place an additional option in the phrase inspector. All this can be seen in the picture. I think this is a very important option and I would be extremely grateful for this decision. Thank you

[lulukom]

And also, as an option for reflection, a new variation for the phrase.. Of course, it hasn’t been fully thought out yet..

[sj1]

Arturia Pigments is a major, well-known plugin. I'm a bit surprised it raises a warning.

RC - Pigments.jpg

[BluGenes]

Yes, you are right and you see things right with the try...catch, which was used in old versions, but C++ exceptions are turned off now in the whole project. I think it is possible to enable exceptions in just one compilation unit as long as I handle the exception in it, so I'll try that.

I use this sometimes.. you could create a custom condition and error code.. but, yea, it's dated.. (2010)

http://blog.think-async.com/2010/04/sys ... art-5.html

[musicdevelopments]

Very strange.
As far as I read on the net, Amplitude 3 uses Visual C++ runtime which may not be found. So my guess is the dll could not be loaded fully as one its dependent dlls was not found.

Arturia Pigments is a major, well-known plugin. I'm a bit surprised it raises a warning.

I cannot check every single plug-in. I think you can add the missing plug-ins manually to the list.

Thanks,
Attila

[sj1]

Hi,

I have VST plugins on my machine in two places:

C:\Program Files\VSTPlugIns
C:\Program Files\Common Files\VST2

RC is only scanning the former.

I apologize if it should be obvious, but where I can set the paths to scan?

[sj1]

I cannot check every single plug-in.

Of course not.

I think you can add the missing plug-ins manually to the list.

Yes, that worked. Thanks!

[musicdevelopments]

And also, as an option for reflection, a new variation for the phrase.. Of course, it hasn’t been fully thought out yet..

This cannot be done as a variation, but there is the Generic Generator that allows you to set the percentage of chord/scale notes. Here 'other' notes are defined as scale notes. If you set Partial Polyphony to 100% and allow a single note for partial polyphony, chord notes will not be polyphonic:



And there is the Random Melody Generstor with almost your proposed controls: