Comments

xberk wrote on 12/2/2018, 11:46 PM

Is this different than nesting .veg files in Vegas?

Personally I prefer to render the "object" (for example, a series intro that is the same in each segment) to an MXF and insert that into the new timeline.

3POINT wrote on 12/2/2018, 11:57 PM

I agree with xberk that you're asking for a feature in Vegas that is already implemented, a long time ago.

Nesting .veg files has the advantage that you always can change the nested .veg in a separate Vegas instance without rerendering and that those changes automatically are taken over in the project that contains those nested .veg's.

3POINT, Theo Houben, Vegasuser since version 5

Recware:GoproHero7Black, YI4k+,PanasonicFZ300/HCX909, Sony PXW-X160

Software:VegasPro16/VegasMovieStudio15/PowerDirector16

Hardware:i7 4770, 16GB, GTX650ti, 1920x1200 display

Playware:Philips 55PFL7108

Gabriel_Isa wrote on 12/3/2018, 12:44 AM

Is this different than nesting .veg files in Vegas?

Personally I prefer to render the "object" (for example, a series intro that is the same in each segment) to an MXF and insert that into the new timeline.

You will have to open another Vegas intance ifterface.If you render it ,you can't change any more.Right?

Gabriel_Isa wrote on 12/3/2018, 12:54 AM

I agree with xberk that you're asking for a feature in Vegas that is already implemented, a long time ago.

Nesting .veg files has the advantage that you always can change the nested .veg in a separate Vegas instance without rerendering and that those changes automatically are taken over in the project that contains those nested .veg's.

I don't think that Adobe and BMD are fools to have this feature .If we can do a job in one interface , why two ? The more infterface the slower the computer run. And it is not convenient any more.

xberk wrote on 12/3/2018, 1:19 AM

>> I don't think that Adobe and BMD are fools to have this feature

What feature?

I've had little problem using two instances of Vegas, cutting and pasting whole sequences or whatever between them -- sometimes I use three instances. Huge time saver. Naturally, if you have heavy FX, you can bring any consumer computer to a crawl, but for many applications mutli instances of Vegas works great.

 

Gabriel_Isa wrote on 12/3/2018, 1:51 AM

>> I don't think that Adobe and BMD are fools to have this feature

What feature?

I've had little problem using two instances of Vegas, cutting and pasting whole sequences or whatever between them -- sometimes I use three instances. Huge time saver. Naturally, if you have heavy FX, you can bring any consumer computer to a crawl, but for many applications mutli instances of Vegas works great.

 

Pr has the nest sequence feature.And Magix has add it to Video Pro X 10.

3POINT wrote on 12/3/2018, 1:54 AM

I agree with xberk that you're asking for a feature in Vegas that is already implemented, a long time ago.

Nesting .veg files has the advantage that you always can change the nested .veg in a separate Vegas instance without rerendering and that those changes automatically are taken over in the project that contains those nested .veg's.

I don't think that Adobe and BMD are fools to have this feature .If we can do a job in one interface , why two ? The more infterface the slower the computer run. And it is not convenient any more.

For me it is a big advantage that Vegas, the only NLE I know, can open more than one instance at the same time. I normally use Vegas Movie Studio, which doesn't support nesting but support also more than one instance. With this feature I'm able to quickly copy/paste parts of one project to another project. Never had the feeling that a second instance slowed down my computer, because I'm working always in one of the instances at the same time.

3POINT, Theo Houben, Vegasuser since version 5

Recware:GoproHero7Black, YI4k+,PanasonicFZ300/HCX909, Sony PXW-X160

Software:VegasPro16/VegasMovieStudio15/PowerDirector16

Hardware:i7 4770, 16GB, GTX650ti, 1920x1200 display

Playware:Philips 55PFL7108

3POINT wrote on 12/3/2018, 1:58 AM

>> I don't think that Adobe and BMD are fools to have this feature

What feature?

Pr has the nest sequence feature.And Magix has add it to Video Pro X 10.

Can you explain the difference/advantage of the Pr and Pro x10 feature against the Vegas nesting feature?

 

3POINT, Theo Houben, Vegasuser since version 5

Recware:GoproHero7Black, YI4k+,PanasonicFZ300/HCX909, Sony PXW-X160

Software:VegasPro16/VegasMovieStudio15/PowerDirector16

Hardware:i7 4770, 16GB, GTX650ti, 1920x1200 display

Playware:Philips 55PFL7108

Marco. wrote on 12/3/2018, 2:26 AM

Nesting sequences means nesting timelines inside the same project so you could have several timelines managed in just one project.

altarvic wrote on 12/3/2018, 2:30 AM

Advantages:

1. You don't have separate projects, all nested timelines are in one project. Each nested timeline has its own properties (resolution etc.) . Insert any timeline as a clip to another timeline.

2. Speed. Less consumption of system resources. You don't need to open multiple Vegas instances.

3. More convenient. Better workflow.

david-tu wrote on 12/3/2018, 8:50 AM

+1 to Altarvic. I find Vegas form of nesting to be very cumbersome. I would rather have several timelines open in one instance of Vegas.

3POINT wrote on 12/3/2018, 9:12 AM

@ Altarvic

For me it is rather an advantage, that nested veg's are separate editable projects and not parts of a multi project timeline. I personally use nesting only for intros/outros, lowerthirds or as chapter building for long complicated projects.

3POINT, Theo Houben, Vegasuser since version 5

Recware:GoproHero7Black, YI4k+,PanasonicFZ300/HCX909, Sony PXW-X160

Software:VegasPro16/VegasMovieStudio15/PowerDirector16

Hardware:i7 4770, 16GB, GTX650ti, 1920x1200 display

Playware:Philips 55PFL7108

xberk wrote on 12/3/2018, 10:29 AM

I know next to nothing about Pr .. does multiple timelines mean you can make the full gamut of changes and edits to any of these nested timelines within the same project? Is there a "main" timeline, or are all timelines equal? Or does a nested timeline have some limitations that the "main" timeline does not? A second instance of Vegas gives you the same tools and abilities in both instances.

Gabriel_Isa wrote on 12/3/2018, 10:58 AM

Nesting sequences means nesting timelines inside the same project so you could have several timelines managed in just one project.

yes haha it is true .

david-tu wrote on 12/3/2018, 11:09 AM

Xberk, with multiple timelines, at least the way it works in After Effects, each is independent, just like a different project. But to switch between them is just a TAB. If you want to "nest" one timeline into another, you just add that timeline as a source to the other one. All assets are shared between timelines, so you don't need multiple entries. Any changes to one timeline is instantaneous in any other timelines that it is nested. You can render each timeline out independently at different rendering options. It is basically like having multiple projects open in the same window with quick access and sharing.

monoparadox wrote on 12/3/2018, 3:07 PM

I often create nested projects from an event via Vegasaur's one click menu to apply track compositing/fx effects that require track application such as Boris BCC Match Move and Corner Pin. Keeps things from getting messy in the main project.

Kinvermark wrote on 12/3/2018, 7:34 PM

+1. Totally agree with you guys about this. Tabbed and stacked timelines (ala Davinci Resolve) are a more elegant and efficient way to edit; especially when dealing with complexity.

Editing speed & efficiency are crucial to Vegas' competitive advantage, so I think this should be a high priority for developers (my guess is that it already is, as it would make a lot of sense to connect tabbed timelines with project media storyboards).

john_dennis wrote on 12/4/2018, 9:34 PM

Having worked with AutoCAD for two decades, the Vegas process of nesting projects makes a lot of sense to me. It is analogous to blocks with attributes and/or external references. I use nesting for animated graphics that I build myself long before or after I do the main project. I sometimes use nesting to resize videos so they show up in the main project at the right size without fooling with it on the main timeline.

In AutoCAD and Vegas there are gotchas with getting a drawing or project without the external references or nested items in the package.

Here's my question. Do the programs that use multiple timelines allow one to export portions of a project for use in other projects?

john-brown wrote on 12/4/2018, 11:08 PM

VPX and Movie Edit Pro have multiple timelines, if you wish, or the term Magix uses is multiple movies. They are tabbed. The main use of these is to have multiple movies on a DVD/BR, each with chapters.

Each movie can be exported as a movie, which is essentially a one movie project. An exported movie can be imported into VPX/MEP as a movie with its own tab, or appended to another one.

VPX only has the nesting feature. Thus you can use one movie as the main timeline, and others for other movies and/or creating nesting objects (events in Vegasese). The movies are listed in the Project Folder of VPX. In the main movie or another one, simply drag the movie that is to be nested onto the timeline. Done. Go back and change the movie that was nested, and it's automatically updated on the main movie timeline. It's fast and easy.

If you have a sequence that you use often but needs minor adjustments in each project, simply save it as a movie and import it into the new project in a separate movie tab. Adjust (as it is a project not an mp4 or wmv). Insert movie on the main timeline (nesting).

As well, objects can be easily copied between movies, as can effects. To copy an entire timeline from one movie to another, Ctrl+A, Ctrl+C, click on the other movie tab, Ctrl+V. It's that fast.

If a movie gets too long, set the playback marker, Alt+Y, everything to the right of the playback marker is now in a second movie, but still in the same project. It's that fast.

Example, I have a project with multiple movies (no nesting) for different activities/family members at Christmas. I can copy objects and effects easily between them. I'll export each movie as an mp4 for distribution to the appropriate family members. For our family, we'll get a multi-movie BR. Etc.

It would be best to see how this works. If anyone wants, I can do up a quick video.

Kinvermark wrote on 12/5/2018, 9:09 AM

 

Here's my question. Do the programs that use multiple timelines allow one to export portions of a project for use in other projects?

@john_dennis

This is a good question as it implies (I guess) that moving to multi-sequence projects might break the current support for Vegas' nested projects. In Resolve you can export/import a project but not a portion thereof. You can export/import a single timeline via XML, but that is quite limited in what elements carry over.

What the implications of this are, I am not sure without further testing. I would say that breaking nested projects to replace with multi-sequences would not be a good idea.

Gabriel_Isa wrote on 12/5/2018, 10:51 PM

 

Here's my question. Do the programs that use multiple timelines allow one to export portions of a project for use in other projects?

@john_dennis

This is a good question as it implies (I guess) that moving to multi-sequence projects might break the current support for Vegas' nested projects. In Resolve you can export/import a project but not a portion thereof. You can export/import a single timeline via XML, but that is quite limited in what elements carry over.

What the implications of this are, I am not sure without further testing. I would say that breaking nested projects to replace with multi-sequences would not be a good idea.

Have you ever use the AE templets ? You can use any part of a project in another one .

john_dennis wrote on 12/6/2018, 9:25 AM

“Have you ever use the AE templets ?”

No, I haven’t.

Gabriel_Isa wrote on 12/6/2018, 11:24 AM

“Have you ever use the AE templets ?”

No, I haven’t.

Just have a try, very good experience.

zdogg wrote on 12/6/2018, 2:38 PM

I have advocated, a few times on these boards, for a sort of Magix/Vegas meetup that would fuse some of the best features of the Magix line, (including Samplitude, especially their object based interface, GUI) into one powerful product. I can see some of that happening already, some cross fertilization IS going on, single features lifted out of one and mapped to the other. So it IS happening, but probably not as rapidly as some would like, and really, Vegas needs to just be re coded from the ground up, I would say, it is one old creeky beast, albeit worth saving as it does things, especially simple compositing, better and faster and more intuitively, than just about anything,