The Border Plugin (still) doesn't work correctly since version 11 on

crazeemix wrote on 8/29/2017, 11:08 AM

Hi guys!

Some of you may be aware of this. We've been talking on other forums forever but only a few people need this plugin to do this specific task so only a few know that it doesn't work the way it used to do (until version 10) when you crop an area in a non-standard shape (for instance a square in a 16:9 video).

I'll try to make it short:

- Import a video or a photo into the timeline;

- Go to Event Pan/Crop;

- Uncheck "Lock Aspect Ratio";

- Crop the video as a square;

- Apply the border plugin to this media;

- Select, for instance, the type Solid at 0,010;

- And here's what doesn't work. Until Vegas 10 (included) the border was following the square shape perfectly. Since Vegas 11 (and now even with the latest Vegas 15!), the border doesn't apply to the selected area but to the full rectangle.

Here's everything in pictures:

VEGAS PRO 10 (working): http://imgur.com/a/ANp52

VEGAS PRO 11 to 15 (not working): http://imgur.com/a/hLhYL

And if you want to try it out yourself, here's the project:

https://www.dropbox.com/s/3vn4uk5bhrg4fo1/test.zip?dl=0

There's no workaround and it should NOT be a workaround. It should work the way it worked until version 10 (with no tricks, just working!) because there's people using it as an important part of the job.

I contacted Magix more than once. First they didn't reply. After a while they said "try this workaround" but nothing, it doesn't work and then they said that it's fine and that it works...YES, SURE.

It's a shame because for this little, tiny plugin, I'm still stuck at Vegas Pro 10. But I can't move one, because that little plugin is essential with the work that I do. Not a huge deal because Vegas 10 works solid, but it's time to upgrade to enjoy the (few) new features and Magix doesn't want my money :/

Comments

crazeemix wrote on 8/29/2017, 11:41 AM

Even if you put the border plugin first in the chain, it doesn't solve the problem.

MAGIX: is it too difficult to make it work like it used to do back in the days?

Former user wrote on 8/29/2017, 11:44 AM

Unless I am misunderstanding your process, it seems to work in Version 12.

crazeemix wrote on 8/29/2017, 12:00 PM

Unless I am misunderstanding your process, it seems to work in Version 12.

It seems it works the way you're doing it...BUT, select a part of the video, for instance just the face of the dog.

The thing is, it doesn't work when you CROP something (you went OUT with your selecion, not INSIDE the video, I hope it does make sense). If you don't want to do everything from start again, just download my project and open it with Vegas 12.

The same project just works when opened with Vegas 10 and above. But not with Vegas 11 and below.

Former user wrote on 8/29/2017, 12:03 PM

Yeah, I see what you are seeing. If I actually try to CROP as opposed to RESIZE, then the border does wonky things. And it is not consistent so it is definitely a bug.

crazeemix wrote on 8/29/2017, 12:09 PM

Yeah, I see what you are seeing. If I actually try to CROP as opposed to RESIZE, then the border does wonky things. And it is not consistent so it is definitely a bug.

Yeah, finally the thing is clear now (thank you for your help!).

Is it so impossible for Magix to fix it? I don't get it 😑

crazeemix wrote on 8/30/2017, 8:26 AM

Am I the only user who needs this plugin to work?

How can I ask (again) Magix to fix this, since it is clear now that it is a bug?

NickHope wrote on 8/30/2017, 9:23 AM

How can I ask (again) Magix to fix this, since it is clear now that it is a bug?

By submitting a support request at https://support2.magix.com/customer/en/vegas/form , including as much detailed information about the problem as you can. Be sure to include a link to this post. You may need to wait for an email response before you can add some attachments such as the screengrabs.

Former user wrote on 8/30/2017, 10:42 AM

This is what happens when you use the CROP with border rather than the RESIZE option.

crazeemix wrote on 8/30/2017, 1:33 PM

While in Vegas Pro 10 (and before) it was working perfectly, like this:

crazeemix wrote on 12/2/2017, 11:39 AM

Hi guys, how's it going?

So, after this post was published in August, I opened a ticket and sent the problem to Magix.

After a while they replied and said that the thing was escalated to the developer and QA teams and that it will be resolved in a future application update.

Now, I waited for the 1st update and nothing. Waited for the 2nd one, now out, and still nothing.

Do you think they can make it before V16 is out? I can't wait to upgrade to V15 but it seems that Magix don't want my money at all...

john_dennis wrote on 12/2/2017, 1:42 PM

I have Vegas Pro 9-13 on an old machine so I opened your project in each of the final versions. (The project would not open in Vegas Pro 9 since you apparently uploaded a Vegas Pro 10 project.)

Vegas Pro 10

Vegas Pro 11

Vegas Pro 12

Vegas Pro 13-453

Vegas Pro 13-453 appears to work on this machine. I'll look into it more on another machine.

john_dennis wrote on 12/2/2017, 1:51 PM

On my main machine (X99, 6850, Windows 7, RX480) this was how your project opened.

It appeared to work properly on my (3770k, Windows 7, intel HD4000 video)

I suspect interaction of hardware, video driver, ad nausea. We could use other workstation configuration results to develop a trend.

I used to work at the foot of the Tetons every summer. It wouldn't hurt my feelings if I could be buried there. Or, just feed me to the wolves that are back in the area. If I lived there year 'round, I'd never get anything done, but what me worry?

matthias-krutz wrote on 12/2/2017, 2:02 PM

And this are my results in VP15.

With AMD R9 380 GPU

and the same with CPU

john_dennis wrote on 12/2/2017, 2:22 PM

Vegas Pro 11 GPU Off

Vegas Pro 12 GPU Off

Vegas Pro 13 GPU was off in the first instance. That's why it worked.

X99-AII GPU Off

3770k, Windows 7, intel HD4000 video GPU was off in the first test. That's why it worked.

john_dennis wrote on 12/2/2017, 3:41 PM

"There's no workaround and it should NOT be a workaround."

There is a workaround. If you create a project with the pixel dimensions that you want for your pictures or video, apply the border and nest that project in your main project, it will work no matter the state of the video acceleration.

Sample Project

There shouldn't be a requirement for a workaround. I just happen to use this type of nesting more than sane humans should.

[Parenthetical Comment]

I've learned that dropbox.com no longer wants my (zero-revenue) business. They've changed the interface and/or backend to the point that I am unable to share a link in spite of having done it successfully for years and years. The longer I live, the more tired I get of learning the same stuff over and over again. After all, has the violin changed as much as dropbox.com in the last 300 years? And yet, some people still seem to be able to use one to make music.

[/Parenthetical Comment]

NickHope wrote on 12/2/2017, 11:16 PM

I get this problem in VP12-15 when GPU acceleration is ON (AMD HD 6970). No problem when it's OFF. I added it to the known issues post.

crazeemix wrote on 1/15/2018, 3:38 AM

I get this problem in VP12-15 when GPU acceleration is ON (AMD HD 6970). No problem when it's OFF. I added it to the known issues post.

EXACTLY! Thank you, that was the problem starting with version 11 indeed (which introduced the GPU acceleration..) 😎

I just tried to disable GPU acceleration in VP13 (and in VP15 demo) and voilà...it now works correctly.

Please Magix, can you fix this thing asap? It's a waste not to take advantage of the GPU.

Thanks everyone on this post for the help anyway...really appreciate it!

3POINT wrote on 1/16/2018, 2:57 AM

Better use Trackmotion 2D Glow (with Blur set to 0,0%) to create a border around every object on the timeline. Advantage also, that object can have any shape.

john_dennis wrote on 1/16/2018, 11:18 AM

"Better use Trackmotion 2D Glow (with Blur set to 0,0%)"

It worked for me with GPU acceleration on. Thank you for adding an arrow to my quiver.

3POINT wrote on 1/16/2018, 2:00 PM

John, I'm a Dutchman and not familiar with the phrase "adding an arrow to my quiver". Can you explain?

john_dennis wrote on 1/16/2018, 6:12 PM

If I was a subsistance hunter using a bow and arrow to feed my family, I would prepare as many arrows as I could before I left camp to hunt the wild beast. Crouching in the tall grass with the beast within sight, I would reach over my shoulder, take an arrow from my quiver (a holder for my arrows that I had made) and fire the arrow deep into the heart of the beast. If my first shot didn’t take my prey down, I’d be glad that 3Point made one for me as I reached for another arrow to take another shot while running after the wounded beast.

vkmast wrote on 1/16/2018, 6:28 PM

That's the most eloquent explanation I've read so far on this. Thanks john_d 😎

walter-i. wrote on 1/17/2018, 2:55 AM

If I was a subsistance hunter using a bow and arrow to feed my family, I would prepare as many arrows as I could before I left camp to hunt the wild beast. Crouching in the tall grass with the beast within sight, I would reach over my shoulder, take an arrow from my quiver (a holder for my arrows that I had made) and fire the arrow deep into the heart of the beast. If my first shot didn’t take my prey down, I’d be glad that 3Point made one for me as I reached for another arrow to take another shot while running after the wounded beast.

Alone this statement made my day!

Thanks John!

john_dennis wrote on 1/17/2018, 10:15 AM

I’m glad you liked it. Lately, I’ve been thinking of tinkering less and writing more.