Are .Veg Files able to be saved to use in other projects? Mine erase!

Comments

GJeffrey wrote on 9/18/2017, 10:57 PM

Do you still have 001.jpg on your destktop?

klever187 wrote on 9/18/2017, 11:21 PM

Ah, I'm starting to understand just what it is you're doing.

After producing AVI ALPHA Media, and thought this is too big, did you then rerender and produce that MP4? Is this how you ended up with that MP4?

Or have I got it wrong?

Hey guys no worries looks like this nested file problem i've been having is finally resolved :D I've been dragging it in to various projects and rendering a few times and it still works :p I've just been dragging into a mock project and it still worked everytime, but was hitting "save as" and giving it a name just in case. I don't know if it was because of auto save or what. But so far so good! Grazie, no I just created my logo then rendered straight to mp4 the chromo key it. But i'll be using the nested file thingy now for all my projects. Thanks guys!

Grazie wrote on 9/18/2017, 11:22 PM

OK, my "Fun With Alpha" VEG. Here it is sitting in a Desert, within my PARENT VEG!

Now, regard that whole VEG as a piece of media. Placed on the Timeline it is an EVENT. And as an EVENT it is fully editable as an EVENT. If you now wish to edit that VEG right click on the "Fun With Alpha" Veg Event and up comes the following:

Click on that, and that "Fun With Alpha" veg, EVENT, opens win a NEW instance of Vegas allow us to edit it! Stunning hey?! Save and close and your Parent VEG is automatically updated.

This sample lasts for 5 seconds and IF rendered would equate to 4.32mb. BUT as a Nested VEG it's only the PROXY that Vegas creates.

I truly implore you, start over and try this method - please.

PROS:

  • No humongously massive file sizes
  • Wanna change your mind? Editable if you go further down the Nesting Chain post MOV animation render.
  • HIGH fidelity transparency ALPHA

 

Last changed by Grazie on 9/18/2017, 11:37 PM, changed a total of 2 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

klever187 wrote on 9/18/2017, 11:40 PM

Thanks for the Thorough explanation Grazie! I just tried what you posted and i'm able to do it as well. And yeah it's WAAAYY better

Grazie wrote on 9/18/2017, 11:50 PM

And yeah it's WAAAYY better

So, have you been using the ANIMATION MOV render? - Yah not getting off that easily . . 😎

Grazie wrote on 9/19/2017, 12:09 AM

As a Postscript to all this, I noticed a "upward flicker" on the end of the first revolution. I went in back through the Nests and found I had clumsily introduced an additional Y-Axis increment - stoopid boy! Any-hoo, I set Phasers on stun and zapped that error with a Y=0 throughout; climbed back UP the Nest ladder; checked with the Parent and all is good.

This proves just how adaptable and valuable Nesting is.

klever187 wrote on 9/19/2017, 5:08 PM

 

So, have you been using the ANIMATION MOV render? - Yah not getting off that easily . . 😎

haha no I'm just using the "event" i created with the nested veg file :D. Is this the correct answer 🤓

Damian wrote on 5/6/2020, 4:01 PM

Ok i was afraid someone would say that because i did render my logo but then when i copy/pasted it in another project I made, the logo was spinning, but it lost its transparency, then I used chroma keyer and dragged it into the logo and placed that little drop to make it transparent and it kind of worked but not really. It became transparent but it had small trails of black around it while it would spin 😕

If you had a transparent background prior to render, then you will still have a transparent background. What render Template did you us and did you activate it back on the Timeline?I have other tips to offer, however let's confirm you've retained your transparency or ALPHA channel component. Leave the Chroma Keying alone.

So far, I don't believe all is lost.

Hi Grazie I have the issue that the nested title project is not transparent in the main project. What went wrong? Many thanks in advance. Damian

Damian wrote on 5/11/2020, 5:38 AM

Is there anyone else wo can hell me?

set wrote on 5/11/2020, 5:42 AM

Can you make screenshot of your 'sub'-project?

Setiawan Kartawidjaja
Bandung, West Java, Indonesia (UTC+7 Time Area)

Personal FB | Personal IG | Personal YT Channel
Chungs Video FB | Chungs Video IG | Chungs Video YT Channel
Personal Portfolios YouTube Playlist
Pond5 page: My Stock Footage of Bandung city

 

System 5-2021:
Processor: Intel(R) Core(TM) i7-10700 CPU @ 2.90GHz   2.90 GHz
Video Card1: Intel UHD Graphics 630 (Driver 31.0.101.2127 (Feb 1 2024 Release date))
Video Card2: NVIDIA GeForce RTX 3060 Ti 8GB GDDR6 (Driver Version 551.23 Studio Driver (Jan 24 2024 Release Date))
RAM: 32.0 GB
OS: Windows 10 Pro Version 22H2 OS Build 19045.3693
Drive OS: SSD 240GB
Drive Working: NVMe 1TB
Drive Storage: 4TB+2TB

 

System 2-2018:
ASUS ROG Strix Hero II GL504GM Gaming Laptop
Processor: Intel(R) Core(TM) i7 8750H CPU @2.20GHz 2.21 GHz
Video Card 1: Intel(R) UHD Graphics 630 (Driver 31.0.101.2111)
Video Card 2: NVIDIA GeForce GTX 1060 6GB GDDR5 VRAM (Driver Version 537.58)
RAM: 16GB
OS: Win11 Home 64-bit Version 22H2 OS Build 22621.2428
Storage: M.2 NVMe PCIe 256GB SSD & 2.5" 5400rpm 1TB SSHD

 

* I don't work for VEGAS Creative Software Team. I'm just Voluntary Moderator in this forum.

Damian wrote on 5/11/2020, 2:47 PM

1. Sub Project title

Title has alpha channel

2. If I add a footage below the title it works as it should be

3. If I work in the main project and add my title .veg project into it, the transparency is gone, even if I see the alpha channel

Marco. wrote on 5/11/2020, 4:22 PM

Es sollte keinen Grund geben, in diesem Projekt ein Gleitkomma-Pixelformat zu wählen. Versuche es mal mit einem 8-Bit-Projekt.

Try an 8 bit source project.

Damian wrote on 5/12/2020, 2:34 AM

8 bit does not solve it.

Marco. wrote on 5/12/2020, 3:03 AM

I can't repro the issue. Could you share your source project for download (via Dropbox, Google Drive or else)?

Damian wrote on 5/12/2020, 2:43 PM

I can't repro the issue. Could you share your source project for download (via Dropbox, Google Drive or else)?

 

I have sent you the link via PM.

Marco. wrote on 5/12/2020, 2:53 PM

Got it. Your projects work fine on my system, both the source project and the nested project with the transparent title animation.

You could try to disable GPU acceleration in both projects via "Optionen/Präferenzen/Video".

Damian wrote on 5/12/2020, 3:48 PM

Maybe I found it, I work with proxies. When I start a new project without proxies, it works, once proxies are created the background is black. Could you please confirm?

Marco. wrote on 5/12/2020, 3:59 PM

Not sure what you mean. Proxies of your video files or a proxy of the nested Vegas project file?

If you'd build a proxy of the nested project file you'd certainly lose the transparency because the proxy video format does not support alpha channel.

Damian wrote on 5/12/2020, 4:06 PM

When the option for proxies is enabled only in the main project vegas creates automatically proxies for the nested project file, therefore there is no chance to work with proxies.

Marco. wrote on 5/12/2020, 4:19 PM

Yes, but the auto-proxy mode only affect sizes from 4097x2161 up, while your source project is 3840x2160. So the auto-proxy mode should not affect it.

Did you modify that minimum size for proxy building in the internal preferences before? It does not build a proxy file on my system (with the default setting for proxy building still untouched).

Damian wrote on 5/12/2020, 4:30 PM

If I disable the proxy option for the main project, save it and manually delete the proxies for the created nested project from the windows folder, there is no black background, but this is not manageable.

Damian wrote on 5/12/2020, 4:33 PM

We need the option for disabling the proxies only for nested projects....

Damian wrote on 5/12/2020, 4:35 PM

Yes, but the auto-proxy mode only affect sizes from 4097x2161 up, while your source project is 3840x2160. So the auto-proxy mode should not affect it.

Did you modify that minimum size for proxy building in the internal preferences before? It does not build a proxy file on my system (with the default setting for proxy building still untouched).

Yeah I did modify to 3840x2160, but didn´t know that proxies are also created for nested projects... I was assuming that it only applied for video files.

Marco. wrote on 5/12/2020, 4:39 PM

One way around would be to manually start the proxy building via the window »Projektmedien«.

Or import the video clips first, then deselect the auto-proxy mode, then import the nested project file(s).

Or lower the frame size of the source project before you import into the main project and reset the source before rendering.

Or set your preview to »Gut« or »Optimal« to temporarely override the proxies.

Or rename a copy of your source project to »Mach mit Title.sfvp0« to let the main project use the project file itself as proxy.