Could Magix develop a dynamic link between Vegas Pro and NukeX ?

Sound_James wrote on 1/28/2018, 4:03 PM

Adobe Premiere Pro has a dynamic link with After Effects.

Avid Media Composer has a dynamic link with Fusion.

 

Now, what would be very nice is if Magix could develop a dynamic link between Vegas Pro and NukeX from Foundry.

Is the Vegas Pro team already working on something like that ?

Comments

Musicvid wrote on 1/28/2018, 7:26 PM

Does Magix own Foundry as Adobe owns AE?

Sound_James wrote on 1/29/2018, 6:12 AM

No, but Magix and Foundry could negotiate with each other to develop a dynamic link between Vegas Pro and NukeX.

pringel wrote on 1/30/2018, 5:22 AM

i would also like to see a dynamic link between nuke and vegas pro.

that would be very handy. 😉

vkmast wrote on 1/30/2018, 5:24 AM

I would not want Vegas "nuked" though.

Musicvid wrote on 1/30/2018, 6:59 AM

The way it works is for foundry to develop a plugin.

Bundling would come later, if Magix liked the product and it didnt add too much cost to the product.

Licensure agreements are a bit trickier then you may know

Rainer wrote on 1/30/2018, 5:51 PM

Interesting. The native Fusion link is to Resolve, since BMD was open to developing a link with Avid, maybe they'd be interested in linking with Magix. As a casual user I don't see much performance difference between Nuke and Fusion (or Blender for that matter), the great advantage of Fusion over Nuke being the free version.

Brandigan wrote on 1/31/2018, 7:54 AM

Doesn't need to be much of a plugin. It seems the functionality is already there in some form, as I use it with Vegas and its Hitfilm integration. It uses the file extension to know which external program to launch through quite a simple .ini file.

I've edited that myself to get it to open different versions of Hitfilm (to retain version information, if I want to go back to it in the same version of Hitfilm later) and even simple old Notepad.exe, just to see how hard it was to direct it.

I can both send a clip to Hitfilm from within Vegas; which then opens up, I make changes, save the file, it updates on the Vegas timeline and carry on, or just drag finalised Hitfilm projects directly into Vegas and it'll render them like normal media.

The functionality is hooked in at the Hitfilm end. During Installation of Hitfilm (after Vegas) it just puts the correctly formatted .ini file in a Vegas folder and probably adds something to the registry to tell Vegas whether to look for the file based on its extension; or reject it outright and popup: "Vegas doesn't recognise this filetype etc."

Marco. wrote on 1/31/2018, 7:58 AM

The magic in this case is not to let HitFilm open the file which is used in the Vegas Pro timeline but to let Vegas Pro read the HitFilm project file including the fx applied in HitFilm.

Brandigan wrote on 1/31/2018, 10:21 AM

Actually you can do both. Open it first in Hitfilm and then drag it again into Vegas and it's also no problem. They share the files quite amicably.

Sound_James wrote on 1/31/2018, 2:01 PM

This topic is not about hitfilm.

It's about vegas pro and nuke.

Let's stay on that topic please.

Musicvid wrote on 1/31/2018, 3:16 PM

You see, none of us pigeons are connected with Magix or Fusion.

So people are trying to give you the closest advice they can; don't dismiss that out of hand, because you may actually need us at some point.

Sound_James wrote on 2/4/2018, 6:08 PM

You see, none of us pigeons are connected with Magix or Fusion.

So people are trying to give you the closest advice they can; don't dismiss that out of hand, because you may actually need us at some point.

This is not about Magix and Fusion.

It's about Vegas Pro and NukeX.

Musicvid wrote on 2/4/2018, 7:13 PM

Actually, i think it's off-topic.