* Request
Could we get receives on tracks, similar to sends (Options: Show sends in TCP (when size permits) ?
* Benefit
It would help to control, for example, ALL the receives in an FX track, without having to adjust them on each track separately (or opening the routing window). This way it would be easier to balance what an FX insert gets as signal from various sources. Other uses would be balancing a headphone mix easier, right there in the TCP and MCP.
* Reason
Well, it would speed workflows and help quick mixing (for headphones). Currently there are scripts for this (that basically have a separate mixer), but a native function would be more than welcome in this case!
* Implementation Suggestion
Add the receives just the same way sends are being shown on both the TCP and MCP.
I wish you luck with it, but this a blank feature request. All it needs now is some people to reply '+1' to truly be the perfect misunderstanding soufflé.
I've no idea why you would want to see the receives. I'm sure you have a reason, but to anyone who doesn't correctly guess what it is, you're just left with 'add this thing to Reaper because I said please nicely'. You get points for being nice, but I imagine that's not what you want. Look at it from the other end of the telescope, say the big things instead of jumping to your assumed conclusion. So, for example:
As part of my workflow I do job 'x'.
The functionality Reaper has to help me with job 'x' is ....
That functionality is missing/sub-optimal/flawed because...
I believe the solution to all of this might be receives in the track panels, but perhaps there might be other solutions.
I wish you luck with it, but this a blank feature request. All it needs now is some people to reply '+1' to truly be the perfect misunderstanding soufflé.
I've no idea why you would want to see the receives. I'm sure you have a reason, but to anyone who doesn't correctly guess what it is, you're just left with 'add this thing to Reaper because I said please nicely'. You get points for being nice, but I imagine that's not what you want. Look at it from the other end of the telescope, say the big things instead of jumping to your assumed conclusion. So, for example:
As part of my workflow I do job 'x'.
The functionality Reaper has to help me with job 'x' is ....
That functionality is missing/sub-optimal/flawed because...
I believe the solution to all of this might be receives in the track panels, but perhaps there might be other solutions.
...that make sense?
But that's, like, hard, man! I thought I could just, you know, wing it!
You're right of course! I was going to post a proper FR in the morning but had so little time I thought most people would get what I mean anyway! But I'll edit the post in the evening to a proper one. Thanks WT!
HeDa's Track Inspector gives you "Returns"!
Robert
While these "additional mixers" will do the job, to me it seems rather counter-intuitive to make this any more complicated than it needs to be. But guess I'm alone on that front!
While these "additional mixers" will do the job, to me it seems rather counter-intuitive to make this any more complicated than it n
Needs to be. But guess I'm alone on that front!
If every FR got put into Reaper, then it would be Bloated like BNAB is!
HeDa has some good working scripts, so why keep adding things to reaper?
If you ever played with BNAB, then you would know where I'm comming from.
Showing sends and receives in TCP and MCP would be awesome. You’d need to link the visual, so when you adjust one, the other would automatically adjust.
I am used to it so it isn’t a huge deal, but I hate always having to look at the routing button to see if a track is receiving something, then you have to click on the button to see what/where.
This is my #2 reaper request behind adding an option to ignore mousewheel on faders in MCP (but not TCP). On that one, I can easily avoid clicking the faders in TCP but in MCP, scrolling tracks w/ mouse is impossible to not hit a fader. That is my #1.
This is my #2 reaper request behind adding an option to ignore mousewheel on faders in MCP (but not TCP). On that one, I can easily avoid clicking the faders in TCP but in MCP, scrolling tracks w/ mouse is impossible to not hit a fader. That is my #1.
HeDa Track Inspector will show all your Receives on a track.
As for the scrolling tracks in the MCP with your mouse wheel. Place your mouse curser on the track name and roll away, it works there.
I've had no problem with it hitting a fader.
HeDa Track Inspector will show all your Receives on a track.
As for the scrolling tracks in the MCP with your mouse wheel. Place your mouse curser on the track name and roll away, it works there.
I've had no problem with it hitting a fader.
Robert
Yep - I’ve played with HeDa Track Inspector. Still would be nice if Reaper did this natively as I prefer the regular Mixer strip as my Inspector.
On scrolling with mouse wheel in MCP, that is what I usually do. But it is down at the bottom or the screen and is not a lot of real estate. If I’m in MCP, I’m usually in the mid to upper part of the screen copying and pasting FX and checking routing.
Oh for the love of god yes please. +10^10
I just spent like the last hour trying to figure out how to do this. LOL but not lol but yeah lol.
No apologies for the FR necro.
And there is an official feature request. I tried to vote "Yes" but just end up with a blank page. Ditto if I try to comment. https://forum.cockos.com/project.php?issueid=5150
Curious if there is any other interest in this feature request.
If this request was implemented, I would never have to click on the routing button to see receives. I could just see all my sends and receives when scrolling in the MCP or TCP (when show sends/receives if space is available is checked).
I feel like not showing receives is tied to old, analog workflows, and doesn’t utilize the potential of a digital interface.
Add receives in TCP and MCP
Linear Mode
