v3 Beta Feedback And Discussion (Bugs, Features, Suggestions)
-
- KVRAF
- 1985 posts since 14 Mar, 2006
another problem with the IAC approach in the AU is that all other apps listening to midi on the OSX system will pickup all that IAC midi data too.
MacPro 5,1 12core x 3.46ghz-96gb MacOS 12.2 (opencore), X32+AES16e-50
-
- KVRAF
- 1985 posts since 14 Mar, 2006
Here's some proof of concept of how you could use AUmfx version of RC in a project. I am using Kushview Element's AUmfx to sub-host RC.vst3 inside of it in the MFX slot of LogicPro. This is functionally the same as if RC came in AUmfx version.
In this case Omnispheres is a multi-timbral instrument with up to 8 parts on 8 midi channels and it works very well driving 8 midi channels to it. No IAC! Sample Accurate!
Could do the same thing with something like VePro as the multi-timbral instrument, then it would support 16 midi channels, no IAC and sample accurate.
Alternatively we can use third party sub hoster and put RC inside it in the instrument slot... like this:
Note in the above though, I crash LogicPro every time when closing the Kushview element window (RC is the cause of crash). And while the above will avoid IAC problems by using RC.vst3 and will be sample accurate and also provides a way to use both midi out and sound fonts from RC too I might add, it does require the use of a third party product, in this case Kushview Element. But honestly these approaches are preferable then to using IAC.
In this case Omnispheres is a multi-timbral instrument with up to 8 parts on 8 midi channels and it works very well driving 8 midi channels to it. No IAC! Sample Accurate!
Could do the same thing with something like VePro as the multi-timbral instrument, then it would support 16 midi channels, no IAC and sample accurate.
Alternatively we can use third party sub hoster and put RC inside it in the instrument slot... like this:
Note in the above though, I crash LogicPro every time when closing the Kushview element window (RC is the cause of crash). And while the above will avoid IAC problems by using RC.vst3 and will be sample accurate and also provides a way to use both midi out and sound fonts from RC too I might add, it does require the use of a third party product, in this case Kushview Element. But honestly these approaches are preferable then to using IAC.
You do not have the required permissions to view the files attached to this post.
MacPro 5,1 12core x 3.46ghz-96gb MacOS 12.2 (opencore), X32+AES16e-50
-
musicdevelopments musicdevelopments https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=223336
- KVRAF
- Topic Starter
- 6010 posts since 9 Jan, 2010
Good catch! It fetched up the same action ID from the note inspector. I fixed that. I have already built beta44 so the fix will be in the next update.BluGenes wrote: Mon Sep 21, 2020 11:08 am Might want to reconsider what is what for the phrase inspector. With the newly added shortcut text, it's now obvious that some of the functions in the inspector don't really relate to "phrase" operations, but, rather on the "track" level.
The shortcut "D" in this case, no clue what is supposed to have focus...
Thanks,
Attila
https://www.musicdevelopments.com
Home of RapidComposer, Melodya, MIDI Mutator and Syne
Summer Sale • June 3-15 • 40% off RapidComposer, Melodya, MIDI Mutator, Syne
Home of RapidComposer, Melodya, MIDI Mutator and Syne
Summer Sale • June 3-15 • 40% off RapidComposer, Melodya, MIDI Mutator, Syne
-
- KVRAF
- 2152 posts since 15 May, 2017
I was also thinking that wherever you reference "all" in the phrase inspector would be more suited as a track level function, rather than a phrase level..musicdevelopments wrote: Tue Sep 22, 2020 11:30 amGood catch! It fetched up the same action ID from the note inspector. I fixed that. I have already built beta44 so the fix will be in the next update.BluGenes wrote: Mon Sep 21, 2020 11:08 am Might want to reconsider what is what for the phrase inspector. With the newly added shortcut text, it's now obvious that some of the functions in the inspector don't really relate to "phrase" operations, but, rather on the "track" level.
The shortcut "D" in this case, no clue what is supposed to have focus...
Thanks,
Attila
-
- KVRAF
- 2152 posts since 15 May, 2017
I must have jumped the starting gun.. lol
edit: oh wait, I miss understood.. that fix would be in beta 45.. oops..

edit: oh wait, I miss understood.. that fix would be in beta 45.. oops..

-
musicdevelopments musicdevelopments https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=223336
- KVRAF
- Topic Starter
- 6010 posts since 9 Jan, 2010
I can't believe I forgot to post this (thanks sj1):
RapidComposer v3.9b44 is available!
Improvements:
RapidComposer v3.9b44 is available!
Improvements:
- Cosmetic changes in the Chord Selector: using vector graphics at some places
- "Generate Progression" button in the chord selector works differently, in accordance with the rest of the UI: left click to generate, right click for options
- Fixed a possible crashing issue during editing and previewing chord progressions in the Chord Selector
- [Plug-ins] Crashing when unloading the plug-ins fixed (introduced in beta35)
https://www.musicdevelopments.com
Home of RapidComposer, Melodya, MIDI Mutator and Syne
Summer Sale • June 3-15 • 40% off RapidComposer, Melodya, MIDI Mutator, Syne
Home of RapidComposer, Melodya, MIDI Mutator and Syne
Summer Sale • June 3-15 • 40% off RapidComposer, Melodya, MIDI Mutator, Syne
-
musicdevelopments musicdevelopments https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=223336
- KVRAF
- Topic Starter
- 6010 posts since 9 Jan, 2010
Hi Dewdman42!
Thanks for the very informative post! I have learnt a lot.
I fixed a few bugs and built a MIDI FX version of RapidComposer. I think it works pretty well in Logic Pro X, even the audio.
I am going to send you the installer in PM, if you are willing to try it.
At the moment it would be a hassle to build BOTH the synth and MIDI FX AU, but if you find that it is useful, I'll solve the build issues.
Thanks!
Attila
Thanks for the very informative post! I have learnt a lot.
I fixed a few bugs and built a MIDI FX version of RapidComposer. I think it works pretty well in Logic Pro X, even the audio.
I am going to send you the installer in PM, if you are willing to try it.
At the moment it would be a hassle to build BOTH the synth and MIDI FX AU, but if you find that it is useful, I'll solve the build issues.
Thanks!
Attila
https://www.musicdevelopments.com
Home of RapidComposer, Melodya, MIDI Mutator and Syne
Summer Sale • June 3-15 • 40% off RapidComposer, Melodya, MIDI Mutator, Syne
Home of RapidComposer, Melodya, MIDI Mutator and Syne
Summer Sale • June 3-15 • 40% off RapidComposer, Melodya, MIDI Mutator, Syne
-
- KVRAF
- 1752 posts since 30 Nov, 2013
Hello Attila! In the new beta, in the Chord Selector, the Icon Filter Notes works only for switching on and when pressed again does not return to the previous view. (Perhaps I don't understand something and it should be so)
-
- KVRAF
- 2152 posts since 15 May, 2017
chord selector, color by chord suggestion isn't working..
-
musicdevelopments musicdevelopments https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=223336
- KVRAF
- Topic Starter
- 6010 posts since 9 Jan, 2010
The notes filter under Chord List works for me, on Windows and macOS.
Color by suggestions indeed does not work... I am checking why.
Thanks,
Attila
Color by suggestions indeed does not work... I am checking why.
Thanks,
Attila
https://www.musicdevelopments.com
Home of RapidComposer, Melodya, MIDI Mutator and Syne
Summer Sale • June 3-15 • 40% off RapidComposer, Melodya, MIDI Mutator, Syne
Home of RapidComposer, Melodya, MIDI Mutator and Syne
Summer Sale • June 3-15 • 40% off RapidComposer, Melodya, MIDI Mutator, Syne
- KVRian
- 1177 posts since 13 Mar, 2017
Hi,
I notice that when the Chord Selector is opened as 'For Chord Progression' (which has extra controls) the window is too tall for the monitor.
Offhand, I'd suggest fewer but longer rows so that the window is fully on the screen.
I notice that when the Chord Selector is opened as 'For Chord Progression' (which has extra controls) the window is too tall for the monitor.
Offhand, I'd suggest fewer but longer rows so that the window is fully on the screen.
-
musicdevelopments musicdevelopments https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=223336
- KVRAF
- Topic Starter
- 6010 posts since 9 Jan, 2010
Do you also experience flashes in the Chord Selector window when changing tabs? I noticed this yesterday but could not fix it yet.
https://www.musicdevelopments.com
Home of RapidComposer, Melodya, MIDI Mutator and Syne
Summer Sale • June 3-15 • 40% off RapidComposer, Melodya, MIDI Mutator, Syne
Home of RapidComposer, Melodya, MIDI Mutator and Syne
Summer Sale • June 3-15 • 40% off RapidComposer, Melodya, MIDI Mutator, Syne
-
musicdevelopments musicdevelopments https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=223336
- KVRAF
- Topic Starter
- 6010 posts since 9 Jan, 2010
Hi Steve,
I suppose you mean the 'Chord List' which gets tall. You can make the rest of the views smaller in size either by excluding data, or by resizing.
Thanks,
Attila
I suppose you mean the 'Chord List' which gets tall. You can make the rest of the views smaller in size either by excluding data, or by resizing.
Thanks,
Attila
sj1 wrote: Wed Sep 23, 2020 11:04 am Hi,
I notice that when the Chord Selector is opened as 'For Chord Progression' (which has extra controls) the window is too tall for the monitor.
Offhand, I'd suggest fewer but longer rows so that the window is fully on the screen.
https://www.musicdevelopments.com
Home of RapidComposer, Melodya, MIDI Mutator and Syne
Summer Sale • June 3-15 • 40% off RapidComposer, Melodya, MIDI Mutator, Syne
Home of RapidComposer, Melodya, MIDI Mutator and Syne
Summer Sale • June 3-15 • 40% off RapidComposer, Melodya, MIDI Mutator, Syne
