RapidComposer 6 beta feedback and discussion

[thebutler]

Hi thebutler,

thanks for your very kind words!

I just uploaded v6.1.1 with bug fixes for both Windows and macOS (UI scaling and retina screens...)
All the bugs reported about the new UI engine have been fixed now.

Thanks,
Attila

You're welcome, much deserved...

I've installed 6.1.1 now and quick checking reveals this previous reported UI 'concern' is still there...

However, this is still happening... (no big deal, just something for future attention maybe)

... some funkiness with UI overall size of RC app when I switched from Windows MME to ASIO in Settings->Audio. Seems it immediately reduced RC's screen real estate to a 'maximum' that it cannot now be altered beyond. I can resize to make the UI even smaller, but only a re-boot of RC will fix the issue... weird.!

More clues...

May be due to screen resolution.? Am running at 2560x1440 (100% scaling, 27" monitor, Win11, Intel Iris XE graphics). Standalone RC app, sized to fit most of screen area (drag sizing handles) - the app is NOT maximised via button next to red 'X' close button at top.

Summary - the app window shrinks in size (always ONLY the right-hand edge) when switching drivers in Settings->Audio (eg. Windows MME to ASIO). This cannot now be re-stretched back to how it was. You can only drag/re-size the UI smaller from the right-hand edge. Closing/re-opening the app cures the problem.

Again, this may just be me and my system.!

Once I've set my ASIO config, I almost never have go back in there to change anything and the UI (after a re-launch) behaves flawless from then on. So its no dealbreaker of any kind. Move on.!

Finally, whilst I was in that area, I just noticed the 'sine wave' test signal produces distorted tone at less than 256 sample buffer size... No big deal, can't think if I ever actually tested before (i.e. has it always been this way.?)

[BluGenes]

Hi BluGenes,

Great Job ... I just created an account and generated a song as a test. Question ,,, is there a way to get the generated MIDI into a DAW ?

Keep up the good work !!

Jim F.

Thanks! Yea, working on that. All kinds of stuff still doesn't work, like tempo, etc. I need to get all the editing stuff working, like midi export, etc., then I can focus on the AI part. Just check back every few days, and if you or anyone have questions, just leave a message on the site. I hate hijacking Atilla's forums. (but I had too this time lol)

[musicdevelopments]

RapidComposer v6.2b1 is available!

Improvements:

• Moved the chord naming scheme selector to the Master Track header
• Fixed import of MIDI files with multiple time signature changes

[BluGenes]

I just noticed that RC v6 is not showing up in Windows installed APPs list. I have an older v6 I need to uninstall..

[musicdevelopments]

OMG, you are right, BluGenes! This new installer does not create an entry in the registry so that Windows can show RC v6 in the installed apps list. I am fixing this right now. Many thanks for letting me know!

Attila

EDIT: this is fixed in the next installer

[BluGenes]

OMG, you are right, BluGenes! This new installer does not create an entry in the registry so that Windows can show RC v6 in the installed apps list. I am fixing this right now. Many thanks for letting me know!

Attila

EDIT: this is fixed in the next installer

You might also want to consider, for those situations were you have to offer a hot fix kind of install were you use a build number in the version. This would make getting a new version from the app easier and would eliminate the "app already up to date" issue when a user clicks to check for a new version, when they know that isn't true. You just have ALWAYS bump the number every time. You can always reset that number after either the minor or major versions update, too.

[musicdevelopments]

That is actually a very smart idea, I have been thinking about this for a while. Now I started to use a build number from the next version. Update checking works for old versions too, so when I upload "v6.1.2 build 2" people will get notified about it.

This does not affect beta versions, where I'll always increment the beta number.

Thanks,
Attila

[magicmusic]

RapidComposer v6.2b1 is available!

Improvements:

• Moved the chord naming scheme selector to the Master Track header
• Fixed import of MIDI files with multiple time signature changes

this version also fix the windows problem with black sides when use windows UI scaling and hidpi DAW, many thanks

[musicdevelopments]

Thank you, magicmusic!

Today I uploaded v6.1.2 build 3, which should also work, if you don't want to use the beta version. From now I'll use build numbers when I don't want to bump the version number for small changes/fixes, so if you check for updates, you'll be able to download this new version.

There is a new setting which fixes problems related to Windows UI scaling for most (unfortunately not all) users. Look for "Windows UI scaling" under Settings / User Interface / Rendering.

Thanks,
Attila

[musicdevelopments]

RapidComposer v6.2b2 is available!

Improvements:

• Added 8 Scene buttons for storing and recalling selected settings during live playback. Right-click a Save button to choose which settings to store and recall.
• Added "Optimize memory usage for loaded phrases" option (Settings / Miscellaneous) that keeps loaded phrases in a compressed state in memory, which reduces memory usage

[foster911]

I want the chord selector window to stay on top, but this doesn't happen. This was possible in RC-6.0.7, but is not possible in the latest version. I select all the top options in Miscellaneous but it still doesn't happen.

By minimizing the main RC window, the Chord Selector window is also minimized. In version 6.0.7, when the main RC window was minimized, the chord selector window was not minimized and kept on top.

Please restore the previous property. I always want the chord selector window to stay on top and be independent of RC itself.

Thanks so much!

[musicdevelopments]

It is interesting because I found that the chord selector always stays on top (on Windows), regardless what I set in the settings. On macOS it works well, it can be a normal window or always-on-top.

I have fixed this, so from the next update, it won't be minimized when the main window is minimized, and also the "chord selector always on top" setting is respected on Windows.

Thanks for reporting this!
Attila

[musicdevelopments]

RapidComposer v6.2b3 is available!

Improvements:

• Mackie Control Universal (MCU) protocol supported to control the transport (Settings > MIDI) from the SSL UC1 and other controllers
• Fixed MIDI file information on the MIDI Import page
• Fixed Live scenes not restoring when reloading the composition
• [Windows] Chord selector window respects the 'always-on-top' setting. It is not minimized when the main window is minimized

[hamlen]

Hello all! I just purchased RC6 (full) and this is my first post.

I can't get the vst3 GUI to display properly in any DAW (v6.2b3 on Win11, Cantabile 4 Performer, also tried Unify 2 and FL Studio). Standalone RC6 renders perfectly, but the vst3 plugin isn't usable because its GUI doesn't resize or scale properly. It appears clipped (some parts inaccessible) or not at all.

Here's what I've tried:

• Tried all combinations of RC6's two renderer options (D3D and Windows UI scaling). No change.
• Turned Windows 11 desktop scaling down to 100%. No change.
• With C4's HiDPI setting turned on, RC6 GUI does not display at all (zero-height window). With it turned off, RC6 GUI is clipped to a small, non-resizable window (unusable).
• Turning C4's plugin upscaling options on/off makes no difference.
• Putting the GUI in "docked" or "detached" views in C4 makes no difference.
• Opening RC6 in Unify 2 crashes U2. RC6 starts to slowly render from left-to-right, progresses off the screen, and U2 crashes.
• In FL, turning off "DPI-aware" and "scaling" makes RC6 barely usable, but it's confined to a small, unresizable window with scroll bars that don't always work correctly.

It seems like the vst3 code responsible for reporting GUI size to the DAW might have a bug? If so, is there any chance this could be fixed?

My use case: I want to use RC6 Live Mode for live performance within Cantabile, for which I'd need it to work in the daw (e.g., for host automation).

Thank you for your help!
--Kevin