RapidComposer v5 beta feedback and discussion

[lulukom]

I support what lovemusic15 wrote and especially with the Mutator .. I will add that there it is necessary to resolve the issue of overlapping (doubling) notes and the possibility of returning to the source file. And probably make the use of algorithms more understandable and yes, everything related to rhythm, of course..

[lulukom]

I hope that maybe even today our wishes come true..))) When we select a chord in the Chord selector, we can choose a chord based on its distance from the tonal center and the color scheme helps with this. What if there is a fader somewhere that adjusts the choice of chords based on distance from the tonal center (closer or farther)?

[lovemusic15]

I support what lovemusic15 wrote and especially with the Mutator .. I will add that there it is necessary to resolve the issue of overlapping (doubling) notes and the possibility of returning to the source file. And probably make the use of algorithms more understandable and yes, everything related to rhythm, of course..

Thank you very much for your comment as always much appreciated I really hope we can get these features added and fixes soon and get the results that we all expect to get when using this software.

I definitely agree that overlapping is a real issue and as soon as my suggestion of changing the rest size rather than just the note length will solve that problem as it's clearly does that in the other software.

[thebutler]

I just came browsing as I noticed a (KVR) alert - and saw it was about the v5.1.1 update; thank you Attila..!

And to lovemusic15 - thanks once again(!) for your efforts, enthusiasm, time and energy providing examples and analysis here in the forum, as to how RC could give a more 'user-friendly' workflow to help ALL users of RC.

[sj1]

it is necessary to resolve the issue of overlapping (doubling) notes and the possibility of returning to the source file.

Overlapping notes I'd put in the category of "bug". That needs to be fixed for the RC algos as they currently exist to be efficiently usable because having to manually edit out such overlaps is anything but "rapid".

Beyond that, there are certainly ideas well-expressed in Captain plugs that could usefully be expressed in new generators/algos in RC. Sometimes when something has been done quite well, imitating makes perfect sense.

So, I suggest adding on, rather than gutting and redoing what's there now - with the caveat that where/if what's there now is truly arguably "wrong", then it should be fixed in order to be a proper expression of exactly what it is.
--
That said, I (we?) have yet to look specifically at whether all the right plumbing exists for RC and Captain/Pilot systems to be used rapidly together. (I too have all these plugs) I think this should be seriously examined first before committing to implementing extensive new algos from scratch.

Our musical eco-systems are getting more integrated overall as time goes by and improvements are made. Sometimes though, corners of interoperability are overlooked to great frustration here "in the field".

Almost always, from my POV, gains of synergy arising from removing interop roadblocks are some of the greatest gains possible!

[sj1]

BTW, I never get notices when the formal product (rather than a beta) is updated. Can anyone tell me where I can turn that on? Thanks!

[lovemusic15]

I just came browsing as I noticed a (KVR) alert - and saw it was about the v5.1.1 update; thank you Attila..!

And to lovemusic15 - thanks once again(!) for your efforts, enthusiasm, time and energy providing examples and analysis here in the forum, as to how RC could give a more 'user-friendly' workflow to help ALL users of RC.

Really appreciate your comments and support, glad you appreciate where I'm trying to go when it comes to simplicity and ease of use, making music is about pure passion and excitement so it's important that a software can help us with that and not hold us up scratching our head trying to work things out.

[lovemusic15]

it is necessary to resolve the issue of overlapping (doubling) notes and the possibility of returning to the source file.

Overlapping notes I'd put in the category of "bug". That needs to be fixed for the RC algos as they currently exist to be efficiently usable because having to manually edit out such overlaps is anything but "rapid".

Beyond that, there are certainly ideas well-expressed in Captain plugs that could usefully be expressed in new generators/algos in RC. Sometimes when something has been done quite well, imitating makes perfect sense.

So, I suggest adding on, rather than gutting and redoing what's there now - with the caveat that where/if what's there now is truly arguably "wrong", then it should be fixed in order to be a proper expression of exactly what it is.
--
That said, I (we?) have yet to look specifically at whether all the right plumbing exists for RC and Captain/Pilot systems to be used rapidly together. (I too have all these plugs) I think this should be seriously examined first before committing to implementing extensive new algos from scratch.

Our musical eco-systems are getting more integrated overall as time goes by and improvements are made. Sometimes though, corners of interoperability are overlooked to great frustration here "in the field".

Almost always, from my POV, gains of synergy arising from removing interop roadblocks are some of the greatest gains possible!

I appreciate your insights and feedback on my suggestions. To clarify, during the MIDI Mutator beta testing, the note overlapping issue was discussed, and I was informed that it's a result of the number of notes in the MIDI, not a bug. However, my belief is that it may be related to the algorithm not analyzing rests but focusing solely on note lengths. This was demonstrated in the syncopation situation within Pilot plugins and their algorithms.

I want to emphasize that my mockups might have given the wrong impression. I am not proposing a complete restart of the algorithm. Instead, my suggestion is to work with the existing structure and incorporate improvements using algorithms found inside Captain plugins.

For the past three years, I've advocated for working more with custom phrases due to frustrations with generators. Unfortunately, achieving the desired results was challenging due to the algorithm's limitations. I acknowledge that Attila is not a producer, but he does value user feedback. While I appreciate Captain plugins being designed by producers, Attila's openness to user input is commendable.

I want to clarify that the issues I'm addressing are not bugs but rather aspects missing from the algorithms and necessary fixes. The required changes are not extensive, as I've manually implemented similar alterations to MIDI files, demonstrating the ability to change the overall shape while maintaining rhythm.

I'm aware Attila operates based on demand, and I can confirm there's potential for RC to seamlessly work with Captain chords based on my comparison tests. The goal is to maintain RC's unique capabilities while upgrading certain aspects, much like enhancing the furniture inside a house without altering its exterior.

I invested in Captain chords and Pilot plugins because I couldn't achieve the desired results in RC. I believe that by addressing these algorithmic aspects, RC can become an all-encompassing solution, offering the best of both worlds.

I hope this clarifies my perspective, and I appreciate the support. Let's work together to enhance RC for everyone's benefit.

[sj1]

I love the thoughtfulness of the users on this Forum!

[BluGenes]

[deleted]

[musicdevelopments]

Thanks lovemusic15 for the mock-up screenshots and all your suggestions!
Now I started implementing them. I am sure I'll have questions because I have never used the mentioned plug-ins and I am neither a producer or composer. But I'll do my best to understand what you meant with the individual knobs, sliders and menu items.

I think I'll build a beta version for the small improvements added in the past 2 days, and let the big rhythm rework begin!

Thanks,
Attila

[lovemusic15]

Thanks lovemusic15 for the mock-up screenshots and all your suggestions!
Now I started implementing them. I am sure I'll have questions because I have never used the mentioned plug-ins and I am neither a producer or composer. But I'll do my best to understand what you meant with the individual knobs, sliders and menu items.

I think I'll build a beta version for the small improvements added in the past 2 days, and let the big rhythm rework begin!

Thanks,
Attila

That's great Attila, if you want I can make a step-by-step video demonstrating each part. I can show you from a producers workflow perspective if that helps

[musicdevelopments]

RapidComposer v5.2b1 is available!

Just a few minor improvements, like keyboard shortcuts added.

Improvements:

• Keyboard shortcuts added for forward/rewind
• Keyboard shortcut added for collecting all scales for the selected chords. The scales are displayed below the master track.
• Keyboard shortcut added for opening the VST editor for the selected track
• (Phrase Inspector) Option added to save multiple selected phrases as rhythm into the rhythm browser
• (Phrase Inspector) Saving phrases/rhythm into the browser is many times faster

[BluGenes]

You fix the the threading crash?

[BluGenes]