Topic: energyXT preset loading problem

Viewing 15 posts - 1 through 15 (of 19 total)
1 2
  • April 16, 2006 at 12:58 #803
    kingtubby
    Participant

    Loading .ext presets from within energyXT vsti consistently causes Podium to crash with the message: ‘a plugin has performed an illegal action: energyXT….’
    This is with v1.56 and the latest eXT beta but I’ve had the same problem going back for quite some time now – only just got round to reporting it though 😳
    Anyone else experience the same problem?

    Mart.

    April 16, 2006 at 18:38 #6555
    Max
    Participant

    Confirmed with 1.55 and latest eXT beta VSTi. VstFX version works fine. This time eXT demo restriction will be the pain (for debugging).

    April 16, 2006 at 19:37 #6556
    kingtubby
    Participant

    VstFX version works fine here too.

    Mart.

    April 17, 2006 at 13:45 #6565
    Zynewave
    Keymaster

    I’ll check it out. I have a license for eXT.

    Are you using eXT: Beta 27-feb-06 ?

    April 17, 2006 at 13:54 #6567
    Max
    Participant

    @Zynewave wrote:

    I’ll check it out. I have a license for eXT.

    Are you using eXT: Beta 27-feb-06 ?

    Yes.

    April 17, 2006 at 14:06 #6568
    kingtubby
    Participant

    @Zynewave wrote:

    I’ll check it out. I have a license for eXT.

    Are you using eXT: Beta 27-feb-06 ?

    Me also.

    April 17, 2006 at 15:48 #6569
    Zynewave
    Keymaster

    Tested with Podium 1.56 and latest eXT beta. I loaded the eXT VSTi version on a Podium track. Added a VSTi inside eXT and saved to an .ext file. Added a reverb plugin and saved to another .ext file. Loading these .ext files causes no crash. Creating presets on the Podium track also recalls the two different plugin setups fine. What am I doing wrong? 😛

    Maybe the crash occurs because the .ext files you are loading have been saved with a previous eXT version? Try saving .ext files with the latest eXT beta version and see if these will load.

    April 17, 2006 at 16:13 #6570
    kingtubby
    Participant

    I can confirm that saving a new .ext then re-opening works as normal.
    As you suggest Frits, it’s opening older .ext files that cause the problem.
    Actually, all my previously saved .ext files have been created and saved using eXT in standalone operation – maybe that’s got something to do with it..

    Mart.

    April 17, 2006 at 17:01 #6572
    Zynewave
    Keymaster

    Perhaps resaving your ext files in the latest standalone beta, will enable them to load in the VSTi version.

    April 17, 2006 at 17:34 #6573
    kingtubby
    Participant

    @Zynewave wrote:

    Perhaps resaving your ext files in the latest standalone beta, will enable them to load in the VSTi version.

    Just gave that a try and it still doesn’t work 🙁

    Mart.

    April 17, 2006 at 18:18 #6575
    Zynewave
    Keymaster

    I doubt that there is anything I can do in Podium to fix this. You can email me one of your older .ext files so I at least can verify if the crash occurs on my system.

    April 17, 2006 at 19:14 #6576
    Max
    Participant

    eXT project file sent.

    April 17, 2006 at 19:21 #6577
    Max
    Participant

    BTW, it’s not an older ext-file. It’s made in the latest beta – I just saved in eXT standalone empty seq project.

    April 17, 2006 at 19:45 #6578
    kingtubby
    Participant

    I just sent one as well – it’s an older ext though.

    Mart.

    April 17, 2006 at 20:06 #6580
    Zynewave
    Keymaster

    I found out why the eXT VSTi crashes. If you bypass or mute the eXT track, you can load the .ext projects saved with the standalone version. Once you unmute or disable bypass of the eXT track though, it will crash in the audio processing code. You’ll notice that your eXT projects has a master in module with both MIDI and audio connectors. If you create new projects with the VSTi version the master in only has a MIDI connector. This is because the VSTi version does not have audio inputs. Since the plugin declares it does not process input, Podium does not provide input buffers to it (for speed and memory optimization reasons), and this is why eXT crashes. If I send dummy input buffers to eXT it does not crash. You should be able to use your projects if you can substitute the master in MIDI/audio module with a master in MIDI only module, but I could not figure out how to do this.

    I’ll send an email to Jørgen about this.

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