VEGAS POST Suites Cant Import VE into VP

alifftudm95 wrote on 11/16/2020, 12:24 PM

Just why? VEGAS Pro cant import VEGAS Effects project.

Last changed by alifftudm95

PC DEKSTOP

CPU: Ryzen 5 3600 X

GPU: RTX2060 6GB

RAM: 32GB 3200MHZ

Storage: 480GB SSD & 1TB HDD

Monitor: BenQ PD2700U 4K HDR

 

LAPTOP

Dell Inspiron 15 7577 4K 8Bit Screen

CPU: Intel i7 7700HQ

GPU: GTX 1060 6GB Max-Q

RAM: 16GB RAM

Storage: 128GB SSD & 1TB HDD

 

 

Comments

alifftudm95 wrote on 11/16/2020, 2:36 PM

Make sure there is a "VegasEffects.fio2007-config" in your VP install directory like "C:\Program Files\VEGAS\VEGAS Pro 18.0" before you launch VP.

I have it here tho

Last changed by alifftudm95 on 11/16/2020, 2:36 PM, changed a total of 1 times.

PC DEKSTOP

CPU: Ryzen 5 3600 X

GPU: RTX2060 6GB

RAM: 32GB 3200MHZ

Storage: 480GB SSD & 1TB HDD

Monitor: BenQ PD2700U 4K HDR

 

LAPTOP

Dell Inspiron 15 7577 4K 8Bit Screen

CPU: Intel i7 7700HQ

GPU: GTX 1060 6GB Max-Q

RAM: 16GB RAM

Storage: 128GB SSD & 1TB HDD

 

 

lan-mLMC wrote on 11/16/2020, 3:50 PM

Open "VegasEffects.fio2007-config" with notepad. You will see something like:

"[FileIO Plug-Ins]
VegasEffectsFileIO=C:\Program Files\VEGAS\VEGAS Effects\VegasEffectsFileIOPlugin.dll
[VegasEffectsFileIO]
Reader={0165FD16-2597-4680-87E9-720A5CCFAC63}
{0165FD16-2597-4680-87E9-720A5CCFAC63}=1
"

You need to make sure there is a "VegasEffectsFileIOPlugin.dll" in the path above in your computer, for example mine is "C:\Program Files\VEGAS\VEGAS Effects\". If not, you should change the path above to right path of your "VegasEffectsFileIOPlugin.dll".

After that, you are supposed to import ".vegfx" correctly. Meanwhile, you will find a "VegasEffectsServer.exe" PID in task manager near "vegas180.exe". This "VegasEffectsServer.exe" means the feature importing ".vegfx" is functioning.

alifftudm95 wrote on 11/17/2020, 3:54 AM

Open "VegasEffects.fio2007-config" with notepad. You will see something like:

"[FileIO Plug-Ins]
VegasEffectsFileIO=C:\Program Files\VEGAS\VEGAS Effects\VegasEffectsFileIOPlugin.dll
[VegasEffectsFileIO]
Reader={0165FD16-2597-4680-87E9-720A5CCFAC63}
{0165FD16-2597-4680-87E9-720A5CCFAC63}=1
"

You need to make sure there is a "VegasEffectsFileIOPlugin.dll" in the path above in your computer, for example mine is "C:\Program Files\VEGAS\VEGAS Effects\". If not, you should change the path above to right path of your "VegasEffectsFileIOPlugin.dll".

After that, you are supposed to import ".vegfx" correctly. Meanwhile, you will find a "VegasEffectsServer.exe" PID in task manager near "vegas180.exe". This "VegasEffectsServer.exe" means the feature importing ".vegfx" is functioning.

Mine says

[FileIO Plug-Ins]
VegasEffectsFileIO=C:\Program Files\FXHOME\VEGAS Effects\VegasEffectsFileIOPlugin.dll
[VegasEffectsFileIO]
Reader={0165FD16-2597-4680-87E9-720A5CCFAC63}
{0165FD16-2597-4680-87E9-720A5CCFAC63}=1
 

And the "VegasEffectsFileIOPlugin.dll" is located at C:\Program Files\FXHOME\VEGAS Effects\VegasEffectsFileIOPlugin.dll

 

All of this in correct path, yet I cant import VE file into VP, why?

PC DEKSTOP

CPU: Ryzen 5 3600 X

GPU: RTX2060 6GB

RAM: 32GB 3200MHZ

Storage: 480GB SSD & 1TB HDD

Monitor: BenQ PD2700U 4K HDR

 

LAPTOP

Dell Inspiron 15 7577 4K 8Bit Screen

CPU: Intel i7 7700HQ

GPU: GTX 1060 6GB Max-Q

RAM: 16GB RAM

Storage: 128GB SSD & 1TB HDD

 

 

alifftudm95 wrote on 11/17/2020, 7:04 AM

I suggest you should re-install VEGAS Effects.

Been there & done that. Still the same.

But to make things more interesting, other clips/projects I can send the media to VE with no problem.

 

It only specifically bug on this clip. Here a download link of the video I shot couple months ago. Its the same clip where VEGAS Pro displayed VE project missing on my previous project.

https://drive.google.com/file/d/1kLml59beM84fqWFt1Mop2JIyybkBn6MQ/view?usp=sharing

PC DEKSTOP

CPU: Ryzen 5 3600 X

GPU: RTX2060 6GB

RAM: 32GB 3200MHZ

Storage: 480GB SSD & 1TB HDD

Monitor: BenQ PD2700U 4K HDR

 

LAPTOP

Dell Inspiron 15 7577 4K 8Bit Screen

CPU: Intel i7 7700HQ

GPU: GTX 1060 6GB Max-Q

RAM: 16GB RAM

Storage: 128GB SSD & 1TB HDD

 

 

set wrote on 11/17/2020, 8:35 AM

Successful without trouble...

Put the C0019 clip to VP18, then right click > Edit in VEGAS Effects. No trouble at all.

 

alifftudm95 wrote on 11/17/2020, 8:39 AM

Successful without trouble...

Put the C0019 clip to VP18, then right click > Edit in VEGAS Effects. No trouble at all.

 

That is weird. I can't have this media sitting in VE, otherwise VP wont import at all.

PC DEKSTOP

CPU: Ryzen 5 3600 X

GPU: RTX2060 6GB

RAM: 32GB 3200MHZ

Storage: 480GB SSD & 1TB HDD

Monitor: BenQ PD2700U 4K HDR

 

LAPTOP

Dell Inspiron 15 7577 4K 8Bit Screen

CPU: Intel i7 7700HQ

GPU: GTX 1060 6GB Max-Q

RAM: 16GB RAM

Storage: 128GB SSD & 1TB HDD

 

 

set wrote on 11/17/2020, 8:41 AM

stupid way - try rename the media to something else...

or, render to Magix Intermediate, and see if now you can do send to VE.

alifftudm95 wrote on 11/17/2020, 8:42 AM

stupid way - try rename the media to something else...

or, render to Magix Intermediate, and see if now you can do send to VE.

Already rename the media, but Haven't tried transcoding it.

PC DEKSTOP

CPU: Ryzen 5 3600 X

GPU: RTX2060 6GB

RAM: 32GB 3200MHZ

Storage: 480GB SSD & 1TB HDD

Monitor: BenQ PD2700U 4K HDR

 

LAPTOP

Dell Inspiron 15 7577 4K 8Bit Screen

CPU: Intel i7 7700HQ

GPU: GTX 1060 6GB Max-Q

RAM: 16GB RAM

Storage: 128GB SSD & 1TB HDD

 

 

lan-mLMC wrote on 11/17/2020, 8:52 AM

Just a guess, you video is AVC+PCM (lossless audio format). This match (AVC+PCM) is not common so your VEGAS Effects can't import it, so your vegfx file is damaged.

You need use handbrake or Xmediarecode or something other to reserve the AVC and convert PCM to AAC;

Or you can install codecs pack such as k-lite to make VEGAS Effects import AVC+PCM. (I have installed k-lite, so your file in my VEGAS Effects function normally.)

set wrote on 11/17/2020, 9:12 AM

I try closing VP18, and rerun, even restart my system as well - in case the problem is in the next session... but no - no issues.

 

If AVC+PCM (XAVC-S/L format?) is the problem... how about other clips? is it the same codec?

alifftudm95 wrote on 11/17/2020, 9:18 AM

I know your problem, you video is AVC+PCM (lossless audio format). This match (AVC+PCM) is not common so your VEGAS Effects can't import it, so your vegfx file is damaged.

You need use handbrake or Xmediarecode or something other to reserve the AVC and convert PCM to AAC;

Or you can install codecs pack such as k-lite to make VEGAS Effects import AVC+PCM. (I have installed k-lite, so your file in my VEGAS Effects function normally.)

That's funny, cause @set able to send the clip to VE with no problem.

All of the media was shot on 1 same camera Sony a6500. The media vary between 4K & FHD with a mixture frame rates of 25,50 & 100FPS (PAL Format)

 

PC DEKSTOP

CPU: Ryzen 5 3600 X

GPU: RTX2060 6GB

RAM: 32GB 3200MHZ

Storage: 480GB SSD & 1TB HDD

Monitor: BenQ PD2700U 4K HDR

 

LAPTOP

Dell Inspiron 15 7577 4K 8Bit Screen

CPU: Intel i7 7700HQ

GPU: GTX 1060 6GB Max-Q

RAM: 16GB RAM

Storage: 128GB SSD & 1TB HDD