I am glad that I will finally see the function that I proposed to you five years ago "selecting events with the right mouse button".

This 'small' change is a huge step, selecting event clips with left click and drag.

 

 

Your cynicism is biting and unbearable. While users like @pierre-k deserve help and respect, it is not acceptable that you uses here a wording that Pierres findings are unreliable, or give advices that seems to be not seriously. Or a wording like "Team Vegas Helpers".

This is the last warning.

@Wolfgang S. You're trying to divide and conquer, creating unrest amongst the public board beta testers. Pierre is one of the great public board beta testers of all time, after every new release he's the one to first show and explain the bugs that the offical beta testers never found. I only speak of his unreliability with his mxf problems, and his testing, and also inability to describe how to action a fault while a fellow public beta tester could.

You later look at the mxf thread that discover that for yourself, but still threaten to ban me. I did not criticize Pierre's work in general, you created a straw man, as said he's brilliant at what he does, but even he may crack when he doesn't get the respect he deserves by way of acknowledgment from those he's trying to help .

@vkmast it could be as easy as this, a moderator (or beta testers) test the bug findings of the user then actions the information to the dev team, and lets the user know by way of moderator. We in the public beta testing team would feel like out hard work is appreciated.

Here's an example from another forum, user describes bug, moderator replicates bug, lets user know it's been actioned, and I know that sometimes happens here, but mostly it doesn't.

There's a post by Vegas Dev in this thread I haven't got to yet, maybe he's showing us all the bugs they know about now and verified, that very good.

Well I see no mention of my HEVC and AVC bugs being fixed, we'll see.

VP22 new features, Looks great, up there with other modern editors now and with all that AI stuff, perhaps even out doing the competition. I am most exited about the AI reframer and Beat detection. I do hope the AI reframer has options though, because in this example a purely 'auto' Ai reframer won't be able to do this, I had to tell it to follow the skeleton, otherwise due to the sheer volume of different people it didn't know who to follow

 

This 'small' change is a huge step, selecting event clips with left click and drag.

@set @VEGASDerek Hi, Is this on the timeline?, left click + drag creates a region, I use that a lot?

 

This 'small' change is a huge step, selecting event clips with left click and drag.

@set @VEGASDerek Hi, Is this on the timeline?, left click + drag creates a region, I use that a lot?

You can now right (or left as well, IIRC, I think it's assignable) click and drag on the timeline itself to highlight multiple events at once.

@fr0sty At the moment you can left click+hold then right click to get the 3 selection options. As I say left click + drag creates a region, how can you have 'click and drag on the timeline itself to highlight multiple events at once' without the current options changing, if they do change how do they is what I'm asking? Thanks.

I think this can be further customized, as well. @Gid

@VEGASDerek

https://www.vegascreativesoftware.info/us/forum/bezier-curve-bug--146534/
Will this be fixed in VP 22? I've pre-ordered it through 2-for-1 deal, but see no possibility that my bug will ever be fixed, nor have any developers answered me. I don't even know if anyone has submitted this issue...

First thing to note: The developers do sometimes drop in and comment on this forum, but that is not its purpose. This is a user forum, where we fellow VEGAS users help each other solve problems. The best way to be sure the developers know about your issues is to file an official support ticket.

Second, you just reported this a few days ago, and the team has been very busy getting 22 ready to release, so chances are they just haven't had the time to even look at the thread. Will it be fixed in 22 at launch? Unlikely... they'll need time to isolate the cause of the bug and implement (and then test) a fix... but perhaps in a post-launch update it can be fixed.

@Todd-AO

You're trying to divide and conquer, creating unrest amongst the public board beta testers.

You have a completely wrong understanding of the role of moderators and beta testers here. Nothing is divided - that alone is a lie and malicious insinuation. You are not the representative of other users, they are adults and of course speak for themselves.

Pierre is one of the great public board beta testers of all time

There is no public beta testing here, and consequently there are no great public board beta testers. So don't make a fool of yourself with this new insinuation. You are not the advocate of other users.

after every new release he's the one to first show and explain the bugs that the offical beta testers never found. I only speak of his unreliability with his mxf problems, and his testing, and also inability to describe how to action a fault while a fellow public beta tester could.

You don't know the beta testing process at all - and judging in your fantasies what you think you know doesn't correspond to reality. If a user finds bugs, they will of course try to reproduce them. But whether this succeeds, whether the things can be fixed, is a completely different question. Your arrogance of always attacking the volunteer beta testers is a clear violation of CR1.

You later look at the mxf thread that discover that for yourself, but still threaten to ban me.

It is exclusively your own behavior, and in fact only your own behavior, that is relevant here. The attempt to hide behind another user, to justify your own behavior with it, does not succeed.

I did not criticize Pierre's work in general, you created a straw man, as said he's brilliant at what he does, but even he may crack when he doesn't get the respect he deserves by way of acknowledgment from those he's trying to help .

We also don't generate a straw man. We try to help, we try to reproduce bugs - and partly we are successful with them. Of course, we are not always. But that doesn't justify your demagogic claims that we would degrade someone to a straw man. This is again a dialectical, malicious insinuation.

Here's an example from another forum, user describes bug, moderator replicates bug, lets user know it's been actioned, and I know that sometimes happens here, but mostly it doesn't.

There's a post by Vegas Dev in this thread I haven't got to yet, maybe he's showing us all the bugs they know about now and verified, that very good.

Beta testers and moderators are usually subject to an NDA. They are therefore still allowed to confirm whether they can reproduce a bug - and they do that quite often. I don't know why it is assumed that this would not happen here.

But they can't make a statement about whether a bug can be fixed. How could they, they don't know the complexity of correction in the software. 

All points together show that you are either not willing or able to take yourself by the nose - and cannot reflect on what you are actually doing here. This means that you are banned for a few days because of a constant violation of CR1.

Maybe you will use the time to think about how you can support the cause here - and to understand what we can accept here, and what we can no longer accept.

Let's not forget, I'll repeat it again here just to remind everyone, this is a USER forum. The developers are under no obligation to post here, they are under no obligation to confirm or deny that they know about any bugs, nor are any of the beta testers. The developers choose to engage when they have the free time to do so, and only then. If you want to make sure a bug report reaches them, the only way to do that is to submit an official support ticket. Even if support doesn't solve the bug for you, the team is still made aware of it.

I think this can be further customized, as well.

@fr0sty Thanks, that makes sense, at the moment right & left click+drag creates a region, it makes sense to change one of those to selection option. ( I never right click+drag, I use the left click+drag so I didn't realise both did the same thing)

Do you know how these three options work with that new design, is there still a left click+hold & a right click to change the selection?

A link to the help document with full descriptions and explanations of the new features is now available in the News Forum post.

@VEGASDerek

Derek.
I have a tip for you to make full use of the new explorer.
Since VP12 I have problem with windows explorer window.
If you mark all the files in the folder, the window freezes and takes a very long time to be functional. I have already posted a lot about this bug.

Tip for improvement:
Can you replace the old light window from Windows with a new dark one that is fully functional?

Clicking the Open link opens a dark explorer window.

It is pointless that VP22, which has an innovative explorer, still has an old explorer from Windows. No?

>the new features
Looks interesting!

But I have to admit to a bit of personal disappointment that there seems to have been no new improvements in the Video Preview window - in particular the ability for 3rd party OFX to overlay and interact controls on it. For example many BorisFX Continuum controls are much more useful/easier to use in After Effects and Da Vinci Resolve; I was hoping that perhaps the closer relationship between BorisFX and Vegas as evidenced by the introduction of Mocha Vegas might have resulted in such improvements.

I realise that I probably only represent a small number of users with such a desire, and understand you only have so much capacity for development. Maybe this is something on the backlog; I just hope it is near the top!