v3 Beta Feedback And Discussion (Bugs, Features, Suggestions)

[DavidBluecame]

Hello,

Thanks for this magnificent piece of software!!! A few bugs I've found in 3.7b4:
* In the Idea Tool, when you set a track as Type: percussion and drag the Percussion Generator to the Phrases box, if you right click the Percussion Generator in the Phrases box and click in the magic wand, there is no information about the rhythms / instruments in the drum kit (or it appears garbled and useless). If you set the Track Type: Normal, then you can see the Percussion Generator magic wand information correctly.
* The Percussion Generator in Idea Tool seems to ignore the Rhythms set in the Rhythms Pattern box.
* If you import a Midi file (with 2 tracks and more than 64 bars for example) and in the Idea Tool you set: Use Existing Melody Track: Track1, Length=64bars, Track2 Phrase for example Chords Generator and click the main Generate Track button, it generates a track of only 16 bars! In some cases I have seen the software gets somehow "locked" to 16bars so further attempts to import the Midi file get limited to 16 bars even if the Midi file is longer (this does not always happen, it's difficult to replicate)

I've also been suffering a recurrent bug starting with v3.65 (the first version I used), where the instruments used in the tracks sometimes (randomly?) get lost and revert back to RCPiano.sf2. That happened to me quite a few times (irrecoverably losing all my VST instrument settings or settings for other General Midi or SF2 instruments). So far I've been unable to replicate the problem which seems to be quite random. This particular bug drives me crazy and forces me to use a DAW to ensure I don't lose instrument settings when I could be using RC instead as a VST/SF2 host...

Thanks and Best regards!

[musicdevelopments]

I would also like, together with the composition to save the active track and active solo buttons .. Thank you.

The solo states are saved from the next beta version.
Thanks,
Attila

[musicdevelopments]

You are so right! I am fixing this right now. I have no idea when it went wrong.

Thanks for reporting this bug!
Attila

EDIT: bug is fixed. Only "Start With Empty Master Track" was affected.

need verification on this one please..

In settings, new composition, click "start with empty master track", 12 bars

your default key should be C major and the new composition master track should be 12 bars of "I" chords. Now, click the scale on the master track and set this to A Major. What do you get? Mine fills with #II..

[musicdevelopments]

Hi David,

Thank you for reporting these bugs. I'll fix them ASAP.

I've also been suffering a recurrent bug starting with v3.65 (the first version I used), where the instruments used in the tracks sometimes (randomly?) get lost and revert back to RCPiano.sf2

This is annoying. Strangely no-one else reported this bug yet. Does this happen when you use UNDO? It would be good to fix.

Thanks!
Attila

[BluGenes]

Hey ! Thanks.. wasn't sure if was me or not.. lol..

what would be kinda cool is the ability to set a specific progression for a new composition. Think of those lonely blues artists out there that play that one progression almost all the time.. lol but seriously, I can see potential time savings there. You could start with whatever you wanted, then just change a couple of chords as needed..

[musicdevelopments]

For this purpose I recommend saving your default new composition as a template. Then you can just click on "Templates" next to "New Composition".

[BluGenes]

oh yea.. lol nm..

[DavidBluecame]

Hi David,

Thank you for reporting these bugs. I'll fix them ASAP.

I've also been suffering a recurrent bug starting with v3.65 (the first version I used), where the instruments used in the tracks sometimes (randomly?) get lost and revert back to RCPiano.sf2

This is annoying. Strangely no-one else reported this bug yet. Does this happen when you use UNDO? It would be good to fix.

Thanks!
Attila

Hi, Attila. I understand, it's a weird and difficult to replicate problem. I will put some effort to try to replicate it. If I can find a procedure to replicate it I'll let you know.

Thank you!

[DavidBluecame]

EDIT: Please ignore this post, I found a setting controlling this. I will investigate more how the Melody Generator works.

Hello,

I'm not sure if this is a bug or not, but it certainly looks like one:
* I created a new composition (basic 4 bars)
* Inserted a melody generator in the first bar
* Set it to "chords only"
* Strangely enough, there were still some notes from the scale but not from the chord there, no matter how many times did I regenerate. I expected the "chords only" mode to generate notes only in the chord.
* If I set the climax to "no climax", then the "previous to the last" note in the melody generator is *never* a chord note. I tried to regenerate many times and all other notes were chord notes except that one which was never a chord note. When I set the interval in 4 equal divisions, the 3rd note was never a chord note. If I set it to 16 equal divisions, for example, the note number 15 in the melody was never a chord note.

That seems weird to me, could it be some kind of algorithm issue or rounding error somewhere in the Melody Generator? If there were (hypothetically) a bug there, I suppose it could also affect the other modes in the Melody Generator, not only the "chords only"?

If this is considered normal and expected behaviour please let me know.

Thanks and best regards!

[DavidBluecame]

EDIT: Please ignore this post, I found a setting controlling this. I will investigate more how the Melody Generator works.

I've tried uninstalling 3.7b4 and reinstalling v3.65 but the same issue happens:

[DavidBluecame]

Please forget about this, I found the setting "Penultimate note is step above tonic"!!!! My mistake, sorry for make you waste your time reading this.

Best regards!

[DavidBluecame]

Hello,

About the "instrument lost" issue, your comment about "undo" gave me a clue. I'm not sure that this is what happened to me, but yes there seems to be some kind of issue with the "undo" function. For example:
* Create a new composition, all defaults.
* Change the instrument in the track to any preset, i.e. Nylon Guitar
* Drag some Phrases and/or Generators (Arpeggio, Melody, for example) to the track, but do not move them afterwards (note: if you go to History you will see that there are no entries for the actions of dragging generators into the track)
* Undo just once
* All the generators disappear, and the patch preset reverts back to the original.

So it seems that dragging phrases/generators into the composition is not recorded in the history, so if you "undo" that, it will actually undo all the "dragged" phrases *and* the last "recorded" action (instrument patch change in this case)

During one of my tests with undo, I got a crash. I have not been able to replicate it yet.

Thanks and best regards!

[DavidBluecame]

Another "annoyance" related to undo is that, if you change the vertical zoom within a track (to see the notes "taller"), when you perform an "undo" operation the vertical zoom reverts back to the default and you have to, again, adjust the vertical zoom in the track(s). This is not as important as the problem above but certainly annoying

Thanks!

[DavidBluecame]

FYI: When you select a phrase and you use "Alt-Drag" or "Alt-Shift-Drag" and you dropped the "rhythmized" version of the phrase in the track, it does not get recorded in the history either.

[DavidBluecame]

I'm not sure if this is a bug, but some specific track changes are not recorded in the history. For example when you change the name/color of a track, or when you change the state of a VSTi instrument, they do not appear in the history. However, perhaps this is the intended behaviour?