VP14/15 BUG - Paste Event Attributes wrongly adjusts Pan/Crop settings

NickHope wrote on 5/16/2017, 12:22 AM

If you copy an event that has Video FX on it, then paste event attributes onto an event of a different resolution, Vegas Pro 14 incorrectly creates a non-default Event Pan/Crop setting on the target event. It should not do so.

Example test procedure:

  1. New project
  2. Set project settings to HD 1080-24p (1920x1080, 23.976 fps)
  3. Media Generators > Checkerboard > Default > drag to timeline
  4. Add a video FX such as Sharpen or Color Curves
  5. Change Project Properties to QFHD 24p (3840x2160, 23.976 fps)
  6. Media Generators > Checkerboard > Default > drag to another part of the timeline
  7. Copy the first (1920x1080) event
  8. Right-click the new (3840x2160) event > Paste Event Attributes
  9. The Pan/Crop setting on the target event is adjusted to crop just the top left quarter of the image.
     

The problem also occurs with video media, and when copying from higher resolution to lower resolution, and if the Video FX is before Pan/Crop in the FX chain.

Tested in Vegas Pro 14 build 252.

There is no problem in VP10, 12 or 13.

I guess this bug may possibly have been introduced when this one was fixed.

Support request: [Ticket#2017051617003842]

Please feel free to confirm or add observations!

Comments

Grazie wrote on 5/16/2017, 1:35 AM

Nick, this is what I'm getting in B211:

What should I be aware of?

NickHope wrote on 5/16/2017, 2:20 AM

Thanks Grazie. Well if you followed the procedure to the letter and that's the target event after pasting then it looks like you don't have this issue.

NickHope wrote on 5/16/2017, 2:23 AM

I'm also seeing the issue in VMS Platinum build 122.

Quitter wrote on 5/16/2017, 2:29 AM

issue confirmed b252

Camcorder: Sony CX 520 VE
Hardware:   Acer NG-A717-72G-71YD, Win 11 , i7-8750 H, 16GB, GTX 1060 6GB, 250GB SSD, 1TB HDD
NLE:  Sony Vegas Pro 13.0 Build 453
            Vegas Pro 14.0 Build 270
            Vegas Pro 21.0 Build 300

 

Grazie wrote on 5/16/2017, 2:52 AM

Nick, please show me what you are seeing.

Quitter wrote on 5/16/2017, 2:59 AM

I'm not Nick, but here it is

Last changed by Quitter on 5/16/2017, 3:02 AM, changed a total of 1 times.

Camcorder: Sony CX 520 VE
Hardware:   Acer NG-A717-72G-71YD, Win 11 , i7-8750 H, 16GB, GTX 1060 6GB, 250GB SSD, 1TB HDD
NLE:  Sony Vegas Pro 13.0 Build 453
            Vegas Pro 14.0 Build 270
            Vegas Pro 21.0 Build 300

 

Grazie wrote on 5/16/2017, 3:10 AM

TU Q. Is this what you're seeing Nick?

NickHope wrote on 5/16/2017, 3:18 AM

TU Q. Is this what you're seeing Nick?

Yes

Thanks Quitter

Grazie wrote on 5/16/2017, 3:21 AM

I'm not getting anything like that. I'll REDO and confirm, but on the face of it the B211 doesn't. Could somebody install B211 to try and confirm/deny?

Marco. wrote on 5/16/2017, 4:51 AM

Following step 1 to 9 of your first post, I can confirm this behavior.

Pondering. In a technical sense this should be correct behavior as you just use the pan/crop setting of the copied event attributes. And technically the way it behaves in former versions is strange. There, if you copy the pan/crop property of an HD event to a QFHD event, the pan/crop property of the QFHD event will be 1920x1080, but it would not be affected this way.

Grazie wrote on 5/16/2017, 6:12 AM

Repeated Nick's steps within B211 and still don't get that Top Left Corner Preview.

 

Marco. wrote on 5/16/2017, 7:13 AM

That probably means it came with build 252.

Jam_One wrote on 5/16/2017, 7:58 AM

Affirmative VP14.252

Why someone may call it a "bug":
[my thought]
Because "Pan&Crop" is not a media's effect/attribute, it is event's one.
And all events - unlike media - do belong to the "project's jurisdiction".
[/my thought]

Last changed by Jam_One on 5/16/2017, 8:05 AM, changed a total of 1 times.

Win 7 Ultimate | Intel i7-4790K @ 4GHz | nVidia GTX 760 4GB * 2

SSD | 32 GB RAM | No Swap file | No Overclock | GPU-in-CPU OFF

t.A.T.u. F.o.R.e.V.e.R.!

 

Grazie wrote on 5/16/2017, 8:50 AM

That probably means it came with build 252.

Well, wasn't there a Build in between? Something hasty? Anyways I'm sticking with B211 for the foreseeable.

Grazie wrote on 5/16/2017, 3:14 PM

Woah, now that's curious.

Quitter wrote on 5/16/2017, 3:22 PM

Sorry Nick, but I cannot reproduce this.
Am I doing something wrong?

You are right.
If i drag the FX out of the window like you do, nothing happens.
If i use the the FX-icon of the event to add the FX, the problem appears

Camcorder: Sony CX 520 VE
Hardware:   Acer NG-A717-72G-71YD, Win 11 , i7-8750 H, 16GB, GTX 1060 6GB, 250GB SSD, 1TB HDD
NLE:  Sony Vegas Pro 13.0 Build 453
            Vegas Pro 14.0 Build 270
            Vegas Pro 21.0 Build 300

 

Quitter wrote on 5/16/2017, 3:37 PM

seems so

 

Camcorder: Sony CX 520 VE
Hardware:   Acer NG-A717-72G-71YD, Win 11 , i7-8750 H, 16GB, GTX 1060 6GB, 250GB SSD, 1TB HDD
NLE:  Sony Vegas Pro 13.0 Build 453
            Vegas Pro 14.0 Build 270
            Vegas Pro 21.0 Build 300

 

Grazie wrote on 5/16/2017, 3:53 PM

If i drag the FX out of the window like you do, nothing happens.
If i use the the FX-icon of the event to add the FX, the problem appears

Nope, not here. Using FX-icon of the event to add the FX, the problem does NOT appear.

Grazie wrote on 5/16/2017, 10:21 PM

So, to be clear Cornico, you found no issues with the 3 Builds? Correct?

Quitter wrote on 5/17/2017, 12:35 AM

I tested it with build 211, 244 and 252

With dragged FX from Video FX everywhere the same behaviour >>> nothing strange
With entering an Event FX 211 no problem and 244, 252 the by Nick reported issue.

So it came with build 244.

Camcorder: Sony CX 520 VE
Hardware:   Acer NG-A717-72G-71YD, Win 11 , i7-8750 H, 16GB, GTX 1060 6GB, 250GB SSD, 1TB HDD
NLE:  Sony Vegas Pro 13.0 Build 453
            Vegas Pro 14.0 Build 270
            Vegas Pro 21.0 Build 300

 

NickHope wrote on 5/17/2017, 2:31 AM
If i drag the FX out of the window like you do, nothing happens.

If i use the the FX-icon of the event to add the FX, the problem appears

Same here, but if I open the Event Pan/Crop window for the source event at any time before pasting event attributes then I still get the problem even if I drag the FX.

None of the changes in build 244 look like they are obviously related to this. It's a strange one.

Grazie wrote on 5/17/2017, 3:30 AM

Thanks Cornico. Evidenced Based Results.

Is it possible with these two builds that dragging ACROSS the graphics of the WORKSPACE will produce this aberration. Many years ago we'd had a similar issue with CONTROL DRAGGING.

Interesting thread.

3d87c4 wrote on 4/23/2018, 12:18 AM

Is there an easy way to fix the altered pan/crop setting on all the affected clips, or do you have to fix them one by one?

Del XPS 17 laptop

Processor    13th Gen Intel(R) Core(TM) i9-13900H   2.60 GHz
Installed RAM    32.0 GB (31.7 GB usable)
System type    64-bit operating system, x64-based processor
Pen and touch    Touch support with 10 touch points

Edition    Windows 11 Pro
Version    22H2
Installed on    ‎6/‎8/‎2023
OS build    22621.1848
Experience    Windows Feature Experience Pack 1000.22642.1000.0

NVIDIA GeForce RTX 4070 Laptop GPU
Driver Version: 31.0.15.2857
8GB memory
 

NickHope wrote on 4/23/2018, 1:56 AM

Is there an easy way to fix the altered pan/crop setting on all the affected clips, or do you have to fix them one by one?

@3d87c4 In VP15, fix one event's pan/crop, then copy it to clipboard, then select all the other target events > right click > Selectively paste event attributes > tick Video event pan/crop settings > OK