I've never seen such an error before:
Conformance errors : 1 AVC : Yes General compliance : Bitstream parsing ran out of data to read before the end of the syntax was reached, most probably the bitstream is malformed (frame [0..23], time [-00:00:00.040..00:00:00.869], offset [0x7AEDF..0x55CF671])
I've never seen such an error before:
Conformance errors : 1 AVC : Yes General compliance : Bitstream parsing ran out of data to read before the end of the syntax was reached, most probably the bitstream is malformed (frame [0..23], time [-00:00:00.040..00:00:00.869], offset [0x7AEDF..0x55CF671])
That was a report from that clip, I don’t know that error either... right now I’m working on something else, and when frameskipping shows up again, I’ll make another MediaInfo report and I’ll also include the render and the raw clip.
I've never seen such an error before:
Conformance errors : 1 AVC : Yes General compliance : Bitstream parsing ran out of data to read before the end of the syntax was reached, most probably the bitstream is malformed (frame [0..23], time [-00:00:00.040..00:00:00.869], offset [0x7AEDF..0x55CF671])
That was a report from that clip, I don’t know that error either... right now I’m working on something else, and when frameskipping shows up again, I’ll make another MediaInfo report and I’ll also include the render and the raw clip.
there you go..
General
Complete name : E:\capturi\gheo\5 iunie 2025 - Nunta Ana & Alin\cam1\C7183.MP4
Format : XAVC
Codec ID : XAVC (XAVC/mp42/iso2)
File size : 128 MiB
Duration : 5 s 760 ms
Overall bit rate mode : Variable
Overall bit rate : 187 Mb/s
Frame rate : 50.000 FPS
Encoded date : 2025-06-05 12:14:21 UTC
Tagged date : 2025-06-05 12:14:21 UTC
Video
ID : 1
Format : AVC
Format/Info : Advanced Video Codec
Format profile : High@L5.2
Format settings : CABAC / 2 Ref Frames
Format settings, CABAC : Yes
Format settings, Reference frames : 2 frames
Format settings, GOP : M=3, N=24
Format settings, Slice count : 8 slices per frame
Codec ID : avc1
Codec ID/Info : Advanced Video Coding
Duration : 5 s 760 ms
Bit rate mode : Variable
Bit rate : 150 Mb/s
Maximum bit rate : 156 Mb/s
Width : 3 840 pixels
Height : 2 160 pixels
Display aspect ratio : 16:9
Frame rate mode : Constant
Frame rate : 50.000 FPS
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 8 bits
Scan type : Progressive
Bits/(Pixel*Frame) : 0.362
Stream size : 103 MiB (80%)
Writing library : AVC Coding
Encoded date : 2025-06-05 12:14:21 UTC
Tagged date : 2025-06-05 12:14:21 UTC
Color range : Limited
Transfer characteristics : BT.709
Metas : 3
Codec configuration box : avcC
Audio
ID : 2
Format : PCM
Format settings : Big / Signed
Codec ID : twos
Duration : 5 s 760 ms
Bit rate mode : Constant
Bit rate : 1 536 kb/s
Channel(s) : 2 channels
Sampling rate : 48.0 kHz
Bit depth : 16 bits
Stream size : 1.05 MiB (1%)
Encoded date : 2025-06-05 12:14:21 UTC
Tagged date : 2025-06-05 12:14:21 UTC
Other
ID : 3
Type : meta
Format : Sony Real Time Metadata
Codec ID : rtmd
Duration : 5 s 760 ms
Bit rate mode : Constant
Time code of first frame : 04:42:23:12
Stream size : 3.09 MiB (2%)
Encoded date : 2025-06-05 12:14:21 UTC
Tagged date : 2025-06-05 12:14:21 UTC
TransferCharacteristics_FirstFrame : CINE4 of EX1/EX3
ColorPrimaries_FirstFrame : BT.709
MatrixCoefficients_FirstFrame : BT.709
IrisFNumber_FirstFrame : 2.805783
FocusPositionFromImagePlane_FirstFrame : 0.594 m
LensZoom35mmStillCameraEquivalent_FirstF : 31.500 mm
LensZoomActualFocalLength_FirstFrame : 20.000 mm
FocusRingPosition_FirstFrame : 75.8026%
AutoExposureMode_FirstFrame : Manual
AutoFocusSensingAreaSetting_FirstFrame : Single Spot Sensing Auto
ImageSensorDimensionEffectiveWidth_First : 23.920 mm
ImageSensorDimensionEffectiveHeight_Firs : 13.455 mm
CaptureFrameRate_FirstFrame : 50.000 fps
ShutterSpeed_Angle_FirstFrame : 355.0°
ShutterSpeed_Time_FirstFrame : 1/51 s
CameraMasterGainAdjustment_FirstFrame : 3.00 dB
ISOSensitivity_FirstFrame : 200
ElectricalExtenderMagnification_FirstFra : 100%
AutoWhiteBalanceMode_FirstFrame : Automatic
ExposureIndexofPhotoMeter_FirstFrame : 200
i will upload more examples as soon the program starts glitching more and more..
I told you it happens randomly, regardless of the clip, codec, or anything else...
it happens just because that’s how Vegas wants.
You need to upload the actual clip, which can not be done by attaching it to your post. You have to use the cloud storage.
You need to upload the actual clip, which can not be done by attaching it to your post. You have to use the cloud storage.
here are the clips
https://s.go.ro/z6ez8ksc
@AUDIS-8 I download Youtube videos using 4K Video Downloader and they all play fine with VP23. All of them. So, how about actually providing one of the Youtube videos that are problematic?
You mention lag, what are your Preview settings?
BTW, my MP4's (all of them from Panasonic) play back just fine. MTS and other files from Canon do also.
Do you understand? Do you get it now?
@BONLEV can you upload a sample clip to the cloud to be tested? I have several MXF files, they play back ok.
I ulpoad the sample clip:
I did some testing with this mxf clip from my sony FX6. In vegas pro 21 build 208 I don't see this "glitching" when scrubbing through the footage on the timeline. In VP 22 and 23 I see it.
When converted this clip with handbrake to mp4 the issue is also gone gone in VP22 and 23.
At this moment I convert my mxf files to mp4 to avoid this issue.
Hope this helps.
Did version 23 also slow down rendering by half for you? My hardware hasn't changed, and after the update, I got this surprise :( Not to mention that this software doesn't like Radeons and has been constantly crashing the driver since version 16. But seriously. I'm seriously considering switching to another program. Back in the Sony days, there were no such jokes. I'm utterly disgusted.
Version 23 is 60 - 100 times slower rendering than version 22 when Event Pan/Crop is used for stills.
I seriously doubt pan/crop for stills is 60-100 times slower during rendering. I do it all the time.
@Karol-Kundzicz wrote:
Did version 23 also slow down rendering by half for you? My hardware hasn't changed, and after the update, I got this surprise :( Not to mention that this software doesn't like Radeons and has been constantly crashing the driver since version 16.
Let's see.... one post in all these years of using the software. No indication of what particular Radeon cards have been used, and no listing of computer hardware at all in the User Profile.
You have to give more specific information if anything is to be done, not generalizations.
As for Radeon cards, I've been using them since VP14-VP23 and the cards work quite well. My drivers are always up to date, and there is no crashing because of them, nor has been. I would have reported it if it had been the case in the over 4600 comments I've made. You can see in my Signature below what I am using and what driver. I am one of the rare all AMD computer user in the forum.
Render speeds... yes, they seem to be slower in VP23 compared to VP22, but not only for me, but for those that are using Nvidia cards too. Here is a POST on what AMD drivers other users have been using.
@BogdanRSC thank you for your files. The first one with the dancing and audio, at about 7.12 (7second 12 frame) there is a "skip" for sure.
The last clip, placing it at the beginning of the timeline, it "skips" at frame 25-27.
Sorry, I don't have a solution for this as to why it is happening. Recording media?
Dear friend, yes, I'm new to this forum and haven't filled out all the information yet. Regarding drivers, I always have the latest ones and keep them up to date. Vegas is the only program that crashes my drivers.
@BogdanRSC thank you for your files. The first one with the dancing and audio, at about 7.12 (7second 12 frame) there is a "skip" for sure.
The last clip, placing it at the beginning of the timeline, it "skips" at frame 25-27.
Sorry, I don't have a solution for this as to why it is happening. Recording media?
The dance video was shot with a Sony A7C II, and the other clip was shot with a Sony A7 IV.
This isn’t a hardware issue — no matter what camera you use, whether it’s Sony, Canon, or Panasonic, all the footage ends up with frame skipping.
The problem is in Vegas 23, and probably in 22 as well, because I never ran into this issue in Vegas 21.
It’s quite a serious problem, especially considering Vegas is trying to compete with DaVinci Resolve and Premiere.
They should really fix this serious issue first before asking people to pay for anything.
@Karol-Kundzicz you've posted that it has been crashing all the time since VP16, yet this is your first post? If I had constant crashing with any software for over 7 years, I'd look for another editing software or would have posted before now.
When it crashes, what happens? Do you get the error report dialog box and send in the necessary information?
@Karol-Kundzicz you've posted that it has been crashing all the time since VP16, yet this is your first post? If I had constant crashing with any software for over 7 years, I'd look for another editing software or would have posted before now.
When it crashes, what happens? Do you get the error report dialog box and send in the necessary information?
I've learned to live with it and often save projects. But recently, I've become interested in the topic and ended up here.
When the program freezes, the image disappears for a few seconds, then I get an error message from the AMD driver. Of course, I fill out all the fields and send a report each time. This doesn't happen every time I run Vegas, and it never happens at the beginning of working with Vegas. After a while, it seems to me that some buffer has filled up and then it crashes.
@Karol-Kundzicz just a suggestion.
Start a new post with more detailed information. To give you an idea of what is needed, read this POST and provide (some of which you have already) "B" and "C" in your post.
This is not normal behavior for AMD GPU's which some users have.
Did version 23 also slow down rendering by half for you? My hardware hasn't changed, and after the update, I got this surprise :( Not to mention that this software doesn't like Radeons and has been constantly crashing the driver since version 16. But seriously. I'm seriously considering switching to another program. Back in the Sony days, there were no such jokes. I'm utterly disgusted.
Version 23 is 60 - 100 times slower rendering than version 22 when Event Pan/Crop is used for stills.
Exactly, it's slow as hell, and they will do NOTHING about it - guess what, next year they gonna tell us that the next version is sooo much better and they changed soooo much "under the hood" - but NOTHING is going to happen, i dont even know why they bring out a new version every year as they literally change nothing and just make it worse and worse. Disgusting.
Thanks for that, there's nothing stopping you getting off the train at the next station while those who appreciate the benefits of Vegas over the years and the move to re-write the code to better deal with the evolving codecs and PC harware will stay on the train I'm sure.
@BONLEV Thank you for taking the time to reply to me! To be honest, while I was complaining here on the forum about the errors in Vegas Pro 23, by some miracle I managed to find the files that were causing the bugs I mentioned earlier.
I’m very grateful to the people who didn’t ignore my posts and gave me feedback. Thanks to you, dear people, and while trying to respond to you, I actually found the source of my problems and shared all the details and files on the forum so that the developers could see them and fix them.
As for the MP4 files from YouTube — that was my mistake. It turned out to be related to choosing between my Nvidia graphics card and the Intel Iris Graphics. When I set:
- Preferences - Video - Nvidia
- File I/O - Nvidia
With these settings, Vegas Pro 23 used a lot of RAM. But somehow, that issue also got resolved, and now I’m almost completely satisfied — almost everything is perfect!
Let’s just hope the VEGAS PRO developers read our comments and keep improving their work.
VEGAS PRO TEAM — YOU ARE THE BEST!!! @VEGAS_CommunityManager
Well… another problem for today in Vegas 23.
While saving a project, it crashed. And surprise… the project disappeared.
7 hours of work went down the drain.
I still can’t believe you have to pay just to get pissed off… 😠
@BogdanRSC There must be a .bak autosave file, no? You can rename it to .veg and continue from there. Or the advanced save feature which saves .veg periodically?
@BogdanRSC There must be a .bak autosave file, no? You can rename it to .veg and continue from there. Or the advanced save feature which saves .veg periodically?
Yeah, I found a backup…
after I posted my rant.
But things like this shouldn’t be happening… wtf??
It feels like this is the first version of Vegas, not version 23…
I'm so glad to hear that and agree losing a project file should never happen.
I never continue to save over the same file. I do incremental saves all the time. All the time.
I don't want to have to reproduce any major work that I will do in a project. I've been doing this way of saving "forever". And if I "think" Vegas is acting strange, incremental save, or Save As.