v7.0pre10 - August 18 2023

[KingHyenX]

would like to see a button to collabse the automation lanes to the tracks,
similar like the folders. i know you can set hotkeys to hide the automation lane.
But it would nice to have a little button to indicate if there are some aktive
automations. or small lines like the folders would be nice.
Actualy, my workaround is a hotkey to hide all automation und bring it back,
when i do some adjustments.

[deeb]

Originally Posted by KingHyenX

would like to see a button to collabse the automation lanes to the tracks,
similar like the folders.

me too.

[deeb]

I would like to ask to consider settings for minimum height of tracks and envelopes in Zoom Options So that the user can set the minimum height that works best for him. In my case i would't mind to loose a little of beauty for the functional benefit.

Example today i tried an old version of my old DAW and i was impressed by the number of tracks i could put in the same space comparing with reaper.

The difference is huge!

[harmonicaman]

Originally Posted by deeb

I would like to ask to consider settings for minimum height of tracks and envelopes in Zoom Options

You can do that, outside options.(it will most probably get ugly, depends on the theme) In the rtconfig.txt, find this :
tcp_heights
the complete line for default v6 theme is:
tcp_heights 4 25 50 64 ; supercollapsed, collapsed, small(norecarm), recarm size
change the second value for default minimum height.


If you don't know how to find the txt, Go to colortheme folder. If you use the default theme (not a unpacked theme) open the file Default_6.0.ReaperThemeZip with winzip/other favorite, the rtconfig.txt is in default_6.0_unpacked.


I'm for multiple Minimum tracks/envelope heights, defined by user.Thing is, for most, WALTER theming is like gibberish symbols on the stargate. It's difficult to explain all the wonders you'll find behind. And Teal'c.

Again (only because zooming is the topic, I won't push more) :
https://forum.cockos.com/showthread.php?t=281769

[ovnis]

Originally Posted by harmonicaman

You can do that, outside options.(it will most probably get ugly, depends on the theme) In the rtconfig.txt, find this :
tcp_heights
the complete line for default v6 theme is:
tcp_heights 4 25 50 64 ; supercollapsed, collapsed, small(norecarm), recarm size
change the second value for default minimum height.


If you don't know how to find the txt, Go to colortheme folder. If you use the default theme (not a unpacked theme) open the file Default_6.0.ReaperThemeZip with winzip/other favorite, the rtconfig.txt is in default_6.0_unpacked.


I'm for multiple Minimum tracks/envelope heights, defined by user.Thing is, for most, WALTER theming is like gibberish symbols on the stargate. It's difficult to explain all the wonders you'll find behind. And Teal'c.

Again (only because zooming is the topic, I won't push more) :
https://forum.cockos.com/showthread.php?t=281769

It's not possible anymore if we are several lanes inside a media item lanes track (for the small size) .
I think that is extremely regrettable. Navigation becomes much more difficult.

[schwa]

Originally Posted by ferropop

Still coming across stuff like this a lot unfortunately :

Is it possible to save a small project in a state where deleting a specific comp area demonstrates this problem? Having trouble reproducing it.

[musicbynumbers]

+ Tracks: vertical zoom accounts for the number of track lanes (experimental)

Seems to work well so far thanks!

Small bug I found was that when using "View: Adjust vertical zoom (MIDI CC/OSC only)" and I had say 20 take lanes (and with zoom set to 100%).

If the 1st/top lane was visible and then I tried to zoom in on say lane 17. It would actually zoom into these top lanes rather than lane 17.

but, If the top lane saw vertically scrolled so it was hidden past the top of the screen and then tried to zoom to lane 17. It would work fine and zoom to lane 17.

[FeedTheCat]

Alt-clicking on an area without an unsynced comp area deletes all comp areas:



Also I think crossfading items into synced areas used to work?

[alphoc]

Originally Posted by deeb

me too.

This is exactly what a DAW should be. but there does not appear to be such a plan.

[deeb]

Schwa: as i told yesterday comping interface feels IMO unfamiliar , since everything we are used to like marquee, RE modifiers stop working.

by turning on: "Allow editing in comping lanes" it feels a step forward to more familiar, but still there is things which IMO make it difficult or unfriendly to use.

Like we have same mouse cursor for moving AI, Items or envelope points i think comp should follow the same rule and not change the operation cursor on different contexts.

First:

I expect if i mouse over a "comp area" and if i drag i will move it and so i don't need a different cursor for this , otherwise confuses users and same principle should be applied for every operation that implies moving.



Second:

"Edit fixed lane comp area" should also have same cursor has for items or AIs: "Move edge cursor" because it is the same operation , i expect i will move edge as for AI, items ..

Third:
"change fixed lane comp area" should no be available replacing the mouse cursor which we are used too and use example Alt + drag for that. This makes the experience more clean.

There might be more, but the logic i think would benefit user being like this, at least when option "Allow editing in comping lanes" is ON.

edit:
Fourth:
This brings me to another thought. Is Comping ON/OFF really necessary? is comping ON and OFF a temporary set of modifiers? because if so i am not sure if is necessary, because i would personally prefer that i could always be able to do comping operations if i wanted too, and not limited to a mode which maybe is not really necessary.


PS: nitpick:

[musicbynumbers]

Originally Posted by alphoc

This is exactly what a DAW should be. but there does not appear to be such a plan.

It would be nice to have this but if we don't get it you can do what I did for now and it works the same.

I went to Mouse modifiers, Track control panel, double click and then set "Alt" up to run the command "Envelope: Toggle show all active envelopes for tracks".

This allows me to double click a track to toggle showing all envelopes for that track, works great.

Doesn't have to be the alt modifier you use but you get the point.

[ferropop]

Originally Posted by schwa

Is it possible to save a small project in a state where deleting a specific comp area demonstrates this problem? Having trouble reproducing it.

You bet! I can't post publicly, can I email?

And thank you.

ps, these are the steps I took to break it:

[PSM-Studios]

Does anybody know why the Meter scaling is only visible in the Master mcp.

[AZpercussion]

Hi devs! Sorry to be annoying with this moment.
Flushing fx on bypass is gone from all changelogs, but it works in dev versions. It seems abandoned. Is there a chance to release?

I'm writing it again because there is no answer and I assume you just missed my posts.

[smandrap]

Originally Posted by PSM-Studios

Does anybody know why the Meter scaling is only visible in the Master mcp.

It's a Theme Adjuster option. The latest pre-version is a bit broken, but you can activate the mcp metering by enabling "verbose MCP" from the script

[schwa]

Originally Posted by AZpercussion

Hi devs! Sorry to be annoying with this moment.
Flushing fx on bypass is gone from all changelogs, but it works in dev versions. It seems abandoned. Is there a chance to release?

This feature is working fine as far as we can tell, but it's a significant enough change in behavior that we are planning to include it in 7.0 rather than a 6.x release.

[AZpercussion]

Ah, thanks for explanation!

[daxliniere]

The workflow for FX Containers is still pretty slow.

Containers are listed as a plugin, rather than as a 'function' or 'utility'. That is to say you can't select one or more plugins that are already inserted and then add them to a Container.

There are many times when you will insert a plugin, make some changes, then decide you need to add another 'complementary' plugin (like gain adjust, MS en-/de-code, etc). This requires you to go back to the FX browser, insert a Container, then populate that container.

In this video example, I hope to illustrate how much simpler the process could be. Select plugins > right-click > Add to FX Container.



Further, it's inconsistent that you can save a preset inside a Container, but that preset isn't displayed in the list of FX, but FX Chains are displayed.

[daxliniere]

You also can't drag'n'drop into an FX Container:


(though I know you can DnD into the FX Container's FX window.)

[Vonnegut]

I was interested in testing it, but the link takes me to 6.82

[Suzuki]

Originally Posted by Vonnegut

I was interested in testing it, but the link takes me to 6.82

Open old/ folder.
https://www.landoleet.org/old/

[daxliniere]

Originally Posted by Vonnegut

I was interested in testing it, but the link takes me to 6.82

I had a similar thing. It's because v6.82rc2 was released after v7.0pre10.
Are you using the ReaUpdate tool? If so, you can click the clock icon and then select v7.0pre10.

However, I'm sure the devs would appreciate another set of eyes on what is likely to be the last v6.x release.

[daxliniere]

Media Item Properties isn't passing keys (CTRL+Z/+Y (undo/redo)) through to the main window.
It looks like it's because the Take Name text box now has focus on open.

(Also, when did 'Auto apply after 2 secs of inactivity' get added?? This is great! I've thought about this many times! <3 )

[MonkeyBars]

Originally Posted by daxliniere

(Also, when did 'Auto apply after 2 secs of inactivity' get added?? This is great! I've thought about this many times! <3 )

Hey cool, never saw that!

Not a fan of the hidden right-click menu features however. Imo we should have an Options button in Item/take Properties as was done in the Actions Window.

[daxliniere]

Originally Posted by MonkeyBars

Not a fan of the hidden right-click menu features however.

They seem to only be used in places where there is no menubar to hold settings.

(The Routing (sends) dialogbox has a right-click menu, too.)

[MonkeyBars]

Originally Posted by daxliniere

They seem to only be used in places where there is no menubar to hold settings.

I don't think that is relevant for macOS...

[daxliniere]

Wot's a Mac?

[dom64]

Originally Posted by daxliniere

Wot's a Mac?

Helps you out when it's raining and you want to jump about in the puddles!

[vseanv]

Reaper bugs out and crashes at around 60 fixed item lanes. (Happened at 59 and 62 layers for me in two different sessions). When you reload the session after crashing, all lanes of the track are showing and you can not toggle the single lane view anymore (it’s grey’d out) and if you try to record or insert a new lane Reaper crashes again.

[mschnell]

Originally Posted by daxliniere

This requires you to go back to the FX browser, insert a Container, then populate that container.

You can save the content as an FX chain and populate an empty container with that FX chain.

Of course it would be more intuitive if the filled container could be saved with a name. That would make the container feature a "Meta-Plugin" paradigm.

[inthevoid]

I've been using the loopback MIDI & audio features in these pre-releases quite heavily (sending & receiving ~256ch of audio and on 16 virtual MIDI loopbacks between project tabs) and have occasionally run into an issue when playing back in the subproject where the UI completely freezes (beach ball cursor on Mac).

For reference, I'm also keeping project tabs synced / running in background. I'm hosting all the VSTs in a main project and playing back MIDI from subproject.

When the freeze happens, the subproject keeps playing back fine, but since the UI & key commands are frozen the only solution is to kill the process and saving is also not possible. Waiting it out doesn't work. I haven't seen this happen at all when I'm not using loopback audio & MIDI channels and it seems to only happen at high track counts (e.g. when I'm using my main VST template).

I can't replicate this consistently, apart from that it has only happened when playing back from the subproject, but thought it might be worth mentioning. If I find any consistent behaviour I will upload a test project with the issue.

[mschnell]

Originally Posted by inthevoid

virtual MIDI loopbacks between project tabs

How do you do this ?

[smandrap]

Originally Posted by mschnell

How do you do this ?

[daxliniere]

That's a cool feature. I guess this loopback is inside REAPER only, though, not a system driver. (Not that there aren't plenty of those already.)

[Hipox]

Regarding the MIDI Loopback: in the past I already pointed out this bug, let's raise it up again.

When some hardware midi device is routed into a track, this track has some FX for velocity modulation and loops back as an midi input, the tracks that receives this (from midi loopback) input does not reflect the velocity changes made on that track in retroactive recordings. The signal seems to be the one directly captured from midi hw device.

[inthevoid]

Originally Posted by daxliniere

That's a cool feature. I guess this loopback is inside REAPER only, though, not a system driver. (Not that there aren't plenty of those already.)

Indeed, this is internal to REAPER only.

[mschnell]

Originally Posted by smandrap

Don't have it in V7.0pre
Is this Mac-only ?
(I did a "Route Midi via GMEM" JSFX for that purpose...)

[inthevoid]

Originally Posted by mschnell

Don't have it in V7.0pre
Is this Mac-only ?
(I did a "Route Midi via GMEM" JSFX for that purpose...)

Definitely not Mac-only - are you clicking the 'Add virtual MIDI...' button under Preferences > MIDI Devices?

[daxliniere]

Originally Posted by mschnell

Don't have it in V7.0pre
Is this Mac-only ?

I have it on PC

[MonkeyBars]

Is the 64 (named?) lane limit hard-coded? Like some other users here, I regularly exceed 100 takes in a recording session. This would make that type of loop recording infeasible or at least very inconvenient. What is the reason for this limit?