Zynewave.
aMUSEdI’m getting occasional random crashes at startup – splash screen loads and then I get an exception with some stuff about divide by zero and a load of numbers. Can’t replicate it easily as it doesn’t happen all the time but just randomly every now and then and I have to reload (which it does fine the second time)
TechnophobiaHave you got any VST’s trying to call home (Tone 2 stuff is a real pain).
I was getting something similar a while back which I put down to Tone 2 stuff. Once I had stopped Podium from getting Internet access it seemed to go away. Not entirely sure they were divide by zero, but definitely random at start up though.
aMUSEdI do have one Tone 2 synth (Firebird +) but its legit so I don’t see why it would be “phoning home”. Also it’s not happening on plugin scan (as Podium afaik doesn’t do a startup plugin scan except when the project is first created) I don’t have an open internet connection anyway on the PC I run Podium on (in fact it doesn’t even have Internet Explorer)
TechnophobiaMarkus (Tone 2) puts some kind of watermark in his latest synths/effects. I have definitely had Gladiator try and phone home on occasion when just opening podium (gladiator already scanned).
I have Internet on my DAW setup, but I disable it before I open Podium to cut down on nasty process/interrupt surprises when recording.
I have not had a crash for some time now so I am not quite sure why Gladiator was causing it in the first place and not now (it was definitely Gladiator though, because I un-installed everything else from Podium)…
Maybe Frits will be able to shed some light on this.
LiquidProj3ctI got Firebird+, Warmverb and Gladiator2. All of them are legit, and all of them phone home… I’ve complained several times to Markus, because this crash all the host I’ve tried… it’s a pain
aMUSEdCaught in the act:
ZynewaveWhen Podium is started, no plugins are loaded into memory. That only happens when you do a scan, import plugins or when you power on an arrangement which will load plugins assigned to tracks.
Does the crash happen before the main Podium window appears?
Most likely causes for crashes at this point, is the initialization of MIDI and audio interfaces, and possibly the ReWire system dll.
Could you post or email a report of your interfaces? (Generated from the Report page in the interfaces dialog).
One thing I would like you to try, is to disable any MIDI inputs and outputs you have enabled, and check if the crash still occurs when starting Podium. That may help narrow down the cause for the crash.
aMUSEdI didn’t think it was plugin related either.
Yes the main window is open (well opening) when it happens.
My interface is a NI Kore running on Win XP pro sp3.
I also have an Access Virus Ti installed so its ASIO driver is present on the system but I use the Kore as my driver in Podium (and most apps). Its a bit difficult to do the check you suggest because I could open Podium say 20 or more times and it not crash – it doesn’t happen often enough for me to be able to make a definitive connection with whether its the audio/midi interface or not (ie I might disconnect it and try opening Podium 20 odd times and not get a crash but that doesn’t mean it’s because of disconnecting it). How about error logging? Can it do that?
Zynewave@aMUSEd wrote:
How about error logging? Can it do that?
There is no error logging in Podium that can catch this type of crash.
How about that interface report? Can you post or email it?
Can you list the MIDI input and output interfaces that you have enabled?
aMUSEdI just did – NI Kore (midi and audio)
Zynewave@aMUSEd wrote:
I just did – NI Kore (midi and audio)
So do you have exactly one Kore MIDI input and one Kore MIDI output enabled, and no other MIDI interfaces?
When I asked for a “report”, I’m referring to the text file you can generate on the “Report” page in the interfaces dialog. It contains technical details that may help me.
aMUSEdThis?
Podium audio manager status report
Log period: 20/02/2009 19:18:48 – 20/02/2009 19:20:02
ASIO device: Kore Controller
– Supported clock sources: External
– Current clock source: External
– Supported sample rates: 44100, 48000, 96000
– Current sample rate: 44100
– Input channels: 2 (11)
– Output channels: 4 (1111)
– Input/Output latency, buffer size: 200/376, 176
– PerformanceCounter: 3579545 Hz
– ASIO sample types: 18, 18
Audio stream buffer errors:
– Output buffer skip count: 1
End of report
ZynewavePodium 2.18 is just released with a bug-fix that I’m almost certain is the cause for the problem reported here.
During my migration to the new delopment tool that I’m now using for building Podium, I managed to isolate a situation where a crash occurred in the initialization of MIDI interfaces. The crash was timing/multicore dependant, so that explains why it only happens on some PC systems.
Please let me know if you still experience random crashes at startup when using Podium 2.18 or later versions.