Dragging audio to the Timeline with the "Drag Audio Only" button should override Source Patching!

Sure thing.

I've tried again and again to explain the workflow issue at hand with provable facts and your response is that I'm being hostile and that none of my responses are of any value?  Why don't you give it a rest Neil?

You've made it clear that according to you, only what's logical to you is actually logical.

You use hostility throughout your responses.

So past your initial post, I do not find any of your posts of any additional interest or value.

And after several days, I am still the only person who has voted for your idea. I don't think your comments are helping to advance your suggestion.

Neil

What's puzzling to me is your refusal to recognize how your arguments don't make any sense.  The current way it works is illogical.  I've explained why at length.  You, nor anyone else, has provided a single valid argument in favour of the way it currently works.  Why defend an illogical workflow by insisting users would need a way to revert to it after it is fixed?

What could possibly be the benefit of preventing users from using the "Drag Audio Only" button when Source Patching for audio is turned off?  If an editor uses that button, isn't it because they WANT to drag the clip's audio to the Timleine?  Every single time?  Whether they remembered to turn on Source Patching for Audio first or not?  If you don't want to drag your clip's audio to the Timeline, simply don't use that button.  Simple!

Limiting the use of the "Drag Audio Only" button to when source patching is turned on is nothing more than a silly stumbling block in an editor's workflow, one that could easily be fixed without any downsides whatsoever to anyone.

@Rag and Bone, as they say, if you don't have anything of value to contribute, why bother writing in the first place? 😉

And that was me, of course ... 😉

Just one vote so far...just saying.

I'm not insisting on anything, nor challenging anyone else's thoughts or ideas. Nor demanding others merely submit passively to my ... thoughts.

I merely added what to me, is a sensible alternative, one that would make this more amenable to more users. And wouldn't hurt your proposal in any way. I see no basis nor logic for your assumption that your process would be 'easy' in code and any mod to it would be difficult. None whatsoever.

We are all welcome to assumptions. We also need allow others the same grace.

Your open hostility is ... unfortunate. Misplaced. And puzzling.

Neil

And why do you insist that users would need an option to revert to the current behaviour when it offers zero benefits and only disadvantages compared to what I suggest, giving much more work for the Pr team to program and adding complexity to Pr?

I challenged you to come up with a single benefit of the current way vs the fix I suggest.  You've failed to provide any.  Rather you seem to get a kick out of arguing for argument's sake.  As I said, the fix I'm suggesting isn't rocket science.  It's extremely simple to understand and self explanatory.

Tell me Neil, what do you get out of trolling on this site?

I have tested it. And used this for years.

Why you insist anyone who even accepts your suggestion, though with an added user option,  is basically an idiot, and can't possibly have tested this ... that I don't get.

Neil

It's just that it's annoying when people respond to a FR raising non-issues that don't apply or don't even make any sense, simply because they didn't understand the post before responding.

What would be the purpose of a toggle to permit it or not?  This would require a lot more programming effort on Adobe's part for zero benefits.  Would having a toggle to make the Spacebar serve as a play/stop shortcut or not be of any benefit to users?  It clearly wouldn't.  Nor would a toggle be of any benefit whatsoever in this case.

Bottom line, when raising issues with a FR, make sure you actually understand the FR first.  Otherwise the issues raised will most likely be incorrect, as was the case here.  I find it baffling since this FR is really simple to understand.  You can try it out for yourself!  Set Source Mapping to Video only, and add a bunch of clips from the Source Monitor to the Timeline, one by one, using drag-drop, or shortcuts for Insert or Overwrite.  Now, on the 10th clip, try dragging that clip's audio to your Timeline using the "Drag Only Audio" button.  Doesn't work, does it?  Why not?  Because that button wasn't programmed to work intelligently, that's why!  Why limit that button's use with Source Mapping when there is simply no advantage whatsoever in doing so?  All I'm asking is for the Pr team to make it intelligent.  You seem to be asking for a toggle so users can choose between:

1. Intelligent way (what I suggest)

2. Stupid way (the limited way it currently works, providing zero benefits to anyone)

Now why on Earth should Adobe fix something only to give users a toggle so that they can revert back to the old, stupid way it worked before?

BTW, before responding, please test it out for yourself so that you ACTUALLY understand the issue at hand first.  Only then is it possible to have an intelligent, productive conversation.