I'm just glad I invested in Continuum some years ago for the perpetual, and have upgraded each year. It is an amazing kit of plugins.

I totally agree. Some 10 years ago I cross-graded from Red and Graffiti to BCC and have been on the BCC 'hamster-wheel' ever since. One of the great features of many BCC FX is access within the FX to basic Mocha (so not Mocha Pro) which allows spline masking/tracking thus limiting the FX to selected areas of the image.

Vegas 23 Pro. Vegas Screen Capture is not working.
First time the Stop Button is not working.
Now i have now no screen is avaible to capture.

Same here in the trial

Hi, this is my problem, when I split an event with keyframes, the new half has the same keyframe pattern, even if the split was after the keyframes that now appear in this new half, do you know if it is a new feature of vp23 or if it is really a bug (if it is the first, how do I turn this off? It's annoying)

Don't add the keyframes before splitting? You are splitting something with them included. They will be there, should they not?

... when I split an event with keyframes, the new half has the same keyframe pattern, even if the split was after the keyframes that now appear in this new half ...

It has always been thus. One way to get around that issue is to render the video event with pan/crop keyframes in place and then split the rendered video - the keyframing is then already embedded in the rendered video. If fearing generational loss by rendering, use a no loss render such as an applicable ProRes render template or an applicable .AVI render with custom settings set to 'Uncompressed'.

@ISPanesLocos

... when I split an event with keyframes, the new half has the same keyframe pattern, even if the split was after the keyframes that now appear in this new half ...

It has always been thus. One way to get around that issue is to render the video event with pan/crop keyframes in place and then split the rendered video - the keyframing is then already embedded in the rendered video. If fearing generational loss by rendering, use a no loss render such as an applicable ProRes render template or an applicable .AVI render with custom settings set to 'Uncompressed'.

@ISPanesLocos

But this only happend me in VP 23 in another versions (22,21,18) the new part of event after divide dont duplicate keyframes,and another detail that I forgot to mention is that it only happens in the keyframes of the effects, such as Image in Image here a video:

Hi, new to VP23, cannot get it to work on capture - Microsoft DV camra an VCR setting, capture boxes just blank, my Sony decks play perfectly into Win 11 PC using WinDV, bu nohing on Vegas capure,

any help or suggestions please

thanks James

Hi, new to VP23, cannot get it to work on capture - Microsoft DV camra an VCR setting, capture boxes just blank, my Sony decks play perfectly into Win 11 PC using WinDV, bu nohing on Vegas capure,

any help or suggestions please

thanks James

Forgive the silly question.

Do you have any Third-Party Firewire Drivers installed? They tend to wreak havoc and the usual culprits are the ones coming from manufacturers (Leonovo, Dell and such)

I'm not clear on whether you're using a laptop or PC workstation, so I'm scenario building here.

@James-Menday Vegas Capture is a screen capture app, not for capturing from DV cameras. You will have to continue using WinDV. The ability to capture from DV and HDV devices with Vegas was discontinued several versions ago.

@James-Menday Vegas Capture is a screen capture app, not for capturing from DV cameras. You will have to continue using WinDV. The ability to capture from DV and HDV devices with Vegas was discontinued several versions ago.

Edit: NEVER MIND. I just realized my mistake. He wants TO CAPTURE/IMPORT videos from a DV camera.

Woops
----------------

I don't think this is exclusive to Screen Capturing.

My Panasonic GH5 is hooked onto my PC and acts as a video input when using VEGAS Capture. My understanding of VEGAS Capture is that its meant to act as a user-friendly OBS.

I know DVCameras are outdated but they should still work.

Thanks for input to my problem,

A bit of a rant here sorry all but.....

I am at a loss that VP23 has a new dedicated Vegas capture 2 app, that specifically states, Microsoft DV Camera and VCR input, but it does not work ?

My PC enables me to input material from my two Sony VCR's and if I plug it in, my Sony camera, using the Microsoft DV Camera and VCR input, however this is a two step process, playing in the material, then importing it into VP23.

I would have thought that VegasCapture 2, with the id of Microsoft DV Camera and VCR input as an input and on the device explorer tab, which allows you to select..."import files from your camera and other devices" would take a step out of the editing process, but apparently not. I raised this with VP support, and after three AI generated messages in reply, I eventually got a responce which said ...there are no further specific solutions in the current knowledge base for this, continue using windv option!

Not the responce I was hoping for from the company who has taken my money!

@James-Menday I think it's just finding all the potential video sources your system has installed; it doesn't mean they are supported.

According to reddit people Magix is ​​no longer developing Vegas 23; they are now focused on Vegas 24. You should keep that in mind.

According to reddit people Magix is ​​no longer developing Vegas 23; they are now focused on Vegas 24. You should keep that in mind.

@NewVegas22 ... Could you please provide a link to that Reddit post ... and was the Reddit comment posted by someone who really knows - like a MAGIX/Vegas staff member?

@NewVegas22, I'm betting "reddit" is wrong!

We've made no announcement about a VP 24 or anything in regards to our release schedule, so it would appear that people are making things up. And I follow Reddit closely and there has been no widespread speculation about updates or new version...so...I'm not entirely sure what all the noise here is at the moment.

The main reason for the pull back of build 356 was the UI update problem which was widely reported here on the forums. The Vegas team continues to work at a rather feverish pace right now.

According to reddit people Magix is ​​no longer developing Vegas 23; they are now focused on Vegas 24. You should keep that in mind.

I'm on Reddit VEGAS Pro frequently and we didn't discuss a claim like that so I think you're misreading a post (about the NVIDIA driver?).

Anyway what VEGASDerek says is authoritative so please report that back to whoever you are discussing this with.