Terje A. bergesen
Forum Replies Created
-
Well, the problem seemed to have been solved… I had installed Studio 9, it has drivers for a analogue capture card I use, and the problem appeared. I then installed Ulead DVD Workshop, and the problem went away.
Had to do a bunch of re-installs, just built a new “super computer” with the Athlon 64 X2 etc… Upgraded from a Pentium 2.0 GHz. Both with only 1G of memory for now.
First rendering test I did:
Pentium: 2 hrs 12 minutes
Athlon: 25 minutesand that is before I have tried to overclock the thing.
Total price for the Athlon about $1000.
—
Terje A. Bergesen -
[Jason Burkhimer] “f that is the case, then why does every 64bit related article mention digital video and content creation as one of the key areas that WILL benefit from the upgrade?”
Good question, I really don’t know. Most video editing requires a decent amount of RAM, but typically not enough to tax the adressing capacity of a 32 bit CPU. There is a possibility that this may change with HD video editing, it depends. With a 32 bit architecture you can directly address about 4G of RAM, currently probably two to four times what most people have. A 64 bit architecture allows direct access to far more RAM, but how effective is RAM in your video editing/rendering process? Assume you are currently using Vegas with 1G of memory, if you could chose, what would you do, double the speed of your CPU or double the amount of memory you have?
No doubt, the next generation of computers will require more memory, 4G of RAM will soon enough be a vague memory. At that stage you will be glad that you have a 64bit address space, but that in and of it self will not make anything faster.
—
Terje A. Bergesen -
The rendering speed increase is coming from a few different areas, better motherboard (CPU-memory interface) better and faster CPUs etc are the prime ones. There is nothing in the 64 bit architecture that in it self would make rendering faster.
People think that because moving from 16 bits to 32 bits gave us a significant performance increase, that there will be something similar moving from 32 to 64 bits. There won’t. For anything but the most specialized applications (nope, video is not one of them), moving from a 32 bits to 64 bits computing platform is a non-event.
—
Terje A. Bergesen -
Well, if you have two instances of Vegas running, that may take a bit of memory. I don’t see any reason to re-install Vegas, but if you do, you will not lose anything. The reason you have two instances of Vegas running is that you have started it twice.
The “easiest” cure is probably just to reboot, make sure you start only once instance of Vegas for your project, and render.
Remember that the way Vegas works is that it starts a new instance of Vegas each time you double click the project (.veg) file. This is by design and in this case a good one. Other programs open their data files in an existing running instance of the program when you doubleclick the data file.
—
Terje A. Bergesen -
I am not sure that you will be happy at the end of your wait.
There is nothing inherent in moving from 32 bit computing to 64 bit computing that will make applications faster. In fact, there are some things about 64 bit computing that may make it slower than 32 bit computing.
The main reasons for 64 bit computing would be for, for example, very large memory-mapped files or (for those with millions) access to huge amounts of memory.
—
Terje A. Bergesen -
Vegas will not capture through the USB port from your Panasonic. You should use, as the others say, Firewire to capture. If you do not have a firewire cable/port, you can use Windows Movie Maker (if you have Windows XP) to capture the tape, and edit in Vegas. I have the Pana GS400, my Firewire port is fried, and I capture like this. I will have Panasonic fix my Firewire port though, since it is preferrable for me to capture using Vegas, it can do scene detection etc.
—
Terje A. Bergesen -
With filter I mean, video filters in Vegas. There is one or two nice creative filters in Ulead MSP that do not exist in Vegas, for example a drawing type filter than can be fun to use in the right circumstances. I know you can accomplish the same in Vegas, I have read the newsletter, but it works better in MSP.
That is about the only thing I use MSP for now. Vegas is so much better.
—
Terje A. Bergesen -
I agree that using an intermediate form and then rendering the M2T file only once will probably yield the best result, you will still be rendering the entire MPEG2 stream which seems overkill if only a couple of transitions and some added text here and there is required to render. In other words, why not do what is done with a DV source, so that no render is done where no render is needed. I can’t see that there is a technical reason for this.
As to the higher bitrates for HDV, I am not sure that this means you have more detail to work with. Considering that HDV has much higher resolution and more color information than SD video, I would expect that a significant amount of the increased bitrate is consumed by the increased amount of information needed.
HDV is 25 MB/s where DVD is somewhere around 8-9 MB/s. Three times higher bitrate with a significantly improved resolution and colorspace isn’t that much.
Or perhaps I am completely wrong 🙂
—
Terje A. Bergesen -
This brings up a point I still don’t quite understand. HDV is MPEG-2. If you edit MPEG-2 in Vegas, it will recompress the whole thing on render. In other words, editing HDV with Vegas when the end product is HD quality MPEG-2 seem to be rather far from the ideal solution.
It should be possible to create a project in Vegas that matches the settings in the MPEG-2 file, edit, and have Vegas render only what actually needs re-rendering, as we have with DV. Or at least, one would think it would be possible…
—
Terje A. Bergesen -
Vegas can edit MPEG.
—
Terje A. Bergesen