I have been up and down this road with much intensity and found out numerous things.
All video is using some type of codec, large or small, that use up CPU cycles.
Here is what I do:
1) Matrox G750 video to external via Video Overlay
2) All videos are NTSC DV 720x480, QT .mov files. (they are digitzed via FCP from DVCam.)
I have a TFT LCD screen with less than 8ms latency. It is a 17" analog computer monitor.
I use this:
http://svideo.com/video2vga.html
This converters either Svideo or Composite to XVGA, and works really well. I have it set for 800x600 and all other controls can done with its remote (brightness, contrast, frequency, ect)
The latency between onscreen picture and external is not even a 1/2 a frame.
Rather than go into all the problems with QT and QT Alternative, I'll just say this. I have dumped them both. Wiped off the system.
You don't need them.
Cinepak Codec: Looks alright but not great.
But, for a 16 minute reel, you are looking at about an hour and a half for convertion.
Here is what you do:
1) download Rad video Tools:
http://www.radgametools.com/down/Bink/RADTools.exe
2) download this codec pack. It has everything and then some. It will play everything. Has QT ALT DS Filters, QT abilities and alot of codecs.
http://www.codec-download.com/latest/k-lite-mega-codec-pack-1.57-12125.html (http://www.codec-download.com/latest/k- ... 12125.html)
The 2 codecs I found to be the best looking as well as the least CPU hungry are these:
Intel IYUV and Indeo 5.11 or 5.2 (there is little difference)
With the Indeo there are some settings I still have to see if it improves the video quality
For example, a 720x480 pic looks nice and uses about 20-22 percent CPU but blurs in places when there is alot of movement.
So, Open Rad Tools select the source file and hit the convert button. Select your destination (default is .AVI).
I have found that the larger the dimensions, the greater the CPU usage.
So I am converting the NTSC DV file (720x480 native) to 320x240. (you can change the size with the furthest right 2 boxes.)
Intel IYUV, 320x240 uses about 8-11 percent CPU and looks the best. It looks better than the NTSC DV AVI.
Indeo 5.11 or 5.2,320x240 uses about 4-6 percent CPU but has a little grain to it and isn't as clear. (again, there are other settings I need to mess with to see)
Intel IYUV, 320x240 uses about 8-11 percent CPU and looks the best. It looks better than the NTSC DV AVI.
Indeo 5.11 or 5.2,320x240 uses about 4-6 percent CPU but has a little grain to it and isn't as clear. (again, there are other settings I need to mess with to see)
Update - Indeo 5.2 - 320x240 - Compression 100 (0 if the worst), Alpha Channel selected is a little better. There is still a little pixelation.
It would be fine for the least amount of CPU useage when you are under heavy CPU load.
You CPU meter of your sequencer isn't going to show you the CPU used from the video.
In Nuendo/Cubase a blank session with just video reads 0%, but in Task Manager it reads 22% when running a native DV. So don't be fooled into thinking that your video isn't using CPU cycles because your sequencer doesn't show CPU activity.
LEX
All video is using some type of codec, large or small, that use up CPU cycles.
Here is what I do:
1) Matrox G750 video to external via Video Overlay
2) All videos are NTSC DV 720x480, QT .mov files. (they are digitzed via FCP from DVCam.)
I have a TFT LCD screen with less than 8ms latency. It is a 17" analog computer monitor.
I use this:
http://svideo.com/video2vga.html
This converters either Svideo or Composite to XVGA, and works really well. I have it set for 800x600 and all other controls can done with its remote (brightness, contrast, frequency, ect)
The latency between onscreen picture and external is not even a 1/2 a frame.
Rather than go into all the problems with QT and QT Alternative, I'll just say this. I have dumped them both. Wiped off the system.
You don't need them.
Cinepak Codec: Looks alright but not great.
But, for a 16 minute reel, you are looking at about an hour and a half for convertion.
Here is what you do:
1) download Rad video Tools:
http://www.radgametools.com/down/Bink/RADTools.exe
2) download this codec pack. It has everything and then some. It will play everything. Has QT ALT DS Filters, QT abilities and alot of codecs.
http://www.codec-download.com/latest/k-lite-mega-codec-pack-1.57-12125.html (http://www.codec-download.com/latest/k- ... 12125.html)
The 2 codecs I found to be the best looking as well as the least CPU hungry are these:
Intel IYUV and Indeo 5.11 or 5.2 (there is little difference)
With the Indeo there are some settings I still have to see if it improves the video quality
For example, a 720x480 pic looks nice and uses about 20-22 percent CPU but blurs in places when there is alot of movement.
So, Open Rad Tools select the source file and hit the convert button. Select your destination (default is .AVI).
I have found that the larger the dimensions, the greater the CPU usage.
So I am converting the NTSC DV file (720x480 native) to 320x240. (you can change the size with the furthest right 2 boxes.)
Intel IYUV, 320x240 uses about 8-11 percent CPU and looks the best. It looks better than the NTSC DV AVI.
Indeo 5.11 or 5.2,320x240 uses about 4-6 percent CPU but has a little grain to it and isn't as clear. (again, there are other settings I need to mess with to see)
Intel IYUV, 320x240 uses about 8-11 percent CPU and looks the best. It looks better than the NTSC DV AVI.
Indeo 5.11 or 5.2,320x240 uses about 4-6 percent CPU but has a little grain to it and isn't as clear. (again, there are other settings I need to mess with to see)
Update - Indeo 5.2 - 320x240 - Compression 100 (0 if the worst), Alpha Channel selected is a little better. There is still a little pixelation.
It would be fine for the least amount of CPU useage when you are under heavy CPU load.
You CPU meter of your sequencer isn't going to show you the CPU used from the video.
In Nuendo/Cubase a blank session with just video reads 0%, but in Task Manager it reads 22% when running a native DV. So don't be fooled into thinking that your video isn't using CPU cycles because your sequencer doesn't show CPU activity.
LEX