v5.60pre10 - October 4 2017

[schwa]

Originally Posted by Mercado_Negro

I don' think this is working correctly:

I don't like that I can't reproduce this. What timebase is the project and track in?

[edit] Aha, got it! Fixing, thanks.

[mawi]

Originally Posted by musicbynumbers

+ FX: fix ID collision in quick-add FX/FX chains menu [t=196760]

It seems the bug is fixed. Thanks!

[mlprod]

Originally Posted by mlprod

Not quite sure what this means?
When I send something to ch 3-4 (sidechain) to another track, when soling both I still cant hear the source track.

Sorry, now I get it. Yes this works now when doing alt solo on source track!
One more thing: Can you make the behaviour also work with the tracks are going directly to HW outs? It doesn not as of now.

[Luster]

Not sure if this is a bug or expected behaviour:
I have a folder F with track A and B within. From the folder track F a send goes to track C. This send now is muted and track C moved into the folder F. When I solo now the folder I only hear track C through folder but not the other tracks.

Of course, when the send would be reactivated we have a feedback loop - I am aware of that. When I delete the send then everything is fine.

Why I do such a move? Because track C was a hardware reverb which I now recorded and want to have in that folder together with the source sounds.

[nofish]

Could we have an option to switch between old and new solo send behaviour please ?
The old one was totally fine for me.

[Luster]

Originally Posted by nofish

Could we have an option to switch between old and new solo send behaviour please ?
The old one was totally fine for me.

Have to agree. When sending reverbs returns into other reverbs the solo behaviour is counter-intuitive.

[mpl]

Originally Posted by mccrabney

also MPL i'm seeing that your script for "Insert 1 measure long automation item for last touched parameter" is creating multiple stacked AIs for the same parameter.

It happened to me some pre`s ago. Pre10 seems ok here.

[dupont]

Originally Posted by mccrabney

also MPL i'm seeing that your script for "Insert 1 measure long automation item for last touched parameter" is creating multiple stacked AIs for the same parameter.

Working fine here on OSX.

[mawi]

I don't like the new solo behavior.

[musicbynumbers]

Just to balance things out.. I like the new so behaviour

But.. either make it optionally or maybe give us mouse modifiers for these things so we define how it should work or a few more solo options in a sub menu when right clicking the solo button?

It seems like it would be good to have all the behaviours available as they all seem to be useful in different situations.

[EpicSounds]

Can someone make a chart to explain the old vs new solo mode?

[Justin]

Originally Posted by EpicSounds

Can someone make a chart to explain the old vs new solo mode?

Suppose you have track A which sends to track B

With both tracks soloed-in-place:

Old behavior: hear A's master send, and A-via-B.
New behavior: do not hear A's master send, hear A-via-B.

The old behavior still exists if A is soloed in the non-in-place mode. You can also just solo A if you want to hear A's master send and A-via-B.

[Dimson]

Here is a test project, with the new behavior of the solo mode, I can not hear the control track (BD). I only hear the send of this track to the reverb bus. In this situation, I need to hear three tracks, BD, Loop and Rev BUSS. In version 5.52 all works correctly.

[Gianfini]

Originally Posted by Lunar Ladder

I've dreamt of one possible solution that I would personally like, but I realize it's not to everyone's liking from a GUI standpoint:

Automation items having the possibility of little "chase snap" icons at their start and end edges. Sort of like the pins that pin UI windows. If you click the icon active, chasing the edge will be dealt with if you seek in the empty space in between that edge and another AI (or project edge). Seek where any corresponding edge(s) haven't got the chase snap activated, don't chase. Then an option whether to default create AIs with that snap on or off. And when not chasing, an option would say whether to go to a baseline value or leave the value where the AIs leave them. (Ideally, even that is something I'd like to have per-item control over =), maybe in the item properties for that one, but the chasing is the big one.)

This way I could have both behaviors at the same time, when ever the exception to the default preference was suitable for a particular parameter

Very nice... if we enter the realm of AIs icons/edges menues then we could add edge icons with the possibility to shape the transition per edge/item (5ms, 10ms, and shape)

g

[Gianfini]

Originally Posted by Luster

Not sure if this is a bug or expected behaviour:
I have a folder F with track A and B within. From the folder track F a send goes to track C. This send now is muted and track C moved into the folder F. When I solo now the folder I only hear track C through folder but not the other tracks.

Of course, when the send would be reactivated we have a feedback loop - I am aware of that. When I delete the send then everything is fine.

Why I do such a move? Because track C was a hardware reverb which I now recorded and want to have in that folder together with the source sounds.

Best would be to forbid nested cross sending at all (so moving track C under F not possible at all until send is deleted)

g

[Luster]

Originally Posted by Gianfini

Best would be to forbid nested cross sending at all (so moving track C under F not possible at all until send is deleted)

Hmm. IMHO not good to forbid stuff - feedback isn't allowed anyway until you allow it in project settings. The deactivated send helps me to understand what I did when I dig the project months later out, you know.

[mccrabney]

Originally Posted by mpl

(regarding "Insert 1 measure long automation item for last touched parameter" is creating multiple stacked AIs for the same parameter.) ... It happened to me some pre`s ago. Pre10 seems ok here.

win10x64 here and it's happening on a newly created track. happening for FX param, volume, etc. behavior is different when there's a time selection -- top AI fills time selection, while your AI is 1 measure as expected. i think this is happening because it overlaps with some Cockos functionality.

so, schwa, i turn to possibly using WRITE mode to enter AIs and i encounter this possible workflow improvement.

let's say that playback is paused/stopped, and i'm using WRITE mode to create a new AI that is fitting the time selection. here's the current behavior, if i turn on WRITE mode for the track and begin moving the parameter:



edgepoints are created automatically, and the write point exists creating slopes between the AI endpoints.

my desired behavior -- EDIT perhaps by key modifier or something?? -- when playback is stopped and NO AI exists yet, entering a point via write mode would do this (Below). would be great if instead of entering/moving 1 point at cursor, it'd enter/move the AI edgepoints.



-------

lastly, i found this bug. if you use write mode to write in an AI, then delete the AI, and then try to enter it again using write mode, you can'd to it.

[Edgemeal]

Originally Posted by mccrabney

lastly, i found this bug. if you use write mode to write in an AI, then delete the AI, and then try to enter it again using write mode, you can'd to it.

I have these options as buttons on toolbar,

A) Options: Bypass underlying envelope outside of automation items
B) Options: Always create new automation items when writing automation and envelope is bypassed outside of automation items
C) Options: Always create new automation items when writing automation


I see same behavior when A or A & C are enabled, otherwise working when A & B enabled or A,B & C are enabled.

Win7/x64

[Justin]

Originally Posted by Dimson

Here is a test project, with the new behavior of the solo mode, I can not hear the control track (BD). I only hear the send of this track to the reverb bus. In this situation, I need to hear three tracks, BD, Loop and Rev BUSS. In version 5.52 all works correctly.

Ahh, gotcha, because the BD is ducking the loop (which is also being soloed). OK let me think about this.

With the current code, you can alt+click solo the BD, which will cause you to hear it, but in that case you won't hear the Rev BUSS.

[kytdkut]

Originally Posted by Justin

Suppose you have track A which sends to track B

With both tracks soloed-in-place:

Old behavior: hear A's master send, and A-via-B.
New behavior: do not hear A's master send, hear A-via-B.

The old behavior still exists if A is soloed in the non-in-place mode. You can also just solo A if you want to hear A's master send and A-via-B.

With the new solo behavior, if you solo a A and B, and A is also sending to tracks C and D you can also hear A-via-C and A-via-D. I find this a bit counterintuitive; if I wanted to hear A-via-B|C|D I would solo each one of those receiving tracks. Maybe I'm just not getting things right?

[vinx]

The old solo behaviour, which is perfect in its way (you hear whatever you're soloing), should be the default one IMHO.
The new "source" mode is really cool but it does not suit everybody because reaper is so much flexible in its routing, and you can do anything with a track (audio, midi, multichannel, sidechain...).

[Luster]

Originally Posted by vinx

The old solo behaviour, which is perfect in its way (you hear whatever you're soloing), should be the default one IMHO.
The new "source" mode is really cool but it does not suit everybody because reaper is so much flexible in its routing, and you can do anything with a track (audio, midi, multichannel, sidechain...).

This sums it up for me. When you solo a track you expect to hear at least the track. Now you have to think why you don't hear the track.

[EcBaPr]

another vote here for keeping it simple as the default always.. speed and ease of workflow helps creativity.

[Gianfini]

Originally Posted by Luster

Dear devs,

might it be possible to implement a bit more variance in the visual possibilities how solo states are presented for every track? I am referring to this FR:
https://forum.cockos.com/showthread.php?t=191234
Just asking because you are now working in this area...
Thanks for consideration.

And this as well


https://forum.cockos.com/showthread.php?t=189706

G

[Gianfini]

Originally Posted by kytdkut

With the new solo behavior, if you solo a A and B, and A is also sending to tracks C and D you can also hear A-via-C and A-via-D. I find this a bit counterintuitive; if I wanted to hear A-via-B|C|D I would solo each one of those receiving tracks. Maybe I'm just not getting things right?

This happened also before, it's not new. Go check in 5.40 or previous

The new behavior is that if you solo A and C and A is sending to C (and C is receiving from other tracks too) you onky hear A through C and not A directly and no other receives through C. Before this whas not possible at all, it's a new feature

Maybe it's triggered in a non super intuitive mode? But it's something possible now that was not possible before

I agree that more visual options on solo button would much improve the understanding of this (e.g. Think of solo button of sending track flashing when in his mode)

G