Hi Luc,
If you are using Podium Free, then there have been updates to the full version since then that improves the scan/import. I just tried scanning my x64 plugin folder from Podium 3.4.2 x86, and the import dialog shows a counter status message “Skipped x files that are not x86 compatible” without requiring restart. I do recommend though that x86 and x64 plugins are kept in separate directory trees.
Please note that Linux is not officially supported by Podium. I have no experience with Linux so I can’t test or comment on anything related to Linux. Current Podium version 3.4 can run on Windows XP even though minimum officially supported OS is Windows 7. Microsoft has ceased support of building for Windows XP in their latest Visual Studio developer tool, so to be able to take advantage of future dev tool improvements I will need to upgrade the dev tools and abandon XP support. This may mean that the future Podium version 3.5 will not run on Linux.
Hi Andy. I’ve just uploaded the demo version of the latest 3.4.1 release. The download link is on the Podium product page. If you want to do more extensive stability testing then send me a mail and I can give you access to the latest full version. If you find stability issues with Podium I would like to get them fixed.
Major version upgrades are traditionally being developed on an independent branch, separate from the work being done on minor feature and bug-fix updates to the current major version. Podium development is all done on one branch/timeline, and my aim is to implement and release feature updates gradually. So the major.minor.revision version numbering is somewhat misleading for Podium. I’ve been considering adopting the date based versioning scheme (“21.9”, “21.9.1”, “22.2” etc.).
I plan to increase the frequency of Podium releases in 2022. Your Podium license is still valid after the upgrade period expires. There is a small discount if you renew the upgrade period before it expires, but you can renew it any time in the future when there are new Podium features that you may find useful.
Hi dagabond. Each project still has its own plugin database embedded in the project file. The plugin database project was introduced in a Podium update with the intention of making it simpler to update your projects with changes to your plugin installations. Your description is the correct way to go about updating plugin setups in your projects.
Final Podium 3.4.0 is now released.
Beta3 is up. It fixes some bugs with the project and track templates which were not working properly. This version also contains a revision of the edit history undo/redo descriptions which now contain more detail. The edit texts have also all been made translatable.
The message I get from Nuance is “Set Audio Properties”. I should add that I’ve been using Nuance in Podium for years without any problem. This recent bug followed an update from New Sonic Arts. There has also been a graphical glitch with their Granite software. So I guess they have made changes that are somehow incompatible.
That error is unfortunately not related to the error I encountered with Nuance v2.125, so even if I create a workaround for the Nuance problem I found it is unlikely to fix all issues with this Nuance version. I’m also not happy about changing the way Podium gets preset bank data from plugins, as this may cause other plugins to start malfunctioning. I’m hoping there will be a Nuance update that fixes these issues.
Thanks for testing. I tried the Nuance v2 demo version and I did experience a plugin crash though I am not sure if it is the same as you encountered. The Nuance plugin crashes when Podium tries to get the Nuance preset bank data from another thread than the main UI thread. I can provoke this crash by deactivating the power button in the arrangement editor with Nuance loaded on a track. This is the first plugin I’ve encountered that has this problem. To fix this I will have to move the preset sync into the main UI thread, which unfortunately means the UI can be blocked for a noticeable time depending on the number of plugins loaded. Before I make that change, I would appreciate if you can confirm if this is the bug you also see. I’ve uploaded a new beta2 in which I’ve added more details to the crash notification. Check if the message says something like: (Nuance.dll – GetBankPreset).
The 3.4.x releases will be maintenance updates where I will work on stability and completing some half-finished work, such as the support for language translation.
VST3 and WASAPI is something I will look at for 3.5 and beyond. The 3.5 release will be where I upgrade from the outdated XP platform toolset, which is no longer being updated by Microsoft, to the latest toolset that has support for the latest C++ language features and more advanced code analysis tools.
The codebase is prepared to support other platforms, but currently only Windows is supported. Years ago I made an iOS port using an SDK from a company that has since shut down, so I can no longer build the iOS version. Don’t get your hopes up for Linux. Currently all my focus is on developing Podium for Windows.
Hi rudesasa. Sorry for the late response. The merge edit action does not take any event fades into consideration. You should do a bounce render of the (group) track where you have your crossfades. The bounce will capture the audio as it is mixed on the track. Afterwards you can use the “Bounce/Export Bounced Audio to Sound File…” menu command if you want to process it in another app.
The payments are now refunded. Please check your PayPal account to verify.
The first two payments are still marked as “pending” on my PayPal panel. I’ve sent a message to PayPal support asking if there is a way we can cancel these two payments.