MusicDevelopments

BluGenes · Post by **BluGenes** » Sun Sep 27, 2020 7:39 pm

Ok, so, I was able to get a custom chord into the rules by creating it in the chord browser. So, all is needed is to add the builder to the chord browser.

lulukom · Post by **lulukom** » Sun Sep 27, 2020 7:56 pm

In my layout options only on/off works, rows and columns are not switched.

lulukom · Post by **lulukom** » Sun Sep 27, 2020 8:06 pm

And I would also like the progressions to be generated without stopping the loop, i.e. during loop playback. I mean in the Chord Selector, of course.

musicdevelopments · Post by **musicdevelopments** » Mon Sep 28, 2020 7:11 am

Right, but this has always worked like that in the Chord Palette.
For multiple scales the notation changes to 'letter' notation.
Roman numerals cannot be used in this case, because roman numerals are relative to the scale root, so each chord should display which scale it belongs to, e.g. with multiple labels but this would be a mess.

BluGenes wrote: Sat Sep 26, 2020 11:08 am Nice change to chord selector, however.. you lose the ability to change notation style if you add more scales..

musicdevelopments · Post by **musicdevelopments** » Mon Sep 28, 2020 7:53 am

lulukom wrote: Sun Sep 27, 2020 7:56 pm In my layout options only on/off works, rows and columns are not switched.

Thanks, lulukom! This stopped working but is fixed now. I think I'll upload a new beta today.

lulukom wrote: And I would also like the progressions to be generated without stopping the loop, i.e. during loop playback. I mean in the Chord Selector, of course.

I would like to propose that we should leave these small improvements (together with custom chords et al) after v4.0. I am way behind schedule, has just started the big source code rework and cleanup which will take 3-4 weeks at least. I will of course fix bugs in the beta version during this time.

Thanks,
Attila

lulukom · Post by **lulukom** » Mon Sep 28, 2020 8:28 am

Thank you, Attila!
And improving the graphics is also a very significant advancement of the program!

BluGenes · Post by **BluGenes** » Mon Sep 28, 2020 8:55 am

Same here, Atilla .. Thanks! Looking forward to it all!

musicdevelopments · Post by **musicdevelopments** » Mon Sep 28, 2020 9:17 am

RapidComposer v3.9b46 is available!

Improvements:

[macOS] New setting: "Audio Unit: Create Virtual MIDI Port" (default is NO)
[Plug-ins] Fixed: notes at the beginning of playback were silent
[Plug-ins] Fixed 2 crashing bugs (one during exit, one during usage)
Fixed: 'allow maximum columns/rows' stopped working in the chord palette
Fixed: shortcuts F1..F4 work again

dbender · Post by **dbender** » Mon Sep 28, 2020 9:37 am

musicdevelopments wrote: Mon Sep 28, 2020 9:17 am RapidComposer v3.9b46 is available!

Improvements:

[macOS] New setting: "Audio Unit: Create Virtual MIDI Port" (default is NO)

Hi Attila -- is this new setting in the AU plugin itself? I can't find it anywhere in Settings in the standalone? (haven't checked the AU plugin in my DAW yet)

And does this mean that the AU plugin sends midi out, and will be a midi source in Studio One? And if so, does the VST and VST3 versions also have that too? (again, sorry but don't have time to open Studio One and experiment to find out)

musicdevelopments · Post by **musicdevelopments** » Mon Sep 28, 2020 9:53 am

This setting can be seen in the standalone too, under Settings / Miscellaneous / "RapidComposer VST/VST3/AU".

A MIDI port is created only in the AU plug-in which sends MIDI event through this port to the host. This has always worked like that, the only change is that you can disable MIDI port creation.
VST and VST3 have proper MIDI implementation, and do not require such a hack

dbender · Post by **dbender** » Mon Sep 28, 2020 10:12 am

Thank you!

sj1 · Post by **sj1** » Mon Sep 28, 2020 1:20 pm

sj1 wrote: Sat Sep 26, 2020 1:47 pm On Windows, got a crash when I unchecked the new 'Use Smaller Chord Buttons' for the Chord List.

So far, I do not observe this problem in b46. If I see it again I will mention it. Cheers!

lulukom · Post by **lulukom** » Mon Sep 28, 2020 3:48 pm

deleted

sj1 · Post by **sj1** » Mon Sep 28, 2020 3:51 pm

musicdevelopments wrote: Mon Sep 28, 2020 7:53 am I would like to propose that we should leave these small improvements (together with custom chords et al) after v4.0. I am way behind schedule, has just started the big source code rework and cleanup which will take 3-4 weeks at least. I will of course fix bugs in the beta version during this time.

The pace at which you improve and evolve this program is truly exceptional! I can only anticipate joyfully what you'll be able to do in the future after you've done the code rework that you've decided is necessary.

Thank you for all that you do, and maybe up-the-road you'll be able to comment a bit on a few of the things you've remained silent on so far.

lulukom · Post by **lulukom** » Mon Sep 28, 2020 3:56 pm

Yes, for example, what's new in version 4 ? There is no limit to my curiosity!)

MusicDevelopments

KVR Audio

v3 Beta Feedback And Discussion (Bugs, Features, Suggestions)