Well thank you once again Magix. You have just managed to put me back 2 years. I took the chance on 306 because I was having crashing and freezing with 304 and now I am back to jerky unstable playback. I really don't know what the answer is here. You keep sending us half ass updates with absolutely no improvements for most users and then ask us how we like the update. "IT SUCKS" I'm wondering what my future is editing with this pig. I apologise for my rant but you are ruining my business. Fix the issues that you are getting feedback on "which you are asking for" and stop bringing out new features no one needs. Doug
I am dismayed about points 1 and 2, the missing icons. The reply that I received from Magix last week was that the programmers were not aware of this. How can this be? I reported this here with every patch. You have been getting valid feedback in these threads and we expect that you will follow up.
In the last couple of days, on a short project of about 5 minutes, with patch 306, I have experienced 2 crashes, actually freezes, as there was no error message. I had to quit using the task manager and restart VPX. In both cases, I was trying to modify a fairly simple title.
I noticed slowdowns on the timeline, just manipulating objects; restarting or rebooting solved the problem temporarily. Exporting the 5 minute project took about half an hour each time. I have a lot of effects, but no Neat Video. In one export, my one 3D title was not behaving correctly; it was fine on the timeline.
In another export, one clip was black. It was also black on the timeline for no reason that I could see. This had happened with some other clips during editing, a clip would go black, again, for no obvious reason. Restarting/rebooting solved the problem each time and I was able to export.
As for playback, well, that is always jerky, even after rendering a short section and playing it back. This is not new and I wonder each time why the rendered section, usually just a transition, does not play back smoothly.
The loss of the use of the Xara interface (the video does not show up in Xara) has been frustrating and I had to use various workarounds. This should have been fixed with patch 306.
Item 10, using external audio editors, is another frustration. I expect at least Video Sound Cleaning Lab to work properly, but it doesn't. As an aside (off-topic), and as I pointed out in the video that I submitted to Magix, VSCL does not allow VST's. There is no way that I could find to add the path to the VST's. This is ridiculous; Music Editor 3, which comes with VPX and MEP allows defining VST paths. VSCL, which is supposed to be a step up and costs more money, does not even have this standard feature of ME3. So what is the point of buying VSCL? Magix should fix this and issue a patch for VSCL - and fix the interface with VPX.
It is nice to have new features, but it seems that in doing so, Magix breaks something that worked previously. This has been frustrating, as you can see by the threads about the new version and the patches.
Merry Christmas and looking forward to everything getting fixed early in the new year.
So today I needed to purchase the yearly service agreement for $149.00. Now I cannot render a standard .mp4 without having my PC give me the blue screen. Rendering locks up, I have to hold the power on button 5 sec to shut down the PC.
Happens all the time, with different formats, tried .avi which resulted in lower cpu usage, and cooler temps, but then the audio was off sync, fading in and out. I really can't believe this. Trying to dvd now.
Update: made a DVD folder with no problem
Update 2: is it possible now that the blue screen is a result of my CPU not being throttled back somehow, I'm seeing very high system temps. Is my system shutting down on a .mp4 format, render to DVD seems to be working, with cooler temps.
That can be risky. I tried that once and it wiped most of my programs. It was like doing a complete format. I requested a download link to an earlier version from support but they didn't respond. The earlier ones have issues anyway.
This is hard to believe. After several failed attempts, I rebooted, started VPX again, and it gave me an error that it was already running, and gave me option to start it again, so I did. I had two sessions running, and it completed the render. I rebooted again, opened VPX, rendered the same task, no problem. Merry Christmas
The second one looks worse to me although the 3rd shot in the first one looks totally out of focus. The third HDTV 60fps one looks good.
What bitrate were the respective files rendered at?
That can be risky. I tried that once and it wiped most of my programs. It was like doing a complete format.
This should not happen with a simple rollback to an earlier Windows Restore point. AFAIK a restore point is automatically created when any program is installed. Are you sure you didn't choose a Windows Reset or Repair instead of a Restore to an earlier (most recent) restore point?
@Scenestealer Hi Peter. No, I actually did it from a restore point I created for the purpose of undoing the Magix mess. It only happened to me once but I haven't been game to try it again. Restoring back to an earlier version of VPX is no use because it's been no good since VPX 8. I tried to convince myself that moving from 7 to 8 and beyond was a good thing but this forum speaks for itself. I have read threads on the Vegas forum and it seems that as soon as Magix touched it, everything went to the dogs. I'm glad I still have VPX 7 to fall back on. Doug
Also, as I continue to experiment, rendering to mpg rather than mp4 makes a world of difference. The best I've seen so far. Original data 1920x1080 rendered to 1280x720, transitions are smooth.
Yes but did you use the same settings CBR, BR, etc. as the MP4? If not, I am sure the exported file size would be much bigger as Mpeg2 is a much less efficient compression algorithm.
I also noticed changing the framerate from 59.94 to 29.97 has no effect on file size.
This would be expected if you were using CBR at the same bitrate as the extra frames would be compressed twice as much to fit the fixed size of the Constant Bit Rate data stream.
Constant Bit Rate should be avoided if you want small file sizes and good quality for the reason John has pointed out plus you are wasting bits of the total available data stream on simple frames that can be efficiently compressed with fewer bits.
I seemed to narrow it down to the Main Concept Codec. Using the default creates a much better improved video, with smooth transitions.
Again, are we comparing apples with apples - were the export template settings identical?
Also, sometimes Magix tweak these template settings from version to version.