MAGIX business practice of only including 1 year of updates for a one-off license is absolutely pointless when 3-6 months are spent being a beta tester for the product.
I would suggest that you always wait six months after a product's release before buying it, so you can easily skip the “beta phase.”
Walter
MAGIX business practice of only including 1 year of updates for a one-off license is absolutely pointless when 3-6 months are spent being a beta tester for the product.
I would suggest that you always wait six months after a product's release before buying it, so you can easily skip the “beta phase.”
Walter
That would be ideal. However, a user would then only receive 6 months of updates.
If you don't want one thing or the other, then you're trying to square the circle—I wish you the best of luck with that!👍
Walter
There is only one thing wrong with Vegas, and that is the bug fix update cycle. They wait to long between bug fix releases. Just look at the sheer number of fixes in each release. To many for one release. They should bring out more releases in-between (with obviously fewer bugs fixed) than is the case now. Reason for it is the chances of introducing a regression bug is always present, and having more releases can rectify such bugs faster.
Anyway that is my personal opinion.
It would be preferable if VEGAS was 1 year of updates from the day of purchase as the version # aren't really in sync with the development cycle anyway.
Do you know which ring is a square?
Do you know which ring is a square?
This is a metaphorical expression meaning an impossible task.
Do you know which ring is a square?
Boxing.
After reverting back to the stable Build 302, every time I open VP 23 a requester box opens prompting me to update DLM Smart Mask 2 from V 23.1.0.1 to V23.1.0.2. This box also was opening when I originally updated to VP Build 356. DLM Smart Mask 2 has something to do with the VP AI engine, but is it specifically designed to work optimally with Build 356 or is it okay to update it when using Build 302?
I think it would likely work with 302 and hopefully fixes issues with NVIDIA GPUs and SmartMask. I haven't seen any user feedback on it though.
Cleaning up files and folders following upgrade from Vegas Pro 22 Suite to Vegas Pro 23 Suite - I am more than a little annoyed that Upgrade version from MAGIX appears to simply install another parallel program and not remove V22. Aside from the fact the Upgrade did not include Acid Pro 12 as advertised, I would be grateful to know how I can seriously verify what is new, and what can be removed in order to have one clean, full installation of the Vegas Pro 23 Suite. Has anyone experienced the same problems with the rather poor Installationsmanager - as MAGIX Support appears silent on providing a list of what is actually NEW?
@Anders-Berggreen, I would certainly not uninstall V22 right now considering the many reported issues with V23.
Thank you andyrpsmith - I guess from posts that Support team needs to remind Sales that customer service & complaints matter.
You can have several versions of Vegas installed at the same time, Vegas 22 and Vegas 23, and earlier versions. These versions are independent apps. Therefor, the installer should not uninstall existing versions of Vegas.
Jøran
So,
RogerS, are you going to pull the trigger on it, or wait...?
@Videoimpressions0622 At the moment I'm still on 356 with the new DLM. I'm not planning to uninstall the newer model even if I go back to 302.
If you don't want one thing or the other, then you're trying to square the circle—I wish you the best of luck with that!👍
Walter
Well, no... as stated I'm not updating.. so I'm not trying to "square the circle". But your eloquent description of the resolution does confirm the issue quite well. Good job. 👍
I'd like products that I buy to work. I know it's a MASSIVE ask, but it would be nice.
I'd like products that I buy to work. I know it's a MASSIVE ask, but it would be nice.
There is another saying on this topic that I really like.
“New products are like bananas—they are delivered green and ripen at the customer's end.”
But Magix is not alone in using this method; it is the case with many products.
It is up to us how we deal with it.
Walter
Previous build - could not preview with GPU acceleration (Radeon RX580).
GPU acceleration works with this patch but now the cursor does not move when previewing.
Sticks at the start point and only moves when I stop playing.
Back to V19 again......
If you don't want one thing or the other, then you're trying to square the circle—I wish you the best of luck with that!👍
WalterWell, no... as stated I'm not updating.. so I'm not trying to "square the circle". But your eloquent description of the resolution does confirm the issue quite well. Good job. 👍
I'd like products that I buy to work. I know it's a MASSIVE ask, but it would be nice.
I have a shocking solution for you. When a new Vegas is released, feel free to play with the Trial version but buy it before the next new version is released. It is usually fixed to a greater extent (even if with new bugs). Or don't buy the new version at all. Vegas doesn't yet bring such revolutionary news to be worth an annual update.
Recently moved from V12 (!) to V23 - due to new PC, new camera etc. Under V12 I could construct an HD 1960 x 1080 project and render this for DVD Architect blu-ray OR render down to SD 720 x 576 for PAL Widescreen DVD.
I can't find this render to SD option under V23, even though it is described in the user manual (see page 1112).
Any ideas where it is hiding?
Exactly. This is all I have after my V23 installation