RapidComposer v5 beta feedback and discussion

[lulukom]

Hello Attila. Beta 10 scans VST3 better, but when opening Scaler2 it crashes.

[lulukom]

Screen Shot 2023-09-30 at 12.05.40.png

[lovemusic15]

[lovemusic15]

Hello Attila
Appreciate your feedback on this.

Bug ?

[musicdevelopments]

Hello Attila. Beta 10 scans VST3 better, but when opening Scaler2 it crashes.

Hello lulukom,

Scaler crashed with an OpenGL error (in the AMDRadeonX3000GLDriver), RC has nothing to do with the crash. RC uses Metal by default, and it was not running in any of the threads at the time of the crash. Did you select OpenGL in RC too? Did this happen only once, or always?

EDIT: OK, now I see what the problem is from your previous crash dump, where RC and Scaler are both flushing OpenGL buffers at the same time however RC does this from the main UI thread and Scaler does this from another thread which is very wrong. They should fix their own bug. As a workaround you could select 'software' rendering in RC until this is fixed in Scaler.

I try to implement blacklisting during plug-in scanning if one of the loaded plug-ins crash.

Thanks,
Attila

[lulukom]

Hi Attila. I have known for a long time that there were some problems with video, but I never switched rendering from default. I tried to choose software rendering, but so far Scaler 2 and RC do not get along together. So far this is a crash. Just in case, I’m attaching a report. Yes, it would probably be right to create a blacklist for scanning plugins. Yes, indeed, custom fonts work (though only on one of my Macs and they are not as beautiful as in version 4)). Thank you . Custom Phrases still takes too long to load.

[lovemusic15]

Hi Attila. I have known for a long time that there were some problems with video, but I never switched rendering from default. I tried to choose software rendering, but so far Scaler 2 and RC do not get along together. So far this is a crash. Just in case, I’m attaching a report. Yes, it would probably be right to create a blacklist for scanning plugins. Yes, indeed, custom fonts work (though only on one of my Macs and they are not as beautiful as in version 4)). Thank you . Custom Phrases still takes too long to load.

Hi lulukom,

I never use scaler inside RC but just to check your theory I tried it and you're exactly right it does crash RC. am on a pc

[lulukom]

Hello lovemusic15 . Thanks for support !)

[lovemusic15]

No problem lulukom

[lulukom]

Attila, hello. I think that Scaler is not to blame, in any case, for the crash of the DP. RС crashes in DP and independently as a plugin. Rendering is set to software. I am attaching the report.

[BluGenes]

If you were able to save the state of RC during a VST3 scan between each VST tested, then, when a crash would happen, on restart of RC (show "apologize for the crash" screen), read the last saved state, add the offending VST to a list, skip that VST, then start scanning from that point. I would put a "finish scan" button to do that on the plugins page.

Have a button in the plugin's page that when clicked, show the list VST's that could be added manually and maybe allow double click in that list to add them manually, one at a time.

Yea, the above two paragraphs are how I would type my request into co-pilot.. lol

But, it's an idea..

[lovemusic15]

BluGenes that's a nice suggestion.

Do you have any suggestions on how to address the problem I'm encountering with Rhythm Lab? I considered having Rhythm Lab analyze the notes to recreate patterns with similar syncopation, but do you have any other suggestions? I'm trying to find a way to maintain syncopation without losing it. the problem is demonstrated in my previous video post.

[BluGenes]

BluGenes that's a nice suggestion.

Do you have any suggestions on how to address the problem I'm encountering with Rhythm Lab? I considered having Rhythm Lab analyze the notes to recreate patterns with similar syncopation, but do you have any other suggestions? I'm trying to find a way to maintain syncopation without losing it. the problem is demonstrated in my previous video post.

thanks.. actually, not yet. I am playing catch up as my internet was down in a very bad on and off state all last week. I couldn't really do anything productive at all.

I haven't played with the rhythm lab just yet, but, getting there..

If you could make a video on what you know about it, that could help too. I'll try and make time to watch your stuff some time soon, too..

[musicdevelopments]

Hi Attila. I have known for a long time that there were some problems with video, but I never switched rendering from default. I tried to choose software rendering, but so far Scaler 2 and RC do not get along together. So far this is a crash. Just in case, I’m attaching a report. Yes, it would probably be right to create a blacklist for scanning plugins. Yes, indeed, custom fonts work (though only on one of my Macs and they are not as beautiful as in version 4)). Thank you . Custom Phrases still takes too long to load.

Hi lulukom,

blacklisting plug-ins is implemented now. I'll upload a new beta version later today.
The crash report you included is another OpenGL crash in Scaler. RapidComposer was not doing anything when this happened. Scaler accesses OpenGL not from the main UI thread, which is a very bad idea (serious issue).
Font rendering was not changed since v4, so the same TTF should look the same on v5.
Custom phrases (as included in the v5 installer) are loaded in a few seconds because they are compressed archives (many phrases are in a single file rather than in many small files).
If you use your own custom phrases that are individual files, then yes, they are loaded with the same speed as with v4. But I hope you did not copy the 42000 phrases from the v4 Custom Phrases folder to v5, because you don't need to, those files are in the distribution.

Thanks,
Attila

[musicdevelopments]

If you were able to save the state of RC during a VST3 scan between each VST tested, then, when a crash would happen, on restart of RC (show "apologize for the crash" screen), read the last saved state, add the offending VST to a list, skip that VST, then start scanning from that point. I would put a "finish scan" button to do that on the plugins page.

This is implemented in beta11 which will be uploaded shortly. The state is saved and if there is a crash, the crashed plug-in is added to a blacklist, and the next scanning will start from where the previous one stopped, skipping the plug-ins in the blacklist. The blacklist can be checked and cleared under Settings / Miscellaneous / Plug-in Hosting.

Thanks,
Attila