Eric Vinyard
Forum Replies Created
-
CC 2015 solves this problem.
-
I can understand conflicts with software, but I don’t know of any sources that say codec packs irrevocably overwrite essential Windows files.
That being said, I’m fairly certain this is not my problem – from what I’ve read, Blu-Ray files use something that Windows thinks is AVCHD but is actually not, and which is also unsupported by Premiere. And, as it turns out, Vegas as well, I guess. I can’t for the life of me imagine why.
-
You… should probably not ever give advice to anyone. Ever.
-
I’m having the same problem. I have noticed, however, that if I export as non-multiplexed files and then multiplex them in TMPGEnc, the resulting .mpg file plays without the skips/pauses. I don’t understand why CS5 doesn’t seem to be able to render a multiplexed .mpg that doesn’t have these glitches. Terribly frustrating.
-
Interesting. Thanks for sharing, that’s really good to know. If you happen back on this thread, out of mere curiosity do you use NVidia or ATI? Or some third party (if one exists these days).
-
I’m not posting here to defend my position that I find Vegas’ full-screen mode unacceptable for my purposes, I’m posting to find out why it renders fullscreen video with lower quality than it renders it in a window, even when that window is stretched to a size equal to and even larger than the fullscreen preview.
This conversation was headed in the right direction when you mentioned that Vegas uses certain .dll files for fullscreen rendering which might be the source of the problem. Anything else is wasting my time and yours.
-
That’s an interesting bit of information about the .dll files, thank you for that!
I suppose I haven’t fully explained why the preview is so important to me, but it’s because I do commentary tracks for movies with a group of friends, and I’ve been using Vegas to record the tracks while we watch the film. That way everything is pre-synched and we can go back and edit the track as appropriate, or stop the movie and recording at the same time. Premiere has the same feature but I prefer Vegas’ editing workflow for sound. And since we’re enjoying the film on an external projector while we record, I really just want the clearest picture possible.
I’m not sure where to go next from here, except for perhaps testing other versions of Windows. I think if it comes to that I’ll just use Premiere for the initial recording and if I can’t get used to it for editing, import the files into Vegas for that.
-
Yes, I’ve tried that, and it has no effect. I wouldn’t really expect it to; pixellation is quite a different problem than interlacing artifacts. Also, I get the same results whether the source footage is interlaced or progressive.
I’ve toggled all of the options for “preview” and “preview device” in the preferences section and none of them have improved the way the image looks in fullscreen mode.
-
The original footage here is 720×480.
Keep in mind that the preview image is rendered properly both in Premiere and in the Vegas preview window, even when that window is dragged to the second desktop. It’s only in Vegas’ fullscreen mode on any monitor that the preview appears blocky even on the highest settings.
For instance: My primary monitor is 1920×1080. If I undock the preview window and then stretch it to fill the screen, the preview window remains smooth, even at such a high resolution. If I select my primary monitor as the preview playback monitor, however and then begin previewing the project in fullscreen mode, the image will suddenly look pixellated and blocky – just as it does on any digital secondary monitor I use.
In other words, I get the same results at all resolutions.
-
By your logic, the “PREview” window in Vegas would also be relegated to producing a shoddy picture, but it isn’t.
I really don’t care what other people are happy to get; it doesn’t change what’s happening here. It doesn’t change the fact that Premiere is clearly capable of rendering a superior image in fullscreen; it doesn’t change the fact that Vegas would be as well if it were using the same method that it uses to draw in a window.
If it’s a problem for me, then it’s a problem. Please stop trying to talk me out of the fact that I have one. 😛
Thank you for trying to help, but I think you may be wasting your time… I’m not interested in changing my perspective by settling for less, I’m keen only to figure out why Vegas renders a windowed preview differently than it renders a fullscreen one and whether or not this is normal behavior for the program.