Zynewave's Forum Page
Forum Replies Created
-
ZynewaveKeymasterWhen exactly does it crash? Right after you press OK or Apply in the interfaces dialog?
Years ago, the creative sound cards had to be used in 48000 sample rate to work. I don’t know if that still is a requirement, but that could explain the error message. Another reason for this kind of error message, is if you have other programs running that uses/locks the soundcard drivers.
Podium does not yet support WMA, so you need to get an ASIO driver working. You could alternatively try the free http://asio4all.com driver. In the ASIO4ALL control panel you select the WMA drivers of your AudioBox, and then select the ASIO4ALL driver in the Podium setup.
ZynewaveKeymasterUsing keyboard: With the first loop event selected, press the Insert key repeatedly to append ghost copies.
Using mouse: Start a normal drag/move of the first loop event, and then press and hold the control key when you drop it. Holding the control key changes the mouse cursor to an arrow, to indicate ghost copy. Press the control key repeatedly to toggle the mode for dropping either ghost copies or unique copies (mouse cursor toggles between arrow and ‘+’).
ZynewaveKeymasterThere is no shortcut to close it. It will stick around, until you open up another object that will replace the tabs. In the future I may provide a way to close a tab.
ZynewaveKeymasterCurrently there are no easy workarounds for that. The sound files are kept open/locked for performance reasons. It ensures the files can be read quickly when edited or streamed. This behavior may change in the future.
Rather than saving with different names and then relinking the files in the project, it may be quicker if you close the Podium project, save the sound files in your external editor, and then reopen the Podium project.
ZynewaveKeymasterAfter a few beta versions and emails, the bug seems to have been fixed. The Prodipe driver froze if it was initialized before the UI had finished initializing. Podium 3.2.4 has just been released with a fix for this, along with a few minor new features I had been working on.
ZynewaveKeymasterA bug was fixed in 3.2.3 which could have caused the wrong VST folders to be detected if you were using both Podium x86 and x64 versions. If you use Podium x64, check the VST folders in preferences does not have the ‘(x86)’ in their paths.
The Podium plugin scanning should only detect either x86 or x64 plugins, depending on which Podium version you use. Only if you have jBridge installed and enabled in Podium preferences will Podium scan both x86 and x64 plugins.
I would only recommend using jBridge if you have some essential plugins that are not yet available as x64. I dislike that jBridge creates wrapper files and saves these in the plugin folders.
ZynewaveKeymasterHi,
I don’t have any experience with the bcr2000, so I can’t say to what extent it will work with Podium. You will need to set up the bcr2000 for Mackie emulation mode.
Frits
ZynewaveKeymasterI have uploaded a beta of Podium 3.2.4. You can download it from the ‘My Downloads’ page.
I hope you got time to try the following:
Once you have configured your ASIO driver in Podium, and exited, open up the Podium.ini file in a text editor and add the line: DebugLog=1 below the [Settings] line. This will make Podium create a PodiumDebugLog.txt file the next time you start Podium. If Podium freezes, then please email the debug log to me. I will hopefully be able to see at which ASIO call the freeze happens.
ZynewaveKeymasterSorry for the delay. I started implementing the startup logging, but I had to interrupt this work to solve some issues with the website. I hope to have a version for you within a week.
February 26, 2014 at 22:17 in reply to: Restricted to Podium license ownersZynewaveKeymasterThis content is restricted to Podium license owners.ZynewaveKeymasterOk, I understand. To find out why this particular ASIO driver causes Podium to hang on startup, I think I’ll need to add an option to write startup progress to a log file. I’m going to visit family this weekend, but next week I’ll see if I can get a beta version ready that you can test with.
ZynewaveKeymasterIf you worked on a project, does this mean you have gotten Podium to start up without hanging?
Are you using jBridge?
If you still experience problems, also try temporarily to increase the ASIO buffer size, to see if that improves stability. I use a buffer size of 512. Smaller buffer sizes can hurt performance, and make it more sensible to CPU spikes.
ZynewaveKeymasterThe report looks ok. At least the driver is running when you initially enable it. In order to try to pinpoint the problem, could you please try the following:
Delete the Podium.ini file and start Podium.
On the Preferences/Plugins page, disable ReWire and jBridge (if you have it installed).
Restart Podium.
Enable your Prodipe audio driver, but only enable the main stereo output (no inputs).
Restart Podium.
If Podium hangs on startup, try the steps above once again, but this time select 44100 instead of 48000 samplerate.ZynewaveKeymasterThe next few releases will be minor improvements and bug fixes. I’m currently revising the code that handles VST plugin loading. The next feature update will be 3.3, and it will mostly include various UI improvements. I’ve recently purchased a 23″ touch display, so I’m experimenting with adding gesture support to Podium. That may appear in 3.3.
February 10, 2014 at 00:59 in reply to: Restricted to Podium license ownersZynewaveKeymasterThis content is restricted to Podium license owners.