Can you open the .bak.veg project (Backup project) or make reset of VP.

Probably something not right with the replacement jpg file. Perhaps try 'change' the file?

I've been a more than loyal customer since audio-only V1. Tonight when I click on Vegas to launch, nothing happens. Last night I finished rendering a project with minimal issues. I removed one static image (jpg) and replaced it with another image (jpg)

At that point, I could not render the project. It would hang at 7% stuck on that particular image which was the exact same type of file and size. Both were small screenshots. Both had the same exact effect and preset.

It seems it's always the smallest of things, still continuous crashes, being unable to get Vegas to even start, that keeps me from being able to be productive. I don't want to use DaVinci, I'm too vested in Vegas, but lately, feeling like a don't have much of a choice.

I don't know what's going to happen. I am encouraged by some of the shifts in the communication from above regarding Vegas' long-standing problems, but I really doubt the Magix team has the resources or capability to rebuild this app using modern code/tools, which is what is required (there are still dependencies going back to unsupported versions of C++, for goodness sakes!).

And even if you could magically rebuild Vegas with sound architecture: it's 2023! Many of Vegas' tools are wildly outdated (just try doing some color work with 10-bit SLOG3, if you want to see how far behind Resolve VP20 is). So, it is hard to be hopeful. But I will still keep rooting for Vegas until they pry it from my cold dead fingers. :)

w/regard to your issue, I always save multiple versions of my veg files, numbered so I can keep track of them, at every major edit/change. Because I've had this happen too: you do something (who knows what) and the project refuses to open, and there's no way to recover hours/days of work. Sorry for the hard times. Hope you get your file to open!

And even if you could magically rebuild Vegas with sound architecture: it's 2023! Many of Vegas' tools are wildly outdated (just try doing some color work with 10-bit SLOG3, if you want to see how far behind Resolve VP20 is). So, it is hard to be hopeful. But I will still keep rooting for Vegas until they pry it from my cold dead fingers. :)

The grading of 10bit slog3 can be done with Vegas, and I do not see why the the color grading portal is outdated (it has been developed in the last to upgrades). True, there are still some bugs in the HDR workflow, but you can grade the different log formats like slog or vlog in an appropriate way.

Examples see here: https://www.vegascreativesoftware.info/de/forum/render-to-4k-make-artefacts-and-random-dropping-frames--139806/?page=2#ca874207

@Silverglove

without further information about your system, the footage you grade, the project settings nobody can try to help you.

@Silverglove You might want to check all the media listed in Project Media and make sure there are no zero-length clips in there. A project containing an inadvertent zero-length media event will hang on render every time. Check by right-clicking on the clips in Project Media and choose "Explore Containing Folder"... easy to spot at a glance in Windows Explorer details-view if all your media is in the same folder. If you haven't already, also recommend running "Clean Project Media" in the Tools menu. I always do that after deleting media from the timeline. Then I check the Project Media tab to make sure no hard-to-see slivers of deleted media got left behind.

@Silverglove Some info would help in trying to solve your problems.

Compare the properties details of both jpg files. I'd use Irfanview for that.

What is your Vegas version and build. What are your pc specs especially GPU.

Yes, both are identical files.

Vegas: 20 v326

Intel i9 10900KF 3.70GHz, 64 GB ram, NVIDIA GeForce RTX 3090, 2 TB NVME

@Silverglove You might want to check all the media listed in Project Media and make sure there are no zero-length clips in there. A project containing an inadvertent zero-length media event will hang on render every time. Check by right-clicking on the clips in Project Media and choose "Explore Containing Folder"... easy to spot at a glance in Windows Explorer details-view if all your media is in the same folder. If you haven't already, also recommend running "Clean Project Media" in the Tools menu. I always do that after deleting media from the timeline. Then I check the Project Media tab to make sure no hard-to-see slivers of deleted media got left behind.

I clean project media every time I remove a clip and then some, so definitely not that. When you say zero length, what do you mean per se? It's hanging on a .jpg. And this is the simplest of edits and project in general, which makes it even more frustrating.

And even if you could magically rebuild Vegas with sound architecture: it's 2023! Many of Vegas' tools are wildly outdated (just try doing some color work with 10-bit SLOG3, if you want to see how far behind Resolve VP20 is). So, it is hard to be hopeful. But I will still keep rooting for Vegas until they pry it from my cold dead fingers. :)

The grading of 10bit slog3 can be done with Vegas, and I do not see why the the color grading portal is outdated (it has been developed in the last to upgrades). True, there are still some bugs in the HDR workflow, but you can grade the different log formats like slog or vlog in an appropriate way.

Examples see here: https://www.vegascreativesoftware.info/de/forum/render-to-4k-make-artefacts-and-random-dropping-frames--139806/?page=2#ca874207

@Silverglove

without further information about your system, the footage you grade, the project settings nobody can try to help you.

Not grading, just trying to render a simple .jpg :(

The first clip, which is the exact same type as the second clip (extension and size, and effect)

Maybe something about the filename? Either too long or has a special character? Also make sure it's not locked by another app... browsers sometimes do that.

I've long-noted some bug in how Vegas handles still image files (JPG or PNG.. not sure there's a difference).

When "GPU Acceleration of Video Processing" is using my RX470 GPU, although things work, memory will climb and not be released. Disabling GPU that behavior doesn't happen.

While I admit I haven't checked to see if this behavior still exists in the latest build, I wonder if you're running into something related. Try launching Vegas, disable your GPU (preferences, Video), close/re-open Vegas and see if your project loads.

Another thing to try is resizing your image (scale down).. I've sometimes gotten huge images from clients that are only going to be slightly pushed in and ultimately rendered 1920x1080 so downscaling really didn't hurt.

I've long-noted some bug in how Vegas handles still image files (JPG or PNG.. not sure there's a difference).

When "GPU Acceleration of Video Processing" is using my RX470 GPU, although things work, memory will climb and not be released. Disabling GPU that behavior doesn't happen.

While I admit I haven't checked to see if this behavior still exists in the latest build, I wonder if you're running into something related. Try launching Vegas, disable your GPU (preferences, Video), close/re-open Vegas and see if your project loads.

Another thing to try is resizing your image (scale down).. I've sometimes gotten huge images from clients that are only going to be slightly pushed in and ultimately rendered 1920x1080 so downscaling really didn't hurt.

You're probably the closest on this. For years have always had issues with image files. And that's what seemed to be an issue here; although, The first project rendered with no issue, I replaced the very first .jpg with another .jpg that was the exact same format, size, and aspect ratio. In fact, the size is only 26.14 KB. Tiny. And you are spot on. I did end up disabling GPU acceleration, and it chugged through. I was able to get the render done before my posting but am forever frustrated by the lack of stability and the hoops I must go through to do the simplest things. The only two reasons I stay with Vegas are A) Navigation. Nobody has come close to Vegas in the way the timeline is manipulated with the mouse click, scroll/ center on zoom as well as the speed with which I can switch between tools. B) The unparalleled audio editor as many of my videos are very audio intensive.

Thanks again for your reply!!

Maybe something about the filename? Either too long or has a special character? Also make sure it's not locked by another app... browsers sometimes do that.

definitely not the issue. Both files share the same name with the exception of 1A and 1B

The grading of 10bit slog3 can be done with Vegas, and I do not see why the the color grading portal is outdated (it has been developed in the last to upgrades). True, there are still some bugs in the HDR workflow, but you can grade the different log formats like slog or vlog in an appropriate way.

Examples see here: https://www.vegascreativesoftware.info/de/forum/render-to-4k-make-artefacts-and-random-dropping-frames--139806/?page=2#ca874207

@Wolfgang S. Vegas' 32-bit Full Range mode is flat-out broken for working with SLOG3, at least for the media I've tried. At some point I may try to post about that on the VP20 issues thread, but there are more issues than I have time to report.

As far as the color grading tools being outdated, look at what the (free) competition offers:

That's just one tiny aspect of Resolve's tools!

I've long-noted some bug in how Vegas handles still image files

Testing my new PC build with Vegas 20 V 326. I put a Video clip ( see media info ) and some jpegs ( see media info ). I just used a simple cross fade transition. I cropped the jpegs in event pan crop and used a mask with some feathering so they could be seen in the video below. In the video you can see preview slows down to 8fps when it comes to the transition and jpeg file. That is with Hardware Decoder to use set to NVIDIA Geforce 4090 and then tried it with Intel Graphics 770. Both slowed down when previewing. Preview/full.

My old system that had a 3900X and Radeon Vll used to also struggle when it came to jpegs. I could be playing back ProRes files on my timeline with no problem. But to be clear I had to use Shutter Encoder to take my 4K videos from my Sony AX 700 and render them to ProRes to play back smoothly on the Vegas timeline. If not the Vegas timeline would struggle unless I encoded those files to ProRes. If i inserted any picture file the preview would struggle until it got past that image, even when using ProRes video.

I tried the same clips marked below with Resolve Ver 18 ( Free Version ) cropped, feathered jpegs, added transitions and made them longer. Resolve played them back with no dropped frames. I was tempted to leave Vegas and try out Resolve but I do not have the patients to learn it.

jpeg MediaInfo. All events taken with Phone do not if was Apple or Android.

Video used MediaInfo

Hardware decoder used. And tried it with Intel and decoder off. Same results.

Video clip of slowdown with transition.

@Silverglove

Hi

. . . . Both files share the same name with the exception of 1A and 1B . . . .

As @Howard-Vigorita suspects and has commented on - the first image does contain an illegal character, the @ symbol. While this is allowed in Linux or MAC OS environments it is not allowed in a Windows environment

Try renaming the images without the @ , then re-import it and try the export again.

John EB

@Sassylola

Is there a special reason that your Project Properties are set to interlaced?

john_dennis: I set that by mistake. I went back and set project properties to progressive. Still have dropped frames as before as shown in above video. Thanks

Hardware decoders don't support jpegs, they decode video. I'd set file io back to defaults.

Resolve leverages the computational ability of GPUs better than Vegas, but requires better hardware.

For jpegs if they're massive and you're not punching in try resizing them to project resolution before importing to Vegas. Does that help performance? I do that for time lapses.

The grading of 10bit slog3 can be done with Vegas, and I do not see why the the color grading portal is outdated (it has been developed in the last to upgrades). True, there are still some bugs in the HDR workflow, but you can grade the different log formats like slog or vlog in an appropriate way.

Examples see here: https://www.vegascreativesoftware.info/de/forum/render-to-4k-make-artefacts-and-random-dropping-frames--139806/?page=2#ca874207

@Wolfgang S. Vegas' 32-bit Full Range mode is flat-out broken for working with SLOG3, at least for the media I've tried. At some point I may try to post about that on the VP20 issues thread, but there are more issues than I have time to report.

As far as the color grading tools being outdated, look at what the (free) competition offers:

That's just one tiny aspect of Resolve's tools!

 

Sounds more like you just don't know how to use it... I grade SLOG3 in VEGAS all the time, works just fine. Same for VLOG. I'd be interested in seeing what media is causing you such issues.

As for Resolve, just like VEGAS started its life as a DAW, and as such has far better audio recording, effects, and editing capabilities than Resolve does, the same is true for Resolve with color grading, it began its life as a colorist's toolbox. Of course it's going to have well-developed color tools... but once you get to workflow speed and ease of use, that's where it falters.

There is no perfect NLE.

@Sassylola Hi, just for the sake of sharing, I sort of recreated your project but I used UHD AVC MP4's with constant fr, I also tried it with FHD content, both showed the frame dropping as in your vid,

Vegas is quite poor reg playback on my machine, I use Adobe AE for effects because of that but.. I've tried quite a lot of software & as far as i an tell all require some kind of caching to play smoothly, some do it better, quicker than others & some do it automatically, most tho only need 1 loop play to fil that cache, Vegas seems to need to loop play several times before it gets up to speed, I know there's Ctrl M & B but If Vegas could find a way to auto cache on 1 loop play that would improve it no end,

@Wolfgang S. Vegas' 32-bit Full Range mode is flat-out broken for working with SLOG3, at least for the media I've tried. At some point I may try to post about that on the VP20 issues thread, but there are more issues than I have time to report.

As far as the color grading tools being outdated, look at what the (free) competition offers:

That's just one tiny aspect of Resolve's tools!

This is simply wrong, the slog and vlog workflow works in Vegas. What do you think that I do since years with my FS7 or EVA1 10bit log footage?

👍

Vegas' 32-bit Full Range mode is flat-out broken for working with SLOG3,

This may depend on the Sony camera- haven't been impressed with the Alpha series and ACES in Vegas but FS footage seems different (don't have an FS so haven't tested it much).

As far as Vegas vs Resolve for audio I think Resolve is much more modern and I sometimes bounce audio to it to finish in Fairlight, which is a full-fledged DAW that has fewer issues with VSTs than Vegas.