Hello,

Yes I am

https://i.imgur.com/rATdxpJ.jpg

Software was upgrade few hours ago, so it's a fresh today install.

This was a known issue with the German version that I thought had been fixed in an early VP15 build. See this comment: https://www.vegascreativesoftware.info/us/forum/known-issues-in-the-latest-version-of-vegas-pro--108942/?page=2#ca676139

Please report it by submitting a support request at https://support2.magix.com/customer/en/vegas/form , including as much detailed information about the problem as you can.

Which format are you rendering to?

The format can be seen in the first link I posted.
Magix AVC/AAC MP4, and it's as described in that comment above, except it's in Italian version and not in ProRes.

I will send a Support Request.

Hello and sorry for bumping this.

How long does it usually takes for support to reply back?

I'm not sure if my request went through, as I received this:

But I'm not seeing any YES!/NO buttons, so I replied to that instead, making me wonder if it went through :think:

You will normally receive a standard acknowledgement email from support@magix.net with the ticket number in the title. Thereafter you may or may not get a further email response about the actual issue. The timing varies greatly and it can take anything from days, to months, to never.

AnandaT told me that Support are aware of this issue and will fix it in a new patch.

Hey, it's me again.

Regardless what Support said, the issue is still present in the current version of Vegas (build 361).
Only way around that I've found is starting my preset from one of the default one that is already set at 59.94FPS, and if I don't touch it again, it will stay when I save.

Attached is a video with the issue in action.


 

Already started a new ticket with the Support..

Just because, I'm bumping this again to re-state that the issue is still present in build 387.

EDIT - But not in the actual latest build, sorry!

Build 416 is the newest version and there I see this

Build 416 is the newest version and there I see this

Oh wow, I was quite sure I was on the latest version already. My post above sounds quite stupid :D

Thanks for telling, I will check ASAP.

Thanks for the update. Can anyone with the German version confirm is this is fixed? I would like to remove it from the known issues list if it is.

To test, try setting a custom frame rate in the MAGIX AVC/AAC and MAGIX ProRes templates, and see if it "sticks" through to the finished render, rather than reverting to 23,976 or something else.

I believe the error was caused by use of a comma rather than period in some localized versions of Vegas.

I cannot repro this issue with VP15 build 387 (German localized) using ProRes (Magix Intermediate). And it works fine in some cases using Magix AVC, but in some others it doesn't. Will see how it's doing in build 416.

I now found in build 387 for Magix AVC rendering only the QSV render option ristricts the frame rate selection while using MainConcept doesn't.

Using QSV the render options are limited to standard values and as long as I type a value which conforms to the standard fps values it works fine. Only if I try to use non-standard fps values it jumps back to 23,976 fps.

Meanwhile I tested with build 416 and it's exactly same. So if this QSV render limitation is meant to be an issue it still exists. Or if it was something else it seems it was already solved in build 387. German localized.

But here this all is totally different from what AnandaT experiences which seems to be bound to NVENC rendering (and which I cannot check with Intel only grafics). For NVENC it seems that even selecting different fps values from the dropdown menu doesn't work and always reverts to 23,976. This never happens on my (Intel) system.