Bug reports

[Jrmuzik]

Im using RC 5.2.3 and Bitwig 5.1. I haven't changed anything or updated anything lately, however, Im receiving this new error randomly. I have never seen this error with RC before. Its now showing up on all of my Recent RC 5 projects. Any idea how to prevent this? It sucks because I never extracted the midi from RC. JPG is in attached file.

[musicdevelopments]

This is strange, I'll check this today.

Bitwig (like all hosts) saves the plug-in state when you save the composition so that it can restore next time. It may save also during editing for undo/redo purposes. According to this message RapidComposer could not restore its state from the data received from Bitwig.

EDIT: I could not reproduce this in Bitwig demo mode (my trial version expired, I must get a license).

[musicdevelopments]

Hello Jrmuzik,

can you send me a Bitwig project that - when loaded - will display the error message?
I'd be able to tell exactly why RapidComposer does not restore its state.
I saved and loaded many Bitwig projects with RapidComposer, so far without problems. (I do not have old projects)
Do you also use Bitwig v5.1.9?

Thanks,
Attila

[vne5]

Rapdicomposer 5 is having issues in Ableton 12. No sound sometimes, the cursor is off quite a bit. when I try to change key, I need to place the cursor consoderably above the key for it to highlight. Using Mac M1 with Sonoma 14.4.1

[musicdevelopments]

Hello vne5,

thanks for reporting this bug.

Do you use a retina screen? Is this with the latest RC version, v5.2.3?
Which plug-in format do you load into Ableton: VST3 or AU?

Do you experience this immediately after loading the plug-in, or later during usage? Maybe after closing and re-opening the plug-in window?

I loaded the RC VST3 into Ableton, so far it worked well.

Thanks,
Attila

[DLate]

Save selected phrases from popup phrase menu not working. With alt drag popup show somewhere behind app.
Windows 11, last beta.

[DLate]

When moving notes in editor beat dissapeared.

More strange things.

[DLate]

Bug when draw notes in melody editor. Step to reproduce:
1. Drop motive generator and open editor.
2. Add section.
3. Draw note in that section.

[musicdevelopments]

Bug when draw notes in melody editor. Step to reproduce:
1. Drop motive generator and open editor.
2. Add section.
3. Draw note in that section.

Hello DLate!

I tried hard to reproduce this, but I could not
Neither this one below:

Save selected phrases from popup phrase menu not working. With alt drag popup show somewhere behind app.

There is something wrong with that phrase that you opened in the Phrase Editor.
I'd be grateful, when this happens, please send me the composition file so that I could reproduce and fix the editing issues in the Phrase Editor.

Thanks!
Attila

[MC-909]

Hello, I would like to report a bug with the scrolling wheel in the latest version on a Mac m1. From what I've seen it's only occurring in the AU plugin version, but it seems even the stand alone version is not so 'Magic Mouse friendly'. is there an option to let the program handle scrolling according to your OS native settings so there is no difference in 'feel'?

I surely appreciate and understand the tweak able scrolling settings, but having it default at the same 'feel' as my native settings would be a better starting point imo.

At the moment I'm completely unable to use your program because scrolling UP is almost impossible, every slight movement results in the page scrolling down like crazy.

Pls advice, tnx!

[fycfung]

Hi! I'm on MacOS Sonoma 14.5 on Intel Macbook Pro, using an external monitor at 1920 x 1200 (default resolution) over HDMI, and when I open RapidComposer 5.3.1, and then try to resize it, all the text/graphics suddenly become way too big and I can't scroll around or use anything (most of the functionality is off the screen, and the menus/buttons don't seem to have their click targets aligned with where they are rendered). I can repro the problem by opening it in my laptop primary display (it looks OK) and then moving the window to the external display (then everything is too big).

[alice1215]

I'm on Windows 10, using both standalone and VST versions, and I noticed a few bugs:

1) I can't rename lines. In version 4 it was possible, but in 5.3.x I can rename only project and parts.
2) When I connect Kontakt 7 as a VST sound output in standalone version, it crashes often. There are no issues with built-in soundfonts.
3) While CTRL+dragging phrases from one track to another, while the track has Kontakt 7 as a VST sound output, standalone version crashes every time.

If needed, I can record short screencasts so you can reproduce every scenario.

Other than that you created an awesome software, testing for the 3rd day in a row

[musicdevelopments]

Hello, I would like to report a bug with the scrolling wheel in the latest version on a Mac m1. From what I've seen it's only occurring in the AU plugin version, but it seems even the stand alone version is not so 'Magic Mouse friendly'.

Hello MC-909,

thanks for reminding me; this should have been fixed long ago.
Yesterday v5.3.2 was uploaded with trackpad and Magic Mouse scrolling implememted.

Thanks,
Attila

[musicdevelopments]

Hi! I'm on MacOS Sonoma 14.5 on Intel Macbook Pro, using an external monitor at 1920 x 1200 (default resolution) over HDMI, and when I open RapidComposer 5.3.1, and then try to resize it, all the text/graphics suddenly become way too big and I can't scroll around or use anything (most of the functionality is off the screen, and the menus/buttons don't seem to have their click targets aligned with where they are rendered). I can repro the problem by opening it in my laptop primary display (it looks OK) and then moving the window to the external display (then everything is too big).

Hi fycfung!

I am afraid it is a known issue, that moving the RC window from retina to non-retina screen (or vice versa) does not behave well. This is very difficult to fix at the moment.
If you have to do that, there is a setting under Settings / User Interface called "Disable retina screen detection" which will improve things.
You can set "Disable retina screen detection" in the standalone application, the same setting is used by the plug-in, when loaded.

Also, such rendering issues exist since we started to use hardware accelerated rendering. It is advised to select 'software' rendering when this happens. The following screenshot shows both options, under Settings / Miscellaneous:



Thanks!
Attila

[musicdevelopments]

I'm on Windows 10, using both standalone and VST versions, and I noticed a few bugs:

1) I can't rename lines. In version 4 it was possible, but in 5.3.x I can rename only project and parts.
2) When I connect Kontakt 7 as a VST sound output in standalone version, it crashes often. There are no issues with built-in soundfonts.
3) While CTRL+dragging phrases from one track to another, while the track has Kontakt 7 as a VST sound output, standalone version crashes every time.

If needed, I can record short screencasts so you can reproduce every scenario.

Other than that you created an awesome software, testing for the 3rd day in a row

Hello alice1215!

Welcome to this forum, and thanks for your first post!

You are right, it is not possible to rename lines in version 5. Lines are named automatically. Even if you change their order, they will be renamed. This was my decision to simplify things, I may be wrong though. So far no other users complained about this.

I was testing Kontakt 7 tracks today but did not find any problems. Even Ctrl-dragging worked from one track to the other. This was on Windows 11, as I have no access to a Windows 10 PC right now. Which Kontakt version do you use? Does it matter which instrument is selected in Kontakt? Do both the source and target tracks need to be set up for Kontakt? I'd be grateful for any hints so that I can fix this.

Thanks,
Attila