ZynewaveFrom the Podium 3.2.4 release notes:
Podium can create a PodiumDebugLog.txt file for diagnostics of ASIO drivers. Add the line “DebugLog=1″ under the “[Settings]” line in Podium.ini to enable creation of the log file.
1/ Start Podium.
2/ Select the menu Setup>Explore Setup Folder.
3/ Quit Podium.
4/ In the file explorer, double-click Podium.ini to open it in notepad.
5/ Add the line DebugLog=1 under the [Settings] line.
6/ Save Podium.ini and close notepad.
7/ Start Podium.
8/ Try to configure the ASIO driver to get the 192k error message.
9/ Quit Podium.
10/ In the file explorer there is now a PodiumDebugLog.txt file. Email this to me.
ZynewaveI run Windows 7 with the font scaling set to 110%. Podium adapts to this very nicely except for the main Setup/Preferences dialog which overflows the available space.
Thanks. This is now fixed. There were a handful of other dialogs that didn’t scale properly as well.
The Shortcut Keys guide insists on using Internet Explorer when all other actions involving web-based content open the default system browser (in my case Firefox). I would prefer to not have to use Internet Explorer at all.
I have Chrome as my default browser, and I would also prefer not to have IE open. The default way to programmatically open a URL unfortunately does not work when a # anchor is included. So Podium calls iexplore explicitly with the url. In a future update Podium could try to look up the users default browser in the registry.
ZynewaveNot directly in the note editor. You can use ‘pitch bend’ automation. If you have a MIDI keyboard with a pitch bend wheel, you can record the automation. Otherwise you can add the automation from the ‘Track>Automate parameter>MIDI parameters’ submenu.
ZynewaveHi,
I assume you have followed the hints given on this page:
http://zynewave.com/recommended-freeware-plugins/
If you add new plugins or change your plugin folder structure, you need to rebuild the plugin database in Podium. On the “Create New Project” page, select the “Rebuild and load plugin database” option before creating the project. For existing projects, select the “Rebuild and load…” command from the “Devices” menu on the project page.
Zynewave@The Telenator: Your license does not expire, so you can continue to use Podium and WarmVerb after your upgrade period expires. If at some point in the future Podium gets a feature upgrade that is useful to you, you can at any time purchase a new upgrade period.
ZynewaveWhen 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.
ZynewaveUsing 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 ‘+’).
ZynewaveThere 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.
ZynewaveCurrently 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.
ZynewaveAfter 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.
ZynewaveA 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.
ZynewaveHi,
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
ZynewaveI 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.
ZynewaveSorry 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.
Zynewave