I can't open a coloring pack in a .veg file

bananadineapple wrote on 5/25/2018, 12:47 AM

So I'm using Sony Vegas 14. I want to download and used pre-made coloring packs I found on youtube. So I tried every instruction to save the coloring packs to the plugins, or copy paste video attributes, but the error "An error occurred while loading plugin. The specified plug-ins are not installed to this system"

Can someone please help me on what to do?

Comments

Grazie wrote on 5/25/2018, 1:47 AM

Can someone please help me on what to do?

@bananadineapple : Sure. You need to supply more information:

1] What Website?

2] Is the Plugin it meant for Vegas Pro?

3] Is it an OFX?

 

bananadineapple wrote on 5/25/2018, 5:27 AM

@Grazie 

1) I got it from Youtube, its one of those coloring packs that is already in a .veg file

2) I think so because its a .veg file that has already a coloring pre-made (i'll send a sample: http://www.mediafire.com/file/jh86nrcvwomj94c/thesongcontinues+coloring+1.veg)

3) It's supposed to have preset OFXs already when you open it

Grazie wrote on 5/25/2018, 5:53 AM

1) I got it from Youtube, its one of those coloring packs that is already in a .veg file

Really? Never heard of those before. Have you got a YT Link I can look at?

2) I think so because its a .veg file that has already a coloring pre-made (i'll send a sample: http://www.mediafire.com/file/jh86nrcvwomj94c/thesongcontinues+coloring+1.veg)

Well, the Plugin's s/w may need to have been installed. I'd need to know more and to hear from somebody here that's had success.

3) It's supposed to have preset OFXs already when you open it

Who says? Are there any specs or instructions with it?

It doesn't sound good so far.

Last changed by Grazie on 5/25/2018, 5:53 AM, changed a total of 1 times.

Grazie

PC 10 64-bit 64gb * Intel Core i9 10900X s2066 * EVGA RTX 3080 XC3 Ultra 10GB - Studio Driver 551.23 * 4x16G CorsVengLPX DDR4 2666C16 * Asus TUF X299 MK 2


Cameras: Canon XF300 + PowerShot SX60HS Bridge

NickHope wrote on 5/25/2018, 6:37 AM

The last time this happened, it turned out the user hadn't noticed the requirement for a specific third party plugin, mentioned in the YouTube video description.