@BONLEV 😂 okey

How do I disable this notification? It’s annoying... every time I start up the program...

Hey!
I'm getting back to the frame skipping issue.
I noticed that if I restart the project before rendering, the frames where the skipping happens run normally... or how should I put it? The frame skipping disappears.
At least it’s a temporary solution, although it doesn’t seem normal to have to restart the editor and the project just to get rid of a bug… temporarily… because once you start editing again, it randomly comes back.

Purchase a new license???

Purchase a new license???

Aha… so it’s going to nag me for another 24 days… until I renew the license… wtf, Vegas?

Purchase a new license???

Aha… so it’s going to nag me for another 24 days… until I renew the license…

@BogdanRSC - it's WARNING (not nagging) you that it will stop working to give you time to do something about it - either extend your subscription or purchase a perpetual license or let it expire and quit using VEGAS.

Purchase a new license???

Aha… so it’s going to nag me for another 24 days… until I renew the license…

@BogdanRSC - it's WARNING (not nagging) you that it will stop working to give you time to do something about it - either extend your subscription or purchase a perpetual license or let it expire and quit using VEGAS.

That’s what I understood too… that it’s a “warning.”
But to bug me about it 3 weeks in advance seems a bit desperate to me…
They could’ve made the “warning” 3–5 days before the license expired.

That’s what I understood too… that it’s a “warning.”
But to bug me about it 3 weeks in advance seems a bit desperate to me…
They could’ve made the “warning” 3–5 days before the license expired.

And if you're out of town the week before and it expires while you're gone? I can understand starting the warning a month early.

Still no support for 32 bit audio as in GH7.

I posted previously on this https://www.vegascreativesoftware.info/us/forum/32-bit-float-audio-by-panasonic-gh7-xlr2-device-is-not-available--146930/

 

This is unfortunate. 32 bit audio files from the GH7 w. the XLR adapter are game changer in post audio editing. Vegas Pro 23 is my main editor and I thought for a long time that my mic and xlr adapter where misconfigured because there were no audio in the video files once imported to VP23.

Then I tested them in DaVinci Resolve and it played perfectly. The info is there. Hope that Magix can introduce 32bit support soon. I don't think I'll be going through the some effort to convert the files (and lose the benefit of using 32bit to begin with) when other editors can work with them natively.

I found that doing a conversion with ShutterEncoder to audio/32 bit float took a few seconds and is a lossless conversion. It yielded a wav file that loads fine in VEGAS:

https://www.dropbox.com/scl/fi/q129lx5x5jgd6wjcm2s5o/01-Float-32-bit-PGH70213.wav?rlkey=33w43hallmdyo668qvy2d0xt6&dl=0

I agree native support for this unusual combination would be better. My VEGAS 23 does open the audio in this MOV file but it sounds distorted.

Why doesn't my LUT work when I apply it? But other LUTs that come with the program do?

Anyone else having this problem?

What is your LUT? The ones I have load in the color grading panel and with the LUT Fx.

Qual é a sua LUT? As que eu uso carregam no painel de correção de núcleos e com o LUT Fx.

I load my custom LUTs. I select them, but they don't make any changes to the video. And when I select one from Vegas itself, it loads.

Is it a .cube file?

É um arquivo .cube?

yes! It appears in the Lut catalog, but when I select mine, it doesn't apply.

Is it a .cube file?

Is it a .cube file?

In the previous version (22) it works normally. It's only in version 23 that it's not applying.

You aren't providing much information. Can I test this LUT (can you send it to me privately?) My non Vegas LUTs are working.

Você não está fornecendo muitas informações. Posso testar essa LUT (você pode me enviar em particular?) Minhas LUTs que não são do Vegas estão funcionando.

Thank you so much, friend. I managed to do it. I just had to reinstall Vegas and it started reading my LUTs again.

Glad to hear it! Also there's a newer build than 278 that fixes various bugs.

https://www.vegascreativesoftware.info/us/forum/faq-where-can-i-download-vegas-pro-and-other-vegas-software--104782/

Hey!
I'm getting back to the frame skipping issue.
I noticed that if I restart the project before rendering, the frames where the skipping happens run normally... or how should I put it? The frame skipping disappears.
At least it’s a temporary solution, although it doesn’t seem normal to have to restart the editor and the project just to get rid of a bug… temporarily… because once you start editing again, it randomly comes back.

@BogdanRSC I see that you have 5xxx series GPU (I have a 5090), I experience probably the same type of frame skipping in VP23, in my case it is the occasional frame out of sequence.
The phenomena of the issue being introduced by a timeline play is exactly what I also experience.
Somehow the issue seems linked to a combination of 5xxx series, the new decoding method, timeline play (seems to store some decoded stuff in memory or disk), and maybe the type of media and project setting.
What kind of media you have and the project (I use 4K - 25P XAVC on a 25P full HD timeline)?
I have notified the developers about this issue for quite some time now, I hope they will fix it.
One of the best workarounds I found is to enable the legacy AVC decoding in the file/IO preference menu of Vegas 23.
Another workaround could also disable all HW decoding in the file I/O preferences, but I am not to fond of that workaround.
 

Hey!
I'm getting back to the frame skipping issue.
I noticed that if I restart the project before rendering, the frames where the skipping happens run normally... or how should I put it? The frame skipping disappears.
At least it’s a temporary solution, although it doesn’t seem normal to have to restart the editor and the project just to get rid of a bug… temporarily… because once you start editing again, it randomly comes back.

@BogdanRSC I see that you have 5xxx series GPU (I have a 5090), I experience probably the same type of frame skipping in VP23, in my case it is the occasional frame out of sequence.
The phenomena of the issue being introduced by a timeline play is exactly what I also experience.
Somehow the issue seems linked to a combination of 5xxx series, the new decoding method, timeline play (seems to store some decoded stuff in memory or disk), and maybe the type of media and project setting.
What kind of media you have and the project (I use 4K - 25P XAVC on a 25P full HD timeline)?
I have notified the developers about this issue for quite some time now, I hope they will fix it.
One of the best workarounds I found is to enable the legacy AVC decoding in the file/IO preference menu of Vegas 23.
Another workaround could also disable all HW decoding in the file I/O preferences, but I am not to fond of that workaround.
 

I use hardware decoding because I usually edit HEVC 4:2:0 10-bit.

With legacy AVC decoding it either freezes or crashes.

The workaround I’ve found is to ignore those frame-skipping issues, and before export I restart the project.

Without zooming on the timeline or doing any other edits, I just render.

So far, that’s what worked.

I hope they fix this problem and finally implement GPU decoding for HEVC 4:2:2 10-bit.

Otherwise, I’m switching to DaVinci 🤷

@BogdanRSC Ok I understand, legacy AVC decoding is not that great with HEVC. For me it is not an issue as my clips are not HEVC. Your workaround probably would also work for me, although without a prior check on the timeline before a render, it is pretty risky, because if the frame skipping/ frame out of order would be present, it is going to be rendered with the frame issue present.