Topic: parameter changes in SIR does podium crash

Viewing 10 posts - 1 through 10 (of 10 total)
  • June 7, 2004 at 01:57 #209
    kagemusha
    Participant

    When I assign a parameter change (dry) to SIR on a seperate track and draw a curve it will eventually crash podium after a few runs and stops.
    I tried with another vst but no problems there.

    Seems a SIR incompatibility

    Regards
    Eli

    June 7, 2004 at 13:13 #3452
    Zynewave
    Keymaster

    Yes, it seems SIR 1.0.0.5 does not like to be automated. I could not make it crash with the dry parameter only, but once I had tried automating attack level (not recommended 😯 ), a little later a dialog saying ‘SIR GUI: invalid pointer error’ popped up inside SIR, and the plugin editor went dead. The SIR audio processing were still okay, but closing the editor and reopening it again made Podium vanish up in thin air.

    Not much I can do about it unfortunately. SIR is a fine plugin otherwise.

    Frits

    June 7, 2004 at 15:47 #3454
    Sardaukar
    Participant

    A plug-in is able to bring down a host like that?
    darn. There is no way to prevent a plug-in crash ,crashing a host? darn. sounds dangerous.

    June 7, 2004 at 16:17 #3455
    duncanparsons
    Participant

    sadly, this is a fact… The host loads the dll into it’s own address space, and so if there is a bad exception, windows sees the host, not the dll, and zaps it!

    the best host exception catching in the world will not stop some crashes!

    o well, c’est la vie (or in this case, c’est la mort!)

    DSP

    June 7, 2004 at 16:21 #3456
    Zynewave
    Keymaster

    A plug-in is able to bring down a host like that?

    Yes. To optimize latency and CPU usage, the plugin code is called directly from the audio processing thread in Podium. The plugin thus acts as an extension to the host code, and has access to the same memory and system resources as the host. Podium wraps all calls to the plugin in protective code that will catch basic illegal operations, but it is still possible for the plugin to corrupt the host memory without the host knowing about it.

    Calling plugin code directly from the audio thread is the way it is done in all major sequencers to the best of my knowledge. Access to a plugin could theoretically be encapsulated in separate processes, which then would make the host secure, but this would be at the cost of added latency and extra CPU usage.

    Edit: You’re fast Duncan 😉 I started this before I saw your response.

    June 12, 2004 at 16:28 #3506
    Sardaukar
    Participant

    Kagemusha.

    You might like to know, there is a new version of SIR released. Hope this fixes your problem

    http://www.knufinke.de/sir/index_en.html

    Dan

    June 12, 2004 at 16:59 #3507
    Zynewave
    Keymaster

    Thanks for the tip Dan :),

    Just tried 1.008. It did appear to behave better. I could automate more parameters and longer than the previous version, but then all of a sudden *POOF*, back to the desktop. I was automating 4 parameters simultaneously, so maybe a moderate use of automation will be possible.

    Frits

    June 17, 2004 at 16:08 #3513
    kagemusha
    Participant

    @Sardaukar wrote:

    Kagemusha.

    You might like to know, there is a new version of SIR released. Hope this fixes your problem

    http://www.knufinke.de/sir/index_en.html

    Dan

    Thanks.
    I tried it. It seems a bit more stable but I had a crash.
    At the end I think SIR is not the right plugin to use as an “experimental” FX. When you try to change the length of the reverb the play cursor in podium freaks out (internal clock becomes erratic) and also suffering cpu peaks. Perhaps because its a convolution reverb which makes it not ideal to do parameter changes like length changes etc.

    Eli

    June 17, 2004 at 16:11 #3514
    kagemusha
    Participant

    @Zynewave wrote:

    Thanks for the tip Dan :),

    Just tried 1.008. It did appear to behave better. I could automate more parameters and longer than the previous version, but then all of a sudden *POOF*, back to the desktop. I was automating 4 parameters simultaneously, so maybe a moderate use of automation will be possible.

    Frits

    Can you change the length of a reverb. I get strange behaviour. >> complete cpu overload I think. Even if the curve is on/off ( from full lenght to shorter lenght in one step)

    Eli

    June 17, 2004 at 16:53 #3517
    Zynewave
    Keymaster

    Can’t remember what happened with length, but one of the other parameters I tried caused stutter in the audio and CPU overload. SIR must be doing some heavy internal calculation on the Impulse sound when certain parameters are changed.

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