Thanks for notifying me. This was brought to my attention by another user a couple of days ago, and I thought I had fixed it. It was a WordPress or perhaps a plugin update that started the issue, but the problem seems to be with the site caching. I’m using the CloudFlare service to cache the website on servers around the world. It is apparently only some parts of the world that has the problem. I have not seen the problem myself here in Denmark. If I disable the CloudFlare caching, the problem went away for the other user, who I believe is in Poland. I just tried to purge all caches on the CloudFlare control panel. Could you tell me if you still see the problem?
It’s frustrating how much time I have to spend maintaining the website. I need to update WordPress and its plugins for security reasons, but then I risk running into these kinds of problems. The latest update to the slider plugin seems to have messed up the video scaling. I’m considering removing all pages with videos and animated slides on the website, and just refer to the YouTube page.
Apologies for the delay with the next beta. I have spent the last couple of weeks working on my iOS part-time job. I will return to Podium development again this coming week.
Hi,
I did not know about this plugin. Perhaps it became freeware only after I created the recommended freeware plugin list. I did not find any good 32/64 bit VST drum plugins at the time, so it is perhaps time that I update the plugin list.
Cheers,
Frits
Thanks for the feedback and for testing. I plan to upload a new beta next week.
Once again, I’ve had to spend some time fixing issues with updates to the website backend software. Let me know if you find something that is broken.
Perhaps the plugin works lige e.g. NI Kontakt, where only one VST preset containing the complete current state of the plugin is exposed to the host. You will then need to use the VSTi’s editor to load presets. If there is a MIDI input indicator in the Xpand editor window (like in NI Kontakt) you could check that to see if your MIDI keyboard input is received by the plugin.
Yes, the problem and solution may be what MLS described. The underlying bounce track can become divided into multiple sound files if you have been using the segment cut/paste commands. It’s a system I’ve been meaning to change, so that hidden bounce tracks will always automatically adjust to be just one sound file the length of the entire arrangement.
Hi, given the SDK changes, can Windows XP continue to be supported for foreseeable versions? Thanks.
That’s a good question. I haven’t yet tested the latest Podium beta on my old XP box, but compilation of XP compatible code is still supported in Visual Studio 2015. However, I read somewhere on the Microsoft site, that they intend to drop XP support in the next major VS upgrade. If Podium should continue to support XP, I will have to continue to use VS 2015, which means I won’t be able to take advantage of future improvements to both the C++ language and the VS compiler 🙁
I don’t know when, but at some point I will have to drop XP support. Another incentive to drop XP support, is that the libraries the compiler uses to enable apps to run on XP are older and not as optimized as the newer non-XP libraries. The newer libraries takes advantage of more advanced API’s introduced in newer Windows OS versions.
Hi Daid,
How much RAM do you have in your machine?
Are you trying to bounce only the master track?
Instead of moving all plugin tracks into a group track, you could try to bounce individual plugin tracks. This should reduce the resources required on subsequent master track bounces.
Frits
Hi Jeremiah,
First of all, please confirm that you are running Podium x86. The RGC sfz plugin is not available as a x64 plugin.
I assume you refer to this plugin: http://www.memorymoon.com/me80.htm
The demo installer is only for v2.1. Can you confirm that the problem also exist with v2.1 demo, or is there a more recent demo version?
Beta3 is up. Apart from further code optimizations, I’ve added one small new feature:
Would it be worthwhile to make the metronome sound folder location configurable in the Preferences dialog? Any other wishes for metronome enhancements?
Some ideas I had:
Allow “Metronome3.wav”, “Metronome4.wav” etc. to make it possible to have custom sounds for each beat. You could e.g. record yourself saying One, Two, Three, Four.
Add a second pair of bar/beat gain settings in the Metronome preferences, to have separate levels for preroll and punch-range. That would e.g. allow you to mute the metronome in the punch range.