Zynewave.
nicholas.hHi, I’m not sure if this is the right place to post, as these issues affect 324 also, but I noticed a few low-hanging fruits (?) which could be addressed:
In the Sound Editor toolbar, the Scalpel tool doesn’t do any slicing. Instead, it functions exactly like the Pencil tool, editing the sample data. (Might just be a behind-the-scenes action mapping issue. I’ve just hidden the button for now.)
More trivially, the Help tooltip for the Pencil button is identical in both sequence editor and sound editor. I like this design efficiency, but we should note the different behaviour in each context: for example, in the Sound Editor, the Pencil tool cannot select and rearrange events, so the tooltip is confusing. (Okay this is nitpicking, sorry! But maybe some basic clarification in the text could be good!)
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.
WhisperingTreeAfter I purchased Podium, I first attempted to install v3.2.5 Beta5 x64 on my Win8.1 x64 PC. It didn’t install anything, such as programs under C:\Program Files\, and threw no error messages. Therefore, I installed v3.2.4 x64, and it has been working fine.
Perhaps the problem is that I have neither the Microsoft Visual C++ 2015 Redistributable nor the KB2999226 Universal C Runtime installed before installing v3.2.5 Beta5. I found update 2, which includes both, here: https://www.microsoft.com/en-us/download/details.aspx?id=51682
Including 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. Also, if Podium v3.2.5 x86 installs the x86 redistributable, a user with x64 Windows will need to install the x64 redistributable later when an x64 program is installed. Better for the x64 Windows user to only install the x64 redistributable, which supports both x64 and x86 programs.
My first suggestion is to put a link the latest update of the Microsoft Visual C++ 2015 Redistributable on the Podium downloads page with note saying that it is a requirement for v3.2.5. My second suggestion is to throw an error dialog in the v3.2.5 installer if the redistributable or KB2999226 is not installed.
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.
WhisperingTreeMy 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. I now have Podium_325_x64_beta5.exe in the same folder as Podium.exe. I also now have Microsoft Visual C++ 2015 Redistributable Update 2 x64 installed.
I am still learning v3.2.4, so often I don’t know whether a problem is due to my lack of experience with Podium versus a Podium bug. When I find a problem, I would like to try v3.2.5 to see if it is a bug already fixed. I could solely use v3.2.5 beta instead, but I understand it is not fully tested and could have bugs not in v3.2.4. So I see the need to go back and forth between v3.2.4 and v3.2.5 beta.
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)?
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.
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.
nicholas.hHi, I just gave beta6 a run, testing the 64-bit edition on Windows 8.1 and 32-bit edition on XP.
On Windows 8.1, no issues.
On XP, the Browser no longer showing any content. No subfolders, no WAVs that were previously displayed.
Also on XP, the Setup > Load Color Setup menu list is empty.
(There’s also a UI issue I encountered: The MIDI Event list gets ‘dirty’ when transposing notes in a separate MIDI editor window. New event list items are added, but older entries are not removed… until you close the window, or change to Event list to the timeline and back again. But you might want to forget about this for now, because it’s not specific to the beta. It also occurs in both editions of 3.2.4.)
ZynewaveHi Nicholas, thanks for alerting me on the XP issue. I’ve uploaded a new beta7 where this should be fixed.
nicholas.hThanks, can confirm the files are now correctly displaying, previewing, loading etc. in the Browser and Load Color Setup menu on XP.
CarbonflakeI’ve updated to beta 7 and both splash logo and “about” section show “3.2.5”.
Is it just an oversight?
Probably as the metronome folder feature is present meaning I’m running the latest version.
And any chance of fixing the scalpel tool in the audio editor? At the moment, if works just like the pencil tool.
Thanks!
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?
ZynewaveBeta8 is now uploaded, and that is hopefully the last beta before I’ll release 3.2.5.
I have been experimenting with sample-rate conversion, and I chose to integrate the r8brain-free-src library in Podium. It is created by Aleksey Vaneev of Voxengo. Link:
https://github.com/avaneev/r8brain-free-src
I needed SRC to complete the newly added support for custom metronome sounds. Now the metronome sound files will play at their original pitch no matter which sample-rate you use in your arrangements. So far the metronome is the only place where I use the SRC, but in future Podium versions I’ll work on supporting SRC for resampling of sound files, and on sound events placed in arrangements.
nicholas.hHi, I gave beta8 a test (32-bit only on Win 8.1 and XP), set preferences to look at a folder with four Metronome sounds, each at a different sample rate. They all played back correctly at original pitches as hoped and expected.
Oh yeah, I tried thinking about uses for the Scalpel tool in the audio editor. (I only mentioned it before because I assumed it was mismapped.) Really it should split or slice things up… but it doesn’t seem worth the hassle to duplicate arrangement view functionality. So, could the Scalpel button just be hidden by default?
LevendisHi nicholas.h,
You’re able to adapt any element of Podium’s GUI by editing Editor Profiles. Access the controls from Setup > Editor Profiles….
Here is a setup file which has been altered to exclude the scalpel tool from Podium’s default setup:
Setup file that eliminates scalpel tool in Sound Event Editors
Use the menu command Setup > Load Setup… and select the file to apply it.