Topic: Instruments not remembering their presets.

Viewing 9 posts - 1 through 9 (of 9 total)
  • July 11, 2010 at 14:57 #2304
    German Fafian
    Participant

    Hi there.
    I know there are a couple older posts about this but since they are a bit older I decided to open a new thread.
    My problem so far is with Drumaxx and Sytrus ( reported in a 2009 thread I think)
    I load each vsti in a channel (multi channel for Drumaxx) and then load a preset.
    I save the project and close it.
    I load the project again and neither instrument loads with the preset I saved it with.
    Drumaxx even loads to the deafult routing to the main channel in the folder channel. 😕
    I’m I missing soimething here?
    I will check all ther instruments I have and see if I get the same result.
    So far only these IL plugs have shown this behaviour.
    Harmless, Morphine, Toxic Biohazard are working as expected and I own all of them (no demos)
    I re-installed the registry key for both just in case but the behaviour persists.
    Later and thanks 8)

    July 11, 2010 at 16:45 #18799
    Trancit
    Participant

    The problem with those two plugins is, that Podium doesn´t recognize preset changes, you make with the internal plugin preset browser…

    Load Sytrus in a track, open the preset tab in the inspector and switch through the presets, using the arrow keys beside the “Synth String- Rich Ensemble” window…look at the preset tab in the inspector…there are no changes…

    To let Podium recognize the used preset, use the preset tab in the inspector or save a new preset library file, if you had made changes…then Podium will save the correct preset as well…

    Same with Drumaxx…

    Trancit

    July 11, 2010 at 18:21 #18800
    German Fafian
    Participant

    Oh. Ok.
    Cool. Will try this as soon as the Spain – Holland game is over 😉

    July 12, 2010 at 07:05 #18802
    German Fafian
    Participant

    Back from the celebration!!!! 😀
    Oddly enough Sytrus does not show any presets in the inspector 😕
    Will reinstall it and see if it was something I did wrong during install.
    Other than that I might be able to save all presets from within FL as FXB.
    I’ll see when I get home tonight.
    Thanks 8)

    July 12, 2010 at 07:31 #18803
    Trancit
    Participant

    @German Fafian wrote:

    Back from the celebration!!!! 😀
    Oddly enough Sytrus does not show any presets in the inspector 😕
    Will reinstall it and see if it was something I did wrong during install.
    Other than that I might be able to save all presets from within FL as FXB.
    I’ll see when I get home tonight.
    Thanks 8)

    I just installed Sytrus 2.6.8 and all the presets are shown without any problems in the inspectors preset panel…. 😯

    Trancit

    July 12, 2010 at 10:03 #18804
    German Fafian
    Participant

    Weird indeed.
    Imust have installed something in the wrong place and I just had this flash about Data files being installed in another folder alltogether :doh!:
    while my vsti folder is in a custom folder in another disk :double Doh!:
    I’ll check it as soon as i’m back from work.
    Thanks dude.

    July 12, 2010 at 21:16 #18811
    siegfried
    Participant

    This seems to be a nasty bug 🙁

    July 13, 2010 at 04:51 #18817
    German Fafian
    Participant

    Well.
    I re-installed the plugs and let it install the data files in their default folder but the VSTi in the folder where my plug ins are located and now everything works 😀
    The only thing is that Maxx Claster’s plugs do not ahow their presets in the inspector.
    They only show a “local Preset” kind of message but Podium does remember the presets.
    So I am a happy camper now.
    Off for the final touches to my new tune 😀
    Thanks for the help.

    July 13, 2010 at 11:44 #18826
    LiquidProj3ct
    Participant

    Hi, Maxx’s plugins have their own way to handle presets [using IL Downloader], to it’s imposible that Podium can manage those non-internal presets.

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