Topic: NUSofting DK+ Crashes in podium 2.06 *Solved*

Viewing 7 posts - 1 through 7 (of 7 total)
  • November 16, 2008 at 17:18 #1733
    DFusion
    Participant

    Hi Frits 🙂
    I was just playing with Podium 2.06 and 2 instances of DK+ Crashes in podium so that the second instance gets the red i button next to it.

    This also happened in V2.05.

    How to make it crash:

    First you create a sequence in DK+ instance 1 and then you click the E button and drag it to the Podium sequencer to copy the midi sequence to the dk+ track.

    Then Play back the loop 1 time and then try to open up DK+ instance 2 and it crashes.

    Hope you can look into this since this is the only drum machine i have.

    Thanks.

    November 20, 2008 at 02:45 #13441
    Zynewave
    Keymaster

    It’s possible that DK+ cannot cope with multiprocessing of multiple instances. Try disabling the “plugin multiprocessing” option in Podium preferences, and see if this fixes the crash problem.

    November 20, 2008 at 08:09 #13445
    DFusion
    Participant

    Hi Frits.
    I have also tested it with multiprocessing off since that was my first guess.

    But it still crashes so there must be something else that is wrong.
    It works fine in all the other hosts i use but not in Podium.

    November 22, 2008 at 23:12 #13456
    Zynewave
    Keymaster

    I’ve tried the DK+ 1.50 demo. I followed your instructions and tried various other things using two instances, but I can’t get it to crash.

    Maybe you could try the DK+ demo and check if you can get it to crash.

    November 23, 2008 at 11:51 #13460
    DFusion
    Participant

    Hi Frits 🙂
    Thanks for looking into this for me.
    I just did a new test and it works fine if i load 1 instance and make a pattern like i described and then add a new instance after that and load a soundset.

    But if i load 2 instances at once and then select a soundset for instance 1 and make a midi loop in podiums sequencer and then tries to open instance 2 and add a soundset there then Podium just vanish from the desktop without any warning.

    With Podium 2.05 and 2.06 i got a warning but 2.07 just shuts down and give me the desktop.

    November 23, 2008 at 12:36 #13463
    Zynewave
    Keymaster

    @DFusion wrote:

    But if i load 2 instances at once and then select a soundset for instance 1 and make a midi loop in podiums sequencer and then tries to open instance 2 and add a soundset there then Podium just vanish from the desktop without any warning.

    Still no crash for me (using the DK+ demo).

    With Podium 2.05 and 2.06 i got a warning but 2.07 just shuts down and give me the desktop.

    If the plugin are doing something illegal, such as overwriting memory not belonging to the plugin, then the outcome may be random. There are no changes in 2.07 that involves plugins, but just the fact that code has been added can change the memory layout, and thus cause different results with crashing plugins.

    November 28, 2008 at 19:27 #13475
    DFusion
    Participant

    I have done some heavy testing to see what it is that made it crash so badly and i found a solution to the problem 🙂

    The problem was a setting in DK+’s preference menu that wasn’t enabled.

    When i enabled the “Do not send Midi events to the host when clicking on a pad” option it works just fine without any crashing or instabilities 😀

    Problem solved 8)

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