v6.78+dev0407 - April 7 2023

[Vagelis]

When only one lane is visible and we record to another lane, its still possible to see the recording but I'm not sure if this was the intention.

[Vagelis]

I think that it would make sense to reset the lane number to one after removing all items with lanes, instead of showing the number of the top lane.

[skylar_battles]

Vagelis, what action is removing all those lanes at once? I haven't been able to figure that out.

[Vagelis]

Originally Posted by skylar_battles

Vagelis, what action is removing all those lanes at once? I haven't been able to figure that out.

It's Razor edit to select all items and then delete. With RE you can move/edit comp areas as well.

[Funkybot]

Originally Posted by schwa

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

Maybe this isn't working as expected then, or just behaves differently based on other criteria but it seems like by default, MIDI items at least, are defaulting to playing all.

Example:

1. Record some MIDI, hit stop, go back to start
2. Go back to start, record some MIDI, hit stop, go back to start
3. Go back to start, record some MIDI, hit stop, go back to start
4. Press play

Result: multiple lanes playing.

This is with the default option "Record input (audio or MIDI)".

This layering behavior is great for laying MIDI drums into separate fixed lanes, so definitely want to keep it, but maybe not the best for a default. And toggling the behavior per track would indeed be desirable.

Might even be good to add some of these options to the "Input" right click menu on the TCP near the record options.

[Funkybot]

In regards to my above post, I also should note that when you're recording MIDI as outlined above, you're not hearing the prior lanes. So it's strange that you'd hear only the currently recording track while recording, but while playing back you hear all lanes. That makes the current behavior not useful for layering drums. In that use-case, you'd want to hear the prior pass.

I think there should be a toggle we can set per track: "Play all lanes when not comping" or "Play last lane when not comping". The default should be play last. But I'd want those options in the right-click menu for the TCP input channel.

[schwa]

Originally Posted by Funkybot

Example:

1. Record some MIDI, hit stop, go back to start
2. Go back to start, record some MIDI, hit stop, go back to start
3. Go back to start, record some MIDI, hit stop, go back to start
4. Press play

Result: multiple lanes playing.

The intended behavior as per the changelog line is: "play existing lanes plus the new recorded lane if multiple lanes were previously playing, otherwise play only the new recorded lane."

So, after step 2, if you only want to hear a single lane, click the lane 2 button (or the lane 1 button). Then there will only be one lane playing, so recording into a new lane will result in only the new lane playing.

[skylar_battles]

If you want to hear selected lanes while recording you need to tick "monitor track media when recording" which is available in the right click context menu on the record arm button.

[Vagelis]

Dragging the edge of an item with unsynced areas could create overlapped areas even without a crossfade. But then clicking/moving the overlapped area it seems to remove it. Would it be possible not to create it when there's no crossfade?

[Funkybot]

Originally Posted by schwa

The intended behavior as per the changelog line is: "play existing lanes plus the new recorded lane if multiple lanes were previously playing, otherwise play only the new recorded lane."

So, after step 2, if you only want to hear a single lane, click the lane 2 button (or the lane 1 button). Then there will only be one lane playing, so recording into a new lane will result in only the new lane playing.

I think it's the "if multiple lanes were previously playing" that's throwing me off. If I'm recording one lane at a time as outlined above, and I'm not hearing those prior lanes during recording, then I'd say the "if multiple lanes were previously playing" condition was not met. There was only ever one lane playing. Therefore, I'd expect, "play only the new recorded lane" to be in effect. But it's not. I'm hearing all lanes. Which isn't what it says. At least, not how I'm reading it.

It's also unintuitive to NOT hear all lanes while recording, then jump to hearing ALL lanes on playback. The recording/playback behavior should be consistent and not change IMO. If I'm going to hear all on playback, then I should hear all on recording and vice versa. Seems logical to keep it consistent.

And I hope it doesn't come across like I'm arguing for any one behavior. Just kind of jumping in and checking on the lane behavior on a Saturday and being a bit confused by what I'm running into. I think before this eventually goes live, trying to figure out how to simply and clearly communicate the various permutations of options will need to be taken into account. It can't be hard to figure out the difference between "layer mode" (which may involve setting 2 or 3 different options right now) and "last lane mode" especially in regards to the various recording/monitoring modes we have today.

[deeb]

Some thoughts:
Maybe if a track is in fixed item lanes and comping is off:
- the recording mode should defined in “new recording that overlaps existing media items” setting
- the “monitor media while recording would not be necessary to be ticked. That’s what we went to do when layering.
- Allow to create comp or edit selected comp from the lanes right click menu to create an empty space or edit a specific comp
- only the resulting comps would be shown in the lanes
- would be welcome to have fxchains and/or audio outputs

When comping with “new comp” or “edit comp”
- just the items of that comp would be displayed.

With this workflow I think we would have a perfect workflow for everyone.

[skylar_battles]

sounds like Vangelis could explain what a synced vs. unsynced comp area is? Haven't been able to figure that out.

deeb I assume you've also run into the issue of takes mode in lanes actually behaving as tape mode even when set to takes mode? My fault!

Forgive my thoughts yesterday, all 3 record modes should be honored in fixed lanes It was a judgment error. deeb was right!

My apologies because my line of thinking prior makes it IMPOSSIBLE to not lose content of the first pass when doing loop recording which is not desired behavior, unless it is selected in tape mode. Takes mode still trims behind the first loop and acts no differently than tape mode. Sorry for repeating just trying to be clear.

Also edited my previous post about actions whose keystrokes don't show up in the context menu. 5 total so far

Another is this a bug or lack of understanding:

"Duplicate items to new lane" from the context menu seems to only be able to work on items across 1 track and not multiple. Is this by design or part of the lack of lane selection actions at the moment?

[Gass n Klang]

Originally Posted by Edgemeal

v6.78+dev0407 - April 7 2023

+ Recording: improve record pass logic [t=277944] [t=254484]

nice, could we have further improvements on this? To use recpass as a take number indicator, we need a window that shows the current recpass during recording and the next recpass value when recording is stopped. Besides it would be super helpful if we could add a description. In classical music recordings I normally want to differenciate takes by production date or rehearsal and concert (e.g. day1-001).

Edit:
there seems to be bug: create 2 tracks. record midi to track 1 only (recpass 1), then do a new midi recording on both tracks. They won't have the same recpass. seems to work with audio inputs though

[Vagelis]

Originally Posted by skylar_battles

sounds like Vangelis could explain what a synced vs. unsynced comp area is? Haven't been able to figure that out.

Unsynced comp area is when the area in fixed lanes is not longer "tied" with the item in comp lane, so you can edit the item in comp lane separately from its source. If you move or edit an item in comp lane, it automatically unsyncs from the comp area in fixed lanes, and the edits are not being reflected to the source to destroy it. There's also a circle indicator on unsynced areas in comp lane and if you double click on the area, it recomps/syncs the unsynced edits and pastes them to a new lane as a new source. That way the edits will not get lost and we can recomp them with the rest sources bellow.

With synced comp areas the items in comp lane are always "tied"/synced with the areas in fixed lanes. They can stay in sync if you move or edit the areas in comp lane instead of the item (because editing the item will unsync).
So moving the area in comp lane it will also move the comp with the source in fixed lanes, which is useful when we want to move a comp somewhere else on the timeline and comp it with other sources (also pretty useful when only the comp lane is visible and switch comps from the arrows)
I prefer to do this in fixed lanes though, because I can see all lanes and then i can copy an area, drop it to a new empty lane bellow other comps and switch between them without loosing anything.
Also synced areas are extremely useful when there are multiple comp lanes. Yep, you can create multiple comp lanes and switch comp variations, but in order to see those comps or change them at anytime later they have to be synced.

So you can choose the way you want to work with. I personally like to edit comps and items in fixed lanes where everything stays in sync and apply the crossfades in comp lane. If I want to make multiple edit variations from a source, I edit the item in comp lane to unsync, then double click on the area to recomp the new edits to a new lane, comp again the initial source, edit, recomp etc...
Other people like to leave their sources untouched and edit the items in comp lane to unsync, but you can choose your own way since there's lot of flexibility.

EDIT: not sure if I covered it all, check also the comp area mouse modifiers to have a better view of the functions and let me know if you have any other questions.

[Vagelis]

Another weird behavior where unsynced areas sync with fades.

[deeb]

Originally Posted by Vagelis

It's Razor edit to select all items and then delete. With RE you can move/edit comp areas as well.

It’s not because of this. You achieve the same with item selection and delete if you have the option:”automatic remove empty lanes at bottom” (right click In lanes)

this seems the default, but I would like to change that at some point. I like to have to have full control on the lanes. No magic deleting. I couldnÂ’t imagine if this would happen in tracks also.

[Vagelis]

Originally Posted by deeb

It’s not because of this. You achieve the same with item selection and delete if you have the option:”automatic remove empty lanes at bottom” (right click In lanes)

I know...RE is what i used in my gif to select the items since it's what i prefer using in lanes over marquee selection, didn't say it's because of this...
You can use the right click menu or mouse modifiers to delete lanes as well but one at a time.
No need to have "”automatic remove empty lanes at bottom” enabled.

[Justin]

Originally Posted by Gass n Klang

there seems to be bug: create 2 tracks. record midi to track 1 only (recpass 1), then do a new midi recording on both tracks. They won't have the same recpass. seems to work with audio inputs though

thx, fixing

[skylar_battles]

Added some more info last night to my prior post made on 11:03AM yesterday that might be helpful for sorting out these 5 command ids not showing up in the context menu and also about the record into lane function not honoring takes mode in loop recording, per my severely misguided request.

It seems deeb and FeedTheCat agree about the 3 record modes being honored when recording into lane and in practice it only makes sense.

Don't exactly know pre-release etiquette yet but I can paste the most relevant info here if that's helpful to see, or anyone can reference the edited post. Thanks everyone!

Vangelis thanks for the excellent and detailed explanation! The level of flexibility can be intimidating at times but is worth it!

I studied all of the mouse modifiers and the only one I couldn't figure out was for:

Fixed Lane Comp Area - Command Option Left Click "Heal comp area with adjacent areas on same lane"

Also don't exactly understand the use case for command double click, "extend comp area to next comp area"?

[Andreya]

Got a reproducible crash here when recording items into fixed lanes while looping, but only with ChrisGlitch playing on the audio. Segfaults the first time it reaches the loop point every time.

And if I replace ChrisGlitch with Avocado, it doesn't crash, but the Avocado doesn't do its thing until record stops.

EDIT: To be clear, I've got a beat on a different track, sending from that to another one. The second track has fixed lanes enabled, and is set to record its output. The glitch plugins go on the first track.

Attaching the stack.

[Hipox]

Originally Posted by Funkybot

I think it's the "if multiple lanes were previously playing" that's throwing me off. If I'm recording one lane at a time as outlined above, and I'm not hearing those prior lanes during recording, then I'd say the "if multiple lanes were previously playing" condition was not met. There was only ever one lane playing. Therefore, I'd expect, "play only the new recorded lane" to be in effect. But it's not. I'm hearing all lanes. Which isn't what it says. At least, not how I'm reading it.

Agreed, thanks for clarifying this!

[ferropop]

Originally Posted by skylar_battles

Fixed Lane Comp Area - Command Option Left Click "Heal comp area with adjacent areas on same lane"

If you Split an Area (so two adjacent comp areas are on the same lane) this will heal the split - combining them together into one comp area.

Also don't exactly understand the use case for command double click, "extend comp area to next comp area"?

If you have two adjacent areas but there's a gap in between them, it will "fill the gap" by moving the right-edge of the first area to the left-edge of the second area, binding the edges together.

[schwa]

Originally Posted by Andreya

Got a reproducible crash here when recording items into fixed lanes while looping, but only with ChrisGlitch playing on the audio. Segfaults the first time it reaches the loop point every time.

And if I replace ChrisGlitch with Avocado, it doesn't crash, but the Avocado doesn't do its thing until record stops.

EDIT: To be clear, I've got a beat on a different track, sending from that to another one. The second track has fixed lanes enabled, and is set to record its output. The glitch plugins go on the first track.

Attaching the stack.

The crash is happening within the plugin code. I'd be surprised if this crash actually has to do with fixed lanes -- if you take the track out of fixed lanes mode does it not crash?

[skylar_battles]

ferropop thanks so much for those responses! I was able to test out and understand what you meant so I can apply that information to my workflow when necessary!

Would you also be in favor of all 3 of the recording modes being honored when recording into fixed a item lane with myself, deeb and, FeedTheCat?

I feel like we may be in similar recording situations at times and when tracking vocals, if you wanted to punch into a difficult spot, if the original recording pass was pretty good you would want to keep it in addition to creating more takes over a specific part, right?

Also with how it is at the moment you could only take one pass of takes while recording into a lane in loop record before they are all printed over and another pass of takes is made which doesn't make sense at all.

[ferropop]

Originally Posted by skylar_battles

ferropop thanks so much for those responses! I was able to test out and understand what you meant so I can apply that information to my workflow when necessary!

Would you also be in favor of all 3 of the recording modes being honored when recording into fixed a item lane with myself, deeb and, FeedTheCat?

I feel like we may be in similar recording situations at times and when tracking vocals, if you wanted to punch into a difficult spot, if the original recording pass was pretty good you would want to keep it in addition to creating more takes over a specific part, right?

Also with how it is at the moment you could only take one pass of takes while recording into a lane in loop record before they are all printed over and another pass of takes is made which doesn't make sense at all.

There's been discussion all long about what the proper defaults should be and afaik the devs are waiting before deciding on anything because things are constantly changing.

But yes, daily I'm in the situation where some vocals have been comped and I want to add new takes without affecting the comp, but also have the auto-mute kick in on a time selection. Then there's situations where I want a different configuration of all of the above. So it's difficult (even for one person, let alone everyone) solving what the desired behaviours should be.

This almost requires switchable profiles for doing specific things. Auto comp if existing comp exists? Auto comp only time selection? Auto-mute comp when recording? Auto-mute only on time selection? When should reaper Play All Lanes? When should it auto-set the last recorded lane as active? All of these interact with each other, and all of them define different desirable behaviours depending on what you're doing.

Maybe that's a solution - being able to define exact behaviour combinations and load them when you need them, and being able to pick one as Default.

[skylar_battles]

But I suppose this is different than a default because it's just a behavior that takes precedence when record into lane is on a for a specific lane (not most of the time when doing new recording passes)

If the record mode from arrange view isn't the same as record into lane is just becomes confusingly inconsistent, so my thinking is that it's an important option to have and will help the system make sense for recording into a lane. Otherwise what defines the behavior?

Just thinking about it more it makes more sense because if you are setting up a loop recording and using create new media items to access fixed item lanes, by "default" if you record into a lane it will create overlapping media items unless you have changed that setting. (the "what happens for overlapping media items that occur during recording" mode)

Only then if you select record into a lane and also change thew record mode to one of the other 2 would it exhibit those same exact behaviors in loop record and otherwise. Right now it almost works like this.

I think you're posing some great well thought out questions but on the simplest level of recording into a single playing lane, having the record modes be consistent seems like an important asset to the system.

I feel like recording into material that is part of a synced comp is more niche than the basics of the record modes being consistent as for the most part if you wanted to punch a small bit of source material usually I would think do to that before comping, but if not you could always duplicate items in relevant areas to another lane and to some punches there and use that as the source for the part you wanted to improve.

I guess to put it more simply, I think accommodating the scenarios you are mentioning is made possible with the consistency of Reaper's record modes being the same in fixed lanes. All I'm really asking is for takes mode to work like takes mode and not tape made when recording into lanes It behaving predictably won't take options away from users if that makes sense.

You could also make an action to record into lane and change the record mode in arrange view and another to disable that recording lane and change modes in order to record more full passes. That seems to keep things simple and functional as opposed to another set of recording modes as it's really close at the moment.

Sounds like 4 of us total are on board for that now!! maybe chickentiko as well?

[deeb]

Originally Posted by skylar_battles

If the record mode from arrange view isn't the same as record into lane is just becomes confusingly inconsistent, so my thinking is that it's an important option to have and will help the system make sense for recording into a lane. Otherwise what defines the behavior?

The record modes needs are exactly the same has for tracks, so lanes should inherit this modes too. Unless they build same modes but specifically to FIP.

[skylar_battles]

You were right from the beginning so hopefully we'll see the change in the next dev version! Didn't mean to screw it up!! It is far less complicated this way and more applicable.

[deeb]

Yeah. I think this will be possible. What do you think of the thoughts I posted earlier in thread: about 2 views: layering lanes and comping lanes. This does not exist at all, I just imagine that it could work nice. You get the picture?

This:

Originally Posted by deeb

- Allow to create comp or edit selected comp from the lanes right click menu to create an empty space or edit a specific comp
- only the resulting comps would be shown in the lanes

When comping with “new comp” or “edit comp”
- just the items of that comp would be displayed.

[skylar_battles]

For sure! Flexibility is key so glad I figured out my my past thinking was flawed as soon as I tried some loop recording within a fixed lane.

- the recording mode should defined in “new recording that overlaps existing media items” setting YES

- the “monitor media while recording would not be necessary to be ticked. That’s what we went to do when layering. YES
addition: menu option would be greyed out or change to relevant info "Monitored lanes are determined by lane selection prior to recording" I'm big on menu options specifying relevant info to not confuse users.

- Allow to create comp or edit selected comp from the lanes right click menu to create an empty space or edit a specific comp
- only the resulting comps would be shown in the lanes

I don't quite understand what these 2 mean. Is the first of these 2 points a request for a specific right click action in the context menu and the 2nd I'm not sure. Maybe the first of these points is what I was trying to to with duplicate media items to tracks but that action only works across a single track with adjacent items.

- would be welcome to have fxchains and/or audio outputs YES but I imagine there's more to tackle first

When comping with “new comp” or “edit comp”
- just the items of that comp would be displayed.
Wouldn't this cause an issue if you want to comp from material that is not displayed?

[chickentiko]

Imo - the cleanest implementation would be this:

Non comping lanes (let's call them "record lanes") should behave in the same way as normal tracks. (Follow record mode set in options menu, tape style/takes/create new item lane)

Comping lanes can have special comping features but can't be recorded into. Only comped from "record lanes". I'm sure someone will have a cool way of displaying this on the interface. Could be a pretty unique feature of reaper if it works well. Looking ahead, who knows, maybe you could have whole comp tracks and comp ACROSS tracks, but I'm certainly getting ahead of myself here.

If tape mode (trim item behind new recording) is selected, then record into the "active lane" (yellow dot) and trim item behind. If multiple lanes are active, record into all active lanes and trim item behind. (This is kind of like pro tools style playlists). It's a great workflow if you want a more manual approach to takes. It is definitely my preferred method as you are left with higher quality takes to edit from, rather than tonnes of "half takes" or poor takes. The workflow would feel something like this: select the lane you want to listen to, notice a mistake, immediately hit record to fix the error. Done. No need to select "record into lane".


If create new item lane record mode is selected, use the current behaviour and make a new lane for every recording.

Implementing take mode in the fixed lane system could get messy, but it's a cool idea, and if the Devs choose to go with our suggestion of having take lanes behave as normal tracks with regards to recording, then this could be pretty cool. It would make fixed lanes feel more like different VERSIONS of the track as opposed to simply different takes, if you get my jist.

Just my two cents....

[deeb]

Originally Posted by skylar_battles

“When comping with “new comp” or “edit comp”
- just the items of that comp would be displayed.”


Wouldn't this cause an issue if you want to comp from material that is not displayed?

That is why in layering lanes context you could edit selected comp which would display only the lanes which hold the selected comp material and the comp it self.

And then back to layering: only the comps(not the material)and whatever recorded or imported during layering mode is displayed in the layering view.

The thing is: a comp is made of several material, but this material should not be displayed in the layering view. This material is irrelevant in the layering perspective because only the Comp Is effectively a layer that we might want to layer with other material. Hope it makes sense …

[skylar_battles]

Thanks for your response chickentiko!

But the issue is the take mode is already implemented in the fixed lane system because if you loop record in tape mode reaper gives you takes otherwise you would just print over everything and that wouldn't make sense.

At first I thought takes would be a nightmare, but ultimately without them it creates the issue I've described. Reaper has no logical behavior in loop record if it's just printing over itself that's why it creates takes.

For the record at the moment for the record into lane feature:

create new media items works as expected
tape mode works as expected
takes mode does NOT work as expected. destructively removes first pass instead of keeping it

The issue with comp lanes having different features at all is that nothing differentiates them as comp lanes - it's just how they are used even though they are action that make it seem otherwise. You could use an action to create a comp lane and then use it for something else - Reaper won't care and I doubt that's something that they want change for flexibility's sake which is why I think for simplicity we should have these record modes mirror what they normally do.

Recording into fixed item lanes with create new media items and the lanes armed seems like an extra step compared to just recording normally which will automatically create more more recoding passes and put them in their own fixed lanes. So even though create overlapping items in lanes seems useless for the most part, without it it becomes really confusing as the system seems to be designed to just record without arming a lane and to give you the resulting recording passes in fixed item lanes. I also think if lane selection and lane recording are not 2 separate things that could cause issues as often you want to hear lanes in addition to what you're recording and then selecting those lanes would cause them to be recorded on as well. So I think the simplest think is to just allows takes mode to work as takes mode and not tape mode. In most cases when not punching in you can delete bad recording passes and just record again automatically creating more lanes.

[skylar_battles]

deeb, a bit confused on what you mean there. could you maybe explain a use case so I could better understand?

[deeb]

Originally Posted by chickentiko

Imo - the cleanest implementation would be this:

Implementing take mode in the fixed lane system could get messy, but it's a cool idea, and if the Devs choose to go with our suggestion of having take lanes behave as normal tracks with regards to recording, then this could be pretty cool.

If I am able to record with takes, means that from each cycle of recording the last take will be listanable and in this way if I pick my instrument or midi keyboard we record - stop - record - stop - record - stop and I already have 3 layers playing simultaneously and all the versions are managed by the take system which is great!

[deeb]

Originally Posted by skylar_battles

deeb, a bit confused on what you mean there. could you maybe explain a use case so I could better understand?

I will make graphic tommorow. 🙏🏻

[skylar_battles]

thanks deeb!

chickentiko, you'll see the issue if you take a pass you like and try to record some punch ins in loop record. You lose content of source material which should only occur when tape mode is selected.

So this workflow could be
1. separate loop and time selection
2. set loop selection 4 bars long and time selection for auto punch in
3. set lane to record
4. change record mode to takes mode
5. Reaper will record new passes of takes for the difficult section while keeping the original performance that was imperfect for reference or to revert to

So since takes and tape mode are similar in loop record but not the same being able to make this small choice is very helpful for punch ins where you want to preserve the original material and possible revert to it. Then if you select the original slice of the punch in and crop to active take and then heal the item it would be like you never tried to punch in.

With how it is now it can't be restored besides with using undo which is often not desired so herein lies why the option is necessary.

So actually then only mode that makes sense to use for punch ins with record into lane would be takes actually even though it sounds counterintuitive as tape mode would cause you to lose all of your punch attempts every time you start recording again which is mostly not desired and right now the only behavior we have UNLESS create new medias items is chose for overlapping recorded media and that which does create overlapping items. Even though not useful, I think appropriate for continuity.

Maybe a simpler may to think about it now is, per try recording into a lane, you only have one chance to punch in for every pass because it deletes all takes in time selection when you start recording again for that lane. That's why we need the takes option. It would be the only logical way to cycle through choices as media items in a fixed lane that are overlapping will immediately become impossible to manage and tape mode is destructive which is probably never desired when working with fixed lanes. Makes me think takes within lanes actually only makes sense.

The controversial thing, is that I can only see the logic of using takes mode when recording into a fixed item lane if anything it could only allow takes modes when recording into a lane with overlapping items. That is how I'd end up using this function anyway otherwise I just record on the track creating more fixed item lanes. But I'm sure that would confuse people which is why all 3 modes should be honored

But if recording into a lane was fixed to takes mode only, you could easily cycle takes with T and shift T to audition different punch in attempts while looping the section. now that seems like the only use case to me after all of this thought but I support all the options being available. Also it being fixed to takes only would save a step, because why would you record into a lane and want to create items on top of it or lose the contents of the original performance? Just some thoughts that I can't help but share.


And actually because this seems like the only use case considering the action could be changed to "Record into lane (takes only)"

So record arming a lane and the track would be enough to create some alternate choices for a section in the takes format.

Then you would never have to bother changing the record mode from create new media items and could also switch between punching in just recording more passes. You would just keep the track record armed 100% of the time with the record mode set to create new media items, and then toggle "Record into lane (takes only)" if there was a lane you wanted to reattempt or a section within in it to be accessed by time-selection auto punch or media item auto punch.

What other use cases would there be for recording into a lane besides punch in attempts? I can't think of any which is why strangely it could only allow takes mode. I can't think of when the other would be useful but please share. Record into lane allowing takes only would make the steps in the above explanation much faster.

Poll in separate thread: https://forum.cockos.com/showthread.php?t=278077

[ferropop]

Not sure if this is related to all the MIDI stuff that has been happening, but the action "Insert new MIDI item..." is creating 5 bars by default instead of 4.

It still works correctly if there is a Time Selection (size of item = ts) but if running the action with no time selection this is new/odd.

[Justin]

Originally Posted by ferropop

Not sure if this is related to all the MIDI stuff that has been happening, but the action "Insert new MIDI item..." is creating 5 bars by default instead of 4.

It still works correctly if there is a Time Selection (size of item = ts) but if running the action with no time selection this is new/odd.

thanks, fixing!

[deeb]

Originally Posted by skylar_battles

deeb, a bit confused on what you mean there. could you maybe explain a use case so I could better understand?

i ment this: