ZynewaveHi,
Sorry to hear about your troubles. The only .dll files that the Podium installer installs are the Zynewave VST plugins, and (since 3.1.0) the optional ReWire.dll file. The Podium installer does not install or update any Windows system files. I have no idea whether the ReWire.dll file affects the Windows system the first time it is run. You could try installing Podium without the ReWire.dll feature.
I googled “ntalpcsendwaitreceiveport” and the first post that came up was this:
I haven’t checked other links to the problem, but it seems the problem is quite common.
Are you using XP Home or Pro / 32 or 64-bit?
ZynewaveHmm, this may be something that have gone bad in the latest 3.1.0 update, where I did some track-related fixes. I’ll investigate this.
ZynewaveThanks for your suggestions Telenator. Yes, too much time was spent on the Mackie implementation, but this was a feature that had been requested numerous times in the past. I’m glad to finally have it crossed out on my todo list. As for the nearest future, I’m currently doing some experiments with the Podium file management, which would apply to your no.5 feature.
ZynewaveThe Podium free updates are identical to the “not free” version (apart from the specified limitations). The Free releases are just published some months after the licensed version releases.
ZynewaveThe list of changes is linked to in the “Podium Free Releases” announcement topic at the top of this forum. Read the first post in that topic for instructions on how to get notified by email upon new Podium Free releases.
ZynewaveZynewave@4mica wrote:
is the option for the rewire.dll related to the new control support?
No. The bundled rewire.dll is to solve the problems that came with the update to the latest ReWire SDK (64-bit support) in the previous release.
ZynewaveZynewave@MelodyMan wrote:
Are cheaper controllers like the Presonus faderport also supported?
Haven’t tried it, and have not heard from users testing with it. If it can emulate Mackie MCU mode, it should work at least partially. Since it is a single fader device, there will be problems with the track navigation since Podium expects the device to support 8 faders.
Zynewave@rwelteroth wrote:
Hi Frits,
beta4 works (almost) as expected. The indicated channels can now be controlled by the respective channel on the controller no matter wether there are effects or not. Only the visible channels can be controlled. If I change visibility of channels for example by opening or closing a group channel, channel assignment is adjusted (ok at least to my needs).
Only thing I would change is that neither the master channel nor return channels can be assigned to the controller (or am I missing anything?). At least the possibility to control the return channels would be nice.
Maybe it’s alright for 3.1.0 right now but as you are currently working on this, some more improvements might be welcome and maybe also quite easy to implement (one idea that comes to mind here is the option to fix the master channel to controller channel 1 while assigning the other controller channels dynamically).Greetings
Richard
Thanks for testing. Please try beta5. I’ve set the inclusion of master and bus tracks as default, and only if the device is a genuine MCU (with its own separate master fader) will the master track be deselected from the main faders. Track 1 should then be the master track on the NanoKontrol2. It won’t lock fader 1 to the master track, since this will stray too far away from MCU compatibility I think. Let me know if there are other minor issues that needs to be corrected.
ZynewaveBeta4 is up. This should fix the problem with faders/pan knobs not responding on some tracks. Please report if there are further problems.
Zynewave@Klemperer: Thanks for testing. Good to know that Kore2 now works.
@rwelteroth wrote:
Create a new group track with one child track and automation of the level on the child track.
In the mixer, these 3 tracks can be controlled by the first 3 controls on the nanokontrol.
Add an vsti effect to the child track and the child track cannot be controlled with the respective control channel on the controller anymore.
Remove the effect from the child track and it can be controlled again.Can anyone confirm this?
Confirmed. I’ll look into this tomorrow. I’ll probably upload a beta4 once I find out what’s going on. With a bit of luck, that will be the final beta before 3.1.0 can be released.
ZynewaveZynewaveZynewave