Menu
Home
Forums
New posts
Search forums
What's new
Featured content
New posts
New media
New media comments
New resources
Latest activity
Media
New media
New comments
Search media
Resources
Latest reviews
Search resources
Nyuuz
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Menu
Log in
Register
Install the app
Install
Home
Forums
Labrish
Nalij
Jinaral kantent
Scorch 2 compatibility has a few hard limits
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
[QUOTE="Bombastus, post: 91631, member: 2178"] Scorch 2 requires Windows 10 or newer on an x86-64 Intel or AMD processor, while Windows on ARM devices are explicitly unsupported. The processor detail is easy to miss because the operating-system line by itself sounds much broader. A recent Windows laptop can still be the wrong machine. Mac support is wider. Sauceware lists macOS 10.11 or newer and supports both Intel and Apple Silicon processors, so an M-series Mac clears the processor requirement without relying on the older Intel-only position many plugins once had. The format choice is narrower than the machine support. Scorch 2 ships as VST3 and AU, which covers most current production setups but leaves some older sessions and certain hosts outside the clean path. [HEADING=2]VST3 and AU cover most DAWs but not every host[/HEADING] Sauceware names FL Studio, Ableton Live, Logic Pro, Cubase, Studio One, Bitwig, Reaper, and Reason as compatible DAWs. On Windows, VST3 is the relevant format. On macOS, hosts can use VST3 or AU where the DAW supports them, while Logic Pro users will normally encounter the AU build. The important catch is Pro Tools. Scorch 2 has no native AAX version, so it will not appear in Pro Tools as a normal AAX instrument after installation. Sauceware suggests using a third-party wrapper such as Blue Cat PatchWork if you want to host the VST or AU version inside Pro Tools. A wrapper is a workaround, not native support. It adds another piece of software between the session and Scorch 2, and collaborators need to account for the same setup if they expect the session to reopen cleanly elsewhere. Sauceware even treats an unsuitable AAX-wrapper situation as a legitimate compatibility problem under its refund guidance. Older Scorch users should check archived projects before removing anything. The first Scorch was sold in VST, VST3, and AU formats, including older 32-bit and 64-bit builds, while [B][URL='https://goldmidi.com/community/threads/sauceware-audio-rebuilt-scorch-2-for-rap-producers.77036/']Scorch 2 compatibility requirements[/URL][/B] are centered on VST3 and AU. An old session that expects the earlier VST build does not automatically swap itself to the new plugin. [HEADING=2]Windows on ARM is the easy requirement to misread[/HEADING] Windows 10 or newer sounds simple until processor architecture enters the picture. Scorch 2 specifically requires an Intel or AMD x86-64 processor on Windows, so machines built around Qualcomm Snapdragon and other Windows on ARM hardware fall outside the supported specification even when they run a current Windows release. Windows can translate some x86 applications on ARM machines, but vendor support still matters with audio plugins because the host, plugin, authorization layer, and low-latency audio path all have to cooperate. A plugin launching through translation is not the same thing as its developer promising the configuration will work. The same architectural problem has been studied more broadly on Apple hardware. [B][URL='https://doi.org/10.1145/3652032.3657565']Research on dynamic binary translation[/URL][/B] found that translated legacy x86 execution can carry performance costs compared with direct native execution. The paper does not test Scorch 2, but it helps explain why an explicit processor-support line matters more than assuming an operating system can translate everything safely. Apple Silicon users have a cleaner answer because SauceWare explicitly lists the platform as supported. The specification does not force you to decode model numbers or guess whether an M1, M2, M3, M4, or later Apple Silicon machine belongs to the supported processor family. [HEADING=2]Installation needs more than a compatible processor[/HEADING] The current specification also leaves out two numbers people often copy from the original Scorch page. Sauceware does not state a RAM minimum or a processor clock-speed floor for Scorch 2, while the older product material listed both. Repeating the old 8 GB memory figure or 2.9 GHz processor guidance as a Scorch 2 requirement would therefore mix two generations of the plugin. Scorch 2 asks for 10 GB of free disk space and a display resolution of at least 1280 by 720. Neither requirement is demanding for a current production computer, but storage can become relevant on laptops where sample libraries already occupy most of the internal drive. Internet access is also required for installation and activation. The published requirement names those two stages rather than describing Scorch 2 as an always-online instrument, so the practical constraint is strongest on studio machines kept offline or firewalled from the public internet. Sauceware's support policy gives one useful escape hatch. If an unsupported OS or DAW setup, or the lack of AAX plus an unsuitable wrapper, means the plugin genuinely cannot run, the company says to contact support and points to its 14-day money-back guarantee. This matters most for Pro Tools and unusual Windows hardware, where the plugin-format label alone can make compatibility look simpler than it is. [/QUOTE]
Insert quotes…
Name
Post reply
Home
Forums
Labrish
Nalij
Jinaral kantent
Scorch 2 compatibility has a few hard limits
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.
Accept
Learn more…
Top