Why can't select multiple audio events & change their properties?

Sorry I'm confused.Are we talking about event(-bridged media) properties or event setting properties?

Why can't select multiple audio events & change their properties?

The "technical" reason is that you work on an event/mirror which can be bridged back to its source/source-properties.But a bunch events selected means bridge breakdown. It's not audio only, multiple video events also lose their bridge in this matter.Event has no properties -> Insert Empty EventThat's why there're event-, track- and media-levels. You can fulfill your requirement in Mediapool.

MXF rendering problem picture is sqeezed

MXF rendering problem picture is sqeezed

Forget your "highest quality", you are looking for an intermediate format with better quality. Do you know where to compare it? Here: VideoID                          : 1Format                      : ProResFormat version              : Version 0Format profile              : 422 LTCodec ID                    : apcsDuration                    : 18 s 535 msBit rate mode               : VariableBit rate                    : 434 Mb/sWidth                       : 3 840 pixelsHeight                      : 1 620 pixelsDisplay aspect ratio        : 2.40:1Frame rate mode             : ConstantFrame rate                  : 59.940 (60000/1001) FPSColor space                 : YUVChroma subsampling          : 4:2:2Scan type                   : ProgressiveBits/(Pixel*Frame)          : 1.164Stream size                 : 959 MiB (100%)Writing library             : magxLanguage                    : EnglishEncoded date                : UTC 2023-03-14 13:08:20Tagged date                 : UTC 2023-03-14 13:08:20Color primaries             : BT.709Transfer characteristics    : BT.709Matrix coefficients         : BT.709 ideoID                          : 2Format                      : AVCFormat/Info                 : Advanced Video CodecFormat profile              : High 4:2:2 Intra@L5.2Format settings, CABAC      : NoFormat settings, GOP        : N=1Format settings, wrapping m : FrameCodec ID                    : 0D01030102106001-0401020201323001Duration                    : 18 s 535 msBit rate                    : 545 Mb/sMaximum bit rate            : 600 Mb/sWidth                       : 3 840 pixelsHeight                      : 2 160 pixelsDisplay aspect ratio        : 16:9Frame rate                  : 59.940 (60000/1001) FPSStandard                    : ComponentColor space                 : YUVChroma subsampling          : 4:2:2Bit depth                   : 10 bitsScan type                   : ProgressiveBits/(Pixel*Frame)          : 1.096Stream size                 : 1.18 GiB (100%)Color range                 : LimitedColor primaries             : BT.709Transfer characteristics    : BT.709Matrix coefficients         : BT.709Delay_SDTI                  : 65700  1st one is ProRes-422LT 2nd one is Sony MXF AVC-Intra

MXF rendering problem picture is sqeezed

Reason that you must render it in MXF container?

MXF rendering problem picture is sqeezed

Membership since 2016...Brille, Fielmann.

Rendering freezes

Yes, selecting a portion of the timeline. It's nothing to do with any portion of the video, but there is a problem with video load from the layers. I have used 6 video layers, but when I removed a few, it was able to render successfully. Does this mean that Vegas Pro has some limitation with the number of video layers? NO! More possible your HW: with Intel i3 8GB RAM.  

Export 16-bit PNG?

Then the rendered still is exact 16bit: 4x16=64bit.And in ACES it's 32floating=128bit. Funny is, snapshot if saved in HDR10-mode, it's 8bit ST2084 color space (also with alpha-channel).

Export 16-bit PNG?

It can only create 64bit or 128bit (ACES-mode) depth stills.

[bugs] Vegas 20 - summary (I hope) of the VST crashing issues

...is that no one from Vegas ever answers and support is not existing. Sure!Even us the users won't follow you, else you report the concrete issue that is reproducible under certain HW and project environment and so on. How much you did spend or how long you do your job does really interest nobody.    

[bugs] Vegas 20 - summary (I hope) of the VST crashing issues

You msut have bought a faked VEGAS. 😬😬 These days half the posts are from you, and we even don't know what HW you use, what a project you build and what parameters you did or didn't changed in the e.g. app preferences, etc...😌😌😌

[bug] Explorer is breaking parent / child relationship

My sympathies for your suffering, such a long period. My movie just showing VEGAS explorer doesn't torture me, where I've established my media libraries and use them every day.

[bug] Explorer is breaking parent / child relationship

New project to use for benchmarks...

OH, No!I mixed up the test with that from @Howard-Vigorita, I'll make a try for this thread in minutes. AVC   HEVC  

New project to use for benchmarks...

@Reyfox I was hoping you'd post your times and I reckoned you'd be around 8 seconds for the AI test which would validate my 7 seconds... But 3 seconds! We are doing it right aren't we? 😧 We need more AMD's to post. Where are you @Yellandkeil ? Do you mean my AVC-Rendering? It's similar as the HEVC-Rendering, AVC=03:23min, HEVC=03:26min.   Be frankly, such test is not very meaningful for me; I do HDR10, never use AVC and stability is the highest principle. I've just rolled AdrenalinEdition back to 22.5.1, with the newer driver 23.2.2 I got better performance but had (a small) problem with the 2nd screen preview switching between HDR/SDR. Anyway quite satisfied with my HW thus less comparison with/to the other, and the next upgrade would be in 5 years or so.  

AndrenalinEdition New Version 23.2.1 Awesome

Didn't try it before, here your wish: AI-Section=00:16Project including AI=02:41

What determines whether a camera can record video in 8-bit or greater?

@john_dennis, may I point out?If your project is 8bit full, it means the preview window is working in sRGB space, so your waveform should be set to sRGB, too. If the waveform is set to monitor signal's luminance - Y channel - its peak can and can only be allowed till 100%, no matter what signal from SDR. Or you will produce non-standard video?Salut, soldier!  

What determines whether a camera can record video in 8-bit or greater?

You should know somehow the develop history of TV-video. After YUV colorspace is born, the 420, 422 sub-sampling comes more and more refined, i.e. bandwidth allows from 8bit to 10bit to do finer sampling and save/transfer it. That time it was only in the definition Rec709.  Advanced technique then let camera went to 10bit422...Logs gradually, etc. etc. The Rec2020 definition afterward comes never to practice, or as it's mature, the HDR format appears.  

What determines whether a camera can record video in 8-bit or greater?

The data transfer bandwidth/speed determines.

Sony FDR-AX700 and Colour Space of Sony's XAV-S Videos

😁😁 I AM so silly that I forgot to tell him which preview window my scopes are monitoring. Ohyeye. 😰😰😰 I swear, from now on never reply silly and Silly.Bye.

Sony FDR-AX700 and Colour Space of Sony's XAV-S Videos

Assuming you're about producing traditional TV-videos and won't go 32bit...blabla, you have 2 choices for project-setup:  1, 8bit legacy. This mode does tough neither your edit invironment nor properties of the footage you put onto timeline. Say you are editing with a computer monitor (its color space is sRGB or its color range=0-255), then you adjust all your footage right on the timeline till you're satified and, by rendering out, add the levels filter to limit your signal to 16-235 (that's the TV-video's color range).  2, 8bit full range. This is the idiot-easy mode presuming you alread sit in front of your computer monitor. Footage that you put onto timeline will be determined which color range they do have, if it's limited (16-235) then VEGAS expands the range to 0-255. After you finished your edit and go rendering, VEGAS converts your timeline signal automatically to standard TV-color range.  2.1, During the edit if you find VEGAS's expansion is absurd and cuts too much details of your footage, you also can adjust the footage color range manually and vice versa.  3, So, forget your Sony FDR-AX700, forget XAV-S, any source footage with no matter what kind range are all welcome in VEGAS.  For production, your project must aim at parameters/properties of that product instead of source material which can, may and dare vary.  4, Be assiduous and take some time to study the scopes till you know how they function and what they are monitoring. I can assure you, asking in any forum is the most silly way. Forgive my rudeness. 

AI FX in VP20 build 326 - working great for some

Tested on my system. Total render time: 3:18 GPU is not utilized much. Hmm, 8 sec less than me; whether your HW config better or Winpro11 better. 👍👍

Vegas pro 20 wont open vids after the recent update on feb 01 2023

You've almost turned over the whole forum!While you found the solution and forgot us, we're so anxious about your safety. 😱😱And ours, what's happened on feb012023!? 😁😁😁 Please mark your found-a-way-around-it as solved and tell us HOW.

Sony FDR-AX700 and Colour Space of Sony's XAV-S Videos

MediaInfo does transfer meta-data, does NOT analyse content/signal.The Info is 100% accurate thus.