It's OK, order-wise. If only the AVC format was accelerated like HEVC, Vegas 17 would be the first new version I'd buy after a long divorce... Unfortunately, NONE of acquisition formats I use can be played back at full 50p (not in UHD)!

Well, making the change showed a lower fps playback.

Where do you see that?

In the first video a see a playback of not more than 1fps in the preview display and in the second same playback the full 50p playback of an HEVC 4K GOPro 7 Hero clip in the display

I assume you have posted the video clips in the wrong order?

Not not I'm aware of.

It's OK, order-wise. If only the AVC format was accelerated like HEVC, Vegas 17 would be the first new version I'd buy after a long divorce... Unfortunately, NONE of acquisition formats I use can be played back at full 50p (not in UHD)!

Yeah, 8K R3Ds could be given some love by CUDA/TENSOR/RT decode/debayer in Vegas too. :)

The first clip before you make the change has a playback rate of 3.nnn fps, the bottom later clip has a lower fps of 2.nnn fps

Unfortunately, NONE of acquisition formats I use can be played back at full 50p (not in UHD)!

@megabit

On what system are you using Vp17? On my i7-8700k with AMD RX570 I can play UHDp50 AVC footage from a GH5 in a UHDp50 project with the internal preview 1920x1080 Best(Full) with 50fps indication.

Here a screen shot with the GPU loads. The CPU is loaded by 42%

@Former user

the bottom later clip has a lower fps of 2.nnn fps

I never have or shall know that "lower fps of 2.nnn fps" means this:

To me it looks like a preview display playback of 50 fps.

"The first clip before you make the change has a playback rate of 3.nnn fps, the bottom later clip has a lower fps of 2.nnn fps"

You're looking at the wrong numbers, the current frame number instead of the frame rate.

The first video plays with about 1 fps. The bottom video plays with full 50 fps.

Ok got it now, thanks Marco, not up long.

Unfortunately, NONE of acquisition formats I use can be played back at full 50p (not in UHD)!

@megabit

On what system are you using Vp17? On my i7-8700k with AMD RX570 I can play UHDp50 AVC footage from a GH5 in a UHDp50 project with the internal preview 1920x1080 Best(Full) with 50fps indication.

Here a screen shot with the GPU loads. The CPU is loaded by 42%

Just see my signature (you will be surprised)... Also - since I grade for HDR10 - I only record in 10bit, 4:2:2 mode which is why all my GH5 internally-recorded clips are just 25p; when I need 50p (most of the time) I grab my Shogun Inferno. But even those files cannot be played at full 50 fps in Best/Full settings, and with my reference monitor connected via Decklink! It's so weird I'd be suspecting something bad is happening to my workstation - but it's enough to open Resolve or Assimilate Scratch or The Foundry Nuke and bang! - all my clips/projects play back at full 50 fps speed again!

Piotr

Remains the original question: Why is the program making such wrong settings??????

VP17 is very good. Wow. Much improved. I love the new color wheels and its new lay out. On my 1950X system, I can precisely adjust color correction with just the mouse. VP17 play back my GH5 4K 60P full frame rate @ best with color correction, all sailing smooth. My 2nd system is a aging i7 4930K at 4.5ghz with R9 290X can play back full frame rate at best 4K 60P. But when I add color correction to the sample clip. The playback came to it knee. Also, it is impossible to use color wheel with the mouse or holding down CTRL key on less powerful system.

Vegas 17 are not able to play back 8K Red footage with proxy. Import 8K is fine but playback came to it knee. I can run 8K 60P smooth and can scrub smoothly with Davinci Resolve. But over all I am still very satisfied VP17 . It is very good and I am sure Magix will continue to improve better and better.

Me thinks the develpers don't use the product they produce. E.g., why the clunkiness in the color wheels? -- each "clik" is .10 and should be .05 without the CNT key held, which brings it to .01. But .10 is way too gross, who adjusts like this? Ans: NO ONE...but the developers seem to not care. That is what makes APPLE so good, the interface is elegant and doesn't mess you up, doesn't "encourage" mistakes. Like the color adjust sliders don't work with arrow keys, as you might expect, and it starts moving my time line, even though I just clicked on the slider, (and other program adjustments allow for the arrow, i.e., not system wide consistent) . But should only be after a definite clik.

Megabit, my 4k 10 bit Gh5 footage plays at a decent clip without hardware decoding acceleration (I have an AMD GPU that isn't supported yet, and no quicksync), so something must be up with your setup. I do still proxy for multicam, but just one angle at a time does ok.

@zdogg

Answer: ME! Sure, I like to use CTRL w mouse wheel to make fine adjustments, but when I need to make a coarse adjustment quickly I just let go of the CTLR key and roll away. Fast and accurate for me.

Morale of the story: It's a personal thing. So don't accuse the Dev's of not caring or using their own products - that's not rational.

.05 is plenty coarse for this type work..... IMHO.

Probably worth a feature request: FX adjustment increments fine = ??, med = ?? coarse = ??.

For the last users who responded

What has all this to do with this topic and my question in it?

@Kinvermark I am not a person who can't be pleased. But the program excells in concept, and really falls short on elegent implementation of those concepts. Probably because the code is old, or Gary won't lose his love of his original creation, but no reason for the constant clunkiness of some of the very basic routines.

Now, I cut them slack because of the inherant complexity of this type program, but my patience has worn fairly thin. I LIKE the idea of the color wheels, the story board and Nested projects. I also like the idea of fixing stuff that has vexed this program for decades now. I know that some editors work with a couple of tracks and that's it. For those folks, things are probably peachy.

But the real reason to get excited about this program is its compositing and for that, the functionality is there in a WYSIWYG way, but it just won't get out of it's own way sometimes by way of the GUI. Sorry for the rant.

I tried the color wheels, meh........ I hope I will be more bowled over by nested projects (looks brilliant Gary, no kidding) just haven't tried it, and same with the other new stuff, and some of it looks brilliant. Story board, brilliant. New auto split thing, brilliant as well, some really cool stuff in VEGAS, well conceived. I LOVE the program, I just wish it did things with a smoothness that just seems to escape the grasp of the developers, and that is why I say they might not use it, much at all, OR in the same ways as others, more sold on it's reall potential, OR they work on such setups that are high powered to the point that some of these situations are mitigated. I've got a great machine, and don't have these GUI issues elsewhere, i.e., Adobe or Resolve.

"What has all this to do with this topic and my question in it?"

Correct, back to topic please. This is about playback performance dependend on the hardware decoder selection.

Addendum..... the new color curves panel was really slow to respond, I grabbed and pulled the handles and nothing, then after a lag it moved, but once that happens, you never know where the thing is going to end up..... so again, not picking nits here, things just ain't up to speed as of yet.... the old curves NEVER did that for me, going back many years. So how is this an "improvement." I need more than bells and whistles, I need functionality.

Sorry for 'off topic' - I read the OP's title, "what a difference." and then responded to someone's comments on Color wheels, so there is an element of confusion based on topic header.....but, apologies all the same.

Dang it my 1070 on desktop and 2060 on laptop do not accelerate timeline playback even with trying all the settings