Bug reports

[musicdevelopments]

phrase browser missing.

not sure if bug or compatibility issue.

downloaded and reinstalled twice.

right-clicked many areas of screen. resized plugin window. can add a pic if helpful.

if helpful: using a xeon 2145 cpu and rtx 5060 ti gpu

phrase browser missing in reaper 7.x, fender studio pro 8.
plugin crashed cubase and plugin crashed in bitwig.

Hello Mickey_Mousing,

there have been issues on Retina displays (macOS) and with UI scaling (Windows) in the initial v6.1 release. Not just rendering issues but the VST3 plug-in was hanging. Please download v6.1.1, all bugs are fixed now.

Thanks,
Attila

[musicdevelopments]

Hi Atilla,

I am no longer able to delete a chord from the master track. I normally use the "delete" key for this action. Did something change ?

Hi Jim,

the delete key works here... it glues the selected chord(s) with the previous chord.
Of course you can use Alt-click to split and glue chords quickly.

Thanks,
Attila

[CarlosCox]

Hi, I just bought Rapidcomposer 6 this week and found a little quirk. I can't delete phrases in the track using the delete key. Backspace key worked fine, but not the delete key on my 108 key keyboard. And today, after asking the AI for advice, I tested all the possibilities, and found that if I turned off the numlock on my numpad, the delete key can delete phrases as it should be. But as soon as I turn on the numlock, the delete lost its function. I think this could be a bug, but I don't know. And btw, I'm using a Logitek G613 keyboard.

[musicdevelopments]

Hi CarlosCox,

welcome to this forum!
Thank you for reporting this bug. I think I managed to fix it today, so if you re-download the current version (v6.1.1) the Delete key will most probably work. The fix will be officially in v6.1.2, but I did not want new users to be affected by this issue.

If you cannot find the download links, you can download the demo version from musicdevelopments.com (they are the same installer).

Thanks!
Attila

[jdfair]

Hi Atilla,

I can confirm that the "delete" key works as is used to with 6.1.1. update ... regardless of the status of the "Num Lock" key. Thanks for the fix !

Jim F.

[musicdevelopments]

Hi Jim,

thank you for your feedback! I am afraid there are other issues (e.g. AZERTY layout does not work) that need to be fixed. And I am not sure if Chinese/Japanese/Korean language input works well... It used to work but a few things broke with v6.1.

Thanks,
Attila

[Distomen1]

Hello, I wanted to say that Rapid composer is the best program on the market, as a long-time user I am very satisfied with it.I wanted to say that on Windows 11 in the vst version, when we click on the chord selector, the windows display does not work correctly, there are graphical bugs.I want to send a photo but I don't know how to do it.

[musicdevelopments]

Hello Distomen1,

thanks for your kind words!
Please make sure you download the v6.1.1 update, because in v6.1.0 there were some rendering issues because of the new rendering library that I started to use. I did my best to fix them, and yes, the Chord Selector was affected too.

Thanks!
Attila

[Distomen1]

Thank you very much for your answer, I have version 6.1.1 and window rendering is still bugged every time. But I'm glad you'll fix it soon.

[musicdevelopments]

Really? Exactly these sorts of graphics issues were fixed in v6.1.1, but I'll check it again.
Do you use Windows UI scaling perhaps? Does it work well when you set it to 100% temporarily?

Thanks,
Attila

[Distomen1]

This works fine when scaling is set to 100. At 125% these scaling problems occur.

[musicdevelopments]

I see. Could you please check the build date under the Support tab?

[Distomen1]

Build on Apr 16 2026

[musicdevelopments]

Will you try this version that uses Direct3D12 rather than Direct3D11?
https://www.musicdevelopments.com/downl ... ct3D12.exe

In future versions this can be set under Settings / User Interface. I did not expect that several users would have issues with Direct3D11. There are more buggy drivers than you can imagine... Anyway, I hope it will work well.

Thanks,
Attila

[Distomen1]

It's still the same, but it's no longer a problem for me because I changed the scaling to 100%. Regards