Forum Replies Created

  • Amber 🙂

    July 26, 2005 at 10:29 pm in reply to: Problems Capturing Audio Only

    More info! What happens when you try? Is the option greyed out? Do you have the option, and select it, but nothing is digitized? More info.
    Ed

    Ed,
    OK, let me start from the beginning of the process: 90% of the audio I bring in comes in via DAT machine. This is hooked up directly through my AJA Io. In this case, I have to do a “capture now” to grab the audio. The other way audio comes in is via BetaSP, which is also hooked up to my AJA Io.

    Here’s my problem:
    I’ve narrowed this problem down to the “capture now” option. When I try to capture audio only, the option is available for both ‘Audio Only’ and ‘Capture Now’.
    When my device control is a ‘non-controllable device’ the following occurs:
    I click ‘capture now’, it pretends like it’s capturing, then nothing shows up in my browser/bins. No audio file, no video file, nothing. It was all a big fake-out. I’ve tried looking to see if it may have captured and is on my AV drive, but with no avail.
    When my device control is set to my BetaSP deck, the following occurs:
    I click on ‘capture now’, it says ‘waiting for timecode’ at the bottom of the capturing window. I hit play on my deck. Immediately the following error message pops up: “ERROR: Final Cut Pro HD was unable to read the movie file it just captured” This message is immediately followed by: “Capture Now has reached the end of the tape. All existing footage between the point where you started the caputre and the end of tape was captured successfully.” This in itself is a false statment. The tape is not at its end and FCP captured nothing b/c it didn’t even give it a chance to get anything before the error message came up.
    SO, all this to say, my capture now is really the culprit. What’s going on here? To weasle my way around this, I am able to capture audio & video via non-controllable device doing a capture now and it works fine. I can also get video via noncontrollable device and it captures.

    I appreciate any help you can offer.
    Amber

  • Amber 🙂

    July 26, 2005 at 10:28 pm in reply to: Problems Capturing Audio Only

    More info! What happens when you try? Is the option greyed out? Do you have the option, and select it, but nothing is digitized? More info.
    Ed

    Ed,
    OK, let me start from the beginning of the process: 90% of the audio I bring in comes in via DAT machine. This is hooked up directly through my AJA Io. In this case, I have to do a “capture now” to grab the audio. The other way audio comes in is via BetaSP, which is also hooked up to my AJA Io.

    Here’s my problem:
    I’ve narrowed this problem down to the “capture now” option. When I try to capture audio only, the option is available for both ‘Audio Only’ and ‘Capture Now’.
    When my device control is a ‘non-controllable device’ the following occurs:
    I click ‘capture now’, it pretends like it’s capturing, then nothing shows up in my browser/bins. No audio file, no video file, nothing. It was all a big fake-out. I’ve tried looking to see if it may have captured and is on my AV drive, but with no avail.
    When my device control is set to my BetaSP deck, the following occurs:
    I click on ‘capture now’, it says ‘waiting for timecode’ at the bottom of the capturing window. I hit play on my deck. Immediately the following error message pops up: “ERROR: Final Cut Pro HD was unable to read the movie file it just captured” This message is immediately followed by: “Capture Now has reached the end of the tape. All existing footage between the point where you started the caputre and the end of tape was captured successfully.” This in itself is a false statment. The tape is not at its end and FCP captured nothing b/c it didn’t even give it a chance to get anything before the error message came up.
    SO, all this to say, my capture now is really the culprit. What’s going on here? To weasle my way around this, I am able to capture audio & video via non-controllable device doing a capture now and it works fine. I can also get video via noncontrollable device and it captures.

    I appreciate any help you can offer.
    Amber

  • Amber 🙂

    July 26, 2005 at 10:28 pm in reply to: Problems Capturing Audio Only

    More info! What happens when you try? Is the option greyed out? Do you have the option, and select it, but nothing is digitized? More info.
    Ed

    Ed,
    OK, let me start from the beginning of the process: 90% of the audio I bring in comes in via DAT machine. This is hooked up directly through my AJA Io. In this case, I have to do a “capture now” to grab the audio. The other way audio comes in is via BetaSP, which is also hooked up to my AJA Io.

    Here’s my problem:
    I’ve narrowed this problem down to the “capture now” option. When I try to capture audio only, the option is available for both ‘Audio Only’ and ‘Capture Now’.
    When my device control is a ‘non-controllable device’ the following occurs:
    I click ‘capture now’, it pretends like it’s capturing, then nothing shows up in my browser/bins. No audio file, no video file, nothing. It was all a big fake-out. I’ve tried looking to see if it may have captured and is on my AV drive, but with no avail.
    When my device control is set to my BetaSP deck, the following occurs:
    I click on ‘capture now’, it says ‘waiting for timecode’ at the bottom of the capturing window. I hit play on my deck. Immediately the following error message pops up: “ERROR: Final Cut Pro HD was unable to read the movie file it just captured” This message is immediately followed by: “Capture Now has reached the end of the tape. All existing footage between the point where you started the caputre and the end of tape was captured successfully.” This in itself is a false statment. The tape is not at its end and FCP captured nothing b/c it didn’t even give it a chance to get anything before the error message came up.
    SO, all this to say, my capture now is really the culprit. What’s going on here? To weasle my way around this, I am able to capture audio & video via non-controllable device doing a capture now and it works fine. I can also get video via noncontrollable device and it captures.

    I appreciate any help you can offer.
    Amber

  • Amber 🙂

    July 26, 2005 at 6:06 pm in reply to: AE 6.5 and Invig. Classic

    I should add that this was the error message that popped up when the AfterEffects crashed while trying to apply the effect to a layer.

    “After Effects has crashed while invoking effect plug-in 3D Invigorator?”

    Amber

  • Amber 🙂

    July 26, 2005 at 6:01 pm in reply to: AE 6.5 and Invig. Classic

    Hi Matt,

    You’re using v3.1.1, correct? Yes.

    Are you on the Mac or the PC? Mac dual 2.5 OS 10.3.9

    Can you tell me what you mean by “invoking effect plug-in 3D Invigorator?” Do you mean that you get a crash when you apply the Invig effect to a layer? Sorry, that was the smartmouth coming out in me. That’s correct, though. I randomly get a crash when I apply the Invig. effect to a solid layer. Also, sometimes the file imports correctly with the effect, some times it doesn’t.

    Also, can you send me the file you’re trying to Invigorate? I’d like to take a
    look.
    I certainly can. Just tell me where to email it.

    Thanks for your help, Matt. I appreciate it!

    Amber

  • Amber 🙂

    June 30, 2005 at 8:50 pm in reply to: Invig. Classic 3.1 and AE 6.5

    Great! I can now save my work! Thanks so much.

    A few other problems have come to my attention…
    1. AE crashes while “invoking effect plug-in ‘3D Invigorator'”
    2. After selecting the file to ‘invigorate’, nothing shows up in either the scene pvw or the viewer window. I have to try to import the file multiple times before it works correctly.

    Any solutions for this?

    Thanks,
    Amber

  • Amber 🙂

    June 30, 2005 at 7:53 pm in reply to: Invig. Classic 3.1 and AE 6.5

    Thanks,
    I’ll check it out and let you know.

    ‘preciate your help!

    Amber

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy