More info on my problem with 32K audio being captured instead of 48K...
I have two computers (1 Dell and 1 Compaq). The Dell has an Adaptec 1394 card and the Compaq has a built in 1394 port. I have two Canon XL1s cameras both configured for 16bit audio which means 48K audio too. On both computers, if I use VV3a's capture utility, all of my video clips show up with 32K for the audio properties when they should be 48K.
Next, I downloaded and installed the demo for Scenalyzer (www.scenalyzer.com). This is a capture utility similar to the one in VV3a. On both computers, the same footage I captured using VV3a's capture utility comes in a 48K using Scenalyzer.
So, it appears to me there is not a problem with my cameras or my computer setup. It seems that if one capture utility (Scenalyzer) can capture correctly, then something must be wrong with VV3a's capture utility. I know everyone does have have this problem, but I have heard from some other people who do have this same problem.
I don't know if the audio captured using VV3a is really 32K or 48K. Maybe the problem it is just in the header information VV3a's capture utility puts on the file and can be an easy fix.
Sonic Foundry, do you have any suggestions?
Thanks,
Ron
I have two computers (1 Dell and 1 Compaq). The Dell has an Adaptec 1394 card and the Compaq has a built in 1394 port. I have two Canon XL1s cameras both configured for 16bit audio which means 48K audio too. On both computers, if I use VV3a's capture utility, all of my video clips show up with 32K for the audio properties when they should be 48K.
Next, I downloaded and installed the demo for Scenalyzer (www.scenalyzer.com). This is a capture utility similar to the one in VV3a. On both computers, the same footage I captured using VV3a's capture utility comes in a 48K using Scenalyzer.
So, it appears to me there is not a problem with my cameras or my computer setup. It seems that if one capture utility (Scenalyzer) can capture correctly, then something must be wrong with VV3a's capture utility. I know everyone does have have this problem, but I have heard from some other people who do have this same problem.
I don't know if the audio captured using VV3a is really 32K or 48K. Maybe the problem it is just in the header information VV3a's capture utility puts on the file and can be an easy fix.
Sonic Foundry, do you have any suggestions?
Thanks,
Ron