It's a VEGAS issue, the GPU is fine. Having this video file for download should help with the troubleshooting of it.
It's a VEGAS issue, the GPU is fine. Having this video file for download should help with the troubleshooting of it.
Yes @RogerS i found this issue now.
i change my Hardware decoder thing
i had changed it yesterday to intel to see if my last problem we are talking about in this thread, can be affected with it or not?
so now when i change it back. its gone.
my problem solved at this issue by shifting back on AMD, but even VEGAS can take it as bug or not, its on them.
I think there have been a number of decoding issues reported with AMD systems.
I think there have been a number of decoding issues reported with AMD systems.
it occurred again
i have to restart my Vegas to get it to back normal.
Do you have to use 300? There are many known issues. I'd use 208 if you need to get things done and come back when there's a fix.
how to get back to 208 now all projects are saved in 300
Don't start any new projects in 300; finish what you are working on with workarounds like converting media to ProRes.
Or copy and paste the timeline from 21.300 to 20.411 and then open the VP 20 project in 21.208.
original media i get from client.
https://www.swisstransfer.com/d/b652ac33-a679-4a0b-ac97-854642372e2a
Can't download the sample file successfully, but speaking of why '34fps', this is usually from cellphone video android. Yeah, the frame rate usually unstable.
Try moving your monitor to the motherboard hdmi connector which should be driven by its Intel igpu.
As said, we should try to re-work what is the issue with the files, that we have as download.
Can you open this project file (VP 21 b314) - maybe you have to relink your footage:
https://drive.google.com/file/d/1Krx_r8CemYcWFwhra-iEvtt-gnw7lsbQ/view?usp=sharing
As said, we should try to re-work what is the issue with the files, that we have as download.
Can you open this project file (VP 21 b314) - maybe you have to relink your footage:
https://drive.google.com/file/d/1Krx_r8CemYcWFwhra-iEvtt-gnw7lsbQ/view?usp=sharing
As said, we should try to re-work what is the issue with the files, that we have as download.
Can you open this project file (VP 21 b314) - maybe you have to relink your footage:
https://drive.google.com/file/d/1Krx_r8CemYcWFwhra-iEvtt-gnw7lsbQ/view?usp=sharing
still crashing..
what changes made in 314 it cause more crashes.
it was even opening in 300
take a look i opened your sending project also and also again by my side.
this was also Vegas reinstalled. with fresh downloads from trials.
if you are note facing any error please send me you export preference file. let me try that. atleast
Ok. Here is a version of the small test project, with the same files - but saved with VP 20 b411.
If you have also VP20 installed, please try to open that in VP20.
And - you should also be able to open it in VP21 b314.... at least here that works.
https://drive.google.com/file/d/1cpjqsa4VWUIgAegnMZg6k27Dj00JqK3f/view?usp=sharing
And here an EDL file, generated in VP21 b314
https://drive.google.com/file/d/1CoECyojdgWvbTOVRg51JPgqknK2FQBy-/view?usp=sharing
ok sir.... this is what happening, something which is working good in 20 is not working in 21_300 and then in new update 21_314 it is more worse.
if possible watch it till end by forwarding when u needed.
i dont know what is going on. just tell me whenever that type of clip will come i have to convert it. to AVC and Variable Frame Rate to Fixed Frame Rate only when there is one clip only and when i want to work in 21 only.
but whenever there are several clips like this properties i have to use 20.
uff...
i know this is only my issue right now..
i hope VEGAS team will work on it too.
please.
this is some information if you needed to helping in getting issue.
as display aspect ratio as per MediaInfo is ok in 20 but in 21 it is messing up.
as i ask to Gemini about this.
and also this
@Wolfgang S. as you can see sir.. crash problem solved after filtering from v20 but still stretching problem as it is not auto set pixel aspect ratio to Square Pixels.
I have to review your video in detail. May take some time.
I have to review your video in detail. May take some time.
no problem sir,, take your time.
I am not sure, if I understand everything what you have shown here. Sure, you have to re-link the media files in VP20. Sure, you have to adjust the PAR, both in the project settings and also for the event.
But what I have not understood is, what you mean by "crash problem solved after filtering from V20"? I have not seen that you had re-opend the project file, stored by VP20, with VP21 b314 again?
Yes, the PAR should be recognized in a correct way - this is one bug. But what about the crashes? Why are they gone?
Nevertheless, the information we have so far is sufficient. The team should examine the issue with the PAR. A report was created.
Concerning the stretch, you should also check the pixel aspect ratio in the event properties.
This needs to be set to 1,0000 (Square). That wasn't the case for me.
ok i got it.
my client's media file has pixel aspect ratio 3.1605
i need to change it to 1.000 from media side as you described not in project setting as i was trying before.
Downloaded this clip with the same results in vp21 b314. The metadata is unusual:
General Complete name : D:\2024-05-18 S23 tests\20240427_174438(imbly).mp4 Format : MPEG-4 Format profile : Base Media / Version 2 Codec ID : mp42 (isom/mp42) File size : 388 MiB Duration : 22 s 625 ms Overall bit rate : 144 Mb/s Frame rate : 60.000 FPS Performer : Galaxy S23 Ultra Encoded date : 2024-04-27 07:45:32 UTC Tagged date : 2024-04-27 07:45:32 UTC xyz : -38.5174+145.1167/ com.android.version : 14 Video ID : 1 Format : HEVC Format/Info : High Efficiency Video Coding Format profile : Main@L5.1@High Codec ID : hvc1 Codec ID/Info : High Efficiency Video Coding Duration : 22 s 625 ms Source duration : 22 s 617 ms Bit rate : 144 Mb/s Width : 2 160 pixels Height : 3 840 pixels Display aspect ratio : 0.562 Frame rate mode : Variable Frame rate : 60.000 FPS Minimum frame rate : 58.824 FPS Maximum frame rate : 62.500 FPS
I find it strange because I just tried to shoot the same with my own S23 which loads perfectly in Vegas. My metadata regarding the aspect ratio and orientation is totally different from yours:
General Complete name : D:\2024-05-18 S23 tests\20240518_133808.mp4 Format : MPEG-4 Format profile : Base Media / Version 2 Codec ID : mp42 (isom/mp42) File size : 113 MiB Duration : 6 s 434 ms Overall bit rate : 147 Mb/s Frame rate : 59.687 FPS Performer : Galaxy S23 Ultra Encoded date : 2024-05-18 17:38:17 UTC Tagged date : 2024-05-18 17:38:17 UTC xyz : +41.7826-069.9565/ com.android.version : 14 Video ID : 1 Format : HEVC Format/Info : High Efficiency Video Coding Format profile : Main@L5.1@High Codec ID : hvc1 Codec ID/Info : High Efficiency Video Coding Duration : 6 s 434 ms Bit rate : 146 Mb/s Width : 3 840 pixels Height : 2 160 pixels Display aspect ratio : 16:9 Rotation : 90° Frame rate mode : Variable Frame rate : 59.687 FPS Minimum frame rate : 59.682 FPS Maximum frame rate : 59.721 FPS Real frame rate : 60.000 FPS
Note that my shot is also in a vertical orientation but rather than reversing the width and height, metadata instead specifies a 90 degree rotation with a more regular aspect ratio. My Samsung S23 Camera app is v14.1.01.7 and indicates it is the latest version.
@iEmby I was curious about this when I looked at your MediaInfo, why is there is xyz, is this a lock rotation in the phone camera setting or something? Also there's aspect ratio 0.562.. ? Source stream size, do you upload via a streaming service to your PC somehow.?
Yours was created with a Samsung S23 Ultra, the same as my phone so I created one of my own which loads into Vegas without issues, (In Vegas mine shows pixel aspect ratio at 1.000), If you can share your phone settings I'll try it?
@Howard-Vigorita Hi, I was wondering what was going on with his files in this post from page 1, I'm former user, do you understand what is going on & why it say Source Duration below Duration on his file?
@Gid @Howard-Vigorita i don't know about this metadata.. actually its my client who use his phone to shoot videos and send me for add music, subtitles and overlays. so on that sunset video i face that issue. after than i ask her to don't shoot HEVC just shift setting to H264. so he did so.. now i dont have any issue.
but i thought that i should report this error. that's why i posted. I myself confused about this.
@iEmby It would be interesting to find out why both say "Performer .... : Galaxy S23 Ultra" but one has 'Source' (yours) but mine & @Howard-Vigorita don't have that in the info.
I just did a quick Google search but couldn't find out why 🤷♂️, I don't think it's as simple as the format change from AVC to HEVC, there must be some kind of conversion or something going on somewhere, maybe in the transfer to her PC from her phone, or to yours over the net, or some kind of editing that was done at her end.
The fact that it says Source suggests to me that MediaInfo doesn't think that is the orig file that came straight from the phone, but I'm guessing.
A lot of your other files don't have this Source in the info so maybe that rules out transfer over the net unless she uses a different transfer site to the other files you've shared. 🤷♂️