RapidComposer v5 beta feedback and discussion

[musicdevelopments]

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?

When you click on "Scan VST plug-ins...", an alert opens (to intimidate users) and then you can select the path you want to scan ("Select a directory to scan"). IIRC the scan depth is 2, so .dll's are read also from the subdirectories of the selected path.

Thanks,
Attila

[sj1]

OK, so that's two separate scans, initiated by me, rather than a list of multiple directories to scan.

Got it. Thanks!

[lovemusic15]

I'll have to get back to you on this. I did watch the video, but, I need more time to look into this one..

Right now, the biggest issue that needs to be fixed at the moment is the scanning problems..
[/quote]

No problem BluGenes

[lovemusic15]

Hi Attila

I've noticed you mentioned that you've fixed and updated the Rhythm LAB, but I'm still encountering the same problem. As you can see, I've converted my MIDI to rhythms Mapper

[lovemusic15]

However, when I access the drop-down menu for accents, the closest settings I can find to describe the accents are 1/4, 1/8, and 1/16.

[lovemusic15]

Unfortunately, as soon as I select one of these options, everything defaults to 16th notes. Consequently, the results I was expecting are not achievable right from the start.

I kindly request that you address this issue by either ensuring that the software properly analyzes the notes or providing us with the option to drag our own rhythms and save them as accents to create new rhythms. I've detailed all the necessary information and suggestions in my previous posts and videos.

Thanks

[BluGenes]

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?

[lulukom]

Attila, look at another plugin crash.

[plopseaw]

Hi Atila,

Finally got the chance to try b12 again.

The standalone works for me but the plugin version is not working.

It loads and the window appears but it's not possible to click on anything except at odd places. Its seems like the plugin has a scaling issue compared to the mouse. If I click far left I can get some of the right side (e.g. like changing from composition to phrase)

If I resize the window then it appears almost blank like its over scaled.

Iam on an M2 MacBook Pro with Sonoma. Display scaling is set to default. The DAW this time is Bitwig.

[musicdevelopments]

Attila, look at another plugin crash.

Thanks, lulukom, but it is not RapidComposer to blame this time. All RC threads are in waiting state, except for the custom phrase loader, but that is not the one that crashed. I am not able to tell exactly what caused the crash but I am 98% sure it was not RapidComposer. The invalid address that was accessed is 0x000040dedeadbec0, and I assume the bottom 32 bits was 0xDEADBEEF originally. There is no such data pattern in RC.

Thanks,
Attila

[musicdevelopments]

It loads and the window appears but it's not possible to click on anything except at odd places. Its seems like the plugin has a scaling issue compared to the mouse. If I click far left I can get some of the right side (e.g. like changing from composition to phrase)

If I resize the window then it appears almost blank like its over scaled.

Hi plopseaw,

can you send me screenshots or (if I may ask) a video about the resizing? I have no access to an M1 or M2 macbook unfortunately.

EDIT: there is indeed an issue with mouse positions on retina screens in the AU plug-in, VST3 works well. I'll have a fix shortly.

Thanks!
Attila

[musicdevelopments]

RapidComposer v5.0b13 is available!

I managed to make plug-in scanning crash-proof on Windows. On macOS this is so difficult to implement, that it is not worth the effort.

Improvements:

• VST3 scanning made faster and more reliable: plug-in instance is not created, only information is gathered (this should have worked like this before, but due to a bug it did not...)
• [Windows] VST2 and VST3 scanning is now crash-proof, RC does not quit when a plug-in crashes, instead it adds it to the blacklist
• Pressing Ctrl during setting velocity values in the CC editor will set all selected notes to the same velocity
• User guide updated for v5

[sj1]

Hi.

With b13, (Win 10, standalone) I unchecked 'Skip plug-ins in the black list', then started a VST scan.

RC immediately crashed.

I will be happy to send in a crash report if someone will advise me where to find it. Thanks.

[sj1]

Hi. In my testing, by single-adding a plugin that was already on the blacklist I now have it on the blacklist twice.

I would like to edit the blacklist file to remove the duplicate. Where can I find that? Thanks.'

[musicdevelopments]

However, when I access the drop-down menu for accents, the closest settings I can find to describe the accents are 1/4, 1/8, and 1/16.

Hi lovemusic,

The drop-down menu is for simple rhythm presets so that the user does not have to start editing from scratch. Selecting a preset will overwrite the whole rhythm pattern.
I am going to watch the videos that you uploaded, but I think you misunderstand the Rhythm Lab. It does not analyse anything, it just creates a simpler pattern from all available notes by using probabilities.

Thanks,
Attila