Sometimes when using the left-right arrows to go to a keyframe, the keyframe does not get selected and you have to click on it yourself. This is annoying but that's the way it is. So, click on the keyframe to turn it on - blue - and then delete.
BTW, you can select multiple keyframes and move or delete them.
I cannot reproduce the issue, either using your method as shown in your video clip, or by my method shown below using VPX 22.0.1.244, which patch version of VPX 16 are you using?
It is strange indeed, over the years I have come to the conclusion that subtle hardware and more likely Windows differences can make or break whether i can reproduce issues, I think this may be the case here.
I tested on my laptop, cannot confirm on PC for a few more days, however from experience, with Windows installations of 100+ identical PC's, subtle differences with a small percentage of them could, and did, occur.
I wrote the text with the test version (22.0.1.215 / UDC2). Note that last year, I only didn't buy it because after testing with VPX15 another annoying bug wasn't fixed (clips moved to the project folder are limited to one second). I contacted support, who confirmed the bug. So I figured that one year would be enough for them to fix it. So I downloaded this version to test and confirmed it again with a new ticket to the technical area. "This time even the owner noticed! " So I thought I should go deeper into the tests. Now I see that there is version ... 244! So I'm taking advantage of this question: do you have any history of the items that you fixed since this version 215?
My version of MMS214 doesn't have the same defect that I showed!
I can almost consistently show/repeat the non-selection of keyframes but it usually happens on the second time keyframing is used, that is a second object and beyond.
Try this. Put 2 images on the timeline. Apply Camera/Zoom Shot to the first - Custom, change the rectangle, move along the timeline, change the rectangle, a few times so get some keyframes. Use the arrows to go back and forth to the kfs.
Go to the second image and do the same. Use the arrows to go to next/previous kf does not select the keyframe - doesn't turn on blue.
Go back to the first image, arrows to select kfs works. Go the second, arrows don"t select the kf. The playback marker moves there.
Worse, but intermittent. On the second object, select a kf, change the rectangle. Occasionally a second kf gets put at that location. I see this as there is a jump and using the arrows to go to the kf, then when pressing to the next one the playback marker stays at that location as there is a second kf there. I just tried to reproduce this but can't. Grrr.
I have almost finished a tutorial on CZS and had a lot of trouble with this.
Image 1 - the KF's are added however the SPR effect in the keyframe pane is not automatically selected when the 1st and subsequent KF's are added. I have to click the SPR header to activate, and can then step through the KF's.
Image 2 - behaves the same as image 1.
Did I miss anything?
The duplication of a KF I have seen before and is as you say intermittent.
Roberto already wrote this: "I contacted support, who confirmed the bug and I had already been able to reproduce this problem".
John EB gave me this answer on September 28 at 13:28: "It is strange indeed, over the years I have come to the conclusion that subtle hardware and more likely Windows differences can make or break whether I can reproduce issues, I think this may be the case here".
After reading your answer and watching your video, you confirm my findings. Thanks👍 for that.
I will submit everything to Magix Support Germany.
Best wishes, Rob
PS. in Pro X13 on my other computer I was able to reproduce this BUG
While there is no update, I went to the forum to check the progress of the Vegas Pro 22 updates: 78 between fixed and improvements build 194: 51 build 122: 27
and vpx16 - zero ?
Regardless of whether they are software with different proposals, at least there should be competent responsibility regarding bug fixes!
(Black Friday promotions should start on November 5th)
I would like to respond to your topic regarding no updates? Regarding Vegas Pro updates, it is best to go to the Vegas Forum, this is the Magix Forum......
You write VPX16 - zero? I would like to point out that the last version 22.0. 1.244 was released for this in September 2024. Here are the changes in version 22.0.1.244:
Optimized subtitle generation
Localization adjustments
Notification when language-to-text quota is reached
Fixed crashes related to .tif files
Fixed misbehavior when importing, moving, cutting, or deleting a part of the video in storyboard mode
Fixed behavior during AV1 export in combination with NVIDIA GeForce RTX 40xx
Compatibility adjustments when using photos from the iPhone 15 Max
Yes, not 0, but not much was done and the few bugs that we have pointed out have not been fixed. It seems to me that Magix is not helping its cause by not fixing the few obvious bugs that we have pointed out. Robert's point was that compared to VPX, Vegas got a lot of attention.
The Project Temp Folder problem with trimmed clips, using the left/right arrows in the keyframe area not selecting keyframes (intermittent but easily reproducible) are the two main complaints that we have had. Magix should just fix them and be done with them. Two bugs - TWO! These should not be sitting there for a year waiting for the next version.
The other main problem that I have mentioned is not being able to open a wave file on the timeline in Sound Forge Audio Cleaning Lab 4 as we could for every version of SFACL and ACL and AML for the last dozen years. SFACL4 opens but without the wave file. SFACL3 and all previous versions open with the wave file. Just fix it!
In fact, fix the other two main problems with SFACL4 - the startup error, and the interface with SpectraLayers. Magix keeps refusing to do this and it is affecting sales. If they think that this is not important to users, just look at the SFACL4 bug video that I posted on my YouTube site. It has 1,875 views. Seems to me that others think that this is important.
Instead of fixing SFACL4, Magix created the new Magix Capture interface and messed it up as well. I don't recall anyone ever requesting for a new interface for recording video and audio, so why spend time on it. How did they mess it up? There is no mono/stereo option for recording audio. Audio is recorded at 44.1 kHz instead of 48 kHz for both audio recording and video with audio recording. Audio recordings are saved as MP3 files instead of Wave. My point is don't spend time correcting this interface, fix SFACL4 instead, and get more sales and allow us to promote purchasing SFACL4. More sales means more money. Fixing Magix Capture won't bring any new sales.
I don't think I have ever had a completely trouble free version of MEP / MMS or VPX. They seem to solve one problem (often one we don't even know exists or we suffer from in our personal workflow) and replace it with one or more problems that previously didn't exist that we do use.
Current instances for me are in MMS 2024 suite I have to go though the process of activating the program with it's registration every time I open it. OK it's only two more clicks but it's Annoying.
I have tried everything to get it to load without having to do that including a complete fresh instal of both the program and Windows.
In VPX 14 the Master effects are never saved in the audio mixer including the limiter. I've worked around it by using a third party limiter in the standard effects section on the master volume output which does save the settings.
I don't blame the developers for this but the people with the purse strings who were last listed as the private equity firm Capiton AG and that is a venture capital and private equity company so my hopes were never high after that news. Having said that the problems must have been there long before that for them to get involved. There has been no news on the current state of affairs at Magix since March.
Prior to that I've had problems editing audio, editing animated text with both of the internal editors refusing to load and until recently I have always had a system that met all running requirements but apparently that is no longer true if I wish to use A.I. with the newest releases which states I should have a 10th gen Intel CPU for minimum spec to use those functions that rely on it.
Where exactly did you find these update references? (From this post, I did a quick Google search and found them on websites but without identifying which corrections these numbers were made to 22.0.1.215 ... 1.219 ... 1.236)
.....Where exactly did you find these update references?....
Before I install an update, I click on a blue text in the update screen and then copy this data and save it. Unfortunately I can't give a print screen of this, but I will certainly do that for you with a next update.
....Yes, not 0, but not much was done and the few bugs that we have pointed out have not been fixed...
I can't really judge whether Vegas releases updates faster than Magix, because I focus more on questions regarding MMS/VPX, Photostory and Music maker. I do agree with you though, that Magix Capture interface is a big fiasco. As for your other comments, I will look into them at a more quiet time.
I have yet to encounter the first program that has been programmed completely problem-free and error-free. I know because I programmed a lot in various programming languages up until 1995. When you think you have solved one problem, two others have taken its place.
.....The current instances for me are in the MMS 2024 suite, I have to go through the process of activating the program with its registration every time I open it......
What you could do is to start VDL2024 as an administrator or do the following:
right-click on the shortcut
click on properties and then on Advanced.
check the box for Run as administrator c
click OK
The example is in Dutch
As for VPX 14 I will look at that at a later time.
I had already tried that. It was one of the first things I tried but thanks for posting anyway.
I thought after I had done a fresh instal of Windows that it would have taken. Possibly a hardware conflict somewhere is causing that. Apart from being mildly annoying it's not a game changer.
As for the VPX 14 problem. The workaround I'm using takes no longer to set up than using the 'correct' method and and the Tone Boosters limiter is more flexible.
I was just pointing out some of the current 'quirks' on my setup that haven't been present in the past. Apart from some other documented problems there is nothing currently that upsets my current workflow.
Compared to the problem I have had trying to get my emails from my service provider back online after getting booted off due to 'security concerns', and having to go through their security update procedure, the problems with either programs pale into insignificance.