Terje A. bergesen
Forum Replies Created
-
If you can upload the file somewhere (no need to include the media) some of us can try to open it in Vegas and see if it works for us.
—
Terje A. Bergesen : https://terje.bergesen.info/ -
[David Timar] “I tried to render the same project on 2 computers.”
Does the error occur on the same spot in the rendering process? If so there is a problem at this point, and it should be possible to isolate what that is. If it happens on different spots, the error is probably memory related or similar.
[David Timar] “What is Vegas doing when rendering to WMV???”
When Vegas renders to VMW it uses the Microsoft media encoder to do the job. Essentially Vegas just hands the frames to the Microsoft product and lets it do the job. The error message you are seeing actually looks like a Microsoft error message, but I can’t say for sure.
[David Timar] “Also, somebody said that Vegas can use upto 2GB of RAM. Well I don’t see a way to go above 1024MB in the Options”
The amount of memory Vegas can use is determined by Windows, and the limit is 2G. The 1024 option is not how much memory Vegas is using, just how much memory Vegas is using for a specific task. I’d recommend keeping this number very low for this particular task.
Other than this, I’d recommend trying Gary’s suggestion.
—
Terje A. Bergesen : https://terje.bergesen.info/ -
Dual core with 2G of RAM will make you a much happier person.
-
Just one more thing…
After only three attempts (Quicktime Pro crashed twice when changing settings after selecting Export) I was able to open a Vegas H.264 movie in Quicktime Pro and convert it to a .mov file with faststart and streaming download enabled. Since it already was an H.264 move, QuittTime Pro didn’t try to actually convert the movie, it just wrapped it appropriately. Thank goodness. The conversion would have taken hours (it took 10 minutes to encode in Vegas).
The movie was 320×240, 3 minutes, H.264 encoded at 768K. Standard online stuff. From clicking OK in Quicktime Pro until the movie was encoded for faststart streaming download took about 10-15 seconds on my AMD dual core box. Not including the QuitTime crashes.
So, the solution seems to be relatively simple. Get Vegas. Export in H.264. Use Quicktime Pro ($29 or whatever it is from Apple) to change the wrapper, and Robert is your mothers brother.
I’d get Sorenson though. At least they know how to write software for the PC that doesn’t crash constantly.
-
[lunchmoney] “Besides, these encodes are for web streaming/progressive download on a web site so I need the .mov wrapper. Even if the files did play after changing the extension to .mov, it still wouldn’t give me the wrapper with the faststart optimized for streaming that I need.”
Let me address one thing first. The email response you got from Sony support is absurd if that is the full response (and depending on what your question was). Vegas fully supports H.264. Both for editing (since 7e) and for export.
The information above was the information I was looking for when I asked you why you needed a Quicktime wrapper etc. I also think I can give you the answer. To my knowledge, at least I haven’t been able to find out how, the H.264 video file created by Vegas isn’t wrapped to enable faststart, streaming optimization etc. To support this in Quicktime you need the tools from Apple.
So, the answer to your original (incomplete) question is: Yes, Vegas fully supports H.264 export into a Quicktime readable format (leave the mp4 extension and it opens in Quicktime fine). It doesn’t appear that information pertaining to streaming, faststart etc is included. For this you need Quicktime pro, and this can not be invoked from within Vegas 7.
Are there work arounds? Yes. You can export to DV-AVI (or whatever format you would like) and do the conversion using Quicktime pro. This isn’t particularly hard, and given that the encoding it self is an insignificant part of your work flow, that alone should not be a gating factor in your purchasing decision. IMHO.
Other than that, again IMHO, if I was going to work with Quicktime and Apples tools, I’d buy a Mac. I have Quicktime pro on my PC and I have never in my entire life used software of such abysmal quality. Quicktime Pro crashes easier on the PC than would a house of cards built in New Orleans under Hurricane Cathrina. I love Mac OSX, and I love a lot of the products Apple deliver on the Mac, but whoever is in charge of Quicktime Pro for Windows should be summarily fired. It’s the worst piece of crap software ever. Oh, and when I (extremely rarely) can get it to encode something, it is also the slowest piece of junk H.264 encoder on the market today. By many orders of magnitude.
If you want to work professionally with Quicktime on Windows, forget about Apple and get Sorenson. Use Vegas for editing though. None better on the PC, IMHO.
-
…but just to be clear, if you didn’t understand DSE. You can export a Quicktime H.264 from Vegas, you can just change the file extension from .mp4 to .mov and all is well.
-
Sorry if I offended, just trying to help. As Gary pointed out, there was a rationale behind my question. Sorry if I offended you by trying to help, I will try not to try to help in the future.
-
To convert a drive to NTFS under Windows XP (2000 as well if I remember correctly), open a command-line window and run the following command:
convert /FS:NTFS x:
x above is the drive in question. If it is your only drive, replace x with C to get convert /FS:NTFS C:
If you convert the drive that has the Windows installation, it will tell you that it can’t do that and that it will convert it after a re-boot. A convert doesn’t destroy any data and it is relatively quick if you have some space available on your drive. Please note that you should take a backup of your data before you run this, you can never be too careful.
-
Seems like the ConvertXtoDVD program doesn’t work properly. You should use some other software to create your DVD.
-
If I want to render as H.264 and play it in the Quicktime player, I render it as H.264 using the MainConcept H.264 renderer. This plays on Mac and PC using Quicktime. The MainConcept renderer doesn’t use Quicktime wrapping. Please note that the MainConcept encoder can encode in any format H.264, from iPod to HD.
The Quicktime encoder in Vegas is for Quicktime 7, which obviously doesn’t support H.264.
My question to you is why it matters? Why are you asking, given that the wrapper is completely irrelevant. Vegas renders H.264 fine, for consumption on Mac and PC both. I can’t figure out why the wrapper matters. Is it critical to you whether the movie, which is identical, has a .mov file extension or a .mp4? If the .mp4 file extension bothers you, you could even change it to .mov, works like a charm. Still wouldn’t have a Quicitime wrapper, but that should be irrelevant.