@Len Kaufman Usually clips get duplicated if you Ctrl + drag. Is your finger anywhere near your keyboard Ctrl? That's the only cause I can think of.
@EricLNZ Thank you, Eric. I'll try to be more conscious of that. I'll keep you posted if that's the thing. I hope it's as simple as that.
In Vegas 23, I cannot find a way to swap the timeline with the docking area. In other words, put the timeline on the top, which I have been doing for decades. There's always been a checkbox for this in Options | Preferences, usually on the Display panel.
@EricLNZ Though I can't try your suggestion just now, as my computer is rendering out a lengthy video, I did some digging, i.e. Google, which is surprisingly good at finding out things about VP. It confirms what you said, but there is a "condition" which can change the function. It said ctrl+drag if you place the cursor on the edge of the clip speeds up a clip. And if you place the cursor in the body of the clip, it will create a dupe. Never heard that one before. When the render is finished, I will experiment. Came across another option which I, and likely others, will find useful, and that is described here: 
In that technique, you create a box around the entire area of clips, including multiple timelines, and that will allow you to drag a bunch of clips. I'm learning something new every day. There is so much depth to VP, in all its iterations. I often marvel at the complexity of it, and the minds that went into putting it together.
I'm still missing "lock in time" to prevent a clip from moving unintentionally when clicked on, but still being modifiable, "lock clip" just prevents every- and anything.
Thanks for the update! Always great to see VEGAS Pro getting steady improvements. I’ll install build 278 and give it a try, curious to see how it runs compared to the last version. Appreciate the team’s hard work keeping things moving forward.
What is going on here? - the visual differences between gui of V22 and V23 are a matter of taste, not that I am happy about them, but the visual difference between the previews of the same frame in the same project are a disaster. The V23 preview is plain wrong.
Are you using ACES? 23 is using an updated version.
Hello Editors,
I am here to drop a big concern message.
I always used Vegas 20, as so far it is the most stable one:
I will now list a couple of bugs I've found so far. Given that the previous two versions are still experiencing the same issues, I am 99% sure that half of these bugs (or poorly implemented features) will remain. So, I guess this will be the third refund... but let's get started!
Specs: i9-13900K - 4090RTX - 64Gb Ram 6000Hz - Win 11.
1. Color Grading Bug: Curve Tolerance.
Comparison between Vegas 23 (left) and Vegas 20 (right).
All the curves have an error with the color grading selection, meaning that if you obtain a curve with a certain angle range, Vegas will completely skip color data, creating 'color holes' in the video (or color jumps).
The same settings in Vegas 20 don't create any problem. Is this related to the new ACES? Probably, but disabling it doesn't solve the issue.
If you know some settings in order to revert to the old color system, please advise. Maybe I am not disabling it correctly!
Even if it's a fixable issue, having the new ACES + these problems, doesn't make sense. Not everyone joins this forum seeking replies, making new customers and editors leave Vegas, and considering it a non-professional software.
2. Color Grading UI: 3x Slower UX
I always color grade videos taken with external cameras (Sony, Xiaomi, Apple).
Since I create my own LUTs, but even without creating those, I always need to 'touch' the RGBW Color Grading Graphs.
The new system in place makes the work slower, and it doesn't work properly:
Video: 
Is there a way to revert to the 4 graph panels mode?
Vegas should be the king of speed, considering... well... everything! The all-in-one program that can do anything, superfast.
With this color grading redesign, it not only makes everything slower, but it's also not practical. In previous Vegas versions, we had 4 functional panels that you could drag and drop anywhere. Now we have one window which has 5 panels inside, each one of which has sliders glitching in the UI, going behind the preview, or below pinned curves. Moreover, I need 3x more time to edit colors. WHY?
3. Preview is Pixelated
This is something I don't understand...
Again, same clip, same settings, same quality, yet on Vegas 23, the preview, when zoomed in, is pixelated.
Yes, I did check all settings. What is wrong with the program? Did anyone experience the same issue?
4. Small UI Bug - Not Critical
Just something small that itches my brain. Curves go above the track layer limit.
5. AI FX: Not Working and/or Crashing Vegas
6. Render Settings and Compatibility Mode: Super Slow Rendering!
One of the main features of this new Vegas is at what speed it can render. It should be faster than previous versions.
While rendering a basic clip is actually faster (by 30%, not that big of a difference, since the website states a 400%), here's the big problem that will make their new Core Engine basically useless: it cannot render FX and transitions properly.
Here's how you will notice that the new Vegas is indeed 400% slower (yes, I am not exaggerating).
Take 2 clips and overlap them to create a normal crossfade effect. You can try out for a 8-second crossfade effect (this is just for testing purposes).
Now render using an old version (I used Vegas 20) and then, the same crossfade time, with Vegas 23, like I did in the example above.
As you can see, a basic crossfade effect took 4x the time with the new Vegas. Amazing! (I want to cry)
You can try any render template, any bitrate. The results can 'improve' by being only 3x slower, to 12x slower if you are using some super-crazy effects like... color grading, black & white, sharpening, Film effects.
If you are crazy enough, try to render a project within a project, but first, take a week off.
7. Rendering: Cancel Causing Crash.
This has been reported already, if I recall it correctly, but I'll list it here anyway.
Hitting "cancel" during a rendering process will make Vegas crash.
8. Reported Already: Above 1080p Assets Will Make the Pan-Crop Tool Not Function Properly.
I don't understand why, but when using 2k or 4k assets (anything above 1080p), Crop goes crazy: jumping, zooming in and out, and stretching!
Check the video below, and you will see all those behaviors happening when moving the window. This has also been reported for Masks. This could also affect Smart Mask and other FX where zoom is used.
Video: 
CONCLUSIONS
These bugs and glitches have been found after using the program for 1 project (1 hour) and some more testing (1 hour), for a total of 2 hours. I am sure I will find and report more.
More users are reporting more issues, which is good, and I hope the Developers will address all of them.
But let's be realistic...
This is the third version, which is not working properly after Version 20, with bugs that are critical to the point that make the program unusable.
Because Version 21 and 22 haven't been fully fixed and are now abandoned, how can I trust Vegas 23 to be fixed when we have way more serious issues?
I could go to Premiere, but it's laggy, not compatible with 4k videos and Effects, and slow as hell when combining with After Effects and Media Encoder. Plus, it's missing basic editing functionalities, making it not an editing tool but something to throw right into the bin.
DaVinci is the same as Adobe, but all-in-one. So another program to throw away.
The only option is Vegas to me, and I'll keep defending it even if it has all these issues, but at the same time, it's not something I can accept.
A proper Community Management or Production Management would notify at release time that Vegas 23 has issues A, B, C, ...
Also, how come QA did not notice these problems when testing?
To my eyes, I feel like Vegas Team has no clue about these issues.
The support team is not qualified enough and will tell you that the issues I reported here (like I did for Vegas 22) are problems only on my machine. Two months later, they would contact you, saying those bugs were real and that they have now been fixed. But during the first approach, they will make you feel like an idiot, crazy.
Again, keep in mind that not everyone is in this forum like we do.
We are all here sometimes to complain, sometimes to praise and advise, because we like Vegas and we trust the program. But this is the third time that a bomb has exploded, and it's worse than ever, without considering the lack of communication.
In the meantime, if someone could advise me properly on how to go back to older color spaces so that I can try to fix bug 1, that would be nice. I cannot use Vegas 23 right now, not even to simply cut a clip into 2 pieces.
Vegas Team, please, improve your communication.
I hope this message will be considered and will serve as feedback to solve the issues I reported, and that other editors reported.
@Len Kaufman I've moved lots of clips along with music and titles, and no duplicate issues. What is your specific computer hardware? There hasn't been (at least to my knowledge) of others experiencing duplicate clips when lassoing a group and moving them.
Anyone else?
@Thomas97 There's a lot here so it might be good to also create a new post so we can try to replicate bugs or help you with UI issues that aren't obvious.
You refer to ACES but are you using ACES? You are in 32-bit full mode with view transform on?
For the 4 panel graph, do you mean the color curves? You prefer to have R, G, B and overall luminance as separate graphs than overlaid as in below here? The problem I see with 23's implementation is that the lines are all on top of each other unless you toggle one off or move one out of the way.
For pixelation the screenshot isn't high enough resolution to see an issue.
Are these issues specific to the footage you are using? I don't see general issues with cropping and masking. The reported issue is about a problem that returned where a proxy file resulted in an offset Fx.
@Risi: The old Device Explorer is still available and needs to be enabled in the preferences > Deprecated Features.
Regarding VEGAS Capture - make sure that no other apps are using and blocking the capture devices. Close the browser etc. and try again.And in the new version this option are not available as default? Does it mean that if I upgrade in sometime this explorer would disappear and I won't be able to import my MTS AVCHD files?
You can obtain the file joining by opening the DOS prompt and entering the following command: copy /b 00000.mts+00001.mts+00002.mts+00003.mts myvideo.mts. Before entering the command, you must, of course, navigate back to the specific directory, also through the prompt.
@Len Kaufman I've moved lots of clips along with music and titles, and no duplicate issues. What is your specific computer hardware? There hasn't been (at least to my knowledge) of others experiencing duplicate clips when lassoing a group and moving them.
Anyone else?
@Reyfox I haven't been lassoing them. I've been selecting groups of clips, music, titles and sliding them. Sometimes it works properly; sometimes it duplicates.
@Risi: The old Device Explorer is still available and needs to be enabled in the preferences > Deprecated Features.
Regarding VEGAS Capture - make sure that no other apps are using and blocking the capture devices. Close the browser etc. and try again.And in the new version this option are not available as default? Does it mean that if I upgrade in sometime this explorer would disappear and I won't be able to import my MTS AVCHD files?
You can obtain the file joining by opening the DOS prompt and entering the following command: copy /b 00000.mts+00001.mts+00002.mts+00003.mts myvideo.mts. Before entering the command, you must, of course, navigate back to the specific directory, also through the prompt.
or use ffmpeg and the "concat" function to append the files with a a:copy v:copy to a .mp4 container losslessly
@Len Kaufman when you say you are selecting the clips, how?
I've clicked on the first clip in a group and then hold down Shift key and click on the last clip in the group I want to move around. No issues. Also, creating a Group, no issues. And using the right mouse button to select anything on the timeline grouping them together. Everything works as it should, albeit a little stuttering along the way moving the clips on the timeline.
@Reyfox Same as you: Click 1st clip, shift, last clip, move.
@Len Kaufman have you tried an alternative method like the one using the RMB? I prefer that myself.
@Thomas97 There's a lot here so it might be good to also create a new post so we can try to replicate bugs or help you with UI issues that aren't obvious.
You refer to ACES but are you using ACES? You are in 32-bit full mode with view transform on?
For the 4 panel graph, do you mean the color curves? You prefer to have R, G, B and overall luminance as separate graphs than overlaid as in below here? The problem I see with 23's implementation is that the lines are all on top of each other unless you toggle one off or move one out of the way.For pixelation the screenshot isn't high enough resolution to see an issue.
Are these issues specific to the footage you are using? I don't see general issues with cropping and masking. The reported issue is about a problem that returned where a proxy file resulted in an offset Fx.
Hello @RogerS
I'll create a separate post then, and I'll reply to those questions there as soon as I have some time!
@Reyfox Have not tried RMB. Will try it tonight.
Are you using ACES? 23 is using an updated version.
ACES? - huh? - I don't know, in that regard I use the software as is out of the shrink wrap. Ah well, something to look in to, thank you!
First image project properties in V22
Second image project as loaded in V23
@digilyd Out of the shrink rap is 8-bit full, so not 32-bit full with ACES.
The only other difference is VEGAS can now for the first time correctly read color spaces other than the standard Rec709 and Rec2020 ones. If that's causing unexpected issues for your footage (or you just don't like the effect) you can disable it in internal preferences. Hold down shift, go to options, search for color and change "("enable extended color format conversion" from TRUE to FALSE. Then restart VEGAS.
What is going on here? - the visual differences between gui of V22 and V23 are a matter of taste, not that I am happy about them, but the visual difference between the previews of the same frame in the same project are a disaster. The V23 preview is plain wrong.
@digilyd The preview quality setting on your video preview is different, comparing is best done with the same settings (e.g. both BEST (full))
I have many V23 app crash by clicking under the last track to move the cursor when reading.
Do you also encounter this ? I'm working on Win10 Pro.
I've NEVER had this issue with V19.