Maybe. But to deliver a patch that fixes such an issue within 2 days is a nice reaction time.
Double click on media files loads into trimmer instead of timeline, fix it please, thanks.
@RogerS Indeed you can, but it doesnt apply to media in the explorer and that inconsistency I find very annoying!
I want my double-click to be the trimmer from either source.
That the issue is with the Explorer wasn't clear to me as from project media it worked as I expected.
Maybe. But to deliver a patch that fixes such an issue within 2 days is a nice reaction time.
I totally agree, and the list of bug fixes is impressive. The problem, however, is that the information about what's new in version 239 gets lost in the long list of bug fixes. Maybe people who experience this problem are angry because they don't know that the problem has been fixed.
Jøran
I don't see the information about what was fixed in 239 in the release notes; these notes are relative to 194 (so don't have the regression in 237 with VFR media listed at all). I think that's just confusing for users who have 237, transparency would be better here.
@jjOn This is a preference you can set yourself.
But since V 22 it doesnt act as written :)
It works correctly for me V22 239.
@andyrpsmith it doesn't work for me V22 239. I want to double click into trimmer from explorer.
@Vincent-Brice @andyrpsmith @VEGAS_CommunityManager @jjOn
Double click on media files loads into trimmer instead of timeline. This still works normally from the Project media window, however from Explorer Window, it always drops it onto a track, which can overwrite existing clips or otherwise screw up your timeline if you're not careful. There are new buttons next to each file in Explorer Window and i think one of them does as we want, but that's too many button clicks. I think we all want it to go back to the way it used to behave, yes?
I've never imported clips that way from the Explorer in Vegas.
... i think one of them does as we want, but that's too many button clicks
While double clicking the file name does load the media on to the timeline, a single click on the orange/white icon just to the right of the file name under the Actions column loads the media into the Trimmer window:
One click rather than two clicks seems better to me and, nevertheless, double-clicking by habit on that icon still achieves the media loading into the Trimmer window.
Lut filter still uses all of VRAM and Ram the memory leak still exists on this build.
I have to agree that, in cases of a very rapid follow-up fix like this, I would prefer build 239 to be presented independently as a new release (with a separate post from build 237 in the News forum, and just that one fix in the release notes), rather than trying to present it as if build 237 never existed.
The last change ("yesterday") of https://www.vegascreativesoftware.info/us/forum/update-vegas-pro-22-build-239--148287/ now has added this text: (This build fixes the issue with variable frame rate media that was discovered with build 237.)
This version also has bad synchronization.
Please download this test project.
https://drive.google.com/file/d/1UfhBs3_nkoJaZ64_JgnX-HcL9dBV9yvx/view?usp=drive_link
There are two events in the project.
The one on the left has bad audio synchronization.
The one on the right needs to be shifted by 0.04 to be synchronized with the video.
Can you confirm this?
@all users from the OP:
"If you are having any issues using the update or have specific questions, please create a new thread."
That seems right to me, Pierre. Or to test it another way, if I line up the audio so they match the video is out of sync between the two.
General Complete name : C:\Users\rsmit\Dropbox\Videos\VP22 synchronization\VP22 synchronization\Clip0065.MXF Format : MXF Format version : 1.3 Format profile : OP-1a Format settings : Closed / Complete File size : 193 MiB Duration : 31 s 680 ms Overall bit rate mode : Variable Overall bit rate : 51.1 Mb/s Frame rate : 50.000 FPS Encoded date : 2024-11-14 12:19:54.000 Writing application : Sony Mem 2.00Video ID : 2 Format : AVC Format/Info : Advanced Video Codec Format profile : High 4:2:2@L4.2 Format settings : CABAC / 2 Ref Frames Format settings, CABAC : Yes Format settings, Reference fra : 2 frames Format settings, GOP : M=3, N=12 Format settings, wrapping mode : Frame Format settings, Slice count : 4 slices per frame Codec ID : 0D01030102106001-0401020201316001 Duration : 31 s 680 ms Bit rate mode : Variable Bit rate : 46.5 Mb/s Maximum bit rate : 50.0 Mb/s Width : 1 920 pixels Height : 1 080 pixels Display aspect ratio : 16:9 Frame rate : 50.000 FPS Color space : YUV Chroma subsampling : 4:2:2 Bit depth : 10 bits Scan type : Progressive Bits/(Pixel*Frame) : 0.448 Stream size : 175 MiB (91%) Color range : Limited Color primaries : BT.709 Transfer characteristics : BT.709 transfer_characteristics_Origi : xvYCC Matrix coefficients : BT.709Audio #1 ID : 3 Format : PCM Format settings : Little Format settings, wrapping mode : Frame (AES) Codec ID : 0D01030102060300-0402020101000000 Duration : 31 s 680 ms Bit rate mode : Constant Bit rate : 1 152 kb/s Channel(s) : 1 channel Sampling rate : 48.0 kHz Frame rate : 50.000 FPS (960 SPF) Bit depth : 24 bits Stream size : 4.35 MiB (2%) Locked : YesAudio #2 ID : 4 Format : PCM Format settings : Little Format settings, wrapping mode : Frame (AES) Codec ID : 0D01030102060300-0402020101000000 Duration : 31 s 680 ms Bit rate mode : Constant Bit rate : 1 152 kb/s Channel(s) : 1 channel Sampling rate : 48.0 kHz Frame rate : 50.000 FPS (960 SPF) Bit depth : 24 bits Stream size : 4.35 MiB (2%) Locked : YesAudio #3 ID : 5 Format : PCM Format settings : Little Format settings, wrapping mode : Frame (AES) Codec ID : 0D01030102060300-0402020101000000 Duration : 31 s 680 ms Bit rate mode : Constant Bit rate : 1 152 kb/s Channel(s) : 1 channel Sampling rate : 48.0 kHz Frame rate : 50.000 FPS (960 SPF) Bit depth : 24 bits Stream size : 4.35 MiB (2%) Locked : YesAudio #4 ID : 6 Format : PCM Format settings : Little Format settings, wrapping mode : Frame (AES) Codec ID : 0D01030102060300-0402020101000000 Duration : 31 s 680 ms Bit rate mode : Constant Bit rate : 1 152 kb/s Channel(s) : 1 channel Sampling rate : 48.0 kHz Frame rate : 50.000 FPS (960 SPF) Bit depth : 24 bits Stream size : 4.35 MiB (2%) Locked : YesOther #1 ID : 1-Material Type : Time code Format : MXF TC Frame rate : 50.000 FPS Time code of first frame : 04:57:24:38 Time code of last frame : 04:57:56:21 Time code settings : Material Package Time code, stripped : YesOther #2 ID : 1-Source Type : Time code Format : MXF TC Frame rate : 50.000 FPS Time code of first frame : 04:57:24:38 Time code of last frame : 04:57:56:21 Time code settings : Source Package Time code, stripped : YesOther #3 ID : 7 Format : Acquisition Metadata Format settings, wrapping mode : Frame Muxing mode : Ancillary data / RDD 18 Codec ID : 0D010301020E0000 Duration : 31 s 680 ms Frame rate : 50.000 FPS IrisFNumber_FirstFrame : 3.700123 FocusPositionFromImagePlane_Fi : 1.900 m AutoExposureMode_FirstFrame : Full Auto AutoFocusSensingAreaSetting_Fi : Manual CaptureFrameRate_FirstFrame : 50.000 fps ShutterSpeed_Time_FirstFrame : 1/50 s CameraMasterGainAdjustment_Fir : 15.00 dB ElectricalExtenderMagnificatio : 100% AutoWhiteBalanceMode_FirstFram : AutomaticOther #4 Type : Time code Format : SMPTE TC Muxing mode : SDTI Frame rate : 50.000 FPS Time code of first frame : 04:57:24:38
@all users from the OP:
"If you are having any issues using the update or have specific questions, please create a new thread."
I understand that this is how it should be. But first I want to check here whether it makes sense to open new threads. And it is more logical to discuss here the problems that arose in this version. If we cannot discuss new bugs here, then this whole thread is useless. What else should we discuss here?
Thank you for understanding me.
@pierre-k you seem to have posted a new comment about this bug now here:
I assume you want to continue there? The "specific questions" tend to get lost in these "general comment" threads.
Yes, I will continue there. Unfortunately, I cannot change the text of the thread, even though I started it once. I would need to change it to ....VP21 b300 - VP22. Still unresolved bugs with 4K MXF and HEVC files
Hi, folks,
Another timeline UI confusion in V22 - the ruler bars now are dark solid (not punctual and negative as in V19) that in selected audio event brings false clicks/ peaks visual appearance.
The same broken bars efect in trimmer window is even worse.
Can it be changed to the "old" look, thanks.