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

[BluGenes]

major bug.. phrases are disappearing..

edit: k, now it's working.. closed and restarted..

edit: now it's back.. It's the apply melody, using a melody generator

[musicdevelopments]

Hi Nigel!
Thanks for your very kind comment , and for being so helpful and enthusiastic for so many years.
Definitely no boardroom meetings
Attila

Every few days since it's release 10 years ago there has been fixes and new features added.
The development decisions don't have to go up through a hierarchy to be discussed in a boardroom meeting.
I think we are actually communicating with a higher being from another planet that has tapped into our internet, Attila is just the earthly name

[musicdevelopments]

Yes, you are right, this behaviour has changed.
I added new settings to the playback options, and moved another one from Settings / Miscellaneous to its logical place:

It seems that "Automatic Timeline Selection Playback Head Capture" (if I may so term it) is currently an undefeatable built-in behavior. I've seen no demonstrable counter-example to this so far.

I am suggesting that it would be better if this were not the case, by which I mean that for playback to begin from the current location of the playback head (however that was arrived at) would always be appropriate.

[sj1]

I limited the number of chords to 16 when using {chords}. It makes no sense to make a very long file name consisting of a hundred chord names.

Hi Attilla,

Thank you for your response! Briefly on this particular first -

I agree about hundreds, but not necessarily about 16. My point-of-reference would be a typical jazz tune form of say, 32 bars. There might be as many as (and generally no more than) 2 chords per bar.

Hence, if there has to be a hard-coded limit, I would suggest 64 or a tad higher.

Yes, it is true that exporting the whole form using {chords} is a semi-extreme case, but really I'd say the goal here is is to let the user work within whatever form(s) they wish rather than to pre-figure a limitation in that respect. OTOH, if there is a file name size limit per the OS, then that's not on RC!

I say semi-extreme because I've been routinely exporting half-forms, and in some cases full forms.

Also, whenever it might be necessary to edit lengths after an export, it is much easier and quicker to discard MIDI and name characters from longer clips to make shorter ones than it is to assemble together MIDI and name characters from shorter clips to make longer ones.

If you love 16 here, you could make this a settable option with 16 as the default. Only nuts like me might raise the number higher. It's a flexibility I'd appreciate to have.

This comment ran for longer than I thought ... (more to come on the other subject).

[sj1]

Yes, you are right, this behaviour has changed.
I added new settings to the playback options, and moved another one from Settings / Miscellaneous to its logical place:

You mean this is coming in the next beta? (b29)

[sj1]

this is a mystery because I was able to Ctrl-drag the chords track and it created a valid MIDI file. You are right that the notes are missing from the MIDI file on your screenshots, but how did you make that MIDI file?

I loaded SJ_Summertime_02a.rcCOMP, 4 bars were already selected, I did nothing but dragged the first track using Ctrl-drag and dropped to a folder (on Windows). The MIDI file included the notes.

I did not have luck with your previous upload either. The second chords track did not contain any phrases. Was it intended? I have checked the rcCOMP file and there were no phrases saved with the second track. I suspect that some settings are different on our setup.

Thank you kindly for trying it out and letting me know your findings.

I'm now suspecting user error. (Mea culpa!) I think I somehow slipped into thinking that {chords} would not only create names but also generate the chord symbols into notes auto-magically! My apologies.

[sj1]

I would like to ask about MIDI Export being tied to the timeline selection rather than the chord symbol selection.

For example, in this picture:

RC - Timeline vs. Chords 01.jpg

The actual export will be of the chords A7 Dm7 A7 Dm7, whereas the track and exported file title is (Gm7 C7 Fm7 Bb7 Em7b5).mid.

Offhand, I would tend to favor this kind of export to be of the selected chord area (thus with no chance of a name mismatch) rather than the selected timeline area. Perhaps though there is a good reason for using the selected timeline area. Could you consider and comment?

I will try to train myself not to allow/create such mismatches if necessary (but it would be cool from my POV if they simply could not happen).

[BluGenes]

Anyone else having issues with phrases disappearing?

[musicdevelopments]

All right, I increased the maximum chord count in file-names to 64.

I agree about hundreds, but not necessarily about 16. My point-of-reference would be a typical jazz tune form of say, 32 bars. There might be as many as (and generally no more than) 2 chords per bar.

Hence, if there has to be a hard-coded limit, I would suggest 64 or a tad higher.

[musicdevelopments]

Yes, indeed! In about 2 hours...

You mean this is coming in the next beta? (b29)

[musicdevelopments]

Hi BluGenes,

in what circumstances did they disappear? After saving and loading, or when applying variations?

BTW there are collapse/expand buttons added to variations, as well as a mute/unmute button that lets you easily turn off variations, and turn them back on:



Thanks,
Attila

Anyone else having issues with phrases disappearing?

[yellukhan]

Thank you so much Attila!

a quick look..
i am not seeing that collapse-expand-mute options
am i missing something?

[lulukom]

I think it will appear within 2 hours)

[musicdevelopments]

Yes, sorry for the teaser... I'll upload it shortly.

[yellukhan]

ah!
i thought 3.9b28 was the latest
its my fault, sorry