RapidComposer v4 beta feedback and discussion (locked)

[sj1]

Hi again.

Sorry to report v4.6b4 still quits here during a VST3 scan.

[sj1]

Hi.

In Idea Tool, I seem to be observing that with a timeline section selected, regenerating all the active tracks/sections together via Big Lightning works nicely, but trying to regenerate only a single track's section via that track's small lightning is having no effect.

[sj1]

v4.6b4 VST2 scan also failed. There does not seem to be a log file generated for this.

[sj1]

Hi.

I noticed today that the MIDI Mutator is not a live-action thing wrt. the full Composition. The Idea Tool, by contrast, is.

What I mean is that in the Idea Tool I can loop, hear the loop, (re-)generate, undo, redo etc. all while playing back the Composition (or looped section thereof).

In the MIDI Mutator, I cannot do these things, though I immediately wanted to!

At some future point, could the MIDI Mutator be given the same sort of live-action abilities wrt. the Compositoin that the Idea Tool has?

[Mykyndryd_]

"I wanted to ask everyone's opinion about the following: I want you to be able to assign an own instrument to phrases and individual notes. So there won't a strict 1 to 1 relationship between tracks and instruments"

Hi Attila. This is a real departure from the standard DAW like structure and effectively would do away with the need for tracks as you could have one giant canvas with everything happening from within strategically placed phrases including the instruments. This is hugely a great concept. I like it! The biggest drawback I see to this however, is that even though RC isn't a DAW, most people initially approach it as such and it might make RC seem more complicated but what a powerful feature that would be. An exciting thought!

My personal opinion for next development is definitely along the AI-learn functionality on a polyphonic basis.
I know that isn't one of the 2-4 hour developments. (Followed by the "Create me a hit" button )
Cheers. Mike.

[sj1]

-- deleted --

[sj1]

Hi.

I'm observing in the Idea Tool that the Big Lightning is generating across the entire selected area of timeline as it should, but the small lightning on an individual track is only generating across an initial section of the selected area of the timeline.

RC - Timeline Gen Good 01.jpg

RC - Timeline Gen Short 01.jpg

[sj1]

-- deleted --

[musicdevelopments]

Thanks! I added a small button for timeline selection.

When you double-click on the empty area, the timeline is selected automatically, when you have the right setting for "When zooming into lines/parts"

Thanks,
Attila

Hi again.

Adding a 'Select in TImeline' capability to the Structure Browser would be a nice additional support for the workflow mentioned above.


RC -Struture Browser Select in Timeline Action 02.jpg


Actually, probably even better (quicker) would be another tiny icon, for both Parts and Lines, which has the effect of making the timeline selection.

[sj1]

When you double-click on the empty area, the timeline is selected automatically, when you have the right setting for "When zooming into lines/parts"

Ah, I see that now. Nice! Thanks very much.

[sj1]

This morning the single-track lightnings in the Idea Tool changed from doing incorrect partial regenerations (as shown a few posts above) to doing no generations at all.

Aside from fixing this directly, it occurs to me that if we could shift-click on the lightbulb to have it act as a "solo" for Idea Tool generation then this would be a work-around that would allow single-track generation via the Big Lightning.

[magicmusic]

Hi Attila

In the B4 it is same. VST 3 did not allow realtime play with midi keyboard

this i write before . I test with falcon and unify and rc detect correct as multitimbral instrument and midi play work correct in the VST 2 version. but on the VST 3 version the midi data of keyboard is not send to the plugin and no realtime midi play is possible.

[musicdevelopments]

Yes, I am afraid there was still an issue when unloading plug-ins. The good news is that today I fixed all reference count issues, and all VST3 plug-ins now work reliably, and this means scanning, editing, unloading. Even the latest Kontakt 7 works perfectly. A new update will be available in an hour.

I do not recommend scanning VST2 plug-ins at all, this was always dangerous. Loading .dll's into the application and executing them can easily crash the application.

Thanks,
Attila

Hi again.

Sorry to report v4.6b4 still quits here during a VST3 scan.

[musicdevelopments]

Hi magicmusic,

thank you! This is fixed in the update that will be available later today.

Attila

Hi Attila

In the B4 it is same. VST 3 did not allow realtime play with midi keyboard

[musicdevelopments]

Hello Mike,

thanks for your feedback!
You are right, this must be postponed until v6 or v7

I am excited about using machine learning, this is an area that I have zero knowledge about, but it is great that I can always learn something new. I remember more than 30 years ago (!) my friend and me wrote software for a neural network and trained it to recognize all forms of the letter 'A'. It was fun in the good old days.

Thanks!
Attila

My personal opinion for next development is definitely along the AI-learn functionality on a polyphonic basis.
I know that isn't one of the 2-4 hour developments. (Followed by the "Create me a hit" button )
Cheers. Mike.