[RogerS, I dunno what happened to the quote, sorry 'bout that .... ]
Sorry, I haven't used 8 bit except in case of forgetting to enable 32 ever since I found that option because 8 bit is like printing on a Miller printing press with its plane 3" sidepieces while 32 bit is like printing on a M.A.N. UltraMAN or a Planeta with sidepieces from a foundry and will all kind of strengthening structures but of course; I ought have specied that.
I had put your post aside in my mind as something to look into because it looked like a highly probable solution, but ended up checking that preferences menu again and again and again for a couple of hours and tried in vain searching the online manual for V23 (great that all manual versions appear to be available, much praise!). It is in "[shift] Options\Internal" and NOT at all in the preferences menu. Yes, I know, mouse knows it is somewhere around there - I could have given the same incorrect route - but for me, who doesn't go there regularly, it was very confusing.
However, the suggestion is to the point, it was INDEED the very issue,.thank you for solving this!
What I do not understand is how it is an advantage to alter the display of a file, it is a great solution for the backlight issues when making video in that room with all its windows, but *if* I enable it, will what I render then look right displayed with other software - for instance after a detour over youtube and a browser or in VLC?
... tried in vain searching the online manual for V23 (great that all manual versions appear to be available, much praise!). It is in "[shift] Options\Internal" and NOT at all in the preferences menu. Yes, I know, mouse knows it is somewhere around there ...
@digilyd the trick is to press down on the Shift key before clicking on Options... then the secret Internal choice will display at the bottom of the drop-down menu.
... tried in vain searching the online manual for V23 (great that all manual versions appear to be available, much praise!). It is in "[shift] Options\Internal" and NOT at all in the preferences menu. Yes, I know, mouse knows it is somewhere around there ...
@digilyd the trick is to press down on the Shift key before clicking on Options... then the secret Internal choice will display at the bottom of the drop-down menu.
Thank you, it is well meant, but I did explain that.
[RogerS, I dunno what happened to the quote, sorry 'bout that .... ]
Sorry, I haven't used 8 bit except in case of forgetting to enable 32 ever since I found that option because 8 bit is like printing on a Miller printing press with its plane 3" sidepieces while 32 bit is like printing on a M.A.N. UltraMAN or a Planeta with sidepieces from a foundry and will all kind of strengthening structures but of course; I ought have specied that.
I had put your post aside in my mind as something to look into because it looked like a highly probable solution, but ended up checking that preferences menu again and again and again for a couple of hours and tried in vain searching the online manual for V23 (great that all manual versions appear to be available, much praise!). It is in "[shift] Options\Internal" and NOT at all in the preferences menu. Yes, I know, mouse knows it is somewhere around there - I could have given the same incorrect route - but for me, who doesn't go there regularly, it was very confusing.However, the suggestion is to the point, it was INDEED the very issue,.thank you for solving this!
What I do not understand is how it is an advantage to alter the display of a file, it is a great solution for the backlight issues when making video in that room with all its windows, but *if* I enable it, will what I render then look right displayed with other software - for instance after a detour over youtube and a browser or in VLC?
I'm sorry, I did write hold shift and go to options but did not explicitly say "internal" to find the menu. That's my omission.
The act of previewing is an alteration of the original file. I'm not sure what you are working with but the primaries and gamma may be different from regular Rec709 or 2020? For my BT 601 footage the reds used to show up as orangeish in VEGAS, because VEGAS didn't know how to interpret it. I thought it was a quirk of Canon cameras. However now the colors are properly mapped and red is red. I assume the same may be true for your footage where you are finally seeing what it's supposed to look like.
Or if something's wrong with the implementation of this new function there could be a bug? (Happy to test a sample file if you make one available).
When you render it should be what you see in VEGAS. VEGAS will change the data to standard Rec709 colors and gamma (or the format you choose if not Rec709) and then VLC, etc. will look the same as the VEGAS preview window.
RogerS, thank you, I'll get back to you, briefly my workflow is shoot multicam with Panasonic 990-series cameras, prep files - colour correction and if need be zoom in, sometimes I downrender to 1080p from 4k and imagemix to archive file for final editing.
Press alt-shift-4 you to go back and forth between full screen and regular view while playing back in real time.
Oh, and losing Voukoder, but Vouk is working on that.
Only for the paid for Pro version
@Reyfox Right now, I’m also going to get on my motorcycle and we’ll keep going))
These 2 changes I started talking about here, judging by your response, I understand no one noticed them, including you, and since no one cares except me about these two changes, just restore them.
The most important change is about the functions of the right and left mouse buttons. This is really important! Super important!!! Please give the option to customize the mouse buttons so the left button does what all Vegas Pro versions except 22 and 23 used to do, and the right button does the new action that the left button does now—and that’s it.
Look at the photo example.
Please take this note very seriously. And then restore the old function of the Esc key.
Look at how the Esc key used to work—this is how it should be restored.
Look at how the Esc key works now—that is completely wrong.
All my complaints come from genuine love for Vegas. I have been your longtime fan! Except for these two changes I described above—again, the mouse button customization is super important.
Everything else I mentioned is simply unacceptable for Vegas company in 2025.
Vegas 10 can still handle all kinds of video files without ever crashing. It opens quickly, like an iPhone icon. Vegas 10 served me with truth and honor for a long time. Then I switched to Vegas 20. A perfect replacement! The dark theme appeared—though not fully—but still. The video preview became more powerful, and the blue “Avatar” style splash screen was great. Everything was good until Vegas 23 appeared.
Vegas 23 is the most beautiful! Its splash screen is wonderful! Its dark theme is perfect! The new style is perfect, 10 out of 10! But...
This is already the third time I’m deleting this message and rewriting it, thinking about how to explain it so you would make these changes in the new Vegas 23 build.
Fix your most beautiful Vegas 23. Make it perfect. Vegas 23 crashes compared to Vegas 22—fix that. The same project works great in Vegas 20 and Vegas 22, but Vegas 23 crashes.
Also, Vegas 23 starts up like my grandfather’s old truck—it sparks, random windows pop up in the center of the screen, then a couple of windows swap places, then windows disappear completely, and then Vegas 23 pops out like a clown from the bottom left corner.
I wrote this comment so emotionally because after seeing how Vegas 23 starts I doubted that anyone on your team—or even on the forum—has eyes, if no one is speaking up. Unfortunately, it just shows that no one cares. There is no idealist on the team or among customers, as I understand.
And know this, Reyfox: if I had a million dollars, I would give it to you as a sign of respect to the company... and ask to make those changes with the Esc key and mouse buttons just for me in a special update)))))) That’s all, honestly, as it is.
It’s like a Samurai who has a sword in his right hand and a small knife in his left, and he’s been using that for 15 years. Then Vegas 22-23 come along and say to the Samurai: “Hey dude, now the knife is in your right hand and the sword in your left, now go fight.” Isn’t that right, Reyfox?
So please give the samurai his sword back in his right hand! 🗡️🥷
Respectfully - Anonymous.
hello!
any news on an update that fixes freezes, crashing when canceling rendering, support for rtx50 series gpu's .. and fixes for other bugs?
@EricLNZ & @johnny-s & Friends from VEGAS TEAM
I hope their best minds visit the forum and read the messages. If not, I’ll personally show up at their office and insist on it. Thanks to you, friends, for letting me know. Honestly, I thought Reyfox was one of the programmers, but it’s no big deal, and it’s kind of funny because of it)))) Victory will be ours))))
AFAIK all magix developers that post here have a name that their first name part has “Vegas”
FYI: The MAGIX employees/VEGAS team members can be recognized from this hexagon graphic attached to their avatar. Green means he/she is online.The developers keep an eye on these forums and may post and comment here from time to time.
Other contributors (including forum moderators who have an "M" in their avatar's hexagon graphic) are peer users and not MAGIX/VEGAS employees or members of the VEGAS team.The lightning bolt hexagon graphic is for "Power Users" (appointed by admin).
hello!
any news on an update that fixes freezes, crashing when canceling rendering, support for rtx50 series gpu's .. and fixes for other bugs?
We have a patch just about ready to go with a number of fixes in it. We currently waiting on some infrastructure changes to be completed at the Magix offices before we are able to release the patch. The RTX 50xx improvements are currently being worked on and we hope to have this ready to go for the first major update (slated to be released before the end of the year). I plan to post information soon on the User Insights section of the Hub window that will give an update to features and improvements that the team is currently working on.
@Reyfox Right now, I’m also going to get on my motorcycle and we’ll keep going))
These 2 changes I started talking about here, judging by your response, I understand no one noticed them, including you, and since no one cares except me about these two changes, just restore them.
The most important change is about the functions of the right and left mouse buttons. This is really important! Super important!!! Please give the option to customize the mouse buttons so the left button does what all Vegas Pro versions except 22 and 23 used to do, and the right button does the new action that the left button does now—and that’s it.
Look at the photo example.
Please take this note very seriously. And then restore the old function of the Esc key.
Look at how the Esc key used to work—this is how it should be restored.
Look at how the Esc key works now—that is completely wrong.
All my complaints come from genuine love for Vegas. I have been your longtime fan! Except for these two changes I described above—again, the mouse button customization is super important.
Everything else I mentioned is simply unacceptable for Vegas company in 2025.
Vegas 10 can still handle all kinds of video files without ever crashing. It opens quickly, like an iPhone icon. Vegas 10 served me with truth and honor for a long time. Then I switched to Vegas 20. A perfect replacement! The dark theme appeared—though not fully—but still. The video preview became more powerful, and the blue “Avatar” style splash screen was great. Everything was good until Vegas 23 appeared.
Vegas 23 is the most beautiful! Its splash screen is wonderful! Its dark theme is perfect! The new style is perfect, 10 out of 10! But...
This is already the third time I’m deleting this message and rewriting it, thinking about how to explain it so you would make these changes in the new Vegas 23 build.
Fix your most beautiful Vegas 23. Make it perfect. Vegas 23 crashes compared to Vegas 22—fix that. The same project works great in Vegas 20 and Vegas 22, but Vegas 23 crashes.
Also, Vegas 23 starts up like my grandfather’s old truck—it sparks, random windows pop up in the center of the screen, then a couple of windows swap places, then windows disappear completely, and then Vegas 23 pops out like a clown from the bottom left corner.
I wrote this comment so emotionally because after seeing how Vegas 23 starts I doubted that anyone on your team—or even on the forum—has eyes, if no one is speaking up. Unfortunately, it just shows that no one cares. There is no idealist on the team or among customers, as I understand.
And know this, Reyfox: if I had a million dollars, I would give it to you as a sign of respect to the company... and ask to make those changes with the Esc key and mouse buttons just for me in a special update)))))) That’s all, honestly, as it is.
It’s like a Samurai who has a sword in his right hand and a small knife in his left, and he’s been using that for 15 years. Then Vegas 22-23 come along and say to the Samurai: “Hey dude, now the knife is in your right hand and the sword in your left, now go fight.” Isn’t that right, Reyfox?
So please give the samurai his sword back in his right hand! 🗡️🥷
Respectfully - Anonymous.
That's how I feel seeing all the bugs and issues rolling in for vp23. I've been using it for TWENTY years because of how fast, efficient and intuitive it is. VP21 felt like it was going in a wonderful direction... EXCEPT for a ludicrous amount of crashes and the inability to play back certain footage (that every other nle can do) smoothly without proxies. I know it's a small company, I THINK they are trying but my goodness it feels like more like a side hobby project than a professional video editing software development company. I tried vp23 and still no ability to playback AVC or HEVC 10bit 60fps footage without proxies. A full day's wedding worth of footage takes an entire day of lost time to proxy everything, let alone the time lost due to 3-5 daily crashes while editing. I know the playback will never be better at this point but there's NO excuse for the instability and crashes. I'm so willing to shell out full price for new versions too if the software functioned properly. Just like you said, all respect to them, it's not personal, but if we're going to be paying we should also expect to get software that's not broken and actually improves over time.
AFAIK all magix developers that post here have a name that their first name part has “Vegas”
FYI: The MAGIX employees/VEGAS team members can be recognized from this hexagon graphic attached to their avatar. Green means he/she is online.The developers keep an eye on these forums and may post and comment here from time to time.
Other contributors (including forum moderators who have an "M" in their avatar's hexagon graphic) are peer users and not MAGIX/VEGAS employees or members of the VEGAS team.The lightning bolt hexagon graphic is for "Power Users" (appointed by admin).
Of course if your using say a smartphone then the hexagons contents are not visible and it's necessary to click to view.
J'ai un problème avec l'audio (Vegas Pro 23). Lorsque j'importe une vidéo .VOB (venant d'un DVD) ou un fichier .MP3, la piste audio affiche le message "(Pics non disponibles)" ou "(média déconnecté)", donc, pas de son. Avec un fichier .m4a, j'ai du son mais c'est saccadé, entrecoupé. !?! C'est quoi la solution ? Merci d'avance.
@AUDIS-8:There's an option
@VEGASFlorian Too bad the selection edit tool only selects events and not envelope points... if it could select envelope points for dragging or deleting, we wouldn't need the envelope edit tool which is broken in vp23.
Is there a way to use Mocha Vegas in VP 23? I was sad to learn it was not included anymore, I am holding onto VP 22 until I know I can find a tracker that is affordable and works well. When I tried the built in Motion Tracker in VP 23 on a simple shot, this was the result... I really hope that I am doing something wrong and someone can educate me.
Mocha Vegas is not included in V23.
Constantly, constantly, constantly crashes. Not been able to use it for more than 5 minutes. How about fixing the old inherant bugs first or push out an uipdate that resolves the terrible stability?
@Mark-Hinson there is zero way for anyone to know what you are referring to. How about starting your own new thread with information from this POST, especially "B" and "C" if you really want help. You have zero info in your User Profile so no one knows what your computer hardware consists of, what project media you are using (not "MP4" but specific file info and what created them), at what point does Vegas crash, etc, and what "inherent" bugs are you referring to.