v5.11pre4 - November 22 2015

[mccrabney]

+ MIDI editor: add actions to set grid type (straight, dotted, triplet, swing)

awesome, guys!! could we please have CC action control over swing, as well? that would get us even closer to hardware-style sequencers.

great work.

[Justin]

Originally Posted by EvilDragon

16384 values is still much less than what you can have with a 32-bit floating point value scaled from 0.0 to 1.0, though.

True, though whether it is meaningfully less so is less clear.

[nicholas]

Originally Posted by schwa

It's the existing render option "embed project tempo". Previously this option would have no effect if there were any tempo changes in the project, even if the rendered portion of the project was at a constant tempo. Now, if the option is enabled, tempo information will be embedded in the rendered item, as long as the project tempo remains constant throughout that particular section of the project.

Thanks

[RobU]

Originally Posted by Matt Riley

It would be great to have an option to view/edit CCs as envelopes instead of bars.

This ^^^

+1000

[ovnis]

It would be great to have an option to view/edit CCs as envelopes instead of bars.

Of course ! +100

[Mercado_Negro]

I think there are many things missing in current envelope/automation behavior to even think in automation items and whatnot.

[EDIT] In fact, before those missing things there should be area selection because many aspects of automation would depend on it.

[Lawrence]

I agree with Mercado Negro.

Seems like some "subjectively more basic" things should maybe be addressed before leaping directly onto the flashier shiny stuff like automation clips. Like maybe just moving automation lanes around.

[Justin]

Originally Posted by Mercado_Negro

I think there are many things missing in current envelope/automation behavior to even think in automation items and whatnot.

[EDIT] In fact, before those missing things there should be area selection because many aspects of automation would depend on it.

I agree, the point of the functionality added was just to enable general utility (and it only took a day to implement)

[mehmethan]

Hi Developers,
while your on reaproxy, I'm asking for a feature for reaproxy projects if it's possible. (I hope this is the right place to do it)

- When you make some changes on reaproxy project, New render should be added to the master project as a new take not as a new item and a new version of reaproxy project should be saved.
So each take of the rendered item will match with a different version of reaproxy project

This way we can go back and forth between renders and version projects to compare.

Thanks

[Mercado_Negro]

Originally Posted by Lawrence

I agree with Mercado Negro.

Seems like some "subjectively more basic" things should maybe be addressed before leaping directly onto the flashier shiny stuff like automation clips. Like maybe just moving automation lanes around.

Originally Posted by Justin

I agree, the point of the functionality added was just to enable general utility (and it only took a day to implement)

That's exactly how I see it. This feature took you a day to implement while jumping into all the automation stuff must be much more complex with lots of internal Q&A's and whatnot.

I'm sure it will be a great set of pres when that happens. Until then, patience

[Dimson]

Originally Posted by Matt Riley

It would be great to have an option to view/edit CCs as envelopes instead of bars.

+1000

[Lawrence]

Originally Posted by Mercado_Negro

That's exactly how I see it.

Whoa. Am I being irrationally optimistic or did Justin just "agree" with the need for area selection?

[drew]

Originally Posted by nicholas

+ Recording: enable auto-new file switching for background recording projects

Originally Posted by timothys_monster

Can someone please elaborate what this means?

I guess it's about the "start new files every... [x] MB" functionality in Prefs>Recording settings.

(That switches to new files and is auto, so it sounds right.)

By the way, I understand that function creates noticeable glitches in playback with the default fade settings. Presumably it shouldn't be doing any xfades at all when the recording itself is meant to be joining seamlessly!

[casrya]

MIDI link is a nice one thanks! Will get rid of some MIDItoReaControlPath and piz midiconverter3 usage

[casrya]

Originally Posted by Justin

True, though whether it is meaningfully less so is less clear.

Hi Justin, Just wondering if MIDI link is sample accurate on VST3/JSFX that supports it or is it still sent at block level?

[timbralzoom]

Originally Posted by Matt Riley

It would be great to have an option to view/edit CCs as envelopes instead of bars.

definitely +1

[ceanganb]

And +1

[Justin]

Originally Posted by casrya

Hi Justin, Just wondering if MIDI link is sample accurate on VST3/JSFX that supports it or is it still sent at block level?

It is still sent at the block level, hopefully those VST3s can take MIDI events natively? We'll look at adding support for sample accurate via MIDI eventually, but I can't say when that will happen (as it is quite a bit more complex!).

[Justin]

Originally Posted by drew

By the way, I understand that function creates noticeable glitches in playback with the default fade settings. Presumably it shouldn't be doing any xfades at all when the recording itself is meant to be joining seamlessly!

Oops, that is true, I'll look at having that fixed (the underlying audio is gapless, but the resulting project not, ugh)!

[BlackBart]

Originally Posted by mehmethan

Hi Developers,
while your on reaproxy, I'm asking for a feature for reaproxy projects if it's possible. (I hope this is the right place to do it)

- When you make some changes on reaproxy project, New render should be added to the master project as a new take not as a new item and a new version of reaproxy project should be saved.
So each take of the rendered item will match with a different version of reaproxy project

This way we can go back and forth between renders and version projects to compare.

Thanks

+1...I've been requesting a similar thing...a way to update the parent project with the new (Save As) versions. I like your "new take for the new version" concept.

[PitchSlap]

Originally Posted by Travesty

Me too, would be great for those who sequence drums in audio on the arrange page

That's my main reason for needing it too. After watching a dozen or so "Producer Masterclass" tutorial videos, it's pretty obvious this is a VERY common way of working and I think this is long overdue in Reaper, especially as the functionality has already been coded for the MIDI editor and just needs to be integrated in the main timeline...

[ankely]

Originally Posted by PitchSlap

Any chance of finally getting the main grid to be as functional as the MIDI editor? Been hoping for swing for ages...

Thanks.

This would be very handy…

[casrya]

Originally Posted by Justin

It is still sent at the block level, hopefully those VST3s can take MIDI events natively? We'll look at adding support for sample accurate via MIDI eventually, but I can't say when that will happen (as it is quite a bit more complex!).

Excellent thanks! On a related note while coding some sample accurate JSFX recently I noted that while the automation lanes trigger slider_next_chg() calls, parameter linking (even coming from sliderupdate()/slider_automate() in @sample) do not.

So if/when you tackle the MIDI linking it would be great if you could take a look at this too!

That said, I do accept that really it is up to the target VST to do proper parameter smoothing but I am sure I am not the only accuracy obsessed reaper user out there

Cheers,

casrya

[musicbynumbers]

Justin mentioned that you can use the item right click option "open copy in external editor" whilst in the master project to duplicate the underlying Pip as a new take. Even if you have this set to open an external real editor (like wavelab or RX) it actually just creates a copy of the reaproxy and appends the name with "001", "002" etc. That works quite well.

Most of us certainly wouldn't want every save adding both another 32bit wav file and a project file. Especially if you have used things like Kontakt Orchestra patches which can bloat a project file upto 50 to 100mb easily

It also stops it from working as expected from things like mastering projects whereby you want to be working on the originals anyway. As an option it's fine but not as default behaviour.

Or even better. As a tick box option in the save as dialogue it would be great but since proxies are just normally projects. I'm not sure if reaper would be able to add that option. Hopefully!

Originally Posted by mehmethan

Hi Developers,
while your on reaproxy, I'm asking for a feature for reaproxy projects if it's possible. (I hope this is the right place to do it)

- When you make some changes on reaproxy project, New render should be added to the master project as a new take not as a new item and a new version of reaproxy project should be saved.
So each take of the rendered item will match with a different version of reaproxy project

This way we can go back and forth between renders and version projects to compare.

Thanks

[TheWhistler]

Originally Posted by cfillion

It's time to get rid of my "divide/multiply grid size" custom actions workarounds!

This is a huge step forward in midi editing. It always made me feel strange, to not have this in musical terms.

I combined this with quantize to grid, now this feels like any other (normal) midi editor to me.

THIS IS THE HIGHLIGHT OF MY DAY !!!

Thanks devs.

[EvilDragon]

One thing that is missing though is for the MIDI editor grid actions to report their state properly... so that toggle buttons can show the currently selected state!

[semiquaver]

hmmm...

an action to "create new proxy version" which saved deltas - like real version control - would be incredible...

in any case, accessing multiple versions of a proxy could be used for multiple takes of automation, or more generally for playlist-like functionality. - the visual of multiple takes might not be wanted though....

[semiquaver]

having to manually move the END marker after opening and working with a Proxy is an annoyance.

maybe render should default to end of project unless an END marker is placed ?

[musicbynumbers]

Originally Posted by semiquaver

having to manually move the END marker after opening and working with a Proxy is an annoyance.

maybe render should default to end of project unless an END marker is placed ?

It does normally. If there's no start or end markers then it normally does. Maybe that's a bug then as the normal behaviour is to go with what reaper normally sees as the project end.

[J Reverb]

+ Parameter modulation: allow controlling/modulating FX parameters with track MIDI events/monitoring

Thanks !
This would be perfect with a momentary min max fixed note velocity setting.

[EvilDragon]

Question for devs: how much work would it be to enable parameter linking via parameter modulation across tracks, not just on the current track?

This would make it much easier to link the controls of same plugins across different tracks...

[DarkStar]

^^^^
+1
http://forum.cockos.com/showthread.php?t=134423

[musicbynumbers]

Originally Posted by EvilDragon

Question for devs: how much work would it be to enable parameter linking via parameter modulation across tracks, not just on the current track?

This would make it much easier to link the controls of same plugins across different tracks...

Although it would be great if there was a dropdown menu system to do this, I did try it across tracks the other day and it did work via the sends system. I even put it on bus 2 as to not get in the way of any normal midi stuff.

I had one midi control (via reacontrolmidi) controlling multiple link parameters on multiple tracks. Even placed the reacontrolmidi on an item and drew in the automation on the item and it worked so there is some cool things you can do already.

Would be great to have it "menued" though and behind the scenes.

[EvilDragon]

Yes, my question is simply to have it natively without needing to work around with by having yet another plugin loaded to the track... Sort of like a very logical extension to the already great parameter modulation system.

[Justin]

Originally Posted by EvilDragon

Question for devs: how much work would it be to enable parameter linking via parameter modulation across tracks, not just on the current track?

This would make it much easier to link the controls of same plugins across different tracks...

It would be very difficult because tracks can be processed asynchronously and in parallel from one-another.

[EvilDragon]

Shame... It would've been a killer feature.

[timothys_monster]

Originally Posted by EvilDragon

Shame... It would've been a killer feature.

Is that of any help for you?

http://forum.cockos.com/showpost.php...3&postcount=31

By the way, love the responsiveness of the devs during the last few pres.

[EvilDragon]

Originally Posted by timothys_monster

By the way, love the responsiveness of the devs during the last few pres.

Yep, that IS nice.


I'll check the script out later. The benefit of parameter modulation would be scaling and offseting the linked controls, though...

[Mercado_Negro]

Originally Posted by timothys_monster

Is that of any help for you?

http://forum.cockos.com/showpost.php...3&postcount=31

By the way, love the responsiveness of the devs during the last few pres.

Whoa! That's amazing, thanks for sharing that. I just tried it and I couldn't believe my eyes. Linking plug-ins parameters across tracks is something I've needed so many times.

[Reno.thestraws]

+ MIDI editor: add actions to set grid type (straight, dotted, triplet, swing)

I'm waiting for this since 1974