RapidComposer v4 beta feedback and discussion (locked)

[ValliSoftware]

[*] [macOS] Installer executed as M1 on Apple M1 systems

Installer works great now, thanks.

I'm just testing away.
I'll create a video for how I do my setup with Rapid Composer as a MIDIFX.

[musicdevelopments]

RapidComposer v4.3b13 is available!

Thanks for reporting the bugs!

Fixes:

• Fixed: chords with spaces were not handled correctly in imported MIDI markers
• [Windows] Fixed: VSTi windows are properly refreshing
• [Windows] Fixed deadlock when using VSTi plug-ins

[BluGenes]

lucky 13.. lol.. seems to be working.. just a heads up, beta 12 had the same silent crash. Had to re-boot before installing 13. The issue was probably GUI related, so, it should be resolved with 13..

[musicdevelopments]

Yes, the new UI engine is a substantial low-level change. I expected a few hiccups but I think everything will be fine now. If all goes well, the macOS version will get the same hardware acceleration in a few days. If all this works, new features will arrive much faster.

Thanks,
Attila

[musicdevelopments]

I'll create a video for how I do my setup with Rapid Composer as a MIDIFX.

That would be cool! Thanks in advance!
Attila

[musicdevelopments]

RapidComposer v4.3b14 is available!

Minor fixes in this update:

• Fixed: chords will always be valid and editable when read from MIDI markers
• Fixed: unrecognized chords are smartly handled: e.g. when "9 11" is missing, "9" will be used
• A few complex chords and dozens of alternate chord names have been added to the chords definitions

[lulukom]

Is this a new update rate in action? )))

[sj1]

Fixed: chords will always be valid and editable when read from MIDI markers

Hi,

What exactly is a "MIDI marker" as relates to the new feature here.

As an element of specific terminology, that's not one I am familiar with.

[lulukom]

Well, by the way, me too))

[BluGenes]

It's typically used for a cue point in a DAW..

[Mykyndryd_]

RapidComposer v4.3b14 is available!

Minor fixes in this update:

• Fixed: chords will always be valid and editable when read from MIDI markers
• Fixed: unrecognized chords are smartly handled: e.g. when "9 11" is missing, "9" will be used
• A few complex chords and dozens of alternate chord names have been added to the chords definitions

Thanks Attila. This version is performing well for reading embeded complex chord names.

[BluGenes]

Bug and a crash.. beta 14..

Drag midi on to a track, then delete it, then stretch the timeline out bigger.. RC won't close and eventually crashes.. (I dragged midi from my desktop)

[sj1]

It's typically used for a cue point in a DAW..

Well, "cue points" (aka "markers") in a DAW I understand and use all the time in all my DAWs.

I've always considered them to carry location information (not harmony information) and given them labels (if any) like 'Verse', 'Chorus' etc.

But in what way/format can these even make it into an exported file at all? (other than the DAW's own file format)

Has the MIDI-file spec been expanded since the last time I read thru it? (quite possible!)

What exactly does RC expect/need to see in order to recognize and parse these "MIDI markers"? What DAWs, and what file formats exported from those DAWs, create and hold that info? Is the user then expected to label harmony information instead of location information in the MIDI markers in order to take advantage?

I'm just trying to understand this from a technical/data perspective. This feature could be a great workflow enhancer, or it could be something I'll never use. I can't tell until I understand it in the first place!

[sj1]

And also, if those who are testing the MIDI markers feature could mention the DAW(s) they are using, and how they are testing it, that would be clarifying I think. Thanks!

[BluGenes]

it's described in the midi spec sheet as meta data events.

https://www.cs.cmu.edu/~music/cmsip/rea ... pdated.pdf