Topic: Podium (Free) not working with Asio Driver

Viewing 7 posts - 1 through 7 (of 7 total)
  • October 6, 2014 at 16:51 #27265
    ExTheSea
    Participant

    I am testing Podium Free and i’m not able to start playback and as a result also not record anything when i use the asio driver of my Focusrite Audio Interface. The same behaviour occurs when using the standard windows audio driver and turning the buffer size really low.
    When using a higher buffer size it works as expected but the latency and the audio glitches makes it unusable.

    • This topic was modified 10 years, 2 months ago by ExTheSea.
    October 11, 2014 at 19:33 #27304
    Zynewave
    Keymaster

    Other users have reported issues with Focusrite ASIO drivers. I assume you have updated to the latest driver version. May I ask which Focusrite audio interface you are using?

    You could alternatively try the asio4all.com free driver.

    October 11, 2014 at 21:58 #27306
    kill_em_all
    Participant

    I have the same problem with Focusrite 2i2. The drivers are new, installed them last week. ASIO 4ALL has the same behavior, shows me CPU overload, with varying numbers 3-6 on the red box.
    Thanks

    October 12, 2014 at 17:54 #27308
    Zynewave
    Keymaster

    3-6 is an average CPU usage percentage, which is not a lot. If the CPU indicator is showing red overload, it means that occasionally the ASIO buffer could not be filled in time, causing dropouts in the sound. This can happen due to plugins that occasionally perform some heavy initialization, perhaps as a result of preset or parameter changes. It could also be other programs/drivers on your Windows PC that blocks the CPU for a brief period. Some network drivers have been known to cause these issues, although that was years ago I last heard such reports.

    Could you try to increase the ASIO buffer size to see if this reduces the occurrences of overload?

    October 14, 2014 at 16:38 #27340
    ExTheSea
    Participant

    Sorry for the late reply. I abandoned podium for a bit because of this problem:
    I’m using Focusrite Scarlett 2i4.
    I could also get the same problem when using the standard drivers and setting the buffer size really low (to e.g. only 3ms buffer size).
    When it happens CPU indicator is completly red. The machine i’m trying is not really made for audio stuff as i’m using it for all other computer related things too. So there might be a problem with something like network drivers or else. I also tried creating project without loading any vsts without any success.

    Also: I’m currently evaluating Reaper which shows no issues so it is probably podium or one-core-processing (because of the free limitation) specific…

    October 14, 2014 at 19:02 #27341
    kill_em_all
    Participant

    Yes, I confirm the same behavior, the native driver allows max 10 ms latency, but that does not change anything.At 4ms latency it shows me a buffer size of 460 samples. As ExTheSea, other DAWs are dealing ok with this.
    I noticed that at initializing the project the CPU is showing a high value 80-90 than the value drops to the 3-4, but the box remains red. I can play the VSTs that I load, it’s just the playback that is stuck.

    How can I know what drivers are conflicting with Podium?

    October 14, 2014 at 22:00 #27347
    ExTheSea
    Participant

    I even had it down to showing a 0 and still being red and as a result not working…

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