@Joe-is-Hungry-Channel wrote:
They did not fix the active Take information being missing when Track minimized even know they knew about it, Nice work guys!! I mean it worked in version 22 but you broke it in 23 and don't care to fix a known bug. Not a good look guys. Maybe the next update huh?
Do you mean the way this looks on my computer when the track i minimized?
I already mentioned it when the last update came, and I was told it was a known issue. I think the point here is when you are updating, is you fix more than you break. it has also got more crashes, in fairness I need to set this to default and give it a try. Hopefully they will at least address know bugs, they did not happen this update
Well, it is working as you can see on my computer in B356
... How on earth did you get a response so quick?
Helps to give them what they need. When I mentioned I had preserved the problem veg project that did the same thing on different machines, one being freshly rebuilt with it's 1st vp23 install, they apparently wanted to examine it being unable to reproduce the playback head freeze-up themselves. They were able to figure it out without my 4k media clip which is about an hour long. I think the bug reared its head on me when I hit the Maximize Track Height button to make it easier to edit the envelopes on the audio track. I managed to polish off the envelope edits on that project after my copy/paste workaround but I'm holding off using vp23 for any more envelope edits for now. If you don't use envelopes, or don't alter track heights, it might not be an issue. I'm in the video-edit phase of that project using a w64 mixdown of the audio track without envelopes in vp23 version with b356... so good, so far.
Well, I have to eat some very humble pie. B356 has gone bust for me. I now experience the cursor stuck where ever it is placed, and never moving as the audio plays back, but no video.
On top of that, I get the dreaded "Vegas is working" window which leads to "terminate or ignore". Doesn't matter, I can not work any more. Hours down the drain.
I'll try B302 again, but it was no joy for me before either.
Since B356 is withdrawn due to serious issues on several systems, it makes no further sense to discuss these issues here. Just revert back to B302 and wait for the release of the next build, which will hopefully solve all those issues.
I'm just afraid that such too early releases of buggy builds will push more Vegas users direction other NLE'S and will cause the premature dead of Vegaspro.
I must be the only one left with B356 working. As I do not have anything to edit at the moment and have V22 fully working great I will just leave V23 as is and see what happens until the next update is posted.
Also I posted that during the trial I rendered a project at 4K while others were restricted to 720p. Well I found a rendered file with the Magix logo over every frame and it was in 4K. I know why, it was because I rendered in AV1 with HOS Render+ in 4K.
@andyrpsmith I have also sofar no serious issues with B356.
So far, I've edited for 3 hours with B302 and everything is working fine. Lots of images, keyframing, parent/child tracks and most of them minimized since there are close to 100 tracks. Everything has been responsive, but I do save often incrementally. There were no changes done to the computer, and @EricLNZ nothing showing up in Reliability Monitor. What would happen with B356, I'd get the "Vegas is working..." then the option later to terminate or ignore. I tried both. I did cold boot of the computer, and still the issue was there, cursor would not move, audio would continue to play.
I'll "update" to B356 to see if it still works as it did before. It's Sunday evening, and while Vegas is updating, I can do something else.
I'm a sucker for punishment.... I gotta know....
Hi @Reyfox
I don't have your hardware expertise, and I conclude that I didn't encounter any problems that the developers probably already checked because they removed the post from the publicity! Even so, for me, version 356 is stable: I tested it minimizing, maximizing, changing sizes on average across 20 tracks, as well as wrapping with envelopes, in projects averaging 15 minutes. The cursor didn't give any unexpected signals, and in practically two days of testing, it rendered satisfactorily. Initially, I was happy with this version; I noticed more smoothness! One situation you could test is closing all loaded applications and deleting all files from the Windows temporary folder %temp%. In the posts I read about this version, I didn't find anyone who, in any test, only tested it in GPU-off mode to concentrate or not the problems involved with the graphics cards.
Thanks!
I just finished a 4-hour color grading session with b356 and I like it for that. I'm still working on the 38-minute long project that 1st broke b356 for me. But now with the enveloped audio track replaced by a w64 intermediate mixdown. Video-edits have been totally solid so far. Working on an 11900k/5080 machine with 581.59 Nvidia driver.