v5.65rc5 - December 9 2017

[Triode]

v5.65rc5 - December 9 2017
+ Fades: improve behavior of crossfade shape actions [t=200422]
# API: always return current tempo from GetTempoTimeSigMarker, but only return time signature if the marker sets a new time signature [p=1922791]
# Preferences: increase size of control surface settings window
# Ruler: let the timeline get a bit smaller

[EvilDragon]

Originally Posted by Triode

# Preferences: increase size of control surface settings window

Why, now there's lots of empty space everywhere? At least elements inside the larger window would need to be centered, or repositioned/enlarged to fit?


(Thanks for adding more info about web interface in the main Preferences section, though!)

[ovnis]

" # Ruler: let the timeline get a bit smaller "
Great ! Thx.

[heda]

some glitches in freehand tempo


thanks for let the timeline get a bit smaller
what about making it larger. The icons in the main toolbar don't get larger, as other toolbars do when there is room and the Preference/Appearance/Don't scale toolbar buttons above 1:1 is off.

[EvilDragon]

I can confirm the above ^^^ happening for freehand tempo drawing.

[juliansader]

I'm a few versions late, but...

Originally Posted by Edgemeal

v5.65pre16 - November 22 2017
+ Ruler: control+shift+drag on tempo markers adjusts tempo on both sides of marker

This (wonderful) mouse modifier does not appear to work on timesig markers.

[EvilDragon]

Yes, because it's supposed to map tempo, not timesig changes?

[Edgemeal]

Reaper hung on me while drawing tempo, So I close Reaper from taskbar and Windows (Win7_x64) shows message "Reaper not responding", I then created a dump file, then click OK on the windows message and the Reaper exe exited. Not sure if the dump file is useful or not, will leave on google for a day...

Reaper_5.65.RC5_Dump.zip
https://drive.google.com/open?id=1Yv...1YELChA0CBmzPn

[juliansader]

Originally Posted by EvilDragon

Yes, because it's supposed to map tempo, not timesig changes?

It should change the *tempo* of the marker, without affecting the time signature.

[Justin]

Originally Posted by juliansader

I'm a few versions late, but...



This (wonderful) mouse modifier does not appear to work on timesig markers.

Hmm yeah I think we can make that work

[Mercado_Negro]

Selected automation items now look darker (label color) and letters are black. It's very hard to read that now.

[Klangfarben]

Originally Posted by heda

what about making it larger. The icons in the main toolbar don't get larger, as other toolbars do when there is room and the Preference/Appearance/Don't scale toolbar buttons above 1:1 is off.

This would be great if it scaled like other toolbars.

[Edgemeal]

Hung again when drawing tempo, All I really did was add some markers, a couple regions, moved those around a bit, went to draw tempo again and hung. This time I saved to dump before attempting to close Reaper. HTH.

Reaper_5.65.RC5_Dump(2).zip
https://drive.google.com/open?id=1MY...5xNfFh4OraK1Ob

[FnA]

Hung REAPER within 3 seconds three times in a row. Win7 x64.

New project
-Alt+T show tempo envelope
-Jerk Control drag back and forth moving to bottom of lane

[Eddy]

can tempo be automated with a controller now?

[EvilDragon]

Originally Posted by Mercado_Negro

Selected automation items now look darker (label color) and letters are black. It's very hard to read that now.

Hm, that didn't change in this prerelease cycle.

[Soli Deo Gloria]

First of all, Justin, immense thanks for bringing back the functionality to make Breeder´s actions work again!!!!. This is extremely valuable, really!! On my first rough tests, they seem to work as before. As I continue working with them I will be paying careful attention to their behaviour.

Originally Posted by heda

some glitches in freehand tempo

Originally Posted by EvilDragon

I can confirm the above ^^^ happening for freehand tempo drawing.

That is with the native freehand drawing, isn´t it? With "SWS/BR: Freehand draw envelope while snapping points to left side grid line (perform until shortcut released)" I can´t seem to replicate the issue, so it probably has something to do with the native implementation. I recall that one of the first actions Breeder designed to achieve freehand drawing in Reaper´s tempo envelope, a couple of years ago, showed a similar buggy behaviour. If I remember correctly, he finally conceived the freehand action snapping points to left side, as the title implies, to avoid this issue. He explained the reason to me on that occasion, but I am not able to find the mail, at this moment, where he talks about it.

[EvilDragon]

Yah that's with native action.


I'm not sure why Cockos just doesn't take Breeder's code in natively.

[lou latch]

Originally Posted by Triode

v5.65rc5 - December 9 2017
+ Fades: improve behavior of crossfade shape actions [t=200422]

Does it have anything to do with this odd behaviour: forum.cockos.com/showthread.php?t=186661

Fade shape changing to default, when healing split audio left hand of it.

gif:
https://forum.cockos.com/attachment....0&d=1484864317

It didn't show up recently, but i thought it might be related and worth posting now (and it's pretty annoying).

Sorry if inappropriate!

[EvilDragon]

No, it has to do with this thread: https://forum.cockos.com/showthread.php?t=200422

[EvilDragon]

Devs, seeing that we got some more mouse modifier love in this pre cycle, it would be really nice if we had some additional mouse modifiers for copying regions WITHOUT content, for example. We already have "move region but not contents", but it would be also great to "copy region but not contents"!

[juliansader]

Originally Posted by Triode

v5.65rc5 - December 9 2017
# API: always return current tempo from GetTempoTimeSigMarker, but only return time signature if the marker sets a new time signature [p=1922791

Get and Set are now symmetric, which is a good improvement.

* In the tempo envelope chunk, have tempo points gained a new flag? It seems like 2 is a new flag that indicates the point sets a timesig but not tempo.

* In Get/SetTempoTimeSigMarker, is there any difference between 0 and -1 for bpm, timesig_num and timesig_denom?

* In the new pre-release, GetTempoTimeSigMarker returns timesig_num and timesig_denom = -1 if the marker only changes the tempo, not the timesig. Prior to v5.65, it returned 0. Some existing extensions and scripts may depend on this value. In the case of Breeder's freehand tool, everything seems to work fine now -- but it is just a lucky accident, since even his code checks for 0:

GetTempoTimeSigMarker(NULL, id, &position, NULL, NULL, NULL, &num, &den, NULL);
        InsertStretchMarkerInAllItems(position, true, GRID_DIV_DELTA / 2);

        if (den != 0)
        {
          double positionQN = TimeMap_timeToQN_abs(NULL, position);
          if (SetTempoTimeSigMarker(NULL, id, position, -1, -1, newVal, num, den, g_envMouseEnvelope->GetDefaultShape() == LINEAR))
          {
              if (SetTempoTimeSigMarker(NULL, id, TimeMap_QNToTime_abs(NULL, positionQN), -1, -1, newVal, num, den, g_envMouseEnvelope->GetDefaultShape() == LINEAR))
              pointsEdited = true;
          }
        }
        else
        {
          int measure; double beats = TimeMap2_timeToBeats(NULL, gridDiv, &measure, NULL, NULL, NULL);
          if (SetTempoTimeSigMarker(NULL, id, -1, measure, beats, newVal, 0, 0, g_envMouseEnvelope->GetDefaultShape() == LINEAR))
            pointsEdited = true;
        }

[musicbynumbers]

Originally Posted by EvilDragon

Devs, seeing that we got some more mouse modifier love in this pre cycle, it would be really nice if we had some additional mouse modifiers for copying regions WITHOUT content, for example. We already have "move region but not contents", but it would be also great to "copy region but not contents"!

That would be great!

[Mercado_Negro]

Originally Posted by EvilDragon

Hm, that didn't change in this prerelease cycle.

Hmm it actually changed in RC1 so yes, it does pertain to this prerelease cycle

Pre18:



RC1:

[juliansader]

Interesting example of bug in Region copying: Calculation of edge point value fails, but if the user makes any small change in the tempo envelope before copying, the problem is fixed:



This occurred directly after copying the Region to 15 and 16.

The RPP, based on FnA's report, is attached.


EDIT: To avoid the problem, the small change must be made *to the left* of the region. If the change is made to the right of the region, the problem will still occur.

[EvilDragon]

Originally Posted by Mercado_Negro

Hmm it actually changed in RC1 so yes, it does pertain to this prerelease cycle

Pre18:



RC1:

Hm, not over here in my theme it didn't.

[vitalker]

Originally Posted by Mercado_Negro

Hmm it actually changed in RC1 so yes, it does pertain to this prerelease cycle

Confirmed here on some(all I've tested) themes.

[EvilDragon]

I'm not sure even which theme color decides the color for selected/unselected AI text... nothing pinks up in theme element finder...


Devs?

[Soli Deo Gloria]

Originally Posted by EvilDragon

I'm not sure why Cockos just doesn't take Breeder's code in natively.

Schwa showed some reticences, a couple of threads ago, to make the native actions adapt to any grid size. This was related to his mention about potential inefficiency in processing with dense tempo maps. Anyway, I´ve been creating dense tempo maps for quite some time with Breeder´s actions, and although I have a setup that might be considered still respectable in 2017 (I7 3770K, 3.50 Ghz, SSD, 32Gbs of RAM), I haven´t seen any unusual spike or risky situation regarding CPU management in big projects like that (I even emailed them some example to emphasize my assertion). As Breeder´s code seamlessly solves it, I won´t insist too much on the native action, really. Needless to say, though, I fully support what you say, and Breeder´s code would be a good thing to include in native´s repertoire of actions.

Originally Posted by juliansader

In the case of Breeder's freehand tool, everything seems to work fine now -- but it is just a lucky accident, since even his code checks for 0:

Fingers crossed!! I expect they won´t break again for any reason or show at any moment some hidden incompatibility with that aspect of the new API that you highlight ...

[heda]

REAPER 5.65rc5, x64

I can't make a region to be on the second lane. I can fix it by having only two lanes. But it should fit like the others.

[_Stevie_]

It would be sooo awesome, if we had a better differentation between Beats and Subdivisions. Just an example mockup.

How it looks now:



My example mockup:

[juliansader]

Originally Posted by Soli Deo Gloria

Schwa showed some reticences, a couple of threads ago, to make the native actions adapt to any grid size. This was related to his mention about potential inefficiency in processing with dense tempo maps.

An interesting difference is that the new native function can insert linear tempo changes, whereas Breeder's only works with square shaped points.