RapidComposer v4 feedback and discussion

Official support for: musicdevelopments.com
User avatar
KVRist
173 posts since 11 May, 2014

Post Wed Nov 24, 2021 8:36 am

musicdevelopments wrote:
Tue Nov 23, 2021 9:12 am
[*] [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.

User avatar
KVRAF

Topic Starter

4600 posts since 9 Jan, 2010

Post Wed Nov 24, 2021 10:54 am

RapidComposer v4.3b13 is available!

Thanks for reporting the bugs! :tu:

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
https://www.musicdevelopments.com
Innovative music software for creative musicians - home of RapidComposer, Melodya and Syne

KVRian
1327 posts since 15 May, 2017

Post Wed Nov 24, 2021 11:25 am

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..

User avatar
KVRAF

Topic Starter

4600 posts since 9 Jan, 2010

Post Wed Nov 24, 2021 9:59 pm

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
https://www.musicdevelopments.com
Innovative music software for creative musicians - home of RapidComposer, Melodya and Syne

User avatar
KVRAF

Topic Starter

4600 posts since 9 Jan, 2010

Post Thu Nov 25, 2021 2:22 am

ValliSoftware wrote:
Wed Nov 24, 2021 8:36 am
I'll create a video for how I do my setup with Rapid Composer as a MIDIFX.
That would be cool! Thanks in advance! :clap:
Attila
https://www.musicdevelopments.com
Innovative music software for creative musicians - home of RapidComposer, Melodya and Syne

User avatar
KVRAF

Topic Starter

4600 posts since 9 Jan, 2010

Post Thu Nov 25, 2021 10:01 am

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
https://www.musicdevelopments.com
Innovative music software for creative musicians - home of RapidComposer, Melodya and Syne

KVRian
1328 posts since 30 Nov, 2013

Post Thu Nov 25, 2021 10:07 am

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

User avatar
sj1
KVRian
601 posts since 13 Mar, 2017

Post Thu Nov 25, 2021 11:46 am

musicdevelopments wrote:
Thu Nov 25, 2021 10:01 am
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.
Last edited by sj1 on Fri Nov 26, 2021 3:36 am, edited 1 time in total.

KVRian
1328 posts since 30 Nov, 2013

Post Thu Nov 25, 2021 11:48 am

Well, by the way, me too))

KVRian
1327 posts since 15 May, 2017

Post Thu Nov 25, 2021 12:58 pm

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

User avatar
KVRist
189 posts since 10 Feb, 2018 from Cumbria, UK

Post Thu Nov 25, 2021 2:03 pm

musicdevelopments wrote:
Thu Nov 25, 2021 10:01 am
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. :tu:

KVRian
1327 posts since 15 May, 2017

Post Thu Nov 25, 2021 2:05 pm

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)

User avatar
sj1
KVRian
601 posts since 13 Mar, 2017

Post Fri Nov 26, 2021 3:44 am

BluGenes wrote:
Thu Nov 25, 2021 12:58 pm
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! :wink:

User avatar
sj1
KVRian
601 posts since 13 Mar, 2017

Post Fri Nov 26, 2021 3:46 am

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!

KVRian
1327 posts since 15 May, 2017

Post Fri Nov 26, 2021 4:39 am

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

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

Return to “MusicDevelopments”