I have a fairly powerful machine by today standards without being extreme:
2.40 Ghz Intel Core 2 Duo
4 GB of DDR2 RAM (800 Mhz)
Intel D975XBX2 Motherboard
eVGA Nvidia 7950 GT graphics card with 256 MB of RAM
2 Western Digital Caviar SE with 16 MB of Cache (Video editing files are in the dedicated drive)
I'm running Vista Home Premium with SP1 (bought it with SP1 included and installed it from scratch). I checked that there are no unnecessary services running and the system is clean of malware, spyware and all that, I scan it often and make sure that it's clean.
However, when I load AVCHD files from my Canon HF100 in Vegas Pro 8 and play them from the timeline they play slow, depending on the action going on they might play at 7 fps and then maybe go up to 15 to finally stabilize at around 11, but it can go down again to even 5 fps. This is while having quality set to Preview (Full), and changing to Draft (Full) doesn't really make a difference. Setting any quality to (Half) will actually make it worse, I suppose because Vegas has to downscale on the fly.
This only happens when playing back from the timeline, if I choose the source file in either the Project Media or the Explorer tabs, they play at 29.97.
I checked my project settings, and everything matches the source files: 1920x1080, 29.97, upper field, pixel ratio square and color depth 8 bit.
My source files are 17 Mbps, but I tried older AVCHD files from a Panasonic SD5 I had, which were 13 Mbps, and the same happens.
Obviously there are no filters or any pan/crop applied to the events I'm playing.
I'm just wondering if it's that Vegas is slow for timeline playback, or if maybe I have something else installed in my system that is interfering with Vegas and making it play video so slow. Does anybody know if Vegas has its own internal codec engine for timeline playback, or if it relies on systemwide codecs for that?
I would think that with a dual core processor and 4 GB of DDR2 RAM my computer would be capable of handling AVCHD pretty well, so I think the problem might be somewhere else, but I hope somebody more knowledgeable can enlighten me.
2.40 Ghz Intel Core 2 Duo
4 GB of DDR2 RAM (800 Mhz)
Intel D975XBX2 Motherboard
eVGA Nvidia 7950 GT graphics card with 256 MB of RAM
2 Western Digital Caviar SE with 16 MB of Cache (Video editing files are in the dedicated drive)
I'm running Vista Home Premium with SP1 (bought it with SP1 included and installed it from scratch). I checked that there are no unnecessary services running and the system is clean of malware, spyware and all that, I scan it often and make sure that it's clean.
However, when I load AVCHD files from my Canon HF100 in Vegas Pro 8 and play them from the timeline they play slow, depending on the action going on they might play at 7 fps and then maybe go up to 15 to finally stabilize at around 11, but it can go down again to even 5 fps. This is while having quality set to Preview (Full), and changing to Draft (Full) doesn't really make a difference. Setting any quality to (Half) will actually make it worse, I suppose because Vegas has to downscale on the fly.
This only happens when playing back from the timeline, if I choose the source file in either the Project Media or the Explorer tabs, they play at 29.97.
I checked my project settings, and everything matches the source files: 1920x1080, 29.97, upper field, pixel ratio square and color depth 8 bit.
My source files are 17 Mbps, but I tried older AVCHD files from a Panasonic SD5 I had, which were 13 Mbps, and the same happens.
Obviously there are no filters or any pan/crop applied to the events I'm playing.
I'm just wondering if it's that Vegas is slow for timeline playback, or if maybe I have something else installed in my system that is interfering with Vegas and making it play video so slow. Does anybody know if Vegas has its own internal codec engine for timeline playback, or if it relies on systemwide codecs for that?
I would think that with a dual core processor and 4 GB of DDR2 RAM my computer would be capable of handling AVCHD pretty well, so I think the problem might be somewhere else, but I hope somebody more knowledgeable can enlighten me.