Mark thank you very much. I did try that before, but it was redirecting me to a "NOT FOUND" webpage. I had to copy the link and paste into my browser, it's now downloading. Thanks again.
@john_dennis wrote:
If I had to get something out the door, I'd stop shooting Vegas/hardware/media/driver/phase of the moon bugs and move on with my life. Some video formats exist to let cameras cram ten pounds of stuff on to an SD card and some video formats exist to make non-linear editors work smoothly. Pick one for each task.
Ok... I just tried that same clip again in B636. First time dragging it to the timeline and trying to play it back... crash. Restart Vegas, it asks if I want to continue where I left off, yes, and it played back fine. I decided to move the cursor to different locations on the clip, it worked for a few changes, and then crash again. Not good.
So with the clip in hand, and several editors on my computer, I decided to see "who" was able to handle the clip. Pinnacle Studio 25 Ultimate, a consumer editor, handled it without a problem. Timeline playback was smooth, so I decided to add a LUT to it. No problem playing it back smoothly.
Next up was Magix Movie Edit Pro 2022. Again, no problem playing back the clip with a bleach bypass filter added.
Next, Videostudio Pro 2022. Crash. Hitfilm Pro 2021.3 won't let me even import the clip
Vegas' sister so to speak, Magix Video Pro X 12, no problems. Resolve Studio 18 (the one oft mentioned here in this forum), no problems.
So, two under $100 consumer editing programs handle the clip without issue including grading the color. VPX and Resolve also, no problem. I personally do think that Vegas should be able to handle it. Yes, you can convert it to something that Vegas will like, but it's more time involved instead of just dropping it on the timeline.
I have no "dog" in this fight. I use the tool that will get me the results with the least amount to stress. I absolutely LOVE editing in Vegas. And it handles all of my footage from my Panasonic cameras without an issue. But when the other "top" editors and a couple of consumer editors handle the footage without a blip... this is something that the Vegas developers should consider.
Your observations are correct.
The Shade Tree Vegas Pro Historian elaborates:
Vegas 13-453
Vegas 14-270
Vegas 15-416
Vegas 17-455
Vegas 18-527
Vegas 19-550
@john_dennis, the "shade tree historian" (I did know about shade tree mechanics back in the day), I've removed 14-17 from my computer and only have 18 and 19 still installed. The results you see in VP19 are what I get with VP18 and AMD RX480 on or off.... it's a "no go" for me.
Great work "historian"!
@john_dennis Well that's interesting, So for VP 17 and 18 you're using SO4 decoder AND GPU decode is working fine?
Someone , I think Reyfox brought up their being 2 decoders for AMD, are you using the auto selection or the other one?
@Former user
Vegas Pro 17
Vegas Pro 18
Vegas Pro 19-550 GPU OFF
NVIDIA GPU decoder did not go backwards in compatibility with this file, it crashed VP17 and VP18 as well
Interesting about the other platforms, of less value, having no problem with the file. For shits and giggles, I loaded the file into WinxHD and rendered it out, then tried it again in VP, no issues at all with it.