v7.0pre10 - August 18 2023

[mschnell]

Originally Posted by inthevoid

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

Yep. it adds a "Reaper Loopback 1" device.

It looks very different from your picture, but supposedly it's the same....

Yep I see that I can route midi from one Tab to another. GREAT !

(So my plugin is useful for e.g. routing Midi to the Monitor FX chain )

[vseanv]

Ok I got home from work and went to test out some things with the Media Item lanes comping features... sorry if this has already been reported but I have found that Auto Punch selected Items and time selection auto-punch to be not working with the current system in Pre 10

Auto Punch selected Items on a comp lane seems to work but the wave is not added as a take, and the selected item is automatically unselected afterwards... seen here



and Auto-punch time selection just doesn't seem to work at all when a track has fixed item lanes enabled. It just records as if we are in normal mode.

[vseanv]

And just for documentation sake, here is the behaviour I'm getting when I record past 64 takes in pre 10... funnily enough when I was recording the lice cap it didn't crash... it will usually crash when this happens...

[vseanv]

lastly... time selection auto-punch is also bugging out a bit when comping is turned off and you're trying to punch in on a comp section.. for some reason, sometimes but not others the recording continues into the next item beyond the time selection...

[machinesworking]

Originally Posted by 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) ......
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.

OK so first off, I've used Digital Performer forever, and this looks a lot like DP's Chunks and V-racks feature. A project is hosting VSTi's etc. and other projects can access those VSTs etc. The caveat in DP is that the V-Rack (virtual rack) doesn't allow for host/plugin automation, only MIDI notes and CC's etc.

So far being a noob at projects in general I haven't been able to play a MIDI track sending to Loopback 1 and get it to trigger an instance of Diva on a separate Project tab. I'm sure it will happen any pointers are welcome.

The real question though is did Reaper break the wall? Are you able to use plug in automation in the MIDI subproject? As metioned above the biggest limitation with DPs V-Racks are that the MIDI project can't write plug in automation.

[Gass n Klang]

can we have an option to collapse lanes automatically when turning off comping (and vice versa)?

[Gass n Klang]

bug/inconsistency:

some child-tracks (in fixed lane mode) with a parent in one razor edit group. razor editing the child-tracks affects only the lane youre editing in all child-tracks. razor editing the parent affects all lanes of all child tracks.

Shouldn't it affect only the "active" comp lane?

[Gass n Klang]

I don't understand, why we have specific comp lanes because you already can comp to any lane. This overcomplicates the system somewhat I think.

Why not just drop comp lanes (as a specific lane with a specific name), allow comping to any lane as is (but just give any lane a number)?

[schwa]

There is no difference between lane types. If a lane is created by a comping action, it is automatically named something like 'C1', but as you note, you can comp to any lane.

Because comping actions usually create a lane at the top of the track, another option would be to not name the lane at all, but I'm not sure that would be more useful.

[schwa]

Originally Posted by vseanv

Auto Punch selected Items on a comp lane seems to work but the wave is not added as a take, and the selected item is automatically unselected afterwards

This is a little bit of an odd situation, recording into an active comping lane. I suppose what should happen is the recording should happen and force any comp areas that get overwritten to go out of sync.

[schwa]

Originally Posted by vseanv

Auto-punch time selection just doesn't seem to work at all when a track has fixed item lanes enabled

If you are recording into a specific lane, it should work as expected. If you are actively comping, then the entire new recording should be added as a new lane, but only the time selection will be copied to the comping lane. If you are not recording into a specific lane or actively comping, we can change it so the auto-punch works as expected.

[mschnell]

Originally Posted by Gass n Klang

can we have an option to collapse lanes automatically when turning off comping (and vice versa)?

What exactly does "turn off comping" do ?

[mschnell]

Originally Posted by schwa

There is no difference between lane types. If a lane is created by a comping action, it is automatically named something like 'C1', but as you note, you can comp to any lane.

Because comping actions usually create a lane at the top of the track, another option would be to not name the lane at all, but I'm not sure that would be more useful.

There are slight inconsistencies when using a project as a template, as the lane names are preserved even for deleted lanes and reappear when lanes are created, which is decently unexpected. (Supposedly this also happens when deleting a renamed lane and having it be created afterwards.

[mschnell]

Originally Posted by schwa

There is no difference between lane types.

And using a comp line as a comp source seems to work as expected, recreating the snippets.

[vseanv]

Originally Posted by schwa

There is no difference between lane types. If a lane is created by a comping action, it is automatically named something like 'C1', but as you note, you can comp to any lane.

Because comping actions usually create a lane at the top of the track, another option would be to not name the lane at all, but I'm not sure that would be more useful.

it would not...autonaming to C1 is highly useful.

[DancingJedi]

How in the world do you use that midi loopback feature!!!? That sounds amazing! Does it work for hardware? Does this mean we no longer have to render subprojects!?

[inthevoid]

Originally Posted by DancingJedi

How in the world do you use that midi loopback feature!!!? That sounds amazing! Does it work for hardware? Does this mean we no longer have to render subprojects!?

Yes, you can send MIDI from subprojects to say, a master project (and then have the audio loop back into the subproject if you want). Truly game changing stuff!

Only drawback is you can't then render the subproject with any audio that comes back without first printing it into the subproject (as far as I'm aware, please do correct me if I'm wrong!)

[mschnell]

Originally Posted by inthevoid

Yes, you can send MIDI from subprojects to say, a master project (and then have the audio loop back into the subproject if you want). Truly game changing stuff!

Only drawback is you can't then render the subproject with any audio that comes back without first printing it into the subproject (as far as I'm aware, please do correct me if I'm wrong!)

That means that such a Midi stream is handled completely different from an audio stream between the same source and destination ?

That is weird and not along the lines of how Reaper is supposed to work. ?!?!?!?

[DancingJedi]

What are the directions to even trying this out!? I know it's just a pre-release (and the manual for Version 7 will explain it all when the time comes) but I want to test this out immediately!

[jinotsuh]

.
.
.
.