osara
osara copied to clipboard
jcsteh
Is it possible to add a button in the track parameters that takes you to the send or receive FX chain list?
Hello, while mixing I feel the need to switch to the FX Chain of the track send or the Receive. In this way it would be possible to pass from the source track to the receiving track, from the receiving track to the source; to get to the desired FX Chain list faster.
For instance:
Parameter: Combo box 2 Reverb send volume
Value: progress cursor 0.00dB
0.00dB
FX Chain: 2 Reverb Button ALT + p
Filter: ALT + f
Close Button ALT + c
It should also include the Pan, Mute and Mono of all sends or Receives.
In my opinion this improves the work a lot and makes it faster. Greetings!
It might be possible - I'm not entirely sure - but the user experience for this feels very obscure to me. That is, it doesn't feel intuitive that you would access the FX chain for a send by going into the Track parameters dialog, locating a send parameter and then finding a button to open the FX chain. It's also very specific to send parameters, which would make it difficult to implement cleanly, even if it is possible.
@ScottChesworth , I'd appreciate your thoughts on this.
Hmm, it drifts a country mile wide of Reaper's mainstream UX. I can see how it'd be useful in situ though. A closer approximation of the mainstream UX (and even bigger productivity boost) would be the ability to have multiple parameter dialogs open, our spin on how sighted users can already float multiple FX windows on screen at the same time when needed. However, pretty sure that's been requested before and was deemed to be a boat load of work?
I might be way off base here but I can definitely see having easier access to send volumes, mutes, pans, etc would be super useful. The IO dialogue is not the friendliest and is a boat load of tabbing just to change a send value by 1 DB. Just my thoughts
On 6 Sep 2021, at 6:58 pm, ScottChesworth @.***> wrote:
Hmm, it drifts a country mile wide of Reaper's mainstream UX. I can see how it'd be useful in situ though. A closer approximation of the mainstream UX (and even bigger productivity boost) would be the ability to have multiple parameter dialogs open, our spin on how sighted users can already float multiple FX windows on screen at the same time when needed. However, pretty sure that's been requested before and was deemed to be a boat load of work?
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/jcsteh/osara/issues/569#issuecomment-913473593, or unsubscribe https://github.com/notifications/unsubscribe-auth/ASBXTTL23LUG3GP2ZQFBLP3UAR7DBANCNFSM5DOJEKJA.
I'm not sure multiple open Parameters dialogs have been discussed, at least not at length. I honestly don't know how you'd make a decent UX for that, in the same way that accessing multiple open FX chains isn't great for screen reader users. Happy to discuss if you have ideas on how the UX would work, though.
@mattymc2: You can already access send volumes/pans/mutes from the OSARA Track Parameters dialog.
I honestly don't know how you'd make a decent UX for that, in the same way that accessing multiple open FX chains isn't great for screen reader users.
My first thought was to mimic the UX of multiple tabs being open in a browser. However, if you don't mind lifting a design from another DAW wholesale, I remember loving how Pro Tools handled this. Two additional combo boxes, one to choose the track and another to choose which plug-in you want to display parameters for. In PT, the parameters updated as you chose options. When you changed your choice of track, the params of the first plug-in in its chain were populated by default. So essentially, only one instance of the parameters dialog, but the params of any plug-in on any track were quick to reach without leaving the dialog, locating the next track, reloading etc. I've no idea what that might do in terms of a performance hit, it was difficult to gauge that when I used to use PT because it was like wading through mud by default with VoiceOver turned on. My concern would be repopulating VST3's on the fly, they often have boat loads of generic params needlessly exposed. Does that give you any ideas, bring you out in a cold sweat, or do anything else?
I'm sure I'm missing something here, but I honestly don't follow how that would be more efficient. Pressing a key to get to the track list, selecting a track, pressing tab and then selecting an effect doesn't seem any less keystrokes than pressing escape, selecting a track, pressing p and then selecting an effect. If anything, the former might actually be more keystrokes.
Aaaa crap sorry man. Completely flaked on this! Shows how much I use that dialogue, really need too. Thanks for the heads
On 6 Sep 2021, at 7:07 pm, James Teh @.***> wrote:
@mattymc2 https://github.com/mattymc2: You can already access send volumes/pans/mutes from the OSARA Track Parameters dialog.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/jcsteh/osara/issues/569#issuecomment-913480196, or unsubscribe https://github.com/notifications/unsubscribe-auth/ASBXTTIHM72CIUT4FCLYKYDUASADRANCNFSM5DOJEKJA.
I honestly don't follow how that would be more efficient.
- A combo box control is first letter navigable, the track list isn't. At high track counts, that could be a pretty big advantage, particularly if the user is willing to adapt their track naming conventions. For example, track names could begin with characters that local verbosity settings don't report, enabling the user to jumped through categories.
- Track names could be reported without other contextual info, clarifying navigation through them for new users (or anyone who finds the amount of status reports distracting/overwhelming really).
- Focus. Staying inside one window and tackling a bunch of tasks related to parameters lessens the chances of distraction. This point may only serve to highlight my current frustrations around discipline, but I'm listing it anyway. :)
Ah, I didn't think of first letter nav. That would only work if you didn't have the track numbers before the track names in the combo box, though, which might be problematic for some users.
That said, this too feels pretty far off REAPER's mainstream UX. Also, it introduces a bunch of inconsistency into that dialog, both UX and code. Right now, the core UX and code is the same for all OSARA parameters dialogs. If we did this, it'd need extra controls when dealing with track FX, but those controls wouldn't exist when dealing with item parameters, take FX, etc.
I'm a no go on this unless we can come up with a better, more consistent UX.
I understand James, It could help speed up a mix a lot! I found a ReaPack action but it doesn't work well:
Script: Archie_Track; Show only send of selected track(s).lua
It seems to work but when you have very complex routing it's not good ...
Greetings!
Right now, the core UX and code is the same for all OSARA parameters dialogs. If we did this, it'd need extra controls when dealing with track FX, but those controls wouldn't exist when dealing with item parameters, take FX, etc. I'm a no go on this unless we can come up with a better, more consistent UX.
Fair points, I hadn't considered the code differences. Given how much of a headache keeping the parameters dialog stable cross platform has already been, it doesn't seem like the juice is worth the squeeze.
Hi everyone! If you disable all items from Reaper's "View" menu and read the pseudo status bar with NVDA, you will read the track selected with sends and receives in TCP. For instance:
HiHat; [recvs] Kick, Snare [sends] hi saturo
crash noise [recvs] Kick
vox group [sends] 6
saturated group [recvs] 18
When there are many sends or receives, it puts a number directly.
saturated group [recvs] 18
vox group [sends] 6
Could this help for our purpose? Reaper seems to already work by looking at the sends or receives of the selected track. I think it is a nice step forward in TCP. Perhaps now it is possible in the Track Parameters to be able to go to the send or receive track. Thank you!
Effectively Reaper gives the possibility to identify sends and receives. There is a script that displays the sends of the selected trace in the TCP: "Script: Archie_Track; Show only send of selected track(s).lua" If we could integrate this possibility into the track parameters the work in a very complex project would be a great achievement. It can happen that the routing is very complex and a button on the track parameters for the send and the Receive simplifies the management of the project.