Bitwig

flechtwerk · Post by **flechtwerk** » Tue Jan 21, 2020 11:28 pm

I'm demoing the demo version of Papen Punch 2 and I'm truly loving it, exactly the kind of drum plugin I had been looking for a while.

Unfortunately, after some minutes of use, it always starts to completely freeze the Bitwig gui for long amounts of time (the music continues playing happily though). Bitwig does unfreeze from time to time but it stays completely unusable as long as I have an instance of Push 2 running.

I was wondering if everybody else has that problem or if there is anyone succesfully using Punch 2 in Bitwig?

The Bitwig support gave me the following answer:
"this is a known problem with this plugin because compared to other VSTs it communicates over 32.000 user-automatable parameters to the host.
Usually, VSTs with that many parameters let the user decide which ones they want to actually use and should get send to the host, so that the host does not always have to scan ten thousands parameters that are not needed."

The Rob Papen support first said it was a known problem that would be taken care of soon and that there shall be an update "in the second week of January", but now they say there won't be such an update and that they didn't have any such reports although the plugin is selling in considerable numbers. So I'm a bit confused...

For some reason at least the AU version is crashing Ableton 10 and Reaper 6 also, so I started to wonder whether the problem lies with my system somehow (all the other plugins work fine though and everything I use is up to date & legit).

Meffy · Post by **Meffy** » Tue Jan 21, 2020 11:29 pm

I'll give it a shot. What kind of system are you running it on? I have Bitwig on a Mac and two Win10 machines.

[edit] Oops, my mistake. I don't have Punch 2, just the original.

flechtwerk · Post by **flechtwerk** » Tue Jan 21, 2020 11:33 pm

Thanks! I'm working with MacOs 10.14.6. on a MacBook Pro 2,9 GHz i7, 16 GB RAM.

Meffy · Post by **Meffy** » Tue Jan 21, 2020 11:34 pm

I spoke too soon, haven't got Punch 2 yet. Sorry about that.

I'll download and try it after supper.

flechtwerk · Post by **flechtwerk** » Tue Jan 21, 2020 11:38 pm

Ah thanks, that would be nice!

But the original one is working well? Maybe I shall get that one for now if there's no workaround... Though it would be a pity, I really like Punch 2 a lot.

Meffy · Post by **Meffy** » Tue Jan 21, 2020 11:50 pm

Don't think I've tried it on my old MacBook Pro (2013, I think). I know it's got Logic Pro on it, but not Bitwig. They have a demo too, so I'll use that.

Right now it's charging, battery was totally drained.

Meffy · Post by **Meffy** » Wed Jan 22, 2020 12:29 am

Working now, demo Punch 2 on demo Bitwig. Mid-2012 MBP running High Sierra, i5 @ 2.5 GHz with a measly 4 Gb RAM.

After 15 minutes I still get audio and the UI is responsive. Will let it cook and try it now and then.

flechtwerk · Post by **flechtwerk** » Wed Jan 22, 2020 12:53 am

Thanks! I'm also fooling around with it and the problem seems only to arise when I select the track with Punch 2 in it, so Bitwig's explanation about too many automatable parameters to be checked upon might be right... Funny thing is that there is never a problem with the audio, just the Bitwig gui.

Meffy · Post by **Meffy** » Wed Jan 22, 2020 1:27 am

Weird, still running smoothly here. Hope you're able to track down the source of the problem and get past or around it. Sorry I couldn't break it too.

flechtwerk · Post by **flechtwerk** » Wed Jan 22, 2020 9:17 am

It's good to know it's at least working in principle. Though it makes no sense your older MacBook can easily handle the 32.00 automatable parameters and mine can't. Maybe I'll try a re-install of Bitwig. And I'll also stay in touch with the Bitwig support.

Thanks a lot for running the test!

bite_me · Post by **bite_me** » Sun Jan 26, 2020 10:39 am

Works flawless here with the full version in Win7.
Demo produced lots of crashes.

flechtwerk · Post by **flechtwerk** » Sun Jan 26, 2020 6:49 pm

Thanks for letting me know! It's strange the Bitwig support team gave me the answer about Punch 2 having too many automatable parameters since it's working fine on other systems.

Well, I'll keep trying to fix it. I'm also tempted in testing the full version though that means I'd have to buy it...

flechtwerk · Post by **flechtwerk** » Sun Jan 26, 2020 7:36 pm

I solved it, so in case anyone else is running into a similar problem: I had to remove the drivenbymoss Push 2 controller script (it wasn't enough that Push was not connected). Now it's working like a charm!

So obviously Bitwig can handle the plentitude of automatable parameters, but the controller script can't. I'll post it in the relevant forum.

bite_me · Post by **bite_me** » Tue Jan 28, 2020 7:02 am

Crashes still occur while exchanging samples in sample mode.

flechtwerk · Post by **flechtwerk** » Tue Jan 28, 2020 6:02 pm

Ah! I haven't tried that yet, but I will. Otherwise it's running fine, Bitwig might still freeze for some seconds when i'm changing presets (guess it's too many parameter changes at the same time), but it's not too disturbing.

Bitwig

KVR Audio

Is anyone successfully using Papen Punch 2 with Bitwig?