Punch2 Rob Papen no multiout version

[carlosigls]

I am having trouble with the Punch2 plugin. This plugin comes with two versions: one multi-output and the other without multiple outputs. Mixcraft only recognizes the version without multiple outputs. Let's see if we can solve this.

[Acoustica Greg]

Hi,

Are you using Mixcraft 9.0 build 460? When you say it doesn't recognize the multi-out version, what do you mean? That's it's just not loading in Mixcraft? Are you using 64-bit Mixcraft?

Greg

[Acoustica Greg]

Or maybe they are there and you just need to display them? Make sure that you've got the multi-outs selected:

[carlosigls]

Yes, It is not seen when I search the plugin, only the version without multi-output is seen. In Reaper if you see both versions of the plugin.

[Acoustica Greg]

Hi,

When you installed the plugin, which VST folder did its VST files go into? Did you just allow it to install, or did you move files around after you installed?

Send us your Mixcraft-log.txt file.

To find the mixcraft-log file, highlight the following line and press Ctrl+C to copy it:

Code: Select all

%appdata%\Acoustica\Mixcraft\

Press the Windows Key+R to pop up the Run box in Windows. Click in the Run box and press Ctrl+V to paste in the line from above. Finally, click OK to go to the location of the mixcraft-log.txt file. Submit an Acoustica Support Request and attach the log file along with a brief description of the problem.

Greg

[carlosigls]

I did not move anything, it is the same directory for Reaper and Mixcraft. The two versions are seen in Reaper and Mixcraft only one.

[Acoustica Greg]

I did not move anything, it is the same directory for Reaper and Mixcraft. The two versions are seen in Reaper and Mixcraft only one.

Hi,

Send in your log file.

Greg

[Acoustica Greg]

Hi again,

It looks like the plugin maker used the same VST ID for both versions of the plugin, which makes Mixcraft assume the multi-out version is a duplicate.

You could rename Punch2.dll to Punch2.bak and that would allow the multi-out version to load the next time you start Mixcraft.

Yes, I know you don't have do that in Reaper. Mixcraft is just trying to keep us from having a bunch of duplicate plugins loading all the time. Plug-in makers are supposed to use a unique VST ID for every plugin, so this is bad programming on the plugin maker's part.

Greg

[carlosigls]

Well, from Rob Papen's support they don't say that, they tell me it's your problem. I put what they told me.

Hello,

This a problem we can't solve, or it is more a problem/bug with Mixcraft.

Both versions of Punch-2 have a different instrument name, but need to have the same ID.

Otherwise, you could not load Punch-2 presets into Punch-2Multi.
This would cause bigger problems!

With Cubase, Ableton, Logic this problem doesn't appear. Mixcraft should look also to the name of the product, not only the VST ID.
The programs are Punch2.dll and Punch2Multi.dll

Kind regards,
Support Team Rob Papen

[Acoustica Greg]

Hi,

Yeah, we'll look into this. One possibility would be to ID the plugin by using a combination of its VST ID and its name. This will be something to consider for a future update of Mixcraft (it's not happening today).

That said, in the case of these plugins, you probably just want to use the multi-out one anyway, don't you? Or do you need to use both?

Greg

[carlosigls]

I have no other choice, I will have to use one or the other.

[Acoustica Greg]

Hi,

Yeah, but the multi-out version has... multi-outs.

Most plugin manufacturers use different VST IDs for their plugins. This is a rare case.

That said, your feedback has been logged and we'll see what turns up in future Mixcraft updates.

Greg

[carlosigls]

Thanks for your support.

[Mickytee55]

Hello carlosigls

I had exactly the same problem with Punch 2
However “and not an ultimate fix” I took Greg’s advice and re-named Punch2.dll to Punch2.bak
That “as explained” allows Punch 2 Multi to load instead of Punch 2
Alright, it’s either one or the other, but if Multi is what you need to work with, then it’s solved your problem!

[carlosigls]

It's solved. But I hope that in future updates they will solve this problem.