v7.0pre10 - August 18 2023

[deeb]

but moving while Collapsed does not unsync either, right?

i hope same happens while copying/duplicating collapsed/RE

how can i know if something is unsynced and what is unsynced?

[deeb]

I personally think comping is too complicated, maybe there is no other way around.

1) one thing i imediately dislike is As soon as i start Comping into a lane eventually i still want to move comp sources , double click to edit midi, or marquee and reaper requires me to turn comping off in order to do so. This is unexpected and limiting. Same cursor for moving or marquee select should be displayed while comping sources and if i move them comp lane should adapt this. Comping modifier

2) i am not sure if not better that when moving comp lane items, sources should move too, because if i want to make edits unsynced in another place then i copy/duplicate it to another place and delete the sources. It gives less benefits as is apparently. Comp can be perceived as a unified block/container . if you copy it somewhere you are doing something free of sources.

3) why reaper allows me to do this yellow squares, if i have no items there and i am not allowed (at least easily) to copy or move items into there?




(i might change my thought but this a virgin user experience , will continue)

[Vagelis]

I think the collapse button should never be hidden even at the smallest track height,
because it's useful to know if there are any lanes below, but also to let us expand it to see them all.



In this case the track height is not even that small when it's collapsed but still I can't expand to see all lanes except if I zoom vertically. But i think doing this each time is not ideal.

[Edgemeal]

Originally Posted by mpl

I commented 2 lines with TrackFX_SetNamedConfigParam reduced_name. Everything except these lines works ok.

I used jsfx kanaka MS decoders encoders (i guess its bundled).

FWIW those JSFX names you used in script don't load here (Win10_US English), can only guess you mean these,...
'JS:Mid/Side Encoder' -- "\Effects\utility\KanakaMSEncoder1"
'JS:Mid/Side Decoder' -- "\Effects\utility\KanakaMS5"

[ovnis]

Hi!


The area where we have to click to change the solo track is too much little. I have to try again an incredible number of times each time to select a new solo lane. very painful.

[FeedTheCat]

Originally Posted by Edgemeal

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

Hmm, liking this so far!

If it stays it would be great if at minimum height the lane header buttons stay visible. Afaict it's only off by a few pixels and I guess the header buttons could even be a bit smaller (now that they don't contain text).

[Vagelis]

Originally Posted by Edgemeal

v7.0pre10 - August 18 2023

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

So using this more with collapsing I think I've come to a point that I'd like it if the new and old behavior could be combined.
I like more how we add new lanes with the old behavior where the track height doesn't change so we don't have to scroll for a few lanes, but I like also that with the new behavior it sets the track height to the height of the collapsed lane.
Could there be an option for this? (adding lanes would not change the track height, but when collapse it would change to the height of the lane)
I think this would feel better without messing too much with scrolling or zooming.

[ovnis]

Why numbers are not inside the dot, like before? As intended or bug?



For me, it's a downgrate. Less space for others TCP elements and just ugly/odd.

[Vagelis]

I think the problem with the new behavior regarding the things I wrote above has to do with zooming, when it happens it's also scrolling the view.

It would be much more preferable if it didn't scroll the view to the bottom and we could see the top of the track. In case we want to see the lanes below after zooming, then we could scroll down separately. If this could be solved then this behavior could be better after testing again.

EDIT: Even though an option as mentioned previously would be welcome since the old behavior doesn't take too much space on screen when adding new lanes.

[deeb]

Originally Posted by ovnis

Why numbers are not inside the dot, like before? As intended or bug?



For me, it's a downgrate. Less space for others TCP elements and just ugly/odd.

i feel that too. Numbers are there but can be renamed , still they take too much space and we have no option to hide them:




Also this buttons take too much space in TCP: (all the extra space this button have is space not available where it matters most - project space ...)

[ovnis]

Why We can't reduce the width like before:





Before :


Now :


Before :


Now (less space for TCP elements):

[Vagelis]

Also I think in this case autoscroll should happen. (after collapsing return the view to the top of the track to see the collapsed lane)

[schwa]

Originally Posted by ovnis

The area where we have to click to change the solo track is too much little. I have to try again an incredible number of times each time to select a new solo lane. very painful.

Where are your buttons? All I can think of is that your theme does not have lane_solo_on/lane_solo_off images, plus you have defined the theme colors for "track fixed lane button" and "track fixed lane button when this lane plays" to be the same as the background color.

[FeedTheCat]

Apparently there's a difference between track height being set manually (by resizing) vs height being set automatically by zooming.

When set manually, the height doesn't shrink after collapsing. Maybe make it always shrink so that we can give this experimental option a fair shot?



Another thing to note in this gif is that the collapse button disappears, so after collapsing you can't press it again to un-collapse. I agree with Vagelis that it should stay visible at min height (maybe even over a single lane header button)

[schwa]

Originally Posted by ovnis

We can't resize (witdh) the fixed track panel now. Is it a bug?

You can resize the fixed lane control area, but the minimum size is larger, because the lane numbers are now always displayed next to the buttons. This is intentional.

[FeedTheCat]

Originally Posted by Daodan

And sorry my stupidity but how to move items with comp areas without using Razor when lanes are collapsed?

The only thing that I can think of to make this possible would be making comp areas selectable (which I'm definitely not opposed to). Then we could marquee select to copy them together and even switch takes together in certain selected comp areas only. The selection could work similarly to how solo marker selection used to work.

Guess that's out of scope though for the v7 release.

[ovnis]

Originally Posted by schwa

Where are your buttons? All I can think of is that your theme does not have lane_solo_on/lane_solo_off images

I have deleted it. With previous versions, it worked great:



Why did you remove the possibility to reduce the width of the window like before?

plus you have defined the theme colors for "track fixed lane button" and "track fixed lane button when this lane plays" to be the same as the background color.

It seems to does nothing:

[img]https://i.imgur.com/h5KXwcU.gif[/img]

[deeb]

Originally Posted by schwa

You can resize the fixed lane control area, but the minimum size is larger, because the lane numbers are now always displayed next to the buttons. This is intentional.

But would be better IMO if users could minimize fully. It’s their option. In a 1280x800 screen every bit of space matters and reaper makes things too big in TCP.. even the minimum size for tracks is ridiculously big.. I have noticed I could put maybe double of tracks visible in the same area in my old DAW.

[ovnis]

Originally Posted by schwa

You can resize the fixed lane control area, but the minimum size is larger, because the lane numbers are now always displayed next to the buttons. This is intentional.

It's sad because it's a wast of space for others TCP elements.

Why not leave the choice as before?

[schwa]

Originally Posted by ovnis

I have deleted it.

Do you maybe have lane_solo_on/lane_solo_off images still in the theme, but they are empty files or fully transparent or something? What happens if you switch to an old theme like the v5 one?

[ovnis]

Originally Posted by deeb

But would be better IMO if users could minimize fully. It’s their option. In a 1280x800 screen every bit of space matters and reaper makes things too big in TCP.

Some of my theme buttons disapears because fixed lanes area is too large, now.

It's a good idea to be able to reduce this area as much as possible and only use shortcuts/actions/mouse modifiers. Having the ability to reduce it until you can't see it anymore would be a good idea.

With the hatched part I know very well that it is a fixed track lane and with track colors I can see if it's a mute, solo or camp track.

[ovnis]

Originally Posted by schwa

Do you maybe have lane_solo_on/lane_solo_off images still in the theme, but they are empty files or fully transparent or something? What happens if you switch to an old theme like the v5 one?

It works with v5 but not with v9!

[deeb]

^^ [and the buttons. They could be almost 1/3 of the space. Yes that is what I am considering just name and vol.

[FeedTheCat]

Razor copying only works nicely when the copied area contains a synced/unsynced comp area.

[ovnis]

Originally Posted by schwa

Do you maybe have lane_solo_on/lane_solo_off images still in the theme, but they are empty files or fully transparent or something? What happens if you switch to an old theme like the v5 one?

I have lane_solo_on/lane_solo_off still in my theme. They are transparents.

[beingmf]

Originally Posted by Edgemeal

* Includes feature branch: export mouse modifiers as a script

Hot!

[schwa]

Originally Posted by ovnis

I have lane_solo_on/lane_solo_off still in my theme. They are transparents.

Well... what are you trying to accomplish? You have effectively made those buttons disappear and now you are having trouble knowing where they are so you can click on them.

[deeb]

Schwa: relatively to comping, as far as I remember unless now with re tool there is no place in reaper where the marque selection is not available has default left click modifier. why this changes in comping? It’s totally unexpected. Is like a shock comping interface. Everything we are used to do gets changed: no re , no marquee selection , no copy .. what !!

[Daodan]

Originally Posted by deeb

Schwa: relatively to comping, as far as I remember unless now with re tool there is no place in reaper where the marque selection is not available has default left click modifier. why this changes in comping? It’s totally unexpected. Is like a shock comping interface. Everything we are used to do gets changed. no re , no marque , no copy .. what !!

If I understand correctly you can enable "Allow editing in comping lanes" in lane right click menu and you'll be able to use those tool.

[deeb]

Originally Posted by Daodan

If I understand correctly you can enable "Allow editing in comping lanes" in lane right click menu and you'll be able to use those tool.

Ohhh but then why is this default ? I will try. Thanks

[Sexan]

Maybe I've misunderstood:

This will ALWAYS promote to last comp? Just asking since I'm not sure is it supposed to create new comp or promote to last comp (when comping is not enabled)

[ovnis]

Originally Posted by schwa

Well... what are you trying to accomplish? You have effectively made those buttons disappear and now you are having trouble knowing where they are so you can click on them.

To have the most beautiful/ergonomic theme. I tested a lot of buttons and I realized that the least bad option was not to put buttons inside my theme.

Because before, i knowed where to click! It was to click on the numbers or letters.
But now, they are not within theses invisible buttons. They are offset.

[schwa]

Originally Posted by Sexan

This will ALWAYS promote to last comp? Just asking since I'm not sure is it supposed to create new comp or promote to last comp (when comping is not enabled)

In general, actions that create a comp area will activate the most recently used comping lane if there is no active comping lane.

[Sexan]

Originally Posted by schwa

In general, actions that create a comp area will activate the most recently used comping lane if there is no active comping lane.

ah ok thank you

[ovnis]

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

Do you know how to have the previous behavior? Is there an option?

I don't like this new behavior because the media item lane track takes too much space (height size).

I loved the fact that the previous edia item lane had the same size than other tracks.
If I wanted to enlarge the edia item lane, I zoomed on it. Currently, I have no choice at all. If there are lots of lanes inside media item lane track, it will take lots of space. It's less options and freedom.


Before:

(The black font for the media lanes! :love: )






Now:

[Sexan]

ok little weirdish:


So now track with enabled lanes have minimum height, but when you collapse it goes to another height and when you expand lanes it goes to third height.

BTW not a fan of disappearing lane buttons at some height (since it cannot fit vertically could it change to some horizontal variation?)

And also could the lane collapse/expand button be on top rather than bottom so it does not move all the time when resizing?

[rain]

Compared to v6.81 the v7pre has almost double amount of CPU consumption in
Performance Meter: RT CPU %
just with one VST-Plugin in Monitor FX chain (which is the mathaudio RoomEQ at high resolution setting)
and this also leads to crackles at 128 samples ASIO-Buffer, whereas v6.81 with same plugins does not crackle at 128 samples buffer.

When disabling Monitor FX chain, the high CPU consumption disappears. So somehow the VST-interface or threading code must have changed.

That is a pity. Must go back to 6.81 and can only try portable v7pre because of this.

[ferropop]

Originally Posted by rain

Compared to v6.81 the v7pre has almost double amount of CPU consumption in
Performance Meter: RT CPU %
just with one VST-Plugin in Monitor FX chain (which is the mathaudio RoomEQ at high resolution setting)
and this also leads to crackles at 128 samples ASIO-Buffer, whereas v6.81 with same plugins does not crackle at 128 samples buffer.

When disabling Monitor FX chain, the high CPU consumption disappears. So somehow the VST-interface or threading code must have changed.

That is a pity. Must go back to 6.81 and can only try portable v7pre because of this.

This might be connected to my issues with AudioMovers ListenTo that sits in my Monitoring Chain and provides a HQ realtime stream of Reaper's audio for remote sessions. In the last couple pres it has been constantly disconnecting, something I haven't experienced before. I contacted their support but they're having no connectivity issues.

[ferropop]

Schwa crash bug with Melodyne:



1. I have a Fixed Lanes comp, with Melodyne edits
2. I recreate the comp using the old Items/splits method with the same media
3. Putting Melodyne on that track results in an instant a crash.


I came across this because, when Melodyne is on a Fixed Lanes comp there is a significant cut in the audio when changing active takes - which did not used to be the case in item/splits comping. It doesn't even have to involve the currently playing items - you could be on bar 1 and change the active take on bar 45 and the audio will completely drop out for up to a second. It's very jarring and disruptive. So I wanted to compare/contrast that this did not used to be the case in the old takes/splits system with Melodyne - you'd change the active take and it would instantly swap over with no dropout. Couldn't get that far to prove it however lol . But hope you can look at both as they are related.

[ferropop]

Still coming across stuff like this a lot unfortunately :