Activity › Forums › Apple Final Cut Pro Legacy › Capture encountered a problem reading the data on your source tape
-
Capture encountered a problem reading the data on your source tape
Graeme Fyfe replied 14 years, 8 months ago 12 Members · 16 Replies
-
Greg Jennings
May 13, 2010 at 1:27 amI am running into this problem right now. All the research I have seen says that the only solution is to get your deck or camera professionally cleaned, but the problem will still be there with the tape you are working with. If anyone knows a work around, please let me know!
-
Benjie Westafer
May 13, 2010 at 3:06 amMy ‘workaround’ was to give up on capturing through firewire. Instead, I used S-Video through a BlackMagic Intensity Pro to DV; yes, I’m very cheap and a noob. The results were decent and got the job done. I’m still unsatisfied; but, my mentor in this business keeps trying to beat into my skull that one can’t let the perfect be the enemy of the good. I do try to learn.
-
Tony Sherman
May 25, 2010 at 3:44 pmI got round problem by changing DV50 PAL 48 Khz in Audio/video settings>summary>capture preset to DV PAL 48Khz so check your settings are correct. Was it luck, coincidence or one of FCP many idiosyncrasies? I don’t know but it worked.
In general I find that 95% of capture problems are down to one of the many settings needing a tweak.
-
Preston Benson
September 27, 2010 at 7:12 pmI began receiving this message after messing with the TC/UB functions in my Z1U, no matter what tape I was using. Well I actually didn’t change anything, but for some reason, something had changed as I looked through the settings and reaffirmed the default selections. So I solved the problem by resetting the TC Preset and the UB Preset. Strangely, I couldn’t recreate the problem and confirm what exactly fixed it, but hopefully this helps, as I was utterly perplexed when this happened to me.
-
Doug Buckser
May 1, 2011 at 4:09 amG’day Tony,
This just solved a problem which was driving me crazy for a couple of days. Thanks so much for contributing the message.
Regards,
Doug -
Graeme Fyfe
September 13, 2011 at 8:42 amI’m sure – from the posts – that there are numerous causes (and therefore remedies) to this issue, but I’ve experiencing it this morning and it turned out to be an issue with the capture settings.
Someone had been using my workstation and changed them in my absence – changed them back to PAL DV and all good.
Hope you get it sorted.
Reply to this Discussion! Login or Sign Up