Official release note:
The Podium codebase has been updated according to modern coding practices and standards. After 30 years of development the codebase needed to be modernized to be able to exploit advancements in hardware and software technologies. The 3.4.x releases will be the last to support Windows XP.
As I’ve mentioned previously on the forums, I’ve been doing a major rewrite of the codebase over the last couple of years. I felt this was an investment I needed to make in order to be able to continue developing Podium in the future. In addition to the technological advancements, I’ve also gained more coding experience over the years, so there were places in the codebase that needed to be improved.
Beta1 is available on the My Downloads page of license owners. I’d appreciate any feedback if you try the beta1.
This release contains numerous bug fixes and performance improvements, too many to list. Since a large part of the codebase has been rewritten there is a risk that there are bugs I have missed. Please keep backups of your projects if you try the beta.
Also, are any of you still using Windows XP?
Do you think that with such a rewrite, Linux support could be thought about ? this would make transitioning between the two OSes less of a pain.
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.
Yeah I can understand the priority.
Is the VST3 support considered a high priority ? as lots of VSTs start to only have vst3 versions due to steinberg not licensing vst2 at all anymore
(synthesizer v being an example of a vst3 only vst)
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.
Very exciting to see further development. Podium is still my DAW of choice.👍
Early indications are that 3.4 is perfectly stable, and a VSTi synth (Wiggle) that previously would not load, now loads fine. Which is awesome. So far, big 👍.
Excellent to see this 🙂
I’m still using an XP box for music making, but the two albums I’m working on will be the last on that machine. I have bought a new one as a replacement which will run newer plugins, but I need to test jBridge with it. Most of my arsenal of plugins are from 2005 and before, and 32bit only. A lot are late betas of things that I preferred the sound to the final product, and there’s been little released since then that I’ve wanted to get – my needs are very simple 🙂
I’ll give 3.4 a spin and see how I get on!
A strange behaviour is happening with the sampler plugin called Nuance by New Sonic Arts. When I open Podium 3.4, Nuance gives the “plugin has performed an illegal operation” message. I close Podium, restart it, and Nuance works fine. Happens every time – I need to open Podium, close it, then the 2nd time Nuance works fine.
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).
By the way, I would have a suggestion, it could be a good idea to have an alternative purchase method that would be similar to fl studio but more as an alternative
basically either paying the current 50$ price for a year long update licence or maybe having a higher pricing tier for lifetime updates, something around 200$
Hi Fritz. I tried the Podium beta2 3.4. 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.
Anyway, thanks, and good luck.
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.
Final Podium 3.4.0 is now released.