I've just purchased and installed Vegas Pro 18. When in the "Event Pan/Crop" window, Vegas 18 will crash if I try to insert a keyframe.

I'm seeing the same on laptop and sent already a lot of crashreports.
Never had a reaction, lucky you see it also, look

Please state your hardware .

Yes, that's what I'm seeing also. It will crash the same way with any video or .jpg media.

My Error report is different from dcrandall's. The report would not copy for pasting , hence screenshot

Same here. Clicking "sync cursor" also causes a crash. Hardware in signature.

I've submitted a Support Ticket

I just tried it with XAVC-S and JPEG and it does not for this member of the Red team.

Working for me too with xavcs

This is such a basic function that it must be working for most users. It's not working for me, and at least 3 other people though.

I tested it only on my laptop from signature and at least @dcrandall has a laptop with same CPU and GPU (Nvidia) , so lets wait if others who see this have also that kind of equipment.
In about 2 weeks I'm back from vacation and I can try it on desktop.

Same here as OP... have only tested on my 9900k and xeon systems where I have my two v18 licenses installed. With jpegs on the timeline it also blows up if I so much as touch the clip-fx button. When I did that v18 audio editing walk-though, I did it most of it in v18 until I tried to add the pip-jpeg windows to the beginning as an after-thought... I had to switch to v17 for that.

This is weird. It works perfectly in VP17. Now I notice clicking on the fx button on the header clip crashes too.

I've spent all day trying various settings, re-installed VP18, run Windows dism.exe - all to no avail. Doesn't matter what file you add to a new clean project (avc long, xavc-s long even avi files) same result! Tomorrow I'll uninstall all my plug ins and introduce them one by one. I don't hold much hope though as all the plug ins I've used work OK.

How strange .... My fx seems to work OK, it's the keyframes that are wonky.

I just tried it with XAVC-S and JPEG on my intel 8550 laptop with the intel 620 and it does not fail for this member of the Blue team, either.

OS Name    Microsoft Windows 10 Pro
Version    10.0.19041 Build 19041
Other OS Description     Not Available
OS Manufacturer    Microsoft Corporation
System Name    DELL-5770
System Manufacturer    Dell Inc.
System Model    Inspiron 5770
System Type    x64-based PC
System SKU    0811
Processor    Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz, 1992 Mhz, 4 Core(s), 8 Logical Processor(s)
BIOS Version/Date    Dell Inc. 1.2.5, 2/20/2020
SMBIOS Version    3.0
Embedded Controller Version    255.255
BIOS Mode    UEFI
BaseBoard Manufacturer    Dell Inc.
BaseBoard Product    0XH3XD
BaseBoard Version    A00
Platform Role    Mobile
Secure Boot State    On
PCR7 Configuration    Elevation Required to View
Windows Directory    C:\WINDOWS
System Directory    C:\WINDOWS\system32
Boot Device    \Device\HarddiskVolume2
Locale    United States
Hardware Abstraction Layer    Version = "10.0.19041.423"
User Name    DELL-5770\John
Time Zone    Pacific Daylight Time
Installed Physical Memory (RAM)    16.0 GB
Total Physical Memory    15.9 GB
Available Physical Memory    10.1 GB
Total Virtual Memory    49.5 GB
Available Virtual Memory    41.6 GB
Page File Space    33.6 GB
Page File    C:\pagefile.sys
Kernel DMA Protection    Off
Virtualization-based security    Not enabled
Device Encryption Support    Elevation Required to View
Hyper-V - VM Monitor Mode Extensions    Yes
Hyper-V - Second Level Address Translation Extensions    Yes
Hyper-V - Virtualization Enabled in Firmware    Yes
Hyper-V - Data Execution Protection    Yes
 

Hello everyone, yes, I am having the same problem. Sent my crash reports; tried calling MAGIX. No response. Now I am dead-in-the-water, trying to complete a project. Reverted to Vegas 17. I wish I never accepted the upgrade offer until I waited for user community feedback on the stability of new software releases. Well, never again.

I have reinstalled VP 18.

Solved. Tried CTRL+Shift reset again (couldn't get it to activate before the reinstall) and all is fine.

Thanks very much to all for replying.

 I wish I never accepted the upgrade offer until I waited for user community feedback on the stability of new software releases. Well, never again.

First builds of a new version can be problematic for some users. VP18 has been okay for me thus far, but the release build of VP17 was not. It wasn't until the first update of VP17 that things settled down and it became useable.

At least you got VP18 at the intro upgrade price and you will get the upgrades for free, so please don't chuck the baby out with the bath water. And you've highlighted a problem that no doubt will be seen by the VEGAS team, and you've lodged a crash report like j-v did.

As has been suggested on the forum over the years, it's maybe not ideal to continue with an existing project in a new VP version right upon its release. But easier said than done because I've fallen for the same trap in the past.

When I got v18 the day it was released, I ran it through all the benchmarks and rendered a few older v16 and v17 projects and it was golden. I couldn't resist doing a project with it. Different story. I got a lockup pretty quickly so I restarted in v17 and managed to soldier on with v18 in parallel, avoiding v18 landmines I hit like track motion and event pan/crop... using pip-fx at the track level was a functional substitute. Found v18 very addictive and would generally get way ahead of the v17 clone in my editing. Was lovin' it right up till it abruptly crashed. Hitting cntrl-S allot caused the crashes to be less frequent and simplified recovery. Turning Live Save on under Advanced Save tools did the same thing. Was a learning experience for me, motivating me to work out most of the tricks to transfer edits from v18 back to v17 after every crash. Copying clips and saving/reloading FX as filter packages is easy enough. Found I could also copy and paste exact clip positions on the timeline using the Edit Details window set to Events. Same trick works for markers and regions. And the Envelope Edit tool can copy and paste track envelopes. Wonder if a script could do it all.