Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums AJA Video Systems Audio clicks & pops from FCP through AJA IoLA – not there until the AJA box

  • Audio clicks & pops from FCP through AJA IoLA – not there until the AJA box

    Posted by Travis Ballstadt on February 22, 2006 at 4:45 am

    Hi…trying to troubleshoot my wife’s machine at her office.

    G5 DP2.7GHz
    8GB RAM
    FCP Studio
    AJA IoLA
    Sony DVW A500 Digital Betacam Deck

    DVCPro 50 footage (SDX900)
    DVCPro 50 sequence for editing the show
    10bit NTSC sequence for graphics & printing to tape

    Have updated all drivers & firmware. This is the 2nd different DigiBeta deck we’ve tried, as well.

    Sending TV show episodes to tape, network requires 4-channel: 2 stereo, 2 discreet.

    When the sound on the music channel drops completely away, we can see and hear pops hitting on the audio meter. It seems to be little glitches from other channels popping in and out of channel 4. Sometimes it’s a voice. Sometimes it’s nat sound. Sometimes it’s only a little click.

    Probably happening all the time, but it’s only visible/audible when it’s isolated. It doesn’t seem to do it on any other channel.

    These audio files are mastered in ProTools and brought into the timeline as one long file for each segment, so there are no parts of the sequence that have nothing there.

    The pops do not show up on the Final Cut mixer, and are not audible on the studio monitors directly from FCP.

    The pops only show up when running through the AJA IoLA box, either viewing on external monitor or printing to tape.

    Audio is all 48K.

    All we can do to get rid of them is keyframe the mixer to pull all sound out of that track once the music fades down. Sure, no big process, but our sound mixer is already doing that in ProTools. It’s doing the same thing twice. There’s nothing there, so why should we have to bring it down on every show?

    travis ballstadt
    http://www.thrillcateditorial.com

    Michael replied 20 years, 1 month ago 5 Members · 13 Replies
  • 13 Replies
  • Jeremy Garchow

    February 22, 2006 at 6:30 pm

    have you tried an audio mixdown? How are your audio outputs in the timeline set up (i.e. how do you have your stereo mix going to 1&2 and ‘discreet’ going to 3&4)?

    HOw do you know that it is the aja box causing the clicks? How do you monitor your sound when there’s no aja?

    Are the Pro Tools files 16 bit 48k aifs? Is there a green bar on them?

    I’ll stop here.

    Jeremy

  • Travis Ballstadt

    February 22, 2006 at 6:37 pm

    This is an audio mixdown. There are four tracks of audio on the timeline, each going to a separate channel on the digibeta. Only four audio files on the entire timeline.

    travis ballstadt
    http://www.thrillcateditorial.com

  • Travis Ballstadt

    February 22, 2006 at 6:39 pm

    Sorry, didn’t read all of it.

    The tracks are routed in FCP. Tracks 1 & 2 are a stereo pair, tracks 3 & 4 are mono tracks. The sequence has 4 audio outputs, routed to the respective channels of the AJA.

    When not previewing on an external monitor, the sound is routed through the digital output of the G5 into a pair of studio monitors. A second pair of identical studio monitors are connected to the audio out of the digibeta.

    travis ballstadt
    http://www.thrillcateditorial.com

  • Jeremy Garchow

    February 22, 2006 at 6:58 pm

    Alright. SO you have chosen 4 channels of audio in the audio outputs section of the sequence settings? And then you have ch 1&2 setup as stereo and ch 3&4 setup as dual mono? Then in the timeline you have option clicked ch 1 and selected the output as 1&2, then you have option clicked ch2 and selected the output as 1&2, then you have option click channel 3 and set the output as ch3 and then you option clicked ch4 and selected the output as ch4? Then you open the mixer tool and FCP is showing 4 channels in the master section and you don’t have the downmix button pressed?

    I’m not talking about the audio mixdown from ProTools, I’m talking about an FCP audio mixdown. Go to the sequence->render only->mixdown menu and mixdown the audio within FCP. This can fix some weird audio glitches.

    Jeremy

  • Travis Ballstadt

    February 22, 2006 at 8:01 pm

    Right. Everything is routed properly, and the process works, except for these little pops and clicks. Everything is going to the proper channel, but for some reason, there are little glitches happening in channel 4.

    I’m not at my wife’s office today, but I have told her to try the mixdown idea. I’ll post back when I hear.

    travis ballstadt
    http://www.thrillcateditorial.com

  • Bob Zelin

    February 23, 2006 at 12:15 am

    contact AJA tech support –
    trust me, just do it.

    bob Zelin

  • Travis Ballstadt

    February 23, 2006 at 2:22 am

    Talked to them yesterday. He had me revert from driver v 2.1 back to 2.0, which didn’t work at all. Couldn’t send any video until we re-updated to v2.1. We can print now, but we’re still getting the pops.

    An audio mixdown didn’t work, either.

    I think tomorrow I’m going to have her try changing to an 8 channel ouput sequence, routing the problem track to a different output and plugging the corresponding cable into channel 4 of the digibeta deck to see if it’s still there.

    travis ballstadt
    http://www.thrillcateditorial.com

  • Jeremy Garchow

    February 23, 2006 at 4:31 am

    Or better yet switch the order of the cables, put aja ch 4 to ch 1 of the deck and aja ch 1 to ch 4 of the deck and see if you get the pops on ch1 of the deck.

  • Christopher Wright

    February 23, 2006 at 8:35 pm

    Good advice! You can tell Jeremy has done some troubleshooting before!!

  • Travis Ballstadt

    February 23, 2006 at 9:59 pm

    We’ll try that, but this is the second DigiBeta deck that we’ve had the problem with, so we’re pretty sure it’s either FCP or the AJA…

Page 1 of 2

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