Zynewave.
swayzakhi
I’ve just rebuilt my DAW around an Asus P5K-E WiFi motherboard, with E6600, 2 GB ram, 2 x 320GB WDs, RME Multiface I, Yamaha sw1000xg, Windows XP SP3.
Everytime I launch Podium, it allows me to create a project then crashes … “Podium.exe has encountered a problem …etc.”.
This seems to happen after I minimise the arrangement and then right click on the Windows Start button to open the Explorer.
Most perplexing and frustrating ..
UPDATE: After disabling the VSTi scan, it didn’t crash so maybe a rogue plugin ?
Zynewave@swayzak wrote:
This seems to happen after I minimise the arrangement and then right click on the Windows Start button to open the Explorer.
Minimize the arrangement? You mean minimize the main Podium window?
Have you enabled the “release drivers when Podium does not have focus” option in Preferences?
Please send me a copy of your project file, as it is before the crash.
roninI had a similar problem. I use a lot of free plugs and almost every host I’ve tested crashes while scanning them. Podium was clever enough to mark plugins which crashed immediately but there seem to be some other bad plugs which crashed podium after the scan was completed. You can try to save a template after the scan has completed, reopen podium and use the template.
swayzak@ronin wrote:
I had a similar problem. I use a lot of free plugs and almost every host I’ve tested crashes while scanning them. Podium was clever enough to mark plugins which crashed immediately but there seem to be some other bad plugs which crashed podium after the scan was completed. You can try to save a template after the scan has completed, reopen podium and use the template.
I don’t suppose there is a list round here of “rogue” plugins for Podium is there ?
I got no message about a specific .dll.
It HAS to be a plugin though because it’s stopped doing it on this project (with no VSTi scan).
I’ve got too many now to try them one by one.
I will say that Renoise also flagged up Vaz Modular 3 Effect dll, Korg midifilter/mixer/mixer 2/mixer 3 dlls (from Legacy collection) and the Tascam GVI nfx as problems (and disabled them).
I could try these to start with …
However, after deleting the scan file created (as advised by Renoise) to try and scan them again, they have been enabled now.
swayzak@Zynewave wrote:
@swayzak wrote:
This seems to happen after I minimise the arrangement and then right click on the Windows Start button to open the Explorer.
Minimize the arrangement? You mean minimize the main Podium window?
Have you enabled the “release drivers when Podium does not have focus” option in Preferences?
Please send me a copy of your project file, as it is before the crash.
Yes – minimising the whole Podium window.
Unfortunately I saved over the original with this new non VST scan version.
Would it help if I recreated the original and sent it to you ?
EDIT Actually I think the minimising thng is a red herring – I recreated the VST plugin search and came back to the PC a few minutes after the search had finished. The crash message was there with Podium window maximised. I’ve sent it to you anyway Frits in case it gives any other clues.
Zynewave@swayzak wrote:
@ronin wrote:
I had a similar problem. I use a lot of free plugs and almost every host I’ve tested crashes while scanning them. Podium was clever enough to mark plugins which crashed immediately but there seem to be some other bad plugs which crashed podium after the scan was completed. You can try to save a template after the scan has completed, reopen podium and use the template.
I will say that Renoise also flagged up Vaz Modular 3 Effect dll, Korg midifilter/mixer/mixer 2/mixer 3 dlls (from Legacy collection) and the Tascam GVI nfx as problems (and disabled them).
I’ve also experienced what ronin described on my previous PC. I never determined exactly which plugin was the sinner, but from your list I had the Vaz Modular installed.
A bad behaving plugin may not cause a crash during the scanning, but it may still corrupt the host memory without the host knowing about it. This can then lead to a crash later on when the host accesses whatever is stored in that memory area. So if you experience this type of crash, a good advise is to save your project immediately after a scan, exit Podium to clear out the memory, and then restart Podium. The problem will then only reappear if you happen to load the rogue plugin on a track.