Plug'n Script V3 [Now 3.1] released - with VST, VST3, AU Export and new GUI

[Blue Cat Audio]

Dear fellow developers,

We are pleased to announce the release of Blue Cat's Plug'n Script 3.0, a new version of our scripting plug-in that can be programmed to create custom audio and MIDI effects or virtual instruments inside most Digital Audio Workstations (DAW).

Initially released in 2014 to add scripting capabilities to your favorite DAW, Plug'n Script V3 has now evolved into an integrated audio plug-ins development environment, with a brand new graphical user interface with streamlined workflow and VST plug-in export capabilities. It has never been so easy to create VST plug-ins!



The plug-in is available alone or as part of Blue Cat's Crafters Pack, a bundle designed for creative people who care about tools that adapt to their own workflow: it includes Blue Cat Audio's most powerful software to quickly build a custom audio and MIDI toolbox.

Upgrade to the new version is free for customers who purchased the plug-in since March 2016, and others can upgrade for a small fee (offers received by email). A special introduction price (20% off the plug-in) is available to new customers until november 5th, while registered Blue Cat Audio customers are granted an extra 10% discount during the same period. Demo versions are available for download on http://www.bluecataudio.com, in most popular plug-in formats for Mac and PC.

New in Blue Cat's Plug'n Script 3.0:
- Brand new GUI design, with improved usability and touchscreen support, fully zoomable.
- Scripts can now be exported as independent VST plug-ins.
- Customize the user interface in the plug-in (no code required), or write your own layout for each script.
- Separate player and editor modes for optimal workflow.
- Parameters display format can now be set by scripts.
- Retina displays support on Mac (high resolution for text and vector graphics).
- Changed demo limitations: up to 5 instances allowed, bypass time changed to half a second, and bypass parameter is not affected anymore.
- New installer on Mac.
- New version of the Angelscript engine (2.31.1).
- Fully compatible with previous versions of the plug-in. Warning: changed the identifier of the VST3 version on Mac. See this post for more details: https://www.bluecataudio.com/Blog/tip-o ... es-on-mac/
- Fixed minor issues on Mac OS High Sierra (https://www.bluecataudio.com/Blog/commu ... atibility/).
- Fixed native file recorder script issues (file names were not properly generated for rotation).
- Fixed MIDI channel issue with VST3: MIDI channel for note events was offset by one in the VST3 plug-in version.
- Removed specific mono and stereo versions for the VST plug-in - please unsintall previous version first if you do not need them (new installer will not remove them).
- Dropped support for Windows XP and Mac OS X 10.6 and earlier.

System requirements:
- Intel Mac running Mac OS 10.7 or newer.
- PC running Windows Vista or newer.

Pricing:
Blue Cat's Plug'n Script: 79 EUR or $79 (instead of 99 EUR or $99), until November 5th.

[Youlean]

This plugin is interesting, so tried it out but my antivirus is detecting something...

[Blue Cat Audio]

This looks like a false positive - unless the binary was infected on your machine. As you can see below, virustotal reports 3 false positives out of 64 anti virus engines:
https://www.virustotal.com/#/file/6c981 ... 805de86c7/

[Youlean]

This looks like a false positive - unless the binary was infected on your machine. As you can see below, virustotal reports 3 false positives out of 64 anti virus engines:
https://www.virustotal.com/#/file/6c981 ... 805de86c7/

False positive or not this should be fixed if only because people with Avast can't use this plugin.

[jsp1979]

This looks like a false positive - unless the binary was infected on your machine. As you can see below, virustotal reports 3 false positives out of 64 anti virus engines:
https://www.virustotal.com/#/file/6c981 ... 805de86c7/

False positive or not this should be fixed if only because people with Avast can't use this plugin.

There's no fix. The issue is with Avast. They should be contacted to white list it. There the ones saying it is dangerous when it isn't.

[whyterabbyt]

This looks like a false positive - unless the binary was infected on your machine. As you can see below, virustotal reports 3 false positives out of 64 anti virus engines:
https://www.virustotal.com/#/file/6c981 ... 805de86c7/

False positive or not this should be fixed if only because people with Avast can't use this plugin.

Yes. Please report this to Avast so they can fix their incorrect diagnosis.

[Youlean]

Not sure if reporting this to Avast will be permanent fix since when BCA release and update it might be listed as a virus again. It might be better to check what going on in code and prevent it there...

[Miles1981]

Probably the fact that it's compiling on the fly, which is flagged by the antivirus?

[Youlean]

Probably the fact that it's compiling on the fly, which is flagged by the antivirus?

No, precompiled binaries are flagged.

[whyterabbyt]

Not sure if reporting this to Avast will be permanent fix since when BCA release and update it might be listed as a virus again. It might be better to check what going on in code and prevent it there...

You're assuming that 'what's going on' isn't intrinsic to the software's functionality. Given what this does, though, it almost certainly is, as Miles1981 indicated. Something like in-memory compilation, self-modifying code etc.

Its actually better for anti-virus companies to modify their detection algorithms to suit the requirements of real-world software than to expect the developers of said software to have to 'work round' the erroneous flagging of perfectly legitimate software functionality. All those other antivirus systems don't have a problem, so its up to Avast to get up to speed; that's their job, detecting viruses.

[Youlean]

You're assuming that 'what's going on' isn't intrinsic to the software's functionality. Given what this does, though, it almost certainly is, as Miles1981 indicated. Something like in-memory compilation, self-modifying code etc.

I am not saying that BCA is distributing viruses and I am trying to help, but "almost certainly" is not good enough for anyone that is using PC for other that browsing through the internet. As I said above this is precompiled binary and Avast detected virus before I run anything. I was just reading manual.

Its actually better for anti-virus companies to modify their detection algorithms to suit the requirements of real-world software than to expect the developers of said software to have to 'work round' the erroneous flagging of perfectly legitimate software functionality.

Are you developer of this plugin? If not, how can you be 100% sure that there isn't something malicious there? Also detecting viruses is cross connected thing. Maybe binary have similar bytes to some legitime viruses that only Avast detect so if they remove detection for that you might get viruses.. . Just saying.

[sinkmusic]

Very nice update !
Exporting to VST is a great feature indeed !

[Blue Cat Audio]

About this virus thing: it is a common issue with any binary and it is not related to the functionality of our software: we do not do self-modifying code etc. Here they may just have detected a portion of binary that more or less corresponds to the signature of a virus/malware.

There is not much we can do except ask for false positive check. If they acknowledge the false positive, there is no risk that it won't find this particular malware in other binaries, don't worry.

In this particular case, it is actually just one of the included binary scripts (multi gain script compiled for 32-bit windows) that triggers the warning, so I guess you can let Avast remove it - it won't break the plug-in. You will just not be able to load this particular script. One thing we can try to do is sign these binary scripts like we do sign our plug-ins), sometimes it helps...

[msorrels]

One thing we can try to do is sign these binary scripts like we do sign our plug-ins), sometimes it helps...

Or sometimes it hurts. A few years ago Norton claimed the signed version of our app was infected but the unsigned version of the exact same binary was clean. Not even they could explain that one.

[whyterabbyt]

Are you developer of this plugin? If not, how can you be 100% sure that there isn't something malicious there?

Are you claiming that there is? Despite the fact that the vast majority of virus checkers arent flagging anything?

Maybe binary have similar bytes to some legitime viruses that only Avast detect so if they remove detection for that you might get viruses.. . Just saying.

Simple byte sequence comparisons? That would be a rather naive approach for a modern virus checker, especially if it cant handle lists of exceptions as you seem to be implying; if that's all Avast can manage, surely its best to discount their findings entirely.

Its rather strange; false positives are commonplace with virus checkers, Avast in particular have falsely labelled entire swathes of the web unsafe, that the false-positive identification of Win32:Evo-gen by Avast has a long history, Avast know that this is common enough they provide a form for reporting false positives, and yet you seem curiously determined for this not to be something Avast have to deal with.