I can say I'm not so disappointed in 8.1 as much as in 8.0c, because at least it seems more stable and so far it hasn't frozen when rendering a long timeline to AVC (fingers crossed).
But I just found a bug that again makes me think that those people at Sony Creative don't take Vegas too seriously.
One of the workarounds I use to save some time when I want to preview a few seconds in the timeline that might be too long for a simple RAM preview is to render to an MPEG-2 preset I made at half the size of the timeline (960x540). That way it renders a little faster than to 1920x1080 and since I have the timeline monitor set to 960x540, it works well for me.
Now, in Vegas 8.0b and c I used to do this all the time, but since I started with 8.1 a few days ago I noticed this huge bug. If you do a pre-render to 960x540, Vegas 8.1 changes the project properties to that size. I tried this several times and that's exactly what it does. I'm sure any of you will be able to reproduce this. And this change doesn't go into the undo queue. You have to go to the project properties and change it manually again.
Come on, how can Vegas be taken seriously by pros when it comes with these kinds of ridiculous bugs? This is yet another example of lack of proper testing before they launch a product.
But I just found a bug that again makes me think that those people at Sony Creative don't take Vegas too seriously.
One of the workarounds I use to save some time when I want to preview a few seconds in the timeline that might be too long for a simple RAM preview is to render to an MPEG-2 preset I made at half the size of the timeline (960x540). That way it renders a little faster than to 1920x1080 and since I have the timeline monitor set to 960x540, it works well for me.
Now, in Vegas 8.0b and c I used to do this all the time, but since I started with 8.1 a few days ago I noticed this huge bug. If you do a pre-render to 960x540, Vegas 8.1 changes the project properties to that size. I tried this several times and that's exactly what it does. I'm sure any of you will be able to reproduce this. And this change doesn't go into the undo queue. You have to go to the project properties and change it manually again.
Come on, how can Vegas be taken seriously by pros when it comes with these kinds of ridiculous bugs? This is yet another example of lack of proper testing before they launch a product.