3.21pre3

[rob.manderson]

v3.21pre3 - January 19 2010
+ ReaSamplOmatic: properly loop very short samples
+ ReaComp/ReaXComp: better RMS calculation on playback start
+ Master RMS no longer has inaccurate peak on start of playback
+ Tweaks to mixer/track list track reordering
+ New folder now shows up on plug-in rescan if new plugins were added
+ Actions: show/hide all envelopes
+ Toolbar: key shortcuts are back in tooltips

v3.21pre2 - January 17 2010
+ Custom actions: fixed possible corrupted action list when deleting custom actions
+ Mixer: if autoarrange is on, arrange view ordering follows track moves in mixer
+ Mixer: click on empty space to deselect all tracks
+ Screensets: track views can save/restore custom mixer track order

v3.21pre1 - January 14 2010
+ Automation: fixes for automating-when-closed support
+ FX browser: fully recursive finding of FX chains, JS FX
+ JS: slider_automate command, to write slider automation from within JS code
+ Mixer: freely arrangeable tracks, autoarrange can be enabled/disabled
+ ReaScript: GetSetChunkState chunk length limit increased to 1MB
+ ReaScript: added GetUserFileNameForRead
+ ReaVocode/Voice/Verb[ate]/SamplOmatic/Insert/Gate/Fir: smooth changes in various gain/pan parameters
+ VST/AU: ignore automation messages when loading/restoring plugins (avoid hang)
+ VST scanning: faster scanning, better subdirectory search order

[jonespnice]

Originally Posted by rob.manderson

v3.21pre3 -
+ Tweaks to mixer/track list track reordering

Great addition, thanks.

[jas]

Originally Posted by rob.manderson

v3.21pre3 - January 19 2010
+ ReaComp/ReaXComp: better RMS calculation on playback start

This is better now with instances of ReaComp on OSX.

[nofish]

Originally Posted by rob.manderson

v3.21pre3 - January 19 2010

+ New folder now shows up on plug-in rescan if new plugins were added

I often add plugins this way and was missing the New folder.
Nice addition, thanks.

[wallace]

Originally Posted by rob.manderson

v3.21pre3 - January 19 2010
+ ReaSamplOmatic: properly loop very short samples

Cool!
Thanks.

[Dstruct]

Originally Posted by rob.manderson

+ ReaSamplOmatic: properly loop very short samples

Better in 3.21pre3 but still not 100% the same sound as looped on audio track! (Under headphones) I still can hear some 'distortion' when looped in ReaSamplOmatic5000 ...

[Fabian]

Originally Posted by rob.manderson

+ Master RMS no longer has inaccurate peak on start of playback

Whoaa... that was quick!

[EricM]

Originally Posted by rob.manderson

+ Actions: show/hide all envelopes

Awesome, now just add another action that toggles hide/show and
I can replace the "toggle show all active envelopes".

[musicbynumbers]

Originally Posted by EricM

Awesome, now just add another action that toggles hide/show and
I can replace the "toggle show all active envelopes".

Toggle actions are great maybe we need to make a list of actions that could do with a toggle function to half our key commands?

[DarkStar]

Originally Posted by EricM

Awesome, now just add another action that toggles hide/show and I can replace the "toggle show all active envelopes".

Originally Posted by musicbynumbers

Toggle actions are great maybe we need to make a list of actions that could do with a toggle function to half our key commands?

IMO, all 2-state functons should have 3 Actions:
-- switch to state 1,
-- switch to state 2,
-- toggle state.

[Jeffos]

many good things, here! about JS directories: it would really great to have user configurable paths.. known FR I know.. just for the 10 characters limit:

Originally Posted by DarkStar

IMO, all 2-state functons should have 3 Actions:
-- switch to state 1,
-- switch to state 2,
-- toggle state.

+3

[gofer]

It would be so cool to have some functional actions at hand that allow to build toggles, cycles and conditional stuff with macros.

For example I would love to build a toolbar button that cycles the selected track(s) automation through trim/read-read-touch (and only those 3 modes). I'd never expect such a personal preference of functions to be reflected in a built-in action, so it would be a godsend to me if I could knit those myself by some easy means. I guess it can be done with scripts, but that shows to be over my head .

[Fabian]

Originally Posted by gofer

It would be so cool to have some functional actions at hand that allow to build toggles, cycles and conditional stuff with macros.

Maybe not the proper thread but... well said. For/while/until-loops and if/then/else would be great.

EDIT: Ah! Yes, of course, ReaScript already has all of that. 'nuff said (for me)...

[schwa]

Originally Posted by gofer

For example I would love to build a toolbar button that cycles the selected track(s) automation through trim/read-read-touch (and only those 3 modes). I'd never expect such a personal preference of functions to be reflected in a built-in action, so it would be a godsend to me if I could knit those myself by some easy means. I guess it can be done with scripts, but that shows to be over my head .

ReaScript is really the way to go for this. You can see from the attached script that it would not be simple to add control-flow functionality to custom actions, and since the functionality is already there in ReaScript, there's not much reason to.

envmode_cycle.py:

MIXED_MODE=-1
TRIMREAD_MODE=0
READ_MODE=1
TOUCH_MODE=2

envmode = MIXED_MODE

n = RPR_CountSelectedTracks(0)
for i in range(0,n):
  track = RPR_GetSelectedTrack(0,i)
  tmode = RPR_GetTrackAutomationMode(track)
  if envmode == MIXED_MODE:
    envmode = tmode
  elif envmode != tmode:
    envmode = MIXED_MODE
    break

if envmode == TRIMREAD_MODE:
  envmode = READ_MODE
elif envmode == READ_MODE:
  envmode = TOUCH_MODE
else:
  envmode = TRIMREAD_MODE

for i in range(0,n):
  track = RPR_GetSelectedTrack(0,i)
  RPR_SetTrackAutomationMode(track, envmode)

[DarkStar]

Originally Posted by DarkStar

IMO, all 2-state functions should have 3 Actions:
-- switch to state 1,
-- switch to state 2,
-- toggle state.

And all N-state functions (up to a reasonable limit) should have N+2 Actions:
-- switch to state 1,
-- switch to state 2,
-- switch to state 3,
-- switch to state N,
-- switch to next state (and from state N to state 1)
-- switch to previous state (and from state 1 to state N)

[Coerce]

Originally Posted by schwa

ReaScript is really the way to go for this. You can see from the attached script that it would not be simple to add control-flow functionality to custom actions, and since the functionality is already there in ReaScript, there's not much reason to.

No offense schwa but your average user looking for a toggle function is going to be put off by the answer "go make a script". Most people want to use software not have to mod it to their own needs.

Any chance someone could explain what was done to the mixer tracks?

+ Tweaks to mixer/track list track reordering

The pre seems pretty stable here as I don't use folders. I I make a folder I get no warning when moving tracks in mixer and I can see it messing up the folder structure.

[schwa]

Originally Posted by Coerce

No offense schwa but your average user looking for a toggle function is going to be put off by the answer "go make a script". Most people want to use software not have to mod it to their own needs.

The specific request was a toggle function that cycles through three of the five possible automation states. As gofer said, that won't ever be a built-in action. So, it needs to be designed by the user.

ReaScript can do this. Adding enough complexity to the custom action system to support something like this is not realistic -- the resulting custom action would be just as complex, and therefore just as off-putting (or just as appealing, depending on the user), as the script example.

Most 2-state actions do already have toggle actions associated with them (any that are missing, we can add). We can also add cycling actions for multi-state actions, if people make specific requests.

But the issue being addressed with the reascript example was custom cycling actions.

[Mercado_Negro]

Good but... can I haz dat toggle az a natif akshon? pweeese!

[Coerce]

Originally Posted by schwa

The specific request was a toggle function that cycles through three of the five possible automation states. As gofer said, that won't ever be a built-in action. So, it needs to be designed by the user.

ReaScript can do this. Adding enough complexity to the custom action system to support something like this is not realistic -- the resulting custom action would be just as complex, and therefore just as off-putting (or just as appealing, depending on the user), as the script example.

Most 2-state actions do already have toggle actions associated with them (any that are missing, we can add). We can also add cycling actions for multi-state actions, if people make specific requests.

But the issue being addressed with the reascript example was custom cycling actions.

Thanks for the eloquent reply. I'll have to start looking in to reascript for a few cycling actions like cycling the grid sizes etc.

Anyway back on topic, thanks

[Evan]

Originally Posted by Coerce

No offense schwa but your average user looking for a toggle function is going to be put off by the answer "go make a script". Most people want to use software not have to mod it to their own needs.

I completely agree. But I have another direction in mind. Allow as much depth as you want, for programmers and tweakers, but make it simple for the average user to reap the benefits.

If I can have the functionality, somebody else has elaborately created and given away for free, with a simple drag-n-drop or a file copy, then me -the average user- is happy!

The SWS extensions is one example. The save/load-able custom menus and toolbars is another (though not 100% portable at the moment, you need to copy bitmaps separately etc..).

So, on this topic... "go make a script" is fine as long as one person makes a script, and others can share in a couple of easy steps.

[EvilDragon]

Originally Posted by schwa

The specific request was a toggle function that cycles through three of the five possible automation states. As gofer said, that won't ever be a built-in action. So, it needs to be designed by the user.

ReaScript can do this. Adding enough complexity to the custom action system to support something like this is not realistic -- the resulting custom action would be just as complex, and therefore just as off-putting (or just as appealing, depending on the user), as the script example.

Most 2-state actions do already have toggle actions associated with them (any that are missing, we can add). We can also add cycling actions for multi-state actions, if people make specific requests.

But the issue being addressed with the reascript example was custom cycling actions.

schwa, what do you think about a FR I posted quite some time ago? Here's the link.

This is probably as easy as it could get. In this case, if a custom action was bound to a toolbar button, provided that the custom button has enough different images to show different states (for example, take a look at Ripple editing icon, which has 3 states!), this should all work easily. Of course, Reaper would need to remember the last active state.

On that topic: is there a way from ReaScript to tell Reaper which button state image to use, for these multi-state toggle buttons? If there's not (and something tells me there isn't a way), it should be.

Say, we have a button with 3 states. Make a requirement that the images should be called like this:

imagename_00.png
imagename_01.png
imagename_02.png
---
imagename_99.png

and Reaper would automatically recognize and use those, if we define the starting image in ReaScript API. This way we could have up to 100-state buttons, as unrealistic as it sounds, but possible to do, and makes a lot of sense anyways.


I'd really like to have some dev feedback on this. Thanks!

[gofer]

*blushes*
No, Schwa did you...? *copies script and shoves it onto a toolbar* ...indeed, you did. Wow thank you! I'm sure this is something that can only happen with Cockos.

Thanks so much, Schwa Really, I just used that as an example. Never did I assume or even expect you or anyone to actually take their time and code it for me. That makes two buttons less on my envelope toolbar



I understand the benefit would most probably not be worth the effort. My hope was it could be done with a few strategic clever meta actions, but get a grip on how it's not that easy.


Maybe I just hoped to get around the syntax stuff that is involved with coding and is the actual hurdle for me. I can deal with the logical part, planning which steps I'd have to go through in which order to achieve my aim, but am struggling with syntax problems even with simple JS code I tried to write. But I can see how this is getting too far out of what Reaper needs to deliver inbuilt.


I need a goferspeak -> Python (or Pearl) translator

[Mercado_Negro]

Originally Posted by gofer

I need a goferspeak -> Python (or Pearl) translator

Me too

[jedstar2000]

Great update

While your playing around with the toolbar. I seem to be experiencing varying behavior between key stoke actions and right click toolbar actions.(my custom macros behave one way with keystrokes and another with armed toolbar actions very strange)

Also it would be great to be able to arm custom toolbar actions via a keystroke (great for changing tools)

[d. gauss]

Originally Posted by rob.manderson

+ Mixer: freely arrangeable tracks, autoarrange can be enabled/disabled

happy happy, joy joy! been waiting a looooong time for that one. cudos!