MusicDevelopments

BluGenes · Post by **BluGenes** » Tue Jul 07, 2020 2:09 pm

Happens to me to in Win version..

lulukom · Post by **lulukom** » Tue Jul 07, 2020 2:12 pm

Is it always or sometimes ?

BluGenes · Post by **BluGenes** » Tue Jul 07, 2020 2:16 pm

seems to be always.. I added tempos to the middle of a composition and it changes the start tempo.. (and it ignored the changes)

lulukom · Post by **lulukom** » Tue Jul 07, 2020 2:18 pm

So there is a problem (

BluGenes · Post by **BluGenes** » Tue Jul 07, 2020 2:20 pm

sj1 wrote: Mon Jul 06, 2020 6:03 pm Here, I'm just focusing and asking about working with RC itself, "after-the-fact" as it were. It is RC that gets me where I ultimately want to go here, and the RC environment is preferred!

Hey, no problem, it is what it is.. This conversation reminded me of a video I did a while ago and it shows the difference between a mock up and a finished composition. You can not do what I did in RC, just can't be done.. check it out if you have time, think the run time is about 5 minutes..

viewtopic.php?p=7824743#p7824743

BluGenes · Post by **BluGenes** » Tue Jul 07, 2020 2:21 pm

lulukom wrote: Tue Jul 07, 2020 2:18 pm So there is a problem (

yup.. great catch man! not get the attention of the wizard locked in that dungeon.. hehehe

sj1 · Post by **sj1** » Tue Jul 07, 2020 5:27 pm

BluGenes wrote: Tue Jul 07, 2020 2:20 pm You can not do what I did in RC, just can't be done..

I like it it!

Certainly RC has it's own special and important set of goals, not precisely identical with those of other programs and general purpose DAWs.

Even among DAWs per se, there really is no "one DAW to rule them all". Sometimes a given DAW is reluctant to incorporate what is -clearly- a superior feature of another, and that can be lamentable. In many cases however, TMTOWTDI and opinions will differ on which way or how many alternatives to implement. Different tools serve different jobs, and different personalities.

Sometimes all the tools fall short of wants and needs that seem pretty obvious to one or some set of users. C'est la Vie, but it is certainly fair for anyone to describe what they hope for and why. Doing so can help further creativity and evolution in broadly beneficial ways.

RC has many unique aspects, and these are it's primary strengths. Trying to match general purpose DAWs feature-for-feature would take more away from RC's line of development than would be added to it (IMO).

What I would count as *very* important for RC is "easy in", "easy edit", and "easy out". This will allow RC to be a most excellent productive companion to whatever other general purpose DAW(s) someone uses.

RC has some very good MIDI import and export features. Personally I'm very impressed here, and even more so now with the new {chords} tag and sectional drag-outs with the chord names. This is great stuff!

I do think that "easy edit" must include the easy definition and re-arrangement of the composition's sub-structures inside RC. I'd be surprised if Attila's own ideas in this area have not already visited and gone beyond my own. Some of it still awaits coding though ...

So, my own comments in this area are simply documenting specifically where I see (or sometimes hit) potholes in my personal commute. YMMV.

P.S. No lack of DAWs here, take my word for it!

musicdevelopments · Post by **musicdevelopments** » Wed Jul 08, 2020 9:27 am

Hi sj1,

it is important to keep in mind that
1. scales (like tempo and signature) are inherited from higher structural levels (composition > parts > lines > chords).
2. you can change the scale for the composition, parts, lines and for the smallest unit, chord boxes.

This means if you use a new scale under a chord, the scale will automatically change back to the old scale after the chord.
That is you are overriding the scale for the duration of a chord but the scale is restored at the beginning of the next chord. This is the explanation that you cannot 'remove' the scale change for the next chord. However you can insert another scale change.

I know it sounds complicated and not logical, and you were not the only user who complained about it (rightfully), but this is how the inheritance works in RC. Most people think linearly, like in a DAW you insert a tempo change, which remains active for the rest of the timeline until another tempo change is inserted. Maybe I should simulate this behavior for a better user experience?

Thanks,
Attila

sj1 wrote: Fri Jun 26, 2020 9:20 pm Hi,

I'm finding the 'Remove Scale Change' button to be extremely elusive.

This picture shows a successful access to the 'Remove Scale Change' button after right-clicking on "C Major", but right-clicking on the (redundant) "Ab Major" just before (in an attempt to delete it) does not produce the 'Remove Scale Change' button. Similar experiences take place for me throughout the timeline.

musicdevelopments · Post by **musicdevelopments** » Wed Jul 08, 2020 9:41 am

Hi lulukom, BluGenes,

how can I reproduce this? It works well here. I can insert a tempo/scale/signature change to anywhere:

I tried this on macOS too, using beta22.
The next beta version is ready but I don't want to upload it until I fix all/most bugs reported here.
So please describe what I need to do to reproduce this.

Thanks for your help!
Attila

lulukom wrote: Tue Jul 07, 2020 12:40 pm Hello to all !
Is it just me or everyone ...?
The new scale, tempo and signature are inserted only at the beginning of the master track, but not where the cursor is! You cannot insert scale, tempo and signature anywhere in the master track (((((((
But it seems to me that someone reported this? I missed it and now I got it myself ((((
Or now everyone plays from beginning to end only in C Major 4/4 and T = 120?)))))))
(Mac Os Mojave / RC 3.9 b22 )

musicdevelopments · Post by **musicdevelopments** » Wed Jul 08, 2020 9:55 am

An example when the scale or tempo is overridden for a chord box. Please note the 'path' ('AC' is an internal name for the chord box):

The next tempo refers to the composition tempo. It is "physically" the same as the composition tempo, so if you change that, you change the composition tempo...

BluGenes wrote: Tue Jul 07, 2020 2:16 pm seems to be always.. I added tempos to the middle of a composition and it changes the start tempo.. (and it ignored the changes)

BluGenes · Post by **BluGenes** » Wed Jul 08, 2020 10:08 am

ok, my fault.. tempo change is working for me.. What I did was a super duper massive over the top example.. lol I used default tempo, then dropped to 20 bpm in the middle for one bar and it did work.

edit: however.. the first time it allowed the change and worked.. (as defined in part line) now it says as defined in composition.. and it can't be deleted..

musicdevelopments · Post by **musicdevelopments** » Wed Jul 08, 2020 10:09 am

BluGenes wrote: Sun Jun 28, 2020 3:35 pm yes.. If you did in the correct steps, then RC not running when FX window closed..

Right, at the moment all initialization takes place when the editor window is opened.
Is this a big issue? I cannot easily fix this

Only by loosing hair

Thanks,
Attila

BluGenes · Post by **BluGenes** » Wed Jul 08, 2020 10:13 am

lol

see edit post

BluGenes · Post by **BluGenes** » Wed Jul 08, 2020 10:16 am

oh no.. well, i can live with that, it just behaves as it did when RC was bridged as a vst... thought that since you switched to the vst3 it would be different..

BluGenes · Post by **BluGenes** » Wed Jul 08, 2020 10:27 am

ON tempo change, never mind.. I finally understand it.. I was having an issue with removal and tempo changes longer than one bar. If you work backwards in the progression, you can force longer tempo changes. And once you remove the changes, everything reverts back properly.. I'll point this out in my next video... best explained by example...

MusicDevelopments

KVR Audio

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