Skip to main content
Known Participant
February 3, 2023
Open for Voting

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

  • February 3, 2023
  • 18 replies
  • 1651 views

When dragging audio to the Timeline from a clip in the source monitor with the "Drag Audio Only" button, that audio should get dragged to the Timeline regardless of whether or not the Timeline's source patching for audio is turned on or off!

 

What's the sense of preventing a user from using the "Drag Audio Only" function when audio source patching is turned off, when it's clear that what they want is to drag&drop their audio?!  This is counter intuitive and illogical from a USER'S point of view.  It might make sense from a programmer's POV, but who cares if it provides absolutely zero benefits to the user and only makes the interface more tedious to deal with?

 

Adobe, please make Pr more FLEXIBLE and INTELLIGENT! 

Thank you!

18 replies

R Neil Haugen
Legend
February 4, 2023

I simply don't understand the angst.

 

I've already said this would be fine in my opinion with a toggle to permit it or not.

Everyone's mileage always varies ...
Known Participant
February 3, 2023

What's worrysome is that both you and RobShultz are "Community Expert"s, and yet here you are both, unable to understand an extremely easy editing concept.

 

Part of avoiding being "disagreeable", as you say, is not posting nonsense before even understanding the concept at hand.  It's not that I disagree with you Neil, it's that your statements were flat out incorrect.

 

You wrote: "What is a path or workflow you might like, is not necessarily something someone else might like."  Please enlighten me... what is there that anyone could possibly not like about the Pr team fixing the workflow inconvenience I'd like them to fix?  If you can come up with a single valid argument, I'm all ears.  But as I wrote already, there are simply no downfalls to this workflow quirk being fixed.... unless the editor is a masochist who enjoys extra unnecessary steps in their workflow just because...

 

So much for the 'Expert' designation.  But I digress.  By all means guys, keep posting irrelevant arguments rather than contributing anything of value to the conversation.

 

 

 

 

Community Expert
February 3, 2023

You've posted your request in the right place. If the Adobe engineers agree they will take it up. Now may be a good time to sit back and have a decaf cup of coffee.

R Neil Haugen
Legend
February 3, 2023

What is a path or workflow you might like, is not necessarily something  someone else might like.

 

You are most welcome to post your ideas, please do so ... but also, you should expect others to comment on what they might like or not like. That's how a group process works.

 

I find the diversity of how humans do things always fascinating. But I don't get disagreeable with anyone simply because we disagree. I never expect anyone to agree to begin with.

 

Neil

Everyone's mileage always varies ...
Known Participant
February 3, 2023

You completely miss the point Neil.  Using the "Drag Audio Only" button in the Source Monitor is an EXTREMELY SPECIFIC action.  The chances of someone using that button by mistake instead of using a keyboard shortcut to Insert/Overwrite or instead of Drag & Droping a clip from the Source Monitor is next to ZERO.  THAT'S why that command should be respected every time a user uses it.  Period!  IF a user wants to drag just the AUDIO from the Source Monitor to their Timeline, why are they forced to turn on Audio Source Patching first if they want it OFF for all of the other clips they're sending to their Timeline using the other 3 methods mentioned?

 

As I said and repeat, the current way it works may seem logical from a programming standpoint, but it is 100% certifiably ILLOGICAL from a workflow standpoint.

 

Can't you see that?

 

You wrote as a defense of the current workflow: ...often include very detailed audio tracks, as in some place b-cast specs require a TON of specific tracks in specific order."  The point of my FR is that the "Drag Only Audio" button DOES work if ANY audio track is patched, but it DOESN'T work if they're all turned off.  So that comment is irrelevant.

You also wrote: "you would not want to allow a simple override by drag/drop. Especially, as it's quite possible with 'small' track heights, to accidentally drop on the wrong track."  Except that that is exactly the way dragging audio from the Source Monitor currently works.  Even if A1 is patched, the user is allowed to drag the audio to ANY audio track, whether it is enabled or not.  I have zero issues with that part of the workflow.  That makes this argument equally irrelevant.

 

As you can hopefully see now, your response is misguided, just as Rob's is.

 

My FR is to remove a tiny yet annoying bit of friction in Pr's workflow.  This would benefit every editor that encounters the same situation I come across from time to time, while also providing zero disadvantages to all other users.

R Neil Haugen
Legend
February 3, 2023

I don't think Rob's comment was at all unthinking. I thought he has a pretty good point.

 

For many colloborative uses, a senior/lead editor will set the sequences or oversee their setup. Which will often include very detailed audio tracks, as in some place b-cast specs require a TON of specific tracks in specific order.

 

In those situations, you would not want to allow a simple override by drag/drop. Especially, as it's quite possible with 'small' track heights, to accidentally drop on the wrong track. I've done that many times myself.

 

But ... allowing this as a user toggle choice, I can see.

 

I would not agree with this as a total override.

 

Neil

Everyone's mileage always varies ...
Known Participant
February 3, 2023

@RobShultz, if an editor uses the "Drag Audio Only" button, it's because they WANT to drag a clip's audio to the Timeline.  Period.  That's why that specific button should override Source track targeting.  Isn't that an easy enough concept to understand?  Now... If an editor drags the CLIP from the Source Monitor, then YES, it should respect Source track targeting.  But that is NOT what I'm talking about here.  Please at least try to understand the Feature Request before responding with a pointless response.

Community Expert
February 3, 2023

I can think of multiple users where the main editor turned off audio track patching to a channel so that a clipped wouldn't be dragged into that track. There may be good reasons why the feature you're mentioning is working as it was designed to work.