ZynewaveI’ve updated to beta 7 and both splash logo and “about” section show “3.2.5”.
Is it just an oversight?
It doesn’t show the beta number, if that is what you’re missing. The only clue to beta version number is in the filename.
And any chance of fixing the scalpel tool in the audio editor? At the moment, if works just like the pencil tool.
That is on purpose, as I couldn’t find an obvious alternative use for the scalpel tool in the audio editor. What would you want the scalpel tool to do?
ZynewaveIf you are looking for the actual dll files, then they should be located in:
C:\Program Files\Common Files\VST2\Zynewave
Unless you selected a different installation folder for the plugins in the Podium installer.
In the Podium Preferences dialog, on the Plugins page, you should enter the “C:\Program Files\Common Files\VST2” as one of the scan folders.
ZynewaveHi Nicholas, thanks for alerting me on the XP issue. I’ve uploaded a new beta7 where this should be fixed.
ZynewaveHi Hermu. The release of new Podium versions has once again been delayed due to me having to take on other jobs. I will be adding another free year of upgrades to all existing customers once 3.2.5 is released. I released another beta version today, and I only have one feature I would like to work on before finalizing the 3.2.5 release.
ZynewaveAt long last I’ve wrapped up a new beta6. The changelog so far:
My five year old Windows7 development PC had for some time shown signs of instability, and a few weeks ago the power-supply short-circuited, so I thought it was time to upgrade. I’m now developing Podium on a new Windows 10 PC with the latest Microsoft developer tools. The old PC is repaired and repurposed as a test PC for Windows7 compatibility. Windows XP support should still be intact in the new Podium builds.
ZynewaveZynewaveZynewaveThere is no license number. If you go to the ‘My Downloads’ page you can download the installer again.
ZynewaveMy previous post was based on the assumption that the v3.2.5 beta download was an installer instead of a replacement for Podium.exe in a v3.2.4 installation.
Thanks for the feedback. I have written a Beta-installation.txt file that I will include in future beta zip files, to avoid confusion.
Which files are NOT compatible between v3.2.4 and v3.2.5 beta? For example, Podium.ini, PluginDatabase_x64.pod and project files (.pod)?
There should be no incompatibilies between 3.2.4 and 3.2.5. There may be some new Podium.ini setup settings in 3.2.5, so if you go back to 3.2.4, then these settings will be reset to default next time you start 3.2.5.
ZynewaveIncluding the redistributable in the v3.2.5 installer may not be the best solution. When the user installs v3.2.5, a newer update with bug and security fixes may be available.
The beta zip file contains just the executable, so for it to work properly, a ‘true’ Podium installer for a previous version needs to be installed beforehand. The installer should only install the Visual C++ redistributable if it is not already installed, or if the installed version is older. It will not remove a newer version that is already installed. The same applies for the ReWire.dll that is also included in the installer. To make the installer as user friendly as possible, I think it is a good idea to have everything contained in the one Podium installer file. I think there are users who would be annoyed if the installer shows an error, and asks them to download and install a separate redistributable from a Microsoft website.
ZynewaveIt should be working now. You may need to refresh the page in your browser. I’ve updated the login plugin, and revised my customizations of the login templates. As a bonus, I also believe this update has fixed the issues with the Lost Password page that many users have had problems with.
ZynewaveThanks for notifying me. It seems a recent WordPress update has caused an incompatibility with the themed login plugin I’m using. I need to do some php coding to make it work. I’ll report here when I have fixed it.
ZynewaveBeta5 is up.
There have been many posts from new users about unsuccessful scan/import of plugins. I think many of these are due to the x86/x64 incompatibility. In beta5 I’ve added code that checks for x86/x64 if a plugin dll fails to open. The plugin scanning dialog and the plugin import error message will show if plugins were skipped due to x86/x64 mismatch.
ZynewaveThanks for testing Nicholas. Good to know it still works on XP 😉 It was on my todo list to test that the new compiler creates code that still is compatible with XP.
ZynewaveThanks for the bug reports. New beta is finally up. Apart from a lot of code optimization, the following issues have been fixed:
Metronome changes working too however accelerating the tempo via the bpm value (say …120bpm and key in 200bpm) in the Tempo Event Properties box gives me an instant app hang if the song is playing at the time.
Some text is still cut off for me at 125% DPI setting, for example:
Minimize Podium while plugin windows are open, then restore it. The effect selectors’ “active state” color isn’t applied until the UI is refreshed in some way (change track values, change editor profile, open/close inspector, etc.).