Topic: Podium.exe not closing after fire wire error

Viewing 2 posts - 1 through 2 (of 2 total)
  • #1735
    Mike G
    Participant

    Hi,
    Not sure if this is a windows issue, a device driver issue or a podium issue.

    It’s not a show stopper I can still work but it can slow me down and it’s a bit annoying.

    Sometimes my fire wire port locks up, it’s got a dodgy connection, you see, bain of my life!!!
    When this happens, podium says “Can’t initialise divice for 44 khz” or similar msg, and I can’t use my audio interface (no sound etc)

    So I close podium so I can try to open it again after my firewire connection has been “wiggled” and other very technical things such as unplug fire wire cable and then plug in again etc..

    But although podium is no longer on screen, I look in windows task mgr I see the previous instance of podium still running
    I can’t end task it, the task just never goes away. I think if I leave it long enough it will go away but it’s quicker to just reboot windows.

    This also happens after other crashes such as plug ins that crash.

    Why is podium process not killed off?

    Obviously while the old podium process is still running starting a new one is pountless it can’t access anything and you get lots of msgs about other programs having access to stuff etc.

    Hope that makes sense.

    Thanks,
    Mike G

    #13457
    Zynewave
    Keymaster

    When Podium is exiting, it will “release” the drivers as one of the final steps. Thus if the driver somehow locks up during deinitialization, then Podium.exe may appear to hang.

Viewing 2 posts - 1 through 2 (of 2 total)
  • You must be logged in to reply to this topic.
© 2021 Zynewave