1. IMPORTANT:
    We launched a new online community and this space is now closed. This community will be available as a read-only resources until further notice.
    JOIN US HERE

1.1 fails in LogicPro 7.2.1

Discussion in 'ELEKTRIK PIANO' started by egor, 14/5/06.

Thread Status:
Not open for further replies.
  1. egor

    egor NI Product Owner

    Messages:
    12
    I downloaded and installed the Elektrik Piano 1.1 update into my Mac (dual G5), OS X 10.4.6

    I launched Logic 7.2.1 and tried to instantiate the updated Elektrik Piano update, but was greeted by an error message:

    "Error code -50 was returned by the CoreAudio Driver".

    So, I opened AU manager and rescanned the Elektrik Piano AU (v1.1.10). It passes all tests.

    I relaunch Logic, but the same problem exists (error code -50).

    I launched the standalone version of Elektrik Piano and it plays. BUT, when I check the ABOUT box, it tells me that it's version 1.0.2, not v1.1.10. Huh?

    So I re-download and reinstall Elektrik Piano 1.1 -- exact same results.

    So, Elektrik Piano is now completely non-functional in my Logic environment... any ideas?
     
  2. flavum@optonline.net

    flavum@optonline.net NI Product Owner

    Messages:
    5
    Exact same problem here. I also checked the plug-in versions (AU and VST) to see if they appeared as v1.1, but they're still at 1.0.2.x.

    EP is currently unuseable with Logic Pro 7.2.1.
     
  3. Achim @ NI

    Achim @ NI NI Product Owner

    Messages:
    2
    Please try to delete the AU ("/Library/Audio/Plug-Ins/Components/Elektrik Piano.component") before running the update. Maybe there's a problem with file permissions for that file, so deleting it makes it possible for the installer to write the new AU. EP 1.1 runs without a problem here in Logic 7.2.1.

    Best, Achim.
     
  4. flavum@optonline.net

    flavum@optonline.net NI Product Owner

    Messages:
    5
    Achim - Thanks for the tip. Your technique works and EP is running again with Logic. Since the update requires an admin password, I'm surprised that it was a permissions problem. I would have thought that the update would ignore permissions since it had admin priviledges. Tom
     
Thread Status:
Not open for further replies.