Those are some great ideas for a more settings type video @RogerS :) but for this video series, im more looking for what other people say is how some setting or feature work in VP but its not true...things like that

Okay, reframe it that way.

"People say to record in VBR with max and average set to the same value for best quality" etc. [my inspiration was a FB post from today]

Beyond that you can mine Reddit and Facebook for bad advice.

ye im already on reddit looking sometimes, but figured i would try you guys in here also, always good to have more options :)

but its really not that easy looking for "faults" on reddit when i dont know what to look for or search after :)

Watch what Kodabarz and I respond on Reddit (he actually does a good job explaining why what people are doing is wrong).

Beyond that I'm not sure what's common enough to be worth debunking. I don't go out of my way to watch bad tutorial videos these days.

oh i know about Koda, i use him all the time over discord for all my million questions :) hes very much involved in my explained vids :)

whats your name on reddit?

so it has to be some typical beginner errors

I list some common problems of new users that I have seen:

• Close a window by mistake then don't know how to restore.
• Float the window by mistake and then don't know how to dock it.
• The button disappears because the track head is too short.
• FX or Track Motion dialog cannot pop up because they are hidden under the taskbar.
• Always create a loop area accidently.
• Don't know how to close the loop area created accidently.
• Only render a very short loop area created accidently, because the option "Only render loop" is turn on.
• Render lots of black screens or unnecessary parts, because "Only render loop" is turn off and lots of unnecessary clips or markers in the timeline.
• Video/image event was unexpectedly cropped in Pan/Crop: example. caused by not matching output aspect ratio.
• Often create unnecessary Pan/Crop keyframes by mistake.
• When masking in pan/crop is interrupted. How to continue it with connecting to the previous point.
• The track was unexpectedly A-B-expanded.
• Events in other tracks is often split by mistake, because no event was selected before splitting.
• After finishing the video editing, users found that somewhen lots of events in the lower track were accidentally split.
• Shift+B pre-rendering failed halfway caused by low ram in preferences.
• FX can't take effect caused by split screen view.
• Events cannot be snapped to each other closely caused by Quantize to frame.
• Logo/Text position in rendered video is different from that in the preview, caused by wrong render aspect ratio.
• .Mov with channel cannot be displayed correctly in Vegas.
• The imported video is displayed as a green screen caused by unsupported 10bit footages.
• The imported video only shows audio tracks.
• Render is stuck halfway.
• Rendering is stuck at 99%.
• Vegas crash caused by GPU accelerated processing.
• Vegas crash caused by over-old graphics card driver.

The myth about Vegas not being "industry standard" 😩 seems to not want to die...

The myth about Vegas not being "industry standard" 😩 seems to not want to die...

I wonder what that "industry standard" is? Is the standard set down 'on paper' somewhere with specific criteria listed? Or is it a moveable feast dependent on the personal preferences of those spouting "industry standard"?

Years ago on the forum discussing the meaning of a "professional" NLE, the pertinent comment (not by me) was that if someone uses an NLE for a professional project, then the NLE is professional.

I think it's a rather self serving thing that certain "other" NLE makers ( and users ) like to propagate... it's been Final Cut for video, pro Tools for audio, Apple for computers etc etc. Of course there never was any numeric or statistical or qualitative proof, but that's how myths work I guess...

so it has to be some typical beginner errors

I list some common problems of new users that I have seen:

• Close a window by mistake then don't know how to restore.
• Float the window by mistake and then don't know how to dock it.
• The button disappears because the track head is too short.
• FX or Track Motion dialog cannot pop up because they are hidden under the taskbar.
• Always create a loop area accidently.
• Don't know how to close the loop area created accidently.
• Only render a very short loop area created accidently, because the option "Only render loop" is turn on.
• Render lots of black screens or unnecessary parts, because "Only render loop" is turn off and lots of unnecessary clips or markers in the timeline.
• Video/image event was unexpectedly cropped in Pan/Crop: example. caused by not matching output aspect ratio.
• Often create unnecessary Pan/Crop keyframes by mistake.
• When masking in pan/crop is interrupted. How to continue it with connecting to the previous point.
• The track was unexpectedly A-B-expanded.
• Events in other tracks is often split by mistake, because no event was selected before splitting.
• After finishing the video editing, users found that somewhen lots of events in the lower track were accidentally split.
• Shift+B pre-rendering failed halfway caused by low ram in preferences.
• FX can't take effect caused by split screen view.
• Events cannot be snapped to each other closely caused by Quantize to frame.
• Logo/Text position in rendered video is different from that in the preview, caused by wrong render aspect ratio.
• .Mov with channel cannot be displayed correctly in Vegas.
• The imported video is displayed as a green screen caused by unsupported 10bit footages.
• The imported video only shows audio tracks.
• Render is stuck halfway.
• Rendering is stuck at 99%.
• Vegas crash caused by GPU accelerated processing.
• Vegas crash caused by over-old graphics card driver.

The post editing function of the forum seems to be disabled, so I can only add one here:

Due to hover scrub's current behavior, new users often accidentally set in/out point for media files when dragging them to timeline.