* Includes feature branch: 128 channels per track * Includes feature branch: fixed lane collapsing * Includes feature branch: configurable naming for in-project MIDI items * Includes feature branch: updated Windows manifest for newer OS features * Includes feature branch: always running non-bypassed FX when the UI is visible * Includes feature branch: crossfade new recording with existing media items if configured * Includes feature branch: video from background projects * Includes feature branch: FX containers * Includes feature branch: improvements to aligning takes after recording * Includes feature branch: arrange view override mouse modifier sections * Includes feature branch: toolbar armed/special animations * Includes feature branch: pooled and unpooled ARA edits * Includes feature branch: fixed lane comping * Includes feature branch: shortcut import/export improvements and multiple main keyboard sections * Includes feature branch: preview item selection for grouped tracks * Includes feature branch: GR metering as embedded UI for third-party VSTs * Includes feature branch: media item fixed lanes + Recording: improve record pass logic [t=277944][t=254484] + Routing window: improve display of new destination channels in menu [p=2666998] # Free item position: fix behavior when adding new recorded items to FIPM tracks # Media item lanes: actions to insert/add lanes automatically convert track to fixed lanes if needed # Media item lanes: add action to delete lane at bottom of track # Media item lanes: display keyboard shortcuts in fixed lane context menus # Media item lanes: fix TCP display after undoing item delete # Media item lanes: fix undo after running action to add lane at bottom of track # Media item lanes: improve predictability of auto-punch selected items recording on fixed lane tracks # Media item lanes: rename "copy items to new lane" actions to "duplicate items to new lane" # Media item lanes: when recording into a specific lane, trim existing content behind new recording # Performance meter: fix missing media column
Thanks so much for implementing recording into lane trimming behind and adding the shortcuts to the context meant. I’ll test everything as soon as I can.
Wasn’t the missing action actually regarding deleting the top lane not the bottom lane, as in a selection it’s impossible to delete multiple lanes at once so it just defaults to the top selected lane? Or maybe the action is misnamed?
Carryover from the single-channel logic (giving you 4 extra slots)... can remove it if it's bothersome
Thanks for the explanation! It's a judgement call here, but yeah I think it's a bit confusing as is. If you're keeping with the default on the single-channel options giving the user 4 new channels to add, then perhaps the multichannel options should also give 1 more option than currently populated, so you can start the multichannel all the way up to the max single channel offered.
When leaving Fixed Lanes mode, the Lanes real estate (to the right of the M/S buttons) remains as blank and wide as opposed to returning to the narrow non-Lanes state:
__________________
Cheers... Andrew K
Reaper v6.80+dev0621 - June 21 2023 • Catalina • Mac Mini 2020 6 core i7 • 64GB RAM • OS: Catalina • 4K monitor • RME RayDAT card with Sync Card and extended Light Pipe.
# Media item lanes: add action to delete lane at bottom of track
^^^
Here is a quote from me 2 days ago regarding this:
“The action "delete lane (including media items)" is missing from the actions list. Can you please add it? Also this same action ignores the rest of the selection besides the top lane when run and is only able to delete one”
Is that action in response to this and does it work opposite to the previous behavior for that entry in the context menu? Sorry not at the computer to test if anyone is interested they can test and otherwise I’ll test later and report back.
When I record Takes on regular track (back to back) the earlier item length changes (+.010?) and you get a crossfade between items (similar to using comps in a Fixed Lane). Is this expected? Also how can an item's length just change, wouldn't that effect its sound?
Here are some more thoughts and questions about the actions in the comp lane context menu:
EDIT: 5 ACTIONS total missing from context. Check my next post in this thread
Also the order of options in the bottom chunk of the context menu could be improved as well as the naming so there is more consistency. My suggestions would be:
Add empty lane above this lane (NAME CHANGE!)
Add empty lane at bottom
Delete lane (including any media items)
Automatically remove empty lanes at bottom of track
I think the name change and order change make much more sense.
USER ERROR as I explain in next post: The following action isn't working correctly:
Action ID: 42501 Item lanes: Delete lane at top of track (including media items)
For example if you have 3 lane from top to bottom 1,2 & 3 and only lane 3 selected, if you run the action the remaining lane is lane 2 and lane 3 and 1 are removed instead. Seems like a bug.
I noticed some quirks with the modified record into lane feature:
Create new media items works as expected - stacks material behind the other material
Tape mode - works as expected, prints over material then makes more takes on loop
On the other hand, takes mode does not work as expected!
The user would expect the first pass over a media item to create the first take but instead it trims behind on the first pass and creates takes on loop which is not the behavior that matches takes mode when not in fixed lanes which is confusing and must be a bug
Also this dev release doesn't let you make a new ReaScript. When you select new ReaScript, it behaves the same as selecting load Reascript. So I don't believe there is a way to paste code for a new action at the moment.
So effectively takes mode in loop recording within fixed item lanes behaves identically to tape mode which is an error. Thanks everyone!
^^ they are not on it. They are on making lanes as is supposed to be. Chill, after lanes are good then it will finalized. Comp works on lanes and not the opposite . I know nothing but that is how I feel.
^^ they are not on it. They are on making lanes as is supposed to be. Chill, after lanes are good then it will finalized. Comp works on lanes and not the opposite . I know nothing but that is how I feel.
Instead of blaming and speaking bad to others who tried to help you, why don't you keep your opinion for you instead of trying to create noise for other people's requests?
^^ they are not on it. They are on making lanes as is supposed to be. Chill, after lanes are good then it will finalized. Comp works on lanes and not the opposite . I know nothing but that is how I feel.
Instead of blaming and speaking bad to others who tried to help you, why don't you keep your opinion for you instead of trying to create noise for other people's requests?
You didn’t try to help. You were basically trying to make my self opinions has silly and not fundamented.
You didn’t try to help. You were basically trying to make my self opinions has silly and not fundamented.
I think you have an ego issue, I tried to help you in the past when you didn't know nothing and thought that switching from comping to layering was not possible. I tried to let you know that's already possible and when i said that you should try it you called me no thanks "I'm straight". Then a couple of pres back you started to blaming the testers of fixed lanes and RE because of your needs. Thonex yesterday tried to help you again and you talked to him to keep silent. WTF is this behavior doing in this thread i have no idea...
And now instead of looking at the features, you create noise for the rest of us here.
I think you have an ego issue, I tried to help you in the past when you didn't know nothing and thought that switching from comping to layering was not possible. I tried to let you know that's already possible and when i said that you should try it you called me no thanks "I'm straight". Then a couple of pres back you started to blaming the testers of fixed lanes and RE because of your needs. Thonex yesterday tried to help you again and you talked to him to keep silent. WTF is this behavior doing in this thread i have no idea...
And now instead of looking at the features, you create noise for the rest of us here.
You and other try to redicule what does not fit your vision. It happened in RE and it happened here. In the end what you try to redicule tends to be implemented, and instead of a half wacky feature becomes a full feature. I spend time to help devs and reaper, if not welcome they can tell me so, not you and anyone in this forums.
Don’t play victim. Treat others with respect you will receive the same. I won’t talk more about this.
# Media item lanes: when recording into a specific lane, trim existing content behind new recording
Thanks!
I'd personally prefer if classic take recording didn't trim on the first recording pass/loop.
Also when "Creates new media items in fixed lanes" is selected, it would be great if "Record into lane" acted like a manual "starting point". Trim (or layer) record into the lane and move the "Record into lane" marker to the next lane after each recording pass/loop iteration.
I guess this "starting point" functionality could also be an extra option, but I don't really see much value in recording multiple item layers into a single lane. The only use cases I can think of:
1: Recording a layer on top of an existing item to replace a part while keeping the source (with enclosing item mix behavior)
2: When using lanes like track alternatives it could be useful to have a single lane contain multiple layers?
Both of these seem extremely niche to me. Overall, lanes are far superior for any layering workflow. So I wouldn't mind if this old style of layer recording was completely removed from REAPER.
Thanks!
1: Recording a layer on top of an existing item to replace a part while keeping the source (with enclosing item mix behavior)
2: When using lanes like track alternatives it could be useful to have a single lane contain multiple layers?
Both of these seem extremely niche to me. Overall, lanes are far superior for any layering workflow. So I wouldn't mind if this old style of layer recording was completely removed from REAPER.
1) Someone yesterday referred a use case which seemed interesting and related:
Quote:
Originally Posted by chickentiko
This would be amazing. It would be a bit like pro tools style playlists. "Record into lane" doesn't work like this currently. It puts the new item BEHIND the old one. It would be more useful if it wrote over it, tape style.
The advantage to this workflow over auto comping is incase you need to record a really difficult phrase multiple times until you"got it". It would mean fewer lanes but higher quality lanes, as opposed to 100s of lanes full of mistakes that you'd need to delete anyway.
What do you think?
2) "I wouldn't mind if this old style of layer recording was completely removed from REAPER."
If I get it right, I would mind if there is no way to record media item takes in a single lane. Is super useful and not at all “old school” is actually “new age”
I am more about having options as much as possible and viable then removing functionalities.
Some general thoughts on fixed lane header buttons:
I'd prefer it if dragging to reorder was not possible on the button itself (only on lane background). Instead dragging on the button could be used to solo multiple lanes (like dragging on tcp solo/mute). Maybe even drag to delete multiple lanes?
Imo it would be more consistent if double click on the lane background selected all items in that lane (instead of renaming lane).
If I get it right, I would mind if there is no way to record media item takes in a single lane. Is super useful and not at all “old school” is actually “new age”
^^oki thank you. But i got it right since until now i can't record Media Item Takes while in FIL, so my opinion is the same. I prefer having layers (but just last one playing) then no layers and no Media Items Takes. If they allow Media Takes recording per lane. Everything changes.
You and other try to redicule what does not fit your vision. It happened in RE and it happened here. In the end what you try to redicule tends to be implemented, and instead of a half wacky feature becomes a full feature. I spend time to help devs and reaper, if not welcome they can tell me so, not you and anyone in this forums.
Don’t play victim. Treat others with respect you will receive the same. I won’t talk more about this.
LOL, whatever, if you mean to switch from comping to layering that's already possible Because I didn't said anything about recording to you...
Also don't tell me about you spending time here, since I'm from the very start of the development.
So just don't put your ego on me again as I'm not gonna be tolerant again, as you should treat others good first and not the opposite because that's not helping at all.
LOL, whatever, if you mean to switch from comping to layering that's already possible Because I didn't said anything about recording to you...
Maybe you should re read again what you wrote.
Originally Posted by deeb View Post
“Maybe you can show your experience recording midi (layering and monitoring previous lanes) and switch back and forth between layering and comping. And all the things that already been written.”
Originally Posted by deeb View Post
“Maybe you can show your experience recording midi (layering and monitoring previous lanes) and switch back and forth between layering and comping. And all the things that already been written.”
You: I already tried you should too
Yeah first your answer was with a touch of irony and then you wrote "no thanks I'm straight", which was the reason this thread was closed. Nice!
And then my answer went to that it's possible to switch from layering to comping and that you should try it by your self instead of just saying it's not possible. If recording to midi was not the behavior you wanted don't blame or speak bad to me. End of discussion, now move on.
Can one of you please stop responding to the other one? Thx...
Yep, I'm pretty much done here. Sorry for the noise to everyone, but i felt i had to make clear a few things since i wasn't the one who started it here.
When leaving Fixed Lanes mode, the Lanes real estate (to the right of the M/S buttons) remains as blank and wide as opposed to returning to the narrow non-Lanes state:
Leaving fixed lanes mode how? Note also that there is a preference in Appearance/Track Control Panels to align TCP controls when fixed item lanes are used, which will cause all tracks to display that area when any track in the project is set to fixed lanes.
When I record Takes on regular track (back to back) the earlier item length changes (+.010?) and you get a crossfade between items (similar to using comps in a Fixed Lane). Is this expected? Also how can an item's length just change, wouldn't that effect its sound?
Yes, that's a bug in the new-ish code that applies autocrossfades to recorded items, essentially a greater-than-or-equal-to test that should be strictly greater-than.
Action ID: 42501 Item lanes: Delete lane at top of track (including media items)
For example if you have 3 lane from top to bottom 1,2 & 3 and only lane 3 selected, if you run the action the remaining lane is lane 2 and lane 3 and 1 are removed instead. Seems like a bug.
I'm not able to reproduce a problem with this action. Could you post a screencap?
Regarding recording into Fixed Lanes: I find myself every time after recording into a new track with the option (something like 'Record into Fixed Lanes') switching from default 'Play all lines' to 'Play only last recorded' (sorry, not on a computer now so names are just guesses).
Is there an option to select a default style from options which lines will be playing after recording for new tracks?
Treat others with respect you will receive the same.
Nothing I have ever seen coming from your end. You are handing over hearts without meaning it. People have feelings you know? Don't play with their hearts.
Regarding recording into Fixed Lanes: I find myself every time after recording into a new track with the option (something like 'Record into Fixed Lanes') switching from default 'Play all lines' to 'Play only last recorded' (sorry, not on a computer now so names are just guesses).
Is there an option to select a default style from options which lines will be playing after recording for new tracks?
That option was removed a while ago.
v6.77+dev0304 - March 4 2023
+ Media item lanes: after recording with comping disabled, play existing lanes plus the new recorded lane if multiple lanes were previously playing, otherwise play only the new recorded lane
Hey Shwa! Here is a gif. I am running command ID 42501 EDIT: DONT THINK THIS A BUG
I think part of my confusion is if some of the actions I am assigning keystrokes to are the same as those in the context menu.
For example many say "under mouse" while none do ion the context menu, but most actions I add shortcuts to show up but not all.
Here are the ones I've found that the shortcuts don't get visually added to the context menu:
Command ID: 42487 Item lanes: Comp into a new copy of lane under mouse for track under mouse
Command ID: 42499 Item lanes: Comp into lane under mouse for track under mouse
Command ID: 42471 Item lanes: Record into lane under mouse
Command ID: 42478 Item lanes: Play only lane under mouse
Command ID: 42480 Item lanes: Toggle playing lane under mouse
5 missing keystrokes total from context menu ^^^
The 2nd attachment shows the missing keystrokes - I assigned keystrokes to every action that you can see in the screenshot with the only exception being "allow editing source media while comping," so every other action should have keystroke representing it.
And also thought I should reiterate simply that record into lanes is super close besides that takes mode actually functions like tape mode (no difference at all) which is an issue for loop recording in takes mode, as the user would expect the first pass to make another take and not to trim behind.
Sorry if I before I said takes mode wouldn't make sense to use within fixed item lanes, because without all 3 record modes being represented identically to how they would work in arrange view, things get super confusing.
Thanks to the best devs <3!!! We are grateful
Edit: Just realized I don't think this is a bug and I'm misunderstanding the action. The action "delete lane (including any media items) is different than the than action ID 42501 which I was triggering with a keystroke. So I suppose the action I was looking for is based on lane selection which doesn't exist yet.