Bug reports

[musicdevelopments]

https://i.imgur.com/XEKaAZU.png
I think phrase order is broken

You need to uncheck "Select phrases from the list in random order":



By default 'A', 'B', 'C', etc are not assigned in the order of phrases in the list.

Thanks,
Attila

[heliacal]

I am still getting a 2+ minute shutdown of DAW's when Rapid Composer is used as a VST.

Please always include whether you are on macOS or Windows, and even more details are welcome, like DAW + versions.

I assume you are on macOS, and your Documents folder is on iCloud. Does your DAW have read/write access to your ~/Documents folder?

If your DAW is not Logic Pro X, please start your DAW in the Terminal, and examine the printouts when you shut it down with RapidComposer. (This does not work with Logic Pro X as it hosts instruments in another process.)

Thanks,
Attila

Oh god, I'm so sorry. Yes my desktop is a Mac. Actually I was syncing my RC documents folder with One Drive so it would sync with my Surface Pro. My bad...

[Brian Collins]

Here's a nasty one for you.

Occasionally RC causes Studio One to completely crash out on Windows. Unfortunately there is no pattern to any triggering cause - it generally happens after a while. Other than the disruption to my "flow", I can live with it, as I have S1 configured to take regular backups and I don't expect to lose more than five minute's work. And I am only doing this for fun - my livelihood is not at risk!

However, S1 does provide a DMP file which unambiguously points the finger to a null-reference bug in RC. There is a stack dump, which would require the SYM files from your Windows VST build to interpret. But if you have such files, it provides an opportunity to track down a fatal crash. I am running the unreleased "5.5.4fixed" version.

The top-level text analysis of the DMP file can be found at http://www.brianavid.co.uk/RC-Crash-Jun-13.txt. And of course I can send you the DMP file itself if it would help you.

[Brian Collins]

See the video: [DELETED - re-recording below]

Following this recipe, the chord notes displayed in the phrase editor are confused between scale-relative and chord-relative. I am not sure I can trust what it it has internally and how the phrase can be used in different contexts.

EDIT: I now have an explanation - an unexpected setting controls how chords are displayed. There is no bug here

[thebutler]

See the video:

Following this recipe, the chord notes displayed in the phrase editor are confused between scale-relative and chord-relative. I am not sure I can trust what it it has internally and how the phrase can be used in different contexts.

Brian - can you re-record (or re-render the output) with better narration level please.? It's super low volume and can't really make out what all you're describing...

(headphones aren't to hand and I suspect won't be for many others too.. )

[Brian Collins]

Re-recorded at . Hopefully that will be louder enough

[thebutler]

Yes, better thanks.!

I kind of see what you mean and what you're getting at; but needs someone with deeper RC inside knowledge than me to comment either way I'm afraid. Maybe Attila or Gene Brown (BluGenes) will see your post.. (mind, I think Attila is pretty busy working on a v6 of RC for us..!).

[Brian Collins]

I kind of see what you mean and what you're getting at; but needs someone with deeper RC inside knowledge than me to comment either way I'm afraid. Maybe Attila or Gene Brown (BluGenes) will see your post.. (mind, I think Attila is pretty busy working on a v6 of RC for us..!).

I now have an explanation and there is no bug here. I had an unexpected setting. Thanks for looking at it

[musicdevelopments]

Here's a nasty one for you.

Occasionally RC causes Studio One to completely crash out on Windows.

Hi Brian,

this is worrying. I'd be grateful if you temporarily use the VST3 version with full debug symbols (that I'll send you in PM) and let me know where it crashes. I'd love to fix this serious bug.

Many thanks for your help!
Attila

[Brian Collins]

Two things:

1) Still no crash today with the debug VST, though I am having great fun trying

2) In one of my "fun" attempts, I added a tempo ritardando in Studio One and the RC playhead went very weird. See the video at:
Watch the S1 playhead at the top as it follows the Tempo track. and see what RC does when the tempo changes.

[musicdevelopments]

Yes, I am afraid this is not really implemented. When RC receives a tempo change from the host during playback, it applies the new tempo as if the whole composition uses that tempo. Real-time tempo changes aren't handled yet.

[Brian Collins]

Yes, I am afraid this is not really implemented. When RC receives a tempo change from the host during playback, it applies the new tempo as if the whole composition uses that tempo. Real-time tempo changes aren't handled yet.

I guessed that might be the case. It looked as RC is basing timing on real time (seconds) and computing the bar location from the most recently set tempo at that real time number of seconds. So the RC play head can accelerate, decelerate or (in my case) go backwards. I shall use Midi copies in my DAW when I want to play with tempos.

[thebutler]

Real-time tempo changes aren't handled yet.

Has to be a good candidate for inclusion in v6...

[Brian Collins]

A minor display bug.

With automatic sharps and flats setting, in C Mixolydian, generally I see B-flat, but the progression is giving me A-sharp:


I am reporting just about everything that looks like a bug. I hope that is what is wanted. I am playing for hours with RC to try to get it to crash again, so I have a lot of opportunity to find strangenesses.

BTW ... what are the check-boxes that sometimes appear in the header against scale, tempo and time signature? I am guessing it relates somehow to the host DAW.

[musicdevelopments]

A minor display bug.

With automatic sharps and flats setting, in C Mixolydian, generally I see B-flat, but the progression is giving me A-sharp:

You are perfectly right! I improved Scale::IsFlatOrSharp() to include all church modes!

I am reporting just about everything that looks like a bug. I hope that is what is wanted.

Yes, thank you, I am grateful for all bugs reported!

BTW ... what are the check-boxes that sometimes appear in the header against scale, tempo and time signature? I am guessing it relates somehow to the host DAW.

The check boxes mean that you want to override higher-level settings. By default scale/tempo/signature are inherited from highest level (composition) to the lowest level (chord section). The hierarchy levels: Composition -> Parts -> Lines -> Chord sections. These can be overridden, just like you assigned a different scale to the first chord in Part 1, Line 3. Note that you typically override scale in Parts or Lines, but of course it is possible to use your own scale for the duration of a chord.

Thanks,
Attila