Brian Mackenziie
February 28th, 2006, 06:27 AM
Hi guys
I have just installed the Premiere Pro 2.0 Tryout on my Matrox RTX100 system (P4 3Ghz, Windows XP Pro SP2, 2Gb RAM, 250Gb SATA RAID-0 plus other IDE) and am having problems with capturing in Matrox AVI format.
I have previously worked with both Premiere 6.5 and Premiere Pro 1.5 on this system without too many problems, other than for the fact that the RTX100 driver would occassionally cause the machine to hang when first booted. This was a minor issue as it happened perhaps once in every 10 boots and was resolved by rebooting the machine. It was irritating enough however that I decided to set up dual boot and move Premiere Pro and Matrox to a new copy of Windows XP, booting from another hard disk.
As I was installing from scratch I decided to give Premiere Pro 2.0 and Matrox XTools 6153 a workout, and have been very pleased with the result, bar the anomally I describe below.
All worked well - both partitions boot as intended, the original partition loads more quickly and without ever hanging, and the new partition is clean except for Premiere Pro, Matrox XTools 6153, Nero 7, Acronis TrueImage (for ghosting) and the soundcard drivers (Createive SB Audigy - note I did not load any of the Audigy software - just the drivers to enable the devices in Device Manager to operate correctly).
Everything works fine - except...
Video capturing an analogue source which is being fed into the RTX100 via the breakaway box Composite feeds sockets (from a VCR) works perfectly for durations up to around 20 minutes. If I allow it to run for longer, when I come to hit Stop Recording, control never comes back to me - the Capture module appears to crash, I have to use Task Manager to kill PPro and the AVI file containing the capture is unreadable thereafter. This happens each and every time where the capture duration exceeds about 20 minutes, yet up to the point where I click on Stop, everything appears to be working (I can see the capture file size increasing as one would expect - but as soon as I click Stop, the capture module stops responding).
Where the capture duration is less than about 20 mins, clicking Stop gives me the dialogue box requesting the file name to be applied to the clip, as expected.
I am not an expert with PPro but nor am I a novice, having used the previous versions I referred to above. I am a professional software deveoper by trade so I know my way around PCs too, but am at a loss to know what is causing this and hoped someone may be able to make some suggestions.
As per tracking any software issues I have done some testing to try and eliminate possibibilites and the following may be of use in helping provide a diagnosis.
This only happens when the captured video format is set to "Matrox AVI" (which, with AVI being the native format for working on in Premiere Pro without requiring timeline rendering). If I set the format to "Matrox M2V" then the capture works perfectly.
I've tried changing the settings for the scratch disk locations although I don't think this is the problem - I have a very fast system with the RAID-0 SATA drives (2x120Gb approx) used for video editing. I sincerely don't believe disk performance is the reason for this). Changing the video and audio capture locations to different disks made no differece.
I have also used a freeware video capture program, as well as Microsoft Movie Maker 2.1, to capture clips in excess of an hour, without problem.
My problem appears to be specifically related to Premiere Pro capturing in Matrox AVI format, where the clip duration exceeds approximately 20 minutes.
Does anyone have any ideas as to what may be causing this? Failing that, could anyone recommened an alternative to Premiere Pro for capturing analogue video via the Matrox RTX100 card in AVI format which I would then be able to import directly into Premiere Pro for editing? I have no objection to using another tool to capture the clips providing the format is compatible with PPro.
I hope someone can shed some light on this - it is (for me) spoiling what I otherwise think is an excellent product.
Many thanks in advance
Brian Mackenzie
I have just installed the Premiere Pro 2.0 Tryout on my Matrox RTX100 system (P4 3Ghz, Windows XP Pro SP2, 2Gb RAM, 250Gb SATA RAID-0 plus other IDE) and am having problems with capturing in Matrox AVI format.
I have previously worked with both Premiere 6.5 and Premiere Pro 1.5 on this system without too many problems, other than for the fact that the RTX100 driver would occassionally cause the machine to hang when first booted. This was a minor issue as it happened perhaps once in every 10 boots and was resolved by rebooting the machine. It was irritating enough however that I decided to set up dual boot and move Premiere Pro and Matrox to a new copy of Windows XP, booting from another hard disk.
As I was installing from scratch I decided to give Premiere Pro 2.0 and Matrox XTools 6153 a workout, and have been very pleased with the result, bar the anomally I describe below.
All worked well - both partitions boot as intended, the original partition loads more quickly and without ever hanging, and the new partition is clean except for Premiere Pro, Matrox XTools 6153, Nero 7, Acronis TrueImage (for ghosting) and the soundcard drivers (Createive SB Audigy - note I did not load any of the Audigy software - just the drivers to enable the devices in Device Manager to operate correctly).
Everything works fine - except...
Video capturing an analogue source which is being fed into the RTX100 via the breakaway box Composite feeds sockets (from a VCR) works perfectly for durations up to around 20 minutes. If I allow it to run for longer, when I come to hit Stop Recording, control never comes back to me - the Capture module appears to crash, I have to use Task Manager to kill PPro and the AVI file containing the capture is unreadable thereafter. This happens each and every time where the capture duration exceeds about 20 minutes, yet up to the point where I click on Stop, everything appears to be working (I can see the capture file size increasing as one would expect - but as soon as I click Stop, the capture module stops responding).
Where the capture duration is less than about 20 mins, clicking Stop gives me the dialogue box requesting the file name to be applied to the clip, as expected.
I am not an expert with PPro but nor am I a novice, having used the previous versions I referred to above. I am a professional software deveoper by trade so I know my way around PCs too, but am at a loss to know what is causing this and hoped someone may be able to make some suggestions.
As per tracking any software issues I have done some testing to try and eliminate possibibilites and the following may be of use in helping provide a diagnosis.
This only happens when the captured video format is set to "Matrox AVI" (which, with AVI being the native format for working on in Premiere Pro without requiring timeline rendering). If I set the format to "Matrox M2V" then the capture works perfectly.
I've tried changing the settings for the scratch disk locations although I don't think this is the problem - I have a very fast system with the RAID-0 SATA drives (2x120Gb approx) used for video editing. I sincerely don't believe disk performance is the reason for this). Changing the video and audio capture locations to different disks made no differece.
I have also used a freeware video capture program, as well as Microsoft Movie Maker 2.1, to capture clips in excess of an hour, without problem.
My problem appears to be specifically related to Premiere Pro capturing in Matrox AVI format, where the clip duration exceeds approximately 20 minutes.
Does anyone have any ideas as to what may be causing this? Failing that, could anyone recommened an alternative to Premiere Pro for capturing analogue video via the Matrox RTX100 card in AVI format which I would then be able to import directly into Premiere Pro for editing? I have no objection to using another tool to capture the clips providing the format is compatible with PPro.
I hope someone can shed some light on this - it is (for me) spoiling what I otherwise think is an excellent product.
Many thanks in advance
Brian Mackenzie