@john_dennis

Yep, I can do it. Thanks for the help John, I guess that this is my unique option if I want to nest anything without crashing hahaha.

You really helped me a lot, maybe you have any idea of what's the bug behind this issue?

@X-Jake

I don't have any insight on why nesting fails on your system from the error report. More information about your work environment might help someone.

Work This: https://www.vegascreativesoftware.info/us/forum/important-information-required-to-help-you--110457/

Kernel errors are rare. You may have tripped over a bug. You could edit your topic title with the word [BUG] so the developers are sure to notice it. They are good about monitoring this forum.

As far as I can tell, nobody in this thread has confirmed or denied this error, so I went ahead and tested it and it works for me:

And here on the Timeline:

Great tool. Makes Nesting much simpler and straightforward, fast, and could be addictive too!

KUDOS to the devTeam.

OK, not an error, but some advice. I opened my monster project of some 2,597 pieces of Media. I then made a Selection of six Events on the TL. I hit the Create Nested TL:

This it does, however, there doesn't appear to be an immediate sync-BACK to the original VEG. What I get is a new VEG in its own TL with the original VEG all but gone. Close this, and there is now no path to the Original VEG. This is unfortunate. OK, obviously there is much happening and this means a lot of heavy lifting by VP108. I've got an i9 plus the other bits on my Rig, so, maybe there is a performance issue that is creating your issue but not on mine.

@VEGASDerek - A suggestion: This Create Nest Icon returns me to the original VEG with this newly hatched Nest sitting front and centre.

@Grazie Any luck getting nesting to work? I have a very light project with one event, which is selected. Click on the nest icon and the results are the same as what you got, an empty project. Vegas 21 build 187.

I quite regularly get crashes with nesting, so I don't use it but keep trying it because I do want it to work. What I don't remember seeing before is a render box popping up before & after creating/closing the nest? .. BTW just tried it 4 times, crashed 3 times at different times, twice closing the nest, once was closing that project.

Opening nest

closing nest

Extra Information
   File:                C:\Users\gidjo\AppData\Local\VEGAS Pro\21.0\gpu_video_x64.log
   File:                C:\Users\gidjo\AppData\Local\VEGAS Pro\21.0\fileio_x64.log
   File:                C:\Users\gidjo\AppData\Local\VEGAS Pro\21.0\persist.prefs
   File:                C:\Users\gidjo\AppData\Local\MAGIX\FileIO\1.0\So4HardwareDetectionError.log
   File:                C:\Users\gidjo\AppData\Local\MAGIX\FileIO\1.0\So4HardwareDetectionOutput.xml
   File:                C:\Users\gidjo\AppData\Local\VEGAS Pro\21.0\dx_video_grovel_x64.log
   File:                C:\Users\gidjo\AppData\Local\VEGAS Pro\21.0\svfx_video_grovel_x64.log
   File:                C:\Users\gidjo\AppData\Local\VEGAS Pro\21.0\ocio_x64.log
   File:                C:\Users\gidjo\AppData\Local\VEGAS Pro\21.0\dx_grovel_x64.log
   File:                C:\Users\gidjo\AppData\Local\VEGAS Pro\21.0\vst_grovel.log
   File:                C:\Users\gidjo\AppData\Local\VEGAS Pro\21.0\vegas_script_x64.log
   File:                D:\desk stuff\Desktop\newerr.veg
   File:                D:\desk stuff\Desktop\newerr_Untitled Timeline.veg

Problem Description
   Application Name:    VEGAS Pro
   Application Version: Version 21.0 (Build 187)
   Problem:             Unmanaged Exception (0x00000000)
   Fault Module:        C:\Program Files\VEGAS\VEGAS Pro 21.0\vegas210.exe
   Fault Address:       0x00007FF758DB061E
   Fault Offset:        0x00000000004D061E

Fault Process Details
   Process Path:        C:\Program Files\VEGAS\VEGAS Pro 21.0\vegas210.exe
   Process Version:     Version 21.0 (Build 187)
   Process Description: VEGAS Pro
   Process Image Date:  2023-11-02 (Thu Nov 02) 18:23:24
 

For those who need some explanation about nesting timelines: https://www.vegascreativesoftware.com/us/video-editing/edit-videos-timeline-collaborative/#:~:text=VEGAS%20Pro%27s%20approach!-,NESTED%20TIMELINES%20THE%20VEGAS%20PRO%20WAY,streamlined%20and%20efficient%20as%20possible.

@Grazie Any luck getting nesting to work? I have a very light project with one event, which is selected. Click on the nest icon and the results are the same as what you got, an empty project. Vegas 21 build 187.

@Robert Johnston - Haven't explored it anymore. I skim-read the link from @3POINT and my head started to ache.

I'll await developments from them upstairs to make this once straightforward feature become Grazie-Proof. 😉

I just did some Timeline nesting tests without issues. The main advantage of using Timeline nesting is that you don't need to open (anymore) a second instance of Vegas for editing the nested Timeline, it's done in ONE Vegas instance and you can jump fast between the nested Timeline and the main Timeline.

@3POINT - That easy hey!? You may have just re-inspired me to have a further go. So, no separate VP instance being visible?

@X-Jake

It is a bug, I just did a small test on my system with my media and my simple and small test project, and "bang" immediate crash of Vegas when I confirmed the new project (not the master) after using the nesting button...

As far as I am concerned the bug is confirmed.

Now on the subject of nesting, I use nesting a lot, but more the old Vegas way: creating projects, editing and saving them (let's, call them modular sub projects), then create a "master" Vegas project, edit and save, and then dropping the sub projects "as sort of modules" into the main project as any other media. After that, I do tend to use the nesting button to go back and forth to already existing projects. There is a subtle difference in using the nesting button (only one nest deep allowed) vs "old" nesting where you can go up to 7(?) nesting deep (out of my head, but it is somewhere in the internal prefs). Obviously the old way requires opening a new (or second Vegas instance) to be open to edit the nested project.

@3POINT - That easy hey!? You may have just re-inspired me to have a further go. So, no separate VP instance being visible?

Indeed, not when you use the buttons on the toolbar. Take care that nested timeline changes must be saved before turning back to the main timeline and that there is always some time needed for caching before the nested timeline is updated in the main timeline.

This great feature is not finalized.

1. If you edit the nested timrline and make it longer or shorter, the new length is not reflected in the master project. It either loops or is too short. Turning on auto ripple doesnt help.

2. If you select only video events to create your nested timeline then decide later on to add an audio track to the nested project, this audio track never appears in the master project

3. The proxy audio file (like @Former user memtioned) is always rebuilt after going back to the master project even though there is absolutely no modification in the audio.

4. Vegas crashes often when you open another program while the nested timeline is opened.

5. If you select vevents A, B C to create your nested timeline then later decide to keep only A and B for example, C can't be deleted from the master project media pool.

It hope those issue will be fixed

@GJeffrey - Ah, you’ve just reminded why I ran away. Oh, dear me. 😩

This great feature is not finalized.

1. If you edit the nested timrline and make it longer or shorter, the new length is not reflected in the master project. It either loops or is too short. Turning on auto ripple doesnt help.

It has always been that way because a nested timeline behaves like an normal (video) event, which doesn't change length when you replace content.

My early experience with nesting was not great which is why I've stuck with - if using sepaate VP sub-projects - to copy/paste them into the master project. Now with Vegas Pro 21 and recently having replaced spinning discs with SSDs including much more recently replacing the C drive with a Samsung 990 M.2 SSD, I am getting great timline performance (yes, mostly in Preview mode) with my current project which has now reduced to under 4 hours in length (under 2 hours is the desired final length). Absolutely no problems with hours and hours of editing today.

Unfortunately the crash I had, I could not reproduce any more. Fortunately the crash dump was send to Magix/Vegas with some comments, hopefully this was helpful. Strangely enough, although Vegas did fully crash when creating the nest as I posted before, when I started Vegas again, the nest was apparently successfully created and I can go back and forth... Attempting to reproduce the bug again failed....

My best guess is a race condition not properly handled or something not properly initialized which causes a crash sometimes (media being not ready?) when using nesting. I did start Vegas fresh when the issue occurred. These things are very nasty to reproduce.

These things are very nasty to reproduce.

@bitman - Yeah, these are the worst for the DevTeam. I'm staying well clear. 😩

@GJeffrey 👍

4. Vegas crashes often when you open another program while the nested timeline is opened.

This is prob what happened when I earlier said "crashed ..... once was closing that project"

This is a totally fresh launch of Vegas, only turned the PC on ½hr ago, 2x ProRes .mov UHD clips.

5. If you select vevents A, B C to create your nested timeline then later decide to keep only A and B for example, C can't be deleted from the master project media pool.

I just dragged this .veg back onto the timeline, opened it's nest it looked exactly like the dragged in .veg, just one event.

When the .veg is opened using the folder button top left, the nest then shows the two clips that were nested.

Making no changes to the project, looking briefly at this thread, back to Vegas & closing the project I get no crash this time 🤷‍♂️

--------

PS, deleted all the recent files .veg etc. Recreated the same timeline with those two clips, nested, added Vegas Color Corrector instead of the BCC+ fx, returned to Parent nest, had a quick look at this thread, back to Vegas, closed that project - crash.

I tried without fxs or crossfades with success - no crash, but if I do anything with the nested clips I get a crash in some way or another,

Another day, another attempt to reproduce, and yes, Vegas crashes again: in the same way in my case: PC fresh start, do some office stuff (no vegas, nor any other video, photo or audio stuff) for an hour or so, have nothing active, start Vegas for the first time after an hour of PC activity, then create a nest via the button, it fatally crashes.

I am not sure, but I see briefly that when experimenting with the nesting button, I get the impression that the media goes offline when going from nest to main or vice versa. I had sometimes issues like "mediastream has changed" playing around with nesting, and it goes downhill from there.

I have my "close media files when not the active application" enabled by the way.

Does your media gets offline when you depart when you nest or you go back?

Are the crashes linked to this?