Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Media 100 Analog inputs broken

  • Analog inputs broken

    Posted by Marc Morel on July 3, 2009 at 3:44 pm

    Hi All,

    Both my composite and component analog inputs from Betacam SP have stopped working since I upgraded from M100 v.12.1.3 (on Tiger 10.4.10) to v.13.0.3 (on Leopard 10.5.6)and the Aja Kona_LHe driver to the latest v.6.0.3_NDD yesterday. Nothing was changed in the patching, just the software updates and yet, the V Signal Indicator box in the Edit Suite remains yellow. SD-SDI from my Digibeta works perfectly.

    The Ref In triangle in the Aja Control Panel also is yellow.

    I see flashes of the incoming video on my NTSC monitor if I click on the desktop, thus leaving the M100 app, while trying to digitize so I figure the signal is getting into the Mac.

    Any ideas or insights would be greatly appreciated,

    Marc

    MacPro 2×3 GHz Intel, 5 GB ram, Mac OS 10.5.6, Media100 v.13.0.3, QT v. 7.6.2, Aja Kona LHe 6.0.3 NDD

    Marc Morel replied 16 years, 10 months ago 7 Members · 15 Replies
  • 15 Replies
  • Mitch Merback

    July 3, 2009 at 4:58 pm

    Make sure you are passing analog audio signal as well – I’ve had problems getting video until M100 sees audio too…

    Mitch Merback

  • Jim Wigler

    July 3, 2009 at 5:24 pm

    Instead of puttzing around with Media 100 anything, move on to Final Cut Pro and save yourself anymore grief.

    Final Cut Pro simply works! Not only is the program quite awesome, but it works seamlessly with the entire Adobe suite of programs.

    Every time I revert to Media 100 because of some insane belief that it will excel at something, I am bitterly disappointed. A perfect example was a little while ago when I created a montage using slow motion and various effects. When I exported it, the slow motion was missing (although rendered) and the audio effects were missing, too.

    It is also a blessing never having to deal with the people at BorisFX ever again.

  • Olof Ekbergh

    July 3, 2009 at 6:04 pm

    I don’t agree with Jim’s views of M100.

    As a matter of fact I have way more problems with my AJA HDe and Matrox MX02 in FCP than in M100.

    However, he does have point, test to make sure AJA works in FCP. If not then uninstall and reinstall AJA drivers.

    Did you do the AJA FirmWare update?

    You may want to dump M100 prefs, something you have to do in FCP on a regular bases, but only rarely in M100.

    Also I stayed with QT 7.6 it works great. Did you install the latest QT 7.6.2 (I think)?

    Olof Ekbergh

  • Floh Peters

    July 4, 2009 at 10:25 am

    This was a joke, right? If yes, it was really funny. While FCP has some nice features (some of them I would love to see in Media100), it definitely is not a syst that “just works”. There are many more places in FCP where you can mess with your settings, and some (like the input selection) are not even within the app. Media100s hardware integration is much more robust, and the preference and project setting management is definitely superior. Plus, it is actually built for peoffesional workflows.

  • Marc Morel

    July 4, 2009 at 11:22 am

    Hi All,

    -Thanks Mitch, tried it ten times, having seen that happen before. No joy.
    -Thanks Jim, I’ve worked with both and I’ll stick with Media 100. Just let it go . . .
    -Thanks Olof, tried pretty much everything you suggested, except the Aja firmware upgrade which is for the Kona3 cards and I’m still having problems.
    -Thanks Floh, I agree, and that’s why I don’t mind troubleshooting this first problem ever in 7 years.

    I’m in contact with Support and will let the forum know when the solution is found.

    Marc

  • Wickham Strub

    July 5, 2009 at 2:16 am

    Hey Marc,

    It’s a bug. We introduced it with v13.0.3 when we added support for the AJA LHi card.

    We’ve already got a fix, I expect to release 13.0.4 on Monday the 6th.

    ~Wick

  • Marc Morel

    July 5, 2009 at 11:40 am

    Thanks Wick, Matt sent me 13.0.2 on Friday afternoon to get me through the weekend, I’ll keep an eye open for 13.0.4 tomorrow.

    Marc

  • Wickham Strub

    July 6, 2009 at 9:25 pm

    We had a few last-minute scares today so I held off on releasing to be sure they weren’t show-stoppers. All were false alarms.

    We will post 13.0.4 tomorrow.

    Fixed in this release:

    – Audio acquired via HDV with QuickTime v7.6.2 installed now plays back correctly.
    – Analog acquire (broken in v13.0.3) is fixed.
    – Export to After Effects now works correctly with After Effects CS4.

  • Wickham Strub

    July 7, 2009 at 8:45 pm

    Okay, let this be a lesson to you all. NEVER give a specific date.

    If you deliver when you said you would every one just thinks, “Big deal, that’s what he said he was going to do.”

    If you miss it, you look like you’ve failed.

    Guess which camp I’m in today?

    Sorry, no 13.0.4 yet.

    It should be up tomor… uhh… REAL soon! Yeah, that’s it.

    ~Wick

  • Marc Morel

    July 8, 2009 at 12:11 am

    Jon Lovitz would be proud . . . Yeah! That’s the ticket.

    Thanks for the update,

    Marc

Page 1 of 2

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