Zynewave's Forum Page

@pavouk100 wrote:

@Zynewave wrote:

Previous Podium releases were built using the 10 year old (pre-Vista) VS6 compiler. As Podium is now built using the latest Microsoft compiler and libraries, I’m suspecting that something in the Podium process has now become “Vista-aware” and thus enforces the User Access privileges. Probably both Synth1 and Guru are trying to write files in e.g. the Program Files directory, which is not allowed for non-admin user accounts.

I’ve checked, and I believe that the difference is in the embedded manifest. 2.18 contains element, which was not present in previous builds. This manifest element certainly makes the app ‘UAC aware’.

You’re right. That part in the manifest is now generated by default in the VS9 linker. I’ve been revising my build settings in VS9 the last few days, and I noticed that I have the option to disable UAC in the linker options. I wonder if it is a good idea to disable this? :-k There may be other factors in the new build that contributes to the changed behaviour of Synth1/Guru.

@kingtubby: I’ll probably release a 2.19 beta in a few days. I’d appreciate if you could try this out and see if this fixes the Guru problems.

@moikkelis wrote:

easy sidechain

Please post a description of how you would want the sidechain feature to be easier. I assume you’ve read the sidechain tutorials in the wiki. These explain the steps needed to configure a side-chain capable plugin for sidechain usage. Once you’re past that setup (which can be saved in a template for easy inclusion in your future projects), I don’t see how the actual use of the sidechain feature can be much easier?

I’ve just tried to become wiser on UAC and “run as administrator” by reading a bunch of articles on the Microsoft developer network website.

I learned that even though you are logged in as administrator, when you start an application it is still being run as if you are a standard user. So I still suspect the issue with Guru is that it tries to write to a restricted location (such as the “program files” folder or some parts of the registry), which requires administrator privileges. If so, then you have to use the “run as administrator” when starting Podium. Do you know where Guru stores your serial number info? Are any of Gurus data files stored in the Program Files folder?

Thanks for the project file.

It turns out that many plugins define different sizes for the VST midi events that are sent to the host. I have patched Podium so that it now accepts the different sizes. I briefly tested this with eXT2 and QuicKeys, which appears to work now. Fix will be available in Podium 2.19.

Podium 2.18 is just released with a bug-fix that I’m almost certain is the cause for the problem reported here.

During my migration to the new delopment tool that I’m now using for building Podium, I managed to isolate a situation where a crash occurred in the initialization of MIDI interfaces. The crash was timing/multicore dependant, so that explains why it only happens on some PC systems.

Please let me know if you still experience random crashes at startup when using Podium 2.18 or later versions.

I have regretted implementing the note timing randomization feature in Podium. It is a feature that would be best supported in a MIDI plugin. Once Podium gets support for MIDI plugins, I will consider removing this feature and instead offer it as a MIDI plugin. That will make the track properties more clean. With the MIDI plugin it would also be easier to add more parameters for extended control, such as what you request here.

No.

If you use two tracks, remember to copy the sequencs events as phantom events. That way you only have to edit the notes on one of the tracks, and it will automatically be applied on the second track.