Zynewave.
civelloHi there, first I want to say I’m pretty impressed. Coming from software designed with very powerful midi editing capabilities (Sequitur on BeOS), so far Podium is the best I’ve seen in the windows world.
So, after installing the demo (1.05) and getting a few plugins loaded (multitimbral Halion, z3ta+, and a few Powercore plugins), Podium is hanging on the splash screen. There are three little windows in the taskbar, one with just the Podium icon, a second that says ‘Podium Demo’ and a third that says ‘C:AudioVST-PluginsHalionHalion.dll’. The only thing I can do is right-click on the ‘…Halion.dll’ icon in the task bar and choose close, which closes everything. Any ideas?
d
kagemushaHi,
As far as I know one of the two podium Icons is the asio (audio) driver. It appears briefly when starting podium. It is possible it hangs when the driver is not accessible. But even in the latest versions, podium just loads with a warning.
The Halion icon I never saw. I thought podium only loaded/initialised the vsts when enable the monitoring switch or start playing and not while loading the application
With which audio drivers are you working? Is it ASIO?
Is there something else using the audio card
ZynewaveHi civello,
To be able to start Podium without hanging, you could temporarily move or rename your project file (.pod), so that Podium will not find and auto-load the project on startup.
The Halion icon I never saw. I thought podium only loaded/initialised the vsts when enable the monitoring switch and not while loading
If plugins are imported as multitimbral, they are configured as global plugins and thus are loaded when the project is loaded.
After starting Podium you could try to load the moved/renamed project to see if the Halion dialog will appear again and if so, what the the dialog is telling you.
The extra Podium icon in the start bar could be the lingering Splash window. Not necessarily a driver dialog.
Frits
civelloHey guys, my audio interface is a MOTU 828mkII — Fritz, before I saw your reply, I moved Halion temporarily out of the c:audiovst folder, then when Podium loaded, I removed the Halion device. I restarted the program, then re-imported Halion, added a few Halion tracks, saved, and everything seems to be alright (well.. z3ta isn’t retaining the patch I selected for it and Halion’s banks are cleared out, but I think that’s a separate issue that has to do with me getting used to this program… I hope?)
If I see it again, I’ll try renaming the .pod file and see if it gives me more info when it tries to load Halion.
thanks!
civellojust read your response in the ‘Preset recall bug??’ thread…gotcha.
comprehensive new program => learning curve! 😉
Zynewavejust read your response in the ‘Preset recall bug??’ thread…gotcha.
comprehensive new program => learning curve!
Great, this forum software is turning out to be a very valuable support tool 8)
You might also want to check out this topic regarding library presets.
kagemusha@Zynewave wrote:
The Halion icon I never saw. I thought podium only loaded/initialised the vsts when enable the monitoring switch and not while loading
If plugins are imported as multitimbral, they are configured as global plugins and thus are loaded when the project is loaded.
The reason I assumed it is because when I load a project with Halion it takes a lot of time to start playing (or after pressing the monitoring button) .But the reason is that it’s only at that moment Halion start to load its samples >> not while loading the project.
ZynewaveThe reason I assumed it is because when I load a project with Halion it takes a lot of time to start playing (or after pressing the monitoring button) .But the reason is that it’s only at that moment Halion start to load its samples >> not while loading the project.
There are several steps involved in starting a plugin. Loading the project will instantiate global plugins so you can open the plugin editor. The VST2.3 spec introduced a new initialization step that is supposed to occur when adding/removing a plugin to the audio processing. Podium calls these functions when starting monitoring, so it may well be this that causes the delay you notice. I doubt there are any plugins other than the Steinberg plugins, that respond to these new effStartProcess/effStopProcess functions. Also any plugin presets are only recalled when monitoring is activated.