Printable Version of Topic

Click here to view this topic in its original format

Plugivery Forums _ Plug & Mix _ Pm-basspeg Crashes Reaper

Posted by: obeatz Jan 14 2017, 07:53 AM

Hi there,
while scanning for new plugins Reaper crashes when recognising PM-Basspeg. The other four new additions seem to work so far. I double checked in two different machines / WIN10 64bit
Cheers

Posted by: Perry Diels Jan 14 2017, 06:13 PM

Apparently not only Reaper... same with Cubase 9/Cubase 8.x/Vegas/Ableton Live 9/WaveLab/... (Windows 64-bit)

Cubase 9 does not crash during its scan for new plug-ins, but it adds "PM-Basspeg" wisely to its integrated 'blacklist' and hence the plug-in cannot be used (BTW great new feature in C9) When trying to manually 'force' the plug-in out of the blacklist, Cubase 9 crashes.

There is obviously something wrong with "PM-Basspeg"

I also confirm that the other new plug-ins are working OK.

Looking forward for an update to Basspeg!

Best regards.

Posted by: johnk Jan 14 2017, 11:06 PM

Was trying to send a bug report but the normal channel failed. Looks like others are ahead of me anyway.

Confirming the failure of Basspeg in Reaper ver 5.x

This said, really welcome the chorus and pitch controls, and above all, the entry of a noise gate in the suite. Makes the environment nearly complete.

John K

Posted by: damoflplug Jan 15 2017, 03:19 AM

also crashes in Studio One 3.3.3 and in FL Studio 12.4.1

Posted by: SantoClemenzi Jan 15 2017, 03:35 PM

Same problem here. Win 10 Home 64 bit, after installation of new version with new plugins Reaper crashed during the VSTs check. Cleared and re-scanned all plugins didn't solve the problem, it still crashes whenever the Basspeg is reached during the scan. Hope for a quick fix, it was actually the most interesting for me tongue.gif

Thanks anyway for these new additions, i LOVE Plug & Mix stuff, hope to receive a fix for the basspeg soon!

Posted by: johnk Jan 15 2017, 05:50 PM

Santo,

Can't fix the plug, but uninstall the suite, or just the dll for Basspeg. Probably fresh install after uninstall is best.


Next, find the reaper-vstplugins.ini file. Look in the Users folder for your user name. Then go to the Appdata\roaming folder, then the Reaper folder. Open the ini file with notepad. Basspeg will be one of the last line entries. Delete the line after deleting the plugin and then save the file.

Restart Reaper and everything should work. Then if you want, reinstall the P&M suite with Basspeg unchecked. Note that failed plugs in the ini file have a name of the dll = then some numbers. The line does not have a comma followed by the plugin name. Successfully registered plugs have the dll name, = , bunch of numbers, a comma, and the plugin name. Only strange thing is that this method of failing plugs should have protected Reaper from crashing on restart.

Hope this helps,

John

Posted by: aoVI Jan 16 2017, 05:32 AM

Basspeg crashing Studio One 3.3.3 (win7/64) on initial scan here as well. Other plugs working fine.

Posted by: SantoClemenzi Jan 16 2017, 08:50 AM

QUOTE (johnk @ Jan 15 2017, 05:50 PM) *
Restart Reaper and everything should work. Then if you want, reinstall the P&M suite with Basspeg unchecked. Note that failed plugs in the ini file have a name of the dll = then some numbers. The line does not have a comma followed by the plugin name. Successfully registered plugs have the dll name, = , bunch of numbers, a comma, and the plugin name. Only strange thing is that this method of failing plugs should have protected Reaper from crashing on restart.


Hi John! Thank you very much for your explanation, actually Reaper crashed only the first time during VST scanning (I tried twice because I also tried to clear the cache and re-scan), but after the first time basspeg was simply skipped and ignored so everything worked fine. Hope to have a fix on the plugin because I'd like to try it smile.gif

Thanks again!

Posted by: ruckus Jan 16 2017, 12:17 PM

Also crashing in FL Studio 12 (all other VIP plugins load ok).
-------------------------
FL Studio Plugin Manager:
Name: PM-Basspeg, Status: error, Format: VST, Bits: ?, Effect/Synth: ?, Vendor: Plug and Mix, Filename: PM-Basspeg.dll
-------------------------
Plugin will crash FL Studio if you try and load it into an FX slot.

Windows 10 Home, 64bit, FL Studio Producer Edition v12.4.1 [build 4] - Signature Bundle - 64Bit

Posted by: johnk Jan 17 2017, 02:37 AM

Santo, you are welcome.

Thought that it might be a clear cache and rescan issue. Once failed, the plug should be blacklisted and not cause a subsequent crash.

This gets off topic a bit, but wanted to mention about the vst ini file for Reaper users. Knowing how to use this remote file can save a lot of grief.

Verified that all the P&M plugs are safe except Basspeg. Then the issue about the fragile state of Pitch Me, which registers okay but can crash the program after the fact.

The Reaper vst ini file contains the log of all successful and all failed vst/vsti load attempts. Failed plugs are not given a name and remain blacklisted. If you delete just the line for the failed plug, you can restart Reaper and only retry the failed plug, and not have to do a complete breakdown and rescan everything.

Almost like a registry cleaning, it is a good idea to go thru this file every now and then. Delete off all entries that don't have a name after the number sequence. Save the file and rescan, for a couple reasons.

Blacklisted plugins may have been dumped for some momentary glitch never to see the digital light of day again. Deleting the entry will give a new scan on restart and the plug might work. (Basspeg did not)

Sometimes a vst will register but with a name not remotely related to the dll file name. If you have a bunch of plugs, hard to tell if it was blacklisted or named something you would never look for. Searching the file for the dll name will show if the plug is blacklisted or if abc.dll is really registered as xyz. Note you can also change the name of the plug in this file and it will show up the way you want it to.

@ruckus, hope the devs get a fix in the works. Incredible suite of tools

John

Posted by: SantoClemenzi Jan 17 2017, 08:39 AM

QUOTE (johnk @ Jan 17 2017, 02:37 AM) *
The Reaper vst ini file contains the log of all successful and all failed vst/vsti load attempts. Failed plugs are not given a name and remain blacklisted. If you delete just the line for the failed plug, you can restart Reaper and only retry the failed plug, and not have to do a complete breakdown and rescan everything.


Great explanation John! Thank you very much! Can't wait for a fix to this new version, apparently there are some issue pending for this latest release, I'm sure they'll be all addressed soon by the plug&mix team!

Posted by: mfkne Jan 17 2017, 03:53 PM

Crashes besides Studio One also Live 9.7. and Mu.Lab 7, freezes also Tracktion 7 sad.gif (Win 10, 64 Bit)

Posted by: keithadv Jan 17 2017, 09:23 PM

I can add Sonar Platinum (64-bit) to the list. It crashes the scanner first time around and then is added to the ignore list.

Posted by: DH-DC Jan 17 2017, 09:40 PM

Same for me ... Live 9.7.1 Suite 32-Bit Pm-basspeg crashes on scan.

I also got a crash, trying to go through presets on another Plugin. I think it was some sort of runtime error. I can't be 100% sure as my computer is in use and ableton is out or order for now.

Posted by: Perry Diels Jan 18 2017, 04:55 PM

If we look at this thread I believe we may simply summarize the issue as "not working with any host" whether it be 64- or 32-bit.
This makes me wonder; has the product been tested before its release, and if so with which host? Maybe something just went wrong during the final compilation, who knows. But anyhow where are the P&M moderators? No response from them on this ubiquitous problem?

We all look forward for a solution, or at least some feedback would be nice dry.gif

Posted by: Ali Zogheib Jan 18 2017, 06:13 PM

Hi everyone,

Ali here, marketing for Plugivery.

Thanks for contacting our support team recently and raising issue with regards to the new 5 P&M plug-ins and Chainer. Our developers have been made aware and have fixed the following issues. New builds are now available on our download site http://download.plugivery.com/pvdl/?do=browse&dir=release&bid=72

For AAX, please delete the InstalledAAXPlugIns file in the following paths to force Pro Tools to rescan at launch...

Mac: Users/<your name>/Library/Preferences/Avid/Pro Tools

PC: C:\Users\UserName\AppData\Roaming\Avid\Pro Tools

--------------------

Fixed:

• [Mac] No new plug-ins available in Chainer.

• [Windows] Basspeg causes crashes in DAWs.

• Clarisonix and Distorted not validated as 64-bit AAX plug-ins.


Known Issues:

• [RTAS] Avid have depreciated support for the RTAS format however we will look to make the bundle available as many of you have requested if we can.


Note: Our support for this format may discontinue also in the near future as we usher those to update to Pro Tools 10.3.7 or above to stay compatible with moving and growing technologies as we expand.

Hope this helps, let us know if you're having any other issues!

Posted by: johnk Jan 18 2017, 06:21 PM

Thank you Ali.

There is still the issue with Pitch Me. This plug registered fine in Reaper, but the state is very fragile. Moving the knobs too quickly creates a loud sustained crash. It does work however in Reaper with care.

It was reported earlier on the forum that Pitch Me was crashing other DAWs as well.

Best,
John

Posted by: Ali Zogheib Jan 18 2017, 06:23 PM

Thanks for pointing that out John, I will make sure to make our development team aware of the issue.

Cheers,
Ali

Posted by: Perry Diels Jan 18 2017, 06:42 PM

Thanks for the update Ali!

But unfortunately, the problems is still there with Basspeg, it is blacklisted in Cubase 9 and it makes the other DAW's crash.
To my surprise, because this specific issue is listed under the bug fixes wink.gif

Still looking for a new update


Posted by: johnk Jan 18 2017, 07:56 PM

Confirming crash in Reaper still

Posted by: DH-DC Jan 19 2017, 12:03 AM

Tried the latest release version today and got the same result. Crash!!!

The Download Link seems to still show the same version number which is confusing.

Posted by: johnk Jan 19 2017, 02:55 AM

Don't have a Mac, but got a note that the Mac installer works with all plugs, no problems.

Windows problems only. Focus for the devs needs to be on fixing Basspeg and Pitch Me. Only wish I could code and help out.

John

Posted by: gokidsmusic Jan 19 2017, 02:48 PM

Basspeg still crashes Sonar Platinum (64-bit) scanner

Posted by: Teksonik Jan 20 2017, 05:22 AM

I can confirm that even the version of Basspeg contained in the installer dated January 16th is crashing Reaper on scan and FL Studio on load here (Win 10 64 Bit). The issue has also been reported in the thread at KVR where Ali has replied.

The download package still shows 3.3.0 (0033000).

Posted by: cazzari Jan 20 2017, 08:39 AM

Basspeg still fails Studio One 3.3 scan

Posted by: cme Jan 21 2017, 09:58 PM

QUOTE (cazzari @ Jan 20 2017, 01:39 AM) *
Basspeg still fails Studio One 3.3 scan


I am having trouble with it in Mixbus 32C also. On a Windows 10 machine. Just read where they fixed it on the 18th. I had downloaded the bundle before then. But why hasn't the version number changed? It makes it quite difficult to know what version you really have. Seems as it's been 3.3.0 for long time now.

Posted by: cme Jan 21 2017, 10:41 PM

QUOTE (cme @ Jan 21 2017, 02:58 PM) *
I am having trouble with it in Mixbus 32C also. On a Windows 10 machine. Just read where they fixed it on the 18th. I had downloaded the bundle before then. But why hasn't the version number changed? It makes it quite difficult to know what version you really have. Seems as it's been 3.3.0 for long time now.


So the download just finished for the 64-bit VST and it still doesn't work for me. In Mixbus, Reaper, or Studio One. Any suggestions?

Posted by: johnk Jan 22 2017, 12:36 AM

cme,

No suggestions since us lay people can't fix. It is nothing you are doing wrong, and probably nothing you can do to get the offending plugs to work. Reporting the problem like you have done is the critical duty of the end user to the collective, user and developer.

I have a lot of faith in this set of tools and also that the devs are listening, and that a fix is soon to come.

Wanted to add again the fragile performance of Pitch Me, which does not all the time crash outright, and is recognized by Reaper as a legitimate vst.

Another older thread somewhere on this forum reported a different plug as causing a loud rapid popping that red-lined everything and had to be shut down to restart. This is the exact symptom I'm experiencing with Pitch Me if the knobs are moved too fast. Probably harder to troubleshoot since the failure is intermittent. Pitch Me needs some love as well as Basspeg

John

Posted by: Teksonik Jan 23 2017, 12:29 AM

Sorry, Basspeg still crashes Reaper on scan and FL Studio on load.

P&M installer version 3.3.1 (033100) dated 22 January.

I'm not too sure what's going on. I'm using Win 10 64 bit, 64 bit version of the P&M plugins, 64 Bit Reaper and FL.

None of that is an exotic setup nor are Reaper or FL obscure and hard to get for testing.

Posted by: Perry Diels Jan 23 2017, 04:17 PM

What's going is simply a mayor bug in Basspeg. It crashes on all systems so far.
I believe they made a correction to the installer file numbering system in order to avoid further confusion... but Basspeg is still not repaired.
Maybe we need to wait for 3.3.2 now!

Posted by: Ali Zogheib Jan 23 2017, 06:10 PM

Hi again everyone, Ali from Plugivery here.

We just wanted to update you that all remaining issues re P&M and the new 5 plug-ins should now be resolved. The developers have fixed validation, crashes with Basspeg on Windows systems…
Also, the version number for the VIP Bundle and the Chainer have been updated.

Important Note: users will need to rescan plug-ins in their DAW and clear any blacklist files on their systems. This means for Logic, deleting the AU Cache file in…

/Users/<your name>/Library/Caches/AudioUnitCache

and Pro Tools the InstalledAAXPlugIns file in these paths…

*Mac*: Users/<your name>/Library/Preferences/Avid/Pro Tools

*PC*: C:\Users\UserName\AppData\Roaming\Avid\Pro Tools

Hope this helps, please let us know if you are still having some issues.

Thanks!

Posted by: Perry Diels Jan 23 2017, 06:25 PM

Hi Ali,

In what version is it supposedly resolved? As of writing this message, the latest version on the download page is 3.3.1 which still has the bug(s) as confirmed in this thread. Will you soon post a Windows 3.3.2 version?

Note: With P&M 3.3.1 - JAN 32rd. Basspeg is still not working!

Posted by: cme Jan 23 2017, 11:08 PM

QUOTE (Perry Diels @ Jan 23 2017, 11:25 AM) *
Hi Ali,

In what version is it supposedly resolved? As of writing this message, the latest version on the download page is 3.3.1 which still has the bug(s) as confirmed in this thread. Will you soon post a Windows 3.3.2 version?

Note: With P&M 3.3.1 - JAN 32rd. Basspeg is still not working!


I probably won't have time to install until tomorrow, but I'll give it a go and see what happens. Fingers crossed, but not holding my breathe. haha

Posted by: johnk Jan 24 2017, 12:23 AM

Confirmed that Basspeg still crashing Reaper with 3.3.1 version.

Posted by: ruckus Jan 24 2017, 03:43 AM

Error on scan, fixing causes crash (setting attributes to effect).
File: PlugAndMix VIPbundle VST 64b Pc v3.3.1(033100)

- - - - - - -
Windows 10 Home, 64bit, FL Studio Producer Edition v12.4.1 [build 4] - Signature Bundle - 64Bit


Posted by: cme Jan 24 2017, 01:43 PM

Still not showing up in Mixbus and crashing Studio One here. It is ironic that the one I want to try the most is the one that refuses to cooperate. Hopefully it's worth the wait. smile.gif

Posted by: SantoClemenzi Jan 24 2017, 02:05 PM

QUOTE (cme @ Jan 24 2017, 01:43 PM) *
Still not showing up in Mixbus and crashing Studio One here. It is ironic that the one I want to try the most is the one that refuses to cooperate. Hopefully it's worth the wait. smile.gif


Can't wait to check out Basspeg! smile.gif

Posted by: Perry Diels Jan 24 2017, 02:08 PM

They have confirmed via e-mail that the engineers are looking into it. I guess we need to wait for 3.3.2 now.
Hopefully this week.

Posted by: Ashley Smith Jan 27 2017, 04:15 PM

We have a fix for Basspeg and have been sending out test builds to those that have reported through our support system. We had to recompile with older toolset as an upate threw us off for this one plug-in.

Through this year we'll be moving to a new framework to allow faster fixes, optimized production, new product releases and more.

Stay tuned for version 3.3.2... it's coming asap! Promise!

Posted by: cme Jan 28 2017, 04:35 PM

How do we report through the support system? I must have missed that. First time I've had any problems though. Which is a great thing. Good work guys. Keep it up. smile.gif

Posted by: Ashley Smith Feb 1 2017, 05:39 PM

P&M VIP Bundle 3.3.2 and Chainer 1.2.2 have been released. Please see the news item http://www.dontcrack.com/news/2017/02/plug-and-mix-3-3-2-and-chainer-1-2-2-updates-available/

cool.gif

Posted by: cme Feb 10 2017, 06:19 PM

Thanks for the update. Fixed it for me. And more importantly sounds fantastic. biggrin.gif

Powered by Invision Power Board (http://www.invisionboard.com)
© Invision Power Services (http://www.invisionpower.com)