You're right. I redo the teste here and only happened with quick sync enabled. Apparently this is a problem that occurs when using quick sync.

No, it's more or less universal to call it 59.94i (fields) for HD and 29.97i (frames) for <720p. Makes no difference what one calls it, it's all the same.

I've checked this out with QSV on my ageing laptop. It does seem to be down to terminology. If a file including an audio stream is rendered with QSV then MediaInfo reports the "Frame rate" as 59.94 and the "Original frame rate" as 29.97. Without QSV, or without an audio stream (using the Blu-ray 60i template), you only get "Frame rate" reported as 29.97. All these files behave in Vegas as 29.97 frames per second / 59.94 fields per second. If you match your project settings to any of them it should be the same.

I blame camera manufacturers in the early days of HD/HDV, trying to make the specs of their cameras sound better.

For me the terminology is not a problem. The important thing for me is that it simply works as it should.

The problem is that when I pull the rendered file to the Vegas 15 timeline the playback in the preview happens fast and ends in half the time of the audio.

Vegas 14 recognizes frame rate 29.970i but preview playback and rendering are full of glitches. Premiere Also recognizes frame rate 29.970i and both preview playback and rendering are normal.

I frankly do not understand anything else. Why does such a simple thing have to be so complicated? I really like Vegas, but every day I run into a new problem. I do not even know if I expect new features or new bugs.

The problem is that when I pull the rendered file to the Vegas 15 timeline the playback in the preview happens fast and ends in half the time of the audio.

I don't see this issue with files rendered either with QSV encode mode or MainConcept encode mode. My old laptop has Core i7 4510U with Intel HD Graphics 4400.

Does it happen when you render with both QSV encode mode and MainConcept AVC encode mode?

What build of VP15 do you have? If it's not 361, then update.

What CPU are you using?

If you're running build 361, then my guess is that this is specific to certain models of CPU (certain versions of Intel HD Graphics).

Vegas 14 recognizes frame rate 29.970i but preview playback and rendering are full of glitches.

You're covering a lot of ground in that demo video. How VP14 renders Sony AVC in CPU-only mode is a separate issue really. You could make this easier here for everyone by slowing down and analyzing one issue at a time. Anyway, are you running VP14 build 270?

It is not simple, there is a learning curve, and a combined 40 years of experience is here trying to help you. So take a deep breath.

Please upload a sample to a fileshare.

Since file properties aren't giving us the full picture, your next logical step is to go into Source Media, change the frame rate to 29.97i, and render a test. Do report back.

Since your HD source header incorrectly reports 29.97, Magix qsv decoder (only?) may be misinterpreting it as another factor of 59.94. Doesn't happen too much, but the trigger in this case is the file header itself.

One thing I'm certain of: if this is to make it to a confirmed bug status, which is considered kind of a feather in your cap around here, the unpaid professionals who are trying to help you will benefit from a little more patience and even a bit of forgiveness for not being perfect the first time.

In case you are curious about how sequential troubleshooting protocol works, Nick has written a guide we can all benefit from. Read carefully, there will be a quiz ​

;?) https://www.vegascreativesoftware.info/.forum/important-information-required-to-help-you--110457/

This test was done in Vegas pro 15 Build 321 and 361.

This only happens when I use the intel quick sync rendering mode in the Magix AVC / AAC codec.

I think the problem is not the CPU. If the problem was the CPU this problem would occur in all software. Vegaspro 14 Build 244 and Premiere CC2017 here work without any problems.

It would be very coincidental that this happens only in Vegas Pro 15. The fact is that this is not right. That's the truth. I can not call the wrong of right and not the right of wrong.

Anyway I will avoid using the quick sink.

...I think the problem is not the CPU...

But you get the problem with your CPU, whatever model that is, and I don't get the problem with mine.

If this is a repeatable problem in VP15 build 361, please report it by submitting a support request. That's the best way to draw the developers' attention to bugs and get them into their backlog.

I say this by the simple fact that I also tested in Vegas Pro 15 the Sony / AVC / MVC codec that also uses the quick sync and is normal. So I believe it's the Magix AVC / AAC encoder. If the problem were in the CPU this would occur in both codecs since the two use the quick sync.

YOUR PROBLEM WAS EXPOSED BY FAULTY FILE HEADERS. Each QSV decoder is different. We believe you have a real issue; however, this is the first time wev'e seen it. If that werent enough, i just washed my crystal ball and i cant do a thing with it.

Upload a file. Try changing Source Media Properties. File a Magix Support Request. We don't work for them! Don't confront. If you want to speculate, it's better done on the Off-Topic forum. You are in a peer support area, and we are so dumb here, we don't know any other way. Anyway, Best of luck.

YOUR PROBLEM WAS EXPOSED BY FAULTY FILE HEADERS. Each QSV decoder is different. We believe you have a real issue; however, this is the first time wev'e seen it. If that werent enough, i just washed my crystal ball and i cant do a thing with it.

Upload a file. Try changing Source Media Properties. File a Magix Support Request. We don't work for them! Don't confront. If you want to speculate, it's better done on the Off-Topic forum. You are in a peer support area, and we are so dumb here, we don't know any other way. Anyway, Best of luck.

The goal of the post was only to report the problem and who might find a solution. I know I am among colleagues and in no way offended anyone. I just showed my opinion on the subject. If someone interpreted my opinion in another way this is not my problem. I am responsible for what I speak and not for what people understand. Thanks to all who have tried to help especially @Nick Hope, for whom I have great admiration for the knowledge and willingness to help everyone here on the forum.

Joelson, could you please share the file rendered by QSV in the Magix AVC encoder? Would like to see if it also decodes with a half-length video stream on my systems, so we can establish whether this is an encoding or decoding issue.

And would still like to know what CPU you have.

I suspect a couple of translation errors. If joelson is uncomfortable sharing his content, he should have said so up front.

Joelson, você poderia por favor compartilhar o arquivo renderizado pelo QSV no codificador Magix AVC? Gostaria de ver se ele também decodifica com um fluxo de vídeo de meio-comprimento em meus sistemas, para que possamos estabelecer se isso é um problema de codificação ou decodificação.

E ainda gostaria de saber qual CPU você tem.

Oi Nick, estou lhe enviando o link com o arquivo original e também com o arquivo transcodificado.

https://drive.google.com/file/d/12SWgI4li_Zgbmqh1EsDTDTyfNPmt4jZa/view?usp=sharing

Eu fiz este teste em um PC com o CPU Intel Core i5-3340 @ 3.1GHZ com 8GB de memória. Se você precisar de mais informações, basta perguntar. Obrigado!

Foi minha culpa ter enviado apenas o vídeo original no início do post. O correto seria ter enviado os dois vídeos (original e transcodificado). Desculpa por isso! 

Thanks. With your rendered file I can confirm that the video stream plays with the same type of errors that you experienced in both VP15 and VP14. So that seems to confirm that it is an encoding problem, rather than a decoding problem, and in my opinion it does seem to be related to the CPU/Intel HD Graphics version.

Yours (with problem): Core i5-3340 with Intel HD Graphics 2500

Mine (without problem): Core i7 4510U with Intel HD Graphics 4400

How old is your PC? I see that your CPU launched in Q3'13. This issue might just be something that affects older CPUs.

I suspect a couple of translation errors. If joelson is uncomfortable sharing his content, he should have said so up front.

@Musicvid Joelson shared the source file in the first post 👆😉

p.s. Please leave the files online for a few days so the developers can pick them up.

Yes, in my haste i thought the link was more properties. As a result of the heads up I shared privately with you last week, I am temporarily banning myself from the forum until I have completed my own grading tests (that other thread) and posted them in an informal survey, which I hope the nontesters will try to undermine.

At least that may appease my ego until this stuff begins to taper, knowing that the majority opinion will prevail, based on controlled, blind testing on a level playing field, as opposed to the background noise being generated by two missive-prone narcissists.🙃​​​​​

To keep me away from the keyboard for a bit, I plan to detail the car, pick up all the trash in the park, reread Carnegie, write a script for a TV pilot, repaint the master suite, and then after lunch maybe just kick back for an hour...

We've helped each other through some spots Nick, I've been told in advance this one will be short-lived. Calibrate your big monitor, because my tired eyes won't give me right feedback from the sensitive grading comparisons I'm about to take on.

Has the OP actually changed the source media frame rate as a temporary fix?

Or does he know where to access it?

-- The first thing one has to do to get out of a hole is to stop digging.

Thank you Nick!

Now I know I'm not going crazy and that the problem really happens.

@Musicvid I realize that you are a person with enough knowledge and your help will always be welcome. I was wrong and you and Nick were right. I saw that you also intend to help many here in this forum.

I ask you to reconsider the fact of excluding yourself temporarily, because surely your advice and tips will be greatly missed for everyone here.

Actually, I'm the one who's going to stop. I have a habit of testing everything to see if it works properly and this has given me a lot of headache and that's why I decided to stop.

Thanks also for your help and I'm sorry if at some point my immature comments made you feel bad. I am still learning and in the learning processes we all make mistakes.

Nick Hope, Marco and MusicVid are the best on this forum. Thanks for your help!

Nick Hope, Marco and MusicVid are the best on this forum. Thanks for your help!

Indeed. The wealth of knowledge in their posts during their participation on the SCS/Magix forums (43 years and 28+K posts between them) is astounding and has kept the forums going. Not forgetting a few other old stalwarts from the early '00s still around, of course. They know who they are. Thanks from me as well.

And vkmast, the one with perfect recall, has logged 101 solutions in under 2 years, second only to Nick. I downloaded your second file, and may have a stopgap fix for you later. Oh, welcome to our nuthouse!

I won't be gone long, to the chagrin of a few, it's just some meds that have a collateral effect on hyperlexia, the written kind.

https://en.m.wikipedia.org/wiki/Hyperlexia

Thanks, Mv, but at least Marco. is deservedly ahead there 😎

There are certainly many other names that deserve to be on the list. Everyone here is important and everyone is contributing in whatever way they can to help. Thank you all!