I would need to have a default vst effect applyed for any midi file i would open, and this used to work in previous versions of synthfont. Aaltough there is been sometime since i don't use synthfont, and meanwhile i have re-installed windows 7. So today i download the current version, and like always i have loaded the vst effect i want to use in all midis, and click SET DEFAULT, i did exactly like i used to do in previous versions. But EVERYTIME i open a new midi, or even when i start the program without any midi loaded, it NEVER loads the vst effect in there, it's always empty no matter how many times i click set default after i manually load it, the only way to keep it there is to save a arranjment for every single midi file i open in there, don't tell me i really have to do this now... I even tried the SynthFont1350A.exe and SynthFont1350B.exe versions i seen in aother discussion and exactly the same problem.
In previous versions this used to work so well, why now it seems to be broken ? I think i will have to downgrade for the moment, while this isn't fixed or until someone is able to tell me what i could be doing wrong, i already tried all settings and nothing fixes this.
Yes!! I finally discovered what is causing this bug, i can't belive how SIMPLE it is. I found a earlier version of the program in my hdd (1.325) and i installed and compared both SynthFont.ini files and i noticed that when we set a default vst effect in the older version in the section [Default VST Effects] there is a entry called "Bypass all=0" and in the newer versions this setting is never created at all when the .ini is generated from scratch and after we click on SET DEFAULT. I found this is the cause of the problem because i then deleted the .ini file and started the most recent version to make it generate a new one, then when i added a new vst effect and i made it as default, again i notice that entry wasn't created, even if i would click the "bypass all" button on/off! As soon as i added manually this entry into the .ini file, it all behaved like before and it's working again, at least so far.
So here's the fix of the problem until the new version comes out (and no SynthFont1350B.exe doesn't fix it) : in case you aren't upgrading from a earlier version, and if the .ini file is generated by the new version, you have to manually add the entry "Bypass all=0" after "[Default VST Effects]" after setting a default vst effect. (UPDATE : i now noticed you have to do this everytime you use the SET DEFAULT button again, since clicking that button makes the entry vanish again)
Hate to tell you this, but versions 1.350A & B are test versions, which have already been superceded (I tested version 1.350F yesterday). The BYPASS setting works as per normal in the current (test) versions. The problem is, unfortunately, slightly more involved..
No no i haven't just used the test versions, i first downloaded the current version in the main page (1.345) and there is already this bug, only after that i tested in version A & b. Anyway for the moment i will be using 1.325 since it's the only other version i have before 1.345, while the bug doesn't get fixed.
Trust me, the 'bug' is in every version. You may not, however, notice it in every single VST(i) that's out there. For example: I use Cakewalk's Dimension Pro VSTi & Cakewalk's Perfect Space VST, both of which require parameters that SF cannot handle correctly in the save feature (implementation of set parameters, as well as playback itself are perfect though). Now, as I've not used Dimension Pro until a few months ago, this was never an issue for me. Now, of course, it is. Perfect Space has never saved correctly, but as it has its own internal save function, I've never been too bothered with the quirk between it and SF. The problem, however, seems to have a common source and as Kenneth pointed out in another thread just before, he's "working.. working.. thinking.. thinking..".
In short: you may not notice the problem at the moment with the older version & the VST(i) that you're currently using, but you may well find things a little different when using a new VST(i), much like I did with the aforementioned Cakewalk features. That said, however, if the version you're using now works fine for you, then, for sure, stick with that until Kenneth has come up with a working solution (which he always does eventually anyway).
Good luck mate and remember that SF is always a work-in-progress ;)
Oh i see... so maybe the bug manifests differently in each different VST, anyway the one i use, i garantee it always worked perfectly when using the set default option in all previous versions, so at least with this vst there isn't much problems, except now in the current version. The one i use and i used douzens of times in the past without problems is Garritan Ambience.dll so i don't know about the others, i just tested this one several times yesterday in the new version and then in the older version and that extra entry is only missing in these new versions, according to what you say this is quite weird then :) Must be because of the way the vst was done, i don't know.
Cool, I use Garritan Ambience as well - it's pretty awesome as a VST. Now, Garritan Pocket Orchestra as a VSTi, however.. has the problems as described ;)
I'm not a programmer, so I cannot tell you what the reasons behind it are (at least, none that make sense to me, so explaining it to anyone else would be silly ;) ).
Patience my friend. All will be well in the end :)
Thanks :) By the way i am a programmer, but only in visual basic.net so i understand about these things of programming, even tough i am definetly not experienced in handling vst, soundfont and midi stuff in visual basic, lool