Zynewave.
wickI have decided to try the demo again to consider moving over, but I’m hitting a problem before I get going. On first startup after installation, selecting my vst folder, halfway through the scan the program just disapears. On starting up again I’m back to the start again – not even my audio settings have been remembered. I assume its reacting badly to a particular plugin, but how do I find out which one and why, when other hosts dont have a problem scanning the same plugins?
PodianerAre there any Betabugs Plugins in your VST folder? I remember some of them not being imported well by using the “scan” option, but they were fine when imported seperately. Before you start creating a new project, try to rename your Plugins directory. Then start a new project, and click “create”. Now save your project. Rename your plugins directory and then try to import your plugins by pressing the button on the devices tab.
Hope this helps..
wickWell, I have created a project without scanning for VST at all. I then saved the project and requested the scan, which had the same result (crash) but at least I dont have to go through the setting up again. Is there any debug log that shows what happens? I appreciate it may not show the faulty plug but it would at least show all the successful ones which would be a start. Otherwise I’m into a laborious session to find the faulty plug (I dont have any beetabugs plugs). To be honest, at that stage I probably give up.
ZynewaveThere is no log, but the filename of the currently scanned plugin is displayed in the import dialog. It should be scanned alphabetically after filename. The file displayed when the crash occurs should be the sinner. If you find out which plugin is causing the crash, then please let me know.
thockinPodium *always* crashes during plugin scanning for me, too. It seems to crash on the VSTi versions of the ImageLine (FLStudio) plugins – Sytrus, Wasp, SimSynth, Poizone, etc.
What’s going on? I really want to give Podium a shot, but this is dumb.
Can you PLEASE implement a safe scan that doesn’t blow up? These plugins are OK in other hosts…
koalaboyI just registered to say I had this exact problem this morning. I downloaded the latest demo yesterday, and fired it up this morning before going to work (I’d not got on with it last time I tried, about a year ago, but I found the videos on the wiki very informative this time).
Anyway, once it came to scan the plugins, it hung my entire machine 😯 when it got to the FL Studio (7) multi-out VST. I was going to have another go tonight with all of the FL VSTs moved elsewhere, as I want to give Podium a good try, but I don’t have a problem with them anywhere else.
I hope this helps.
Michael.
koalaboyAs an update, I removed the following two VSTs from my folder:
FL Studio VSTi.dll
FL Studio VSTi (Multi).dll
After this, Podium works fine. These are the files for FLStudio to be a VST within another host, and one of these at least is causing the problem.
Michael.
ZynewaveI downloaded the latest FL7 demo version (which includes a bunch of Imageline VST demo plugins). I get a crash upon import of one of the IL plugins AFTER one of the main FL Studio dlls have been imported. I tried renaming the plugins to reorder the import order, and it crashes no matter what plugin comes after the main FL VST. Weird :?. I’ll do more experiments tomorrow.
ZynewaveThe crash seems to occur because the Podium memory pool gets corrupted at some point during scan of a FL Studio plugin. Debugging did not help in determining exactly where the crash occurs.
But I think the crash occurs due to multi-threading conflicts. Podiums scan procedure is running in a separate thread, and it appears that IL plugins are messing things up if some plugin functions are called from a thread different than the UI thread. Question to thockin and koalaboy: Are you using Hyperthreading or Dual core/processor PCs? If so, you could try to configure Podium to use only one processor. That got rid of the crash on my system: Bring up the Windows Task Manager, locate the Podium.exe process, right click, select “Set Affinity”, and ensure only processor is selected. This setting is not remembered, so quitting Podium will restore the full affinity mask.
I have modified the Podium scan procedure, so that all plugin calls are done from the UI thread. Hopefully that will also fix the reported issues with scanning of Betabugs plugins. Fix coming up in 1.80 release.
koalaboyI am using a dual-core machine, yes. That may well do it. Something else to bear in mind is that my FL configuration – and I don’t know if this continues in the VST mode – is set to dual-processor, as they implemented multicore in FL7, so that may have some effect.
It doesn’t really worry me too much, as I don’t ever use FL in VST form – I just always install it regardless. I’m happy to leave those two VSTs out. I’m never keen on setting process affinity, as that defeats the point of dual-core 8) — I did, however, do the test for you, and sure enough it doesn’t crash if I set the affinity, so it certainly looks like you found the cause.
Anyway, hopefully it’s helped stop another crash situation.
Michael.
thockin@Zynewave wrote:
Question to thockin and koalaboy: Are you using Hyperthreading or Dual core/processor PCs?
Indeed, it is multi-core. This makes the crash on FLStudio plugs go away. However, now it hangs when probing the FL Studio plugins about half the time. I just scanned 6 times and it hung 3 times.
Zynewave@thockin wrote:
@Zynewave wrote:
Question to thockin and koalaboy: Are you using Hyperthreading or Dual core/processor PCs?
Indeed, it is multi-core. This makes the crash on FLStudio plugs go away. However, now it hangs when probing the FL Studio plugins about half the time. I just scanned 6 times and it hung 3 times.
It’s likely that this problem is not there with the fix I made to the scan procedure. The 1.80 demo version will be released within a week.