# Sound Forge Pro Guide > Independent Sound Forge 2026 review with current price, official 15-day trial, Pro 18 upgrade advice, Windows tutorials and troubleshooting. Public Ghost content for AI and LLM tooling. This file includes a bounded export of public pages first, then recent public posts. Append `.md` to any post or page URL to get the content in Markdown (for example, `/example-post.md`). ## Pages ### About SoundForgePro.com URL: https://soundforgepro.com/about/ Last updated: 2026-09-16T07:25:03.000Z **SoundForgePro.com is an independent editorial guide to Sound Forge and related audio-editing workflows.** The site is intended to help readers understand documented features, compare options, follow procedures and identify facts that may have changed between the MAGIX and Boris FX eras. **Correction, September 16, 2026:** an earlier version of this page said every article came from actual use and described Erick Finn as a Germany-based music producer with a personal recording, mixing, mastering and post-production history. We do not have evidence that substantiates those statements. They have been removed and should not be treated as proof of credentials, location, a test setup or hands-on product use. ## What the site publishes Coverage includes Sound Forge features, installation and purchasing information, editing and restoration workflows, troubleshooting, audio concepts and browser-based audio tools. A page may explain vendor documentation, work through a calculation or report a narrowly recorded browser check. Those forms of evidence are different from operating Sound Forge or listening to processed audio. The site's [review methodology](https://soundforgepro.com/review-methodology/) explains those evidence boundaries and what a hands-on claim would require. It also explains how the current review rating should be read. This About page summarizes the site's purpose rather than repeating that process in full. ## How claims are handled Current editorial work starts with the reader's task, checks relevant official documentation and attributable sources, and records limits when direct access or evidence is missing. Version-sensitive claims such as prices, supported systems, bundle contents and menu paths need a dated source. Community discussion can identify a question, but it does not prove a product fact or a result for every user. The [Editorial Policy](https://soundforgepro.com/editorial-policy/) describes the site's sourcing and disclosure rules. Documentation-led guidance is not presented as a measurement or listening result. A numerical fixture proves only the calculation it exercises. A browser check proves only the specified browser behavior. Claims about a Windows application session, audio output or a physical setup require separate evidence tied to that claim. ## Editorial identity Erick Finn is the editorial byline used for this site. The byline identifies responsibility for the published work; it does not, by itself, establish professional credentials, residence, equipment ownership or a history of using Sound Forge. Readers should judge a page by its cited evidence, stated limits and correction record. The existing [author profile](https://soundforgepro.com/author/erick/) and linked Facebook and X profiles remain the site's author and social references. ## Corrections and contact Facts can change and editorial checks can miss an error. The [Corrections Policy](https://soundforgepro.com/corrections/) explains how to report a disputed claim and how material changes are recorded. Include the page URL, the wording at issue and a primary source or reproducible steps when possible. ### Disclaimer & Independence URL: https://soundforgepro.com/disclaimer/ Last updated: 2026-10-09T21:08:48.000Z SoundForgePro.com is an independent editorial guide to Sound Forge and audio-editing workflows. It is not the official product website or a vendor support service. The [About page](https://soundforgepro.com/about/) explains the site's purpose and authorship. **Correction, September 16, 2026:** this page previously described its editors as software users and made unqualified claims about vendor payment, approval and affiliate income. Those statements have been removed because the records available for this review did not establish them. ## Separate from the vendor This is a separate publication, not an official Boris FX, MAGIX, Vegas Creative Software, Sony Creative Software or Sonic Foundry site. Product names, links and illustrations do not indicate vendor endorsement. For purchase, account or license support, use the vendor's official support channels. Our [review methodology](https://soundforgepro.com/review-methodology/) distinguishes documentation-based guidance from measured tests. An editorial rating, illustration or byline does not establish that someone tested a product or listened to an audio result. ## Affiliate links A separate editorial identity does not establish the absence of financial relationships. The [Editorial Policy](https://soundforgepro.com/editorial-policy/) requires any material relationship affecting a recommendation to be disclosed near the relevant content. A general disclaimer or a plain-looking URL is not a substitute for that disclosure. The US Federal Trade Commission's [endorsement guidance](https://www.ftc.gov/business-guidance/resources/ftcs-endorsement-guides-what-people-are-asking) explains why readers need to know about relevant payments, free products or commissions. This page does not certify every historical recommendation or private arrangement. ## Trademarks Product names and logos belong to their respective owners and are used here to identify the software discussed. Boris FX [announced its acquisition](https://blog.borisfx.com/press/boris-fx-acquires-vegas-pro-sound-forge-and-acid-pro) of Sound Forge, Vegas Pro and ACID Pro from MAGIX on March 30, 2026\. References to earlier vendors in a guide may concern a historical version. ## Accuracy Software, prices, system requirements and licensing terms can change. Check the current vendor documentation and offer before buying or applying version-specific instructions. Keep an untouched copy of your audio before destructive processing, and check the saved result before replacing an original. To report an error, follow the [Corrections Policy](https://soundforgepro.com/corrections/) and include the page URL, disputed wording and supporting source or reproducible steps. ### Editorial Policy and Disclosure Standards URL: https://soundforgepro.com/editorial-policy/ Last updated: 2026-10-10T14:10:32.000Z **SoundForgePro.com is a separate editorial site about Sound Forge and related audio-editing workflows. It is not an official Boris FX, MAGIX, Sony Creative Software, or Sonic Foundry publication, and references to their products do not imply vendor endorsement.** **Correction, September 16, 2026:** an earlier version made broad claims about sponsorship, affiliate revenue, outside approval, universal sourcing, hands-on authorship and update practices that we could not substantiate across the site's history. It also used a speculative product-integration example that no longer provided reliable current context. Those statements have been removed or limited below. This policy describes the standard for current editorial corrections and future work; it does not certify every older page. ## Evidence and sourcing Claims should be matched to the most direct source available. Product features, supported systems, prices, bundle contents, release details and menu paths should be checked against current vendor documentation or another source responsible for the fact. A source should be linked near the claim when it helps the reader verify it. Older ownership or feature history should be labeled with the relevant period instead of being presented as current. Documentation supports what a vendor publishes. It doesn't prove application performance, listening results or personal use. Community reports can point to a question worth investigating, but they don't settle the result for every user. A calculation, browser check or application test should be described only within the limits of the evidence recorded for it. The [Review Methodology](https://soundforgepro.com/review-methodology/) explains these distinctions in detail. ## Reviews and recommendations A recommendation should identify the evidence behind it and separate documented capabilities from direct observation. If a page reports a hands-on test, it should state the software build, relevant settings, input material, equipment or environment, measurement method and limitations. Without that record, the wording should remain documentation-led rather than imply a product session or listening comparison. Ratings are editorial judgments unless a page explicitly defines another method. They must not be described as user aggregates, laboratory scores or measured category averages without corresponding evidence. The current [Sound Forge review](https://soundforgepro.com/sound-forge-pro-review-2026/) explains how its rating should be read. ## Commercial relationships and disclosures If a sponsorship, affiliate arrangement, free access, gift or other material relationship affects a page, it is disclosed clearly near the relevant recommendation or link so readers can weigh it. Paid or affiliate links, if used, also carry the appropriate rel attribute (sponsored or nofollow). A September 16, 2026 review of the current public HTML found no outbound links marked `rel="sponsored"` and no recognizable affiliate redirect pattern. Where a material relationship applies, readers should be able to rely on a clear page-level disclosure instead of guessing from URL formatting. The site's [Disclaimer](https://soundforgepro.com/disclaimer/) explains the separate-site and trademark context. ## Authorship and automation Erick Finn is the editorial byline used on this site. The byline shows who is responsible for published work; on its own it doesn't prove credentials, location, equipment ownership or hands-on product use. The [About page](https://soundforgepro.com/about/) describes the site's current purpose and identity boundaries. AI-assisted tools and scripts may help with research, drafting, claim comparison and technical validation. Their output isn't a source, and it doesn't show that anyone operated Sound Forge, listened to audio or verified a product claim. Material statements are checked against the cited source before publication. ## Updates and corrections Current corrections should keep the page URL where practical, update visible text and dependent structured data together, and add a dated note when an earlier material claim could mislead a reader. A modified date should reflect a substantive change; it isn't a cosmetic freshness signal. To report an outdated instruction, unsupported experience claim or other factual error, follow the [Corrections Policy](https://soundforgepro.com/corrections/) and include the page URL, the disputed wording and a primary source or reproducible steps when possible. ## Publication boundaries - No fabricated named users, quotations, testimonials, test sessions or measurements. - No cracks, keygens, serial numbers or unofficial download mirrors. - No synthetic or altered interface presented as a genuine product screenshot. - No speculation presented as a confirmed feature, acquisition plan or release commitment. ### Corrections Policy URL: https://soundforgepro.com/corrections/ Last updated: 2026-10-10T14:13:16.000Z **This page explains the current correction process for SoundForgePro.com. It does not certify that every older article or past edit followed the same process.** **Correction, September 16, 2026:** an earlier version promised that every repeated fact would be checked on every related page, that each substantive change would receive an amber update box near the top, and that a July 2026 review covered 44 articles and changed four pages. The available records do not substantiate those universal and historical claims, so they have been removed. ## What we treat as a correction A correction fixes a factual error or an unsupported material claim: a wrong price, product owner, supported system, menu path, feature description, measurement or statement of direct experience. New information that nobody could have known when a page went up may be labeled as an update instead. Spelling, layout and internal-link changes that don't change the meaning count as maintenance edits. ## How a current correction is handled 1. Identify the exact wording and the evidence that contradicts or qualifies it. 2. Check the most direct current source available. For a reproducible technical issue, record the relevant build, settings and steps. 3. Correct the visible page. Add a dated correction or update note when the earlier wording was material enough that a reader should know it changed. 4. Dependent structured data gets updated too when it represents the corrected fact. Structured data has to match the visible page, and having it doesn't guarantee any search feature. 5. Change the modified date only for a substantive revision. The published date remains the original publication date. 6. Specifically identified related pages and shared references are checked when the same disputed fact may appear there. The [Editorial Policy](https://soundforgepro.com/editorial-policy/) describes current sourcing and disclosure standards. The [Review Methodology](https://soundforgepro.com/review-methodology/) explains what documentation, calculations, browser checks and hands-on claims can support. ## Revision record and limits The corrected text normally replaces the inaccurate wording at the same URL, with a dated note naming the material point that changed. This Ghost site doesn't currently offer a complete public version archive or a line-by-line diff for every page, so the modified date tells you a page changed without listing each revision. Each correction covers the evidence and pages reviewed for that issue. Historical examples appear only when the underlying records back up their dates, scope and counts. ## Report an error Send a report through Erick Finn's [Facebook profile](https://www.facebook.com/profile.php?id=61589292558018) or [X profile](https://x.com/Erick%5FSoundF). Include: - the page URL; - the exact sentence, table entry or structured-data fact at issue; - what you believe is wrong; - a primary source, screenshot or reproducible steps, when available; - the relevant product version, operating system and settings for a technical report. These profiles are the public reporting routes the site currently shows. The [About page](https://soundforgepro.com/about/) explains the editorial byline and evidence boundaries. ### Terms of Use URL: https://soundforgepro.com/terms/ Last updated: 2026-10-09T22:12:19.000Z By using SoundForgePro.com you agree to these terms. If you do not agree, do not use the site. ## Informational content only Everything on this site is published for general informational purposes. Guides describe documented workflows and settings; audio setups differ, and results on your system may differ. Nothing here is professional, legal, or purchasing advice. Verify current prices, licensing terms and system requirements on official vendor pages before buying anything. ## No warranty The site is provided "as is", without warranties of any kind. We work to keep content accurate and current (see the [Editorial Policy](https://soundforgepro.com/editorial-policy/)), but we do not guarantee that any page is free of errors or up to date at the moment you read it. ## Limitation of liability To the maximum extent permitted by law, SoundForgePro.com is not liable for any loss or damage arising from the use of this site, including data loss caused by following editing or restoration workflows. Back up your audio files before applying destructive edits. ## Intellectual property Original text and original illustrations on this site are copyright of SoundForgePro.com and may not be republished without permission. Sound Forge, Boris FX, MAGIX, iZotope and all other product names are trademarks of their respective owners; their use here is for identification and does not imply affiliation or endorsement. ## External links The site links to external resources, including official vendor pages. We are not responsible for the content, availability, or terms of external sites. Outbound links to vendor pages carry a plain referral tag (`?ref=soundforgepro.com`) that identifies this site as the traffic source; it does not track you. It is not an affiliate tag — this site earns no commission on anything you buy. ## Changes These terms may be updated; the current version is always at this URL. ### Privacy Policy URL: https://soundforgepro.com/privacy/ Last updated: 2026-07-30T10:29:55.000Z This page describes what data is processed when you use SoundForgePro.com, in plain language. Last updated: July 15, 2026. ## The short version - No advertising networks, no ad trackers, no ad-personalization scripts. The site uses Google Analytics 4 for aggregate traffic statistics only. - No affiliate links and no affiliate tracking — outbound vendor links earn this site nothing. - Reading the site requires no account and no personal data. - If you subscribe by email, your address is stored by our publishing platform and used only to deliver posts. ## Hosting and technical data The site runs on [Ghost(Pro)](https://ghost.org/), a managed publishing platform operated by the Ghost Foundation, with content delivered through the Fastly CDN. Like any web host, the platform processes technical request data (such as IP addresses and browser information) in server logs to deliver pages and protect the service. We do not use this data to identify visitors. ## Analytics The site uses Ghost's built-in, first-party analytics and Google Analytics 4 (GA4). Both show aggregate information such as page views, approximate location at city level and device type, so we can see which guides are read. GA4 is configured for measurement only: no Google advertising features, no ads personalization, and GA4 does not log full IP addresses. We do not sell or share this data, and there is no cross-site tracking pixel on this site. ## Email subscription Subscribing is optional and free. If you subscribe, your email address is stored in Ghost and used solely to send you new posts. Every email includes an unsubscribe link; unsubscribing or deleting your membership removes you from the list. We do not sell, rent, or share subscriber emails with anyone. ## Cookies The site sets functional cookies provided by the Ghost platform (for example, to keep a subscriber signed in) and Google Analytics cookies (names starting with \_ga) used to distinguish visits for aggregate statistics. There are no advertising or cross-site tracking cookies. ## Outbound links Links to vendor pages carry a static referral tag (`?ref=soundforgepro.com`) that tells the destination site where the visit came from. It contains no personal data. ## Your choices and rights You can read this entire site without providing any personal data. Analytics can be blocked with any content blocker or Google's own opt-out browser add-on, and the site works fully without it. Subscribers can unsubscribe or request deletion of their membership data at any time. For privacy questions or data requests, contact the author via Facebook or X. ## Changes If our data practices change — for example, if new tooling is added — this page will be updated first, with the "last updated" date above reflecting the change. ### Contact URL: https://soundforgepro.com/contact/ Last updated: 2026-09-27T09:29:05.000Z SoundForgePro.com is written and maintained by one person, [Erick Finn](https://soundforgepro.com/author/erick/). There's no support team and no contact form, but real messages get real answers. ## How to reach me - [**X (Twitter): @Erick\_SoundF**](https://x.com/Erick%5FSoundF) is the fastest route. A public mention or a DM both work. - [**Facebook**](https://www.facebook.com/profile.php?id=61589292558018) gets checked less often than X, but messages there do get read. There's no public email inbox for this site. The social profiles above are the reliable way to get through, and they also let you confirm you're talking to the actual author. ## What to write about - **Factual errors.** A wrong price, a menu path that's gone, a claim that doesn't match the current build. When a report checks out, the article gets corrected with a dated note. - **Questions about a guide.** If a workflow from this site behaves differently on your system, include your Sound Forge version and Windows build. - **Topic suggestions.** If a Sound Forge task isn't covered here, say so. Gaps get prioritized by how often people ask about them. ## What this is not the address for - **Sound Forge product support.** Boris FX handles licensing, activation and refunds, so start at the [official product page](https://www.soundforge.com/sound-forge/). - **Sponsored posts, link placements, or advertising.** The site doesn't sell placements of any kind, so those messages go unanswered. ## Response time Usually within a few days. It's a one-person site run alongside real production work, so thanks for your patience. Error reports jump the queue. ### Review Methodology: Research and Evidence URL: https://soundforgepro.com/review-methodology/ Last updated: 2026-10-09T21:08:37.000Z **Our review methodology is documentation-led editorial research.** SoundForgePro.com explains audio-editing workflows and buying decisions using vendor documentation, attributable sources and clearly limited checks. Reading a manual, checking a calculation or trying a browser tool doesn't amount to hands-on experience with the Windows application. **Correction, September 15, 2026:** an earlier version of this page described a specific Windows computer, recording interface, monitoring equipment and software installations as our test bench. It also said every guide and recommended setting had been tested in Sound Forge. We could not substantiate those claims with corresponding test records, so we have removed them. They should not be relied on as evidence of product testing. ## How we research a guide The current correction process starts with the reader's task and the existing article. We compare relevant search results, read official help and product pages, and check individual claims against their sources. Menu instructions, platform requirements, prices and bundle contents each need their own evidence, since a product announcement doesn't confirm every workflow. We keep current documentation apart from historical versions and give a check date wherever the facts can change. When sources conflict or access is incomplete, the article should explain the limit instead of turning an inference into a fact. Community reports can flag a problem worth investigating, but they aren't controlled tests, and they don't prove every user will run into it. The [Editorial Policy](https://soundforgepro.com/editorial-policy/) sets out the site's sourcing rules. ## What our checks can prove - **Documentation review:** supports a description of a documented feature or procedure. It can't measure speed, stability, sound quality or compatibility with your particular setup. - **Numerical examples:** check the stated calculation and its assumptions. The [Channel Converter guide](https://soundforgepro.com/sound-forge-channel-converter/), for example, uses channel-mixing arithmetic. Its correction records cover synthetic routing cases; no recordings were processed in a Windows Sound Forge session. - **Browser-tool checks:** exercise a specified web implementation. The [left/right speaker tool](https://soundforgepro.com/left-right-speaker-test/) has recorded Chromium checks of Web Audio panning, start/stop behavior and responsive layout. Output was muted, so those checks didn't confirm audible channel routing, physical speakers or an iPhone. - **Application or listening tests:** require their own evidence. A browser result, mathematical example, illustrative image or source quotation must not be presented as a Sound Forge session or listening comparison. For a hands-on result to mean something, the article has to say what was tested, the software build, the relevant equipment, input material, settings, measurement method and limitations. Supporting logs, output files or genuine captures have to match that claim. Without them, read the passage as documentation-based guidance rather than a measured result. Try any consequential processing on a copy of your audio and compare the saved output before you apply it to an archive or delivery job. ## Ratings and recommendations The [Sound Forge review](https://soundforgepro.com/sound-forge-pro-review-2026/) explains its 4.2/5 as an editorial judgment about documented capabilities and buying fit. It isn't a user aggregate, a laboratory benchmark or an average of measured category scores. Read its reasons and limitations before you take the number as a recommendation for your work. This methodology page doesn't certify any particular build's performance or promise a re-test after every release. ## Automation and editorial limits AI-assisted tools are used in this correction workflow for research, drafting, claim checking and technical validation. Scripts can compare saved revisions, validate links and structured data, and run numerical fixtures. Neither an AI response nor a passing script is evidence that someone operated Sound Forge or listened to an audio result. Google's [people-first content guidance](https://developers.google.com/search/docs/fundamentals/creating-helpful-content) asks publishers to explain who created content and how it was produced, and its [review guidance](https://developers.google.com/search/docs/specialty/ecommerce/write-high-quality-reviews) calls for evidence behind experience claims. They're useful standards for disclosure. They don't endorse this site or guarantee search rankings. ## Corrections and scope This page describes the evidence boundaries of the current correction work. It doesn't certify that every older article followed this process, or that repeated editorial checks add up to independent product tests. Material corrections belong in the affected article and its structured data. Shared claims on other pages need their own review, and this correction doesn't validate them. To report an unsupported claim or an outdated instruction, follow the [Corrections Policy](https://soundforgepro.com/corrections/) and include the page URL, the disputed wording and the source or reproducible steps that support your report. ### Image Rights and Licensing URL: https://soundforgepro.com/image-rights/ Last updated: 2026-10-09T21:08:43.000Z This page explains who owns the images published on SoundForgePro.com and where to request permission to reuse them. ## Original SoundForgePro.com images Illustrations and graphics credited to SoundForgePro.com are original editorial material. You may link to the page where an image appears. Republishing, modifying or using an original image in another publication, product or commercial project requires written permission. ## Interface illustrations Some guides use original instructional illustrations that reproduce the layout or controls of an audio application so readers can follow a workflow. These are editorial reconstructions, not proof that we installed or tested the software, and they do not imply sponsorship or affiliation with the software vendor. ## Third-party images and trademarks Product names, trademarks, logos and official images remain the property of their respective owners, including Boris FX, Microsoft, SOURCENEXT, Parallels and Steinberg. When an image is identified as third-party material, SoundForgePro.com cannot grant a license for it. Permission must be requested from the relevant rights holder. ## How the image metadata works Image metadata names the creator or rights holder indicated by the image source or an explicit credit. A licensing link on a third-party image points to this policy so the ownership boundary is clear; it does not transfer any third-party rights to SoundForgePro.com. ## Request permission or report an attribution issue For permission to reuse an original SoundForgePro.com image, or to report an incorrect credit, use the [contact page](https://soundforgepro.com/contact/). Include the page URL and the image you mean. We will confirm whether we control the requested rights before granting permission. ## Posts ### Speaker Polarity Test: Check If Speakers Are Out of Phase URL: https://soundforgepro.com/speaker-polarity-test/ Last updated: 2026-10-08T06:30:18.000Z Sit centered between your speakers, turn the volume down and press **Play A/B**. Switch between In phase and Right inverted while it plays. With correct wiring, In phase sounds centered and fuller in the bass, and the inverted version sounds wide and hollow. If it is the other way round, plus and minus are swapped at one speaker. If you have a phone polarity app or a handheld tester, switch to **Pulse for a tester** instead. Polarity only makes sense once both speakers play on the correct sides, so if you are not sure of that, run the [left and right speaker test](https://soundforgepro.com/left-right-speaker-test/) first. Browser tool · no microphone ## Check speaker polarity Signals are made on this device. No microphone, no upload. A browser can't see your wiring: you listen, or a tester reads the pulse. !**Lower system volume before Play.** Tool level starts at 5%, caps at 25% and is not dB SPL. Stop at any crackle, buzz or discomfort. **By ear**Listen A/B **With a tester**Pulse for a tester Listen A/B · both speakers **In phase** L R Low noise · 40–200 HzSame signal both sides Playback**Stopped** Press Play, then switch versions while it plays. Play A/BStop **Listen A/B.** Sit centered between the speakers, press Play and switch versions while it plays. Signal Low noise · 40–200 HzPink noise80 Hz tone Version In phaseRight invertedAlternate 3 s **Pass:** In phase sounds centered and fuller in the bass; Right inverted sounds wide, hollow and hard to place. **In phase is the hollow one:** \+ and − are swapped at one speaker. Swap them at that speaker only, then play again. Inverted almost silent: the device is playing in mono. Both versions sound the same: [check that both speakers are playing](https://soundforgepro.com/speaker-test/). **Subwoofer:** choose 80 Hz tone and In phase, then try the sub's phase or polarity switch from your seat and keep the setting that sounds louder. **Pulse for a tester.** A positive-going pulse once per second, 20 times, for a phone polarity app or a handheld tester. The page plays the pulse; it does not listen. Send pulses to LeftRightBoth **Pass:** compare like with like. Left woofer against right woofer, same pulse, tester held close to the driver and away from bass ports. Matching readings mean the pair is wired the same way. **Opposite readings on matching drivers:** check that speaker's wiring. A tweeter or midrange reading opposite its woofer can be correct by design. Tool level 5% Ready. Pick a mode, then press Play. Space plays or stops when focus is outside the controls. Band-limited noise, pink noise, an 80 Hz sine and a 9 ms positive pulse. Not calibrated output or an SPL reading. Press Escape to stop. ## How to test speaker polarity 1. **Check left and right first.** A polarity check compares two speakers that already play on the correct sides. If one channel is silent or the sides are swapped, fix that before anything else. 2. **Lower the volume and sit centered.** Turn the system volume down before you press Play. The tool level starts at 5% and caps at 25%, but it cannot see your amplifier or the speakers' own volume knob. Sit where both speakers are the same distance from you. 3. **Play the low noise in phase.** Press Play A/B with Low noise and In phase selected. You should hear a steady rumble that seems to come from the space between the speakers. 4. **Switch to Right inverted.** Tap Right inverted while it plays, then go back to In phase. If switching by hand is too fast to judge, choose Alternate 3 s and the page swaps the versions every three seconds. 5. **Decide which version sounds fuller.** The version with more bass and a firm center is the one that matches your wiring. If that is In phase, your speakers are wired the same way round. If it is Right inverted, one speaker is reversed. 6. **Fix one speaker and play again.** Swap plus and minus at one speaker only, then repeat the A/B. In phase should now be the fuller version. If the low noise is hard to judge on small speakers, try Pink noise. Space plays or stops when focus is outside the controls, Escape always stops playback, and sound ends when you switch tabs or leave the page. Changing mode stops whatever is playing. The A/B stops on its own after 30 seconds, and the pulse run after 20 pulses. ## What each result means The listening A/B compares how your two speakers add up at your seat. The pulse mode gives an external tester something to read, one driver at a time. Each result tells you where to look next. | What you notice | What it means | What to do | | -------------------------------------------------------------------------- | ---------------------------------------------------------------------- | -------------------------------------------------------------------- | | In phase sounds centered and fuller; Right inverted sounds wide and hollow | Both speakers are wired the same way round | Nothing to fix | | In phase sounds hollow; Right inverted sounds fuller | Plus and minus are swapped somewhere in one speaker's path | Swap plus and minus at one speaker, then play again | | Right inverted is almost silent | The device is playing in mono: a single speaker, or Mono audio is on | Turn Mono audio off; a one-speaker device has no polarity to compare | | Both versions sound the same | Sound is reaching only one speaker, or you are sitting far to one side | Check left and right, then sit centered | | Little difference with Low noise | Small speakers may not play much of the 40–200 Hz band | Switch to Pink noise | | Pulse: matching drivers give the same reading | The pair is wired the same way | Nothing to fix | | Pulse: left woofer and right woofer read opposite | One of the two is wired backwards | Check that speaker's cable and terminals | | Pulse: a tweeter or midrange reads opposite its woofer | Often deliberate in the crossover design | Compare it with the same driver in the other speaker | ![Four speaker polarity checks: in phase sounds centered and full, a battery moves the woofer forward, a multimeter on DC volts with a battery at the far end, and a pulse tester where matching drivers read the same](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/10/speaker-polarity-test-methods.webp) Four checks and what a wrong result points to. A tweeter reading opposite its woofer is not automatically a fault. I'd start with the listening A/B. It needs nothing but your ears and the page, and it checks the thing that actually matters: whether the two speakers add up or cancel where you sit. The battery and meter checks answer a narrower question, which wire is which, and they are the ones to reach for when the A/B says something is reversed but you can't see the markings. ## Polarity vs phase: what "out of phase" means Speakers wired backwards are usually called "out of phase", but the accurate word is polarity. In a Sound On Sound [Q&A on what phase is](https://www.soundonsound.com/sound-advice/q-what-phase-and-how-can-it-be-used-line-analogue-recorders), Hugh Robjohns writes that "the term 'phase' is frequently misused to mean polarity or delay — which are entirely different things". Reversing polarity "simply swaps the positive and negative halves of the cycle over — a kind of mirror image", and it does so equally at every frequency. A delay is different: it shifts phase by an amount that is "frequency dependent". Robjohns names the wiring fault directly: miswired loudspeaker cables with the two wires "accidentally reversed in one connector create a polarity reversal too." Mike Senior makes the same distinction in his Sound On Sound article [Phase Demystified](https://www.soundonsound.com/techniques/phase-demystified): "180 degrees out of phase" is often used for a waveform that has been flipped upside down, which is "more unambiguously referred to as polarity reversal". This page checks the polarity of your speaker wiring. To check whether a recording has a flipped or delayed channel, load it into the [phase correlation meter](https://soundforgepro.com/phase-correlation-meter/), and for fixing that inside Sound Forge, see the guide to [mono compatibility and phase correlation](https://soundforgepro.com/mono-compatibility-phase-correlation/). ## Why reversed speakers sound hollow With one speaker reversed, its cone moves out while the other moves in, so part of the sound cancels between them. The audiocheck.net [stereo polarity test](https://www.audiocheck.net/audiotests%5Fpolaritycheck.php) explains that a single speaker's direction "has no influence on the perceived sound", but with two or more speakers "polarity defines how these speakers interact". The cancellation is "stronger at lower frequencies" and "will result in a loss of bass. It also drastically distorts the stereo imaging." Paul White's list of [common studio problems](https://www.soundonsound.com/techniques/studio-sos-common-studio-problems) in Sound On Sound describes the same thing in practical terms: "a loss of bass, a lack of focus in the sound-stage", and a feeling "like having your ears sucked out by a sink plunger!" That is why the default signal is noise limited to 40–200 Hz rather than a single tone. Robjohns calls checking polarity with a constant tone "surprisingly difficult" in his guide to [creating a test CD](https://www.soundonsound.com/techniques/creating-test-cd), and his later [SOS audio test files](https://www.soundonsound.com/techniques/sos-audio-test-files) note that with a sine wave "the relative phases of the two channels are notoriously difficult to detect by ear". Band-limited noise puts its energy where the cancellation is strongest. Pink noise covers the whole range for small speakers, and the 80 Hz tone is there for subwoofer alignment. Matt Houghton describes the listening cue in a Sound On Sound [Q&A on polarity inverters](https://www.soundonsound.com/sound-advice/q-whats-point-polarity-inverter-monitor-controller): check "whether the stereo image becomes more or less focused when flipped". The comparison works best from a seat the same distance from both speakers. If your desk or sofa sits well to one side, the [speaker placement calculator](https://soundforgepro.com/speaker-placement-calculator/) helps you set up an equal triangle first. ## How to fix reversed speaker polarity The fix is a swap at one end of one speaker. audiocheck puts it plainly: "simply flip the connecting wires of one of your speakers — not both!" Swapping both leaves them just as mismatched as before. - **Passive speakers.** Follow each cable from the amplifier to the speaker and make sure plus goes to plus at both ends. IEC 60268-5, the international standard for loudspeakers, says the positive terminal is "marked with a + symbol, or a red marking, or in a way stated by the manufacturer". On the cable itself, one conductor usually carries a stripe, ridge, printed text or a different color. Klipsch's support article on [speaker polarity](https://support.klipsch.com/hc/en-us/articles/360025618891-Polarity) suggests the easy way to avoid the mistake in the first place: "the simplest solution is to use color coded speaker wire". - **Active speakers.** White gives the usual cause as "an incorrectly wired balanced cable". Swap the two speakers' cables and run the A/B again. If the problem moves to the other side, the cable is the culprit. - **Something upstream.** If the wiring checks out and the A/B still says one side is reversed, look at the equipment before the speakers: a polarity switch on an interface, preamp or monitor controller (Robjohns notes the "invariably misnamed 'Phase' button" on preamps is a polarity reversal), a DSP or room-correction setting on one channel, or an inverted output. In a Sound On Sound [Q&A on inverted aux outputs](https://www.soundonsound.com/sound-advice/q-why-are-my-mixers-aux-outs-polarity-inverted), Robjohns explains that "the aux outputs are commonly inverted on many budget mixers as a deliberate design 'feature'". Replacing a run anyway? The [speaker wire size calculator](https://soundforgepro.com/speaker-wire-size-calculator/) tells you what gauge the length needs, and buying a cable with clearly marked conductors saves you from repeating this check. ## Check speaker polarity with a battery The battery check answers a narrower question: which lead of a passive speaker or its cable is positive. IEC 60268-5 defines the positive terminal as the one where a positive voltage causes "an increase of sound pressure at the front of the drive unit", and its test method is to "apply a positive d.c. voltage briefly" to that terminal. In plain terms, with battery plus on the speaker's plus, the cone moves forward, toward you. 1. **Disconnect the cable at the amplifier or receiver.** Klipsch's method starts "with the speaker wire disconnected at the amplifier or receiver". Never do this with an amplifier connected. 2. **Find the woofer.** Watch the largest driver. Take the grille off if you can, or shine a light across the cone so small movements are easier to see. 3. **Touch the battery briefly.** Hold the lead you think is positive on the battery's plus terminal and the other on minus, for a moment only. Axiom Audio's Mike Rogers, in his video on [speakers wired out of phase](https://www.axiomaudio.com/blog/phase), says to "touch this a couple of times to the battery." 4. **Read the movement.** Klipsch: "The woofer will move forward if the polarity is correct. If it moves backward, the polarity is reversed". On a bare driver, Celestion's [Dr Decibel FAQ](https://celestion.com/dr-decibel/) describes the same result as the cone moving "away from the magnet assembly a small distance". 5. **Mark the lead and repeat on the other speaker.** Use the same battery and the same lead-to-terminal pairing for both, so you are comparing like with like. Sources disagree on the battery: Klipsch and Axiom use a 9-volt battery on complete speakers, while Celestion writes, "we usually use a 4.5V radio battery" for its guitar drivers. There is no universal figure. I'd start with the smallest battery you have and keep the contact brief, moving up only if the woofer doesn't visibly move. Watch the woofer only. A tweeter is small and easy to damage, and in a passive speaker it normally sits behind a crossover capacitor that blocks DC anyway, so it won't show you anything. The battery check is also for passive speakers only. A powered speaker or subwoofer has its own amplifier inside, so never put a battery on its inputs. ## Check speaker wire polarity with a multimeter A multimeter cannot read polarity from music playing through a speaker. What it can do is tell you which conductor of an unmarked run is which, which helps with in-wall cables, long runs and car doors where you can't see both ends at once. The method uses the sign on a digital meter's DC-volts display. Fluke's guide to [measuring DC voltage with a digital multimeter](https://www.fluke.com/en-us/learn/blog/digital-multimeters/how-to-measure-dc-voltage-with-a-digital-multimeter) notes that "if the probes touch opposite terminals, a negative symbol will appear in the display." 1. **Disconnect both ends of the run** from the amplifier and the speaker. 2. **Put a battery on the far end.** Connect battery plus to the conductor you want to call positive and minus to the other. 3. **Set the meter to DC volts.** Fluke reminds you to put the red probe "into the input jack marked V, not A". 4. **Measure at the near end.** Red probe on one conductor, black on the other. A plain reading means the red probe is on the positive conductor. A minus sign means it is on the negative one. Mark the positive conductor. 5. **Remove the battery** before you reconnect anything. This sign trick is for a digital meter. Fluke warns that on an analog meter the red lead should always touch the positive terminal: "Otherwise, damage to the meter will occur." ## Pulse polarity testers and phone apps Handheld polarity testers and phone apps work in pairs: one part plays a pulse, the other listens with a microphone and reports which way the first movement went. Klipsch notes that "commercially available polarity testers can also be used". The Pulse for a tester mode here is the playback half: one positive-going pulse per second, 20 times, to Left, Right or Both. The page plays the pulse; your tester or app does the listening. The readings are easy to misread. These rules come from the people who make the apps and testers: - **Compare like with like.** The developer of the Android [Polarity Checker app](https://play.google.com/store/apps/details?id=com.dwa%5Fict.polaritychecker) writes "Red is NOT bad!!", because many crossover designs connect some drivers in reverse polarity, "so for instance the high frequency speaker CAN be opposite polarity to the low frequency speaker". Andy Wehmeyer of Audiofrog, in his guide on [how to test for polarity](https://www.audiofrog.com/how-to-test-for-polarity/), says a passive crossover "might necessitate a polarity reversal on the mid" and that "the phase shift in a crossover isn't a mistake. It's how crossovers work." So check the left woofer against the right woofer, not a tweeter against a woofer. - **Use the same pulse.** The same app listing warns that "using a different pulse signal CAN give opposite readings" and asks you to "use the same pulse when comparing!" - **Hold the microphone close.** Measure "as close to the speaker as possible (and away from bass-ports)". Studio Six Digital's [Speaker Polarity app page](https://studiosixdigital.com/audiotools-modules-2/speaker-test-modules/speaker%5Fpop/) suggests that "6″ to 2′ will usually work well". - **Play one speaker at a time.** Wehmeyer advises turning off "the REST of the speakers to avoid some unwanted contribution from the other speakers." The Left and Right buttons do this for a stereo pair. Subwoofers and midbass drivers need a longer pulse. Wehmeyer writes that the pulses on the CD supplied with one handheld tester are "not long enough to allow you to get a polarity reading for midbass speakers or subwoofers through low pass filters". The pulse here follows the shape he describes as more useful: "a right triangle and the entire waveform is ABOVE zero", about 9 milliseconds long, which is "enough to provide some signal at really low frequencies." Studio Six adds that "you may need louder signals to test subwoofers". The tool level is capped at 25%, so raise the amplifier a little at a time if the tester gets no reading. One more limit: the pulse leaves the browser positive-going, but your operating system, interface, amplifier or a DSP can invert it on the way, as the aux-output example shows. A single reading on its own says less than a comparison between two speakers fed through the same chain. To prove what a chain does to absolute polarity, Robjohns' test files guide suggests recording asymmetrical test signals in a DAW or viewing them "directly on an oscilloscope". ## Subwoofer polarity and phase A subwoofer's polarity or phase control isn't a wiring fix. It lines the sub up with your main speakers where their ranges overlap. In a Sound On Sound [Q&A on aligning a subwoofer with satellites](https://www.soundonsound.com/sound-advice/q-how-do-ensure-my-subwoofer-and-satellite-speakers-are-phase-aligned), Robjohns explains that the two "usually cross over somewhere around 80-100 Hz", and that if they cancel "there would be a large dip in amplitude through the cross-over region". His method is to "play a sine wave tone at the appropriate crossover frequency (typically 80Hz)" and "adjust the subwoofer phase to find the loudest perceived output at the listening position". A simple 0/180 switch is fine, he adds, "because the wavelengths involved are so long". To do that here, choose Listen A/B, the 80 Hz tone and In phase, then try each setting of the sub's switch or dial from your seat and keep the one that sounds loudest. A helper at the sub makes this much quicker. The page sends stereo, not a separate LFE channel, so this works when the sub receives bass from the main left and right channels. If your crossover sits at another frequency, play that frequency on both channels with the [online tone generator](https://soundforgepro.com/online-tone-generator/). The loudest setting can be 180 degrees, and that is not a wiring fault. ## Car speaker polarity The same rules apply in a car, with three complications: no seat is centered between the speakers, the wiring hides behind door panels, and many systems run through a factory or aftermarket processor. - **Use fader and balance.** Play the pulse with balance and fader set so one speaker plays at a time, then compare the left front woofer with the right front, and the rear pair with each other. - **Listen for bass, not the image.** From the driver's seat the listening A/B is a rough check, because one side is much closer. Low frequencies are the least affected by where you sit, so judge which version has more bass rather than which sounds centered. - **Doors without removing the panel.** A pulse tester held at the grille reads the woofer directly. With the head unit or amplifier disconnected, the battery and meter checks work at the harness end of each speaker's wires. - **Component sets.** A separate tweeter can read opposite its woofer by design. Compare left tweeter with right tweeter. ## Headphone polarity Headphones behave differently because nothing cancels in the air between them. audiocheck says out-of-phase headphones leave you with "the impression of a sound twisted inside your head", with no cancellation "because the two speakers are physically separated by your head". This page is built for speakers. The [headphone test](https://soundforgepro.com/headphone-test/) has its own optional phase step with a 500 Hz tone and the right side inverted. ## What this polarity test cannot tell you - It cannot see your wiring. There is no microphone: you listen to the A/B, or an external tester reads the pulse. - The A/B checks relative polarity, whether your two speakers match. It does not prove the absolute direction at the cone, because equipment in the chain can invert the signal. - It cannot separate the drivers inside one speaker by ear. Use a pulse tester on each driver and compare matching drivers. - A device with one speaker, or with Mono audio on, has nothing to compare. - Spatial audio, virtual surround, room correction, EQ and similar processing in your device or speakers can blur the difference. Turn them off for the test. - It plays stereo only, so it does not test center, surround or LFE channels, and it is not a sound level measurement. ## How the page makes the signals Every signal is written as a list of numbers into a Web Audio [AudioBuffer](https://developer.mozilla.org/en-US/docs/Web/API/AudioBuffer), whose samples MDN describes as having "a nominal range between -1 and +1". The inverted version writes the same samples into the right channel with every sign flipped, so the two sides are exact mirror images. The low noise is pink noise passed through a 40 Hz high-pass and a 200 Hz low-pass filter, and the tone is an 80 Hz sine. The pulse jumps to its peak, falls back to zero over 9 milliseconds and never goes below zero, once per second. Sound only starts after you press a button, as the [browser autoplay rules](https://developer.mozilla.org/en-US/docs/Web/Media/Guides/Autoplay) require, and the page never asks for the microphone, reads files or uploads audio. ## Speaker polarity FAQ ### How do I test speaker polarity? Sit centered at low volume and compare the same noise played in phase and with one side inverted. With correct wiring, the in-phase version sounds centered and fuller. To find which wire is which, touch a battery briefly to a disconnected cable end: the woofer moves forward when battery plus is on the speaker's plus. ### How can I tell if my speakers are out of phase? Reversed speakers sound thin in the bass, with a wide, hollow center that is hard to place. In the A/B above, the in-phase version should be the fuller one. If it is the hollow one, swap plus and minus at one speaker only. ### Can I check speaker polarity with a battery? Yes, on passive speakers. Disconnect the cable at the amplifier, touch the battery to the cable end briefly with plus to plus and watch the woofer: forward means the leads are correct, backward means they are reversed. Leave tweeters and powered speakers out of it. ### Can a multimeter check speaker polarity? Not from music playing through a speaker. It can identify the conductors of a disconnected cable: put a battery on the far end, set the meter to DC volts at the near end, and a minus sign means the red probe is on the negative conductor. ### Is there an app that can test the polarity of my speakers? Yes. Polarity apps and handheld testers read a pulse with a microphone, and this page can play that pulse to one speaker at a time. Compare matching drivers with the same pulse, because a tweeter can read opposite its woofer by design. ### Why does my polarity tester show a tweeter as reversed? Crossovers shift phase, and many designs connect the tweeter or midrange in reverse polarity on purpose. Compare it with the same driver in the other speaker; if the two match, the wiring is fine. ### Does speaker polarity matter for a subwoofer? Yes, but you set it by ear rather than by the label. Play a tone at the crossover frequency, often 80 Hz, try each polarity or phase setting from your seat and keep the loudest. That can be 180 degrees. ### Does speaker polarity matter? For a pair, yes: one reversed speaker costs bass and blurs the stereo image. On its own, a single speaker's direction has no audible effect according to audiocheck's polarity test page. What matters is that speakers playing together match. ### Speaker Test: Check Output, Left/Right, Rattle & Polarity URL: https://soundforgepro.com/speaker-test/ Last updated: 2026-10-10T14:06:34.000Z Turn your volume down, press **Play check tone** and work through the five steps: output, channels, range, rattle and polarity. Each step tells you what a pass sounds like and what to check if it fails, so in a few minutes you know whether your speakers play, play on the correct side, play cleanly from low to high and are wired the same way round. For a deeper check of left and right on their own, the [left and right speaker test](https://soundforgepro.com/left-right-speaker-test/) has a dedicated workflow. Browser tool · no upload ## Run a five-step speaker test Tones and noise are made on this device. The page does not request a microphone, read a file or upload audio. !**Lower system volume before Play.** Tool level starts at 5%, caps at 25% and is not dB SPL. Stop at any crackle, buzz or discomfort; never turn up a tone you cannot hear. **1**Output **2**Channels **3**Range **4**Rattle **5**Polarity Step 1 of 5 · Output **440**Hz SineBoth speakers · 2 s Playback**Stopped** Press Play to start this step. Play check toneStop BackNext: Channels **Output.** Play a 2-second 440 Hz tone on both speakers. **Pass:** a soft, steady tone from the speakers you mean to test. **No sound:** check the output device in your sound settings, mute, the speakers' own power and volume knob, and unplug headphones. The full checklist sits below the tool. **Channels.** Short bursts of noise on one side at a time. Play bursts on LeftBothRightL then R **Pass:** Left comes only from the left speaker, Right only from the right, Both sits between them. **Swapped or one side silent:** fix the wiring or balance before going on; the channel guide below covers each case. **Range.** Six short tones from 60 Hz to 10 kHz. Play all, or tap one to repeat it. Tone 60 Hz125 Hz250 Hz1 kHz4 kHz10 kHz Output LeftBothRight **Pass:** every tone is clean. Low tones getting quieter on small speakers is normal. **Fail:** crackle, buzz, or a high tone that is clear on one side and dull or missing on the other. **Rattle sweep.** A slow glide upward. Press Stop the moment anything buzzes; the readout keeps that frequency. Sweep Low · 20–500 Hz · 30 sFull · 20 Hz–20 kHz · 40 s Output LeftBothRight Hold the stop frequency for 5 s **Pass:** the tone rises smoothly with no buzz, rattle or crackle. **Buzz at one frequency:** hold it, then press on cabinet panels, the grille and nearby objects until the noise stops. **Polarity.** Pink noise on both speakers. Switch between the two versions while it plays. Version In phaseOne side invertedAlternate 3 s **Pass:** In phase sounds centered and fuller in the bass; One side inverted sounds wide, hollow and hard to place. **Reversed:** if In phase is the hollow one, + and − are swapped on one speaker. If inverted goes almost silent, the device is playing in mono. Tool level 5% Ready. Start with step 1\. Space plays or stops when focus is outside the controls. Sine tones and pink noise, 20 Hz–20 kHz. Not calibrated output, an SPL reading or a hearing test. Press Escape to stop. ## How to run a speaker test 1. **Lower the system volume first.** The tool level starts at 5% and stops at 25%, but it cannot see your amplifier, the speakers' own volume knob or your phone's buttons. Start low and raise it only until the check tone is comfortable. 2. **Play the check tone.** Step 1 plays 440 Hz on both channels for two seconds. Nearly every speaker reproduces this frequency well, so silence here is a routing or connection problem, not a weak speaker. 3. **Check each channel.** Step 2 plays short bursts of noise on Left, Both or Right, or left first and then right. Noise is easier to place than a pure tone, so you can point to where each burst comes from. 4. **Play the six range tones.** Step 3 runs 60, 125 and 250 Hz, then 1, 4 and 10 kHz. Listen for crackle, buzz or one side sounding duller than the other. Repeat any tone on Left or Right to compare the speakers. 5. **Run the rattle sweep.** Step 4 glides slowly upward. Press Stop as soon as anything buzzes, then use Hold to replay that frequency while you look for the cause. 6. **Compare polarity.** Step 5 plays pink noise in two versions. The in-phase version should sound centered and fuller; the inverted one wide, hollow and hard to place. If it is the other way round, [one speaker is wired backwards](https://soundforgepro.com/speaker-polarity-test/). Space plays or stops the current step when focus is outside the controls, Escape always stops playback, and sound ends when you switch tabs or leave the page. Changing step stops whatever is playing. ## What each result means A speaker test hears the whole chain at once: the device, its sound settings, the cable, the amplifier, the speaker and the room. A failed step tells you where to look first, not which part is broken. | Step | A pass sounds like | If it fails, check | | -------- | ------------------------------------------------------------------------------ | ---------------------------------------------------------------------------------------------------- | | Output | A soft, steady 440 Hz tone from the speakers you meant to test | The selected output device, mute, the speakers' power and volume knob, headphones still plugged in | | Channels | Left only from the left speaker, Right only from the right, Both in the middle | Balance, Mono audio, the cable at the amplifier or interface | | Range | Every tone clean; 60 Hz quieter on small speakers is normal | Crackle on every tone points to a connection; a high tone missing on one side points to that speaker | | Rattle | A smooth rise with no buzz, rattle or crackle | Loose panels, grilles, screws and objects nearby; then the driver itself | | Polarity | In phase sounds centered and fuller in the bass | Plus and minus swapped on one passive speaker, or a miswired balanced cable on an active one | ![Five speaker test steps with what a pass sounds like and what to check when each fails: output, channels, range, rattle and polarity](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/10/speaker-test-steps.webp) One symptom per step: what to listen for, and where to look first when a step fails. ## No sound from your speakers? Start with the route. Most silent speakers are fine; the sound is simply going somewhere else. Work through these in order and press Play check tone after each change. - **The output device.** Computers often have several outputs: built-in speakers, a monitor, an interface, a Bluetooth headset that connected on its own. Pick the speakers you want to test before anything else. - **Volume and mute everywhere.** Check the system volume, the app or browser tab, and the speakers themselves. Microsoft's guide to [fixing sound problems in Windows](https://support.microsoft.com/en-us/windows/hardware/audio/fix-sound-or-audio-problems-in-windows) puts it simply: "Some speakers and apps have their own volume controls. Be sure to check them all." - **Power and cables.** Powered speakers need their own power and often have a switch at the back. Reseat each cable; on a computer, Microsoft notes that some systems use a green jack for output and a pink one for the microphone, while others label them. For USB speakers, try a different USB port. - **Headphones.** A plugged-in headset can take over the output. Unplug it, or switch Bluetooth off for a moment, and play the tone again. ### Speaker test on Windows Select the Speakers icon on the taskbar, then the arrow to the right of the volume slider; its tooltip reads "Select a sound output". Choose your speakers from the list. If they are missing or silent, Microsoft's guide adds three checks: open the device's properties and make sure "Use this device (enable)" is selected, set **Audio enhancements** to Off under Advanced settings, and run the audio troubleshooter under **Troubleshoot > Other troubleshooters**. If one side is quiet or both sides play the same thing, open Settings > System > Sound and look at two controls covered in Microsoft's article on [audio playing in only one channel](https://support.microsoft.com/en-us/windows/hardware/bluetooth/fix-bluetooth-audio-only-playing-in-one-channel). Under the device's Volume settings, both Left and Right should be at the same level, "typically 100". And **Mono audio** should be off, because it "converts stereo sound into a single channel". With Mono audio on, the channel and polarity steps cannot work. ### Speaker test on Mac Open System Settings > Sound > Output and select your speakers. Apple's page on [Mac speakers with no sound](https://support.apple.com/guide/mac-help/if-you-cant-hear-sound-from-your-speakers-mchlp1439/mac) lists the details: the output volume slider is not all the way to the left and Mute is not selected. External speakers need their own power and volume up. USB speakers should appear under USB in System Information; if they don't, unplug them and plug them in again. With digital output, Apple says the computer's volume controls can't change the level; adjust the volume on your receiver instead. Two more settings matter for this test. Apple's [sound output settings guide](https://support.apple.com/guide/mac-help/change-the-sound-output-settings-mchlp2256/mac) describes the **Balance** slider, which should be centered, and notes that an app's volume "can only be equal to or less than the computer's output volume". For speakers on an external audio interface, Audio MIDI Setup has its own check. Apple's guide to [configuring stereo speakers in Audio MIDI Setup](https://support.apple.com/guide/audio-midi-setup/set-external-speakers-stereo-surround-sound-ams1005/mac) says to select the output device, click Configure Speakers, then "Click the Left or Right speaker icon to test the speaker". The same page notes you may need to configure them manually "if the left and right speakers are connected backwards". ## One speaker silent, or left and right swapped Play Left, then Right, in step 2\. If one burst is silent, swap the two speakers' cables at the amplifier or interface. If the silence moves to the other speaker, the problem is upstream: the output, the cable or a setting. If it stays with the same speaker, look at that speaker, its power or its own input. If left and right are reversed, swap the cables at one end, or fix the mapping in Audio MIDI Setup on a Mac. A small difference in level between sides is common when you sit off-center or one speaker is near a wall. The [speaker placement calculator](https://soundforgepro.com/speaker-placement-calculator/) helps you set up an equal triangle before you blame the speakers. For named Left, Center and Right checks and a full list of channel fixes, use the [dedicated left/right speaker check](https://soundforgepro.com/left-right-speaker-test/). ## Speaker polarity: what out of phase sounds like Polarity is a wiring mistake that leaves both speakers playing on the correct sides and is still wrong. In his [rundown of common studio problems](https://www.soundonsound.com/techniques/studio-sos-common-studio-problems) for Sound On Sound, Paul White describes the result: one woofer moves in while the other moves out, causing "a loss of bass, a lack of focus in the sound-stage" and a feeling "like having your ears sucked out by a sink plunger!" He gives the usual causes as crossed positive and negative cables on passive speakers, or an incorrectly wired balanced cable on active ones. The polarity step plays pink noise because a steady sine tone makes the difference hard to hear. Hugh Robjohns calls checking polarity with a constant tone "surprisingly difficult" in his Sound On Sound guide to [building a test CD](https://www.soundonsound.com/techniques/creating-test-cd), and the same guide describes band-pass pink noise test tracks with polarity reversals in one channel. Matt Houghton suggests the same kind of listening in a [Q&A on polarity inverters](https://www.soundonsound.com/sound-advice/q-whats-point-polarity-inverter-monitor-controller): check "whether the stereo image becomes more or less focused when flipped". - **Normal wiring:** In phase sounds like a solid band of noise between the speakers, with more weight low down. One side inverted sounds spread out, thinner and oddly pressurized. - **One speaker reversed:** the two versions trade places. The fix is to swap plus and minus at one speaker. On passive speakers, check that red goes to red and black to black at both ends of both cables. On active speakers, check the balanced cables. - **Almost silent when inverted:** your device is playing in mono, either because it has a single speaker or because Mono audio is on. Summing the two channels cancels a signal that is inverted on one side, which is why Robjohns notes that summing to mono will "reveal a polarity error in the system". Turn Mono audio off, or accept that a one-speaker device has no polarity to check. Use Alternate 3 s if switching by hand is too fast to judge. The polarity step checks your speakers' wiring. To check whether a recording has an inverted channel, load it into the [phase correlation meter](https://soundforgepro.com/phase-correlation-meter/). ## Find a rattle or buzz A buzz that appears at one point in the sweep is usually something vibrating in sympathy rather than the speaker failing. Celestion's [Dr Decibel speaker FAQ](https://celestion.com/dr-decibel/) makes the point for guitar cabinets: "buzzing is often caused by a cabinet panel or part of the amp that's come loose". Check that screws are tight and that no wires are resting on the back of the speaker cone. The same advice carries over to desk and shelf setups. Stop the sweep at the buzz, press Hold and work outward from the speaker while it plays. Press lightly on the cabinet, the grille, the stand, the desk and anything sitting near the speaker. When the buzz stops under your hand, you have found it. If nothing nearby changes it, compare the same frequency on Left and Right in step 3\. A buzz on one speaker only, at every level, points to the driver: Celestion notes that "small tears often cause buzzing". ## Test a passive speaker with a multimeter If a passive speaker stays silent on a channel you have proved works, a multimeter can tell you whether there is an unbroken path through it. This applies to passive speakers and bare drivers only. Powered speakers have an amplifier inside, so leave them to the manufacturer's service guidance. 1. **Disconnect it.** Celestion's first step is to disconnect the speaker from the amplifier by removing the wires from its terminals. 2. **Move the cone gently, if you can reach it.** Celestion says to move it in and out by hand without forcing it; there should be no grating or scraping, and it should spring back. Skip this if a grille or dust cap is in the way. 3. **Measure resistance across the terminals.** Celestion's rule of thumb for a single driver: "An 8ohm speaker should measure somewhere between 5 and 8ohm and a 16ohm around double that." A reading far outside that range suggests a bad joint, and an open circuit means no path at all. The number on the meter will not match the rating, and that is expected. Rated impedance is not a DC reading. Dynaudio's Otto Jørgensen explains in an [expert note on impedance](https://dynaudio.com/magazine/2023/july/impedance-ask-the-expert) that "impedance varies with frequency", and that under IEC 60268-5 an 8-ohm speaker's impedance should never fall below 6.4 ohms within its rated range. Pat Brown at ProSoundTraining makes the same point in his piece on [nominal versus minimum impedance](https://www.prosoundtraining.com/2010/03/17/which-impedance-nominal-minimum-maximum-average/): impedance is "both complex and frequency-dependent". On a complete speaker with a built-in crossover, the reading at the input terminals includes the crossover parts. So don't judge it against the single-driver rule; compare it with the other speaker of the pair. Two matching readings and one open circuit is a clear answer. If the cables themselves are long or thin, check them with the [speaker wire size calculator](https://soundforgepro.com/speaker-wire-size-calculator/). ## Judging speaker sound quality Test tones confirm that speakers work. They don't tell you whether you will enjoy listening to them; for that you need music, and a fair comparison. Sean Olive describes a 1994 Harman study of [sighted versus blind listening tests](https://seanolive.blogspot.com/2009/04/dishonesty-of-sighted-audio-product.html) in which 40 Harman employees rated four speakers. When listeners could see the speakers, preference rose "for the larger, more expensive loudspeakers". The blind tests also showed clear positional effects, so where a speaker stands changes how it is judged. Level matters as much. In Olive's write-up on [evaluating iPod music stations](https://seanolive.blogspot.com/2010/04/evaluating-sound-quality-of-ipod-music.html), the products were "level-matched within 0.1 dB at the listening position by playing pink noise through each unit". You won't match that by ear. But you can get closer by setting each speaker so the [pink noise generator](https://soundforgepro.com/pink-noise-generator/) sounds equally loud from your seat, then switching quickly between them with the same few tracks. I'd use songs you know well, played from a source you trust. A demo video recorded through someone else's speakers mostly tells you about your own speakers and that recording, not the ones on screen. ## Subwoofer polarity The polarity step compares your two main speakers. A subwoofer has its own polarity or phase control, and its job is different. In Sound On Sound's [audio test files guide](https://www.soundonsound.com/techniques/sos-audio-test-files), Robjohns describes setting it with an 85 Hz tone, adjusted "to make the tone sound as loud as possible at the listening position". This page sends stereo, not a separate LFE channel. If your system passes bass from the main channels to the sub, play 85 Hz on both channels in the [online tone generator](https://soundforgepro.com/online-tone-generator/) and try the sub's polarity or phase settings from your seat, keeping the one where the tone sounds loudest. ## Phone speakers and water On a phone, this page plays through the phone's current media output, so the first three steps work as a quick speaker check. Water is a different matter, and here the manufacturer's guidance beats any test tone. Apple Watch has a built-in water-clearing feature: Apple's article on [Water Lock and ejecting water from Apple Watch](https://support.apple.com/en-us/108352) says that when you press and hold the Digital Crown to unlock it, "a series of tones plays to clear any water that remains in the speaker". On watchOS 8 or earlier, you rotate the crown instead. For iPhone, Apple's [splash and water resistance guide](https://support.apple.com/en-us/108039) describes drying, not tones. Tap the iPhone gently against your hand with the connector facing down, then leave it in a dry area with some airflow. To check the speaker, place it speaker side down on a lint-free cloth and see if water drips out. Apple notes that water in the port "might degrade speaker or microphone performance until it completely evaporates". So a muffled iPhone speaker after a splash is worth a few hours of drying before you test it again. ## Keep speaker tests quiet Test signals are steady, with none of the pauses and dynamics of music, so start quiet and stay brief. The tool level starts at 5% and caps at 25%, each step stops on its own (two seconds for the check tone, about 11 seconds for the range tones, 30 or 40 seconds for a sweep, 30 seconds for polarity), and Escape stops everything. High frequencies need the most care. Robjohns warns in the test files guide that a 24 kHz tone "could damage speaker tweeters without anyone hearing it". The full sweep here stops at 20 kHz and the range tones top out at 10 kHz, but the principle holds: if a high tone goes silent, turn it off rather than up. Stop at any crackle, buzz or discomfort. ## What this speaker test cannot tell you - It does not measure sound pressure level, frequency response or distortion. There is no microphone and no calibration. - It hears your speakers, room and hearing together; it cannot separate them. - It is not a hearing test. If you cannot hear 10 kHz on either side, that is not proof your tweeters are dead. - Processing in your operating system, browser or speaker, such as enhancements, spatial audio, EQ or Bluetooth codecs, changes what you hear. - It plays stereo only. It does not test center, surround or LFE channels. ## How the page makes the sounds Tones come from a Web Audio [OscillatorNode](https://developer.mozilla.org/en-US/docs/Web/API/OscillatorNode) set to a sine wave, which MDN describes as "in effect, a constant tone". Each tone fades in and out to avoid clicks. The sweep uses an exponential frequency ramp, which MDN's [exponential ramp reference](https://developer.mozilla.org/en-US/docs/Web/API/AudioParam/exponentialRampToValueAtTime) recommends for frequency changes "because of the way the human ear works". The noise is pink: white noise filtered so each octave carries equal energy, which Sound On Sound calls "a very natural-sounding form of noise". For the inverted version, the page writes the same noise into the right channel with every sample's sign flipped. Sound only starts after you press a button, as the [browser autoplay rules](https://developer.mozilla.org/en-US/docs/Web/Media/Guides/Autoplay) require, and nothing is recorded or uploaded. ## Speaker test FAQ ### How do I test my speakers? Lower the volume, play a short mid-frequency tone to confirm sound comes out, then check left and right separately, listen to a few tones from low to high, sweep for rattles and compare polarity. The tool above runs those five steps in order. ### Why is there no sound from my speakers? Usually the output is set to another device, something is muted, or the speakers are off or turned down. Select the speakers as the output in Windows or macOS, check every volume control including the speakers' own, unplug headphones and reseat the cables. ### How do I know if my speakers are out of phase? Play the polarity step. With correct wiring, In phase sounds centered and fuller and One side inverted sounds wide and hollow. If In phase is the hollow one, swap plus and minus at one speaker or check the balanced cable on an active speaker. ### How do I test a speaker with a multimeter? Disconnect the passive speaker from the amplifier and measure resistance across its terminals. Celestion's rule of thumb for an 8-ohm driver is a reading between 5 and 8 ohms. An open circuit means no path through the speaker. ### Can a sound remove water from my phone speaker? Apple Watch plays its own water-clearing tones when you turn off Water Lock. For iPhone, Apple's guidance is to tap out excess liquid with the connector facing down and let the phone dry with some airflow; water in the port can muffle the speaker until it evaporates. ### Is a speaker test safe? Yes, if you keep it quiet and brief. Lower the system volume before you press Play, stop at any crackle or discomfort, and never turn up a high tone you cannot hear. ### Does the speaker test use my microphone? No. The page generates tones and noise on your device and does not request microphone access, read files or upload audio. ### Are test tones or music better for testing speakers? Tones are better for finding faults: a silent channel, a rattle or reversed polarity. Music is better for judging sound quality, as long as you compare speakers at matched levels with tracks you know well. ### Bass Test: 20–200 Hz Tones for Speakers & Subwoofers URL: https://soundforgepro.com/bass-test/ Last updated: 2026-10-06T07:15:57.000Z Start at 100 Hz, keep the level low and press **Play lower step** until the note fades, buzzes or stops sounding lower. The last clean step is where your speakers, subwoofer or headphones stop giving you usable bass at that seat and that volume. For a quick left/right channel check, the [left and right speaker test](https://soundforgepro.com/left-right-speaker-test/) is faster; for broadband room listening, use the [pink noise generator](https://soundforgepro.com/pink-noise-generator/). Browser tool · no upload ## Play bass test tones Sine tones are made on this device. The page does not request a microphone, read a file or upload audio. !**Lower system volume before Play.** Tool level starts at 5%, caps at 25% and is not dB SPL. Stop at any buzz, rattle, knocking or discomfort; never turn up a tone you cannot hear. Test tone · sine **100**Hz Bass2× 200 · 3× 300 Hz Playback**Stopped** Pick a step, then press Play tone. Play toneStop Play lower stepPlay higher step Test steps in hertz 202531.5405063 80100125160200 Tone length 2 s5 sHold Output LeftBothRight Tool level 5% Exact frequencyAny value from 20 to 200 Hz Frequency Hz 20 Hz63 Hz200 Hz Slow sweepGlide between two frequencies to find rattles Start Hz End Hz Seconds Run sweep Ready. Start at 100 Hz, then use Play lower step. Space plays or stops when focus is outside the controls. Sine only, 20–200 Hz. Not calibrated output, an SPL reading or a hearing test. Press Escape to stop. ## How to run a bass test 1. **Turn the physical volume down first.** The tool level starts at 5% and stops at 25%, but it cannot see your amplifier, your subwoofer gain or your phone's volume buttons. 2. **Play 100 Hz for 5 seconds.** This confirms the sound is going where you expect and gives you a reference note that almost any speaker can reproduce. 3. **Press Play lower step.** The ladder runs 200, 160, 125, 100, 80, 63, 50, 40, 31.5, 25 and 20 Hz, about a third of an octave apart. Each step should be the same smooth hum, only lower. 4. **Note the last clean step.** Stop when the tone disappears, buzzes, rattles, flutters or no longer sounds lower than the step before. Never turn the volume up to chase a tone you cannot hear. 5. **Sweep slowly through any problem area.** Open **Slow sweep**, glide from 80 Hz down to 30 Hz over 30 seconds and press Stop the moment something rattles. The readout keeps the frequency where you stopped. 6. **Repeat with Output set to Left, then Right.** If one side buzzes and the other does not, check that speaker, its position and its connection before blaming the room. Space plays or stops the tone when focus is outside the controls, Escape always stops it, and playback ends when you switch tabs or leave the page. ## Pressed Play but hear nothing? Press Stop, select 100 Hz and set Output to Both. Check which device your computer or phone is sending sound to, and whether Bluetooth headphones grabbed the output. If 100 Hz is silent too, the problem is the route rather than the bass. Confirm it with a 440 Hz tone in the [online tone generator](https://soundforgepro.com/online-tone-generator/). A **Blocked** status means the browser did not start audio. Browsers only let a page start sound in response to a click, tap or key press, as described in MDN's [autoplay guide for media and Web Audio](https://developer.mozilla.org/en-US/docs/Web/Media/Guides/Autoplay), so press Play tone again. If 100 Hz plays but 25 Hz and 20 Hz do not, that is a result, not a fault. ## How to read your bass test result A bass test hears the whole chain at once: the source device, any processing, the amplifier, the speaker, the room, your seat and your ears. The result describes that setup at that position, not the speaker on its own. | What you hear | Most likely cause | What to try next | | ---------------------------------------------------------- | ------------------------------------------------------------------------------------- | ------------------------------------------------------------------------ | | Steps get gradually quieter, then fade out | The speaker's low-frequency roll-off, plus your ears' lower sensitivity to quiet bass | Treat the last clearly audible step as the practical limit at this level | | The pitch stops falling, or the tone turns buzzy | Harmonic distortion: the speaker adds tones at 2× and 3× the step | Count the previous step and lower the level to confirm | | A buzz or rattle at one step only | Something vibrating in sympathy: a loose object, panel, grille or cabinet part | Use Slow sweep to find the frequency, then touch or move nearby objects | | Boom or silence at one step that changes when you move | A room resonance (room mode) at your listening position | Hold the step and move your head or chair forwards or backwards | | Thin bass with speakers well out from the back wall | The wall reflection canceling the speaker's own bass | Try a different distance to the wall rather than more EQ | | A dip around the subwoofer crossover | The subwoofer and main speakers partly canceling each other | Check the subwoofer's phase setting while a crossover step plays | | Earbud or headphone bass comes and goes as you adjust them | A broken seal around or inside the ear | Reseat them or try a different ear-tip size | ![Five bass test results matched to causes: gradual fade, harmonic distortion, rattle, room mode and crossover dip](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/10/bass-test-results.webp) Match what you hear to the likely cause before you change EQ, placement or settings. ### Lowest clean step or harmonic distortion? This is the trap in most bass tests. Sound On Sound's guide to [reading speaker specifications](https://www.soundonsound.com/sound-advice/understanding-speaker-specifications?page=2) explains that harmonic distortion changes with level and gets worse as a speaker approaches its limits, which "usually happens at low frequencies first". That distortion adds tones at two and three times the test frequency, so a small speaker playing 40 Hz can put out 80 Hz and 120 Hz instead. You hear something, and it feels like you are hearing 40 Hz. The AudioCheck [low-frequency sweep](https://www.audiocheck.net/audiotests%5Ffrequencychecklow.php) makes the same warning about anyone who seems to hear tones below 20 Hz. Two checks keep the result honest. First, each step should sound lower in pitch than the one above it; if 31.5 Hz sounds like the same note as 40 Hz, or higher, you are hearing overtones. Second, lower the tool level a little: distortion changes strongly with level, so a buzz that vanishes at a lower level was coming from the speaker being pushed. Record the last step that passes both checks. ### Why bass gets quieter as you step down Part of the fade is your hearing. Equal-loudness curves, summarized on HyperPhysics' [equal-loudness curves page](http://hyperphysics.phy-astr.gsu.edu/hbase/Sound/eqloud.html) and standardized in ISO 226 ([revised in 2023](https://doi.org/10.1250/ast.e23.66)), show that the ear discriminates against low frequencies at soft levels and responds more evenly when sound is loud. A perfectly flat speaker would still make 31.5 Hz sound weaker than 100 Hz at a quiet setting. So a gentle fade is normal. What deserves attention is a sudden drop between neighboring steps, a change in character, or a difference between the left and right speakers. Once a speaker passes its low-frequency limit, its output falls away quickly: Sound On Sound gives the roll-off as 12 dB per octave for a sealed cabinet and 24 dB per octave for a vented one, roughly 4 or 8 dB per step on this ladder once the slope is under way. ### Room modes: why the result changes when you move Low notes have long wavelengths, and a room reinforces some of them and cancels others. Genelec's [monitor setup guide](https://assets.ctfassets.net/4zjnzn055a4v/3oerOc4piQKHTbc2tm2sK7/fa3f672b49d6fba7bc90fabb140e3c0d/Genelec%5FMonitor%5FSetup%5FGuide.pdf) notes that if you sit in the null of a room resonance, that frequency drops a lot in level "and audio may appear to be missing". Hold the step that vanished, then move forwards or backwards; if it comes back, the speaker was fine and the seat was the problem. The same guide suggests sitting at least 1 meter (about 3 ft) from the walls and avoiding the exact center of the room. The [speaker placement calculator](https://soundforgepro.com/speaker-placement-calculator/) helps you plan the triangle once you have a better spot. ### Wall distance: boom or missing bass Walls change bass in two opposite ways. According to Genelec, a speaker placed against a wall gets about 6 dB more bass level, a corner raises that to 12 dB, and three close surfaces can add up to 18 dB. Sound On Sound notes that most studio monitors offer simple low-frequency EQ for exactly this reason, so you can match the bass to the placement. Pull the speaker away from the back wall and a different problem appears: the reflection from the wall arrives out of phase and cancels part of the bass. Genelec's table puts the lowest canceling frequency at 86 Hz for a speaker 1 meter from the wall and 429 Hz at 0.2 meters, and says EQ does not help, because the reflection grows along with the speaker's output. How deep the dip is depends on how much bass the wall reflects. Genelec's answer is to keep the distance from the speaker front to the wall behind it under 0.6 meters (2 ft), with at least 50 mm (2 in) of clearance for a rear port, and to trim the extra boost with the speaker's low-frequency control. A desk or console in front of desktop monitors can also raise the 160 Hz and 200 Hz steps. ## Subwoofer test Find your crossover frequency first: it is where the subwoofer takes over from the main speakers. Genelec subwoofers cross over at 85 Hz by default, with 50 to 120 Hz selectable on its SAM models, and Sound On Sound describes bass management as typically rolling the main speakers off at 80 to 100 Hz. What counts is the setting on your own receiver or subwoofer. 1. **Play the steps around the crossover.** For an 80 Hz crossover that means 63, 80 and 100 Hz. They should sound about as strong as each other. 2. **If the crossover step is weaker, check phase.** Set Length to Hold, play that step and have someone switch the subwoofer's phase between 0 and 180 degrees while you stay in your seat. Keep whichever setting sounds fuller. Genelec describes subwoofer phase as being set to maintain the level through the crossover range. 3. **Step below the crossover.** From here down, you are hearing only the subwoofer. Its last clean step is the useful low limit of your system at that seat. Placement matters as much as settings. Genelec notes that a corner maximizes subwoofer output, but the flattest response is usually somewhere else: a single subwoofer usually goes along the front wall, slightly off-center, and two subwoofers can be flatter still. Sound On Sound also warns that unless a subwoofer is very large and not working hard, its distortion "will be much higher than from the loudspeaker", so the harmonic check above matters even more on the lowest steps. This page outputs a stereo signal, not a dedicated LFE channel. If your subwoofer stays silent at 40 Hz, check that your receiver or audio interface sends bass from the main channels to it (the speaker-size or bass-management setting), and check the subwoofer's own low-pass and level controls. ## Headphones and earbuds Headphone bass depends on the seal. AudioCheck explains that sealing your ear canal creates a volume that acts as a pressure chamber. If the low steps come and go when you move your head, reseat the earbuds, try another tip size, or check for hair or glasses arms breaking the seal of over-ear pads. Switch off bass boost, preset EQ and spatial audio before you compare results. For channel, balance and phase checks on headphones, use the [online headphone test](https://soundforgepro.com/headphone-test/). ## Phones, laptops, speakers and subwoofers: what to expect I'd avoid any chart that promises a cut-off for a whole category of devices. Small devices such as phones, laptop speakers and compact Bluetooth speakers usually run out of bass several steps earlier than full-size speakers or a subwoofer, and that is not a fault. For your own model, look up the maker's stated low-frequency figure and check that it comes with a tolerance. [Sound On Sound's guide](https://www.soundonsound.com/sound-advice/understanding-speaker-specifications) shows why a bare range tells you nothing: "40Hz-25kHz" means little until you know whether that point is 3, 6 or 10 dB down. Even then, your room and seat can move the result by more than the spec sheet suggests. ## Bass test songs or test tones? Use both, for different jobs. Tones isolate one frequency at a time, which is what you need to find the limit, a rattle or a room null. Music shows timing, texture and balance, which tones cannot. For songs, pick tracks you already know well from a system you trust, play them at a normal level, and skip "bass boosted" uploads: they are processed to exaggerate low end and can push small speakers into distortion. If the question is really about balance rather than extension, [bass vs treble](https://soundforgepro.com/bass-vs-treble/) explains what each band does. ## Keep bass tests quiet and short Low tones invite you to turn up, because the ear hears quiet bass less well than the midrange. The tool starts at 5%, caps at 25% and stops by itself after 2 or 5 seconds unless you choose Hold. A browser percentage is not a sound pressure level: the real loudness depends on your amplifier, speakers and room. Stop at any buzz, rattle, knocking sound or discomfort, and use Hold only while you are adjusting something. ## What this bass test cannot tell you - It does not measure sound pressure level, frequency response or distortion. There is no microphone and no calibration. - It cannot separate the speaker from the room, the seat and your hearing; it only reports what reaches you. - It is not a hearing test. - Processing in your operating system or player app, such as bass boost, loudness, EQ or spatial audio, changes the result. - It plays a stereo signal only. It does not send a dedicated LFE or surround channel. To see which low frequencies are inside a recording rather than in your playback system, open the file in the [audio spectrum analyzer](https://soundforgepro.com/audio-spectrum-analyzer/). ## How the page makes the tones The tones come from a Web Audio [OscillatorNode](https://developer.mozilla.org/en-US/docs/Web/API/OscillatorNode) set to a sine wave. A gain stage fades each tone in and out to avoid clicks, and a [ChannelMergerNode](https://developer.mozilla.org/en-US/docs/Web/API/ChannelMergerNode) sends it to the left channel, the right channel or both. The sweep uses an exponential frequency ramp, which MDN recommends for frequency changes "because of the way the human ear works". The tool offers sine only, because other waveforms carry harmonics of their own that would hide the distortion you are listening for. Nothing is recorded or uploaded. ## Bass test FAQ ### What is a bass test? A bass test plays low-frequency tones, usually from about 200 Hz down to 20 Hz, so you can hear where your speakers, subwoofer or headphones fade, distort or rattle. It checks the whole playback chain at your listening position. ### What frequency should I start a bass test at? Start at 100 Hz, which nearly every speaker can play, then step down. On the [audio frequency chart](https://soundforgepro.com/audio-frequency-chart/), bass covers roughly 60 to 250 Hz and sub-bass 20 to 60 Hz; the sub-bass steps are where speakers usually reach their limits first. ### Why can I hear a tone lower than my speaker should play? Usually because of harmonic distortion: the speaker adds tones at two and three times the test frequency, and you hear those instead. If a step does not sound lower than the one above it, or its buzz disappears when you lower the level, count the previous step as your limit. ### Is a bass test safe? Keep it quiet and brief. The tool starts at 5% and caps at 25%, but it cannot see your amplifier or volume buttons, so set those low first. Stop at any buzz, knocking sound or discomfort, and never turn up a tone you cannot hear. ### Does the bass test use my microphone? No. The page generates the tones on your device and does not request microphone access, read files or upload audio. ### What is a good bass test song? A track you already know well from a system you trust, played at a normal level. Skip "bass boosted" uploads; they exaggerate the low end and make small speakers distort. ### Will my subwoofer play these tones? Only if your receiver, interface or subwoofer routes bass from the main left and right channels to it, usually through bass management or the subwoofer's own crossover. The page sends stereo, not an LFE channel. ### Open-Back vs Closed-Back Headphones URL: https://soundforgepro.com/open-back-vs-closed-back-headphones/ Last updated: 2026-10-10T13:55:55.000Z **Choose closed-back headphones when you record near a microphone, work around other people or need to keep outside noise down. Choose open-back headphones for listening and editing in a quiet room when sound leaking out will not bother anyone. For mixing, the back of the earcup is only a starting point: the response, fit and consistency of the actual headphone matter more than the category name.** - **Recording a vocal or instrument?** Start with closed-back to reduce [cue or click bleed into the microphone](https://soundforgepro.com/reduce-headphone-bleed-vocal-recording/). - **Working in a quiet room without an open mic?** Open-back is worth considering if you prefer its less isolated presentation. - **Sharing a room, commuting or working around noise?** Closed-back is usually the practical choice. ## What open-back and closed-back actually mean The terms describe the outer housing behind the headphone driver. An open-back earcup has an acoustically transparent area, such as a grille or perforations, so sound can pass between the cup and the room. A closed-back earcup uses a solid outer housing to reduce that exchange. [Beyerdynamic's explanation of the two designs](https://support.beyerdynamic.com/hc/en-us/articles/200994502-What-is-the-difference-between-open-and-closed-headphones) makes the important practical point: open cups admit room sound and let playback escape; closed cups are built to limit both. Those labels do not describe the whole headphone. Pads, clamp force, glasses, hair and how the cup sits around your ear all affect the seal. Even a closed model can leak at a high playback level or isolate poorly if it does not fit you. [RTINGS shows that leakage and isolation vary between individual models](https://www.rtings.com/headphones/learn/open-vs-closed-back), including closed models. Treat the construction as a useful expectation, then check the actual pair. In practice the choice comes down to three questions about where you listen, asked in this order. ![Decision chart for choosing headphones: if a microphone is open while you listen, choose closed-back; if other people are nearby or the room is noisy, closed-back; in a quiet room with no open mic either design works, with open-back an option if you prefer it; then check the model for leakage, isolation, fit and impedance](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/09/open-vs-closed-back-decision-v2.webp) Answer the microphone question first: it is the one situation where the wrong back design ends up in the recording itself. ## The differences that change your decision | What matters | Open-back | Closed-back | | ------------------------ | --------------------------------------------------------------------------------------- | -------------------------------------------------------------------------- | | Sound heard by others | More playback can escape into the room. | Usually less leakage, depending on fit and level. | | Room noise you hear | Little passive isolation; you remain aware of the room. | More passive isolation when the pads seal well. | | Near a live microphone | Cue sound may reach the mic. | Usually the safer monitoring choice, but not bleed-proof. | | Quiet, private listening | Often preferred for a less enclosed presentation. | Still viable; the exact model decides sound quality. | | Long sessions | Ventilation may help with heat. | May feel warmer, though pads, weight and clamp matter more to some people. | | Travel and handling | Often an indoor design: exposed grilles, non-folding frames and long cables are common. | More often built to fold or travel, though build still varies by model. | | Laptop or phone output | Check impedance and sensitivity before relying on a weak output. | Often lower impedance and easier to drive without a separate amplifier. | Passive isolation is the physical reduction of outside sound by the earcup and seal. Active noise cancellation is a separate electronic feature found on some headphones. A closed-back label alone does not promise ANC, and ANC does not tell you whether the headphone is suitable for recording or mixing. Passive isolation also affects how loud you listen: the RTINGS explainer linked above notes that it lets you hear music or game audio without cranking the volume, because less outside noise competes with it. The same explainer flags two differences that have nothing to do with sound. Open-back models are usually meant for indoor use, so exposed grilles, lighter materials, non-folding frames and long cables are common; RTINGS adds that the lighter build can make them more fragile and poorly suited to rough handling or travel. Closed-back models often have lower impedance, which makes them easier to drive without a dedicated headphone amplifier. RTINGS names exceptions both ways, including the closed FiiO FT1, built with audiophiles rather than commuters in mind, and the open Sennheiser HD 650, a well-built design that has stood the test of time. Check the build, cable and impedance of the model itself. ## For recording, keep the cue out of the microphone A singer or instrumentalist often hears a click, guide track or previous takes while the microphone remains open. Open-back cups let some of that playback into the room, where the mic can pick it up. Closed-back cups reduce that risk, which is why [Shure recommends closed-back headphones for tracking](https://www.shure.com/en-us/insights/how-to-choose-the-right-headphones-for-your-studio-recording). Neumann likewise positions its [closed-back NDH 20 for monitoring in a tracking room](https://www.neumann.com/en-us/products/headphones/ndh-20). Closed-back does not mean zero bleed. Keep the cue at a workable level, check the pad seal, and consider where the microphone points. If the headphone mix contains a loud click, a short test recording can tell you whether it is audible in the mic signal; the [Sound Forge Pro recording walkthrough](https://soundforgepro.com/how-to-record-audio-in-sound-forge-pro/) covers arming, metering and input monitoring for that kind of test take. That is a check on your recording setup, not a reason to buy a different pair before you know the problem. If you are recording an acoustic source but there is no headphone playback near the open mic, leakage may not matter. The decision depends on the actual monitoring path, not just the word *recording*. Streaming, podcasting and voice chat put the same trade-off in a different room. [Sweetwater's open-back vs closed-back guide](https://www.sweetwater.com/insync/open-back-vs-closed-back-headphones-whats-the-difference/) suggests closed-back when you stream with noisy roommates or need to stay focused, and open-back when you want to hear what is happening around you and keep your own voice at a reasonable level. RTINGS adds the catch for anyone on a live microphone: an open pair leaks sound that the mic can pick up, which is why it points to closed models such as the Sony MDR-7506 for recording, tracking and broadcasting. If you choose closed-back and still want to hear your voice naturally, send a little of the microphone into the headphones; the [voice-over recording guide](https://soundforgepro.com/sound-forge-pro-for-voice-over-recording/) explains how the driver choice affects the delay before you hear that monitored voice. For gaming itself, RTINGS finds both designs workable: an open-back headset's wider sound field can help you place sounds, while competitive players often prefer closed-back models that block distractions around cues such as footsteps. ## For mixing, judge the model rather than the back Open-back designs are often liked for a spacious, less closed-in presentation in a quiet room. [Neumann positions its open-back NDH 30 for editing, mixing and mastering](https://www.neumann.com/en-us/products/headphones/ndh-30). That does not mean an arbitrary open-back headphone has a neutral response or will make better mix decisions. Closed-back models can also be designed for critical work: [Neumann explicitly includes mixing among the NDH 20's uses](https://www.neumann.com/en-us/products/headphones/ndh-20). The two models illustrate the limit of a category rule. A headphone's tuning, distortion, pad condition, seal and your working environment affect what you hear. The enclosure can influence presentation, but it is not an accuracy certificate. If you mix in a quiet room, an open pair can be a sensible option. If the room is noisy or someone else is nearby, isolation may be more valuable than a wider-feeling presentation. In either case, keep a few familiar references and check important decisions on another playback system when possible. Headphones are one listening view, not a guarantee that a mix will translate everywhere. ## If you can buy only one pair Choose for the constraint you cannot work around. If you record vocals, track instruments with a click, travel or share a room, I would start with a well-fitting closed-back pair. It handles those settings and can still be used for editing and mixing if the particular model gives you a response you can learn. A quiet-room listener who never tracks with an open mic can reasonably choose open-back instead. If you later use two pairs, give each a job: closed-back for tracking and noisy settings, open-back for quiet-room listening if you prefer its presentation. That is a workflow choice, not a rule that every studio needs two pairs. A producer choosing specific headphones for Ableton Live can use the [Ableton Live headphone guide](https://abletonlive.net/best-headphones-for-ableton-live/) for model and connection decisions; this comparison is about construction across applications. ## What about comfort, bass and soundstage? Open cups can allow more airflow, so some listeners find them cooler over a long session. Closed cups can feel warmer, but the pad material, weight and clamp can outweigh the housing difference. RTINGS treats these comfort differences as general tendencies, not a promise about every pair. The useful comfort check is the actual fit on your head for the kind of session you do. Open-back is often described as more spacious, while closed-back can feel more intimate. Those are common listening impressions, not promises about every model. Bass is even less safe to predict from the enclosure alone: a poor seal can reduce low frequencies on a closed pair, and a well-designed open pair can have controlled bass. If tonal accuracy matters, compare measurements and listening evidence for the model you are considering instead of assuming one construction always has more or better bass. ## Does semi-open solve both problems? Not automatically. Semi-open is a loose category for designs between fully open and fully closed. [Beyerdynamic notes that its semi-open models behave more like open models](https://support.beyerdynamic.com/hc/en-us/articles/200994502-What-is-the-difference-between-open-and-closed-headphones). Another manufacturer's semi-open model may behave differently. Check its leakage and isolation rather than assuming it splits the difference exactly in half. ## Three checks before you decide 1. **Name the room and task.** Is a mic open? Are other people close enough to hear your playback? Is outside noise likely to mask quiet details? 2. **Check the specific model.** Look for independent leakage, isolation and response information. Note the pad material and whether a good seal is likely with glasses or your usual fit. 3. **Keep the next task separate.** Construction tells you how a pair interacts with the room. Once you own it, our [headphone test](https://soundforgepro.com/headphone-test/) can help check channels, rattles and sweep anomalies; it does not measure the headphone's frequency response. For most readers, the decision is straightforward once the setting is clear: closed-back when privacy, isolation or microphone bleed matters; open-back when the room is quiet and leakage is acceptable. The model still has to earn its place on your head and in your work. ### Ribbon vs Condenser Microphone: Which Fits Your Recording? URL: https://soundforgepro.com/ribbon-vs-condenser-microphone/ Last updated: 2026-10-10T13:56:07.000Z **Choose a condenser if you need a flexible first microphone for vocals, acoustic instruments or a range of sessions. Choose a ribbon when its pickup pattern and frequency response solve a particular recording problem—often a sharp-sounding source, a useful room, or an amplifier you want to capture without an exaggerated top end.** Check the actual microphone, not the category: an active ribbon can require phantom power, a passive ribbon may need more clean gain, and neither design automatically sounds “warm” or “bright.” - **Start with a condenser** if you want a broadly useful mic, higher output for a quiet source, or a cardioid pattern that suits the room. - **Consider a ribbon** if you want its particular response and off-axis behavior, and its pattern, gain and handling needs fit your setup. ## Ribbon vs condenser at a glance | Question | Ribbon | Condenser | | --------------- | -------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------- | | What moves? | A thin conductive ribbon moves in a magnetic field. | A diaphragm moves relative to a backplate; electronics convert the changing capacitance into a usable output. | | Pattern | Usually figure-eight, but not always; check the model's polar plot. | Cardioid, omni, figure-eight and switchable designs are available. | | Power | Passive ribbons need no power; some active ribbons require 48 V phantom power. | Active electronics need power; the source depends on the model. | | Output and gain | A passive model may need substantial clean gain; active models can provide much more output. | Often higher sensitivity; check the actual output and self-noise specifications. | | Handling | Protect the element from strong air blasts and follow the maker's connection advice. | Handling varies by model; wind, plosives and overload still matter. | | Best use | A deliberate choice for a source, pattern and placement. | A practical starting point when one mic must cover several jobs. | A ribbon is a form of *dynamic* microphone in the technical sense: motion in a magnetic field generates its signal. The familiar moving-coil handheld mic uses a coil instead of a ribbon. A condenser uses a different capsule and active electronics. [Shure's recording guide explains these operating principles](https://www.shure.com/damfiles/default/global/documents/publications/en/performance-production/microphone%5Ftechniques%5Ffor%5Frecording%5Fenglish.pdf-bb0469316afdb6118691d2f3f5e3ff01.pdf); the label alone does not tell you what you will hear from a specific model. Our [condenser microphone guide](https://soundforgepro.com/what-is-a-condenser-microphone/) explains that capsule in more detail, while the [dynamic vs condenser comparison](https://soundforgepro.com/dynamic-vs-condenser-microphone/) covers the separate moving-coil choice. ## What changes the sound? “Ribbons are dark; condensers are bright” is a weak buying rule. Many ribbons are chosen because they avoid a pronounced upper-frequency edge on a source that already has plenty of it. But the frequency response varies from one ribbon to another, and condensers range from restrained to strongly voiced. Royer, for example, describes different responses even within [its own ribbon families](https://royerlabs.com/faqs/), and [Sound On Sound's ribbon microphone explainer](https://www.soundonsound.com/sound-advice/do-need-ribbon-microphone) points out that many modern designs have a very extended high-frequency response, citing the RØDE NT-R as flat to about 22 kHz. Distance changes the tone as well. The same explainer notes that proximity effect is even more pronounced in a ribbon: within two or three feet of the source the bass starts to rise, which is part of why ribbons are perceived as warm. Royer's FAQ gives a guitar-cabinet example, noting that a ribbon closer than about 4 inches to the grille cloth will sound bass-heavy. When you compare a ribbon with a condenser, put both at the same distance, or you may be hearing the placement rather than the transducer. Start with what you want to change in the recording. A guitar cabinet that sounds piercing at the intended position may invite a ribbon with a suitable published response. A quiet acoustic instrument recorded at a useful distance may make a condenser's output and noise specifications more attractive. For a lead vocal, neither category is a shortcut: voice, sibilance, distance, room and the mic's individual response decide. Use these as starting points, then compare specific models on the source you record. ## The room can overturn the choice A common figure-eight ribbon hears from the front *and the rear*, with low-sensitivity directions at its sides. In a room with an unpleasant reflection behind the mic, that rear pickup may be a problem. In a good room, it may be exactly what you want. A cardioid condenser can be easier to aim away from unwanted sound, though moving closer and improving the room may matter more than swapping transducers. Those side nulls are the useful part of a figure-eight. Sound On Sound's explainer gives two examples. For a performer who sings while playing acoustic guitar, a figure-eight positioned for the guitar can capture it while picking up hardly any vocal; in practice that means the mouth sits in a side null. Under a low ceiling, an upright ribbon hears the source and whatever is behind it, but not the reflections bouncing off the floor and ceiling. The article also notes that Mid-Side stereo needs a figure-eight for the Sides microphone, a job ribbons suit well. Each pattern has a different place for the sound you want to keep out of the recording. ![Two polar charts side by side. Figure-8 ribbon: equal front and rear lobes, the rear with opposite polarity, and nulls at both sides, so unwanted sound should be aimed at the sides. Cardioid condenser: one front lobe, about 6 dB down at the sides and a null directly behind, so unwanted sound should be aimed behind it. Ideal shapes; real microphones change with frequency](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/10/ribbon-vs-condenser-pickup.webp) Put the sound you do not want where each pattern is least sensitive: at the sides of a figure-eight, behind a cardioid. Do not buy from the icon printed on the box. Read the model's polar chart across frequencies and consider where the unwanted sound comes from. [Shure's ribbon microphone primer](https://www.shure.com/en-US/insights/talkin-ribbon-microphones) describes a ribbon mic as usually bi-directional, and “usually” matters: [AEA's KU5A](https://aearibbonmics.com/audio-products/ku5a/) is an active ribbon with a supercardioid pattern that runs on standard 48 V phantom power. “Ribbon” does not promise a figure-eight pattern. For a connected-mic level and room check, use our [microphone test](https://soundforgepro.com/microphone-test/) after you have selected and set up the hardware. ## Passive, active and phantom power - **Passive ribbon:** no phantom supply for its electronics. Output can be low, especially on quiet or distant sources; inspect sensitivity, recommended preamp input impedance and available clean gain. - **Active ribbon:** built-in electronics raise and buffer the output. Some models require standard 48 V phantom power: [Royer specifies it for the R-122 MKII](https://royerlabs.com/r-122-mkii/). The warning that phantom power *always* destroys ribbons is wrong. So is the promise that every passive or vintage ribbon is safe under every connection condition. [Royer says properly applied phantom power is safe for its ribbons](https://royerlabs.com/faqs/), while miswired cables and live cross-patching can create damaging transients. Check your microphone manual; turn power off before connecting, disconnecting or patching, and use correctly wired cables. Do not apply another manufacturer's advice to an unidentified vintage mic. Condenser power requirements also vary: many XLR studio condensers use phantom power, while other designs use batteries, dedicated supplies or USB. Confirm the exact voltage and connection in the manual before you buy an interface or switch on P48. ## Gain, noise and loud sources When comparing a passive ribbon with a condenser, read sensitivity in the same units and note the source level and distance. Lower output does not mean worse fidelity, but it asks more of the preamp. An active ribbon may narrow or erase that output gap. The [Royer SF-2 documentation](https://royerlabs.com/sf-2-3/) is a useful example of why you cannot apply a passive-ribbon gain rule to every ribbon model. Input impedance is the other half of that question for a passive ribbon. Royer's [preamp considerations for ribbon microphones](https://royerlabs.com/preamp-considerations/) recommend a preamp input impedance of at least four to five times the mic's output impedance, so a 300-ohm ribbon should see 1,200 to 1,500 ohms or more. Too low a load damps the ribbon: Royer says it tends to sound dull, with rolled-off bass and slightly diminished highs, and its output drops, so you add gain and with it noise. The same page recommends at least 60 dB of usable gain, says very quiet sources may need 70 dB or more, and treats active ribbons as the exception, closer in operation to phantom-powered condensers. Sound On Sound's explainer calls the weak-output reputation largely historic, with modern ribbons at least comparable to a moving-coil dynamic, so treat those figures as a check for a passive model and your quietest source rather than a rule for every ribbon. For a quiet passage, compare the condenser's self-noise and the full ribbon-to-preamp chain. For a loud cabinet or brass instrument, check each model's maximum SPL and, separately, whether strong moving air could reach the ribbon. A high SPL rating is not permission to put an unprotected ribbon in an air blast. [Royer's handling guidance](https://royerlabs.com/ribbons-dos-and-donts/) treats wind and connection precautions as practical limits, distinct from level handling. ## Which mic should you try for each job? - **First all-round studio mic:** start with a condenser whose pattern, noise and maximum-SPL figures cover the sources you actually record. - **Electric guitar cabinet:** a ribbon can be a purposeful choice when its response suits the amp; protect it from direct air movement and respect the specific model's limits. A suitable condenser is also viable. Royer's FAQ describes engineers placing an R-121 close to the cabinet for exaggerated bottom end and blending it with an SM57 for that mic's aggressive top; when you blend two mics on one cabinet, check polarity and timing, which the [mono compatibility and phase correlation guide](https://soundforgepro.com/mono-compatibility-phase-correlation/) shows how to read. - **Bright brass or aggressive percussion:** consider a ribbon for its response, then verify the pattern and air-blast exposure. Do not assume every ribbon will tame every source. - **Quiet strings or acoustic guitar:** a condenser is an efficient starting point at moderate distance. An active ribbon may fit if its response and rear pickup serve the music and room. - **Vocals in a reflective room:** solve distance, pattern and reflections first. A figure-eight ribbon may hear an objectionable rear wall; a cardioid condenser is often easier to position. A close moving-coil microphone is a third option when the room or handling constraints call for it. ## Five specifications before spending 1. **Polar pattern and off-axis response:** what enters from the rear and sides at the intended placement? 2. **Sensitivity:** how much output will the source produce, and how much gain is available? 3. **Noise:** what does the active microphone or complete preamp chain contribute on quiet material? 4. **Maximum SPL and air protection:** can the exact model handle the level and the air movement independently? 5. **Power and input load:** does the mic need P48 or another supply, and what preamp impedance does its maker recommend? If you can answer those five questions for two actual models, you have a much better comparison than a ribbon-versus-condenser slogan. I would buy the condenser for flexibility when I cannot name a specific reason to choose the ribbon. I would buy the ribbon when its published response and pickup behavior solve that named problem—and the room, gain and handling conditions support it. Our [budget ribbon microphone comparison](https://soundforgepro.com/best-budget-ribbon-microphones/) then helps narrow the choice to individual models. At the low end of the market, keep Sound On Sound's warning in mind: a ribbon must be very thin and accurately tensioned, and the article says super-cheap models can use foil that is too thick and not properly tensioned, so buy from a reputable maker. ### Microphone Polar Patterns Explained: Cardioid, Omni and More URL: https://soundforgepro.com/microphone-polar-patterns/ Last updated: 2026-10-10T13:56:01.000Z **A microphone polar pattern shows how sensitive the microphone is to sound arriving from different directions. It helps you place the microphone, control room sound and reduce bleed, but it is not a hard boundary around the capsule. Read it as a map of sensitivity, then check the actual microphone's frequency-labeled plot before making a precise placement decision.** - **Most open room sound:** start with omni when the room is worth hearing and the microphone design supports it. - **Front focus:** cardioid is the usual starting point for one source in a less controlled space. - **Front and rear pickup:** figure-eight hears two opposing lobes and rejects the sides. - **Tighter front lobe:** supercardioid or hypercardioid narrows the front, but each leaves a rear lobe. ## What does a microphone polar pattern mean? A polar pattern, also called a pickup pattern, describes sensitivity by arrival angle. [Shure describes directionality as the microphone's sensitivity relative to the direction or angle of arriving sound](https://www.shure.com/en-GB/insights/microphone-basics-transducers-polar-patterns-frequency-response). The pattern tells you which directions receive the strongest response and which directions receive less. A polar plot is usually drawn as a circle around the microphone. The microphone sits at the center, 0 degrees marks the front, 90 degrees marks the side and 180 degrees marks the rear. A plot that reaches farther from the center represents greater sensitivity at that angle. The circles or rings usually show a change in decibels, so read the legend before comparing shapes. [LEWITT's guide uses a 360-degree field and 5 dB rings to explain this reading method](https://www.lewitt-audio.com/blog/polar-patterns). The diagram is a compact summary of a measurement condition. It does not tell you that sound stops outside the outline, that every frequency has the same shape or that a source can move anywhere inside the lobe without a tonal change. ## The three broad pattern families Microphone makers commonly group patterns into omnidirectional, unidirectional and bidirectional families. The familiar cardioid, supercardioid and hypercardioid shapes sit inside the unidirectional group. Figure-eight is another name for bidirectional. | Family | Where it is most sensitive | What to watch | | --------------- | ----------------------------- | -------------------------------------------------------------------------------------------------------------------------------- | | Omnidirectional | Broadly around the microphone | Room sound and unwanted sources remain part of the recording; high-frequency response can become more directional. | | Unidirectional | Primarily from the front | Cardioid-family patterns reduce sound from some angles, but off-axis tone, rear lobes and proximity effect depend on the design. | | Bidirectional | Front and rear lobes | The sides are the main null region; placement behind the microphone still matters. | ## Common microphone polar patterns The chart below draws the five classic shapes on one 5 dB grid, so you can compare how wide each front lobe is, where the rear lobes sit and at which angle each null falls. Real microphones depart from these ideal curves, which is why the sections that follow keep pointing back to the model's own plot. ![Five polar charts on a 5 dB grid comparing omnidirectional, cardioid, supercardioid, hypercardioid and figure-8 pickup, with nulls marked at 180, about 125, about 110 and 90 degrees and rear lobes of inverted polarity shown dashed](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/09/microphone-polar-patterns-compared.webp) The five classic shapes on one scale. Supercardioid, hypercardioid and figure-8 each have a rear lobe of opposite polarity; real microphones depart from these ideal curves as frequency changes. ### Omnidirectional An omnidirectional microphone is designed to respond broadly from all angles. It can sound open and natural in a good room and can suit a wide source where pointing the capsule at one performer would be restrictive. The tradeoff is control: an omni pattern cannot favor one direction over another, so a noisy room, nearby instrument or monitor can enter the recording. Omni does not mean identical response at every frequency. [Neumann notes that pressure transducers can become more directional at high frequencies](https://www.neumann.com/en-us/knowledge-base/glossary/glossary-microphones). Check the model's plot when the upper-midrange or treble balance matters. Pressure-operated omni microphones generally do not show the same proximity effect as gradient microphones, but a multi-pattern microphone in its omni setting still needs to be judged by its own design and documentation. ### Cardioid Cardioid is the standard front-facing pattern. A typical cardioid plot is strongest at 0 degrees and least sensitive at 180 degrees, with a broad front lobe that narrows toward the sides. That makes it a useful starting point for a single voice or instrument when you want less room and background sound than an omni microphone would capture. [Shure's polar pattern basics guide](https://www.shure.com/en-us/insights/microphone-directionality-polar-pattern-basics) estimates that, in many cases, a cardioid reduces ambient noise by about two-thirds compared with its omni counterpart. The rear minimum is a null direction, not a promise of silence. Real microphones vary with frequency, and a source placed slightly off axis can sound different even when its level falls. Keep the unwanted source near the part of the plot with the lowest response, then listen for both level and tone. ### Supercardioid Supercardioid tightens the front pickup compared with cardioid and rejects more from the sides. It also has a small rear lobe, so a source directly behind the microphone is not automatically in a safe zone. A narrow front lobe rewards consistent orientation and can be useful when side spill is the main problem. The same Shure guide gives a typical minimum-sensitivity angle of about 125 degrees for supercardioid, while [DPA's polar pattern guide](https://www.dpamicrophones.com/mic-university/technology/listen-to-your-polar-pattern/) places the supercardioid null at approximately ±135 degrees. That spread is the point: the angle is a family reference, not a universal setting for every microphone or frequency. Shure turns it into stage advice for both tighter patterns: avoid putting a wedge monitor directly behind the microphone and place it to either side at the least sensitive angle instead. Inspect the manufacturer's polar plot before placing a monitor, another instrument or a second voice near that angle. ### Hypercardioid Hypercardioid narrows the front response further and can reject the sides strongly, but its rear lobe is usually more pronounced than the supercardioid rear lobe. Shure gives about 110 degrees as a typical minimum-sensitivity angle for hypercardioid and warns that the rear is more sensitive than with supercardioid. DPA places the hypercardioid null nearer ±115 degrees and adds a detail the pattern name hides: supercardioid, hypercardioid and figure-eight rear lobes all pick up with inverted polarity. If a source in that rear lobe also reaches another open microphone, the two copies arrive with opposite polarity and can partly cancel when the channels are mixed. This is a precision pattern. Small changes in the microphone or source angle can change the balance, and placing an unwanted source directly behind the microphone can defeat the reason for choosing it. Use the actual plot and the actual room rather than treating the word *hypercardioid* as a guarantee of maximum isolation. ### Figure-eight or bidirectional A figure-eight microphone has two main lobes: one at the front and one at the rear. Its lowest-sensitivity regions are at the sides, around 90 and 270 degrees. That makes it useful when you want to capture two opposing sources or keep a side source out of the pattern. Front and rear pickup are not automatically identical in tone. The microphone's frequency response, housing and orientation still matter. When placing a figure-eight, treat the side nulls as useful directions for unwanted sound and remember that the area behind the microphone is an active pickup lobe. That rear lobe has inverted polarity, which matters most when a figure-eight is part of a stereo pair. [RØDE's polar pattern explainer](https://rode.com/en-us/about/news-info/what-are-a-microphones-polar-patterns) names Blumlein and mid/side as figure-eight stereo methods and describes the simpler X/Y pair as two cardioids held together at a 90-degree angle. All three depend on how two channels combine, so check any stereo capture in mono as well; the [mono compatibility and phase correlation guide](https://soundforgepro.com/mono-compatibility-phase-correlation/) shows what to listen for and what the meter can confirm. ### Wide cardioid and subcardioid Wide cardioid, often called subcardioid, sits between omni and cardioid. [Shure describes subcardioid as close to omni but still slightly directional](https://www.shure.com/en-US/insights/specialist-polar-patterns-hypercardioid-and-subcardioid). It keeps a broad front area and some rear sensitivity, with less aggressive rejection than a conventional cardioid. It can be a sensible compromise when you want a natural room contribution without making the microphone fully open. The label describes a family shape, not a fixed curve. Compare the plot at the frequencies that matter for the source. A microphone can be wide at low frequencies and tighter at high frequencies, or show a different balance because of its capsule and acoustic path. ## How to read a polar pattern chart 1. **Find the front.** Locate 0 degrees and confirm which end of the physical microphone points there. End-address and side-address microphones do not present the capsule in the same way. 2. **Read the rings.** Identify the decibel spacing. A line one ring inward is lower sensitivity by the amount shown in the legend, not automatically a silent zone. 3. **Locate the nulls.** The deepest inward points are the directions with the lowest sensitivity in that plot. They are the first places to aim an unwanted source, but they are not guaranteed cancellation at every frequency. 4. **Compare frequency traces.** If the chart shows several colors or line styles, the shape is frequency-dependent. A microphone can have a smooth cardioid at one band and a wider or more uneven response at another. 5. **Check the off-axis tone.** A source can become darker, thinner or otherwise colored as it moves around the capsule. [Shure identifies off-axis coloration as a change in frequency response with angle](https://www.shure.com/en-GB/insights/microphone-basics-transducers-polar-patterns-frequency-response). 6. **Translate the map into placement.** Turn the microphone so the desired source is in the intended lobe and the strongest unwanted source is near a null. Then verify the result at the working distance. ## Why the same microphone changes with frequency A polar pattern is not a single three-dimensional sticker. Wavelength, capsule size, acoustic ports, housing and the microphone's operating principle all affect how the response changes with frequency. A plot may show several frequency groups for that reason. This matters when the unwanted sound has a different spectrum from the desired source. A pattern can reject a midrange spill source while allowing more high-frequency or low-frequency energy through. It can also preserve level reasonably well off axis while changing the tone. For a critical placement, use the manufacturer's plot for the exact model and do not borrow the curve from a similar-looking microphone. Shure's basics guide warns that on some microphones, particularly cheaper designs, a pattern specified as supercardioid may hold at 1 kHz and sit closer to omnidirectional at 150 Hz. Shotgun, or lobar, microphones show the effect even more clearly. [Shure's shotgun microphone guide](https://www.shure.com/en-US/insights/choosing-a-shotgun-microphone-the-long-and-short-of-it) explains that the interference tube narrows the pattern only above a frequency set by the tube's length; rejecting sound down to about 100 Hz would take a tube around 5.5 feet long. Below that point the pattern comes from the capsule itself, usually hypercardioid, so a shotgun's tight treble focus does not come with equally tight bass rejection. ## Off-axis sound and nulls **Off axis** means that sound arrives from an angle away from the microphone's front reference. The volume usually changes, but the tonal balance can change as well. That is why turning a singer's head or rotating a microphone can alter clarity even when the source remains the same distance away. A **null** is the lowest-sensitivity direction in a polar plot. It is useful for placing a monitor, fan or nearby instrument, but it is not a magic eraser. The null can move or become shallower at another frequency, and reflections can reach the capsule from other angles. Use it as a placement advantage, then check the whole acoustic path. Once reflections are baked into a take, no pattern choice can remove them; the guide to [removing echo from audio without wrecking speech](https://soundforgepro.com/remove-echo-from-audio/) covers what editing can still reduce. ## Polar patterns and proximity effect Proximity effect is the increase in low-frequency response that can occur as a gradient-type directional microphone moves closer to a source. It is strongest on axis for many directional designs, but the amount depends on source geometry, operating principle, distance and orientation. [DPA explains that proximity depends on the source, the gradient microphone and the angle of incidence](https://www.dpamicrophones.com/mic-university/background-knowledge/proximity-effect-in-microphones-explained/), and that a pressure-operated omni microphone does not show the same effect. This is why a universal rule such as “move the mic this far away” is misleading. Read the manufacturer's frequency response and use the intended source distance as a starting condition. When a close vocal sounds too heavy, first check the microphone's distance and angle. Moving it, changing the pattern or choosing a design with a different low-frequency response may solve the problem before EQ. If the source is a plane-like instrument or the microphone is used off axis, the result can differ from the familiar close-vocal example. ## Which polar pattern should you choose? | Situation | Starting point | Decision to verify | | ------------------------------------------------- | ---------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------- | | One source, untreated room, unwanted sound behind | Cardioid | Keep the unwanted source near the rear minimum and check off-axis tone. | | Side spill is the main problem | Supercardioid or hypercardioid | Map the rear lobe and minimum-sensitivity angle before placing other sources. | | Good room, wide source or natural ambience | Omnidirectional or wide cardioid | Confirm that the room and other sound sources are worth capturing. | | Two opposing sources | Figure-eight | Put the sources on the front and rear lobes and keep the loudest unwanted sound near the sides. | | Close source with too much low end | Omni, a wider pattern or a different placement | Check the microphone's operating principle and frequency response; pattern labels alone do not predict the bass change. | There is no universally best pattern. The useful match is the one that puts the desired source in a stable lobe, the unwanted source near a real null and the room contribution at a level you can accept. On a multi-pattern microphone, make sure the switch matches that choice. [The Podcast Host's pattern guide](https://www.thepodcasthost.com/equipment/microphone-polar-patterns/) says that when podcasters complain their Blue Yeti sounds bad, the usual cause is that it is set to omnidirectional for solo or remote-call recording, and recommends switching it to cardioid. If you are still deciding what kind of microphone to buy for that job, the [USB vs XLR microphone comparison](https://soundforgepro.com/usb-vs-xlr-microphone/) covers the trade-offs beyond the pattern. ## What to check before trusting a chart Before you use a polar pattern as a placement rule, confirm five details in the microphone documentation: - Which end or side of the microphone is the front reference? - Which frequencies are shown, and are the traces measured under the same conditions? - Does the chart show a typical pattern or the exact model and selectable mode? - Are rear rejection, side rejection or acceptance-angle values defined in the document? - Does the microphone's operating principle change the proximity-effect expectation? The spec terms in that list have plain meanings. The LEWITT guide linked above defines the acceptance angle as the zone in which sensitivity falls by no more than 3 dB and gives about −20 dB as a typical cardioid rear rejection, which means sound from behind is picked up at roughly a tenth of the front sensitivity. It describes the distance factor as how far a directional microphone can sit from the source, compared with an omni, while keeping the same ratio of direct and reflected sound. A figure quoted without its frequency tells you less than the plot it came from. A good example is the [Neumann U 87 Ai documentation](https://www.neumann.com/en-us/products/microphones/u-87-ai), which lists omni, cardioid and figure-eight modes and publishes separate official diagrams. The diagrams are useful model evidence, but they should not be presented as a universal picture of every microphone with the same pattern label. ## The short answer Choose a polar pattern by asking where the desired sound is, where the unwanted sound is and how much room you want in the recording. Use cardioid for a practical front-focused starting point, omni for an open response in a suitable room, figure-eight for front-and-rear pickup with side rejection, and supercardioid or hypercardioid when a narrower front response is worth managing the rear lobe. Then read the exact microphone's plot. Check the nulls, frequency traces, off-axis tone and proximity-effect conditions before you lock the stand position. If you are checking the resulting input rather than the pattern itself, the [SoundForgePro microphone test](https://soundforgepro.com/microphone-test/) covers level, clipping and noise as a separate signal check. ### How to Edit Breaths in Sound Forge Without Making Speech Sound Chopped URL: https://soundforgepro.com/edit-breaths-sound-forge/ Last updated: 2026-10-06T07:04:04.000Z A breath can tell you where a thought ends and the next one begins. If every inhale disappears, spoken audio may sound hurried even when each word is clean. If one inhale jumps out, it can distract more than a small mouth click. Decide phrase by phrase: keep it, turn it down, or replace the damaged part while keeping the pause. ## Listen before selecting anything Play the sentence before the inhale and the one after it at normal listening level. Ask whether the breath gives the listener a useful beat, whether it is simply louder than the surrounding speech, or whether it contains a click, rustle, bump or other damage. The waveform helps locate the event, but a quiet-looking breath can still be conspicuous after compression. If nearly every inhale jumps out, the cause may be upstream: heavy compression, or a microphone placed directly in the speaker's breath stream. Correcting that before the next session saves editing every inhale by hand. | What you hear | First choice | Listen for afterward | | ---------------------------------------------- | ------------------------------------- | -------------------------------------------------- | | A natural inhale that supports the phrasing | Keep it | Does the next sentence start comfortably? | | An otherwise clean inhale that draws attention | Reduce its level | Can you still hear a human taking a breath? | | An inhale with a rustle, lip noise or bump | Repair the event or replace that part | Do both joins and the background sound continuous? | ![Three breath-editing choices: keep a natural inhale, reduce a loud inhale, or replace a damaged inhale with matching room tone](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/09/breath-decisions-guide-q90.webp) Keep natural breaths, soften distracting ones, and reserve replacement for a breath that cannot be repaired cleanly. If the unwanted sound is a single dry tick rather than the inhale itself, use a local repair. The [mouth-click guide](https://soundforgepro.com/remove-mouth-clicks-from-audio/) covers that narrower problem. You may be able to leave most of the breath alone. ## Make a working copy and mark the whole breath Save a separate working version first. Find the start of the inhale after the previous phrase and the point where it settles before the next phrase. Avoid selecting the end of a consonant or the start of a vowel along with it. Zoom in to place the boundaries, then zoom out to check their position in the sentence. A breath may have a sharp onset followed by a soft tail; treating only the loudest spike can leave the rest sounding oddly detached. Keep the original pause length in mind before you cut anything. In Sound Forge Pro 2026, [ordinary Paste](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/paste.htm) deletes a current selection and inserts the clipboard contents. If the replacement is shorter or longer, the next phrase moves. That can be intentional, but it should be a listening decision, never an accidental side effect of replacing audio. When the pause must keep its length, use [Edit → Paste Special → Overwrite](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/overwrite.htm) instead. It replaces the selected audio without moving what follows, but if the clipboard is shorter than the selection, only the clipboard's length is overwritten and the rest of the original stays. Copy a replacement at least as long as the part you are covering. ![A breath selected from its onset to its tail between two phrases, and a comparison in which a shorter pasted replacement moves the next phrase earlier while Overwrite keeps the pause length unchanged](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/09/breath-selection-overwrite.webp) Select the breath from onset to tail, then use Overwrite when the next phrase has to stay where it is. ## Reduce a loud but clean inhale Select just the distracting breath. The documented [Process → Volume](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/volume.htm) dialog uses negative Gain values to attenuate selected audio. Preview a modest reduction and replay the full phrase. If the breath vanishes into a sudden pocket of silence, undo and use less. There is no fixed reduction that suits every voice or microphone. Watch the selection before you confirm: with no selection, Volume affects the whole file. If a straight level change makes either edge obvious, [Effects → Envelope](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/envelope.htm) lets you shape a gradual dip across the breath and return to the original level. Keep the transition inside the breath rather than fading the neighboring words. You can also use the documented [Graphic Fade](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/fade.htm) where a short transition is needed. Check the result by ear; the right curve depends on the recording. Long narration can hold hundreds of breaths. Once one reduction sounds right, select the next breath and use [Edit → Repeat](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/repeat.htm), which runs the last operation again with the same dialog settings. Hold Shift when you choose it to reopen the dialog and adjust the amount for a louder or softer inhale. Each repeat is still a listening decision, not a batch job. ## Replace a breath only when the breath itself is spoiled For a rustle or bump throughout an inhale, look first for a clean breath from the same speaker and recording setup. A mismatched inhale may be more conspicuous than the original flaw. If no suitable breath exists and the phrase reads naturally without one, use a segment of the recording's own room tone to keep the pause from dropping into digital silence. The [room-tone guide](https://soundforgepro.com/room-tone-sound-forge/) explains how to choose a matching source. 1. **Choose a clean source.** Listen for hum, speech tails and chair noise before copying it. Match the channel layout and general background character of the destination. 2. **Match the time.** Measure the portion you are replacing and prepare a source of suitable length. Overwrite keeps the pause length fixed; with ordinary Paste, a different length moves the next phrase, so check where it lands. 3. **Join both ends.** Inspect the entry from speech into the replacement and the exit into the next phrase. [Shape brief transitions](https://soundforgepro.com/crossfade-audio-sound-forge/) as needed so neither edge clicks or makes the room suddenly change. 4. **Replay in context.** The replacement is successful when the pacing and background feel ordinary, not when the waveform looks perfectly flat. A short clean breath often works better than room tone because it preserves the speaker's phrasing. Room tone is most useful when the damaged breath must go and the pause still needs a continuous background. If the noise sits on just one part of a breath, replace or repair that part instead of discarding the whole inhale. ## Why a noise gate rarely solves this by itself Sound Forge's [Noise Gate](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/noise%5Fgate.htm) removes signals below a threshold. It has no way to know that one low-level sound is a useful inhale and another is unwanted noise. A threshold that catches quiet breaths may also make the gaps between words unnaturally empty. Use a gate for a threshold problem when that behavior serves the file; make breath decisions in the sentence. If you do need one, the [noise gate guide](https://soundforgepro.com/how-to-use-noise-gate-sound-forge-pro/) explains how to set it and when gentler expansion or controlled room tone sounds more natural. Dedicated breath processors work differently from a level gate. [Waves describes its DeBreath plug-in](https://www.waves.com/plugins/debreath) as letting you control how much breath remains on a vocal track and add room tone where breaths have been reduced. On a long narration that can handle the first pass, but audition the result with the same sentence-level checks. ## Check the edit after your later processing Replay a few normal breaths, the strongest inhale and the two words around every repaired join. Listen at conversational volume and compare with the unedited copy at similar loudness. Compression or limiting later in the chain can bring a remaining breath forward again, so repeat this check after those steps. Don't keep lowering every breath just because you can see it. How much breathing sounds right also depends on the delivery. For interview shows, the [podcast editing workflow](https://soundforgepro.com/sound-forge-pro-for-podcasters/) shows where breath edits sit among the other passes. For audiobooks, long-time helpers in an [Audacity forum thread about removing breath sounds](https://forum.audacityteam.org/t/how-do-you-remove-the-sound-of-breath/42242) warn that the human quality check at ACX, Audible's audiobook marketplace, can reject narration with pulsing backgrounds or other signs of heavy processing, which is one more reason to keep pauses natural. For the larger sequence from recording through delivery, see the [voice-over workflow](https://soundforgepro.com/sound-forge-pro-for-voice-over-recording/). The [export checklist](https://soundforgepro.com/audio-export-qa-checklist/) helps catch a bad join before the file leaves your desk. A listener should hear the thought and its timing, not the repair. ### How to Reduce Headphone Bleed in a Vocal Recording URL: https://soundforgepro.com/reduce-headphone-bleed-vocal-recording/ Last updated: 2026-10-05T06:51:34.000Z A click track can hide under a singer's headphones and still end up on the vocal mic. You notice it when the music drops away: a little tick between lines, sometimes a ghost of the backing track. Before reaching for a gate, listen to where the leak actually sits. The quiet spaces and the words need different treatment. Keep the original take and work on a copy. Play a few seconds before and after each problem at the level you'll use for the finished vocal. If the click is audible only between phrases, you have room to edit it. If it lands on a consonant or a held note, turning down that moment turns down the performance too. ## First, make sure it is headphone bleed Listen to a section where the performer isn't singing. A regular tick that follows the cue click, or faint music that matches the headphone mix, points toward leakage from the earcups. An irregular tap may instead be handling noise or a physical knock; a constant electrical hum is another problem. Compare the timing with the original cue track if you have it. Don't label every sharp peak in the waveform as a leaked click until you hear it. Also check whether the leaked sound is in the raw vocal file or only in a monitor or mix bus. Editing the vocal cannot fix a click that was added later in the playback chain. The [recording troubleshooting guide](https://soundforgepro.com/sound-forge-pro-not-recording-audio/) is useful when the captured signal itself seems wrong. Then decide whether the leak matters. In an [r/audioengineering thread on headphone bleed](https://www.reddit.com/r/audioengineering/comments/anj2ju/tips%5Ffor%5Fheadphones%5Fbleeding%5Finto%5Fmic/), one reply warns that bleed which sounds offensive in a soloed vocal may be a non-issue in context, and another recordist says their headphones bleed noticeably yet it has never been a problem once the track is mixed. Some bleed even survives on finished records: [Wikipedia's article on spill](https://en.wikipedia.org/wiki/Spill%5F%28audio%29) quotes engineer Dave Pensado, who called the headphone spill on a Christina Aguilera vocal “honest” and suited to the song. Find the leak with the vocal soloed, then judge any edit with the backing track playing. ## Prevent the next take from leaking Start with [closed-back headphones](https://soundforgepro.com/open-back-vs-closed-back-headphones/) that sit securely around both ears. Turn the cue down until the performer can still hear pitch and timing without a loud click escaping into the room. A softer click sound or a cue mix that needs less overall level may be easier to sing against. If the performer moves one cup off the ear, ask for a quick check: the exposed driver can become the loudest source in front of the mic. Shape the cue as well as its level. In the same thread, one reply suggests EQing the headphone monitor mix so the singer gets enough to follow without feeding the mic, and another lowers or mutes the drum track because its sharp transients always poke through. Look at the earpads too: one recordist there found that very soft, wrinkled cushions leak more because they don't seal against the head. If closed-back headphones still leak, earbuds are the next step. In a [HomeRecording.com thread about headphone bleed](https://homerecording.com/bbs/threads/closed-back-headphones-im-getting-bleed.431158/), one member wears cheap earbuds under unplugged closed-backs for an extra barrier. A singer who switched to in-ear monitors, though, found that the closed-in occlusion effect affected their phrasing and breathing; another member suggested a little sidetone, some of the singer's own voice in the ears, without overdoing it. Record a few seconds with the headphones playing and the performer silent, then listen to the mic track alone. Repeat after any change to the cue level, fit or mic position. Distance and microphone orientation can help, but avoid moving the mic so far away that the voice becomes thin or the room takes over. A clean capture matters more than an elaborate repair later. ![Top-down view of a singer in closed-back headphones at a condenser microphone with a pop filter: cue sound leaks from both earcups and reaches the mic along with the voice](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/09/headphone-bleed-leak-path.webp) Leak from the earcups arrives at the mic together with the voice, so the fixes start at the headphones: a lower cue, a tight seal and a softer click. ## Choose the edit by where the leak lands **In a silent gap:** reduce the short section or replace a suitable gap with ambience from the same recording. Leave enough of the natural breath and room sound for the phrase to flow. **At the edge of a word:** use a very short level shape and audition the consonant in context. A click and a crisp consonant may occupy the same instant; the aim is a less distracting phrase, not an empty-looking waveform. **Under the voice:** compare another take or arrange a pickup if possible. A gate responds to overall level; it cannot tell the headphone music from a simultaneously sounding vocal. Specialized de-bleed processing is a separate option, but check whether it improves the actual words before keeping it. ![Three waveform cases: a click in a pause, a click at a word edge, and repeated clicks beneath the vocal](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/09/headphone-bleed-decisions-desktop-q90.webp) A gap allows a local level edit. Once the cue overlaps a word, compare takes before you process the voice. ## Reduce a click between phrases in Sound Forge Select the affected gap in your working copy. Sound Forge Pro 2026 documents [Process → Volume](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/volume.htm): a negative Gain value attenuates the selected audio. Make the selection before opening it, because with nothing selected the command changes the entire file. Try a modest reduction and listen across both joins. Muting every gap can make the room suddenly disappear. For a more gradual dip, the documented [Process → Fade → Graphic](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/fade.htm) command lets you shape the level of the selection with an envelope. Keep its low point around the click and return to the original level before the next syllable. The [room-tone guide](https://soundforgepro.com/room-tone-sound-forge/) covers filling a pause when a deep dip leaves an obvious hole. A [Noise Gate](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/noise%5Fgate.htm) can suppress signal below a set threshold during breaks. That is helpful only when the leak is quiet enough and the voice or desired breaths stay above the threshold. If the click remains above it, the gate opens on the click; if a word tail falls below it, the tail can vanish. For threshold, attack and release decisions, use the [separate Noise Gate guide](https://soundforgepro.com/how-to-use-noise-gate-sound-forge-pro/). For a few isolated ticks, a local edit is often easier to judge than gating the whole take. ## What if the click or music is under a word? Listen for the vowel, consonant and timing you need to keep. A negative gain change to the whole section reduces both the voice and the leak. Heavy broadband cleanup may make a click less obvious while softening the singer's diction. If an alternate line exists, compare its tone and phrasing; if a pickup fits, that may preserve the performance better than processing. Don't splice fragments into a different statement in spoken-word material. For a valuable take, iZotope lists [De-bleed in RX Standard and Advanced](https://www.izotope.com/products/rx-advanced?tab=features). According to the [RX 12 De-bleed documentation](https://docs.izotope.com/rx12/en/de-bleed.html), the module's main mode now uses machine learning and asks which source to keep, such as Vocals, while Classic mode keeps the RX 11 method: it learns the leak from a separate bleed-source track, such as the clean click, which must match the vocal's sample rate and line up with it within a few milliseconds. SpectraLayers Pro 13 also lists DeBleed among its repair processes, as the [restoration software comparison](https://soundforgepro.com/audio-restoration-software/) notes. These are external restoration products, not Sound Forge features, and the result still needs a before-and-after listen at matched level. A clear rhythm in the background is not proof that the overlapping vocal can be perfectly separated. Check consonants, breaths and word endings against the original; the [AI audio restoration guide](https://soundforgepro.com/ai-audio-restoration/) explains how to compare a processed voice. ## Listen once more after the mix changes Check the edit with the backing track, then solo the vocal again. Compression or a louder final balance can expose a faint click you did not notice in the raw take; an overdone gap can also sound more conspicuous once the track is mixed. Stop when the cue no longer draws the ear and the line still sounds like a person singing, not a row of disconnected syllables. ### How to Reduce Lavalier Clothing Rustle in Sound Forge URL: https://soundforgepro.com/reduce-lavalier-clothing-rustle-sound-forge/ Last updated: 2026-10-09T21:07:51.000Z A lavalier can sound clean while the wearer stands still, then crackle as soon as a collar moves. That is a different problem from steady background hiss. The microphone may be brushing fabric, or the cable may be carrying movement into its mount. For the next take, fix that contact first. For a recording you already have, decide where the rustle lands before trying to remove it. Keep the unprocessed recording. Listen to a full sentence at a normal level and mark three things: the quiet gaps you can change freely, the words that must remain clear, and any stretch where the noise follows every movement. A jagged waveform may help you find an event, but it will not tell you whether a consonant was lost. ## Start with the mic and the clothing Place the capsule where a loose collar, jacket edge or hair will not brush its grille during ordinary movement. Secure the cable near the mount so it does not tug at the capsule when the wearer turns. Use a clip or concealer made for that microphone and garment; a rigid mount pressed between two moving layers can simply move the noise to another spot. DPA's [4080 lavalier clip description](https://www.dpamicrophones.com/accessories/lavalier-clips-and-concealers/dmm0014?variant=145) explicitly ties its short cable trail to reducing cable noise. That is an example of the principle, not a universal fitting for every lav. Tape can do more than a clip here. In an [r/videography thread about lav rustle](https://www.reddit.com/r/videography/comments/smcwwy/any%5Ftechniques%5Fto%5Fminimize%5Flav%5Fmic%5Fclothing%5Frustle/), one videographer describes folding two small “footballs” of gaffer tape, sandwiching the mic head between them with its tip just past the point, and taping the package inside the clothing with a strain-relief loop taped above and below. A [PodcastVideos walkthrough for hiding a lav under a polo shirt](https://www.podcastvideos.com/hide-lavalier-mic-polo-shirt/) uses a double-sided sticky at the bottom of the button placket, a small fur piece over the capsule as a buffer against the fabric, and a cable saver about 15 cm down the cable so tugs do not reach the mic. Rycote says its [Undercovers lavalier covers](https://rycote.com/products/lavalier-solutions/covers/) are designed to minimize clothing rustle, yet opinions differ: in a [JWSound thread on minimizing lav rustle](https://jwsoundgroup.net/index.php?/topic/35245-best-options-for-minimizing-clothing-rustles-on-lav-mics/), the original poster found them fine for seated interviews but not once the subject moved, and another recordist wrote that they often create more noise. Judge any mount on the actual garment. ![Lavalier tape-sandwich mount in two steps: the mic capsule between two folded tape triangles with its tip just past the points, then the package inside a shirt with a small cable loop taped above and below](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/09/lav-tape-sandwich.webp) Tape sandwich with a strain-relief loop: the capsule is held flat between tape triangles, and tape on both sides of the loop keeps a pull on the cable away from the mic. Ask the wearer to turn, look down, reach, and sit as they will during the recording. Listen to that short sample before the real take. If the mic must be hidden, leave the sound inlet unobstructed and check that the concealer itself is not being squeezed by fabric. A windscreen can help with air movement, but it will not stop a cable rubbing on a shirt. The [voice-over recording guide](https://soundforgepro.com/sound-forge-pro-for-voice-over-recording/) covers the wider capture workflow. If the mount is secure and the noise remains, look at the fabric. In the same JWSound thread, one mixer names the quality and type of fabric as the main issue and calls leather the worst case even for a shotgun microphone; another describes a hospital series where the rustle disappeared once the actors went back to wearing cotton tank tops under their scrubs. A quieter layer or a different position can beat any accessory. When no lav position survives the wardrobe, recordists in the r/videography thread point to a boom and shotgun mic instead, provided someone is free to operate it. ## Choose the repair by where the rustle falls **Between words:** reduce the burst locally or replace a short gap with matching room tone. Keep the end of the preceding word, breaths that belong in the sentence, and the next consonant intact. **Across a word:** compare another take or a pickup before processing. Lowering a section of audio also lowers the speech inside it. A more selective repair may help, but it cannot guarantee a word hidden by a loud fabric scrape. **Under most of the take:** choose the few passages that matter most, then consider whether a new recording with a better mount is possible. A [broad noise reduction pass](https://soundforgepro.com/how-to-remove-background-noise-in-sound-forge-pro/) is unlikely to treat constantly changing cloth contact as though it were a stationary hiss. ![Lavalier rustle decisions: secure the microphone and cable, reduce noise in a pause, and protect a word overlapped by fabric noise](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/09/lav-decisions-desktop-v2-q90.webp) Check the mount first. In an existing take, a rustle between words is a local edit; a rustle over speech needs a more cautious choice. ## Repair a rustle in a pause with Sound Forge Work on a copy. Select only the noisy interval, with enough space on either side to hear the joins. In Sound Forge Pro 2026, [Process → Volume](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/volume.htm) lets you reduce the level of a selection with a negative Gain value. Make the selection first: the documented command applies to the entire file if no data is selected. A moderate dip may be less noticeable than total silence. If the background drops abruptly, use [Process → Fade → Graphic](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/fade.htm) to shape a short level change. Listen from before the previous word through the next one. If the pause develops an obvious hole, matching ambience from the same recording may be better than muting. The [room-tone guide](https://soundforgepro.com/room-tone-sound-forge/) explains how to fill a gap without making it sound empty. ## When fabric noise covers speech Compare the original line with any alternate take. A clean word from another take is often safer than an aggressive attempt to erase a scrape. A pickup can work when its voice, distance and room sound fit. For an interview, keep the speaker's actual meaning intact; do not manufacture a different statement from fragments. If there is no alternate, make a short local repair on a copy and compare the whole phrase at a similar listening level. The same part of the signal may contain both cloth noise and a consonant. Turning it down can make the sentence less intelligible even when the waveform looks calmer. Listen for the word, not for an attractive before-and-after display. EQ is the tempting shortcut, but it rarely separates the two. iZotope's [RX 10 documentation on lavalier rustle](https://docs.izotope.com/rx10/en/de-rustle/index.html) describes the noise as varying unpredictably, from higher-frequency brushing to lower-frequency thuds, so there is seldom one band you can cut without also cutting part of the voice. In a [sound.stackexchange.com thread on cloth rustle](https://sound.stackexchange.com/questions/26778/how-to-remove-cloth-rustling), one editor brought the noise down “to acceptable levels” with selective noise reduction followed by EQ, but could not remove it completely. If you try a cut, keep it local to the damaged phrase and compare it with the original; the [Sound Forge equalizer guide](https://soundforgepro.com/how-to-use-equalizer-sound-forge-pro/) covers the controls. Other answers in that thread report better results from de-click or de-crackle processing than from broad noise reduction, and better still, though slower, from spectral repair. Sound Forge Pro 2026 has a [DeClicker / DeCrackler](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/proonly/declicker%5Fdecrackler.htm) in the Effects menu, but Boris FX describes it for the crackle of scratched records, so treat it as an experiment on a copy rather than a rustle tool. The [repair chapter of the Sound Forge Pro 2026 help](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/proonly/repair.htm) says Sound Forge Pro Suite also includes SpectraLayers; when it is installed, [Tools → Edit in SpectraLayers (Standalone)](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/proonly/editing%5Fwith%5Fspectralayers%5Fpro.htm) opens the file there and offers to export the changes back when you close it. Dialogue-isolation tools that separate a voice from everything around it are another route, and the [AI audio restoration guide](https://soundforgepro.com/ai-audio-restoration/) explains why their output still needs a word-by-word comparison with the original. For an important take, iZotope describes [De-rustle in RX Advanced](https://www.izotope.com/products/rx-advanced?tab=features) as a tool for lavalier clothing noise. It is a separate product, not a Sound Forge command, and the feature description is no promise that a buried word can be recovered. Check the edition you have and compare the result with the original. If the wording remains uncertain, treat that as an editorial problem rather than guessing what was said. ## Finish the edit in context Play the repaired sentence with the surrounding audio, then listen again after your usual level or compression work. A soft rustle may become more obvious then, while heavy cleanup can make the voice dull or uneven. Stop when the speech is clear and the repair no longer calls attention to itself. For other short recording defects, the [clicks and pops guide](https://soundforgepro.com/how-to-remove-clicks-pops-sound-forge-pro/) covers the separate case of isolated transients. ### How to Reduce Keyboard Noise in a Voice Recording with Sound Forge URL: https://soundforgepro.com/reduce-keyboard-noise-voice-recording-sound-forge/ Last updated: 2026-10-02T06:56:33.000Z Typing under a voice recording is easy to notice and hard to remove cleanly. A key hit in a pause is a small edit. A hit across a consonant shares the same instant as the speech you want to keep. A run of typing beneath every sentence is a recording problem first. I would make those three decisions before opening a noise-reduction control. Keep an untouched copy of the take. Listen to the whole sentence at an ordinary level, then mark the offending hits. The visible spike can help locate a keypress, but the ear decides whether the word and its natural rhythm survive an edit. ## Choose the edit by where the key lands **In a pause:** lower the isolated hit or replace only a short gap with matching room tone. Preserve the end of the previous word and the start of the next. **On a word:** compare the original with another take or a pickup. A precise repair tool may reduce the hit, but it cannot promise to recover speech hidden beneath it. **Throughout the recording:** make a small number of local repairs where the distraction matters most. For the next take, separate the keyboard from the microphone or stop typing while speaking. ![Three typing-noise cases in a voice recording: a key hit in a pause, a hit over a word, and repeated typing beneath speech](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/09/keyboard-decisions-desktop-q90.webp) Find the key hit in relation to the words before choosing a local edit, another take, or a change to the recording setup. This guide is about keyboard noise in spoken-word audio. The existing [clicks and pops guide](https://soundforgepro.com/how-to-remove-clicks-pops-sound-forge-pro/) covers a wider set of isolated defects, including clicks outside this recording situation. ## Remove a key hit in a pause Zoom in until you can select the hit without selecting a breath, a word tail or the next consonant. In Sound Forge Pro 2026, [Process → Volume](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/volume.htm) can attenuate selected audio using a negative Gain value. Check the selection before applying it: the documented command changes the whole file if nothing is selected. A modest reduction often keeps the pause more believable than complete silence. Listen across the edit from a few words before the hit. If the background appears to jump down and back up, shape the change more gradually. [Process → Fade → Graphic](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/fade.htm) lets you adjust an envelope over selected audio. Keep the edges outside the important parts of the neighboring words. A fade that sounds clean in isolation can still leave an obvious hole in a sentence. When the hit fills much of a quiet gap, consider room tone from the same session instead of muting it. Choose a piece without a hidden breath, click or change in ambience; retain the timing and listen across both joins. The [room-tone guide](https://soundforgepro.com/room-tone-sound-forge/) explains why a natural pause matters to an edit. When the typing falls only between sentences, a gate is the batch version of this edit. Sound Forge's [Effects → Noise Gate](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/noise%5Fgate.htm) is documented for removing noise from silent breaks, and the [noise gate guide](https://soundforgepro.com/how-to-use-noise-gate-sound-forge-pro/) shows how to set it from a measured pause and the quietest word you need to keep. It cannot remove a key that lands while you speak, because the voice holds the gate open. A user in an [OBS forum thread](https://obsproject.com/forum/threads/help-noise-gate-audio-filter-to-remove-keyboard-and-mouse-sounds.146323/) describes exactly that limit: the gate removed clicks made between words, while clicks made during speech stayed easy to hear. Set it gently enough to keep quiet word endings and some room tone; a gate that drops to silence after every phrase can draw more attention than an occasional key. ## When the click overlaps a word Start with the unprocessed line and any alternate take. If the second take has the word intact, that gives you a safer starting point than trying to erase a click from the first. A short pickup can also work if its distance, tone and background fit the surrounding phrase. For an interview or quotation, keep the spoken wording faithful; do not assemble a different statement from pieces. If no alternate exists, try a local attenuation on a working copy and compare it against the original at a similar playback level. The keyboard transient and the consonant may occupy the same time. Turning down the transient can turn down the consonant with it. Listen to the whole word and the words on either side, then choose the version that communicates the speech more clearly. For a consequential take, a dedicated repair editor can offer a more selective attempt. iZotope lists [Spectral Repair in RX Standard](https://www.izotope.com/products/rx-standard?tab=features) for selecting unwanted sounds in a spectral display. RX is separate from Sound Forge, and a visible shape is not proof that a damaged syllable can be restored. Check the current edition before buying or relying on a module, and compare the repaired phrase with the original. If the word remains uncertain, flag it for editorial review rather than filling it in by guesswork. ## When typing runs under the whole take Continuous typing is not the same as a few marked clicks. General noise reduction can be useful for a steady background, but sharp key hits change from moment to moment and can overlap speech. Applying more processing across the whole take may make the voice sound hollow while leaving the most distracting hits. iZotope's [dialogue-cleanup guidance](https://www.izotope.com/community/blog/how-to-remove-background-noise-from-dialogue-recordings) likewise distinguishes noise types and favors careful listening to the result. Two narrower tools are worth a trial on a copy. If each keystroke also arrives as a low thump carried through the desk and the mic stand, a High Pass band in Sound Forge's [Modern Equalizer](https://soundforgepro.com/how-to-use-equalizer-sound-forge-pro/) can reduce that rumble. Raise the cutoff only until the voice begins to sound thin, and expect the sharp click itself to remain. [DeClicker / DeCrackler](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/proonly/declicker%5Fdecrackler.htm) is documented for crackle and the single clicks typical of scratched records, not typing, so compare consonants and word onsets closely before keeping its result. Pick the passages that matter: an opening line, a crucial answer, a pause that draws attention to a key. Edit those locally and listen to the result in context. If the keyboard remains audible on nearly every word, consider whether the take is usable as it stands or whether a new recording is possible. The broader [noise-reduction guide](https://soundforgepro.com/audio-noise-reduction-software/) can help distinguish persistent hiss or hum from these short transients. If the recording only has to be understood, for a transcript or meeting notes rather than publication, the goal changes. For a half-hour meeting with constant typing near the microphone, a long-time [Audacity forum regular](https://forum.audacityteam.org/t/remove-keyboard-sounds/95009) suggested a telephone-style band limit that keeps roughly 300 Hz to 3 kHz, since plain words stay intelligible without the rest; High Pass and Low Pass bands in the Modern Equalizer can do the same in Sound Forge. Machine-learning speech enhancement is another route for a file like this, but it can change the voice and the room, and the [AI audio restoration guide](https://soundforgepro.com/ai-audio-restoration/) lists the retention and training terms to check before you upload a private meeting or interview. ## Prevent it on the next recording Move the microphone closer to your mouth and lower the input gain to match: your voice comes back to the same level, while the keyboard, whose distance has not changed, gets quieter. Keep the stand off the desk you type on, or use a shock mount if it has to share that surface. Aim the mic at your voice and turn its least-sensitive side toward the keyboard; for a cardioid, that is directly opposite the side you speak into. As the [dynamic vs condenser comparison](https://soundforgepro.com/dynamic-vs-condenser-microphone/) explains, neither microphone type rejects background sound on its own, so placement does most of the work. Record a short sample while speaking and typing as you normally would. Listen back before committing to a long take. If the script is on screen, arrange the workflow so you can stop typing during spoken lines. In a remote conversation, ask the other participant to do the same when possible. ![Top-down desk layout with the microphone close to the speaker's mouth on a boom arm and shock mount, its heart-shaped cardioid pickup facing the voice and its least-sensitive rear side pointing at the keyboard](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/09/keyboard-setup.webp) Put the keyboard behind the microphone, where a cardioid hears least, and bring the voice closer instead of turning the gain up. After any repair, check the edited section again once your normal compression or level work is in place: those steps can bring a remaining click forward. Judge the whole sentence, not a single spike. If the pause still feels natural and the words remain clear, stop there. The [voice-over workflow](https://soundforgepro.com/sound-forge-pro-for-voice-over-recording/) covers the surrounding recording and delivery decisions. ### How to Reduce Wind Noise in a Voice Recording with Sound Forge URL: https://soundforgepro.com/reduce-wind-noise-voice-recording-sound-forge/ Last updated: 2026-10-04T20:02:54.000Z A gust can sound like a low thump, a rolling roar, or a burst that swallows a syllable. Those are not the same edit. If the gust sits between words, you can usually deal with that small interval. If it runs under the voice, you have to preserve the words while reducing what you can. And if the microphone overloaded, a quieter version of the damage is still damage. My rule is to locate the gust first, then decide how much of it the listener actually hears in the sentence. Do not process a whole outdoor recording to fix three rough seconds. ## Find out where the wind is Save a working copy and listen to the passage at an ordinary level. Mark each gust and note whether it lands in a pause, partly under a word, or across an entire phrase. Listen for crackly distortion as well as bass-heavy rumble. A waveform can help you find a large burst, but it cannot tell you whether a consonant remains intelligible. **Gust in a pause.** Reduce or replace that interval while keeping the pause and room tone continuous. Listen for an abrupt join. **Rumble under clear speech.** Try a restrained low cut or local level shaping, then compare the same phrase with the original. Too much filtering can thin the voice. **A word is obscured or distorted.** Look for another take or record the phrase again if possible. A filter cannot restore missing speech detail. ![Three wind-noise cases in a voice recording: a gust in a pause, rumble beneath speech and a damaged phrase](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/09/wind-decisions-guide-q90.webp) Choose the repair by where the gust lands. A quiet gap, intelligible speech and a damaged word call for different decisions. Do not mistake this for ordinary steady hiss. The [noise-reduction software guide](https://soundforgepro.com/audio-noise-reduction-software/) discusses more general cleanup choices; intermittent wind buffeting needs closer decisions at each event. ## When the gust is between phrases Zoom in around the pause and select the gust without catching the tail of the previous word or the attack of the next. In Sound Forge Pro 2026, [Process → Volume](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/volume.htm) lets you lower a selected region with negative Gain. Start gently, preview, then listen from the previous sentence into the next. Without a selection, the command can affect the whole file, so check what is highlighted before applying it. If a sudden level step makes the background jump, use a gradual transition. The documented [Process → Fade → Graphic](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/fade.htm) offers an envelope for the selected audio. Bring the level down after the first word has finished and back up before the next begins. The aim is not a ruler-flat gap; it is a pause that still belongs to this recording. For a gust that fills most of the pause, matching ambience from a clean section of the same recording may sound less conspicuous than digital silence. Check the source for a hidden breath or speech tail, preserve the original timing, and listen across both joins. The [restoration hub](https://soundforgepro.com/audio-restoration/) has related repairs when the interval also contains clicks or handling noise. When gusts fall only in the gaps across a long take, a gate can handle them in one pass instead of one selection at a time. Sound Forge's [Effects → Noise Gate](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/noise%5Fgate.htm) is documented for removing noise from silent breaks, and the [noise gate guide](https://soundforgepro.com/how-to-use-noise-gate-sound-forge-pro/) explains how to set its threshold against the pause and the quietest word. It will not help once wind runs under a word: the voice opens the gate and the gust comes through with it, and the silence around that moment can make the remaining wind more obvious. Set it gently, then listen where the gate opens and closes. ## When wind sits under the voice Keep the words as your reference. Wind often brings a strong low-frequency component: [Shure's wind guidance](https://www.shure.com/en-US/insights/shure-tech-tip-methods-to-minimize-wind-noise) explains why reducing the very low end can help. Try a conservative low cut on a working copy, and compare the same phrase at matched listening loudness. Move only as far as the voice allows. If the result loses its weight while the gust is still obvious, more filtering is a poor trade. There is no frequency setting I can give you without hearing this voice and microphone. A deep voice, a close recording and [a lavalier buffeted by clothing](https://soundforgepro.com/reduce-lavalier-clothing-rustle-sound-forge/) will not tolerate the same move. The [Sound Forge equalizer guide](https://soundforgepro.com/how-to-use-equalizer-sound-forge-pro/) explains the EQ controls; use it for the mechanics, then make the judgment in context. A broad level reduction over the whole word is rarely a substitute: it turns down the speech with the wind. Slope is a separate choice from where the filter starts. Shure's wind guidance uses a microphone with both a steep and a gentle low-frequency roll-off switch as its example, and regulars in an [Audacity forum thread on wind noise](https://forum.audacityteam.org/t/removal-of-wind-noise/27705) reached for a steep high-pass. Their starting points, around 100–120 Hz, are places to begin listening rather than a setting to copy. In the [Modern Equalizer](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/modern%20equalizer.htm), a High Pass band's slope is changed from the three-dot control on its filter icon, from 6 up to 36 dB per octave. One of those regulars also drew the limit plainly: if the wind is whistling or rushing rather than a low thump, it stays in the recording. That sound shares frequencies with the voice, so a filter cannot take it out without taking some of the voice too. ![Frequency chart comparing a gentle and a steep high-pass filter that share one corner: the steep curve cuts the low wind rumble while leaving the voice, and neither reaches rushing wind that overlaps the voice](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/09/wind-highpass.webp) A steeper high-pass removes more rumble below the same corner; wind that overlaps the voice stays unless you cut the voice too. A dedicated wind tool can sometimes be worth trying on an important take. For example, iZotope lists [De-wind in RX Advanced](https://www.izotope.com/products/rx-advanced?tab=all-modules) for intermittent low-frequency wind at the microphone diaphragm. That is a separate product and edition, not a Sound Forge command. Even with a specialist tool, listen for altered consonants and false confidence about words you can no longer hear clearly. Speech-isolation tools are the other route people try. In an [r/Logic\_Studio thread about wind](https://www.reddit.com/r/Logic%5FStudio/comments/1768k12/how%5Fcan%5Fi%5Fremove%5Fwind%5Fnoise/), the original poster found that Final Cut Pro's voice isolation did a surprisingly good job on wind, at the cost of a slightly thinner voice tone, and later reported that Logic's built-in Voice Isolation plug-in also worked well. In a [DVXuser thread](https://www.dvxuser.com/threads/audio-software-to-remove-wind-noise-from-a-video-clip.5712371/), members pointed a video editor to DaVinci Resolve's dialogue isolation and to an online AI service. Treat any of these as a separate pass on a copy, and compare consonants and breaths against the original before you bring the result back into Sound Forge. Before uploading a private recording to a web service, check its retention and model-training terms, as the [AI audio restoration guide](https://soundforgepro.com/ai-audio-restoration/) explains. In that same thread, exporting an audio-only WAV instead of sending the large video file is what finally got the job through. ## When the gust has ruined a word First compare another take, a second microphone or the unprocessed original. If a word is buried by a heavy burst or the input clipped, reducing the low end cannot recover information that was never captured cleanly. Sometimes a less polished but intelligible alternate is the better edit. For a new voice-over, a short pickup of the phrase is preferable to a plausible-sounding guess at the syllable. If there is no replacement, decide whether the listener can still understand the sentence. Keep enough of the original texture to avoid an obvious hole, and do not present an aggressive cleanup as restored speech. For a quoted or consequential statement, mark the uncertain word for editorial review instead of silently changing its meaning. ## Prevent the next gust before you hit record Editing works best when wind never reaches the diaphragm. Use a windshield suited to the microphone and conditions, watch where the mic points, and make a brief outdoor test before the real take. RØDE's [outdoor recording guidance](https://rode.com/en-us/about/news-info/audio-for-film-101-ways-to-reduce-wind-noise-when-recording-outside) covers placement and wind protection; Shure also recommends physical shielding and attention to mic position. A foam cover that helps indoors may not be enough for a strong outdoor gust. For that, both RØDE and Shure describe an artificial-fur cover, the one crews call a dead cat; Shure notes it is typically fitted over a zeppelin-style blimp. Also set the input level lower than you would indoors, so a gust has room before it clips. A reply in the r/Logic\_Studio wind thread makes the same point, and a clipped gust is the kind of damage no later edit can undo. Replay the repaired section after any later compression, limiting or overall EQ, because that processing may make a remaining gust more noticeable. Compare with the original at similar loudness and listen to the whole sentence, not only the repaired half-second. If your broader task is spoken-word capture and delivery, the [voice-over recording workflow](https://soundforgepro.com/sound-forge-pro-for-voice-over-recording/) provides the surrounding steps. ### Phase Correlation Meter URL: https://soundforgepro.com/phase-correlation-meter/ Last updated: 2026-10-10T13:56:13.000Z A phase correlation meter tells you how closely the left and right channels move together. Load a stereo file below to see the relationship at the playhead, inspect its shape, and hear what happens when the channels meet in mono. I use the mono preview as the deciding check: a number can flag a problem, but it cannot tell you which sound matters. Audio Tools · local file ## Check the stereo relationship Load a file, inspect correlation and stereo shape, then listen to the mono fold-down. Choose audio file Or drop one file here. Your audio stays in this browser. The file is decoded and analyzed locally and is not uploaded by this tool. Choose a browser-decodable audio file to begin. No file selected. Current 2,048-sample window **—**−1 to +1 −10+1 Whole-file correlation**—** Correlation is a clue, not a pass/fail score. Compare the reading with what you hear in mono. Stereo vectorscope LeftCenterRight Load a stereo file to see its shape. The numerical reading above is the text alternative. PlayPlayback position 0:00 / 0:00 Preview:StereoMono fold-down Mono preview uses (L + R) / 2 and an 80% output gain. Current correlation covers 2,048 samples at the playhead and updates up to ten times a second; whole-file correlation combines every paired sample. Silence has no defined correlation. Browser decoding support and available memory vary. Lower your volume before playback. ## Read the number, then listen The current reading covers 2,048 paired samples near the playback position, roughly 46 ms at 44.1 kHz or 43 ms at 48 kHz. Conventional correlation meters usually average over a longer stretch, typically around 600 milliseconds according to [Sound On Sound's explanation of phase correlation meters](https://www.soundonsound.com/sound-advice/q-what-are-my-phase-correlation-meters-telling-me), so this reading can jump much more quickly when a vocal, effect or transient enters. Whole-file correlation combines every paired sample in the decoded recording into one normalized result; it is not an average of the numbers you see while the meter moves. Use the position control to inspect a passage, rather than assuming the file-wide value describes every moment. Near **+1**, the channels move together. That is ordinary for a centered voice or identical left and right channels; it does not mean a mix has the right amount of width. Around **0**, the channels share less of the same movement. Wide ambience can sit there without losing anything important. A **negative** reading means opposing information is present in that window. If it lasts through a crucial sound, switch to mono and listen for a loss of body, attack or clarity. A brief dip on its own is a reason to check, not a verdict. Typical causes of a sustained negative reading include a stereo width or spread setting pushed beyond 100%, which [Apple's guide to the Logic Pro Correlation Meter](https://support.apple.com/guide/logicpro/correlation-meter-lgcef24f430f/mac) lists as a source of negative values, and one channel with inverted polarity. At −1 the channels are identical but opposite, so they cancel in mono. The number is also broadband: every frequency contributes to one value. A loud, centered bass line can hold the reading positive while a quieter pad or double-tracked part cancels underneath it, so the mono preview still has the final say. Check the low end with particular care, because cancellation there removes weight rather than just width. When you need to locate the problem by frequency, a multiband correlation meter such as Voxengo Correlometer, covered in our [free metering plug-ins roundup](https://soundforgepro.com/free-metering-plugins/), splits the reading into bands. ## Use the shape to find the moment The vectorscope plots the left/right relationship for the same short window. A narrow, upright trace suggests a strong center relationship; a wider cloud suggests more side information. A trace that flattens toward a horizontal line points to out-of-phase content; [Apple's goniometer guide for Logic Pro](https://support.apple.com/guide/logicpro/goniometer-mode-lgcef24f3cd5/mac) reads the shapes the same way. If the trace leans to one side, check whether your channels are balanced and routed as expected. The [left/right speaker test](https://soundforgepro.com/left-right-speaker-test/) helps you rule out a monitoring mix-up before changing the file. ![Three vectorscope traces compared: a vertical line reading +1 for identical channels, a round cloud near 0 for wide stereo, and a horizontal line reading −1 for polarity-inverted channels](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/09/phase-correlation-states.webp) Vertical means the channels move together, a round cloud means wide, and a flat horizontal trace means they oppose each other. Choose **Mono fold-down** while the file plays to hear the channels combined as (L + R) / 2, with the preview output at 80%. The position stays put when you switch modes. Listen for an element changing or disappearing, not just a difference in loudness. Headphones can reveal a cancellation change, but they cannot tell you exactly how it will sound through a particular room and speaker system. ## What this check can and cannot do The file is decoded and analyzed in your browser; this tool does not upload the audio. It accepts one browser-decodable file at a time. Format support and available memory depend on your browser and device, so a file that opens in an editor may still fail here. Mono input is playable, but there is no left/right correlation to calculate. Silence also has no stable correlation reading, and multichannel files need a different analysis than a single left/right pair. If mono reveals a real loss, the [Sound Forge mono-compatibility guide](https://soundforgepro.com/mono-compatibility-phase-correlation/) shows how to confirm it with the editor's Mono-Compatibility Meter and Phase Scope, then find the cause and repair the source. Once you have changed it, run the [audio export QA checklist](https://soundforgepro.com/audio-export-qa-checklist/) on the actual delivered file. Correlation cannot certify a mix for every playback system; the important question is whether the parts your listener needs survive the fold-down. ### MIDI CC Chart: Control Change Numbers 0–127 URL: https://soundforgepro.com/midi-cc-chart/ Last updated: 2026-10-02T07:03:09.000Z **This MIDI CC chart lists every MIDI 1.0 Control Change number from 0 to 127.** Search by controller number, name or hex value, then narrow the table to common controls, MSB/LSB pairs, switches, RPN/NRPN or Channel Mode messages. The assignments come from the current [MIDI Association Control Change reference](https://midi.org/midi-1-0-control-change-messages); the receiving instrument still decides which messages it supports. **Quick lookup rule** Use `CC64` for a decimal number and `0x40` for hex. A plain value such as `40` can match both decimal CC40 and hexadecimal 0x40, which is CC64. ## Common MIDI CC numbers These are the controls musicians reach for most often. Select one to jump to its full row in the chart. CC1**Modulation**Modulation Wheel or Lever CC7**Channel volume**Channel Volume (formerly Main Volume) CC10**Pan**Pan CC11**Expression**Expression Controller CC64**Sustain**Damper Pedal on/off (Sustain) CC71**Resonance / timbre**Sound Controller 2 (default: Timbre/Harmonic Intens.) CC74**Brightness**Sound Controller 5 (default: Brightness) CC91**Reverb send**Effects 1 Depth (default: Reverb Send Level – see MMA RP-023) (formerly External Effects Depth) ## Complete MIDI CC chart: 0–127 MIDI 1.0 · CONTROL CHANGE ### Find a controller number Search names, decimal CC numbers or hex. Filters and search work together. Download CSVPrint full chart Search the chart Clear All 128 Common MSB 0–31 LSB 32–63 Switches 64–69 Sound 70–79 Effects 91–95 RPN / NRPN 96–101 Undefined Channel Mode 120–127 **128** rows shown **No matching controllers**Clear the search or switch back to All 128.Reset chart In this chart, MSB/LSB labels are reserved for defined controller pairs and parameter-number fields. Other controls are labeled by function so an overview-table label is not mistaken for a controller pair. __MIDI 1.0 Control Change numbers 0 through 127__ | CC | Hex | Binary | Standard function | Value / behavior | Type / pairing | | ------------ | ---- | -------- | --------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------ | ------------------------------- | | **CC0**0 | 0x00 | 00000000 | **Bank Select** | 0-127 | MSB · paired with CC32 | | **CC1**1 | 0x01 | 00000001 | **Modulation Wheel or Lever** | 0-127 | MSB · paired with CC33 | | **CC2**2 | 0x02 | 00000010 | **Breath Controller** | 0-127 | MSB · paired with CC34 | | **CC3**3 | 0x03 | 00000011 | **Undefined** | 0-127 | MSB · paired with CC35 | | **CC4**4 | 0x04 | 00000100 | **Foot Controller** | 0-127 | MSB · paired with CC36 | | **CC5**5 | 0x05 | 00000101 | **Portamento Time** | 0-127 | MSB · paired with CC37 | | **CC6**6 | 0x06 | 00000110 | **Data Entry MSB** | 0-127 | MSB · paired with CC38 | | **CC7**7 | 0x07 | 00000111 | **Channel Volume (formerly Main Volume)** | 0-127 | MSB · paired with CC39 | | **CC8**8 | 0x08 | 00001000 | **Balance** | 0-127 | MSB · paired with CC40 | | **CC9**9 | 0x09 | 00001001 | **Undefined** | 0-127 | MSB · paired with CC41 | | **CC10**10 | 0x0A | 00001010 | **Pan** | 0-127 | MSB · paired with CC42 | | **CC11**11 | 0x0B | 00001011 | **Expression Controller** | 0-127 | MSB · paired with CC43 | | **CC12**12 | 0x0C | 00001100 | **Effect Control 1** | 0-127 | MSB · paired with CC44 | | **CC13**13 | 0x0D | 00001101 | **Effect Control 2** | 0-127 | MSB · paired with CC45 | | **CC14**14 | 0x0E | 00001110 | **Undefined** | 0-127 | MSB · paired with CC46 | | **CC15**15 | 0x0F | 00001111 | **Undefined** | 0-127 | MSB · paired with CC47 | | **CC16**16 | 0x10 | 00010000 | **General Purpose Controller 1** | 0-127 | MSB · paired with CC48 | | **CC17**17 | 0x11 | 00010001 | **General Purpose Controller 2** | 0-127 | MSB · paired with CC49 | | **CC18**18 | 0x12 | 00010010 | **General Purpose Controller 3** | 0-127 | MSB · paired with CC50 | | **CC19**19 | 0x13 | 00010011 | **General Purpose Controller 4** | 0-127 | MSB · paired with CC51 | | **CC20**20 | 0x14 | 00010100 | **Undefined** | 0-127 | MSB · paired with CC52 | | **CC21**21 | 0x15 | 00010101 | **Undefined** | 0-127 | MSB · paired with CC53 | | **CC22**22 | 0x16 | 00010110 | **Undefined** | 0-127 | MSB · paired with CC54 | | **CC23**23 | 0x17 | 00010111 | **Undefined** | 0-127 | MSB · paired with CC55 | | **CC24**24 | 0x18 | 00011000 | **Undefined** | 0-127 | MSB · paired with CC56 | | **CC25**25 | 0x19 | 00011001 | **Undefined** | 0-127 | MSB · paired with CC57 | | **CC26**26 | 0x1A | 00011010 | **Undefined** | 0-127 | MSB · paired with CC58 | | **CC27**27 | 0x1B | 00011011 | **Undefined** | 0-127 | MSB · paired with CC59 | | **CC28**28 | 0x1C | 00011100 | **Undefined** | 0-127 | MSB · paired with CC60 | | **CC29**29 | 0x1D | 00011101 | **Undefined** | 0-127 | MSB · paired with CC61 | | **CC30**30 | 0x1E | 00011110 | **Undefined** | 0-127 | MSB · paired with CC62 | | **CC31**31 | 0x1F | 00011111 | **Undefined** | 0-127 | MSB · paired with CC63 | | **CC32**32 | 0x20 | 00100000 | **LSB for Control 0 (Bank Select)** | 0-127 | LSB · paired with CC0 | | **CC33**33 | 0x21 | 00100001 | **LSB for Control 1 (Modulation Wheel or Lever)** | 0-127 | LSB · paired with CC1 | | **CC34**34 | 0x22 | 00100010 | **LSB for Control 2 (Breath Controller)** | 0-127 | LSB · paired with CC2 | | **CC35**35 | 0x23 | 00100011 | **LSB for Control 3 (Undefined)** | 0-127 | LSB · paired with CC3 | | **CC36**36 | 0x24 | 00100100 | **LSB for Control 4 (Foot Controller)** | 0-127 | LSB · paired with CC4 | | **CC37**37 | 0x25 | 00100101 | **LSB for Control 5 (Portamento Time)** | 0-127 | LSB · paired with CC5 | | **CC38**38 | 0x26 | 00100110 | **LSB for Control 6 (Data Entry)** | 0-127 | LSB · paired with CC6 | | **CC39**39 | 0x27 | 00100111 | **LSB for Control 7 (Channel Volume, formerly Main Volume)** | 0-127 | LSB · paired with CC7 | | **CC40**40 | 0x28 | 00101000 | **LSB for Control 8 (Balance)** | 0-127 | LSB · paired with CC8 | | **CC41**41 | 0x29 | 00101001 | **LSB for Control 9 (Undefined)** | 0-127 | LSB · paired with CC9 | | **CC42**42 | 0x2A | 00101010 | **LSB for Control 10 (Pan)** | 0-127 | LSB · paired with CC10 | | **CC43**43 | 0x2B | 00101011 | **LSB for Control 11 (Expression Controller)** | 0-127 | LSB · paired with CC11 | | **CC44**44 | 0x2C | 00101100 | **LSB for Control 12 (Effect control 1)** | 0-127 | LSB · paired with CC12 | | **CC45**45 | 0x2D | 00101101 | **LSB for Control 13 (Effect control 2)** | 0-127 | LSB · paired with CC13 | | **CC46**46 | 0x2E | 00101110 | **LSB for Control 14 (Undefined)** | 0-127 | LSB · paired with CC14 | | **CC47**47 | 0x2F | 00101111 | **LSB for Control 15 (Undefined)** | 0-127 | LSB · paired with CC15 | | **CC48**48 | 0x30 | 00110000 | **LSB for Control 16 (General Purpose Controller 1)** | 0-127 | LSB · paired with CC16 | | **CC49**49 | 0x31 | 00110001 | **LSB for Control 17 (General Purpose Controller 2)** | 0-127 | LSB · paired with CC17 | | **CC50**50 | 0x32 | 00110010 | **LSB for Control 18 (General Purpose Controller 3)** | 0-127 | LSB · paired with CC18 | | **CC51**51 | 0x33 | 00110011 | **LSB for Control 19 (General Purpose Controller 4)** | 0-127 | LSB · paired with CC19 | | **CC52**52 | 0x34 | 00110100 | **LSB for Control 20 (Undefined)** | 0-127 | LSB · paired with CC20 | | **CC53**53 | 0x35 | 00110101 | **LSB for Control 21 (Undefined)** | 0-127 | LSB · paired with CC21 | | **CC54**54 | 0x36 | 00110110 | **LSB for Control 22 (Undefined)** | 0-127 | LSB · paired with CC22 | | **CC55**55 | 0x37 | 00110111 | **LSB for Control 23 (Undefined)** | 0-127 | LSB · paired with CC23 | | **CC56**56 | 0x38 | 00111000 | **LSB for Control 24 (Undefined)** | 0-127 | LSB · paired with CC24 | | **CC57**57 | 0x39 | 00111001 | **LSB for Control 25 (Undefined)** | 0-127 | LSB · paired with CC25 | | **CC58**58 | 0x3A | 00111010 | **LSB for Control 26 (Undefined)** | 0-127 | LSB · paired with CC26 | | **CC59**59 | 0x3B | 00111011 | **LSB for Control 27 (Undefined)** | 0-127 | LSB · paired with CC27 | | **CC60**60 | 0x3C | 00111100 | **LSB for Control 28 (Undefined)** | 0-127 | LSB · paired with CC28 | | **CC61**61 | 0x3D | 00111101 | **LSB for Control 29 (Undefined)** | 0-127 | LSB · paired with CC29 | | **CC62**62 | 0x3E | 00111110 | **LSB for Control 30 (Undefined)** | 0-127 | LSB · paired with CC30 | | **CC63**63 | 0x3F | 00111111 | **LSB for Control 31 (Undefined)** | 0-127 | LSB · paired with CC31 | | **CC64**64 | 0x40 | 01000000 | **Damper Pedal on/off (Sustain)** | ≤63 off, ≥64 on | Switch / pedal | | **CC65**65 | 0x41 | 01000001 | **Portamento On/Off** | ≤63 off, ≥64 on | Switch / pedal | | **CC66**66 | 0x42 | 01000010 | **Sostenuto On/Off** | ≤63 off, ≥64 on | Switch / pedal | | **CC67**67 | 0x43 | 01000011 | **Soft Pedal On/Off** | ≤63 off, ≥64 on | Switch / pedal | | **CC68**68 | 0x44 | 01000100 | **Legato Footswitch** | ≤63 Normal, ≥64 Legato | Switch / pedal | | **CC69**69 | 0x45 | 01000101 | **Hold 2** | ≤63 off, ≥64 on | Switch / pedal | | **CC70**70 | 0x46 | 01000110 | **Sound Controller 1 (default: Sound Variation)** | 0-127 | Sound controller | | **CC71**71 | 0x47 | 01000111 | **Sound Controller 2 (default: Timbre/Harmonic Intens.)** | 0-127 | Sound controller | | **CC72**72 | 0x48 | 01001000 | **Sound Controller 3 (default: Release Time)** | 0-127 | Sound controller | | **CC73**73 | 0x49 | 01001001 | **Sound Controller 4 (default: Attack Time)** | 0-127 | Sound controller | | **CC74**74 | 0x4A | 01001010 | **Sound Controller 5 (default: Brightness)** | 0-127 | Sound controller | | **CC75**75 | 0x4B | 01001011 | **Sound Controller 6 (default: Decay Time – see MMA RP-021)** | 0-127 | Sound controller | | **CC76**76 | 0x4C | 01001100 | **Sound Controller 7 (default: Vibrato Rate – see MMA RP-021)** | 0-127 | Sound controller | | **CC77**77 | 0x4D | 01001101 | **Sound Controller 8 (default: Vibrato Depth – see MMA RP-021)** | 0-127 | Sound controller | | **CC78**78 | 0x4E | 01001110 | **Sound Controller 9 (default: Vibrato Delay – see MMA RP-021)** | 0-127 | Sound controller | | **CC79**79 | 0x4F | 01001111 | **Sound Controller 10 (default undefined – see MMA RP-021)** | 0-127 | Sound controller | | **CC80**80 | 0x50 | 01010000 | **General Purpose Controller 5** | 0-127 | General-purpose control | | **CC81**81 | 0x51 | 01010001 | **General Purpose Controller 6** | 0-127 | General-purpose control | | **CC82**82 | 0x52 | 01010010 | **General Purpose Controller 7** | 0-127 | General-purpose control | | **CC83**83 | 0x53 | 01010011 | **General Purpose Controller 8** | 0-127 | General-purpose control | | **CC84**84 | 0x54 | 01010100 | **Portamento Control** | 0-127 | Portamento control | | **CC85**85 | 0x55 | 01010101 | **Undefined** | — | Undefined | | **CC86**86 | 0x56 | 01010110 | **Undefined** | — | Undefined | | **CC87**87 | 0x57 | 01010111 | **Undefined** | — | Undefined | | **CC88**88 | 0x58 | 01011000 | **High Resolution Velocity Prefix** | 0-127 | High-resolution velocity prefix | | **CC89**89 | 0x59 | 01011001 | **Undefined** | — | Undefined | | **CC90**90 | 0x5A | 01011010 | **Undefined** | — | Undefined | | **CC91**91 | 0x5B | 01011011 | **Effects 1 Depth (default: Reverb Send Level – see MMA RP-023) (formerly External Effects Depth)** | 0-127 | Effects control | | **CC92**92 | 0x5C | 01011100 | **Effects 2 Depth (formerly Tremolo Depth)** | 0-127 | Effects control | | **CC93**93 | 0x5D | 01011101 | **Effects 3 Depth (default: Chorus Send Level – see MMA RP-023) (formerly Chorus Depth)** | 0-127 | Effects control | | **CC94**94 | 0x5E | 01011110 | **Effects 4 Depth (formerly Celeste \[Detune\] Depth)** | 0-127 | Effects control | | **CC95**95 | 0x5F | 01011111 | **Effects 5 Depth (formerly Phaser Depth)** | 0-127 | Effects control | | **CC96**96 | 0x60 | 01100000 | **Data Increment (Data Entry +1) (see MMA RP-018)** | N/A | Data increment | | **CC97**97 | 0x61 | 01100001 | **Data Decrement (Data Entry -1) (see MMA RP-018)** | N/A | Data decrement | | **CC98**98 | 0x62 | 01100010 | **Non-Registered Parameter Number (NRPN) – LSB** | 0-127 | NRPN · LSB | | **CC99**99 | 0x63 | 01100011 | **Non-Registered Parameter Number (NRPN) – MSB** | 0-127 | NRPN · MSB | | **CC100**100 | 0x64 | 01100100 | **Registered Parameter Number (RPN) – LSB\*** | 0-127 | RPN · LSB | | **CC101**101 | 0x65 | 01100101 | **Registered Parameter Number (RPN) – MSB\*** | 0-127 | RPN · MSB | | **CC102**102 | 0x66 | 01100110 | **Undefined** | — | Undefined | | **CC103**103 | 0x67 | 01100111 | **Undefined** | — | Undefined | | **CC104**104 | 0x68 | 01101000 | **Undefined** | — | Undefined | | **CC105**105 | 0x69 | 01101001 | **Undefined** | — | Undefined | | **CC106**106 | 0x6A | 01101010 | **Undefined** | — | Undefined | | **CC107**107 | 0x6B | 01101011 | **Undefined** | — | Undefined | | **CC108**108 | 0x6C | 01101100 | **Undefined** | — | Undefined | | **CC109**109 | 0x6D | 01101101 | **Undefined** | — | Undefined | | **CC110**110 | 0x6E | 01101110 | **Undefined** | — | Undefined | | **CC111**111 | 0x6F | 01101111 | **Undefined** | — | Undefined | | **CC112**112 | 0x70 | 01110000 | **Undefined** | — | Undefined | | **CC113**113 | 0x71 | 01110001 | **Undefined** | — | Undefined | | **CC114**114 | 0x72 | 01110010 | **Undefined** | — | Undefined | | **CC115**115 | 0x73 | 01110011 | **Undefined** | — | Undefined | | **CC116**116 | 0x74 | 01110100 | **Undefined** | — | Undefined | | **CC117**117 | 0x75 | 01110101 | **Undefined** | — | Undefined | | **CC118**118 | 0x76 | 01110110 | **Undefined** | — | Undefined | | **CC119**119 | 0x77 | 01110111 | **Undefined** | — | Undefined | | **CC120**120 | 0x78 | 01111000 | **All Sound Off** | 0 | Channel Mode | | **CC121**121 | 0x79 | 01111001 | **Reset All Controllers (See MMA RP-015)** | 0 | Channel Mode | | **CC122**122 | 0x7A | 01111010 | **Local Control On/Off** | 0 off, 127 on | Channel Mode | | **CC123**123 | 0x7B | 01111011 | **All Notes Off** | 0 | Channel Mode | | **CC124**124 | 0x7C | 01111100 | **Omni Mode Off (+ all notes off)** | 0 | Channel Mode | | **CC125**125 | 0x7D | 01111101 | **Omni Mode On (+ all notes off)** | 0 | Channel Mode | | **CC126**126 | 0x7E | 01111110 | **Mono Mode On (+ poly off, + all notes off)** | Note: This equals the number of channels, or zero if the number of channels equals the number of voices in the receiver. | Channel Mode | | **CC127**127 | 0x7F | 01111111 | **Poly Mode On (+ mono off, +all notes off)** | 0 | Channel Mode | **Reference scope:** this is a musician-facing overview of MIDI 1.0 Control Change assignments. For product implementation work, use the full specification and the device manufacturer’s implementation chart. **Undefined does not mean universally free** An undefined number is unassigned in the standard table. A manufacturer can still use it for a product-specific function, and a controller preset can already map it. Check both ends of the connection before treating an undefined CC as conflict-free. ## What a Control Change message contains A MIDI 1.0 Control Change message identifies three things: the MIDI channel, the controller number and a value. The channel is encoded in the status byte; the two data bytes carry the CC number and its value. Standard data bytes stay in the 0–127 range, as shown in the [MIDI 1.0 message summary](https://midi.org/summary-of-midi-1-0-messages). ![MIDI Control Change message divided into channel, controller number and value, with paired MSB and LSB lanes](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/09/inline-midi-message-msb-lsb.webp) A standard Control Change message carries channel, controller number and value. Some defined controller pairs can combine an MSB and LSB for finer resolution when both devices support the pair. Status**1011nnnn**Control Change on channel n *→* Data byte 1**0ccccccc**Controller number, 0–127 *→* Data byte 2**0vvvvvvv**Controller value, 0–127 That distinction matters when a device appears to ignore a knob. The number may be correct while the transmitter and receiver are on different channels. A DAW may also remap the message before it reaches the instrument. ## MSB, LSB and optional 14-bit control CC0–31 form the most-significant-byte side of defined controller pairs, while CC32–63 carry the matching least-significant byte. For example, Channel Volume uses CC7 as the MSB and CC39 as its LSB partner. A receiver that implements both can interpret the pair as a finer value; a receiver that implements only the MSB still gets an ordinary 7-bit control. 7-bit path**CC7 = 96** One message gives one of 128 possible values. Paired path**CC7 = 96 + CC39 = 18** The defined MSB/LSB pair can express a finer combined value when the receiver supports it. Do not assume that every named MSB entry has active 14-bit support on every instrument. The table defines the pair; the receiving product’s implementation chart tells you whether it listens to both messages and in what order. ## Switch controllers and Sustain CC64 CC64 is the Damper Pedal or Sustain switch. Values 0–63 mean off and 64–127 mean on in the standard table. The same threshold pattern appears on several nearby switches. A pedal may send only 0 and 127, but intermediate values are still interpreted by the threshold unless the product documents a different or extended behavior. 0**Off**0–63 **64** 127**On**64–127 ## RPN and NRPN are sequences, not single controls Registered Parameter Number and Non-Registered Parameter Number messages use controller pairs to select a parameter, followed by Data Entry to change it. The official table defines RPN selection with CC101 and CC100, NRPN selection with CC99 and CC98, and Data Entry with CC6 plus optional CC38\. CC96 and CC97 increment or decrement the selected value. 1. **Select the parameter family.**Send CC101/100 for RPN or CC99/98 for NRPN. 2. **Choose the parameter number.**The MSB and LSB values identify the selected parameter. 3. **Send the value.**Use CC6 for Data Entry MSB and CC38 when the implementation accepts the LSB. 4. **Optionally clear the RPN selection.**For RPN, CC101 = 127 and CC100 = 127 is the documented null selection. The selected parameter can remain active, so a later Data Entry message may alter it unintentionally. That is why the null RPN step is useful in streams that continue carrying unrelated controller data. NRPN meanings are manufacturer-defined; use the product documentation for the parameter numbers. ## CC120–127 are Channel Mode messages The last eight numbers are reserved for channel-level behavior. Treating them as spare assignable knobs can create abrupt or confusing results. CC120**All Sound Off**0 CC121**Reset All Controllers (See MMA RP-015)**0 CC122**Local Control On/Off**0 off, 127 on CC123**All Notes Off**0 CC124**Omni Mode Off (+ all notes off)**0 CC125**Omni Mode On (+ all notes off)**0 CC126**Mono Mode On (+ poly off, + all notes off)**Note: This equals the number of channels, or zero if the number of channels equals the number of voices in the receiver. CC127**Poly Mode On (+ mono off, +all notes off)**0 ### All Sound Off versus All Notes Off **All Sound Off (CC120)** tells the receiver to silence sound promptly. **All Notes Off (CC123)** behaves like note releases, so a sustain state or an instrument’s release stage can allow sound to continue. The [official message summary](https://midi.org/summary-of-midi-1-0-messages) keeps these behaviors separate. If the goal is recovery from a stuck note, check sustain and controller state rather than assuming CC123 is an instant mute. ## Why a MIDI CC may not work **Wrong MIDI channel** The controller number can be right while the receiver listens on another channel. Confirm transmit, track and receive channels. **The receiver does not implement that CC** Standard assignments are not a promise that every product responds to every number. Check the manufacturer chart. **MIDI Learn or a remap changed the route** Software can translate, consume or reassign incoming controller messages before they reach the instrument. **Local Control creates a doubled path** With a keyboard connected through software, local sound plus returned MIDI can trigger the same instrument twice. Review Local Control and monitoring. **Sustain is still active** A note-off message can arrive correctly while CC64 remains on. Send sustain off and then resolve any remaining stuck-note state. **The message needs a sequence** RPN, NRPN, Bank Select and some high-resolution controls depend on ordered messages rather than one isolated CC. ## Use the device’s MIDI implementation chart The universal table tells you what a CC means in the MIDI 1.0 overview. It cannot tell you whether a specific synthesizer, pedal, controller or plug-in receives it. Search the product manual for “MIDI implementation,” then check: - the supported receive and transmit channels; - whether the CC is received, transmitted or both; - the documented value range and switch threshold; - whether MSB/LSB pairs, RPN or NRPN are supported; - any product-specific use of numbers marked undefined in the standard table. Bank Select is a good example. The standard uses CC0 and optional CC32 before Program Change, but bank numbering and byte requirements vary by product. The MIDI Association’s [message guide explains the standard mechanism](https://midi.org/about-midi-part-3midi-messages); the instrument manual supplies the actual bank map. ## Build the rest of the MIDI picture [**MIDI channels explained**Understand how one connection keeps parts and instruments separate.](https://soundforgepro.com/midi-channels-explained/) [**MIDI velocity explained**Separate note attack values from continuous controller messages.](https://soundforgepro.com/midi-velocity-explained/) [**MIDI aftertouch explained**See how pressure data differs from ordinary CC automation.](https://soundforgepro.com/midi-aftertouch-explained/) ### MIDI 1.0 vs MIDI 2.0: What Actually Changes URL: https://soundforgepro.com/midi-1-vs-midi-2/ Last updated: 2026-10-06T07:09:05.000Z **MIDI 2.0 builds on MIDI 1.0\. Its Channel Voice messages offer finer resolution and expanded control of individual notes. The broader MIDI 2.0 architecture also includes Universal MIDI Packet (UMP) and MIDI Capability Inquiry (MIDI-CI). These are separate pieces: UMP can carry either protocol, and MIDI-CI features can work with MIDI 1.0\. Before buying around any feature, check that the complete path from controller to destination supports it.** THE SHORT VERSION MIDI 1.0: broad compatibility Compact byte-stream messages, familiar channel architecture and broad support across existing equipment. MIDI 2.0 Protocol: finer performance data Higher-resolution Channel Voice messages and expanded per-note control, carried in UMP. Compatibility: designed to coexist Translation is a design priority, but not every MIDI 2.0 message has a MIDI 1.0 equivalent. Buying rule: check the complete path A logo on one product does not prove that the feature reaches your software or destination. ## MIDI 1.0 vs MIDI 2.0 at a glance | Layer | MIDI 1.0 | MIDI 2.0 | Why it matters | | ------------------- | ------------------------------------------------------- | ------------------------------------------------------------------------------ | ------------------------------------------------------------ | | Core role | Performance and control protocol | Extends the familiar musical model | Choose by the performance data you need | | Message packaging | Traditional byte stream or MIDI 1.0 messages in UMP | MIDI 2.0 Protocol messages in UMP | UMP itself does not identify the performance protocol | | Channel Voice data | Commonly 7-bit; defined 14-bit cases include Pitch Bend | 16-bit note/release velocity; relevant controller and pitch values use 32 bits | Useful resolution depends on the complete path | | Per-note expression | Includes polyphonic key pressure for individual notes | Adds per-note controllers and per-note pitch messages | MIDI 1.0 already has some note-specific expression | | Device discovery | MIDI-CI can work while using MIDI 1.0 Protocol | MIDI-CI is part of the broader architecture; UMP also has discovery mechanisms | Discovery and performance protocol are separate capabilities | | Configuration | Profiles and Property Exchange can work with MIDI 1.0 | Profiles and Property Exchange are included in the broader architecture | Check the exact Profile or supported resource at both ends | The MIDI Association’s [protocol specification](https://midi.org/universal-midi-packet-ump-and-midi-2-0-protocol-specification) distinguishes UMP from the messages it carries. Its [MIDI-CI documentation](https://midi.org/details-about-midi-2-0-midi-ci-profiles-and-property-exchange-updated-june-2023) confirms that Profiles and Property Exchange can operate with MIDI 1.0; the [MIDI 1.0 message summary](https://midi.org/summary-of-midi-1-0-messages) also defines polyphonic key pressure. The table separates performance messages from packet format and device configuration. A MIDI 2.0 label can cover different feature sets. Check the specific capability in the product documentation, then confirm support throughout your connection. ## MIDI 2.0 is an extension, not a reset The [MIDI Association’s current MIDI 2.0 overview](https://midi.org/midi-2-0) is explicit: MIDI 2.0 builds on MIDI 1.0 architecture and semantics rather than replacing them. Notes remain notes. Channels, controllers and program changes still describe recognizable musical jobs. That choice protects a huge installed base. A musician should not have to discard a dependable keyboard, sound module or controller because a newer protocol exists. Translation between MIDI 1.0 and MIDI 2.0 was given high priority in the design, so mixed systems are expected rather than treated as a temporary failure state. **A newer cable or a MIDI 2.0 label alone does not establish support for the feature you need.** Higher-resolution performance messages and automatic configuration solve different problems. A destination still needs to implement each feature it is expected to use. ## Universal MIDI Packet changes the container UMP is the common packet format at the center of modern MIDI transport. The official [Universal MIDI Packet and MIDI 2.0 Protocol specification page](https://midi.org/universal-midi-packet-ump-and-midi-2-0-protocol-specification) describes a format that can carry messages from both the MIDI 1.0 Protocol and the MIDI 2.0 Protocol and can be adapted to standardized or proprietary transports. 32bits 64bits 96bits 128bits **UMP message widths: 32, 64, 96 or 128 bits, depending on the message type.** These numbers describe the size of the UMP message. They do not mean every controller has 128-bit precision. The distinction matters because “128-bit MIDI” sounds more dramatic than the standard actually claims. According to the MIDI Association’s [February 2026 implementation overview](https://midi.org/the-state-of-midi-2-0-high-resolution-performance-and-the-rise-of-profiles-update-feb-2026), UMP messages are fixed multiples of a 32-bit word and may occupy 32, 64, 96 or 128 bits. The payload and meaning depend on the message type. ## Where MIDI 2.0 adds useful precision MIDI 1.0 Channel Voice messages commonly use 7-bit data, giving 128 possible values. [Defined exceptions include 14-bit Pitch Bend and paired controller messages](https://midi.org/the-state-of-midi-2-0-high-resolution-performance-and-the-rise-of-profiles-update-feb-2026). Resolution describes the available values; audible stepping also depends on the receiving instrument and its parameter handling. MIDI 2.0 extends the resolution of Channel Voice data. The same February 2026 official overview documents 16-bit [Note On velocity](https://soundforgepro.com/midi-velocity-explained/), 16-bit release velocity, 32-bit controller data and 32-bit pitch values in the relevant MIDI 2.0 messages. It also adds richer per-note control, so a gesture can affect one note rather than every note sharing a channel. NOTE AND RELEASE VELOCITY**16-bit** More values are available to describe attack and release data. CONTROLLER DATA**32-bit** Continuous controls can carry finer values when every stage preserves them. PITCH DATA**32-bit** Documented MIDI 2.0 pitch messages provide a much larger value space. PER-NOTE CONTROL**expanded** New messages target individual notes instead of treating the channel as one block. More numbers do not automatically produce a better performance. The instrument has to generate meaningful detail, the path has to preserve it and the destination has to use it. A high-resolution message translated into a MIDI 1.0-only section may be reduced to the closest representation available there. ## MIDI-CI, Profiles and Property Exchange solve different problems MIDI-CI discovers compatible devices and supports configuration features. Profiles define behavior; Property Exchange communicates documented resources. Neither requires the performance messages to use the MIDI 2.0 Protocol. 01 ### MIDI-CI discovers capabilities MIDI Capability Inquiry provides bidirectional discovery and configuration mechanisms. Compatible devices can establish shared support before using a Profile or exchanging properties. 02 ### Profiles define known behavior A Profile is a behavior contract for a device type or task. When both sides support the Profile, they can agree on a predictable response instead of relying entirely on manual mapping. 03 ### Property Exchange moves structured resources Property Exchange lets compatible devices inquire about, retrieve and set supported resources. These can describe configuration or device properties such as controller and patch names. Access depends on the resources and operations the device implements. The MIDI Association’s [MIDI-CI, Profiles and Property Exchange details](https://midi.org/details-about-midi-2-0-midi-ci-profiles-and-property-exchange-updated-june-2023) also records an important terminology change: the older MIDI-CI Protocol Negotiation mechanism was deprecated and replaced by protocol-selection mechanisms in the UMP architecture. A current guide should not present the older term as the active design. ## The weakest link sets the usable feature A MIDI connection is a chain, not a badge. Consider a controller sending high-resolution per-note data to an instrument inside music software. The feature may pass through several layers: ![Compatibility chain from MIDI controller through transport and host software to the destination instrument](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/09/inline-midi-compatibility-chain.webp) The usable MIDI 2.0 feature depends on support across the full path; translation can preserve compatible data but cannot invent an unavailable equivalent. 1**Controller or device**generates the required MIDI 2.0 performance message. 2**Transport**carries that message in UMP. 3**OS or host**exposes the message to the music software. 4**Music software**preserves the required data while recording, routing or processing it. 5**Destination**interprets the data and applies the supported control. If one stage supports only MIDI 1.0, translation may keep notes, ordinary controllers and other shared semantics moving. A MIDI 2.0-only per-note message with no MIDI 1.0 equivalent cannot survive unchanged through that section. This is why compatibility and full feature preservation are two different claims. ## What happens in a mixed MIDI 1.0 and MIDI 2.0 setup? A mixed setup can remain completely useful. The expected behavior falls into three broad cases: **Shared meaning exists** The message can be translated, possibly with lower resolution. Notes and common performance data are the obvious examples. **A defined capability is missing** Use the documented fallback or common feature set supported by both products. Do not assume that a Profile or property is available when one side does not expose it; discovery cannot add missing support. **No MIDI 1.0 equivalent exists** The unique MIDI 2.0 behavior may be dropped, simplified or unavailable across the MIDI 1.0-only section. A mixed connection can preserve useful musical data while losing detail that has no equivalent in the older protocol. Check the translation and routing behavior documented for the products in that path. ## How to decide whether MIDI 2.0 matters for your setup Start with the job. “MIDI 2.0 support” is too broad to guide a purchase because one product may support UMP transport, another may add Profiles, and another may expose high-resolution Channel Voice data. 1 **Name the feature** High-resolution velocity, per-note control, a specific Profile, Property Exchange or another documented capability. 2 **Check both endpoints** Confirm that the sending and receiving products document the same feature, not just generic MIDI 2.0 compatibility. 3 **Check the middle** Verify the transport, operating system or host and music software preserve that message or capability. 4 **Find the translation point** If part of the chain is MIDI 1.0-only, determine what remains equivalent and what is reduced or unavailable. 5 **Read dated support notes** Implementation changes. Use current first-party documentation for each product before buying around one promised workflow. I would pay for MIDI 2.0 because a documented feature solves a real control problem, not because the number is newer. A stable MIDI 1.0 path remains the better choice when it already carries everything the workflow needs. ## Four claims to treat carefully ### “MIDI 2.0 gear makes MIDI 1.0 obsolete” The standard was designed as an extension with translation compatibility. Existing equipment can remain useful inside a mixed chain. ### “UMP means every control is 128-bit” UMP supports several message widths. Packet size and the resolution of one musical value are separate facts. ### “One MIDI 2.0 device upgrades the studio” The required feature has to survive the controller, transport, host, software and destination path. ### “Backward compatible means lossless translation” Shared semantics can be translated. A MIDI 2.0 message with no MIDI 1.0 equivalent cannot be preserved unchanged. ## Which protocol should you use? Use MIDI 1.0 when it already supports the performance data and routing you need. Choose MIDI 2.0 Protocol support for a documented requirement such as finer velocity resolution or expanded per-note control, with support across the full path. If the benefit you want is a Profile or Property Exchange, check that capability separately. It can work with MIDI 1.0, so you may not need to change the performance protocol. ### MIDI Channels Explained: Ports, Tracks and the 16-Channel Limit URL: https://soundforgepro.com/midi-channels-explained/ Last updated: 2026-10-02T07:02:42.000Z **MIDI 1.0 provides 16 logical channels per port. Software usually displays them as channels 1 through 16, while the four-bit channel field in a Channel Message status byte uses values 0 through 15\. Each independent MIDI port has its own set of 16\. A DAW track can listen to one channel, every channel or a routed combination, so the limit does not mean 16 tracks or 16 devices for your entire setup.** MIDI CHANNELS AT A GLANCE **Addresses per port**16Displayed as channels 1–16 **Encoded values**0–15Four bits inside a Channel Message status byte **System Messages**No channel fieldThey follow a different message scope **DAW tracks**Separate layerA track chooses what port and channel to hear ## What “16 MIDI channels” actually means A channel is a logical address inside one MIDI 1.0 data path. It lets a receiver separate messages that travel through the same port. A keyboard part can use channel 1, a bass part channel 2 and a drum instrument another channel while all three message streams share one connection. The important boundary is *per port*. The [MIDI Association’s guide to MIDI messages](https://midi.org/about-midi-part-3midi-messages) describes 16 logical channels for Channel Messages. Add a second independent MIDI port and you add another channel namespace: port B channel 1 is distinct from port A channel 1. **Use the complete address.** “Channel 4” is incomplete when several ports exist. “Interface port B, channel 4” identifies the actual route. This is why the familiar number 16 is easy to misread. It is not a universal ceiling for a studio, a song or a computer. It describes the address space available inside one MIDI 1.0 port or equivalent stream context. ## How the channel number fits inside a MIDI 1.0 message A MIDI 1.0 Channel Message’s status byte identifies its message type and channel. The upper four bits identify the message type and the lower four bits carry the channel value. The official [MIDI 1.0 message summary](https://midi.org/summary-of-midi-1-0-messages) writes the channel field as `nnnn`. Message type**1001**Example: Note On + Channel field**nnnn**Binary value 0000–1111 \= Status byte**1001nnnn**Message type and address together Four bits can represent 16 values: decimal 0 through 15\. Interfaces translate those values into the friendlier labels 1 through 16\. That offset explains why technical tables may show zero-based values even though a controller display says channel 1. The channel number travels with Channel Voice messages such as Note On, Note Off, Control Change, Program Change, [Channel Pressure](https://soundforgepro.com/midi-aftertouch-explained/) and Pitch Bend. This allows one port to carry independent performance data for several receiving parts. ## Channel Messages and System Messages use different scopes Not every MIDI 1.0 message belongs to a channel. The [MIDI Association’s message summary](https://midi.org/summary-of-midi-1-0-messages) separates Channel Messages from System Messages. System Messages do not contain a channel number in their status byte. CHANNEL MESSAGE**Addressed to one channel** Notes, controllers and other performance data can be separated by the four-bit channel field. SYSTEM MESSAGE**No channel number** Timing, synchronization, system-exclusive data and related functions use their own scopes and formats. This difference matters when troubleshooting. Changing a track from channel 1 to channel 2 can redirect notes and controllers, but it does not turn a channel-independent System Message into channel 2 data. The two categories solve different addressing problems. ## Port, channel and DAW track are three separate layers Most routing confusion comes from collapsing these layers into one word. Keep them separate: 1 **Port** The physical or virtual path. It defines which set of 16 channel addresses you are using. 2 **Channel** The address carried by a Channel Message inside that port. 3 **DAW track** A software container that decides which port and channel input it accepts and where the result goes. The [MIDI Association’s connection overview](https://midi.org/midi-connections) covers the transport and connection layer. A current first-party DAW example makes the software layer visible: the [Ableton Live routing manual](https://www.ableton.com/en/live-manual/12/routing-and-i-o/) documents separate input-type and input-channel selectors, including individual channels and an all-channels choice. The exact controls vary among DAWs, but the distinction remains useful. ![Diagram showing two MIDI ports with separate channel sets feeding selectively routed DAW tracks](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/09/inline-port-channel-track.webp) Each port has its own channel set; DAW tracks decide which port and channel combinations to receive. ## A practical two-port example Imagine an interface with two independent MIDI inputs. A keyboard enters port A on channel 1\. A pad controller enters port B on channel 1\. The channel numbers match, but the complete addresses do not. PORT A · CH 1**Keyboard performance** Track 1 listens only to this address and plays a piano instrument. PORT B · CH 1**Pad performance** Track 2 listens only to this address and plays a percussion instrument. ALL PORTS · ALL CHANNELS**Broad input** Track 3 would hear both controllers unless another filter or routing rule separates them. The first two routes use different complete addresses because the port is part of the address. In this example, an overly broad track input or the wrong port or channel selection can still send the performance to the wrong destination. My recommendation is to name the source as **port + channel**, then name the destination track before adding more complex routing. That description can expose a missing selection or an accidental “all inputs” setting. ## When “all channels” helps—and when it hides a mistake An all-channels input is useful when one controller is the only source on a port, when a performance intentionally spans several channels or when you need to confirm that messages are arriving at all. It removes one filter from the path. It becomes risky when several controllers share the accepted input path. A track listening to everything may trigger from the wrong keyboard, duplicate a performance on two instruments or make a channel assignment look irrelevant. If broadening the input produces activity at the relevant input meter, that is evidence that messages reach that point; changing a selector alone proves nothing. Once you have identified the source, restore the intended port and channel selection. **Use one channel**For a defined controller-to-instrument route **Use all channels temporarily**To check for an input-channel filter while watching the relevant activity meter **Use several channels intentionally**For multitimbral or expressive workflows with a documented channel plan ## Four channel myths that cause bad routing decisions ### “One channel equals one physical device” A channel is an address. One device may use several channels, and several receivers can be configured to respond to the same channel. ### “A MIDI track consumes one of the 16 channels” A track is a container and routing decision inside software. Many tracks can listen to the same incoming channel, and one track may accept more than one channel. ### “Channel 1 is always the first byte value” User interfaces label the first channel as 1, while the four-bit field encodes it as value 0\. The display label and encoded value use different counting conventions. ### “A MIDI system can only address 16 parts” The sixteen-address set belongs to one port. Multiple independent ports provide multiple sets, as long as the sender, receiver and software preserve the port distinction. ## DAW-neutral MIDI channel troubleshooting ### The activity meter moves, but the instrument stays silent Confirm the track is listening to the source’s exact port and channel. Then check the destination instrument and monitoring state. A visible message only proves that data reached the point where the meter sits. ### The wrong instrument plays Look for a track set to all ports or all channels. Also check whether two tracks are armed or monitored from the same address. ### Changing the channel does nothing The receiving track may accept every channel, or the receiver may be configured to ignore channel separation. Narrow the input first, then change one channel assignment at a time. ### Two devices on channel 1 interfere Check their ports before changing channel numbers. If they use separate ports, they already have separate complete addresses. If they share one port, assign deliberate channels or filters. ### Only one part of a multitimbral instrument responds Match each part’s receive channel to the transmitting route. Verify that the correct port reaches the device and that no software layer merges or rewrites channels. ### Notes work, but synchronization behaves differently Determine whether the missing data is a Channel Message or a System Message. Channel selection cannot repair a message that has no channel field. ## What should you remember? MIDI 1.0 gives each port 16 logical channel addresses. Channel Messages carry the address in four bits of the status byte, while System Messages do not use a channel number. Ports, channels and DAW tracks remain separate layers. Once you describe a route as **source port → channel → destination track**, the 16-channel limit becomes a clear addressing rule instead of an arbitrary restriction. ### MIDI Aftertouch Explained: Channel, Polyphonic and MPE URL: https://soundforgepro.com/midi-aftertouch-explained/ Last updated: 2026-10-06T07:24:13.000Z **MIDI aftertouch is pressure data produced after the initial key strike, while a key or pad is still held. It can apply one pressure value to an entire [MIDI channel](https://soundforgepro.com/midi-channels-explained/) or address pressure to individual notes. Nothing audible happens until the receiving instrument maps that data to a destination such as vibrato, filter movement or level.** AFTERTOUCH AT A GLANCE **When it happens**After the attackPressure changes while the note remains held **Two MIDI 1.0 forms**Channel or per-noteThe message determines how pressure is addressed **Possible destinations**Vibrato, tone, levelThe patch chooses what pressure changes **Required path**End-to-end supportController, transport, receiver and mapping all matter ## Aftertouch starts where velocity stops [Velocity](https://soundforgepro.com/midi-velocity-explained/) describes the attack gesture that begins a note. Aftertouch describes continued pressure after that attack. The simplest way to hear the distinction is to imagine one sustained synth note: 1. 01 **Strike the key** The Note On message carries the note number and its velocity. 2. 02 **Hold the note** The note continues without needing a new Note On event. 3. 03 **Apply more pressure** A pressure message can change while the note is already sounding. 4. 04 **Release the key** Releasing the key sends a Note Off message. This is separate from the pressure messages sent while the key is held. This timing makes aftertouch useful for shaping a sustained sound without moving a wheel, pedal or knob. It does not replace velocity. A performer can strike a note softly, then increase pressure to bring in vibrato or brightness after the tone begins. **Attack and pressure are separate gestures.** Velocity tells the instrument how the note begins. Aftertouch gives the instrument changing pressure information during the held portion of the note. ## Channel Pressure and Polyphonic Key Pressure The [MIDI Association’s guide to MIDI messages](https://midi.org/about-midi-part-3midi-messages) separates two pressure-message types. They differ in what the pressure value addresses, not merely in how sensitive the keyboard feels. | Message | Addressing | Data carried | Musical consequence | | --------------------------- | ------------------------------ | ------------------------------- | -------------------------------------------------------------------------------------- | | **Channel Pressure** | One value for the MIDI channel | Pressure value | Held notes on that channel generally receive the same pressure control at the receiver | | **Polyphonic Key Pressure** | A specific note | Note number plus pressure value | One held note can carry a different pressure value from another | The official [MIDI 1.0 message summary](https://midi.org/summary-of-midi-1-0-messages) shows the structural difference clearly: Polyphonic Key Pressure includes both a key number and a pressure amount, while Channel Pressure carries a single pressure data value. The summary recommends sending the greatest pressure value among the currently depressed keys as Channel Pressure. It is not an average, and the message contains no note number. ![Infographic comparing pressure timing and note addressing for Channel Pressure, Polyphonic Key Pressure and MPE](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/09/inline-midi-aftertouch-addressing.webp) Pressure begins after the attack; the message architecture determines whether it addresses a channel, a note number or a separate channel used for MPE expression. Channel Pressure and Polyphonic Key Pressure are dedicated MIDI messages, not [MIDI CC numbers](https://soundforgepro.com/midi-cc-chart/). In the MIDI Association’s message guide, Control Change carries a controller number and a control value; the two pressure-message types use their own message formats. ## Where MPE fits—and where it does not MPE can also provide per-note pressure, but it reaches that result through a different architecture. The [MIDI Association’s MPE specification overview](https://midi.org/mpe-midi-polyphonic-expression) explains that MIDI Polyphonic Expression assigns individual MIDI 1.0 channels to notes so each note can receive its own pitch, timbre and pressure-related expression. CHANNEL PRESSURE**One channel, one pressure stream** The pressure message carries one value for the channel and does not identify an individual note. POLY KEY PRESSURE**Note number inside the pressure message** Pressure can be addressed directly to a particular note while notes share a MIDI channel. MPE**Separate channels for independent expression** Per-note expression comes from channel allocation and a coordinated set of messages. These mechanisms can serve similar musical goals, yet they are not interchangeable names. A controller may support polyphonic aftertouch without operating as an MPE controller. An MPE performance may carry per-note pressure through channel-based messages rather than Polyphonic Key Pressure. Compatibility depends on what the controller sends and what the receiving instrument understands. ## What can aftertouch control? Aftertouch is a source of modulation, not a fixed sound command. The instrument or patch decides the destination and the response curve. Common choices include: - **Vibrato depth**Increasing pressure can introduce or intensify pitch modulation after the note starts. - **Filter movement**Pressure can brighten or darken a sustained sound without retriggering it. - **Amplitude**A patch can use pressure to swell a note, although pressure does not contain a universal gain value. - **Timbre or wavetable position**Pressure can move through tonal states or layers when the sound engine exposes a suitable destination. - **Effect amount**Pressure can change an effect parameter where the instrument exposes that route. Per-note pressure does not guarantee independent effect control for each note. Check whether the destination belongs to one voice or the whole sound. The [Surge XT manual’s explanation of voice and scene modulation](https://surge-synthesizer.github.io/manual-xt/#voice-vs-scene-modulators) gives a concrete example: a voice modulator can control filter cutoff for each voice, but cannot control shared scene parameters such as FX levels. Its [pressure-source definitions](https://surge-synthesizer.github.io/manual-xt/#voice-and-note-properties) classify Poly AT as a voice modulator; Channel AT operates at scene level with MPE disabled and at voice level in MPE mode. These are Surge XT’s documented limits, so check the equivalent routing rules in your own instrument. I prefer one clearly audible destination before adding a second. If pressure opens a filter, increases vibrato and raises level at once, it becomes hard to tell whether the gesture is expressive or simply unstable. Start with a modest range, then add another destination only when it solves a musical need. ## The full path from finger pressure to sound Aftertouch can appear to “do nothing” even when one part of the setup supports it. The entire chain has to preserve and interpret the data: 1**Controller sensing** The keybed or pad must measure pressure after the initial strike. *→* 2**MIDI message** The controller must transmit Channel Pressure, Polyphonic Key Pressure or an MPE-compatible stream. *→* 3**Transport and routing** The connection and software path must pass the message without filtering or remapping it incorrectly. *→* 4**Receiver mapping** The instrument must recognize the incoming data and assign it to a destination. *→* 5**Audible response** The chosen patch needs enough modulation depth for the listener to hear the change. That sequence is more useful than asking whether a keyboard or synth “has aftertouch” in isolation. A controller can send pressure that a patch ignores. A compatible instrument can wait for a message that the controller never produces. Notes passing through a route do not prove that pressure survives it. For example, the [Midihub Filter documentation](https://blokas.io/midihub/docs/filter/) lists Channel Pressure and Poly Aftertouch among the event types it can discard independently of Note On and Note Off. Check any event filters between the controller and instrument. ## How to choose a controller or patch Product pages often use the word *aftertouch* without making the scope obvious. Before buying or configuring anything, check five details: 1. **Which pressure type does the controller send?**Look for explicit wording: Channel Pressure, Polyphonic Key Pressure, polyphonic aftertouch or MPE. A generic “aftertouch” label may not answer the question. 2. **Which keys or pads sense it?**Some products apply pressure sensing to a keyboard, others to pads, and some to both. Confirm the playing surface you plan to use. 3. **Can the receiver read the same form?**A patch that accepts Channel Pressure is not automatically a polyphonic-pressure destination, and the reverse is also true. 4. **Is pressure already mapped?**Preset designers may leave aftertouch unassigned. Support in the instrument does not guarantee that every preset uses it. 5. **Can you shape the response?**A curve, threshold or modulation-depth control can matter more in practice than a long list of possible destinations. A controller’s pressure settings can also belong to a particular playing surface. In the [Launchkey 37 settings documented by Novation](https://userguides.novationmusic.com/hc/en-gb/articles/27612201863186-Launchkey-37-Settings), Pad Aftertouch can be Off, Channel or Poly, while Pad AT Threshold sets when pressure begins to register on the pads. The key and pad velocity curves are separate settings. A velocity-curve option therefore does not tell you whether held pressure can be adjusted. For a monophonic lead or a pad where every held note should swell together, Channel Pressure may be enough. If you want to lean on one note inside a chord while the others remain stable, you need a genuinely per-note route such as Polyphonic Key Pressure or a compatible MPE path. ## DAW-neutral aftertouch troubleshooting ### Notes play, but pressure changes nothing Confirm that the patch maps the received pressure source to an audible destination. Increase the modulation depth temporarily so a subtle mapping cannot hide the result. ### Every held note changes together The setup may be using Channel Pressure. Check the controller’s transmitted message and the receiver’s expected source before assuming per-note pressure is broken. ### Only some presets respond The instrument may support pressure globally while individual patches use different mappings. Compare modulation assignments rather than treating preset behavior as a hardware test. ### Pressure appears in a monitor but not in the instrument The data reaches the monitor, but that does not confirm the route from the monitor to the instrument. Check downstream filters and routing, then receiver support, message type, channel arrangement and the patch’s modulation matrix. ### The response jumps too quickly Reduce modulation depth or adjust the pressure curve where the controller or instrument allows it. Change one stage at a time so stacked curves do not obscure the cause. ### MPE mode makes routing confusing Remember that MPE coordinates multiple channels. Check the documented zone and channel arrangement for the controller and receiver rather than treating it like one ordinary channel. ## What should you remember? Aftertouch is a second gesture that begins after the note attack. Channel Pressure sends one pressure stream for a channel. Polyphonic Key Pressure addresses a note number. MPE creates per-note expression by assigning notes to separate channels. Whichever route you use, the data becomes musical only when the controller, message path, receiver and patch agree on what pressure should do. ### MIDI Velocity Explained: What the Numbers Actually Control URL: https://soundforgepro.com/midi-velocity-explained/ Last updated: 2026-10-02T07:02:21.000Z **MIDI velocity is a value carried with a note event. It describes the force or speed of the playing gesture, but it does not define one fixed loudness. The receiving instrument decides whether that value changes level, brightness, sample layers, attack or some combination of them.** VELOCITY IN ONE MINUTE **Attached to**An individual noteEach note can carry its own attack value **MIDI 1.0 field**7-bit dataNote On attacks use 1–127; 0 means Note Off **Common result**Dynamic and tonal changeThe instrument chooses the actual response **Not the same as**Channel volumeVolume, expression and aftertouch use separate messages ## The useful mental model: gesture → value → response Velocity becomes much easier to understand when you keep three stages separate: 1. 01 **Gesture** A performer strikes a key, pad or drum surface, or an editor enters a value for a note. 2. 02 **MIDI value** The note message carries a number representing that attack gesture. 3. 03 **Instrument response** The receiving sound engine maps the number to amplitude, timbre, samples, envelopes or another destination. The middle stage is standardized data. The last stage is an implementation choice. That distinction explains why copying the same velocity values between two instruments can produce a performance that feels very different. ![Diagram showing a playing gesture becoming a MIDI velocity value and then an instrument response curve](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/09/inline-midi-velocity-response.webp) A performance gesture creates a MIDI value; the receiving instrument decides how that value becomes sound. ## What Note On and Note Off velocity carry The [MIDI Association’s message guide](https://midi.org/about-midi-part-3midi-messages) describes note activation and release as separate events. A MIDI 1.0 Note On message carries the note number and a velocity field. A Note Off message also carries the note number and a release-velocity field. | Message | When it occurs | Velocity describes | Typical use | | ------------ | -------------------- | ------------------- | ------------------------------------------------------------------------- | | **Note On** | The note begins | The attack gesture | Level, tone, sample layer or envelope response | | **Note Off** | The note is released | The release gesture | Often ignored, but available to instruments that support release response | The official [MIDI 1.0 message summary](https://midi.org/summary-of-midi-1-0-messages) writes both velocity fields as seven-bit data. Many editors show that range in decimal form. The number is precise as protocol data, yet its audible meaning still depends on the patch receiving it. In MIDI 1.0, Note On velocity 0 means Note Off for that note and channel. It is not an extra-soft attack; use values 1–127 for a note onset. The MIDI Association’s [technical discussion](https://midi.org/community/midi-specifications/zero-velocity-note-on) quotes this rule from the specification, and JUCE’s [MIDI message documentation](https://docs.juce.com/master/classjuce%5F1%5F1MidiMessage.html) treats zero-velocity Note On as a note-off by default. This exception concerns MIDI 1.0 Note On, not the separate release-velocity field. ## Why velocity is not simply volume Velocity is commonly mapped to note amplitude, so the shortcut “higher velocity means louder” often works as a first approximation. It breaks down as soon as an instrument also changes tone or articulation. A sampled piano may switch or blend between recordings made at different playing intensities. A synthesizer may open a filter, shorten an attack or increase modulation depth. A drum instrument may use the value to select a different hit character. These are examples of possible mappings, not rules imposed by the MIDI note message. **The number belongs to the note. The sound belongs to the instrument.** Velocity tells the receiver about the gesture. It does not contain a decibel target, a fixed gain change or a universal instruction for timbre. There is no universal conversion from a velocity value to decibels. This variation is measurable. Roger Dannenberg’s paper [The Interpretation of MIDI Velocity](https://www.cs.cmu.edu/~rbd/papers/velocity-icmc2006.pdf) compared several synthesizers and found materially different velocity-to-amplitude behavior, with still wider differences among piano implementations. The measurements are historical examples rather than current product rankings, but they establish the point: one velocity number does not imply one acoustic result. ## What a velocity response curve changes A response curve maps incoming velocity to an instrument’s internal response. “Linear,” “soft” and “hard” labels are common ideas, but their exact behavior is not universal. Think about the shape rather than trusting the name. ### Even response Input changes are spread more evenly across the available output range. This is the clearest starting point, not an objective reference for every patch. ### Early response Lower input values reach more of the instrument’s response sooner. It can help a light touch reach a stronger response, but leaves less room for fine control at the quiet end. ### Late response More input is required before the response rises strongly. It can preserve extra room near the quiet end for a player with a firm touch. A curve can sit in the controller, the DAW, the instrument or more than one place. Stacked curves can exaggerate or compress the result, so change one layer at a time. My practical rule is to solve the mismatch at the earliest reliable point that serves the whole setup. If only one patch behaves badly, adjust that instrument rather than reshaping every performance globally. ## Velocity vs volume, expression and aftertouch These controls can all affect dynamics, but they describe different actions. Treating them as substitutes usually produces flat or unpredictable edits. | Control | Scope | When it acts | Use it for | | ------------------------ | ------------------ | ------------------------------------ | ------------------------------------------------------------------------------ | | **Note velocity** | Individual note | At attack or release | The character and dynamic intent of each note | | **Channel Volume (CC7)** | MIDI channel | As a separate Control Change message | Overall channel-level control supported by the receiver | | **Expression (CC11)** | MIDI channel | As a separate continuous controller | Ongoing expressive movement where the instrument maps it appropriately | | **Aftertouch** | Per key or channel | While held keys are pressed further | Sustained pressure-based modulation supported by the controller and instrument | The current [MIDI 1.0 Control Change table](https://midi.org/midi-1-0-control-change-messages) assigns Channel Volume to CC7 and Expression Controller to CC11\. Aftertouch belongs to Polyphonic Key Pressure or Channel Pressure messages, as the MIDI message guide explains. None of these assignments forces one gain relationship or sound destination; the receiver’s implementation still matters. Our [MIDI CC chart](https://soundforgepro.com/midi-cc-chart/) is the broader controller-number reference, while this page stays focused on note velocity. ## MIDI 1.0 and MIDI 2.0 velocity resolution MIDI 1.0 uses a seven-bit velocity field. [MIDI 2.0](https://soundforgepro.com/midi-1-vs-midi-2/) expands Note On velocity and release velocity to 16-bit values, from 0 to 65,535, according to the MIDI Association’s [2026 high-resolution performance overview](https://midi.org/the-state-of-midi-2-0-high-resolution-performance-and-the-rise-of-profiles-update-feb-2026). **MIDI 1.0**7-bit velocity fieldA compact range that remains the common reference in editors and hardware **MIDI 2.0**16-bit note and release velocityFiner protocol resolution when every part of the path supports and uses it More numerical steps do not guarantee a more expressive sound. The controller must capture useful detail, the message path must preserve it, and the instrument must map it meaningfully. A coarse or insensitive response curve can still waste high-resolution input. ## A DAW-neutral way to edit velocity 1. **Choose the instrument first.**Velocity edits only make sense against the patch that will interpret them. Changing instruments can change the musical effect of the same values. 2. **Listen for a musical problem.**Identify notes that jump out, disappear or trigger the wrong articulation. Do not start by making the lane look tidy. 3. **Edit relationships before numbers.**Decide which notes should lead, support or recede. Adjust their relative shape instead of chasing a universal target value. 4. **Preserve useful variation.**Repeated notes with identical values may sound mechanical on a responsive instrument, but random values are not automatically human. Keep accents tied to phrasing. 5. **Check the response curve.**If a large range of incoming values produces almost no change—or too much change—fix the mapping before rewriting every note. 6. **Compare at the same listening level.**If the edit makes the passage louder overall, reduce monitoring bias before deciding that it is better. ## When velocity seems to do nothing ### Every note sounds equally loud The patch may ignore velocity, use a narrow response range or route it mainly to timbre. Check the instrument’s modulation and response settings. ### Small value changes feel extreme The response curve may be too steep for the controller or performance. Test a gentler curve before compressing the entire note lane. ### The tone changes more than the level That may be intentional. Some instruments use velocity to select brighter layers, change filter response or alter attack behavior. ### Edits work on one patch but fail on another If the same values reach both instruments, their different mappings can explain the changed result. If the values change along the way, inspect routing or velocity processing first. Rebalance for the destination patch. ## What should you remember? Velocity is per-note performance data, not a universal volume command. Edit it to shape accents, dynamics and articulation, then judge the result through the instrument that will actually play the notes. If the response feels wrong across the whole performance, inspect the curve or mapping before forcing every value into a new pattern. ### Parametric EQ vs Graphic EQ: Which One Should You Use? URL: https://soundforgepro.com/parametric-eq-vs-graphic-eq/ Last updated: 2026-10-08T13:38:25.000Z **Choose a graphic EQ when you want fast, repeatable control over a fixed set of frequency bands. Choose a parametric EQ when you need to place a band at a specific frequency and control how wide or narrow the adjustment is.** Neither design is automatically better sounding. The useful difference is how the controls let you solve the problem in front of you. CHOOSE BY THE MOVE YOU NEED **Fast broad shaping**Graphic EQFixed bands make the overall curve easy to read and repeat **Narrow resonance**Parametric EQPlace a band on the problem and adjust its width **System or venue tuning**Graphic EQMany fixed bands support visible, repeatable correction **Detailed mix correction**Parametric EQFrequency, gain and Q provide focused control with fewer bands ## Parametric EQ vs graphic EQ at a glance | Difference | Graphic EQ | Parametric EQ | | -------------------- | -------------------------------------------------------------------------------------------- | -------------------------------------------------------- | | **Band position** | Fixed center frequencies | Adjustable center frequency | | **Main controls** | Gain for each fixed band | Frequency, gain and Q or bandwidth for each band | | **Fastest use** | Broad, visible shaping across many preset bands | Targeting a known frequency or creating a specific curve | | **Typical strength** | Repeatable system, live and pedal adjustments | Detailed corrective and creative work | | **Main limitation** | The exact frequency you want may fall between bands | More decisions per band can slow down simple shaping | | **Quality verdict** | The category does not determine sound quality; filter design and implementation still matter | | The fixed-versus-adjustable distinction is the cleanest definition. [Yamaha’s current console documentation](https://manual.yamaha.com/pa/mixers/dm7/rm/en-US/8365295627.html) describes graphic EQ modes with fixed one-third-octave bands, while its separate parametric mode uses a different control structure. A current [dbx 31-band graphic equalizer](https://dbxpro.com/en/products/231s) is another clear hardware example: the bank of sliders makes the whole correction curve visible at once. ## What changes when frequency, gain and Q are adjustable? A parametric band normally gives you three linked decisions: - **Frequency** chooses where the band acts. - **Gain** sets how much that area is boosted or cut. - **Q or bandwidth** controls how narrowly or broadly the adjustment spreads around the selected frequency. The [FabFilter Pro-Q band-control documentation](https://www.fabfilter.com/help/pro-q/using/bandcontrols) shows these controls separately and also shows why “parametric” does not describe one universal feature set: filter shapes, slopes, dynamic behavior and range depend on the product. [A higher Q generally makes a bell filter narrower](https://docs.tokyodawn.net/nova-manual/), while a lower Q makes it broader. I would keep that explanation qualitative unless the filter type and implementation are known; one numerical conversion is not safe for every equalizer. ![Diagram comparing fixed graphic EQ bands with adjustable parametric EQ frequency, gain and bandwidth controls](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/10/inline-parametric-vs-graphic-eq-controls-v20261006.webp) Graphic EQ divides the spectrum into fixed bands. Parametric EQ lets each band move to a chosen frequency and change its gain and width. A graphic EQ reduces those choices. Each slider already belongs to a marked center frequency, so the immediate question is how much to raise or lower it. That makes a graphic layout quick to scan and easy to reproduce from a note or photograph. It also means a narrow problem may sit between two available centers, forcing you to share the move across adjacent bands or accept a wider correction. ## Where a graphic EQ is the better tool 01 ### Broad tonal shaping If the job is “less low-mid weight” or “a little more presence,” fixed neighboring sliders make the shape obvious. You can build a smooth contour without choosing a fresh center frequency for every move. 02 ### Repeatable live adjustments A fixed bank is easy to document and recall. The same slider always refers to the same marked band, which is useful when several operators need to understand the setting quickly. 03 ### System and venue tuning One-third-octave layouts remain practical when the task is to see and adjust many standardized bands across the audible range. The control surface communicates the overall correction immediately. 04 ### Pedal and compact hardware use A row of fixed bands can be faster under performance conditions than selecting a band, frequency and Q through shared knobs or menus. “Fixed” does not mean random or crude. The bands can be closely spaced, the gain range can be carefully chosen, and the filters can be well designed. The limitation is placement flexibility, not an automatic lack of quality. ## Where a parametric EQ is the better tool ### Finding a narrow resonance When the problem is concentrated around a specific frequency, adjustable placement is the decisive advantage. You can move one band onto the resonance, choose a narrow enough bandwidth and reduce it without pulling a large neighboring region down with it. A [spectrum analyzer](https://soundforgepro.com/audio-spectrum-analyzer/) can help locate persistent energy, but the graph should start an investigation rather than make the EQ decision for you. ### Making broad musical moves with fewer bands Parametric does not mean narrow. A low-Q bell can cover a broad region, and shelf filters can reshape the ends of the spectrum. One adjustable band may create the curve that would require several fixed graphic bands. The tradeoff is that you must choose the shape and width rather than simply move the nearest slider. ### Working around neighboring material Adjustable bandwidth gives you more control over what stays outside the move. That matters when a harsh resonance sits close to useful presence, or when low-mid buildup must be reduced without thinning the whole source. The separate [Sound Forge equalizer guide](https://soundforgepro.com/how-to-use-equalizer-sound-forge-pro/) handles the software-specific workflow; this comparison stays with the general decision. ## Why more bands do not automatically mean better sound Band count tells you how many controls are available, but those controls do different jobs in the two designs. Thirty-one fixed bands provide a detailed map of predetermined points. Four adjustable parametric bands can be placed wherever the source needs them. Neither number is a quality score. **Do not compare “31 bands” with “4 bands” as if they were the same unit.** A graphic band gives gain control at a fixed center. A parametric band usually gives placement, gain and width. Count controls only after you compare what each control can do. More controls can even make a poor decision harder to see. A jagged graphic curve may introduce several adjacent changes when one broad move would have worked. A parametric EQ can create the opposite problem: a screen full of narrow notches that treats every analyzer peak as a defect. Use the fewest moves that solve an audible, repeatable problem. ## The product matters as much as the category name Two equalizers in the same category can behave differently. Product documentation may specify different gain ranges, frequency limits, Q behavior, filter shapes, slopes, phase response, channel modes and analysis features. The current [Image-Line reference for Fruity Parametric EQ 2](https://www.image-line.com/fl-studio-learning/fl-studio-online-manual/html/plugins/Fruity%20Parametric%20EQ%202.htm), for example, documents selectable filter shapes and adjustable band width in that particular implementation. Those details are evidence of variation, not universal requirements for every parametric EQ. The same caution applies to graphic equalizers. A 15-band model, a 31-band model and a compact pedal may offer different spacing or gain ranges; band count alone does not tell you either. Check the actual center frequencies, adjustment range and channel format before deciding that the label alone fits the job. ## A neutral workflow for choosing the EQ 1. **Name the move.** Is it a broad tonal preference, a narrow resonance, a repeatable system curve or a quick performance adjustment? 2. **Choose the control model.** Use fixed bands when speed and repeatability dominate. Use adjustable frequency and Q when placement and width dominate. 3. **Start broad.** Make the smallest simple move that addresses the problem before adding narrow corrections. 4. **Level-match the result.** [Compare at similar perceived loudness](https://docs.tokyodawn.net/nova-manual/) so a level change does not distract from the tonal decision; adjust output gain or use a documented loudness-compensated bypass. 5. **Bypass and simplify.** If several bands do not survive a fair before-and-after check, remove them rather than defending the curve. ## Which EQ should you choose? **Choose graphic EQ for:** broad visible shaping, standardized system correction, repeatable live settings and fast hardware or pedal adjustments. **Choose parametric EQ for:** specific resonances, controlled bandwidth, detailed mix correction and curves that need adjustable placement. **Use both when:** a stable graphic curve handles the room or system while a parametric EQ addresses a small number of source-specific problems. **Choose neither by reputation:** read the actual control range and filter options, then match them to the task. Category and band count do not guarantee the result. If you remember one distinction, make it this: graphic EQ gives you many fixed places to work; parametric EQ lets you choose the place and width of each move. Pick the one that makes the needed correction easier to understand and easier to undo. ### Compressor vs Limiter: Which One Should You Use? URL: https://soundforgepro.com/compressor-vs-limiter/ Last updated: 2026-10-06T07:31:29.000Z **Choose a compressor when you want to shape how a sound moves from quiet to loud. Choose a limiter when the immediate job is to restrain peaks and set a maximum output level. Use both when you need both jobs: broad dynamic control first, then a last line of peak control. A limiter is related to compression, but an infinite ratio alone does not turn every compressor into a dependable brickwall limiter.** SHAPE THE MOVEMENT**Compressor** Bring loud passages closer to quieter ones, change the envelope of hits or control an uneven performance. RESTRAIN THE PEAKS**Limiter** Catch occasional high transients or keep the output under a chosen ceiling. DO BOTH JOBS**Compressor → limiter** Let compression handle the broader level changes; ask the limiter to manage what remains. ## The difference is the job, not just the ratio A downward compressor begins reducing gain when its detector sees a signal above a threshold. The ratio describes how the level above that threshold is changed. At 4:1, for example, a sustained 4 dB increase at the detector corresponds to roughly 1 dB of output increase in the idealized, settled transfer curve. Real compressors also depend on attack, release, knee, detector and design. The [FabFilter compressor control reference](https://www.fabfilter.com/help/pro-c/using/dynamicscontrols) explains the threshold and ratio relationship; its [design notes](https://www.fabfilter.com/help/pro-c/using/styleandcharacter) show why matching numbers on different compressors need not produce the same response. A limiter also reduces gain, but the practical goal is usually to keep peaks within a maximum output range. A dedicated peak limiter can use lookahead and an output ceiling to act on brief transients before they escape. [FabFilter's limiter documentation](https://www.fabfilter.com/help/pro-l) describes peak limiting and output-level control as its central jobs. Neither category is a promise of a particular sound: a compressor can control peaks, and a limiter can audibly change the envelope when it works hard. ![Compressor and limiter waveforms showing broad level control and brief peak restraint below a ceiling](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/09/inline-compressor-vs-limiter.webp) A compressor shapes a longer swell; a limiter restrains short peaks under a chosen ceiling. | Decision | Compressor | Limiter | | ------------------- | ---------------------------------------------------- | -------------------------------------------------------------------------------- | | Main aim | Shape the dynamic range and envelope | Restrain peaks and control maximum output | | Typical controls | Threshold, ratio, attack, release and knee | Input/drive, output ceiling, release and often lookahead or true-peak options | | What to watch | How phrases and transients feel after gain reduction | How often peaks trigger reduction and whether the result distorts or loses punch | | Poor substitute for | A guaranteed final output ceiling from ratio alone | Repairing an uneven performance or upstream clipping | ## What the controls change **Threshold** decides when the detector asks for gain reduction. **Ratio** changes the transfer relationship above that point. A higher ratio generally restrains level increases more strongly, but it does not say how quickly the processor acts. **Knee** changes how gradually compression begins around the threshold. Those controls describe the static transfer behavior more than the whole listening result. **Attack** affects how quickly reduction engages, while **release** affects recovery afterward. A slower attack may allow the front of a hit through; a very fast one can alter it. Release that recovers poorly for the source can make the level move in a way you did not intend. The [FabFilter time-control guide](https://www.fabfilter.com/help/pro-c/using/timecontrols) documents those response stages and explains that lookahead anticipates peaks by adding latency. No millisecond value works for every source or processor. That is why “limiter = compressor at infinity ratio” is incomplete. Infinity ratio describes an idealized transfer slope after the detector and timing have done their work. A compressor with a nonzero attack may let a transient pass before full reduction takes hold. A dedicated brickwall limiter is designed around the additional problem of peak containment, often with lookahead and a defined ceiling. Use the actual processor's documented behavior and meters, not its category label, to decide whether it can meet a delivery constraint. ## Which one should you reach for? ### The loud phrases jump out, but the track has no dangerous spikes Start with a compressor. Listen to whether the phrases sit more consistently and whether the transient character still suits the part. Adjust the threshold and timing for the source; do not add a limiter just because one is available. ### The balance feels right, but a few peaks exceed the output you need Start with a limiter. Check whether it catches only those peaks or has to stay in gain reduction much of the time. If it is doing extensive work, the level or dynamics earlier in the chain may need attention. ### The performance moves widely and still has sharp peaks Try a compressor for the broader movement, then a limiter for the remaining peaks. This is a division of work, not a rule that every mix or master needs two processors. ### The source has already clipped during recording Neither processor restores the lost waveform automatically. Lowering a clipped signal before a limiter reduces its level, but the clipped shape remains. Find the overload point in the recording or earlier signal path instead. I would make the choice from the problem I can describe. “This vocal disappears between phrases” points toward dynamic shaping. “The output occasionally crosses the intended ceiling” points toward peak containment. “Make it louder” is too vague: more level can come at the cost of transient shape, distortion or fatigue, so decide which tradeoff is acceptable before adding gain. ## When a compressor and limiter share a chain A practical starting arrangement is **source → compressor → limiter → output**. The compressor changes the longer movement you want to control; the limiter catches peaks that still reach the end of the chain. The arrangement is an editorial starting point, not a manufacturer-prescribed order for every mix. 1. **Set levels before either processor.** A limiter at the end cannot undo distortion introduced earlier. 2. **Use the compressor to solve a musical problem.** Listen for consistency, groove and transient shape, not just a gain-reduction number. 3. **Put the limiter on the remaining peak problem.** Set an output ceiling appropriate to the actual destination, then inspect when and how often it acts. 4. **Compare at sensible playback levels.** A louder version can seem more exciting even if it has lost the movement you meant to keep. Some chains need only one processor; others need a different order for a deliberate sound. A limiter before compression can be a specific effect or an upstream safety stage, but it changes what the following compressor receives. Treat the sequence as a reasoned choice, not an inherited preset. ## What true-peak limiting adds A stored digital sample peak is not always the highest level produced when the signal is reconstructed. A true-peak limiter estimates potential inter-sample peaks and can reduce them before output. [FabFilter's true-peak explanation](https://www.fabfilter.com/help/pro-l/using/truepeaklimiting) describes oversampled peak detection and why reconstructed peaks matter. True-peak mode lowers a particular downstream clipping risk; it is not a guarantee for every encoder, sample-rate conversion or playback chain. Nor does it fix distortion already baked into a recording. If you have a specified delivery ceiling, check the current requirements for that destination. The [streaming loudness and true-peak guide](https://soundforgepro.com/streaming-loudness-standards/) covers the platform-specific questions; do not copy a generic number from someone else's master. ## Four mistakes that make the choice harder - **Judging only by ratio.** Timing, detector, knee and lookahead can matter as much as the transfer slope. - **Using a limiter to level every phrase.** It may restrain the tallest moments without making the whole performance feel controlled. - **Pushing a ceiling without checking the chain.** Output limiting cannot repair earlier clipping or bad gain staging. - **Equating more loudness with a better result.** Listen for punch, distortion and how the quieter passages relate to the loud ones. If you need instructions for a particular device, keep the same decision but follow that program's documentation for its controls. A generic answer about dynamic shaping should not pretend that Fruity Limiter, Logic Compressor and Live's devices share the same interface or behavior. ## The short decision Use a compressor to shape dynamic movement, a limiter to contain peaks, and both only when the signal presents both problems. Check the actual response in context. The name and ratio tell you what the processor is built to attempt; its timing and design determine what happens to the sound. ### What Is a VST Plugin? Instruments, Effects and Compatibility URL: https://soundforgepro.com/what-is-a-vst-plugin/ Last updated: 2026-10-02T07:01:50.000Z **A VST plug-in is a piece of audio software that runs inside a compatible host, usually a digital audio workstation (DAW). It can generate sound, change sound, or do both. The host handles the session and routes signals; the plug-in performs its particular job.** Think of a synthesizer playing notes from a MIDI track or a compressor shaping a recorded vocal. Both can be VST plug-ins, although they take different kinds of input. VST stands for Virtual Studio Technology. It names an interface between a host and a plug-in, not a sound style or a guarantee that a download will work on your computer. [Steinberg's VST developer documentation describes](https://steinbergmedia.github.io/vst3%5Fdev%5Fportal/pages/What%2Bis%2BVST/Index.html) the host–plug-in exchange of audio, events, inputs, outputs and parameters. You do not have to learn its software specification to use a plug-in, but that division of jobs clears up most beginner confusion. ## What does the host do? The host is the application that loads the plug-in. In a DAW, it manages the timeline and places the plug-in on a track or in a signal chain. Other compatible hosts may have no timeline or tracks, but they still supply the appropriate inputs and handle the result. A plug-in exposes controls and processes what it receives. A virtual instrument can use note events to produce audio; an effect usually takes audio in and sends processed audio back. HOST**DAW or compatible audio app**Inputs · routing · output → INSTRUMENT**Notes in · sound out** → EFFECT**Audio in · changed audio out** The host supplies the context and routes the output. Instruments and effects do different jobs within that relationship. This is a simplified signal-flow picture. A real product may accept several kinds of data or combine instrument and effect functions. The distinction I would remember is the responsibility: the host runs the session, while the plug-in contributes a sound source or a processing stage. ## VST instrument or VST effect? ### Instrument A synthesizer, [sampler](https://soundforgepro.com/sampler-software/) or drum instrument responds to performance data and produces audio. Put one on a track when you need a sound source. An instrument may also process an incoming signal, so check the individual product rather than treating the label as a rigid technical limit. ### Effect An EQ, compressor, reverb or delay changes audio from a microphone, instrument or another plug-in. Put one where the sound already exists and needs shaping. Different effects take and return different channel layouts. When you browse a shop or a host's plug-in list, ask a more useful question than “Is this a VST?”: *Am I looking for a sound source or a way to process one?* [Image-Line also distinguishes instruments and effects](https://www.image-line.com/fl-studio-learning/fl-studio-online-manual/html/basics%5Fexternalplugins.htm) in its documentation, although its instructions for discovering them apply specifically to FL Studio. ## Is every plug-in a VST? No. “Plug-in” is the broad word for software added to a host; “VST” names one audio plug-in interface. A host can support other interfaces, and a software company may supply the same named product in several formats. The format tells you how a particular build communicates with a host. It does not tell you whether the product is a synth, an EQ or something else. The file you download and the format your host can load have to match. Renaming an extension cannot make a build for another plug-in interface, operating system or processor work. If an unfamiliar format appears on a product page, check your host's supported formats and the developer's downloads before assuming that the product name alone is enough. ## What is VST 3, and does it sound better? VST 3 is a newer version of the VST interface. [Steinberg lists capabilities](https://steinbergmedia.github.io/vst3%5Fdev%5Fportal/pages/Main%2Bbenefits%2Bof%2BVST%2B3/Index.html) such as dynamic I/O, sample-accurate automation and note expression in its VST 3 documentation. Those are possibilities in the interface, not a promise that every host or every plug-in implements each one. Steinberg also describes VST 3 as an interface redesigned from VST 2, rather than a file you can turn into VST 3 by changing its name. I would not choose between two products by the numeral alone. A format version is not a measurement of sound quality. Check the exact plug-in version, the features you need and what your host supports. A developer may offer different builds under one product name, and an older project may depend on a particular installed build. ## How do I know whether a VST will work? Before downloading, line up four things: 1. **Operating system.** Look for the correct Windows, macOS or Linux build, if the developer offers one for your system. 2. **Processor architecture and version.** Check what the developer requires and whether your host can load that build. A product name can cover different binaries. 3. **Format and host support.** Confirm that your host accepts the delivered VST version. Do not assume every DAW accepts every plug-in format. 4. **Authorization and installation method.** Check the developer's license requirements and installer instructions. Finding a file on disk is not the same as successfully loading an authorized plug-in. Steinberg documents [standard VST 3 plug-in locations](https://steinbergmedia.github.io/vst3%5Fdev%5Fportal/pages/Technical%2BDocumentation/Locations%2BFormat/Plugin%2BLocations.html), but the presence of a file in a standard folder is only one part of the story. The host still needs to support the build and discover it. If your task is actually to find an installed plug-in in FL Studio, use the [FL Studio plug-in database guide](https://flstudiopro.com/fl-studio-plugin-database/); that is a different, host-specific problem. For a plug-in that fails to appear in Sound Forge Pro, see the [Sound Forge Pro plug-in troubleshooting guide](https://soundforgepro.com/sound-forge-pro-vst-plugins-not-showing/). ## Three shortcuts that lead people astray “VST means virtual instrument.” An instrument can be a VST, but effects can be VST plug-ins too. “The same plug-in name means the same file everywhere.” A vendor may ship different platform or format builds. Match the actual download to your host and system. “VST 3 automatically sounds better than VST 2.” The interface describes how software communicates with its host. It does not certify the quality of the developer's processing. If you remember one thing, make it the signal path: **the host loads and routes; the plug-in generates or processes**. Once you know whether you need an instrument or an effect, compatibility becomes a concrete check instead of a guess based on the word “VST.” ### Audio Interface vs Mixer: Which Recording Path Do You Need? URL: https://soundforgepro.com/audio-interface-vs-mixer/ Last updated: 2026-10-09T21:04:49.000Z **Choose an audio interface if you mainly need separate computer tracks and a straightforward recording path. Choose a mixer if you need hands-on control of several sources in a room, on stage or during a stream.** A USB mixer can do both jobs, but its channel strips do not tell you how many independent tracks the computer can record. That last number is the one I would check before buying anything. ## The difference that changes your recording An interface takes audio into and out of a computer. Depending on the model, it combines microphone preamps, instrument or line inputs, conversion, headphone and speaker outputs, and monitoring controls; [Audient's iD14 specifications](https://audient.com/products/audio-interfaces/id14/overview/) show one current arrangement, including digital expansion. A mixer gives you a physical place to set levels and build a mix from several sources, with channel controls and routing that vary by model. [Yamaha's MG series description](https://usa.yamaha.com/products/proaudio/mixers/mg%5Fseries%5Fxu%5Fmodel/index.html) shows how those controls are organized on an analog console. These categories overlap. Some mixers also include a USB audio interface. The useful question is not “Which box sounds better?” but “Where does each microphone or instrument go, and what reaches the recording software separately?” Neither category name guarantees better sound or [lower latency](https://soundforgepro.com/audio-latency-calculator/). __Choose by the job, then verify the exact model__ | Your priority | Start with | Check before buying | | ------------------------------------------------------- | ---------------------------- | ----------------------------------------------------------------------------- | | Record one or two sources and edit each later | Audio interface | Simultaneous analog inputs, preamp and instrument modes, headphone monitoring | | Mix several sources by hand or work without a computer | Mixer | Input types, aux/monitor outputs, physical controls, standalone operation | | Mix live and keep each source on its own computer track | Multitrack USB mixer | Actual USB send count, source selection and pre/post-fader tap | | Capture only the finished stereo mix | Stereo USB mixer may suffice | Whether the USB pair carries the main mix you intend to record | ## Ten channel strips do not mean ten recording tracks Here is the trap. A mixer can accept several microphones and instruments, blend them to a stereo bus and send only that left/right pair over USB. You hear every source, but the recording contains the blend rather than the singer’s original isolated channel; later source separation is not the same as having recorded a clean individual track. Yamaha lists the [MG10XU USB audio connection as 2-in/2-out](https://usa.yamaha.com/files/download/other%5Fassets/2/1507032/MG10XU%5Ftechnical%5Fspecifications%5FEn%5FB0.pdf) even though it has more than two physical mixer inputs. A multitrack mixer can instead send multiple independent channels to the computer. The [Allen & Heath ZEDi-10FX technical sheet](https://www.allen-heath.com/content/uploads/2023/06/ZEDi-10FX-Technical-Datasheet.pdf) specifies a 4-in/4-out USB interface. Its USB source selection still matters: four USB paths do not mean that every physical socket can always appear as a separate track at once. Mackie's [Onyx family](https://mackie.com/en/products/mixers/onyx-series) offers multitrack USB recording, but the channel count and routing depend on the model. Read the routing diagram for the specific unit, not the family headline. Think of the paths this way: 1. **Interface:** microphone → preamp and conversion → its own computer input and track. 2. **Stereo USB mixer:** several channel strips → a combined stereo mix → a left/right computer recording. 3. **Multitrack USB mixer:** several channel strips → selected independent USB sends → separate computer tracks, subject to that model's routing. These are simplified signal paths, not universal wiring diagrams. A mixer may offer both individual sends and a stereo mix; an interface may have its own software or hardware mixer. The manual decides which path is available. ## Four situations that make the choice clearer ### Voice, guitar or a small overdub setup If you record one part at a time, or a voice and instrument simultaneously, I would begin with an interface that has the required preamp and instrument inputs. Count sources recorded in the *same take*, not everything permanently plugged into the room. If the count is unclear, work through [how many audio interface inputs you need](https://soundforgepro.com/how-many-inputs-audio-interface/); the number alone will not tell you whether the device supplies the right input types. ### Rehearsal, live sound or a stream with several people A mixer makes sense when someone needs to reach for channel levels, mute a source, or feed a separate monitor or auxiliary mix while the session is happening. Yamaha's [MG model table](https://usa.yamaha.com/products/proaudio/mixers/mg%5Fseries%5Fxu%5Fmodel/specs.html) shows why the exact layout matters: auxiliary sends, groups and USB capability differ even within one family. If you also want a recording, decide whether the final stereo mix is enough or whether you need every source separately afterward. ### A band whose takes need separate editing later Count the microphones and direct inputs needed at once, then require that many independent recording channels to reach the computer. A console with plenty of physical inputs but only stereo USB capture does not solve that editing task. A multitrack USB mixer or an interface with enough simultaneous inputs can; compare the channel-by-channel routing and monitor feeds of the actual candidates. ### Recording without a computer Do not assume “USB mixer” means standalone recording. A conventional analog mixer can make a live mix without a laptop, but it may not store the audio. The [Mackie Onyx owner’s manual](https://mackie.com/img/file%5Fresources/Onyx%5FSeries%5FOM.pdf) makes the distinction clear: Onyx16 can record multiple tracks to a computer via USB, while direct recording to an SD card captures a stereo mix. Confirm the recording medium, number of stored tracks and supported file format for the exact model you are considering. ## The questions I would put beside two candidate models - **How many sources must be recorded in the same take?** Separate microphone, line and instrument needs; a stereo source normally needs two analog channels. - **How many independent channels go *from the device to the computer*?** The USB “in” and “out” labels may use the device's viewpoint. Find the routing table and identify the sends to recording software. - **Can I choose what each USB channel carries?** Check whether it sends an individual input, a group, an aux mix or the main stereo bus. - **Where is the USB tap in relation to gain, EQ and fader?** A pre-fader send and a post-fader send behave differently if you move a control during a take; do not assume a console fader changes the recorded track. - **Who needs a separate headphone or monitor mix?** Count independent feeds, not just headphone sockets. Check what can be routed to each. - **Will it work in the way you need without a computer?** Distinguish live mixing from onboard recording, and confirm driver and operating-system support if computer recording matters. My rule is simple: buy for the signal path you need on your hardest realistic session. An interface is often the tidy answer for separate tracks; a mixer is the ergonomic answer for live control; a hybrid earns its place only when its actual USB sends and monitoring cover both jobs. The model's routing diagram matters more than the word printed on the box. ### What Is Phantom Power? When to Use 48V URL: https://soundforgepro.com/what-is-phantom-power/ Last updated: 2026-10-06T07:20:41.000Z **Phantom power is a DC supply sent through a balanced microphone connection, usually from an interface, mixer or recorder. The switch is commonly marked `48V` or `P48`. Turn it on when the connected microphone or active device requires that power; do not use it as a substitute for gain.** **Turn P48 on**For an XLR condenser microphone or another device whose manual explicitly requires phantom power. **Leave P48 off**For USB microphones, most moving-coil dynamic microphones and any device with a different or unknown power requirement. **Stop and check**For passive ribbon microphones, adapters, unbalanced connections or a grouped phantom switch that also feeds other inputs. ## What does the 48V switch do? It supplies a small DC current to the microphone through the same balanced XLR connection that carries the audio signal. In the common P48 arrangement, the two signal conductors receive [equal positive voltage relative to the cable shield](https://service.shure.com/articles/en%5FUS/Knowledge/what-is-phantom-power), as Shure explains. The audio remains a differential signal while the power rides on the connection as common-mode DC. `48V` describes the nominal system. It does not mean every microphone input delivers exactly 48.000 volts under every load, and it does not mean every device that uses an XLR plug expects P48\. Read the microphone and input manuals when the model is unfamiliar. **Pin 1**shield / reference **Pin 2**audio + DC feed **Pin 3**audio + DC feed ## Which microphones need phantom power? Many studio condenser microphones use phantom power for their internal active electronics. Neumann explains how [an impedance converter buffers the capsule’s output](https://www.neumann.com/en-us/knowledge-base/neumann-im-homestudio/homestudio-academy/what-is-a-condenser-microphone), and why tube condensers use a dedicated power supply. Other microphones can use batteries or low-voltage plug-in power. Check the model rather than assuming every condenser takes P48. Swipe sideways to read the model checks → | Device | P48 decision | What to check | | ------------------------------- | ----------------------- | ------------------------------------------------------------------------------------------------------------------------------------------ | | XLR condenser microphone | Usually on | Confirm the model's required voltage and whether it accepts the input's phantom range. | | Active ribbon microphone | Often required | Follow the microphone manual. Active ribbons are not the same as passive ribbons. | | Passive ribbon microphone | Use caution | Keep P48 off unless the manufacturer explicitly says the model is safe with it; connection faults and unsuitable adapters change the risk. | | Moving-coil dynamic microphone | Usually off | A correctly wired balanced model normally does not need phantom power. It still does not gain sensitivity when P48 is enabled. | | USB microphone | Not applicable | An XLR input’s P48 switch is not a power setting for a USB connection. Follow the microphone’s specified connection method. | | 3.5 mm lavalier or electret mic | Not the same system | Many use low-voltage plug-in power. The input or adapter must provide the method the microphone specifies. | | DI box | Model-dependent | Some active DI boxes require phantom power; passive DIs generally do not. Check the exact unit. | | Inline preamp | Often required upstream | Some inline gain devices draw phantom power from the interface while passing the microphone signal onward. | For a concrete active-ribbon example, the [Royer R-122 MKII specifies 48-volt phantom power](https://royerlabs.com/r-122-mkii/). A ribbon capsule alone does not tell you whether to enable the switch. DI boxes differ in the same way: the [Radial J48 runs on 48V phantom power](https://www.radialeng.com/product/j48), while the [passive Radial JDI needs no power](https://www.radialeng.com/product/jdi). Read the requirement for the unit you are connecting. An inline booster can also change the answer. The [Cloudlifter CL-1](https://cloudmicrophones.com/products/cloudlifter-cl-1) uses 48V but does not pass phantom power to the microphone. Enabling P48 powers the booster; it does not supply a downstream condenser that needs phantom power. For a passive ribbon, check both the model and the connection. [Neumann recommends keeping phantom power off for ribbons](https://www.neumann.com/en-us/knowledge-base/neumann-im-homestudio/homestudio-academy/how-to-connect-your-microphone-to-an-audio-interface) because faulty connections and hot-plugging can put them at risk. A familiar XLR plug is not a guarantee of safe wiring. ## Phantom power is different from gain, plug-in power and USB power **Phantom power** DC supplied through a balanced professional microphone connection, commonly the nominal 48 V P48 system. **Plug-in power** RØDE describes [plug-in power, also called bias power](https://rode.com/en-us/about/news-info/audio-for-film-101-a-guide-to-powering-your-video-mic), as a low-voltage supply for compatible 3.5 mm microphones. It is not interchangeable with P48. **USB connection** An interface’s XLR phantom switch does not control a separate [USB microphone](https://soundforgepro.com/usb-vs-xlr-microphone/). Follow that microphone’s connection and power instructions. **Gain** Amplification in the preamp or input stage. Raising gain makes a signal larger; enabling phantom power only supplies a device that needs it. If a dynamic microphone is quiet, switching on phantom power is not the fix. Check the input type, cable, distance, preamp gain and whether the source needs an inline preamp. Power and gain solve different problems. ## How to switch phantom power safely I recommend checking the power requirement before adjusting gain. It avoids chasing a level problem while the microphone’s electronics are still unpowered. For an unfamiliar microphone, use the following conservative connection sequence. Follow any model-specific instructions first; [Yamaha’s AG08 manual](https://manual.yamaha.com/pa/live%5Fstreaming/ag08/en-US/10042095499.html), for example, requires the affected channel faders to be at minimum when switching phantom power: 1. **Turn P48 off.** If the switch is grouped, check which other inputs will lose or receive phantom power. 2. **Turn the input gain, monitor and headphone levels down.** This reduces the chance of a connection pop reaching speakers or ears. 3. **Connect the microphone with a suitable cable.** Avoid improvised adapters and damaged or unbalanced wiring. 4. **Enable P48 if the microphone requires it.** Once the connection settles, bring input gain and monitor level up gradually. 5. **Before disconnecting, mute or lower the monitoring path and switch P48 off.** [Neumann advises connecting with P48 off](https://www.neumann.com/en-us/knowledge-base/neumann-im-homestudio/homestudio-academy/how-to-connect-your-microphone-to-an-audio-interface) and warns against hot-plugging while it is on. If your equipment manual specifies a wait time, follow it before unplugging. This sequence reduces avoidable pops and makes the power decision visible. It cannot repair a faulty cable, a damaged input or an incompatible adapter. ## Can one 48V switch affect more than one input? [Neumann notes that phantom switches may be individual or shared](https://www.neumann.com/en-us/knowledge-base/neumann-im-homestudio/homestudio-academy/how-to-connect-your-microphone-to-an-audio-interface). For a specific shared-switch example, the [Yamaha AG08 manual](https://manual.yamaha.com/pa/live%5Fstreaming/ag08/en-US/10042095499.html) says its switch feeds channels 1 and 2\. A shared switch matters when one of those inputs is connected to a passive ribbon, a device with a different power requirement or an adapter. Check the exact inputs controlled by your own unit before enabling P48. Look at the labels beside the switch and the manual for the exact unit. If you cannot confirm which channels are tied together, leave P48 off until you know what is connected to every affected input. ## What the common symptoms mean **No signal after enabling P48** The microphone may need a different power method, the cable may be faulty, the input may be set to the wrong source or the device may not be connected to a compatible XLR preamp. **Crackle or intermittent audio** Stop and inspect the cable, adapter and connector. Do not keep toggling phantom power while a poor connection is in the chain. **A loud pop** Lower monitoring levels, mute the output and use the connection sequence above. A pop alone does not identify the failed part. **A passive ribbon is connected** Switch P48 off, check the model manual and inspect the entire path before reconnecting. Some [ribbon microphones](https://soundforgepro.com/best-budget-ribbon-microphones/) are designed to tolerate phantom power; others require more caution. **The mic is still quiet** Phantom power does not add preamp gain. Set an appropriate gain level or use a compatible inline preamp if the microphone and input require one. **The device expects another voltage** Do not substitute P48\. Use the power supply or interface specified by the manufacturer. ## Can phantom power damage a dynamic microphone? Shure explains that [equal DC voltage on the two signal conductors](https://service.shure.com/articles/en%5FUS/Knowledge/what-is-phantom-power) leaves a balanced dynamic microphone unaffected. This assumes correct wiring. A wiring fault, an unbalanced adapter, a damaged connector or an unusual microphone design can change the situation. Leaving P48 off when the microphone does not need it is still the sensible default. [Passive ribbon microphones](https://soundforgepro.com/ribbon-vs-condenser-microphone/) deserve a separate decision. Neumann distinguishes properly wired connections from the risks of faults and hot-plugging for delicate ribbon elements. The exact microphone, wiring and connection method matter. If the manual does not clearly approve phantom power, keep it off. If the microphone still has no level, work through the signal path and gain staging; the [SoundForgePro microphone test](https://soundforgepro.com/microphone-test/) can help you inspect input level and clipping after the connection is known to be compatible. ### USB vs XLR Microphone: Which Setup Should You Buy? URL: https://soundforgepro.com/usb-vs-xlr-microphone/ Last updated: 2026-10-02T07:01:19.000Z **Choose USB when you need one microphone that connects directly to your computer with the fewest separate parts. Choose XLR when you need several microphones or sources at once, or want to choose and replace the microphone and interface independently.** Neither plug guarantees better sound. The room, mic, placement, gain and rest of the signal path still matter. **One voice, simple desk**Start with a USB mic whose headphone monitoring and host compatibility meet your needs. **Two people or more sources**Start with XLR mics and an interface or recorder with enough simultaneous microphone inputs. ## What actually changes in the recording chain? **USB microphone**Voice → microphone capsule → built-in preamp and conversion → USB → computer **XLR microphone**Voice → microphone capsule → XLR cable → compatible preamp and conversion → computer or recorder A USB mic sends digital audio to a compatible host; its conversion takes place inside the mic. A typical XLR mic sends an analog signal to an [interface, mixer or recorder](https://soundforgepro.com/audio-interface-vs-mixer/) that supplies the required input and, for computer recording, conversion. [RØDE's connection guide lays out both paths](https://rode.com/en-us/about/news-info/xlr-vs-usb-microphones-which-is-better-for-you). Some recorders and cameras have suitable XLR inputs already, so a separate desktop interface is not always required. USB and XLR describe a connection, not whether a microphone uses a dynamic or condenser capsule. They also do not describe how a voice will sound. Compare actual microphones and the complete chain, not just the connector on the back. ## USB vs XLR at a glance Swipe sideways to compare the XLR column → | Question | USB microphone | XLR microphone | | -------------------------- | ----------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------ | | What do you connect? | A compatible computer or mobile host, usually with one USB cable. | A compatible XLR input on an interface, mixer or recorder, then the recording device as needed. | | What is included? | Preamp and conversion are built into the mic. Headphone output, mute and gain controls depend on the model. | Choose the microphone and external input/conversion equipment separately; controls depend on that equipment. | | One person? | Usually the shorter equipment list. | Useful if you already have an interface or want a modular setup. | | Several simultaneous mics? | Possible in some software and host setups, but combining independent digital devices takes extra care. | A multi-input interface or recorder gives the mics one recording system and a clear input count. | | Future changes? | Replacing the mic may also replace its integrated preamp and conversion. | Change the mic or the interface independently, subject to input and power compatibility. | ## Does XLR sound better? No connector can repair a noisy room, poor placement or clipping. XLR gives you more control over the external chain, but that flexibility is not an audible upgrade by itself. A well-chosen USB microphone can suit a voice better than an ill-chosen XLR mic plugged into an expensive interface. I would choose the mic for the source and room first, then decide which connection gets it into the recording system with the controls I need. There are microphones with both outputs. RØDE lists both XLR and USB connectivity for the [NT1 5th Generation](https://rode.com/en-us/microphones/studio/nt1-5th-generation), which makes the distinction particularly clear: the capsule can be the same while the downstream path changes. That example does not prove the two outputs will produce identical files or that either connection is inherently superior. ## Compare the complete kit, not the microphone price Build a checkout list for each route before deciding which one is cheaper. Do not put an XLR mic's price beside a complete USB mic and call it a fair comparison. Swipe sideways to compare the full kit → | Item | USB route | XLR route | | ------------------------- | ---------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------- | | Microphone | USB mic | XLR mic | | Cable and host connection | USB cable; adapter only if the host requires one | XLR cable; interface/recorder connection to the host if recording there | | Input and conversion | Inside the mic | Compatible interface, mixer or recorder; check the number and type of inputs | | Monitoring | Headphones and a monitoring route supported by the mic or host | Headphones and a suitable interface/recorder monitoring route | | Shared accessories | Stand or arm, pop filter where needed, headphones and room treatment as the job requires | | If you already own an interface with a free mic input, XLR may require fewer new purchases than the table first suggests. If you are starting from an empty desk with one voice, USB often removes the interface purchase. Prices and included cables vary by model, so use the actual basket rather than a fixed dollar rule. ## Check how you will hear yourself Before ordering a USB mic, verify whether the exact model has a headphone jack, whether it can mix live input with computer playback, and where its gain and mute controls live. A mic without the monitoring route you want may be awkward even if its recording sounds good. RØDE notes that these controls are [present on many USB models, not all of them](https://rode.com/en-us/about/news-info/xlr-vs-usb-microphones-which-is-better-for-you). For XLR, look at the interface or recorder instead: headphone output, direct-monitor controls, enough independent headphone mixes for your session, and appropriate inputs for the microphones. For example, RØDE lists a headphone output and direct monitoring on its [AI-1 interface](https://edge.rode.com/pdf/products/67/AI-1%5FDatasheet.pdf). Check the exact device and routing: a direct-monitor path may not include effects applied in recording software. ## What if two people need separate microphones? For a planned two-person recording, I would usually start with two XLR microphones and a device with two simultaneous microphone inputs. Each voice then has its own channel, gain setting and track if the recording setup supports it. Count *mic inputs*, not just sockets or playback channels; an instrument-only input may not accept the mic you chose. Multiple USB mics are not impossible. On macOS, for example, [Apple documents Aggregate Devices](https://support.apple.com/en-us/102171) that combine separate audio devices and explains clock-source and drift-correction settings. That is a supported method in a particular host, not a guarantee that arbitrary USB mics will be simple or reliable together on every device or in every app. If the multi-mic session matters, check the software's supported routing before buying. ## Three checks before you buy 1. **Host:** does the specific USB mic support your operating system, tablet or phone, its connector and available power? For XLR, does your interface or recorder connect to that host? 2. **Inputs and power:** how many sources must be recorded separately at once, and does each XLR mic need phantom power or another supply? Check the exact model manual rather than treating all XLR mics alike. 3. **Monitoring:** can you hear the live input and playback where you need to, through the mic, interface or recorder, with the controls your session requires? If the answer is one voice, one compatible computer and a short equipment list, choose a USB mic with the right capsule, pattern and monitoring. If the answer is multiple separate inputs or a chain you expect to change piece by piece, choose XLR and budget for the entire system. Once connected, our [microphone test](https://soundforgepro.com/microphone-test/) can help check input level, clipping and room noise; it answers that setup question rather than the purchase decision here. ### Dynamic vs Condenser Microphone: Which One Fits Your Recording? URL: https://soundforgepro.com/dynamic-vs-condenser-microphone/ Last updated: 2026-10-04T20:03:21.000Z **Choose a dynamic microphone when you can work close and want a sturdy, lower-output mic for a loud or nearby source. Choose a condenser when higher output, fine transient detail or a little more working distance helps—and the room is quiet enough to support it.** Neither type automatically rejects background sound, and neither one owns “studio quality.” The practical choice comes from the source, distance, polar pattern, room and recording chain. THE SHORT ANSWER **Choose dynamic**Close spoken voice, loud sources, stage use, rough handling or a room you need to keep out of the recording. **Choose condenser**Quiet or detailed sources, greater output, nuanced transients or controlled recording spaces. **Check either way**Polar pattern, working distance, sensitivity, gain, maximum SPL and connection requirements. ## Dynamic vs condenser microphone at a glance | Decision point | Moving-coil dynamic | Condenser | | --------------------- | -------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------ | | How it works | A diaphragm moves a coil through a magnetic field | A diaphragm and backplate form a capacitor; active electronics turn capsule changes into a usable signal | | Power | Passive models generally need no capsule power | Needs an appropriate power source; many XLR studio models use phantom power, but not all condensers use P48 | | Typical output | Often lower, so more preamp gain may be needed | Often higher, which can reduce the gain required from the preamp | | Electronic self-noise | No active microphone electronics in a passive moving-coil design; the preamp and rest of the chain still add noise | Active models publish a self-noise specification that matters most on quiet sources | | Loud sources | Commonly comfortable with close, high-level sources | Model-dependent; many condensers have high maximum-SPL ratings and some add a pad | | Handling | Often selected for rugged stage and portable use | Ranges from robust stage condensers to more delicate studio designs | | Room sound | Close placement can strengthen the direct voice relative to the room; lower output itself does not reject room sound | Distant placement can make reflections and background sound more obvious; compare pattern and distance at matched levels | | Common fit | Live vocals, podcasting close to the mouth, guitar cabinets, drums and handheld use | Studio vocals, acoustic instruments, overheads, piano, ambience and detailed capture | Those are tendencies, not promises. A cardioid condenser used five inches from a speaker can capture less room than an omnidirectional dynamic placed two feet away. A low-sensitivity dynamic can also produce a noisier result if the interface preamp is pushed hard. Compare the setup, then compare the models. ## How the two microphone types work DYNAMIC ### Diaphragm, coil and magnet Sound moves the diaphragm and its attached voice coil inside a magnetic field. That motion generates the electrical signal. A passive moving-coil microphone does not need active capsule electronics. CONDENSER ### Diaphragm, backplate and electronics Sound changes the distance between a conductive diaphragm and a fixed backplate, changing the capsule’s capacitance. An impedance converter and output electronics turn that tiny change into a practical microphone signal. [Shure’s operating-principle comparison](https://service.shure.com/articles/en%5FUS/Knowledge/difference-between-a-dynamic-and-condenser-microphone) shows the coil-and-magnet structure of a moving-coil dynamic beside the charged diaphragm-and-backplate structure of a condenser. The mechanism explains several common tendencies, but it does not dictate the polar pattern or guarantee one sound. Condenser capsule types and power arrangements vary beyond this comparison; the [condenser microphone guide](https://soundforgepro.com/what-is-a-condenser-microphone/) covers those choices in detail. ## Which type is better in an untreated room? A dynamic is often the easier choice for speech in an untreated room, but the useful advantage usually comes from **working close and increasing the direct-to-room ratio**. The microphone receives a stronger direct voice relative to reflections when you move closer. You can then use less preamp gain for the same recorded level. Lowering gain alone does not change the voice-to-room ratio. The label on the microphone does not create acoustic noise cancellation. Distance, aiming and directionality do the heavy work. [Shure’s recording-techniques guide](https://www.shure.com/damfiles/default/global/documents/publications/en/performance-production/microphone%5Ftechniques%5Ffor%5Frecording%5Fenglish.pdf-bb0469316afdb6118691d2f3f5e3ff01.pdf) treats microphone distance and directional characteristics as separate choices because both change the balance of direct sound and room reflections. **Start with distance** Move the microphone close enough for a strong direct signal without creating plosives, excessive proximity effect or an uncomfortable performance. **Aim the rejection** Point the least-sensitive part of [the selected polar pattern](https://soundforgepro.com/microphone-polar-patterns/) toward the loudest unwanted source when the microphone’s pattern chart supports that placement. **Control the source** Turn down speakers, move the computer, close the window and reduce hard nearby reflections before asking software to repair the recording. ## Sensitivity, gain and noise: follow the complete chain Sensitivity tells you how much electrical output a microphone produces for a stated acoustic input. Condensers often provide more output, while many moving-coil dynamics need more preamp gain. [Shure’s sensitivity guide](https://service.shure.com/articles/en%5FUS/Knowledge/how-do-i-compare-the-sensitivity-of-two-microphones) makes the key distinction: sensitivity is an output specification, not a score for sound quality. 1**Source level**How much acoustic energy reaches the capsule **→** 2**Mic output**Sensitivity and distance set the signal leaving the microphone **→** 3**Preamp gain**Raises both the wanted signal and noise already in the chain A passive moving-coil dynamic has no active microphone electronics producing a published self-noise figure. That does not make the recording noise-free. If its output is low, the interface may need substantial gain, and the preamp’s equivalent input noise becomes more noticeable. A condenser adds its own electronic self-noise, yet its higher output may ask less of the preamp. For a soft voice or quiet acoustic instrument, compare microphone sensitivity, condenser self-noise where applicable and the interface’s available clean gain. For a loud cabinet or snare, those limits are less likely to decide the purchase. ## Power and connections Most passive moving-coil dynamics work from an XLR microphone input without phantom power. Many studio condensers need [phantom power](https://soundforgepro.com/what-is-phantom-power/) from the interface or preamp, but the requirement belongs to the individual model. USB condensers receive power over USB; electret and tube designs may use other systems. [Neumann’s interface connection guide](https://www.neumann.com/en-us/knowledge-base/neumann-im-homestudio/homestudio-academy/how-to-connect-your-microphone-to-an-audio-interface) recommends making the XLR connection with gain and phantom power down, enabling the required power after the connection is secure, and lowering the system again before disconnecting. Follow the microphone and interface manuals when their sequence or power requirement differs. Once the microphone is connected, use our [online microphone test for level, clipping and background noise](https://soundforgepro.com/microphone-test/) at your intended working distance. A short listening sample can reveal a problem in the setup before you judge the microphone type. ## Can condenser microphones handle loud sources? Yes—if the model’s maximum SPL and pad arrangement suit the source and placement. “Condenser” does not mean “quiet sources only.” The specification sheet is more useful than the category slogan. 152 dB SPL**Shure KSM27: −15 dB pad, ≥2.5 kΩ load** The guide specifies this limit at 1 kHz under those conditions; a 1 kΩ load lowers the rating. 144 dB SPL**Neumann TLM 102** Another current condenser specification that contradicts the idea that all condensers overload easily. The [KSM27 guide](https://pubs.shure.com/guide/KSM27/en-US) specifies 152 dB SPL at 1 kHz with its −15 dB pad and a load of at least 2.5 kΩ (147 dB SPL into 1 kΩ), while [Neumann rates the TLM 102](https://www.neumann.com/en-en/products/microphones/tlm-102/) for 144 dB SPL at 0.5% THD. These figures do not prove that every condenser fits every loud source. They prove that you must check maximum SPL, distortion conditions, pad settings and placement for the model in front of you. ## Which microphone fits each recording job? | Recording job | Useful starting point | What can change the answer | | ----------------------------------------------- | --------------------- | ---------------------------------------------------------------------------------------------------------------- | | Podcast or stream in a reflective room | Dynamic | Close placement, a compatible polar pattern and enough clean interface gain matter more than the category alone | | Podcast or stream in a quiet treated room | Either | A condenser offers more output and often more fine detail; a dynamic can still give the voice the preferred tone | | Sung lead vocal | Either | Voice, performance distance, plosives, room, frequency response and desired texture decide the model | | Acoustic guitar, strings or detailed percussion | Condenser | A dynamic can work when isolation, close placement or a softer top end serves the arrangement | | Guitar cabinet or close drum | Dynamic | A condenser with adequate maximum SPL and a suitable frequency response can be equally valid | | Drum overheads, piano or room pair | Condenser | Pattern consistency, self-noise, phase relationship and room quality become central | | Handheld live vocal | Dynamic | Stage condensers are viable when handling noise, feedback margin and power are controlled | | Travel, rehearsal and rough handling | Dynamic | A robust powered microphone may still win when output and detail are more useful than passive simplicity | I would treat every row as a starting point, then listen for the reason to change it. “Dynamic for stage, condenser for studio” is quick shopping advice. It is not a recording rule. ## Specifications to compare before buying - **Polar pattern and off-axis behavior.** A cardioid label alone does not show how the microphone responds at different frequencies or angles. - **Sensitivity.** Use it to estimate output and gain demand, not to rank fidelity. - **Frequency response.** Read the graph and stated test conditions; do not reduce it to one advertised range. - **Maximum SPL and pad.** Check the distortion threshold and whether the published maximum assumes an engaged pad. - **Self-noise.** Relevant for active microphones on quiet or distant sources; less decisive beside a loud source. - **Power and connector.** Confirm phantom voltage, USB requirements, battery or dedicated supply and interface compatibility. - **Physical use.** Weight, mount, handheld noise, [wind protection](https://soundforgepro.com/reduce-wind-noise-voice-recording-sound-forge/) and durability can decide the real-world winner. ## A simple decision sequence 1. **Name the source.**Is it a quiet voice, acoustic instrument, loud amplifier, drum, stage vocal or room? 2. **Choose the working distance.**Close placement favors direct sound; more distance includes more of the room. 3. **Map unwanted sound.**Identify reflections, fans, traffic, monitors and other instruments, then choose and aim the polar pattern. 4. **Check the chain.**Confirm power, connector, microphone output and enough clean preamp gain. 5. **Read the model specifications.**Use sensitivity, self-noise, maximum SPL and response data to rule models in or out. 6. **Choose the voicing and handling you prefer.**Once the setup works technically, frequency response, transient character, size and durability can make the final decision. ## The final choice Pick a dynamic microphone when close placement, rugged handling and a controlled result from a loud or nearby source are the priorities. Pick a condenser when higher output, detailed transients or a wider practical working distance help and the room can support them. If background sound is the problem, solve distance and directionality before blaming the transducer type. If noise is the problem, follow the signal from source level through microphone output and preamp gain. If loudness is the problem, read the actual maximum-SPL specification. That process gives you a microphone that fits the recording instead of a category that merely sounds familiar. ### Best Free Metering Plugins: 8 Tools for Loudness, Spectrum and Phase URL: https://soundforgepro.com/free-metering-plugins/ Last updated: 2026-10-09T21:03:41.000Z **If you want one free meter that covers the most everyday checks, start with Voxengo SPAN. Add Youlean Loudness Meter when delivery loudness and true peak are the question, TDR Prism when you need to see masking or compare a reference, and Voxengo Correlometer when stereo phase is the concern.** These tools are not eight versions of the same plugin. Each answers a different monitoring question, and choosing by that question is more useful than filling the master bus with overlapping graphs. CHOOSE THE QUESTION FIRST **Loudness and true peak**Youlean Loudness MeterClear starting point for LUFS-oriented delivery checks **Broad spectrum and levels**Voxengo SPANOne flexible view for frequency, level and correlation **Masking and references**TDR PrismPerceptual weighting and comparison between sources **Stereo phase risk**Voxengo CorrelometerMultiband correlation and mono-compatibility diagnosis ## Free metering plugins compared by diagnostic task | Question | Free plugin | What it shows | Current compatibility note | Do not expect it to | | --------------------------------------------------------------------------- | ----------------------------- | ------------------------------------------------------------------------------------------------------------ | --------------------------------------------------------------------------------------- | -------------------------------------------------------------------------- | | **How loud is the program, and where are true peaks?** | Youlean Loudness Meter | Free integrated loudness, loudness range, true peak, PLR and DR readouts, with loudness and true-peak graphs | Windows and macOS; application, VST2, VST3, AU and AAX | Decide the correct delivery target without a platform specification | | **Where is the spectral energy, and are levels or correlation suspicious?** | Voxengo SPAN | FFT spectrum, level statistics, EBU R128/K-system views, true-peak clipping and correlation | 64-bit Windows and macOS; VST/VST3/AU/AAX families vary by OS | Tell you whether a tonal choice is musically right | | **Which frequencies may be masked, and how does a reference differ?** | TDR Prism | Perceptual spectrum, auditory masking and source comparison | Windows, macOS and Linux; available formats vary by OS | Replace listening-level matching or arrangement decisions | | **How do RMS, crest factor, loudness and dialog measurements relate?** | TBProAudio dpMeter5 | RMS, EBU R 128, dialog-gated, true-peak, crest and loudness-range views | Windows and macOS; current developer downloads list common plugin formats | Run DIAL measurements at sample rates other than 44.1 or 48 kHz | | **Do I need a spectrum analyzer with detailed display controls?** | MeldaProduction MAnalyzer | Spectrum, normalization, smoothing, prefiltering, deharmonization and integrated level meters | Included in the current MFreeFXBundle | Provide every paid resize, preset and sonogram feature in the free tier | | **Can I get a simpler real-time spectrum display?** | Blue Cat FreqAnalyst | Mono/stereo spectrum, smoothing, zoom and threshold controls | Windows and macOS in VST/VST3/AU/AAX families | Include the Pro edition’s curve storage, precision tools or 3D spectrogram | | **Can I check level, loudness and M/S without a large analysis suite?** | HOFA 4U Meter, Fader & MS-Pan | Peak, hold, EBU, loudness range, M/S and file analysis | PC and Mac; verify the current installer because the page retains legacy format wording | Replace a dedicated spectrum or phase-analysis tool | | **Is the stereo problem limited to part of the spectrum?** | Voxengo Correlometer | Correlation across 4–64 bands, phase-risk cues and sidechain comparison | 64-bit Windows and macOS; VST/VST3/AU/AAX families vary by OS | Prove that width, polarity or timing is correct by itself | **How I made the shortlist** I compared current product pages and official documentation, then grouped tools by the measurement problem they document. SoundForgePro did not install or benchmark these plugins for this article, and I have not turned a product-page claim into an accuracy ranking. ## Loudness, spectrum, masking and correlation answer different questions A meter becomes useful only after you can finish the sentence: “I need to know whether…” A loudness meter can show program loudness and true peak, but it cannot explain a harsh upper midrange. A spectrum analyzer can show where energy accumulates, but it cannot decide whether that energy belongs there. A [correlation meter](https://soundforgepro.com/phase-correlation-meter/) can warn about possible mono loss, but a positive reading is not a quality certificate. ![Decision map matching six audio questions with loudness, spectrum, masking, dynamics, stereo correlation and level meters](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/09/inline-metering-question-map.webp) Choose the meter from the question: delivery level, tonal balance, masking, dynamics, stereo phase or a quick channel check. DELIVERY ### Loudness and true peak Use these readings when a broadcaster, podcast host or other destination gives a measurable delivery specification. If you need a quick browser check before opening a DAW, the [SoundForgePro LUFS meter](https://soundforgepro.com/lufs-meter/) covers that separate task. TONAL BALANCE ### Spectrum Use a spectrum view to locate persistent low-end buildup, narrow resonances or missing regions. The [browser audio spectrum analyzer](https://soundforgepro.com/audio-spectrum-analyzer/) explains the FFT view without turning the graph into an automatic EQ instruction. MASKING ### Perceptual comparison Use masking and reference overlays to ask whether one source hides another or whether two spectra differ. Match playback level before treating a brighter or louder reference as better. DYNAMICS ### RMS and crest factor Use level history and crest factor to describe the relationship between average and peak behavior. They are clues about dynamics, not targets that every genre must share. STEREO ### Correlation and mono compatibility Use correlation to find frequency regions that may cancel when summed. The full [mono-compatibility and phase-correlation guide](https://soundforgepro.com/mono-compatibility-phase-correlation/) owns the corrective workflow. CHANNEL CHECK ### Peak, hold and M/S Use compact meters for gain staging, mid/side balance and fast file checks when a full spectral display would add noise rather than information. ## 1\. Youlean Loudness Meter: start here for loudness and true peak Youlean is the clearest first addition when the destination gives you a loudness or true-peak requirement. The [current Youlean product page](https://youlean.co/youlean-loudness-meter/) describes loudness, loudness range, dynamics and true-peak measurement and lists Windows and macOS application, VST2, VST3, AU and AAX options. The free edition includes integrated loudness, true peak, loudness range, PLR and DR readouts, plus loudness and true-peak graphs. It supports mono, stereo and 5.1 audio and does not expire. I would start there for delivery checks. Pro adds streaming presets, a dynamics graph, PDF/PNG/SVG exports, custom presets, A/B states and drag-and-drop analysis; you do not need those extras just to read integrated loudness and true peak. **Choose it when:**a delivery requirement is written in LUFS or true peak and you want a dedicated view rather than a multipurpose analyzer.**Do not expect it to:**choose the correct target for you. Streaming and broadcast requirements change by destination; use the current specification, not a remembered universal number. ## 2\. Voxengo SPAN: the most useful general-purpose starting point SPAN is my default recommendation when someone asks for “a free meter” but has not yet narrowed the problem. According to the [official SPAN page](https://www.voxengo.com/product/span/), it combines an FFT spectrum analyzer with stereo, mono and mid-side views, level statistics, true-peak clipping detection, EBU R128/K-system metering and stereo correlation. That breadth makes it a sensible first diagnostic panel. The advantage is consolidation: one plugin can reveal a low-frequency concentration, a clipping concern and a suspicious correlation reading without opening three windows. The danger is assuming one window gives one answer. Read each section independently and follow the clue with the relevant listening or mono check. **Choose it when:**you want one flexible analyzer for spectrum, levels and a quick stereo check across common 64-bit Windows or macOS hosts.**Do not expect it to:**decide that a spectrum is balanced because it follows a preferred slope, or that a correlation value makes the mix safe in every playback system. ## 3\. TDR Prism: best for masking and reference comparison Prism earns its place because it asks a more useful question than “what does the spectrum look like?” The [TDR Prism documentation](https://www.tokyodawn.net/tdr-prism/) describes perceptual weighting, human auditory filters, real-time masking indication and comparison between regular inputs, sidechains, audio files and other Prism instances. That makes it especially relevant when two sources compete or a reference seems different but the cause is unclear. Reference comparison still needs level discipline. A louder reference often appears fuller and clearer before any spectral judgment begins. Prism can show the difference; it cannot remove the bias created by mismatched playback level or tell you whether an arrangement should leave more space. **Choose it when:**you need to compare sources, inspect likely masking or view the spectrum through a perceptual model.**Do not expect it to:**solve masking automatically. The useful response may be arrangement, timing, level, panning or sound choice rather than EQ. ## 4\. TBProAudio dpMeter5: best for dynamics and dialog-oriented readings dpMeter5 is the stronger choice when the question includes RMS, crest factor or dialog-gated measurements rather than only integrated loudness. The [current dpMeter product page](https://www.tbproaudio.de/products/dpmeter) lists RMS, EBU R 128 and DIAL modes, along with integrated, momentary, peak, true-peak, loudness-range and crest readings. For dialog work, check the session sample rate first: the [dpMeter5 manual limits DIAL measurements to 44.1 and 48 kHz](https://www.tbproaudio.de/assets/content/manuals/dpMeter5%20manual.pdf). This restriction applies to DIAL mode, not to every measurement in the plugin. Choose a dialog-gated reading only when your delivery requirement calls for it; a music mix and a dialogue program may need different measurements. **Choose it when:**you need several level and dynamics views in one plugin, especially RMS, crest factor, loudness range or dialog-gated readings.**Do not expect it to:**provide DIAL measurements outside the documented 44.1 or 48 kHz sample rates. ## 5\. MeldaProduction MAnalyzer: detailed spectrum work with a free-tier caveat MAnalyzer is a broad spectral tool for readers who want more than a simple curve. The [official MAnalyzer page](https://www.meldaproduction.com/MAnalyzer) documents smoothing, normalization, super-resolution, prefiltering and deharmonization, along with spectrum analysis and integrated peak and loudness meters. Sonogram access requires the paid MFreeFXBundle upgrade. Two limits matter. First, Melda’s page still describes its loudness meter as EBU R128 and ITU-R BS.1770-3 compliant, so that is the revision to report. Second, the [MFreeFXBundle comparison](https://www.meldaproduction.com/MFreeFXBundle) says paid activation adds resizing, preset management and sonogram access in analyzers and equalizers. Do not assume the product headline means every displayed feature is available without the upgrade. **Choose it when:**you want configurable spectrum analysis and the rest of the free Melda bundle is useful to your workflow.**Do not expect it to:**include every interface, preset or sonogram feature in the free tier, or to document a newer loudness revision than BS.1770-3. ## 6\. Blue Cat FreqAnalyst: a simpler real-time spectrum view FreqAnalyst fits the opposite preference: a focused spectrum display without the broader metering stack. Blue Cat describes the [free FreqAnalyst](https://www.bluecataudio.com/Products/Product%5FFreqAnalyst/) as a mono and stereo real-time spectrum analyzer with control over frequency transformation, smoothing, zoom and thresholds, available for Mac and Windows in common plugin formats. The same page clearly separates the Pro edition. Saving and restoring curves, precise measurement tools, a 3D spectrogram and related advanced functions are not safe claims for the freeware version. If your question is simply “where is the energy?”, that limitation may be useful: fewer controls can make the first diagnosis faster. **Choose it when:**you want a straightforward spectrum monitor and do not need masking, multitrack comparison or a dense loudness panel.**Do not expect it to:**include the Pro edition’s curve storage, precision measurement or 3D spectrogram features. ## 7\. HOFA 4U Meter, Fader & MS-Pan: quick level and M/S checks HOFA’s 4U utility is useful when you want a compact channel tool rather than another large graph. The [current HOFA freeware page](https://hofa-plugins.de/en/freeware-en/) describes peak and hold metering, EBU readings, loudness range, M/S encode/decode, stereo/mono switching and drag-and-drop file analysis. The page also retains legacy 32-bit and RTAS wording alongside current format families. Treat that as a reason to check the actual installer for your current OS and host before planning a session around it. The feature fit is clear; the compatibility sentence should stay cautious. **Choose it when:**you need compact level, loudness and M/S controls for fast channel or file checks.**Do not expect it to:**replace a detailed spectrum analyzer or a dedicated multiband correlation display. ## 8\. Voxengo Correlometer: best for multiband stereo correlation Correlometer is the specialist in this group. The [official Correlometer page](https://www.voxengo.com/product/correlometer/) documents correlation metering across 4 to 64 bands, phase-issue detection, mono-compatibility checking and sidechain support. A broadband meter may look acceptable while a narrower frequency region cancels; the multiband view is designed to expose that distinction. Correlation remains a clue, not a verdict. Negative or unstable bands deserve a mono sum and a routing check, but the display does not tell you whether the cause is an intended stereo effect, a polarity error, a timing offset or a harmless local feature. Diagnose the cause before narrowing the entire mix. **Choose it when:**you suspect that stereo cancellation is concentrated in a frequency range or need to compare phase behavior between signals.**Do not expect it to:**prove that a mix is correct, or to replace a real mono playback check. ## What the loudness standards do—and do not—tell you [ITU-R BS.1770-5](https://www.itu.int/rec/R-REC-BS.1770-5-202311-I/en) defines algorithms for measuring program loudness and true-peak audio level. [EBU R 128-2023](https://tech.ebu.ch/docs/r/r128.pdf) uses program loudness for broadcast normalization, maximum true peak for the upper technical limit, and loudness range plus momentary and short-term measures to further characterize a program. Those documents explain the measurement framework; they do not create one universal target for music, podcasts, broadcast and every streaming platform. Use the destination’s current rules. SoundForgePro keeps the changing delivery details in the separate [streaming loudness standards guide](https://soundforgepro.com/streaming-loudness-standards/) and [podcast loudness guide](https://soundforgepro.com/podcast-loudness-standard/). If you are working specifically inside Sound Forge, the [Sound Forge loudness-meter walkthrough](https://soundforgepro.com/sound-forge-loudness-meters/) covers that software-specific path. ## A practical two-meter workflow For a delivery check, establish the destination’s current loudness and true-peak requirements before choosing a meter or changing the audio. A preset is a convenience, not a substitute for those requirements. 1. **Name the failure you are checking.**Clipping, delivery loudness, tonal buildup, masking and mono loss are different failures. 2. **Choose one primary meter.**Use Youlean or dpMeter5 for delivery and dynamics, SPAN or FreqAnalyst for spectrum, Prism for masking, or Correlometer for phase. 3. **Add one secondary view only when it changes the decision.**For example, pair a loudness meter with SPAN, or Prism with Correlometer. Avoid three spectrum analyzers showing the same clue. 4. **Confirm the graph with an audible check.**Level-match references, sum to mono when phase is the issue, and bypass processing before accepting the meter’s implication. 5. **Verify the final delivery readings.**For delivery work, compare the final readings with the requirements you established at the start. ## Which free meter should you download? **You want one broad starting tool** Choose **Voxengo SPAN**. It covers spectrum, levels, true-peak clipping and a quick correlation view without forcing you into a single delivery workflow. **You have a defined LUFS or true-peak requirement** Choose **Youlean Loudness Meter**. The free edition covers integrated loudness, loudness range and true peak. Use your destination specification to set the target; streaming presets and export reports are Pro extras. **You need RMS, crest factor or dialog-gated views** Choose **TBProAudio dpMeter5**. Choose the view required for your material; DIAL measurements require a 44.1 or 48 kHz session. **You are comparing a mix with a reference or hunting masking** Choose **TDR Prism**. Level-match first so the comparison answers a spectral question rather than a loudness bias. **You want a simple spectrum display** Choose **Blue Cat FreqAnalyst**. Choose **MAnalyzer** when you need a more configurable tool and accept the free-tier limits. **You are troubleshooting stereo cancellation** Choose **Voxengo Correlometer**. Follow suspicious bands with mono listening and routing checks instead of treating the graph as a pass/fail light. **You need quick channel, EBU or M/S checks** Choose **HOFA 4U Meter, Fader & MS-Pan**, then verify that the current installer supports your OS and plugin host. The useful free-meter setup is usually smaller than the download list. Pick the question, choose one tool that answers it, and add a second meter only when it covers a different problem. That keeps the screen readable and makes every measurement lead to a decision. ### Best Budget Ribbon Microphones: 8 Picks from $128 to $649 URL: https://soundforgepro.com/best-budget-ribbon-microphones/ Last updated: 2026-10-04T20:03:27.000Z **The MXL R144 is the cheapest sensible entry into [ribbon microphones](https://soundforgepro.com/ribbon-vs-condenser-microphone/) in this comparison, while the Golden Age R2 MKII is the stronger passive value below $200 and the R1 Active MKIII is the easier budget match for a modest preamp.** If you can spend more, the sE X1 R adds phantom protection, the VR2 provides much higher active output, and the Royer R-10 is the long-term passive step-up. The right choice depends on your preamp, room and source—not price alone. START WITH YOUR SIGNAL CHAIN **Lowest entry price**MXL R144$128 passive ribbon; plan for quiet gain **Best passive under $200**Golden Age R2 MKII$179; never apply phantom power **Best budget active**Golden Age R1 Active MKIII$229; requires 48 V phantom power **Price note:** all prices below are US advertised prices captured on September 22, 2026\. They are a dated comparison, not a promise of current stock or future pricing. The sE VR2 price was a temporary sale when checked. ## Budget ribbon microphone comparison | Model | Price\* | Design | Phantom-power rule | Sensitivity / load note | Stated response | | ------------------------------ | --------- | ------------------- | ------------------ | ---------------------------------------------------------- | --------------------------------------- | | **MXL R144** | $128 | Passive | Do not use | \-56 dBV; load above 1.5 kΩ | 20 Hz–17 kHz | | **Golden Age R2 MKII** | $179 | Passive | Never apply | \-50 dB; 1.2 kΩ recommended load | 30 Hz–18 kHz | | **Golden Age R1 Active MKIII** | $229 | Active | Required | Buffered output; manufacturer lists no numeric sensitivity | Not listed on manufacturer product page | | **sE X1 R** | $249 | Passive | Protected | 1.8 mV/Pa (-55 dBV) | 20 Hz–16 kHz | | **Avantone CR-14** | $279 | Passive dual ribbon | No power needed | \-52 dBV; 3 kΩ recommended load | 30 Hz–15 kHz ±3 dB | | **sE VR1** | $409 | Passive | Protected | 1.8 mV/Pa (-55 dBV) | 20 Hz–18 kHz | | **sE VR2** | $419 sale | Active | Required | 14.1 mV/Pa (-37 dBV) | 20 Hz–18 kHz | | **Royer R-10** | $649 | Passive | Conditional | \-54 dBV; 700 Ω or higher load | 30 Hz–15 kHz ±3 dB | \*September 22, 2026 US snapshot. A frequency-response range does not tell you how flat or suitable a microphone sounds, so it is not used as a quality score. **How I chose these picks** I compared current manufacturer specifications, manuals, electrical requirements, included hardware and the dated US price snapshot. I did not treat retailer copy or a published frequency range as a listening test, and SoundForgePro did not audition these microphones for this article. ## 1\. MXL R144: the lowest-cost introduction The MXL R144 is the place to start when the goal is to learn how a passive figure-8 ribbon fits your recording chain at the lowest price in this comparison. At $128 in the captured price snapshot, it leaves room in the budget for the part that matters just as much: a quiet preamp or suitable clean-gain stage if your existing interface becomes noisy at high gain. The [current MXL R144 specifications](https://mxlmics.com/products/r-144/) list a passive figure-8 design, -56 dBV sensitivity, 250-ohm output impedance and a recommended load above 1.5 kΩ. That low sensitivity is not a defect, but it tells you why this microphone is a poor impulse purchase for a quiet singer and a noisy interface. The [R144 manual](https://www.mxlmics.com/manuals/R144.pdf) warns never to apply power to the microphone and to avoid strong air bursts that can damage its ribbon. **Choose it when:**you want the cheapest credible route into ribbon placement and already have enough clean gain for the source.**Skip it when:**you record quiet sources through a preamp that hisses near the top of its gain range, or you need a forgiving shared setup where 48 V may be left on. ## 2\. Golden Age R2 MKII: best passive value under $200 The Golden Age R2 MKII is my passive value pick below $200\. Its documented sensitivity is higher than the R144’s, so it needs less preamp gain for the same source level and distance. Both microphones include a shock mount; the R2’s higher output is the reason I would consider paying the difference between their $128 and $179 price snapshots. The [R2 MKII manual’s specifications](https://goldenageaudio.com/wp-content/uploads/2025/08/R2-MKII-Manual.pdf) give a figure-8 pattern, roughly 3.2 mV/Pa sensitivity, 250-ohm output impedance and a 1.2 kΩ recommended load. The same manual is direct about power: never apply [phantom power](https://soundforgepro.com/what-is-phantom-power/). I would choose this model only when I can keep 48 V off throughout the session. **Choose it when:**you want a passive figure-8 microphone below $200, have a suitable preamp and can control phantom power reliably.**Skip it when:**several people use the same patching setup or you cannot guarantee that 48 V will stay off. ## 3\. Golden Age R1 Active MKIII: best inexpensive active ribbon The R1 Active MKIII is the most affordable active design here. Its internal buffer changes the buying question: instead of demanding the same amount of clean preamp gain as a low-output passive ribbon, it uses 48 V to produce a stronger, more stable output. That can make more sense than buying a cheap passive ribbon and then adding another gain device. The [R1 Active MKIII specification](https://goldenageaudio.com/microphones/ribbon-microphones/r1-active-mkiii/) describes an active FET buffer, mandatory 48 V phantom power, a switchable -10 dB pad and a low-cut switch. Golden Age states a 160 dB maximum SPL at 1 kHz and 1% THD. The manufacturer’s product page does not list numeric sensitivity or a full frequency-response specification, so those figures are unavailable for a like-for-like comparison here. **Choose it when:**your interface supplies proper 48 V but does not offer especially quiet high gain, or you want pad and low-cut controls on the microphone.**Skip it when:**your recorder cannot supply phantom power or you specifically want a passive ribbon circuit. ## 4\. sE Electronics X1 R: best protected passive option under $250 The X1 R is the safer passive choice for a busy home studio. It still behaves like a low-output passive ribbon, but sE builds in phantom-power protection. That does not remove the need for careful cabling and gain staging, yet it reduces one common operational risk compared with models whose manuals prohibit phantom power. The [official X1 R page](https://seelectronics.com/products/x1-r/) specifies a figure-8 pattern, 1.8 mV/Pa sensitivity, 200-ohm output impedance, a 20 Hz–16 kHz stated response and phantom protection. At $249 in the price snapshot, it is not the cheapest way to get a ribbon. The extra money buys a more forgiving electrical design, not proof that it will suit every source better. **Choose it when:**you want a passive ribbon under $250 but value phantom protection in a shared or frequently repatched studio.**Skip it when:**your main problem is insufficient clean gain; an active ribbon may solve that more directly. ## 5\. Avantone CR-14: best passive package under $300 The CR-14 is the package pick below $300\. Avantone includes a [shock mount, wooden presentation box and metal road case](https://avantonepro.com/en/products/cr-14), which matters if the microphone will move between storage and sessions instead of living permanently on a stand. It is also the only dual-ribbon design in this shortlist. Avantone lists the CR-14 at $279 and specifies a passive figure-8 design, -52 dBV sensitivity, output impedance at or below 600 ohms and a 3 kΩ recommended load on the [current CR-14 product page](https://avantonepro.com/en/products/cr-14). The 30 Hz–15 kHz ±3 dB stated response should be read as a specification, not a verdict about detail or darkness. **Choose it when:**you want a passive ribbon with protective storage and a shock mount included in the price.**Skip it when:**you already have suitable mounting and storage, or an active output is more useful than the accessory package. ## 6\. sE Electronics VR1: a step-up passive ribbon The VR1 is the step-up passive option for buyers who want sE’s phantom protection and a stated response extending to 18 kHz. It keeps the familiar passive-ribbon constraint—1.8 mV/Pa sensitivity—so it still belongs with a quiet preamp rather than being treated as a plug-and-forget upgrade. The [VR1 specifications](https://seelectronics.com/products/vr1/) list a figure-8 pattern, 300-ohm output impedance, 20 Hz–18 kHz stated response and a 230 g body. The shared [VR1 and VR2 manual](https://seelectronics.com/wp-content/uploads/2021/11/VR1VR2UserManual.pdf) separates the models clearly: the VR1 is passive, while the VR2 is active and requires P48\. The $409 snapshot places the VR1 above the strict budget tier, so buy it for that documented design fit rather than because a higher price guarantees a preferred sound. **Choose it when:**you want a light, protected passive ribbon and already trust your preamp with low-output microphones.**Skip it when:**you are spending more mainly to escape high-gain preamp demands; the active VR2 is the relevant comparison. ## 7\. sE Electronics VR2: best step-up active choice The VR2 is the most straightforward electrical match in the group. Its active circuit raises sensitivity to 14.1 mV/Pa, or -37 dBV, which is dramatically higher than the 1.8 mV/Pa specified for the passive X1 R and VR1\. That does not make the VR2 automatically better, but it can make the complete recording chain quieter and easier to operate with ordinary interface preamps. The [VR2 product page](https://seelectronics.com/products/vr2/) specifies a figure-8 pattern, 200-ohm output impedance and required P48 phantom power. The $419 captured price was a temporary $100 discount, so treat it as an opportunity observed on September 22, 2026 rather than its permanent market position. **Choose it when:**you want ribbon behavior without asking the preamp for extreme gain, and your interface supplies reliable 48 V.**Skip it when:**you prefer a passive signal path or the sale has ended and the new price changes the value equation. ## 8\. Royer R-10: the long-term passive step-up The Royer R-10 sits outside many definitions of “budget,” but it belongs in this comparison because it shows what the next passive step costs. At $649 in the captured retailer snapshot, it is for someone who has already decided that a passive figure-8 ribbon fits the work and wants a model with extensive manufacturer placement guidance and [service support](https://royerlabs.com/warranty/). The [R-10 specifications](https://royerlabs.com/r-10/) list -54 dBV sensitivity, 100-ohm output impedance, a recommended load of 700 ohms or greater and a 30 Hz–15 kHz ±3 dB stated response. Royer’s [R-10 manual](https://www.royerlabs.com/pdf/manuals/R-10manual.pdf) covers proximity effect, rear-lobe polarity, preamp loading and placement around loud sources in more depth than most product pages. Royer also gives a more nuanced phantom-power rule than “always safe” or “always dangerous.” Its [technical guidance on ribbons and phantom power](https://royerlabs.com/ribbon-mics-and-phantom-power/) says Royer ribbons are normally unaffected by phantom power, but damaged or miswired cables and phantom-powered patching can damage the ribbon. Royer recommends turning phantom off before connecting or disconnecting its passive microphones; I would also keep it off while repatching. **Choose it when:**you have a suitable preamp, already understand figure-8 placement and want a passive model intended as a longer-term studio purchase.**Skip it when:**this is your first ribbon experiment or the extra spend would leave the gain chain, stand and wind protection unresolved. ## Active versus passive ribbon microphones Active and passive ribbons can use similar ribbon motors, but they interact with the rest of the signal chain differently. A passive microphone sends the ribbon transformer’s low-level output directly toward the preamp. An active model adds internal electronics that require power and provide a stronger, less load-sensitive output. ![Diagram comparing passive and active ribbon microphone signal paths alongside a figure-8 pickup pattern with side nulls](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/09/inline-active-passive-ribbon-chain.webp) A passive ribbon relies on clean preamp gain; an active ribbon uses its required 48 V supply, while a figure-8 pattern remains sensitive at the front and rear and rejects sound from the sides. PASSIVE ### Choose around the preamp Check sensitivity, the manufacturer’s recommended input load and how noisy your preamp becomes at high gain. Loud guitar cabinets and brass demand less gain than quiet vocals or distant room placement. ACTIVE ### Choose around power and headroom Confirm the exact phantom requirement before connection. A higher output can suit ordinary interfaces, but the active circuit and pad limits still matter on very loud sources. Do not buy an inline booster automatically. Start with the microphone’s manual, then compare its sensitivity and recommended load with your preamp’s input impedance and available clean gain. An active ribbon may already provide enough output, while a passive model may call for a quieter preamp or a suitable clean-gain stage. ## How much preamp gain and input impedance do you need? There is no honest universal gain number for ribbon microphones. Required gain changes with source level, distance, microphone sensitivity and the noise performance of the preamp. A close guitar cabinet may need little gain; a soft voice at a cautious distance may expose hiss from the same interface. 1. **Read sensitivity first.**A more negative dBV figure indicates lower output. The R144 at -56 dBV and R-10 at -54 dBV will generally ask more of the preamp than the active VR2 at -37 dBV. 2. **Check the recommended load.**MXL recommends above 1.5 kΩ for the R144, Golden Age states 1.2 kΩ for the R2 MKII, Avantone states 3 kΩ for the CR-14, and Royer specifies 700 Ω or higher for the R-10. 3. **Listen for preamp noise before buying another device.**Connect correctly with phantom set for that model, raise gain for the intended source and judge whether hiss becomes intrusive at the working level. 4. **Match the fix to the problem.**If gain noise is the limitation, an active ribbon or suitable clean-gain stage may help. If room pickup or air movement is the problem, more gain hardware will not fix it. ## Phantom power: required, protected, conditional or prohibited The usual warning that “phantom power kills ribbon microphones” is too broad to guide a real setup. The safe instruction is model-specific. Some active ribbons require 48 V, some passive ribbons include protection, Royer permits properly wired balanced phantom systems under stated conditions, and two inexpensive models here explicitly prohibit it. | Rule | Models | What to do | | ------------------------- | ---------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | 48 V required | Golden Age R1 Active MKIII; sE VR2 | With phantom disabled and gain down, allow any previously active phantom supply to discharge before connecting the microphone using a known-good balanced cable. Then enable the required P48 supply. | | Phantom-protected | sE X1 R; sE VR1 | No power is needed, but protection reduces the risk of an accidental correctly wired supply. | | Permitted with conditions | Royer R-10 | Use a properly wired balanced cable. Turn phantom off before connecting, disconnecting or using a patchbay. | | Prohibited by manual | MXL R144; Golden Age R2 MKII | Keep phantom power off. Do not assume another manufacturer’s protection applies. | | No power specified | Avantone CR-14 | The microphone is passive and needs no power. Follow the current manufacturer documentation and use cautious connection practice. | For any passive ribbon, turn phantom off and lower the preamp gain before touching the connection. If phantom was active, [allow the supply to discharge](https://www.bumblebeepro.com/ribbon-microphone/ribbon-mic-phantom-power/) before connecting or disconnecting the mic; follow your preamp or interface maker’s shutdown guidance rather than assuming a universal delay. Then connect a known-good balanced XLR cable and raise gain. Avoid hot-patching through a phantom-powered patchbay. ## Figure-8 placement changes the room you record Seven models in this shortlist have a manufacturer-documented figure-8 pattern. The current manufacturer page for the R1 Active MKIII identifies it as a ribbon microphone but does not state the pattern in its visible specification, so verify the latest manual before planning around side rejection. A figure-8 microphone hears from the front and rear while rejecting sound near its sides. The deep side nulls are useful, but the open rear lobe means the room behind the microphone remains part of the recording. FRONT ### Aim the marked side at the source Start on axis, then rotate or move the microphone rather than reaching for EQ immediately. REAR ### Choose what the microphone faces behind it A hard wall close to the rear lobe can return early reflections. More distance or absorption behind the microphone changes that contribution. SIDE NULL ### Point the side at unwanted sound Rotate the microphone so a nearby monitor, cymbal or other source sits near 90 degrees to the ribbon. DISTANCE ### Use proximity effect deliberately Moving close increases bass on a pressure-gradient figure-8 microphone. Backing away reduces that rise and increases room contribution. The rear lobe also has opposite polarity to the front on the R-10, as Royer documents. That matters when combining the ribbon with another microphone: change distance and check the summed result rather than assuming the two signals will align because both capsules face the source. ## Protect the ribbon from air movement A ribbon can handle high sound pressure while still being vulnerable to a strong blast of air. SPL and wind are different problems. A kick-drum port, an uncovered vocal plosive, compressed-air cleaning or fast movement of the microphone can stress the ribbon even when the musical level looks acceptable on paper. - **Use a pop filter for close vocals.** Set enough distance that the filter disperses the air pulse before it reaches the ribbon. - **Stay away from ports and wind sources.** Place a ribbon beside or at a safe distance from a kick port rather than directly in the jet of air. - **Move the microphone slowly.** Do not swing it across a room or blow into it to test whether it is connected. - **Lower gain before connecting.** Follow the exact phantom-power rule for the model and use a known-good balanced cable. - **Store it protected.** Use the supplied box, bag or case and keep the microphone away from dust, moisture and accidental impact. ## Which budget ribbon microphone should you buy? **You have a capable, quiet preamp and want the cheapest trial** Choose the **MXL R144**. Keep 48 V off and budget for a pop filter and stable stand. **You want a higher-output passive option below $200** Choose the **Golden Age R2 MKII**. Its strict no-phantom rule makes careful session practice essential. **Your interface preamp is ordinary, but it supplies 48 V** Choose the **Golden Age R1 Active MKIII**. The active buffer is more useful than chasing a cheap passive microphone plus uncertain extra gain. **Several people repatch the studio** Choose the **sE X1 R** for a protected passive design, or the active **VR2** when stronger output is the priority. **You need protective storage in the package** Choose the **Avantone CR-14**. Its case, box and shock mount make the package easier to move and store responsibly. **You are ready for a longer-term passive purchase** Compare the **sE VR1** and **Royer R-10** around preamp load, service expectations and total budget. Do not spend $649 while leaving the stand, cable or gain chain unresolved. For most first-time buyers, the decisive question is not “which ribbon is best?” It is “which ribbon fits the system I already own?” Start with the power rule, preamp and room. Once those three fit, source placement becomes a useful creative choice instead of a troubleshooting exercise. ### How Many Inputs Do You Need on an Audio Interface? URL: https://soundforgepro.com/how-many-inputs-audio-interface/ Last updated: 2026-10-10T13:19:15.000Z **Count the sources you need to record at the same time.** One mono source uses one input; a stereo analog source normally uses two. Then check whether those channels provide the right mix of microphone preamps, line inputs and instrument/Hi-Z inputs. Do not choose an interface from the biggest I/O number on the product page. ## Audio interface input planner SIMULTANEOUS RECORDING · CHANNEL COUNT ### Build your largest likely session Enter only sources that must be captured at the same time. A device you record later does not need a permanent channel in this count. Reset **Microphones**Vocals, amps, acoustic instruments −+ **× 1** **Direct guitar or bass**One instrument/Hi-Z path per source −+ **× 1** **Mono line sources**Mono synth output, preamp or outboard return −+ **× 1** **Stereo keyboards or synths**Left and right analog outputs −+ **× 2** **Drum microphones**Count each microphone separately −+ **× 1** **Planned spare channels**Add only for a specific likely source −+ **× 1** TARGET ANALOG INPUTS**4** **4** in use + **0** planned spare Mic preamps 1 Instrument / Hi-Z 1 Line channels 2 A four-input interface is the first standard size that fits this session. Confirm that two channels accept line level and one accepts an instrument signal. **The total is a target, not a product recommendation.** A four-channel result does not prove that every four-input interface has the required preamps or input modes. Check the channel-by-channel specification. ## The five-step way to count inputs 1 **Choose the largest simultaneous session** Write down the one setup you reasonably expect to record in a single pass. 2 **Count mono sources once** Each microphone, direct guitar, direct bass or mono line output takes one channel. 3 **Count stereo analog sources twice** A keyboard using left and right outputs takes two line-input channels. 4 **Match the electrical input type** Mark how many channels need mic preamps, line mode or instrument/Hi-Z mode. 5 **Add only deliberate headroom** Add a spare channel for a source you are likely to record soon, not for every device you might someday own. COPYABLE SESSION CHECK**Use this before comparing interfaces** Copy checklist Largest simultaneous session: Microphones: __ × 1 = __ Direct guitar/bass: __ × 1 = __ Mono line sources: __ × 1 = __ Stereo analog sources: __ × 2 = __ Drum microphones: __ × 1 = __ Needed now: __ channels Specific near-term spare: __ channels Target total: __ channels Required mic preamps: __ Required instrument/Hi-Z inputs: __ Required line-input channels: __ Headphone feeds: __ Independent monitor pairs: __ Count the session first; compare products second. ## Common recording setups and their arithmetic | Session | Channel arithmetic | Minimum used | Practical target | | ------------------------------------ | ---------------------------------------------------- | ------------ | ----------------- | | **One vocal** | 1 microphone | 1 | 2 inputs | | **Vocal + direct guitar** | 1 mic + 1 instrument | 2 | 2 inputs | | **Stereo keyboard** | Left + right line outputs | 2 | 2 inputs | | **Vocal + stereo keyboard** | 1 mic + 2 line channels | 3 | 4 inputs | | **Vocal + guitar + stereo keyboard** | 1 + 1 + 2 | 4 | 4 inputs | | **Four-person podcast** | 4 microphones | 4 | 4 mic preamps | | **Small drum setup** | 4 microphones | 4 | 4 mic preamps | | **Expanded drum setup** | 8 microphones | 8 | 8 mic preamps | | **Band with four drum mics** | 2 vocals + 2 guitars + 1 bass + 2 keyboard + 4 drums | 11 | 12 or more inputs | The “practical target” rounds up only where a common hardware size is needed to fit the minimum. It does not mean spare channels are always better. If your largest real session uses two channels, paying for eight unused analog inputs may add cost and desk space without improving the recording. ## Mono versus stereo: the easiest place to miscount A microphone is normally recorded to one mono channel. So is a guitar or bass connected directly to an instrument input. [Focusrite’s channel examples](https://support.focusrite.com/hc/en-gb/articles/206849779-Mic-Guitar-heard-on-only-one-side-of-Speakers-Headphones) show a microphone or direct guitar as one mono source, while a guitar and vocal recorded together use two separate channels. A keyboard or synthesizer is different when you want its stereo output. Its left and right analog outputs feed two inputs, which Focusrite also explains in its guidance on [recording stereo line-level equipment through two mono interface inputs](https://support.focusrite.com/hc/en-gb/articles/26494786477202-I-m-getting-little-or-no-signal-from-my-line-level-equipment). If the instrument has a dedicated mono output and you are happy to record it in mono, it uses one channel instead. ![Channel plan showing one microphone, one direct guitar and a stereo keyboard using four audio interface inputs](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/09/inline-four-input-channel-plan.webp) One microphone uses one channel, one direct guitar uses one, and a stereo keyboard uses two: 1 + 1 + 2 = 4 inputs. MICROPHONE**1** *+* DIRECT GUITAR**1** *+* STEREO KEYBOARD**2** *\=* INPUTS**4** A MIDI controller does not use an analog audio input merely because it controls a software instrument. Count analog inputs only when you record audio from the keyboard’s own outputs or another hardware sound source. ## Four sockets can still be the wrong four sockets After calculating the channel total, label every channel by source type: MIC**Microphone preamp** Needed for microphones connected at mic level. Four podcast microphones require four simultaneous microphone preamps, not one preamp and three line-only channels. LINE**Line input** Used for keyboards, synthesizers, external preamps and other line-level sources. A stereo keyboard usually needs two line channels. INST**Instrument / Hi-Z** Used for a passive guitar or bass connected directly. A socket that accepts line level does not automatically provide the appropriate high-impedance mode. Manufacturers may place XLR and quarter-inch connectors in one combo socket. That provides connector and mode flexibility, but it remains **one simultaneous channel**. You cannot record an [XLR microphone](https://soundforgepro.com/usb-vs-xlr-microphone/) and a quarter-inch guitar through the same combo socket at the same time. **Do not count holes in the front panel.**Count simultaneous channels, then verify what each numbered channel accepts. ## Why advertised I/O is not the mic-preamp count A large headline number can combine several categories. Focusrite’s current [Scarlett 18i20 specifications](https://us.focusrite.com/products/scarlett-18i20), for example, list 26 simultaneous inputs while separately listing eight microphone preamps, eight line inputs, instrument inputs, ADAT, S/PDIF and loopback channels. Audient’s [iD24 specifications](https://audient.com/products/audio-interfaces/id24/tech-specs/) describe ten input channels as two analog plus eight digital. Neither example means there are 26 or ten microphone sockets. Read the specification in this order: 1. **Simultaneous analog input channels** — the sources you can physically connect and record at once. 2. **Mic preamps** — how many microphones can run without external preamps. 3. **Instrument/Hi-Z channels** — how many guitars or basses can connect directly. 4. **Digital inputs** — ADAT or S/PDIF paths that require compatible external hardware. 5. **Loopback channels** — internal routing paths, not extra physical sockets. ## When two, four or eight inputs make sense 2 INPUTS**Solo and overdub recording** Enough for one vocal plus one direct instrument, a stereo keyboard, or two microphones. It fits well when parts are recorded one after another. 4 INPUTS**Small simultaneous setups** Useful for vocal plus stereo keyboard, a four-mic podcast, or a compact drum setup. Check that the four channels include the modes you need. 8 INPUTS**Drums and ensembles** Useful when several microphones must remain separate, such as an eight-mic drum session or a small band tracked together. 12+ INPUTS**Larger live sessions** Relevant when a band’s vocals, instruments, stereo sources and drum microphones must all be recorded in one pass. Choose the smallest arrangement that handles your largest realistic session cleanly. If an eight-channel drum recording is a real plan for next month, expansion matters. If it is only a vague possibility, a smaller interface may be the better purchase. ## ADAT and S/PDIF can expand a system, with conditions An interface with digital input can accept channels from a compatible external preamp or converter. That can be a sensible path when you need two channels today and more microphone inputs later. But the connector alone does not guarantee a fixed number of added channels. Channel capacity can fall as sample rate rises. Current examples show the dependency clearly: the Scarlett 18i20 lists 16 ADAT channels at 44.1/48 kHz and up to eight at 96 kHz, while Audient documents [eight ADAT channels at 44.1/48 kHz](https://support.audient.com/hc/en-us/articles/12670713792404-iD24-ADAT-setup) and four at 88.2/96 kHz for the iD24\. These are model-specific examples, not a universal ADAT promise. Before counting digital expansion, verify the interface, external device, optical-port mode, supported sample rates and clocking arrangement. If the future setup requires eight additional preamps at 96 kHz, check that exact condition rather than relying on the number printed beside “ADAT.” ## Inputs are only half of the hardware check The recording count answers how many sources enter the interface. It does not answer how many people can hear independent mixes or how many speaker systems can remain connected. - **Monitor outputs:** count the speaker pairs or external destinations you need connected. - **Headphone outputs:** one socket may be insufficient for two performers, even when the interface has enough inputs. - **Independent cue mixes:** two headphone sockets do not necessarily mean two separately routable mixes. - **Direct monitoring:** Focusrite defines [direct monitoring](https://support.focusrite.com/hc/en-gb/articles/207546305-What-is-direct-monitoring) as routing an input directly to headphone or line outputs while it is also sent to the recording software. Check how the chosen hardware handles mono, stereo and mix control. - **Application limits:** some conferencing and streaming software accepts only mono or stereo input even when the hardware exposes more channels. Focusrite documents this constraint for [some Windows video-call applications](https://support.focusrite.com/hc/en-gb/articles/360016391940-Using-multiple-Inputs-in-Windows-Video-Call-Software). ## The final purchase check Write one sentence: *“My largest likely session is…”* List the sources, add the channels, and label each as mic, line or instrument. Then compare interfaces against that finished requirement. **A good input count is boringly specific.** “Four channels: one mic preamp, one instrument input and two line inputs for a stereo keyboard” is a useful requirement. “As many inputs as possible” is not. ### Speaker Wire Size Calculator: AWG by Length and Ohms URL: https://soundforgepro.com/speaker-wire-size-calculator/ Last updated: 2026-10-08T06:30:10.000Z **Speaker wire is sized from the full electrical loop, not the one-way distance printed on a floor plan.** Enter the distance from amplifier to speaker, nominal speaker impedance and conductor material. The calculator recommends the thinnest listed AWG that keeps round-trip cable resistance within your chosen limit. ## Speaker wire size calculator SPEAKER CABLE · ROUND-TRIP RESISTANCE ### Choose wire gauge by run length and load The default recommendation keeps cable resistance at or below 3% of nominal speaker impedance. Reset One-way run ftm Nominal impedance 2 Ω4 Ω6 Ω8 Ω16 Ω Conductor Copper 10% CCA estimate Cable-resistance limit **%** Nominal RMS power *optional* **W** **Copper model:** published DC resistance at 20°C. Power changes the watt estimates, not the recommended AWG. RECOMMENDED GAUGE**16 AWG**Thinnest listed gauge within the 3% limit HEADROOM**0.49 percentage points**2.51% cable-to-load resistance ratio Round-trip cable 50 ft Cable resistance 0.201 Ω Voltage at nominal load 97.55% Level change −0.22 dB Speaker-power reduction 4.84% Estimated speaker power 95.16 W Estimated cable heating 2.39 W **What the threshold means:** the selected percentage is *cable resistance divided by nominal speaker impedance*. It is not the percentage of amplifier power lost. GAUGE COMPARISON**Every listed size with the current inputs** “Within limit” uses the resistance ratio, not the power-reduction column. | AWG | Cable R | R / nominal Z | Level | Speaker-power reduction | Result | | --- | ------- | ------------- | ----- | ----------------------- | ------ | ## What the recommendation actually limits A speaker cable sits in series with the speaker. Longer and thinner conductors add more resistance, so a little less voltage reaches the nominal load. This calculator compares the complete cable-loop resistance with the impedance value you selected. At the default 3% limit, an 8-ohm speaker permits up to 0.24 ohm of round-trip cable resistance. That 3% figure is a design choice, not a universal safety rule. Tighten it when the run is long or the load is low; loosen it only when the resulting level and power figures are acceptable for the job. A 2-ohm load reaches the same resistance ratio with one quarter of the cable resistance allowed for an 8-ohm load. **Read the result in this order** **AWG** answers the sizing question. **R / nominal Z** shows whether that gauge meets your chosen threshold. **Level and power** show different consequences of the same series resistance. ## How the calculation works The distance input is one way, but current travels through two conductors: out to the speaker and back to the amplifier. The calculator doubles the run, then applies the conductor’s DC resistance per 1,000 feet. Its copper table uses 20°C values from the [MWS Wire Industries technical book](https://mwswire.com/wp-content/uploads/2024/01/MWS-techbook.pdf). AWG dimensions and resistance calculations are standardized in [ASTM B258](https://store.astm.org/standards/b258). ![Amplifier-to-speaker cable path showing one-way distance and the full outgoing-and-return conductor loop](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/09/inline-speaker-wire-loop.webp) A 25-foot speaker run contains 50 feet of conductor in the electrical loop: 25 feet out and 25 feet back. Round-trip length**2 × one-way run** Cable resistance**round-trip length × Ω per unit length** Voltage ratio**Zspeaker ÷ (Zspeaker + Rcable)** Level change**20 × log10(voltage ratio)** Speaker-power ratio**voltage ratio²** The calculator treats the amplifier as an ideal voltage source and the selected speaker impedance as a fixed resistive load. That simplified model is useful for comparing wire sizes consistently. It does not turn a speaker’s nominal impedance into a constant real-world value. ## Worked example: 25 feet, 8 ohms, 16 AWG A 25-foot one-way run contains 50 feet of conductor. At 4.019 ohms per 1,000 feet, 16 AWG copper contributes 0.20095 ohm. Dividing that by an 8-ohm nominal load gives a 2.5119% resistance ratio, so 16 AWG fits a 3% threshold. Cable resistance**0.20095 Ω** Voltage ratio**97.55%** Level change**−0.215 dB** Speaker-power reduction**4.841%** At 100 W nominal**95.16 W at load** Cable heating estimate**2.39 W** The figures are not interchangeable. The 2.5119% resistance ratio is a sizing threshold. The 4.841% figure is the modeled reduction in power delivered to the nominal load relative to the same voltage source with no cable resistance. The level change is expressed separately in decibels. ## Copper versus the 10% CCA estimate The copper-clad-aluminum option is deliberately narrow. It models **10% CCA at 62.9% IACS conductivity**, the value listed in the MWS Wire Industries table for [10% copper-clad aluminum](https://mwswire.com/clad-metals-wire/). The calculator therefore multiplies the copper resistance by about 1.5898. “CCA” is not one universal conductor specification. Copper proportion, aluminum alloy, strand geometry and product construction can differ. If a manufacturer publishes resistance for the exact cable, use that value instead of treating this estimate as a product certification. COPPER**Base resistance table** 20°C DC-resistance values for the listed AWG sizes. 10% CCA ESTIMATE**1.5898× copper resistance** Based only on the stated 62.9% IACS conductivity assumption. ## Does amplifier power change the recommended gauge? Not in this resistance-ratio model. Length, conductor resistance and nominal speaker impedance determine the relative voltage and power ratios. Entering 50 W or 500 W changes the estimated watts reaching the speaker and the watts dissipated in the cable, but it does not change which AWG meets a 3% resistance limit. Power still matters outside this narrow comparison. Terminations, insulation temperature, bundling, installation method and product ratings all affect whether a cable is suitable. The calculator is not an ampacity or electrical-code tool. ## Where this model stops A loudspeaker is not a fixed resistor. Its impedance changes with frequency, and a nominal 8-ohm speaker may rise well above or dip below that figure across its operating range. The calculator uses nominal impedance because it is a practical input for comparing gauges; it cannot predict the exact frequency response of a specific amplifier, crossover, cable and loudspeaker combination. - **Temperature:** conductor resistance changes as temperature changes. The [published copper resistance table](https://mwswire.com/wp-content/uploads/2024/01/MWS-techbook.pdf) uses a 20°C reference; this calculator does not apply a temperature correction. - **Connections:** plugs, binding posts, splices and oxidation can add resistance that is not included here. - **Construction:** published cable resistance may differ from a nominal AWG table, particularly for clad conductors and unusual strand designs. - **Reactive behavior:** capacitance and inductance are outside this short-run resistance model. For in-wall, outdoor, plenum or other regulated installations, gauge alone is not enough. Check the jacket and use markings for the intended location. The [UL wire and cable guide](https://www.ul.com/thecodeauthority/knowledge/wire-cable-guide) explains why location and use designations must be checked separately. ## Speaker wire is not amplifier power wire This page sizes the cable between an audio amplifier’s output and a loudspeaker. It does not size the DC cable from a battery or power supply to an amplifier. That separate job depends on supply voltage, current draw, fuse protection, run length and installation conditions. A car-audio power-wire chart cannot be substituted for the speaker-cable calculation here. Once both speakers are wired, run the [left and right speaker test](https://soundforgepro.com/left-right-speaker-test/) to confirm channel assignment. If bass collapses when both channels play together, [recheck polarity at every terminal](https://soundforgepro.com/speaker-polarity-test/) before blaming cable gauge. ### Best Sampler Software by Workflow: Chopping, Instruments, Drums and Mobile URL: https://soundforgepro.com/sampler-software/ Last updated: 2026-10-06T07:03:47.000Z **The best sampler software depends on what you need to do with audio.** Serato Sample fits fast chopping and flipping, Kontakt 8 fits detailed multisampled instruments, Groove Agent 6 fits drum-centered work, Waves CR8 fits layered creative sampling, Koala fits mobile capture, and Decent Sampler fits free library playback. Before buying anything, check whether your DAW already covers the job. CHOOSE BY THE JOB **Chop a loop quickly**Serato SampleSlicing, stems, pitch and time tools **Build an instrument**Kontakt 8Zones, mappings, groups and wave editing **Program drums**Groove Agent 6Kits, patterns, grooves and personal samples **Work on a phone or tablet**Koala SamplerCapture, sequence, resample and export **Play free libraries**Decent SamplerFree player for dspreset and dslibrary instruments ## Start with the sampling job, not the product list “Sampler” describes several different tools. One turns a four-bar loop into playable slices. Another maps hundreds of recordings across notes and velocities. A drum sampler organizes pads, patterns and kit pieces. A mobile sampler prioritizes immediate recording and resampling. A library player may load finished instruments but offer little authoring depth. That is why a single numbered ranking is misleading. A producer who wants to flip a vocal phrase should not evaluate software by the same criteria as a sound designer building a chromatically sampled instrument. Define the job first, then compare products inside that category. 01 ### Chopping and flipping Fast slicing, tempo sync, pitch control, stem separation and pad triggering. 02 ### Multisampled instruments Key and velocity mapping, zones, groups, looping and detailed sample editing. 03 ### Drum sampling Pad layout, kits, pattern editing, groove libraries and separate mixer routing. 04 ### Creative layering Several sample layers, keyboard zones, modulation and effects inside one instrument. 05 ### Mobile capture Recording, sequencing, resampling and practical export from a phone or tablet. ![Sampling workflow that routes recorded audio into loop chopping, multisampled instruments, drum kits, layered sound design and mobile beat making](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/09/inline-sampler-workflow.webp) Start with the source audio, then choose the sampler category that matches the work you need to finish. ## Do you need another sampler at all? Most current DAWs include at least one sampling tool. That built-in option has a practical advantage: it follows the DAW’s browser, automation, routing and project-saving conventions. If it already imports your audio, creates the required slices or zones, and recalls the project reliably, another plug-in may add choice without removing a real bottleneck. **Check the sampler you already own** - Can it import your own recordings and the formats you actually keep? - Can it slice, map or layer samples in the way the project requires? - Can you route pads or groups separately when the mix needs it? - Does the project reopen correctly on every computer you use? - Is the missing feature worth adding another license, installer and dependency? A third-party sampler makes sense when the missing capability is specific: stem-based chopping, deep instrument construction, a drum-pattern environment, cross-platform mobile capture or access to a particular library ecosystem. Buy for that gap rather than for the longest feature list. ## Sampler software comparison by workflow | Sampler | Best fit | Why it belongs in that category | Check before choosing | | ------------------ | ------------------------------ | ---------------------------------------------------------------------------- | ---------------------------------------------------------------- | | **Serato Sample** | Fast chopping and flipping | Sync, slicing, stem isolation, pitch/time processing, cue pads | Plug-in format and host support | | **Kontakt 8** | Multisampled instruments | Zones, MIDI and pitch mapping, Group, Mapping and Wave editors | Authoring depth, library requirements and project portability | | **Groove Agent 6** | Drum sampling | Acoustic and electronic kits, pattern editor, MIDI grooves, personal samples | Host compatibility and whether you need its pattern environment | | **Waves CR8** | Creative layered sampling | Up to eight layers, loops or one-shots, keyboard zones | Current supported hosts and how collaborators will recall it | | **Koala Sampler** | Mobile capture and beat making | Mic recording, sequencing, resampling, effects, MIDI and WAV export | Platform-specific export features | | **Decent Sampler** | Free library playback | Free player for dspreset and dslibrary instruments | Whether playback is enough or you need deep instrument authoring | These are job-based recommendations, not a claim that one product sounds better or performs more efficiently than another. Vendor documentation can establish formats and functions. It cannot establish a universal winner for every producer, computer and project. ## Best for chopping and flipping: Serato Sample Serato Sample is the clearest fit when the source is an existing track or loop and the goal is to find pieces, rearrange them and keep the result in time. The current [Serato Sample product page](https://serato.com/sample) lists sync, chopping, stem isolation, pitch shifting and time stretching. It also supports up to 32 cue points mapped to pads, with triggering from a computer, MIDI hardware or a piano roll. The per-pad output option matters once the idea moves into the mix. Individual pads can go to different channels for separate EQ, effects and level control. Serato supplies Sample as a VST, AU and AAX plug-in, so this is a host-based choice rather than a standalone instrument-building environment. **Choose it when**The repeated task is turning finished audio into playable slices quickly.**Look elsewhere when**You need detailed key zones, velocity layers or a standalone multisampled library workflow. ## Best for building multisampled instruments: Kontakt 8 Kontakt 8 fits the opposite end of the spectrum: turning many recordings into a structured playable instrument. In [Native Instruments’ Classic view documentation](https://docs.native-instruments.com/ni-tech-manuals/kontakt-manual/en/classic-view), a Zone wraps one sample with information about the MIDI data that triggers it and the pitch at which it was recorded. The same documentation describes the Group, Mapping and Wave editors used to organize and shape that structure. Kontakt can run standalone or as a plug-in. Current [Kontakt compatibility information](https://www.native-instruments.com/products/kontakt) lists VST3, AU and AAX on macOS where applicable, and VST3 and AAX on Windows. When loaded as a plug-in, it receives MIDI from the DAW and sends audio to the DAW mixer. That depth is useful only if the project needs it. If your entire task is slicing one loop into pads, a large instrument-authoring environment can slow down the decision rather than improve it. Kontakt belongs on the shortlist when mappings, groups, zones and reusable instruments are the work. ## Best for drum-centered sampling: Groove Agent 6 Groove Agent 6 combines sampling with a drum and beat-making environment. [Steinberg describes acoustic kits, electronic sounds and percussion](https://www.steinberg.net/vst-instruments/groove-agent/), five acoustic kits, a pattern editor, more than 1,000 MIDI grooves and patterns, and support for personal samples in Beat Agent. This makes it more than a grid that fires one-shots. The pattern and groove layer can be valuable when drum programming is part of the same decision. It is less compelling if you already prefer your DAW’s sequencer and only need a lightweight pad instrument. **Choose it when**Drum kits, pattern construction and sample triggering belong in one environment.**Look elsewhere when**You want a general-purpose melodic instrument builder or the fastest possible loop slicer. ## Best for creative layering: Waves CR8 Waves CR8 sits between a simple slicer and a deep library platform. The [CR8 manual](https://www.waves.com/1lib/pdf/plugins/cr8.pdf) documents up to eight sampler layers made from one-shots or loops. Those layers can be mixed together or spread across MIDI keyboard zones. Samples can be dragged from a DAW or computer and played from a MIDI keyboard. That design suits one-off playable textures, layered hits and evolving patches built from personal audio. It is a practical candidate when several samples need to behave as one instrument but a full library-authoring system would be excessive. Check the current host list before committing a project to it. Compatibility tables change, and a collaborator needs the same plug-in and access to the same source files for dependable recall. ## Best for mobile sampling: Koala Sampler Koala prioritizes capture and immediacy. Its [official description covers recording through a phone microphone](https://koalasampler.com/), loading personal sounds, sequencing beats, adding effects and resampling the app’s output. It also lists MIDI control, Ableton Link and WAV export. The [current Koala manual lists iOS, Android, Mac and Windows availability](https://manual.koalasampler.com/). One export detail is platform-specific: Koala lists Ableton Live Set export as iOS only. Treat that as a compatibility condition, not a minor footnote, if the mobile project must move into a particular desktop session. Koala is the strongest choice here when the phone or tablet is part of the instrument. It is not a substitute for detailed multisample mapping, and temporary desktop offers should not be mistaken for permanent pricing. ## Best free option for playing libraries: Decent Sampler [Decent Sampler](https://www.decentsamples.com/product/decent-sampler-plugin/) is a free player for libraries in the `dspreset` and `dslibrary` formats. Its current download page provides plug-in and standalone options across Windows, macOS and Linux, plus AUv3 and standalone operation on iOS. The word “player” defines the expectation. It is useful when the target library already exists in the Decent Sampler ecosystem and you need a no-cost way to play it. It should not be presented as a feature-for-feature replacement for Kontakt’s deeper instrument-authoring workflow. Free software also does not make every downloadable library free for every use. Read the library’s own license before assuming you can redistribute its samples, use them in templates or package them inside another instrument. ## Compatibility checks that prevent broken projects A sampler can fit the musical job and still be wrong for the production setup. Run these checks before building a project around it. 1. **Operating system and processor.** Use the current vendor requirements for every computer that must open the project. 2. **Plug-in format.** Confirm that the host loads the supplied VST3, AU, AAX or other required format. The product name alone does not prove host compatibility. 3. **Standalone operation.** Decide whether you need the sampler outside a DAW for performance, library work or sound preparation. 4. **Personal sample import.** Check the exact file types, channel formats and length limits used by your archive. Use the [WAV, FLAC and MP3 format guide](https://soundforgepro.com/wav-vs-flac-vs-mp3-editing-mastering-archive/) when deciding what to keep editable, lossless or compact. Do not assume every sampler accepts every file. 5. **Project recall.** Keep the original recordings, note the plug-in version and test how the project locates moved files before collaboration or archiving. 6. **Export path.** Confirm whether you need stems, MIDI, a DAW-specific project, a reusable instrument or only a rendered WAV. ## Plan project portability before the sampler becomes essential Sampler sessions depend on more than the plug-in file. They can depend on external recordings, library folders, expansion licenses, plug-in versions and paths that exist on only one machine. A project that opens today may fail after a drive move or on a collaborator’s computer. Keep a project-local copy of recordings when the license permits it, preserve the original file names and render important parts to audio before archiving. Large uncompressed libraries grow quickly, so estimate their storage with the [audio file size calculator](https://soundforgepro.com/audio-file-size-calculator/) before copying them across several machines or backup drives. For an instrument you expect to revise later, also keep notes about root pitches, mappings and processing. Printed audio is the fallback; it should not be the only surviving record of how the instrument was built. ## Sampler software and sample rights are separate decisions Buying a sampler does not clear the audio loaded into it. There are at least three separate permissions to check: the software license, the license for any included library, and the rights to recordings imported by the user. The [US Copyright Office explains](https://www.copyright.gov/music-modernization/sound-recordings-vs-musical-works.pdf) that a musical work and a sound recording are separate works that may be owned and licensed separately. Its [guidance on sound recordings](https://www.copyright.gov/circs/circ56a.pdf) also states that copyright in a recording is not a substitute for copyright in the underlying composition. **Before using imported audio** Who owns or licenses the sound recording? Does the underlying composition require separate permission? What does the library license allow in released music, client work and templates? Does it prohibit redistribution of isolated samples or instrument files? This is a practical checking framework, not legal advice. When the source is commercially released music or the planned use is unclear, get advice for that specific recording and use. ## Which sampler should you choose? | Your situation | Start with | Reason | | ------------------------------------------------------ | ------------------ | ------------------------------------------------------------------------------------------- | | You want to chop and rearrange tracks or loops | **Serato Sample** | Its documented workflow centers on sync, slicing, stems, cue pads and pitch/time changes. | | You are constructing a detailed playable instrument | **Kontakt 8** | Zones and dedicated mapping, group and wave editors match that job. | | You want drums, patterns and grooves together | **Groove Agent 6** | The drum environment includes kits, pattern editing, grooves and personal samples. | | You want layered playable textures from personal audio | **Waves CR8** | Eight-layer stacking and keyboard zones fit compact creative instruments. | | You capture ideas on a phone or tablet | **Koala Sampler** | Recording, sequencing, resampling and export are built around an immediate mobile workflow. | | You need to play compatible free libraries | **Decent Sampler** | It is a free player for the Decent Sampler library formats. | My decision rule is to name the finished result before naming the product. “I need to turn this loop into 16 playable slices” is useful. “I need the most powerful sampler” is not. Once the job is concrete, the unnecessary products fall away quickly. Start with the sampler already in your DAW. Move to a third-party option only when a documented feature removes a real limitation, and make compatibility, project recall and sample rights part of the choice from the beginning. ### Bass vs Treble: What They Change and How to Balance Them URL: https://soundforgepro.com/bass-vs-treble/ Last updated: 2026-10-06T05:19:43.000Z **Bass is the low part of sound—the weight, thump and rumble—while treble is the high part—the attack, brightness and fine detail.** Neither should automatically be higher than the other. Start with both controls centered, identify the problem you can actually hear, and make one small change at a time. THE SHORT VERSION **Bass**Weight, body and low-end movementToo much sounds boomy or muddy **Treble**Attack, brightness and fine detailToo much sounds sharp or brittle **Best starting point**Flat or centered controlsChange one control, then compare ## Bass vs treble: the practical difference | Question | Bass | Treble | | ----------------------- | ---------------------------------------- | -------------------------------------------- | | **Where is it?** | Lower-frequency region | Higher-frequency region | | **What do you notice?** | Kick impact, bass notes, warmth, rumble | Cymbal attack, consonants, string noise, air | | **Too much** | Boomy, muddy, swollen, masks other parts | Harsh, hissy, brittle, tiring | | **Too little** | Thin, weak, lacking weight | Dull, veiled, lacking definition | | **Simple control** | Broad low-frequency boost or cut | Broad high-frequency boost or cut | The labels describe broad regions inside one continuous spectrum. They are useful listening words, not walls. A bass guitar produces harmonics well above the bass region, and a cymbal produces energy across more than the top octave. The same is true of speech: its fundamental pitch and its intelligibility cues do not live in one tidy box. ![Audio spectrum moving from broad low-frequency bass waves through musical midrange detail to fine treble oscillations](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/09/inline-bass-vs-treble.webp) Bass, midrange and treble overlap inside one continuous spectrum. The edges are working ranges, not universal cutoffs. ## What frequency ranges count as bass and treble? A useful beginner map places bass in the low end, midrange through the center, and treble toward the top. You will often see bass described as roughly 20–250 Hz and treble as roughly 4–20 kHz. Treat those figures as orientation, not a standard that every speaker, EQ or tone knob follows. LOW ### Bass About 20–250 Hz Rumble, kick weight, bass fundamentals CENTER ### Midrange About 250 Hz–4 kHz Most musical body, voice and definition HIGH ### Treble About 4–20 kHz Attack, brightness, sibilance and air Real controls use curves rather than hard borders. One Yamaha receiver, for example, specifies a bass turnover at 350 Hz and a treble turnover at 3.5 kHz; another device can use different points and a different boost or cut range. That variation is why [the manufacturer’s tone-control specification](https://manual.yamaha.com/av/17/rxa3060/en/pages/c6%5Fsf11.html) matters more than a generic chart when you need an exact answer. For a more detailed breakdown of sub-bass, low mids, presence and air, use the [audio frequency chart](https://soundforgepro.com/audio-frequency-chart/). This page stays with the broader decision: what to change when the playback sounds too heavy, thin, harsh or dull. ## What does the bass control change? A bass control raises or lowers a broad low-frequency range. Boosting it can add weight to kick drums, bass lines, low piano notes and cinematic effects. Cutting it can reduce boom and make a crowded low end easier to follow. More bass is not the same as better bass. A large boost can use amplifier and speaker headroom quickly, hide midrange detail and exaggerate room resonances. If the sound is boomy at one seat but weak at another, the control may be compensating for placement or the room rather than fixing the cause. **If bass sounds wrong** **Too much:** try a small bass cut after checking speaker position and room boundaries.**Too little:** check polarity, placement and headphone seal before adding boost. ## What does the treble control change? A treble control raises or lowers a broad high-frequency range. A modest boost can make attacks and quiet details easier to notice. A modest cut can calm sharp cymbals, hiss or an overly bright speaker. Treble is not a master “clarity” control. Speech intelligibility and musical definition also depend heavily on the midrange. If dialogue is buried under music or effects, pushing the treble high may add hiss and sibilance without solving the balance. Start with the mix mode, center channel or dialogue setting when the device provides one. **If treble sounds wrong** **Too much:** lower it slightly and check whether the listening level itself is tiring.**Too little:** check speaker angle, obstructions and hearing-safe playback before adding boost. ## Frequency is not volume Hertz and decibels answer different questions. Hertz describes how often a waveform repeats each second and places it in a pitch region. Decibels describe level or a change in level. Turning up the treble does not move a sound to a higher pitch, and turning up the bass does not simply raise the whole system’s volume. Hz ### Where in the spectrum? Low numbers correspond to slower cycles and lower pitch regions; high numbers correspond to faster cycles and higher regions. dB ### How much level or change? A tone control may add or subtract decibels from a broad part of the spectrum while leaving other regions less affected. Our hearing is also less sensitive at some frequencies than others. The [NIDCD explanation of frequency and decibel measurement](https://www.nidcd.nih.gov/health/how-sound-measured) describes this frequency-dependent response. It helps explain why equal meter readings do not guarantee equal perceived loudness across the spectrum. ## How to set bass and treble without guessing 1. **Start centered or flat.**Disable loudness, bass boost, virtual surround and preset EQ while you establish a reference. 2. **Name one problem.**Choose a concrete word such as boomy, thin, harsh or dull. “Not exciting enough” is too vague to guide a useful adjustment. 3. **Check the physical setup.**Look at [speaker placement](https://soundforgepro.com/speaker-placement-calculator/), room boundaries, headphone seal and anything blocking a driver before using tone controls as a repair tool. 4. **Move one control a little.**Use a small step, then listen to the same passage. Leave the other control alone so you know what caused the change. 5. **Compare at matched loudness.**A louder setting often seems better for a moment. Reduce the overall volume if a boost made the comparison louder. 6. **Stop when the problem is solved.**Do not keep turning the knob because the first change helped. Extreme settings usually trade one fault for another. My rule is simple: if you cannot describe what improved, return to center. A repeatable small correction is more useful than a dramatic curve you cannot explain. ## Which control should you change? | What you hear | First check | Small adjustment to try | | ---------------------------- | ---------------------------------------------------- | -------------------------------------------------------------------- | | **Boomy or swollen** | Speakers close to a wall or corner; room resonance | Reduce bass slightly | | **Muddy** | Low-mid buildup; several parts competing | A bass knob may help, but a targeted EQ is usually better | | **Thin or weak** | Speaker polarity, headphone seal, listening position | Add a small bass boost only after the physical checks | | **Harsh or brittle** | Playback level, bright recording, speaker angle | Reduce treble slightly | | **Hissy or overly sibilant** | Source noise or vocal sibilance | A treble cut may soften it; targeted EQ or de-essing is more precise | | **Dull or veiled** | Obstruction, off-axis speakers, worn pads | Add a small treble boost after checking the setup | | **Dialogue still unclear** | Midrange balance, center channel, mix mode | Do not assume more treble is the answer | ## Bass and treble settings for speakers and soundbars Begin with the controls centered and the speakers placed symmetrically. Pulling a speaker away from a wall or corner can reduce boundary reinforcement before you touch the bass control. Moving the listening position can also [change the low end](https://soundforgepro.com/bass-test/) more than a small tone adjustment. For a soundbar, keep the bass moderate enough that effects do not cover dialogue. If speech remains hard to understand, check the dialogue, center, night or clear-voice modes before adding a large treble boost. Those controls may address the relevant channel or dynamic range more directly. If the problem changes sharply from seat to seat, use an [audio spectrum analyzer](https://soundforgepro.com/audio-spectrum-analyzer/) as a diagnostic aid and compare several positions. The graph can show where energy changes, but it does not choose a preferred tonal balance for you. ## Bass and treble settings for headphones With over-ear and in-ear headphones, fit comes first. A weak seal can remove bass, while pad wear or a shifted ear position can alter the balance. Fix the fit before compensating with EQ; otherwise the correction may be wrong the next time the seal changes. Headphones also remove the room from the playback path, but the model’s tuning and your anatomy still affect what reaches the eardrum. Use familiar recordings, keep the overall level steady and avoid copying somebody else’s bass and treble numbers without the same device. For production work, a colored playback chain can push decisions in the opposite direction. [Yamaha’s neutral-monitoring guidance](https://hub.yamaha.com/proaudio/recording/the-importance-of-neutral-monitoring-in-the-home-studio/) explains the basic trap: exaggerated bass or treble can lead a mixer to remove those regions, producing a mix that translates poorly elsewhere. ## When bass and treble controls are not enough | Tool | What it changes | Use it for | | --------------------------------------------------------------------------- | ---------------------------------------- | ---------------------------------------------------- | | **Bass and treble controls** | Two broad low and high regions | Fast overall tonal balance | | **Graphic EQ** | Several fixed frequency bands | Broad correction with more control | | **[Parametric EQ](https://soundforgepro.com/parametric-eq-vs-graphic-eq/)** | Selectable frequency, gain and bandwidth | Specific resonances, mud, harshness or surgical work | Use the simplest control that solves the problem. Two knobs are enough when the whole playback is broadly too dark or too heavy. A narrow ring, boxy voice or one aggressive cymbal area needs a more precise tool. The [Sound Forge equalizer guide](https://soundforgepro.com/how-to-use-equalizer-sound-forge-pro/) covers that software workflow without turning this beginner comparison into an editing tutorial. ## Tone balance does not make a loud level safe Cutting treble may make loud playback feel less sharp, but it does not remove the risk created by excessive level and exposure time. The [NIDCD overview of noise-induced hearing loss](https://www.nidcd.nih.gov/health/noise-induced-hearing-loss) explains that both sound level and exposure duration affect risk. Set a comfortable overall volume first. Use tone controls for balance, not as permission to listen louder. ## So, should treble be higher than bass? No universal ratio works across rooms, speakers, headphones and recordings. Center both controls, solve the physical setup first, then adjust the specific symptom in a small step. If the sound becomes fuller without turning muddy, or clearer without turning harsh, the setting is doing its job. The useful setting is the one you can explain and repeat. Keep it close enough to neutral that different recordings still retain their own character, and use a more precise EQ only when the problem has a specific frequency rather than a broad tonal tilt. ### What Is a Condenser Microphone? How It Works and When to Use One URL: https://soundforgepro.com/what-is-a-condenser-microphone/ Last updated: 2026-10-04T20:03:15.000Z **A condenser microphone turns sound into an electrical signal with a thin conductive diaphragm and a fixed backplate that form a capacitor.** Its capsule and active electronics need power, but that does not mean every condenser uses 48-volt phantom power. The right choice depends on the source, recording distance, room noise, polar pattern, self-noise and maximum sound level. THE SHORT VERSION **Best fit**Detailed voice and instrument recording in a controlled space **Needs power**Yes, but the source may be phantom power, USB, a battery or a dedicated supply **Check first**Polar pattern, sensitivity, self-noise, maximum SPL and connector type ## What is a condenser microphone? “Condenser” is the older name for a capacitor. Inside the capsule, a lightweight diaphragm sits very close to a rigid backplate. Together they act as the two plates of a capacitor. When sound moves the diaphragm, the distance between the plates changes, so the capacitance changes with the waveform. [DPA defines this as an electrostatic microphone design](https://www.dpamicrophones.com/dict/condenser-microphone/); it is a different way of converting acoustic movement than the moving-coil mechanism in a typical [dynamic microphone](https://soundforgepro.com/dynamic-vs-condenser-microphone/). The capsule signal has extremely high impedance and cannot simply travel down a normal microphone cable on its own. An impedance converter and other active electronics turn it into a useful output. [Neumann’s capsule explanation](https://www.neumann.com/en-us/knowledge-base/neumann-im-homestudio/homestudio-academy/what-is-a-condenser-microphone) shows the diaphragm, backplate and impedance-conversion stages as separate parts of the same system. 1**Sound wave**moves the diaphragm **→** 2**Capacitance changes**in step with the waveform **→** 3**Active electronics**produce a usable mic-level signal ## Does a condenser microphone need phantom power? A condenser needs power for its active circuitry, but [**48 V phantom power**](https://soundforgepro.com/what-is-phantom-power/) **is only one delivery method**. Many studio XLR condensers use P48 from an audio interface, mixer or external preamp. USB microphones receive power over USB. Compact electret microphones may use low-voltage plug-in power, some models accept batteries, and tube microphones commonly ship with a dedicated supply. | Microphone connection | Likely power source | What to check | | --------------------------------------- | --------------------------------- | --------------------------------------------------------------------- | | Professional XLR condenser | Often 48 V phantom power | The voltage range in the manual and whether the interface supplies it | | USB condenser | USB bus power | Supported port, cable and operating-system requirements | | 3.5 mm electret lavalier or compact mic | Often plug-in power | Device compatibility; plug-in power is not the same system as P48 | | Battery-capable condenser | Internal battery or phantom power | Battery type, switch position and allowed alternatives | | Tube condenser | Dedicated external supply | Use only the specified supply and cable | Phantom power places equal DC voltage on the two signal conductors of a balanced XLR connection while the audio travels over the same cable. [Shure’s phantom-power explanation](https://service.shure.com/articles/en%5FUS/Knowledge/what-is-phantom-power) describes why equal voltage does not become part of the differential audio signal. That design does not make every adapter, damaged cable or microphone safe. Use the power method named by the microphone manufacturer. **Do not improvise the power connection.**A 3.5 mm microphone that expects plug-in power should not be connected directly to a P48 input through a passive shape-changing adapter. A compatible active adapter must translate the connection and power system. ## What does a condenser microphone sound like? There is no single “condenser sound.” The category includes tiny lavalier capsules, pencil microphones, large studio models, measurement microphones and stage condensers. Capsule size, tuning, polar pattern, electronics and placement can matter as much as the transducer family. The low-mass diaphragm often allows strong transient detail and useful high-frequency extension. Higher sensitivity can also produce more output from quiet sources. It does not prove that a microphone is more accurate or better: [Shure’s sensitivity guide](https://service.shure.com/articles/en%5FUS/Knowledge/how-do-i-compare-the-sensitivity-of-two-microphones) explicitly separates output level from microphone quality. A sensitive microphone used farther from the source can make room reflections, computer fans and street noise more obvious. That is a placement and signal-to-noise problem, not a rule that a condenser “hears everything.” [RØDE’s practical guide](https://rode.com/en-us/about/news-info/what-is-a-condenser-microphone-and-when-to-use-one) notes the tendency to capture unwanted background sound in reflective rooms. In a difficult space, move the microphone closer, aim its rejection toward the noise, reduce reflective surfaces where possible, and solve the cause before reaching for [audio noise reduction software](https://soundforgepro.com/audio-noise-reduction-software/). ## Four specifications that matter 01 ### Polar pattern [Cardioid, omnidirectional and figure-eight](https://soundforgepro.com/microphone-polar-patterns/) describe directionality, not sound quality. Read the pattern chart and place unwanted noise toward an area of stronger rejection. 02 ### Sensitivity This tells you how much electrical output the microphone produces for a stated sound pressure. Higher sensitivity can reduce the gain required from the preamp, but it is not a quality score. 03 ### Self-noise The active electronics add their own noise. A lower A-weighted self-noise figure matters most for quiet sources, distant recording and passages with wide dynamics. 04 ### Maximum SPL This is the loudest specified sound pressure the microphone can handle within a stated distortion limit. A pad may raise the usable ceiling on models that include one. Self-noise and maximum SPL describe opposite ends of the usable range. A microphone for quiet acoustic detail benefits from low self-noise; one placed close to a snare, brass bell or loud cabinet needs enough SPL headroom. The [Shure recording guide](https://www.shure.com/damfiles/default/global/documents/publications/en/performance-production/microphone%5Ftechniques%5Ffor%5Frecording%5Fenglish.pdf-bb0469316afdb6118691d2f3f5e3ff01.pdf) explains both figures and why electronic overload can happen before the capsule itself reaches a mechanical limit. ## When should you use a condenser microphone? | Recording task | Condenser fit | Decision point | | ---------------------------------------------------- | -------------------- | --------------------------------------------------------------------------------------------------- | | Lead vocals in a treated or quiet room | Often a strong fit | Choose the polar pattern and distance for the voice; manage plosives with position and a pop filter | | Acoustic guitar, piano, strings or percussion detail | Often a strong fit | Check transient response, self-noise and the room contribution | | Podcasting or streaming at a desk | Depends on the room | Close placement and cardioid rejection matter more than the word “condenser” | | Untreated bedroom with fans or traffic | Use with care | Improve distance and noise control; a dynamic may be easier to manage | | Close loud drums, brass or guitar cabinet | Model-dependent | Verify maximum SPL and engage the microphone pad if its manual calls for it | | Live stage with high monitor level | Application-specific | Feedback margin, handling noise, durability and pattern consistency can outweigh extra sensitivity | | Field recording | Application-specific | Wind protection, weather tolerance, battery life and connector power are decisive | For spoken-word work, microphone choice is only the first step. After the recording chain is clean, use a consistent [podcast loudness target](https://soundforgepro.com/podcast-loudness-standard/) or the appropriate [streaming loudness standard](https://soundforgepro.com/streaming-loudness-standards/) for delivery. ## Condenser or dynamic: the practical distinction A dynamic moving-coil microphone generates its signal through a diaphragm, coil and magnet and normally needs no power at the capsule. It is often chosen for durability, loud sources and stage work. A condenser uses a capacitive capsule plus active electronics and is often chosen when sensitivity, transient detail or a small diaphragm is useful. That is an orientation, not a winner. A close dynamic in a noisy room can produce a cleaner voice recording than a distant condenser. A condenser rated for high SPL can work perfectly well on loud instruments. Compare the exact models, distance, polar pattern and room instead of choosing from category stereotypes. ## “Condenser” and “large-diaphragm condenser” are not synonyms Large-diaphragm condensers are one part of the category. Small-diaphragm “pencil” microphones, miniature electret lavaliers, shotgun microphones and measurement microphones can also use condenser principles. Diaphragm size affects engineering tradeoffs, but it does not let you predict “more bass” or “better vocals” without the response, polar behavior and placement of the specific microphone. ## How to connect an XLR condenser safely 1. **Check the manual.**Confirm the connector, required phantom voltage and any dedicated supply or adapter. 2. **Turn the gain and monitor level down.**Switch phantom power off before making the connection. 3. **Connect a balanced XLR cable.**Seat both ends fully and avoid loose adapters or damaged cables. 4. **Enable phantom power only if required.**Allow the circuit a few seconds to settle, then raise gain while watching the input meter. 5. **Set position before chasing gain.**Move the microphone closer or adjust its angle if the voice is quiet or the room is too prominent. 6. **Power down before disconnecting.**Lower gain, switch phantom power off, wait briefly, then unplug. Once connected, you can [test the microphone in your browser](https://soundforgepro.com/microphone-test/) to confirm that the operating system and browser receive a signal. That check does not replace setting gain in the recording application or listening for clipping, hum and room noise. ## Quick choice checklist - **Choose the source and distance first.** Quiet sources and detailed acoustic recording may favor a condenser; close loud work may favor either type depending on the model. - **Listen to the room.** If the recording position captures fans, traffic or hard reflections, fix distance and environment before buying for “detail.” - **Match the polar pattern to the placement.** Directionality is useful only when the microphone is aimed with both its pickup and rejection areas in mind. - **Check power and connector compatibility.** Never assume that an XLR plug, USB cable or 3.5 mm adapter supplies the right power. - **Read self-noise and maximum SPL in context.** The best figure depends on whether the source is very quiet, very loud or somewhere between. A condenser microphone is a strong choice when its sensitivity, pattern, noise floor and SPL capacity match the job. Start with the source and room, then choose the power system and specifications that support that setup. The label on the box should confirm the decision, not make it for you. ### Speaker Placement Calculator: Stereo Starting Positions URL: https://soundforgepro.com/speaker-placement-calculator/ Last updated: 2026-10-02T07:13:39.000Z **Start with symmetry, not a magic distance.** Enter the room size, choose a placement method, and the calculator will return speaker spacing, wall clearance, listening distance, and coordinates for a two-speaker stereo setup. Every result is a starting position: room boundaries, furniture, speaker design, and low-frequency behavior still decide where the final setup belongs. ## Speaker placement calculator STEREO TOOL · FEET OR METERS ### Find a practical starting position Reset Measurements start at the wall behind the speakers. The diagram is a top view. Units Feet Meters Room width **ft** Side wall to side wall. Room length **ft** Speaker wall to rear wall. Placement method **38% + 60° triangle**Choose the speaker wall distance; the tool places the listener at 38% of room length. **Cardas box speakers**Uses room width to calculate side and front-wall clearance for box speakers. Speaker fronts from the wall **ft** Measure to the front face of the speaker. Check the maker’s minimum clearance. STARTING POSITION ### 38% + 60° triangle Side-wall clearance**—**each speaker Front-wall distance**—**speaker face Speaker spacing**—**center to center Listening position**—**from speaker wall Speaker to listener**—**each side Top-view speaker placement diagram Two speakers form a symmetrical triangle with the listening position. WALL BEHIND SPEAKERS L R LISTENER Top view. Keep the left and right distances equal. Show exact coordinates Origin: front-left corner when facing the wall behind the speakers. | Point | X from left wall | Y from speaker wall | | ------------- | ---------------- | ------------------- | | Left speaker | — | — | | Right speaker | — | — | | Listener | — | — | Keep left/right movement symmetrical, aim both speakers at the listening position, and verify center image and [bass balance](https://soundforgepro.com/bass-vs-treble/). ## How to use the calculator Measure the clear inside width and length of the room. The “speaker wall” is the wall behind the speakers, and the calculator measures forward from that surface. Speaker coordinates refer to the center of each front face; the listener coordinate refers to the center of the head. 1. Choose feet or meters. Switching units converts the values already entered. 2. Enter room width and length. 3. Choose the 38% + 60° method for a flexible stereo triangle, or Cardas for box speakers in a symmetrical rectangular room. 4. For the 38% method, enter the distance from the wall to the speaker fronts. 5. Mark the calculated points with removable tape, keep left and right movements equal, and refine from there. If you are unsure whether the channels are routed correctly after moving the monitors, run the [left and right speaker test](https://soundforgepro.com/left-right-speaker-test/) before judging the stereo image. ## Which placement method should you choose? ### 38% listening point and 60° stereo triangle This mode starts the listener at 38% of the room length from the wall behind the speakers. The 38% guideline is commonly used to avoid beginning at the exact center of a rectangular room, where strong axial-mode problems can coincide. [RealTraps describes it as a theoretical starting location](https://realtraps.com/art%5Froom-setup.htm), not a final measurement. You supply the speaker distance from the wall because monitors differ. A rear-ported speaker, a sealed cabinet, and a model designed for wall mounting may need different boundary clearance. From that line, the calculator forms a symmetrical 60° included angle at the listener. That follows [Genelec’s stereo placement guidance](https://www.genelec.com/monitor-placement): the angle between left and right monitors starts at 60°, with both monitors aimed toward the listening position. Choose this method when you already know how far the speakers can sit from the front wall and want the spacing that completes the stereo triangle. ### Cardas box-speaker method The [Cardas formula for conventional box speakers](https://www.cardas.com/system-setup) calculates both wall distances from room width: the front-face center starts at 0.276 times the room width from each side wall and 0.447 times the room width from the wall behind the speakers. The listener then completes an equilateral triangle. Use this mode only for conventional box speakers. Cardas Audio publishes a [separate method for panel and dipole speakers](https://www.cardas.com/system-setup); mixing its coefficients with the box-speaker formula would create a layout that belongs to neither method. Cardas can also fail cleanly in a short, wide room. If the equilateral listening point lands at or beyond the rear wall, the calculator will say so instead of squeezing the geometry into the room. ## What the results mean **Side-wall clearance** is the horizontal distance from the center of each speaker’s front face to its nearest side wall. Both values must match if the room allows it. **Front-wall distance** is measured from the wall behind the speakers to the center of the speaker fronts. It is not the clearance from the cabinet’s rear panel. **Speaker spacing** is center to center, not cabinet edge to cabinet edge. Measure from the same reference point on both speakers. **Listening position** is the distance from the speaker wall to the center of your head. The coordinate table removes ambiguity when you are laying out tape marks on the floor. ## Verify the starting position in five steps 1. **Preserve symmetry.** Match the left and right wall distances as closely as the room permits. Unequal early-reflection paths can pull the image toward one side. 2. **Aim both speakers consistently.** Start with the tweeters directed at the listening position unless the manufacturer recommends another toe-in angle. 3. **Check the phantom center.** Play a centered mono voice or vocal. It should sit between the speakers rather than inside one cabinet. 4. **Move in small equal increments.** If the center is stable but bass is strongly uneven, move both speakers or the listener by the same small amount and listen again. 5. **Measure when accuracy matters.** Geometry cannot predict every boundary, furnishing, crossover, or room-mode interaction. A calibrated microphone and room-response measurement can show problems that listening alone may not isolate. ## Common speaker placement mistakes - **Measuring from different points.** Switching between cabinet backs, baffles, tweeters, and stands makes a symmetrical drawing asymmetrical in the room. - **Putting the listening position at the exact room center.** The calculator warns when a result approaches the 50% length line, but nearby measurements still matter. - **Forcing a triangle that does not fit.** A narrow room may not support a 60° triangle at the selected depth. Change the speaker-wall distance or use another defensible layout. - **Ignoring the speaker manual.** Manufacturer guidance for boundary compensation, ports, stand height, and orientation can override a convenient generic starting point. - **Changing only one speaker.** Unless you are correcting a known room asymmetry, move both sides together so you can hear what the distance change actually did. ## What this calculator cannot predict A room rectangle does not describe wall construction, large windows, doors, alcoves, furniture, treatment, subwoofers, speaker directivity, or crossover behavior. The calculator also does not estimate SPL, reverberation time, acoustic treatment, surround layouts, or ceiling coverage. Use the output to establish a clean, repeatable starting geometry. Then use listening and measurement to choose the final position. For other practical utilities, see the [SoundForgePro Audio Tools](https://soundforgepro.com/tag/audio-tools/) collection. ### WAV vs FLAC vs MP3 for Editing, Mastering and Archive URL: https://soundforgepro.com/wav-vs-flac-vs-mp3-editing-mastering-archive/ Last updated: 2026-10-09T20:08:40.000Z If the file will be edited, mastered or encoded again, keep a lossless source. WAV is the safest default for active work, FLAC is a strong choice for lossless storage and transfer, and MP3 belongs at the delivery end of the chain. **The practical rule:** edit and master from WAV or FLAC, keep one lossless master, and make an MP3 only when you actually need a smaller listening copy. Converting an MP3 to WAV changes the file format. It can't bring back audio the MP3 encoder threw away. ## The short answer by task | Task | Best starting choice | Reason | | -------------------------------- | ---------------------- | ------------------------------------------------------------------------------------------- | | Editing | WAV | Broad compatibility and a direct, uncompressed working file when the WAV contains PCM audio | | Mastering | WAV or lossless source | Preserves the available signal through processing and later exports | | Archive | FLAC or WAV | Both can preserve the audio losslessly; FLAC usually uses less storage | | Client handoff for more work | WAV, or FLAC if agreed | Keeps a lossless source for the next editor or engineer | | Review copy or general listening | MP3 | Small, widely playable file when further production is not expected | This is a workflow decision; no single format wins everywhere. The receiving software, the delivery specification, metadata requirements and your future editing plans all still matter. ## What WAV, FLAC and MP3 actually store A file extension tells you only part of the story. The underlying encoding and file parameters determine what the file can preserve and how software handles it. ### WAV is a container, usually carrying PCM Microsoft documents [WAVE as part of the RIFF family](https://learn.microsoft.com/en-us/windows/win32/xaudio2/resource-interchange-file-format--riff-): the file is built from chunks, including a format chunk that describes the audio and a data chunk that carries it. In everyday production a WAV usually holds uncompressed PCM, but the extension alone doesn't guarantee one codec, sample rate or bit depth. That distinction matters when someone asks for “a WAV.” A 16-bit, 44.1 kHz stereo file and a 24-bit, 96 kHz mono file can both be WAV files. Check the requested parameters instead of treating the extension as a complete delivery specification. ### FLAC compresses without discarding audio information [FLAC is lossless](https://www.xiph.org/flac/2024/12/19/rfc-9639-published.html). The decoder rebuilds the original audio the encoded stream represents, so moving between PCM and FLAC doesn't cause the kind of generational loss you get with MP3\. How much smaller the file gets depends on the material, and no honest fixed percentage covers every recording. FLAC also has defined metadata structures and stores [an MD5 signature of the decoded audio](https://www.rfc-editor.org/rfc/rfc9639.html#section-8.2) in its STREAMINFO metadata. That helps with integrity checks, but it's no substitute for backups, duplicate storage or a documented archive process. ### MP3 trades information for a smaller file MP3 uses [perceptual, lossy coding](https://www.loc.gov/preservation/digital/formats/fdd/fdd000012.shtml). It reduces or discards information according to the encoder, bitrate and characteristics of the audio. The result is useful when size and playback compatibility matter more than retaining a production master. Once [that information is gone](https://developer.mozilla.org/en-US/docs/Glossary/Lossy%5Fcompression), putting the decoded result in a WAV container can't bring it back. The WAV may be bigger, but its useful source quality is still capped by the MP3 it came from. ![WAV for editing, FLAC for lossless archives, and MP3 for delivery without converting MP3 back into a working master.](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/10/wav-flac-mp3-roles.webp) Keep the workflow moving from a lossless source toward the delivery copy. A larger container cannot reverse an earlier lossy encode. ## Use WAV for active editing when compatibility matters most WAV is the straightforward working format when the project will move between editors, restoration tools, video applications or mastering systems. An uncompressed PCM WAV avoids asking each application to decode a compressed source while you work, and it is easy to inspect for [sample rate, bit depth and channel layout](https://developer.mozilla.org/en-US/docs/Web/Media/Guides/Formats/Audio%5Fconcepts). None of that makes FLAC unsuitable audio. A correctly decoded FLAC gives you exactly the audio its lossless source held. The real issue is software support and workflow friction. If every application in the chain reads FLAC correctly, you can use it with no audio-quality penalty. If compatibility is in doubt, make a deliberate WAV working copy and keep the original FLAC. If MP3 is your only source, don't pretend a conversion improves it. Open the best original you have, make the edit you need, and save the working version losslessly so repeated saves don't add another MP3 encode. Make the new MP3 once, at the end, if the delivery still calls for it. ## Keep mastering lossless from input to approved master Mastering changes level, dynamics, frequency balance, fades and sequencing. Those decisions may be revised, and the approved master may later feed several delivery formats. A lossless source keeps the available signal intact through those stages. WAV is usually the simplest mastering deliverable because its PCM parameters are explicit and broadly accepted. FLAC can carry the same underlying audio losslessly, but the mastering engineer or distributor may specify WAV for compatibility. Follow the written delivery specification instead of converting sample rate or bit depth simply because a larger number looks safer. Keep the approved lossless master apart from listening copies. An MP3 is fine for approval, but it shouldn't become the file you use for a later revision, a vinyl pre-master, a broadcast version or a new streaming encode. ## Choose FLAC or WAV for an archive, then protect the archive itself For long-term storage, both FLAC and uncompressed PCM WAV can preserve the audio without lossy coding. FLAC is attractive when storage and transfer size matter. WAV is attractive when maximum compatibility with older or specialist production systems matters. The format choice is only one part of preservation. Keep more than one copy, store copies in separate locations, retain the original filenames and project notes, and verify that archived files can still be read. If embedded metadata is important, check what survives the exact export and import path rather than assuming every field maps cleanly between formats. Large or unusual WAV projects need special attention. Sound Forge documentation includes [preferences for large Wave renders](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/general%5Fpreferences.htm) and support decisions around compressed formats. There is no useful universal size rule for every WAV workflow; the receiving application, filesystem and chosen WAV variant determine the real limit. ## Match the client handoff to what happens next Ask one question before exporting: will the recipient continue production, or only listen? - **More editing, mixing or mastering:** send WAV unless both sides have agreed on FLAC and confirmed support. - **Lossless archive or transfer:** send FLAC when smaller storage is useful and the recipient accepts it. - **Review, email or casual playback:** send MP3 at an appropriate bitrate and keep the lossless master elsewhere. - **Formal delivery:** follow the written sample rate, bit depth, channel, naming and metadata specification. Boris FX warns that [audio peaking near 0 dB can clip after MP3 conversion](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/proonly/normalizing%5Faudio.htm). Leave sensible headroom before encoding and inspect the encoded file rather than assuming the lossless master and MP3 will peak identically. ## Why repeated MP3 conversion is a bad source workflow Every fresh MP3 encode asks a lossy encoder to make another round of decisions. Decoding an MP3 to WAV stops further loss while you edit that WAV, but the first encode stays baked in. Encoding the result back to MP3 can add another generation of loss. Avoid chains such as MP3 → WAV → MP3 → WAV → MP3\. Keep the earliest lossless source you can obtain. If no lossless source exists, preserve the original MP3 unchanged, create a lossless working file for edits, and limit the workflow to one final lossy export. Bitrate labels don't change that history. A high-bitrate MP3 made from a low-bitrate MP3 can't restore the discarded signal. All it does is re-encode an already limited source into a new, often larger, lossy file. ## A practical Sound Forge format workflow 1. Identify the best available source and keep an untouched copy. 2. Confirm its sample rate, bit depth, channels and encoding before editing. 3. Use WAV as the working file when broad compatibility is the priority. Keep FLAC lossless if the complete toolchain supports it. 4. Edit and process without creating intermediate MP3 files. 5. Save an approved lossless master before making delivery copies. 6. Use [Save As or Render As in Sound Forge](https://soundforgepro.com/how-to-convert-audio-files-sound-forge-pro/) to create the requested output format. 7. Check whether required markers, regions and other metadata are supported by the target format. [Sound Forge documentation](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/saving%5Fa%5Ffile%5Fas%5Fa%5Fdifferent%5Fname%5For%5Ftype.htm) notes that unsupported metadata may be stored in an associated `.sfl` file. 8. Open the exported file and complete the [audio export QA checks](https://soundforgepro.com/audio-export-qa-checklist/) for duration, channels, boundaries, metadata and playback. Keep format conversion at a clear handoff point. It is easier to trace a problem when the archive master, working file and delivery copy each have one defined role. ## Decision checklist - Will anyone edit, master or encode the file again? Keep it lossless. - Does the next application accept FLAC reliably? If not, use PCM WAV. - Is storage the main concern for a lossless archive? FLAC is usually the practical choice. - Is the file only for listening or approval? MP3 may be enough. - Did the client specify sample rate, bit depth, channels or metadata? Follow those values exactly. - Are you converting from MP3? Label the result honestly and keep the original MP3. - Did you verify the exported file rather than only the Sound Forge project? ### Room Tone: Record, Edit and Use It in Sound Forge URL: https://soundforgepro.com/room-tone-sound-forge/ Last updated: 2026-10-04T20:02:48.000Z Room tone is the quiet background texture captured by the microphone when nobody is speaking. Use it to fill dialogue edits where a cut would otherwise fall into digital silence or change the noise floor abruptly. The cleanest result comes from tone recorded with the same microphone, position, gain and room state as the dialogue. **The practical rule:** choose a clean room-tone passage longer than the gap, place it without changing the intended timing, then soften both boundaries with short crossfades. If the join still calls attention to itself, fix the match before making the fades longer. ## What room tone is — and what it is not [A quiet room is never completely silent](https://www.izotope.com/community/blog/basics-of-room-tone-audio-editing). The recording can contain ventilation, distant traffic, computer fans, electrical noise, microphone self-noise and the way the room reflects those sounds. Together they form a low-level texture that the listener may ignore [until it suddenly disappears](https://www.izotope.com/community/blog/how-to-clean-up-audio-and-remove-background-noise). Room tone doesn't give you permission to keep a bad background. A strong hum, a clipped word, [clothing rustle](https://soundforgepro.com/reduce-lavalier-clothing-rustle-sound-forge/), chair movement or a handling thump is still a defect, and it needs its own repair or replacement. If the whole recording needs cleanup, start with the [Sound Forge background-noise workflow](https://soundforgepro.com/how-to-remove-background-noise-in-sound-forge-pro/), then build the fill from material that matches the cleaned dialogue. | Material | Purpose | What can go wrong | | --------------- | ------------------------------------------------------------------- | --------------------------------------------------------------- | | Room tone | Preserves the local noise floor and acoustic texture across an edit | A mismatched microphone or room state makes the patch obvious | | Digital silence | Contains no recorded room texture | The sudden drop can sound like a gate or missing section | | Ambience | Builds a broader sense of place: street, café, office, forest | It may add events that do not belong in a close dialogue repair | | Noise reduction | Reduces unwanted steady or intermittent noise | It can change the texture that the fill needs to match | ## Why digital silence exposes a dialogue edit A dialogue recording has a continuous floor underneath the words. Remove a breath, click or sentence and replace it with absolute silence, and that floor stops for the duration of the cut. The listener may not identify the cause, but the change can feel like a mute switch, a noise gate or a broken recording. The problem is contrast. A quiet patch of matching room tone can be less noticeable than a perfectly silent patch surrounded by audible room noise. This is especially clear on headphones, in sparse voice-over, and after compression or limiting raises the background between phrases. The same goes for two takes with different backgrounds. Room tone can hide a short boundary, but it can't make a noisy room sound like a quiet one. A large mismatch calls for a broader dialogue-editing decision; a longer patch won't solve it. ## Record tone before the setup changes Capture room tone while the dialogue setup is still in place. Keep the same microphone, polar pattern, distance, angle, preamp or interface input, gain, sample rate and room state. Don't move the microphone closer to the wall, switch off a fan that ran during the take, or ask everyone to stand somewhere else. Each of those changes gives you a different recording, even if the room looks the same. In Sound Forge, use the same input path as the dialogue session. The [current recording workflow](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/record%5Fnew.htm) provides input selection, arming and [manual recording controls](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/recording%5Foptions.htm). Our full [Sound Forge recording guide](https://soundforgepro.com/how-to-record-audio-in-sound-forge-pro/) covers the setup; for room tone, the important part is preserving the existing chain rather than inventing a new one. 1. Finish the take and leave the microphone where it is. 2. Ask people to remain in position and stop speaking or moving. 3. Keep doors, ventilation, computers and other steady sources in the same state. 4. Record one uninterrupted stretch, then capture another if the room contains occasional traffic or mechanical cycles. 5. Name the file after the room, microphone or scene so nobody mistakes it for generic silence. If you control the session, about a minute gives you far more choice than a token pause. There's no magic duration here. What you want is enough clean, uninterrupted material to cover the expected edits without repeating the same fingerprint. ## Select a clean passage that actually matches Don't pick a region just because the waveform looks small. Listen for chair creaks, breaths, lip noise, distant voices, footsteps, traffic changes and the tail of the previous word. A clean selection keeps a stable texture from start to finish. Match the moment as well as the room. Tone recorded beside a loud computer fan may not fit a later take made after the fan slowed down. A microphone aimed toward a reflective wall may sound brighter than one turned toward curtains. When several usable passages exist, label or preserve them rather than forcing one sample across the whole program. Use a longer source than the repair whenever possible. That gives you room to move the edit points away from small noises and reduces the chance of an audible loop. ## Fill an exact gap with Paste Paste is the straightforward choice when the room-tone selection can replace the target gap exactly. Sound Forge documentation states that [Paste inserts clipboard audio at the cursor](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/paste.htm). If a target selection exists, that selection is removed before the clipboard audio is inserted. 1. Save a new version before destructive editing. 2. Copy the clean room-tone section. 3. Select the complete gap that needs replacement. 4. Match the clipboard duration to the target selection before pasting. 5. Paste, then confirm that the following word, marker and total file timing remain where expected. The duration check matters. A longer or shorter clipboard selection can move everything after the edit. If the program must stay locked to picture or a fixed runtime, verify the file length immediately rather than discovering the shift at export. ![Dialogue, room-tone selection, gap replacement, short crossfades and a continuous noise floor.](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/09/room-tone-dialogue-edit-workflow-sunburst-v3-20260919.webp) The repair works in this order: match the tone, fill the exact gap, then soften both boundaries until the join disappears. ## Use Mix/Replace when the boundaries need control Mix/Replace is useful when the patch needs level balancing and fades rather than a hard substitution. Sound Forge provides [separate Source and Destination levels plus Fade In and Fade Out controls](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/mix.htm) with curve choices. That lets you bring the tone into the selection gradually while preserving or replacing the destination as the edit requires. Start with the room-tone level close to the background on both sides, then add a short fade at each boundary. There's no universal millisecond value: a tight speech edit may need only a small transition, while a slow mechanical cycle may need more room. Lengthen the fade only until the join disappears. No fade length can rescue tone that's brighter, louder or rhythmically different. Dragging a selection to mix can display an envelope, which helps show where the source enters and leaves. The dedicated [Sound Forge crossfade guide](https://soundforgepro.com/crossfade-audio-sound-forge/) explains fade curves and overlap decisions in more detail. ## Stop a short room-tone sample from turning into a loop A tiny clean fragment can sound harmless once and artificial after the fifth repeat. A soft fan wobble, electrical pulse, distant bird or traffic swell becomes a rhythm when the same sample returns at fixed intervals. - Use the longest clean source available. - Alternate between two or more matching passages. - Move the repeat boundary away from distinctive events. - Crossfade the joins so the waveform and texture don't jump. - Listen through the complete pause instead of auditioning only each boundary. If you need a very long fill, a dedicated ambience-matching or synthesis tool may suit the job better than hand-building dozens of repeats. Treat that as a separate production choice, and don't pass generated texture off as recorded room tone. ## Room tone belongs inside the wider voice edit Use room tone after deciding which speech, breaths and mouth sounds should remain. Removing every breath can make a performance feel assembled, while leaving a loud click untouched gives the fill the wrong job. The [mouth-click repair guide](https://soundforgepro.com/remove-mouth-clicks-from-audio/) covers short defects, and the [voice-over workflow](https://soundforgepro.com/sound-forge-pro-for-voice-over-recording/) shows where editing, cleanup and final processing fit. Check the edit again after compression, limiting and loudness changes. Those stages can lift a quiet background and expose a loop or mismatch that seemed harmless before. The repair is done when the pause sounds like the same recording carrying on. A waveform that merely looks full doesn't count. ## Practical room-tone checklist - The microphone, placement, gain and room state match the dialogue. - The source contains no speech tail, breath, movement or isolated noise. - The replacement covers the exact intended duration. - The noise floor matches before fade length is adjusted. - Both boundaries disappear at normal listening level. - No short pattern repeats often enough to become recognizable. - The edit still works after the final processing chain. - Markers, following words and total runtime remain in place. Before delivery, reopen the exported file and check the repaired pause in context. Our [audio export QA checklist](https://soundforgepro.com/audio-export-qa-checklist/) covers duration, channels, metadata and boundary checks. ### Ocenaudio vs Sound Forge: Free Simplicity or Pro Workflow? URL: https://soundforgepro.com/ocenaudio-vs-sound-forge/ Last updated: 2026-09-30T20:26:55.000Z Ocenaudio is the better choice when you want a free editor for fast cuts, level changes, spectral inspection and occasional VST effects on Windows, macOS or Linux. Sound Forge Pro makes more sense when audio editing is part of a repeatable Windows workflow built around batch processing, restoration, mastering and a larger plug-in collection. **My short answer:** start with Ocenaudio if most of your work is one file at a time. Pay for Sound Forge when the workflow around the edit is what's pushing you toward a stronger editor; a basic cut or fade won't justify it. ## Ocenaudio vs Sound Forge at a glance | Decision | Ocenaudio | Sound Forge Pro | | -------------------- | ------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------ | | Best fit | Quick editing, speech cleanup, spectral inspection and occasional effects | Detailed restoration, mastering, batch jobs and repeatable production work | | Platforms | Windows, macOS and Linux | Windows; check the current [system requirements](https://soundforgepro.com/sound-forge-pro-system-requirements/) before buying | | Price position | Free download | Commercial product; editions and offers change | | Effects | Native effects, VST support and real-time preview | VST workflow with a dedicated Plug-In Manager and room for larger chains | | Spectral work | Real-time configurable spectrogram for inspection | Better fit when spectral work belongs to a wider restoration process | | Batch and automation | Choose it for direct single-file work; verify any repeatable bulk task you depend on | Documented batch and scripting path for repeated processing | | Learning curve | Usually easier to approach for occasional editing | More workspace, routing and plug-in organization to learn | ## Choose Ocenaudio when the edit should stay simple Ocenaudio's best argument goes beyond being free: the editor keeps the path from opening a file to finishing a correction short. The official [feature page](https://www.ocenaudio.com/en/features) documents VST support, real-time effect preview, multi-selection, long-file editing and a configurable spectrogram. That's a useful toolset, and hardly a stripped-down toy. Multi-selection is especially practical for speech. You can mark several non-adjacent regions and apply the same change without rebuilding the selection each time. Real-time preview also helps with EQ, gain and filtering because you hear the result while adjusting the control instead of processing, undoing and trying again. The spectrogram gives Ocenaudio a clear role in cleanup work. It helps you spot a whistle, a hum band, a click cluster or some other visible anomaly before you decide what to change. It won't make every repair automatic, but it gets you to the part of the file that needs attention faster. If your normal job is trimming an interview, cleaning a voice note, checking a suspicious frequency or converting a finished edit, Ocenaudio may already be enough. It also belongs on the shortlist in our broader guide to the [best Sound Forge alternatives](https://soundforgepro.com/best-sound-forge-alternatives/). ## Choose Sound Forge when the workflow repeats Sound Forge earns its place when the same kinds of files arrive every week and the processing chain has to remain organized. The distinction appears in three areas: [batch work](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/proonly/scripting%5F-%5Foverview.htm), specialist restoration and plug-in management. A folder of files is a different problem from one waveform. If you need to apply a known chain, keep naming rules and deliver consistent formats, use the [Sound Forge batch-processing workflow](https://soundforgepro.com/how-to-batch-process-files-sound-forge-pro/) as the deciding reference. Saving clicks is only part of it. The bigger win is lowering the chance that file seven gets a different setting from file one. Restoration and mastering also benefit from a workspace that can hold a deeper chain. Our [audio restoration guide](https://soundforgepro.com/audio-restoration/) covers the order of diagnosis and repair, while the [mastering workflow](https://soundforgepro.com/sound-forge-pro-for-mastering/) explains where metering, processing and export checks fit. Ocenaudio can make individual edits inside those jobs; Sound Forge is the stronger center for the complete process. The official Sound Forge [Plug-In Manager documentation](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/proonly/plug-in%5Fmanager.htm) describes a dockable tree view, favorites and categories by VST version and 32/64-bit type. That organization matters after your plug-in list stops fitting comfortably in one menu. It also gives you a clearer route when a plug-in is missing, alongside our [VST troubleshooting guide](https://soundforgepro.com/sound-forge-pro-vst-plugins-not-showing/). ![Decision diagram comparing Ocenaudio quick editing with Sound Forge batch restoration and mastering workflows](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/09/ocenaudio-sound-forge-workflow-map.webp) Ocenaudio covers the short path from file to finished edit. Sound Forge becomes useful when the processing chain has to be repeated, organized and extended. ## Where the two editors genuinely overlap Both products can sit in front of a waveform and handle the work most people picture when they hear “audio editor”: selecting a region, cutting, fading, changing gain and applying an effect. Both can also take VST effects, although exact plug-in compatibility still depends on the plug-in format, architecture, operating system and current application build. This overlap is why a raw feature checklist produces the wrong purchase. If all you need is an EQ adjustment and a clean export, Sound Forge's larger environment may not improve the result. If every edit must feed a named chain, several output formats and an archive routine, Ocenaudio's direct interface may leave you rebuilding process decisions outside the editor. The price tag doesn't settle audio quality. A careful gain change or fade won't turn “better” just because it came from a more expensive application. Choose the environment that helps you make the right edit, repeat it when you need to and check the export. ## Platform and cost may settle the choice first Ocenaudio currently offers builds for Windows 10+ 64-bit, current and legacy macOS, and several 64-bit Linux package formats. The [download page](https://www.ocenaudio.com/en/download) listed version 3.21.3 when this comparison was checked on September 19, 2026\. Treat that number as a point-in-time check; use the download page for the latest build and platform details. If you edit on macOS or Linux, Ocenaudio wins this comparison before the deeper workflow questions begin. Sound Forge is a Windows choice. A Mac user who needs something closer to a full production environment should compare several alternatives rather than trying to make a Windows-only purchase fit the machine. For Windows users, cost should follow the bottleneck. A free editor is the sensible choice when it completes the job. Sound Forge becomes easier to justify when batch processing, restoration chains, mastering tools or plug-in organization save real production time. Check the maintained [Sound Forge pricing guide](https://soundforgepro.com/sound-forge-pro-pricing/) because editions and offers can change. ## Which editor fits your work? | Your regular job | Better starting point | Reason | | ---------------------------------------------------------- | --------------------- | ------------------------------------------------------------------------------------------------- | | Trim interviews, remove pauses and adjust speech levels | Ocenaudio | Fast selection, multi-selection and effect preview cover the core task without a larger workspace | | Edit on macOS or Linux | Ocenaudio | It has current cross-platform builds; Sound Forge is Windows software | | Inspect a problem frequency in a long recording | Ocenaudio | The real-time spectrogram and long-file focus suit diagnosis and local repair | | Process a recurring folder of files with the same chain | Sound Forge Pro | Batch and scripting workflows are closer to the actual requirement | | Restore vinyl, tape or damaged archival recordings | Sound Forge Pro | A larger restoration chain and plug-in workspace are more useful as the job grows | | Prepare masters with repeatable metering and export checks | Sound Forge Pro | The editor is better positioned as the center of a broader mastering process | | Occasionally repair one file | Ocenaudio | Buying a larger environment does not solve a problem you do not have | ## Run this trial before you commit 1. Open one easy file and one awkward file from your real workload. 2. Check whether the editor reads the format, channel layout and metadata you need. 3. Apply the effect chain you use most often and confirm every essential plug-in appears. 4. Make three separate corrections in the same long recording. 5. Repeat the job on five files without relying on memory for each setting. 6. Export the required formats and reopen them to verify duration, channels, metadata and audible boundaries. 7. Count the steps you only take because the editor can't keep your process. The fifth step is the dividing line. If the work remains quick and obvious, Ocenaudio is doing its job. If repetition turns into manual housekeeping, Sound Forge's batch and organizational tools have a concrete purpose. ### Mono Compatibility and Phase Correlation in Sound Forge URL: https://soundforgepro.com/mono-compatibility-phase-correlation/ Last updated: 2026-10-09T21:08:03.000Z Mono compatibility is the ability of a stereo file to keep its important content when the left and right channels are combined. If a mix loses its vocal, bass weight, center image or attack in mono, the problem is usually not “mono sounding bad.” It is two channel signals partially canceling each other. Sound Forge gives you two useful warnings: the Mono-Compatibility Meter shows whether the channels are moving toward a risky relationship, and the Phase Scope shows the shape of that relationship. Neither meter replaces the final check. The reliable decision comes from folding the file to mono and listening to what survives. ## What the correlation reading actually tells you [Phase correlation](https://soundforgepro.com/phase-correlation-meter/) describes how similarly the two channels move over time. Treat it as a range of clues rather than a score you must maximize. | General reading | What it suggests | What to check in mono | | ------------------- | ------------------------------------------------------ | ------------------------------------------------------------------------------------------ | | Positive, toward +1 | The channels share a lot of similar information | Usually stable, but confirm that the mix has not become unnecessarily narrow | | Near zero | The channels are less related or strongly decorrelated | Often normal for ambience and wide effects; check important center elements | | Negative | Some energy in one channel opposes the other | Listen for missing bass, a hollow vocal, softened transients or a collapsing stereo effect | A reading near +1 isn't a universal target. A mono voice, a centered kick or an identical left/right signal naturally sits high. Wide ambience, modulation and reverb may hover closer to zero and still fold down fine. The warning starts to matter when an important sound changes or disappears. ![Diagram comparing positive, near-zero and negative phase correlation with stereo channels folded to mono](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/09/phase-correlation-fold-down-guide.webp) Correlation predicts risk. The mono result tells you whether the relationship is actually damaging the mix. ## Turn on the Sound Forge phase tools Current Sound Forge Pro 2026 documentation places the Mono-Compatibility Meter and Phase Scope in the Channel Meters window, Hardware Meters window and Record dialog. Right-click the meters and enable **Show Mono-Compatibility Meter**, then enable **Show Phase Scope**. The [documented compatibility meter](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/proonly/mono%5Fcompatibility%5Fmeter.htm) lights its right or top half when the channels are similar. Movement into the left or bottom half warns that channel differences can cancel during a mono downmix. Watch it through the actual problem section; a loud chorus or a convenient ten-second loop won't show you everything. ## Read the Phase Scope without chasing a perfect shape The [Phase Scope documentation](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/proonly/phase%5Fscope.htm) lists four views: Lissajous – XY Plot, Lissajous – Rotated, Polar – Linear Plot and Polar – Circular Plot. Real music and dialogue produce diffuse traces, so look for direction and change rather than a clean textbook line. - **Lissajous – XY:** a forward-slash tendency is the safer orientation in the documented examples; a backslash tendency points toward cancellation. - **Lissajous – Rotated:** a mainly vertical trace is safer; a strong horizontal trace warns of opposing channel movement. - **Polar views:** a centered trace is generally safer than left/right traces pulling apart. The scope is most useful when you compare moments. If the vocal sounds solid until a widening effect enters and the trace immediately spreads or rotates, you have a much better repair lead than a single average correlation number. ## Make a real mono fold-down Use a copy of the file for diagnosis. In Sound Forge, open **Process > Channel Converter**, choose one output channel, and mix the left and right sources into that mono output. The official [Channel Converter guide](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/proonly/channel%5Fconverter.htm) documents independent contribution controls for both source channels. The separate [Sound Forge Channel Converter walkthrough](https://soundforgepro.com/sound-forge-channel-converter/) explains the broader conversion workflow. Don't judge only by whether mono comes out quieter. Summing conventions and channel content can both change level. Listen for a change in balance or tone instead: - Does the vocal move backward or become hollow? - Does the kick or bass lose its center weight? - Do snare hits, picked notes or consonants lose their leading edge? - Does a wide pad become thin, swirly or nearly disappear? - Does one side sound healthy alone while the combined version fails? Use the [loudness meter guide](https://soundforgepro.com/sound-forge-loudness-meters/) if level changes are pulling your attention away from the tonal comparison. Match playback sensibly, and don't mistake “louder” for “better correlated.” ## Trace the cause before changing the file Phase trouble usually comes from one source or process. Isolate the left and right channels, then bypass or inspect likely contributors one at a time. | Likely cause | Typical clue | First repair to try | | ------------------------------------------ | ---------------------------------------------------------------- | ---------------------------------------------------------------------------- | | Polarity inversion | Strong cancellation across much of a duplicated signal | Correct the polarity on the affected channel or source | | Haas delay or micro-delay widening | A sound is wide in stereo but hollow or comb-filtered in mono | Shorten the delay, lower the delayed side or use a mono-safe widening method | | Duplicated tracks | Two near-identical layers fight after a small timing shift | Align the layers or keep one centered and make the other genuinely different | | Multimic timing | Low end or attack changes when microphone channels combine | Adjust timing or polarity at the source-track level | | Chorus, modulation or reverb | The effect return is unstable while the dry source remains solid | Narrow, filter or reduce the return rather than flattening the dry sound | | Different low-frequency content in L and R | Bass loses focus even though upper frequencies remain wide | Keep critical low frequencies more centered and check the crossover region | The [left/right speaker test](https://soundforgepro.com/left-right-speaker-test/) helps confirm channel routing before you blame the file. A swapped or missing channel in the monitor path can imitate an editing problem. ## Fix the source, not the whole stereo image Start with the smallest change that restores the missing information. Correct an inverted channel. Realign one duplicate. Reduce a short side delay. Narrow only the effect return. Keep the bass component centered while leaving higher ambience wide. Converting the complete mix to mono can hide the symptom, but it also removes the stereo design. Pushing every correlation reading toward +1 has a similar cost. The goal is stable priorities: the center, low end, vocal and defining transients should survive, while decorative width can remain wide. When the problem exists only for a few moments, repair those moments. A single automated width reduction or local effect change is usually less audible than narrowing the entire file. ## Use this repeatable check 1. Select the section where the mix changes most noticeably. 2. Enable the Mono-Compatibility Meter and Phase Scope. 3. Note what happens when the suspect element enters. 4. Create or monitor a true mono fold-down. 5. Check the center, low end, vocal and transients. 6. Listen to the left and right channels separately. 7. Repair the source of the disagreement. 8. Repeat the mono check at a modest playback level. Then switch back to stereo and make sure the repair didn't strip out useful width. A good fix makes mono more dependable without shrinking the stereo image more than it has to. ## Run the final export check Check the beginning, loudest section, widest section and ending in both stereo and mono. Use the [headphone test](https://soundforgepro.com/headphone-test/) to catch routing and balance problems, then follow the [audio export QA checklist](https://soundforgepro.com/audio-export-qa-checklist/) before delivery. Mono compatibility matters because real playback is unpredictable: small speakers, grouped devices, club systems, accessibility feeds and social platforms can all narrow or sum a signal. You don't need to make every mix mono. You do need to know its important information stays intelligible when stereo separation shrinks. ### How to Reduce Sibilance in Sound Forge Without Dulling the Voice URL: https://soundforgepro.com/reduce-sibilance-sound-forge/ Last updated: 2026-10-06T07:10:18.000Z Sibilance is the sharp, sustained energy that makes S, SH and Z sounds jump out of an otherwise balanced voice. The wrong repair is easy to hear: the consonants collapse, the speaker starts to sound as if they have a lisp, and the whole recording loses its air. The safer route is to work out the shape of the problem first, then use the narrowest treatment that fixes it. ## Confirm that the problem is actually sibilance A bright consonant doesn't automatically call for de-essing. Listen to how long it lasts and where the energy sits before you pick a tool. | What you hear | What it usually is | Better first move | | ------------------------------------------ | -------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------- | | A long, bright hiss on S, SH or Z | Sibilance | Manual level repair, dynamic EQ or a de-esser | | A low thump on P or B | Plosive | Local level and low-frequency repair; see the [plosive removal workflow](https://soundforgepro.com/remove-plosives-from-audio/) | | A tiny isolated tick | Mouth click or edit click | Short event repair; compare with the [mouth-click guide](https://soundforgepro.com/remove-mouth-clicks-from-audio/) | | Every word feels edgy, not just consonants | Broad tonal imbalance, clipping or microphone coloration | Check the recording, then consider broader EQ or restoration | ![Visual guide comparing sibilance, a plosive, a mouth click and an overly bright recording](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/09/sibilance-diagnostic-guide-q92.webp) Duration and frequency shape help separate sibilance from plosives, clicks and broad brightness. ## Find the harsh band by ear first Start with the most obvious S sound in the file. Loop a short phrase, but keep enough of the vowel before and after it to hear whether the voice stays natural. [A spectrum graph](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/proonly/viewing%5Fa%5Fspectrum%5Fgraph.htm) can show a concentrated rise in the upper mids or treble, but let it confirm what you hear. It shouldn't pick the band for you. A useful search area often sits somewhere around 4–10 kHz, and that's only a starting region. The speaker, microphone angle, room, codec and earlier processing can all move the painful band. Sweep a narrow monitoring band until the hiss is unmistakable, then widen it just enough to catch the full consonant. If the vowels start to sound papery, the band is too wide or too low. ## Repair isolated syllables before reaching for a processor When only a handful of consonants are distracting, manual repair usually sounds cleaner than running a de-esser across the whole file. 1. **Preserve the source.** Save a new version before destructive edits. 2. **Select the sibilant portion.** Include the sustained hiss and leave the rest of the word alone. 3. **Reduce level gently.** Use gain reduction or a short envelope and listen to the transition into the following vowel. 4. **Shape only if level repair is not enough.** Apply a small local EQ cut to the selected event instead of pulling treble out of every sentence. 5. **Check the boundary.** Add a tiny fade if the edit creates a click, then replay the complete phrase. This method takes longer when a recording has dozens of similar events. What you get in return is control: a soft S can stay untouched while one aggressive consonant gets a precise edit. ## Use Dynamic EQ for repeated sibilance Sound Forge 2026 documentation [describes Dynamic EQ as a Suite feature](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/proonly/dynamic%20equalizer.htm). If it's in your installed edition, it suits repeated sibilance well, because the selected band only changes when its level triggers the processor. Confirm your license and available effects before you build the workflow around it. 1. Create a bell band around the harshest part of the S sound. 2. Set the band to reduce level when that region becomes dominant. 3. Lower the threshold until strong sibilants trigger reliably, while vowels and cymbals pass without obvious movement. 4. Use a quick attack to catch the front of the consonant. Set the release so the reduction recovers before the next vowel without fluttering. 5. Start with a small amount of reduction. Increase it only while the word keeps getting easier to hear, and back off as soon as the consonant loses definition. In the documented Dynamic EQ, that level-dependent behavior comes from Band Dynamics. Switch it on for the selected band, then set Threshold, Ratio, Attack and Release as you would on a compressor: a ratio above 1 pulls the band down once it crosses the threshold. It's still an EQ band, though, and the documentation lists no detector-listen control like the ones dedicated de-essers offer. ## Do not use static EQ as an automatic de-esser Static EQ applies the same cut whenever audio passes through. That's useful when the entire recording is too bright. When the problem only shows up on certain consonants, it's wasteful, because it also strips presence from vowels, breaths and room tone. If the voice is harsh throughout, use the [Sound Forge equalizer guide](https://soundforgepro.com/how-to-use-equalizer-sound-forge-pro/) to fix the broader balance first, then reassess the S sounds that are left. A smaller de-essing stage after tonal correction often sounds more natural than asking one processor to solve both problems. ## When a dedicated VST3 de-esser is the better choice Current Sound Forge documentation [covers VST3 plug-ins](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/proonly/plug-in%5Fmanager.htm). A dedicated de-esser earns its place when you need to audition the detector signal, [switch between wide-band and split-band processing](https://www.fabfilter.com/products/pro-ds-de-esser-plug-in), or set the detection range more precisely. Check the plug-in format, [scan path](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/vst%5Feffects%5Fpreferences.htm) and license on your own system before you commit a project to it. | Mode | What moves when sibilance is detected | Where it tends to help | Main risk | | ---------- | ------------------------------------------- | ------------------------------------------------------------ | ------------------------------------------------- | | Wide-band | The whole signal turns down briefly | Exposed speech and vocals where the level dip is unobtrusive | Pumping or a small audible volume hole | | Split-band | Mainly the high-frequency region turns down | Dense mixes or voices that must keep their body stable | A dull or phasey top end if the band is too broad | Use the [detector-listen function](https://www.waves.com/plugins/deesser) if the plug-in has one. You should hear mostly the offending hiss. If whole syllables, vowels or musical detail dominate the detector signal, narrow or move the range before you add more reduction. ## Prevent lisping, dullness and pumping - **Lisping:** reduce the range or depth until T, S and SH remain distinct. - **Dull vowels:** move the band higher, narrow it, or use split-band processing. - **Pumping:** reduce the wide-band amount or shorten the recovery without making it chatter. - **Missed consonants:** adjust the detector range before lowering the threshold further. - **Inconsistent results:** handle the few outliers with automation or manual edits instead of forcing one setting to catch every event. Don't judge a de-esser by soloing the S sounds. You aren't trying to erase them. You want them to sit inside the sentence. ## Run the final check in context Play the processed voice back at a normal listening level and compare it with the bypassed version at similar loudness, on headphones and on speakers. Then listen to a quiet S, a strong S, an SH sound and a phrase with no sibilance at all. If that last phrase changes noticeably, the processor is working too often. For voice-over work, check the repair before the final limiter or loudness stage, since later compression can push missed consonants forward again. The [voice-over workflow](https://soundforgepro.com/sound-forge-pro-for-voice-over-recording/) covers the broader processing order, and the [export QA checklist](https://soundforgepro.com/audio-export-qa-checklist/) gives you one last pass before delivery. ### Audio Latency Calculator: Samples to Milliseconds URL: https://soundforgepro.com/audio-latency-calculator/ Last updated: 2026-09-30T12:46:23.000Z If your interface says **256 samples**, you don't have a time value yet. At 44.1 kHz that buffer works out to about 5.80 ms in one direction, and at 48 kHz to about 5.33 ms. The calculator below does that conversion for you, keeps input and output estimates apart, and shows a simple round-trip buffer estimate. Use the result to compare settings or plan a recording session. It doesn't measure your whole computer, interface and plug-in chain, and mixing those two things up is where a lot of latency explanations go wrong. ## Audio latency calculator Enter the sample rate and buffer values shown in your audio settings. Sample rate 44.1 kHz 48 kHz 88.2 kHz 96 kHz 176.4 kHz 192 kHz Input buffer Output buffer Match input Estimated combined buffer timeInput + output buffers only **5.33 ms** Input**2.67 ms** Output**2.67 ms** Calculation and system-latency note 128 ÷ 48,000 × 1,000 = 2.67 ms per buffer This estimates buffer time, not complete system latency. Drivers, converters, routing, safety buffers, monitoring stages and plug-ins can add more delay. ## The basic samples-to-milliseconds formula One sample is one slice of a second. The sample rate tells you how many slices are taken each second, so the duration of a buffer is: `milliseconds = samples ÷ sample rate × 1000` For a 128-sample buffer at 48 kHz: `128 ÷ 48000 × 1000 = 2.67 ms` That is the duration represented by the entered buffer. It is useful, precise math. It is still only one part of the path between a sound entering an input and being heard at an output. ## Why sample rate changes the answer Keep the buffer at 256 samples and raise the sample rate from 44.1 kHz to 48 kHz. The number of samples stays the same, but each sample occupies less time. The estimate drops from about 5.80 ms to about 5.33 ms. A higher sample rate can therefore reduce the time represented by the same buffer. It also changes the amount of data your system processes. I would compare the timing estimate with the stability of the actual session rather than choosing a sample rate for latency alone. ## Buffer size, input latency and output latency Buffer size is a block of samples that the audio system processes together. Smaller blocks mean less time per block. They also leave less time for the system to complete its work before the next block arrives. The input estimate describes one entered buffer at the chosen sample rate. The output estimate describes one buffer on the way to playback. If both directions use 256 samples at 48 kHz, each displayed direction is about 5.33 ms. Real drivers may expose input and output values that are different. Enter them separately when you have them. If your software reports a safety buffer or another additional stage, keep that value in mind rather than hiding it inside a neat-looking total. ## What the round-trip estimate means For a simple buffer-only model, add the input and output estimates: `round-trip buffer estimate = input latency + output latency` With 256 samples in and 256 samples out at 48 kHz, you get about 10.67 ms. That's the time the two buffers represent together. It doesn't promise a singer will hear exactly 10.67 ms between a source and the monitored signal. A complete round trip can include interface conversion, driver behavior, safety buffers, routing, monitoring stages and plug-in delay. Some systems report these pieces differently. That is why a value shown by a driver or measured with a loopback can disagree with the calculator. ## How to read the result for recording and overdubbing With direct monitoring, the software buffer may not sit in the monitored path at all. The calculator still explains the software path in that case, but it can't describe what the performer hears through the interface’s direct-monitor mix. For software monitoring, the round-trip estimate is the number to watch first. A shorter path generally makes live playing and voice-over easier to judge, but the right setting depends on the system staying stable while recording. For overdubs, treat the estimate as a timing clue. If a new take feels late, check the monitoring route and the reported latency before you start nudging clips by eye. A buffer conversion won't diagnose every timing problem, but it can show whether the displayed settings already add up to several milliseconds of travel. ## Why the calculator can differ from your driver The calculator only knows the values you type in. Your driver may include values that don't show up in the buffer control, round numbers differently, or report an end-to-end figure instead of a single buffer duration. Plug-ins can add processing delay too. A linear-phase processor, a look-ahead dynamics tool or any other latency-inducing stage can change what you hear even when the audio buffer stays the same. Bypass or remove those stages only as a diagnostic step in the software you already use; this page doesn't claim a test result for any particular plug-in. When the number matters for a live performance or tight overdub, use the interface or DAW’s documented latency readout and, where appropriate, a loopback measurement. Keep the calculator result as a transparent estimate alongside that evidence. ## Related Sound Forge workflows Latency is one part of a recording chain. If you are setting up a voice session, the guide to [Sound Forge Pro for voice-over recording](https://soundforgepro.com/sound-forge-pro-for-voice-over-recording/) helps with the wider workflow. For recording setup questions, see [how to record audio in Sound Forge Pro](https://soundforgepro.com/how-to-record-audio-in-sound-forge-pro/). If a project needs a different technical format, the guide to [changing sample rate in Sound Forge Pro](https://soundforgepro.com/how-to-change-sample-rate-sound-forge-pro/) covers that separate task. The calculator here interprets timing and doesn't convert sample rates. ## Questions this calculator can answer ### How many milliseconds is 512 samples at 48 kHz? About 10.67 ms for one buffer: `512 ÷ 48000 × 1000`. If you mean a simple input-plus-output estimate with 512 samples in both directions, it is about 21.33 ms. ### Does a higher sample rate always make latency better? It makes the same sample count represent less time. It does not guarantee a better complete system result, because stability, driver behavior, routing and processing stages still matter. ### Is buffer latency the same as round-trip latency? No. One buffer is one direction in this model. The simple round-trip estimate adds the input and output buffers, while a real round trip may include additional stages. ### Should I always use the smallest buffer? No. Choose a buffer that gives the monitoring response you need while the session remains stable. The smallest setting is not automatically the most useful setting. ### GoldWave vs Sound Forge: Which Audio Editor Fits Your Work? URL: https://soundforgepro.com/goldwave-vs-sound-forge/ Last updated: 2026-10-09T21:04:44.000Z GoldWave and Sound Forge overlap enough to make a feature list confusing. Both can record, cut, process and convert audio. The useful difference is how far you expect the editor to sit at the center of your workflow. **My short answer:** GoldWave is the easier value choice for fast waveform editing, conversion and repeatable batch jobs. Sound Forge Pro makes more sense when you need a deeper Windows mastering/restoration environment, third-party plug-in organization, scripting and documented multichannel workflows. ![Fast batch audio workflow compared with an extensible restoration and mastering workflow](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/09/editor-choice-workflows-20260917.webp) GoldWave fits compact repeated conversion work; Sound Forge Pro fits a deeper setup built around plug-ins, scripting and multichannel files. ## GoldWave vs Sound Forge at a glance | Decision | GoldWave | Sound Forge Pro | | ---------------- | -------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------ | | Best fit | Quick editing, recording, restoration basics and bulk conversion | Detailed editing, mastering, restoration chains and extensible production work | | Batch work | Strong built-in batch processing, folders/subfolders and command-line processing | Batch Converter plus a broader scripting system | | Plug-in workflow | Built-in effects and supported plug-ins, with a simpler overall environment | Dedicated Plug-In Manager and a workflow designed around larger effect collections | | Automation | Presets, batch processing and command-line options | JScript, VBScript, C# and compiled DLL scripts documented by the vendor | | Multichannel | Check the exact format and task before committing | Official help documents editing and rendering workflows for supported multichannel formats | | Licensing | Official store lists one-year and lifetime licenses | Edition and offer depend on the current Sound Forge product page | | Learning curve | Usually quicker for occasional editing and conversion | More workspace depth to learn, especially with plug-ins and scripts | ## Choose GoldWave for speed and batch conversion GoldWave's clearest advantage is the amount of routine work it puts in one compact editor. Its [official documentation](https://goldwave.com/help/desktop/FileBatch.html) covers batch conversion, effects, metadata changes, folder recursion and preservation of folder hierarchy. The product page also documents [command-line processing](https://www.goldwave.com/goldwave.php) for advanced bulk jobs. That combination fits speech cleanup, format conversion, archive preparation and repeated processing where the steps are known. If your regular task is “apply this chain to a folder and convert the results,” GoldWave deserves the first trial. The [current official store](https://www.goldwave.com/gwbuy.php) lists a one-year license and a lifetime license. The one-year option expires a year after purchase, when the software returns to evaluation mode, while the lifetime option never expires and includes free upgrades. Prices and package terms can change, so check the store; a comparison article isn't a quote. ## Choose Sound Forge Pro for an extensible editor Sound Forge Pro becomes more convincing when the editor must grow with a larger restoration or mastering setup. The 2026 help system documents a [Plug-In Manager for organizing and loading effects](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/proonly/plug-in%5Fmanager.htm), and a [Script Editor](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/proonly/scripting%5F-%5Foverview.htm) that can run or create JScript, VBScript, C# and compiled DLL scripts. The vendor says its Batch Converter was built with that scripting system. Sound Forge also documents [multichannel editing for supported formats](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/multichannel%5Faudio-overview.htm), including Wave and Wave64, with channel-count rules for some video-oriented formats. That doesn't make every multichannel production automatic. It does mean the application has a documented path for work that goes beyond a simple stereo file. If you already own restoration, metering or mastering plug-ins and want them arranged around detailed waveform editing, Sound Forge Pro is the stronger fit of these two. Check the [current Sound Forge pricing guide](https://soundforgepro.com/sound-forge-pro-pricing/) for the site's maintained edition and offer notes. ## Editing and restoration: the practical difference For isolated cuts, fades, gain changes and straightforward noise cleanup, either editor can be enough. The decision changes when the file needs a chain of precise repairs, repeated revisions and specialist plug-ins. GoldWave keeps the workflow direct. Sound Forge gives more room for an organized plug-in library and custom automation. Neither purchase lets you skip source-safe editing. Keep an untouched original, save a new version before destructive processing, and compare processed audio at matched loudness. For restoration planning, work from the [audio restoration guide](https://soundforgepro.com/audio-restoration/) instead of picking software off a marketing checklist. ## Which one should you buy? - **Pick GoldWave** if low-friction editing, conversion and folder-based batch work cover most of your jobs. - **Pick Sound Forge Pro** if you expect plug-in-heavy restoration, custom scripts, detailed mastering work or supported multichannel files. - **Trial both** if your deciding issue is device routing, a specific file codec or a third-party plug-in. Compatibility at the exact version level matters more than a general feature claim. - **Keep your current editor** if it already gets the work done reliably. A new waveform editor earns its place when it removes a real bottleneck. Another layout on its own isn't enough. ## Questions to answer during the trial 1. Can it open and save the files you actually receive without an extra conversion? 2. Does it see your recording device and preferred driver mode? 3. Do your essential plug-ins load, preserve settings and render correctly? 4. Can you repeat a five-file job without rebuilding every step? 5. Can a colleague reopen the result with the metadata and channel layout intact? 6. Does the license match how many systems and how long you need to use it? ### Audio Export QA Checklist: Catch Problems Before Delivery URL: https://soundforgepro.com/audio-export-qa-checklist/ Last updated: 2026-10-09T21:06:04.000Z An export isn't finished when the progress bar disappears. The delivered file can still have the wrong channel layout, a clipped encode, a missing tail, stale metadata, or a perfectly valid format the recipient never asked for. This checklist keeps the creative approval and the technical handoff apart. ## 1\. Freeze the delivery specification Write down the destination requirements before you open the render dialog. “High quality WAV” is not a specification. Note the container, codec, sample rate, bit depth or bitrate, channel layout, loudness target, peak ceiling, filename pattern and metadata requirements. ![Audio export moving through edit, level, channel, listening and delivery checks](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/09/export-qa-chain-20260917.webp) Approve the rendered file itself: verify the edit, meters, channel behavior, reopened export and final delivery copy. | Field | Example only | Verify against | | ------------------- | --------------------------------------------------- | --------------------------------------------- | | Container and codec | WAV PCM or AAC in MP4 | Client, platform or broadcaster specification | | Sample rate | 48 kHz for many video workflows | The destination and source project | | Bit depth / bitrate | 24-bit PCM master; delivery bitrate set by platform | Required master and distribution copies | | Channels | Mono, stereo or named multichannel layout | Playback route and delivery contract | | Loudness and peak | Program-specific LUFS/LKFS and true-peak ceiling | Current destination standard | | Metadata | Title, artist, episode, ISRC or BWF fields | Release sheet or asset manifest | Targets vary. [EBU R 128](https://tech.ebu.ch/publications/r128) uses −23 LUFS as its program loudness reference for European broadcast workflows, while web platforms publish their own encoding recommendations. [YouTube's current upload guidance](https://support.google.com/youtube/answer/1722171?hl=en), for example, recommends an MP4 container with 48 kHz audio encoded as AAC-LC, Opus or Eclipsa Audio. Neither example should be copied into an unrelated delivery. ## 2\. Preserve a clean master - Save a new project or file version before final processing. - Keep a lossless master at the native production sample rate and an appropriate bit depth. - Create distribution encodes from that master instead of repeatedly transcoding a lossy file. - Apply dither only when reducing bit depth, and avoid applying it again to an already dithered master. ## 3\. Check the edit before rendering - Confirm the start is clean and intentional. Look for a clipped first transient or too much pre-roll. - Listen all the way through the final fade, reverb and ambience tail, and make sure the selection doesn't cut it short. - Check edits, crossfades, mute regions and processing bypass states. - Confirm markers, regions and channel routing if the export depends on them. - Bypass any temporary monitoring correction that shouldn't print into the file. ## 4\. Check level, loudness and headroom Peak normalization and loudness normalization solve different problems. Peak normalization moves the highest sample to a chosen ceiling. Loudness normalization changes gain according to an average program measurement. [Sound Forge's documentation](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/proonly/normalizing%5Faudio.htm) also warns that converting to a compressed format such as MP3 can clip peaks sitting at or near 0 dB, and it suggests normalizing to about −0.9 dB as a starting point. That's a reason to leave margin rather than aiming blindly at 0 dBFS. - Measure the full program. A highlighted excerpt won't do. - Check sample peaks and true peaks when the destination specifies them. - Confirm the loudness measurement mode and gating match the requested standard. - Listen after any limiter, normalization or codec stage for pumping, distortion and softened transients. - Don't raise a quiet master just to make the waveform look bigger. ## 5\. Verify channel layout and polarity Open the rendered file and inspect it as a new asset. Confirm that mono hasn't turned into dual mono by accident, left and right aren't swapped, and a multichannel file follows the expected order. For stereo material, check both channels separately and do a mono compatibility listen if the destination may sum them. The [left/right speaker test](https://soundforgepro.com/left-right-speaker-test/) helps you check the playback path. You still need to check the channel metadata and waveform inside the delivered file. ## 6\. Reopen the actual export Don't approve the timeline and assume the render matches it. Close the render dialog, import or open the output file, then listen to the start, several transitions, the loudest section and the end. Check duration, silence, fades, sample rate, bit depth or codec, channels and metadata on the exported asset itself. ## 7\. Test the delivery copy - Play it in a second application or on the destination device when practical. - For a lossy encode, compare it with the lossless master at matched loudness. - Confirm the filename, extension and version number are unambiguous. - Check that album, episode or reel assets use the same naming pattern. - Create a checksum when files move through a formal handoff or archive. - Keep the master, delivery file and notes together so the export can be reproduced. ## A compact sign-off block | Check | Pass condition | | ------------- | -------------------------------------------------------------------------------------- | | Specification | Format, sample rate, depth/bitrate, channels and targets match the written requirement | | Content | Correct version, complete beginning and tail, no accidental mute or bypass | | Level | Requested loudness and peak limits verified on the full export | | Channels | Layout, order, polarity and mono behavior are intentional | | Metadata | Required fields present and stale fields removed | | Playback | Rendered file reopens and plays in a second path | | Handoff | Filename, checksum and accompanying notes identify the approved version | ### How to Remove Plosives from Audio Without Thinning the Voice URL: https://soundforgepro.com/remove-plosives-from-audio/ Last updated: 2026-10-09T01:14:31.000Z A plosive is a short burst of air that hits the microphone on consonants such as P and B. On the waveform it may look like an oversized low-frequency thump, but the useful consonant and the unwanted blast often overlap. That is why a broad high-pass filter across the whole recording can solve one problem by making the voice sound smaller. ## Start with the smallest repair My preferred order is local level reduction, local low-frequency control, then spectral repair if the burst still calls attention to itself. Each step should affect only the plosive and its immediate transition into the next sound. 1. **Duplicate or preserve the source.** Work on a copy or save a new version before destructive editing. 2. **Find the actual burst.** Listen at normal speed, then inspect the first few tens of milliseconds around the consonant. Do not select the whole word by habit. 3. **Reduce level first.** Lower the selected burst or use a short volume envelope. A modest change often controls the pressure wave without dulling the syllable. 4. **Apply local low-frequency reduction.** If the thump remains, use a high-pass filter or low-shelf cut only on the problem area. Move the cutoff while listening in context rather than copying a number from another voice. 5. **Use spectral repair for the residue.** When the blast is visible as a concentrated low-frequency event, attenuate that region instead of processing the full spectrum. 6. **Repair the boundaries.** Add tiny fades or crossfades if the edit clicks, then compare the repaired phrase with the untouched audio before and after it. ## Why a global high-pass filter often goes too far A high-pass filter is useful when the recording has continuous rumble or when every plosive shares the same low-frequency problem. It is a poor first choice for one or two isolated blasts. A permanent filter changes vowels, chest resonance and proximity effect throughout the file, while the defect may last only a fraction of a second. If you do use a global filter, set it for the recording rather than the label “voice.” Raise the cutoff until the thumps improve, then back it down until the body of the voice returns. Compare at matched loudness; a brighter result can seem clearer simply because its midrange is more exposed. ## A decision map for difficult plosives ![Plosive burst isolated for local gain, low-frequency EQ or spectral repair](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/10/plosive-repair-map-20260917-v20261006.webp) Start with a local level reduction, then add a local high-pass or low-shelf cut, and use spectral repair only if the burst still stands out. | What you hear | Likely repair | What to protect | | ------------------------------------ | ----------------------------------------------------------------- | ----------------------------------------------------------------- | | A soft puff with no obvious thump | Short level reduction or volume envelope | The attack that makes the word intelligible | | A deep P or B thump | Local high-pass or low-shelf cut after level repair | Vowel weight immediately after the consonant | | A broad blast covering speech detail | Spectral attenuation in several light passes | Upper harmonics and the natural transition into the word | | A click at the edit boundary | Move the boundary to a zero crossing or add a tiny crossfade | Timing and consonant definition | | Dozens of similar plosives | Consistent preset or batch-assisted pass, followed by spot checks | False positives on kick drums, handling noise and low male vowels | ## What Sound Forge can do in this workflow Sound Forge gives you sample-level selection, gain changes, EQ, fades and plug-in processing in a single-file editor. The exact tool matters less than the selection. Zoom far enough to include the pressure burst without cutting away the consonant, preview the edit in the full sentence, and keep the original available for comparison. If you have a dedicated restoration plug-in, use it as a targeted repair rather than an automatic excuse to process the entire file. [iZotope describes De-plosive](https://www.izotope.com/community/blog/removing-plosives-from-a-voice-recording) as a tool for attenuating low-frequency plosive energy while preserving the voice; that still requires listening for missed events and overcorrection. ## Prevention is cleaner than restoration Shure and RØDE both point to [microphone position and a pop filter as the first defense](https://content-files.shure.com/Pubs/introduction-to-home-recording-and-podcasting/homerecording-podcasting.pdf). [Place the microphone slightly off axis](https://help.rode.com/hc/en-us/articles/7645976167311-Why-Does-the-Microphone-Capture-Mouth-Noises) so the air burst does not strike the capsule directly. Keep the pop filter far enough from the capsule to slow the air before it reaches the microphone, and keep the speaker's distance reasonably consistent. A high-pass filter on the way in can reduce rumble, but it cannot undo capsule or preamp overload. Record a short phrase with repeated P and B sounds before the real take. The [online microphone test](https://soundforgepro.com/microphone-test/) can expose the burst and clipping risk before you open the editor. ## Quality check before export - Listen to the repaired word in the full sentence, not only in a loop. - Compare before and after at similar loudness. - Check headphones and speakers; a plosive can disappear on small speakers yet remain obvious on headphones. - Listen for a missing consonant, a hollow vowel or a click at either boundary. - Scan the rest of the file for events that need the same treatment, then run the [audio export QA checklist](https://soundforgepro.com/audio-export-qa-checklist/). ### Online Microphone Test: Level, Clipping and Noise Check URL: https://soundforgepro.com/microphone-test/ Last updated: 2026-10-04T20:03:38.000Z Run this test before you open a recorder or start changing drivers. It answers one narrow question: is the browser getting a clean enough signal from the microphone you plan to use? Press Start, speak at the distance and level you'll actually record at, then make a short sample and listen back. Start microphone test Permission is requested only after you press Start. Audio stays in this tab. MicrophoneStop test Listening… RMS**— dBFS** Peak**— dBFS** Headroom**— dB** Record 10-second sampleStop recordingDiscard00:00 The sample is held as an in-memory browser Blob. Stop, discard, reload or close the tab to remove it. ## How to read the microphone meter The numbers are digital levels in **dBFS**. Zero dBFS is the digital ceiling; it has nothing to do with acoustic sound pressure. A peak near 0 dBFS means the converter or browser stream has almost no headroom left. It tells you nothing about how loud the room is in dB SPL. | Result | What it means | Next move | | --------------------------------------------- | ----------------------------------------------------------------------------- | ----------------------------------------------------------------- | | Peak above −1 dBFS | The stream is at or very near the digital ceiling | Reduce interface or system input gain and repeat the loudest line | | Peak from roughly −12 to −6 dBFS | A practical spoken-word starting range with useful headroom | Listen to the sample for room tone, handling noise and processing | | RMS stays below about −45 dBFS while speaking | The selected input may be too quiet, too far away or muted | Confirm the device, distance and gain before boosting later | | Meter moves in silence | You are seeing the current input chain, including gain and browser processing | Mute fans and HVAC, move the mic, or lower unnecessary gain | Treat these ranges as working guides rather than a delivery standard. A drum hit, whispered narration and a video call need different margins. What you're avoiding is clipping on one side and a recording so quiet that later gain drags the noise up with it on the other. ![Microphone signal shown at low, healthy and clipped recording levels](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/09/microphone-level-guide-20260917.webp) A useful input check separates a signal that is too quiet from one with working headroom and one already flattened by clipping. ## Run a useful 30-second check 1. Select the real input after permission is granted. Device labels may be hidden before the browser has permission. 2. Say a quiet phrase, a normal phrase and the loudest line you expect to record. 3. Watch the peak as well as the moving average. A short overload is easy to miss by ear. 4. Record a short sample and listen on headphones. Check for plosives, hum, room echo, [keyboard vibration](https://soundforgepro.com/reduce-keyboard-noise-voice-recording-sound-forge/) and automatic gain changes. 5. Stop the test before changing cables, interfaces or microphones. The Stop button ends every media track and the live analysis. ## Why the noise reading is only an input-chain estimate The page measures the samples the browser delivers. It can't calibrate the microphone, preamp, interface or room. Input gain changes the reading, and so do automatic gain control, echo cancellation and noise suppression. The settings line shows those values whenever the browser exposes them. Use the quiet reading to compare one controlled change at a time: fan on versus off, microphone close versus far, laptop on the desk versus isolated. Just don't call the result the room's acoustic noise level. ## If the meter is silent Start with the selected device. A laptop may offer a built-in array, a webcam microphone and an interface all at once. If the right name is selected and the meter still doesn't move, check the hardware mute, the interface gain and the operating system's input level. Close any communication software that might be holding the device in exclusive mode. If the browser says permission is blocked, change the microphone permission for this site in the browser's site settings. Pressing Start over and over won't override a stored denial. ## If the signal clips Lower gain at the earliest controllable point. If the microphone or interface clips before the signal reaches the browser, pulling a fader down later only makes the clipped waveform quieter. Repeat the loudest phrase after every gain change and leave margin for a performance that is stronger than the rehearsal. When the problem is a burst on P or B rather than broad overload, use the workflow in [the plosive-removal guide](https://soundforgepro.com/remove-plosives-from-audio/); prevention with placement and a pop filter is usually cleaner than repair. ## Privacy and browser support The test calls the browser's [getUserMedia()](https://developer.mozilla.org/en-US/docs/Web/API/MediaDevices/getUserMedia) method only after Start. The live waveform comes from an [AnalyserNode](https://developer.mozilla.org/en-US/docs/Web/API/AnalyserNode). The optional sample uses [MediaRecorder](https://developer.mozilla.org/en-US/docs/Web/API/MediaRecorder) and stays as a temporary Blob in this tab. There is no upload step. Microphone access requires HTTPS and a browser that supports the relevant media APIs. Stop, Discard, reload and closing the tab all remove the in-memory sample; Stop also ends the microphone tracks. ## What this test cannot diagnose It can't identify a damaged capsule, measure frequency response, certify a noise floor, calculate dB SPL or prove that a Sound Forge recording route is set up correctly. For editor-specific input and driver problems, use the [Sound Forge recording troubleshooting guide](https://soundforgepro.com/sound-forge-pro-not-recording-audio/). This page is the quick browser-side check you run before that deeper path. ### Pink Noise Generator URL: https://soundforgepro.com/pink-noise-generator/ Last updated: 2026-10-09T12:41:22.000Z This pink noise generator starts with the useful part: press Play and hear a fresh signal made in your browser. Pink is selected by default; White and Brown are included as quick comparisons. Nothing is recorded or uploaded, and the 30-second WAV export is created locally on the same device. Browser generator · no upload ## Play pink noise The signal is created on this device. The page does not request a microphone, record a room or upload audio. !**Start with device volume low.** Tool level starts at 5% and is not calibrated dB SPL. Stop if the sound feels uncomfortable. Noise color White0 dB/oct Pinkabout −3 dB/oct Brownabout −6 dB/oct Noise power-density slope comparison White is flat, pink falls about three decibels per octave, and brown falls about six decibels per octave. LOWHIGH Selected profile**Pink · 1/f** Equal power in each octave gives a softer top end than white noise. Playback**Stopped** Pink noise is ready. Press Play to start. ready Play pink noiseStop Tool level 5% Stop timerOff15 min30 min60 min WAV · selected levelDownload 30s WAV Ready. Audio starts only after you press Play. Digital noise reference, not a calibrated acoustic source, hearing test or medical treatment. Press Escape to stop. ## How to use the pink noise generator 1. **Turn your device volume down before starting.** The tool level begins at 5%, but that percentage is only digital gain inside this page. It is not a sound-pressure reading. 2. **Leave Pink selected and press Play.** If you want a direct comparison, switch to White or Brown while the player is running. The signal changes without starting a second audio stream. 3. **Set a timer or download a short file only if you need it.** The timer fades the signal before stopping. Download creates a new 30-second mono, 16-bit PCM WAV using the selected tool level. It is not a recording of the stereo preview; keep external-player volume low when opening it. If an iPhone stays silent, keep device volume low and check that sound is routed to the intended speaker or headphones. Tap Play again if the page reports blocked playback. A running audio context confirms that the browser started its audio engine; it cannot confirm that your output device is audible. Stop before changing the output route. ## What pink noise actually is Pink noise is random noise whose power spectral density is proportional to 1/f. That density falls by about 3 dB each time frequency doubles, leaving roughly equal power in each octave. The University of Illinois [acoustical-physics notes on white, pink and brown noise](https://courses.physics.illinois.edu/phys406/sp2017/Lecture%5FNotes/P406POM%5FLecture%5FNotes/P406POM%5FLect15.pdf) show the three profiles as 1/f⁰, 1/f¹ and 1/f². That distinction is why pink noise sounds less bright than white noise. White noise is flat per hertz, and higher octaves contain many more hertz-wide bins than lower octaves. Pink noise reduces the density as frequency rises, balancing power by octave rather than by one-hertz slice. The slope describes a statistical signal rather than a fixed pitch. Pink noise contains continuously changing random samples across a broad spectrum. If you need an exact periodic frequency such as 440 Hz, reach for the [Online Tone Generator](https://soundforgepro.com/online-tone-generator/) instead. ## Pink vs white vs brown noise | Noise color | Power-density profile | Typical impression | Useful check | | ----------- | ------------------------ | ---------------------------------- | ------------------------------------------------------------- | | White | Flat per hertz, 1/f⁰ | Bright, steady hiss | Broadband signal path and obvious high-frequency response | | Pink | About −3 dB/octave, 1/f | Softer and more balanced by octave | Broad listening comparison and spectrum reference | | Brown | About −6 dB/octave, 1/f² | Deeper, bass-heavy rumble | Compare how a system handles stronger low-frequency weighting | Those descriptions aren't promises that every laptop, phone, speaker or headphone reproduces the profile accurately. Small speakers may remove much of the low end from brown noise, and a room and playback system can create peaks and dips that aren't present in the digital source. ## How this browser generator works The page creates an output-only Web Audio graph after a deliberate Play tap. That matters because modern browsers restrict audible autoplay; [MDN's Web Audio best-practice guidance](https://developer.mozilla.org/en-US/docs/Web/API/Web%5FAudio%5FAPI/Best%5Fpractices) recommends creating or resuming the audio context from a user gesture. White mode starts from independent random samples. Pink mode filters those samples to approximate a 1/f spectrum; Brown uses leaky integration for a bass-heavy, approximately 1/f² profile. The live player generates two independent channels. Stop briefly fades the output before disconnecting the source. The pink filter follows [Paul Kellet's published filter design](https://www.firstpr.com.au/dsp/pink-noise/). These are finite-band approximations, not certified reference spectra at every sample rate. A browser interruption can stop playback. [MDN documents an interrupted AudioContext state on iOS Safari](https://developer.mozilla.org/en-US/docs/Web/API/BaseAudioContext/state) when a page is backgrounded or another app takes audio. This tool stops on page hide and rebuilds an interrupted context on the next user tap. ## What the tool can and cannot tell you The generator can supply a practical digital reference, let you hear the difference between nominal noise colors and create a short file for an editing test. It cannot certify the acoustic result at your ears. Browser gain, system volume, amplifier gain, transducer sensitivity, fit and distance all change the real sound-pressure level. To inspect what a microphone or finished file actually contains, use the [Audio Spectrum Analyzer](https://soundforgepro.com/audio-spectrum-analyzer/). When you want to map a peak or EQ term to a broad region, open the [Audio Frequency Chart](https://soundforgepro.com/audio-frequency-chart/). A generated target and a measured result are different jobs. ## A careful note about sleep and focus claims People commonly use steady background noise because they prefer it or because it makes intermittent room sounds less distinct. That personal use is not the same as a proven treatment. A [systematic review of white and pink auditory stimulation in adults](https://pmc.ncbi.nlm.nih.gov/articles/PMC9163611/) found positive results in some studies but concluded that the evidence was not strong. Another [systematic review of continuous noise as a sleep aid](https://pubmed.ncbi.nlm.nih.gov/33007706/) rated the overall evidence as very low quality. A [2026 laboratory study of 25 adults](https://pubmed.ncbi.nlm.nih.gov/41627391/) found less REM sleep during its pink-noise condition than during the quiet control night. A separate [2026 pilot study of 12 adults](https://www.nature.com/articles/s43856-026-01380-5) found that pink noise reduced some traffic-noise-related sleep disruptions under different laboratory conditions. Both studies were small and short-term. Neither establishes that leaving this browser generator on will improve your sleep. Treat the generator as an audio tool. It isn't a treatment for insomnia, tinnitus, ADHD, hyperacusis or another condition. If a symptom affects sleep, hearing or daily life, the useful next step is professional advice rather than increasing the volume of a browser signal. ## Keep the level conservative Noise can feel less eventful than music, but exposure still depends on how loud it is and how long it plays. The [WHO safe-listening guidance](https://www.who.int/news-room/questions-and-answers/item/deafness-and-hearing-loss-safe-listening) recommends keeping personal-device volume down, limiting time and taking breaks. CDC/NIOSH likewise explains that hearing risk depends on both measured level and exposure duration. This page intentionally starts at a low tool gain and caps its own control at 25%. That cap cannot override a device or amplifier set too high, so lower system volume first. Stop immediately if the sound is uncomfortable, if your ears ring or if hearing feels dulled. ## Pink noise generator FAQ ### Is this pink noise generator free? Yes. Playback, color comparison, the timer and the 30-second WAV export work in the browser without an account or upload. ### Does the page record my microphone? No. The tool creates an output signal and never calls for microphone access. It does not read an audio file or send generated samples to a server. ### Why does pink noise sound softer than white noise? Pink noise reduces power density as frequency rises, by about 3 dB per octave. White noise remains flat per hertz, so its upper octaves contain more total power and usually sound brighter. ### Is pink noise the same as rain? No. Rain can have a broadly similar soft, steady character, but a real rain recording contains changing impacts, resonances and environmental detail. Pink noise is a statistical 1/f signal. ### Can I use the downloaded WAV as a calibrated test signal? You can use it as a nominal digital pink-noise file, but it does not calibrate the playback chain. Acoustic calibration still requires suitable measurement equipment, a known reference level and a controlled procedure. ### Audio Frequency Chart: EQ Bands & Instruments URL: https://soundforgepro.com/audio-frequency-chart/ Last updated: 2026-10-10T13:19:21.000Z An audio frequency chart is a map; it doesn't prescribe EQ moves. Use this EQ frequency chart by task: choose Problem for muddy, harsh or sibilant symptoms, Voice & instruments for approximate source regions, or EQ bands for broad ranges. Then find the exact peak or buildup in the recording itself. The chart covers the conventional full-band reference from 20 Hz to 20 kHz. When you're ready to make a correction, use the [Sound Forge equalizer guide](https://soundforgepro.com/how-to-use-equalizer-sound-forge-pro/) and judge the result in the full mix. Interactive reference · no upload ## Find the frequency region Problem Voice & instruments EQ bands Rumble Boomy Muddy Boxy Honky Harsh Sibilant Dull 20 Hz–20 kHz logarithmic map Muddy · 200–500 Hz Audio frequency chart from 20 hertz to 20 kilohertz Seven broad audio bands on a logarithmic scale. The selected range is highlighted. Approximate regions · scroll sideways for the full chart. Problem range ### Muddy **200–500 Hz** Excess or masking here can blur low instruments and make a mix feel crowded. EQ advice Listen in the full mix, then sweep a modest bell to locate the actual buildup before cutting. Play short tone Stop Reference: 316 Hz Need the real peaks? [Analyze a file or microphone](https://soundforgepro.com/audio-spectrum-analyzer/). Download SVG Download PNG **Keep system volume low.** Not calibrated SPL or a hearing test. Press Play for a two-second reference tone. ## How to read an audio frequency chart Frequency is the number of cycles per second, measured in hertz. The scale is logarithmic because equal musical intervals are frequency ratios: moving from 100 Hz to 200 Hz is one octave, and so is moving from 5 kHz to 10 kHz. A linear chart would squeeze most of the useful low and midrange detail into the left edge. The seven bands in this tool are working conventions. They aren't physical borders. [iZotope’s Tonal Balance Control explanation](https://www.izotope.com/community/blog/why-izotope-created-the-tonal-balance-control-plug-in), for example, groups the spectrum into four regions. Our 200–500 Hz “Muddy” search overlaps two of our EQ bands, and that's on purpose: a problem range doesn't have to respect a band boundary. ## The seven broad EQ frequency bands | Band | Starting range | What it often contributes | Too much can sound like | | ---------- | -------------- | ---------------------------------------- | ----------------------------- | | Sub-bass | 20–60 Hz | Deep weight, room or handling rumble | Rumble, wasted headroom | | Bass | 60–250 Hz | Kick and bass weight, warmth, vocal body | Boom, woolliness | | Low mids | 250–500 Hz | Body and density | Mud, boxiness | | Mids | 500 Hz–2 kHz | Definition, note identity, speech detail | Honk, nasal or telephone tone | | Upper mids | 2–4 kHz | Presence, attack and intelligibility | Harshness, fatigue | | Presence | 4–8 kHz | Consonants, edge and close detail | Sibilance, brittleness | | Brilliance | 8–20 kHz | Air, sheen and very fine transients | Hiss or brittle top end | “Muddy” might mean one resonant track near 280 Hz, several parts masking each other, or a room problem. Solo can help you locate a source; judge the correction in the mix. For consonant harshness, [iZotope’s vocal-editing guide](https://www.izotope.com/community/blog/vocal-editing-101) suggests looking around 5–10 kHz, while this tool gives a wider 4–10 kHz starting window. Neither is a preset for every voice. ## Fundamental, harmonics and spectral energy are different For a periodic sound, the fundamental frequency is the repetition rate of the complete waveform. Harmonics occur at whole-number multiples of that rate; the fundamental need not be the strongest audible component. The [UNSW explanation of spectra and harmonics](https://phys.unsw.edu.au/jw/sound.spectrum.html) separates those components from the overall shape of the spectrum. A recorded instrument can also contain breath, bow or impact noise that does not follow a harmonic series. A bass note can have a low fundamental while much of its audible definition sits higher. A small speaker may reproduce enough harmonics for you to identify the pitch even when it delivers little of the fundamental. So the tallest spectral peak isn't automatically the note you hear. For exact note-to-hertz values, use the [musical note frequency table](https://soundforgepro.com/musical-note-frequency-chart/); this page is an EQ-region reference. ## Voice frequency: pitch is not speech bandwidth Voice charts often blend three different ideas: vocal-fold pitch, the wider set of harmonics and formants in the acoustic signal, and the pass-band used to transmit speech. They aren't interchangeable. [ITU-T speech and audio coding material](https://www.itu.int/en/ITU-T/studygroups/2013-2016/16/Pages/q10.aspx) describes conventional narrowband speech coding as typically 300–3,400 Hz and wideband coding as typically 50–7,000 Hz. Those are transmission categories; they don't describe the full natural output range of every speaker. The source overlays are approximate editing regions. They aren't measured instrument limits or complete playing ranges. “Lower voice” and “Higher voice” are examples rather than gender categories, and singers can move outside both boxes. A five-string bass or a detuned guitar can reach below the marked starting region. Use the recording to separate body, clarity and consonant noise, because a colored bar can't tell you what's missing. ## Equal level does not mean equal loudness A 60 Hz tone and a 1 kHz tone at the same digital amplitude won't necessarily seem equally loud. [ISO 226:2023](https://www.iso.org/standard/83117.html) specifies equal-loudness combinations for pure tones under defined listening conditions, with data from 20 Hz to 12.5 kHz. The chart therefore describes where a sound sits in frequency; perceived loudness is a separate matter. The browser tone is only a short reference, so start with system volume low. It isn't calibrated sound pressure, a hearing test or permission to raise the level until every frequency seems equally loud. [CDC/NIOSH noise guidance](https://www.cdc.gov/niosh/noise/about/noise.html) also makes clear that hearing risk depends on both level and exposure duration. ## How to use the chart without over-EQing 1. **Name the symptom first.** “The vocal is difficult to understand” is more useful than “I should boost 3 kHz.” 2. **Check the arrangement and level.** Masking, balance and microphone position can create the problem before EQ does. 3. **Use the chart to choose a search region.** Don't cut the whole highlighted band on reflex. 4. **Measure the actual signal.** Open the [Audio Spectrum Analyzer](https://soundforgepro.com/audio-spectrum-analyzer/) for a file, microphone or test tone. 5. **Make a small change and compare in context.** Bypass the EQ at matched loudness and keep the change only if the mix improves. If the problem is a fixed electrical tone rather than broad tonal balance, use the [hiss and hum removal workflow](https://soundforgepro.com/remove-hiss-hum-sound-forge/). If you need an exact continuous frequency or sweep, the dedicated [Online Tone Generator](https://soundforgepro.com/online-tone-generator/) gives you finer control than the short reference button here. ## Chart, analyzer, tone generator or note table? | You need to… | Use | | ----------------------------------------------------------------- | --------------------------------------------------------------------------------------- | | Map a listening term, band, voice or instrument to a broad region | This Audio Frequency Chart | | Measure peaks in a real file or microphone signal | [Audio Spectrum Analyzer](https://soundforgepro.com/audio-spectrum-analyzer/) | | Hear a precise tone or run a controlled sweep | [Online Tone Generator](https://soundforgepro.com/online-tone-generator/) | | Convert a musical note, MIDI number and frequency | [Musical Note Frequency Chart](https://soundforgepro.com/musical-note-frequency-chart/) | | Identify one sustained live note | [Pitch Detector](https://soundforgepro.com/pitch-detector/) | ## Audio frequency chart FAQ ### What is the audio frequency range? For a general full-band audio reference, this chart uses 20 Hz to 20 kHz. That is a conventional system range, not a promise that every person can hear every frequency or that every microphone, speaker and recording reproduces the full span. ### What frequency range is bass? This chart treats 20–60 Hz as sub-bass and roughly 60–250 Hz as bass. The boundary is a working convention. Bass instruments also produce upper harmonics and attack detail above 250 Hz, so their useful energy does not end at the bass-band border. ### What frequency range sounds muddy? Mud is often associated with excess or masking in the low mids, roughly 200–500 Hz, but it is not one universal frequency. Use the range to search, then listen to the full mix and inspect the real signal before cutting. ### Where is vocal sibilance? The tool uses 4–10 kHz as a broad search region for vocal sibilance, not a fixed boundary. The exact center changes with the speaker, consonant, microphone and processing, so a de-esser or dynamic EQ should be tuned to the recording rather than copied from a chart. ### Can I use this chart as an EQ preset? No. It is a search map. A fixed preset cannot know the source, arrangement, room, microphone or the problem you are trying to solve. Use the chart to choose a region, verify it by ear and measurement, then make the smallest useful change. ### Musical Note Frequency Chart & Calculator URL: https://soundforgepro.com/musical-note-frequency-chart/ Last updated: 2026-10-09T21:07:57.000Z Choose a note from C0 through B8, or enter a frequency from 0.001 to 50,000 Hz to find the nearest equal-tempered note and cents offset. The A4 reference accepts 400–480 Hz. This page uses scientific pitch notation, where middle C is C4. In Hz → Note mode, the Hz value shown is your input, not the exact target frequency of the nearest note. Switch to Note → Hz to calculate that target when it is within C0–B8\. Outside that note-picker range, select a note manually. Frequencies outside MIDI 0–127 still return a mathematical note label, but not a valid MIDI note number. Values are rounded for display; calculations use unrounded numbers. Changing A4 rescales this 12-TET chart; it does not select another temperament or retune an audio file. For example, A4 = 432 Hz puts C4 at about 256.869 Hz. Use the [Audio Tools directory](https://soundforgepro.com/tag/audio-tools/) to choose a measurement or playback tool instead. Free browser calculator · no upload ## Convert notes and frequencies 12-tone equal temperament. Change A4 only when your source uses another reference. Note → Hz Hz → Note NoteCC♯ / D♭DD♯ / E♭EFF♯ / G♭GG♯ / A♭AA♯ / B♭B Octave012345678 Frequency **Hz** A4 reference **Hz**Reset ResultCopy **A4**440.000 Hz MIDI**69** Offset**0.00 cents** Names**A4** Need a live reading? Use the [Pitch Detector](https://soundforgepro.com/pitch-detector/). For playback, keep system volume low and open the [Tone Generator](https://soundforgepro.com/online-tone-generator/). Frequency chart ### C0–B8 at 440 Hz A4 Sharps Flats ‹ ShowOctave 0Octave 1Octave 2Octave 3Octave 4Octave 5Octave 6Octave 7Octave 8 › Find a note or value C0**16.35** *MIDI 12*C♯0**17.32** *MIDI 13*D0**18.35** *MIDI 14*D♯0**19.45** *MIDI 15*E0**20.60** *MIDI 16*F0**21.83** *MIDI 17*F♯0**23.12** *MIDI 18*G0**24.50** *MIDI 19*G♯0**25.96** *MIDI 20*A0**27.50** *MIDI 21*A♯0**29.14** *MIDI 22*B0**30.87** *MIDI 23* C1**32.70** *MIDI 24*C♯1**34.65** *MIDI 25*D1**36.71** *MIDI 26*D♯1**38.89** *MIDI 27*E1**41.20** *MIDI 28*F1**43.65** *MIDI 29*F♯1**46.25** *MIDI 30*G1**49.00** *MIDI 31*G♯1**51.91** *MIDI 32*A1**55.00** *MIDI 33*A♯1**58.27** *MIDI 34*B1**61.74** *MIDI 35* C2**65.41** *MIDI 36*C♯2**69.30** *MIDI 37*D2**73.42** *MIDI 38*D♯2**77.78** *MIDI 39*E2**82.41** *MIDI 40*F2**87.31** *MIDI 41*F♯2**92.50** *MIDI 42*G2**98.00** *MIDI 43*G♯2**103.83** *MIDI 44*A2**110.00** *MIDI 45*A♯2**116.54** *MIDI 46*B2**123.47** *MIDI 47* C3**130.81** *MIDI 48*C♯3**138.59** *MIDI 49*D3**146.83** *MIDI 50*D♯3**155.56** *MIDI 51*E3**164.81** *MIDI 52*F3**174.61** *MIDI 53*F♯3**185.00** *MIDI 54*G3**196.00** *MIDI 55*G♯3**207.65** *MIDI 56*A3**220.00** *MIDI 57*A♯3**233.08** *MIDI 58*B3**246.94** *MIDI 59* C4**261.63** *MIDI 60*C♯4**277.18** *MIDI 61*D4**293.66** *MIDI 62*D♯4**311.13** *MIDI 63*E4**329.63** *MIDI 64*F4**349.23** *MIDI 65*F♯4**369.99** *MIDI 66*G4**392.00** *MIDI 67*G♯4**415.30** *MIDI 68*A4**440.00** *MIDI 69*A♯4**466.16** *MIDI 70*B4**493.88** *MIDI 71* C5**523.25** *MIDI 72*C♯5**554.37** *MIDI 73*D5**587.33** *MIDI 74*D♯5**622.25** *MIDI 75*E5**659.26** *MIDI 76*F5**698.46** *MIDI 77*F♯5**739.99** *MIDI 78*G5**783.99** *MIDI 79*G♯5**830.61** *MIDI 80*A5**880.00** *MIDI 81*A♯5**932.33** *MIDI 82*B5**987.77** *MIDI 83* C6**1046.5** *MIDI 84*C♯6**1108.7** *MIDI 85*D6**1174.7** *MIDI 86*D♯6**1244.5** *MIDI 87*E6**1318.5** *MIDI 88*F6**1396.9** *MIDI 89*F♯6**1480.0** *MIDI 90*G6**1568.0** *MIDI 91*G♯6**1661.2** *MIDI 92*A6**1760.0** *MIDI 93*A♯6**1864.7** *MIDI 94*B6**1975.5** *MIDI 95* C7**2093.0** *MIDI 96*C♯7**2217.5** *MIDI 97*D7**2349.3** *MIDI 98*D♯7**2489.0** *MIDI 99*E7**2637.0** *MIDI 100*F7**2793.8** *MIDI 101*F♯7**2960.0** *MIDI 102*G7**3136.0** *MIDI 103*G♯7**3322.4** *MIDI 104*A7**3520.0** *MIDI 105*A♯7**3729.3** *MIDI 106*B7**3951.1** *MIDI 107* C8**4186.0** *MIDI 108*C♯8**4434.9** *MIDI 109*D8**4698.6** *MIDI 110*D♯8**4978.0** *MIDI 111*E8**5274.0** *MIDI 112*F8**5587.7** *MIDI 113*F♯8**5919.9** *MIDI 114*G8**6271.9** *MIDI 115*G♯8**6644.9** *MIDI 116*A8**7040.0** *MIDI 117*A♯8**7458.6** *MIDI 118*B8**7902.1** *MIDI 119* Showing octave 4\. Choose a note to load it into the converter. ## Common musical note frequencies With A4 set to 440 Hz, middle C (C4) is about 261.626 Hz, A3 is 220 Hz and A5 is 880 Hz. In this 12-TET model, moving up an octave doubles frequency; moving down halves it. The common-note table below stays at A4 = 440 Hz even when you change the interactive chart. | Note | Frequency at A4 = 440 Hz | MIDI note | | ------------- | ------------------------ | --------- | | C2 | 65.406 Hz | 36 | | E2 | 82.407 Hz | 40 | | A2 | 110.000 Hz | 45 | | C3 | 130.813 Hz | 48 | | A3 | 220.000 Hz | 57 | | C4 (middle C) | 261.626 Hz | 60 | | A4 | 440.000 Hz | 69 | | C5 | 523.251 Hz | 72 | | A5 | 880.000 Hz | 81 | For piano note frequencies, the 88-key range runs from A0 at 27.5 Hz to C8 at about 4,186.009 Hz in A440 12-TET. This is an ideal 12-TET reference, not a full tuning specification for an acoustic piano: [string stiffness can require stretched octaves](https://dsprelated.com/freebooks/pasp/Stiff%5FPiano%5FStrings.html) rather than exact 2:1 tuning. Both endpoints are included above; the chart extends farther to C0–B8 for synthesizers, analysis and other instruments. For the keyboard range, see the [note table maintained for instrument builders](https://www.liutaiomottola.com/formulae/freqtab.htm). ## What A4 = 440 Hz changes [ISO 16:1975](https://www.iso.org/standard/3601.html) specifies 440 Hz for the tuning note A in the treble stave, and ISO lists the standard as current after its 2022 confirmation. That makes A4 = 440 Hz the sensible default for a general reference chart. It's still a reference, though; it doesn't claim that every ensemble, historical recording or instrument uses the same pitch. If a session is tuned to A4 = 442 Hz, changing the reference recalculates the entire table. A4 becomes 442 Hz, A3 becomes 221 Hz and A5 becomes 884 Hz. Don't change the field just to make one unstable recording look centered; confirm the reference used by the source first. ## How note-to-frequency conversion works In twelve-tone equal temperament, an octave has a 2:1 frequency ratio and is divided into 12 equal semitone ratios. The [UNSW acoustics reference](https://newt.phys.unsw.edu.au/jw/notes.html) expresses the MIDI-to-frequency conversion as: **frequency = A4 reference × 2(MIDI note − 69) / 12** A4 is MIDI 69\. The inverse calculation finds a fractional MIDI position from a frequency. Rounding that position selects the nearest note; the leftover logarithmic distance is reported in cents. One semitone is 100 cents, so 445 Hz at an A4 reference of 440 Hz is still nearest to A4, roughly 19.6 cents sharp. ## Why octave labels sometimes disagree This page uses scientific pitch notation: middle C is C4 and A4 is the reference A above it. Some synthesizers, DAWs and hardware use a [different octave number for the same MIDI note](https://help.morningstar.io/en/article/midi-note-numbering-standards-1hu91ts/). Match MIDI note 60 when octave labels disagree, and confirm the tuning reference separately. A MIDI note number is a key identifier, not a guarantee of one frequency: pitch bend, transposition or custom tuning can change the sound. Sharps and flats can also name the same equal-tempered pitch. C♯4 and D♭4 both map to MIDI 61 and the same frequency here. The Sharps/Flats control changes spelling only; it doesn't touch the calculation. ## Chart, pitch detector or spectrum analyzer? | You need to… | Use | Why | | ------------------------------------------- | ----------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------ | | Look up or convert a known note or Hz value | This chart | It performs deterministic 12-TET math without microphone access. | | Identify one sustained live note | [Pitch Detector](https://soundforgepro.com/pitch-detector/) | It estimates one sustained fundamental within roughly 65–2,000 Hz; much of this chart is outside that range. | | See several frequencies and harmonics | [Spectrum Analyzer](https://soundforgepro.com/audio-spectrum-analyzer/) | A complex sound contains more than one spectral component. | | Hear a precise test frequency | [Tone Generator](https://soundforgepro.com/online-tone-generator/) | It generates 20 Hz–20 kHz after Play; chart notes below 20 Hz are outside its range. | A spectral peak isn't automatically the note you perceive. Musical sounds commonly include harmonics above the fundamental, and a strong harmonic can be taller than the fundamental in a spectrum. Use the table for known values, the detector for one live pitch and the analyzer when you need the full frequency picture. ## Musical note frequency FAQ ### What frequency is middle C? Middle C is C4 in scientific pitch notation. It is approximately 261.626 Hz in twelve-tone equal temperament when A4 is set to 440 Hz, and it is MIDI note 60. ### What musical note is 440 Hz? At the default A4 = 440 Hz reference, 440 Hz is A4 and MIDI note 69\. Changing the reference can change both the nearest note and its cents offset. At A4 = 442 Hz, 440 Hz is A4 about 7.85 cents flat; at A4 = 480 Hz, its nearest note is G4, about 49.36 cents sharp. ### How do I convert Hz to the nearest note? Enter the frequency in Hz → Note mode. The calculator finds its fractional position relative to A4, rounds to the nearest equal-tempered note and keeps the remaining distance as cents. A positive value is sharp of the displayed note; a negative value is flat. ### Are C-sharp and D-flat the same frequency? They are enharmonic equivalents in the 12-TET model used here, so C♯ and D♭ share a frequency and MIDI number. Other tuning systems can treat enharmonic spelling and pitch relationships differently. ### Why does my synth call middle C C3 instead of C4? Octave numbering is not universal across instruments and software. This chart uses scientific pitch notation, where middle C is C4\. Match the MIDI number or frequency when your device uses another octave-label convention. ### Online Pitch Detector: Note, Hz & Cents URL: https://soundforgepro.com/pitch-detector/ Last updated: 2026-10-09T20:59:43.000Z Press **Start microphone**, allow access and hold one clean note for about a second. The detector shows the nearest note, measured frequency and how many cents the pitch sits sharp or flat. Audio is analyzed inside this browser: the page does not record or upload it. This is a free live-input tool, not a file uploader or vocal-range test. Its search range is approximately 65–2,000 Hz; low bass E1 (41.2 Hz), A1 (55 Hz) and 50/60 Hz hum are outside it. A harmonic from an out-of-range source is not a valid reading of its fundamental. Browser pitch tool · local microphone ## Find the note you are playing Microphone access is requested only after Start; your browser may reuse an existing permission. Audio is analyzed on this device and is not recorded or uploaded. Detector status **Ready** Use one steady voice or instrument note. Chords and noisy rooms can confuse the reading. Start microphone Stop Detected note **–** Waiting for a stable note Frequency**– Hz** Tuning**– cents** Target**– Hz** −50 flat0+50 sharp Input level**– dBFS**0% Pitch confidence**–**0% **Reference pitch**Default A4 = 440 Hz+ A4 reference Hz Reset 440 Ready. Press Start microphone, allow access, then hold one note for about a second. ## How to use the pitch detector 1. **Choose a quiet position.** Move away from fans, loud speakers and other instruments. Reflections and background notes can make the fundamental less stable. 2. **Press Start microphone.** Your browser may ask for microphone permission unless you already granted it; input selection, when available, is in the browser or operating-system audio settings. On a phone, point the built-in microphone toward the source without covering it. 3. **Play one sustained note.** A voice vowel, guitar string, piano note or other clear monophonic source works better than speech, percussion or a chord. 4. **Read note, Hz and cents together.** The note name is the nearest equal-tempered pitch. Frequency is an estimate of the fundamental, not a guaranteed identification. A negative cents value is flat; a positive value is sharp. 5. **Stop when finished.** Stop or Escape releases this tool’s microphone tracks and clears the readings. Hiding the page or navigating away also cancels capture; a late permission grant is discarded. Press Start again to resume. If the reading jumps, don't chase every number. Hold the source steady, bring it closer without clipping the input, and give the confidence bar a moment to settle. The display uses a short rolling median, which reduces isolated outliers after several readings but also delays changes between notes. ## How to read note, frequency and cents | Readout | What it means | How to use it | | ------------- | ------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------ | | Note + octave | The nearest note in twelve-tone equal temperament, using C4 for middle C and sharp names (C♯ equals D♭ here) | Identify the pitch region, such as A4 or E2 | | Frequency | The estimated fundamental in cycles per second | Compare the measured Hz with the target | | Cents | The logarithmic distance from the nearest target note | Negative is flat, positive is sharp; zero is centered | | Input level | RMS level of the digital input frame in dBFS, not acoustic loudness or sound pressure | Move closer if too quiet; move back if the input distorts | | Confidence | How clearly the current frame supports one repeating pitch period | Treat low-confidence note names as provisional; the percentage is not a calibrated probability of the correct note | One semitone contains 100 cents, so a reading near +50 is halfway from the displayed note toward the next semitone. Cents are logarithmic: the same musical interval uses the same cents distance at low and high frequencies. The number is still an estimate; don't expect every phone microphone or noisy room to resolve the pitch to laboratory precision. For the note-to-frequency equations behind the display, see the [UNSW explanation of notes, MIDI numbers and cents](https://www.phys.unsw.edu.au/jw/notes.html). A4 uses MIDI 69, C4 uses MIDI 60, and cents = 1200 × log2(measured frequency / target frequency). The **In tune** label means within ±5 cents of this mathematical target, not a claim about hearing thresholds or professional piano tuning. ## When to change the A4 reference The default is A4 = 440 Hz. Leave it there for ordinary modern tuning checks. Open **Reference pitch** only when an ensemble, recording, historical practice or supplied brief uses another reference. Changing A4 changes the target-note map; it doesn't change the audio captured by the microphone. For example, at A4 = 440 Hz the A below middle C is A3 at 220 Hz, and the A immediately above middle C is A4 at 440 Hz. A5, one octave above A4, is 880 Hz. Every octave doubles or halves frequency. Other notes follow the equal-tempered ratio of the twelfth root of two. If you need to create a known reference rather than measure one, use the [online tone generator](https://soundforgepro.com/online-tone-generator/). Keep its output quiet. A second device can supply a reference tone, but turn it off before measuring an instrument so the detector does not follow the reference instead. For a static equal-tempered lookup across octaves, use the [musical note frequency chart](https://soundforgepro.com/musical-note-frequency-chart/). The A4 field accepts 415–466 Hz in 0.1 Hz steps. Invalid values clear the note display until corrected; Reset 440 restores the default. The browser is asked to disable echo cancellation, noise suppression and automatic gain control, but these are preferences, not guarantees about device processing. A rejected or quiet frame clears the previous note rather than showing it as a fresh measurement. ## Sources that work well and sources that do not - **Voice:** sustain one vowel at a comfortable level. Spoken sentences change pitch too quickly for a stable tuner-style reading. - **Guitar and bass:** use a note within 65–2,000 Hz, pluck one string and let the initial attack pass. Use the settled body of the note; overtones and fret noise can dominate the first instant. - **Piano and keyboards:** play one note. The sharp attack may jump briefly before the sustained tone settles. - **Wind and bowed instruments:** hold one steady note with consistent breath or bow pressure. - **Chords:** not supported as chord recognition. Several fundamentals and overtones compete, so the result may jump between partials. - **Drums, clicks and noise:** usually unsuitable. A transient or broadband signal does not provide one persistent fundamental period. The supported display range is deliberately limited to roughly 65–2,000 Hz. That covers common voice and instrument fundamentals while leaving enough samples for useful browser analysis. Frequencies outside the range may appear as silence, a harmonic or an unstable result. For a full view of energy across many simultaneous frequencies, use the [audio spectrum analyzer](https://soundforgepro.com/audio-spectrum-analyzer/); it answers a different question from this note detector. ## How the browser estimates pitch The page reads short microphone frames through the Web Audio API and applies a YIN-style fundamental-frequency estimate. The original [YIN pitch-estimation paper](https://pubmed.ncbi.nlm.nih.gov/12002874/) describes a difference function and cumulative mean normalization designed to reduce common autocorrelation errors. Here, a confidence threshold rejects weak or ambiguous frames, and a short median smooths accepted frequencies before note conversion. The detected frequency is converted to an equal-tempered MIDI-note position relative to the selected A4 reference. The nearest integer identifies the note; the remaining logarithmic distance becomes cents. The algorithm runs in page memory, and the microphone source is connected to an analyzer rather than the audio output, so the page shouldn't play your input back through the speakers. Browser microphone capture is available only in a secure context and requires explicit permission, as documented for [MediaDevices.getUserMedia()](https://developer.mozilla.org/en-US/docs/Web/API/MediaDevices/getUserMedia). Mobile browsers can also suspend Web Audio until a user action, so the page creates and resumes its audio context inside the Start action, consistent with [AudioContext.resume()](https://developer.mozilla.org/en-US/docs/Web/API/AudioContext/resume). ## Why the pitch reading jumps or stays blank - **Permission blocked:** allow microphone access for soundforgepro.com in the browser’s site settings, then press Start again. - **No signal:** stop this detector, then open the [online microphone test](https://soundforgepro.com/microphone-test/) to check the selected input and its level. If that meter moves but the pitch display stays blank, return here and hold one steady note within 65–2,000 Hz. A moving input meter confirms a signal; it does not guarantee a detectable fundamental. - **Signal too quiet:** reduce the source-to-microphone distance. Do not boost until the room noise becomes louder than the note. - **Reading jumps by an octave:** wait past the attack, play more softly or change microphone position. A strong harmonic can briefly look more periodic than the fundamental. - **Wrong note during a chord:** isolate one note. This page is a monophonic pitch detector, not a chord detector or key finder. - **Phone does nothing after Start:** reload the HTTPS page, make sure the browser has microphone permission and press Start again from the visible button. Private or embedded browsing modes can apply stricter permission rules. ## Where pitch detection fits an editing workflow Pitch detection is useful before a destructive edit: identify a sustained tone within the supported range or document a note before time/pitch processing. Use a spectrum analyzer for 50/60 Hz mains hum; those fundamentals are below this detector’s range. It won't repair the audio, though. For recorded material, inspect the spectrum as well, then make the change in your editor and measure again. If you're changing pitch or duration in Sound Forge, the [time-stretch and pitch-shift guide](https://soundforgepro.com/time-stretch-pitch-shift-sound-forge/) separates musical transposition from duration changes and explains where artifacts tend to appear. Use the tone generator for a fixed test signal and the spectrum analyzer for broadband peaks; this detector is for one live fundamental. ## Privacy and measurement limits - The detector requests microphone access only after you press Start. Stopping capture does not revoke a saved site permission or stop another tab that uses the same microphone. - The detector does not save a recording, upload audio or connect the microphone to speaker output. Ordinary site analytics are separate; detector events contain no audio, note or frequency values. - Stop, Escape, page hide and navigation release this tool’s tracks. A pending request is canceled logically: the browser prompt may remain, but any late stream is stopped rather than analyzed. - The reading depends on the source, room, microphone, sample rate and browser. - It is not a calibrated frequency counter, hearing test, vocal-range diagnosis or proof of instrument intonation. [Stopping a media track](https://developer.mozilla.org/en-US/docs/Web/API/MediaStreamTrack/stop) releases this tool’s use of the source; it does not necessarily switch off hardware shared with another app or tab. A browser-reported muted or ended microphone track stops this session. Use the [Audio Tools hub](https://soundforgepro.com/tag/audio-tools/) to choose a different measurement. ## Online pitch detector FAQ ### Does the pitch detector record or upload my voice? No. The live MediaStream is analyzed in the current browser tab. The page does not create a recording, send audio to a server or play the microphone signal through the output. ### What does a negative cents reading mean? A negative value means the measured pitch is flat relative to the nearest displayed target; a positive value means it is sharp. Zero is centered. One semitone equals 100 cents. ### Can it detect guitar, bass, piano and voice? It can estimate one clear, sustained note within roughly 65–2,000 Hz. Low bass E1 at 41.2 Hz and A1 at 55 Hz are outside the range; their overtones may produce misleading readings. Let sharp attacks settle and play one note at a time. ### Can this tool identify chords or a song key? No. It is a monophonic pitch detector. Chord recognition and key estimation require analysis of several simultaneous or time-varying pitches and are separate tasks. ### Why does the detector show the wrong octave? A strong overtone, noisy attack, very low note or weak fundamental can produce an octave error. Hold one note, wait past the attack and adjust microphone position. Even high confidence can describe the wrong octave; compare with the expected register before trusting it. ### Should I change A4 from 440 Hz? Keep 440 Hz unless the ensemble, recording or delivery brief uses another reference. Changing A4 remaps the target frequencies and cents values; it does not alter the captured sound. ### Online Headphone Test: L/R, Balance & Sweep URL: https://soundforgepro.com/headphone-test/ Last updated: 2026-10-08T22:43:14.000Z A useful headphone test should answer one question at a time: are the channels routed correctly, does the center stay centered, is there an obvious rattle, and does either side drop out during a controlled sweep? Start with your system volume low, then run the five short checks below. The signals are generated on this device; the page doesn't request a microphone or upload audio. Browser tool · no microphone ## Run a five-step headphone check Signals are generated on this device. The page doesn't record, upload, or listen to anything. !**Lower system volume before the first test.** Tool level starts at 5%, stops at 20%, and is not dB SPL. Never turn up a missing high or low tone sharply. 1Channels 2Center 3Bass 4Sweep 5Phase ### 1\. Confirm left, center, and right The highlighted output should match the ear that hears the tone. 500 Hz sine **L**Left ear **R**Right ear Expected**Choose a channel**Left should play only left; Right only right; Center should sit between both ears. LeftCenterRightStop Mark the step only after testing all three positions. Sounds rightNeeds checking ### 2\. Compare the center and each side Use both signals. A center that pulls sideways is a symptom; it isn't proof of a failed driver. Level comparison **Center check stopped** — Pink noise exposes broad tonal differences; the 500 Hz tone is easier for a simple level comparison. Pink center500 Hz centerL → RStop If the pull stays with one ear after reversing the headphones, this page can't diagnose it. Stop and compare another source. Sounds rightNeeds checking ### 3\. Listen for low-frequency rattle Start at 80 Hz and step down. Each preset stops after two seconds. Short sine tones **Bass preset** — Do not raise volume to force audibility. Recheck a buzz at a lower level and on a second device. 80 Hz60 Hz40 Hz30 Hz Stop Quiet or missing deep bass can reflect seal, fit, playback chain, hearing, or the headphones. No obvious rattleNeeds checking ### 4\. Run a controlled listening sweep The 40 Hz–12 kHz sweep is a comparison, not a hearing test or frequency-response measurement. 12 seconds **Sweep position** — Listen for a one-sided dropout, buzz, or sudden change. Stop immediately if any range is uncomfortable. Run sweep1 kHz4 kHz8 kHz 12 kHz · shortStop Do not chase a faint 8 or 12 kHz tone by raising the level. No obvious issueNeeds checking ### 5\. Compare in-phase and inverted The two states should feel different. This optional comparison isn't a standalone wiring diagnosis. 500 Hz · optional **In phase**Both channels receive the same waveform polarity. The image often feels more centered. **Right inverted**The right waveform is inverted. The image often feels diffuse or harder to center. In phaseRight invertedStop Channels**Not marked** Center**Not marked** Bass**Not marked** Sweep**Not marked** Phase**Optional** If several checks need attention, repeat at low level on another device before blaming the headphones. Difference is clearUnsure Previous Ready. Audio starts only after you press a test control. Next step Tool level 5% ## How to run the headphone test 1. **Confirm left, center, and right.** Put the headphones on in their marked orientation. Left should play only through the physical left side, Right only through the right, and Center through both. 2. **Compare the center image.** Try both [pink noise](https://soundforgepro.com/pink-noise-generator/) and the 500 Hz tone. The image should sit near the middle rather than leaning obviously to one side. 3. **Check low frequencies at a restrained level.** Start at 80 Hz and work down. Each preset is short. Listen for a buzz or rattle; do not turn up a quiet 30 or 40 Hz tone to force audibility. 4. **Run the controlled sweep.** The sweep moves from 40 Hz to 12 kHz over 12 seconds. Listen for a one-sided dropout, a repeatable rattle, or a sudden change between the earcups. 5. **Compare phase only if useful.** The in-phase signal often feels more centered than the right-inverted version. Treat this as an optional comparison, not proof of a wiring fault. Mark each step as you go. The summary stays in the current page only; it isn't saved or sent with analytics. Press **Stop** before changing headphones, adapters, cables, or output devices. Escape also stops playback. ## What your headphone-test result means | What you hear | Check next | What it does not prove | | -------------------------------------- | --------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------- | | Left and right are reversed | Confirm the earcup markings, cable orientation, adapter, interface routing, and app output | It does not immediately prove the headphones were wired incorrectly | | Both sides play during a one-side test | Turn off Mono audio in the operating system and check any app or interface downmix | It does not mean the stereo test itself is broken | | The center pulls left or right | Check system balance, fit or earbud seal, debris, cable seating, and a second source | It does not isolate the driver, your hearing, or the source by itself | | One side is silent | Reseat the plug, charge and re-pair wireless earbuds, compare another app, then test another device | A silent side alone cannot distinguish a driver fault from a connection, pairing, or source problem | | Bass buzzes or rattles | Stop, lower the level, reseat the headphones, and repeat on another device | It does not prove permanent damage; fit, hair, debris, enclosure parts, or the source can also rattle | | A sweep range becomes quiet | Repeat at low level, swap the headphones left-to-right, and compare another output | It is not a calibrated frequency-response or hearing measurement | ![Five headphone test symptoms mapped to routing, mono, balance, connector, and second-device checks](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/10/headphone-test-result-map-v1-v20261006.webp) Treat each result as a symptom. Change one variable at a time before blaming the headphones. If your only question is whether a channel is silent, reversed, or collapsed to mono, the dedicated [left/right channel test and routing checklist](https://soundforgepro.com/left-right-speaker-test/) goes deeper. If you need an arbitrary reference frequency rather than a guided headphone check, use the [20 Hz–20 kHz online tone generator](https://soundforgepro.com/online-tone-generator/). Use this guided check when you want to compare several symptoms in one place. ## Separate a headphone problem from a source problem Don't keep repeating the same test on the same setup. A second path tells you more than another ten clicks. Follow this order to change one variable at a time: 1. **Repeat at a lower level.** A rattle that disappears may have been caused by the playback level or something physically touching the earcup. 2. **Reseat the connection.** Push a wired plug fully home, remove a questionable adapter, or reconnect both wireless earbuds. 3. **Try another app or browser tab.** This separates a page or app route from the device-wide route. 4. **Try a second phone, computer, interface, or headphone output.** If the symptom follows the headphones, hardware or fit becomes more likely. If it stays with the source, inspect that source first. 5. **Reverse the headphones on your head for the center check.** If the quieter side moves with the earcup, investigate the headphone path. If it stays with the same ear, stop treating the web test as a hardware diagnosis. This process still doesn't replace measurement equipment or a hearing assessment. It simply keeps an operating-system setting, loose connector, pairing problem, or poor seal from being mistaken for a dead driver. ## Check mono and balance in Windows or macOS When Left or Right plays through both ears, check mono before changing hardware. Microsoft documents the current Windows 11 path as **Settings → Accessibility → Audio → Mono audio** in its guide to [making Windows easier to hear](https://support.microsoft.com/en-US/accessibility/windows/make-windows-easier-to-hear). Turn Mono audio off for a stereo channel test. Windows 10 uses the corresponding Ease of Access audio setting. If one side is quiet on Windows, select the active output under **Settings → System → Sound** and inspect its left/right levels when the device exposes them. Microsoft’s current [one-channel Bluetooth troubleshooting](https://support.microsoft.com/en-US/Windows/Hardware/Bluetooth/fix-bluetooth-audio-only-playing-in-one-channel) also covers balance, re-pairing both earbuds, charging, firmware, and a second-device comparison. Not every driver presents the same controls, so use the labels shown for your actual output. On a Mac, Apple lists the output-device **Balance** control under **System Settings → Sound → Output** in its [current sound-output guide](https://support.apple.com/en-euro/guide/mac-help/mchlp2256/mac). Apple also provides **Play stereo audio as mono** under Accessibility audio settings. Center the balance and turn mono off before interpreting a hard-panned channel test. ## Testing Bluetooth headphones, earbuds, and AirPods The tool works with a Bluetooth output selected by the browser and operating system. Channel orientation and broad level comparisons do not depend on low latency, so a small wireless delay is usually irrelevant here. Pairing state, however, matters: true-wireless earbuds can end up with only one side connected, and a calling or communication mode can change how the playback chain behaves. Charge both earbuds, return them to the case if the manufacturer’s pairing procedure requires it, reconnect the complete set, and confirm that normal stereo music plays before blaming the web test. If one side fails on only one computer or phone, inspect that source. If it fails on every source, the earbud or its charging/pairing state deserves closer attention. ## Why the sweep is not a frequency-response test A browser can set a digital oscillator frequency accurately, but this page has no measurement microphone, acoustic fixture, ear simulator, calibration file, or reference sound-pressure level. What reaches you also depends on the converter, amplifier, headphone driver, pad or ear-tip seal, fit, operating-system processing, and your own hearing. That makes the sweep useful for comparison rather than measurement. A repeatable buzz in one earcup is worth isolating, and a quiet patch can be worth comparing on another output, but neither result is a frequency-response graph. Failing to hear a 12 kHz preset also doesn't diagnose hearing loss or prove a tweeter or driver is broken. Never raise an extreme tone sharply to chase it. ## What the phase comparison can tell you The optional phase step sends the same 500 Hz waveform to both channels, then inverts the right channel for comparison. Many listeners hear the in-phase signal as more compact or centered and the inverted version as more diffuse. The difference can be less obvious with a loose earbud seal, unusual processing, spatial-audio features, or individual perception. If both versions sound identical, first disable spatial effects and repeat on a second source. Don't turn that one observation into a wiring verdict. Confirm suspected polarity problems with known equipment or an acoustic/electrical measurement path. ## How the browser test works and what it sends The tones use the Web Audio API’s [OscillatorNode](https://developer.mozilla.org/en-US/docs/Web/API/OscillatorNode), while the channel buttons use [StereoPannerNode](https://developer.mozilla.org/en-US/docs/Web/API/StereoPannerNode) to position the signal left, center, or right. The pink-noise buffer, sweep, gain, and phase comparison are built in the current page after you press a control. The component has no microphone request, upload control, file picker, or audio-network request. When site analytics is available, playback events can include the selected test mode, signal type or preset frequency; blocked-playback events can include an error category. The Sounds right/Needs checking answers you mark are not sent. Audio itself is not uploaded. Leaving or hiding the page stops playback. ## Keep headphone test tones short and quiet The tool-level control starts at 5% and stops at 20%, but that percentage isn't dB SPL. The physical output still depends on the phone, computer, interface, amplifier, and headphones. Lower the system volume before pressing the first test, keep checks short, and stop at discomfort. The [World Health Organization’s safe-listening guidance](https://www.who.int/news-room/questions-and-answers/item/deafness-and-hearing-loss-safe-listening) emphasizes both level and duration, recommends keeping personal-device volume below 60% of maximum, and advises breaks from loud sound. The practical rule for this page is stricter: begin low, do not chase missing extreme frequencies with more level, and stop immediately if a tone feels sharp or uncomfortable. ## Online headphone test FAQ ### Is this a hearing test? No. It has no calibrated headphone, sound-pressure reference, clinical protocol, or response recording. It can reveal a symptom worth checking, but it cannot measure hearing or provide a diagnosis. ### Can I test Bluetooth headphones or AirPods? Yes, if the browser is playing through that output. First confirm that both earbuds are connected and normal stereo audio works. Wireless delay does not stop a channel check, but pairing, mono, balance, communication mode, or spatial processing can affect what you hear. ### Why do both ears play during the Left or Right test? The system, app, interface, or accessibility settings may be combining stereo into mono. Turn off Mono audio, confirm the correct output, and repeat. Use the dedicated left/right guide if the route still collapses. ### Why is one side of my headphones quieter? Check balance, earbud seal or pad fit, debris, plug seating, wireless pairing, the current source, and a second device. If the symptom follows the same physical earcup across sources, the headphone path becomes more likely; one browser result alone is not enough to identify the cause. ### Can the sweep measure headphone frequency response? No. It is an uncalibrated listening comparison. Measuring frequency response requires a controlled acoustic measurement chain; this page cannot separate the headphones from fit, source, processing, room leakage, or the listener. ### Tempo-Synced Delay & Reverb: BPM Timing Guide URL: https://soundforgepro.com/bpm-delay-reverb-time-guide/ Last updated: 2026-10-09T21:08:32.000Z **Quick answer:** choose delay time by where the repeat should land. For a dry hit on a quarter-note beat, a quarter-note delay lands on the next beat and an eighth-note delay lands halfway between them. A dotted eighth lasts three-quarters of a quarter note; an eighth-note triplet lasts one-third. Set feedback, filtering, wet level, reverb pre-delay, and decay separately. If a synced effect masks the next note or creates an unwanted echo, change it. Already know the tempo? Use the [BPM to milliseconds calculator](https://soundforgepro.com/bpm-to-ms-calculator/) for the exact straight, dotted, or triplet value. If the tempo is unknown, measure it first with [Tap Tempo](https://soundforgepro.com/tap-tempo/). This guide begins after the arithmetic: it is about choosing and checking the result. At 120 quarter-note BPM, a quarter note is 500 ms, an eighth is 250 ms, a dotted eighth is 375 ms, and an eighth-note triplet is about 166.7 ms. These are placement options, not recommended reverb settings. Check the beat unit first: in [compound meter such as 6/8](https://www.dolmetsch.com/musictheory15.htm), you may tap dotted quarters. A dotted-quarter pulse of 80 means quarter-note BPM of 120, not 80\. Entering 80 in a quarter-note calculator would make every result 50% too long. ## Choose the delay by where the repeat lands A tempo-synced delay is a rhythmic layer. The dry performance supplies one pattern and the repeats add another, so auditioning the effect on a held note tells you less than playing the real phrase. Start with one exposed bar, then add the rhythm section and the next vocal or instrumental entrance. | Starting division | What to listen for | Reject it when | | ------------------- | ---------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------- | | Quarter note | Repeats reinforce the main beat and leave broad space between echoes. | The repeat competes with the next downbeat or makes the phrase feel slower. | | Eighth note | The echo fills the midpoint between quarter-note beats. | Fast material becomes a continuous wash instead of a readable pattern. | | Dotted eighth | The repeat lands three sixteenth-note steps after the source, creating syncopation against straight playing. | The played rhythm already occupies that gap or the repeats disguise the intended accent. | | Eighth-note triplet | The first echo arrives one-third of a quarter note after the source; three such intervals fill one quarter note. | The song is straight and the triplet pull sounds like a timing error rather than deliberate tension. | Apple describes [Delay Designer as a rhythmic multitap effect](https://support.apple.com/en-ie/guide/logicpro/lgcef18b8dc5/mac) with synchronization and quantization, while [Ableton's current Delay](https://www.ableton.com/en/manual/live-audio-effect-reference/) can switch between beat divisions and millisecond Time mode. Those controls place the repeat; they don't decide whether it belongs in the arrangement. ![First delay repeats at 120 quarter-note BPM: 500, 250, 375 and 166.7 milliseconds](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/09/delay-timing-20260913.webp) At 120 quarter-note BPM, compare when the first repeat arrives: quarter 500 ms, eighth 250 ms, dotted eighth 375 ms, and eighth-note triplet about 166.7 ms. These numbers place the echo; they do not set feedback or reverb decay. ## Hear straight, dotted, and triplet as different grids A dot adds half the original note value: a dotted eighth is an eighth plus a sixteenth. The [Soundbrenner dotted-note lesson](https://www.soundbrenner.com/blogs/articles/dotted-notes) illustrates this rule. An eighth-note triplet instead fits three equal notes into one quarter note, as the [Dolmetsch grouping lesson](https://www.dolmetsch.com/musictheory15.htm) explains. These are different timings, not interchangeable labels for an offbeat echo. For dotted-eighth guitar delay, play the intended picking pattern while adjusting the repeat. The effect is the composite rhythm made by the pick attack and echo, not a magic setting produced by the delay alone. The practical lesson in [GuitarPlayer's delay-pedal guide](https://www.guitarplayer.com/lessons/how-to-get-the-most-out-of-your-delay-pedal) is useful here: delay time follows both tempo and the rhythmic value you want to generate. If the plugin already has a reliable Sync mode, use it when the project changes tempo. Enter milliseconds when the device has no sync, when a fixed time is intentional, or when you need an offset that the note menu cannot express. Ableton's current manual also exposes fractional offsets around the synced division, which is a reminder that strict grid placement and musical feel are not always identical. ## Set feedback, filtering, and wet level after delay time Delay time answers *when the first repeat arrives*. Feedback answers how much delayed output returns to the input, so it controls the continuation and density of the echo pattern. Wet level sets how prominent that pattern is, and filtering decides which parts of each repeat survive. One correct BPM value can't set those three controls for you. Begin with one or two clearly audible repeats. Add feedback only until the last useful echo survives, then lower the wet level in the full arrangement. Check the effect in mono and through a small speaker: a wide, filtered repeat can feel unobtrusive in headphones while masking the center of the mix elsewhere. If the delay starts to oscillate or build unexpectedly, mute the effect output and reduce feedback before continuing; stopping the source alone may leave a feedback loop running. ## Treat reverb pre-delay as a gap, not reverb length Apple defines [Space Designer pre-delay](https://support.apple.com/guide/logicpro/use-global-controls-lgcee0be400c/mac) as the time between the original signal and the first early reflections. That gap can help the source attack remain identifiable, but longer is not automatically clearer. Apple's current guidance says the suitable value depends on the envelope of the source; too much can become an audible echo or separate the source unnaturally from its reflections. Ableton's Hybrid Reverb supports both time-based and beat-synced pre-delay. Its manual cites 1–25 ms as typical for natural sounds in that product context. A strict note division may be much longer than that, especially at a slow tempo. Use the calculator to obtain the number, then compare it with a shorter unsynced setting. Keep the synced option only if the gap supports the groove without announcing itself as a separate repeat. Compare two settings on the same phrase, keeping the reverb level unchanged. First try a short unsynced gap; then try the note value you calculated. Listen to the consonant or pick attack and the space before the next note. Choose the clearer result unless a distinct echo is the effect you want. ## Do not turn reverb decay into a fake formula Pre-delay and decay are different controls: pre-delay postpones the onset of the early reflections, while decay describes how the reverberant energy falls away. Plugin labels and algorithms vary, and convolution reverbs inherit the behavior of their impulse responses. A bar-length number can be an audition point, but it isn't proof that the audible tail ends cleanly on that boundary. For example, Ableton Reverb defines Decay as the time for the level to fall by 60 dB, not the instant when the sound is cut off. Set decay while listening to the next phrase rather than only the tail in solo. Shorten it when consonants, snare hits, bass movement, or a scene cut lose definition; lengthen it only when the arrangement has room for the tail and the transition benefits from the added sustain. If the reverb is on a send, check the send level before changing decay. A tail can feel too long simply because too much signal is feeding it. For the actual desktop steps, use the [Sound Forge reverb workflow](https://soundforgepro.com/how-to-add-reverb-in-sound-forge-pro/). It covers selection boundaries, tail handling, preview, rendering, and verification: the parts a BPM formula can't answer. ## A repeatable seven-step timing check 1. **Confirm the pulse.** Confirm which note value the tempo represents. The calculator expects quarter-note BPM; in 6/8, a dotted-quarter pulse of 80 corresponds to quarter-note BPM of 120. 2. **Choose the intended placement.** Decide whether the first repeat should reinforce the beat, fill a midpoint, or create dotted or triplet syncopation. 3. **Set sync or enter milliseconds.** Use plugin sync when it follows the project correctly; otherwise copy the exact value from the BPM-to-milliseconds calculator. 4. **Reduce the pattern.** Start with low feedback and a modest wet level so the first repeat can be judged. 5. **Play the real phrase.** Include the rhythm section and the next entrance; do not approve the effect from a held note in solo. 6. **Set reverb separately.** Compare synced and shorter unsynced pre-delay, then adjust decay against the next phrase. 7. **Bypass and verify.** Match apparent level, check mono and a small speaker, and keep the effect only when the groove is clearer or intentionally transformed. ## Four mistakes that make synced effects sound wrong - **Choosing by the label alone.** “Dotted eighth” describes timing, not suitability for every guitar, vocal, or synth part. - **Using feedback to repair the wrong time.** More repeats cannot make a badly placed first repeat fit the phrase. - **Equating pre-delay with decay.** Moving the start of the reflections does not set how long the reverberant tail lasts. - **Approving in solo.** A beautiful isolated tail can erase the next lyric or drum accent in context. ## Tempo-synced delay and reverb FAQ ### Should delay always be synced to BPM? No. Sync is useful when the repeat should follow the song grid or tempo automation. Milliseconds are appropriate for fixed slapback, intentional offsets, unsynced hardware, and effects that should not move with tempo. ### What is the difference between dotted-eighth and triplet delay? A dotted eighth lasts three sixteenth-note steps, or three-quarters of a quarter-note beat. An eighth-note triplet divides one quarter-note beat into three equal parts. They place repeats on different grids. ### Does more feedback change the delay time? No. Delay time places the first repeat. Feedback sends some delayed output back into the delay input, changing how many repeats continue and how dense or unstable the pattern becomes. ### Should reverb pre-delay match the song BPM? It can be a useful audition point, but it is not compulsory. Compare the synced value with a shorter unsynced gap and keep the setting that preserves the source attack without producing an unwanted echo. ### Is reverb decay the same as pre-delay? No. Pre-delay is the gap before early reflections begin. Decay describes how the reverb tail falls away after it starts. Set and verify them separately. ### BPM to MS Calculator: Delay & Note Times URL: https://soundforgepro.com/bpm-to-ms-calculator/ Last updated: 2026-10-05T06:35:40.000Z Browser calculator · no upload ## Convert BPM to note times Know the tempo? Enter it below. If not, find it first with [Tap Tempo](https://soundforgepro.com/tap-tempo/). Quarter-note tempo BPM 6080100120128140174 Quarter note**500.0 ms**60,000 ÷ BPM One 4/4 bar**2.000 s**four quarter-note beats Quarter rate**2.000 Hz**1,000 ÷ milliseconds Click any value to copy Copy table | Note | Straight | Dotted | Triplet | | ----------- | -------- | -------- | -------- | | 1/4 quarter | 500.0 ms | 750.0 ms | 333.3 ms | | 1/8 eighth | 250.0 ms | 375.0 ms | 166.7 ms | | 1/16 | 125.0 ms | 187.5 ms | 83.33 ms | More divisions: whole, half, 1/32, 1/64 | 1/1 whole | 2000.0 ms | 3000.0 ms | 1333.3 ms | | --------- | --------- | --------- | --------- | | 1/2 half | 1000.0 ms | 1500.0 ms | 666.7 ms | | 1/32 | 62.50 ms | 93.75 ms | 41.67 ms | | 1/64 | 31.25 ms | 46.88 ms | 20.83 ms | Reverse: milliseconds to BPM Delay time ms Note1/1 whole1/2 half1/4 quarter1/8 eighth1/161/321/64 FeelStraightDottedTriplet Tempo**120.0 BPM** Showing exact timing from a 120 BPM quarter-note pulse. Each value is calculated from BPM; displayed and copied values are rounded. Quick answer: use this calculator when you already know the quarter-note BPM and need the matching time in milliseconds. Divide 60,000 by BPM for one quarter note. At 120 BPM, that is 500 ms; an eighth note is 250 ms, a dotted eighth is 375 ms, and an eighth-note triplet is about 166.67 ms. ## How to use the BPM to milliseconds calculator 1. **Enter the quarter-note tempo.** Type the BPM from the session, score, device, or pedal. The table updates without reloading the page. 2. **Choose the rhythmic column.** Straight values stay on the regular binary grid; dotted values last one and a half times as long; triplet values fit three notes into the time normally occupied by two. 3. **Copy the exact row you need.** Use milliseconds for an unsynced delay, reverb pre-delay, modulation period, gate, or another time control that accepts ms. 4. **Check the result in context.** Mathematical synchronization puts a repeat on the grid. It does not decide whether that repeat is too dense, too loud, or masking the next phrase. If the song tempo is unknown, measure it first with our [Tap Tempo BPM counter](https://soundforgepro.com/tap-tempo/). Tap along with the track, then enter the resulting BPM here to calculate delay times. ## The BPM to ms formula A minute contains 60,000 milliseconds. When the BPM number represents quarter-note beats, the duration of one quarter note is: `quarter-note milliseconds = 60,000 ÷ BPM` At 120 BPM, `60,000 ÷ 120 = 500 ms`. Halve that duration for an eighth note and halve it again for a sixteenth. Apple's [Logic Pro Delay Designer documentation](https://support.apple.com/en-ca/guide/logicpro/lgcef18b94fb/mac) gives the same practical checkpoints: at 120 BPM, an eighth-note grid is 250 ms and a sixteenth-note grid is 125 ms. ![120 BPM converted to quarter, eighth, dotted eighth, and triplet eighth milliseconds](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/08/bpm-to-ms-timing-map-v1.webp) At 120 BPM, one quarter note is 500 ms; the eighth-note, dotted-eighth, and triplet-eighth values follow from that pulse. The calculator derives every duration from the entered BPM, without chaining rounded results. Copied values use the same rounding as the display: for example, the eighth-note triplet at 120 BPM copies as 166.7 ms. That is a practical setting, not an exact representation of the repeating decimal. ## Straight, dotted, and triplet delay times Each straight note lasts half as long as the previous division: whole, half, quarter, eighth, sixteenth, thirty-second, and sixty-fourth. Starting from a 500 ms quarter note, the straight eighth is 250 ms and the straight sixteenth is 125 ms. A dot adds half of the original note's duration, as the [Soundbrenner dotted-note explanation](https://www.soundbrenner.com/blogs/articles/dotted-notes) explains. Therefore a dotted eighth at 120 BPM is `250 × 1.5 = 375 ms`. A triplet uses three notes in the time normally occupied by two; the [Dolmetsch note-grouping lesson](https://www.dolmetsch.com/musictheory15.htm) describes that three-in-the-time-of-two relationship. The calculator multiplies the straight note by exactly two-thirds. Dotted and triplet aren't quality presets; they're different rhythmic placements. Copy the number, listen against the performance, and change the division when the repeats fight the groove or crowd the next transient. ### BPM to ms chart for common tempos If you only need the numbers for a common tempo, this chart lists the same values the calculator shows at those BPMs. Every row assumes quarter-note BPM, and the rounding matches the display: one decimal at 100 ms and above, two decimals below that. For any other tempo, type the exact BPM into the calculator at the top of the page. __Note lengths in milliseconds at common quarter-note tempos__ | Quarter-note BPM | 1/4 note | 1/8 note | Dotted 1/8 | 1/8 triplet | 1/16 note | | ---------------- | -------- | -------- | ---------- | ----------- | --------- | | 60 | 1000.0 | 500.0 | 750.0 | 333.3 | 250.0 | | 70 | 857.1 | 428.6 | 642.9 | 285.7 | 214.3 | | 80 | 750.0 | 375.0 | 562.5 | 250.0 | 187.5 | | 90 | 666.7 | 333.3 | 500.0 | 222.2 | 166.7 | | 100 | 600.0 | 300.0 | 450.0 | 200.0 | 150.0 | | 110 | 545.5 | 272.7 | 409.1 | 181.8 | 136.4 | | 120 | 500.0 | 250.0 | 375.0 | 166.7 | 125.0 | | 128 | 468.8 | 234.4 | 351.6 | 156.3 | 117.2 | | 140 | 428.6 | 214.3 | 321.4 | 142.9 | 107.1 | | 150 | 400.0 | 200.0 | 300.0 | 133.3 | 100.0 | | 160 | 375.0 | 187.5 | 281.3 | 125.0 | 93.75 | | 174 | 344.8 | 172.4 | 258.6 | 114.9 | 86.21 | ## Convert milliseconds back to BPM Open the reverse panel when a pedal, preset, or old project gives you a delay time but not its tempo. Select the note division and feel that the number represents; without those two pieces, one millisecond value can map to several valid tempos. The note multiplier is measured in quarter notes: whole = 4, half = 2, quarter = 1, eighth = 0.5, sixteenth = 0.25, 1/32 = 0.125, and 1/64 = 0.0625\. The feel multiplier is 1 for straight, 1.5 for dotted, or 2/3 for triplet. Do not use 1/8 as the multiplier for an eighth note. The inverse formula is: `BPM = 60,000 × note multiplier × feel multiplier ÷ milliseconds` For example, 375 ms is 160 BPM if treated as a straight quarter note, but it is 120 BPM when treated as a dotted eighth. The reverse control asks for both labels instead of guessing. ## Where the timing values are useful Use the millisecond table when a delay pedal, hardware unit, or plugin is running in free-time mode rather than synchronizing directly to the project. Apple documents both approaches: [Logic's MIDI Note Repeater](https://support.apple.com/en-gb/guide/logicpro/lgce9c809354/mac) can use milliseconds when sync is off and bar/beat values when sync is on. If a plugin already follows tempo automation correctly, its sync mode is usually safer for a song that changes tempo. The same period can be expressed as a rate in hertz with `1,000 ÷ milliseconds`. A 500 ms period repeats twice per second, so it's 2 Hz. That's useful when an LFO, tremolo, auto-pan, or filter exposes Hz instead of note values. The rate is calculated from the unrounded time. This calculator gives you the timing math. The [BPM delay and reverb time guide](https://soundforgepro.com/bpm-delay-reverb-time-guide/) explains how to choose among the valid note values when repeats, pre-delay, or decay must fit an arrangement. A note-related setting can be a repeatable starting point, but it is not automatically right: shorten the time or reduce the wet level when consonants, drums, or the next phrase lose definition. For the actual desktop workflow, use the [Sound Forge reverb guide](https://soundforgepro.com/how-to-add-reverb-in-sound-forge-pro/); it covers selection, preview, tails, and verification. ## Quarter-note BPM, meter, and rounding limits The entered BPM must count quarter notes. In 6/8, a tempo marking of dotted quarter = 80 means 120 quarter notes per minute, so enter 120 here. The quarter-note result is 500 ms and the dotted-quarter pulse is 750 ms. The bar readout still describes four quarter notes in 4/4; it is not the length of a 6/8 bar. Don't treat the rounded display as proof of sample-accurate placement. A device may quantize delay time, a plugin may smooth parameter changes, and a performance can drift around the grid. If the job is changing the audio itself to a new duration or BPM, use the [time-stretch and pitch-shift workflow](https://soundforgepro.com/time-stretch-pitch-shift-sound-forge/) and verify the rendered file rather than assuming one delay-time number changes the recording. ## BPM to milliseconds FAQ ### What is the formula for BPM to milliseconds? For quarter-note BPM, divide 60,000 by BPM to get one quarter note in milliseconds. Multiply by 0.5 for an eighth note or 0.25 for a sixteenth. Then multiply by 1.5 for dotted timing or 2/3 for triplet timing. ### How many milliseconds is 120 BPM? At 120 quarter-note BPM, one quarter note is 500 ms, an eighth note is 250 ms, a sixteenth is 125 ms, and one 4/4 bar is 2,000 ms. ### What is a dotted eighth delay at 120 BPM? A straight eighth at 120 BPM is 250 ms. A dot adds half of that value, so the dotted eighth is 375 ms. ### How do I convert milliseconds back to BPM? Select the note division and feel represented by the delay time. Calculate 60,000 × note multiplier × feel multiplier ÷ milliseconds, using 0.5 for an eighth note and 1.5 for dotted timing. Thus 375 ms as a dotted eighth gives 60,000 × 0.5 × 1.5 ÷ 375 = 120 BPM. ### Is BPM to ms the same as tap tempo? No. Tap tempo estimates BPM from the timing of your presses. BPM to ms starts with a known BPM and converts it into note durations for delay, reverb, modulation, or other timed controls. ### Tap Tempo: Free Online BPM Counter URL: https://soundforgepro.com/tap-tempo/ Last updated: 2026-10-10T13:48:15.000Z Browser tool · no listening ## Tap the beat, read the BPM This page times your button or key presses on this device. It doesn't use a microphone, read a file or upload any audio. **TAP**Click here or press Space / T on each beat Estimated tempo **\-**BPM Two taps give the first estimate. Tap stability**Building** Recent taps**0** Tap interval**\- ms** Rounded**\- BPM** Half-time ÷2 Measured Double-time ×2 ResetPlay clickCopy BPM Ready. Tap once per beat and keep the page focused. Stability describes your recent tap intervals. It can't confirm the song's true tempo. Use this tap tempo counter to find a song’s BPM in your browser. Play the track and tap the large pad on each beat, or press Space or T. Two taps give the first estimate; keep tapping for several beats and watch whether the number settles. This free BPM counter, sometimes called a BPM tapper, measures the timing of your input. It never listens to the recording. ## How to get a stable tap-tempo reading 1. **Choose a pulse.** Tap the beat you would count or nod to, not every drum hit. Keep the same counting level throughout the sequence. 2. **Tap and release consistently.** Click or touch the TAP pad, or press Space/T. Keyboard taps register on keydown, and mouse, pen and touch taps register the moment you press, so hold length doesn't shift the timing. Release before the next beat. 3. **Build a short sequence.** Try four to eight steady taps as a starting point, not an accuracy guarantee. The first tap starts the sequence; the second creates one interval. 4. **Check the result and stability.** Steady describes similarity among retained intervals. It cannot tell whether you followed the right beat or tapped consistently early. Press Play click to hear a quiet click at the displayed tempo over the song. It starts when you press it, so listen for drift rather than downbeat alignment; tapping again stops it. 5. **Choose the counting interpretation.** Half-time divides the estimate by two; Double-time multiplies it by two. Measured returns to the original tap rate. None of these controls changes the music. 6. **Copy or start again.** Copy BPM copies the displayed one-decimal value and “BPM”. Record the beat unit separately. Use Reset before a new song or a deliberate tempo change. Space and T work while the page is active and focus sits on the TAP pad or ordinary page content. They leave links, other buttons, form fields and editable text alone. Release the key between beats, because held-key repeats are ignored. Modified shortcuts such as Ctrl+T and Command+T still go to the browser. ![Eight tap pulses converted into intervals and a stable 128 BPM estimate](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/10/tap-tempo-intervals-v1-v20261006.webp) The first tap starts the clock; later taps create intervals that the page can average into a BPM estimate. ## Why the same beat can look half or double A passage counted at 75 pulses per minute can also be counted at 150 if you tap twice as often, and neither number is automatically the right project tempo. Match the beat unit in your score, DAW or reference track, then stick with it. A syncopated kick or snare pattern may skip beats, so following every audible hit isn't always the same as following the pulse. If you tap every other quarter-note beat and read 60 BPM, Double-time gives 120 quarter-note BPM. If you tap eighth notes at 240 BPM, Half-time gives 120 quarter-note BPM. These are counting conversions; playback speed doesn't change. A genre's usual BPM range can't tell you which reading is right. ## How this BPM counter calculates the estimate The counter takes a [performance.now() timestamp](https://developer.mozilla.org/en-US/docs/Web/API/Performance/now) when an input handler runs. This clock reports milliseconds and only moves forward, so ordinary system-clock changes can't reverse the intervals. Browser timer precision, event processing, device latency and your own tapping still affect the measurement. One decimal place is display resolution. It doesn't promise 0.1 BPM accuracy. The formula is **BPM = 60,000 ÷ average retained interval in milliseconds**. Two timestamps 500 ms apart give 120 BPM. Intervals of 480, 500 and 520 ms average 500 ms, which also gives 120 BPM. The tool averages the intervals first; it doesn't average their individual BPM values. Only the latest nine taps, which make up to eight intervals, stay in the calculation, so the Taps readout stops at nine instead of counting forever. Once three intervals exist, the tool finds their median and keeps intervals from 65% through 155% of it, endpoints included. Filtering only kicks in if at least two intervals remain; otherwise the whole window is used. A message tells you how many intervals were left out. This filter can discard more than one interval, and it may mistake a real tempo change for a timing miss. It won't repair every accidental double tap either. Press Reset instead of trying to push a new tempo through an old window. With fewer than three retained intervals, stability reads Building. After that it's Steady when the mean absolute interval deviation is at most 2.5% of the mean, Close through 6%, and Uneven above 6%. Those are this tool's thresholds; they aren't measured confidence limits for a song's tempo. Interval shows the retained average rounded to a whole millisecond. Half-time and Double-time change the BPM reading but leave this measured interval as it is. Rounded shows the selected BPM rounded to an integer; it doesn't guess a “standard” tempo. The main result and Copy BPM only appear when the selected, unrounded BPM falls between 20 and 400 inclusive. ## Reset, copy and browser timing A pause doesn't wipe the displayed result straight away. On the next tap, the sequence starts over if the gap is longer than the larger of 3,000 ms or 2.5 times the median interval in the current window. Before any interval exists, the threshold is 3,000 ms. The comparison is strict, so a gap exactly at the threshold stays in the sequence. A pulse slower than 20 taps per minute can't build a first sequence, because its first interval is longer than three seconds. Manual Reset clears the taps and puts you back in Measured mode. Automatic pause resets keep the selected half/double reading. When the document becomes hidden, an active sequence is cleared and Measured mode comes back. Switching to another tab can therefore clear a result, while simply moving focus to another visible window doesn't count as hiding the document. The pad listens for the browser's [pointerdown event](https://developer.mozilla.org/en-US/docs/Web/API/Element/pointerdown%5Fevent), which fires when a mouse button goes down or a finger or pen makes contact with the screen, so how long you hold each press doesn't change the intervals. Space and T count on keydown in the same way. The screen, keyboard and browser still add their own input delay, so stick to one input method; these controls aren't a calibrated timing test. [Clipboard writing](https://developer.mozilla.org/en-US/docs/Web/API/Clipboard/writeText) needs a secure context and can be blocked by browser policy or permissions. If Copy BPM fails, select the number and copy it by hand. Copying 120.0 BPM gives you only the number, with no beat unit, interval, time signature or audio file attached. ## What tap tempo can and cannot tell you The result is most useful for a passage with a pulse you can repeat. A single rolling average can't describe every part of a performance that speeds up, slows down or moves in free time. Reset at the new section and take another reading. If the Play click, a separate metronome or a project click drifts against the music, question both your estimate and whether the performance really changes tempo. A steady display proves neither. Ableton's [Tap Tempo instructions](https://www.ableton.com/en/manual/audio-clips-tempo-and-warping/) also start with one tap per beat. Our counter doesn't control Ableton, start a DAW transport, send MIDI clock or play a metronome. It gives you a number to check and enter somewhere else. This tool never asks for a microphone, audio file or recording, and its timing calculation runs in the page. That doesn't mean the website as a whole sends no data: the tool can fire generic started/copied analytics events when site analytics is available. Those events carry neither the BPM nor the tap timestamps. ## Beat units and your next step BPM means beats per minute, but a beat isn't always a quarter note. In [compound duple 6/8](https://viva.pressbooks.pub/openmusictheory/chapter/compound-meters-and-time-signatures/), the usual dotted-quarter beat holds three eighth notes, with two of those beats per bar. Six eighth-note divisions don't necessarily mean six main beats. The [BPM-to-milliseconds calculator](https://soundforgepro.com/bpm-to-ms-calculator/) expects quarter-note BPM. If you tap dotted-quarter beats at 80 BPM, multiply by 1.5 and enter 120 there. The dotted-quarter interval stays at 750 ms, while each quarter lasts 500 ms. Half-time and Double-time can't do that 1.5 conversion for you. If you tap all six eighth notes per bar at 240 BPM instead, halve it to 120 quarter-note BPM. Keep the note value next to the copied number. A time signature on its own doesn't set the tempo. MuseScore's [tempo documentation](https://musescore.org/en/handbook/4/tempo) separates written metronome marks from its quarter-note-based playback BPM. Check what the destination field expects before you enter a tap result. If your next job is changing a recording's duration rather than finding its beat rate, use the [time-stretch and pitch-shift guide](https://soundforgepro.com/time-stretch-pitch-shift-sound-forge/). For other browser measurements, return to [Audio Tools](https://soundforgepro.com/tag/audio-tools/). Manual tempo detection stays here; note-duration conversion stays in the calculator. ## Tap tempo FAQ ### How does tap tempo calculate BPM? It divides 60,000 by the average retained interval in milliseconds. An average of 500 ms gives 120 BPM. The rolling window holds up to nine taps and eight intervals; it measures your input, not the song directly. ### How many times should I tap? Two taps provide the first interval. Try four to eight steady taps as a starting point, but no tap count guarantees accuracy. Keep the same beat unit, and reset if you lose the pulse or change sections. ### Why is the result half or double the BPM I expected? You may be counting a slower pulse or a faster subdivision. Half-time divides the estimate by two and Double-time multiplies it by two. Confirm the beat unit against your score or project; the controls do not analyze or change the audio. ### Does the page listen to or upload my song? No. This tool does not request a microphone or audio file. It calculates tap intervals in the page. Play click only generates a short sound in your browser; it records nothing. Generic started/copied analytics events may still be sent when site analytics is available, without BPM values or tap timestamps. ### Why did the tap sequence reset? Reset clears it manually. After a sufficiently long pause, the next tap starts a new sequence. The pause threshold is the larger of three seconds or 2.5 times the existing median interval. Hiding the document also clears an active sequence. ### Does one decimal mean 0.1 BPM accuracy? No. It is the output's display resolution. Your tapping, input latency and browser processing can all affect the estimate. Steady describes retained interval consistency, not certified tempo accuracy. ### Can I use this in 6/8? Yes. Choose the beat unit you intend to count. Tapping dotted-quarter beats at 80 BPM corresponds to 120 quarter-note BPM or 240 eighth-note BPM. The counter cannot infer that note value or the time signature from your taps. ### Online Tone Generator: Play Sine, Square & Sweep Tones URL: https://soundforgepro.com/online-tone-generator/ Last updated: 2026-10-09T00:56:02.000Z Set a frequency, keep the level low, choose a waveform and press Play tone. Sine is the shape for one clear reference frequency; the other shapes are there when you deliberately want harmonics. For broadband checking rather than one-frequency isolation, the [pink noise generator](https://soundforgepro.com/pink-noise-generator/) is the better fit. The signal is generated in this browser and stops when the tab is hidden. Browser tool · no upload ## Generate a test tone The oscillator runs on this device. The page does not request a microphone, read a file or upload audio. !**Lower system volume before Play.** Tool level starts at 5%, caps at 25%, and is not dB SPL. Stop if uncomfortable. Current frequency **440**Hz A4 · 0 centsSine wave Playback**Stopped** Choose a frequency and press Play tone. Play tone Stop Copy settings Waveform SineSquare TriangleSawtooth Tool level 5% Frequency & presetsExact tuning from 20 Hz to 20 kHz Exact frequency Hz 20 Hz200 Hz2 kHz20 kHz 50 Hz60 Hz100 Hz A4 · 4401 kHz5 kHz Frequency sweepSet start, end and duration Start Hz End Hz Seconds Run sweep Ready. Press Play tone or Run sweep to start; Space also toggles a tone outside controls. Digital reference only: not calibrated output, a hearing test or a response measurement. Press Escape to stop. ## How to generate an exact tone 1. **Turn down the physical output first.** Lower the computer, phone, interface, amplifier or headphone level before starting. The tool-level percentage cannot tell you the sound pressure reaching your ears. 2. **Enter the frequency in hertz. Enter 20 to 20,000 Hz, using up to two decimal places. You can also drag the logarithmic slider or choose a preset. If you are starting from a note name, use the** [**note frequency chart**](https://soundforgepro.com/musical-note-frequency-chart/) **to look up its hertz value.** 3. **Start with Sine.** It isolates the chosen fundamental without the strong harmonics produced by square and sawtooth waves. 4. **Press Play tone.** Adjust the tool level only as far as needed for a short check. Press Stop before changing cables, outputs or headphones. 5. **Use Sweep only for a controlled scan.** Set the start, end and duration. The sweep stops automatically at the end. Space toggles continuous playback when focus is outside a control; Escape stops immediately. The tool also stops when the page is hidden, so a high tone shouldn’t keep sounding unnoticed in another tab. If you need to identify a live note from a microphone rather than generate a reference tone, use the [Pitch Detector](https://soundforgepro.com/pitch-detector/). ## Pressed Play but hear no sound? Press Stop first and keep system volume low. Select Sine at 440 Hz for the retry; do not troubleshoot with an extreme frequency. Confirm the intended media output, check mute and any Bluetooth device that may have taken the sound, then return to this tab and tap Play tone explicitly. A hidden tab is intentionally stopped. If the status says Blocked, the browser did not start its audio context. A direct tap can retry activation; the page cannot override browser policy or select every system output. If the status says Playing but stays silent, compare ordinary audio in another app, then try this page in another browser. Report the phone model, OS and browser versions if only this tool fails. A Playing label is not proof that sound reached the speaker. ## What the tone-generator settings change | Control | What it changes | Useful starting point | | ---------- | ----------------------------------------------------------------- | ------------------------------------------------------------------ | | Frequency | Oscillator cycles per second, shown in hertz | 440 Hz for an A4 reference; 1 kHz for a clear midrange test signal | | Waveform | The shape of each cycle and therefore its harmonic content | Sine for one target frequency | | Tool level | Digital gain before the browser output | 5%, then only as high as needed | | Sweep | Moves exponentially from the start frequency to the end frequency | Short, low-level scans over the band you actually need | The readout also gives the nearest note in twelve-tone equal temperament relative to A4 = 440 Hz. That’s a convenience for tuning and pitch comparison; it doesn’t claim that every instrument, ensemble or historical tuning uses 440 Hz. ![Sine, square, triangle and sawtooth waveforms stacked at the same frequency, about four cycles each](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/08/tone-waveforms-comparison-v1.webp) From top: sine, square, triangle and sawtooth. The same fundamental can drive very different harmonic content. ## Sine, square, triangle or sawtooth? **Sine** is the right default for locating one frequency. **Square** adds strong odd harmonics and sounds hollow or buzzy, while **Triangle** carries odd harmonics too, though they fall away faster, so it comes across softer than square. **Sawtooth** contains a dense harmonic series and usually sounds brightest. Penn State’s [Fourier synthesis demonstration](https://www.acs.psu.edu/drussell/Demos/Fourier/Fourier.html) shows the difference: sawtooth uses all integer harmonics, while square and triangle use only odd ones. Those extra harmonics matter. A 100 Hz square wave isn’t only a 100 Hz test: the playback chain also receives energy at higher multiples. If you’re tracing a single hum frequency, comparing a crossover region or checking where a rattle begins, start with sine and change shape only when those extra frequencies are part of the test. Those are ideal harmonic series. The [Web Audio oscillator specification](https://www.w3.org/TR/webaudio-1.0/#OscillatorNode) requires filtering above half the context sample rate to limit aliasing. At high fundamentals, fewer harmonics remain, so the browser’s output does not retain every harmonic of an ideal square or sawtooth. ## Practical frequencies and what they can tell you - **50 or 60 Hz:** compare a suspected mains-related hum with the local electrical frequency. A real recording can also contain 100 or 120 Hz and higher harmonics, so a match is a clue rather than a full diagnosis. Our [50/60 Hz hum repair guide](https://soundforgepro.com/remove-hiss-hum-sound-forge/) shows how to confirm the recorded peak before filtering. - **100 Hz:** a simple low-frequency check for [small speakers, headphones and obvious buzzes](https://soundforgepro.com/headphone-test/). Keep the level conservative; a quiet or distorted result can come from the output device, enclosure, room or routing. - **440 Hz:** an A4 pitch reference and an easy-to-hear routing signal. - **1 kHz:** a common midrange reference that is useful for tracing signal flow and checking whether an output is alive. - **5 kHz:** a short high-frequency check. Do not compensate for reduced audibility by turning it up aggressively. If the job is simply to confirm which physical side is left or right, use the dedicated [left/right speaker test](https://soundforgepro.com/left-right-speaker-test/), which provides channel-specific controls and a symptom-led routing checklist. This page handles frequency generation and leaves stereo diagnosis to that one. ## How to use a frequency sweep without over-reading it A sweep is useful for finding the point where a rattle starts, [a speaker stops producing useful output](https://soundforgepro.com/bass-test/) or the perceived level changes sharply. Narrow the range first. For example, if a cabinet buzz seems confined to bass, scan 40–200 Hz instead of running 20 Hz–20 kHz every time. What you hear is the combined result of the digital tone, output route, converter, amplifier, transducer, room and listener. A louder patch during the sweep doesn’t by itself measure frequency response, and a quiet patch won’t tell you which part of that chain caused it. Repeat at a lower level, move your listening position and compare a second output before blaming a component. To inspect frequencies inside an existing recording rather than generate them, open the file in our [audio spectrum analyzer](https://soundforgepro.com/audio-spectrum-analyzer/). It reports FFT peaks from the selected local file; the tone generator does not analyze incoming audio. ## How the browser makes the signal The control uses the Web Audio API’s [OscillatorNode](https://developer.mozilla.org/en-US/docs/Web/API/OscillatorNode). Its frequency parameter is expressed in hertz, and its standard waveform types include sine, square, triangle and sawtooth. A GainNode applies the visible tool-level setting and short ramps at the start and stop reduce hard-edge clicks. The sweep schedules an exponential change between two positive frequencies. Playback starts only after an explicit Play action or the Space shortcut because browsers may block audible Web Audio without user activation, as described in MDN’s [Web Audio best practices](https://developer.mozilla.org/en-US/docs/Web/API/Web%5FAudio%5FAPI/Best%5Fpractices). No microphone or file API is used. ## Keep test tones short and quiet The page deliberately starts low and limits its own gain, but your device, interface and amplifier still determine the physical output. A browser percentage is not dB SPL and cannot guarantee a safe listening level. The [World Health Organization’s safe-listening guidance](https://www.who.int/news-room/questions-and-answers/item/deafness-and-hearing-loss-safe-listening) recommends keeping personal-device volume to no more than 60% of maximum and, where level monitoring is available, below an 80 dB average. These are general listening guidelines, not a starting volume or a guarantee for test tones. Begin much lower and do not raise an inaudible high or low tone to reach a percentage. Duration matters as well as loudness. NIOSH identifies [repeated occupational exposure at 85 dBA or higher](https://www.cdc.gov/niosh/noise/prevent/understand.html) as hazardous, although its limit is an occupational recommendation rather than a calibration for this browser tool. The practical rule here is simpler: begin low, use short checks, never raise an inaudible extreme tone abruptly and stop at any discomfort. ## What this tool does not prove - It does not measure acoustic level, distortion, frequency response or room response. - It does not certify a speaker, headphone, converter or broadcast chain. - It cannot diagnose hearing or replace calibrated audiometry. - It does not guarantee that the physical output exactly matches the digital level shown on the page. - It does not save or export a WAV file in this version. ## Online tone generator FAQ ### Can I generate an exact frequency? You can enter 20 to 20,000 Hz, with up to two decimal places. The page rounds extra decimal places when you finish editing the field. This sets the digital oscillator; it does not calibrate your converter, speaker or listening environment. ### Why can I not hear a very high or low tone? The output device, level, route and listener can all limit audibility at the extremes. Do not keep raising the volume to force an inaudible tone. Compare another known output and treat the result as a clue, not a hearing diagnosis. ### Which waveform should I use for a speaker test? Start with sine when you want to isolate one frequency. Square, triangle and sawtooth add harmonics, so they can excite other parts of the playback chain and sound much brighter at the same tool setting. ### Can I use this as an online hearing test? No. The page has no calibrated headphones, reference sound-pressure level or clinical procedure. It can generate a reference signal, but it cannot measure hearing or provide a diagnosis. ### Does the tone generator record or upload audio? No. It creates the oscillator and gain stages in the current browser. It does not request microphone access, read a local audio file or send an audio stream to the server. ### Left and Right Speaker Test: Check Stereo Channels Online URL: https://soundforgepro.com/left-right-speaker-test/ Last updated: 2026-09-30T21:27:15.000Z Use this left and right speaker test as a quick left and right sound test: play **Left**, **Center** and **Right**. Then use L → R for a smooth pan. It also works as a left and right audio test for checking channel identity through speakers, headphones or earbuds. If a side is swapped, silent or playing through both outputs, match the symptom below. The test requests no microphone and uploads no audio. Browser stereo test · no microphone ## Stereo test: left, center and right This test generates audio locally. It does not access your microphone, read files or upload audio. !**Start with your system volume low.** The tool level starts at 8% and is capped at 30%; it is not a sound-pressure reading. Stop immediately if the signal feels uncomfortable. **L**Left output **R**Right output Now playing **Stopped** Choose Left, Center or Right. The highlighted side should match what you hear. Left Center Right L → R Stop Test signal 440 Hz sine Pink noise Tool level 8% Did the sound match? Yes, correct Wrong / missing [Match the symptom below →](#what-your-result-means) Ready. Choose a test button to start. Keyboard: L = left, R = right, B = center; Escape = stop. This checks browser output routing. It won’t test hearing or calibrated speaker performance. ## How to run the stereo test 1. **Start low.** Set the computer, phone, amplifier or headphone volume to a comfortable low level. The tool-level control starts at 8%; keep your system volume low too. 2. **Press Left.** You should hear the signal only from the physical left speaker or left earbud. 3. **Press Right.** The same signal should move completely to the physical right side. 4. **Press Center.** With [matching speakers or headphones](https://soundforgepro.com/headphone-test/), the sound should appear centered rather than pulling clearly to one side. 5. **Try L → R.** The signal should move smoothly across the stereo image. Press Stop before unplugging a cable or changing an output device. Use the 440 Hz sine for a clear routing check. [Pink noise](https://soundforgepro.com/pink-noise-generator/) spreads energy across a wider range and can make an obvious left/right tonal difference easier to hear. Neither mode measures frequency response or acoustic level. ## What your result means | What you hear | What the test establishes | What to check next | | -------------------------------------- | --------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------ | | Left plays left; Right plays right | The browser reaches the expected stereo channels | If one app is still wrong, check that app’s output and channel settings | | Left plays right; Right plays left | This test reaches the opposite physical sides; compare a known-good stereo source | Speaker position, left/right cable mapping, interface mixer or virtual channel mapping | | One side is silent | One output path is missing during this test | OS balance, connector seating, cable swap, interface channel and a second device | | Left or Right plays through both sides | The stereo signal is being collapsed or mirrored | Mono accessibility settings, mono speaker hardware, Bluetooth profile or a routing utility | | Nothing plays | The browser has no audible route or playback was blocked | Mute state, selected output, site sound permission and the system sound test | This is a routing test rather than a component tester. A silent side can come from software balance, a loose connector, a cable, an interface, an amplifier channel, the speaker itself or the output device the operating system has selected. Change one thing at a time. ![Speaker test diagnostic paths for reversed channels, one silent side and stereo collapsed to mono](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/08/left-right-speaker-test-diagnostic-v1.webp) Match the symptom before changing hardware: reversed routing, a missing side and mono summing require different checks. ## If left and right are reversed First confirm that you are facing the speakers from the normal listening position and that the earcups are worn on the marked sides. Then trace the signal from the output toward the speakers: 1. Check any explicit left/right swap or channel-mapping control. Ordinary balance changes level, and mono combines channels; neither is a reversal fix. 2. Bypass virtual mixers, spatial-audio utilities and interface loopback software. 3. Verify that the left physical output feeds the left speaker or amplifier input. 4. Compare a known-good stereo recording in another player. If it is reversed too, correct the physical or software mapping you identified; do not change several connections at once. Do not reconnect powered speaker-level wiring while equipment is live. Follow the hardware maker’s shutdown instructions. ## If one speaker or earbud is silent Open the operating system’s balance control and make sure one channel hasn’t been turned down. Then reseat the connector, remove adapters temporarily and repeat the test with another known-good headphone or speaker output. That comparison separates an output-route problem from a fault that follows one headset or speaker pair. For a wired setup with separate, compatible left/right line-level cables, a controlled check can narrow the silent-side fault. Stop playback and shut down as the hardware maker directs. Swap only the cable ends at the source outputs, keeping each cable connected to the same physical speaker or amplifier input. Replay Center at low volume. If the silence moves to the other physical side, suspect the source output or its upstream routing; if it stays, investigate that cable and downstream branch with a known-good cable. This is not an instruction to swap mains, powered speaker-level wiring or wireless connections. If every browser and the system sound test work but Sound Forge does not, use our [Sound Forge no-sound troubleshooting order](https://soundforgepro.com/sound-forge-pro-no-sound/). It checks the selected playback device, Windows audio path and driver mode without starting with a reinstall. ## If Left or Right plays through both sides A stereo test can be collapsed to mono before it reaches the speakers. Check mono-audio accessibility settings, a mono Bluetooth or call profile, a single-speaker device, an interface mixer that sums channels, and any virtual cable or broadcast software in the route. For output balance, [Microsoft’s channel troubleshooting guide](https://support.microsoft.com/en-US/Windows/Hardware/Bluetooth/fix-bluetooth-audio-only-playing-in-one-channel) explains how to compare the selected output’s Left and Right levels. Mono audio is a separate accessibility setting. On iPhone, [Apple puts both controls](https://support.apple.com/en-lamr/guide/iphone/iphb80ab7516/ios) under Settings > Accessibility > Audio & Visual. On macOS, disable mono in [Accessibility > Audio](https://support.apple.com/en-gb/guide/mac-help/unac611/mac) and center the output balance under [Sound > Output](https://support.apple.com/en-gb/guide/mac-help/mchlp2256/mac). For a stereo check, temporarily disable [Windows mono audio](https://support.microsoft.com/en-us/accessibility/windows/make-windows-easier-to-hear): on Windows 11, open Settings > Accessibility > Audio; on Windows 10, open Settings > Ease of Access > Audio. Restore any accessibility setting you rely on after testing. A phone’s single built-in speaker can’t tell you anything about stereo separation. Use wired or stereo Bluetooth headphones, a known stereo speaker pair or an audio interface with separate left and right outputs. ## How the browser routes the signal The page creates either a 440 Hz sine wave or a short locally generated pink-noise buffer with the Web Audio API. A stereo panner routes that source from full left (−1) through center (0) to full right (+1), the range defined for [StereoPannerNode](https://developer.mozilla.org/en-US/docs/Web/API/StereoPannerNode). A gain stage applies the visible tool-level control and a short fade to avoid a hard start or stop. The mono source uses equal-power stereo panning: at Center it feeds both channels at about 0.707 of the hard-panned amplitude per channel. That describes digital routing, not a guaranteed acoustic center or equal loudness in the room. [Speaker placement](https://soundforgepro.com/speaker-placement-calculator/), reflections and downstream processing still matter. Playback starts from a test button or the L, R and B keyboard shortcuts. Browsers can block audible Web Audio without user activation, as explained in MDN’s [autoplay guidance](https://developer.mozilla.org/en-US/docs/Web/Media/Guides/Autoplay). The implementation does not call the microphone API, read a local file or send an audio stream to the server. ## What this test cannot tell you - It is not a hearing test and cannot distinguish an ear difference from an equipment difference. - It does not calibrate sound-pressure level, speaker sensitivity or frequency response. - It cannot name the failed component from one silent-channel result. - Center is a practical phantom-center check, not a matched-speaker measurement or a separate surround center channel. - Phone speakers, soundbars and Bluetooth devices may apply their own mixing or processing. ## When the file—not the speakers—is wrong If this browser test routes correctly but an exported file has a missing, swapped or one-sided channel, inspect the file rather than the playback hardware. The [Sound Forge Channel Converter guide](https://soundforgepro.com/sound-forge-channel-converter/) explains mono/stereo conversion and channel selection, while the [browser spectrum analyzer](https://soundforgepro.com/audio-spectrum-analyzer/) can show whether a file contains different left and right content. ## Frequently asked questions ### What does this stereo test check? It checks whether left and right stay on the correct sides, whether the same signal reaches both channels as a practical center check, and whether a pan moves smoothly across the stereo image. It does not identify a failed component or measure hearing, sound-pressure level or frequency response. ### Does the stereo test use my microphone? No. It generates a signal in the browser and sends it to the current audio output. It does not request microphone access, record sound or upload audio. ### Can I use it to test headphones and earbuds? This tool checks left/right routing and the smooth pan on headphones or earbuds. For balance, frequency sweeps and a broader listening check, use our [full headphone test](https://soundforgepro.com/headphone-test/). ### Why does Left play through my right speaker? This test is reaching the opposite physical sides. Compare a known-good stereo recording in another player, then check speaker placement, cable mapping and any interface or virtual-mixer channel swap. Ordinary balance changes levels rather than swapping channels. ### Why do both sides play when I press Left? The route may be summing stereo to mono. Check mono accessibility settings, Bluetooth call mode, a mono playback device and any mixer or routing software between the browser and the speakers. ### Is pink noise better than the 440 Hz tone? They answer slightly different practical questions. The steady tone makes channel identity clear; pink noise can make a broad tonal or level difference easier to notice. Neither is a calibrated speaker measurement. ### Best Audio Noise Reduction Software: 8 Tools by Job URL: https://soundforgepro.com/audio-noise-reduction-software/ Last updated: 2026-10-06T06:52:05.000Z The best audio noise reduction software depends on where the noise lives. For a recorded file with hiss, **iZotope RX 12 Standard** is the strongest broad specialist, while **Acon Digital Restoration Suite 2** gives a more affordable manual and adaptive denoiser. For speech mixed with changing traffic or room sound, **Antinode Clear** and **Waves Clarity Vx Pro** offer dedicated speech-cleanup workflows. **Audacity 4.0.0** remains the sensible free choice for steady noise. A live microphone is a different job again: **NVIDIA Broadcast** processes the virtual mic before the call or stream. A feature table cannot tell you how a denoiser will handle your worst recording. This guide matches eight current tools to recorded audio, speech-only cleanup and live microphones, then gives you a five-step comparison protocol for your own recording that exposes damaged consonants, watery artifacts and false “improvements” caused by extra loudness. Versions, requirements and displayed US prices were checked on September 12, 2026. ![Noise-only profiling, voice separation and live virtual microphone workflows](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/09/noise-cleanup-workflows-20260912.webp) Choose the processing path first: learn only unwanted noise, separate dialogue, or route a cleaned live microphone. ## Choose the Workflow Before the Product Noise reduction software falls into three practical families. A conventional editor or restoration plugin learns a noise profile or estimates a noise floor, then attenuates matching frequencies. It's often the cleanest route for constant noise such as stable hiss, fan noise and tape noise because you can control what gets removed. Speech-separation tools instead try to isolate a voice from changing ambience and reverb. They can reduce manual setup for dialogue, but may reshape tone or articulation. Live suppressors sit between the microphone and another app, so latency, hardware and virtual-device routing matter as much as cleanup quality. A noise gate is no substitute for denoising: it lowers the background between phrases but doesn't remove noise under speech or music. If the fault is actually clicks, clipping, hum, codec damage or a corrupt file container, start with the broader [audio restoration diagnosis guide](https://soundforgepro.com/audio-restoration/). The separate [audio restoration software comparison](https://soundforgepro.com/audio-restoration-software/) covers those wider repair jobs. ## The Shortlist - **Best overall for recorded material:** iZotope RX 12 Standard. - **Best-value manual/adaptive plugin set:** Acon Digital Restoration Suite 2. - **Best simple speech plugin:** Antinode Clear. - **Best pro real-time dialogue plugin:** Waves Clarity Vx Pro. - **Best full editor for Creative Cloud teams:** Adobe Audition. - **Best free offline option:** Audacity 4.0.0. - **Browser speech cleanup with minimal setup:** Adobe Podcast Enhance Speech v2. - **Best live mic option for an RTX PC:** NVIDIA Broadcast. ## Audio Noise Reduction Software Comparison | Tool | Best job | Processing | Platform / host | Checked cost | | ---------------------------- | ------------------------- | ---------------------- | ------------------------ | --------------------------------- | | **RX 12 Standard** | Mixed recorded damage | Local editor + plugins | Windows, macOS | $399 perpetual | | **Acon Restoration Suite 2** | Profile/adaptive denoise | Local plugins | Windows, macOS hosts | $99 displayed | | **Antinode Clear** | Voice noise + reverb | Local real-time plugin | Windows, macOS hosts | $69 displayed | | **Waves Clarity Vx Pro** | Pro dialogue in real time | Local plugin | Compatible DAW/NLE hosts | $699 MSRP; $249 page price | | **Adobe Audition** | Editor + video workflow | Local editor | Windows, macOS | $22.99/mo annual plan | | **Audacity 4.0.0** | Steady noise for free | Local editor | Windows, macOS, Linux | Free, open source | | **Adobe Podcast v2** | One-click spoken audio | Cloud browser service | Modern browser | Free use; premium limits differ | | **NVIDIA Broadcast** | Live mic and calls | Local virtual device | Windows + RTX GPU | Free app; compatible GPU required | This shortlist uses current vendor documentation, edition boundaries, platform requirements, trial terms and processing model. It is a workflow comparison rather than a measured sound-quality ranking. Use the table to shortlist tools, then compare the candidates on the recording that represents your actual work. ## 1\. iZotope RX 12 Standard: Best Overall for Recorded Material [RX 12 Standard](https://www.izotope.com/en/shop/rx-standard/) is the broadest choice here because it combines a standalone restoration editor with specialist modules. [Spectral De-noise](https://izotoperx.net/voice-denoise-vs-spectral-denoise/) handles tonal and broadband noise with a learned profile or adaptive processing. Voice De-noise covers vocal recordings in real time, and the editor gives you a spectrogram when the problem is local rather than spread across the whole file. For changing crowds or traffic, [Dialogue Isolate](https://docs.izotope.com/rx12/en/dialogue-isolate.html) separates voice, noise and reverb in Standard and Advanced. Advanced adds its Best/Offline quality mode and multiband controls. Voice De-noise is a different processor, not another name for Dialogue Isolate. The [Dialogue Isolate settings guide](https://izotoperx.net/izotope-rx-dialogue-isolate/) on izotoperx.net shows the voice, noise and reverb controls in use. The current US price is $399\. That's expensive if you only need to remove a constant laptop fan twice a year, and it becomes defensible when location dialogue, old recordings and mixed repair jobs arrive repeatedly. Standard also avoids a common edition mistake: RX Elements includes six repair plugins, but not the standalone RX Audio Editor or Spectral De-noise. **Choose it for:** changing noise, detailed inspection and recurring paid repair. **Skip it for:** live call cleanup or occasional steady hiss that Audacity or Acon can handle. If the decision is specifically between this suite and the site’s core editor, use the [Sound Forge vs iZotope RX comparison](https://soundforgepro.com/sound-forge-pro-vs-izotope-rx/). ## 2\. Acon Digital Restoration Suite 2: Best Value for Controlled Denoising [Acon Digital Restoration Suite 2](https://acondigital.com/products/restoration-suite/) packages DeNoise, DeHum, DeClick and DeClip as plugins. DeNoise 2 can work adaptively or learn a measured noise profile. Its dynamic profiles are useful when the noise floor changes over time, while the conventional profile route keeps the operator in control when a clean noise-only passage exists. The current page price is $99\. Acon advertises a free upgrade to Restoration Suite 3 for qualifying purchases, but still describes version 3 as coming soon; this comparison covers the available version 2\. This is a noise reduction plugin suite, not a standalone editor, so budget for a compatible host and verify the demo in that exact host. Acon lists VST/VST3/AAX on Windows and VST/VST3/AAX/AU on macOS. **Choose it for:** music, field recordings and dialogue where you want a controllable noise profile without buying RX Standard. **Skip it for:** one-click browser speech cleanup or a live virtual microphone. ## 3\. Antinode Clear: Best Simple Speech Plugin [Antinode Clear](https://antinodeaudio.com/clear) (formerly Supertone Clear) separates voice from noise and reverb with three primary controls for voice, ambience and voice reverb. Processing is local and real time through AU, VST, VST3 or AAX, which makes it easier to keep a dialogue edit inside a DAW or video workflow instead of uploading the file. The page displayed a $69 one-time price, but its sale-date copy was internally stale when checked. Verify the live checkout rather than relying on an old roundup. The trial inserts noise every 60 seconds and doesn't save or load profiles, so use it to judge voice tone and artifact behavior rather than to deliver a finished job. **Choose it for:** podcast, interview and voice-over cleanup where speed matters. **Skip it for:** music, archive restoration or a fault that needs spectral selection rather than voice separation. ## 4\. Waves Clarity Vx Pro: Best Pro Real-Time Dialogue Plugin [Clarity Vx Pro](https://www.waves.com/plugins/clarity-vx-pro) is built around real-time voice noise reduction and automation. That makes it useful when a mixer needs to ride processing through a changing scene instead of applying one setting to an entire file. It's a dialogue tool; it isn't a general music denoiser. Waves showed a $699 MSRP and a $249 page price on the evidence date. Waves pricing changes often, so compare the live price with Antinode Clear, Acon and the RX edition that supplies the module you actually need. Also check host and operating-system compatibility before buying; a plugin is only useful if the production system can load it reliably. **Choose it for:** professional dialogue mixing, automation and real-time preview. **Skip it for:** someone who still needs a complete editor, or a simple free fix for steady hiss. ## 5\. Adobe Audition: Best Full Editor for Creative Cloud Teams [Adobe Audition](https://www.adobe.com/products/audition/noise-reduction.html) covers more than one denoising model. Its Noise Reduction process learns a noise print for constant backgrounds; Adaptive Noise Reduction follows variable broadband noise in real time; DeNoise offers a quicker effect; and the Spectral Frequency Display helps isolate a narrow event visually. The Waveform and Multitrack editors also keep cleanup beside the rest of a podcast or video-audio workflow. Its [noise-print process is Waveform-only](https://helpx.adobe.com/audition/desktop/effects-reference/noise-reduction-restoration-effects.html); Adaptive Noise Reduction can also run in the Multitrack Effects Rack. Choose the editor mode before looking for the effect. The US Audition plan was $22.99 per month on an annual billed-monthly contract, with a seven-day trial. That subscription makes sense when Premiere Pro round-trips or the wider Creative Cloud workflow save time. It's harder to justify as a single-purpose denoiser when you already own an editor and only need a plugin. **Choose it for:** editors who need waveform, multitrack, spectral repair and Adobe integration. **Skip it for:** a perpetual-license requirement or live call suppression. ## 6\. Audacity 4.0.0: Best Free Offline Option [Audacity’s Noise Reduction](https://www.audacityteam.org/features/noise-reduction/) effect is still the best free starting point when the recording contains a stable fan, hiss or room tone and provides a short noise-only passage. Capture the profile, process a copy, and use the Residue monitor to hear what the effect wants to throw away. Recognizable consonants or musical detail in the residue mean the settings are too aggressive. The current [Audacity 4.0.0 download](https://www.audacityteam.org/download/) is free and open source on Windows, macOS and Linux. Noise Reduction is documented for steady-noise cleanup. Audacity 4 saves new .aup4 projects; it opens .aup3 projects by converting them without changing the original, but cannot save the converted project back to .aup3\. The [official 4.0 compatibility notes](https://www.audacityteam.org/changelog/) also list several missing Audacity 3 workflows and some incomplete export, rendering, analyzer and effect paths. Use 4.0.0 for a new noise-profile workflow, but keep a tested 3.7.9 workflow when a documented 4.0 omission blocks an existing project. Profile reduction still struggles when traffic, another voice or room reflections change under the wanted speech. A noise gate can tidy gaps afterward, but it cannot remove noise that overlaps the voice. **Choose it for:** steady noise, offline privacy and a zero-dollar starting point. **Skip it for:** one-click separation of speech from non-stationary noise. ## 7\. Adobe Podcast Enhance Speech v2: Browser Speech Cleanup with Minimal Setup [Enhance Speech v2](https://podcast.adobe.com/enhance-speech-v2) is the quick route when the input is spoken audio and the operator doesn't want to configure a denoiser. Adobe positions it for noise, echo and distant voice, with controls for speech, music and ambience in the premium workflow. Premium also adds video support and bulk upload. The [free-plan limits](https://podcast.adobe.com/en/features) are 30 minutes and 500 MB per file, with one hour per day; free use lacks bulk upload, video and strength adjustment. Premium allows files up to two hours and 1 GB, within four hours per day. The tradeoff is control and privacy. The file is processed as a cloud upload, and speech enhancement can change tone as well as remove noise. Keep the original, download the result as a new file and compare at matched loudness. Do not use it for confidential material unless the project’s data policy permits that service. **Choose it for:** fast podcast, interview and voice-note rescue. **Skip it for:** music, local-only processing or work that requires a transparent audit trail. ## 8\. NVIDIA Broadcast: Best Live Mic Option on an RTX PC [NVIDIA Broadcast](https://www.nvidia.com/en-us/geforce/broadcasting/broadcast-app/faq/) creates a virtual microphone or speaker that other apps can select. Its Noise Removal and Room Echo Removal effects run in real time using RTX Tensor Cores, so the job happens before Discord, Zoom, OBS or another compatible app receives the signal. The app is free, but the hardware isn't. The linked US NVIDIA FAQ, checked September 12, 2026, lists a GeForce RTX 2060, Quadro RTX 3000 or TITAN RTX, with Windows 10 64-bit, 8 GB RAM and driver 570.xx or later. Check the current installer before upgrading an older system. The separate Studio Voice effect requires an RTX 3060 desktop GPU or higher; that is not the baseline for Noise Removal. Don't stack it with another microphone noise suppressor; double processing can strip articulation and adds unnecessary system load. **Choose it for:** streams, calls and voice chat on an existing RTX system. **Skip it for:** restoring an already recorded music or archive file. ## Match the Tool to the Noise | Problem | Start with | Why | | --------------------------------------- | ---------------------------------------------------------------- | ---------------------------------------------------------------- | | Steady hiss, fan or tape noise | Audacity, Acon DeNoise or RX Spectral De-noise | A representative noise profile is available. | | Changing traffic or crowd behind speech | Antinode Clear, Clarity Vx Pro or RX Dialogue Isolate | Speech separation/adaptive processing fits non-stationary noise. | | Room reverb around dialogue | Antinode Clear, Adobe Podcast v2 or a dedicated de-reverb module | Denoising alone does not model reflections. | | Live microphone on an RTX PC | NVIDIA Broadcast | The virtual device cleans the signal before the call or stream. | | Music plus several repair faults | RX 12 Standard or Acon inside a trusted editor | Speech-only regeneration can alter instruments and ambience. | | Confidential or unreleased audio | Local editor or plugin | No cloud upload is required. | If you only need to [remove background noise in Sound Forge](https://soundforgepro.com/how-to-remove-background-noise-in-sound-forge-pro/), follow that product-specific workflow. It explains where the current tools live, how to capture a clean noiseprint and when a missing module means the problem is the edition or installation rather than the audio. ## A Trial Protocol for Your Own Recording ![Four checks for a level-matched noise reduction comparison and final export](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/09/noise-reduction-ab-checks-20260912.webp) Keep an untouched reference, match the listening level, check for damaged detail, then export with diagnostic monitoring off. 1. **Choose one difficult comparison file.** Use 30–60 seconds from a real project containing quiet words, sibilants, breaths and the worst noise. Add a stable-hiss section only if that noise genuinely exists in the job. 2. **Keep one untouched reference.** Duplicate the file and never process the reference. Disable loudness normalization, auto gain and enhancement features that are not part of the comparison. 3. **Match loudness before deciding.** A louder result can seem clearer even when the processing has damaged useful detail. Use a meter and attenuate whichever version is louder until the comparison is level matched. The browser [LUFS meter](https://soundforgepro.com/lufs-meter/) can make that pre-check without uploading the file. 4. Listen to what was removed. Identify what the monitor plays. Wanted consonants in a removed-noise output are a warning; a difference signal may also contain deliberately reduced reverb or other legitimate changes. Judge the normal output at matched level, and turn diagnostic monitoring off before export. 5. **Check five failure points.** Judge steady noise, changing noise, room reverb, consonants and the silent tail separately. Export a lossless WAV and re-check it outside the plugin host before paying. For a visual check of hum bands, broadband noise and harmonics before processing, the local [audio spectrum analyzer](https://soundforgepro.com/audio-spectrum-analyzer/) can inspect the file in the browser. A spectrum cannot tell you whether speech sounds natural, but it can stop you from treating a narrow 60 Hz problem like full-band noise. ## What Noise Reduction Cannot Fix A denoiser can't recreate detail that the microphone never captured. It can't reliably separate two people speaking over each other, rebuild peaks lost to hard clipping or repair a corrupt container that won't decode. Strong processing may make the background quieter while leaving speech less intelligible. That's a failed repair, even if the waveform looks cleaner. Stop when the noise no longer distracts at normal playback level. Chasing silence often creates metallic tails, chirps, phasey vowels and missing consonants. For material with several damage types, run the [AI audio restoration guide](https://soundforgepro.com/ai-audio-restoration/) and the broader diagnosis before buying another “one-click” tool. ## Frequently Asked Questions ### What is the best audio noise reduction software? RX 12 Standard is the strongest broad choice for recorded material because it combines adaptive and profile-based denoising with a standalone spectral editor. It is not the best value for every job. Audacity is better for a free steady-noise fix, Antinode Clear or Clarity Vx Pro fit speech separation, and NVIDIA Broadcast fits a live RTX microphone. ### What is the best free noise reduction software? Audacity 4.0.0 is the best free offline starting point for stable hiss, fan noise and similar backgrounds when the file contains a clean noise-only sample. Adobe Podcast Enhance Speech can be faster for spoken audio, but it is a cloud service and changes more than the noise floor. ### Can noise reduction remove background voices? Sometimes a speech-separation model can reduce a competing voice, but it cannot guarantee a clean recovery when both speakers overlap in the same time and frequency range. Test Antinode Clear, Clarity Vx Pro, RX Dialogue Isolate or a comparable speech tool on the actual passage and listen for missing consonants and altered tone. ### Is AI noise removal better than a noise profile? AI speech separation is often more useful for changing traffic, room sound and unpredictable ambience. A measured noise profile is usually more controllable for stable hiss or fan noise. Neither is universally cleaner; the wanted signal and the noise behavior decide. ### Does a noise gate remove noise under speech? No. A gate reduces the signal when it falls below a threshold, so it can quiet gaps between phrases. Noise that overlaps speech remains. Use denoising first, then apply a gentle gate only if the remaining background between phrases still needs control. ### Should I upload confidential audio to an online cleaner? Only if the project’s privacy, client and retention rules permit that service. For unreleased, legal, medical or otherwise sensitive recordings, use a local editor or plugin unless the organization has approved the cloud processor and its terms. *Fact-checked September 12, 2026 against current product pages and documentation from iZotope, Acon Digital, Supertone (now Antinode Audio), Waves, Adobe, Audacity and NVIDIA. Displayed prices and system requirements can change; verify the live vendor page before purchase.* ### Audio Spectrum Analyzer Online: FFT & Frequency Peaks URL: https://soundforgepro.com/audio-spectrum-analyzer/ Last updated: 2026-10-09T21:01:01.000Z Open an audio file or microphone below to inspect its current frequency content. The audio is decoded and measured in this browser; it isn't uploaded, and the page doesn't send filenames, samples or measured values to analytics. Start with the logarithmic view and a 4096-point FFT. That's a readable general-purpose setup for speech, music, hum and resonances. Increase the FFT size when two nearby steady tones blur together; reduce it when you need the display to react faster to short events. Free browser FFT tool · no audio upload ## Audio spectrum analyzer Open a local file, use the microphone, or run a 440 Hz test. Inspect frequency peaks in real time. The 440 Hz test is silent; selected files play through your output. Ready Choose audio file Use microphone Silent 440 Hz test **No source selected.** Choose a file, microphone or test tone. Play Stop Analyzer settingsFFT size, scale, channel and smoothing FFT size 2048409681921638432768 Frequency scale LogarithmicLinear Channel Mix / monoLeftRight Smoothing 0.70 Freeze Peak hold on Reset peaks Download CSV Download PNG Resolution — Dominant frequency**—**Start an input FFT peak level**—**Per-bin magnitude; not RMS, sample peak or SPL Input**None**Sample rate — Peak tableSpectral peaks; note labels may identify harmonics ### Strongest spectral peaks | # | Frequency | Level | Nearest note | | - | --------- | ----- | ------------ | | — | Waiting | — | — | **Privacy:** audio samples, filenames and readings stay in this page. **Limit:** an ordinary microphone is not a calibrated sound-level meter. ## How to analyze an audio file or microphone 1. **Choose the source.** Open a browser-decodable audio file, allow microphone access only when you need a live input, or run the internal 440 Hz / A4 test to check the display path. The internal source does not test file decoding, microphone calibration or external recording accuracy. 2. **Set the question.** Keep the logarithmic scale for musical balance, hum and broad tonal problems. Switch to linear when equal spacing in hertz matters more than equal spacing by octave. 3. **Choose FFT size.** Use 4096 as a practical start, 8192–32768 for narrower steady peaks, or 2048 for quicker motion. The displayed Hz-per-bin value shows the actual spacing. 4. **Read the shape before the number.** A single narrow spike, a harmonic series and a broad high-frequency shelf point to different problems. Hover or touch the graph only after you identify the pattern. 5. **Freeze or export the evidence.** Freeze holds the current curve, not playback or microphone capture. Peak hold keeps the highest observed value in each bin. PNG captures the graph; CSV includes all non-DC bins up to Nyquist, including frequencies outside the plotted range. Press Stop to end the source. ![Actual FFT graph of a 440 Hz sine with neighboring-bin spread and a decibel magnitude scale](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/09/spectrum-440hz-actual-20260913.png) Actual export from the silent 440 Hz test at 48 kHz with a 4096-point FFT (11.72 Hz per bin). The finite window spreads the tone across neighboring bins; the level is FFT magnitude, not sound pressure. ## Read a spectrum without guessing | Pattern | Likely meaning | Next useful check | | --------------------------------- | -------------------------------------------- | ---------------------------------------------------------------------------------------- | | One stable narrow peak | A tone, electrical whine or strong resonance | Check whether harmonics repeat at exact multiples | | 50 or 60 Hz with multiples | Mains-related hum is plausible | Compare 100/120 Hz and higher harmonic lines, then inspect the recording chain | | Wide energy across many high bins | Hiss, air or broadband noise | Compare a noise-only region with wanted program | | Regular harmonic ladder | A pitched source or nonlinear distortion | Read the fundamental, then compare harmonic levels rather than deleting every upper peak | | Curve changes every frame | Normal for speech, music and transients | Use smoothing or freeze; do not treat one moving frame as a full-file average | A spectrum shows level by frequency at the current moment. The strongest peak can be a harmonic rather than the fundamental, so its nearest-note label may be an octave or another interval away from the played note. It can't tell you whether the sound is musically right, and it won't show when a frequency occurred across the whole file. That second job belongs to a [spectrogram](https://izotoperx.net/how-to-read-izotope-rx-spectrogram/), where time is another axis. ## What FFT size changes The browser's analyzer uses a sample window whose length is the selected FFT size. The bin spacing is the context sample rate divided by that size. At 48 kHz, a 4096-point FFT spaces bins by about 11.72 Hz; 16384 narrows that to about 2.93 Hz. The graph stops at the lower of 20 kHz or the context's Nyquist frequency, which is half its sample rate. The larger window separates nearby steady components more clearly, but covers more time and responds less tightly to short events. Think of it as a tradeoff rather than a quality slider. The [MDN documentation for AnalyserNode.fftSize](https://developer.mozilla.org/en-US/docs/Web/API/AnalyserNode/fftSize) defines the supported power-of-two range, and the [Web Audio visualization guide](https://developer.mozilla.org/en-US/docs/Web/API/Web%5FAudio%5FAPI/Visualizations%5Fwith%5FWeb%5FAudio%5FAPI) explains why you get half as many frequency bins as the FFT size. Smoothing changes the display over time. A high value calms movement and makes a stable tonal balance easier to read, but it can hide a short click, so lower it when the event is brief. Smoothing doesn't repair or filter the source. Peak hold can retain a source-start transient, so let a steady tone settle and press Reset peaks before judging its spectrum. ## Why the graph says dBFS, not sound-pressure dB The displayed level is the magnitude of an FFT bin. It isn't a time-domain sample peak, an RMS level or a true peak. The [Web Audio analysis method](https://www.w3.org/TR/webaudio-1.0/#fft-windowing-and-smoothing-over-time) applies a Blackman window, a normalized transform and smoothing before it converts magnitude to decibels, so bin position, windowing and smoothing all shape the number. Don't compare it directly with a full-file loudness or peak meter. A microphone adds its preamp, device gain and system processing on top of that uncertainty, and without a calibrated chain the reading isn't dB SPL. Use the microphone mode to find relative peaks, harmonics and changes. It can't certify workplace noise, speaker sensitivity or room SPL. A phone and a measurement microphone can draw similar frequency shapes while reporting very different absolute levels. ## What “local” means here The file chooser creates a temporary browser object URL; Web Audio reads it in the page. Microphone mode uses the permission-controlled media stream. The implementation has no audio upload endpoint, and analytics records only coarse actions such as starting a source or exporting a graph. Format support follows the browser and operating system. This tool gives the selected file to an HTML audio element and starts analysis only after the browser reports that it can play the media. The [MDN documentation for HTMLMediaElement.canPlayType()](https://developer.mozilla.org/en-US/docs/Web/API/HTMLMediaElement/canPlayType) explains why support is reported as “probably,” “maybe” or unsupported rather than as one universal format list. PCM WAV is the safest troubleshooting input when a compressed file refuses to open. The channel selector changes what gets analyzed; the file still plays through your speakers the same way. Mix / mono sums the available channels, so opposite-polarity stereo can cancel out. Left and Right inspect the first two channels separately, and Right can be silent on a mono source, so use Mix / mono for mono recordings. For a full-file loudness or true-peak check, use the [LUFS meter](https://soundforgepro.com/lufs-meter/); for another measurement job, pick from the [audio tools hub](https://soundforgepro.com/tag/audio-tools/). Turn your system volume down before selecting a file, because file mode plays the recording while it analyzes it. Microphone mode doesn't go to your speakers, and the internal 440 Hz test is silent. If the graph stays empty, choose Mix / mono, unfreeze it and check the source. For microphone access, use HTTPS and allow permission in the browser; [a permission request can remain pending](https://developer.mozilla.org/en-US/docs/Web/API/MediaDevices/getUserMedia) until you answer it. Stop cancels this tool’s pending start. If a file won't open, try a short PCM WAV, and press Play if mobile autoplay is blocked. ## Continue the measurement in Sound Forge For a single voice or instrument’s pitch, use the [monophonic pitch detector](https://soundforgepro.com/pitch-detector/) and check its confidence rather than reading the highest FFT peak as a tuner. For work inside the editor, the [Sound Forge Spectrum Analysis guide](https://soundforgepro.com/how-to-use-spectral-analysis-tool-sound-forge-pro/) covers its menus, snapshots, monitoring and Sonogram. Once you identify a stable line or noisy band, move to the repair that matches the pattern. Use the [hiss and hum workflow](https://soundforgepro.com/remove-hiss-hum-sound-forge/) for steady electrical lines or broadband noise, and the [Sound Forge equalizer guide](https://soundforgepro.com/how-to-use-equalizer-sound-forge-pro/) when a measured resonance needs a restrained, listenable correction. ## Frequently asked questions ### Is my audio uploaded to SoundForgePro? No. The selected file, microphone samples, filename and measured values remain in this browser. Tool events contain an action label, not audio content, filenames or readings. Ordinary site analytics may still use browser or session identifiers; local audio processing is not a promise of anonymous browsing. ### What is the best FFT size for audio? There is no universal best size. Start at 4096\. Increase it for closely spaced steady frequencies; reduce it for faster response to short events. Use the displayed Hz-per-bin value to judge frequency spacing. ### Why is the microphone reading not dB SPL? The browser receives a level shaped by the microphone, preamp, device gain and operating-system processing. Without calibration, it can compare relative spectral energy but cannot produce a defensible sound-pressure level. ### What is the difference between a spectrum and a spectrogram? A spectrum plots level against frequency for the current moment. A spectrogram adds time, so you can see when each frequency appears. This tool is a spectrum analyzer, not a full-file spectrogram. ### Why does a 440 Hz tone show nearby frequencies too? An FFT divides a finite sample window into bins. A tone that does not land exactly at a bin center spreads energy into neighboring bins, and the analyzer's windowing shapes that leakage. Read the dominant peak and bin resolution rather than expecting one isolated pixel. ### Can the analyzer remove hum or noise? No. It identifies frequency patterns but does not process or download modified audio. Diagnose first, then make a restrained repair in an editor and compare the same passage again. **Last fact-checked:** September 13, 2026 against the W3C Web Audio specification, MDN documentation and this analyzer’s implementation. ### What Is True Peak? dBTP, Sample Peak and Codec Headroom URL: https://soundforgepro.com/true-peak-explained/ Last updated: 2026-10-10T13:29:37.000Z **True peak is an estimate of the highest level reached by the continuous waveform represented by digital audio.** It is reported in dBTP. A sample-peak meter stops at the largest stored sample magnitude; a true-peak meter reconstructs points between those samples and looks for a higher crest. As an illustrative example—not a measurement of a supplied test file—a WAV might have a sample peak of −0.1 dBFS and an estimated true peak of +0.7 dBTP. In this example every stored sample remains below full scale; the overshoot appears between samples in the reconstructed curve. Sample-rate conversion and lossy encoding can change that curve again. **Practical answer:** use Integrated LUFS to judge program loudness and true peak to protect the top of the signal. Follow a written delivery ceiling when one exists. Without one, −1 dBTP is a common starting point for lossy delivery, not a law that every platform enforces. Measure the actual encoded deliverable before sending it. ## True peak, sample peak and LUFS at a glance Swipe horizontally to compare every column → | Measurement | What it reads | Unit | What it answers | | ------------------- | ------------------------------------------------- | ------------------------------- | ----------------------------------------------------------------- | | Sample peak | Highest stored PCM sample magnitude | dBFS | Did any stored sample reach digital full scale? | | True peak | Estimated maximum of the reconstructed waveform | dBTP | Could the represented signal crest higher between samples? | | Integrated loudness | Gated program loudness over the measured duration | LUFS | How loud is the whole program by the chosen measurement standard? | | Limiter ceiling | A processing control, not a measurement result | dBFS or dBTP, depending on mode | What maximum should the limiter try to hold? | The units are related to full scale, but they do different jobs. A low true peak doesn’t make dialogue consistently loud, and a correct LUFS result won’t guarantee safe peaks. A limiter set to −1.0 on a sample scale isn’t automatically the same as −1.0 dBTP either. ![Sample peak at minus 0.1 dBFS compared with a reconstructed waveform crest at plus 0.7 dBTP](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/10/sample-peak-vs-true-peak-v20261006.webp) The stored samples stay below full scale while the reconstructed curve rises above it between sample instants. ## Why the highest sample can miss the highest crest PCM audio stores a sequence of sample values taken at discrete moments. Playback doesn’t turn those values into a staircase: ideal bandlimited reconstruction gives a continuous signal through the sample values. A practical DAC and its filter approximate that model; their output depends on the implementation, so not every physical waveform passes exactly through every stored value. Near a fast transient, the smooth reconstructed curve can rise higher than either neighboring sample. That between-sample maximum is commonly called an inter-sample peak. The sample-peak result remains correct about the data it inspected; it simply answered a narrower question. [ITU-R BS.1770-5](https://www.itu.int/dms%5Fpubrec/itu-r/rec/bs/R-REC-BS.1770-5-202311-I%21%21PDF-E.pdf) notes that sample-peak under-reading can commonly reach several decibels for transients with significant high-frequency content. It also explains why the problem is generally less severe at higher original sampling rates. Neither statement means every dense master has a huge hidden overshoot. The waveform, sample phase and bandwidth determine the difference. Floating-point PCM can also store sample values above 0 dBFS; that is a different issue from a between-sample overshoot. A positive dBTP reading describes an estimated peak above the full-scale reference. It doesn’t prove that every converter, phone or streaming path clipped audibly, since downstream headroom and implementation vary. It does tell you the file is close enough to the boundary that reconstruction or later processing deserves attention. ## How a true-peak meter makes the estimate The current [BS.1770-5 recommendation](https://www.itu.int/rec/R-REC-BS.1770-5-202311-I/en) specifies a true-peak measurement method built around oversampling. The meter inserts intermediate values, applies an interpolation filter and then searches the higher-rate signal for its maximum. It’s recreating a standards-defined view between the original samples, not recording the output of every possible physical converter. Oversampling accuracy matters. The ITU document shows that increasing the oversampling ratio reduces the possible under-read. [EBU Tech 3343-2023](https://tech.ebu.ch/docs/tech/tech3343.pdf) describes about 0.5 dB of possible under-read for a 4× true-peak meter at a 48 kHz base rate and uses that context when explaining its production headroom. This is why two meters can disagree slightly without either being a sample-peak meter. They may use different oversampling ratios, filters, channel handling or update behavior. For contractual work, use the meter and mode named by the specification. For ordinary preflight, the useful question is whether the reading leaves comfortable room rather than whether two displays match to the last tenth. ## Reconstruction is only the first place peaks can change A source WAV is not always the file a listener receives. Sample-rate conversion changes the represented samples. AAC, MP3 and other lossy codecs discard and rebuild information according to their own models. Decode filters then create another sample sequence. The loudest point after that path can differ from the source measurement. ![Four-stage path showing PCM samples, reconstructed true peak, lossy encoding and playback devices where peak shape can change](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/08/where-peaks-change-mobile.webp) Source measurement is necessary, but the encoded deliverable is the file that must survive the real distribution path. Apple’s [Digital Masters technology brief](https://www.apple.com/apple-music/apple-digital-masters/docs/apple-digital-masters.pdf) makes the operational point directly: levels that show no overs in PCM can still clip after encoding. Apple supplies tools for auditioning and checking the AAC result and recommends leaving at least 1 dB of headroom in its workflow. That doesn’t mean every codec always adds one decibel. Content, bitrate, sample-rate conversion and encoder implementation all matter. What it means is that “the source meter was clean” isn’t the final QA result when the deliverable is compressed audio. ## What true-peak ceiling should you use? Start with the destination rather than a number copied from a mastering chart. | Situation | Defensible decision | Scope | | ------------------------------------------------------ | ----------------------------------------------------- | ----------------------------------------------------------------------- | | Client or broadcaster supplies a ceiling | Use that ceiling and its named meter/mode | The written specification wins | | EBU generic linear PCM production | Maximum −1 dBTP | EBU R 128 production context | | EBU MPEG-1 Layer II or Dolby AC-3 distribution example | Maximum −2 dBTP | Specific data-reduction systems in Tech 3343 | | Spotify master around −14 LUFS | Keep below −1 dBTP | Current Spotify mastering guidance | | Spotify master louder than −14 LUFS | Keep below −2 dBTP | Spotify warns louder masters are more vulnerable to encoding distortion | | No written spec, lossy delivery expected | Use −1 dBTP as a starting point, encode and remeasure | House workflow, not a universal platform rule | Spotify’s current [loudness-normalization guidance](https://support.spotify.com/us/artists/article/loudness-normalization/) is a useful example of scope: it advises below −1 dBTP around −14 LUFS and below −2 dBTP for louder masters. Our [streaming loudness comparison](https://soundforgepro.com/streaming-loudness-standards/) separates this advice from playback normalization and other delivery specifications. Spotify’s advice does not establish a rejection threshold for Apple, YouTube or another distributor. ## True-peak limiting is not the same as typing a lower ceiling A conventional limiter can hold its output samples below a dBFS ceiling and still produce a higher reconstructed peak. In true-peak mode, a limiter uses an oversampled prediction in its detection path and controls gain against that estimate. Three practical limits remain: - **The mode must actually be enabled.** A plugin may show a true-peak meter while its limiter remains in sample-peak mode. For example, FabFilter Pro-L 2 documents [separate True Peak Limiting and TP metering controls](https://www.fabfilter.com/help/pro-l/using/truepeaklimiting); watching the meter is not the same as enabling the limiter mode. - **The source can change after the limiter.** EQ, gain, sample-rate conversion or encoding later in the chain can create a new maximum. - **A ceiling is not a sound-quality target.** More limiting can reduce transients and raise distortion even when the final dBTP number looks safe. If a clean master misses a delivery ceiling by a few tenths, lower the final gain or use a controlled true-peak limiter and compare level-matched audio. Lowering gain also lowers integrated loudness, so recheck both the LUFS target and peak ceiling. If the limiter is working hard, revisit upstream processing instead of treating the ceiling as the whole master. ## How to measure true peak without confusing it with LUFS Scan the complete file with an offline meter, or reset a playback meter and run the program from start to finish. Record both Integrated LUFS and maximum true peak. The first number describes program loudness; the second describes the highest estimated reconstructed crest. ![Browser LUFS meter reporting −23.0 LUFS integrated loudness and −18.0 dBTP estimated true peak as separate results, with sample peak alongside](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/10/lufs-meter-true-peak-real-v20261006.webp) Read Integrated LUFS and Estimated True Peak as separate checks. One cannot substitute for the other. The [SoundForgePro browser LUFS meter](https://soundforgepro.com/lufs-meter/) keeps the audio on the device and reports Estimated True Peak alongside loudness and sample peak. Its current limits are mono or stereo, 20 minutes and 200 MiB per file. Use a whole-file desktop meter for longer or multichannel programs. The browser result is a local pre-check, not a certification. If a broadcaster, client or certification process names a compliant meter, use that specified tool for final acceptance. For the current Sound Forge interface and meter-reset route, use the [Sound Forge LUFS and true-peak guide](https://soundforgepro.com/sound-forge-loudness-meters/). If the loudness result itself needs a constant gain correction, the [Sound Forge normalization workflow](https://soundforgepro.com/how-to-normalize-audio-in-sound-forge-pro/) separates Peak, RMS and LUFS decisions. ## A five-step true-peak delivery check ### 1\. Read the written specification Record the exact ceiling, unit, measurement standard, channel layout and file format. “Peak” is ambiguous unless the brief says sample peak or true peak. ### 2\. Meter the complete program Scan the complete file offline, or reset a playback meter and play the full program. Save the maximum dBTP result; a short preview can miss the loudest transient. ### 3\. Control the peak deliberately If correction is needed, reduce gain or use a limiter in verified true-peak mode. Don’t pile on heavy limiting just to make a warning disappear. ### 4\. Encode the delivery file Create the actual AAC, MP3, video mux or other required deliverable with the specified sample rate and bitrate. ### 5\. Reopen, remeasure and audition Inspect the delivered file, not only the source session. Listen around the loudest transient and compare the encoded result with the lossless master. ![Five-step true-peak delivery check from reading the specification through remeasuring the encoded file](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/08/true-peak-delivery-check-mobile.webp) A true-peak ceiling belongs inside a delivery workflow: specify, measure, control, encode and verify. ## Five mistakes that make true-peak advice unreliable - **Calling dBTP a loudness target.** True peak measures the highest reconstructed level; LUFS describes program loudness. - **Calling every reconstructed overshoot audible clipping.** A positive estimate flags risk, while the playback path determines the actual outcome. - **Using −1 dBTP as a universal upload rule.** It is a common starting point and a real value in specific standards, but scope matters. - **Checking only the source WAV.** The codec or sample-rate conversion can create a different peak shape. - **Assuming the limiter guarantees the deliverable.** Processing after the limiter and the final encode still need verification. ## True peak FAQ ### Can true peak be above 0 dBTP when no sample clips? Yes. Every stored sample can remain below 0 dBFS while the reconstructed waveform rises above full scale between samples. A true-peak meter estimates that crest by oversampling and interpolation. ### What is the difference between dBTP and dBFS? dBFS is the full-scale reference commonly used for stored digital sample levels. dBTP uses the same full-scale reference for a true-peak measurement that accounts for between-sample reconstruction. ### Is −1 dBTP the correct ceiling for every platform? No. −1 dBTP is a common starting point and an EBU limit for generic linear PCM production, while other delivery systems or platform guidance can specify a different ceiling. Follow the written destination requirement. ### Does true peak affect LUFS? They describe different properties. Changing gain or limiting can affect both results, but a true-peak number does not tell you the program's Integrated LUFS, and a LUFS result does not reveal its maximum reconstructed peak. ### Does a true-peak limiter guarantee that AAC or MP3 will not clip? No. It reduces risk at the limiter output, but later sample-rate conversion and encoding can change peak shape. Encode the required format, reopen it and measure the deliverable. ### How do I measure true peak correctly? Use a true-peak meter to scan the complete file offline, or reset it and play the full program. Record the maximum dBTP value. For formal delivery, use the standard, meter and mode named by the specification; then repeat the check on the encoded file. *Last fact-checked September 7, 2026 against ITU-R BS.1770-5, EBU Tech 3343-2023, Spotify for Artists, Apple Digital Masters and FabFilter’s Pro-L 2 documentation.* ### Streaming Loudness Standards: What Platforms Publish URL: https://soundforgepro.com/streaming-loudness-standards/ Last updated: 2026-10-09T21:01:19.000Z **There is no universal streaming loudness standard.** Spotify publishes a −14 LUFS Normal playback reference for music. Apple documents Sound Check but doesn't give one public LUFS delivery target on its current consumer page. YouTube publishes codec, channel and sample-rate guidance, yet the encoding page cited below doesn't declare a −14 LUFS requirement. A master loudness, an upload specification, a distributor’s normalization target and the level a listener gets from a particular device are four separate facts. A chart that puts all four under one “platform target” heading looks useful and can still send you in the wrong direction. **Practical answer:** keep a clean master at its native resolution, follow any written delivery specification, measure Integrated LUFS and true peak together, and check the encoded file. A platform’s playback number tells you how it handles gain. It doesn't give you permission to crush every master down to that number. ## Streaming loudness guidance at a glance Swipe horizontally to compare every column → | Service or standard | Published loudness information | True-peak information | What it actually governs | | ------------------------------------------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------- | | [Spotify music](https://support.spotify.com/bi-en/artists/article/loudness-normalization/) | Normal −14 LUFS; Premium Loud −11 and Quiet −19 | Mastering guidance: below −1 dBTP at −14 LUFS; below −2 dBTP when louder than −14 | Playback normalization and mastering advice, not a universal upload rejection threshold | | [Apple Music Sound Check](https://support.apple.com/en-ie/109331) | Normalizes songs toward a similar playback loudness; no public numeric target on the current consumer page | Separate Apple Digital Masters advice: leave at least 1 dB of headroom and check the AAC encode | Optional playback matching plus a separate mastering/delivery workflow | | [YouTube upload guidance](https://support.google.com/youtube/answer/1722171?hl=en) | No public LUFS upload target stated on the current encoding page | No numeric true-peak upload ceiling stated there | Content Manager partner encoding page: MP4, 48 kHz, stereo plus optional 5.1/Eclipsa workflows | | [AES77-2023](https://aes.org/publications/standards-store/) / public AESTD1008 | Separate documents; the public 2021 TD1008 examples include −18 assorted/speech, −16 track-normalized music and −14 album-loudest-track | Public TD1008 recommends no more than −1 dBTP at lossy codec input | Industry guidance for distributors, not a promise that every consumer service implements it | | [EBU R 128 S2 v3](https://tech.ebu.ch/docs/r/r128s2.pdf) | −23 LUFS with correct metadata; −20 to −16 is a conditional interim range, not a general target (see the v3 footnote below) | Device-side true-peak limiting where a higher playback target leaves insufficient headroom | Broadcaster streaming and reproduction strategy | ![Spotify, Apple Music and YouTube loudness documentation status with published and unpublished LUFS guidance](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/08/platform-status-map.webp) Spotify publishes numeric music-playback levels. Apple documents Sound Check without a public consumer LUFS target. YouTube’s current encoding page does not publish a −14 LUFS upload target. ## Master, upload, distribution and playback are different stages Start by naming the stage attached to a number. Your master might measure −10 LUFS. A distributor may store that file unchanged, write loudness metadata, or calculate a gain offset. The player may then apply that offset, ignore it, offer several normalization modes or change behavior by device. ![Four-stage loudness chain from master and upload through distribution metadata to device playback](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/08/loudness-pipeline.webp) A single LUFS value cannot describe the master, delivery file, distribution process and listener playback at the same time. Spotify measures loudness at upload and applies normalization during playback, including compressed and lossless formats. Its Normal reference is −14 LUFS under ITU 1770\. The same artist-support page leaves the web player and third-party devices such as TVs or speakers out of normalization, so don't expect identical playback everywhere. Apple’s current Sound Check support page describes the feature without a numeric target: Sound Check adjusts loudness between songs so they play at a similar volume. That backs up the statement “Apple Music can normalize playback.” It gives no support at all to “Apple rejects anything that is not −16 LUFS.” The cited YouTube encoding page carries a notice limiting its features to Studio Content Manager partners. It lists stereo, stereo plus 5.1 and stereo plus Eclipsa Audio, with 48 kHz audio and AAC-LC, Opus or Eclipsa codecs. That's all this format summary covers; it doesn't say every ordinary upload has to be stereo only. ## What Spotify’s −14 LUFS number does—and does not—mean On Spotify’s Normal setting, a −9 LUFS track needs roughly −5 dB of playback gain to land near −14 LUFS. A −14 LUFS track needs no loudness gain move. A −18 LUFS track could theoretically receive up to +4 dB, but available headroom can prevent the full lift. ![Loud, matched and quiet masters showing Spotify-style gain changes toward minus 14 LUFS with true-peak headroom](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/08/normalization-gain.webp) Normalization changes playback gain, not the balance, compression or distortion already printed into the master. Spotify states that louder material is turned down without adding distortion. For softer material, it considers headroom and leaves 1 dB for lossy encoding; its example stops a −20 LUFS file with a −5 dBFS true peak at −16 LUFS rather than forcing it to −14\. Premium users can also select Loud at −11 or Quiet at −19 LUFS. Loud mode uses a limiter, while the web player and some third-party playback paths remain exceptions. So the lesson isn't “master everything at −14.” A dynamic master below −14 may stay under the nominal target when positive gain would run out of headroom, and a dense master above −14 usually gets turned down. Neither outcome fixes an over-limited mix. Album example: say a quiet interlude sits 6 LU below the next track on purpose. Spotify describes one shared gain adjustment during album playback, which keeps that gap intact. In shuffle or a mixed playlist it adjusts tracks individually, so the relationship can change. Compare both paths before you touch the interlude, and don't normalize every album track separately just to make the meter line up. ## Apple Music and YouTube: document the unknowns ### Apple Music Apple documents that Sound Check can match playback loudness and can keep album relationships intact. Its [Apple Digital Masters technology brief](https://www.apple.com/vn/apple-music/apple-digital-masters/docs/apple-digital-masters.pdf) recommends leaving at least 1 dB of headroom, avoiding clipping and auditioning the AAC encode. That headroom advice isn't a published numeric Sound Check target. Apple also treats loudness as a creative decision, so use the encode check to catch damage rather than to make every song equally dense. ### YouTube YouTube’s [Stable volume and Voice boost controls](https://support.google.com/youtube/answer/14106294?hl=en) can change a listening comparison. Stable volume balances loud and quiet passages; it is unavailable on some videos and off for YouTube Music and official music videos. Voice boost, where available on computer or TV, emphasizes dialogue and reduces background sounds; enabling it switches Stable volume off. Record these settings when comparing an upload with your master. Neither feature is an upload LUFS requirement. ## Where AES77 and EBU R 128 S2 fit [ITU-R BS.1770-5](https://www.itu.int/rec/R-REC-BS.1770-5-202311-I/en) defines how program loudness and true peak are measured. It doesn’t choose one creative master level for Spotify, Apple Music and YouTube; AES and EBU documents build distribution strategies on top of those measurements. The AES catalog lists AES77-2023 as a recommended practice for internet streaming and on-demand distribution. The examples below come from its separately published 2021 technical predecessor, not an independent review of every clause in the paid standard. The freely available [AESTD1008 technical document](https://aes.org/wp-content/uploads/2024/01/20210924%5FTD1008%5Fv3.13.pdf) covers audio-only distribution, not sound accompanying video. Its examples show why a single number is inadequate: its table distinguishes assorted speech-anchored content at −18 LUFS, track-normalized music at −16 and album-loudest-track normalization at −14\. It also recommends a maximum true peak no higher than −1 dBTP at the input to a lossy codec. EBU R 128 S2 v3 recommends streaming −23 LUFS programs unchanged with correct loudness metadata. Without that metadata, it describes an interim −20 to −16 LUFS range for when the broadcaster wants to control dynamic treatment. But page 4, footnote 2 says revised device standards now make it possible to treat streaming like broadcast, so the higher range shouldn't be presented as the default. This is a broadcaster's distribution strategy. It doesn't require every independent music master to measure −23 LUFS. ## True peak is the second half of the decision Integrated LUFS tells you the measured program loudness. [True peak estimates reconstructed peaks between samples](https://soundforgepro.com/true-peak-explained/). A gain move that raises loudness also raises true peak by roughly the same amount until a limiter intervenes. Spotify’s current mastering guidance says to keep a −14 LUFS master below −1 dBTP and a louder master below −2 dBTP because louder material is more susceptible to distortion after encoding. AES TD1008 recommends no more than −1 dBTP at the lossy codec input. These are defensible references, but the written destination specification still wins. ![Browser LUFS meter with the Spotify Normal reference selected, reading −23.0 LUFS integrated and −18.0 dBTP estimated true peak with a +9.0 dB gain comparison](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/10/lufs-meter-results-real-1-v20261006.webp) Measure Integrated LUFS and true peak together. The meter result describes the file; it does not tell you which platform rule applies. The [SoundForgePro LUFS Meter](https://soundforgepro.com/lufs-meter/) measures local audio without uploading it. The current browser tool accepts mono or stereo files up to 20 minutes and 200 MiB. For a longer program, measure the complete file with a desktop meter, and don't average LUFS readings from separate chunks. It's a practical pre-check. A meter or measurement mode named in a contract still takes priority. ## A six-step streaming loudness workflow ### 1\. Name the exact destination and content type Music track, album, [podcast](https://soundforgepro.com/podcast-loudness-standard/), live stream and video each count as a different delivery class. Note the platform, distributor, client and intended player path. ### 2\. Save an unconstrained archive master Keep the best lossless version before any destination-specific gain, codec or limiter changes, and keep its native resolution: Apple explicitly advises against upsampling or padding a 16-bit file to 24-bit to claim a higher-resolution source. Spotify says one high-quality stereo master per track covers its compressed and lossless playback, so you don't need a separate master for every playback format. ### 3\. Measure the complete program Reset the meter, play the full file and record Integrated LUFS, maximum true peak and channel layout. For an album, preserve the intended relationship between tracks. ### 4\. Simulate the likely gain move Subtract measured loudness from the documented reference, then add that gain to the measured true peak. A −18 LUFS file with a −3 dBTP maximum, for example, needs +4 dB to reach −14 LUFS, which predicts +1 dBTP. With a −1 dBTP ceiling, only +2 dB fits without peak control. If the destination really does require both targets, fix the offending peaks or dynamics and measure the full file again before encoding. If the number is only a playback reference, don't force the master to hit it. ### 5\. Encode the actual delivery file Use the current codec, sample rate and channel requirements. If you need a gain correction in Sound Forge, the [Peak, RMS and LUFS normalization workflow](https://soundforgepro.com/how-to-normalize-audio-in-sound-forge-pro/) separates a constant gain move from dynamics processing. ### 6\. Reopen, remeasure and audition Check the encoded file as well as the lossless session. Listen to the loudest transient, a quiet passage, the opening and the ending. Where a platform offers a preview or unlisted upload, compare that playback too, keeping in mind that one device doesn't speak for all of them. For Sound Forge’s own meter routes and reset sequence, use the [Sound Forge LUFS and true-peak guide](https://soundforgepro.com/sound-forge-loudness-meters/). That tool-specific page covers the interface; the cross-platform decision lives here. ## Streaming loudness standards FAQ ### Is −14 LUFS the standard for every streaming service? No. Spotify publishes −14 LUFS for its Normal music-playback setting, but other services document different behavior or do not publish one public numeric target. An upload requirement, distribution recommendation and playback target are not the same thing. ### Does Spotify reject music that is not −14 LUFS? Spotify’s current documentation describes measuring files during upload and applying gain during playback. Louder masters are normally turned down; softer masters may be raised only as far as headroom allows. That is not a simple −14 LUFS rejection gate. ### What LUFS target does Apple Music use? Apple publicly documents that Sound Check matches playback loudness, but its current consumer support page does not state one universal LUFS target. Follow current distributor requirements, avoid clipping and audition the encoded Apple delivery path. ### Does YouTube require −14 LUFS? The cited YouTube encoding page publishes no -14 LUFS upload requirement and carries a Content Manager partner notice. Its format recommendations include 48 kHz audio, AAC-LC/Opus/Eclipsa and stereo or specified surround combinations. Player processing, including Stable volume where available, is a separate issue. ### Should I master louder so streaming normalization turns the track down? Only if that sound is the artistic choice. Downward normalization changes gain; it does not undo clipping, limiting or lost transient contrast. Compare level-matched versions before choosing the denser master. ### What true peak should I use for streaming? There is no universal ceiling, but −1 dBTP is a common defensible starting point for lossy delivery. Spotify advises below −1 dBTP around −14 LUFS and below −2 dBTP for louder masters. A written platform, distributor or client specification overrides the general starting point. *Last fact-checked September 7, 2026 against Spotify for Artists, Apple Support and Apple Digital Masters, YouTube Help, the AES catalog and public AESTD1008, EBU R 128 S2 and ITU-R BS.1770-5.* ### Podcast Loudness Standard: LUFS, True Peak and Export Check URL: https://soundforgepro.com/podcast-loudness-standard/ Last updated: 2026-10-09T20:58:38.000Z **If you need one practical starting point, finish a stereo podcast near −16 LUFS integrated and keep true peak at or below −1 dBTP.** For a mono file, −19 LUFS is a common dual-mono convention rather than a universal upload rule. The platform or client specification still wins. That distinction is the part most loudness charts blur. [Apple Podcasts currently recommends](https://podcasters.apple.com/support/893-audio-requirements) overall loudness around −16 dB LKFS with a ±1 dB tolerance and a true-peak value that does not exceed −1 dB FS. Spotify’s public [−14 LUFS documentation](https://support.spotify.com/bi-en/artists/article/loudness-normalization/) describes music playback normalization and mastering guidance; it isn't proof that every podcast file must be delivered at −14 LUFS. ## Podcast loudness targets at a glance Swipe horizontally to compare every column → | Destination or workflow | Integrated loudness | True peak | What the number means | | -------------------------------------------------------------------------------------------------------------------- | ---------------------- | --------------------------- | -------------------------------------------------------------------- | | Apple Podcasts recommendation | Around −16 LKFS, ±1 dB | Does not exceed −1 dB FS | Documented preparation guidance for podcast audio | | Common stereo podcast start | −16 LUFS | At or below −1 dBTP | Widely used convention; confirm the host or client brief | | Common mono dual-mono convention | −19 LUFS | At or below −1 dBTP | Three LU lower than the stereo convention; playback handling matters | | [PRX recommendation](https://help.prx.org/hc/en-us/articles/360022234293-How-should-I-format-my-podcast-audio-files) | −16 to −19 LUFS | Follow the production brief | PRX explicitly says there is no single set industry standard | These aren't four competing truths. Apple publishes a platform recommendation, PRX publishes a working range, and the −16/−19 pair is a production convention built around channel playback. None of them turns a poor mix into a compliant episode merely because the integrated number lands on target. ![Mono minus 19 LUFS and stereo minus 16 LUFS podcast loudness conventions with dual-mono playback paths](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/08/mono-stereo-loudness.webp) −19 LUFS mono and −16 LUFS stereo are common starting conventions. They do not override a platform or client delivery specification. ## There is no single enforced podcast loudness standard Podcast delivery is less uniform than broadcast delivery. A host may publish a recommendation, a network may provide a production sheet, and a player may apply its own optional playback processing. Those are three different things. Apple’s current page is unusually specific: around −16 dB LKFS, ±1 dB, with the true peak kept at or below its stated ceiling and measured under ITU-R BS.1770-5\. Apple also accepts both mono and stereo MP3 for subscriber audio and RSS distribution. Its page doesn't say that every mono RSS file must be −19 LUFS. [For music playback, our streaming loudness comparison](https://soundforgepro.com/streaming-loudness-standards/) explains Spotify’s Normal, Loud and Quiet settings and the exceptions for web players and third-party devices. The official music guidance linked above is the source for those settings; neither that page nor our comparison establishes a podcast-upload requirement. The practical rule is simple: label each number by its scope. Is it an upload requirement, a production recommendation, a playback reference, or just your own repeatable house target? If the source doesn't say, don't promote the number to a rule. ## Why mono is often quoted at −19 LUFS A true mono file has one measured channel. Many listeners hear it through two speakers. If the player copies the mono signal to both channels without reducing each by about 3 dB, the common −19 LUFS mono convention compensates for that extra combined power relative to a −16 LUFS stereo target. This is a channel-playback convention, not a guarantee of equal loudness on every device. The catch is implementation. [Auphonic’s technical explanation](https://auphonic.com/blog/2020/06/09/loudness-normalization-mono-productions/) notes that playback devices do not all apply the expected dual-mono offset consistently. That is why “mono always equals −19” is too confident. - If the client says −19 LUFS mono, deliver −19 and document the measurement. - If the host says around −16 LKFS for all podcast audio, do not silently substitute −19. - If no one specifies a target, choose one convention, test it on the actual player path, and keep every episode consistent. Duplicating one mono channel into identical left and right channels also changes what the file is. A two-channel dual-mono export is stereo as far as many encoders and meters are concerned, even though the content is the same in both channels. Check the delivered file rather than the session label. ## Read Integrated LUFS and true peak together [ITU-R BS.1770-5](https://www.itu.int/rec/R-REC-BS.1770-5-202311-I/en) defines measurement algorithms for program loudness and true-peak signal level. It doesn't tell every podcast where to land; it makes measurements comparable. LUFS and LKFS name the same loudness scale; no conversion is needed when the measurement method, channel layout and measured region are the same. LU expresses a difference: moving from −20 to −16 LUFS is a rise of 4 LU. These are digital program measurements, not sound-pressure readings at the listener’s ears. - **Integrated LUFS (I)** accumulates the gated loudness of the measured program. Reset the meter and measure the complete episode or the exact program region named by the brief. - [**True peak (dBTP)**](https://soundforgepro.com/true-peak-explained/) estimates peaks in the reconstructed signal, including values between stored samples. Compare that measured maximum with the delivery ceiling; it is not an average-loudness target. - **Short-term loudness (S)** uses a three-second window in EBU Mode and helps locate passages that jump forward or disappear. - **Momentary loudness (M)** uses a 400 ms window. These windows follow the definitions in [EBU Tech 3341](https://tech.ebu.ch/docs/tech/tech3341.pdf); momentary loudness reacts quickly enough to diagnose individual phrases. - **Loudness range (LRA)** describes gated variation across the program. There is no universal “good podcast LRA” that replaces listening. A file can pass integrated loudness and still be hard to follow. One painfully loud intro and several quiet interviews may average to the requested LUFS. The meter reports the program; it won't edit the conversation for you. ![Browser LUFS meter with a custom −16 LUFS target and −1 dBTP ceiling, reading −23.0 LUFS integrated and −18.0 dBTP true peak with a +7.0 dB gain comparison](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/10/lufs-meter-results-real-v20261006.webp) Measure the complete finished file, then read Integrated LUFS and true peak together. The browser meter is a practical pre-check, not a substitute for a required certified meter. You can [measure a local file in the SoundForgePro LUFS Meter](https://soundforgepro.com/lufs-meter/); the audio stays on the device. Use it for editorial and delivery pre-checks. If a broadcaster, network or contract requires a certified measurement path, use the specified conforming tool. The current browser tool accepts mono or stereo files up to 20 minutes and 200 MiB. For a longer episode, use a desktop meter on the complete delivery file; do not average LUFS readings from separate chunks. ## Normalization does not fix uneven dialogue Constant-gain loudness normalization moves a measured program toward a target without changing its internal dynamics. Some automatic normalization tools also apply limiting or other processing; check their options. If an episode measures −20 LUFS and the target is −16, a first estimate is +4 dB. For an unclipped linear gain change, true peak rises by the same 4 dB. If the original true peak is −3 dBTP, that predicts +1 dBTP—2 dB above a −1 dBTP ceiling. Only +2 dB fits under that ceiling without peak control, leaving the loudness near −18 LUFS. Constant gain alone cannot satisfy both targets; fix the peaks or dynamics and measure again. Repeating a clean gain calculation is not inherently destructive. Repeated lossy exports, clipping or additional dynamics processing can be. If the target and peak ceiling conflict, return to the lossless working master and address that conflict instead of repeatedly encoding the episode. 1. Use clip gain or automation to correct isolated speakers and phrases. 2. Use compression only as much as needed to narrow uncomfortable level swings. 3. Apply the required loudness gain before a final true-peak limiter, or use a coordinated loudness/peak process. Adding positive gain after a limiter raises its output above the previous ceiling. 4. Measure integrated loudness and true peak again after that processing. 5. If either result fails, revise the gain/dynamics settings and remeasure both; do not approve an unmeasured final gain move. If you work in Sound Forge, the [Peak, RMS and LUFS normalization guide](https://soundforgepro.com/how-to-normalize-audio-in-sound-forge-pro/) separates a constant gain move from compression and limiting. For the full edit before this stage, use the [Sound Forge podcast workflow](https://soundforgepro.com/sound-forge-pro-for-podcasters/). ## Five steps from finished edit to delivery file ![Five-stage podcast loudness workflow from editing through post-encode remeasurement](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/08/final-file-workflow.webp) Edit, control dynamics, measure the full program, encode the delivery file, then reopen and measure that file again. ### 1\. Finish the editorial and restoration work Do not set final loudness while cuts, noise reduction or music balances are still changing. Every material edit invalidates the measurement. ### 2\. Control the internal level differences Listen to the quietest usable sentence, the loudest sentence, the intro and any inserted ad or music. Fix the distracting differences before chasing an integrated number. ### 3\. Reset and measure the full program Include the exact start, silence, credits and tail that will be delivered. Compare Integrated LUFS and true peak with the chosen delivery specification. If either fails, adjust gain or dynamics on the lossless working copy as described above, then reset and measure the complete program again. Encode only after both checks pass. ### 4\. Encode the actual delivery file Keep a lossless archive master. Create the MP3 or AAC using the host’s current channel, sample-rate and bitrate requirements. Apple’s current RSS guidance accepts MP3 or AAC and recommends AAC in an MP4 container for efficient streaming and accurate seeking. ### 5\. Reopen, remeasure and listen Lossy encoding can change reconstructed peak behavior. Measure the uploaded-format file, then audition the opening, the loudest passage, a quiet dialogue section and the end. The file you send is the file that must pass. ## Four loudness mistakes that survive a green meter ### Measuring only the loudest minute That gives a useful short diagnostic rather than the integrated result of a 45-minute episode. Reset and run the complete program. ### Using peak normalization as loudness matching Two files can share the same sample peak and sound radically different. Peak normalization sets the highest sample amplitude; it doesn't equalize perceived program loudness. ### Treating playback normalization as an upload gate A player may turn material down, leave it unchanged, or behave differently by device and listener setting. Playback references aren't automatically delivery specifications. ### Checking the WAV but not the MP3 or AAC The archive master is not what the listener downloads. Reopen the encoded file and verify it after the codec. ## Podcast loudness FAQ ### What is the standard LUFS for a podcast? −16 LUFS integrated for stereo is the most useful general starting point, usually paired with a true-peak ceiling around −1 dBTP. It is a convention and, in Apple’s case, close to a documented platform recommendation—not one universally enforced upload rule. ### Should a mono podcast be −19 LUFS? −19 LUFS is a common dual-mono convention because it sits 3 LU below the familiar −16 stereo target. Use it when the host or client asks for it, or when your tested playback workflow expects the offset. Do not override a written −16 specification merely because the file is mono. ### Does Spotify require podcasts at −14 LUFS? Spotify’s current public −14 LUFS page documents music playback normalization and artist mastering guidance. It does not establish a universal −14 LUFS podcast-upload requirement. Follow the podcast host or production brief and label Spotify’s number by its actual scope. ### What true peak should a podcast use? −1 dBTP is a practical common ceiling and aligns closely with Apple’s current podcast guidance. A stricter client specification wins. True peak is a maximum reconstructed peak, not the episode’s average volume. ### Can loudness normalization replace compression? Constant-gain normalization cannot replace compression: it changes overall gain without evening out speakers or phrases. Some normalization tools include a limiter or leveler, so inspect the enabled processing. If peaks prevent the gain move from reaching the target, control those peaks and remeasure both loudness and true peak. ### Should I measure before or after exporting? Both. Measure the lossless master to approve the mix, then reopen and measure the encoded delivery file because MP3 or AAC processing can change peak behavior. *Last fact-checked September 7, 2026 against Apple Podcasts for Creators, Spotify Support, ITU-R BS.1770-5, EBU metering guidance, PRX and Auphonic technical guidance.* ### Free Online LUFS Meter: Loudness & True Peak URL: https://soundforgepro.com/lufs-meter/ Last updated: 2026-10-10T13:19:10.000Z Drop a finished WAV or another browser-decodable audio file into the meter below. The meter analyzes decoded audio on this device without uploading your file or sending its name or readings to analytics. Reset clears the selected file and results. Site analytics may still record ordinary page visits. The four useful numbers are integrated loudness, loudness range, estimated true peak and sample peak. Read them together: a single LUFS value can’t tell you whether the file will cross a peak ceiling, and a peak reading says nothing about how loud the whole program feels. Browser tool · local analysis ## Measure audio loudness locally Your audio stays on this device. The page does not upload the file or send its name and readings to analytics. **Drop an audio file here** or press Enter to choose one · mono or stereo · up to 200 MiB and 20 minutes Formats depend on your browser's decoder. WAV is the safest choice for a final check. Reset or Escape cancels the result; native decoding cannot always stop immediately. Analysis times out after 120 seconds. The limits are not a mobile-memory guarantee: compressed files can expand substantially when decoded. If decoding fails, close unneeded apps or use a desktop editor; an unsupported file has no valid reading. Reference Spotify Normal reference EBU R128 broadcast ATSC numeric reference Custom Target LUFS/LKFS Peak ceiling dBTP Analyze file Reset Integrated loudness**N/A**LUFS · gated full-file reading Estimated true peak**N/A**dBTP · 4× polyphase pre-check Loudness range**N/A**LU · shown for files of 1 minute or longer Sample peak**N/A**dBFS · highest decoded sample Estimated gain, not a guaranteed peak-safe result. True peak under-read by about 0.43 dB in one retained test; that is not a maximum error bound. Remeasure the processed and encoded delivery file in a conforming meter. All readings describe browser-decoded audio, which may be resampled. This is a practical browser pre-check, not a certification meter. Our deterministic tests matched FFmpeg's integrated loudness within 0.1 LU; the true-peak estimate can read about 0.4 dB lower on difficult broadband material. Verify regulated or final delivery in a conforming production meter. ## How to measure LUFS without uploading the file 1. **Choose a mono or stereo file.** PCM WAV is the safest final-check format; compressed formats work only when your browser can decode them. 2. **Select a reference.** Use a numeric reference or the recipient’s specified values. The ATSC preset does not add dialogue gating or certify A/85 compliance; the measurement remains gated full-program loudness. 3. **Press Analyze file.** The browser decodes the full program and runs the loudness calculation in a local worker. 4. **Read the gain plan.** If the LUFS target needs more gain than the peak ceiling allows, the meter says so instead of pretending that normalization is a one-number fix. ## Read the four numbers in this order | Reading | What it answers | What it does not answer | | ------------------------- | ------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Integrated LUFS | How loud the complete gated program measures | Whether inter-sample peaks cross a delivery ceiling | | Estimated true peak, dBTP | How high the reconstructed waveform may rise between stored samples | Whether the track is dynamically healthy or musically balanced | | Loudness range, LU | How widely short-term loudness varies across the program | Whether a particular genre “should” be more or less dynamic. EBU R128 does not recommend LRA for programs shorter than one minute because there are too few short-term data points. | | Sample peak, dBFS | The highest amplitude in the browser-decoded samples | The original stored-sample peak when decoding has resampled the file, or the peak of a later encoded delivery | ### Momentary vs Short-Term vs Integrated vs LRA These readings answer different questions, so do not judge the file from one number alone. | Reading | Time span | What it tells you | | ------------------ | ---------------------------------------------- | ------------------------------------------------------------------------------------------- | | Momentary maximum | Loudest rolling 400 ms window | The strongest brief burst in the file. It is not the loudness target for the whole program. | | Short-Term maximum | Loudest rolling 3-second window | The loudest sustained passage, useful for finding a section that stands above the rest. | | Integrated LUFS | From measurement start to stop | Overall gated program loudness. On this page, that means the complete selected file. | | LRA | Gated Short-Term values across the measurement | How widely program loudness varies. It is measured in LU, not LUFS. | **Do not compare unlike numbers.** This meter reports the maximum Momentary and Short-Term values found in the file, not live moving readings. An LRA of 7 LU and a target of −14 LUFS answer different questions. The measurement follows the gated program-loudness method described in [ITU-R BS.1770-5](https://www.itu.int/dms%5Fpubrec/itu-r/rec/bs/R-REC-BS.1770-5-202311-I!!PDF-E.pdf): K-weighted energy is measured in overlapping blocks, then very quiet material is excluded by absolute and relative gates. That is why long silence at the head or tail does not simply drag the integrated result down like an ordinary average. **Compare the same decode and channel mode.** The browser’s [decodeAudioData method resamples audio to the AudioContext rate](https://developer.mozilla.org/en-US/docs/Web/API/BaseAudioContext/decodeAudioData). The footer reports that decoded rate, not necessarily the original file rate. Sample peak therefore means decoded-sample peak here, and all readings can differ from a native-rate desktop scan. Mono is measured as one channel, without dual-mono compensation. Duplicating identical audio into two channels raises its loudness reading by about 3.01 LU; opposite polarity does not cancel energy in this meter. Match the [channel and peak settings of your reference meter](https://ffmpeg.org/ffmpeg-filters.html#ebur128-1) before comparing. Integrated loudness requires a complete 400 ms block. Momentary and short-term maxima use 400 ms and 3-second windows sampled every 100 ms. The final incomplete block is omitted. LRA uses gated short-term values with a 1.5-second zero tail for file analysis, as described in [EBU Tech 3342](https://tech.ebu.ch/docs/tech/tech3342.pdf). This interface hides LRA below one minute. Silence or an empty loudness gate has no finite integrated value; N/A is not a loudness target. ![LUFS meter results for a 28-second mono WAV: −23.0 LUFS integrated, −18.0 dBTP estimated true peak, −18.0 dBFS sample peak, loudness range N/A](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/10/lufs-meter-results-real-v1-v20261006.webp) A 28-second file still gets integrated loudness, estimated true peak and sample peak readings; loudness range stays N/A because this meter reports LRA only for files of one minute or longer. ## A target is a reference, not a grade Choose the recipient’s reference rather than treating a preset as an approval badge. These presets change only two numbers; they do not select a different measurement algorithm. For spoken-word delivery, use the publisher's or host's stated target instead of borrowing a music or broadcast preset; the [podcast loudness standard](https://soundforgepro.com/podcast-loudness-standard/) guide covers common stereo and mono targets, true-peak checks, and export verification. - **Spotify Normal** is a playback-normalization reference of −14 LUFS. Spotify also advises keeping true peak below −1 dBTP for masters at or below that level and below −2 dBTP for louder masters, because lossy encoding can add peak energy. Those details are in [Spotify’s loudness-normalization guidance](https://support.spotify.com/artists/article/loudness-normalization/). - **EBU R128** uses −23 LUFS and a −1 dBTP maximum permitted true peak for linear audio during production. Distribution or codec specifications may require a lower ceiling, as explained in the [current EBU recommendation](https://tech.ebu.ch/docs/r/r128.pdf). - **ATSC A/85** uses −24 LKFS absent metadata and a −2 dBTP ceiling in its television delivery context. As of September 14, 2026, ATSC lists A/85:2026-07, approved July 8, 2026, on the [ATSC A/85 technical page](https://www.atsc.org/atsc-documents/a85-techniques-for-establishing-and-maintaining-audio-loudness-for-digital-television/). LUFS and LKFS name the same unit, but the measurement method still matters. A/85 differentiates long-form dialogue measurement from short-form full-program measurement. This tool does not detect dialogue or classify content; its ATSC preset changes only the reference numbers and is not an A/85 compliance result. None of those numbers can decide how much compression, limiting or musical density a master needs. Spotify also recommends −14 integrated LUFS in its mastering tips, but that is not a universal requirement for every service or release. Its web player and some third-party devices do not apply normalization; listener settings and album playback can also change the outcome. ## When gain alone cannot satisfy both references Suppose a file measures −18 LUFS with an estimated true peak of −2 dBTP, and the selected reference is −14 LUFS with a −1 dBTP ceiling. Loudness asks for 4 dB of gain, while the estimated peak allows only 1 dB. These readings cannot be satisfied together by gain alone. Because the peak is an estimate, even the suggested 1 dB is not a guaranteed safe ceiling; verify the actual processed output. The remaining 3 dB needs a processing decision. The gain calculation assumes the same blocks survive the absolute loudness gate; a large level change can alter that set, so remeasure after processing. It would require a limiter, compression, clipping or a different mix decision. The meter reports that conflict but doesn’t process the file, because choosing how peaks are controlled is an audible mastering decision. ## Numerical checks and measurement limits On September 14, 2026, we reran deterministic 44.1 and 48 kHz fixtures through this worker and FFmpeg 8.1.2’s `ebur128` filter: steady tones, low-frequency weighting, broadband noise, gated dynamics, correlated and anti-phase stereo, inter-sample peaks and 65-second level changes. Separate silence and endpoint-impulse checks cover missing results and boundary samples. These are numerical tests, not listening tests or a complete ITU/EBU conformance suite. | Metric | Largest observed difference in our fixture set | How to use it | | ------------------- | -------------------------------------------------------- | --------------------------------------------------------------------------------------- | | Integrated LUFS | Within 0.1 LU | Suitable for a practical local loudness check | | Loudness range | Within 0.1 LU on the two 65-second level-change fixtures | Short clips are excluded from this comparison; the interface hides their LRA | | Estimated true peak | About 0.4 dB lower on the hardest broadband-noise case | Use as a pre-check; verify regulated or final delivery in a conforming production meter | The limits are mono or stereo, up to 200 MiB (209,715,200 bytes) and 20 minutes. Duration and channel count can be checked only after decoding. A 20-minute stereo decode at 48 kHz needs 460,800,000 bytes, about 439 MiB, for one 32-bit sample buffer alone; decoder, copies and worker overhead require more. A small compressed input may therefore exceed a phone’s available memory. It relies on the browser’s audio decoder, so extension support isn’t universal. It won’t certify a broadcast master, inspect encoded-platform output or replace listening after gain and dynamics changes. ## Check the same file in Sound Forge If Sound Forge is already in your workflow, use this browser meter as a quick independent read, then repeat the measurement in the editor before export. Our [Sound Forge LUFS, R128 and true-peak guide](https://soundforgepro.com/sound-forge-loudness-meters/) shows the current Channel Meters, separate Loudness Meters window, EBU/ATSC presets and loudness-log route. Use this page for a local file reading. Use the Sound Forge guide when you need the editor’s monitoring, presets or loudness-log workflow. For another local measurement task, use the [audio tools directory](https://soundforgepro.com/tag/audio-tools/). For gain and dynamics decisions after measuring, continue with the [mastering guides](https://soundforgepro.com/tag/mastering/). ## Frequently asked questions ### Is my audio uploaded to SoundForgePro? No. The browser reads and decodes the selected file locally. The tool does not send the audio, filename or measured values to our server or analytics. ### Which file formats does the LUFS meter support? It supports audio formats your browser can decode. PCM WAV is the most dependable choice; MP3, AAC/M4A, OGG, FLAC and AIFF availability can differ by browser and operating system. ### What is the difference between LUFS and dBTP? Integrated LUFS describes gated program loudness over time. dBTP describes the estimated highest reconstructed peak between samples. One is a loudness measure; the other is a peak-safety measure. ### Should every song be mastered to −14 LUFS? No. −14 LUFS is Spotify’s Normal playback reference, not a universal mastering instruction. Musical density, dynamics, genre, release context and true-peak headroom still require judgment. ### Why can true peak be higher than sample peak? A digital-to-analog or lossy-codec reconstruction can form a waveform crest between stored samples. Oversampled true-peak estimation looks between those sample points; an ordinary sample-peak meter does not. ### Can this tool normalize or download a corrected file? No. It measures and calculates a peak-aware gain plan but does not alter the audio. Limiting or compression is an audible decision that should be made in an editor or mastering chain and checked again afterward. ### Audio Restoration: Diagnose and Repair Damaged Audio URL: https://soundforgepro.com/audio-restoration/ Last updated: 2026-10-08T22:33:16.000Z **Quick answer:** audio restoration starts with diagnosis. A preset comes later, if at all. Play the file in another app and through another output before you edit anything. A fault that repeats at the same timestamp across independent playback paths points toward the recording or encoded file; one that changes with the player, driver, cable or device usually belongs to playback. Work on a copy only once you know which problem you're dealing with. This guide is a fault map rather than a plug-in tour. Read the waveform, spectrum and timing together, then route each symptom to the narrowest repair that can solve it. No processor can guarantee the exact samples that were never captured, were overwritten or were discarded by a codec. ![Waveform and spectrum of one recording with four marked faults, hum, clicks, clipping and a room tail, each routed to its first repair test](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/10/editor-triage-v2-v20261006.webp) Four faults, four traces: hum runs as a steady low line, clicks as thin vertical streaks, clipping as flat-topped blocks and a room tail as a fading decay. ## What Audio Restoration Means Audio restoration is the controlled reduction or reconstruction of unwanted changes in a recording while preserving as much of the wanted performance as possible. Typical targets include hiss, mains hum, clicks, crackle, clipping, dropouts, wow and flutter, room reflections and damage from lossy encoding. The goal is not “zero noise.” The goal is a more usable recording without distracting repair artifacts. That definition matters because three very different problems are often grouped under *audio repair*: 1. **Signal damage:** the file opens and plays, but the sound contains noise, distortion, missing moments or unwanted acoustics. Restoration tools can help. 2. **File or container damage:** the player cannot open, seek or decode the file, or the recording ends unexpectedly. Header repair, recovery software, remuxing or another source comes before audio processing. 3. **Playback-chain trouble:** the same file is clean on one device and faulty on another. The driver, interface, cable, enhancement, clocking or loudspeaker needs attention. Editing the file would bake in a needless change. Missing information is a limit within signal repair, not a separate fault category. If silence overwrote a word, a clipped converter discarded the original peak shape or a codec removed upper-band data, software can estimate, mask or synthesize a plausible result. What it can't do is pull the exact original samples out of nowhere. ## Diagnose Damaged Audio Before You Process It Save the original, make a short working copy, and mark the exact timestamp where the defect is obvious. Then run the cheapest tests first: | Symptom | Diagnostic check | Likely class | First move | | -------------------------------------------------------- | --------------------------------------------------------------------- | ------------------------------- | ------------------------------------------------------------------------------------------ | | The same fault occurs at the same timestamp everywhere | Two players and two outputs agree | Recorded signal or encoded file | Inspect waveform, spectrum and source history | | The file will not open, seek or reach its expected end | A media probe reports a header, index or decode error | Container or data recovery | Preserve the source; recover a readable copy before signal processing | | Only one app or device crackles | A second path is clean | Playback chain | Bypass enhancements; check driver, format and hardware | | A steady pitch remains under speech or music | The spectrogram shows horizontal lines at a fundamental and harmonics | Hum or whine | Find the fundamental; use narrow reduction before broad denoise | | Needle-like ticks occur at isolated moments | The waveform shows short discontinuities or impulses | Clicks and pops | Repair locally before running a full-file de-click pass | | Loud moments have repeated flat shelves | Sample-level zoom shows values held at the same ceiling | Possible clipping or limiting | Check source history and float headroom; test declipping only if peak information was lost | | Words smear into their pauses | Reflections continue after the direct voice | Room reverb or echo | Decide whether tail control is enough or dedicated de-reverb is required | | The WAV is clean but a small delivery file sounds watery | One encode changes the upper spectrum and transients | Lossy codec damage | Return to the lossless master and encode once | Change one variable at a time. Switch the driver, sample rate and output device together and the problem may disappear, but you won't know which stage failed. A useful diagnosis predicts what the next test will do. ## Read the Waveform, Spectrum and Timing Together A waveform is best at showing level over time. Use it to locate discontinuities, repeated flat shelves, DC offset, dropouts and the envelope of a reverb tail. It's poor at telling a 60 Hz hum from low musical content, though, because both can look like ordinary oscillation at a wide zoom. A spectrogram adds frequency. Stable electrical hum can form horizontal lines at a fundamental and its harmonics; short clicks often spread vertically across many frequencies. Steady hiss raises a broader noise floor, but its spectral shape need not be flat. A lossy codec may remove or rearrange upper-band energy, and reflections extend energy after the direct sound. Display settings and wanted musical content can resemble these patterns. Use them to choose a test, not to set processing strength automatically. Timing is the third clue. A fault attached to edit boundaries suggests discontinuities. Distortion that follows only loud vowels or drum hits points to overload, and crackle that changes between playbacks usually means a real-time driver or buffer problem. A constant line at 60 Hz in North American material or 50 Hz in many other power systems supports mains hum, but check harmonics and local context before cutting a musical note that happens to share the frequency. Meter readings support a diagnosis; they do not decide it alone. Crest factor can be calculated from compatible peak and RMS readings over the same selection; do not assume it is a dedicated Statistics field. Sample peak, true peak, RMS, loudness, DC offset and crest factor each answer a different question. Our [Sound Forge Statistics guide](https://soundforgepro.com/how-to-use-statistics-sound-forge-pro/) explains what each reading can and cannot prove. ## Choose a Repair Order, Then Test It ![Audio restoration order from diagnosis and confirmed clipping through local repair, noise control and verified export](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/08/restoration-order-desktop.webp) Confirm the fault, handle true clipping before later processing, then keep every repair reversible and verify the export. 1. Copy the source. Preserve the original file and its metadata. Never make the only copy your experiment. 2. Verify playback and channels. Test another app and output to separate recording defects from playback faults. Check left/right balance and mono compatibility; do not change polarity or sum channels simply because the waveform looks asymmetric. 3. Test confirmed clipping early. First lower gain if a floating-point source still retains intact peaks above 0 dBFS. If peak information was actually clipped, try conservative declipping before later processing reshapes it. Compare with the unchanged copy. 4. Fix isolated faults. Treat short clicks or gaps locally when useful surrounding sound remains. Check that interpolation preserves consonants and attacks. Correct measured DC offset separately; it is not click repair. 5. Compare noise-reduction orders. Hum often comes first when its fundamental and harmonics dominate. If broadband noise hides the tone, test broadband reduction first. Compare both orders on a short passage instead of applying a fixed full-file chain. 6. Test difficult reconstruction separately. De-reverb and codec-artifact mitigation estimate overlapped or discarded information. Compare them with the simpler repair, and also test another position in the chain if needed. Reject changes that damage wanted speech or music. 7. Set level and verify the export. Compare at matched playback loudness, disable Inverse/Delta/noise-only monitoring, and render a new lossless file. Reopen it outside the editor and check the repaired passage, transitions and ending. That sequence is a starting point, not a mandatory recipe. [iZotope’s repair-order walkthrough](https://www.izotope.com/community/blog/order-of-audio-repair-operations) puts deep clipping damage early but explains why source conditions can change the order. After each stage, compare bypassed and processed playback at matched loudness. If a difference monitor is available, check its definition: a removed-noise signal and all changed signal are not the same thing. Reconstructed peaks can legitimately appear in a difference signal. Judge the normal output, then turn off diagnostic monitoring before rendering. ## Route Each Fault to the Right Repair ### Steady hum, whine and broadband hiss When tonal hum dominates, begin there. If broadband noise prevents reliable hum detection, compare the reverse order. A 60 Hz fundamental may have 120 and 180 Hz harmonics; 50 Hz interference may have 100 and 150 Hz companions. Narrow notches or de-hum can spare more of the spectrum than broad noise reduction, but they can still cut wanted bass notes. For profile-based hiss reduction, select noise without speech or music, as [Audacity’s noise-reduction guidance](https://manual.audacityteam.org/man/noise%5Freduction.html) explains; adaptive methods work differently. The [hiss and hum workflow](https://soundforgepro.com/remove-hiss-hum-sound-forge/) separates tonal and broadband faults, while the [background-noise guide](https://soundforgepro.com/how-to-remove-background-noise-in-sound-forge-pro/) covers profile selection and artifact checks. ### Clicks, pops and crackle A very short isolated click may respond to interpolation when clean material surrounds it. Larger gaps and dense crackle need different treatment; a sensitive full-file pass can mistake percussion and consonants for damage. Start with the biggest isolated events, then compare a conservative automatic pass with the unchanged copy. The [clicks-and-pops guide](https://soundforgepro.com/how-to-remove-clicks-pops-sound-forge-pro/) covers that local-first workflow. For [mouth clicks in spoken voice](https://soundforgepro.com/remove-mouth-clicks-from-audio/), distinguish the lip or saliva sound from wanted articulation before processing. ### Hard clipping and upstream overload First identify where overload happened. A floating-point file may retain intact peaks above 0 dBFS; lowering gain can reveal them, but cannot undo clipping that occurred earlier. Lowering an already clipped signal only makes its distortion quieter. Flat shelves are a clue, not proof by themselves: limiting and the source waveform also matter. The current [Sound Forge DeClipper help](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/proonly/declipper.htm) describes interpolation from surrounding material, not guaranteed recovery of the lost original. Follow the [clipping-repair guide](https://soundforgepro.com/fix-clipped-audio-sound-forge/) for inspection and matched comparisons. For harshness without clear clipping, [diagnose distorted audio](https://soundforgepro.com/fix-distorted-audio/) across input, processing, codec and playback stages. ### Room echo and reverberation A gate can reduce exposed tails between phrases, and EQ can tame resonant buildup. Neither separates direct speech from reflections that overlap the words. Dedicated de-reverberation may reduce that overlap, with possible modulation or damaged consonants at aggressive settings. The [echo and room-reflection guide](https://soundforgepro.com/remove-echo-from-audio/) separates manual tail control from true de-reverb and shows where a gate stops helping. ### Lossy codec artifacts Return to the highest-quality source. If a WAV or earlier master exists, don't “restore” the MP3 and then encode it again. Missing high frequencies won't reappear through normalization or EQ; an enhancer may create plausible brightness, but that's synthesis, not recovery. Keep one lossless master and create each delivery format once. The [MP3 export guide](https://soundforgepro.com/how-to-export-mp3-from-sound-forge-pro/) covers bitrate and verification without treating lossy delivery as an archive format. ### Vinyl, tape, speed instability and dropouts Carrier condition and playback setup come before software. Use an appropriate stylus or tape machine and confirm the playback speed. For fragile, moldy or sticky material, get a preservation specialist’s assessment before cleaning or replaying it. Software cannot guarantee repair of damage introduced during a bad transfer. The [vinyl restoration workflow](https://soundforgepro.com/sound-forge-pro-for-vinyl-restoration/) covers capture, side splitting and conservative cleanup. Persistent speed instability, broken carriers and irreplaceable recordings can justify specialist equipment and handling. ## Preserve the Source Before Restoring the Sound Restoration and preservation are related but not identical. Restoration changes an access or production copy so it's easier to hear; preservation keeps an authentic, documented source that can be revisited when better tools or information become available. The International Association of Sound and Audiovisual Archives separates [signal extraction, ingest, archival storage, preservation planning and access](https://www.iasa-web.org/tc04/audio-preservation) in its TC-04 guidance. That is a useful model even for a family cassette: capture once as carefully as practical, keep the unprocessed transfer, document what you did, and make restored listening copies from it. For media-independent digital audio, the Library of Congress [Recommended Formats Statement](https://www.loc.gov/preservation/resources/rfs/audio.html) prefers native resolution to up-sampling and uncompressed files to compressed delivery. It also prefers WAVE with embedded Broadcast WAVE metadata to WAVE without it. As a specific digitization example, the Library’s [National Jukebox documentation](https://data.labs.loc.gov/jukebox/README.html) describes 96 kHz/24-bit Broadcast Wave preservation masters. That project choice is not a rule that every podcast needs 96 kHz. Preserve native information, keep metadata, and make restored listening copies separately from the master. For an ordinary project, a practical package is: - the original carrier or received file, unchanged; - a lossless transfer or working master at the captured resolution; - a short text log naming the source, date, equipment and processing steps; - one or more restored access copies; - delivery files such as MP3 or AAC generated from the lossless master. ## Where Sound Forge Fits Sound Forge is strongest when one finished or transferred audio file needs close waveform editing, measurements, plug-in processing and repeatable export. In its 2026 product announcement, [Boris FX describes Sound Forge as a dedicated environment](https://blog.borisfx.com/press/boris-fx-acquires-vegas-pro-sound-forge-and-acid-pro) for detailed work beyond a DAW timeline; the current [Sound Forge Pro 2026 online help](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/topics/workingwith.htm) remains the version reference for menu and workflow details. Use it as a diagnostic bench: - mark one clean and one damaged passage; - zoom to sample level for discontinuities and shelves; - use spectral views and analysis for tonal or broadband patterns; - build a short plug-in chain with a reason for each stage; - bypass, loudness-match and render a new file; - batch only after one representative file passes inspection. Consider a specialist tool or workflow for detailed spectral editing, source separation, advanced de-reverb, container recovery or a full multitrack mix. These are different jobs, not reasons to run every damaged file through a larger suite. The [audio restoration software comparison](https://soundforgepro.com/audio-restoration-software/) covers product selection; this hub covers diagnosis. If the problem is specifically noise, [choose noise-reduction software by noise type and workflow](https://soundforgepro.com/audio-noise-reduction-software/). A free local editor can be enough for a small repair; before using a cloud service on private audio, check whether uploading it is acceptable. ## Know the Limits Before You Promise a Result ![Practical limits of restoration for hum, clicks, clipping, reverb, codec damage and missing audio](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/08/restoration-limits-v2.webp) Restoration can reduce faults and estimate short gaps; it cannot guarantee discarded or overwritten samples. Stop when the repair becomes more audible than the fault. A little residual hiss may be less distracting than metallic denoise artifacts, and speech with unstable consonants often sounds worse than a faint room. One remaining click may respond to a targeted repair; an over-sensitive de-click pass may soften every transient in the recording. Re-record when the performance can be repeated and the clean take costs less than a compromised repair. Escalate to a specialist when the carrier is fragile, the only copy is irreplaceable, the transport needs alignment, the recording contains legal or historical evidence, or your test pass changes wanted material without making the fault acceptable. AI tools deserve the same controlled review. Compare the same passage at matched playback loudness, listen for changed consonants and ambience, and disclose when missing content was generated rather than recovered. The [AI audio restoration guide](https://soundforgepro.com/ai-audio-restoration/) matches tool classes to noise, reverb, damaged vocals and missing bandwidth without treating plausible reconstruction as proof of the original signal. ## Audio Restoration FAQ ### What is audio restoration? Audio restoration is the controlled reduction or reconstruction of unwanted changes in a recording while preserving the wanted performance. It includes noise reduction, de-clicking, de-hum, declipping, reverb reduction, speed correction and repair of short dropouts. ### Can badly damaged audio be fully restored? Not always. Steady hum and isolated clicks may improve substantially. Severe clipping, overwritten audio, heavy lossy encoding and reflections that overlap the direct sound contain information that was discarded or mixed together, so an exact original cannot be guaranteed. ### What should I fix first in an old recording? Preserve the source and verify playback first. If peak information was truly clipped, test declipping before other processes reshape it; if a float file retains intact peaks above 0 dBFS, try lowering gain first. Repair isolated faults and compare hum-first with broadband-noise-first on a short passage. Treat de-reverb and codec reconstruction as separate experiments, not compulsory final stages. ### Is audio restoration the same as repairing a corrupted audio file? No. Restoration processes sound that can be decoded. A file that will not open, seek or reach its expected end may need header, container or data recovery before an audio editor can work on its signal. ### Should I remove all hiss from a recording? No. Stop when additional reduction damages speech, music, ambience or transients more than the remaining hiss distracts the listener. A small noise floor often sounds more natural than metallic or pumping artifacts. ### What format should I use for a restoration master? Keep a lossless file at the source or capture resolution rather than up-sampling or repeatedly encoding a lossy format. Broadcast WAV is useful when embedded preservation metadata matters; ordinary PCM WAV can be a practical working master when metadata is documented separately. ### Can Sound Forge restore old recordings? Sound Forge can inspect and edit a single file closely, reduce several common noise and impulse problems, host restoration plug-ins and produce repeatable exports. Fragile-carrier playback, deep spectral reconstruction, advanced de-reverb and container recovery may require other tools or a specialist. ### How to Remove Mouth Clicks from Audio Without Damaging Speech URL: https://soundforgepro.com/remove-mouth-clicks-from-audio/ Last updated: 2026-10-09T21:05:52.000Z **To remove mouth clicks from audio without damaging speech, repair each event according to where it lands, not according to how annoying it sounds.** A short click in the gap between words can often be repaired locally, using a tiny bridge for an impulse or matching room tone for a longer click. The same edit across a *t*, *d* or *k* can punch a hole in the word. That second case needs a processor tuned for mouth noise or a careful time-frequency repair. **Go straight to your case**[Hear the test](#hear-the-original-clicks-and-two-repairs)[Click in a pause](#how-to-repair-a-mouth-click-in-a-pause)[Click over speech](#how-to-remove-a-mouth-click-over-speech) I built a controlled test to measure the difference. Seven copies of one real CC0 teeth click were placed over the same LibriVox speech recording: four in measured low-energy gaps and three directly over spoken audio. A targeted repair removed the four gap clicks while leaving every sample outside those selected intervals untouched. A generic whole-file de-click pass barely moved this broader mouth transient and changed more of the surrounding file. The takeaway here has little to do with one algorithm losing. It's that “mouth noise” isn't a preset. Diagnose the transient, listen to what was removed, and stop before wanted articulation starts showing up in it. ![Waveform and spectrogram guide distinguishing mouth clicks, digital clicks, plosives and sibilance](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/08/diagnostic-map-v2.webp) Four sharp-sounding faults have different shapes, durations and repairs. ## The Short Answer: Remove the Smallest Defect You Can Isolate - **Click in a pause:** zoom in, select only the transient and use a tiny interpolation, redraw, replace or silence edit. Audition both boundaries. - **Click across speech:** use a specialist Mouth De-click processor or spectral repair. Muting the interval would take the speech with it. - **One click inside a paid line while the speaker is available:** record a pickup before forcing an aggressive repair. A clean re-take is often faster and safer than rebuilding a vowel. - **Clicks throughout a clean voice track:** test a conservative whole-track pass on a duplicate. If available, audition the residual or “clicks only” output for missing consonants; also compare the repaired speech with the source. - **Needle-thin click at an edit or digital dropout:** follow the [current Sound Forge clicks and pops guide](https://soundforgepro.com/how-to-remove-clicks-pops-sound-forge-pro/); that is a different fault family. - **Low thump on a *p* or *b*:** use plosive repair or a local low-frequency edit, not mouth de-click. - **Long bright *s* sound:** use [de-essing](https://soundforgepro.com/reduce-sibilance-sound-forge/). A de-clicker hunts for short events and won't handle sustained high-frequency energy. If the recording also has hum, room reflections, clipping or broadband noise, start with the [audio restoration diagnosis hub](https://soundforgepro.com/audio-restoration/). It keeps you from stacking unrelated processors on a problem you haven't even named yet. ## How to Tell a Mouth Click from the Other Sharp Noises A mouth click is a brief oral transient produced around tongue, teeth, lips and saliva movement. It may be a single spike, a small asymmetric burst or a sticky cluster with a short decay. Unlike a digital click caused by an abrupt discontinuity, it doesn't have to be one sample wide. It also isn't a plosive's broad low-frequency air blast, and it isn't sibilance either: it doesn't stretch across the whole *s* or *sh*. Listen at normal speed first, then zoom far enough to see the event without losing the surrounding word. A waveform identifies the timing and amplitude jump; a spectrogram shows whether the event cuts vertically across a broad band, blooms mainly at low frequencies or continues as high-frequency energy. Use these checks before touching a control: 1. **Does the sound occur before, after or inside a word?** Timing determines whether a local edit can be invisible. 2. **Is it one event or dense crackle?** A cluster may need click widening, [de-crackle](https://izotoperx.net/izotope-rx-remove-crackle/) or several local repairs rather than one interpolated line. 3. **Does the waveform jump at an edit boundary?** Move or crossfade the edit before blaming the speaker. 4. **Does it vanish when you change the playback device?** Then the file may be clean. Check the playback path with the [distorted-audio fault test](https://soundforgepro.com/fix-distorted-audio/). Don't diagnose from a boosted top end alone. Compression, limiting and bright EQ make small clicks easier to hear, but they say nothing about what caused them. Repair first; master later. ## A Controlled Test: Seven Real Clicks over One Voice The speech is an 11.12-second excerpt from Claudia Caldi’s LibriVox reading of “Epitaph on a Sailor” in [*Short Story Collection Vol. 106*](https://librivox.org/short-story-collection-vol-106/). The contaminant is the 12 ms core of [colorsCrimsonTears’ CC0 “Click” recording, made by clamping teeth together](https://freesound.org/people/colorsCrimsonTears/sounds/562294/). LibriVox labels its recordings public domain in the United States and advises listeners elsewhere to verify local copyright status. The inserted click stands in as a controlled proxy for a short oral transient; nobody is claiming every lip smack or saliva noise has the same shape. I inserted the click seven times at −14 dBFS. Four events sit in low-energy gaps; three overlap high-energy speech. The local method replaces only a 16 ms selected interval around each gap click with a straight bridge between its edges. The three over-speech clicks are deliberately left alone because deleting their interval would delete voice too. The generic baseline is FFmpeg's `adeclick` filter in overlap-save mode at thresholds 4, 3 and 2\. Its [current filter documentation](https://www.ffmpeg.org/ffmpeg-filters.html#adeclick) describes how it works: samples detected as impulsive noise are replaced with values interpolated by autoregressive modeling, a lower threshold flags more samples as noise, and overlap-save leaves samples that aren't interpolated unchanged. It's a generic impulse remover, not a processor designed specifically for mouth noise. ![Mouth-click repair benchmark: targeted gap repair lifts whole-file SI-SDR to 20.92 dB and changes nothing outside the click windows, while three speech-overlap clicks remain.](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/10/same-file-mouth-click-benchmark-v2-v20261006.webp) Targeted repair improved the four measured gap clicks and deliberately left three speech-overlap clicks untouched. | Version | Overall click-window error reduction (higher is better) | Residual gap-click error vs clean speech RMS (lower is better) | Change outside all click windows | Interpretation | | --------------------------------- | ------------------------------------------------------- | -------------------------------------------------------------- | ------------------------------------------------- | ------------------------------------------------ | | **Click input** | Baseline | +0.0019 dB | Unchanged source | Seven known events | | **Targeted gap repair** | 3.6795 dB | −43.4058 dB | No changed samples | Local repair worked for the four isolated clicks | | **Generic de-click, threshold 2** | 0.1890 dB | −0.4652 dB | Error at −35.3418 dB relative to clean speech RMS | Poor match for this broader transient | Benchmark manifest and reproducibility record **Original reproducibility run:** August 15, 2026\. The retained source files were rebuilt with FFmpeg 8.1.2, Python 3.9.6, NumPy 1.26.4, SciPy 1.13.1, SoundFile 0.13.1 and pystoi 0.4.1 on Apple Silicon. Reruns on September 4 and September 7, 2026 in the same dependency environment reproduced all six retained benchmark WAV files and four MP3 previews byte for byte, together with every reported metric. - **Speech source:** LibriVox public-domain excerpt, source SHA-256 `3e360ac43a4b43915a5454be456c4b087a2c10433ea00533cf1362be034ce76f`. - **Click source:** colorsCrimsonTears CC0 recording, source SHA-256 `1665d81003ef59b862a24807286a6e592ab4875a9faf973e8b9627df23f35874`. - **Construction:** 48 kHz mono; a 12 ms transient at −14 dBFS; gap positions 2.43, 5.01, 6.90 and 9.30 seconds; speech-overlap positions 1.20, 5.37 and 8.16 seconds. - **Generic commands:** `adeclick=threshold=4:method=save`, then thresholds 3 and 2\. Overlap-save keeps non-interpolated samples unchanged according to the FFmpeg documentation. - **Targeted method:** straight interpolation across a 16 ms interval around each of the four gap clicks. The three clicks over speech were intentionally left untouched. - **Metrics:** SI-SDR measures scale-invariant waveform similarity; higher is better. STOI estimates intelligibility after 16 kHz resampling. Residual click error is RMS error relative to clean-speech RMS inside ±15 ms windows; lower is better. - **Key master hashes:** input `98967068aa7c9b1aae7fcc4db2e87e99a335dc52ee1d6cf77005e88911458252`; aggressive generic pass `9e3d9975db2e055a9d278f77d3a98a7f95514f979f12dd8ed5b39d063b024f4c`; targeted gap repair `ceca16d48938e9d61d2c2a5118fc63b0f5424ed00ef91443ed2f5effac88a93c`. - **Evidence hashes:** build script `c98c1d4b74ddba69ab246d8d6798ad89f0e088f079c32a1e9a39398fc6b20ee0`; manifest `5a5e192ebbb07a55aed5e7a86dc94c4cf62de519228401d7ccf05b371408b5b5`. **Measurement detail:** the original input and targeted-repair scores use floating-point arrays before 24-bit export; the FFmpeg variants are scored from their WAV outputs. A separate 24-bit readback check reproduced the displayed SI-SDR, STOI and overall click-window improvement. Targeted gap error rounded to −43.4057 dB after readback instead of −43.4058 dB before export. No MP3 was scored. The public table and audio previews are derived from this one controlled file. They do not rank every de-clicker, voice, room or click type. Our [review methodology](https://soundforgepro.com/review-methodology/), [editorial policy](https://soundforgepro.com/editorial-policy/) and [corrections policy](https://soundforgepro.com/corrections/) explain how tests, commercial relationships and revisions are handled. The residual-error levels and outside-window error are relative to clean-speech RMS, where lower is better. Click-window improvement and SI-SDR run the other way: higher is better. STOI is a separate intelligibility estimate. Overall SI-SDR improved from 17.2373 dB to 20.9168 dB after the gap repairs even though the three clicks over words remained. STOI stayed at 0.991559\. The aggressive generic pass reached 17.3590 dB SI-SDR and 0.990857 STOI. These measurements compare each file with the known clean reference; listening to consonants, room tone and repair boundaries still gets the final word. The outside-window figure needs careful reading. −35.34 dB doesn't mean the output was “35 dB worse.” It means the generic processor made detectable changes outside the known click windows at an error level 35.34 dB below the clean speech RMS, while delivering only 0.189 dB of click-window improvement. That's a poor risk-to-reward result for this source, though it says nothing about every de-clicker or every mouth click. ## Hear the Original, Clicks and Two Repairs Use headphones and keep the playback level fixed. The four MP3 files are listening previews, not the files used for scoring. The test uses 48 kHz mono audio, with 24-bit WAV outputs and the measurement boundary explained in the reproducibility record above. Listen once for the seven clicks, then again for word endings and consonant attacks. ### Clean reference The untreated public-domain speech gives you the articulation and room tone that every processed version should preserve. Clean public-domain speech reference [Download Clean public-domain speech reference](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/media/2026/08/clean-reference.mp3) ### Seven-click input Four clicks land in gaps and three cross speech. The source click is real; its placement and gain are controlled. Seven mouth/teeth clicks over speech [Download Seven mouth/teeth clicks over speech](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/media/2026/08/mouth-click-input.mp3) ### Targeted repair of gap clicks The four isolated clicks are bridged locally. The three clicks over words remain, making the limit audible rather than hiding it behind a “clean” label. Four gap clicks repaired; three over-speech clicks left [Download Four gap clicks repaired; three over-speech clicks left](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/media/2026/08/targeted-gap-repair.mp3) ### Generic whole-file de-click This is the most aggressive tested open baseline. It changes more of the file but barely reduces the broader mouth transients. Generic whole-file de-click baseline [Download Generic whole-file de-click baseline](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/media/2026/08/aggressive-adeclick.mp3) ## Prevent Mouth Clicks Before Recording ![Voice recording setup for testing hydration, off-axis microphone position and headphone monitoring](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/08/mouth-click-prevention-v2.webp) A short monitored test can reduce later editing without pretending to replace a clean re-take. [The U.S. National Institute of Dental and Craniofacial Research](https://www.nidcr.nih.gov/health-info/dry-mouth) recommends water as one way to ease dry mouth, but that's health guidance; it doesn't prove one sip will remove a recorded click. If persistent dry mouth affects speaking or swallowing, its guidance says to ask a dentist or doctor about the cause. For a session, keep ordinary water available and record a short monitored test after the speaker has settled. [RØDE’s current mouth-noise guidance](https://help.rode.com/hc/en-us/articles/7645976167311-Why-Does-the-Microphone-Capture-Mouth-Noises) recommends testing an off-axis microphone angle and notes that sensitive studio microphones can emphasize mouth noise. Treat its 45-degree example as a starting point instead of a mandatory position: compare a small angle and a little more distance through the actual recording chain, then keep the version that preserves clarity. A pop filter deals with the plosive air bursts described in the RØDE guidance; it can't stop clicks that start inside the mouth. If a sharp sound has a room tail, listen for reflections as well: treating the room may soften the repeat, but the original oral click will still be there. Check the result with a short recording. For voice work, save the test take and its mic position with the session notes. The [Sound Forge voice-over workflow](https://soundforgepro.com/sound-forge-pro-for-voice-over-recording/) covers recording, monitoring and delivery, while the [podcast workflow](https://soundforgepro.com/sound-forge-pro-for-podcasters/) handles repeated spoken-word production. ## How to Repair a Mouth Click in a Pause ![Audio editor comparing an isolated mouth click in a pause with a click overlapping speech](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/10/gap-vs-speech-editor-v2-v20261006.webp) A gap offers clean repair boundaries; a click over a word shares the interval with wanted articulation. 1. **Duplicate the file or save a new version.** Never experiment on your only copy. 2. **Mark the click at normal speed.** If you hunt only at extreme zoom, it is easy to repair a harmless waveform detail and miss the audible event. 3. **Zoom to the shortest complete transient.** Keep the selection inside the low-energy gap and include no more decay than necessary. 4. **Choose the smallest suitable repair.** Interpolate or redraw a very short impulse; replace or silence only when the surrounding gap makes that edit natural. 5. **Audition before, through and after the boundary.** A repaired center can be quiet while either edge clicks. 6. **Return to normal zoom.** The edit has to disappear inside the sentence. Looking smooth under a microscope isn't enough. In Sound Forge 2026, the native command is **Tools → Repair → Interpolate**. The [official Interpolate documentation](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/proonly/interpolating%5Fsound%5Fdata.htm) says the selection should be less than 2 ms in most cases; with no selection, the cursor is treated as the middle of a glitch shorter than 1 ms. That's the right scale for a tiny impulse, and it's not permission to interpolate a 12 ms mouth sound across a syllable. Use the [full native repair walkthrough](https://soundforgepro.com/how-to-remove-clicks-pops-sound-forge-pro/) for Interpolate, Pencil and DeClicker/DeCrackler controls. For a longer click that sits entirely inside a pause, use matching room tone instead of stretching a tiny-interpolation tool past its purpose. Copy a clean gap from the same recording, replace a span of equal length without shifting the speech that follows, and blend only the patch edges if you need to. Keep both transitions inside the pause and listen through the whole sentence. Don't paste digital silence into an audible room bed, and don't use this replacement across a word. [Audacity’s official repair guide](https://manual.audacityteam.org/man/click%5Fremoval.html) makes the same scale distinction in another editor: automatic Click Removal expects a selection of more than 4,096 samples, while Repair is for an individual selection no longer than 128 samples. The numbers are tool-specific, but the principle travels: use a local repair for a local defect. ## How to Remove a Mouth Click over Speech When the click overlaps a consonant or vowel, silence and straight-line replacement take wanted speech out along with the defect. Start with a processor built for mouth noise. iZotope currently lists [Mouth De-click in RX 12 Standard and Advanced](https://www.izotope.com/products/rx-standard), not Elements, and describes it as tuned for clicks and lip smacks on long selections or individual events. For settings that keep speech natural, see the [RX 12 Mouth De-click guide](https://izotoperx.net/izotope-rx-mouth-de-click/). That product distinction matters. iZotope’s legacy De-click plug-in help separates Click, Thump and Discontinuity types, but those labels don't tell you what your current Mouth De-click interface looks like. The same help warns that too much sensitivity can damage wanted audio. Its [Clicks only output](https://help.izotope.com/docs/rx-plug-in-pack/De-click.html) lets you hear the difference between original and processed audio, and if speech turns up in that residual, back off. A safe specialist pass looks like this: 1. select one difficult phrase plus a clean phrase; 2. start at low sensitivity and no extra click widening; 3. preview at matched level; 4. listen to the removed signal or delta where available; 5. raise sensitivity only until the target click is caught; 6. stop if *t*, *d*, *k*, breaths or vocal texture enter the residual; 7. switch off Listen, Clicks only or delta output, confirm that normal repaired speech is playing, then process the smallest sensible region before considering the whole track. iZotope’s guide to [digital clicks and mouth noise](https://www.izotope.com/community/blog/removing-digital-clicks-and-pops-from-audio) recommends the dedicated Mouth De-click tool for oral noise and local use when events are sporadic. Its [vocal-cleanup guide](https://www.izotope.com/en/learn/clean-up-vocals.html) likewise treats stubborn mouth clicks as targeted work in the standalone editor rather than a reason to flatten an entire vocal. Another candidate is [Greenlit Audio’s Mouth De-Click](https://greenlitaudio.com/mouth-declick), with free processing and paid controls. Its [current setup notes](https://greenlitaudio.com/mouth-declick/help) limit processing to 44.1, 48 and 88.2 kHz, and other rates pass through dry. It reports 400 ms latency. Offline application in Audacity can leave the first couple of seconds untreated, and versions before 0.3.1 could return the whole selection unchanged. Check the actual render and the installed version rather than trusting the repair counter. This plug-in wasn't part of the benchmark above. If Mouth De-click still leaves one click behind, use spectral repair on that event. A mouth click often shows up as a short vertical feature, but select only the energy that doesn't belong to the surrounding consonant. Process once, compare, and undo if the word loses definition. ## Repair Mouth Clicks in Sound Forge [Boris FX positions Sound Forge](https://blog.borisfx.com/press/boris-fx-acquires-vegas-pro-sound-forge-and-acid-pro) as a dedicated environment for detailed audio work beyond the timeline. In this workflow it handles close waveform inspection, markers, native repair, plug-in hosting and final assembly around one file, even when a specialist repair runs in another application. 1. Open a copy of the original WAV and create markers for representative clicks. 2. Repair the obvious gap clicks with the smallest native edit. 3. For clicks over speech, send a duplicate selection to RX standalone, or test a compatible installed plug-in if it appears in your Sound Forge setup. 4. Before rendering, switch off any removed-signal monitoring mode. Reimport normal repaired speech without changing sample rate, channel count or start time. 5. Level-match bypass and processed playback. 6. Check every marked consonant and every edit boundary on headphones and monitors. 7. Export a new lossless master and leave the capture untouched. Don't assume you have an RX license, plug-in format or menu path just because another user does. RX 12 Elements includes generic De-click, and the current edition comparison puts specialist Mouth De-click in Standard and Advanced. If your host doesn't recognize the plug-in and your RX license includes the standalone editor, use that editor for the round trip. RX Elements has no standalone editor, so check the edition before you choose this route. Run noise reduction after mouth-click repair when practical. Broadband denoise can blur the transient without removing it; compression and limiting can then make the remainder more obvious. For the next stage, use the [background-noise guide](https://soundforgepro.com/how-to-remove-background-noise-in-sound-forge-pro/) or compare conventional repair with the tested [AI audio restoration workflow](https://soundforgepro.com/ai-audio-restoration/). ![Safe mouth-click removal workflow from diagnosis to residual listening and a new master](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/08/safe-mouth-click-workflow-v2.webp) Listen to the removed signal; if it contains speech, reduce the processing or choose a narrower edit. ## Five Repairs That Usually Make the Voice Worse - **Silencing inside a word.** The click disappears because part of the word disappears. - **Turning sensitivity up until the track looks clean.** Visual cleanliness can hide softened consonants and dulled attacks. - **Running several blind passes.** Each pass sees the artifacts created by the previous one. Repeated processing can trade clicks for lisping or dullness. - **Using de-essing for every bright noise.** De-essing controls sustained sibilant energy. Precise mouth-click repair is a different job. - **Compressing before cleanup.** Compression followed by makeup gain can bring quiet clicks forward, and dynamics processing may change their shape. Perfectly sterile dialogue isn't always the best dialogue. Remove distractions and obvious client-delivery defects, but keep [natural breaths](https://soundforgepro.com/edit-breaths-sound-forge/), articulation and presence. A casual podcast doesn't need the same cleanup density as an audiobook pickup or an exposed commercial voice-over. If the speaker is still available and one important word needs heavy reconstruction, record the pickup. ## Mouth-Click Removal FAQ ### What causes mouth clicks in audio? Mouth clicks are short oral transients associated with movement of the tongue, teeth, lips and saliva during speech. Close, bright microphone placement and later compression or high-frequency boost can make them more obvious, but they are different from digital dropouts and edit-boundary clicks. ### Can Audacity remove mouth clicks? Audacity can repair some clicks. Its official guide uses Click Removal for a larger selection and Repair for an individual selection up to 128 samples. A click over speech may still need a specialist mouth-noise processor or careful spectral repair. ### Can Sound Forge remove mouth clicks? Sound Forge can repair tiny isolated defects with Interpolate or Pencil and can run its current DeClicker/DeCrackler tools. For mouth clicks embedded in speech, test a specialist Mouth De-click processor in a compatible plug-in setup or standalone editor, then reimport the result. ### Should I remove every mouth noise? No. Remove distracting clicks and delivery failures, but keep natural articulation and breath texture. Processing every small oral sound can make speech dull, lisping or unnaturally sterile. ### Does a pop filter stop mouth clicks? A pop filter mainly reduces air blasts from plosive consonants. It does not remove clicks generated inside the mouth. Water may ease dry mouth, while mic angle, distance and a short monitored test address the recording path. ### Should mouth de-click run before noise reduction? Usually repair obvious clicks first. Broadband denoise may smear their shape, while compression or limiting can make them louder. Test the order on a short duplicate when the recording has several overlapping faults. ### What sensitivity should I use for Mouth De-click? There is no universal number. Start low on one difficult phrase and increase only until the target click is detected. Monitor the removed signal if the tool offers that output; back off when it contains consonants, breaths or vocal texture. Always compare normal repaired speech with the source. ### Can AI remove mouth clicks automatically? Some AI voice cleaners advertise mouth-noise removal, but the same safety rule applies: compare with an untouched source at matched level and inspect word endings. A generic speech enhancer is not automatically a specialist de-clicker. Before uploading unreleased client dialogue to a web tool, check its storage, retention and model-training terms. ### Audio File Size Calculator: WAV, FLAC, MP3 and AAC URL: https://soundforgepro.com/audio-file-size-calculator/ Last updated: 2026-10-11T10:47:13.000Z [Use the calculator](#calculator) to estimate a file, find recording time from available space, or count complete files that fit on a drive. ## Audio file size calculator BROWSER TOOL · NO UPLOAD ### Calculate size, time or file count Choose what you know. The result updates as you type. Calculate File size Recording time Files that fit Format PCM payload WAV estimate AIFF estimate MP3 / AAC / bitrate FLAC range Duration Hours : Minutes : Seconds Files / stems Available storage Amount UnitMBGBTBMiBGiBTiB Audio settings Sample rate8 kHz16 kHz22.05 kHz32 kHz44.1 kHz48 kHz88.2 kHz96 kHz176.4 kHz192 kHz Bit depth8-bit16-bit24-bit32-bit64-bit float ChannelsMonoStereoQuad6 (5.1)8 (7.1)16 channels32 channels Container allowance Wrapper bytes The default 102-byte WAV wrapper allowance is editable, not a format constant. Change it to match your writer and metadata. Compressed stream Average bitratekbps · use the measured average Overall file bitrate already includes tags and wrappers. A target setting may differ from the finished average. FLAC planning range Low estimate% of PCM High estimate% of PCM Quick presets CD stereo 24-bit mono voice Video stereo 5.1 session MP3 320 Exact PCM payload **86.40 MB** 82.40 MiB Copy CSV Calculation details Batch total 86.40 MB Per minute 17.28 MB Data rate 2,304 kbps Classic RIFF boundary about 4 h 8 min PCM payload is deterministic. A container and its metadata sit outside this byte count. 300 s × 48,000 samples/s × 24 bits × 2 channels ÷ 8 = 86,400,000 bytes. **Five minutes of 48 kHz, packed 24-bit stereo audio contain 86.4 MB of PCM data.** At an average stream bitrate of 320 kbps, five minutes contain about 12 MB before tags and wrappers. Choose PCM for uncompressed sample data, WAV or AIFF to add a wrapper allowance, or average bitrate for MP3, AAC and Opus. FLAC needs a range because its compression depends on the audio. PCM payload uses complete sample frames and the stored sample width, and fractional durations are rounded to the nearest frame. Here, 24-bit means packed three-byte samples, so select 32 if your WAV stores each sample in four bytes. WAV and AIFF add an editable wrapper allowance. FLAC stays a planning band; it can't be a guaranteed bound. ![PCM samples, a PCM WAV or AIFF wrapper, and encoded packets use different size calculations](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/09/audio-container-counting-20260912.webp) Count samples across all channels and multiply by stored bytes per sample. The WAV/AIFF example assumes PCM; bitrate is in bits per second. [Open diagram full size](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/09/audio-container-counting-20260912.webp). ## The audio file size formula For uncompressed PCM, use bytes = seconds × sample rate × stored bits per sample × channels ÷ 8\. A 60-second, 44.1 kHz, 16-bit stereo payload is 10,584,000 bytes: 10.584 MB or about 10.094 MiB. The selected width describes the bytes actually stored, which can be more than the converter’s useful precision. The channel count multiplies complete sample frames. Mono has one sample per frame, stereo has two, and a six-channel recording has six. Microsoft’s current [RIFF overview](https://learn.microsoft.com/en-us/windows/win32/xaudio2/resource-interchange-file-format--riff-) describes WAVE audio as chunks that include format information and the audio data itself. The PCM equation calculates the data; it doesn't account for every possible surrounding chunk. Microsoft’s [WAVEFORMATEXTENSIBLE definition](https://learn.microsoft.com/en-us/windows-hardware/drivers/ddi/ksmedia/ns-ksmedia-waveformatextensible) distinguishes valid precision from stored sample width. For an existing PCM WAVE file, complete frame count multiplied by its block alignment gives the audio-data bytes without guessing that width. Other chunks still sit outside the payload. For encoded audio, use estimated bytes = seconds × measured average bitrate in bits/s ÷ 8\. A stream bitrate estimates the encoded payload, while an overall file bitrate worked out from complete file bytes and duration already includes metadata and container overhead, so don't add that overhead twice. Sample rate and PCM depth alone won't tell you an encoded file’s size. ## How to interpret exact and estimated results PCM payload is deterministic once duration, sample rate, stored bits per sample and channel count are known. WAV and AIFF add container chunks whose size depends on the writer and metadata. MP3, AAC and Opus should be planned from measured average bitrate, while FLAC needs a range calibrated with representative source audio. | Model | What the calculator returns | What to confirm | | -------------------- | ----------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------- | | PCM payload | Exact sample-data bytes from duration, sample rate, stored width and channels | The file’s stored sample width and channel count | | WAV or AIFF estimate | PCM payload plus an editable wrapper allowance per file | Metadata, markers, padding and other chunks written by the application | | Average bitrate | Duration multiplied by the bitrate entered | Use stream bitrate for payload, or whole-file bitrate without adding wrapper overhead again | | FLAC range | A low-to-high percentage of the uncompressed PCM payload | Encode a representative passage and enter its measured ratio when the estimate matters | A requested AAC bitrate doesn't always guarantee the finished size. Apple’s [AAC rate-control note](https://developer.apple.com/library/archive/technotes/tn2271/%5Findex.html) separates CBR, ABR, constrained VBR and quality-based VBR. For planning, enter a measured average bitrate from a representative finished file instead of treating a quality setting as a fixed data rate. ## Three calculations, three planning questions ### Duration to file size Use this before recording, rendering stems, or preparing delivery copies. Enter the longest file duration and the number of files. If a project mixes mono and stereo stems, calculate each group separately instead of pretending every file has the same channel count. ### Storage to maximum recording time Enter writable space, not advertised drive capacity. The three-copy figure divides an aggregate storage budget between one working source and two copies, allowing a wrapper for each copy. It does not measure three destinations. For independent backups, calculate each destination separately and use the shortest resulting recording time as the limit. ### Drive capacity to whole files Use this for repeated interviews, podcast episodes, or delivery batches. The result rounds down to complete files and also shows three-copy sets. A partial final file is not counted. ## MB, MiB, GB, and GiB are different units The [BIPM SI prefix table](https://www.bipm.org/en/measurement-units/si-prefixes) defines mega as 10⁶ and giga as 10⁹. That makes 1 MB equal to 1,000,000 bytes and 1 GB equal to 1,000,000,000 bytes. The [NIST binary-prefix reference](https://physics.nist.gov/cuu/Units/binary.html) defines 1 MiB as 2²⁰ bytes and 1 GiB as 2³⁰ bytes. The same 1,048,576 bytes appear as 1.05 MB or 1.00 MiB after rounding. Neither display means data has disappeared. Compare raw bytes when checking a storage specification against a file browser; the calculator displays both unit systems. ## WAV, AIFF, RF64, and BW64: payload is not the container WAV and AIFF can both carry uncompressed PCM, but they don't share one universal 44-byte wrapper. Each container has its own chunk structure, and real applications can write extra metadata. That's why the calculator offers separate WAV and AIFF choices and shows the wrapper allowance instead of quietly adding 44 bytes to every PCM result. The familiar “4 GB WAV limit” comes from the 32-bit size fields in classic RIFF. Plan around 4 GiB, or 4.29 decimal GB, with a little less left for audio after headers. The [ITU-R BS.2088-2 recommendation](https://www.itu.int/rec/R-REC-BS.2088/en) defines BW64 for long-form audio, and the [EBU RF64 archive](https://tech.ebu.ch/publications/tech3306) points to the ITU specification that replaced Tech 3306\. For a long uninterrupted take, confirm that both the recorder and the receiving application support the large-file container you pick, because the extension alone doesn't prove compatibility. If the recording gets close to that boundary, splitting at a safe edit point is often easier to exchange. The [long-recording split guide](https://soundforgepro.com/split-long-recording-into-tracks-sound-forge/) covers the workflow. Don't drop sample rate or bit depth just to dodge a container limit without checking the delivery requirement. If conversion is needed, read the [sample-rate workflow](https://soundforgepro.com/how-to-change-sample-rate-sound-forge-pro/) and the [bit-depth and dither guide](https://soundforgepro.com/sound-forge-bit-depth-dither/) before you change a master. ## MP3, AAC, and Opus need an average-bitrate estimate One hour at 128 kbps holds a nominal 57.6 MB of encoded payload, and at 320 kbps it's 144 MB. Don't multiply by the channel count again when the selected bitrate already covers the complete stream, as it normally does in an export dialog. CBR usually stays closest to the formula. ABR can miss the target, and a VBR quality setting may not expose a meaningful bitrate until after encoding. The safest workflow is to encode a representative passage, inspect its average, and use that measured value. The [Sound Forge MP3 export guide](https://soundforgepro.com/how-to-export-mp3-from-sound-forge-pro/) explains the related export choices; the [audio conversion guide](https://soundforgepro.com/how-to-convert-audio-files-sound-forge-pro/) covers format changes without overwriting the source. ## Why FLAC must remain a range FLAC saves storage without throwing away PCM information, but how much it saves depends on the signal. Silence, steady tones and correlated channels compress well, while noise-like audio leaves the predictor little redundancy to remove. Compression level changes encoder effort and can change the size; it never makes FLAC lossy. The default 35–85% band is an editable planning assumption. It isn't a measured confidence interval or a guaranteed minimum and maximum. Source material, channel correlation, metadata and encoder settings can all move the result. When storage is tight, encode a representative passage and enter its measured percentage. The fields accept fractions below 1% and values above 100%, since short files or metadata can outweigh the compression savings. The current [FLAC specification in RFC 9639](https://www.rfc-editor.org/rfc/rfc9639.html) supports integer PCM with one to eight channels and bit depths from 4 to 32 bits, but it doesn't directly keep floating-point samples. The calculator disables larger FLAC choices, and even a valid format ceiling doesn't guarantee every player accepts every combination. ## Plan the project footprint, not the delivery file ![Audio storage plan with source master, working edit, delivery copy and two independent backups](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/08/storage-plan-desktop-20260815.webp) Budget the source master, working files, delivery copy, and two independent backup destinations. A 128 kbps MP3 can be the smallest object in the job. The source recording, edit master, rendered stems, alternate mixes, cache, and revisions usually dominate storage. Keep the preservation or edit master lossless, calculate delivery versions separately, and place independent backups on separate storage targets. For multichannel sessions, calculate the recorded channel count first; use the [channel-conversion guide](https://soundforgepro.com/sound-forge-channel-converter/) only when the delivery specification actually calls for a downmix. The “three-copy sets” result is meant literally: one working source and two extra copies. It says nothing about geographic separation, media health or whether you can restore from them. Check backups by opening or checksumming them, and try a restore before you wipe cards or source drives. Leave headroom on every destination. Filesystems, catalog databases, peak files, checksums, and application caches consume space outside the audio calculation. A recorder may also reserve space or stop before the advertised capacity is fully consumed. For field work, calculate with the card size you can actually write, then run a timed test at the exact channel count and recording format. ## Five mistakes that break an audio storage estimate 1. **Calling every uncompressed result “WAV plus 44 bytes.”** Calculate PCM first, then use the selected container’s actual or measured overhead. 2. **Using a target bitrate as if it were measured.** ABR and VBR can finish above or below the setting. 3. **Multiplying total MP3 bitrate by channel count.** The export bitrate usually describes the complete encoded stream. 4. **Treating FLAC as a fixed 50% saving.** Measure representative material or retain a wide band. 5. **Budgeting one copy.** Source, work files, delivery versions, revisions, and independent backups all consume space. For a deadline-critical recording, make a short test with the actual recorder, codec, metadata and destination filesystem, and compare its bytes and duration with this estimate before you record the full session. For other measurements, use the [audio tools hub](https://soundforgepro.com/tag/audio-tools/). This calculator plans storage and never looks at your audio. ## Audio file size calculator FAQ ### How do I calculate an audio file size? For PCM, multiply seconds by sample rate, stored bits per sample and channels, then divide by eight. The 24-bit choice assumes packed three-byte samples; choose 32 if each sample occupies four bytes. For encoded audio, multiply seconds by the measured average bitrate in bits per second and divide by eight. An overall file bitrate already includes wrapper overhead. ### How many MB is one minute of audio? At 44.1 kHz/16-bit stereo, one minute contains 10.584 MB of PCM payload. At 48 kHz/24-bit stereo it contains 17.28 MB. A one-minute 128 kbps stream contains about 0.96 MB before tags and container overhead. ### How many GB is a three-hour audio file? It depends on the format. Three hours of 48 kHz/24-bit stereo PCM contain 3.1104 GB. At 128 kbps, the encoded payload is about 172.8 MB; at 320 kbps it is about 432 MB. ### How many GB is one hour of MP3? At a measured average of 128 kbps, one hour is about 57.6 MB or 0.0576 GB before tags and container overhead. At 320 kbps, it is about 144 MB or 0.144 GB. ### Why is my WAV larger than the PCM calculation? WAV may store each sample in more bits than its valid precision, such as 24 valid bits in a 32-bit container. It also adds RIFF chunks, metadata and padding. First match the stored sample width, then add measured wrapper overhead; do not treat sample padding as a fixed header. ### Can I calculate FLAC size exactly before encoding? No. FLAC size depends on the signal and encoder settings. Use a planning range, then encode a representative minute and measure its ratio to the PCM source. ### Why do Finder and another tool show different file sizes? They may be using decimal MB and GB versus binary MiB and GiB, or they may round differently. Compare the raw byte count before assuming either tool is wrong. ### What happens when a WAV reaches the classic 4 GB boundary? Classic RIFF/WAV has 32-bit size fields. Use a workflow that supports RF64 or BW64, or split the recording before the boundary, and verify compatibility at both ends. ### AI Audio Restoration: What It Fixes and What It Invents URL: https://soundforgepro.com/ai-audio-restoration/ Last updated: 2026-10-09T11:50:36.000Z **AI audio restoration is useful only when the model matches the damage.** Speech enhancement can reduce background noise and room reflections around dialogue. Vocal repair can reconstruct detail in a rough voice recording. Audio super-resolution can estimate content above a bandwidth cutoff. None of those jobs proves that the output matches the lost original. That distinction matters. A cleaner podcast edit may be a better deliverable even if the processor reshaped some ambience. An archive, interview, legal recording, or master source needs a stricter standard: preserve the untreated file, document every generated change, and prefer targeted repair when it can solve the fault without inventing new signal. ![Repair methods for speech noise, local faults, clipped peaks and missing frequency bands.](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/08/model-selector-desktop-20260815-1.webp) Start with the fault, then choose the method. A speech denoiser, de-clicker, de-clipper and bandwidth reconstruction model solve different problems. ## What AI audio restoration can and cannot fix - **Good first use:** steady noise and moderate room sound around spoken voice, especially when a fast listening copy matters more than surgical control. - **Worth a short sample:** distant dialogue, mixed environmental noise, rough phone vocals and compression damage. Check consonants, identity and room tone before processing the whole file. - **Use a dedicated model:** missing high-frequency content, vocal regeneration or source separation. A general speech denoiser isn't built for those jobs. - **Usually try conventional repair first:** isolated clicks, stable electrical hum and visibly flattened clipped peaks. Targeted tools give you clearer controls and a more useful residual. - **Do not promise recovery:** overwritten peaks, discarded codec information, masked words or missing samples. AI can estimate a plausible replacement, but it can't vouch that the replacement was ever in the recording. If the fault is still unclear, begin with the [audio restoration diagnosis guide](https://soundforgepro.com/audio-restoration/). If you already need a desktop suite for spectral repair, de-clicking and batch work, use the [audio restoration software comparison](https://soundforgepro.com/audio-restoration-software/). This page deals with AI behavior and the decisions around it. ## Which AI audio restoration tool should you choose? | Damage or job | Start here | Runs where | Main limit | | --------------------------------------- | ----------------------------------------------------------------------------- | ----------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------- | | Noisy or reverberant spoken voice | [Adobe Podcast Enhance Speech](https://podcast.adobe.com/en/enhance) | Browser / cloud | Fast for auditioning dialogue, but voice character, ambience and upload custody still need review. | | Local speech denoising | [DeepFilterNet](https://github.com/Rikorose/DeepFilterNet) | Local / open source | Its project describes full-band speech enhancement and noise suppression, not general de-clicking, de-clipping or codec recovery. | | Rough spoken or sung vocal | [Kits AI Vocal Repair](https://www.kits.ai/tools/ai-vocal-repair) | Browser / cloud | The service reconstructs vocal detail with voice modeling. Check phrasing and identity, especially on speech or archival material. | | Simple missing high-frequency band | [AudioSR](https://github.com/haoheliu/versatile%5Faudio%5Fsuper%5Fresolution) | Local / open source | Its documentation warns that unfamiliar cutoff patterns, strong noise and reverb can reduce performance. | | Hum, isolated clicks or flattened peaks | Conventional de-hum, de-click or de-clip repair | Desktop editor or restoration suite | Requires diagnosis and adjustment, but the repair is easier to inspect and repeat. | An “online AI audio restoration” label tells you where the file gets processed. It says nothing about what the model does. Adobe Podcast targets spoken voice, and Kits AI positions Vocal Repair for rough voice recordings. DeepFilterNet and AudioSR need a local setup; there's no tap-to-repair phone workflow. For unreleased, legal, medical or client recordings, check retention, access and model-training terms before you upload anything. Don't choose by the most dramatic demo. A vendor picks the source, the damage and the example on its own page. Use a duplicate of your file, include one ordinary passage and one difficult one, and compare the result against a level-matched bypass. ## Four different jobs sold as AI restoration ### 1\. Speech denoising and de-reverberation Speech enhancement tries to make a voice easier to understand by cutting competing noise and, in some systems, room reflections. The [DeepFilterNet project](https://github.com/Rikorose/DeepFilterNet) describes a low-complexity framework for full-band 48 kHz speech enhancement and offers real-time noise-suppression options. That scope is useful, and it's narrow. It doesn't turn the model into a universal click remover, peak rebuilder or music restoration system. [Adobe Podcast’s feature comparison](https://podcast.adobe.com/en/features), checked September 17, 2026, lists audio-only Enhance Speech processing on the free plan: one upload at a time, no strength adjustment, a 30-minute / 500 MB file limit and one processing hour per day. The premium column adds video, bulk upload and strength control, with files up to two hours / 1 GB and up to four processing hours per day. Those are access limits. They don't tell you whether a particular recording will improve. ### 2\. Vocal repair and voice regeneration [Kits AI Vocal Repair](https://www.kits.ai/tools/ai-vocal-repair) says it detects missing high-frequency content, compression artifacts and noise, then uses voice modeling to reconstruct vocal detail. The same page recommends dry vocal input and warns that already mixed or processed vocals may produce limited results. That is the right boundary: treat the output as regenerated voice detail, then check whether the performance still sounds like the same person saying or singing the same thing. For a commercial vocal, a polished reconstruction may serve the production. For oral history, journalism or disputed recordings, changed articulation can alter the evidence. Keep the untreated source and label regenerated passages. ### 3\. Audio super-resolution Super-resolution estimates content above a bandwidth cutoff. The [AudioSR documentation](https://github.com/haoheliu/versatile%5Faudio%5Fsuper%5Fresolution) describes a model for music, speech and other sounds. Its limitations are unusually useful: training simulated missing bandwidth with low-pass filters rather than MP3 compression, and the authors warn about unfamiliar cutoff patterns, severe noise and reverb. Their suggested low-pass preprocessing deliberately removes more bandwidth before reconstruction, so try it only on a duplicate and never present the output as recovered historical truth. The accurate verb is *reconstruct*. Several high-frequency continuations can fit the same low-band signal, and a model picks one that matches what it learned. It can't retrieve data that's no longer in the file. ### 4\. AI mastering presented as repair EQ, compression, limiting and loudness matching can make a recording more consistent. They won't remove a click under a word, rebuild a clipped transient or separate two overlapping speakers. Mastering comes after repair. A louder, brighter export can impress in a quick comparison while the original defect sits there untouched. ![Waveforms and spectrograms of observed audio, a missing gap and AI-estimated audio above the line Plausible ≠ Original](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/08/observed-estimated-desktop-20260815-1.webp) When information is missing, several plausible continuations may fit the surviving signal. Plausible does not mean original. ## What does AI “invent” in restored audio? “Invent” doesn't mean the model ignores the recording and composes at random. It means the inverse problem has more than one acceptable answer. A flat clipped peak could have had several original shapes. A 24 kHz file can't store anything above its 12 kHz Nyquist limit. Reverberant speech holds the direct voice mixed with delayed copies of it, and the dry performance isn't stored anywhere as a separate track. The paper [Diffusion Models for Audio Restoration](https://arxiv.org/abs/2402.09821), published in IEEE Signal Processing Magazine in 2025, covers speech enhancement and music restoration through conditional generation of clean audio. The authors describe the flexibility of data-driven methods and the interpretability risk of end-to-end neural systems. That tradeoff is practical: learned priors can produce natural-sounding candidates in difficult cases, while the operator still needs to distinguish observed signal from generated estimate. For a podcast, a more intelligible listening copy may be exactly the right result, as long as words, timing and speaker identity survived. For an archive, dialect study or evidentiary recording, plausible reconstructed detail isn't evidence of the original. Keep the source, document the model and settings, and mark any passage where content was regenerated. ## When conventional repair is the better first pass AI is most attractive when the damage is broad and difficult to model by hand. It is less compelling when the fault has a clear shape. - **Electrical hum:** stable fundamentals and harmonics can often be reduced with targeted notch or hum tools. Compare the residual so you know whether speech or music was removed with the noise. - **Clicks and pops:** local repair is easier to inspect at the exact event. The [click and pop repair workflow](https://soundforgepro.com/how-to-remove-clicks-pops-sound-forge-pro/) shows the selection and verification steps. - **Clipping:** flattened peaks call for a de-clip model or manual reconstruction; a general denoiser won't help. Even then, severe clipping leaves no guaranteed route back to the original peak shape. - **Export or playback faults:** confirm that the file itself is damaged before processing it. The [distorted-audio fault guide](https://soundforgepro.com/fix-distorted-audio/) separates recording, processing, export and playback causes. Conventional tools can also make an AI comparison more legible. If targeted hum removal solves the problem with fewer side effects, the extra model is unnecessary. If it leaves unstable noise around speech, a speech enhancer may earn a short audition. ## A safer AI audio restoration workflow ![AI audio restoration workflow: source copy, short sample, level match, residual inspection and separate master](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/08/safe-workflow-desktop-20260815-1.webp) Keep the source, process a short sample, match playback level, inspect what changed and export a separate master. 1. **Preserve the source.** Work from a copy. Record a hash when provenance matters and never overwrite the untreated file. 2. **Decide where the file may go.** Confirm retention, access and model-training terms before using a cloud service. Use an approved local workflow when custody is fixed. 3. **Name the damage.** Check the waveform, spectrogram, spectrum and playback path. Do not send an export error or bad headphone connection through a restoration model. 4. **Choose the model class.** Use speech enhancement for speech noise, de-click for impulses, de-clip for flattened peaks and super-resolution only when missing bandwidth is the complaint. 5. **Process a short duplicate.** Include an ordinary passage, the worst fault and a quiet gap. A ten-minute preview of the whole recording tells you less than three deliberate regions. 6. **Match loudness before judging.** Louder and brighter often wins a fast A/B. Reduce the louder path until bypass and processed playback are comparable. 7. **Inspect the residual and transitions.** Listen for missing consonants, pumping ambience, metallic tails, doubled attacks and abrupt changes at edit boundaries. 8. **Export a new lossless master.** Save the service or model, settings and date. Open the export in a second editor and verify start, end, sync, sample rate and channels. ### Make the comparison answer one question Create marked regions for ordinary material, the worst failure and a quiet interval. If the file has stable hum, compare the AI pass with [targeted hum reduction](https://soundforgepro.com/remove-hiss-hum-sound-forge/). If it has impulses, compare local de-click repair. One controlled alternative tells you more than switching among five opaque services. Some services add silence or change duration. Align the output before subtraction and match time and gain precisely, or the residual will mostly show offset and level differences. Use that residual to find what changed, then listen to the source and the result. A residual is a diagnostic view. It doesn't score quality. The [Sound Forge Pro review](https://soundforgepro.com/sound-forge-pro-review-2026/) covers file inspection and batch workflows in the editor. Approve one representative file before scaling a chain or an external AI process. A model update can change an output even when your visible settings stay the same. ## AI restoration export checklist - The untreated source still exists and opens. - The processed file has the expected duration, channels and sample rate. - Words, note attacks and edit timing haven't shifted. - Quiet gaps don't pump or switch ambience unnaturally. - Sibilants, breaths and cymbals don't turn metallic or watery. - The comparison is level-matched. - Generated or reconstructed passages are documented where provenance matters. - The final master has a new filename and does not overwrite the source. ## AI audio restoration FAQ ### Can AI restore bad audio? AI can reduce steady noise, improve spoken-voice clarity, suppress some room reflections and reconstruct plausible missing detail when the model matches the fault. It cannot guarantee the exact original waveform after samples were clipped, overwritten, masked or discarded. ### What is the best AI audio restoration tool? There is no universal best tool. Adobe Podcast and DeepFilterNet target speech enhancement, Kits AI targets vocal repair, and AudioSR targets missing high-frequency content. Choose by damage type, file custody, available control and whether generated detail is acceptable. ### Is there a free AI audio restoration tool? Yes, but the free options solve different jobs. Adobe Podcast has a limited free tier for spoken voice. DeepFilterNet is an open-source local speech enhancer, and AudioSR is an open-source local bandwidth-reconstruction model. None is a universal repair button. ### Can AI restore old music? It can reduce some noise or reconstruct plausible high-frequency detail, but it cannot prove that new detail existed in the performance. Preserve the transfer, work on a duplicate and prefer conservative de-click, de-hum and spectral repair when historical fidelity matters. ### Can AI fix clipped audio? A model designed for de-clipping may estimate missing peak shapes. A general speech denoiser is the wrong first tool. Inspect the flattened peaks, compare a dedicated de-clip process on a short passage and treat the result as an estimate rather than exact recovery. ### Can AI remove echo from audio? Speech-enhancement and de-reverberation models can reduce room reflections and improve intelligibility. They may also thin consonants, change room tone or leave reflections that overlap the voice. Compare a short passage at matched loudness. ### Is AI audio enhancement the same as audio restoration? No. Enhancement aims for a more useful or pleasing result. Restoration tries to reduce known damage while preserving the source. The workflows overlap, but enhancement may regenerate or reshape sound that a conservative restoration would leave unchanged. ### Does AI audio restoration work offline? Yes. DeepFilterNet and AudioSR can run locally after their software, model files and dependencies are installed. Local processing avoids uploading the recording to a cloud service, while backups, shared folders and machine access still need control. ### How do I tell whether AI changed the voice? Keep an untouched source, level-match the output, listen to sibilants, breaths, consonant attacks and word endings, and inspect the residual where available. For high-stakes material, ask a second listener to compare blind and document the model and settings. ### Should I run AI restoration more than once? My default is one pass followed by a matched comparison with the source. Try a second pass only when a named fault remains and the first pass preserved consonants, transients and ambience. Repeated processing can make small artifacts harder to trace. ### Best Audio Restoration Software: 8 Tools Matched to Damage URL: https://soundforgepro.com/audio-restoration-software/ Last updated: 2026-10-09T22:11:08.000Z The best audio restoration software is whichever tool matches the damage and lets you hear the moment cleanup starts removing wanted sound. It also has to fit the way you deliver files. If you want one broad specialist before a specific job forces a different choice, **iZotope RX 12 Standard** is my first shortlist choice for its repair coverage. **Acon Digital Acoustica Premium** is the better value if you also need a conventional editor, **SpectraLayers Pro 13** is stronger when one unwanted sound must be separated visually, and **Audacity 4.0.0** is still the sensible free starting point. That short answer hides the important part: steady hiss, electrical hum, isolated clicks, clipped peaks, room reflections and a voice buried under another sound are not variations of one problem. They call for different repair methods. This guide compares eight current audio restoration and audio repair tools by damage type, platform, workflow and cost. **Versions and vendor pricing were reviewed on September 13, 2026; Sound Forge plan figures below are identified as published list prices, not live checkout quotes.** Subscriptions, sales, regional pricing and taxes can change. If noise is the only damage, narrow the purchase before paying for a full restoration suite: [compare dedicated audio noise-reduction software by job](https://soundforgepro.com/audio-noise-reduction-software/). That comparison separates steady hiss, changing ambience, speech cleanup and live-microphone processing instead of treating every repair tool as though it solved the same problem. ## Audio Repair Software or Corrupted File Repair? Use audio restoration or audio repair software when the file plays but contains hiss, hum, clicks, clipping, room reflections or another unwanted sound. That’s signal repair: the tools below analyze or rebuild audible material. - **File plays, but sounds damaged:** use the restoration comparison below. - **File will not open, is truncated or has a broken header:** preserve the original and use a container- or file-repair workflow; a denoiser cannot restore bytes that are not present. - **The file is healthy, but playback is silent or distorted:** check the output device, driver and monitoring chain before processing the audio. If the failure is still unclear, [diagnose whether it is in the signal, file or playback path](https://soundforgepro.com/audio-restoration/) before buying software. ![Waveform and spectrogram fingerprints for hum, clicks, clipped peaks and reverberation](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/08/damage-fingerprints-desktop-20260815.webp) Hum, impulses, clipping and room reflections require different repair methods. ## The Shortlist: Choose by Repair Job - **Best overall specialist:** iZotope RX 12 Standard: a broad combination of automatic modules, detailed spectral repair and plugin delivery without paying for Advanced. - **Best value all-in-one editor:** Acoustica 8 Premium: editing, spectral repair and restoration plugins for $299 list; the checked launch offer is $224. - **Best for separating one sound:** Steinberg SpectraLayers Pro 13: layer-based spectral selection, unmixing and repair for material that ordinary broadband processing cannot isolate. - **Best for mastering and archives:** Steinberg WaveLab Pro 13: restoration, batch processing, metering, metadata and final delivery in one environment. - **Best for Creative Cloud teams:** Adobe Audition: convenient round-trips from Premiere Pro, waveform and multitrack work, diagnostics and spectral repair. - **Best Windows single-file workflow:** Sound Forge 2026: precise editing, restoration processing and repeatable batch delivery without turning the job into a multitrack session. - **Best free option:** Audacity 4.0.0: capable for constant noise, basic click work and manual edits, with clear limits around deep spectral reconstruction. - **Best low-cost Windows editor:** GoldWave 7.08: practical tape and vinyl cleanup, batch work and command-line control for $59 lifetime or $19 for one year. ## Audio Restoration Software Comparison The matrix covers the currently documented desktop products; historical editions aren’t included. “Plugin” means the package can supply restoration processing inside a compatible host, which doesn’t mean every listed module is available in every edition. Prices are vendor-listed US figures reviewed September 13, 2026; the Acoustica launch discount is shown separately. Regional storefronts and tax can produce a different total. | Software | Best fit | Platform | Workflow | Checked price | | ------------------------ | ----------------------------- | --------------------- | --------------------------- | ---------------------------- | | **RX 12 Standard** | Broad specialist repair | Windows, macOS | Standalone + 18 plugins | $399 perpetual | | **Acoustica 8 Premium** | Editor plus restoration value | Windows, macOS | Standalone + plugins + ARA2 | $299 list; $224 launch offer | | **SpectraLayers Pro 13** | Spectral isolation and layers | Windows, macOS | Standalone + ARA | $359.99 perpetual | | **WaveLab Pro 13** | Archive, mastering, delivery | Windows, macOS | Standalone editor | $499.99 perpetual | | **Adobe Audition** | Video and podcast teams | Windows, macOS | Waveform + multitrack | $22.99/mo annual plan | | **Sound Forge 2026** | Single-file and batch work | Windows | Standalone editor | $299.95 perpetual | | **Audacity 4.0.0** | Free basic restoration | Windows, macOS, Linux | Standalone editor | Free, open source | | **GoldWave 7.08** | Budget Windows cleanup | Windows | Standalone + batch/CLI | $59 lifetime | Price alone can mislead. RX Elements costs less than Standard, but it isn’t a cheaper route to the same module set, and SpectraLayers Elements omits many Pro repair modules. WaveLab Elements is useful software, but the full restoration, spectrum and batch workflow described below belongs to WaveLab Pro. Check the exact edition matrix before comparing products by name. Why are two familiar names missing from the eight? The [Waves Restoration bundle](https://www.waves.com/bundles/restoration) remains a host-based set for profile noise, hum, clicks and crackle, but it isn’t a standalone inspection editor and there’s no declipper in the bundle. [CEDAR Retouch](https://cedaraudio.com/plugins/retouch) is a serious specialist spectral editor with a 14-day trial, aimed at selecting and rebuilding discrete events. Both belong in narrower plugin or spectral-editing comparisons; neither is a like-for-like replacement for every editor above. ## How This Shortlist Was Built This shortlist matches documented repair tools to the jobs they are designed to handle. It considers edition limits, workflow, platform, cost and the amount of control available when a repair starts changing wanted sound. It is not a listening test, and we did not measure these tools. Use the trial protocol below to decide which option preserves your own material best. Each placement was checked against seven practical criteria: - **Repair coverage:** which documented damage classes the current edition can address. - **Inspection and control:** waveform, spectrum, spectrogram, selection, bypass and residual monitoring. - **Workflow fit:** standalone editing, plugin use, ARA, multitrack or cloud processing. - **Repeatability:** presets, batch processing, file naming, metadata and export verification. - **Platform and custody:** operating-system support and whether the source must leave the workstation. - **Edition clarity:** whether the advertised repair tool is actually in the priced edition. - **Current cost and trial:** vendor price, license model and a usable way to test the real file. The order therefore answers “Which tool is the safest first purchase for this repair job?” It doesn’t declare that an automatic result from one product will beat a careful manual repair in another. The trial protocol later in the guide is the tie-breaker for your own recordings. ## What Audio Repair Software Must Actually Do A credible restoration tool should help with at least three stages: identify the fault, control the repair and verify the result. The first stage may use a waveform, spectrum, spectrogram, loudness meter or a difference monitor. For the second you need a useful selection model, adjustable processing and a reversible audition, and the third comes down to level-matched bypass, lossless export and a way to inspect what changed. The damage determines the essential module: - **Constant hiss or fan noise:** noise profiling or adaptive spectral denoise. - **Mains hum and harmonics:** de-hum or narrow harmonic filtering. - **Clicks, pops and crackle:** local interpolation, de-click and de-crackle. - **Flattened peaks:** de-clip, followed by a check for distortion that remains below the peak. - **One cough, horn or chair squeak:** detailed spectral selection and replacement. - **Speech in noise or room reflections:** dialogue isolation or de-reverberation, tested carefully for consonant damage. - **Hundreds of similar files:** batch processing, presets, file naming and verified export. No product restores information with certainty after it has been overwritten or discarded. For [vocal removal and stem separation](https://soundforgepro.com/remove-vocals-sound-forge/) specifically, start with the dedicated workflow before choosing a restoration suite. A declipper estimates a plausible peak. A source-separation model estimates components of a mixture, and a de-reverb processor tries to reduce the reflections that overlap the direct voice. Those can be valuable results, but “reconstructed” is more honest than “recovered.” ## 1\. iZotope RX 12 Standard: Best Overall Specialist **Best for:** editors who regularly receive several kinds of damage and need both a standalone repair bench and restoration plugins inside a DAW or video editor. RX 12 Standard is my starting recommendation for mixed repair work because it combines local [spectral repair](https://izotoperx.net/izotope-rx-spectral-repair/) with dedicated damage-specific modules. The current edition includes the standalone Audio Editor and 18 plugins. Its documented repair set covers De-click, De-clip, De-crackle, De-hum, De-reverb, Dialogue Isolate, Spectral De-noise and Spectral Repair. That combination matters: automatic modules handle repeatable faults, while Spectral Repair gives you a local tool when one event needs attention rather than the whole file. The checked US price is [$399 for RX 12 Standard](https://www.izotope.com/products/rx-standard). Elements is $99, but it is a smaller entry edition; Advanced is $1,399 and adds specialist post-production modules such as De-rustle, De-wind, Dialogue Contour, Ambience Match and Scene Rebalance. Don’t pay for Advanced because a comparison labels it “best.” Pay for it only when those modules belong to your actual delivery work. **Avoid it if:** your jobs are mostly clean single-file edits, trims and exports. RX can do detailed repair, but it isn’t the cheapest ordinary waveform editor and it’s no full music-production DAW either. For the exact tradeoff with this site’s core editor, use our [Sound Forge vs iZotope RX comparison](https://soundforgepro.com/sound-forge-pro-vs-izotope-rx/). ## 2\. Acon Digital Acoustica Premium: Best Value All-in-One **Best for:** someone who wants a conventional audio editor and a serious restoration bundle under one perpetual license. [Acoustica 8 Premium](https://acondigital.com/products/acoustica) combines spectral editing with DeNoise 3, Extract:Dialogue 2 and dialogue-cleaning tools. The current Premium license lists at $299, with a $224 launch offer when checked on September 13, 2026\. It is a perpetual editor-and-plugin package, not just a set of effects that needs another editor. Choose the edition carefully: Standard provides stereo editing and in-app restoration; Premium adds DAW plugins, Extract:Dialogue 2 and support up to 7.1.2\. Ultimate adds DeVerberate 3, DeFilter and 9.1.6 support. All three include ARA2 integration with compatible hosts. Try another option if your job depends on a specific RX Advanced module such as Dialogue Contour or Ambience Match. Acoustica’s Remix provides stem separation alongside its repair tools. Compare its editing workflow with SpectraLayers’ layers on your own file; the Acoustica trial lasts 30 days and requires no card. ## 3\. SpectraLayers Pro 13: Best for Visual Spectral Isolation **Best for:** a repair where the unwanted event can be seen and selected as an object or layer, such as a cough under music, bleed between sources, a tonal intrusion or a sound that overlaps in time but occupies a distinct spectral shape. SpectraLayers approaches audio more like an image editor than a conventional waveform tool. Pro 13 combines manual spectral selection with DeNoise, DeReverb, DeHum, DeClick, DeClip, DeBleed, voice repair and batch processing. Its layer model is the reason to buy it: you can separate, inspect and rebalance components rather than committing every decision to one rendered waveform. [SpectraLayers Pro 13 lists at $359.99](https://www.steinberg.net/spectralayers/compare-editions/); Elements 13 is $89.99 but omits many of the Pro repair and unmixing modules. Steinberg offers a [60-day Pro trial](https://www.steinberg.net/spectralayers/trial/), which is long enough to test several representative failures rather than one flattering demo. **Avoid it if:** most of your work is straightforward trimming, level correction and batch conversion. Spectral layers are powerful, but they introduce a different editing model and more decisions than a simple denoise-and-deliver job needs. ![Audio repair workflows in a waveform editor, spectral editor, DAW plugin chain and cloud service](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/08/workflow-types-desktop-20260815.webp) Choose where the file is inspected and processed. Cloud access and retention terms depend on the service. ## 4\. WaveLab Pro 13: Best for Restoration Through Delivery **Best for:** mastering engineers, archive transfers and long-form delivery work where restoration must continue into sequencing, metadata, loudness control, batch rendering and quality assurance. WaveLab Pro is not merely a repair suite. The current version combines RestoreRig, full restoration functions, a Spectrum Editor, wavelet display, batch processing, external-editor integration and mastering/delivery tools. That wider chain is its advantage: an archive project can move from cleanup to file naming, metadata and final derivatives without pretending restoration ends when the noise disappears. [WaveLab Pro 13 lists at $499.99](https://www.steinberg.net/wavelab/). Steinberg’s [release notes list version 13.0.30 dated July 22, 2026](https://www.steinberg.net/wavelab/release-notes/13/). Elements starts at $99.99 and includes RestoreRig, but its restoration functions are limited and it lacks the Pro batch processor, Spectrum Editor and wavelet display. Confirm the [edition comparison](https://www.steinberg.net/wavelab/compare-editions/) before treating Elements as a lower-priced substitute. **Avoid it if:** you need only occasional dialogue cleanup or one troublesome sound. Its cost and mastering depth make more sense when restoration is one stage in a repeatable production or preservation pipeline. ## 5\. Adobe Audition: Best for Video and Podcast Teams **Best for:** editors already paying for Creative Cloud who need waveform repair, multitrack assembly and an efficient path between audio and Premiere Pro. Audition’s [official restoration documentation](https://helpx.adobe.com/audition/desktop/effects-reference/noise-reduction-restoration-effects.html) covers spectral-frequency editing, Diagnostics, DeClipper, DeHummer, adaptive noise reduction, DeReverb, DeNoise and Sound Remover. The combination of waveform and multitrack views makes it practical for podcasts and video post: repair a source destructively in the Waveform Editor, then return to the mix and automation in Multitrack. The current US single-app offer is [$22.99 per month with an annual commitment billed monthly](https://www.adobe.com/products/audition.html), with a seven-day full-app trial. That is attractive when Audition is already part of the team’s Adobe plan. As a standalone long-term restoration purchase, the subscription can cost more than a perpetual specialist editor. **Avoid it if:** you want a perpetual license, Linux support or the newest specialist source-separation modules. Audition remains useful, but its strongest buying argument is workflow integration, rather than a claim that every restoration algorithm beats a dedicated current suite. ## 6\. Sound Forge 2026: Best for Windows Single-File and Batch Work **Best for:** Windows users who receive one finished WAV, voice recording, vinyl side or folder of similarly prepared files and want fast, exact waveform editing plus repeatable processing. Sound Forge’s strength is focus. It records and edits one file closely, hosts processing chains, supports restoration work and turns a verified setup into repeatable batch output. Boris FX describes the current product around sample-accurate editing, recording up to 32 channels, restoration tools, [WaveColor](https://soundforgepro.com/how-to-use-wavecolor-in-sound-forge-pro/) and batch processing. Boris FX [acquired Sound Forge from MAGIX on March 30, 2026](https://blog.borisfx.com/press/boris-fx-acquires-vegas-pro-sound-forge-and-acid-pro), so older MAGIX pricing and trial articles should not be treated as current. Boris FX’s published launch list prices are $299.95 for Sound Forge and $399.95 for Sound Forge Plus; annual plans were listed at $149.95 and $199.95\. Check the current offer before buying; those launch figures do not establish today’s discounted checkout total. The [official trial is currently 15 days](https://vfx.borisfx.com/sound-forge-trial), Windows only, and does not require a credit card. Our [Sound Forge pricing guide](https://soundforgepro.com/sound-forge-pro-pricing/) explains the editions, while the [2026 Sound Forge review](https://soundforgepro.com/sound-forge-pro-review-2026/) separates its excellent single-file work from the multitrack and deep-spectral jobs it should not own. **Avoid it if:** you work on macOS or Linux, need a full multitrack production environment, or routinely paint around complex interference in a spectrogram. A specialist plugin can extend Sound Forge; that doesn’t make the base editor identical to RX or SpectraLayers. ## 7\. Audacity 4.0.0: Best Free Audio Restoration Software **Best for:** learning the repair order, cleaning constant background noise, fixing isolated defects manually and completing occasional work without a license cost. The current [Audacity 4.0.0 download](https://www.audacityteam.org/download/) is free and open source on Windows, macOS and Linux. Its current manual documents Noise Reduction for steady backgrounds, Click Removal for longer selections, Clip Fix, the tiny-selection Repair effect, spectral selection and ordinary editing. That is a useful basic repair bench, provided you test the exact workflow rather than assuming every Audacity 3 feature carried into the first 4.0 release. Those repair limits still matter. Audacity’s [Noise Reduction guidance](https://www.audacityteam.org/manual/effects/noise-removal-and-repair/noise-reduction/) says the method suits constant background sound, not one-off events. [Clip Fix is most likely to help lightly clipped audio](https://www.audacityteam.org/manual/effects/noise-removal-and-repair/clip-fix/), while [Repair accepts at most 128 samples](https://www.audacityteam.org/manual/effects/noise-removal-and-repair/repair/)—enough for a tiny click, not a missing phrase. [Audacity 4.0.0 became current on September 3, 2026](https://www.audacityteam.org/changelog/) and saves new .aup4 projects. It opens .aup3 projects and converts them without changing the original, but cannot save the converted project back to .aup3\. The official compatibility notes also list Time Tracks, Note/MIDI tracks, Mixer, Macro Manager and the scripting pipe, VAMP/LADSPA hosting and Play-at-speed as unavailable in 4.0, with some exporting, rendering, analyzer and effect features still missing. If one of those paths is essential, keep a tested Audacity 3.7.9 workflow until a 4.x release supplies it. **Avoid it if:** deadlines depend on dialogue isolation, advanced de-reverb, deep batch automation or fast repair of many unrelated faults. “Free” becomes expensive when manual work or failed processing consumes the project budget. Start with our [noise-reduction workflow](https://soundforgepro.com/how-to-remove-background-noise-in-sound-forge-pro/) and move to a trial only after you can name the missing capability. ## 8\. GoldWave 7.08: Best Low-Cost Windows Editor **Best for:** Windows users restoring tape or vinyl, processing many files or building a repeatable low-cost workflow with batch and command-line options. [GoldWave 7.08](https://goldwave.com/), released August 25, 2026, is the current Windows desktop release and requires 64-bit Windows 10 or later with an AVX2-capable processor. It includes noise reduction, pop/click filtering, batch processing, command-line control and the recording, editing and format tools needed around restoration. The current licenses are [$19 for one year or $59 lifetime](https://www.goldwave.com/gwbuy.php). Both include GoldWave Infinity, the separate browser-based cross-platform version. The evaluation mode is not a permanently free edition. [GoldWave](https://soundforgepro.com/goldwave-vs-sound-forge/) is less glamorous than the spectral specialist tools, but the practical feature mix is useful for transfers and repetitive cleanup. Its official [restoration tutorial](https://goldwave.com/help/desktop/AppendixTutorial.html) also gives buyers a clearer idea of the intended workflow than a generic marketplace description. Avoid it if: you need a mature native macOS/Linux desktop editor, modern dialogue separation or detailed layer-based spectral repair. GoldWave 7.08 itself requires 64-bit Windows 10 or later and AVX2; Infinity broadens platform access but is a separate browser application. Buy the desktop editor for efficient conventional restoration. A low lifetime price doesn’t imply every advanced module is included. ## Standalone Editor, DAW Plugin or Cloud AI? Use a standalone editor when you need to inspect a whole file, mark test passages and save successive repairs. Plugins make more sense when processing must follow clips inside an existing mix or video timeline. Packages that offer both let you choose the workflow without changing the repair method. Cloud AI services solve a different workflow. Uploading speech and receiving an enhanced file can be convenient, particularly for a one-off interview. But the service may give you less control over the residual, processing order, model version and revision history. File custody also matters for unreleased music, client interviews, medical material or legal evidence. Read retention and model-training terms before uploading, and keep the original outside the service. For a controlled comparison, run the same source through every candidate. Never compare a vendor demo cleaned by an expert with your own untreated problem file. The separate [AI audio restoration guide](https://soundforgepro.com/ai-audio-restoration/) explains how model-based and one-click services change the workflow, where they can save time and where limited control or file custody should change the decision. It is a guide to that category, not evidence that one desktop suite beats another. ## A Trial Protocol for Your Own Files ![Five-step audio software trial using one source, level matching, residual listening, repeatability and export verification](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/08/trial-test-desktop-20260815.webp) A fair trial uses the same source, matched loudness, residual listening, a repeat run, and a verified lossless export. 1. **Use the same damaged file.** Choose one normal passage, one worst-case passage and one quiet passage. A tool that fixes the easy section may fail on the material that matters. 2. **Match output loudness.** Attenuate whichever version is louder until bypass and processed playback have comparable loudness. Otherwise a level change can masquerade as a cleaner result. 3. **Listen to the residual.** Where available, audition the difference or removed-noise output. Wanted consonants or attacks can warn of overprocessing, but changed reverb or reconstructed peaks may legitimately appear there. Judge the repaired signal too, and turn diagnostic monitoring off before export. 4. **Repeat the job.** Save the chain, reopen the project and process several representative files. Check whether batch output preserves names, sample rate, bit depth, channels and metadata as expected. 5. **Verify a lossless export elsewhere.** Open the rendered WAV in a second player or editor. Check the beginning, end, loudest passage and silence. Never discover a truncated render after deleting the session. Run the trial on the computer that must deliver the work. Plugin formats, operating systems, graphics requirements and copy protection are all part of the purchase. A theoretically stronger processor is the wrong choice if it can’t open the session reliably or if its batch path removes required metadata. ## When Software Cannot Restore the Original ![Four limits of audio repair: clipped peaks, overlapping reflections, lost codec detail and mixed noise](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/10/repair-limits-20260913-v2-v20261005.webp) Restoration estimates missing detail and can alter wanted sound. Keep the untouched original. Missing information is the hard limit. Clipping removes the original peak contour; room reflections overlap the direct voice; lossy codecs discard detail. Repair can estimate a useful result, but cannot certify the exact original. Noise removal has a different limitation: a profile-based processor needs a usable noise sample, while adaptive and model-based tools may not. Either method can remove wanted sound when it cannot distinguish that sound from the noise. Re-record when the performance can be repeated more cheaply than it can be repaired. If a lossless master, camera original or earlier export exists, go back to that source. Use a transfer specialist when the carrier is fragile, moldy, mechanically damaged or irreplaceable. For signal damage that remains repairable, our guides to [reducing echo and room reflections](https://soundforgepro.com/remove-echo-from-audio/) and [diagnosing distorted audio](https://soundforgepro.com/fix-distorted-audio/) show where common one-button claims stop matching the evidence. ## Audio Restoration Software FAQ ### What is the best audio repair software? For mixed audible defects, iZotope RX 12 Standard is our broad specialist recommendation; Acoustica Premium is the better-value editor-and-restoration bundle, and Audacity 4.0.0 is the free starting point. If the audio file will not open or is missing data, use a container- or file-repair workflow instead—restoration processing cannot recreate absent bytes. For module-level detail, see the [full RX 12 review on izotoperx.net](https://izotoperx.net/izotope-rx-12-review/). ### What is the best free audio restoration software? Audacity 4.0.0 is our free starting recommendation across Windows, macOS and Linux. It can reduce constant noise, support spectral selections and repair short local defects, but it does not replace current specialist dialogue isolation, de-reverb or deep spectral reconstruction tools. ### Can audio restoration software fix clipping? A declipper can estimate rounded peaks when clipping is moderate and enough surrounding information remains. It cannot guarantee the exact original waveform after repeated flat plateaus have discarded the peak shape, and it cannot remove distortion created elsewhere in the signal chain. ### Do I need a standalone editor or an audio restoration plugin? Use a standalone editor for diagnosis, local spectral work, versioned repair and final-file inspection. Use a plugin when restoration must remain inside a DAW or video timeline and follow editorial changes. Packages such as RX Standard provide both, so the same repair can move between workflows. ### Is cloud AI safe for confidential recordings? That depends on the service’s retention, access and model-training terms. For confidential, unreleased, medical or legal material, prefer an offline tool unless the organization has approved the service. Keep the untouched original locally and document the model or service version used. ### Which audio restoration software works on Linux? Audacity is the clear native Linux option in this shortlist. The current desktop versions of RX, Acoustica, SpectraLayers, WaveLab and Audition target Windows and macOS, while Sound Forge and GoldWave 7.08 are Windows-only. A GoldWave license also includes the browser-based Infinity app for Linux and other platforms. Verify current system requirements before buying because platform support can change. ### Should I buy software before diagnosing the recording? No. First confirm that the problem is in the audio signal rather than the file container, playback device or monitoring chain. Then identify whether the damage is steady noise, impulses, clipping, reverberation, interference or missing data and trial the tool that owns that repair class. ### What software should I use to clean up old recordings? Start with the carrier and the damage. For a tape or vinyl transfer with steady hiss, hum and isolated clicks, Audacity or GoldWave can be enough for a careful low-cost pass; Acoustica Premium adds a stronger editor-and-restoration bundle. Choose RX Standard when the archive also contains clipping, changing noise, room sound or discrete events that need local spectral repair. Preserve the raw transfer before processing, and use a transfer specialist for fragile or irreplaceable media. ### How to Fix Distorted Audio: Find the Fault First URL: https://soundforgepro.com/fix-distorted-audio/ Last updated: 2026-10-09T21:51:11.000Z **Quick answer:** to fix distorted audio, locate the first stage where the fault appears before opening a repair plug-in. Play the same ten-second passage in another app and on another device, bypass the complete effect chain, then export an uncompressed WAV. If the defect stays at the same timestamp in every copy, inspect the file and capture path. If it appears only in one player, output, or compressed export, repair that stage instead. A declipper cannot fix a Windows driver, a damaged speaker, a dropout, or a poor encoder setting. “Distorted” describes what you hear. It doesn't tell you what failed. Hard clipping, microphone overload, digital dropouts, codec damage and playback faults can all sound harsh, and each needs its own test and its own repair. If the waveform and recording history point to hard clipping, move to the narrower [Sound Forge clipped-audio repair workflow](https://soundforgepro.com/fix-clipped-audio-sound-forge/) for detailed DeClipper settings. ![Five-stage audio path from source and input through processing export and playback with the first fault highlighted](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/08/first-bad-stage-desktop.webp) Test source, input, edit, export, and playback in order; the first bad stage owns the fix. ## Start with these diagnostic checks | What you hear | Diagnostic check | Likely stage | Next move | | -------------------------------------------------- | -------------------------------------------------------------- | ------------------------------------------------- | ----------------------------------------------- | | The same buzz follows the file | Two players and two devices reproduce it at the same timestamp | Capture, stored file, or rendered processing | Inspect the waveform and source history | | Only one device or app sounds wrong | Another output or player is clean | Playback, driver, enhancement, cable, or hardware | Fix playback; do not process the file | | The editor is clean but the delivery file is rough | An uncompressed WAV is clean while MP3 or AAC is not | Export level or codec | Render a safe WAV, then encode once | | Loud sources distort at low interface gain | More microphone distance or an input pad cleans a new take | Microphone or an overloaded input stage | Reduce level at the overloaded stage | | Random clicks or gaps change with buffer size | A larger buffer changes or removes the symptom | Real-time recording or playback path | Check driver, buffer, and sample-rate agreement | Work on a copy. Mark the exact bad timestamp and change one variable per test: 1. **Test playback.** Try another player first; then test different headphones or an output device, changing one thing at a time. 2. **Change the processing state.** Bypass the complete chain. Re-enable one processor at a time only if the bypass is clean. 3. **Change the encoding.** Render an uncompressed PCM or floating-point WAV at the source sample rate with conservative output level. 4. **Change the source.** Open a known-clean file through the same playback route. 5. **Change one stage.** If two settings move together, the test hasn't isolated anything. This order prevents a common bad edit: permanently dulling a clean recording with EQ because one speaker or Windows enhancement was the real problem. ## Hear five files that need different decisions The listening pack uses one 11.12-second voice excerpt from LibriVox, whose recordings are public domain in the United States. Every file is 48 kHz mono and matched to approximately -25 LUFS to reduce overall level differences. Integrated matching does not make every syllable equally loud, so compare the same passage at a comfortable listening level. The hard-clipped copy, simulated input overload, simulated dropouts, and low-bitrate round trip are controlled derivatives. Treat them as evidence examples rather than claims about a named microphone or recorder. The reference was level-processed for comparison: “untreated” in its existing player label means no deliberately added defect, not an untouched source recording. ### 1\. Clean reference Untreated voice used for every controlled derivative. Your browser does not support HTML audio. MP3 preview: -25.12 LUFS, -7.14 dBTP. WAV master: -24.84 LUFS, -6.87 dBTP. [Download the 48 kHz WAV master](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/media/2026/08/01-clean-reference.wav) ### 2\. Hard-clipped, then lowered The signal hit a -1 dBFS ceiling before level matching. The flat shelves remain. Your browser does not support HTML audio. MP3 preview: -25.09 LUFS, -12.75 dBTP. WAV master: -24.83 LUFS, -12.48 dBTP. [Download the 48 kHz WAV master](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/media/2026/08/03-hard-clipped-then-lowered.wav) ### 3\. Simulated input overload A deterministic nonlinear derivative, clearly labeled simulated. Your browser does not support HTML audio. MP3 preview: -25.03 LUFS, -10.63 dBTP. WAV master: -24.76 LUFS, -10.38 dBTP. [Download the 48 kHz WAV master](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/media/2026/08/04-simulated-input-overload.wav) ### 4\. Simulated dropouts Three short missing intervals. Loudness and crest factor remain close to the clean file. Your browser does not support HTML audio. MP3 preview: -25.12 LUFS, -7.14 dBTP. WAV master: -24.85 LUFS, -6.87 dBTP. [Download the 48 kHz WAV master](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/media/2026/08/05-simulated-dropouts.wav) ### 5\. Low-bitrate export round trip The clean source passed through 32 kbps MP3 at a 24 kHz intermediate rate. Your browser does not support HTML audio. MP3 preview: -25.14 LUFS, -7.36 dBTP. WAV master: -24.87 LUFS, -7.10 dBTP. [Download the 48 kHz WAV master](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/media/2026/08/06-low-bitrate-export.wav) Reproducibility and source record Speech: Claudia Caldi reading *Epitaph on a Sailor* in [LibriVox Short Story Collection Vol. 106](https://librivox.org/short-story-collection-vol-106/). Source SHA-256 `4f9447805ec0cc4b07e07fbb1e74316805fe777b62f48d7eb3dcd7fa628a256a`. [LibriVox recordings are public domain in the United States](https://librivox.org/pages/public-domain/); check local status elsewhere. Method: NumPy 2.0.2 for deterministic signal processing and FFmpeg 8.1.2 for loudness matching, explicit 48 kHz mono delivery, and MP3 encoding. Build script SHA-256 `04cbe430a0c7b57d60ec58b5d18af7433267fa3c304182d1ba6fe45331ab8320`. The complete output hashes and measurements are recorded in the dated build manifest. The clean and hard-clipped WAV masters measure -24.84 and -24.83 LUFS, yet the hard-clipped version has 2,975 samples that reached a -1 dBFS ceiling before level matching. The delivered clean and clipped WAVs have crest factors of 18.795 and 13.102 dB respectively. Those figures describe the complete clipping-and-delivery procedure, not clipping measured in isolation. Turning it down changed the peak level, but the discarded curve stayed flat. The dropout example has almost the same integrated loudness and crest factor as the clean file; the missing intervals are the defect. One meter cannot classify both. ![Four distortion fingerprints for hard clipping input saturation digital dropout and low-bitrate codec damage](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/08/distortion-fingerprints-desktop.webp) Clockwise from top left: flat clipping, rounded overload, codec smear, and a dropout require different responses. ## Read the waveform, timing, and spectrum together Repeated flat shelves at the same positive or negative value point to hard clipping, but they don't prove it on their own: limiting or an intentionally square-like musical waveform can look much the same. Check the recording history and listen to the marked passage. Rounded peaks don't prove the recording is clean either, because a microphone, transmitter, preamp or soft limiter can distort while the curve stays smooth. And a sample peak below 0 dBFS doesn't rule out earlier damage or a higher reconstructed true peak. Timing gives another clue. Distortion attached to loud vowels, drum hits, or plosives points toward overload, while a click at an edit boundary suggests a discontinuity. Gaps that appear during recording can indicate a real-time path or stored dropout. Swirling consonants and narrowed high-frequency detail after a small export usually mean a lossy codec. Stable hum and broadband hiss are noise problems even when a client calls them distortion; use the separate [hiss and 50/60 Hz hum workflow](https://soundforgepro.com/remove-hiss-hum-sound-forge/) for those faults. Use the waveform to locate a discontinuity and a spectrogram to see how frequency content changes over time. A spectrum averaged over a selection can show tonal changes, but it can't tell you exactly when a gap happened. The examples came from different operations (hard limiting, nonlinear saturation, three zeroed intervals and a low-bitrate encode/decode) rather than from one universal “distortion” effect. The display helps you decide what to inspect. It won't grade the repair. Statistics provides sample-peak, true-peak, RMS and loudness readings, and Average value can reveal DC offset. Crest factor is derived from compatible peak and RMS measurements; the documented dialog has no dedicated field for it. No single value identifies every distortion type. The [Sound Forge Statistics guide](https://soundforgepro.com/how-to-use-statistics-sound-forge-pro/) explains what those readings measure and how to compare a selection with the complete file. ## Decide whether the file or playback path is damaged Play the marked passage outside Sound Forge, then copy it to a phone or another computer and use different headphones. Keep listening level moderate. If the same consonant buzzes at the same timestamp through every path, the defect is probably stored in the file or was created before it. If the problem changes with the playback route, investigate that route before editing. Distortion on one side alone is inconclusive: the fault could be stored in one channel or introduced by the output. Microsoft's current [Windows distorted-audio support page](https://support.microsoft.com/en-us/windows/hardware/audio/fix-distorted-or-crackling-audio-in-windows) lists audio enhancements, default format, drivers and Windows audio services as playback branches for Windows 11 and Windows 10\. Work through one branch at a time and choose a format the output device supports. Matching rates can simplify a diagnostic test, but a working shared-mode resampling path isn't distorted by nature, and native ASIO doesn't use every Windows default-format setting. A damaged loudspeaker often gets rougher as playback level rises, and a loose cable can react to movement. Bluetooth can switch profiles or add codec constraints. A clean known-reference file is useful here: if it fails through the same output, the user's recording is no longer the first suspect. Noise reduction, normalization, and declipping can't improve a file that was clean before the faulty playback stage. ## 32-bit float headroom is different from clipped PCM ![Smooth over-range float waveform returning after gain reduction versus clipped PCM plateaus remaining flat](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/08/float-vs-clipped-desktop.webp) Float headroom preserves the curve; hard clipping discards the peak shape before level is lowered. For a numerical headroom demonstration, the source was decoded to 32-bit float samples, promoted to 64-bit floating-point arrays, multiplied by exactly 4, and then divided by 4\. That gain is approximately 12.0412 dB; the exact factors, not the rounded dB label, define this numerical test. The recovered output had a maximum absolute numerical error of 0, and its WAV SHA-256 matched the clean reference. A second branch received the same gain but hit a hard -1 dBFS ceiling first. After level reduction, the flat shelves remained and the file no longer matched the source. None of this means every file labeled 32-bit float can be rescued. Floating-point storage can keep values above full scale after clean conversion, but it can't rebuild a microphone capsule, wireless transmitter, preamp or analog stage that saturated before conversion. Lowering gain may reveal headroom around distortion that's already baked in. [Sound Devices explains how float WAV files retain over-range values](https://www.sounddevices.com/32-bit-float-files-explained/), and that storage property still can't lift the limits of the hardware feeding the file. In Sound Forge, lower the level on a working copy and inspect the loud passage at sample scale. If smooth peaks come back and the harshness goes away, the file held recoverable over-range values. If repeated plateaus and harshness remain, the missing peak shape has to be estimated. A declipper can draw a plausible continuation, but it can't guarantee the exact original samples. Once that diagnosis is confirmed, move on to the detailed [clipped-recording repair guide](https://soundforgepro.com/fix-clipped-audio-sound-forge/). ## If loud sources distort at low gain, move upstream A shout, a brass instrument, a snare or an amplified cabinet can overload a microphone capsule before the signal ever reaches the interface gain knob. A transmitter or preamp can fail at yet another point ahead of the clean converter. Turning software gain down can't protect an earlier stage. [RØDE's current microphone-overload guidance](https://help.rode.com/hc/en-us/articles/16024456203151-How-to-Reduce-Audio-Distortion-During-Recording) confirms that exceeding a microphone's maximum SPL can distort the signal before it reaches the recorder. Try one change, then record and compare a new ten-second take: - move the microphone farther from the source; - lower the source level when that is possible; - engage a documented pad only when it sits before the overloaded electronic stage; it can't prevent physical capsule overload; - use a microphone specified for the source's sound-pressure level; - monitor the direct input before software effects. If the new take is clean, software repair is a salvage step for the old file. Sustained upstream overload changes the signal throughout the affected phrase and is usually less forgiving than a few short digital clips. Re-record while the performance and setup still exist. ## Pops, crackle, and dropouts need their own branch Hard clipping usually follows loud peaks, while buffer trouble and dropouts can cause ticks, gaps or bursts at less predictable levels. For one controlled test, raise the audio-interface buffer, close competing real-time loads, use the manufacturer's current driver, and make the device and project sample rates agree. Don't change all four at once. In Sound Forge, use [the documented playback-buffer controls](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/optimizing%5Fsound%5Fforge.htm): Options > Preferences > Audio, or Advanced > Configure for the selected ASIO device. Raise buffering only as far as you need to, since it also adds delay. If the problem occurs during live playback but the rendered WAV is clean, there is no damaged section to restore. Fix the real-time path. If short impulses were recorded into an otherwise good file, use the [click-and-pop repair workflow](https://soundforgepro.com/how-to-remove-clicks-pops-sound-forge-pro/). A full-file DeClipper is poorly targeted for isolated discontinuities, and aggressive de-crackle can soften wanted attacks. The dropout example above contains three deterministic gaps: 12 ms at 2.520 seconds, 18 ms at 6.270 seconds, and 9 ms at 8.840 seconds. Its -24.85 LUFS measurement is close to the clean source, yet three intervals were deliberately removed. This is another reason to keep the timestamp and waveform beside the meter reading. ## If distortion appears only after export Render the same short selection to an uncompressed WAV with optional normalization and lossy encoding disabled. Compare that WAV with playback inside Sound Forge at matched loudness. - If both are distorted, bypass the edit chain and inspect its output level. - If the editor is clean but the WAV is not, isolate each processing stage used by the export. - If WAV is clean but MP3 or AAC is rough, encode once from the lossless master and compare a higher bitrate. - If only an uploaded platform sounds wrong, download or monitor the platform's processed version before changing the master. A lossy codec can smear transients, narrow bandwidth, and add watery texture without a clipping plateau. Re-encoding an already lossy file adds another generation of loss. Keep one verified WAV master and make delivery copies from it. The [Sound Forge MP3 export guide](https://soundforgepro.com/how-to-export-mp3-from-sound-forge-pro/) covers format choice, bitrate, sample rate, and post-export verification. Check output level separately. Reconstructed peaks can rise after declipping, and analog reconstruction can exceed the sample values. A delivery target doesn't prove that existing distortion has been repaired; it only describes the output level. ## Use a controlled Sound Forge diagnostic workflow Sound Forge is useful for this job because it lets you inspect one file closely, bypass a processing chain, select short regions, and render a new file. The current Boris FX Sound Forge Pro 2026 repair documentation places **DeClipper** in the **Effects** menu. Use it only after the tests point to clipped or overmodulated material. 1. **Preserve the untouched source.** Keep an unchanged backup of the source file. Open a separate working copy; avoid unnecessary sample-rate conversion or reduced bit depth. 2. **Mark clean and damaged passages.** Include the exact bad timestamp, one normal phrase, and a quiet ending. A repair that survives one clipped syllable can still damage ordinary audio. 3. **Bypass the complete processing chain.** If the fault disappears, re-enable one processor at a time and watch the chain's output level. 4. **Inspect the stored signal.** Use sample-level zoom and Statistics. Repeated same-height plateaus are a clue rather than proof, so check whether intentional limiting or synthesis explains them. Curved harsh peaks need a different diagnosis. 5. **Route the fault to the smallest suitable tool.** Confirmed short clipping goes to Effects > DeClipper. Isolated impulses go to click repair. Hiss and hum go to stationary-noise tools. Playback faults stay outside the file. 6. **Preview only the affected selection.** Start conservatively. Level-match Bypass and listen to the worst peak, a normal phrase, and the quiet ending. 7. **Render a new file.** Keep the source. Reopen the rendered WAV, verify the marked timestamp, inspect peak level, and listen outside Sound Forge. 8. **Stop when repair damages wanted detail.** Back off if consonants, attacks, pitch, or room continuity become less natural than the original fault. Boris FX describes the current DeClipper alongside DeClicker, DeCrackler, and DeHisser in the [Sound Forge Pro 2026 repair section](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/proonly/repair.htm). The same page says classic restoration commands remain available in the Tools menu. It does not support treating any legacy command label as a universal current path, so this guide keeps the verified current route. [Current iZotope guidance](https://www.izotope.com/community/blog/repairing-a-distorted-audio-track) draws the same line from another restoration tool: select the distorted portion, set or suggest a threshold, preview, adjust, and then render. It also warns that reconstructed peaks can go above zero and that [RX De-clip](https://izotoperx.net/fix-clipped-audio-rx-de-clip/) isn't meant for brickwall-limited masters. The product differs, but the diagnostic lesson carries over: work locally, leave output room, and don't treat every flattened master as capture clipping. For a free option once you've confirmed light clipping, [Audacity Clip Fix](https://www.audacityteam.org/manual/effects/noise-removal-and-repair/clip-fix/) estimates short missing peaks and lowers the level to leave room for them. Try it on a copy of the affected passage before any other processing. It won't cure microphone overload or long missing sections. ## Choose repair, mitigation, or a new recording ![Decision routes for playback fault localized declipping and rerecording an overloaded microphone source](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/08/repair-route-desktop.webp) Fix playback outside the file, declip only confirmed short plateaus, and re-record sustained upstream overload when possible. | Confirmed fault | First action | Realistic result | Stop condition | | ------------------------------------ | ----------------------------------------------------------------- | -------------------------------------------------------- | ------------------------------------------------------ | | Playback-only distortion | Fix device, format, driver, service, cable, or speaker | The original file remains untouched | A known-clean file plays correctly | | Short hard-clipped peaks | Conservative local DeClipper pass | Plausible peak reconstruction and reduced buzz | Attacks or consonants become artificial | | Sustained capsule or preamp overload | Re-record with lower upstream level | A clean replacement when the performance can be repeated | Do not spend longer repairing than recreating the take | | Isolated clicks or gaps | Click repair for impulses; interpolation only for very short gaps | Short faults may become unobtrusive | Wanted transients lose definition | | Low-bitrate delivery damage | Return to a lossless master and encode once | A better-quality delivery if a clean master survives | No lossless or higher-quality source exists | Re-record when whole words stay buzzy after a conservative attempt, when overload covers most of the take, when the only source has been through several lossy exports, or when repair strips out speech detail the job needs. For irreplaceable material, preserve the source and make two derivatives when it helps: a conservative listening copy and, if necessary, a more heavily processed access copy. Do not overwrite the only surviving recording. The unchanged source stays the preservation master; neither processed copy replaces it. ## Prevent the next distorted recording - Record a ten-second rehearsal, stop, and play it back before the full take. - Set level at the stage that's actually overloading. Digital attenuation after capture can't protect an analog input. - Leave practical headroom instead of aiming every peak at 0 dBFS. - Match device and project sample rates, then use the interface maker's current driver. - Monitor before software effects when diagnosing the capture path. - Keep a lossless master and create each delivery format from that master once. - Save processing as a new version so a bad render never replaces the clean source. The [Sound Forge recording guide](https://soundforgepro.com/how-to-record-audio-in-sound-forge-pro/) covers input selection, monitoring, meters, and the short test-recording habit. Prevention preserves the original samples; restoration estimates what damaged stages changed or removed. ## Fix distorted audio FAQ ### Can distorted audio be completely fixed? Sometimes. Short digital clipping, isolated clicks, and an accidental export overload may improve substantially. Complete recovery from sustained microphone, preamp, or codec damage cannot be guaranteed because the original waveform was changed or discarded before repair. ### Does lowering the volume fix distortion? It can restore over-range floating-point audio when the waveform was preserved. Lowering hard-clipped PCM makes the fault quieter but leaves flattened samples and added harmonics. ### Can EQ remove distortion? EQ can reduce an objectionable frequency band, but it cannot rebuild clipped peaks or reverse nonlinear overload. Use it as tonal mitigation after diagnosis, then compare at matched loudness. ### Why is audio distorted only after export? Check the rendered processing chain, output level, sample-rate handling, and lossy encoder. Export a short uncompressed WAV first. If that file is clean, test one delivery format and bitrate at a time. ### Why do speakers sound distorted when headphones are clean? The file may be fine. Test lower speaker level, another cable or output, disabled enhancements, and a known-clean file. A speaker driver, amplifier, Windows setting, or connection can fail while headphones remain clean. ### Can 32-bit float audio still be distorted? Yes. Float can preserve over-range values after clean conversion, but it cannot protect a microphone capsule, transmitter, preamp, or other stage that overloaded before conversion. ### Can Sound Forge repair distorted audio? Sound Forge Pro 2026 includes DeClipper for some clipped or overmodulated passages, plus tools for clicks, crackle, and hiss. It cannot repair a faulty playback device or guarantee recovery from severe upstream overload. ### How do I fix distorted audio on Windows 11? First test the same file in another player and output. For playback-only distortion, Microsoft recommends checking audio enhancements, the default format, drivers, and Windows Audio services. If the defect follows the file at the same timestamp, inspect the file instead. ## Choose the fix that matches the fault Keep the diagnosis simple: find the first bad stage, confirm it with one controlled change, then use the smallest repair that fits. Playback faults stay outside the file. Dropouts and clicks get local treatment. Codec damage sends you back to the lossless master. Confirmed clipping earns a conservative DeClipper test. Sustained upstream overload usually earns a new recording. If more than one defect is present, use the [audio restoration diagnostic guide](https://soundforgepro.com/audio-restoration/) to separate clipping, noise, clicks, and room reflections before combining treatments. ### How to Remove Echo from Audio Without Wrecking Speech URL: https://soundforgepro.com/remove-echo-from-audio/ Last updated: 2026-10-10T14:16:59.000Z Quick answer: when reflections overlap the words, reduce room echo with a dedicated de-reverb processor. For mild tails between phrases, EQ and gentle expansion may be all you need. First rule out a duplicate track, a delay effect or doubled monitoring, because fixing the source keeps far more of the voice than repairing the mix. A distinct repeat can also be an acoustic reflection, so its timing alone won't tell you the cause. Keep the original, work on a lossless copy, and compare every result at matched loudness. Stop when consonants turn watery, vowels become hollow, or word endings disappear. A slightly roomy voice is easier to understand than an aggressively processed voice that no longer sounds human. ![Four audio patterns for room reverb, delayed repeat, feedback loop, and misaligned duplicate tracks](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/08/echo-symptoms-desktop.webp) Read left to right, top to bottom: dense room decay, a discrete repeat, feedback, and a misaligned duplicate require different fixes. ## Choose the fix before you upload the file If you need this recording usable now, choose by the sound of the fault and by where the file is allowed to go. A cloud AI pass is a fast audition for non-sensitive speech. A local de-reverb plug-in gives more control. Neither is the first move when the real problem is a duplicated track, delay return, or monitoring loop. | What you hear | Start here | Where it runs | Honest limit | | -------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------- | ---------------------------------------------------------------------------------------- | | **Mild room tail between phrases** | High-pass only if needed, one small EQ cut, then conservative coreFX Expander settings | Locally in Sound Forge; no new service required | Tightens exposed tails but does not separate reflections under words | | **Room smear remains under speech** | Try a [dedicated de-reverb processor](https://izotoperx.net/izotope-rx-de-reverb/); use [Adobe Enhance Speech](https://podcast.adobe.com/en/enhancespeech) only as a quick cloud audition | Desktop plug-in or cloud, depending on the tool | Can alter consonants, breaths and speaker tone; heavy room sound may not recover cleanly | | **One distinct repeat or a doubled voice** | Check for a delay return or duplicate and mute the unwanted path; if neither exists, investigate an acoustic reflection | Original session or recording setup | Once both copies are mixed into one file, complete separation may be impossible | | **You hear yourself twice while recording or on a call** | Use one monitoring path, headphones, and the call platform's echo cancellation | Interface, recording app, or call settings | Prevents a new echo; it does not repair a loop already baked into the file | If the sound still doesn’t match any row, start with the [audio restoration diagnosis hub](https://soundforgepro.com/audio-restoration/). It separates hum, hiss, clicks, clipping, distortion and room damage before you stack processors. ## Diagnose the echo before processing Start with one sharp consonant, hand clap, or word followed by a pause. Listen for the timing pattern rather than just the amount of room sound. Then test whether the repeat disappears when you mute an extra track, effect return or monitoring path. | What you hear | Fast test | Correct first move | Common wrong move | | --------------------------- | ---------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------- | -------------------------------------------------------- | | **Room reverb** | Each word smears into a dense, fading cloud; the effect worsens as the microphone moves away | Improve capture when possible; use conservative de-reverb when reflections overlap speech | Treating the tail as stationary noise | | **Delayed echo** | You can count one or more distinct repeats after a transient or word | Check delay sends and duplicate returns; if those are absent, consider a strong acoustic reflection | Cutting broad frequency bands from the entire voice | | **Call or monitoring echo** | A call may return speaker sound to a microphone; local monitoring can instead play direct and delayed signals together | Use headphones, one monitoring path, and the call platform's echo cancellation | Trying to restore the export before fixing the live loop | | **Doubled track** | Muting one of two nearly identical tracks removes the effect | Mute the unwanted duplicate before mixdown; align only if both recordings are intentional | Running de-reverb on an editing error | A dense decay points to room reverb, while a separated second event is a discrete repeat that can come from either a reflection or an electronic delay. A growing squeal is feedback: turn the speakers down and break the live loop. If muting one track removes the fault, repair the source session. EQ or gating in Sound Forge can't reliably separate two overlapping copies that are already summed into one file. ## Hear the room and the manual limit These three examples use the same spoken-word excerpt. The dry source is from LibriVox. The room version was made by convolving it with a measured Room 7 impulse response from the [University of Rochester dataset, version 3](https://doi.org/10.60593/ur.d.26801089.v3). The manual version applies an 80 Hz high-pass filter, a small 280 Hz cut and a limited-range FFmpeg gate. This demonstrates a tail-control method, not a Sound Forge plug-in test or true de-reverberation. ### 1\. Dry source Direct voice before the measured room is added. Your browser does not support HTML audio. MP3 preview: -24.97 LUFS, -6.51 dBTP. WAV master: -24.70 LUFS, -6.24 dBTP. [Download the 48 kHz WAV master](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/media/2026/08/01-dry-source.wav) ### 2\. Measured room The same voice convolved with the Room 7 measured impulse response. Your browser does not support HTML audio. MP3 preview: -24.91 LUFS, -8.69 dBTP. WAV master: -24.65 LUFS, -8.42 dBTP. [Download the 48 kHz WAV master](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/media/2026/08/02-room-reverb.wav) ### 3\. Manual tail control High-pass, one low-mid cut, and a configured limited-range FFmpeg agate stage. Pauses tighten; reflections under speech remain. Your browser does not support HTML audio. MP3 preview: -25.03 LUFS, -8.36 dBTP. WAV master: -24.77 LUFS, -8.10 dBTP. [Download the 48 kHz WAV master](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/media/2026/08/03-manual-tail-control.wav) Reproducibility and source record Speech: LibriVox *Epitaph on a Sailor*, source SHA-256 `e0b8d6ac187a010d5dceca4ab5d65efde44d75c03b37592f7ee8d7f77e8e5d1a`. Room: University of Rochester dataset v3, trimmed Room7 Speak1 Mic1 impulse SHA-256 `17fd0873e5a786838e0e3349f89afc43c79221db86fe495aac25fafde0950149`. Method: NumPy 2.0.2 FFT convolution for room synthesis; FFmpeg 8.1.2 for trimming, filtering, loudness normalization, explicit 48 kHz mono output, and MP3 encoding. Build script SHA-256 `9abc334dbffe600d37ce431d7bb50930d41707eec6b75f058872bc2ba0ecadce`. The manual derivative uses 80 Hz high-pass, -3 dB at 280 Hz with Q 1.2, and a configured limited-range FFmpeg agate stage starting near -36.1 dBFS with 8 ms attack and 180 ms release. The MP3 previews measure about -25.0, -24.9, and -25.0 LUFS; the downloadable 48 kHz mono WAV masters measure -24.70, -24.65, and -24.77 LUFS. This reduces the overall level mismatch, but a similar integrated reading does not guarantee that every phrase sounds equally loud. The attached note identifies the sources, settings and build script. The measured room response gives a broadband T30-extrapolated RT60 of about 0.93 seconds in a local calculation: integrate its energy backwards, fit the decay from -5 to -35 dB, then extrapolate to -60 dB. In the samples, compare the pauses and the words separately; lowering a tail does not separate reflections during speech. The reading is Epitaph on a Sailor by Robert Duncan Milne, read by Claudia Caldi in [LibriVox Short Story Collection Vol. 106](https://librivox.org/short-story-collection-vol-106/). LibriVox identifies its recordings as [public domain in the United States](https://librivox.org/pages/public-domain/) and asks users elsewhere to check local copyright status. The room data is credited to Jenna Rutowski, Tre DiPassio, Benjamin R. Thompson, Michael C. Heilemann and Mark F. Bocko, under [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/). Their dataset contains 48 kHz, 32-bit mono responses from 14 rooms; this example trims one response and convolves it with speech. ## Why EQ and a gate cannot erase a room ![Direct speech and room reflections showing a gate reducing tails only between spoken phrases](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/08/manual-limit-desktop.webp) EQ and limited-range gating can tighten exposed tails; reflections that overlap speech remain fused with the voice. A microphone picks up direct speech plus early reflections and a later decay. In a pause, a gate can turn the remaining tail down. During a word, voice and reflections overlap, so static EQ hits both and an open gate lets both through. Conventional noise-profile reduction targets a recurring noise spectrum, and not every AI speech tool works that way. This explains a common failure: the pauses become impressively black while the voice stays hollow. Pushing the gate harder then clips breaths, consonants, and word endings. Pushing EQ harder makes the speaker thin without solving the timing smear. The manual chain is useful when the voice is already understandable and the distraction is mild low-mid bloom plus exposed tails. In Sound Forge, use coreFX Expander for gradual attenuation; the documented Gate is a harder effect that suppresses audio below its threshold. A dedicated de-reverb processor estimates the direct signal and the room over time. That's more appropriate when reflections continue under speech, but it's still estimation. Sibilance, breaths, music, and fast transients can be mistaken for room energy. The safe result is usually the last setting before those artifacts become obvious. ## Reduce mild room reverb in Sound Forge 1. **Preserve the untouched source.** Keep the only original outside the processing chain and make a separate lossless working copy at the source sample rate. For PCM audio, keep its bit depth or use a suitable floating-point working format. Decoding MP3 to WAV won't bring back information that's already gone. 2. **Mark three diagnostic passages.** Choose a quiet phrase, a loud phrase, and a word followed by a clear pause. A setting that survives one easy sentence can still damage the rest of the file. 3. **Build a minimal Plug-In Chain.** Choose View > Plug-In Chain, then Add Plug-Ins to Chain. In the chooser, add Modern Equalizer and coreFX Expander if your installation includes them; place EQ first and click OK. Turn off Bypass for each effect you want to hear. Start without unrelated presets or loudness effects. 4. **Remove unusable low end.** In Modern Equalizer, add a band with + and choose High Pass. Use it only if there's rumble below the useful voice. Raise Frequency carefully, then pull it back before the chest tone disappears. If filtering doesn't help, switch that band off. 5. **Check one boxy frequency area.** Add a Peaking band and try a small cut while you move Frequency, adjusting Q for width. Keep the cut only if the words get clearer without thinning out the speaker. The sample uses -3 dB at 280 Hz with Q 1.2, a setting picked for the demonstration. It isn't a measured room resonance or a universal preset. 6. **Use gentle expansion.** In coreFX Expander, choose Peak or RMS and start with a low Threshold and gentle Ratio. Raise Threshold only while quiet syllables remain intact; tune Attack, Release and Soft for smooth starts and endings. Check Mix and Out Gain. The FFmpeg example caps attenuation near 10.5 dB; that is not a coreFX Range control. 7. Match loudness and bypass. Compare the chain on and off at a similar perceived level across all three passages. Turn the louder path down to match the quieter one; lowering both by the same amount doesn't count as matching. 8. **Commit once and check a clean playback path.** Restore the intended effects after the bypass comparisons. Save As a new audio file to apply the real-time window chain to the file, keeping in mind that Save Chain Preset only stores settings. To process a selection instead, use FX Plug-Ins > Apply Plug-In Chain. Reopen the result without an active processing chain so the check doesn't add the effects a second time, then listen through the entire export, including quiet endings and the loudest phrase. These steps follow the current [Plug-In Chain save and selection behavior](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/proonly/plug-in%5Fchainer.htm), [Modern Equalizer controls](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/modern%20equalizer.htm) and [coreFX Dynamics reference](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/dynamic%20effects.htm). For step-by-step setup details, use the [Plug-In Chainer walkthrough](https://soundforgepro.com/how-to-use-plug-in-chainer-sound-forge-pro/). The [Noise Gate guide](https://soundforgepro.com/how-to-use-noise-gate-sound-forge-pro/) explains the harder alternative, which works quite differently from gentle expansion. **Do not capture a reverb tail as a “noise profile” and call the result de-reverberated.** A stationary hiss or fan can support profile-based reduction. A room tail changes with every word, pitch, and interval. If steady noise is also present, treat it separately with the [hiss and hum repair workflow](https://soundforgepro.com/remove-hiss-hum-sound-forge/). ## Use a dedicated de-reverb processor when speech stays smeared ![Manual EQ and gate path versus dedicated de-reverb with matched listening and an artifact stop point](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/08/manual-vs-dereverb-desktop.webp) Use the cyan manual path for mild buildup and tails; use the magenta specialist path when reflections remain under speech. Move to a specialist when reflections obscure the words or gating makes only the pauses unnaturally quiet. As a starting point, test de-reverb before heavy compression with makeup gain, which can make room tails more noticeable. Do only the rumble reduction that helps; compare another order if the processor behaves poorly. There is no mandatory chain for every recording. 1. Open a lossless copy in a standalone restoration editor, or load a plug-in whose compatibility you have checked in your host. 2. Loop a phrase with consonants, sustained vowels, sibilance and a pause. 3. If the processor offers Learn, give it the direct speech and its decay. An empty tail on its own isn't enough. 4. Start gently and increase reduction only while intelligibility improves. 5. Back off at watery modulation, hollow vowels, detached sibilance or shortened breaths. 6. Compare at matched loudness on another passage; keep the less processed version if the improvement is doubtful. 7. Render to a new file and check it with the processor switched off. If a second pass is worth it, work from that saved derivative and compare it with the original, taking care not to apply the first chain twice. For RX, [the current edition comparison](https://docs.izotope.com/rx12/en/rx-overview.html) lists De-reverb as a plug-in in Elements, Standard and Advanced; the standalone editor is in Standard and Advanced. In [RX 12 De-reverb](https://docs.izotope.com/rx12/en/de-reverb.html), Learn can suggest a reverb profile and tail length from several seconds containing room tone, speech and decay. Reduce the strength if the voice sounds unnatural, and switch off Output Reverb Only before exporting. For speech, [Dialogue Isolate](https://docs.izotope.com/rx12/en/dialogue-isolate.html) in Standard/Advanced offers separate Voice, Reverb and Noise levels; increasing Sensitivity can also damage clarity. Before committing to a Sound Forge plug-in workflow, verify it in your installed build; the standalone editor avoids that host dependency. [Boris FX CrumplePop](https://borisfx.com/products/crumplepop/) offers EchoRemover in its classic VST/AU/AAX plug-in collection and a separate SoundApp for Windows and macOS. The vendor describes SoundApp processing as local; SoundApp and an ARA extension are not the same as loading the classic plug-in. Sound Forge is not explicitly named in its host list. Try loading, previewing and rendering a short copy before relying on compatibility. The classic plug-in FAQ identifies trial-mode beeps; do not mistake those for restoration artifacts. SoundApp has a separately advertised trial, so check the restrictions of the exact product you install before expecting a clean delivery export. For a quick voice-only experiment, Adobe's current [Enhance Speech](https://podcast.adobe.com/en/enhancespeech) says it removes noise and echo from voice recordings and supports audio uploads; its listed Premium features include video uploads. That can be convenient, but it's a cloud service and may reshape the voice rather than provide transparent forensic repair. Check privacy requirements, compare the entire sentence, and keep the original. ## Fix a distinct delayed echo at the source For a distinct repeat, inspect delay sends, duplicated clips and routed returns if the source session survives. Mute each suspected extra path and replay the same words. If the repeat remains in a single dry microphone track, investigate a strong acoustic reflection instead; not every slap-like echo is an editing mistake. When an isolated repeat falls entirely inside a pause, lower that region with a short, smooth volume fade and check both edit boundaries. Don't cut through the next word to get rid of its echo. A repeat that overlaps wanted speech needs separation; a simple volume edit won't do it. Trial de-reverb may help with an acoustic reflection, but it won't reliably undo arbitrary delayed copies. Use a cleaner alternate take if you have one. ## Fix doubled voice, monitoring echo, and call echo ### Doubled or misaligned track Mute the unwanted layer first. If both microphone recordings are intentional, align them and rebalance their levels before deciding whether to keep both. Aligning two copies without reducing level can make the sum louder. Small offsets can cause comb filtering; longer ones may sound like a slap. Once the copies have been mixed, changing delay, gain or processing can prevent exact reversal. ### Local monitoring echo Hearing yourself twice while recording usually means direct hardware monitoring and software monitoring are active together, or the software buffer returns a delayed copy. Choose one path. Keep direct monitoring and mute the software return when low latency is unstable. The [Sound Forge recording guide](https://soundforgepro.com/how-to-record-audio-in-sound-forge-pro/) covers level, device, and monitoring checks before a full take. ### Speakerphone or video-call echo Use headphones and keep only one device connected to call audio in each room. As [Zoom’s echo troubleshooting](https://support.zoom.com/hc/en/article?id=zm%5Fkb&sysparm%5Farticle=KB0061720) explains, muting an extra device’s microphone isn't enough while its speaker is still playing, so disconnect that device from meeting audio. Check the platform’s echo-cancellation setting and turn the speakers down if headphones aren't available. Isolated local participant recordings make a much better repair source than a mixed call, and post-processing can't promise to remove every returned voice. ## Know when the recording cannot be recovered cleanly - **Distant speech in a very live room:** when reflected energy rivals the direct voice, stronger reduction removes speech detail too. - **Clipping plus reverb:** clipping can happen before or after the room is captured. If clipping is confirmed, try the [clipped-audio repair workflow](https://soundforgepro.com/fix-clipped-audio-sound-forge/) on a copy before de-reverb, then reassess both defects. Not every overloaded recording can be rebuilt. - **Several overlapping speakers:** one model may chase changing voices, distances, and reflections at once. - **Music or a finished stereo mix:** sustained notes, cymbals, and intentional reverb can resemble the defect. Use stems when they exist. - **Low-bitrate call audio:** strong processing can expose codec warble and missing high-frequency detail. - **A duplicate already summed to mono:** exact subtraction is unavailable when timing, gain, or processing varies. For an irreplaceable recording, keep the untouched source as the archive master, and save any conservative repair and any more aggressive listening copy separately. A cleaner-looking waveform is never a reason to throw the original away. ## Prevent echo on the next recording ![Distant microphone in a reflective room compared with close microphone placement and thick absorption](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/08/prevent-echo-desktop.webp) Closer placement, headphones, and thick first-reflection absorption improve the direct-to-room ratio before processing. [Shure’s microphone-placement guidance](https://service.shure.com/articles/en%5FUS/Knowledge/critical-distance-and-microphone-placement) explains why distant speech gets blurred by reflected speech. Move the microphone closer and make the room less reflective before relying on software. Add suitable absorption where strong early reflections occur; headphones prevent playback from re-entering the microphone. 1. Move the microphone closer until the direct voice dominates, while controlling plosives and excess proximity bass. 2. Use the microphone’s actual polar pattern: aim a directional mic’s rejection angle toward an unwanted source. An omnidirectional mic has no equivalent null to aim. 3. Treat strong first-reflection points with suitable absorption, and judge the change with a new recording. How much foam you can see tells you nothing. 4. Move away from bare parallel surfaces that create flutter and repeated reflections. 5. Use headphones for calls, overdubs, and software monitoring. 6. Record a ten-second test and listen on headphones before committing to the full take. Treat remaining defects as separate jobs. Short impulses belong in the [click and pop repair workflow](https://soundforgepro.com/how-to-remove-clicks-pops-sound-forge-pro/). Combining echo, hum, clipping, clicks, and loudness into one “clean audio” preset makes it harder to hear which processor caused the damage. ## Remove echo from audio FAQ ### Can echo be removed completely from audio? Sometimes. A duplicated track, active delay send, or monitoring loop can be removed completely while the source session survives. Room reflections already mixed into speech usually can only be reduced. Heavy de-reverb can replace room sound with watery or metallic artifacts. ### Can Sound Forge remove room echo by itself? Sound Forge can reduce mild low-mid buildup and exposed tails with EQ and conservative coreFX Expander settings. A hard Gate is less forgiving because it suppresses the signal below its threshold. Neither tool separates reflections that overlap speech; use compatible de-reverb, specialist restoration, or a new recording when the room remains under the words. ### Does a noise gate remove reverb? A gate can lower the reverb tail when speech has stopped, but it stays open while the person is talking. Sound Forge's documented Gate suppresses audio below its threshold; for gentler attenuation, use coreFX Expander and tune its ratio plus Attack and Release so word endings survive. ### Why does echo removal make speech sound robotic? The processor estimates which energy belongs to speech and which belongs to the room. Too much reduction can reshape consonants, breaths and vowels. Lower the strength and compare a difficult phrase, then check the full recording. A shorter selection is useful for testing, but does not itself make the processing gentler. ### What is the best echo remover setting? There is no universal percentage. Start with the lightest reduction, loop representative speech, and increase it until the room stops masking words. Back off when sibilance detaches, vowels become hollow, or watery modulation appears. ### Should I use an online echo remover? It can be useful for a short, non-sensitive voice clip. Check upload and retention terms, file limits, export quality, and whether the service lets you compare the original at matched loudness. Keep the source and test one difficult sentence before processing a full interview. ### What is the best free way to remove echo from audio? First check for a free source fix: mute a duplicate track, remove a delay send, disable one monitoring path, or use headphones. For mild room tails, try EQ and conservative coreFX Expander settings if you already own a version that includes them; Sound Forge itself is not free. A free cloud speech enhancer can be worth a short test on non-sensitive voice, but keep the original and stop if the speaker turns watery, hollow, or synthetic. ### Can I remove echo from an audio recording on iPhone? For a Mono or Stereo recording in Voice Memos on iOS 26, try Options > Enhance Recording. Apple describes this as [reducing background noise and echo during playback](https://support.apple.com/guide/iphone/play-it-back-iphebbd067ce/26/ios/26). Preview the same phrase with it on and off; do not assume that playback enhancement is included in an exported file. If room smear remains, test a copy in a dedicated editor or speech enhancer. For private audio, check upload and retention terms before using a cloud tool. Call echo or doubled monitoring should be fixed at capture, not treated as a file-cleanup problem. ### Why can I hear myself twice while recording? Direct hardware monitoring and delayed software monitoring may both be active. Choose one path. A second possibility is a duplicated armed track or a call return feeding the microphone. Fix the routing before editing the recorded file. ### How do I prevent room echo in a voice recording? Move the microphone closer, use a directional mic’s rejection angle where helpful, reduce strong reflections with appropriate absorption, use headphones, and record a short test before the full take. Fact-checked September 15, 2026 against current vendor documentation and the cited source records. The six linked audio files were remeasured and matched a fresh replay of the documented sample-building process. The examples are a controlled FFmpeg/NumPy demonstration. ### Remove Vocals in Sound Forge: What Actually Works URL: https://soundforgepro.com/remove-vocals-sound-forge/ Last updated: 2026-10-09T21:06:22.000Z **Quick answer:** Sound Forge Pro can reduce a lead vocal when that vocal sits in the shared center of a true stereo mix. The native method uses Channel Converter to subtract one channel from the other. It can be useful for a rough practice track, but it also removes any kick, bass, snare, lead instrument, or other sound that matches in both channels. For a more selective split, use a compatible, separately installed SpectraLayers edition through Sound Forge’s ARA command. Elements 13 and Go offer a vocal/instrumental split; Pro 13 adds the full set of instrument stems. ## Choose the Vocal-Removal Method by the Required Result | Required result | Best starting point | Main compromise | | ------------------------------------- | ------------------------------------- | --------------------------------------------- | | Professional remix or release | Licensed original stems | Requires source access and permission | | Clean ready-made backing track | Official instrumental | May not exist for the song | | Editable vocal and instrumental split | SpectraLayers Unmix Song | Bleed and resynthesis artifacts | | Fast rehearsal or rough karaoke file | Channel Converter center cancellation | All matching center content is affected | | Mono or heavily widened source | Stem separation or a better source | Center cancellation cannot identify the vocal | For karaoke, you want less audible singing. For an acapella, you want the opposite: the voice with no backing. Channel subtraction can't tell either source apart. When you need vocal and instrumental layers you can edit independently, use source separation. ## How Center Cancellation Works Many stereo masters place the lead vocal at similar level and polarity in the left and right channels. Write the channels as **L = C + SL** and **R = C + SR**, where C is content shared by both channels and S is the channel-specific content. Subtraction gives **L - R = SL - SR**. The identical center term disappears. The equation explains why center content disappears. It removes whatever matches in both channels, and that isn't the same thing as “the vocal.” A centered kick can vanish while a stereo vocal reverb survives. If L and R are identical, as with a mono recording copied to two channels, their mathematical difference is zero. Near-identical channels leave a quiet residual. Sound Forge Pro's [current Channel Converter help](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/proonly/channel%5Fconverter.htm) documents source gain, output routing and **Invert Mix** controls. It doesn't mention the old *Stereo to Stereo - Vocal Cut* factory preset that many legacy tutorials repeat, so treat that name as historical and don't count on finding it as a 2026 preset. The 2004 [Sound On Sound explanation of the karaoke effect](https://www.soundonsound.com/sound-advice/q-can-remove-vocals-track-using-phase) supports the subtraction principle; it says nothing about a current Sound Forge menu label. Old Audio Studio tutorials may mention Vocal Eraser instead. The [current Sound Forge Pro help](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/topics/workingwith.htm) has no Vocal Eraser topic, so don't count on it as a bundled 2026 tool. If Channel Converter is missing, check your installed edition against its own manual instead of following a Pro menu path. ## Remove a Centered Vocal with Channel Converter 1. **Preserve the original.** Make an untouched copy outside Sound Forge before processing. Use a separate working file so an accidental Save cannot overwrite the only source. 2. **Start with a stereo lossless source.** Use the best WAV or FLAC available. Saving decoded MP3 audio as PCM WAV avoids another lossy encode at that save; it cannot restore discarded detail. 3. **Confirm true stereo.** Check that there are two channels. Similar-looking waveforms are only a warning, not proof that the samples match. Test the difference on a separate short file before deciding whether the mix is suitable. 4. **Invert the right channel first.** Open a separate short stereo test file. With the Edit tool, unlock Lock Channel Selection if needed, then drag within the right channel only over the entire test. Confirm that only the right channel and the complete time range are highlighted, then choose Process > Invert/Flip. With no data selected, the entire file is inverted, which will not create the required difference. 5. **Create one mono difference output.** Select the complete test and both channels; unlock channel selection if necessary and drag along the channel divider. Choose Process > Channel Converter, set Output channels to 1, Source 1 to 50.0% and Source 2 to 50.0%, and leave Invert Mix off. These are percentage gains as shown in the current help illustration. Click OK. Because the right source was already inverted, the intended output is 0.5 × (L − R), not the usual 0.5 × (L + R). 6. **Test several difficult sections.** Repeat the test on separate copies of a dry vocal line, dense chorus, bass-heavy passage, cymbal hit and reverb tail. One easy verse is not enough evidence. 7. **Render and run mono QA.** Save the mono test as a new PCM WAV and reopen it. Compare at matched listening level, keeping playback volume comfortable. If acceptable, repeat both operations on an untouched full-length working copy: invert only the right channel over the entire song, then convert both channels. Do not invert an already processed test again. ![Stereo data window with only the right channel selected across the whole range and Process, Invert/Flip highlighted](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/09/sf-vocals-select-right-channel-invert.webp) Only the right channel is highlighted, over the complete range, before Invert/Flip. The [channel-selection instructions](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/selecting%5Fdata%5Fusing%5Fthe%5Fmouse.htm) show how to select the right channel without the left. [Invert/Flip](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/invert%5Fflip.htm) changes that selected data before the mix. A negative gain value in dB is attenuation. It doesn't flip polarity, so typing a minus sign into a gain field won't give you subtraction. The [Sound Forge Channel Converter guide](https://soundforgepro.com/sound-forge-channel-converter/) covers matrix gain, polarity, headroom, and channel conversion in more detail. Hold off on raising the level until you've accepted the cancellation character. A quieter result can hide problems until it is level matched. For hiss, clicks or other damage rather than music separation, use the [Sound Forge restoration guides](https://soundforgepro.com/tag/sound-forge-restoration-guides/) to choose the relevant repair. ![Channel Converter dialog with one output channel, 50.0 percent from Source 1 and Source 2, and Invert Mix unchecked](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/09/sf-vocals-channel-converter-difference.webp) At 50.0% per source this is a sum unless you first invert only the right source as described above; Invert Mix is not a per-source subtraction switch. ## Check the Difference Signal in Mono L - R and R - L contain the same information with opposite polarity. A preset can write one to the left channel and the other to the right. Headphones then produce an exaggerated sense of width, but summing the file to mono can cancel almost everything. For predictable practice playback, keep one difference signal as mono or duplicate it into both channels with the same polarity. Then test the phone, speaker, venue system, or broadcast path that will actually play the file; a wide headphone preview doesn't prove mono compatibility. ## Why the Bass, Drums, and Reverb Change A subtraction matrix knows channel similarity. Centered bass, kick, snare, lead guitar, and synth parts can leave with the lead vocal. Stereo chorus, delay, reverb, backing vocals, and doubled takes differ between channels and can survive as quiet words or ghostly ambience. A vocal panned away from center may remain almost intact. A mono source is the limiting case because left and right are identical. A heavily widened master can fail for the opposite reason: vocal doubles, harmonizers, and stereo effects deliberately make the vocal different across the two channels. Neither outcome means the matrix is broken. The mix is incompatible with that method. ## Can Filtering Restore the Lost Low End? Some vocal-cut workflows blend low frequencies from the original back into the difference signal. The idea can restore weight because the fundamental energy of bass and kick often sits below much of the lead vocal. It remains a compromise. Vocals contain low mids, and bass instruments extend well above a single crossover point. A limited low-frequency blend may be acceptable for rehearsal, but it isn't a reconstruction of the removed center. If preserving the rhythm section matters, go back to the untouched source and use stem separation. Aggressive EQ or stereo widening can't recreate instruments that the subtraction removed. ## Use SpectraLayers 13 Through Sound Forge ARA SpectraLayers estimates separate sources from a finished mix. The [SpectraLayers Pro 13 operation manual](https://download.steinberg.net/downloads%5Fsoftware/SpectraLayers%5F13/help/Pro/%5Funmix%5Fsong.html) lists Vocals, Drums, Bass, Guitar, Piano, Sax & Brass, and Other for Unmix Song. Its quality choices are Fast, Balanced, and High. The manual says Balanced applies more advanced vocal, drum, and bass processing, while High adds finer vocal processing and improves overall separation. Those settings describe processing depth; they aren't a promise that High will sound best on every song. The [SpectraLayers edition comparison](https://download.steinberg.net/downloads%5Fsoftware/SpectraLayers%5F13/help/Pro/%5Fspectralayers%5Feditions%5Fcomparison.html), reviewed September 14, 2026, lists full song unmixing for Pro 13 and vocals-only song unmixing for Elements 13 and Go. SpectraLayers installs separately from Sound Forge, and you need Pro 13 for the full instrument-stem set; separating vocals from the backing works in the smaller editions too. The matrix lists ARA in all three editions, but check how Go comes with your licensed product before assuming it's a free standalone download. Sound Forge supplies the host connection: its [current product comparison](https://www.vegascreativesoftware.com/sound-forge/pricing/) lists VST2, VST3 and ARA support as third-party plug-in support and doesn't bundle SpectraLayers. Sound Forge's [2026 ARA integration help](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/proonly/ara.htm) gives the setup sequence. Install the SpectraLayers VST3 component, set its folder as an **Alternate VST search folder** under **Options > Preferences > VST Effects**, and launch it with **Tools > Edit in SpectraLayers (ARA)**. Use the dedicated ARA command rather than treating the installed component as an ordinary chain effect. The help explicitly warns about this distinction for Melodyne and documents the dedicated SpectraLayers command. 1. **Open an untouched source.** Select the complete song or a representative test range from a lossless copy. 2. **Launch the ARA editor.** Choose **Tools > Edit in SpectraLayers (ARA)**. 3. **Run Unmix Song.** Select the source layer. In Pro 13, choose Modules > Unmix > Unmix Song. For a vocal/backing split, check Vocals and uncheck the other instrument classes so they remain in Other. In Elements 13 and Go 13, the documented module is Unmix Song Vocals under Modules > Unmix; it creates Vocals and Other layers. 4. **Mute before deleting.** In the Layers panel, use Mute on the resulting vocal layer and keep the instrumental layer or stems audible. Use Solo on the vocal to inspect leakage, then clear Solo before judging the backing. 5. **Judge the recombined instrumental.** Listen for damaged cymbals, guitars, piano and reverb in Other. If you generated individual instrument stems in Pro, solo those layers as well, then clear Solo and listen to all retained stems together. 6. **Compare processing depths.** In Pro, try the available Fast, Balanced and High settings on the same untouched excerpt. Keep the least objectionable recombined result, and don't rerun the module on an earlier output just to compare quality settings. 7. **Return and verify the render.** Close the SpectraLayers window without removing or bypassing the ARA effect, and listen to the Sound Forge playback. Use File > Save As and choose Sound Forge Pro Project File (\*.frg) for the working project. Keep its companion folder, then use File > Render As for a new lossless delivery. Reopen that delivery separately and check the vocal mute, start time, duration and channels; a flattened WAV no longer holds editable stems. In [ARA mode, SpectraLayers has no File menu](https://download.steinberg.net/downloads%5Fsoftware/SpectraLayers%5F13/help/Pro/%5Fara%5Fplugin.html): the host manages its state, so there's no standalone Save Project command to look for in that window. Keep the Sound Forge project, the referenced media and the untouched source apart from the rendered delivery, then reopen the project to check that the editing state survived. ![SpectraLayers Layers panel with the Vocals layer muted, no layer soloed and the Drums, Bass and Other stems still playing](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/09/sf-vocals-spectralayers-layers-mute.webp) SpectraLayers Pro with individual stems: mute the Vocals layer and clear Solo before checking the instrumental mix. The [SpectraLayers 13 Layers panel manual](https://download.steinberg.net/downloads%5Fsoftware/SpectraLayers%5F13/help/Pro/%5Flayers%5Fpanel.html) explains the per-layer controls. The [Elements 13 Unmix Song Vocals help](https://download.steinberg.net/downloads%5Fsoftware/SpectraLayers%5F13/help/Elements/%5Funmix%5Fsong%5Fvocals.html) and [Go 13 equivalent](https://download.steinberg.net/downloads%5Fsoftware/SpectraLayers%5F13/help/Go/%5Funmix%5Fsong%5Fvocals.html) confirm the two-layer output. Boris FX’s [project-saving instructions](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/working%5Fwith%5Fprojects.htm) explain why the FRG file and its companion folder must stay together. ## What Stem Separation Gets Wrong A separation model estimates sources that overlap in time and frequency. When a sung consonant shares the same region as a cymbal or distorted guitar, there may be no clean boundary to recover from the stereo master. Common failures include faint words in the instrumental, watery cymbals, softened drum attacks, unstable ambience, missing bass harmonics, and metallic reverb. In a [July 2026 Steinberg forum reply about versions 12 and 13](https://forums.steinberg.net/t/unmix-song-in-slp-13-vs-12/1036507), Robin Lobel called the direct Unmix Song improvements marginal and pointed to other modules that can help with later repair. Don't buy an upgrade expecting the version number alone to give you a cleaner vocal split. ## When a Dedicated Stem Separator Is the Better Tool If SpectraLayers isn't licensed and center cancellation wrecks the rhythm section, Sound Forge has stopped being the efficient place to do the separation. Let a desktop or browser separator estimate the sources, then use Sound Forge for trimming, cleanup, fades and delivery. The [Sound Forge alternatives guide](https://soundforgepro.com/best-sound-forge-alternatives/) separates full audio editors from specialist repair and separation tools. Before uploading client, copyrighted, or unreleased music, read the service's current retention, model-training, privacy, and commercial-use terms. Test one difficult excerpt before paying or processing an album. Download lossless stems when offered, preserve the untouched source, and avoid making claims such as “studio quality” until the actual file passes your checks. Before delivery, check the complete song for vocal bleed, missing bass, damaged attacks and stereo changes. Compare at matched listening level and check mono playback. Approve separation before [normalization](https://soundforgepro.com/how-to-normalize-audio-in-sound-forge-pro/) or the [mastering workflow](https://soundforgepro.com/how-to-master-a-track-in-sound-forge-pro/), which can make quiet remnants more obvious. Keep a lossless master before following the [MP3 export steps](https://soundforgepro.com/how-to-export-mp3-from-sound-forge-pro/). ## Rights Still Apply to a Vocal-Reduced File Being able to reduce a vocal technically doesn't give you permission to distribute, monetize, remix or publicly use the recording. The [U.S. Copyright Office explains](https://copyright.gov/circs/circ56a.pdf) that a musical composition and its sound recording are separate works. Which permissions or exceptions a given use needs depends on the rights involved and the jurisdiction, so settle that before you publish or deliver the processed audio. Describe the output honestly. A file made from a commercial master is a vocal-reduced or stem-separated version, so don't present it as an “official instrumental.” Keep the source, method, software version and processing notes with the project. ## Vocal Removal FAQ ### Can Sound Forge remove vocals from any song? No. The native center-cancellation method requires useful parts of the vocal to match between left and right. Mono, widened, reverberant, and densely overlapping mixes are poor candidates. SpectraLayers can estimate stems, but the output still needs listening checks. ### Why did the bass, kick, or snare disappear with the vocal? Those instruments were mixed into the same center information as the lead. Channel subtraction cannot tell a singer from a centered drum or bass part, so it removes all matching left-right content. ### Can I remove vocals from a mono file? Not with center cancellation. If left and right are identical, subtracting them removes almost everything. Use stem separation, an official instrumental, or original multitrack stems. ### Can Sound Forge isolate vocals for an acapella? Center cancellation produces the opposite type of signal: it rejects matching center content. Use SpectraLayers or another stem separator for a vocal layer, then inspect that layer for instrumental bleed and resynthesis artifacts. ### Why can I not find the Vocal Cut preset? The preset name appears in legacy Sound Forge tutorials, but the current Sound Forge Pro 2026 Channel Converter help does not list it. The checked documentation does not establish which installations retain that preset. Use the two-stage method above: invert the right channel only, then mix both sources at equal gain into one mono output. Invert Mix by itself reverses the combined output and does not remove the center. ### Is SpectraLayers included with Sound Forge? Do not assume it is included. SpectraLayers is a separate installation. Pro 13 is required for full instrument stems, while Elements 13 and Go can split vocals from the remainder. All three list ARA support; verify the license and how your edition is supplied. Sound Forge Pro provides ARA integration when the compatible SpectraLayers VST3 component is installed and found. ### Should I start from MP3 or WAV? Use the best lossless source available. Saving decoded MP3 audio as PCM WAV avoids another lossy encode at that save but cannot restore information already discarded by the codec. ### What gives the cleanest instrumental? An official instrumental or licensed original stems. Every process applied to a finished stereo master must cancel or estimate information that has already been mixed together. ### Should I process the whole album after one good test? No. Test each mix or mix family. Vocal placement, widening, mastering, and arrangement can change between tracks, so a method that works on one song can fail on the next. Documentation reviewed September 14, 2026\. The native sequence combines the documented single-channel selection, Invert/Flip and Channel Converter operations. It has not been verified in a locally installed Sound Forge 2026 session; test the disposable excerpt and reopened output before applying it to a complete song. ### Crossfade Audio in Sound Forge Without Level Dips URL: https://soundforgepro.com/crossfade-audio-sound-forge/ Last updated: 2026-10-09T21:08:26.000Z **Quick answer:** use **Edit → Paste Special → Mix** when you want to commit one waveform into another, and **Options → Event → Automatic Crossfades** when you want an editable overlap between events on the same channel. Either way, align the audio and match its level before choosing a curve. A longer crossfade won't fix bad timing, opposite polarity or mismatched room tone. A clean crossfade has three parts to judge: the handoff into the overlap, the combined midpoint and the exit. If the middle dips, the curves may be wrong for unrelated material or the sources may be canceling. A bump suggests correlated audio adding too strongly. And if it sounds hollow, timing or phase usually needs attention before duration does. The menu paths below follow Sound Forge Pro 2026 for Windows; older Sony/MAGIX and Audio Studio tutorials may use different commands. ## Crossfade vs Fade: Use the Right Edit A fade changes the level of one source over time, often to or from silence. A crossfade overlaps two sources while one falls and the other rises. Use a normal fade when a song ends, a clip starts from silence or there is no second source to preserve. Use a crossfade when continuity must pass from one recording, take, song or ambience bed to another. If the job is to merge two audio files into one seamless transition, the overlap does the work; merely placing the files end to end does not. ## Choose the Sound Forge Crossfade Workflow | Job | Best starting workflow | Trade-off | | --------------------------------- | -------------------------------------- | ----------------------------------------------------- | | Committed mix into a waveform | Paste Special → Mix | Direct and precise, but destructive after application | | Repositionable event transition | Automatic event crossfade | Fast and editable while events remain available | | Short punch-in over a longer take | Manual event fades at both edges | Needs attack and room-tone control | | One source ending in silence | Normal fade, not crossfade | No second source is required | | Different ambience beds | Long-enough overlap plus tone matching | Curve alone cannot fix mismatched noise | ## Paste Special → Mix for a Committed Crossfade 1. **Preserve both sources.** Save a working copy with handles around the outgoing and incoming audio. 2. **Copy the incoming audio.** Choose the Edit Tool, then select and copy the source that should enter during the transition. 3. **Set the destination.** Place the cursor or select the destination range where the overlap should begin. 4. **Open Mix.** Choose **Edit → Paste Special → Mix**. 5. **Match the gains.** Set source and destination sustain levels before judging curves. 6. **Set the transition.** Choose fade-in and fade-out lengths and curve types. 7. **Preview three points.** Hear the start, midpoint, and exit with surrounding context. 8. **Apply and verify.** Apply once, then check new peaks and the resulting boundaries. ![Decision map for a committed Paste Special Mix or editable event crossfade in Sound Forge](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/10/crossfade-workflow-desktop-1-v20261005.webp) Use Paste Special Mix for a committed waveform result or Automatic Crossfades while the event overlap remains editable. The [current Sound Forge Pro 2026 Mix documentation](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/mix.htm) confirms source and destination faders, independent data inversion, fade-in/out lengths, proportional fade lengths and curve choices. It also documents drag-and-drop Mix mode and the **Auto-crossfade Mix with selection** preference. That preference makes the fade curves respect the destination selection and file length; it won't align beats, words or phase for you. The shared [processing-dialog controls](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/using%5Fprocessing%5Fdialogs.htm) provide Preview and Bypass plus pre-roll and post-roll. Use that surrounding audio to judge the handoff; an isolated midpoint can hide a damaged word, late drum hit, or abrupt exit. ## Crossfade Overlapping Events The [current event crossfade help](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/event%5Ffades.htm) places the control at **Options → Event → Automatic Crossfades**. With it enabled, dragging one event over another on the same channel creates a transition. Turn it off and overlapping events punch in and out without fades. 1. Enable Automatic Crossfades. 2. Drag one event over the other to create the required overlap. 3. Show crossfade length with **Options → Event → Show Crossfade Lengths** or **Ctrl+Shift+T**. 4. Right-click the crossfade region, open Fade Type, and choose a curve combination. 5. Move the overlap and audition repeatedly. A shorter event placed entirely inside a longer one does not receive an automatic crossfade. Sound Forge documents a manual punch-in method: drag the shorter event into place, then drag fade handles from its upper corners at both ends. This lets the replacement enter and leave without applying one long crossfade across the entire event. ## Choose Overlap Length by Content There's no universal crossfade duration. The overlap needs enough compatible audio for the handoff, and it has to stay short enough not to blur timing or combine unrelated events. - **Dialogue punch-in:** place the overlap in stable room tone or within a sustained vowel, not across a plosive. - **Drum edit:** protect the intended transient and keep competing hits out of the midpoint. - **Music phrase:** align beat, bar, pitch, and sustain before extending the overlap. - **Ambience:** use enough time for noise and texture to transfer without a noticeable gate. - **Reverb tail:** preserve the complete decay while avoiding a double attack from the incoming source. ![Overlap placement for dialogue, drums, ambience, and reverb tails](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/10/crossfade-placement-desktop-v20261005.webp) Place the overlap in compatible audio: protect speech, align one drum hit, match ambience, and preserve the outgoing decay. If the timing is wrong, a longer crossfade often sounds like flam, chorus, or smear. Align the sources first. The [markers and regions workflow](https://soundforgepro.com/sound-forge-markers-regions/) helps store candidate sync points and consistent audition ranges. ## Fix a Dip or Bump in the Middle Match apparent level and spectral balance before blaming the curves. If one clip is already quieter, even a mathematically complementary pair will hand off to a quieter source. Correct the source or destination sustain level, or choose a better-matched section of room tone first. The midpoint math explains the classic dip. With two equal-level, uncorrelated sources and linear equal-gain fades, each source is at 0.5 amplitude, or **−6.02 dB**, halfway through. Their powers add as 0.5² + 0.5² = 0.5, about **−3.01 dB** relative to one source. An equal-power pair puts each near √0.5, or 0.707 amplitude and −3.01 dB, so the combined power stays near 1 for uncorrelated material. Audacity’s [fade and crossfade explanation](https://manual.audacityteam.org/man/fade%5Fand%5Fcrossfade.html) documents this same use case and warns that equal-power curves can increase the peak. | Source relationship | Likely starting shape | Midpoint risk | | ------------------------------------------------- | ------------------------- | ------------------------------------------------------ | | Different songs, ambience beds or unrelated takes | Equal-power-style overlap | Listen for a bump if shared content becomes correlated | | Same or nearly identical performance | Equal-gain-style overlap | Timing error can still create comb filtering | | Opposite polarity or poor alignment | No curve fixes the cause | Deep cancellation or a hollow image | Sound Forge names event fade curves **fast, slow, linear, smooth** and **sharp**; its current help does not label a specific combination “equal power” or “equal gain.” Treat the math as a starting principle, then audition the available curve pairs at matched level instead of assigning an undocumented formula to a menu name. ![Amplitude and power math for linear equal-gain and equal-power crossfade midpoints](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/10/crossfade-midpoint-desktop-1-v20261005.webp) For equal-level uncorrelated sources, linear equal gain produces a 3.01 dB power dip while equal power holds the summed power constant. A dip means the combined contribution becomes too low or cancellation occurs; a bump means both sources contribute too much or carry correlated content that reinforces. Change one variable at a time: source level, destination level, overlap, or curve. Otherwise a better render tells you nothing about why it improved. ## Curve Choices Are Source-Dependent Event crossfades support combinations of fast, slow, linear, smooth and sharp curves. For unrelated sources, equal-power-style complementary curves can keep perceived level steadier. For highly correlated or near-identical takes, the same curves can create a bump or phase interaction because both clips contain similar energy. That source-dependent split is also documented in [Universal Audio’s current crossfade guidance](https://help.uaudio.com/hc/en-us/articles/360041866811-Editing-Audio), which recommends equal gain for phase-coherent material and equal power for dissimilar material. Listen at the midpoint in stereo and mono. A curve that looks symmetric isn't proof of a transparent handoff. Use the [fade curve guide](https://soundforgepro.com/fade-in-fade-out-sound-forge/) for the behavior of individual envelopes, then judge the sum here. ## Phase and Alignment Problems Two recordings of the same source can be slightly delayed or have different polarity and phase. During overlap, frequencies reinforce and cancel, creating a hollow or comb-filtered sound. Making the crossfade longer extends the damage. ![Same-polarity reinforcement, opposite-polarity cancellation, and time-offset comb filtering](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/10/crossfade-diagnosis-desktop-v20261005.webp) Polarity reversal can cancel an aligned signal; a time offset creates frequency-dependent comb filtering instead. Zoom in and align a clear waveform feature or musical transient. Test polarity inversion only when measurement and listening support it; Sound Forge’s Mix dialog provides **Invert Data** separately for the source and destination. Inversion corrects a constant polarity reversal, not arbitrary time-varying phase differences. The [Sound Forge channel-routing guide](https://soundforgepro.com/sound-forge-channel-converter/) separates polarity inversion from channel delay and frequency-dependent comb filtering. ## Room Tone and Ambience Mismatch A room-tone jump can remain audible even with a smooth level trace because the noise spectra differ. One take may contain air conditioning, microphone self-noise, a moving audience, or a different microphone position. Match a compatible ambience bed, repair the background, or move the edit. For dialogue, build handles containing stable room tone around both takes, and don’t crossfade a breath from one take into an unrelated breath from another; the overlap can sound like a double inhale. Field recordings follow the same logic: keep obvious moving events out of the midpoint. ## Use a Tiny Crossfade for an Edit Click, Not Every Click A cut can click when the waveform jumps abruptly at the boundary. Aligning compatible zero crossings or adding a very short crossfade across the edit often removes that discontinuity. Keep it long enough to hide the jump but short enough not to soften the next attack. The [cut-and-trim workflow](https://soundforgepro.com/how-to-cut-and-trim-audio-in-sound-forge-pro/) covers sample-level boundaries and zero crossings. A crossfade is the wrong tool for general click removal. Mouth clicks, vinyl ticks and random digital impulses are defects inside one source, with no handoff between two clips involved; use the appropriate [click-and-pop repair workflow](https://soundforgepro.com/how-to-remove-clicks-pops-sound-forge-pro/) instead. ## Punch-Ins and Transient Protection Place the incoming attack inside the fully audible section of the replacement rather than in the steepest part of its fade. At the exit, let the original sustain or ambience take over before the replacement ends. Two short manual crossfades usually preserve a punch-in better than one long envelope across the replacement. For drums or rhythmic music, compare the edit with a metronomic reference and in the full mix. A crossfade can remove a click while still shifting the groove by a few milliseconds. ## Committed vs Editable Decisions Paste Special → Mix is appropriate when the position and transition are approved and a single waveform result is useful. Event crossfades are better while timing, overlap, and curves are still being auditioned. Render or commit only after source alignment and room tone are stable. Keep the original files and note the final overlap length and curve combination. If a later processor exposes the transition, return to the editable or pre-mix source instead of layering another crossfade over the committed result. ## Source-Specific Crossfade Strategy ### Dialogue Replacement Choose handles with matching microphone perspective and room tone, and place each edge outside plosives, breaths, and consonant clusters. Use two short manual fades around a replacement rather than letting one long overlap mix different performances for the entire line. ### Music Edit Between Takes [Estimate the tempo](https://soundforgepro.com/tap-tempo/), then align the beat subdivision, pitch and sustain in the editor. Tap Tempo estimates BPM; it does not move or stretch the clips. Compare drum transients and bass phase in mono. If takes were recorded with multiple microphones, alignment can differ by channel; a transition that's clean on the close mic may comb-filter on overheads or room mics. ### Crossfade Between Two Songs Pick the musical handoff before you worry about its duration. Align the downbeat or phrase boundary, match perceived loudness, and decide whether vocals, bass lines or drum transients are allowed to overlap. Event crossfades are easier to revise while timing is unsettled; Paste Special → Mix is better after the transition is approved. For unrelated songs, start with an equal-power-style pair, then shorten the overlap if the midpoint becomes crowded or harmonically tense. ### Loop Seam Audition repeated playback instead of relying on one pass through the seam. The rhythmic period needs to survive, and a transient shouldn't end up duplicated in both sides of the overlap. Ambience and modulation must also cycle naturally; a smooth single seam can still reveal a repeating level pulse. ### Sound-Effect Layer When two effects are intentionally combined, the operation may be a mix rather than a handoff. Keep source and destination levels under control, check summed peaks, and decide whether both should remain audible after the nominal midpoint. Don’t force complementary fade curves if the creative goal is sustained layering. ## Compare One Change at a Time Save candidates from the same source handles and sync point. Keep the overlap fixed while you compare curve combinations, then hold the preferred curves and change overlap length, and adjust source/destination gain last. That sequence shows you which decision fixed a dip, bump, or phase problem. Use markers several seconds before and after the transition so every audition begins with identical context. Level-match candidates, listen in mono, and don't skip a pass at low monitoring level. A midpoint bump that seems exciting at first can sound like an obvious edit after repetition. Before the final comparison, write down the failures that disqualify a candidate: doubled words, transient flam, a room-tone jump, comb filtering or new clipping. Keep the shortest, simplest transition that avoids them. An elaborate curve isn't a benefit if a plain one sounds cleaner. ## Crossfade QA Checklist - Source and destination levels are matched intentionally. - The overlap begins and ends in compatible material. - Attacks, consonants, beats, and reverb tails remain complete. - The midpoint has no dip, bump, click, or doubled event. - Stereo width and mono compatibility remain stable. - Room tone and noise spectrum transfer naturally. - New peaks have been checked after summing. - The final file is saved as a new lossless master. ## Common Crossfade Failures - **Midpoint gets quieter:** match levels, check curve complement, and test for cancellation. - **Midpoint gets louder:** reduce overlap contribution or use curves suited to correlated material. - **Transition sounds hollow:** align timing and check polarity before changing length. - **Speech has a double breath:** move the overlap into stable room tone or a compatible sustained sound. - **Drum hit flams:** align the transient and shorten the overlap. - **Reverb is cut:** extend source handles and preserve the full decay. - **Automatic crossfade did not appear:** check that Automatic Crossfades is enabled and the events share a channel. A short event contained inside a longer one needs manual fades at both edges. ## Crossfade FAQ ### How do I crossfade in Sound Forge? Use **Edit → Paste Special → Mix** for a committed waveform mix, or overlap events with **Options → Event → Automatic Crossfades** enabled. Align and level-match the sources before choosing curves. ### Can Sound Forge crossfade overlapping events? Yes. Overlap two events on the same channel with Automatic Crossfades enabled, then right-click the crossfade region and choose a fade-type combination. ### What is the difference between a fade and a crossfade? A fade changes the level of one source over time, often to or from silence. A crossfade overlaps two sources while one fades out and the other fades in, transferring continuity across the edit. ### Why does my crossfade get quieter in the middle? With equal-level, uncorrelated material, linear equal-gain curves produce about a 3 dB midpoint dip. Unequal source levels or phase cancellation can deepen the drop. Match levels, then test curve, alignment and polarity separately. ### Why can an equal-power crossfade get louder? Equal-power math assumes uncorrelated sources. Similar in-phase audio can reinforce during the overlap, while misaligned similar audio can comb-filter. Try an equal-gain-style pair and correct timing first. ### Why does a crossfade sound hollow? Similar sources are probably misaligned in time or phase, causing comb filtering during the overlap. Align them before changing curve or duration. ### Can a crossfade remove an edit click? A very short crossfade can hide a discontinuity where two clips meet. It is not the right repair for mouth clicks, vinyl ticks or random digital impulses inside one recording. ### What is the best crossfade length? Use the shortest overlap that transfers continuity without cutting attacks, tails, words, beats or ambience. The source and purpose determine the duration. ## Approve the Start, Midpoint, and Exit Align and level-match the sources, place the overlap in compatible material, choose complementary curves from the actual correlation, and judge the start, midpoint, and end in stereo and mono before committing. Last fact-checked September 13, 2026 against the current Sound Forge Pro 2026 Mix, Processing Dialogs and Crossfading Events help, plus the cited crossfade references. ### Time Stretch and Pitch Shift in Sound Forge URL: https://soundforgepro.com/time-stretch-pitch-shift-sound-forge/ Last updated: 2026-10-09T22:00:27.000Z **To change duration without changing pitch**, use **Process > Time > Time Stretch**. In **Process > Time > élastique Timestretch**, change time while keeping the pitch adjustment at zero. To transpose without changing length, use **Effects > Pitch > Shift** with duration preservation enabled. Pitch Bend follows an envelope. Rate-only resampling changes speed and pitch together. These steps follow the Sound Forge Pro 2026 documentation; there was no hands-on Windows or listening test. Older editions and other Sound Forge products may show different controls. Keep the original untouched and save a working copy under a different name before you apply any process. ## Calculate Duration, Speed and BPM Separately **Duration ratio = target seconds ÷ original seconds.** Multiply by 100 for a duration percentage. The speed ratio is its reciprocal: original seconds ÷ target seconds. A field measured in seconds wants a duration, and a percentage won't fit it. To shorten 30.000 seconds to 27.500 seconds, use a duration ratio of 0.916667, or about 91.6667% of the original length. That works out to about 109.0909% speed. Keep extra digits during the calculation and check the final endpoint, because a rounded percentage won't guarantee an exact delivery time. For a fixed musical span, **new duration = old duration × old BPM ÷ new BPM**. An eight-second phrase at 120 BPM becomes 7.5 seconds at 128 BPM: 93.75% duration, or about 106.6667% speed. Use the same beat unit and beat count. Extra silence, a half-time estimate or tempo drift will break that simple calculation. The [tap-tempo tool](https://soundforgepro.com/tap-tempo/) can estimate a pulse, but it can't prove an exact recording tempo. ## Change Duration Without Changing Pitch 1. **Preserve the source.** Save a separate working copy. Preview and Undo are not backups. 2. **Select the passage.** Use a data selection and include the channels that must stay together. With no data selected, the documented time-stretch commands process the entire file. 3. **Open the effect.** Choose Process > Time > Time Stretch or Process > Time > élastique Timestretch. 4. **Set the output target.** Enter the calculated duration in the effect’s displayed units. In élastique, keep pitch adjustment at zero and recheck it after loading a preset or moving the Pitch/Time point. Use the dialog’s ? help for its controls. 5. **Preview difficult material.** Compare exposed speech, an attack and a sustained note where present. Use Bypass to hear the unprocessed signal and pre/post-roll to hear the joins. 6. **Apply and verify.** Check the resulting duration, peaks, boundaries and downstream references. Save under a new name, reopen the result and inspect the actual delivery file. The [current Time Stretch help](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/time%5Fcompress%5Fexpand.htm) confirms both menu commands and the no-selection scope, but leaves effect-specific controls to the dialog’s **?** button. Don't borrow a mode, maximum ratio, formant percentage or shortcut from VEGAS, Cubase, Mac or an older Sound Forge build. Shorter duration makes speech faster; longer duration slows it down. For narration, remove unnecessary pauses before stretching every syllable. For music, confirm the start transient and final beat. Compare each setting from the same original rather than repeatedly processing a stretched result. ## Input Selection Is Not Output Duration In the [processing-dialog controls](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/using%5Fprocessing%5Fdialogs.htm), **More** exposes Start, End and Length for the *input selection*. Shortening Length there selects less audio. It doesn't set the stretcher’s destination length. Set the passage first, then the effect’s output target. With the Event tool, those documented controls differ: Start, Length and Channels are locked, End is unavailable, and previous/next event controls navigate selected events. The [Event tool documentation](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/the%5Fevent%5Ftool.htm) says to preserve editable events in a Sound Forge project. For the single-clip and rate-only recipes here, use a separate audio copy rather than treating an event layout as one data selection. ![Waveform selection with pre-roll and post-roll zones on either side, marking which audio is processed and which is only auditioned](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/09/sf-time-stretch-pre-post-roll.webp) Pre-roll and post-roll let you audition audio around the selection. They do not set the stretch target. Bypass plays the original; it won't undo a process you've already applied. If real-time preview stutters, try the documented non-real-time preview and check the saved result before blaming the stretcher. ## Check Both Joins and Later Timing A processed passage joins untouched audio at each end, so listen across both boundaries. A click suggests a discontinuity, but check the source first, because the fault may already be there. If the join causes it, try a short fade or a controlled [Sound Forge crossfade](https://soundforgepro.com/crossfade-audio-sound-forge/). Don't hide a smeared attack inside the selection behind an unrelated boundary fade. Changing a passage’s length can move later audio in a waveform edit. Don't assume events or every marker type follow the same rule. Note the intended start, end and downstream references, then inspect them after processing. The [markers and regions workflow](https://soundforgepro.com/sound-forge-markers-regions/) helps document those positions. For picture sync, check the changed copy before replacing material in the session. ## Change Pitch Without Changing Duration Select the note or phrase, choose **Effects > Pitch > Shift**, enter the interval in the units the installed effect offers, and enable duration preservation. Preview the exposed note and both joins, then check tuning, length and peaks. The [current Pitch help](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/pitch.htm) says outright that Shift works *with or without* preserving duration. Choosing Shift on its own won't keep edit points fixed. In twelve-tone equal temperament, 12 semitones make an octave and 100 cents make a semitone. **Frequency ratio = 2^(semitones ÷ 12)**; one octave doubles frequency and one semitone multiplies it by about 1.05946\. For positive measured frequencies, **cents = 1200 × log₂(target frequency ÷ source frequency)**. The [note frequency chart](https://soundforgepro.com/musical-note-frequency-chart/) gives you tuning references, but it won't detect the key for you. Formants are resonant regions that shape timbre. They aren't the fundamental or individual harmonics, which is why a correctly transposed voice can still sound unnatural. If the installed effect offers formant preservation, compare it using that effect’s help. Preserving pitch, duration and formants are separate goals, and no checkbox guarantees an unchanged vocal identity. ## Use Pitch Bend for a Changing Interval Choose **Effects > Pitch > Bend** for a rise, fall or return over time. The current Pitch help documents a semitone range, selectable curve types and up to **16 envelope points**. **Preserve original duration** keeps length fixed; the vendor says it works best for small corrections up to about ±2 semitones. That advice is about Bend. It isn't a universal limit for Shift or élastique. The Bend graph’s waveform display is unavailable above **300,000 selected samples**. That's a display restriction; it doesn't cap the file length you can process. It works out to 6.25 seconds at 48 kHz or about 6.803 seconds at 44.1 kHz. ## Correct a Constant Speed-and-Pitch Error A record captured at the wrong constant speed needs linked correction. Pitch-only processing leaves the duration wrong, and time-only stretching leaves the pitch wrong. Work out the intended and captured speeds first. A drifting tape needs a correction that changes over time; one averaged ratio won't fix it. 1. **Keep the capture.** Work on a separate audio copy and note the current sample rate. 2. **Calculate the speed ratio.** Divide intended speed by captured speed. A 45 RPM record captured at 33⅓ RPM needs 45 ÷ (100/3) = 1.35\. Reverse the situation and reverse the ratio. 3. **Calculate the temporary rate.** Multiply the current rate by the ratio: 44,100 × 1.35 = 59,535 Hz in this hypothetical example. 4. **Change playback rate only.** Open Process > Resample > Resample, enter 59,535 in New sample rate and enable Set the sample rate only. The existing samples now play faster and higher without being recalculated. 5. **Verify the correction.** Duration becomes 1 ÷ 1.35, about 74.07% of the capture. Pitch rises 12 × log₂(1.35), about 5.20 semitones. Check the intended speed and tuning, not just the displayed rate. 6. **Convert for delivery.** Run Resample again to the required 44,100 or 48,000 Hz with Set the sample rate only off. Normally leave Allow aliasing/imaging above 3dB off. This preserves corrected pitch and duration, subject to whole-sample rounding. 7. **Reopen the saved result.** Save under a new name; verify duration, pitch, rate, peaks and both ends before delivery encoding. The [2026 Resample documentation](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/resample.htm) includes both the full submenu path and the shortened Process > Resample wording. It describes rate-only changes using close sample rates. Check whether the installed dialog accepts the temporary rate and the playback path can audition it. If not, preserve the capture and audition a separately converted delivery copy rather than substituting an arbitrary rate. Normal [sample-rate conversion](https://soundforgepro.com/how-to-change-sample-rate-sound-forge-pro/) recalculates samples without intentionally changing pitch or duration. Don't use the rate-only checkbox just to meet a delivery specification. ## Reject Artifacts Before Export Level-match the source and candidate. Listen for metallic consonants, softened or doubled drum attacks, unstable bass, and pulsing ambience. Compare the source, preview and saved output before assigning a cause. Inspect peaks and listen in mono as well as stereo. Reprocessing can add artifacts; make alternative renders from the original. [DSP developer Stephan Bernsee’s time/pitch overview](https://blogs.zynaptiq.com/bernsee/time-pitch-overview/) explains signal-dependent smearing, tonal artifacts and formants. There's no universal artifact-free percentage. If the result fails, reduce the change, tighten pauses, recut at a phrase boundary or go back to individual tracks. For note- or source-level edits, compatible Melodyne or SpectraLayers editions may be more suitable. The [Sound Forge ARA help](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/proonly/ara.htm) requires the VST3 installation/search path and uses Tools > Edit in Melodyne (ARA) or Tools > Edit in SpectraLayers (ARA). Ordinary Plug-In Chain loading does not provide that Melodyne integration. Editing capabilities depend on the external edition and material; integration alone proves neither licensing nor polyphonic note-editing rights. Once the edit passes, use the [Core Editing workflows](https://soundforgepro.com/tag/core-editing/) for surrounding edits and exports. Keep a processed master and derive delivery formats from it. ## Time Stretch and Pitch Shift FAQ ### Can Sound Forge slow audio without lowering pitch? Yes. Lengthen the target duration with Time Stretch, or adjust élastique time while keeping pitch adjustment at zero. Check source selection, units and the saved result. ### Does Pitch Shift always preserve length? No. The documented Shift effect supports both behaviors. Enable duration preservation when the selection must keep its length, then verify the endpoint. ### Why is my BPM result wrong? Check for an inverted duration ratio, mismatched beat units, a half-time estimate, extra silence or tempo drift. For the same beat count, target duration equals original duration multiplied by original BPM divided by target BPM. ### Why does stretched speech sound metallic? It can be a processing artifact, but compare the source and saved output first. A source fault or struggling real-time preview can mislead you. Reduce the change or compare another method from the untouched file. ### Why use two Resample passes for varispeed? The rate-only stage changes linked speed and pitch without recalculating samples. A subsequent normal conversion returns the corrected audio to the required delivery rate. Leave Set the sample rate only off for that second stage. ### Should I stretch in several small passes? Not by default. Reprocessing can add artifacts and obscures which setting caused a fault. Compare one-pass renders from the same original instead. **Documentation checked September 15, 2026.** Calculations are illustrative. ### Fade In and Fade Out in Sound Forge: Clean Edges URL: https://soundforgepro.com/fade-in-fade-out-sound-forge/ Last updated: 2026-10-08T13:42:10.000Z **Quick answer:** select the exact range, then choose **Process → Fade → In** for a linear rise from −Inf to 0 dB or **Process → Fade → Out** for 0 dB to −Inf. Use **Process → Fade → Graphic** when the transition needs another curve, an intermediate level, or multiple envelope points. The selection sets the fade length; the curve sets how quickly the level moves inside it. Work on a copy because these commands change the selected audio data. Here 0 dB means unity gain: the original sample level is unchanged, not normalized to 0 dBFS. −Inf means silence. A fade can prevent an edge click, preserve a natural release, shape a musical ending, or move room tone into silence. Those aren't the same job. The shortest fade that removes a sample discontinuity might be perfect for an edit and completely wrong for a song ending. ## Choose the Fade by Purpose | Purpose | Selection strategy | Starting approach | | ----------------------------------- | ----------------------------------------- | ---------------------------------------------------- | | Remove a click at a cut | Tiny range around the discontinuity | Shortest transparent fade | | Preserve a drum or consonant attack | End fade before the transient | Short, conservative fade-in | | Complete a reverb or note tail | Cover the full natural decay | Curve that follows the perceived release | | Fade room tone to silence | Include stable ambience before exit | Smooth transition without a sudden gate | | Musical ending | Align with bars, phrases, and arrangement | Graphic envelope and repeated full-context listening | Fix the selection before you fade. No curve can bring back a clipped attack or a missing tail. Work on a copy or keep enough source handles to move the boundary. ![Decision guide for choosing basic Fade In, Fade Out, or Graphic Fade in Sound Forge](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/10/fade-tool-desktop-v20261005.webp) Use a basic linear fade for a simple edge and Graphic Fade when the envelope needs points or another segment type. ## Basic Fade In and Fade Out 1. Make a working copy, then zoom to the intended transition. 2. Select the complete fade duration. 3. Play from several seconds before the selection through several seconds after it. 4. Choose **Process → Fade → In** or **Process → Fade → Out**. 5. Apply to a copy and audition the full context again. The [current Sound Forge Pro 2026 Fade documentation](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/fade.htm) calls the basic commands Fade In and Fade Out. In moves from −Inf to 0 dB, while Out moves from 0 dB to −Inf. If no data is selected, the fade applies to the entire file, so confirm the selection before committing a destructive operation. > **Selection check:** no selection means the fade is applied to the entire file. In the Graphic Fade dialog, you can refine the range before applying the envelope. Boris FX documents the shared [Preview, Bypass, selection, pre-roll and post-roll controls](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/using%5Fprocessing%5Fdialogs.htm); use them to hear the transition into and out of the selected range instead of judging the fade in isolation. For sample-level boundary work, the official [Sound Forge selection guidance](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/selecting%5Fdata.htm) explains how to set the selection start, end and length. Zero-crossing snapping is covered separately below. For a WAV, FLAC or MP3 delivery, make the fade in a lossless working file first. Then export the approved master once. Reopening an MP3, fading it and encoding it again adds another lossy generation; the [Sound Forge MP3 export guide](https://soundforgepro.com/how-to-export-mp3-from-sound-forge-pro/) covers the separate codec and bitrate choices. ## When to Use Graphic Fade Choose **Process → Fade → Graphic** for a custom envelope. The current help allows up to 16 points. Double-click to create a point, drag points to set level, right-click a point and choose Delete to remove it, and right-click an envelope segment to choose its curve. The graph’s maximum-gain range can also be changed when the envelope needs boost as well as attenuation. Add extra points only when they describe a real listening decision: hold room tone, duck an interruption, recover after a loud breath, or shape a multi-stage musical ending. More points don't automatically mean a smoother fade; they can just as easily create bumps and accidental level changes. ## Linear, Fast, Slow, Smooth, Sharp, and Hold Sound Forge lists Linear, Fast, Slow, Smooth, Sharp, and Hold segment types. Those labels tell you which envelope you picked in the menu; they don't guarantee the same perceived motion on dialogue, drums, ambience and a full music mix. Start with the simplest curve, preview the complete transition, and change one variable if the result sounds wrong. ![Linear amplitude ramp with half amplitude marked at minus 6.02 dB beside Sound Forge segment types](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/10/fade-scale-desktop-v20261005.webp) A straight amplitude ramp is curved on a decibel scale; half amplitude equals about minus 6.02 dB. The ear doesn't hear amplitude as a simple straight ruler, so a visually linear envelope may not feel like a steady loudness change. Linear here describes how sample amplitude changes rather than a straight line on a decibel scale: half amplitude is about −6.02 dB, not −3 dB. That's why the middle of a long linear fade can seem quieter than its waveform suggests. Use the curve that produces the intended motion in context, and check low-level tails at the actual listening volume. ## Short Fades for Click Prevention A click occurs when an edit creates an abrupt sample-value discontinuity. Move the cut to a nearby safe point or zero crossing when possible. [Sound Forge’s current Selection Snapping help](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/selection%5Fsnapping.htm) says edits at zero crossings reduce the chance of glitches. Use Edit → Selection → Snap to Zero (Z) for both edges or Snap Edge to Zero (Shift+Z) for the active edge. In stereo, left and right may cross zero at different samples, so a visually clean point in one channel can still click in the other. If the boundary must stay, or no shared safe crossing exists, apply the shortest fade that makes the step inaudible. A long fade changes articulation and weakens attacks without fixing why the edit was bad. ![Fade boundaries for click repair, attack preservation, natural tails, and room tone](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/10/fade-boundary-desktop-v20261005-v20261006.webp) Boundary first: keep a fade before the attack, follow a natural tail, and use only a tiny repair around a click. Test the repair on headphones and speakers, but do not monitor a suspected full-scale click loudly. Compare with the unprocessed boundary at a safe level. A single click exactly at the cut points to the boundary. Repeating clicks inside the audio point elsewhere; a click that happens only when playback starts or stops may belong to the driver or device rather than the file. | What you hear | Check before making a longer fade | | ------------------------------- | ------------------------------------------------------ | | One click at the edit | Selection edge, zero crossing and a tiny boundary fade | | Regular clicks through the file | Dropouts, digital errors or repeated damage | | Click only on Play or Stop | Audio driver, buffer and playback path | | Thump at many edits | DC offset before treating every edge separately | | Rasp that survives the fade | Clipping or distortion inside the waveform | If the click is not confined to the boundary, stop lengthening the fade. Use the [click-and-pop repair guide](https://soundforgepro.com/how-to-remove-clicks-pops-sound-forge-pro/) for repeated damage or check [DC offset](https://soundforgepro.com/remove-dc-offset-sound-forge/) when many edits produce the same low-frequency thump. ## Preserve Attacks and Consonants A fade-in that overlaps a drum transient, pick attack, inhale, or unvoiced consonant changes articulation. When stable room tone is available, start the selection earlier and let the fade reach full gain before the event. If there's no handle, use a curve that restores level quickly without exposing the boundary click. Judge a speech edit from the previous sentence through the first complete word. Soloing only the fade can make a damaged consonant seem acceptable because the listener has no rhythmic or linguistic context. ## Musical Fade-Outs Choose the musical end before drawing the envelope. Count bars and phrases, identify the last event that must remain intelligible, and listen to vocals, bass, drums, and reverb separately. A curve that suits cymbal decay can make bass disappear too early; a fade that preserves bass may expose vocal breaths. Use Graphic Fade to change slope over time: a gentle initial reduction can preserve the arrangement, followed by a steeper final descent once the last phrase resolves. Avoid a late sudden drop caused by choosing a Hold segment unintentionally. After approving the fade, measure final delivery level only if required. If you normalize after fading, listen to the ending again: positive gain raises the remaining tail and noise together. The [normalization guide](https://soundforgepro.com/how-to-normalize-audio-in-sound-forge-pro/) explains the separate level decision. ## Room Tone, Noise, and Silence Speech and field recordings often sound more natural when room tone fades smoothly rather than cutting to digital silence. Select a stable ambience bed, avoid obvious moving sounds, and fade after the final breath or release. If the noise floor changes inside the fade, the listener may hear a tonal sweep even when the level curve is smooth. Noise reduction before the fade can expose pumping, and the same processing after the fade can react differently as the signal drops. Approve restoration and ambience continuity before finalizing the end, and always compare with the original. ## Fades vs Crossfades A fade changes the level of one source over time, often to or from silence; a crossfade overlaps two sources while one falls and the other rises. Reach for a crossfade when continuity should pass between clips, room tones, takes, or punch-ins, and for a plain fade when the destination is silence or full level within one file. The current [Boris FX event-crossfade documentation](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/event%5Ffades.htm) confirms that overlapping events can receive automatic crossfades and that their fade types can be changed independently. The [Sound Forge crossfade guide](https://soundforgepro.com/crossfade-audio-sound-forge/) covers overlap, complementary curves, midpoint level and phase. Two independent fades placed side by side aren't automatically a transparent crossfade. ### Fade vs Trim vs Level Change Trimming removes time. A fade keeps the selected time but changes its level across that range, while a fixed level change raises or lowers the whole selection by one amount. Use Graphic Fade only when level must move over time; there's no reason to draw a flat multi-point envelope for a simple gain adjustment, or to fade unwanted silence that should be trimmed away. For many separate files, fix and approve one boundary before automating. The [Auto Trim/Crop guide](https://soundforgepro.com/sound-forge-auto-trim-crop/) explains threshold-based silence removal and its own Fade in/Fade out settings. Inspect those resulting edges before adding another fade manually. ## Graphic Fade Workflow for Complex Repairs 1. Mark the start and end of the problem in context. 2. Create outer points at unchanged gain. 3. Add the fewest points needed to reduce or restore level. 4. Choose curve types segment by segment. 5. Preview the hardest transition and the surrounding phrase. 6. Reset and simplify if the envelope creates pumping or bumps. 7. Apply once from the untouched working copy. The current help notes that waveform display in the Graphic Fade graph is unavailable for selections over 300,000 samples. That doesn't block the fade; use the main waveform view, markers, duration readout, and listening context for long selections. ## Final QA - Selection starts and ends at the intended musical or editorial points. - No attack, consonant, breath, or tail is unintentionally weakened. - The curve has no unintended steps or level bumps. - Noise and room tone disappear naturally. - The transition works on headphones, speakers, and at low playback level. - Peaks remain valid if Graphic Fade includes gain above 0 dB. - The processed file is saved as a new lossless master. ## Source-Specific Fade Decisions ### Dialogue and Voice-Over Protect the unvoiced consonants and breaths that keep the edit intelligible; place the fade on room tone before the first syllable when the recording has enough lead-in. If the file starts with speech, keep the repair short and check that the first sound remains intelligible. At an ending, listen through the final consonant and a natural amount of ambience. If several edits use different background beds, match the tone before shaping level. ### Drums and Percussion Transients expose fade mistakes immediately. A fade-in should normally reach full level before the hit unless the attack is intentionally softened. For one-shot samples, preserve the entire release and check that the final fade does not shorten the perceived room or cymbal decay. ### Music Masters Judge the ending in bars and phrases. Check whether vocals, bass, percussion, and reverbs appear to vanish in the intended order. A long master fade needs more than two points only when the arrangement calls for distinct stages; automation bumps are more distracting than a simple well-placed curve. ### Ambience and Field Recordings Choose a section without passing vehicles, birds, footsteps, or wind changes. A smooth level envelope can't make a moving event sound stationary. If an obvious event enters during the fade, move the boundary or repair the ambience bed before fading. ## Make Comparisons Repeatable Save two or three candidate fades from the same untouched working copy. Keep the selection boundaries fixed and change only the curve, or keep the curve fixed and change only the duration. Comparing a short linear fade against a long smooth fade changes two variables at once, so it won't tell you which decision helped. Play each candidate from the same marker, several seconds before the transition. Match monitoring level and ignore which envelope looks prettiest. Include a low-volume pass as well; a tail that feels smooth at editing volume can disappear abruptly at normal listening level. For a group of similar clips, approve a template on the hardest attack and longest tail before applying it broadly. Then inspect outliers. A preset is a starting geometry, not evidence that every source received a correct boundary. ![Controlled fade comparison that changes curve or duration one variable at a time](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/10/fade-compare-desktop-v20261005.webp) Keep the boundary fixed when comparing curves, or keep the curve fixed when comparing duration. ## Common Fade Mistakes - **Applying with no selection:** the whole file is processed. - **Using a long fade to hide a bad cut:** repair or move the boundary first. - **Fading through a transient:** end the fade before the attack or restore level faster. - **Cutting a reverb tail:** extend the selection and follow the actual decay. - **Adding many Graphic points:** simplify to the few decisions the ear needs. - **Confusing fade with crossfade:** overlap both sources when continuity must pass between them. ## Fade In/Out FAQ ### Where are fade controls in Sound Forge? Select the audio and open **Process → Fade**. In and Out apply the basic linear fades; Graphic provides custom points and curve types. ### What is the best fade curve? There is no universal best curve. Choose from the source, duration, attack or tail, room tone and intended perceived motion, then listen in full context. ### How long should a fade be to remove a click? Use the shortest fade that removes the boundary discontinuity without weakening nearby audio. If it must be long, reconsider the cut or diagnose another cause. ### Can Graphic Fade use multiple points? Yes. Current Sound Forge help allows up to 16 envelope points, but fewer points are easier to control and verify. ### Is a fade the same as a crossfade? No. A fade changes the level of one source over time, often to or from silence; a crossfade overlaps two sources and transfers continuity between them. ### Can Sound Forge fade an MP3 or WAV file? Yes, but apply and approve the fade in a lossless working copy before the final export. Re-encoding an already compressed MP3 adds another lossy generation. ### Why does my fade still click? The click may not be a boundary discontinuity. Check for repeated damage, DC offset, clipping, plug-in latency or a playback-device click before making the fade longer. ### Does a linear fade sound linear? Not necessarily. Sound Forge’s basic fade changes amplitude linearly, while decibels and perceived loudness do not follow the same straight line. Compare the curve at normal listening level. ## Fix the Boundary Before Choosing the Curve Fix the boundary first, select the real duration, choose the curve by listening, and use the fewest points and shortest transition that preserve the source’s attack, tail, and ambience. Last fact-checked September 13, 2026 against the current Sound Forge Pro 2026 Fade, processing-dialog, selection, snapping and event-crossfade help. ### Sound Forge Channel Converter: Mono, Stereo & Swap URL: https://soundforgepro.com/sound-forge-channel-converter/ Last updated: 2026-10-09T21:03:17.000Z **Quick answer:** open **Process > Channel Converter**. For a normal stereo fold-down, start with the current system preset **\[Sys\] Stereo to Mono - Use both channels (50%)**. It sends 50% of the left input and 50% of the right input to one mono output. Preview the most revealing section, watch the sample peaks, then compare the result with the original at matched loudness. Use a different matrix when you need one good channel, dual mono, an L/R swap, or a deliberate custom mix. Each source percentage sets its amplitude contribution to an output. Enter **50.0%** for half of an input, not −6 in a percentage box. A 50/50 fold gives **0.5L + 0.5R**. The result depends on whether the inputs reinforce or cancel; it is not a fixed loudness change. ## Choose the Job Before the Preset | Source problem | Required output | Safe starting route | | ----------------------------------------------- | --------------------------------- | ------------------------------------------------------------------------------- | | A finished stereo mix must be mono | One-channel mono | 50% L + 50% R, then check peaks and mono compatibility | | A microphone exists on the left side alone | One-channel mono | 100% left + 0% right, provided the right side is genuinely unusable | | A mono file must satisfy a two-channel delivery | Dual mono | Route the mono source to both outputs; decide the level from the delivery brief | | Left and right were recorded backwards | Stereo with corrected orientation | Use *Stereo to Stereo - Swap Channels* | | A centered element disappears in mono | Diagnosis before conversion | Inspect polarity and timing; do not compensate with gain | Listen to each source channel before processing. A flat-looking side may still contain hiss, room sound, another microphone or a safety track. Check quiet passages before discarding it. Use the [Sound Forge Statistics workflow](https://soundforgepro.com/how-to-use-statistics-sound-forge-pro/) to compare peak and RMS values, but let the delivery requirement decide whether you need one-channel mono, dual mono or stereo. The [Core Editing guides](https://soundforgepro.com/tag/core-editing/) cover the surrounding recording, editing and export steps. ## Read the Channel Converter Matrix The [Sound Forge Pro 2026 Channel Converter help](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/proonly/channel%5Fconverter.htm) defines each row as an output. For stereo input, **Source 1** is left and **Source 2** is right. **Output channels** sets the output count: 1 for mono or 2 for stereo. Each source cell sets that input’s contribution to the row. **Invert Mix** reverses the polarity of the completed output mix. With mono input the help instead calls the per-channel gain field **Output**; there is only one source to distribute. Read one output row at a time: which source should be audible, at what percentage, and with normal or inverted polarity? A stereo swap, for example, needs left input routed to right output and right input routed to left output, with no crossfeed left behind. A stereo-to-mono fold needs one output row fed by both sources. This input-to-output reading prevents accidental double routing. The interface says *Invert Mix*, while the help talks about reversing phase. In audio-engineering terms the control flips polarity: every sample changes sign. It won't move the waveform in time, repair room reflections, or line up two microphones with different delays. ![Channel Converter set to one output with Source 1 and Source 2 at 50.0 percent and Invert Mix unchecked](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/09/sf-channel-converter-stereo-to-mono.webp) Stereo input: follow the single output row across Source 1 and Source 2\. Both contributions are 50.0%; Invert Mix is off. ## Convert Stereo to Mono in Sound Forge 1. **Protect the stereo source.** Save a separate working copy. For a short experiment, make a separate file containing the test passage; do not depend on a channel-count change staying inside a selection. 2. **Choose a revealing selection.** Include the loudest passage plus a section with wide ambience, hard-panned detail, or a centered vocal. 3. **Open Channel Converter.** Choose *Process > Channel Converter*. 4. **Set the 50/50 fold.** The current help illustration shows \[Sys\] Stereo to Mono - Use both channels (50%). If the preset is absent, set Output channels to 1, Source 1 to 50.0%, Source 2 to 50.0%, and Invert Mix off. Check the displayed values even when loading a preset. 5. **Preview and bypass.** Use the processing dialog's Preview and Bypass controls to compare processed and unprocessed audio. 6. **Check cancellation and peaks.** Listen for missing center content, hollow tone, or level jumps, and watch the channel meter for clipping. 7. **Apply and verify.** After approving the test copy, return to the full working copy. Confirm the whole intended time range and both source channels before OK. Save to a different filename, reopen it, and verify the channel count, routing and peaks. Keep the untouched stereo source. A 50% contribution is half amplitude, approximately −6.02 dB, calculated as 20 log10(0.5). The [digital-level help](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/monitoring%5Flevels%5Fin%5Fdigital%5Faudio.htm) rounds this to −6 dB. Identical in-polarity channels return to their original amplitude after a 50/50 sum. Material present on only one side is halved. Opposite-polarity identical channels cancel. **A pure 50/50 sum cannot exceed the larger input sample peak** when both inputs are within full scale: |0.5L + 0.5R| ≤ 0.5|L| + 0.5|R| ≤ 1\. By contrast, 100% + 100% can double identical inputs, a gain of about 6.02 dB, and exceed the integer PCM ceiling. This bound does not excuse an already clipped source, overrange floating-point samples, extra processing gain or later encoding peaks. Check the saved delivery and leave the headroom it requires. Don't normalize before you've decided whether the fold-down is acceptable. A louder preview can sound more convincing while hiding a routing mistake. Approve the channel relationship first, then use the [normalization workflow](https://soundforgepro.com/how-to-normalize-audio-in-sound-forge-pro/) if the mono deliverable needs a separate peak target. ## Check Mono Compatibility, Polarity, and Delay A safe sum depends on how left and right relate. Similar, same-polarity waveforms reinforce each other. If one channel is the exact inverted copy of the other, equal contributions cancel outright. And if one channel is delayed or processed differently, some frequencies reinforce while others cancel, which gives you comb filtering rather than complete silence. Sound Forge includes two useful checks. Its [Mono-Compatibility Meter](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/proonly/mono%5Fcompatibility%5Fmeter.htm) is designed to expose channel relationships that can cancel during a mono downmix. The [Phase Scope](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/proonly/phase%5Fscope.htm) visualizes the relationship in several plots. Neither meter replaces listening: inspect the passage where the meter turns suspicious, then compare stereo and mono at matched loudness. To repair a confirmed polarity-reversed input before summing, invert **only that source channel** first. Invert Mix on the mono row would negate the already combined result: −(0.5L + 0.5R), not 0.5L − 0.5R. Flipping silence cannot recover canceled content. If changing polarity helps one passage but hurts another, investigate timing and different source content. Gain alone cannot align delayed signals. On a working copy, use the Edit tool to [select the affected channel over the full intended range](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/selecting%5Fdata%5Fusing%5Fthe%5Fmouse.htm). Check **Lock Channel Selection** before adjusting the range so you do not accidentally change which channels are selected. Apply [Process > Invert/Flip](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/invert%5Fflip.htm), then select both channels for the mono conversion. With no data selected, Invert/Flip affects the entire file. Confirm the highlighted channel and range rather than relying on a previous selection. Subtracting one channel from the other also removes matching centered bass and drums. It is not source separation. Use the [vocal-removal guide](https://soundforgepro.com/remove-vocals-sound-forge/) for that separate task rather than treating Invert Mix as a vocal-isolation switch. ## Repair Audio Recorded on One Side A mono microphone often arrives as a stereo file with speech on the left and silence on the right. First solo both channels. If the right side contains no useful program, one-channel mono from the good side is usually the cleanest master: set one output, Source 1 to 100%, and Source 2 to 0% when the good signal is on the left. Reverse those values when the good signal is on the right. There's no reason to sum both sides by habit. Mixing a clean voice with an apparently empty channel can add preamp hiss, electrical noise, or crosstalk. Do not overwrite a second microphone or ambience bed either. If the destination requires two channels, create dual mono from the good source after confirming that a one-channel file is unacceptable. Channel conversion cannot repair distortion, hum or room echo already present in the retained source. Confirm the routing before restoration and level-dependent processing; a changed sum level can change how a compressor responds. Duplicating a missing stereo side does not recover the missing performance. ## Convert Mono to Stereo Without Claiming New Width Routing one mono source to both output channels creates **dual mono**. The two channels carry the same program and reproduce a stable center image. It can satisfy a video, broadcast, or ingest system that expects two channels, but it contains no stereo information. For unity-amplitude dual mono, set **Output channels** to **2**, put **100.0%** in each output’s gain field and leave both Invert Mix boxes off. Each output then matches the original mono samples; this does not promise the same perceived loudness through two speakers. The 2026 help illustration uses **\[Sys\] Mono to Stereo - 50 %** instead. At 50.0% per output, each channel is half the source amplitude, about 6.02 dB lower. Choose the gain deliberately rather than assuming that preset preserves per-channel level. ![Mono-to-stereo Channel Converter with two output rows at 100.0 percent each and both Invert Mix boxes unchecked](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/09/sf-channel-converter-mono-to-dual-mono.webp) The unity-gain dual-mono setup described above: two output rows at 100.0% each, both Invert Mix boxes off. The help’s own example uses the 50% preset, which leaves each channel about 6.02 dB lower. For simple duplication without building a matrix, the [Mono to Stereo dialog](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/stereo-mono%5Fmono-stereo%5Fconversion.htm) offers **Left Channel**, **Right Channel** and **Both Channels**. The first two leave the opposite side silent; Both Channels copies the program to both. Verify the saved levels and channel count rather than assuming a quick conversion uses your custom matrix. Delaying, detuning, or filtering one copy may create apparent width, but it also creates a different mix and can weaken mono playback. That's a creative stereo process; it has nothing to do with channel-format repair. If the job is sample rate, bit depth, WAV, FLAC, MP3, or another encoding change, follow the [Sound Forge audio conversion guide](https://soundforgepro.com/how-to-convert-audio-files-sound-forge-pro/) and leave routing untouched. ## Swap Left and Right Channels For a genuinely reversed stereo file, choose **Process > Channel Converter** and load **Stereo to Stereo - Swap Channels**. Verify two outputs: output 1 receives **0% Source 1 + 100% Source 2**; output 2 receives **100% Source 1 + 0% Source 2**. Leave both Invert Mix boxes off. This is L′ = R and R′ = L, with no added crossfeed or gain. Preview an obvious position cue before applying. Rule out the playback chain before modifying the file. Reversed headphones, cables or player routing can make correct media sound backwards. Use the [left/right speaker test](https://soundforgepro.com/left-right-speaker-test/) through the same path, at a comfortable level. Correct the file only when the reversal follows the media to a known-correct playback system. A [2023 community discussion about swapping two presenters](https://www.magix.info/us/forum/easily-swap-left-right-channels-for-a-given-selection--1324268/) reports a misleading selection warning in an older build. That is a historical report, not proof of current selection behavior. For a partial swap, test a disposable copy and inspect the audio before and after the selected range. Cancel if the dialog warns that it will change more than intended. ## Build a Custom Matrix Without Losing the Original Write the intended equation before entering custom values. A sum uses both inputs in normal polarity. A difference needs one source inverted before the sum; inverting the completed output row changes both contributions together. Multichannel routing follows the same input-to-output idea, but verify every channel’s identity and destination rather than assuming a stereo recipe is a surround downmix. **Synthetic routing checks, not a Sound Forge installation test:** with normalized sample values L = 0.8 and R = 0.8, a 50/50 fold returns 0.8; a 100/100 sum returns 1.6 and needs attenuation before integer delivery. With L = 0.8 and R = 0, the 50/50 result is 0.4\. With L = 0.8 and R = −0.8 it is 0; inverting the output still gives 0\. Correcting the reversed input first gives 0.8\. These arithmetic fixtures test the intended equations, not undocumented application rounding, selection handling or export behavior. For a repeated job, test the matrix on three files before batching: the loudest, the noisiest, and the widest or least correlated. Record the input channel count, output count, every non-zero percentage, polarity state, and resulting sample peak. Then use the [Sound Forge batch-processing workflow](https://soundforgepro.com/how-to-batch-process-files-sound-forge-pro/) only for files that share the same structure. ## Verify the Converted File - Confirm the saved file has the intended number of channels. - Solo each output and identify every audible input path. - Compare original and converted files at matched loudness. - Check sample peaks on the processed file and confirm that no clipping was introduced. - Listen in mono for missing center content, hollow tone, or comb filtering. - Check headphones and correctly wired speakers for left/right orientation. - Review the beginning, loudest passage, quietest passage, and end. - Save a new lossless master before lossy encoding. The [processing-dialog documentation](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/using%5Fprocessing%5Fdialogs.htm) explains Preview and Bypass. Extra wet/dry gain or fades, where available, change the result beyond the matrix. Inspect those controls rather than attributing an unexpected level change to the source percentages alone. Reopen the saved file for final checks; a preview is not proof of the exported delivery. ## Common Channel Converter Mistakes - **Mono clips or jumps in level:** inspect both source percentages and the actual correlation; do not assume a preset guarantees matched loudness. - **A centered vocal vanishes:** investigate polarity, delay, or stereo processing before changing gain. - **Dual mono still sounds centered:** that is correct; duplicated mono does not create width. - **A channel swap changes level:** reset the matrix and confirm that each input has one matched route to the opposite output. - **One-sided repair adds hiss:** route the good side alone instead of mixing in the noisy side. - Invert Mix fails to restore a canceled mono result: undo the fold and diagnose the individual sources. Output polarity inversion cannot undo cancellation. ## Sound Forge Channel Converter FAQ ### Where is Channel Converter in Sound Forge Pro 2026? Open **Process > Channel Converter**. To convert channel count without specifying a custom mix, use Audio channels in File Properties or right-click the Channels box in the status bar. ### What setting converts stereo to mono? Start with **\[Sys\] Stereo to Mono - Use both channels (50%)**. It creates one output from 50% left plus 50% right. Preview for cancellation and verify peaks because program-dependent correlation controls the result. ### Does mono to stereo create real stereo? No. Sending one mono source to both outputs creates dual mono. It can meet a two-channel delivery requirement, but it adds no spatial information. ### Can Channel Converter fix audio recorded on the left side? Yes. If the right side has no useful content, route 100% of the left source to one mono output, or to both outputs when dual mono is required. Inspect the quiet side before discarding it. ### Is Invert Mix the same as delaying a channel? No. Invert Mix reverses sample polarity. It does not move the channel in time, align microphones, or correct frequency-dependent phase differences. ## Trace the Route, Then Prove the Output The reliable sequence is short: identify the required channel format, trace every active source-to-output path, preview a revealing section, apply once, and verify the saved file. Channel Converter can fold, duplicate, swap, and intermix channels precisely. It cannot recreate missing stereo information or turn a monitoring fault into a file repair. Documentation and routing arithmetic reviewed September 14, 2026\. UI labels and presets come from the current Boris FX online help and its illustrations. No local Windows Sound Forge execution or acoustic playback test is claimed. ### Remove DC Offset in Sound Forge Without Guessing URL: https://soundforgepro.com/remove-dc-offset-sound-forge/ Last updated: 2026-10-09T21:04:32.000Z **Quick answer:** measure first with **Tools → Statistics**, then open **Process → DC Offset** and use automatic detection or enter the measured correction. Analyze representative program audio instead of relying on the first five seconds when the file begins with a long mute or fade-in. After correction, run Statistics again and check both average value and peaks. DC offset is a constant positive or negative component that shifts the waveform’s baseline away from zero. It can waste headroom, create clicks at edits, and produce unexpected results in later processing. A waveform that merely has larger positive than negative peaks isn’t automatically offset, though, so visual diagnosis alone won’t settle it. ## DC Offset vs Normal Asymmetry The diagrams below show the diagnosis and workflow. A slow oscillation can average near zero over complete cycles and still give a non-zero mean in a shorter selection. | Observation | Likely cause | Correct test | | ----------------------------------------------- | --------------------------- | ----------------------------------------- | | Silence sits consistently above or below zero | DC offset | Average value over a representative range | | Positive peaks are larger, but baseline centers | Natural waveform asymmetry | Longer average near zero | | Baseline slowly rises and falls | Rumble or subsonic movement | Spectrum/listening and time-varying view | | 50/60 Hz tone and harmonics | Mains hum | Spectral analysis, not DC correction | | Click only at one edit | Sample discontinuity | Inspect the edit boundary | ![A constant DC offset compared with natural waveform asymmetry and low-frequency rumble](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/10/dc-offset-diagnostics-v20261009.webp) DC offset versus normal asymmetry: use the measured mean in Sound Forge — peak asymmetry and low-frequency drift are different problems. A signal can have unequal positive and negative peaks while its average remains zero. iZotope’s [explanation of offset versus waveform asymmetry](https://downloads.izotope.com/docs/ozone8/dither/index.html#filter-dc-offset) makes this distinction; the signal principle is not specific to Ozone. Correcting that shape as though it were a constant offset can change the file without solving a problem. A persistent non-zero average across representative captured audio is the stronger test. Captured room tone can reveal a shifted baseline, but inserted digital silence will sit at zero even when the adjoining recording is offset. ## Why DC Offset Matters A positive offset moves every sample upward. That reduces positive headroom while increasing unused negative headroom. Normalization, limiting, distortion, and other nonlinear processing can react differently when the waveform is not centered. Cutting or joining offset material at zero-valued boundaries can also create a step that clicks. The [current Sound Forge 2026 DC Offset documentation](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/dc%5Foffset.htm) warns that glitches and unexpected effects results can occur in offset files. Capture hardware is one possible source, but nonlinear processing can also produce a new mean. A file conversion alone is not enough evidence to diagnose the cause. ## Measure the Offset in Statistics 1. Open a lossless copy of the source. 2. Select a representative range or the complete file. 3. Choose **Tools → Statistics**. 4. Record the **Average value (DC offset)** for each channel. 5. Also record positive and negative peaks for comparison. 6. Repeat on another representative range if the reading changes materially. Use enough real audio to avoid a misleading estimate. A file that starts with digital silence will report near zero in that segment even if the later capture is offset. A long fade-in may underrepresent the stable offset. Conversely, a very short asymmetric note can have a non-zero local mean even when the full recording has no constant DC problem. Boris FX defines [Statistics → Average value](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/statistics.htm) as the sum of the selected sample values divided by the number of samples; a non-zero result can indicate DC offset. Our [Sound Forge Statistics guide](https://soundforgepro.com/how-to-use-statistics-sound-forge-pro/) covers the rest of the readout. Measure left and right separately because one input channel can be offset more than the other. ## Remove DC Offset Automatically 1. Select the complete recording with a consistent offset, including all intended channels. For an edited compilation, work on each source section separately. 2. Open **Process → DC Offset**. 3. Choose **Automatically detect and remove**. 4. Leave first-five-seconds-only disabled when the beginning is not representative. 5. Click OK to process the working copy. 6. Reopen Tools → Statistics on the same range and channels; compare the mean and both peak polarities, then listen across the edited boundaries. Sound Forge offers **Compute DC offset from first 5 seconds only** to speed analysis. The current help explicitly warns that five seconds may be insufficient when a long fade-in or mute occurs at the beginning. Treat the option as an optimization for uniform material, not a default accuracy setting. ![Measuring the average sample value in Statistics, correcting DC offset, then measuring again](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/10/dc-offset-interface-walkthrough-v20261006.webp) Removing DC offset in Sound Forge: measure the same representative scope in Statistics before and after the automatic correction. Check the selection before committing. The [processing-dialog controls](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/using%5Fprocessing%5Fdialogs.htm) let you inspect Start, End and Channels under More; right-clicking the dialog also provides Select All. If the result differs from the expected constant shift, check for unintended wet/dry gain or processing fades rather than repeatedly applying correction. ## Enter a Manual Correction The documented manual path is to record Average value readings in Statistics, open **Process → DC Offset**, choose **Adjust DC offset by**, and enter the correction. Use this when a controlled workflow needs an explicit value or when comparing automatic analysis across selections. Use a signed linear readout in Statistics, such as Percent or Sample Value, and check that the manual adjustment field uses the same units. A negative dB reading describes magnitude below full scale; it is not negative DC polarity and must not be pasted as an opposite-sign correction. The current textual DC Offset help does not specify the adjustment field’s units, so confirm them in the installed dialog or use automatic detection instead. For matching linear units, subtract a positive mean and add the magnitude of a negative mean; verify the same channel and analysis range afterward. ## Correct Before Gain-Dependent Processing ![Three correction scopes compared: the whole file, one edited segment and audio past a fade-in](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/08/dc-offset-scope-guide.webp) Match the Sound Forge DC Offset correction scope to the problem: the whole file, one edited segment, or audio measured past a long mute or fade-in. Correct a meaningful constant offset early, after the capture is safely copied and before normalization, compression, limiting, or nonlinear effects. This removes the constant bias; it does not guarantee equal positive and negative peaks. Natural waveform asymmetry can remain. If an earlier restoration step introduces a new offset, measure again rather than assuming one correction is permanent. **Check for new clipping:** subtracting a positive mean also pushes the most-negative sample farther down. As a numerical example, a minimum of −0.98 and a mean of +0.03 become −1.01 after subtraction, outside the nominal ±1 full-scale range. If the correction would exceed the file’s limits, undo it, lower the working-copy level, remeasure the mean and try again. Do not assume that centering always creates more usable peak headroom. Don’t normalize merely because offset removal changed peak values. First decide whether the delivery needs a peak or loudness adjustment, then follow the [normalization workflow](https://soundforgepro.com/how-to-normalize-audio-in-sound-forge-pro/) from the corrected master. ## Why the Result May Not Read Exactly Zero Subtracting the exact mean from the same analysis range gives zero mean in exact arithmetic; stored-sample rounding can leave a small residual. Measuring a different selection is a different test: a short asymmetric note, fade or low-frequency segment can still have a local mean. A whole-file correction does not force every smaller selection to zero. Judge improvement across representative ranges. If the full file is centered but one short note reports a local average, using that note’s mean to shift the whole file can introduce a new bias. Repeating exact whole-file mean subtraction on an unchanged file should add no meaningful correction. If the measured offset reappears after filtering, compression, limiting, or asymmetric clipping, inspect that process and its output rather than blindly running removal after every step. Before treating a new non-zero reading as a fault, compare its magnitude with the earlier reading on exactly the same selection. A tiny displayed residual without a headroom, edit or audible consequence does not justify another processing pass. ## DC Offset Is Not Hum or Rumble DC is 0 Hz: a constant component. Mains hum is usually 50 or 60 Hz plus harmonics, while rumble varies over time. The traditional Sound Forge **Process → DC Offset** operation changes samples by a constant amount, as described in its [DC Offset glossary entry](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/glossary.htm). That is not a hum notch, a rumble filter or a repair for the underlying electrical fault. Use the [hiss and hum diagnosis](https://soundforgepro.com/remove-hiss-hum-sound-forge/) when the problem is audible noise rather than a constant baseline shift. **coreFX Utility is different.** Its [Remove DC control uses a steep 5 Hz high-pass filter](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/utility.htm), according to the current help. Filtering can address near-DC drift as well as a constant component, but it can also change the signal. Do not treat Utility and Process → DC Offset as interchangeable settings. For a moving baseline, inspect several time ranges and compare the processed bass and edit boundaries before keeping the result. ## Partial Selections and Edit Boundaries Correcting only part of a file can create different baselines on either side of the selection. Even if each section is valid alone, the join may click. For a constant capture-chain offset, process the coherent recording as a whole. For material assembled from different sources, measure and correct each source before joining, then inspect boundaries. Inserted digital silence needs special care: subtracting the recording’s offset from zero-valued samples creates a new offset there. The [limitations of constant-offset removal](https://manual.audacityteam.org/man/dc%5Foffset.html#Limitations%5Fof%5Foffset%5Fremoval) also apply to an edited file containing both biased and unbiased sections. Preserve or restore the zero-valued gaps separately, and check both joins. For an offset repair, use short fades or crossfades after correcting the relevant source sections. The [Sound Forge crossfade guide](https://soundforgepro.com/crossfade-audio-sound-forge/) covers boundary continuity; a crossfade should not be used to hide an uncorrected whole-file offset. ## Three Diagnostic Scenarios ### One Continuous Analog Capture A cassette or preamp capture shows a similar positive average across beginning, middle, and end, and its silent lead-in sits above zero. That pattern supports one coherent whole-file correction. Measure the complete program or several long selections, correct before restoration EQ and limiting, then verify the same ranges, both peak polarities and the joins. ### Edited File from Multiple Recorders The first interview segment measures positive, the second is near zero, and the third is negative. One global average can look acceptable while each section remains offset. Identify source boundaries, correct each coherent recording separately, and crossfade only after their baselines are stable. Keep handles so boundary repairs remain reversible. ### Master That Changes After Limiting The premaster measures near zero, but the limited render reports a persistent mean and shows unequal positive and negative clipping. Compare the input and output of the limiter or nonlinear stage to locate where the mean changed. Check the drive level, saturation and clipping behavior. Removing DC afterward may center the result, but it does not undo distortion that occurred because one side hit the ceiling first. If samples have already been flattened, follow the separate [clipped and distorted audio diagnosis](https://soundforgepro.com/fix-distorted-audio/). ## Prevent the Offset from Returning Check the capture chain before repairing hundreds of files. Record a short test through the same interface input, preamp, cabling, gain, and power arrangement. If new recordings show the same offset, fix or replace the offending stage when practical. Software correction helps, but a repeatable hardware or routing fault shouldn’t stay invisible. In a processing chain, measure after clipping, saturation or waveshaping. The [apShaper manual’s waveshaping discussion](https://apulsoft.com/apshaper/apshaper-manual.pdf#page=24) explains why a nonlinear transfer can create DC even when its input has no offset. Linear gain and EQ do not normally invent a constant component from a well-centered source, though filters and finite selections can change local averages. For batch work, test files from different dates, inputs, and recording devices. Don’t derive one manual correction value from a single file and apply it across all recordings. Automatic detection per coherent file is safer when offsets vary; a fixed correction is appropriate only after measurements prove the same stable bias. ## How Much Offset Is Too Much? There’s no reason to adopt an arbitrary visual percentage as a universal pass/fail threshold. The decision depends on measurement length, program asymmetry, available headroom, edit requirements, and later nonlinear processing. A small stable offset may be technically correctable but inaudible; a larger offset that creates clicks or consumes headroom is clearly actionable. Record the measured mean, peak imbalance, and audible or workflow consequence. Correct when the evidence shows a constant bias and the change improves the file without damaging boundaries. This evidence-based rule is stronger than chasing an exact display value of 0.000 for every short selection. ## Final Verification - Average value is substantially closer to zero on representative audio. - Captured quiet passages with the same original bias are now near the centerline; inserted zero-valued gaps have not acquired a new offset. - Positive and negative headroom are no longer biased by a constant shift. - No new clipping was introduced. - Edits and file boundaries play without clicks. - Left and right channels were checked separately. - The corrected file remains a lossless working master. Keep the before-and-after Statistics readings with the project notes. A documented change is easier to audit than a vague claim that the waveform “looked centered,” and it exposes a later process that reintroduces a measurable bias. ## DC Offset FAQ ### Where is DC Offset removal in Sound Forge? Open Process → DC Offset. Use automatic detection or enter a measured adjustment from Tools → Statistics, then verify the result. ### Is an off-center-looking waveform always DC offset? No. Natural asymmetry and low-frequency movement can look off-center. Measure Average value over representative audio and inspect captured quiet passages, not just inserted digital silence. ### Should I calculate DC offset from the first five seconds? Only when those seconds represent the file. Don’t use the shortcut when the recording begins with a long mute, fade-in, or unusual material. ### Does removing DC offset remove hum? No. DC is a constant 0 Hz component; mains hum and rumble are time-varying frequencies that need separate diagnosis. ### Why is the average still slightly non-zero? Rounding can leave a small residual when remeasuring exactly the corrected analysis range. A different, shorter selection can have its own local mean from waveform asymmetry, fades or low-frequency movement. Compare the same range first rather than repeatedly correcting the whole file. ## Measure the Same Scope Before and After Measure a representative range, distinguish constant offset from waveform shape and rumble, correct the coherent source once, then verify the same scope before later processing. If different sections came from different recorders, treat them as separate sources. DC correction is a preparation step, not a substitute for editing or mastering. The [core editing guides](https://soundforgepro.com/tag/core-editing/) cover the subsequent cut, trim, level and export operations when the recording is ready. ### Sound Forge Bit Depth and Dither: 24-Bit to 16-Bit URL: https://soundforgepro.com/sound-forge-bit-depth-dither/ Last updated: 2026-10-09T21:04:55.000Z **Quick answer:** for a 16-bit delivery, finish processing and any required sample-rate conversion in a high-resolution master. Commit any live plug-in chain before using **Process > Bit Depth > Bit-Depth Converter**. Choose 16-bit, apply one planned dither stage, then save a separate PCM file at that same depth. Check the reopened delivery without applying the chain again. This guide follows Sound Forge Pro 2026 documentation, checked September 14, 2026\. It's a documented workflow; nobody ran a Windows listening test for it. The [Core Editing guides](https://soundforgepro.com/tag/core-editing/) cover the surrounding file-conversion tasks, and this page handles the final precision and dither decision. ## Start with Current Precision, Not the Filename Integer PCM uses a fixed amplitude grid. Processing can calculate values between those grid points. Writing those results back to integer PCM requires quantization, even when both the source and output filenames say 24-bit. An unchanged integer file copied without processing is different: it has no new values to round. | Current signal | Target file | Decision | | --------------------------------- | ------------------------------------- | --------------------------------------------------------------------------- | | Unchanged 24-bit integer PCM | 24-bit integer PCM | No new quantization; don't add dither by habit | | Processed floating-point result | 24-bit integer PCM | Consider one final 24-bit dither stage; check the processor and export path | | 24-bit or higher-precision master | 16-bit integer PCM | Use appropriate dither at final reduction | | Unprocessed 16-bit source | 24-bit or floating-point working file | More room for later calculations, not recovered source detail | | Floating-point working master | Floating-point intermediate | No conventional integer-target dither needed for this handoff | | Approved lossless master | MP3 or AAC | Follow encoder requirements; don't make an unnecessary 16-bit intermediate | **32-bit float is not 32-bit integer.** Floating point stores a value as a significand and an exponent instead of evenly spaced steps across the whole range, so its word length doesn't directly measure fixed-point audio resolution. It can hold above-full-scale calculated values in a compatible processing path, but it can't repair clipping that was already recorded or happened inside a processor. Check the actual output format; the number 32 alone tells you little. [Sound Devices explains the floating-point representation](https://www.sounddevices.com/32-bit-float-files-explained/); [DPA distinguishes the file's range from analog input clipping](https://www.dpamicrophones.com/mic-university/technology/32-bit-floating-point-and-other-conversions/). The [iZotope explanation of integer export and floating-point intermediates](https://www.izotope.com/community/blog/what-is-dithering-in-audio) recommends floating-point files for intermediate bounces and treats float-to-24-bit export as a dither decision. At 24-bit, ordinary flat triangular dither is generally enough, and its practical noise level is very low. That still doesn't justify adding it again to an unchanged 24-bit copy. ## What Dither Changes Rounding or truncating a quiet signal can create signal-correlated error, which you hear as distortion in exposed fades or tails. Well-chosen dither adds low-level noise before quantization to keep that error in check. It won't bring back discarded source information, reduce existing hiss or repair clipping. The [Audacity explanation of dither and unprocessed copies](https://manual.audacityteam.org/man/dither.html) describes why simple edits without amplitude processing can keep integer samples intact without fresh dither. Its product-specific settings aren't Sound Forge controls, though. Noise shaping is a separate choice: it moves noise around the spectrum so it's less audible in some conditions, but the noise is still there. ![Exaggerated 4-bit example comparing correlated quantization error with decorrelated dither noise](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/10/dither-change-desktop-v20261005-v20261009.webp) The exaggerated 4-bit map makes the mechanism visible: dither replaces signal-correlated error with low-level random noise; it does not lower the noise floor or restore bits. ## Convert 24-Bit to 16-Bit in Sound Forge 1. **Preserve the source.** Keep the approved high-resolution master unchanged and work on a separate delivery copy. Retain an FRG project's companion folder with its project file. 2. **Finish and commit processing.** Complete repair, EQ, dynamics, gain and fades. If a live Plug-In Chain is active, write a high-precision working render first with final delivery dither disabled, then reopen that render and bypass the already-applied chain. Use floating point where the chosen format supports it. 3. **Set the required rate and channels.** Perform any sample-rate conversion and channel mixing on the high-resolution copy before final reduction. Confirm the destination's file format, depth, peak limit and loudness requirement. 4. **Open the converter.** Choose Process > Bit Depth > Bit-Depth Converter. Select 16-bit for a 16-bit PCM delivery. 5. **Choose one dither stage.** Select the Dither and Noise shaping settings. Triangular with Noise shaping Off is a straightforward unshaped starting point. Do not also add a separate plug-in dither pass. 6. **Check and apply.** Preview an exposed fade or tail using the processing dialog's preview controls, then click OK. Compare alternatives from the unchanged master, not by repeatedly processing the reduced copy. 7. **Save a separate delivery.** Use File > Save As for an ordinary audio file, or File > Render As for an FRG project. Select the required PCM format and a matching 16-bit template; keep rate and channels unchanged. Use Custom if the format supports it. Do not apply an already-committed chain again. 8. **Reopen and verify.** Check actual format, integer depth, rate, channels, duration, peaks and required loudness. Inspect the beginning, loudest passage, fade and ending without new DSP. If it fails, revise the high-resolution master and make a new delivery. The [2026 Bit-Depth Converter help](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/bit%5Fdepth%5Fconverter.htm) documents the conversion menu, dither choices and OK action. [Save As/Render As help](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/saving%5Fa%5Ffile%5Fas%5Fa%5Fdifferent%5Fname%5For%5Ftype.htm) distinguishes audio files from projects and describes Template and Custom. The [project documentation](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/working%5Fwith%5Fprojects.htm) warns that deleting the companion folder breaks the FRG project. ## Avoid the Live-Chain Order Trap The current [Plug-In Chain documentation](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/proonly/plug-in%5Fchainer.htm) says the live window processes playback and applies effects when the file is saved. Hearing a finished master doesn't mean the underlying samples already carry that processing. If you dither the underlying waveform and then save through EQ, gain or limiting, dither wasn't the last step. The separate **FX Plug-Ins > Apply Plug-In Chain** workflow can commit processing to a selection, and it works differently from the live chain window. The [guide to the two chain workflows](https://soundforgepro.com/how-to-use-plug-in-chainer-sound-forge-pro/) explains their scope. For the converter method above, commit the full-file processing you want first, and make sure the final file doesn't get processed twice. ## Playback Depth Is Not Delivery Conversion The converter help also describes right-clicking the status bar's **Bit Depth** box to set depth for playback only. That shortcut doesn't prove a delivery file has been converted. Use the converter and check the saved file's properties. ![Sound Forge status bar with the Bit Depth box highlighted beside the Sample Rate and Channels boxes](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/10/sf-bit-depth-status-bar-playback-v20261006.webp) Right-clicking the Bit Depth box in the status bar changes playback depth only, separate from the Bit-Depth Converter dialog. The values shown are not recommended delivery settings. ## Set Level and Sample Rate Before Dither Sound Forge's converter help recommends maximizing level before reducing depth. Don't read that as an instruction to normalize every master to 0 dBFS. Set the intended loudness and required peak headroom first, and if the master already meets the brief, leave its level alone. Use [normalization](https://soundforgepro.com/how-to-normalize-audio-in-sound-forge-pro/) only when you need it, and finish [sample-rate conversion](https://soundforgepro.com/how-to-change-sample-rate-sound-forge-pro/) before the final integer quantization. Resampling calculates new sample values; just changing a playback-rate property doesn't resample anything. The delivery specification sets the output rate. There's no universal rule to convert everything to 44.1 kHz. ## Choose Dither and Noise Shaping Separately The converter offers Half Rectangular, Rectangular, Triangular, Highpass Triangular, Gaussian and POW-r. The official help describes Half Rectangular as having maximum dither amplitude 0.5 LSB and signal-dependent noise, and Rectangular as using 1 LSB. Those are the vendor's amplitude descriptions; there's no separate level knob to set. Triangular is described as avoiding conversion distortion and noise-floor modulation. Highpass Triangular pushes more noise toward higher frequencies. Gaussian is available, but the manual says it can do worse than the rectangular or triangular choices. None of these descriptions tell you which setting will be least audible on your recording. **Noise shaping Off** disables the extra shaping stage, but an already high-pass dither spectrum stays high-pass. **High-Pass Contour** moves noise upward. **Equal Loudness Contour** spreads it into high and low frequencies. The manual generally favors Highpass Triangular with shaping, but warns against shaping below 44.1 kHz, and at lower rates Triangular with shaping Off sidesteps that choice. The warning has no documented exception for Equal Loudness Contour. ## POW-r 1, 2, and 3 Are Different Curves POW-r offers three shaping modes. The manual describes #1 as a special dither curve, #2 as extra broad-range shaping, and #3 as stronger optimized shaping. It claims 5–10 dB of dynamic-range extension for #2 and up to 20 dB between 2 and 4 kHz for #3\. Those are algorithm descriptions. They aren't measured results from this article, and they don't add stored bits. The biggest number isn't automatically the best choice. Compare the exposed parts of the actual program and think about what happens to the file next. For files handed off for further processing, don't make strongly shaped 16-bit delivery dither your default intermediate format. ## Keep One High-Resolution Source of Truth Create delivery variants as separate branches from the master. For an audio-CD version, make the required 44.1 kHz, stereo, 16-bit PCM derivative, with rate and channel conversion before dither. A 16-bit WAV for another destination may require a different rate. For MP3 or AAC, feed the encoder the input format it accepts instead of making a 16-bit file just for it. [Apple's Digital Masters workflow](https://www.apple.com/apple-music/apple-digital-masters/docs/apple-digital-masters.pdf), for example, uses a floating-point intermediate for AAC encoding with no extra dither step at that boundary. That doesn't undo an earlier float-to-integer quantization decision. The [file-conversion guide](https://soundforgepro.com/how-to-convert-audio-files-sound-forge-pro/) covers containers and templates. ## Test Dither Without Fooling Yourself Make comparison files from the same master with identical level, rate, channels, target depth and sample range. Change one dither or shaping setting at a time. Listen at normal matched level first. If raising monitor gain to inspect a quiet tail, isolate that quiet section and lower the gain before returning to loud material. A sample-aligned polarity-inverted sum shows you differences. It doesn't score quality. Separate dither renders can contain different noise samples even with identical settings, so a nonzero residue alone doesn't mean the export is faulty. Don't normalize the delivery to inspect it; use a separate test copy if you need amplified analysis. Check peaks and [required loudness](https://soundforgepro.com/sound-forge-loudness-meters/) again on the reopened output, since dither and shaping can change peaks. According to the export help, save-time loudness logging happens before codec encoding, so on its own it can't vouch for a lossy file's decoded peaks. If a delivery fails, fix the master and regenerate it. ## Bit Depth and Dither FAQ ### Do I need dither when converting 24-bit to 16-bit? Use appropriate dither as the normal final reduction step. Finish sample-changing processing first and avoid a second independent dither stage during saving. ### Should I dither a 24-bit export? A processed floating-point result written to 24-bit integer PCM is a quantization decision. One final 24-bit dither stage can be appropriate. An unchanged 24-bit integer copy does not need another pass. ### Does converting 16-bit audio to 24-bit improve quality? It cannot recover lost source detail. A higher-precision working format provides room for subsequent processing, not restoration of the original recording. ### Which Sound Forge dither setting is best? No setting wins for every program. Triangular with Noise shaping Off is an unshaped starting point. The manual generally favors Highpass Triangular with shaping, but warns against shaping below 44.1 kHz. ### Can I normalize after dithering? In a planned workflow, set level before final reduction. If a revision is needed, return to the high-resolution master and regenerate the delivery. If only a reduced file survives, processing remains possible, but it cannot recover the earlier source precision. ### Is 32-bit float the same as 32-bit integer? No. Floating point uses a significand and exponent; integer PCM has a fixed amplitude grid. Check the actual file format and destination support instead of treating the number 32 as a complete specification. ### Sound Forge Auto Trim/Crop: Remove Silence Cleanly URL: https://soundforgepro.com/sound-forge-auto-trim-crop/ Last updated: 2026-09-30T20:13:50.000Z **Quick answer:** save a separate working copy, select the audio you intend to process, and choose **Process > Auto Trim/Crop**. Choose the function first: trimming selection edges, deleting gaps between phrases, and limiting file length are different operations. **Remove silence between phrases (creates regions)** deletes detected silence while creating regions. Use it only when those gaps should disappear. Start with a short test that includes the quietest wanted sound and the longest decay. Set thresholds from that recording, inspect the result, and go back to the unprocessed copy before trying different settings. A tidy Regions List can't tell you whether a consonant or an intentional pause went missing. ## Choose the function before setting thresholds The [Sound Forge 2026 Auto Trim/Crop help](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/proonly/auto%5Ftrim%5Fcrop.htm) lists these five functions. The first two differ in what happens outside your selection. | Function | What it removes | Check before applying | | ------------------------------------------------ | -------------------------------------------------------------------------------------------------- | ------------------------------------------------------------- | | Keep edges outside of the selection | Silence between the selection boundaries and the detected sound. Data outside the selection stays. | The selection includes the wanted attack and tail. | | Remove edges outside of the selection | The same edge silence, plus everything outside the selection. | Other takes outside the selection can be deleted. | | Remove silence between phrases (creates regions) | Detected silence between phrases inside the selection; it also creates regions. | You actually want to delete the gaps, not just mark them. | | Remove data beyond loop points | Data after the selected loop, subject to the minimum length following loop end setting. | The target sampler's requirements for samples after the loop. | | Remove data from start and limit file length | A specified amount at the beginning; it also trims files that exceed the maximum length. | The removed start or end may contain wanted audio. | For one hand-placed crop, use the [manual cut and trim workflow](https://soundforgepro.com/how-to-cut-and-trim-audio-in-sound-forge-pro/). This guide covers level-detected trimming. The [Core Editing guides](https://soundforgepro.com/tag/core-editing/) connect both approaches with recording and export. ## Measure the noise floor and the quietest wanted sound Compare a noise-only passage with the quietest sound you need to keep. Use the meters or [Statistics to inspect peak and RMS levels](https://soundforgepro.com/how-to-use-statistics-sound-forge-pro/), because waveform height is a poor guide once the display is zoomed. Leave any breath or reverb tail out of your noise sample if it belongs in the edit. A useful detection threshold must distinguish those two cases. If speech and background overlap in level, raising the threshold can remove speech along with the noise. If room tone changes halfway through the recording, test that section separately. There is no universal dB setting that preserves every voice, microphone distance, and room. ## Attack and release are level thresholds, not timing controls **Attack threshold** detects the trim/crop start point. **Release threshold** detects the end point. The current help defines **\-Inf.** as complete silence and **0 dB** as maximum amplitude. These controls set detection levels. They have nothing to do with attack or release time in milliseconds. A lower attack threshold can retain a quieter onset, but may also detect background. A lower release threshold can retain more decay, provided the decay remains distinguishable from the noise. Try changes on the original test copy and listen to the whole phrase. Neither setting understands words or musical phrasing. Attack and release don't have to match. Set each one from the sound it needs to detect. If no pair reliably separates wanted audio from the background, place the boundaries by hand instead of forcing a more aggressive preset. ## Use fades to check edges, not repair missing audio **Fade in** and **Fade out** set fade lengths associated with the detected start and end points. The Auto Trim/Crop help describes them as protection against glitches at phrase boundaries. They are separate from the level thresholds. A fade can't rebuild a deleted consonant. If an attack is missing, go back to the unprocessed copy, fix the selection or detection, and then check the fade. An unnecessarily long fade can also soften a transient that survived the trim. Give each boundary only as much fade as it needs, and don't copy one fixed duration across sounds that behave differently. For a deliberate musical entrance or ending, finish the trim first and use the [separate fade-in and fade-out workflow](https://soundforgepro.com/fade-in-fade-out-sound-forge/). Automatic edge treatment and a creative song fade solve different problems. ## Test a short selection before the whole recording 1. Save a separate lossless working copy and keep the source untouched. 2. Listen to the source and compare noise-only audio with the quietest wanted attack and longest tail. 3. Select a short representative range. Check its start, end, and selected channels before processing. 4. Open Process > Auto Trim/Crop and choose the function whose deletion behavior matches the job. 5. Set attack and release thresholds from the source. Set short edge fades; for phrase mode, also set minimum inter-phrase silence. 6. Preview the selection and compare with Bypass. Then apply the operation to the working copy with OK. 7. Inspect the changed waveform, retained audio, and any regions. Listen to complete phrases and both sides of every new boundary. 8. If the result fails, return to the unprocessed copy before changing settings. Process a larger range only after the test preserves the wanted audio. The [official processing-dialog guide](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/using%5Fprocessing%5Fdialogs.htm) documents **Preview**, **Bypass**, **OK**, and **Cancel**. Preview is an audition aid; inspect the applied result as well, especially when the operation changes file length or creates regions. Cancel closes the dialog without applying its settings. ![Shared Sound Forge processing-dialog controls: OK, Cancel, Preview, Bypass, Real-time and More](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/09/sf-auto-trim-processing-dialog-controls.webp) The shared Preview, Bypass, OK and Cancel controls of a Sound Forge processing dialog. Auto Trim/Crop settings appear separately. ## Delete gaps and create regions, or preserve the recording? Choose **Remove silence between phrases (creates regions)** for separated takes or effects only when you really mean to delete the gaps between them. **Minimum inter-phrase silence** sets how much silence has to exist before a new region is created. It won't leave that amount of room tone in the output. Raise that minimum if short pauses inside a phrase are producing extra regions. If adjacent takes merge into one region, check whether their gap meets the setting and whether the noise is getting in the way of detection. Count the results and audition each region; a plausible count doesn't mean the edges are right. If the gaps have to stay in the source audio, [Tools > Auto Region](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/proonly/auto%5Fregion.htm) creates regions from attacks or musical intervals without deleting any silence. It has different controls: attack/release sensitivity, minimum level, and minimum beat duration. Don't carry Auto Trim/Crop threshold values over as though the two dialogs were interchangeable. Auto Region's **Use release point for end of region** option can leave a quiet gap out of a region without deleting the gap from the source. Regions are created the moment you apply the dialog; there's no approval step waiting for you. Inspect their boundaries before you use them. Use the [markers and regions guide to name and adjust regions](https://soundforgepro.com/sound-forge-markers-regions/). When you need separate files, follow the [reviewed-region extraction workflow](https://soundforgepro.com/split-long-recording-into-tracks-sound-forge/). Creating regions and exporting separate files are separate steps. ## Troubleshoot the changed audio - **The first consonant is missing:** reopen the unprocessed test copy. Check whether the selection excluded it, whether detection started too late, or whether the fade softened an intact attack. Lower the attack threshold only if late detection is the cause. - **A tail ends abruptly:** try a lower release threshold on the source copy. If the kept edge is right but clicks, look at the fade instead. Trim by hand when the tail can't be separated from the noise. - **Too many small regions:** inspect internal pauses and minimum inter-phrase silence. A noise spike can also trigger an unwanted event, and duration settings alone won't fix every false detection. - **A quiet phrase disappears:** compare its level with the threshold and the background. Try a more suitable setting for that section, or mark it manually. - **Speech sounds rushed:** restore the pauses from the original. Phrase mode is inappropriate when the gap itself carries timing or room ambience. Continuous applause, changing wind, surface noise, overlapping dialogue, and long musical decays need editorial judgment. When reviewing automatic boundaries takes more work than placing them, use manual trimming. No automated region count replaces listening. ## Loop tails and fixed-length clips With **Remove data beyond loop points**, **Minimum length following loop end** is a count of **samples** kept after the loop. The help explains that some samplers don't use the exact supplied loop points, so check the intended sampler before assuming zero extra samples is safe. This setting has nothing to do with fade-out duration. **Remove data from start and limit file length** removes the specified opening portion and caps the converted file length. It can cut wanted sound as well as silence. The maximum is a ceiling; a shorter file won't be padded out to an exact duration. Check the start and end of every resulting clip. ## Reuse settings only on comparable sources A preset records settings. The editorial decisions are still yours. Before reusing one, try it on the quietest onset, loudest background, shortest intended gap and longest decay among the files. Split inconsistent recordings into separate groups or edit them one by one. Write down the function and the controls that matter for it. Keep output separate from the originals. The [Batch Converter guide](https://soundforgepro.com/how-to-batch-process-files-sound-forge-pro/) covers the larger multi-file workflow; a preset that worked on one take isn't automatically safe for an entire folder. Before delivery, listen to every exported boundary, verify the intended file order and region names, and reopen the saved files. Compare with the untouched source when a beginning, ending, or pause sounds wrong. ## Auto Trim/Crop FAQ ### Where is Auto Trim/Crop in Sound Forge? Open Process > Auto Trim/Crop. Choose the function first, then adjust the controls relevant to it. Check the selected audio and channels before applying a destructive operation. ### Why does Auto Trim/Crop cut off the first word? The selection may exclude it, the attack threshold may miss a quiet consonant, or a long fade may soften an intact onset. Return to the original test copy, identify the cause, and adjust selection, detection, or fade separately. ### Can Auto Trim/Crop split multiple takes? Remove silence between phrases (creates regions) deletes detected gaps and creates regions. It does not export separate files by itself. Review the regions before extraction; use Auto Region instead when the source gaps must remain. ### Should attack and release thresholds match? Not necessarily. Attack detects the start and release detects the end. Set each from the source's quietest wanted attack, decay, and background level rather than assuming one shared value. ### Does minimum inter-phrase silence preserve a pause? No. It sets the minimum silence required before a new region is created. Phrase mode deletes detected silence; the setting is not a retained-pause duration. ### Does Auto Trim/Crop replace a noise gate? No. Auto Trim/Crop removes data according to its selected function and can create regions. It is not continuous background attenuation inside retained phrases. Choose manual editing when deleting gaps would damage the recording's timing. Documentation checked September 14, 2026 against the Boris FX Sound Forge 2026 Auto Trim/Crop, Auto Region, and processing-dialog help. This is a documentation-led workflow, not a report of a newly performed Windows application or listening test. ### Sound Forge Markers and Regions: Navigate & Export URL: https://soundforgepro.com/sound-forge-markers-regions/ Last updated: 2026-09-30T21:29:13.000Z **Quick answer:** press **M** to place a marker at the cursor or during playback. Select a passage and press **R** to store it as a region, or **Ctrl+Alt+R** with the Event tool selected. Right-click the tag and choose **Rename**. To recall the complete region, right-click either boundary and choose **Select Region**. Save the metadata before closing the file. These instructions follow the Sound Forge 2026 documentation. A marker stores one position; a region stores a start and an end. Neither insertion cuts the audio. This guide covers those objects, their saved metadata, and the choice between separate extracted files and one playlist sequence. For recording, trimming, and other editing tasks, use the [Core Editing guides](https://soundforgepro.com/tag/core-editing/). ## Marker, selection, or region? | Object | What it stores | Use it for | Common mistake | | --------- | ----------------------------- | ----------------------------------------------- | --------------------------------------------- | | Marker | One time position | A note, navigation point, or future boundary | Expecting a point to contain an audio span | | Selection | The currently selected range | Auditioning or processing audio now | Clearing it before creating a reusable region | | Region | Named start and end positions | Recalling, auditioning, or extracting a passage | Assuming it is already a separate audio file | Use a marker for a note such as *Check chair squeak*, and a region for the whole passage that needs repair or delivery. Creating a region doesn't apply an effect, start loop playback or make a sampler loop. ## Insert, rename, and recall a passage 1. **Keep a working copy.** Preserve the original audio before editing or replacing metadata. 2. **Place a marker.** Position the cursor and choose Insert > Marker, or press M. You can also press M during playback. 3. **Name the point.** Right-click its tag, choose Rename, type a useful label, and press Enter. 4. **Create a region.** Select the complete passage and choose Insert > Region. The shortcut is R, or Ctrl+Alt+R when the Event tool is selected. 5. **Name and recall the region.** Rename its starting tag. Clear the selection, then right-click either region boundary and choose Select Region. 6. **Check both edges.** Audition the entrance and ending in context. Adjust the boundaries if they cut a wanted sound. 7. **Save and reopen.** Preserve the metadata when saving, keep any required sidecar or project folder, and reopen the working file to check the named range. The [current marker instructions](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/insert%5Fmarker.htm) describe inserting a marker and then renaming it, so pressing M won't necessarily open a naming dialog. A point dropped while listening needs checking: stop, zoom in and audition it instead of assuming the keypress landed on the intended sample. Double-click targets differ. [Double-click immediately to the right of a region tag](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/insert%5Fregion.htm) to edit its name. Double-click the start or end region marker itself to select its audio range. If you keep opening the name field when you want the audio, use the explicit right-click **Select Region** command. ## Use the Regions List for exact positions Open **View > Metadata > Regions List**. The list contains the markers and regions in the active data window. The [Regions List reference](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/regions%5Flist.htm) documents these controls: - Click the leftmost numbered column to move the cursor to a marker or select a region. - Click the Play button beside a region to audition it. - Type new values in Name, Start, End, or Length to edit a region. - Click a column heading to sort the displayed list. Sorting rows leaves the audio order exactly as it was. ![Sound Forge Regions List with row numbers, Play buttons and editable Name, Start, End and Length columns](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/09/sf-regions-list-name-start-end-length.webp) Type new values in the Name, Start, End or Length boxes to check exact marker and region positions. Give regions names that still make sense outside the editor: *01 Opening*, *02 Interview* or *Door\_close\_take03*. Before typing in times from a cue sheet, check the displayed time format so you don't mistake a sample count for seconds. ## Move a region without resizing it With length locking off, dragging one region tag changes that boundary and the duration. Hold **Alt** while dragging either tag to move the whole range at the same length. Hold **Shift** during the drag to override snapping. There's also a persistent **Options > Lock Loop/Region Length** setting. The [length-lock documentation](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/proonly/locking%5Floop%5Fand%5Fregion%5Flengths.htm) says it holds the length constant when you change a start or end time, so if both boundaries move when you only meant to resize one edge, check it. After a move, recall the region and listen again, because an unchanged duration doesn't mean the new position is useful. ## Save markers and regions without losing them In **File > Save As**, select **Save metadata with file**. For a Sound Forge project, use **File > Render As** to produce a media file. The [Save As/Render As reference](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/saving%5Fa%5Ffile%5Fas%5Fa%5Fdifferent%5Fname%5For%5Ftype.htm) includes markers, regions, and playlists among the metadata preserved by this checkbox. Clearing it tells the save operation to ignore that data. The manual lists internal metadata support for MP3, PCA, SFA, WAV, WAV64 and Windows Media formats. That doesn't mean another player will show Sound Forge regions as chapters. When the chosen format can't hold all the metadata, Sound Forge asks to create an external **.sfl** file with the media file's base name. Keep that sidecar with the audio and check the pair after you move them. ### Save a separate list or text record Choose **Edit > Regions List > Save As**, then select **Playlist File (.sfl)** to save the regions/playlist data separately. The same Save As command sits under Playlist/Cutlist as well. For a cue record people can read, choose **Text File (Tab delimited) (.txt)**; the [list-saving instructions](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/proonly/saving%5Fa%5Fregions%5Fplaylist%5Ffile.htm) explicitly support markers and regions in that format. None of these lists can stand in for the audio master. **Save the current list before importing another one.** Choose **Edit > Regions List > Open** to load a saved list into the current sound file. The [import warning](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/proonly/opening%5Fa%5Fregions%5Fplaylist%5Ffile.htm) is blunt: opening a new regions/playlist file clears the current regions and playlist entries instead of adding to them. Use the matching audio revision, then check names and positions. ### Keep an FRG project and its folder together For an editable project, choose **File > Save As > Sound Forge Pro Project File (\*.frg)**. Sound Forge creates the FRG file plus a companion **\[filename\]\_frg** folder holding media and temporary editing files, and the [project documentation](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/working%5Fwith%5Fprojects.htm) warns that deleting the folder breaks the project. Archive both, and remember an FRG can't be played as an audio export. If metadata disappears, first reopen the saved file in Sound Forge to tell missing data apart from another application simply not displaying it. Check the save checkbox, the output format and any SFL sidecar. A [2021 MAGIX forum report about lost track metadata](https://www.magix.info/us/forum/sound-forge-suddenly-not-saving-or-recognizing-tracks--1285849/) shows why the checkbox is worth checking first, though it isn't the whole story: the reporter said it was already on. Don't reset or reinstall the application before you've protected the current audio and list. ## Convert boundary markers into regions For consecutive deliverables, place a marker at the first start, every shared boundary, and the final end. Choose **Edit > Regions List > Markers to Regions**. The [conversion reference](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/proonly/converting%5Fmarkers%5Fto%5Fregions.htm) says it uses all existing markers and creates a region between each consecutive pair. Four distinct boundary markers therefore create three intervals. Save a separate list before removing note markers such as *Check noise*, since a naming prefix won't keep them out of the conversion. Review the resulting count and boundaries before extraction. Without a final closing marker, this conversion won't create the last wanted interval, so select that passage and make a region by hand instead of blindly converting the entire list again. The [long-recording split workflow](https://soundforgepro.com/split-long-recording-into-tracks-sound-forge/) covers track-specific decisions such as applause and continuous recordings. Here, keep the distinction simple: markers define points; the regions define the spans you can deliver. ## Extract regions as separate audio files Choose **Tools > Extract Regions**. In **Regions to extract**, select the wanted rows; Ctrl or Shift selects multiple regions. Choose a clean **Destination folder** and, if needed, a **File name prefix**. The [Extract Regions help](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/proonly/extract%5Fregions.htm) distinguishes two naming modes: - **Use long file names for destination file names** combines the prefix and region name. Number the region names themselves, for example 01 Opening and 02 Interview, when alphabetical ordering matters. - With that checkbox cleared, names follow the legacy 8.3 convention: the first five prefix characters plus a three-digit number starting at **Start file counter index**. That counter doesn't number long region names separately. Click **Extract**, then reopen the outputs and check the count, names, sample rate, bit depth, channel count and both edges. Don't expect this dialog to offer the same format/template controls as Save As. If the verified extracted masters need a delivery conversion, run the [Batch Converter workflow](https://soundforgepro.com/how-to-batch-process-files-sound-forge-pro/) on copies. ## Use a playlist for one rearranged sequence Separate extraction and playlist assembly do different jobs. To build one sequence, open **View > Metadata > Playlist**. Select a region in the Regions List and choose **Edit > Playlist/Cutlist > Add**, or drag it into the playlist window. The [playlist instructions](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/proonly/adding%5Fand%5Fremoving%5Fplaylist%5Fregions.htm) describe arranging regions without touching the source file, and removing an entry from that window leaves its source region and waveform alone. Audition the sequence with the Playlist/Cutlist window's Play button, then choose **Edit > Playlist/Cutlist > Convert to New**. The [Convert to New reference](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/proonly/creating%5Fa%5Fnew%5Ffile%5Ffrom%5Fa%5Fplaylist.htm) says the new sound file follows the sequence you heard in that window. It processes audio only and ignores any video stream. Save the resulting audio separately, because saving an SFL list alone won't deliver that audio sequence. ## Automatic regions are not automatic approval **Tools > Auto Region** can create regions from fast attacks or from musical intervals based on the current tempo. The [Auto Region reference](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/proonly/auto%5Fregion.htm) describes sensitivity, minimum level, minimum beat duration and optional release-point boundaries. Check the results against the actual sounds, since detection has no idea which takes you want to keep. That differs from **Process > Auto Trim/Crop**. Its **Remove silence between phrases (creates regions)** mode deletes detected silence inside the selection while creating regions, according to the [Auto Trim/Crop manual](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/proonly/auto%5Ftrim%5Fcrop.htm). Use a working copy and only choose that mode when removing gaps is intended. The [Auto Trim/Crop guide](https://soundforgepro.com/sound-forge-auto-trim-crop/) covers those destructive modes separately. ## Check boundaries before delivery Listen across each proposed start and end from outside the selected range, and keep the consonants, transients, breaths and decays you want. A small waveform can still be audible. If an exported edge clicks, look at the transition and adjust it, or add a suitable short fade on a copy; the [fade-in and fade-out guide](https://soundforgepro.com/fade-in-fade-out-sound-forge/) covers that step. For a continuous sequence, audition adjacent outputs together as well as one by one. Keep the original master, the saved marker/region list and the delivery files apart, and don't throw away the working metadata just because extraction finished. ## Sound Forge markers and regions FAQ ### Why does R not insert a region with the Event tool? Use Ctrl+Alt+R when the Event tool is selected, or choose Insert > Region after making the intended time selection. ### Why does double-clicking rename instead of select? Double-clicking to the right of a region tag edits its name. Double-clicking the start or end region marker selects the region. Right-click either boundary and choose Select Region if the click target is unclear. ### Can I import a saved list without replacing the current regions? The Regions List Open command clears the current regions and playlist entries when it loads another list. Save the existing list first; do not treat Open as an append command. ### Does saving MP3 always remove markers? No. The current Sound Forge manual lists MP3 among formats that support internal metadata. Select Save metadata with file and verify by reopening. A different player's inability to display those markers is a separate compatibility issue. ### Why is the last track missing after Markers to Regions? The command creates intervals between consecutive markers. Add a closing boundary at the end of the wanted audio, or select the final passage and create its region manually. ### Should I use Extract Regions or Convert to New? Use Tools > Extract Regions for separate files from selected regions. Use Edit > Playlist/Cutlist > Convert to New for one new audio file following the sequence heard in the Playlist/Cutlist window. *Documentation checked September 15, 2026\. Menu and format claims use the current Boris FX help; the historical forum is a troubleshooting signal, not a reproduced Windows test.* ### Split a Long Recording into Tracks in Sound Forge URL: https://soundforgepro.com/split-long-recording-into-tracks-sound-forge/ Last updated: 2026-10-09T21:06:33.000Z **Quick answer:** save a working copy, place a marker at each wanted track start plus one at the final end, then choose **Edit > Regions List > Markers to Regions**. Check and name the regions before using **Tools > Extract Regions**. Reopen the output files to check their boundaries, order and audio format. Keep the continuous original untouched. This workflow follows the Sound Forge Pro 2026 help. It turns concerts, LP sides, cassette transfers, DJ sets and interviews into separate files; separating instruments from a mix is a different job. The [Core Editing guides](https://soundforgepro.com/tag/core-editing/) cover recording and basic edits before this stage. ## Choose the splitting method before editing - **Concert, album or DJ set:** use manual boundaries so applause, quiet music and crossfades remain where you want them. - **Interview or lecture:** mark chapter changes and leave ordinary pauses alone. A hesitation isn't necessarily a new chapter. - **Repeated isolated sounds:** Auto Region can propose regions from attacks or tempo. Inspect them before extraction. - **Clips whose intervening silence must be deleted:** Auto Trim/Crop has a destructive phrase mode. Use a separate working copy. - **Fixed-length chunks:** place boundaries at the required times, then check whether exact duration or an intact word or musical phrase takes priority. There is no universal silence threshold for track detection. Vinyl noise, audience ambience and quiet passages can defeat a rule that works on another recording. ## The seven-step long-recording workflow 1. **Protect the source.** Save a separate working master and retain its marker metadata. 2. **Place all boundaries.** For three contiguous tracks, use four distinct markers, including the first start and final end. 3. **Review each split.** Listen before and after it, preserving attacks, breaths and tails. 4. **Convert markers to regions.** Remove unwanted note markers from the working copy first. 5. **Name and check regions.** Confirm count, order, start and end positions. 6. **Extract into a new folder.** Select only the approved regions and review filename settings. 7. **Reopen the results.** Check joins and file properties before converting or delivering them. ## Save audio and boundaries safely Keep an untouched original outside the output folder. Save a working copy under a different name in a suitable lossless format, keeping the source sample rate, channel count and precision unless you deliberately need a conversion. Saving a lossy source as WAV won't bring back information it has already lost. In [File > Save As](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/saving%5Fa%5Ffile%5Fas%5Fa%5Fdifferent%5Fname%5For%5Ftype.htm), select **Save metadata with file** to retain markers and regions. The help says unsupported metadata can be saved to an external `.sfl` file. Keep that sidecar with the audio and reopen the working file to confirm its boundaries survived. For an extra boundary backup, choose **Edit > Regions List > Save As**. The [regions-list saving instructions](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/proonly/saving%5Fa%5Fregions%5Fplaylist%5Ffile.htm) offer a Playlist File (`.sfl`) or tab-delimited text. A list isn't an audio backup, though. If you use a `.frg` project, keep both the project file and its matching `_frg` folder. The [project documentation](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/working%5Fwith%5Fprojects.htm) warns that deleting that folder breaks the project. And a project isn't a playable delivery file. Keep a cue sheet with titles, intended order and expected count. Finish any whole-recording speed or timing correction before you approve boundary positions. Don't apply cleanup just because you're splitting the file. If outer material needs to go, follow the [cut and trim workflow](https://soundforgepro.com/how-to-cut-and-trim-audio-in-sound-forge-pro/) on the copy. ## 1\. Place the complete marker set Position the cursor and choose **Insert > Marker**, or press **M** during playback. The [marker help](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/insert%5Fmarker.htm) documents both methods. A playback keypress gives you a rough location; zoom in and refine it afterward. To name a marker, right-click its tag and choose **Rename**. Include a marker at the first wanted start, one at every internal track boundary, and a final marker after the last wanted tail. The [Markers to Regions command](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/proonly/converting%5Fmarkers%5Fto%5Fregions.htm) creates intervals between consecutive markers: N markers produce N minus one regions. Three contiguous tracks therefore need four distinct boundary markers. **Every existing marker participates.** An old note such as “repair click here” can become an unwanted split. Save the original list, then remove irrelevant note markers from the working copy before conversion. Material before the first marker or after the last one is outside those intervals. ## 2\. Refine boundaries without damaging continuity Listen several seconds before and after each boundary. A first consonant, breath, pick noise or count-in can precede the tallest waveform peak. Leave the entrance intact, and decide whether applause or room tone belongs at the end of the previous track or the start of the next. For a continuous concert or crossfaded album, keep adjacent regions contiguous: the previous end and the next start should mark the same boundary. Don't add fades or silence to every split by default. A split on its own doesn't have to change the original sequence, but independent edge fades would. For files intended to start and stop independently, audition those edges separately. An abrupt transition to or from silence can click. A nearby zero crossing or short fade may help, but stereo channels need not cross zero together. Preserve timing in both channels. Use the [fade-in and fade-out guide](https://soundforgepro.com/fade-in-fade-out-sound-forge/) when an actual edge treatment is needed, keeping the unaltered continuous master for gapless use. Try consecutive exported files in the intended player or delivery system. Gaps or crossfades added by the player can change what you hear even when the source boundaries are right. Don't promise gapless playback on the strength of region placement alone. ## 3\. Convert, name and inspect regions Choose **Edit > Regions List > Markers to Regions**. Open **View > Metadata > Regions List** to inspect the result. The [Regions List reference](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/regions%5Flist.htm) documents editable **Name**, **Start**, **End** and **Length** cells, column sorting and a play button beside each region. ![Sound Forge Regions List with track names and Start, End and Length columns](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/09/sf-regions-list-name-start-end-length.webp) Check the Start, End and Length columns as well as the region names before you export tracks. Name regions with unique ordered labels such as *01 Opening*, *02 Main Set* and *03 Encore*. Use enough zero padding for the complete set: three digits for a project with 100 to 999 tracks. Sorting the list by name won't replace a check of the actual time order. Right-click a starting or ending region tag and choose **Select Region** to inspect that span. The [region instructions](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/insert%5Fregion.htm) also explain that dragging one region tag changes that region's size. After conversion, don't assume that moving one edge moves its neighbor; check both the preceding End and the following Start. For contiguous delivery, remove unintended gaps and overlaps. If you need only a few non-contiguous excerpts, select each wanted span and use **Insert > Region** instead. This avoids turning unwanted intervals into tracks. The [markers and regions reference](https://soundforgepro.com/sound-forge-markers-regions/) covers insertion shortcuts and region movement in more detail. ## 4\. Extract into a clean output folder Open **Tools > Extract Regions**. The [current extraction instructions](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/proonly/extract%5Fregions.htm) list these controls: - **Regions to extract:** select the approved regions. Ctrl or Shift selects several. - **Destination folder:** use a new folder for this revision, separate from the original and earlier exports. Check existing names before allowing any replacement. - **File name prefix:** review the actual contents. Clear an unwanted prefix rather than assuming it is empty. - **Use long file names for destination file names:** the documented filename combines the prefix and region name, up to 128 characters including spaces. - **Start file counter index:** this belongs to legacy 8.3 naming when long filenames are disabled. It isn't the track-number control for long names. Click **Extract**, then check the resulting count and names. The help gives WAV output examples and doesn't document a codec, sample-rate or bit-depth selector in this dialog, so extraction alone doesn't guarantee every delivery setting is right. Reopen one representative output and inspect its actual codec, sample rate, bit depth and channel count before completing delivery. If FLAC, MP3 or another format is required, use **File > Save As** on the extracted audio files, choosing the file type and Template or Custom settings, or follow the [audio conversion workflow](https://soundforgepro.com/how-to-convert-audio-files-sound-forge-pro/) for a batch. Keep the extracted masters and write converted copies elsewhere. Putting a region label in a filename doesn't embed artist, title or track-number tags. Check the delivered metadata in the receiving software. Historical [community questions about named and tagged exports](https://www.magix.info/us/forum/how-to-save-tracks-as-individually-named-and-tagged-audio-files--1285379/) show the difference, but their old script suggestions aren't a tested 2026 workflow. ## Auto Region is different from silence removal **Tools > Auto Region** creates regions based on fast attacks or the current tempo. Its [documented controls](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/proonly/auto%5Fregion.htm) include Attack sensitivity, Release sensitivity, Minimum level and Minimum beat duration. None of them can identify song titles or musical intent. **Use release point for end of region** can end a region when the sound level drops. That can exclude silence from exported regions without using a command that deletes the underlying audio. It can also omit quiet material you wanted. Review every proposed region, especially for continuous music. **Process > Auto Trim/Crop > Remove silence between phrases (creates regions)** really does delete detected silence inside the selection. The [Auto Trim/Crop help](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/proonly/auto%5Ftrim%5Fcrop.htm) separates this destructive mode from region detection. Attack and Release thresholds are levels rather than fade durations, and Minimum inter-phrase silence sets the qualifying gap. It doesn't decide how much pause is kept. Use that mode only when you actually want shorter gaps. Save a pre-process copy, confirm the selected span, and inspect the result. If it cuts wanted material, undo back to that saved state or reopen the pre-process copy before changing settings. Don't run the already-shortened result through it again in the hope of recovering deleted sound. The [Auto Trim/Crop guide](https://soundforgepro.com/sound-forge-auto-trim-crop/) covers its other modes. ## Check the delivered sequence Reopen every exported file. Listen to the first and last sections, and keep listening past any long reverb or applause tail. Check full files when the recording calls for it; an arbitrary ten-second sample can't vouch for the rest. - **Count and order:** match the cue sheet and check for missing, duplicate or empty files. - **Edges:** preserve the first attack and final tail; audition adjacent files in sequence. - **Duration:** for unchanged, contiguous regions, compare summed durations with the intended span, allowing for displayed rounding. If gaps were intentionally excluded or audio was processed, use that edited span instead. - **Format and tags:** verify codec, sample rate, precision, channels and required metadata in the actual outputs. - **Levels:** check for unexpected clipping or gain changes. Don't normalize every song on its own unless you mean to change the album's level relationships. Use the [loudness-meter workflow](https://soundforgepro.com/sound-forge-loudness-meters/) for deliberate level decisions. Keep the continuous master, boundary backup and approved extraction folder until delivery has been accepted. ## Split a long recording FAQ ### Why is the last track missing? Markers to Regions creates intervals between consecutive markers. Add a final closing marker or create the missing final region, then check its end before extracting. Also confirm that the region was selected in the extraction dialog. ### Can Sound Forge split songs automatically by silence? Auto Region can propose regions from level changes, but it does not understand song boundaries. Auto Trim/Crop's phrase mode deletes detected silence. Use manual boundaries for concerts, crossfades or quiet music whose continuity must remain intact. ### Do I need fades at every track boundary? No. Keep contiguous boundaries unchanged for a continuous sequence. Treat a standalone start or stop only when it needs an edge repair, and keep an unfaded master for gapless delivery. ### Does Extract Regions change the original? The command creates new files from regions. Protect the original with a separate working copy and output folder: earlier processing, saving over the source, or replacing an existing output can still lose wanted material. ### Can I choose MP3 or FLAC in Extract Regions? The current help documents WAV examples and region, folder and naming controls, not an output-codec selector. Convert approved extracted files with Save As or Batch Converter, then verify the format and metadata. ### Why do the filenames sort in the wrong order? Put zero-padded numbers in the region names before extraction and check the filename prefix. The legacy Start file counter index is not a numbering control for long filenames. *Documentation checked September 15, 2026\. This is a documentation-led workflow, not a report of a Windows application or acoustic test.* ### Sound Forge Wave Hammer: Compressor & Maximizer Guide URL: https://soundforgepro.com/sound-forge-wave-hammer/ Last updated: 2026-10-10T14:13:22.000Z **Quick answer:** Classic Wave Hammer and Wave Hammer 2.0 are different processors. Classic Wave Hammer sends one full-band signal through a Compressor and then a Volume Maximizer. Wave Hammer 2.0 splits dynamics across as many as four frequency bands. For the classic workflow, set and level-match compression first, add only the peak control the destination needs, render a new file, then verify that saved file with separate LUFS and true-peak meters. The similar names set two traps. First, if you open Wave Hammer 2.0 expecting the classic Compressor and Volume Maximizer tabs, you won't find them. Second, classic Wave Hammer isn't a button for hitting a file harder until it looks loud. Compression changes punch, density and envelope; maximizing raises level and restrains peaks. Set and judge those stages separately. The [current Boris FX Sound Forge 2026 documentation](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/proonly/wave%5Fhammer-overview.htm) describes classic Wave Hammer DirectX as a compressor followed by a volume maximizer. A separate [current Wave Hammer 2.0 help page](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/proonly/wave%20hammer%202.0.htm) says 2.0 edits dynamics in up to four independent frequency bands. This guide follows the classic effect because its two-stage controls do not transfer directly to 2.0. Documentation checked September 5, 2026\. Boris FX 2026 help confirms the two processor identities; its classic Wave Hammer page directs users to the dialog’s ? help for detailed controls. This guide follows the current and archived documentation. Spotify numbers below are destination-specific guidance. ## Wave Hammer and Wave Hammer 2.0 Are Different Treat them as separate tools. Classic Wave Hammer runs the Compressor first and the Volume Maximizer second; the table below describes that signal flow. Wave Hammer 2.0 is multiband. If the dialog shows crossover bands instead of the classic Compressor and Volume Maximizer sections, this guide doesn't match the effect you opened. | Stage | Main job | What to listen for | Typical failure | | ---------------- | ------------------------------------------- | ------------------------------------------ | ------------------------------------------ | | Compressor | Reduce dynamic range above a threshold | Punch, sustain, vocal consistency, pumping | Flat transients or audible level breathing | | Volume Maximizer | Raise level and control peaks at the output | Peak density, distortion, loss of impact | A loud but brittle or clipped render | Neither stage replaces measurement. Check the file before and after processing with [Sound Forge Statistics](https://soundforgepro.com/how-to-use-statistics-sound-forge-pro/) or the [LUFS and true-peak meters](https://soundforgepro.com/sound-forge-loudness-meters/). Keep the source and final reports so the comparison can be repeated. A waveform that looks full isn't proof the delivery is correct. ![Classic Wave Hammer full-band signal path compared with four-band Wave Hammer 2.0](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/10/choice-desktop-v20261005.webp) Classic Wave Hammer is full-band; Wave Hammer 2.0 splits dynamics across up to four bands. ## Preview Wave Hammer and Save a Processed Copy 1. Save a working copy: Keep the unprocessed source or master intact so every decision remains reversible. 2. Measure the source: Read the current peak, loudness, and dynamic behavior before deciding whether [compression or limiting](https://soundforgepro.com/compressor-vs-limiter/) is needed. 3. Open classic Wave Hammer: Choose it for its full-band Compressor and Volume Maximizer. Older Sony versions place it under Effects > Wave Hammer; check the installed help if your menu differs. Do not choose the multiband Wave Hammer 2.0 processor. 4. Set the Compressor first: Bypass the Volume Maximizer, then set threshold, ratio, attack, and release from representative loud and quiet passages. 5. Level-match bypass: Use compressor output gain to make the processed preview approximately as loud as bypass, then judge punch, breathing, low end, vocal position, and room movement. 6. Set the Volume Maximizer: Enable the maximizer only after compression passes the level-matched comparison. Set Threshold, a conservative sample-peak Output level, Release, and Longer look-ahead for the source; the rendered file still has to pass the destination's separate dBTP limit. 7. Render the final delivery: For a directly opened effect, select the intended range and channels, then click OK to process the working copy. For a whole-file master, clear the temporary audition selection first. If using the Plug-In Chainer, leave the intended effects enabled for saving. Save a new file in the required format instead of overwriting the source. 8. Verify the rendered file: Reopen the saved file and measure Integrated LUFS and True Peak in dBTP. The classic Output level control is not a substitute for this post-render check. The [Sound Forge Plug-In Chainer](https://soundforgepro.com/how-to-use-plug-in-chainer-sound-forge-pro/) is the safer place to work when Wave Hammer belongs to a larger chain because you can change order and bypass individual processors before rendering. Applying the effect directly commits processing to the working file; keep an unprocessed copy for comparison and later revisions. ## Set the Compressor from the Signal, Not a Recipe ![Threshold, ratio, attack and release audition logic for classic Wave Hammer compression](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/08/compressor-desktop.webp) Set the compressor from gain-reduction behavior and listening evidence, not copied control values. ### Threshold Threshold determines where compression begins. Lowering it doesn't just make the file louder; it makes more of the signal eligible for gain reduction. Start high, play the loudest representative section, and lower it until the gain-reduction meter only moves when the material needs control. For a stereo master, 1–3 dB of reduction on the loudest passages is a sensible audition range, not a rule. A spoken-word file may tolerate more consistent compression, while a transient-heavy mix can sound smaller after only 2 dB if the attack is too fast. ### Ratio Ratio controls how strongly levels above the threshold are reduced. Once the signal is above threshold and the compressor has settled, a 2:1 ratio means that a further 2 dB input rise produces roughly a 1 dB output rise. For mastering, 1.5:1 to 2:1 is a conservative audition range. For dialogue or an unruly single source, 3:1 or 4:1 may be appropriate, but only after listening to consonants, breaths, and room tone. ### Attack Attack decides how quickly the compressor reacts. A very fast attack catches peaks but can shave the front off drums, picked strings, and consonants. A slower attack lets the initial transient pass and controls the body that follows. On a full mix, start slowly enough to preserve the kick and snare, then shorten the time only if the peaks remain uncontrolled. ### Release Release determines how quickly compression relaxes. Too short, and the background and reverb can surge between hits; too long, and the next phrase arrives while the processor is still holding the level down. Listen through several musical bars or complete spoken sentences, because a loop of one loud hit can't reveal bad release timing. ### Output Gain, Auto Gain, and Smooth Saturation Output gain restores level after reduction. Use it to match the processed preview to bypass; winning the comparison by being louder proves nothing. For manual level matching, turn automatic gain compensation off first; otherwise changing compression can change the comparison level again. If you deliberately use auto-gain, recheck the matched level after every adjustment. The [Sony Sound Forge 7 manual, pages 198–199](https://manualzz.com/doc/3477138/sony-7.0-sound-forge-software-user-manual), documents the classic Auto gain compensate, Smooth saturation and look-ahead controls. It is historical documentation; use the installed effect’s ? help if a control name or behavior differs. Smooth saturation changes the character of heavy compression; it is not a true-peak safety check. Compare it at matched loudness. If transparent peak control is the goal, reduce excessive compression before adding coloration. ## How to Level-Match the Bypass ![Level-matched Wave Hammer bypass comparison for punch, breathing, low end and room](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/10/ab-desktop-v20261009.webp) Bypass the maximizer and match levels before deciding whether compression improves control. Human hearing is easily biased toward the louder version. If the processed side is 1 dB louder, it can appear clearer, wider, and more exciting even when the envelope is worse. A fair comparison needs approximately equal perceived loudness. 1. Preview the Compressor with the maximizer bypassed. 2. Use output gain to bring the processed signal close to the bypass level. 3. Switch bypass on and off during the same section. 4. Ignore loudness and judge the attack, low-end stability, vocal position, and room movement. 5. Reduce compression if the processed version loses impact or breathes audibly. Don’t chase a perfect LUFS match during every small move. A close meter match plus repeated listening at moderate monitoring level is enough to expose a preset that works only because it is louder. ## Set the Volume Maximizer Second Once compression is stable, enable the Volume Maximizer. Threshold here determines how much material is driven into peak control, and Output level sets the maximum sample-level output in dBFS terms. Release and Longer look-ahead change how that control behaves. Lowering Threshold makes the result denser, which isn't the same as better. The classic manual also warns that longer look-ahead can start attenuation before an attack. If a transient sounds softened before it arrives, compare with that option off instead of treating more look-ahead as automatically preferable. Choose a conservative Output level as a sample-peak control, but don't copy a destination's dBTP limit into that field and call the job finished. [Spotify's current loudness guidance](https://support.spotify.com/us/artists/article/loudness-normalization/) recommends keeping a -14 LUFS master below -1 dBTP and a louder master below -2 dBTP. Those recommendations are Spotify-specific; they aren't universal master settings. A displayed -1.0 dB Output level in classic Wave Hammer doesn't prove that the encoded delivery stays below -1 dBTP. Render the required delivery format, reopen it, and read Integrated LUFS and True Peak with a separate meter. For speech, the maximizer should catch occasional peaks rather than remain in heavy reduction. For music, listen to kick, snare, cymbals, and bass together. If the top end turns grainy or the low end makes the whole mix duck, raise Threshold or revise the compressor instead of pushing Output level harder. ![Classic Wave Hammer sample-peak output level followed by rendered-file LUFS and dBTP checks](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/08/verify-desktop-2.webp) The plug-in output level is a sample-peak control; a separate post-render true-peak meter decides dBTP compliance. ## Starting Settings for Music, Voice and Sound Effects | Source | Compressor starting point | Maximizer approach | Stop when | | ------------------- | ------------------------------------------------------------------------- | ---------------------------------------------------------- | -------------------------------------- | | Stereo music master | 1.5:1–2:1; slow enough attack to preserve transients; 1–3 dB reduction | Set a conservative sample-peak limit; verify rendered dBTP | Kick or snare loses impact | | Podcast or voice | 2.5:1–4:1; moderate attack and release; control phrases, not every breath | Catch occasional peaks after level balancing | Room tone pumps or consonants dull | | Sound effect | Choose attack from the transient you must keep | Use only if a hard output cap is required | The effect loses its intended contrast | These ranges are audition points. Threshold cannot be copied reliably from one file to another because source level changes where the compressor works. A threshold of -18 dB can be gentle on one recording and relentless on another. ## Wave Hammer for Mastering vs Voice On a stereo master, the processor affects everything at once. One bass hit can trigger gain reduction across the entire mix, so small moves matter. Correct frequency-balance problems before asking a broadband compressor to solve them. The [Sound Forge normalization guide](https://soundforgepro.com/how-to-normalize-audio-in-sound-forge-pro/) explains the other boundary: constant gain changes level without reshaping dynamics, but Sound Forge’s RMS Normalize can apply dynamic compression and Loudness Normalize includes dynamic limiting. Check those options before assuming normalization is gain-only. Wave Hammer gives direct compressor and maximizer controls for deliberate envelope changes. On voice, the goal is normally intelligibility and consistent phrases. Remove distracting clicks and large level jumps first, then use compression to narrow the difference between ordinary speech and louder words. The maximizer is the last guardrail rather than the primary leveling tool. The dedicated [Sound Forge podcast workflow](https://soundforgepro.com/sound-forge-pro-for-podcasters/) covers the rest of the chain. ## Presets, Reopening, and the Sound Forge 18 Behavior A preset stores a control state; it doesn't diagnose anything. Preview the loudest and quietest relevant passages before saving one. Name useful presets by job and source, such as “voice light control” or “stereo master 2 dB GR”, rather than “make loud.” A March 2026 [MAGIX community discussion about Wave Hammer in Sound Forge 18](https://www.magix.info/index.php/us/forum/wave-hammer-sound-forge-18--1352824/) documents a recall question and a qualified reply: an experienced user reported that Sound Forge Pro 17/18 and Audio Studio 17 return to the last saved preset, while older versions behaved differently. This is community evidence, not a Boris FX specification. Save a named preset and write the important settings into project notes instead of trusting a transient dialog state. ## Common Wave Hammer Mistakes - **Adjusting both stages together:** you cannot tell whether compression or limiting caused the damage. - **Comparing at different loudness:** the louder preview can seem better even when it sounds worse at matched level. - **Copying a threshold:** threshold depends on the source level. - **Using a fast attack by default:** transients disappear and the master feels smaller. - **Using a short release on bass-heavy material:** the file pumps between low-frequency hits. - **Trusting a preset name:** “Smooth Compression” or “Mastering” cannot know the source dynamics. - **Double limiting:** Wave Hammer maximization followed by another hard limiter can remove impact without providing useful extra loudness. - **Skipping the final render check:** codec conversion can change true-peak behavior. ## Wave Hammer FAQ ### Is Wave Hammer a compressor or a limiter? It is both in series. The first stage is a compressor; the second stage is a Volume Maximizer that limits sample peaks while raising the overall level. ### Should I use Wave Hammer or Normalize? Use Peak Normalize for a constant-gain peak change. RMS Normalize can apply compression when clipping would occur, and Loudness Normalize can limit dynamics, so neither is always gain-only. Choose Wave Hammer when you need its explicit threshold, ratio, attack, release and maximizer controls. Measure the rendered result whichever route you use. ### What ratio should I use for mastering? Start around 1.5:1 to 2:1 and listen for roughly 1–3 dB of reduction on loud passages. The correct value depends on the mix; preserving punch matters more than matching a number. ### What Output level should I use? Use Output level only as a conservative sample-peak setting. A destination's dBTP limit must be verified on the rendered file. Spotify currently recommends below -1 dBTP for a -14 LUFS master and below -2 dBTP for louder masters, but that is Spotify-specific guidance. Classic Wave Hammer's Output level is not a true-peak reading. ### Why does Wave Hammer make the audio pump? The threshold may be too low, the release may be too short, or low-frequency peaks may be driving excessive gain reduction. Raise the threshold, lengthen the release, and reduce the amount of compression while listening through complete phrases or bars. ### Should I use Wave Hammer 2.0 instead of the original? Do not treat 2.0 as a drop-in replacement. Use classic Wave Hammer for the single-band Compressor and Volume Maximizer workflow in this guide. Use Wave Hammer 2.0 when you specifically need multiband dynamics across up to four independent frequency bands and can manage the crossover decisions. ## Choose the Processor Before You Set It Keep the unprocessed source, a named processor preset and the final measurement report together. If the only improvement is extra loudness, return to the level-matched comparison before approving the render. A preset is useful only when you can explain which source problem it solves. ### Sound Forge Loudness Meter: LUFS, R128 & True Peak URL: https://soundforgepro.com/sound-forge-loudness-meters/ Last updated: 2026-10-11T09:54:04.000Z **Quick answer:** in the current layout, choose View > Channel Meters, right-click the meters, and select Loudness Meters in the display menu. If your workspace uses the separate meter window, choose View > Loudness Meters or press Alt+6\. For Channel Meters, choose the standard under Options > Preferences > Status. In the separate window, use Options > Loudness Meters or its right-click menu. Reset, then play the complete required program. M covers 400 ms, S covers three seconds, I accumulates Integrated loudness, LRA describes gated variation, and TP max catches reconstructed peaks. Judge delivery with I and TP max together. The destination sets the target. EBU R128 uses -23 LUFS for program loudness. The [current Sound Forge loudness help](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/loudness%20meter%20v2.htm) lists -23 LUFS and -1.0 for the EBU preset, and -24 LUFS/LKFS with TP max -2.0 for its ATSC preset. Spotify adjusts Normal playback to -14 LUFS, but that's platform behavior and mastering guidance rather than a universal rule for music, podcasts, or video. These are different specifications, and they don't swap for one another. This guide covers the live loudness meter and a complete playback check. For a static scan of a selection or file, the [Sound Forge Statistics guide](https://soundforgepro.com/how-to-use-statistics-sound-forge-pro/) is the better fit. If the reading is already known and the file needs correction, go straight to [peak, RMS, and loudness normalization](https://soundforgepro.com/how-to-normalize-audio-in-sound-forge-pro/). *Documentation checked September 7, 2026\. Sound Forge routes and menu labels were checked against the current Boris FX 2026 help; standards and platform claims were checked against ITU, EBU, ATSC, and Spotify primary sources.* ## LUFS and Peak Answer Different Questions A sample-peak meter reports the greatest absolute sample amplitude, positive or negative. It helps you watch for full-scale overloads, but cannot prove that a recording is undistorted: previously clipped audio can later be turned down. It also cannot tell you how loud a complete program feels. A sparse recording with one hard transient and a dense limited master can share a similar peak while sounding nothing alike. [LUFS describes program loudness](https://soundforgepro.com/lufs-meter/) using frequency weighting and time integration. The current published revision is [ITU-R BS.1770-5](https://www.itu.int/rec/R-REC-BS.1770-5-202311-I), approved in November 2023\. The BS.1770 family underlies EBU and ATSC recommendations, but the measurement method and gating required by the delivery specification still matter. [True peak answers a third question.](https://soundforgepro.com/true-peak-explained/) It estimates peaks that can appear between stored samples when digital audio is reconstructed or encoded. A WAV file may stay below 0 dBFS on an ordinary sample meter and still exceed a delivery ceiling in dBTP. That is why a loudness pass is not complete when Integrated LUFS alone lands on target. ✓ **The shortest useful rule:** sample peak checks stored-sample level, Integrated LUFS checks program loudness, and True Peak checks reconstruction headroom. Meters report these conditions; they do not prevent or repair clipping. ## How to Read M, S, I, LRA, and True Peak ![Momentary, short-term, integrated, loudness range and true-peak measurements explained](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/08/read-desktop.webp) M and S locate changes, I measures the full program, LRA describes gated variation, and TP catches reconstructed peaks. ### Momentary loudness (M) Momentary loudness uses a 400 ms window in EBU Mode. It moves fast enough to catch a word, a drum hit, an edit or a sudden level jump, but it's no instantaneous peak meter. Use it as a locator: it shows you where to listen. It won't tell you what number a whole file should hold. ### Short-term loudness (S) Short-term loudness uses a three-second window. It is usually the clearest meter for comparing a verse with a chorus, one narration sentence with the next, or adjoining sections recorded on different days. A change in S can reflect intentional phrasing or different content. Listen first; if the jump is unwanted, inspect mic distance, clip gain, edit boundaries and dynamics processing. ### Integrated loudness (I) For a full-program reading, make one uninterrupted pass from the required start to the end. Sound Forge’s integrated-meter help says restarting playback resets its values, and the separate-window help also describes recalculation on start, stop, seeking and direction changes. So previews and repeated choruses won't just pile up into one retained average. Reset explicitly before a controlled pass, and check its final values before you start another. ### Loudness Range (LRA) LRA is expressed in LU and summarizes the distribution of short-term loudness after absolute and relative gating. The [EBU Tech 3342 specification](https://tech.ebu.ch/docs/tech/tech3342.pdf) deliberately prevents one gunshot, a long silence, or the noise floor from defining the entire range. It is therefore inaccurate to describe LRA as simply “loudest minus quietest.” LRA is a diagnostic and editorial clue. It isn't a universal quality score. A news read, an audiobook chapter, a classical recording and a film mix shouldn't share one mandatory LRA, and the EBU itself warns against a single maximum value for every program. Ask whether the variation serves the material and the listening environment before you compress it. For clips shorter than a minute, EBU R128 doesn't recommend LRA at all, since there are too few three-second data points; use the short-form measures in the delivery brief instead. ### True Peak (TP max) TP max estimates the highest reconstructed peak during the pass. Delivery specifications call this dBTP, although Sound Forge help labels its true-peak display dB FS, so note that you used the true-peak field and not the ordinary sample meter. If Integrated loudness passes but TP fails, adjust output gain or the limiter setting, then measure both constraints again. Lowering gain can push Integrated loudness below its permitted range. Renaming a meter preset or changing the LUFS target won't make an inter-sample peak go away. ## Open the Loudness Meter in Sound Forge on Windows 1. Open the finished or nearly finished audio file. 2. For the current integrated view, choose View > Channel Meters, right-click the meters, and select Loudness Meters from the display menu. 3. For the separate meter window, choose View > Loudness Meters or press Alt+6. 4. Set the metering mode for the view you opened. Channel Meters uses Options > Preferences > Status; the help calls the standard selector Loudness Configuration on one page and Loudness Modus on another. The separate window uses Options > Loudness Meters or its right-click menu. 5. Choose EBU R128 or ATSC A/85 according to the delivery sheet. 6. Reset before the pass. Use Reset in the integrated display; in the separate window, use Reset Metering Engine. 7. Return to the required start and play the full program without skipping sections, pauses, credits, or the tail unless the specification excludes them. The [current Boris FX shortcut list](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/keyboard%5Fshortcuts.htm) assigns Alt+5 to Channel Meters and Alt+6 to the separate Loudness Meters window in the default keyboard setup. They are different views. The [integrated-meter help](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/loudness%20meter%20v2.htm) calls the Channel Meters version the improved current display, while the [separate-window help](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/loudness%5Fmeters.htm) remains available for that layout. These routes come from the documentation; nobody walked through a fresh installation to check them. The [Channel Meters help documents the right-click display menu](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/play%5Fmeters.htm). If your build or workspace looks different, the separate View > Loudness Meters window is documented too. ## The Sound Forge Display Trap: LU Is Not LUFS Sound Forge can show loudness relative to the selected target in **LU** or as an absolute value in **LUFS**. In relative mode, 0 LU means “at the target.” Under EBU R128 that's -23 LUFS; under the Sound Forge ATSC preset it's -24 LUFS/LKFS. A reading near 0 has nothing to do with 0 dBFS, and it isn't clipping. For screenshots, logs, and client handoff, absolute LUFS is harder to misread. Right-click the meter, inspect the range/display options, and enable the absolute display when you need the actual full-scale value. Use relative LU when riding a program around a known target. i **LU** is a difference. **LUFS** is an absolute loudness value. A move from -25 to -23 LUFS is +2 LU. ## EBU R128, ATSC A/85, and Streaming Targets The table below keeps standards and platform behavior apart. Don't read it as a list of interchangeable mastering presets. | Destination | Loudness reference | True peak | What the number means | | ------------------------------------ | --------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------- | | **EBU R128 v5.0** | \-23 LUFS program loudness | \-1 dBTP maximum for linear production audio; distribution can require a lower ceiling | Broadcast program normalization; use the broadcaster’s exact delivery sheet for tolerances and supplements. | | **Sound Forge ATSC preset** | \-24 LUFS/LKFS | TP max -2.0 in the current help | An application preset. Use the delivery sheet when its target or ceiling differs. | | **ATSC A/85:2026-07** | \-24 LKFS by default without metadata; long form is dialogue-anchored, short form uses full-program measurement | \-2 dBTP | Current television and streaming guidance. For streaming services without another agreement, Annex M recommends one service target from -23 to -27 LKFS. | | **Spotify Normal** | \-14 LUFS playback normalization | Spotify recommends below -1 dBTP at -14 LUFS, or below -2 dBTP for louder masters | Playback behavior and platform mastering advice, not a broadcast acceptance rule or a mandate for every music master. | | **Podcast, audiobook, social video** | Publisher-specific | Publisher-specific | Use the host, network, distributor, or client specification. “The internet uses -14 LUFS” is not a delivery document. | [EBU R128 version 5.0](https://tech.ebu.ch/files/live/sites/tech/files/shared/r/r128v5%5F0.pdf) remains centered on -23 LUFS, LRA, and Maximum True Peak. The current [ATSC A/85:2026-07](https://www.atsc.org/atsc-documents/a85-techniques-for-establishing-and-maintaining-audio-loudness-for-digital-television/) is more nuanced than the old one-line “-24 LKFS” summary. Its [Annex M quick reference](https://www.atsc.org/wp-content/uploads/2026/07/A85-2026-07-Annex-M.pdf) distinguishes dialogue-anchored long form, full-program short form, metadata workflows, and streaming services. LKFS and LUFS are numerically the same label here. A target of -24 LKFS doesn't shift by a unit just because another meter writes LUFS. ## A Full-Program LUFS Measurement You Can Trust ![Loudness delivery workflow from specification through final-file verification](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/08/workflow-desktop.webp) Read the delivery sheet, measure the full program, correct the failed constraint, and verify the rendered file. ![Two documented Sound Forge loudness meter routes with separate configuration and reset steps](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/10/routes-desktop-2-v20261005.webp) Use the integrated Channel Meters display or the separate Loudness Meters window, then configure, reset and play the full program. 1. **Read the delivery specification.** Record the loudness target, tolerance, true-peak ceiling, measurement anchor, channel layout, codec, and file format. 2. Choose the matching mode. Pick the specified method; a matching target number on its own isn't enough. The Sound Forge ATSC preset doesn't show A/85:2026 dialogue-gated compliance, so use a documented matching measurement path when one is required. 3. Check channel interpretation. For six-channel surround, check Options > Preferences > Status > Enable surround processing for files with 6 channels. The documented surround weighting affects the measurement and leaves the samples in the file alone. Confirm the intended channel order and LFE treatment with known material, and don't treat six unrelated channels as a surround mix. 4. **Reset the meter.** Clear Integrated, LRA, and held true-peak data from previews. 5. **Play the complete required program.** Include the opening, pauses, credits, and tail unless the delivery specification excludes them. 6. **Read I and TP first.** These values usually decide pass or fail. Use M, S, the history curve, and LRA to locate the cause. 7. **Correct the smallest real problem.** A gain move may be enough. If peaks block the loudness target, revise dynamics or limiting instead of normalizing repeatedly. 8. **Render the required file.** Use the final codec and settings, even if a temporary format would be more convenient. 9. **Measure the rendered file again.** Encoders can change peak behavior. The file you deliver is the file that must pass. For A/85:2026 long form containing dialogue, [Annex M specifies dialogue-gated BS.1770-1 measurement without the relative-level gate](https://www.atsc.org/wp-content/uploads/2026/07/A85-2026-07-Annex-M.pdf), over the complete composite mix. Short form uses full-program BS.1770-3 or later. Sound Forge’s published preset description doesn't show that dialogue detection is implemented, so use a meter or delivery path with documented support for the required method. Selecting a -24 target isn't enough. ## Diagnose the Failure Before You Process | Meter result | Likely issue | First move | | ------------------------------------ | ----------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------- | | I too low, TP has headroom | The program may have room for an overall gain increase | Check that the required gain fits the TP headroom; if it does, apply it and run another full pass. | | I too low, TP already at the ceiling | Transients or dynamics block a clean gain increase | Control the specific peaks or revise compression/limiting before adding gain. | | I passes, TP fails | Inter-sample or codec-sensitive peaks exceed the ceiling | Revise output gain or use a suitable true-peak limiter; verify both I and TP on the render. | | I passes, speech still jumps | Whole-program average hides section inconsistency | Use S and the history trace to find edits, mic changes, or clip-gain problems. | | LRA looks wide | Could be creative dynamics or inconsistent production | Listen in context; do not compress merely to reduce the number. | | Two meters disagree | Different reset periods, channel layouts, gating, or algorithm versions | Match start/stop points, mode, channels, and BS.1770 compliance before comparing. | If the file needs a final dynamics stage, [Wave Hammer](https://soundforgepro.com/sound-forge-wave-hammer/) can combine compression and limiting, but it should follow diagnosis rather than replace it. For a fuller single-file chain, use the [Sound Forge mastering walkthrough](https://soundforgepro.com/how-to-master-a-track-in-sound-forge-pro/). ## Generate a Loudness Log: Measure at the Right Point ![Rendered audio reopened and remeasured for integrated loudness and true peak](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/08/verify-desktop.webp) Measure the file you will send because encoding can change reconstructed peaks. Sound Forge can document a pass with Tools > Generate Loudness Log; [another current help page](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/proonly/loudness%20log.htm) calls it Create Loudness Log. With no selection it analyzes the whole file, and with a selection it reports that range. The log records the file, format, metering mode and loudness values, and it can travel with a master when its measurement method matches the recipient’s requirements. A log documents the measurement. It doesn't prove every delivery requirement has passed. For the whole-file report, clear any accidental partial selection first. There is an important codec detail in the Sound Forge manual: a loudness log requested during **Save As** is calculated after the plug-in chain but before codec encoding. Reopen and verify WAV delivery too: output format, quantization, dither or clipping can affect the saved samples. For MP3, AAC, or another compressed deliverable, open the saved file and generate the log afterward so the measurement includes any peak change introduced by encoding. For MP3 settings and verification, follow the [Sound Forge MP3 export guide](https://soundforgepro.com/how-to-export-mp3-from-sound-forge-pro/). Don’t approve the encoded file from the pre-codec meter alone: check the actual exported file rather than relying on a measurement taken earlier in the chain. ## Meter, Normalize, and Limiter Are Three Different Jobs The Loudness Meter measures; it never changes the audio. **Process → Normalize** can make a calculated gain or loudness-normalization move. A limiter controls peaks and changes dynamics when gain alone can't reach the target safely. Say a file measures -25 LUFS and -5 dBTP against a -23 LUFS / -1 dBTP delivery. A roughly 2 LU gain increase has enough headroom and may fix it without compression. If the same file measures -25 LUFS and -1.2 dBTP, adding 2 dB will break the peak limit, so the peaks or crest factor need attention before that gain increase. These are gain-only estimates (-5 + 2 = -3 dBTP; -1.2 + 2 = +0.8 dBTP) rather than measured results, and gating, dynamics and export can all move the final readings. Sound Forge’s loudness normalization can be useful for repeatable files, but always remeasure. On a folder job, build and test one representative file before applying the process through the [Sound Forge Batch Converter](https://soundforgepro.com/how-to-batch-process-files-sound-forge-pro/). ## Why -14 LUFS Is Not a Universal Mastering Target [Spotify currently states](https://support.spotify.com/us/artists/article/loudness-normalization/) that its Normal setting adjusts playback to -14 LUFS under ITU 1770\. It measures uploads and applies gain during playback, leaving the uploaded master as it is. Spotify says its web player and third-party devices such as TVs and speakers don't use loudness normalization. None of that means every music master should be forced to exactly -14 LUFS. Genre, crest factor, distortion, album continuity and the sound of the limiter still matter. A louder master may get turned down, and a quieter, highly dynamic master may not be raised all the way if true-peak headroom runs out. Listen for flattened transients or distortion as you set the limiter, and leave the encoding headroom the destination asks for. Hitting a number isn't worth making the master sound worse. For other destinations, compare the [streaming loudness reference](https://soundforgepro.com/streaming-loudness-standards/) with the actual publisher specification before choosing a target. Broadcast is different, because there the number can decide whether a program is accepted. “Spotify turns tracks down” is no argument for sending a -14 LUFS program to a broadcaster that asks for EBU R128 at -23 LUFS. ## LUFS Meter FAQ ### Where is the LUFS meter in Sound Forge? Choose View > Channel Meters, right-click the meters, and select Loudness Meters from the display menu. If your layout uses the separate window, choose View > Loudness Meters or press Alt+6\. Channel Meters uses the loudness settings under Options > Preferences > Status (called Loudness Configuration or Loudness Modus in the help); the separate window uses Options > Loudness Meters or its right-click menu. ### What is Integrated LUFS? Integrated loudness summarizes the measurement period using the selected method. For an EBU-style full-program result, reset and run one uninterrupted complete pass. A/85:2026 long-form dialogue measurement is different and needs its specified dialogue-gated path; a generic full-mix I value is not a substitute. ### What is the difference between LUFS and LKFS? For BS.1770-based program loudness, LUFS and LKFS are numerically synonymous labels. -24 LKFS and -24 LUFS describe the same loudness value. ### Should I choose EBU R128 or ATSC A/85? Follow the client’s specified method and target. EBU R128 uses -23 LUFS; Sound Forge’s ATSC preset uses -24 with a -2 true-peak ceiling. The preset name alone does not establish A/85:2026 compliance: long form with dialogue requires dialogue-gated measurement without the relative-level gate, rather than an ordinary full-mix average. ### What is a good LRA number? There is no universal good LRA. It depends on genre, program type, and listening environment. Use LRA to spot inappropriate variation, then listen before changing dynamics. EBU R128 does not recommend LRA for clips shorter than a minute; use the required short-form measurements instead. ### Why is True Peak higher than sample peak? True Peak estimates the reconstructed waveform between stored samples. Inter-sample peak magnitude can exceed the greatest absolute sample amplitude and may rise further after lossy encoding. ### Can Sound Forge create a loudness report? Yes. Use Tools > Generate Loudness Log, also called Create Loudness Log on another current help page, for a file or selection. For compressed delivery, generate the log from the saved encoded file because save-time logging occurs before the codec. ### Should I normalize every file to -14 LUFS? No. -14 LUFS is Spotify's Normal playback reference and mastering guidance, not a universal delivery target. Follow the destination specification and preserve sound quality. ### Sound Forge 2026 vs Pro 18: Upgrade and Migration URL: https://soundforgepro.com/sound-forge-2026-vs-pro-18/ Last updated: 2026-10-09T21:48:11.000Z **Short answer:** Sound Forge 2026 is a migration decision more than a conventional feature-count upgrade from Pro 18\. The official record clearly supports a new owner, new naming, Boris FX account and Hub access, local text-to-speech processing, Windows 11 support and a different Plus bundle. What it doesn't supply is a dedicated Sound Forge 2026 changelog proving a long list of editor improvements. Keep Pro 18 installed until the current trial passes the jobs, plug-ins and presets that earn money or protect an archive. This comparison belongs to our [Sound Forge comparisons hub](https://soundforgepro.com/tag/comparisons/). It focuses on an existing Pro 18 owner’s upgrade decision. The [current Sound Forge review](https://soundforgepro.com/sound-forge-pro-review-2026/) covers whether the editor fits a new buyer’s work. *Last fact-checked September 14, 2026\. Current product, system, licensing, pricing and transition claims were checked against Boris FX pages; Pro 18 claims were checked against documented 2024 launch material and an authorized regional reseller.* ## Sound Forge 2026 vs Pro 18 at a Glance The waveform editor remains recognizable on both sides. The parts most likely to break a migration happen around it: account ownership, Windows support, third-party entitlements and cloud-dependent services. | Area | Pro 18 | Sound Forge 2026 | | -------------------------- | ---------------------------------------------- | --------------------------------------------------------------------------- | | Original publisher | MAGIX (2024 release) | Boris FX | | Product name | Sound Forge Pro 18 / Pro 18 Suite | Sound Forge 2026 / Sound Forge Plus | | Account route | Original MAGIX registration | Boris FX account and Hub trial | | Text-to-speech | MAGIX Hub service | Processed locally on the current US product page | | Official Windows baseline | Windows 10 and 11 in the documented 2024 offer | Windows 11 | | Public delta documentation | Pro 18 launch and manual describe new features | No dedicated Sound Forge 2026 changelog found in the official pages checked | The current [Sound Forge feature matrix](https://www.soundforge.com/sound-forge/pricing/) still lists sample-level editing, peak and loudness metering, VST2, VST3 and ARA support, batch processing and event-based editing in both current tiers. Those are reasons to use Sound Forge, but the matrix doesn't label them as new since Pro 18. ## What Actually Changed in Sound Forge 2026 [Boris FX announced the acquisition on March 30, 2026](https://blog.borisfx.com/press/boris-fx-acquires-vegas-pro-sound-forge-and-acid-pro). The deal covered Sound Forge, VEGAS Pro and ACID Pro. The Sound Forge line moved from MAGIX's Pro and Pro Suite labels to Sound Forge 2026 and Sound Forge Plus. The [source-checked Sound Forge ownership timeline](https://soundforgepro.com/sound-forge-history/) separates this handover from the earlier Sonic Foundry, Sony and MAGIX eras. ### Ownership and support moved A current purchase now belongs to the Boris FX account and support system. That matters for activation, upgrade eligibility and future updates even when the editor itself looks familiar. It also means old MAGIX instructions and new Boris FX instructions can both be correct, each for a different license. ### Text-to-speech moved from Hub to local processing The [May 2024 Sourcenext release announcement](https://www.sourcenext.co.jp/pressrelease%5Fhtml/JS/2024/2024051601) describes Pro 18 text-to-speech and translation into up to 100 languages. Translation coverage doesn't tell you how many spoken voice languages there are. A [2025 MAGIX community troubleshooting thread](https://www.magix.info/us/forum/sound-forge-pro-18-magix-hub-text-to-speech-downloads-are-white-noise--1345312/) documents users generating speech through MAGIX Hub. That's historical workflow evidence, and it doesn't promise the legacy service or a purchased character balance still works today. The current Boris FX matrix says text-to-speech is processed locally and offers multiple languages and voices. It doesn't publish a side-by-side parity table for voice count, pronunciation, quality or old character allowances. Regional and license offers can also differ, so a buyer should check the exact cart and trial offered in the purchase country. ### Windows 11 became the supported baseline The [current Sound Forge requirements](https://www.soundforge.com/sound-forge/system-requirements/) list Windows 11 and recommend 8 GB RAM. The vendor’s 2 GB application line falls well short of a complete Windows 11 PC specification. The documented Japanese Pro 18 offer from May 2024 supported Windows 10 and 11, but its old hardware requirements won't help you buy a current workstation. Official support and technical possibility are different claims. The Windows 11 listing doesn't prove the current installer can never start on Windows 10; it does mean Boris FX isn't promising Windows 10 support. A stable Windows 10 production machine is a strong reason to leave Pro 18 intact. Our [Sound Forge system requirements guide](https://soundforgepro.com/sound-forge-pro-system-requirements/) adds practical RAM, storage and audio-driver checks. ## What the Official Pages Do Not Prove The checked Sound Forge site has an overview, a pricing matrix and system requirements. As of September 14, 2026, I couldn't find a dedicated Sound Forge 2026 \`What's New\` page or public changelog on those official routes, and that gap limits what any comparison can claim. None of that proves the application binary is identical to Pro 18, or that a specific crash, VST problem or editing delay has been fixed. The [MAGIX community discussion about Sound Forge’s future](https://www.magix.info/de/forum/is-this-the-end-of-sound-forge--1346009/) includes reports of a similar editor and individual fixes. Those are user reports; there's no controlled comparison or official release note behind them. If one bug is the whole reason for upgrading, turn it into a repeatable test: open the same file, load the same plug-in chain, perform the same edit and export the same target. A purchase page can't substitute for that result. ## Two Licenses, Two Account Systems Keep the two account records separate. The [official Sound Forge trial instructions](https://vfx.borisfx.com/sound-forge-trial) use Boris FX Hub and a Boris FX account, and they cover requesting and starting the trial. Entering a legacy Pro 18 serial isn't part of that process. Follow the instructions for your exact current purchase or trial instead of an old activation tutorial. Boris FX’s [MAGIX lifetime-license guidance](https://support.borisfx.com/hc/en-us/articles/44650605900301-What-happens-to-my-existing-lifetime-license-purchased-from-MAGIX) says the existing license stays valid under MAGIX. Its [registration-transfer guidance](https://support.borisfx.com/hc/en-us/articles/44650701122829-Will-my-previous-registrations-transfer-to-Boris-FX) says previous Sound Forge serials can show up in a Boris FX account that uses the original purchase email, which makes upgrade eligibility easier to check. An eligible old registration still isn't the same as owning the current version. Before you change hardware, keep the original order, serial, registered email and authorized installer. Confirm you can reach your legacy account and third-party licenses while the old workstation still works. If the upgrade offer doesn't recognize your purchase, ask Boris FX support to sort it out before you pay. ### A safe account sequence - Confirm access to the original Pro 18 account, order and authorized installer. - Use the same purchase email for the Boris FX account when possible, then confirm upgrade eligibility before paying. - Keep a recoverable Pro 18 setup. Try 2026 on copies of your work, and don't assume installation will carry over every preference or file association. - For the current trial, follow Boris FX Hub’s Request Trial and Start Free Trial instructions. A legacy serial procedure won't substitute for them. - Save a rendered reference file, presets and a list of third-party licenses before moving to a new workstation. For installation details, use our [Sound Forge installation guide](https://soundforgepro.com/how-to-install-sound-forge-pro/). This comparison can't vouch for side-by-side installation or automatic preset migration on your machine. ## Which Pro 18 Plug-ins Carry Over? This is where a vague \`upgrade\` label causes the most expensive mistakes. The old editor license can remain valid while a new purchase has a different bundle. Third-party products can also have separate accounts, installers and activation limits. The [May 2024 Sourcenext announcement](https://www.sourcenext.co.jp/pressrelease%5Fhtml/JS/2024/2024051601) lists Ozone 11 Elements and RX 10 Elements among the bundled products and names SpectraLayers Pro 10, Melodyne 5 Essential, Vandal and VariVerb II in its Suite offer. It marks 3D Reverb as Suite-only. That's one documented regional package, and it doesn't prove every retail or promotional Pro 18 order came with the same extras. The current Plus matrix names four extras: Melodyne 5 Essential, Vandal, VariVerb II and 3D Reverb. Ozone, RX and SpectraLayers aren't on it. The fair reading is that a current purchase doesn't promise those absent products. Saying the upgrade automatically wipes out licenses already attached to the older purchase would be wrong. | Tool | Pro 18 era | 2026 purchase | Migration action | | -------------------- | ------------------------------------------- | ---------------------------- | ------------------------------------------- | | Ozone 11 Elements | Documented with Pro 18-era release | Not listed in current matrix | Confirm original iZotope entitlement | | RX 10 Elements | Documented with Pro 18-era release | Not listed in current matrix | Keep installer, account and serial details | | SpectraLayers Pro | Present in documented regional Suite offers | Not listed in current matrix | Do not assume the new purchase replaces it | | Melodyne 5 Essential | Suite-only in documented launch offer | Included with Plus | Check Celemony activation before moving PCs | | Vandal / VariVerb II | Present in documented Suite offers | Included with Plus | Compare preset recall in the trial | | 3D Reverb | Suite-only in documented launch offer | Included with Plus | Test old projects and presets | Before changing machines, open the iZotope, Celemony and Steinberg accounts used for the original bundle. Record serials and installer versions, then export any presets that matter. If a client archive depends on one of these tools, render a reference master while the old system still works. For a deeper base-versus-Plus decision, use the [Sound Forge versus Sound Forge Plus comparison](https://soundforgepro.com/sound-forge-vs-sound-forge-plus/). Plus is a bundle choice; the current matrix doesn't advertise a faster waveform editor or a larger channel limit for the higher tier. ## Price, Upgrade & Support, and the 2026 Deadline The acquisition announcement listed US launch prices of $299.95 for a perpetual Sound Forge license and $399.95 for Plus. It listed Upgrade & Support prices of $189.95 and $249.95\. Boris FX also announced a simplified previous-version upgrade offer through December 5, 2026. Treat those as announced US prices rather than a guaranteed checkout total. Currency, tax, region and live promotions can change. Compare the [current Sound Forge pricing page](https://www.soundforge.com/sound-forge/pricing/) with the cart immediately before payment; our [current Sound Forge pricing guide](https://soundforgepro.com/sound-forge-pro-pricing/) explains perpetual, subscription and renewal choices without freezing a live promotion into the headline. Boris FX’s [general Upgrade & Support policy](https://support.borisfx.com/hc/en-us/articles/10334870429709-What-is-the-Upgrade-Support-Plan-What-is-U-S) describes a perpetual license that keeps working after its support contract expires, with a 12-month included term and automatic renewal. The policy’s introduction names other Boris products. Before buying Sound Forge, confirm the support term, renewal setting and any reinstatement charge in the offer you actually get. The March launch table isn't a personalized upgrade or renewal quote. ## Run a Real Migration Test Before Paying The [official trial page](https://vfx.borisfx.com/sound-forge-trial) offers a full-featured 15-day Windows trial with no credit card required. Prepare representative source files and reference exports before you start it. ### 1\. Audio interface and recording Select the production driver, set the sample rate and bit depth, record a short pass, stop, reopen and play it. Check channel assignment, meters, monitoring and the file written to disk. ### 2\. VST2, VST3 and ARA Record the plug-in version, format and authorization, then load the chain used in Pro 18\. Save project state where required, close it and reopen it. For ARA, test an FRG project rather than expecting a rendered WAV to retain editable analysis. Compare restored settings and the resulting audio; appearing in a menu is not sufficient. ### 3\. Scripts and batch jobs Run one script and one batch preset against copies of real files. Compare filenames, metadata, sample format, effect order and destination folders. Automation failures often appear after the editor itself seems fine. ### 4\. Pro 18 projects and file types Copy representative Pro 18 work before opening it in 2026\. The [current project documentation](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/working%5Fwith%5Fprojects.htm) says an FRG project has a companion `[filename]_frg` folder containing media and temporary files. Preserve both; deleting the folder breaks the project. Keep untouched originals and reference renders. The documentation does not promise backward compatibility for files resaved by a newer version. ### 5\. Text-to-speech Use names, numbers, abbreviations and mixed-language sentences from a real script. Compare pronunciation, pacing and exported WAV quality with the old Hub result if that service was part of the workflow. Don't infer parity from the word \`local\`. ### 6\. Export and preset recall For an FRG project, use **File > Render As** to create the delivery media. Check duration, channel order, peaks, loudness and required metadata, then reopen the saved file. Reload presets separately after restarting. Compare with a Pro 18 reference render; a null test needs matching alignment, level and deterministic processing. A difference alone does not prove either version is wrong. Our [official-trial guide](https://soundforgepro.com/sound-forge-pro-free-trial-whats-included-and-how-long-it-lasts/) covers the download and clock rules. The [Sound Forge installation guide](https://soundforgepro.com/how-to-install-sound-forge-pro/) handles Boris FX Hub and setup failures. Use those routes for installation; keep this page focused on the handoff decision. ## Upgrade, Keep Pro 18, or Test First? ### Upgrade now Upgrade when a supported Windows 11 setup, current Boris FX support, local text-to-speech or a license for a new workstation solves a specific problem. Choose Plus when one or more of its four named extras justifies the tier difference. ### Keep Pro 18 Keep Pro 18 when it's activated, stable and complete for the job. Boris FX says the MAGIX lifetime license remains valid, and a working production machine doesn't become obsolete because the current product adopted a year name. ### Test first Require the trial to decide when the purchase depends on an undocumented fix, a legacy plug-in, a script or exact preset recall. The absence of a dedicated changelog moves the burden of proof to the handoff test. If the editor itself is still an open question, read the [Pro 18 feature and value guide](https://soundforgepro.com/sound-forge-pro-18/) beside the current review. If the problem is a failed legacy activation rather than an upgrade decision, use the [Sound Forge activation troubleshooting guide](https://soundforgepro.com/sound-forge-activation-failed/). ## Sound Forge 2026 vs Pro 18 FAQ ### Is Sound Forge 2026 the same as Sound Forge Pro 19? No. Boris FX moved the product to year-based naming after acquiring Sound Forge from MAGIX. The current product is Sound Forge 2026, with Sound Forge Plus as the higher tier. No official Sound Forge Pro 19 release is documented. ### What changed from Sound Forge Pro 18 to Sound Forge 2026? The official sources document a new owner, new product names, Boris FX account and Hub access, local text-to-speech processing, a current Plus bundle and Windows 11 as the supported operating system. The official pages checked on September 14, 2026 did not provide a dedicated changelog of editor-engine changes against Pro 18. ### Does upgrading cancel my Sound Forge Pro 18 license? Boris FX says the existing MAGIX lifetime license remains valid under MAGIX. That does not itself grant a current 2026 purchase. Retain the original registration and confirm the exact upgrade entitlement before paying. ### Do Pro 18 plug-ins transfer to Sound Forge 2026? A new Sound Forge 2026 purchase promises the products in its current matrix. It does not promise Ozone, RX or SpectraLayers, which appeared in Pro 18-era offers. Check each original third-party account, serial and installer before changing machines. ### What does Sound Forge Plus add in 2026? The current matrix lists Melodyne 5 Essential, Vandal, VariVerb II and 3D Reverb as the four Plus extras. The listed core editor features are shared with the base Sound Forge tier. ### Does Sound Forge 2026 support Windows 10? The current official minimum requirements list Windows 11\. That statement defines the supported baseline; it does not prove that every installer build fails to open on Windows 10\. A production Windows 10 system should keep its working Pro 18 installation rather than depend on an unsupported setup. ### How long is the Sound Forge 2026 trial? The current product page offers a fully functional 15-day trial with no credit card required. Start it when a real job is ready so you can test the interface, plug-ins, scripts, projects, text-to-speech, exports and presets. ### Is the Sound Forge 2026 upgrade worth it? Upgrade when Windows 11 support, current Boris FX support, local text-to-speech or a new workstation solves a real problem. Keep Pro 18 when it is stable and complete. If the decision depends on a bug fix or a legacy plug-in, require the 15-day trial to prove that exact handoff. ### Sound Forge History: Owners and Versions, 1992-2026 URL: https://soundforgepro.com/sound-forge-history/ Last updated: 2026-09-30T21:29:40.000Z **Sound Forge began as a $25 shareware editor in 1992, according to a contemporary Forbes profile.** Sonic Foundry built it, Sony bought the desktop-software business in 2003, MAGIX took over the product line in 2016, and Boris FX announced its acquisition in March 2026\. Those four names explain the logos on old installers, but they don't make licenses, operating-system support or bundled extras interchangeable. The dates need care. A product's early sale, a company's incorporation, an acquisition announcement and a completed transaction are different events. This timeline distinguishes them and separates Sound Forge's Windows Pro releases from its Mac and Audio Studio branches. *Historical sources and current product information checked September 17, 2026\. Old prices and platform descriptions below refer to their stated periods, not current offers or compatibility guarantees.* ## Sound Forge Ownership in One Minute The ownership path runs Sonic Foundry, Sony, MAGIX, then Boris FX. Sony bought the desktop-software assets; it never bought Sonic Foundry as a whole company. MAGIX's later purchase covered several Sony Creative Software products, though not every Sony software business. ![Sound Forge ownership timeline: Sonic Foundry, Sony in 2003, MAGIX in 2016 and Boris FX in 2026](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/08/ownership-desktop.webp) The four product-owner eras. The 1992 starting point follows Forbes's account of early shareware sales; precise transaction dates are distinguished below. | Period | Owner | What changed | | ----------------------------- | ------------- | ------------------------------------------------------------------------------------------------------------------- | | 1992-2003 | Sonic Foundry | Developed the early editor and the Windows line through Sound Forge 6. | | 2003-2016 | Sony | Acquired the desktop-software business and released Sound Forge 7 through Pro 11. | | 2016-2026 | MAGIX | Acquired the product family, updated the Mac and Audio Studio branches, and released Windows Pro 12 through Pro 18. | | 2026, as checked September 17 | Boris FX | Acquired Sound Forge alongside VEGAS Pro and ACID Pro. The current product uses the Sound Forge 2026 name. | If you need today's buying and setup information rather than the backstory, the [Start Here buying and setup hub](https://soundforgepro.com/tag/start-here/) links to the current review, trial, requirements and pricing. ## 1992 or 1993? The Origin Date Needs Context The [November 1998 Forbes profile of Sonic Foundry](https://www.forbes.com/1998/11/25/feat.html) says Monty R. Schmidt developed an early Sound Forge in 1992 and began selling it as $25 shareware later that year. The same account says Curtis J. Palmer became his partner and chief technology officer, and that Sonic Foundry was formally incorporated in 1994. That backs 1992 as an early development and sales date. It doesn't pin down an exact launch day or a version number for that build, and the $25 figure belongs to that early shareware offer, not to any current Sound Forge license. Later coverage also uses 1993\. [ProVideo Coalition's 2018 report on the 25th anniversary](https://www.provideocoalition.com/acid-pro-and-sound-forge-pro-updated/), for example, dates the product's beginning to 1993, so the sources disagree on the starting year. We haven't found evidence that 1993 specifically marked a separate, broader commercial launch, and that explanation shouldn't be presented as fact. ### Company founding and product release are separate dates [Sony's 2003 announcement](https://sony.mediaroom.com/2003-07-31-Sony-Pictures-Digital-Acquires-Sonic-Foundrys-Desktop-Software-Assets) describes Sonic Foundry as founded in 1991\. Forbes gives 1994 for formal incorporation. These sources describe different events; neither date should replace the documented 1992 shareware account. This article uses 1992 for the early product and attributes the disputed dates rather than inventing a single definitive birthday. ## The Sonic Foundry Era: 1992-2003 Sound Forge's early workflow centered on an audio file: select part of a waveform, edit or process it, then save the result. The program's expansion is visible in period reviews, without needing to call it the first or best audio editor. Martin Walker's [March 1997 review of Sound Forge 4 and its plug-ins](https://www.soundonsound.com/techniques/sonic-foundry-sound-forge-4) covers the 4.0a update, real-time plug-in previews and the separate noise-reduction, spectrum-analysis and batch-conversion tools. It describes the software and paid options of that period. Don't treat it as a current shopping list or a Windows 11 installation guide. The [September 2002 review of Sound Forge 6](https://www.soundonsound.com/reviews/sonic-foundry-sound-forge-6) documents non-destructive editing, background rendering, improved DirectX plug-in management and support for files in up to 64-bit floating-point format. It reports that cut, paste and delete operations no longer required an immediate rewrite of the whole file. Saving the final edited file still did. **64-bit audio files are not the same as a native 64-bit Windows application.** The Sound Forge 6 review shows file-format support; it doesn't prove every internal calculation or plug-in ran at 64-bit precision. The later Pro 12 milestone is about program architecture. Keeping those two claims apart avoids a misleading sixteen-year contradiction. ## Sony Buys the Desktop Software: 2003-2016 Sonic Foundry's [transaction filing with the SEC](https://www.sec.gov/Archives/edgar/data/1029744/000119312503030746/d8k.htm) states that the desktop-software sale closed on **July 30, 2003**. The buyer was SP Software Acquisition Company, a wholly owned subsidiary of Sony Pictures Digital. Sony's public announcement is dated **July 31, 2003**, and that announcement date shouldn't stand in for the completion date. The final consideration was **$19 million in cash, other consideration and specified assumed obligations**. That bought the desktop-software business, including Sound Forge, ACID and Vegas, rather than Sound Forge alone. Sony's announcement also says approximately 70 former Sonic Foundry employees would work for its Madison operation while Sonic Foundry continued its separate communications business. Why do some histories say $18 million? [Mix's May 5, 2003 report](https://www.mixonline.com/recording/sony-buys-sonic-foundrys-desktop-software-assets-373033) described the proposed agreement at that amount, before closing. The proposal and completed transaction are different records. The final filing supports $19 million; the earlier reporting need not be dismissed as a simple arithmetic error. [Sony's Sound Forge 7 announcement, reprinted by Videomaker](https://www.videomaker.com/videonews/2003/10/sony-pictures-digital-networks-ships-sound-forge-7/), documents its 2003 availability and identifies it as Sony's first new professional software release after the acquisition. Version 8 was announced in [January 2005](https://www.kvraudio.com/news/sony%5Fannounces%5Fsound%5Fforge%5F8%5F2903); version 9 was available in [April 2007](https://www.synthtopia.com/content/2007/04/22/sound-forge-9/); and [Sound Forge Pro 10 followed in September 2009](https://www.kvraudio.com/news/sony%5Fcreative%5Fsoftware%5Freleases%5Fsound%5Fforge%5Fpro%5F10%5F12343). [Sony's July 22, 2013 launch material, reproduced by MusicRadar](https://www.musicradar.com/news/tech/sony-creative-software-unveils-sound-forge-pro-11-and-spectralayers-pro-2-580669), confirms that Pro 11 was available as a digital download, with physical products due in August. Pro 11 was the last major Windows Pro version before MAGIX brought out Pro 12 in 2018\. That doesn't mean every patch, Mac release or Audio Studio update stopped in 2013. ## The MAGIX Era: 2016-2026 Sony's [May 20, 2016 sale notice](https://web.archive.org/web/20250324233349/https://www.sonycreativesoftware.com/news/pressreleases/2016/sony-creative-software-sell-products-to-magix) says most of its creative-software products had been sold to MAGIX as of that date, with Sony keeping Catalyst Browse and Catalyst Production Suite. MAGIX's [takeover FAQ](https://www.magix.com/int/magazine/common/sony-product-takeover/) separately dates its official confirmation to May 24\. Those are two announcements about one handover. Sound Forge didn't change hands twice. The acquired Sound Forge family included Pro, Pro Mac and Audio Studio. MAGIX's [2018 product-family recap](https://www.magix.com/us/magazine/music/brand-new-sound-forge-pro-12/) identifies three separate releases: Pro Mac 3 on May 15, 2017; Audio Studio 12 that August; and Windows Pro 12 on April 4, 2018\. The recap itself was published April 9, so its page date is not Pro 12's launch date. Pro 12 brought a native 64-bit Windows Pro edition and VST3 support. Its [original user manual](https://shared.fastly.steamstatic.com/store%5Fitem%5Fassets/steam/apps/821770/manuals/manual%5Fsoundforgepro12%5Fen.pdf) lists a “64bit program version” among the new features. MAGIX's wording about first-time 64-bit operating-system compatibility is best read in that architectural sense; it doesn't prove older 32-bit releases could never run on a 64-bit Windows system. It also wasn't the first 64-bit edition across every Mac and Audio Studio branch. MAGIX then continued the numbered Windows Pro line. Its [official press archive](https://www.magix.com/us/press/) dates the Pro 13 release announcement to April 15, 2019 and the Pro 18 announcement to March 25, 2024\. Pro 18 was the last numbered MAGIX Pro release before the 2026 handover. For changes relevant to an existing installation, use the [Pro 18 to Sound Forge 2026 migration comparison](https://soundforgepro.com/sound-forge-2026-vs-pro-18/) rather than assuming a new owner means a completely rewritten editor. ## The Boris FX Era: 2026 to the Present [Boris FX announced the acquisition on March 30, 2026](https://blog.borisfx.com/press/boris-fx-acquires-vegas-pro-sound-forge-and-acid-pro). It named Sound Forge, VEGAS Pro and ACID Pro as the products bought from MAGIX and said their development teams in Madison and Germany would stay with the organization. That's the announcement date; the release doesn't give a separate legal closing date. As checked September 17, the official product page calls the editor [Sound Forge 2026](https://www.soundforge.com/sound-forge/). Boris FX's launch announcement also names Sound Forge Plus, with extra bundled applications and plug-ins, which moves the naming away from the old Pro 18 sequence. Owning another audio product doesn't, on its own terms, put that product in your Sound Forge license. The current vendor description still centers on working with a single audio file, multichannel files included, instead of arranging a multitrack DAW session. It advertises recording up to 32 audio channels. Channel count and independent timeline tracks are different ideas, so that number doesn't turn Sound Forge into a DAW. ## Major Sound Forge Versions and Turning Points This is a selective release timeline. It isn't a build-by-build changelog. Dates marked as announcements or reviews show the evidence available, so don't read them as exact release days. | Year | Milestone | Documented change | | --------------------------- | --------------------------- | ----------------------------------------------------------------------------------------------------- | | 1992 | Early Sound Forge | Forbes later reported development and $25 shareware sales in this year. | | 1997 review | Sound Forge 4.0a | Sound On Sound documented real-time plug-in previews and separate processing tools. | | 2002 | Sound Forge 6 | Period review documented non-destructive editing, background rendering and 64-bit float file support. | | 2003 | Sound Forge 7 | Sony's announcement confirmed availability after the asset acquisition. | | 2005 / 2007 / 2009 | 8 / 9 / Pro 10 | Successive Sony-era announcements; Pro 10 used the Pro name. | | July 22, 2013 | Pro 11 | Digital download available; physical products followed later. | | 2017 | Pro Mac 3 / Audio Studio 12 | Separate Mac and Audio Studio releases, not Windows Pro 12. | | April 4, 2018 | Pro 12 | Native 64-bit Windows Pro edition and VST3 support. | | April 15, 2019 announcement | Pro 13 | MAGIX continued the numbered Windows Pro line. | | March 25, 2024 announcement | Pro 18 | The last numbered MAGIX Pro release before the Boris FX handover. | | 2026 | Sound Forge 2026 | Boris FX ownership and year-based product naming. | ## Where Your Sound Forge License Lives Now Start with the exact product, version and purchase receipt. A Sony logo, a MAGIX serial and a Boris FX account belong to different generations. Don't delete a working legacy installation or buy an upgrade until the installer, purchase details and relevant presets are stored somewhere safe. For MAGIX-era purchases, the [MAGIX Service Center](https://www.magix.com/us/support/my-service-center/) is where the account starts. MAGIX's [technical-support guidance](https://www.magix.com/us/support/technical-support/) describes serial-number and email-based activation, with conditions that vary by product. A registered license doesn't promise an old build, driver or plug-in will work on your new computer. For current purchases, start at the official Sound Forge website and use the purchase account and instructions that came with that edition. For a bundled copy, check the host product and the exact included Sound Forge version. A legacy MAGIX bundle and a current Boris FX bundle don't share one universal activation procedure. Our [version-specific activation troubleshooting guide](https://soundforgepro.com/sound-forge-activation-failed/) separates those cases, and vendor support should confirm the entitlement before you touch a working setup. The [current Sound Forge system requirements](https://www.soundforge.com/sound-forge/system-requirements/) list Windows 11\. Pro Mac 3's 2017 release belongs to a separate historical branch and isn't a native macOS edition of Sound Forge 2026\. The [Sound Forge for Mac guide](https://soundforgepro.com/sound-forge-for-mac/) explains the current platform choices. ## What Changed, and What Stayed the Same The owner and version tell you which documentation to consult. File-format support, plug-in architecture, operating-system requirements and license management need separate checks. An old tutorial can explain a useful edit while giving the wrong installation instructions for today's release. Use this history to identify the generation, then make the present-day decision with the [current editions and pricing guide](https://soundforgepro.com/sound-forge-pro-pricing/). If your question is whether the smaller Audio Studio product was the same application, the [Audio Studio and Sound Forge comparison](https://soundforgepro.com/sound-forge-audio-studio-vs-sound-forge-2026/) covers that separate branch. ## Sound Forge History FAQ ### Who created Sound Forge? Monty R. Schmidt developed the early editor. Forbes's November 1998 profile says he built and sold it as $25 shareware in 1992, later partnered with Curtis J. Palmer, and formally incorporated Sonic Foundry in 1994. ### Was Sound Forge released in 1992 or 1993? Forbes reported early development and sales in 1992\. Later anniversary coverage uses 1993\. This history follows the 1992 shareware account but does not claim a verified explanation for the discrepancy or an exact first-release day. ### Who owns Sound Forge now? Boris FX owns Sound Forge as of September 17, 2026\. It announced the acquisition of Sound Forge, VEGAS Pro and ACID Pro from MAGIX on March 30, 2026\. The current product is named Sound Forge 2026. ### Is Sound Forge still made by Sony? No. Sony acquired the desktop-software business in 2003 and sold the Sound Forge product family to MAGIX in 2016\. Boris FX announced its acquisition from MAGIX in 2026\. Sony-branded installers and tutorials belong to the older generation. ### How much did Sony pay for Sound Forge? The completed desktop-software transaction involved $19 million in cash, other consideration and assumed obligations. It included Sound Forge, ACID, Vegas and related assets, not Sound Forge alone. The SEC filing gives July 30, 2003 as completion; Sony's announcement is dated July 31. ### What was the last Sony Sound Forge version? Pro 11, available digitally on July 22, 2013, was the last major Windows Pro version before the MAGIX Pro 12 release on April 4, 2018\. The Mac and Audio Studio branches had separate version histories. ### Does current Sound Forge run on Mac? There is no native macOS edition of Sound Forge 2026 in the current product requirements, which list Windows 11\. Pro Mac 3 was a separate historical release in 2017; its existence does not establish current Mac compatibility. ### Do old Sound Forge licenses still work? Check the exact version and purchase route. MAGIX maintains its Service Center for registered products, but activation conditions and operating-system compatibility depend on the release. An ownership change is not proof of entitlement to a newer edition; confirm that entitlement with the vendor before buying or replacing an installation. ### Repair Clipped Audio in Sound Forge: DeClipper Guide URL: https://soundforgepro.com/fix-clipped-audio-sound-forge/ Last updated: 2026-10-09T21:04:26.000Z **Quick answer:** diagnose the overload before choosing a repair. Repeated flat tops support a hard-digital-clipping diagnosis; analog overload can be rounded and requires a separate, cautious listening test. If the source is genuine 32-bit float, lower gain on a copy first; compatible recorder data may reveal an intact curve with no DeClipper required. If repeated flat tops remain, use Tools → Detect Clipping in Sound Forge, select one representative event, then preview Effects → DeClipper with Clip level just below the plateau. Keep the repair only when it sounds less distracting at matched loudness and leaves attacks intact. A declipper can't retrieve the exact samples that were discarded; it estimates a plausible curve from the audio around each damaged interval. Brief clipped syllables and isolated transients may become unobtrusive. A microphone capsule, transmitter, preamp, tape stage, or converter that overloaded for an entire phrase can remain distorted after the displayed peak looks rounded. The useful question is whether enough trustworthy context remains for a conservative estimate. This page repairs distortion already printed into an audio file. If playback or microphone monitoring crackles only inside Windows while the same file is clean elsewhere, start with the [Windows and Sound Forge distortion checks](https://soundforgepro.com/fix-distorted-audio/). A silent output belongs in the [Sound Forge no-sound checklist](https://soundforgepro.com/sound-forge-pro-no-sound/), while a source that never reaches the file needs the [recording-input troubleshooting route](https://soundforgepro.com/sound-forge-pro-not-recording-audio/). For isolated clicks, use the [click-and-pop repair workflow](https://soundforgepro.com/how-to-remove-clicks-pops-sound-forge-pro/). If noise remains after declipping, continue with the [hiss and hum guide](https://soundforgepro.com/remove-hiss-hum-sound-forge/). *Last fact-checked September 15, 2026\. Menu paths refer to current Boris FX Sound Forge Pro 2026 documentation; recorder-specific 32-bit float claims apply only when the cited recording chain preserved the over-range data.* This is a documentation-based review, not a claim of a recorded comparison test. ## Can a Clipped Recording Be Repaired? Sometimes. A recoverable event has a short damaged span with trustworthy audio immediately before and after it. The processor can estimate the missing curvature and timing from that context. Recovery becomes less credible as the plateau grows, the distortion begins earlier in the analog chain, or the same overload repeats through most of the program. | Damage | Typical evidence | Repair outlook | First move | | ---------------------------- | --------------------------------------------------------------------------- | ------------------------------------------------------------------------------------- | --------------------------------------------- | | **32-bit float over-range** | Meter or playback clips, but stored peak shape returns after gain reduction | May be recoverable when the stored over-range data and upstream stages remained clean | Lower gain; no declipper | | **Short hard clip** | A few flat-topped samples on a syllable or transient | Worth a selected test; no guaranteed recovery | Selected DeClipper test | | **Long hard clip** | Wide plateaus across words, notes or choruses | Damage control; original is unknown | Conservative declip, replacement or re-record | | **Analog/hardware overload** | Harsh or compressed sound without a clean fixed digital ceiling | May become less distracting; do not promise clean recovery | Diagnose the overloaded stage | | **Intentional limiter** | Repeated controlled peaks with no unwanted crunch | May not need repair | Check intent and delivery, not shape alone | | **Codec distortion** | Swirl, pre-echo or brittle transients without repeated sample plateaus | DeClipper is the wrong tool | Find the lossless source | ✓ **Best candidate:** a short, audible flat-top event with clean samples on both sides. **Worst candidate:** sustained upstream overload with no trustworthy shape left to estimate. ## Diagnose the Clipping Type Before Processing ![Four waveform patterns separating float headroom hard clipping analog overload and intentional limiting](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/08/diagnosis-desktop.webp) A plateau can mean lost samples, but analog overload, limiting, and intact 32-bit float headroom need different decisions. ### Hard digital clipping Hard digital clipping can leave several consecutive samples sitting at the same positive or negative ceiling, and at close zoom that shows up as a horizontal shelf. The [Audacity Clip Fix manual](https://www.audacityteam.org/manual/effects/noise-removal-and-repair/clip-fix/) describes the same repair limit: interpolation estimates a peak from the surrounding audio and works best on short, lightly clipped sections. Confirm you can actually hear unwanted distortion, not just see the shape. An intentional waveform or a heavily limited master isn't automatically something to repair. ### Analog or hardware overload A microphone capsule, transmitter, preamp, analog mixer or converter input can distort before the file reaches 0 dBFS. The recorded peak may sit below zero and look rounded, asymmetrical or compressed rather than perfectly flat. A loud source can overload the microphone or hardware input even when the finished file has been turned down, and lowering that file can't undo the earlier stage. ### Intentional limiting A brickwall limiter creates dense, repeatable peak shapes on purpose. If the master sounds clean and meets its delivery specification, redrawing those peaks can soften attacks and change the mix. Look at a known unprocessed source if you have one and trust your ears; a flat-looking overview won't tell you enough. ### True-peak overs A true peak above a delivery ceiling estimates the reconstructed waveform between stored samples; it doesn't prove those stored samples were cut flat. Use true-peak measurement for export safety and Detect Clipping for repeated plateaus. The [Sound Forge Statistics guide](https://soundforgepro.com/how-to-use-statistics-sound-forge-pro/) covers peak measurements; the [loudness and true-peak guide](https://soundforgepro.com/sound-forge-loudness-meters/) covers program delivery. ## Test 32-Bit Float Headroom First ![Gain reduction test distinguishing intact 32-bit float headroom from a permanently flattened waveform](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/08/float-decision-desktop.webp) Lower gain on a copy first: a returning curve points to stored over-range data, while a remaining plateau needs more diagnosis. 1. Confirm that the source file really is 32-bit float and isn't a clipped 24-bit file that was converted later. 2. Make a copy and lower gain enough that every displayed peak sits below full scale. 3. Zoom into the suspected event. 4. If a smooth curve appears and the distortion disappears, keep the gain change and stop. There is no missing peak to estimate. 5. If the plateau and harshness remain, the clipping happened before or during capture, or the stored file was already damaged. The [Zoom L6 manual](https://zoomcorp.com/manuals/l6-en/) and [H6studio manual](https://zoomcorp.com/manuals/h6studio-en/) document a recorder-specific case in which 32-bit float WAV data that only looks clipped can reveal an intact curve once you lower the gain. That only works if the recording chain kept the over-range values. The [Zoom F6 manual](https://zoomcorp.com/documents/248/E%5FF6.pdf) separately warns that maximum input level can still be exceeded. No file format can undo a microphone or analog input stage that saturated before the protected data was written. The same test prevents a delivery mistake. A 32-bit float file may carry samples above 0 dBFS that clip when sent directly to a fixed-point playback or export path. Lower gain before converting to 24-bit PCM. If distortion remains, diagnose it before choosing DeClipper. A remaining hard-clipped plateau supports that route; hiss, codec artifacts, playback faults and intentional saturation need different treatment. ## Prepare a Safe Repair Session 1. **Preserve the source.** Save an untouched copy and work in WAV at the original sample rate. 2. **Mark three regions.** Choose the worst clip, a mild clip and a clean transient. A useful setting improves the damaged passages without audibly degrading the clean transient. 3. **Separate channels when appropriate.** A wireless hit or cable fault may damage only one side of a stereo file. 4. **Turn off downstream processing.** Compression, limiting, EQ and normalization can hide the original threshold or exaggerate the result. 5. **Plan a level-matched comparison.** Reconstructed peaks and makeup controls can make the processed version louder. Don't use peak normalization to repair clipping. Constant gain can move a plateau below 0 dBFS, but it can't bring back its shape. The float-headroom test above is the one deliberate exception to leaving levels alone during diagnosis. After repair, the [normalization guide](https://soundforgepro.com/how-to-normalize-audio-in-sound-forge-pro/) explains how to set the delivery level without mixing up loudness adjustment and reconstruction. ## Find the Damage with Tools → Detect Clipping 1. Select the problem passage or the whole file for an initial scan. 2. Choose **Tools → Detect Clipping**. 3. For a sample-plateau scan, leave Use True Peaks off. Set Threshold just below the suspected plateau, and don't assume earlier clipping happened at the file’s current 0 dBFS ceiling. 4. Set Clip Length to require a repeated run of suspicious samples. 5. Run the scan and use the resulting markers in Go To or Regions List. 6. Open each marker at sample-level zoom and confirm it against playback. The current [Sound Forge Detect Clipping help](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/proonly/detect%5Fclipping.htm) documents Threshold and Clip Length, then marks runs of sequential samples with the same value above the threshold. Its Detect all clip-related plateaus preset is meant to find clipping that was later turned down. Treat the scan results as places to inspect; they don't prove every marker needs processing. | Control | What it changes | Safe use | | ---------------------- | -------------------------------------------------- | ---------------------------------------------------------------------------------------------- | | **Threshold** | Lowest level the scan considers | Set just below the shelf; lowering it broadens the search and can include intentional plateaus | | **Clip Length** | Required run of repeated high-level samples | Raise it to ignore isolated samples; lower it only to catch verified short clips | | **Use True Peaks** | Includes oversampled peak estimation | Useful for delivery risk, but not proof of stored flat-top damage | | **DC Blocking Filter** | Compensates for DC/asymmetry in true-peak analysis | Analysis option with true-peak mode, not a command that repairs DC offset in the file | A marker gives you a lead. It doesn't hand you a verdict. Synths, square-like sounds, hard limiting and clipped-then-lowered files can all fool a naive visual check, so process only the markers that match distortion you can actually hear and don't want. ## Repair a Passage with Sound Forge DeClipper ![Nine-step Sound Forge workflow from preserving a clipped source to verifying a DeClipper render](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/10/repair-workflow-desktop-v20261006.webp) Repair one representative event before expanding the selection or reusing a DeClipper setting. ### Nine-step DeClipper checklist 1. **Preserve the source**. Save an untouched master and repair a WAV copy at the original sample rate. 2. **Test 32-bit float headroom**. Lower gain on a copy; stop if a smooth peak returns and the distortion disappears. 3. **Identify the clipping type**. Inspect repeated plateaus for hard digital clipping. Treat rounded analog overload separately; neither intentional limiting nor a true-peak overshoot alone proves lost sample peaks. 4. **Run Detect Clipping**. Choose Tools → Detect Clipping and mark suspicious runs of repeated high-level samples. 5. **Select a representative event**. Choose one audible clipped passage with clean context on both sides. 6. **Open DeClipper**. Choose Effects → DeClipper. For hard digital clipping, set Clip level just below the plateau; evaluate analog overload with the appropriate mode instead. 7. **Preview conservatively**. Adjust the detection controls and Mix on the test passage. Use Inverse for the changed signal and Bypass for the original, then turn both off to hear the normal repair. 8. **Leave output headroom**. Lower Volume as needed so the reconstructed peak doesn't clip the next fixed-point stage. 9. **Verify the render**. With Inverse and Bypass off, apply once and listen through both boundaries. Measure sample and true peak in a new export. Undo a rendered test before including it in a larger pass. The [Sound Forge Repair help](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/proonly/repair.htm) puts the Sequoia restoration effects in the Effects menu. Its [DeClipper page](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/proonly/declipper.htm) describes reconstruction from surrounding material and points to the installed dialog’s ? help. The [Sequoia 2026 control reference](https://cdn.borisfx.com/borisfx/Documentation/sequoia-2026/en/Content/DeClipper.htm) names the Kind of clipping modes Analog, Digital and Analog + Digital. Min. clip length counts consecutive samples; it isn't measured in milliseconds. Confirm those labels in your build instead of carrying settings over from another declipper. | Control | How to approach it | Reject or adjust when | | ---------------- | --------------------------------------------------------- | -------------------------------------------------------------------------- | | Clip level | For hard clipping, start just below the observed shelf | A lower threshold alters healthy peaks | | Min. clip length | Match the shortest verified run of clipped samples | Long settings miss short clips; very short settings catch wanted peaks | | Kind of clipping | Choose a mode that fits the diagnosed overload | The normal output loses clarity or attacks | | Mix | Use enough correction to make the defect less distracting | More correction smears speech or softens attacks | | Volume | Leave room for taller reconstructed peaks | The output clips again, or unequal loudness biases the comparison | | Limiter | Compare with and without this additional peak control | Its effect on dynamics outweighs the improvement; measure the final export | ## Verify the Repair by Ear and Meter ![Seven listening and metering checks for accepting or rejecting a clipped audio repair](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/10/verification-desktop-v20261006.webp) Keep the repair only when it is less distracting, preserves attacks, and removes no recognizable program audio. Judge preservation in the normal repaired output, and remember that a rounded waveform is no listening test. Inverse plays back what changed, and that can include useful reconstructed attacks, so assess preservation in the normal processed output with Inverse off. Declipping usually lifts the reconstructed peak above the old ceiling, and the surviving samples may still carry overload harmonics. Use this acceptance sequence: 1. Listen to the repaired event in isolation. 2. Listen in context at normal volume. 3. Toggle Bypass at matched loudness. 4. Use Inverse to hear the difference signal, then switch it off before judging the normal output. Reconstructed attacks can legitimately appear in the difference. 5. Check the edit boundaries for ticks. 6. Measure sample peak and true peak after rendering. 7. Inspect a second event before batch-applying the setting. 8. Keep the repair only if it is less distracting than the original. Don’t use compression or aggressive EQ to make the A/B “match” before deciding. Those processes can emphasize residual harmonics and conceal timing damage. Repair first, then rebuild the downstream chain. ## Use Manual Repair for Tiny or One-Channel Damage DeClipper isn't always the smallest tool for the job. The current [Sound Forge Repair help](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/proonly/repair.htm) keeps several sample-level options: - **Tools → Repair → Interpolate:** replaces a tiny selection by connecting its boundaries. Boris FX recommends selections under about [2 ms in most cases](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/proonly/interpolating%5Fsound%5Fdata.htm). It draws a straight-line bridge, so undo it if it creates a new tick or changes wanted audio. It's meant for a tiny glitch; an overloaded phrase is too much for it. - **Edit → Tool → Pencil:** redraws individual samples. Zoom in until it becomes available; the maximum zoom-ratio setting lives in Options → Preferences → Editing. Use it for a tiny isolated defect, and don't try to invent an entire missing phrase with it. See the [Pencil tool instructions](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/the%5Fpencil%5Ftool.htm). - **Copy Other Channel:** replaces a short damaged section in one stereo channel with the clean side. It works only when both channels contain similar material. The official [Copy Other Channel guide](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/proonly/copy%5Fother%5Fchannel.htm) recommends a roughly 1–50 ms selection and adds a crossfade. - **Replacement from another take:** for repeated dialogue, room tone, a drum hit or an alternate live mic, an edit can sound more natural than heavy reconstruction. The [crossfade guide](https://soundforgepro.com/crossfade-audio-sound-forge/) covers the boundary. ## Choose the Repair by Recording Type ### Voice, podcast, and interview Work syllable by syllable. Plosives and shouted vowels can produce isolated hard clips worth testing, while a wireless transmitter or mic capsule that overloaded across a sentence often remains fuzzy. Protect consonant timing and breath edges. If one word is irreparable, borrowing the same word or phoneme from another take can beat another DeClipper pass. ### Music and stereo masters Check whether the peaks were limited on purpose. On a stereo mix, select the intended channels and compare the image before and after processing, and don't assume the effect has a stereo-link switch. A one-channel repair needs extra care, since changing one side can shift the balance. Listen for softened drum attacks, smeared cymbals and new roughness in sustained notes. ### Field and live recording Preserve the original and note the recorder format, then test 32-bit float gain first. If the hardware input indicator showed overload, a valid float file may still contain upstream damage. Current Zoom manuals distinguish stored float headroom from hardware clipping for exactly this reason. ### Audio extracted from video or MP3 Ask for the camera WAV, recorder ISO or original video before processing a transcoded copy. Lossy encoding adds its own smearing around a clipped transient. Work in PCM and make one final lossy export; a declipper can't repair repeated MP3 or AAC generations. ## Sound Forge DeClipper vs iZotope RX De-clip If the file is already open in Sound Forge, previewing DeClipper on a selection lets you judge the repair before you reach for another tool. Detect Clipping creates markers, DeClipper offers threshold/length/type controls, and Inverse lets you hear the signal the algorithm changed. Inverse isn't a bin holding only removed noise, and recognizable peak energy in it doesn't invalidate a repair on its own. The [RX 12 De-clip manual](https://docs.izotope.com/rx12/en/de-clip.html) describes digital and analog clipping repair, a threshold histogram, Suggest and output controls; the [RX De-clip walkthrough on izotoperx.net](https://izotoperx.net/fix-clipped-audio-rx-de-clip/) shows how to set Threshold from that histogram. RX Elements only runs this module as a plug-in, so standalone Editor instructions don't apply there. The [iZotope distortion-repair tutorial](https://www.izotope.com/community/blog/repairing-a-distorted-audio-track) also shows why some leftover distortion needs a different module after De-clip. Compare the same damaged selection at matched loudness. These documented differences don't crown a winner on speed or sound quality. If the job also needs spectral reconstruction, dialogue isolation, or several restoration modules after declipping, compare the wider [audio restoration software options](https://soundforgepro.com/audio-restoration-software/) before stacking more broad processing on a damaged master. Boris FX acquired iZotope on July 2, 2026, according to the [official acquisition announcement](https://blog.borisfx.com/press/boris-fx-acquires-izotope-the-award-winning-leader-in-intelligent-audio-technology). Shared ownership alone doesn't tell you which RX edition, if any, comes with your Sound Forge purchase. Check the actual license and installed plug-ins instead of relying on a general help-page bundle description. The [Sound Forge vs RX comparison](https://soundforgepro.com/sound-forge-pro-vs-izotope-rx/) covers the workflow and edition differences. ## Know When to Stop and Re-record Stop after a controlled pass if the normal processed output still sounds harsh or its attacks are damaged at matched loudness. Wanted peak energy in Inverse is no reason on its own to reject a repair. If the performance can be repeated, re-record it, and ask for an alternate mic, camera channel, safety track or 32-bit float original before you settle for a damaged mixdown. For the next recording, set the correct mic/line input, leave fixed-point headroom, keep an eye on the analog stage and source SPL, and record a short loud rehearsal. The [Sound Forge recording guide](https://soundforgepro.com/how-to-record-audio-in-sound-forge-pro/) covers Windows input selection and capture levels. A limiter placed before the stage that would clip can catch the odd peak, but it can't repair a microphone capsule that already overloaded. ## Clipped Audio Repair FAQ ### Does normalizing fix clipped audio? No. Peak normalization changes the level of the waveform that already exists. It can move a plateau below 0 dBFS, but it cannot reconstruct missing samples. Gain reduction is sufficient only when a compatible 32-bit float file retained intact over-range data. ### Does a 32-bit float recording need a declipper? Not automatically. Confirm the file format, lower gain on a copy, and inspect the same event again. If a smooth curve returns and the distortion disappears, no peak reconstruction is needed. If distortion remains, identify its cause; the float format alone neither proves nor rules out earlier clipping. ### Why does audio sound clipped below 0 dBFS? The file may have clipped and then been turned down, or the microphone, transmitter, preamp, tape stage, or converter input may have overloaded before the file was written. The current peak level cannot prove that the source path was clean. ### Can declipping create peaks above 0 dBFS? Yes. Interpolation can reconstruct a peak above the old flat ceiling. Leave output headroom and measure both sample peak and true peak after rendering so the repaired signal is not clipped again downstream. ### Can Sound Forge repair clipping in one channel only? Yes. Select only the damaged channel for a DeClipper test. For a very short event where both stereo channels contain similar material, Tools → Repair → Copy Other Channel may produce a cleaner edit. ### What is the best DeClipper threshold? There is no universal number. For hard digital clipping, start with Clip level just below the observed plateau. If healthy transients are affected, raise the threshold or increase the minimum sample count, then check that the real clips are still treated. Judge the normal output: recognizable peak energy in Inverse is not by itself a failed repair. Rounded analog overload needs a separate mode and listening test. ### Can severe clipping be fully repaired? Usually not. Long plateaus and sustained analog overload remove too much reliable information. A declipper can make the damage less distracting, but replacement audio, a clean alternate channel, or a new recording is often the honest fix. ### Does Sound Forge Audio Studio have DeClipper? Check the installed Audio Studio version’s own effect list and help. This walkthrough follows Sound Forge Pro 2026, whose Repair help places DeClipper in the Effects menu; that does not establish availability in every Audio Studio edition. ## The Practical Declipping Rule Lower the gain first when real 32-bit float headroom is possible. For hard digital clipping, inspect the plateau and try a small selection. For analog overload, evaluate the right mode without expecting a flat top. Keep the version that preserves the performance and sounds less distracting, even if another one has a tidier waveform. If the defect is still unclear, go back to the [Sound Forge restoration hub](https://soundforgepro.com/tag/sound-forge-restoration-guides/) to tell overload apart from clicks and background noise. ### Remove Hiss and Hum From Audio: Sound Forge Guide URL: https://soundforgepro.com/remove-hiss-hum-sound-forge/ Last updated: 2026-10-10T13:30:58.000Z For an existing recording, treat hiss and hum separately. Use narrow EQ cuts or a de-hum processor such as [RX De-hum](https://izotoperx.net/izotope-rx-de-hum/) for measured, stable hum lines; use Effects → DeHisser for the remaining steady broadband hiss. If your DeHisser has Absorption, Inverse and Reduction controls, check the removed signal with Inverse, then switch Inverse off before adjusting final Reduction. Compare the normal processed output with the original at similar loudness, and stop before consonants, attacks or fades become dull or watery. If you can record another take, look for the noise in the recording chain first. Moving a cable or replacing a faulty connection may help more than processing every future file. Software repair can make an irreplaceable take more usable, but it cannot fix the hardware that produced the noise. This Windows guide covers steady hiss and tonal hum in Sound Forge Pro. For changing fan or room noise, use the [background-noise workflow](https://soundforgepro.com/how-to-remove-background-noise-in-sound-forge-pro/); isolated impulses need the [click-and-pop repair workflow](https://soundforgepro.com/how-to-remove-clicks-pops-sound-forge-pro/). The [Sound Forge restoration hub](https://soundforgepro.com/tag/sound-forge-restoration-guides/) helps separate these problems when the recording contains more than one. Documentation checked September 8, 2026\. Menu paths follow Sound Forge Pro 2026 help; detailed DeHisser controls are cross-checked against the Sequoia 2026 reference and must match your installed dialog. This guide does not claim a hands-on test of your build or third-party plug-ins. ## Identify the Noise Before Removing It Listen to an exposed pause and a passage containing wanted audio. A waveform helps locate events in time; a spectrum helps distinguish a broad noise floor from narrow interference lines. Do not use the picture alone to decide what to remove. The diagrams below show patterns to look for, not filter settings to copy. ![Desktop guide comparing hiss hum rumble and changing noise by spectrum shape](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/08/noise-types-desktop.webp) The spectrum shape points to the cause and the first useful repair tool. | What you hear | What to look for | First tool | Main risk | | ------------------------------ | --------------------------------------------------------------------------------------- | ------------------------------------------------------- | ------------------------------------------ | | **Hiss** | Broad, steady energy across many frequencies, often obvious in the upper mids and highs | DeHisser or noise-profile reduction | Dull consonants, cymbals and tape ambience | | **Hum** | One narrow low-frequency line with evenly spaced harmonics | Narrow EQ cuts or dedicated De-hum | Removing bass fundamentals and body | | **Buzz** | A stronger harmonic ladder that reaches higher than a soft hum | Several measured notches or De-hum | A hollow, comb-filtered result | | **Rumble** | Broad low-frequency energy from handling, traffic, turntable or HVAC | High-pass filter, only as high as needed | Thinning a voice, kick, bass or piano | | **Variable fan or room noise** | The spectrum and level change over time | Adaptive/spectral denoiser, automation, or re-recording | Underwater speech and moving artifacts | | **Clicks and crackle** | Short impulses rather than a continuous floor | Click/pop repair | Smearing attacks if treated as hiss | Don’t diagnose by name alone. “Static” may mean hiss, clipping, electrical buzz or intermittent digital crackle. “Hum” may have a weak 50/60 Hz fundamental but strong harmonics, with stronger lines near 100/120 Hz or higher. Measure them, then listen: a visible peak can also be a wanted note. ## Fix Hiss and Hum at the Source First Before changing a connection, stop playback and mute monitoring. Change one part of the recording chain at a time and keep the gain settings unchanged. A noise change after unplugging a source is a clue, not proof of where the fault lies: the connection and ground path have changed too. Substitute a known-good compatible cable or source where possible. Never remove a protective mains earth; [Rane’s interconnection guidance](https://www.ranecommercial.com/legacy/note110.html) explicitly says to keep the original factory grounding intact and leave wiring modifications to trained personnel. For microphone connections, [Shure recommends turning phantom power off before plugging or unplugging](https://www.shure.com/en-EU/insights/what-is-phantom-power-why-do-i-need-it). Follow the mic and interface maker’s shutdown and discharge instructions, then restore the required power only after the connection is secure. Keep monitoring muted during the change. - **Move audio cables away from AC adapters, dimmers and power cables.** - **Use balanced connections where the equipment supports them.** Shure’s [audio troubleshooting guide](https://www.shure.com/damfiles/default/global/documents/publications/en/performance-production/audio-systems-guide-for-video-and-film-production-english.pdf-041a24efe18f0fd3f46465374fbe1839.pdf) identifies unbalanced runs near power and lighting as a common hum pickup path. - **Test laptop power.** Record briefly on battery with nonessential USB devices disconnected. If the noise changes, investigate the power or USB path rather than filtering every future take. - **Set gain at the right stage.** Digital gain after capture raises the recorded noise as well as the voice; it does not improve that recording’s signal-to-noise ratio. Improve the wanted signal at capture while leaving headroom. Recording too hot creates clipping, which needs the separate [clipped-audio repair workflow](https://soundforgepro.com/fix-clipped-audio-sound-forge/). - **For tape or vinyl, service the transfer chain.** Use suitable, format-specific cleaning and check the playback path before capture. Leave alignment or work on fragile media to a qualified transfer specialist. Post-processing should not compensate for a preventable transfer fault. Save a short recording of the normal setup, then repeat with one known-good compatible cable or source substituted. Test battery operation or a nonessential USB connection separately, keeping monitoring muted while reconnecting. Record long enough to capture the recurring noise. These comparisons narrow the search; they do not establish a universal diagnosis. Shure’s [examples of hum and interference](https://www.shure.com/en-US/insights/whats-that-noise-and-how-to-fix-it) include microphone pickup of a nearby AC hum field, so consider placement as well as cables. ![Source-first checklist for tracing hum through cables power and audio hardware](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/10/source-first-desktop-v20261006.webp) A short isolation recording can reveal whether the noise starts in the source, cable, power, or computer path. If the clean comparison depends on input gain, driver mode, or monitoring, repeat it with the [Sound Forge recording setup checklist](https://soundforgepro.com/how-to-record-audio-in-sound-forge-pro/). If the input is silent or refuses to arm, solve the [Sound Forge recording fault](https://soundforgepro.com/sound-forge-pro-not-recording-audio/) before judging the noise floor. ## Prepare a Safe Restoration Session 1. **Keep the original capture.** For a PCM capture, retain its sample rate and precision in a lossless working copy. For an MP3 source, decode once to a PCM or float working file; MP3 has no original PCM bit depth to preserve. Never denoise an MP3 and overwrite the only source. 2. **Mark three test regions.** Use a quiet passage, a dense or loud passage, and a fade or word ending. One setting must survive all three. 3. **Protect true silence and wanted room tone.** A noise-only passage is useful for analysis, but deleting every pause can make edits pump or expose hard cuts. 4. **Make one change at a time.** Hum notch, hiss reduction, gate and compression should be auditioned separately before they become a chain. 5. **Level-match bypass.** The quieter version often seems cleaner. Match output level closely enough that the decision is about damage, not loudness. For a repeatable non-destructive chain, the current [Sound Forge Plug-In Chainer guide](https://soundforgepro.com/how-to-use-plug-in-chainer-sound-forge-pro/) explains how to order, bypass and save processors. Saving a chain preserves processor settings, not every destructive edit. Keep the source media and save the working FRG project where appropriate; render the processed delivery to a new file. Do not overwrite the only capture simply because the chain itself can be bypassed. ## Nine-step restoration checklist Use this checklist as a repeatable pass before committing a repair: 1. **Keep the original**. Leave the source untouched and process the lossless working copy. 2. **Mark test regions**. Reuse the quiet, dense and fade regions for every comparison. 3. **Identify the noise**. Separate broad hiss, narrow hum, low rumble, variable room noise, and isolated clicks. 4. **Measure the spectrum**. Locate the actual hum fundamental and audible harmonics instead of entering a regional preset blindly. 5. **Reduce stable hum**. Cut only measured interference lines with narrow EQ or a dedicated de-hum processor. 6. **Open DeHisser**. Choose Effects → DeHisser for the remaining uniform broadband hiss. 7. **Set Absorption with Inverse**. Back off when words, transients, music, or ambience appear in the removed signal. 8. **Lower final Reduction**. Switch Inverse off first: Reduction has no effect while Inverse is active. Adjust the normal output until speech, attacks and fades remain natural. 9. **Verify the complete file**. Compare bypass at similar loudness and recheck every marked region. Turn Inverse and Bypass off before applying; save and audition a new output file. ## Measure the Noise with Spectrum Analysis 1. Select a short section where the noise is exposed but representative. 2. Open **View → Spectrum Analysis**. 3. Look first below roughly 500 Hz for narrow stable lines, then scan the full range for a broad floor. 4. Move the cursor to the lowest stable peak and note its actual frequency. 5. Check whether additional peaks repeat at integer multiples. 6. Select a second section and click Refresh, or enable Auto Refresh. If the interference peaks move, a fixed notch may miss them; wider cuts can damage more wanted audio. The current [Sound Forge Spectrum Analysis help](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/proonly/spectrum%5Fanalysis-overview.htm) describes the view as amplitude by frequency rather than amplitude by time. Boris FX also recommends a manageable selection in the [Spectrum Graph workflow](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/proonly/viewing%5Fa%5Fspectrum%5Fgraph.htm); a very long selection takes longer and hides time variation. The [full Spectrum Analysis guide](https://soundforgepro.com/how-to-use-spectral-analysis-tool-sound-forge-pro/) covers FFT size, windowing and cursor readouts when the peak is hard to isolate. Use the spectrum to locate, then your ears to decide. A visible line isn't automatically objectionable; the same frequency can belong to a bass note, vocal fundamental, transformer hum or room mode. A/B the proposed cut on the most exposed and most musically important sections. ## Remove 50/60 Hz Hum and Harmonic Buzz To remove hum from audio safely, begin with the measured fundamental. In many systems, mains-related noise starts near 50 Hz or 60 Hz and repeats at integer multiples. Treat that as a hypothesis rather than a preset: a transfer may contain drift, or a harmonic may be stronger than the fundamental. Measure the actual frequency before entering a number. ### Method 1: narrow cuts with Modern Equalizer 1. Select a representative test passage. Open FX Plug-Ins → Apply Plug-In Chain and add Modern Equalizer to an otherwise empty test chain. 2. Add a peaking band at the measured fundamental. 3. Increase Q to narrow the peaking band and lower Gain only until the interference is no longer distracting. Check for ringing as well as lost tone. 4. Add a second band only when the next harmonic is clearly visible and audible. 5. Toggle Bypass to compare the original and processed signal. If the processed version loses body or weakens a wanted note, reduce the cut; a narrower band is useful only if it still catches the hum without objectionable ringing. 6. Preview before applying. A fixed notch is appropriate only while the interference stays put. Undo any rendered test before processing a larger region that includes it, then save the result separately. The [Sound Forge Pro 2026 Modern Equalizer help](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/modern%20equalizer.htm) documents up to eight bands, peaking filters and Frequency, Gain and Q controls. A/B stores two settings; Bypass compares with no EQ. The [Apply Plug-In Chain instructions](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/apply%5Ffx%5Fchain.htm) explain selection-based preview and application. Start with only the proven interference lines. Narrower bands also have a ringing tradeoff, so check note attacks rather than increasing Q indefinitely. ### Method 2: a dedicated De-hum plug-in For a long or changing harmonic pattern, consider a dedicated processor rather than adding more manual cuts. The [RX 12 De-hum manual](https://docs.izotope.com/rx12/en/de-hum.html) distinguishes Static mode for simpler tonal hum from Dynamic mode for complex buzz. Adaptive tracking follows changes over time; iZotope says Dynamic Adaptive plug-in processing is not optimized for real-time use and should be used offline. De-hum is available in Elements, Standard and Advanced, but Elements supplies it only as a plug-in. Sound Forge advertises [VST3 support](https://www.soundforge.com/sound-forge/pricing/), and the [RX 12 requirements](https://www.izotope.com/products/rx-standard) list 64-bit VST3\. That is not a tested-host guarantee: Sound Forge is absent from iZotope’s confirmed host list. Check the actual RX license and test scanning, preview, saved settings and rendering on a copy before depending on it. The [Sound Forge Repair help](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/proonly/repair.htm) refers to included RX plug-ins, but that general statement does not establish what your purchase contains. A standalone fallback needs Standard, Advanced or a trial that includes the editor; Elements alone does not provide it. ✓ **Hum rule:** cut the few lines you can prove are interference. Don’t build a comb filter from every mathematical multiple merely because the analyzer can display one. ## Remove Broadband Hiss with Sound Forge DeHisser DeHisser is for steady low-level broadband noise such as tape, microphone, preamp or converter hiss. It doesn't need a captured noise sample. In the current Sound Forge help, open it at **Effects → DeHisser**. The controls in this sequence are documented in [Sequoia 2026’s DeHisser reference](https://cdn.borisfx.com/borisfx/Documentation/sequoia-2026/en/Content/DeHisser.htm). Sound Forge’s public page directs detailed questions to the dialog’s ? help. Use the sequence only if that installed dialog exposes the same controls; if it differs, follow its own help rather than inferring identical behavior from a shared effect name. 1. **Select the hardest passage.** Start with a quiet phrase, exposed sustain or fade where hiss competes with wanted detail. 2. **Open Effects → DeHisser.** The [current Sound Forge DeHisser page](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/proonly/dehisser.htm) confirms the effect and path. 3. **Raise Reduction temporarily.** This makes the Absorption boundary easier to hear; it is not the final setting. 4. **Increase Absorption slowly.** Stop when the hiss is controlled but consonants, cymbals, pick attack and room tone remain intact. 5. **Enable Inverse.** You should hear mostly noise. If you can identify words, melody, transients or reverb, back Absorption down. 6. **Turn Inverse off, then lower Reduction.** Reduction has no influence in Inverse mode. Adjust it while listening to the normal processed signal, leaving enough residual noise to preserve wanted detail. 7. **Check the other marked regions.** A setting that works in a pause may chew into a loud, bright section or make a fade chirp. 8. **Compare bypass at matched level.** When the normal output is better, turn Inverse and Bypass off and apply once. Save to a new file and listen again. Undo a rendered test before processing an overlapping larger region. The Sequoia 2026 DeHisser control reference gives a Reduction range of 0–30 dB and warns about loss of brightness, phase-like distortion and chirping at excessive Absorption settings. The maximum is not a recommended cleanup target; quiet fades often need less suppression. Overlap increases the overlap between analysis windows; higher values cost more processing power. Resolution changes the internal analysis resolution, and the reference cautions that higher is not automatically better. Leave these alone until the basic settings work, then change one at a time and compare the same passage. ## When to Use a Noise Profile or Adaptive Denoiser DeHisser targets uniform hiss without learning a noise sample. A profile-based denoiser is worth testing when a noise-only passage captures the same steady fan or room bed as the wanted audio. For a narrow camera whine, first consider a measured notch. When the noise changes, adaptive processing or local edits may help, but neither guarantees clean separation from speech. 1. Find a noise-only region from the same recording setup. 2. Capture the profile from a representative section; do not duplicate one tiny block to make it “longer.” 3. Apply a conservative pass to a copy or short test selection. 4. Listen to the residue or removed signal. 5. Lower sensitivity or reduction when wanted speech or music appears in the residue. 6. Before trying a second pass, save the first result separately. Compare both with the original; keep the second only if its extra cleanup is worth any added damage. The [Audacity Noise Reduction manual](https://www.audacityteam.org/manual/effects/noise-removal-and-repair/noise-reduction/) provides a free profile-based alternative, not a Sound Forge menu path. It explains why the profile must contain noise alone and warns that excessive reduction creates metallic or watery artifacts. Audacity’s Noise only output is a diagnostic mode: undo that test before rendering the normal cleaned version. ## Use a Different Workflow for Voice, Tape, Vinyl, and Music ### Voice, podcast, and interview Protect consonants and word endings. Reduce stable hum first, then apply light hiss reduction while checking S, F and SH sounds. A gate can lower noise between phrases, but it cannot remove hiss under speech. If the room noise rises and falls with every word, ease the denoiser and use clip gain or automation on pauses instead of forcing the gate. The [voice-over recording workflow](https://soundforgepro.com/sound-forge-pro-for-voice-over-recording/) covers the capture side before cleanup. ### Cassette and reel-to-reel transfer Keep the untouched tape transfer. Before capture, check the playback speed, head condition and alignment, and any documented noise-reduction encoding. [IASA’s tape noise-reduction guidance](https://www.iasa-web.org/tc04/magnetic-tapes-noise-reduction) explains that encoded tapes need the matching, correctly aligned decoder; decoding and later hiss suppression are different operations. Do not guess at Dolby or dbx settings to make the spectrum look quieter. If the recording is valuable and its playback requirements are uncertain, get specialist help before further handling. Sample the noise near the material you are repairing because the tape noise can change across a reel or cassette. Preserve a little stable tape bed when removing it completely would erase ambience or cymbal tails. ### Vinyl transfer Fix grounding hum before capture, then remove isolated clicks and large pops before broadband reduction so they don't distort the noise estimate. Follow the complete [Sound Forge vinyl-restoration workflow](https://soundforgepro.com/sound-forge-pro-for-vinyl-restoration/) for cleaning, capture, click repair, hum, rumble and final sides. ### Music or stereo master Be cautious with narrow notches on bass notes and with hiss reduction on cymbals, strings and reverb. Process mid and side channels separately only when the evidence supports it; otherwise channel-selective work can shift the stereo image. If the noise is part of an already limited master, a small residual may be less audible than the damage caused by another aggressive process. ## A Safe Processing Order ![Seven-step safe order for measuring hum reducing hiss and checking the residual signal](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/10/safe-order-desktop-v20261006.webp) The repair is finished when the noise is acceptable and the residual holds no obvious wanted audio. Use residue listening to spot damage, then judge the normal processed output in context. A trace of wanted content in the removed signal may be an acceptable compromise, but clearly damaged words, attacks or fades are a reason to back off. | Order | Problem | Why it comes here | Verification | | ----- | -------------------------------- | -------------------------------------------------------------------------- | ------------------------------ | | 1 | Source and transfer faults | Prevents more contaminated audio and may eliminate the need for processing | Short comparison recordings | | 2 | Severe clicks or isolated events | Prevents impulses from confusing broadband analysis | Attack and transient check | | 3 | Stable hum or whistle | Narrow correction removes specific lines before broadband modeling | Analyzer plus bypass | | 4 | Broadband hiss or room bed | Works on the remaining stationary floor | Inverse/residue and fades | | 5 | Gate or pause automation | Cleans exposed gaps after the continuous noise is controlled | Phrase starts and endings | | 6 | EQ, compression, mastering | These can exaggerate residual noise and should follow repair | Full-file A/B at matched level | This order is a strong default rather than a law. A high-pass filter may be needed before a processor that reacts badly to subsonic rumble, and a click buried under heavy noise may be easier to expose after a light denoise pass. Make the exception on a copy and keep it only when the full-file A/B proves it. ## Fix Metallic, Watery, or Hollow Artifacts | Artifact | Likely cause | First correction | | ------------------------------- | ----------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------ | | Metallic or “tinkly” noise | Noise model is wrong or reduction/sensitivity is too aggressive | For profile-based noise reduction, choose a representative noise-only sample; reduce the processing strength | | Underwater speech | Changing noise overlaps the voice and the model is tracking both | Use less adaptive reduction; automate pauses; consider re-recording | | Dull S sounds and cymbals | DeHisser Absorption is crossing into wanted high-frequency detail | Lower Absorption and check Inverse | | Thin voice or missing bass note | Hum notch or high-pass filter is too wide or too high | Narrow the band, reduce the cut, or use a dedicated harmonic tracker | | Hollow/phasey music | Too many harmonic notches or overprocessing in multiple stages | Remove unproven bands and rebuild from the fundamental | | Pumping between phrases | Gate threshold/release or changing denoiser gain | Slow the transition, reduce range, or use manual clip gain | Don’t judge a restoration at an exaggerated headphone level only. Compare quietly and at normal listening level through speakers and headphones. A faint noise floor that disappears in context may be finished, while an artifact that follows every syllable will stay distracting after export. ## When Not to Remove All the Noise Stop processing when the residual noise is less distracting than the side effects. Re-record when the performance can be repeated and the source problem is fixable. If the recording is archival, unique or historically important, preserve the original. For a badly contaminated one-off recording, create two deliverables if useful: a conservative archival master and a more aggressive listening copy. When a unique recording needs spectral reconstruction beyond these file-level tools, compare [dedicated audio restoration software](https://soundforgepro.com/audio-restoration-software/) before stacking more broad processing in Sound Forge. When noise overlaps wanted sound, reducing one may damage the other. [AI-assisted restoration](https://soundforgepro.com/ai-audio-restoration/) can estimate a cleaner signal, but the result still needs listening checks. Do not promise lossless separation or approve a file simply because its noise floor is lower. ## Remove Hiss and Hum FAQ ### Where is DeHisser in Sound Forge? In the current Sound Forge help, choose Effects → DeHisser. If it is missing, verify the installed edition and plug-in state instead of following a Sony- or MAGIX-era screenshot. ### Should I remove hiss or hum first? Remove stable hum first. Narrow notches or a dedicated de-hum processor can reduce specific tones before broadband hiss reduction analyzes the remaining floor. Reverse the order only when a controlled A/B on a copy clearly preserves more wanted audio. ### Is electrical hum always exactly 50 or 60 Hz? No. Those are common mains-related starting points, but the strongest recorded line may be shifted or appear at 100/120 Hz and higher harmonics. Measure the actual spectrum rather than entering a regional preset blindly. ### How much hiss reduction should I use? Use the least reduction that makes the hiss non-distracting; no dB setting is safe for every recording. With the DeHisser controls described here, use Inverse to check what is being removed. Judge the normal output on words, transients and fades, not the residue alone. ### Can a noise gate remove hiss? A gate can lower hiss during pauses, but it does not remove hiss while speech or music is above the threshold. Use it after continuous-noise repair and keep the range and release natural enough that phrase edges do not pump. The [Sound Forge noise-gate guide](https://soundforgepro.com/how-to-use-noise-gate-sound-forge-pro/) covers threshold, attack and release without pretending a gate is broadband audio noise reduction. ### Why does cleaned audio sound metallic or underwater? The processing may be removing wanted audio or following a changing noise floor too aggressively. With profile-based reduction, check the noise-only sample and reduce sensitivity or strength. With DeHisser, revisit Absorption and Reduction. Compare the normal output with the original; if the voice is buried in noise, a new recording may be the only satisfactory option. ### Can EQ remove 50/60 Hz hum? Yes, for stable interference at a few measured frequencies. Try narrow peaking cuts at the audible hum lines and compare the musical content as well. A dedicated processor offers more options for a long or drifting harmonic pattern, but it still needs a test: neither notches nor adaptive tracking are automatically harmless. ### Can iZotope RX De-hum run in Sound Forge? Treat it as an unconfirmed host combination. RX 12 supplies 64-bit VST3 plug-ins and Sound Forge supports VST3, but iZotope does not list Sound Forge among its confirmed RX 12 hosts. Verify your RX license, then test scanning, opening, preview, saved settings and rendering on a copy. Dynamic Adaptive De-hum is intended for offline plug-in use. If you need a standalone fallback, use Standard, Advanced or an editor-enabled trial; Elements alone is plug-in-only. ### Sound Forge Audio Studio vs Sound Forge 2026: What Exists Now? URL: https://soundforgepro.com/sound-forge-audio-studio-vs-sound-forge-2026/ Last updated: 2026-10-10T12:56:19.000Z **Sound Forge Audio Studio 17 and Sound Forge 2026 are products from different eras.** Audio Studio 17 was released by MAGIX in 2023\. The current Boris FX catalog sells Sound Forge and Sound Forge Plus. Audio Studio isn’t in that catalog, which makes this a legacy-versus-current decision rather than a comparison between two current tiers. Keep Audio Studio 17 if you already own it, it activates, and it completes your recording, trimming, cleanup, and export work. Sound Forge 2026 makes sense when you need a supported installation, batch processing, documented restoration tools, current plug-in support, or up to 32-channel files. And if the real requirement is multitrack arrangement, buses, instruments, or a layered mix, what you actually want is a DAW. *Do not buy an old Audio Studio key without verifying the exact edition, authorized installer and refund terms. Ask Boris FX to confirm upgrade eligibility for your purchase before paying. This is a source-based comparison, not a new hands-on benchmark.* ## What exists now? Boris FX [acquired Sound Forge from MAGIX on March 30, 2026](https://blog.borisfx.com/press/boris-fx-acquires-vegas-pro-sound-forge-and-acid-pro). Its current range has two editions: Sound Forge is the core editor, while Sound Forge Plus contains the same editor and adds Melodyne 5 Essential, Vandal, VariVerb II, and 3D Reverb. Audio Studio 17 belongs to the previous MAGIX consumer line. A 2023 release announcement from authorized Japanese publisher SourceNext names [Sound Forge Audio Studio 17](https://sourcenext.co.jp/pressrelease%5Fhtml/JS/2023/2023041801) alongside Pro 17 and Pro 17 Suite. MAGIX forum release notes also identify the 17.0.0.84 initial build and later 17.0.2.109 update. That is enough to verify the product and year without relying on reseller box copy. No Audio Studio 18 is announced in the current Boris FX product catalog or support transition material reviewed for this guide. That supports calling Audio Studio 17 the latest confirmed release, and one that sits outside the current lineup. It doesn’t prove that Boris FX can never reuse the Audio Studio name. ## Audio Studio 17 vs Sound Forge 2026 at a glance | Decision point | Audio Studio 17 | Sound Forge 2026 | | --------------------- | ----------------------------------------------------------------- | ------------------------------------------------------------------------- | | Product era | MAGIX release from 2023 | Current Boris FX release | | Current official sale | No current Boris FX product page | Official subscription, plan, and perpetual options | | Best fit | Existing owner with a stable basic single-file workflow | Current single-file editing, repair, mastering, and repeatable processing | | Batch processing | Not included in the documented Audio Studio edition matrix | Advertised and documented | | Channel support | Up to 6 channels; 32-bit float / 384 kHz in the documented matrix | Up to 32 channels | | Plug-in platform | VST2 and VST3; individual compatibility still needs testing | VST2, VST3, and ARA | | Downloads | Previous releases remain hosted by MAGIX | Installed through Boris FX Hub | | Account records | Retain original MAGIX purchase and registration | Boris FX account and Hub trial | | Update path | No current development promise found | Current Boris FX development and support | The [authorized SourceNext Audio Studio 17 matrix](https://www.sourcenext.com/product/vegas/sound/soundforge-audiostudio/) documents six-channel editing, 32-bit-float/384 kHz formats and VST2/VST3\. It marks Pro scripting, batch processing and RMS/loudness normalization as absent. Those are real edition differences, but they don't mean any microphone will record at the format limit. The page mixes older Pro labels with later bundle names, so rely on the dated release notes for launch extras and on your purchase record for entitlements. ## What Audio Studio 17 still does well Audio Studio 17 has more than a basic peak display. The [2023 launch announcement](https://sourcenext.co.jp/pressrelease%5Fhtml/JS/2023/2023041801) names loudness visualization and a mono-compatibility meter. [Release notes preserved by a MAGIX forum moderator](https://www.magix.info/us/forum/upgrade-read-me-s--1326636/) also describe true-peak display, coreFX Utility and Ozone 10 Elements in the initial release. Measuring loudness and automatically normalizing to a loudness target are different jobs, and an old bundle announcement doesn't create an entitlement today. For stereo editing with an existing VST2 or VST3 chain, you don't automatically need a newer version. The sharper upgrade questions are whether you need Pro batch processing, more than six channels, ARA, or a specific repair tool Audio Studio lacks. Check plug-in recall and the exported file; a plug-in showing up in a menu tells you much less. Owning a purchased version doesn't guarantee a working installation forever. Windows updates, audio drivers, installer access and third-party authorization are all separate dependencies. Keep the working system as it is and try copies of representative files before you replace it. ![Audio Studio 17 loudness view with a momentary loudness graph, M, S and I meters, and LRA and true-peak readouts](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/10/sf-audio-studio-17-loudness-view-v20261005.webp) Audio Studio 17 already had loudness visualization. This view belongs to that older product, not Sound Forge 2026. ## What Sound Forge 2026 adds Sound Forge 2026 continues the professional editor line rather than the old lower-cost Audio Studio tier. The [current product page](https://www.soundforge.com/sound-forge/) documents batch processing, noise reduction, clipping repair and recording up to 32 channels. The [edition matrix](https://www.soundforge.com/sound-forge/pricing/) lists VST2, VST3 and ARA support. Those are good reasons to try the current editor, but they don't prove your plug-in library will work without changes. Move for a specific capability. A newer version number on its own isn't a reason: - **Batch work:** apply repeatable processing and output settings across folders of files. - **Restoration:** use the currently documented DeClicker, DeCrackler, DeClipper, DeHisser, and broadband noise tools. - **Current plug-ins:** work with the advertised VST2, VST3, and ARA platform after testing your own library. - **Multichannel files:** open and process material with up to 32 channels when the file-based workflow requires it. - **Current support:** use the Boris FX account, Hub installer, and current support documentation. Sound Forge Plus doesn’t unlock a stronger core editor; it adds four named tools. Start with base Sound Forge unless Melodyne 5 Essential, Vandal, VariVerb II, or 3D Reverb has a defined place in the workflow. The detailed [Sound Forge vs Sound Forge Plus comparison](https://soundforgepro.com/sound-forge-vs-sound-forge-plus/) separates the editor from the bundle. The [current Sound Forge 2026 review](https://soundforgepro.com/sound-forge-pro-review-2026/) covers the practical strengths and limits of the core editor. ## What Sound Forge 2026 does not solve Sound Forge is still a specialist editor built around a single audio file. It handles events and multichannel files, but arranging a song or podcast across many tracks with buses, sends, instruments, comping and project-wide automation is a different kind of work. If Audio Studio feels limited because you are building layered sessions, the direct upgrade may preserve the category mismatch. Compare [Sound Forge with REAPER for multitrack production](https://soundforgepro.com/sound-forge-pro-vs-reaper/) or choose another DAW. If the work is a finished WAV that needs an exact cut, repair, level change, batch process, or delivery conversion, Sound Forge fits the job it was designed to do. ## Windows and Mac compatibility The [2023 Japanese Audio Studio 17 release announcement](https://sourcenext.co.jp/pressrelease%5Fhtml/JS/2023/2023041801) lists 64-bit Windows 10 and 11\. That's a historical regional specification, and it doesn't promise compatibility with every later driver or Windows update. The [current Sound Forge 2026 requirements](https://www.soundforge.com/sound-forge/system-requirements/) list Windows 11\. Neither source offers a current native Mac edition of these two products. A Mac-first buyer is better off comparing [native alternatives by workflow](https://soundforgepro.com/best-sound-forge-alternatives/) than treating an old Windows license as a Mac upgrade. For the broader buying decision, our [Sound Forge comparisons hub](https://soundforgepro.com/tag/comparisons/) separates edition changes from alternatives to the editor. Use this comparison when you already own Audio Studio; the Pro 18 and Plus comparisons start with different editions. ## Keep, move, or choose another editor ### Keep Audio Studio 17 Keep it when you already own a legitimate license, the current machine is stable, and a representative file moves from recording through export without a workaround. Archive the installer, serial, purchase record, presets, and a note with the working Windows and driver versions. ### Move to Sound Forge 2026 Move when a current support path, batch processing, restoration, 32-channel file support, or a required plug-in workflow solves a real job. Run the official trial with the exact interface, driver, VST folder, source files, output formats, and batch preset you expect to use. ### Choose another editor Choose a DAW for multitrack production. If the job is occasional trimming or conversion and the current Sound Forge price can’t be justified, a simpler editor covers it. The [Sound Forge alternatives guide](https://soundforgepro.com/best-sound-forge-alternatives/) compares Audacity, Acoustica, REAPER, Audition, RX, and WaveLab by work rather than feature count. ## License options and March 2026 price reference The [March 30, 2026 acquisition announcement](https://blog.borisfx.com/press/boris-fx-acquires-vegas-pro-sound-forge-and-acid-pro) lists these US launch prices. Treat them as a historical reference; a September checkout quote may differ. Monthly and annual subscriptions are separate from the perpetual purchase and from the eligibility-dependent Upgrade & Support offer. Check tax, currency, renewal settings and support terms in the offer you actually get. | License at launch | Sound Forge | Sound Forge Plus | | ---------------------- | ----------- | ---------------- | | Monthly subscription | $24.95 | $33.95 | | Annual subscription | $149.95 | $199.95 | | Upgrade & Support Plan | $189.95 | $249.95 | | Perpetual license | $299.95 | $399.95 | Check the [live Sound Forge pricing page](https://www.soundforge.com/sound-forge/pricing/) immediately before purchase. Our [Sound Forge pricing guide](https://soundforgepro.com/sound-forge-pro-pricing/) explains what the subscription, perpetual license, and Upgrade & Support Plan mean. A cheap legacy key carries different risks, so its sticker price isn’t a clean substitute for a current license. ## Does Audio Studio qualify for the upgrade price? Boris FX announced that MAGIX customers who own any previous version of Sound Forge could use a simplified upgrade price through December 5, 2026\. The public wording is broad, yet the transition FAQ reviewed for this guide doesn't name Audio Studio separately. Use the MAGIX purchase email when creating or checking the Boris FX account. Boris FX says previous registrations using the same email can appear in the account to streamline upgrade eligibility. A transferred registration doesn’t convert an Audio Studio serial into a current Sound Forge license, though. Before paying, ask Boris FX sales to confirm eligibility for your exact Audio Studio purchase, and save the answer. The [registration-transfer guidance](https://support.borisfx.com/hc/en-us/articles/44650701122829-Will-my-previous-registrations-transfer-to-Boris-FX) explains why old serials may show up in the current account. It doesn't show that every Audio Studio order qualifies for every current offer. ## Downloads, activation, and support for Audio Studio 17 Boris FX says that versions released before its 2026 line [continue to be hosted by MAGIX](https://support.borisfx.com/hc/en-us/articles/44650730285709-Where-can-I-access-my-existing-product-downloads). Sign in to the MAGIX account that owns the serial and look under registered products or downloads. Stay away from random installer mirrors: a modified package is a security problem, and it still won't give you a valid license. Keep the original Audio Studio purchase record and registered email. The [current trial instructions](https://vfx.borisfx.com/sound-forge-trial), by contrast, use a Boris FX account and Boris FX Hub. A trial account or a transferred old registration doesn't prove you've bought a 2026 license. Follow the instructions that came with your exact purchase. The current catalog shows an actively sold Sound Forge edition. It doesn't commit anyone to new maintenance for Audio Studio 17\. Don't buy a legacy copy expecting its bugs to get a fresh patch. Ask support about the exact version and problem before you replace a working setup. ## Should you buy an Audio Studio 17 key in 2026? The safe default is no unless the seller can prove a complete, transferable purchase. A marketplace listing can outlive the vendor catalog. A serial in a photo, a download link, or a sealed-looking box does not prove that the license is unused, transferable, compatible with the installer, or recoverable in a MAGIX account. Require all four items before considering payment: - The exact product name and edition: Sound Forge Audio Studio 17, not Pro 17 or a bundled voucher. - A legitimate serial with a documented transfer or unused registration state. - Access to the official MAGIX-hosted installer for that SKU and language. - A refund path if activation fails on the intended machine. Don’t value the listing by bundled plug-in names until those entitlements appear in the account. Old promotions changed by country, retailer, and date. If a working editor matters more than collecting a legacy license, test current Sound Forge or a current alternative instead. ## A low-risk migration test The [official Sound Forge trial](https://vfx.borisfx.com/sound-forge-trial) offers 15 days on Windows, so prepare a test pack before you start it. Work on copies, write outputs to a different folder, and keep the working Audio Studio installation until the replacement has proved itself. 1. One file recorded through the interface and driver you use every day. 2. One damaged or noisy file for the restoration tools you actually need. 3. One VST2 or VST3 chain with saved presets and a known reference render. 4. One folder for batch processing with the required naming and output formats. 5. One multichannel file if channel count is part of the reason for moving. 6. One final export checked for sample rate, bit depth, metadata, loudness, and playback. If the paid entitlement, installer, or upgrade state contradicts the account, capture the receipt, serial or order reference, account email, product listing, and exact message. Send that evidence through [Boris FX technical support](https://support.borisfx.com/hc/en-us/articles/10370509834893-How-do-I-contact-technical-support) instead of changing a known-good legacy installation. ## Frequently Asked Questions ### Is Sound Forge Audio Studio discontinued? Audio Studio is absent from the current Boris FX lineup, and version 17 is the latest confirmed release found in official and authorized release material. Calling it a legacy product is supported. A permanent end to the name has not been formally announced in the sources reviewed. ### Is there a Sound Forge Audio Studio 18? No Audio Studio 18 has been announced in the current Boris FX catalog or transition documentation reviewed for this guide. Sound Forge Pro 18 was a separate MAGIX professional product. The current Boris FX editor is Sound Forge 2026. ### Can I still use Sound Forge Audio Studio 17? Yes, if the legitimate license activates and the installed build works with the current Windows system, interface driver, and plug-ins. Back up the installer, serial, purchase record, and presets before moving to another computer. ### Can I still download Audio Studio 17? Boris FX says releases before the 2026 line continue to be hosted by MAGIX. Use the MAGIX account that owns the product. Avoid unofficial installer mirrors and contact support if the registered download is missing. ### Is Audio Studio 17 the same as Sound Forge 2026? No. Audio Studio 17 was the MAGIX consumer edition. Sound Forge 2026 continues the current professional single-file editor with documented batch processing, restoration, VST2, VST3, ARA, and support for files with up to 32 channels. ### Does Audio Studio qualify for the Sound Forge upgrade? The public offer says owners of any previous Sound Forge version can upgrade through December 5, 2026, but Audio Studio is not named separately in the reviewed support wording. Ask Boris FX sales to confirm the exact serial before relying on the price. ### Should an Audio Studio owner buy Sound Forge or Sound Forge Plus? Start with base Sound Forge unless Melodyne 5 Essential, Vandal, VariVerb II, or 3D Reverb is required. Plus adds those four tools to the same core editor. ### Will Sound Forge 2026 replace a multitrack DAW? No. Sound Forge is built around precise file editing, repair, mastering, and repeatable processing. Use a DAW for layered tracks, buses, instruments, comping, and project-wide mixing. *Sources checked September 14, 2026\. Historical Audio Studio features and regional bundles are separated from current Boris FX offers.* ### Sound Forge Activation Failed: License, Sign-In, and Upgrade Fixes URL: https://soundforgepro.com/sound-forge-activation-failed/ Last updated: 2026-10-06T06:55:17.000Z **A Sound Forge activation failure has at least five different meanings.** Current standalone Sound Forge uses a Boris FX login license, while the copy bundled with [Samplitude Suite](https://soundforgepro.com/sound-forge-in-samplitude-suite/) activates through its host. MAGIX, Sony, and Steam releases keep version-specific systems. Pick the wrong branch and a valid license can look broken. Start with the product name, version, purchase route, and exact message, and don't reinstall, remove a computer, or enter an old serial until those four facts agree. The quick current standalone fix is Boris FX Hub > Sign in > Use on This Computer. That sequence doesn't apply to every Sound Forge copy. *Scope: Sound Forge 2026 standalone and trial, Samplitude Suite or Sequoia bundles, MAGIX Pro 12 to 18, Sony 11 and earlier, and Steam-specific errors. Last fact-checked September 4, 2026\. Open the* [Sound Forge troubleshooting hub](https://soundforgepro.com/tag/troubleshooting/) *for installation and startup branches.* ## Choose the Sound Forge license generation first | Copy you own | Activation route | Do not use | | ----------------------------------------------------- | --------------------------------------------------------- | ---------------------------------------------- | | Current standalone Sound Forge or Plus | Boris FX account, then Use on This Computer | Old MAGIX or Sony serial | | Sound Forge included with Samplitude Suite or Sequoia | Hub > host product > Manage Extras; host-based activation | Standalone Sound Forge login-license diagnosis | | MAGIX Sound Forge Pro 12 to 18 | Serial and the registered email for that release | Current Boris FX login license as a substitute | | Sony Sound Forge 11 or earlier | Sony-era serial and online or computer-ID flow | Current Hub activation | | Steam edition | Exact Steam SKU and version-specific procedure | Retail instructions from another edition | If the title bar won't open, use the purchase receipt, installer name, Steam library entry, or account product listing. Error codes alone aren't enough, because the same number can surface in different legacy builds. ![Sound Forge 2026 Samplitude Suite MAGIX Sony and Steam licensing generations compared](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/08/generation-desktop.webp) Choose the instructions that match how the specific Sound Forge copy was licensed. ## Activate current standalone Sound Forge 2026 Boris FX states in its [current Sound Forge licensing article](https://support.borisfx.com/hc/en-us/articles/44687772090253-How-does-licensing-work-for-Vegas-Pro-and-Sound-Forge) that Vegas Pro and Sound Forge use login licensing. The license is tied to the Boris FX account, and the normal online setup needs no activation key. Open Boris FX Hub and sign into the email address used for the purchase. 1. Open Boris FX Hub and confirm the signed-in email matches the purchase receipt. 2. Find Sound Forge or Sound Forge Plus and verify the edition. 3. Choose Use on This Computer. 4. Launch Sound Forge and confirm the paid product opens instead of the trial. The distinction between signing in (step 1) and Use on This Computer (step 3) matters. Boris FX's [sign-in and login-license explanation](https://support.borisfx.com/hc/en-us/articles/44687987049741-What-s-the-difference-between-signing-in-and-using-a-login-license) says that signing in gives access to the account, while Use on This Computer activates the login license. An account avatar or visible product name doesn't prove the machine has been assigned. ![Current standalone Sound Forge activation flow from Boris FX sign-in to Use on This Computer](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/08/standalone-desktop.webp) For current standalone Sound Forge, signing in opens the account; Use on This Computer assigns the license. ## Signed in but Sound Forge still opens in trial mode The [official Sound Forge trial](https://vfx.borisfx.com/sound-forge-trial) lasts 15 days and installs through Boris FX Hub. A paid entitlement can coexist with a trial state until the login license is assigned. Return to the product entry and look for Use on This Computer, then close and reopen Sound Forge. If the account lists the paid product and the current computer, but the application still shows Trial, stop repeating sign-in. Capture the account product page, active-computer list, Hub product entry, and in-app message, then send that evidence through [Boris FX technical support](https://support.borisfx.com/hc/en-us/articles/10370509834893-How-do-I-contact-technical-support). A different serial isn't the fix for the current login-license state. ## Purchased license does not appear in Boris FX Hub Compare the Hub email with the receipt. Then verify the exact item: Sound Forge, Sound Forge Plus, an upgrade, a trial, or a bundle. Boris FX's [account rule](https://support.borisfx.com/hc/en-us/articles/44687905423117-Can-I-have-more-than-one-license-on-the-same-account) allows one login license per product on an account. If a studio needs independent users, its [multiple-license guidance](https://support.borisfx.com/hc/en-us/articles/44687788159501-What-if-I-need-multiple-licenses) points to separate accounts or sales-provided Activation Keys rather than stacking users onto one login license. Previous MAGIX registrations can appear in a Boris FX account when the same email is used, but the purpose is to streamline upgrades. The [registration-transfer guidance](https://support.borisfx.com/hc/en-us/articles/44650701122829-Will-my-previous-registrations-transfer-to-Boris-FX) does not turn an old Pro 18 serial into a current login license. Keep the order confirmation and original purchase email for support. ## Activate Sound Forge bundled with Samplitude Suite This is a separate path. Boris FX says Sound Forge included with Samplitude Suite or Sequoia is installed from Boris FX Hub by opening the relevant host product and choosing Manage Extras. It then activates automatically through the Samplitude host and its serial. No additional Sound Forge activation code is required. Use that route only for an eligible bundle. Boris FX's current [Samplitude product page](https://borisfx.com/products/samplitude) lists Sound Forge with Samplitude Suite, not standard Samplitude. If the extras list is empty, verify the host edition and purchase account before treating Sound Forge as a standalone entitlement. The exact steps are in the official [third-party software installation and activation article](https://support.borisfx.com/hc/en-us/articles/38965048376589-Installation-and-Activation-Third-Party-Software). Do not use the standalone Use on This Computer flow to diagnose a bundled copy unless Boris FX support confirms a separate standalone entitlement also exists. ![Samplitude Suite Sound Forge route through Boris FX Hub and Manage Extras](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/08/bundle-desktop.webp) Bundled Sound Forge is installed under Samplitude or Sequoia Manage Extras and activates through the host. ## No available computers left on a current login license Boris FX allows a current login license on up to two computers, such as a desktop and laptop, for one user. The company says the license is not intended for simultaneous use on multiple computers. If both computer slots are occupied, remove a retired machine in the Boris FX account, then use the license on the new computer. 1. Open the active-computer management page in the Boris FX account. 2. Identify the retired or unavailable machine by name and recent use. 3. Remove that machine to free a current login-license slot. 4. Return to Hub on the new computer and choose Use on This Computer. The [two-computer policy](https://support.borisfx.com/hc/en-us/articles/44746837385485-Can-I-use-my-login-license-on-more-than-one-computer) and [move-a-license procedure](https://support.borisfx.com/hc/en-us/articles/44688004823053-How-do-I-move-my-login-license-to-another-computer) apply to the current Boris FX login license, and they're different from legacy P2 and P3 activation limits. ## Current Sound Forge on an offline workstation The standard login-license setup is online. Boris FX says users who need offline activation or another licensing arrangement should request an Activation Key through sales. The key is tied to one computer and is normally used for special cases; it's different from a MAGIX or Sony serial. Plan the request before isolating the workstation. The official [Activation Key guidance](https://support.borisfx.com/hc/en-us/articles/44687933586317-Can-I-still-use-an-Activation-Key) doesn't promise a self-service conversion for every retail account. ## Legacy MAGIX and Sony activation failures An old license remains valid for the product and release it was issued for. Boris FX says in its [MAGIX lifetime-license guidance](https://support.borisfx.com/hc/en-us/articles/44650605900301-What-happens-to-my-existing-lifetime-license-purchased-from-MAGIX) that an existing license remains valid under MAGIX and can establish upgrade eligibility. It doesn't, however, unlock the current release. Keep the exact product name, version, edition, installer source, serial prefix, and registered email together. Never post the serial publicly or buy a resale key without a documented account transfer. Use the [MAGIX upgrade procedure](https://support.borisfx.com/hc/en-us/articles/44650911032845-How-do-I-upgrade-from-a-MAGIX-version-to-a-Boris-FX-version) when the goal is a current Boris FX release rather than recovery of the old installation. ## Error -14: wrong product or localized version Boris FX defines legacy Error -14 narrowly: the serial belongs to a different product or to a localized or region-specific version. Check whether the key is for Sound Forge Pro or Audio Studio and whether the installer matches its localized release. The [official Error -14 article](https://support.borisfx.com/hc/en-us/articles/43420648093581-What-should-I-do-if-Error-code-14-appears-when-activating-the-program) doesn't direct users to generate a replacement key. ## Error -24: registered email mismatch Error -24 belongs to the legacy serial system. Boris FX's [official Error -24 guidance](https://support.borisfx.com/hc/en-us/articles/43612409262605-Error-24-when-activating) says the entered email differs from the email used for a previous activation of that serial. Sign into the MAGIX account, update or confirm the registered email, then retry with the matching address. If the original account is inaccessible, contact support with proof of purchase. ## Error -58: preserve the full legacy message Error -58 appears in legacy Sound Forge activation results, but no current public Boris FX article reviewed for this page defines one universal Sound Forge cause. Treat it as a legacy branch rather than a 2026 Hub error. Record the full message, product version, installer source, whether a retailer supplied a voucher or a serial, and the registered email. Do not apply an Error -59 folder cleanup based on the number alone. ## Error -59, 16xx, or Account already exists Boris FX groups these legacy messages in one cleanup article. Its procedure is to uninstall the affected software in Control Panel, delete only that product's remaining folders under C:\\ProgramData\\MAGIX\\\[Software\_Name\] and C:\\Users\\\[Username\]\\AppData\\Roaming\\MAGIX\\\[Software\_Name\], then reinstall from the download version in the Service Center account. If the activation dialog does not appear, choose Help > Register Online. Back up presets and confirm the folder contains the exact affected product before removal. Do not delete the entire MAGIX directory or reuse this process for current Sound Forge 2026\. Follow the scoped paths in the [official -59, 16xx, and account-exists procedure](https://support.borisfx.com/hc/en-us/articles/43439967069197-How-do-I-troubleshoot-Error-59-16xx-and-Account-already-exists). ## Steam Error -59 or missing executable Steam editions need their own route because the package layout and entitlement differ by SKU. Boris FX lists missing files, Missing Executable, Error -59, and Error 2 among Steam installation problems. Its first procedure is to uninstall through Steam, uninstall the same software in Windows Apps, restart, then reinstall from the Steam library. If that fails, the official [Steam-specific installation article](https://support.borisfx.com/hc/en-us/articles/43612938524557-How-can-installation-errors-with-Steam-versions-be-resolved) documents an additional file-location procedure. Use its paths only for the named Steam product. A retail serial, standalone 2026 login license, or forum workaround for a different bundle isn't interchangeable with the exact Steam SKU. ## Maximum number of activations reached on a legacy product This message doesn't automatically mean the current two-computer login-license limit. Boris FX says legacy products can use P2 or P3 serial policies. For P2, customer service increases the preliminary activation limit. For P3, the user manages a limited number of activation slots, typically two for regular consumer products, through Help deactivation or the online account. If the old computer is dead, the P3 account route can free its slot. With P2, contact support with the product name instead. The controlling [maximum-activation article](https://support.borisfx.com/hc/en-us/articles/43454503322765-What-can-I-do-when-I-get-the-Maximum-number-of-activations-reached-message) specifically says to distinguish the licensing generation before acting. ![Current Boris FX computer limits compared with legacy Sound Forge P2 and P3 activation slots](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/08/limits-desktop.webp) Current login-license computers and legacy P2 or P3 activation slots are managed differently. ![Legacy Sound Forge error routes for minus 14 minus 24 minus 59 maximum activations and Steam](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/08/errors-desktop-1.webp) Legacy error codes require legacy fixes and do not describe the current 2026 login license. ## Sound Forge 11 and earlier offline activation Boris FX documents a computer-ID process for Sony Creative Software-era Sound Forge 11 and earlier. Launch the installed product and attempt activation. If online activation fails, the legacy application can expose its serial and computer ID after repeated attempts. Use an internet-connected device to generate the activation code for that computer, then enter it on the offline machine. Follow the [official Sony-era offline activation instructions](https://support.borisfx.com/hc/en-us/articles/43368494549261-How-do-I-do-an-offline-activation-of-older-versions-of-Sony-Creative-Software-era-products) because the fields and eligibility are version-specific. This process does not activate Sound Forge 2026, Pro 18, or a Steam edition. ## Activation worked but Sound Forge will not open Once Hub shows the current license assigned and the Boris FX account lists the computer, a launch crash is a different layer. Preserve the working license state and use the [Sound Forge startup-crash workflow](https://soundforgepro.com/sound-forge-pro-wont-open-crashes-startup/). If Hub never completed the product installation, use the [Boris FX Hub installation-failure guide](https://soundforgepro.com/sound-forge-installation-failed/). Separating activation, installation, and startup avoids damaging a layer that already works. ## The safe Sound Forge activation fix order Use this sequence before reinstalling. It's also the visible HowTo sequence represented in this page's structured data. 1. Record the exact product, version, purchase route, signed-in email, and full error message. 2. Classify the copy as current standalone, Samplitude Suite bundle, MAGIX, Sony, or Steam. 3. For current standalone Sound Forge, sign into the purchase account and choose Use on This Computer. 4. For Samplitude Suite or Sequoia, open the host product in Hub and choose Manage Extras. 5. For a current computer limit, remove the retired computer in the Boris FX account and assign the new one. 6. For a legacy error, match -14, -24, -58, -59 or 16xx, Steam, and P2 or P3 limits to the exact version-specific route. 7. Retry once, then send the receipt, screenshots, exact message, and version details to Boris FX support if the state remains contradictory. ## Frequently Asked Questions ### Why am I signed in but Sound Forge still says Trial? Signing in opens the Boris FX account. For current standalone Sound Forge, return to Hub and choose Use on This Computer to assign the paid login license. If the account and active-computer list already show the assignment, capture both screens and contact support. ### Does Sound Forge 2026 use a serial number? The normal current standalone setup does not. Boris FX uses a login license tied to the purchase account. Samplitude Suite bundles, older MAGIX releases, Sony releases, and some Steam editions follow different version-specific routes. ### How do I activate the Sound Forge copy included with Samplitude Suite? Open Boris FX Hub, select the relevant Samplitude or Sequoia product, and choose Manage Extras. Boris FX says bundled Sound Forge activates through the host and its serial, with no separate Sound Forge activation code. ### Can I activate current Sound Forge on two computers? Yes, for one user. Boris FX permits a login license on up to two computers and says it is not intended for simultaneous use on multiple computers. ### Can a Sound Forge Pro 18 serial activate Sound Forge 2026? No. It remains valid for the Pro 18 product it was issued for and may confirm upgrade eligibility, but it does not become a current Boris FX login license. ### What does Sound Forge Error -14 mean? For legacy serial products, Boris FX says the serial belongs to a different product or a localized or region-specific version. Match the installer and product to the license. ### What does Sound Forge Error -24 mean? For legacy products, the activation email does not match the email previously registered to that serial. Confirm or update the address in the MAGIX account before retrying. ### What should I do with Steam Error -59? Use the Boris FX Steam-specific procedure for the exact SKU. It begins with uninstalling through Steam and Windows Apps, restarting, and reinstalling from the Steam library. Do not substitute instructions for a retail or current standalone copy. ### Can current Sound Forge be activated offline? Boris FX handles special current offline setups through an Activation Key requested from sales. The key is tied to one computer and is different from a legacy MAGIX or Sony serial. ## Related Sound Forge licensing and setup guides - [Test the current Sound Forge trial without wasting the 15-day window](https://soundforgepro.com/sound-forge-pro-free-trial-whats-included-and-how-long-it-lasts/) - [Fix a failed Sound Forge installation in Boris FX Hub](https://soundforgepro.com/sound-forge-installation-failed/) - [Fix Sound Forge startup crashes after activation](https://soundforgepro.com/sound-forge-pro-wont-open-crashes-startup/) - [Check whether Sound Forge Pro 18 still fits the job](https://soundforgepro.com/sound-forge-pro-18/) - [Compare current Sound Forge pricing and editions](https://soundforgepro.com/sound-forge-pro-pricing/) - [Open the Sound Forge troubleshooting hub](https://soundforgepro.com/tag/troubleshooting/) *Last fact-checked: September 4, 2026 against current Boris FX licensing, bundle, legacy, Steam, and offline-activation documentation.* ### Sound Forge Installation Failed: Boris FX Hub and Setup Fixes URL: https://soundforgepro.com/sound-forge-installation-failed/ Last updated: 2026-10-06T07:11:05.000Z **If Sound Forge installation failed, save the exact error before retrying.** A stalled Boris FX Hub download, a Windows Installer error and an activation refusal need different fixes. Identify where setup stopped, check the matching branch below, then make one controlled retry. Keep your firewall and antivirus enabled. This guide covers current Sound Forge 2026 on Windows 11, plus clearly marked Sony/MAGIX legacy cases. If you haven't started setup yet, use the [normal Sound Forge installation walkthrough](https://soundforgepro.com/how-to-install-sound-forge-pro/). If the application opens but refuses a license, treat that as an activation problem instead of reinstalling. For other symptoms, start with the [Sound Forge troubleshooting hub](https://soundforgepro.com/tag/troubleshooting/). ## Diagnose the failed layer before retrying | What happened | What to check | | ------------------------------------------------------- | --------------------------------------------------------------------------------------------------- | | Sound Forge is missing from Hub | Account, edition and standalone versus bundle route. Absence does not prove corrupt installation. | | Download stalls or the package cannot open | Official source, package access and the documented Hub network destinations. | | HRESULT -2147024769 or sfvstwrap.dll failed to register | The Sound Forge redistributable repair procedure. Identify the required package before changing it. | | An MSI error number appears | The exact code and log. Error 1603 alone does not identify a cause. | | Setup finishes, but the program crashes | Startup diagnostics rather than another installation. | Take a screenshot or copy the whole message, including the DLL filename, progress stage and time. Record the product edition, installer source and Hub version if visible. Keep account email, serial numbers and logs out of public posts. ## Check Windows, storage and restart state The [current vendor requirements](https://www.soundforge.com/sound-forge/system-requirements/) list Windows 11, a 1.4 GHz processor, 2 GB RAM with 8 GB recommended, and 1,100 MB for Sound Forge or 1,400 MB for Sound Forge Plus installation. Those are application specifications. They aren't the complete requirements for a Windows PC, so check our [Windows and Sound Forge requirements comparison](https://soundforgepro.com/sound-forge-pro-system-requirements/) before you decide an older machine qualifies. Leave extra space for temporary extraction, updates, plug-ins and audio files. The vendor's program-size figure doesn't promise that an almost-full system drive can finish setup. If storage is tight, move your own backed-up files and leave the installer caches alone. On Windows 11, open **Start > Settings > Windows Update**, check the update state and complete a requested restart after saving your work. Microsoft documents that path in its [Windows Update instructions](https://support.microsoft.com/en-us/windows/deployment/updates-lifecycle/windows-update-faq). Record your exact Windows version with **Windows+R > winver.exe**; Microsoft's [version-identification instructions](https://learn.microsoft.com/en-us/dotnet/framework/install/dotnet-35-windows-11#how-to-determine-which-version-of-windows-youre-using) explain that check. A Windows version number matters particularly for legacy .NET prerequisites. ## Choose the current or legacy installation route For current standalone Sound Forge, use the [official Sound Forge trial and Hub page](https://vfx.borisfx.com/sound-forge-trial) or your official purchase download. The trial page routes installation through Boris FX Hub and offers a 15-day Windows trial without a credit card. You don't need to buy a license just to diagnose a failed trial installation. For an eligible Samplitude Suite bundle, check the Samplitude product entry in Hub and **Manage Extras**. Boris FX documents bundled content under the host product in its [audio-product installation instructions](https://support.borisfx.com/hc/en-us/articles/44321380285197-How-do-I-install-Samplitude-Sequoia-Music-Studio). Our [Sound Forge in Samplitude Suite guide](https://soundforgepro.com/sound-forge-in-samplitude-suite/) covers that separate workflow. Do not assume every Samplitude edition includes Sound Forge or substitute a standalone trial for a missing purchased bundle. If a purchased product is absent, compare the signed-in account and exact edition with your receipt. Ask Boris FX to resolve a missing purchase record. Do not change license assignments, create duplicate accounts or paste an old serial into unrelated software as an installation test. For Sony or MAGIX releases, identify the exact version and get its matching installer through the vendor's legacy support route. A current Hub download won't stand in for the installer of every historical edition. Keep a working older installation until you know whether setup reports a specific conflict. ## Handle a stalled or damaged download First distinguish *downloading* from an installer that has already launched. If setup or Windows Update is still working, let it finish. Do not force-stop Windows Installer to reset a progress bar. For a failed download with no active setup, note the state, close Hub normally and reopen it for one attempt from the official source. If you downloaded a separate package, get a fresh copy from the vendor, never from a DLL site or a repackaged installer. Try a normal browser download without an optional download accelerator. This is a controlled download check; it doesn't show that the network caused your error. If Windows reports an unknown publisher, a security detection or a policy block, stop and verify the download with the vendor or your administrator. Do not override the warning merely because a forum says to run setup as administrator. ## Check Hub networking without disabling security Boris FX says Hub needs an internet connection. Its [Hub firewall reference](https://support.borisfx.com/hc/en-us/articles/20359074635277-How-can-I-use-the-Hub-behind-a-firewall), updated June 30, 2026, specifies domain-based rules because service IP addresses change: - `borisfx.com`, TCP 443: product metadata. - `borisfxdownloads.com` and `cdn.borisfx.com`, TCP 443: product installers. - `backend.borisfx.com`, TCP 443: authentication and account management. - `bfxlive.borisfx.com` and `bfxlivefrontend.borisfx.com`, TCP 443: login-license communication. - `activation.genarts.com`, TCP 80: the license-activation destination in the general Hub reference. - `borisfx-com-res.cloudinary.com`, TCP 443: Hub images. This is the vendor's general Hub list, and it doesn't prove every Sound Forge installation uses every licensing endpoint. Give it and the failure time to your network administrator so they can check the relevant outbound access. Google sign-in also needs Google's resources, as the same reference explains. Do not open inbound ports, remove a managed proxy or bypass workplace filtering yourself. A browser reaching the website doesn't mean Hub can reach its download service. ## Handle administrator prompts and policy blocks Microsoft explains that [User Account Control](https://support.microsoft.com/en-us/windows/security/user-account-control-settings) requests approval when an action needs administrator-level permissions. Approve only an expected installer from a source you have verified. If you cannot provide the required authorization on a managed PC, ask its administrator to perform the installation. Keep UAC enabled. Elevation is not a repair for a damaged package, an unsupported Windows version or missing account entitlement. Likewise, do not give Everyone full control of a drive to work around an access error. An administrator should investigate permissions on the exact failing location, using the installer log. ![Windows 11 User Account Control prompt with the app name, verified publisher, Show more details link and Yes button marked](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/09/sf-install-uac-prompt-checks.webp) Before choosing Yes, confirm that the app name and verified publisher match the installer you started. ## Repair HRESULT -2147024769 or sfvstwrap.dll registration errors Boris FX has a [Sound Forge-specific redistributable repair procedure](https://support.borisfx.com/hc/en-us/articles/43615168155533-What-should-I-do-if-the-error-HRESULT-2147024769-or-sfvstwrap-dll-failed-to-register-appears-during-installation) for these messages. It says to install the correct Microsoft redistributable if missing, then open **Control Panel > Programs and Features**, select that redistributable and choose **Change > Repair**. The article notes that uninstalling and reinstalling may not correct this particular problem. The error title doesn't point to one universal Visual C++ year or architecture. Note the installed Sound Forge version and check its log or support before choosing the package. Boris FX mentions VS2012 and VS2008 as examples of dependencies some features use; that isn't an instruction to install both for every 2026 failure. Microsoft's [Visual C++ Redistributable guidance](https://learn.microsoft.com/en-us/cpp/windows/latest-supported-vc-redist?view=msvc-170) says the package architecture must match the application target. Its current v14 package does not replace every older runtime generation; older packages can coexist. Do not remove all Visual C++ entries to make the list look tidy. If Windows names a missing DLL instead, copy its exact filename. A missing runtime file and an application DLL that failed registration are two different diagnoses. Do not download a loose DLL, copy one into System32, or run registration commands at random. Repair only the dependency or product that reliable evidence points to, and escalate if it's unclear. ## Legacy installers asking for .NET Framework A [2022 Sound Forge 10 forum report](https://www.magix.info/us/forum/error-during-soundforge-10-installation--1294442/) describes setup stopping while it tried to install .NET Framework 2.0\. That's historical evidence of one legacy failure. It isn't a prerequisite list for current Sound Forge. Microsoft's [.NET Framework 3.5 instructions](https://learn.microsoft.com/en-us/dotnet/framework/install/dotnet-35-windows) explain that .NET Framework 4 doesn't support applications built for Framework 1.1 through 3.5. **Use this branch only when the legacy installer or vendor identifies that dependency.** On Windows 11 25H2 and earlier, Microsoft provides .NET Framework 3.5 as an optional Windows component. Search Start for **Windows Features**, open **Turn Windows features on or off**, select **.NET Framework 3.5 (includes .NET 2.0 and 3.0)** and follow the prompts. Restart if requested. Do not select unrelated WCF features. ![Windows Features dialog with .NET Framework 3.5 selected and both Windows Communication Foundation items left clear](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/09/sf-install-windows-features-net35.webp) This optional-component route applies to Windows 11 25H2 and earlier; 26H1 and later use Microsoft’s standalone installer instead. **Windows 11 26H1, build 28000, and later use a different route.** Microsoft says .NET Framework 3.5 is available only as a standalone installer there. Follow its [version-specific Windows 11 instructions](https://learn.microsoft.com/en-us/dotnet/framework/install/dotnet-35-windows-11); the installer works only with the Windows version specified. Do not reuse old Windows Features or DISM instructions on that branch. Installing a prerequisite does not certify Sound Forge 10 as supported on a modern Windows release. ## Read the Windows Installer code The following meanings come from Microsoft's [MsiExec error-code reference](https://learn.microsoft.com/en-us/windows/win32/msi/error-codes). Use them when the number is actually a Windows Installer result, not merely a similarly numbered Hub message. | Code | Meaning | Next action | | ---- | -------------------------------------------- | -------------------------------------------------------------------------------------------- | | 1603 | Fatal installation error | Keep the log and identify the failing action; the code alone is not a diagnosis. | | 1612 | Installation source unavailable | Ask the vendor for the matching source or recovery procedure; do not fabricate a cache file. | | 1618 | Another installation is in progress | Let it complete. Finish any requested restart before the next attempt. | | 1619 | Package could not be opened | Verify the package exists and is accessible; obtain a valid copy from the vendor. | | 1622 | Installation log could not be opened | Choose an existing, writable log location. | | 1625 | Installation forbidden by system policy | Contact the administrator; do not bypass policy. | | 1632 | Temp folder full or inaccessible | Check available space and access to that temporary location. | | 1633 | Package unsupported on this platform | Check the OS, architecture and installer generation with the vendor. | | 1638 | Another version of this product is installed | Identify the conflicting product before choosing its supported repair or removal route. | | 3010 | Success; restart required | Save work and restart to complete installation. | Microsoft's [1603 troubleshooting article](https://learn.microsoft.com/en-us/troubleshoot/windows-server/application-management/msi-installation-error-1603) lists possible conditions, including an already-installed application, an encrypted destination, a substitute drive and insufficient SYSTEM permissions. Its stated scope is Windows 10\. Treat those as questions for an administrator reading the log. They don't prove the cause on your Windows 11 machine, and they're no reason for broad permission changes. ## Keep installer caches and existing work intact Microsoft explicitly says not to delete `C:\Windows\Installer`. Its [Windows Installer cache guidance](https://learn.microsoft.com/en-us/troubleshoot/windows-client/application-management/missing-windows-installer-cache) explains that these files are needed for later repair, removal and updates, and cannot simply be copied from another computer. Do not erase ProgramData, AppData, registry branches or all temporary folders to fix an unnamed failure. Do not treat a Hub cache and the Windows Installer cache as interchangeable. If support requests a reset, get the exact product, folder and procedure, preserve the relevant files, and wait for active setup to finish before resetting anything. Back up presets and your own work before any approved product removal. If setup reports success, check whether Sound Forge shows up in Start. If it launches, don't reinstall just because a Hub display looks stale. If it crashes at launch, move to the [Sound Forge startup-crash guide](https://soundforgepro.com/sound-forge-pro-wont-open-crashes-startup/). A license refusal after launch belongs with activation support, and this installer sequence won't fix it. ## Collect Hub logs or a vendor-requested MSI log With the Hub window active on Windows, press **Control+Shift+L**. Boris FX's [Hub diagnostic instructions](https://support.borisfx.com/hc/en-us/articles/20512057218829-I-have-run-into-some-trouble-things-aren-t-working-and-I-m-seeing-strange-error-messages-Please-help) say this saves logs to the desktop. Include the reproduction steps with a private support ticket. If support gives you an actual `.msi` package and asks for a verbose log, Microsoft documents `/i` for installation and `/L*V` for logging. This [MsiExec command syntax](https://learn.microsoft.com/en-us/windows-server/administration/windows-commands/msiexec) is not a logging switch for a Hub `.exe`: ``` msiexec.exe /i "C:\path\vendor-package.msi" /L*V "C:\path\install.log" /norestart ``` **This command starts an installation.** Replace both example paths with the vendor-approved package and an existing writable log destination; do not run it alongside Hub setup or extract an MSI from a bundle without instructions. `/norestart` prevents an automatic restart, but a requested restart still needs completing later. Keep the normal installer prompts visible. If you are unsure which package to use, send Hub logs instead. Your support ticket should contain the product version and edition, Windows version, failure time, exact message, official download source, and the result of the one targeted retry. Attach logs privately after checking them for personal information. State what changed and what didn't; that helps support far more than saying you tried everything. ## The safe retry sequence 1. Save the exact error, product edition, Windows version and failure time. 2. Check the supported platform, available storage and pending restart state. 3. Confirm the matching standalone, bundle or legacy installer route. 4. Use the relevant error branch; obtain administrator help for policy or permission blocks. 5. Make one targeted correction without disabling security or deleting shared caches. 6. Retry once after other setup has finished, then send Hub logs to support if the same failure returns. ## Frequently asked questions ### Does error 1603 mean Sound Forge is already installed? No. Windows Installer defines 1603 as a fatal installation error. An existing installation is one possible condition in Microsoft's troubleshooting guidance, but the exact failing action and log are needed to investigate your case. ### Should I run everything as administrator? No. Approve expected permission requests only for verified installers. Elevation cannot fix a corrupt package or missing purchase entitlement. If a managed PC blocks installation, ask its administrator rather than disabling UAC or changing broad permissions. ### Should I remove all Visual C++ Redistributables? No. For HRESULT -2147024769 or sfvstwrap.dll registration failures, Boris FX documents repairing the correct redistributable through Programs and Features, Change, Repair. Identify the required version and architecture rather than removing shared packages. ### Does current Sound Forge require .NET Framework 3.5? This guide does not establish that as a current requirement. The .NET branch addresses a dependency identified by a legacy installer or vendor. Windows 11 25H2 and earlier use an optional component; 26H1 and later require Microsoft's version-specific standalone installer. ### Can I delete the Windows Installer folder to retry? No. Microsoft says not to delete C:\\Windows\\Installer because its cached files are needed for repair, updates and removal. For a missing installation source, ask the application vendor for the matching recovery procedure. ### Can I use Boris FX Hub on an offline workstation? Boris FX says Hub requires an internet connection. Ask the vendor about an approved installation and licensing arrangement for your exact edition before isolating the workstation. Do not assume a legacy offline activation procedure applies to current Sound Forge. ### What should I send support when the same error returns? Send the product edition and version, Windows version, exact error, failure time, reproduction steps and result of one targeted retry. Export Hub logs with Control+Shift+L while Hub is active and attach them privately to the support ticket. *Documentation checked September 14, 2026\. These are source-based troubleshooting instructions, not a claim that every error was reproduced on a Windows test machine.* ### Sound Forge Pro Won't Open: Startup Crash Fixes (2026) URL: https://soundforgepro.com/sound-forge-pro-wont-open-crashes-startup/ Last updated: 2026-10-09T21:58:10.000Z **If Sound Forge won't open, record where startup stops before reinstalling or resetting anything.** Launch the installed application once without double-clicking an audio file. Note whether no window appears at all, the splash screen freezes, or the workspace opens and then closes. A plug-in or driver name on screen is a lead; it doesn't prove the cause. Start with the Windows failure record. Then test the relevant branch: activation, one file, plug-in scanning, audio initialization or per-user settings. Change one thing per attempt and keep a short result log. Stop when you have a repeatable lead; you don't need to complete every fix. This guide covers Windows startup diagnosis for Sound Forge 2026, with older Sony/MAGIX cases kept clearly separate, and it belongs to the [Sound Forge troubleshooting hub](https://soundforgepro.com/tag/troubleshooting/). The diagnostic steps come from documentation. ## Identify the startup symptom first - **No visible window:** check whether the installed app starts from the Windows Start menu rather than an old desktop shortcut. Look for its process in Task Manager and check for a dialog behind another window. A missing process, hidden dialog and unresponsive process need different follow-up. - **Splash screen freezes:** record the last text or plug-in name, elapsed time and whether Windows marks it not responding. Don't assume a first scan has crashed simply because it takes longer than usual. - **Audio initialization stops:** note the interface, selected driver if known, and any recent driver or device change. - **Only opening a file causes the crash:** test a new empty data window and a known-good local WAV before resetting preferences. - **An activation or installation message appears:** preserve its exact text and use that branch instead of diagnosing every failure as a damaged editor. Don't repeatedly click the icon or end unrelated processes. If you must end an unresponsive Sound Forge process, unsaved work in that process can be lost. Preserve recoverable recordings and projects before resets or cleanup. On a managed work computer, let IT handle account, security and service changes. ## Check 1: read the Windows crash record Press **Windows+R**, enter `perfmon /rel` and press Enter. Microsoft's [perfmon command reference](https://learn.microsoft.com/en-us/windows-server/administration/windows-commands/perfmon) identifies `/rel` as the Reliability Monitor switch. Find the failure at the matching time and open its details. Record the application name and version, faulting module, exception code and problem event name when available. For a visual reference, open the [Reliability Monitor example in this Microsoft Q&A discussion](https://learn.microsoft.com/en-us/answers/questions/1632789/could-someone-just-confirm-that-this-is-how-to-fin). The second attachment is a historical community example and has nothing to do with a Sound Forge crash. View it at full size on the source page, then look for your own failure date and matching event details. For a second view, open Event Viewer and look at **Windows Logs > Application** for the same time. Microsoft's [application-crash guidance](https://learn.microsoft.com/en-us/troubleshoot/windows-server/performance/troubleshoot-application-service-crashing-behavior) identifies Event 1000 as a crash record and explains why `ntdll.dll`, `kernel32.dll` or `KERNELBASE.dll` may be where an earlier fault finally shows up. Seeing them there doesn't prove Windows itself is corrupt. A named plug-in DLL points you toward that product, and an interface-related module points toward that driver. Neither one is a full diagnosis. A hang record such as AppHangB1 describes an application that stopped responding without naming what caused the wait, and a missing record doesn't prove the launch worked. Save the exact symptom and time for support. Keep a note for each attempt: installed edition/build, Windows build, launch method, last visible stage, one change and result. Redact account details and private file paths before posting logs publicly. If support needs a memory dump, ask for scoped collection and private upload instructions; don't copy registry dump commands for an unrelated executable. ## Check 2: separate activation and installation from startup If the message mentions a license, account or serial, first match the installed edition and purchase route to your receipt. Current Boris FX distribution and older Sony, MAGIX or Steam installations are not interchangeable. Preserve a working license state while testing other components. Don't delete license folders, deactivate another computer or reset a trial to investigate a generic crash. Use the [activation troubleshooting guide](https://soundforgepro.com/sound-forge-activation-failed/) to find the licensing branch, but get support to confirm any account-specific instruction that differs from the controls you see. If setup never finished, follow the [installation-failure checks](https://soundforgepro.com/sound-forge-installation-failed/). A successful setup followed by a launch failure belongs here, and reinstalling the Hub again and again won't replace recording that failure. Boris FX also documents a [post-activation launch remedy](https://support.borisfx.com/hc/en-us/articles/43612367340813-Sound-Forge-does-not-launch-after-activating) involving a Sony Creative Software VirtualStore registry branch. That's a narrow legacy route, and it won't repair every Sound Forge 2026 problem. Ask support to confirm the exact edition, version, user branch, backup and restoration plan before making that registry change. Do not adapt the path to a different product or delete parent branches. ## Check 3: if the workspace opens, test a new file Launch Sound Forge from its application entry rather than from the problem file. Choose **File > New**, complete the New Window dialog, and check that an empty data window stays open. The [new-window instructions](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/creating%5Fa%5Fnew%5Fwindow.htm) document its sample-rate, bit-depth and channel settings. Then open a short, known-good PCM WAV from a trusted local folder. Try a copy of the problem file last, and keep the original untouched. These isolation tests narrow things down, but they can't guarantee every effect or audio driver works. If only the copied source triggers the failure, note its format and whether another trusted editor can read it. A working WAV doesn't show that another format, a project dependency or a decoder is healthy. Don't overwrite the source with a conversion or post confidential audio on a public forum. If the workspace never opens, skip this test. ## Check 4: investigate a plug-in scan without moving shared libraries The current [Sound Forge VST Effects documentation](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/vst%5Feffects%5Fpreferences.htm) says configured folders are searched at startup, so a faulty or incompatible plug-in is one possible branch when startup stops during a scan. A [2023 Audio Studio 16 community report](https://www.magix.info/us/forum/sound-forge-audio-studio-16-vst-scan-stuck--1328142/) describes a stuck scan, but its file-moving workaround isn't safe as a general instruction for current Pro or VST3 bundles. If Sound Forge opens far enough, go to **Options > Preferences > VST Effects**. Record the search paths. For a folder containing only the suspect third-party product, use **Remove path** as a reversible test, then restore it with **Add path** after diagnosis. This changes Sound Forge's search list, not the folder on disk. It does not guarantee that the same plug-in is absent from another searched location. **Refresh** rescans; avoid repeatedly starting it while a previous scan remains unresponsive. The per-effect checkbox controls availability after discovery; it is not documented as a universal bypass for loading a plug-in during startup scanning. If startup prevents access to Preferences, ask Boris FX and the plug-in vendor for build-specific isolation instructions. Record the product build and use its official repair, update or uninstall route only after backing up its presets and checking other hosts that depend on it. Don't rename a shared VST directory, move an arbitrary DLL or VST3 bundle, transplant scanner executables, or delete cache files on the assumption that they will rebuild safely. Legacy launch switches and hidden settings from forum posts are not verified current controls. If the scan completes and effects are merely absent, continue with the [missing VST effects workflow](https://soundforgepro.com/sound-forge-pro-vst-plugins-not-showing/). ## Check 5: compare audio-device configurations Save any work you can reach, then close Sound Forge and other audio applications before touching the interface. Follow the interface manufacturer's disconnect procedure and try launching without that external device. A successful launch narrows the search but doesn't prove the physical interface is faulty. And unplugging hardware doesn't guarantee Sound Forge will pick a working replacement driver on its own. If you can reach **Options > Preferences > Audio**, record the original **Audio Device Type** and playback routing. For a Windows-path comparison, select **Microsoft Sound Mapper** if available; it lets Windows choose appropriate playback and recording devices. Alternatively, **Windows Classic Wave Driver** lets you choose a specific audio device. Confirm the intended playback output before testing. The [Audio preferences help](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/audio%5Fpreferences.htm) documents audio-device selection. Keep speaker or headphone volume low before testing playback. Restore the intended device only after closing the app and reconnecting the interface safely. For a driver regression, check the manufacturer's compatibility notes and the supported update or rollback procedure for your exact interface and Windows version. Don't install an unrelated ASIO package. A [2025 Audio Studio 17 thread](https://www.magix.info/us/forum/sound-forge-17-wont-open--1348252/) includes an Event 1000 naming `mgxasio4_x64.dll`, which makes the legacy driver a lead in that case. It doesn't mean every Pro startup crash has the same cause. Do not delete its shared registry registration or DLL as a generic fix. If the app opens but is silent, use the [playback routing checks](https://soundforgepro.com/sound-forge-pro-no-sound/). If playback works and recording fails, use the [recording-input diagnosis](https://soundforgepro.com/sound-forge-pro-not-recording-audio/). Keep those problems separate from failure to launch. ## Check 6: separate resets, cached data and a new profile Don't start by deleting AppData, temporary recordings, license stores or registry keys. A preferences reset may remove useful configuration alongside the suspected fault. Before any reset, preserve source files, recoverable sessions, custom presets, shortcuts, layouts and the settings you can still access. Ask support which exact files or exports preserve the installed build's configuration and how to restore them. A [Pro 18 build 21 community discussion](https://www.magix.info/us/forum/sound-forge-18-build-21back-up-toolbars--1344977/) describes **File > Reset all preferences and clear cached data** and differing observations about what survived. Other legacy threads mention holding Ctrl+Shift at launch. None of these reports confirm a current 2026 reset menu, a universal shortcut or a complete backup recipe. Do not confirm a destructive reset until the exact version's procedure and recovery plan are clear. A separate Windows user can help compare per-user state without erasing the original profile. With the computer owner's or IT's approval, follow Microsoft's [add-user procedure](https://support.microsoft.com/en-us/windows/security/identity-signin/manage-user-accounts-in-windows): **Settings > Accounts > Other users > Add account**. Microsoft also documents the local-account option through **I don't have this person's sign-in information > Add a user without a Microsoft account**. Use a standard account for the application test. Save and close applications in the original session before you sign in to the test user. Try the already installed Sound Forge only if it's available and licensing allows it; don't copy the original AppData or change license assignment just to force the comparison. A new activation prompt or a missing per-user install makes the test inconclusive. If it launches, user-specific settings, permissions or startup software become leads, though that still doesn't prove the original profile is corrupt. Keep the original account. Copy any files created during the test before you remove the temporary account, because removing it deletes its local data. ## Check 7: verify compatibility and named runtime errors The [current standalone requirements](https://www.soundforge.com/sound-forge/system-requirements/) list Windows 11\. Match that requirement to the installed product, and don't apply a current label to an older Pro or Audio Studio release. The [version-specific requirements guide](https://soundforgepro.com/sound-forge-pro-system-requirements/) helps separate those editions. Meeting the requirements doesn't prove the installation or driver stack is healthy. Check for a supported application update and for Windows updates, noting the previous versions before you change anything. For an older application with no suitable update, Microsoft's [compatibility guidance](https://support.microsoft.com/en-us/windows/apps/make-older-apps-or-programs-compatible-with-the-latest-version-of-windows) offers the Program Compatibility Troubleshooter. Treat its suggested settings as a documented comparison. They don't promise vendor support, and they're no reason to run every launch as administrator. Keep a record and undo changes that don't help. If an error names a missing runtime DLL, keep the filename and ask Boris FX which package and architecture that build needs. Microsoft's [Visual C++ Redistributable guidance](https://learn.microsoft.com/en-us/cpp/windows/latest-supported-vc-redist?view=msvc-170) separates package architectures and older side-by-side runtimes, and the newest x64 package won't stand in for every older `msvcr` or `mfc` dependency. Avoid loose DLL downloads and blanket runtime removal. ## Check 8: use a temporary clean boot after narrower checks Microsoft's [clean-boot procedure](https://support.microsoft.com/en-us/windows/experience/startup-boot/how-to-perform-a-clean-boot-in-windows) temporarily limits startup services and apps to investigate interference. It can remove functionality. On a managed device, obtain IT approval. Don't alter advanced boot options, disable antivirus protection as a blanket fix, or bypass organization security policy. If the test would remove required security controls, have IT or support design a narrower comparison instead. 1. Save work, sign in with administrative permission and record the original enabled/disabled state of services and startup apps. 2. Search for **msconfig** and open System Configuration. On **Services**, select **Hide all Microsoft services** before **Disable all**, then **Apply**, subject to the security restriction above. 3. On **Startup**, select **Open Task Manager**. Disable the currently enabled startup apps being tested, keeping your record. Close Task Manager, select OK in System Configuration and restart. 4. Try the same launch with the same file and hardware state. A new licensing or missing-device error means a required service may have been removed, and that's a different failure. 5. If the original problem disappears, restore services and startup apps systematically, testing halves and restarting between comparisons. Stop when you can reproduce the responsible combination. 6. Restore the recorded pre-test state and restart when finished. Microsoft's default restoration uses General > Normal Startup, Services > clear Hide all Microsoft services > Enable all > Apply, plus re-enabling the startup apps disabled for the test. Preserve items deliberately disabled before your investigation rather than blindly enabling everything. A crash that survives a valid comparison makes those disabled components less likely culprits, but it doesn't prove the editor or Windows is damaged. Don't leave the workstation in its diagnostic state. Restore security and the required audio/licensing services before normal work. ## Check 9: reinstall with a recovery plan, or escalate Before uninstalling, make sure you can get the correct installer, license and account, and back up audio, projects, presets and any work you can recover. Follow the [installation guide for the correct product generation](https://soundforgepro.com/how-to-install-sound-forge-pro/), and don't replace a legacy licensed release with a different current edition. Reinstalling the editor won't reliably remove a separate third-party plug-in or fix its licensing. Skip registry cleaners, aggressive third-party uninstall sweeps and trial-reset tools. Keep installer caches and logs unless support names an exact safe cleanup target with a backup. If you can't find a reversible next step, stop and send the edition/build, Windows build, failure time, exact message, module details and one-change test log to [Sound Forge support](https://support.borisfx.com/hc/en-us/categories/43250519345421-Sound-Forge). Include a redacted screen recording if it captures the startup stage. Support can then ask for a targeted dump or a build-specific reset without guessing at shared files. ## Safe startup diagnostic order 1. Preserve recoverable work, identify the installed edition and record one launch without opening a source file. 2. Match the failure time in Reliability Monitor or Event Viewer; treat the module name as a lead. 3. Route explicit installation or activation errors to the matching product-generation instructions without deleting license state. 4. If the workspace opens, test an empty data window, a known-good local WAV and a copy of the problem file. 5. Investigate the indicated plug-in or audio driver with one reversible, supported change; do not move shared libraries. 6. Confirm exact-version backup and recovery before a reset; use an approved separate-user comparison only when licensing and installation allow it. 7. Check compatibility and named dependencies, then consider a security-approved temporary clean boot and restore the original state. 8. Reinstall only with the correct installer and backups, or send the evidence to support before making destructive changes. ## Frequently asked questions ### Why does Sound Forge freeze on the splash screen? A plug-in scan, device initialization or another startup operation may be involved. Record the last visible text and matching Windows event. The displayed component is a lead, not proof of the cause. ### Does AppHangB1 identify the broken component? No. It describes an application that stopped responding. Match its time and application identity to the launch attempt, then compare one change at a time. ### Should I hold Ctrl+Shift and clear the cache? Not as a universal fix. Legacy community reports describe that reset route, but they do not establish current 2026 behavior or what every version preserves. Confirm the exact build's reset, backup and restoration procedure before accepting it. ### Should I run Sound Forge as administrator? Not as a permanent generic repair. An older post-activation problem has a narrowly scoped vendor remedy, while routine elevated launches can conceal a permissions difference. Ask support to identify the cause and use standard permissions for normal work. ### Does unplugging the interface prove its driver is broken? No. A changed launch result narrows the investigation to device-related state, but does not prove a hardware or driver defect. Close audio apps before changing hardware, and do not assume automatic fallback to another driver. ### Does a successful new-user test prove profile corruption? No. Settings, permissions, per-user software and licensing can differ. Preserve the original profile, do not copy its AppData into the test, and treat a different activation or missing-install message as an inconclusive comparison. ### Does Sound Forge 2026 officially list Windows 10? The current standalone requirements list Windows 11\. Check older Pro and Audio Studio requirements separately; compatibility workarounds do not create a vendor support promise. ### Will reinstalling Sound Forge remove a faulty VST? Not reliably. A separate plug-in installation may remain available to the editor after reinstalling. Investigate that product through its vendor rather than deleting shared folders or expecting an editor reinstall to repair it. *Documentation and community evidence checked September 15, 2026\. Historical reports are identified by edition or date.* ### How to Use Sound Forge 2026: Complete Beginner Tutorial URL: https://soundforgepro.com/how-to-use-sound-forge-tutorial/ Last updated: 2026-10-08T09:16:16.000Z Make an untouched source copy, open the working file with File > Open and listen before editing. Select only the required range with waveform focus. Check Options > Snapping > Enable and Crossings rather than blindly pressing F8 and Ctrl+B: those shortcuts toggle the current state. Compare supported processing previews at similar loudness, measure before normalizing, then use Save As for a regular file or Render As for a project. Reopen the delivery to verify it. This tutorial covers [Sound Forge 2026](https://www.soundforge.com/sound-forge/), the current Boris FX release of the audio editor previously sold as Sound Forge Pro. [Boris FX acquired Sound Forge from MAGIX](https://blog.borisfx.com/press/boris-fx-acquires-vegas-pro-sound-forge-and-acid-pro) on March 30, 2026 and now sells Sound Forge and Sound Forge Plus editions. The basic open, select, edit and export loop also applies to recent MAGIX-era releases, although menu locations and included effects can differ. If the editor is not installed yet, start with the [current installation guide](https://soundforgepro.com/how-to-install-sound-forge-pro/). *Part of the [Sound Forge 2026 guide](https://soundforgepro.com/) and the [Core Editing hub](https://soundforgepro.com/tag/core-editing/): open a real file, make one controlled edit, check the level and verify the delivery copy.* **Software:** Sound Forge 2026 | **Edition:** Sound Forge or Sound Forge Plus | **Platform:** Windows 11, per the [current Boris FX system requirements](https://www.soundforge.com/sound-forge/system-requirements/) | **Skill level:** Beginner | **Starting file:** WAV or MP3 | **Result:** an edited file that has been exported, reopened and checked ## Sound Forge Interface: What Beginners Need Five areas matter on the first pass. The data window holds the waveform and selection, and the transport controls handle play and stop. Peak meters warn you when the level approaches clipping; the status bar reports cursor, selection and format values. The Edit tool is what you'll use by default for selection and direct waveform work. Because toolbars can move in a custom workspace, this guide names the menu path or shortcut instead of relying on button position. The [current Standard toolbar exposes five editing tools](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/the%5Fstandard%5Ftoolbar.htm): Edit, Magnify, Pencil, Event, and Envelope. Edit is the normal selection tool. Magnify zooms into a region without discarding the selection, while Pencil redraws individual samples only after you zoom in far enough. If your workspace has been customized, use View > Toolbars rather than expecting these controls in one fixed screen position. The Event tool lets you adjust event positions, edges and fades. To preserve those events after closing the session, save a Sound Forge project, not just a WAV. The project-saving steps below explain the FRG file and companion media folder. Open View > Plug-In Chain when you want to build a processing chain instead of applying effects one at a time. The [current Boris FX help](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/proonly/plug-in%5Fchainer.htm) says a chain can hold up to 32 DirectX and VST plug-ins, preview them together in real time, and apply the chain when the file is saved. You do not need it for your first file; the [Plug-In Chain guide](https://soundforgepro.com/how-to-use-plug-in-chainer-sound-forge-pro/) covers that workflow when you are ready. ![Sound Forge main window with numbered menu bar, toolbar, transport controls, Instant Actions, data windows, channel meters and status bar](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/10/sf-main-window-layout-labeled-v20261006.webp) Toolbars and docks can move, so use the numbered labels to orient yourself. The [Boris FX 2026 Sound Forge window help](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/the%5Fsound%5Fforge%5Fwindow.htm) describes each area of the main window. ## How to Open and Play an Audio File Before opening important audio, make a separate untouched copy in Windows Explorer. Go to File > Open and browse to the working copy. WAV, MP3, FLAC and AIFF are common starting formats, but the installed codecs and edition determine the complete list shown in the Open dialog. File > Open avoids the paste or mix behavior that dragging onto an existing data window can trigger. Once the file opens, the waveform appears in the data window. A stereo file shows left and right channels; a mono file shows one channel. With the waveform focused and no range selected, Space starts and stops normal playback by default. General preferences can change it to Play/Pause; press Esc to stop. Select both stereo channels before judging channel balance. If you need to record instead of opening an existing file, use the [Sound Forge recording guide](https://soundforgepro.com/how-to-record-audio-in-sound-forge-pro/) for the input, driver and level setup. If the transport moves but you hear nothing, check the selected channels, Windows output and your interface connections at a low listening level. The [no-sound troubleshooting guide](https://soundforgepro.com/sound-forge-pro-no-sound/) walks through device and playback routing. Do not keep raising gain to diagnose silence. ## How to Navigate and Zoom the Waveform Use the Up and Down arrow keys, or your mouse wheel, to adjust horizontal waveform magnification, zooming in or out step by step. To see the entire file, choose View > Zoom Time > Out Full. The [Zoom Time documentation](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/magnification%5Fand%5Fzooming.htm) and keyboard reference disagree about Ctrl+Down Arrow, so use the explicit menu command for this step. Press Home or End to jump to the beginning or end of the visible waveform or your active selection. Use Ctrl+Home and Ctrl+End to jump to the very beginning or end of the entire file instead. The [full keyboard shortcuts guide](https://soundforgepro.com/sound-forge-pro-keyboard-shortcuts/) covers zoom presets, marker navigation, and dozens of shortcuts for faster editing. ## How to Make a Precise Selection [Click and drag across the waveform](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/selecting%5Fdata%5Fusing%5Fthe%5Fmouse.htm) to select a range. The selected region highlights, and the status bar shows exactly how long it is. With waveform focus, Ctrl+A selects all data. For a shorter stereo edit, drag along the divider between channels or the loop bar above the ruler to include all channels. Check the highlighted channels before applying a process. Snapping has two parts. Check Options > Snapping > Enable first, then Crossings for automatic zero-crossing snapping. F8 and Ctrl+B toggle those respective states; pressing them when already enabled turns them off. A boundary at zero amplitude reduces the risk of a click, but it does not prove the edit is seamless. Zoom in and listen across both sides of the join. The [current snapping documentation](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/enablesnapping.htm) is the controlling reference when an older tutorial assigns these shortcuts differently. ![Dragging along the divider between two channels to select both channels in a Sound Forge data window](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/09/sf-select-all-channels-divider.webp) For a stereo edit, include both channels: drag along the divider between channels, or in the loop bar above the ruler, to select every channel. ## How to Cut, Copy, Paste, and Trim Audio With a selection active, [Ctrl+X cuts it](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/cut.htm) to the clipboard and removes it from the file. Ctrl+C copies it without removing anything. Ctrl+V pastes clipboard contents at your current cursor position. Use these commands with waveform focus in normal editing mode, not Treat as Cutlist. Listen across the boundary afterward; audio joins can click even when the intended range was selected. With waveform focus and Treat as Cutlist off, Delete removes the selected audio without putting it on the clipboard, which matters if you're just trimming unwanted silence or noise rather than moving that audio somewhere else. The [cutting and trimming guide](https://soundforgepro.com/how-to-cut-and-trim-audio-in-sound-forge-pro/) goes further into precise editing, including Ctrl+T to trim everything outside your selection in one step. ## How to Add a Fade In or Fade Out Select the region and channels you want to fade. Without a selection, the fade affects the entire file. [For a custom shape, choose Process > Fade > Graphic](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/fade.htm), then drag the envelope points; double-click to add a point and right-click a segment to choose its curve. For a simple linear edge, Process > Fade > Fade In or Process > Fade > Fade Out is quicker. Preview the boundary where the dialog allows it, then listen across the fade before saving. ## How to Preview and Apply Effects Processing is organized across the [Process, Effects, and FX Plug-Ins menus](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/applying%5Feffects.htm). [FX Favorites is a folder in the Plug-In Manager](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/proonly/plug-in%5Fmanager.htm), not a separate top-level processing menu; its contents appear in the lower part of the FX Plug-Ins menu. With waveform focus, select the intended range and channels, or press Ctrl+A when the whole file needs the same change. An empty selection can process the entire file, so check the range before clicking OK. Don't commit a setting just because the processed signal is louder. Where the dialog provides Preview, Bypass or A/B, adjust one control at a time and compare at similar output level. Some built-in processes and third-party plug-ins expose different controls, so treat Preview and Bypass as conditional rather than universal buttons. Click OK in the processing dialog only when the level-matched comparison is better for the job. The separate real-time View > Plug-In Chain has no OK-to-apply or Process button; it renders on audio save or project render. ![Sound Forge Plug-in Manager with numbered folder tree, FX Favorites, refresh button, search field and plug-in type options](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/09/sf-plugin-manager-tree-favorites-options.webp) Plug-In Manager with FX Favorites marked 2\. Double-click an effect to open processing for the selection, then preview and confirm. Dragging it onto a data window adds it to the real-time chain. Start with the effects you'll actually need first. The [EQ guide](https://soundforgepro.com/how-to-use-equalizer-sound-forge-pro/) covers frequency correction. The [noise reduction guide](https://soundforgepro.com/how-to-remove-background-noise-in-sound-forge-pro/) covers cleaning up a hum or hiss. The [reverb guide](https://soundforgepro.com/how-to-add-reverb-in-sound-forge-pro/) covers adding space to a dry recording. You don't need to learn all of these before your first export. Pick the one your specific file actually needs. ## How to Undo Edits and Protect the Original Ctrl+Z undoes the last action and Ctrl+Shift+Z redoes it. Open [View > Undo/Redo History](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/undo.htm) to review earlier operations. For ordinary files, Undo past Save must be enabled in General preferences to retain history after saving, and that history ends when you close the data window or exit. Save a project if you need undoable work after reopening. For editable work, [select File > Save As](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/working%5Fwith%5Fprojects.htm) and choose Sound Forge Pro Project File (\*.frg). Retain both the FRG and the generated \[filename\]\_frg folder; that folder contains media and temporary edit data. Deleting it breaks the project. Keep the untouched source too, then use File > Render As for a separate finished audio file. Merely selecting the Event tool does not preserve the session in a plain WAV. ## How to Check Levels and Normalize When Needed [Process → Normalize → Peak level](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/proonly/normalizing%5Faudio.htm) applies constant gain toward a sample-peak target. Average RMS can use dynamic compression, and Loudness mode has dynamic limiting controls, so do not assume every Normalize setting preserves the same dynamics. Choose the mode from the delivery requirement; the [normalization guide](https://soundforgepro.com/how-to-normalize-audio-in-sound-forge-pro/) explains the differences. With waveform focus, select the complete file and all intended channels, then open [Tools > Statistics](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/statistics.htm) for the peak and integrated-loudness measurements. Check the reported scope and clipping information before choosing a target. Normalization changes overall level based on a peak or loudness target, but it does not repair audio that's already clipped, since that distortion is baked into the waveform itself. If the measured level meets the delivery requirement, skip normalizing. If you used the real-time View > Plug-In Chain, first save or render a high-precision lossless processed copy and reopen it without applying the same chain again. Measure and normalize that processed audio, not the unchanged data beneath a live preview. If you are exporting MP3, do not normalize to 0 dBFS merely because the control allows it: current [Boris FX Normalize help](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/proonly/normalizing%5Faudio.htm) warns that compressed encoding can clip peaks at or near 0 dB and gives -0.9 dB peak as a starting point. Treat that as general headroom rather than a universal delivery specification, then reopen and measure the encoded file. The [Statistics measurement walkthrough](https://soundforgepro.com/how-to-use-statistics-sound-forge-pro/) explains the selection, channels and reported units. For a file-level delivery target, do not substitute a short loud passage for a complete-program scan. ## How to Export WAV or MP3 For a regular audio file, use File > Save As. Choose an uncompressed PCM or float WAV template that preserves the required sample rate, channel count and working precision for another editing pass. MP3-to-WAV does not restore audio discarded by MP3 encoding. Choose MP3 when a smaller delivery copy matters, then set the bitrate and metadata deliberately. WAV is a container and can also carry non-PCM formats, so the template matters; the [Microsoft WAVE format structure](https://learn.microsoft.com/en-us/windows/win32/api/mmreg/ns-mmreg-waveformatex) is the technical reason the word WAV alone does not guarantee uncompressed audio. Keep the output name distinct from the working file, and use the [Sound Forge MP3 export guide](https://soundforgepro.com/how-to-export-mp3-from-sound-forge-pro/) for encoder and metadata choices. If you're working inside a Sound Forge project instead of a single audio file, Save As saves the project itself, not a finished media file. Use File, Render As to generate the actual WAV, MP3, or other output file from that project. If you need to convert a whole folder of files at once instead of exporting one at a time, that's a different workflow. The [file conversion guide](https://soundforgepro.com/how-to-convert-audio-files-sound-forge-pro/) and the [batch processing guide](https://soundforgepro.com/how-to-batch-process-files-sound-forge-pro/) cover that directly. ## Your First Sound Forge Project: Complete Workflow Use this seven-step order for the first pass. It keeps each decision audible and gives you a clear rollback point before processing becomes complicated. 1. Make a separate untouched source copy, open the working copy with File > Open, select all intended channels and listen from beginning to end once. 2. Zoom to the edit and inspect Options > Snapping > Enable and Crossings. Use F8 or Ctrl+B only when the corresponding state needs changing, then select the intended range. 3. With waveform focus and Treat as Cutlist off, use Delete to remove the range or Ctrl+T Trim/Crop to keep it. Listen across the join. 4. Select the exact edge and channels before adding a fade. Use Process > Fade > Fade In or Fade Out for a linear edge, or Graphic for a custom curve; listen across the result. 5. Apply only the processing the file needs, using Preview or Bypass where available and comparing at similar loudness. 6. Commit any real-time chain to a separate high-precision lossless copy and reopen it without duplicate effects. Select the complete processed file and all intended channels, measure peak and loudness, and normalize only when the delivery requirement calls for it. 7. Use Save As for a regular file or Render As for a Sound Forge project, then reopen the delivery copy and verify format, duration, peaks and playback. The same sequence works for podcast cleanup, voice-memo repair and quick music edits; only the processing choices and delivery target change. ## Frequently Asked Questions ### Is Sound Forge 2026 the same as Sound Forge Pro? Sound Forge 2026 is the current Boris FX version of the audio editor previously marketed as Sound Forge Pro. Boris FX acquired the software from MAGIX on March 30, 2026, and now sells it in Sound Forge and Sound Forge Plus editions. Older Sound Forge Pro versions have different licensing, support and included effects; compatibility depends on the version and operating system. ### Can I still follow this tutorial in an older Sound Forge Pro version or Sound Forge Audio Studio? The same open, select, edit and export sequence is a useful starting point, but exact controls and advanced features differ by version and edition. Some advanced processing, restoration, plug-in, and workflow features may not be available in [Sound Forge Audio Studio](https://soundforgepro.com/sound-forge-audio-studio-vs-sound-forge-2026/), since its feature set has varied between generations. If a specific menu or effect doesn't match what you see, check which edition and version you're running. ### Does Sound Forge have a free trial? Yes. Boris FX offers a [full-featured 15-day trial](https://vfx.borisfx.com/sound-forge-trial) of Sound Forge. The [full review](https://soundforgepro.com/sound-forge-pro-review-2026/) and the [pricing guide](https://soundforgepro.com/sound-forge-pro-pricing/) cover what's included and how the trial compares to a paid license. ### Is Sound Forge a DAW or an audio editor? Sound Forge is a single-file audio editor, not a full DAW. It's built for editing, restoring, and mastering one audio file at a time rather than arranging and mixing a multitrack production. For multitrack arrangement or MIDI sequencing, use a separate DAW; this does not mean Sound Forge has no MIDI-related functions. ### Can Sound Forge edit multiple tracks at once? Not as a DAW-style multitrack session. Sound Forge can record and handle multiple channels into a single file, but it doesn't provide the track-based arrangement, mixing, and automation environment a DAW does. For that kind of work, pair Sound Forge with a DAW rather than expecting it to replace one. ### Should I export from Sound Forge as WAV or MP3? Choose an uncompressed PCM or float WAV template when you need a lossless archive or expect another editing pass. Choose MP3 when file size and easy delivery matter more than lossless quality. Leave peak headroom before MP3 encoding instead of normalizing directly to 0 dB. ### Can I use Sound Forge on a Mac? There is no current native macOS edition. Sound Forge 2026 lists Windows 11 as its supported system; running Windows on Mac hardware is a separate compatibility question. The [Sound Forge for Mac guide](https://soundforgepro.com/sound-forge-for-mac/) covers the history of the discontinued Mac version and what to run instead if you're on Apple hardware. ### Does Sound Forge edit audio destructively? Applied processing changes ordinary audio data. For a persistent editable session, save a Sound Forge Pro Project File (\*.frg), retain its companion \[filename\]\_frg folder and keep the untouched recording. Event editing alone does not make a rendered WAV an editable project. Use Render As to create the delivery from that project. Repeat the seven-step loop on the next real file, then open a specialist guide only for the problem you can actually hear: [remove background noise without hollowing out the voice](https://soundforgepro.com/how-to-remove-background-noise-in-sound-forge-pro/), [choose the right normalization mode](https://soundforgepro.com/how-to-normalize-audio-in-sound-forge-pro/), or [verify an MP3 delivery copy](https://soundforgepro.com/how-to-export-mp3-from-sound-forge-pro/). Documentation reviewed September 14, 2026\. Menu guidance is based on the current Boris FX help, not a local Windows application test. ### Sound Forge for Mac in 2026: What Actually Works URL: https://soundforgepro.com/sound-forge-for-mac/ Last updated: 2026-10-09T21:45:19.000Z **Sound Forge has no current native Mac version.** The Boris FX editor requires Windows 11\. Sound Forge Pro Mac 3 did exist, but it's a discontinued, separate product, and you can't download it as a Mac edition of Sound Forge 2026. If you need Sound Forge itself, start with a Windows 11 PC that meets the application, operating-system and audio-hardware requirements. If what you need is the editing job done on a Mac, pick a current Mac editor. Parallels is worth investigating, but it isn't a confirmed Sound Forge configuration: emulating Windows applications doesn't guarantee support for the installer, activation, plug-ins or interface drivers. *Documentation checked September 14, 2026\. This is a compatibility decision guide, not a report of hands-on Sound Forge testing in a virtual machine.* ## What Boris FX actually supports in 2026 The [current Sound Forge requirements](https://www.soundforge.com/sound-forge/system-requirements/) name Windows 11, with no mention of macOS, and the [official 15-day trial](https://vfx.borisfx.com/sound-forge-trial) also says Windows only. Neither page documents Sound Forge support in Parallels or on Windows 11 on Arm. That silence doesn't prove it can never work, but it gives no basis for promising compatibility either. Don't read “Windows 11” as a blessing for every Windows computer. Check the processor architecture, the audio interface and the plug-ins along with the OS. Our [Sound Forge system requirements guide](https://soundforgepro.com/sound-forge-pro-system-requirements/) separates the application's specification from Windows' own minimum requirements. [Apple's Rosetta guidance](https://support.apple.com/en-us/102527) is about Intel-based Mac apps, and Rosetta won't turn the current Windows Sound Forge installer into a macOS application. A similarly named App Store product doesn't mean Boris FX has released a Mac version either. ## Five routes from a Mac | Route | Current status | Best fit | Main risk | | ----------------------------- | ----------------------------------------------------------- | -------------------------------------- | ---------------------------------------------------- | | **Windows 11 PC** | Matches the named OS; verify hardware and architecture | Sound Forge recording and file editing | Separate computer and peripheral checks | | **Remote Windows PC** | Editor runs on the Windows host, not macOS | Offline edits and renders | Network delay, audio redirection and file transfer | | **Apple silicon + Parallels** | Windows on Arm route; Sound Forge support unconfirmed | A bounded compatibility trial | Activation, plug-ins and audio-device paths | | **Current Mac editor** | A replacement, not Sound Forge for Mac | A Mac-first production workflow | Rebuilding processing chains and checking plug-ins | | **Intel Mac + Boot Camp** | Apple documents Windows 10, not a current Sound Forge match | Preserving an existing legacy setup | Ended normal OS support; ESU eligibility is separate | ## What happened to Sound Forge Pro Mac 3? Old Mac product pages and retail boxes describe a real historical editor. They don't point to a current download, a supported upgrade or modern macOS compatibility. A [pinned MAGIX Community notice from April 2020](https://www.magix.info/us/forum/osx-catalina-and-sound-forge-mac--1244059/) reproduces a Sound Forge Support response saying there were no plans to make the Mac product compatible with Catalina. A later [MAGIX Community discussion](https://www.magix.info/us/forum/soundforge-mac-bad-crumb-message--1314116/) quotes MAGIX's notice that development had stopped and the product was taken out of its range. That discussion also records a “Bad Crumb” failure after a macOS upgrade. Participants disagree about the underlying architecture and suspect the authorizer. Treat that as an unresolved community diagnosis; it doesn't confirm the whole editor is 32-bit. Apple confirms that [Catalina 10.15 dropped 32-bit app support](https://support.apple.com/en-us/103076), but that general OS fact can't tell you which Sound Forge component fails. If you own Mac 3, protect a working installation before you change anything. Back up the machine and the audio, keep your legitimate installer and entitlement records, and export important work into formats your replacement can reopen. A serial number alone won't guarantee an old authorizer will activate today. Ask MAGIX about your entitlement, and don't count on a mirror, an activation bypass or an OS downgrade to fix it. ## Windows PC or remote access: keep the editor on Windows A local Windows workstation skips the virtualization and network layers entirely. It's my first choice when Sound Forge has to record through a particular interface or reuse an established Windows plug-in chain. That recommendation still depends on the exact computer, drivers and plug-ins being supported, and a clean OS installation isn't an audio-workstation acceptance test. A Mac can instead control a remote Windows machine. Keep source files and processing on the host, then transfer the finished export back for verification. Remote control can suit trimming or batch renders; redirected playback is a poor reference for judging latency or subtle repair artifacts. Record and monitor at the machine connected to the interface rather than assuming that remote audio preserves the same behavior. Remote access needs its own host/client setup and licensing checks. Microsoft's [Windows-on-Mac guidance](https://support.microsoft.com/en-US/Windows/Experience/Platform-variants/options-for-using-windows-11-with-mac-computers-with-apple-m1-m2-and-m3-chips) also describes Windows 365 Cloud PCs, but a cloud desktop doesn't show that your physical interface or Sound Forge workflow is supported there. ## Apple silicon and Parallels: emulation is not product support Microsoft's linked guidance specifically names Parallels Desktop 18, 19 and 20 with Windows 11 Pro or Enterprise on M1, M2 and M3 Macs. [Parallels' current page](https://www.parallels.com/products/desktop/microsoft-authorized-solution-windows-11-arm/) also lists support for newer M4 and M5 hardware. Check the exact Mac, macOS, Parallels release and guest OS combination rather than extending an older authorization statement to every configuration. [Microsoft's Windows on Arm FAQ](https://learn.microsoft.com/en-us/windows/arm/faq) says Windows 11 can emulate x64 and x86 applications, with performance overhead. It separately requires kernel-mode drivers to be native Arm64\. A compatible application, a compatible installer and a compatible driver package are three different questions. Third-party compatibility entries for an older Sound Forge release don't certify Sound Forge 2026 inside Parallels. Check the editor, Hub, account sign-in, activation and every required plug-in before you rely on it. **Budget for separate entitlements.** Parallels does not include a Windows license. Microsoft's guidance requires a unique eligible Windows 11 Pro license for each running instance; Enterprise use has additional organizational licensing terms. Sound Forge is another license after its trial. Check transfer rights before reusing a Windows key, and compare the current [Sound Forge license options](https://soundforgepro.com/sound-forge-pro-pricing/) rather than assuming a Mac 3 serial covers the current Windows product. ## Three audio paths with different driver requirements **Shared host audio:** macOS owns the physical device and Windows uses a virtual audio device. The [Parallels sound troubleshooting guide](https://kb.parallels.com/en/112477) starts with working Mac-side sound and the Parallels audio controller. It distinguishes a USB device attached to macOS from one connected directly to the guest. Start here for an offline-editing trial, then verify recording, channels and monitoring rather than assuming pro-audio performance. ![Parallels Desktop Sound & Camera settings with Sound Output, Microphone and Sync volume with Mac controls](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/10/sf-parallels-sound-camera-settings-v20261005.webp) Parallels Sound & Camera settings for choosing the shared output and microphone. **Class-compliant USB attached to Windows:** a compatible device may use Microsoft's in-box [USB Audio 2.0 class driver](https://learn.microsoft.com/en-us/windows-hardware/drivers/audio/usb-2-0-audio-drivers) instead of a vendor driver. The documentation describes limits around clock selection and device topology. Class compliance doesn't promise that every control, channel or USB-passthrough behavior works in your VM. **Vendor-specific interface package:** any kernel-mode component loaded by the Arm guest has to be Arm64\. A user-mode ASIO component or control app is a separate compatibility question, so don't call the entire package a kernel driver. Ask the manufacturer about the complete package, including its installer, routing and clock controls. [ASIO4ALL 2.22](https://asio4all.org/version-2-22/), released July 23, 2026, adds Arm64/EC support, including an ASIO route for USB Audio Class-compliant devices that lack vendor Arm64 drivers. That doesn't certify Sound Forge in Parallels, and it won't bring back unsupported hardware controls. Install a different audio layer only if your actual workflow needs it, then test again. ## Which Mac alternative fits your work? A Mac application avoids the Windows guest, though its own OS, architecture and plug-in requirements still matter. Treat these as starting points by task. No single editor wins every comparison. - **Waveform editing and restoration: [Acoustica 8](https://acondigital.com/products/acoustica).** My first comparison for a Sound Forge-style file workflow. Acon lists macOS 12 or later and native Apple silicon and Intel support. It offers spectral editing and restoration in a standalone editor. Check the edition for the tools you need. - **Album mastering: WaveLab.** Start with our [Sound Forge versus WaveLab comparison](https://soundforgepro.com/sound-forge-pro-vs-wavelab/). Steinberg's [current Tahoe compatibility matrix](https://helpcenter.steinberg.de/hc/en-us/articles/29503903823762-macOS-Tahoe-Steinberg-Product-Compatibility) lists WaveLab Pro/Elements 13.0.30 as Intel-compatible and Apple-silicon native. Check your precise build and delivery features, especially if you depend on physical CD functions. - **Difficult repair: iZotope RX.** Compare the [restoration workflows in Sound Forge and RX](https://soundforgepro.com/sound-forge-pro-vs-izotope-rx/). The [RX 12 Standard release notes](https://www.izotope.com/en/products/release-notes/rx-standard-release-notes.html) list Intel and native Apple-silicon support on specified macOS releases. They also list a Rosetta-only exception for Spectral Editor AU ARA; standalone support does not certify every integration. - **Free basic editing: Audacity.** Its [Mac download page](https://www.audacityteam.org/download/mac/) offers Intel, Apple-silicon and universal builds. At the time of this check, the ARM64 download carries a “No plugin support” warning. Read that before choosing a build for an effects-dependent workflow, because a native build doesn't automatically mean plug-in parity. Use the [broader Sound Forge alternatives guide](https://soundforgepro.com/best-sound-forge-alternatives/) to narrow the workflow category, then confirm current versions, requirements and checkout terms with the developer. Rebuild processing chains on copies of representative files and reopen exports in the destination app. Our [Sound Forge comparisons](https://soundforgepro.com/tag/comparisons/) collect the longer editor-by-editor trade-offs. ## Intel Mac and Boot Camp: a legacy Windows 10 path [Apple's Boot Camp instructions](https://support.apple.com/en-us/102622) cover Windows 10 on listed Intel Macs and leave Apple silicon out. That documented route doesn't meet Sound Forge 2026's Windows 11 requirement, and internet instructions for bypassing Windows 11 checks carry no Apple or Boris FX support. Normal Windows 10 support ended October 14, 2025\. [Microsoft's Consumer ESU program](https://www.microsoft.com/en-us/windows/extended-security-updates) gives eligible enrolled devices critical and important security updates, but no feature upgrades or full technical support. It excludes commercial scenarios and has regional terms. ESU doesn't make Windows 10 a supported Sound Forge 2026 platform. For an existing older Sound Forge installation, make a recoverable backup before any OS changes and plan the migration. Don't wipe a working Mac or Windows partition to follow a workaround nobody has verified. ## How to evaluate a Parallels setup before relying on it Use this as an acceptance checklist. The official Sound Forge trial is full-featured for 15 days and needs no credit card. Read the current Parallels trial and Windows licensing terms as well, since a free application trial doesn't license the whole system. 1. **Preserve the working system.** Back up source files and use disposable copies. Keep a fallback editor available. 2. **Check the exact VM combination.** Verify your Mac, macOS, Parallels version, Windows edition and license. Install applicable Windows and Parallels Tools updates before the trial. 3. **Verify installation and authorization.** Follow the official Boris FX trial flow through Hub, sign-in, installation and trial activation. Restart the VM and confirm the editor still opens. 4. **Test representative files and plug-ins.** Use the formats, channel counts and processing chains required by your work. Save, close and reopen to check plug-in state. 5. **Choose and test one audio route.** Begin with shared host audio. If direct USB or vendor ASIO is required, verify that package separately. Check input, output, channels, clocking and a recording as long as your normal job. 6. **Export, restart and repeat.** Reopen the rendered file in another application. Verify duration, channels and audible results. Restart Windows and macOS, then repeat activation, plug-in and device checks. Stop if activation fails after a restart, plug-in state disappears, channels go missing, exports differ unexpectedly or recording drops out. Don't buy an interface or change your production machine because of one successful launch. For deadline work, a supported local Windows setup or a compatible Mac editor is the safer bet. ## Frequently Asked Questions ### Does Sound Forge have a Mac version in 2026? No current native Mac edition is listed. Boris FX Sound Forge requires Windows 11\. Sound Forge Pro Mac 3 was a separate historical product whose development was discontinued. ### Can Rosetta run the current Windows Sound Forge installer? No. Rosetta translates Intel-based Mac apps for Apple silicon. It does not make the Windows installer a macOS application. ### Does Sound Forge work in Parallels Desktop? We have no vendor-confirmed result for Sound Forge 2026 in Parallels. Windows 11 on Arm can emulate x64 and x86 apps, but installation, activation, plug-ins and audio devices require separate checks. ### Do I need an Arm64 audio-interface driver in Parallels? Kernel-mode components loaded by the Arm guest must be Arm64\. Shared host audio uses a virtual device; compatible class-compliant USB hardware may use an in-box driver. User-mode ASIO components and control apps need their own compatibility checks. ### Does a Parallels license include Windows or Sound Forge? No. Windows and Sound Forge entitlements are separate from Parallels. Check the Windows edition, per-instance license and transfer rights, and use the official Sound Forge trial before buying. ### Can I use Boot Camp for Sound Forge 2026? Apple's documented Boot Camp route is Windows 10 on listed Intel Macs. It does not match the current Sound Forge Windows 11 requirement. ESU enrollment does not change that application requirement. ### Can I still activate Sound Forge Pro Mac 3? That depends on the old installer, entitlement, authorizer and operating system. A valid serial is not a current activation guarantee. Preserve a working system and contact MAGIX rather than treating an OS downgrade as a verified fix. ### What is a good Mac alternative to Sound Forge? Start with Acoustica for file editing and restoration, WaveLab for mastering, RX for specialist repair or Audacity for free basic editing. Verify the chosen version's macOS, processor and plug-in requirements before migrating. ### Best Sound Forge Alternatives in 2026 URL: https://soundforgepro.com/best-sound-forge-alternatives/ Last updated: 2026-10-09T21:01:08.000Z **The short answer:** Acoustica is the closest paid Sound Forge alternative for general file editing. Audacity is the best free option. RX 12 is the specialist for difficult repair, WaveLab Pro 13 is the mastering choice, Adobe Audition fits Premiere workflows, and REAPER is the better move when the missing feature is a full DAW. No single alternative honestly wins across the board, because those applications replace different jobs. Sound Forge is a Windows file editor built around opening audio, selecting a region, processing it and delivering the file. A popular DAW can cut a WAV and still make a poor replacement for that daily rhythm. **Fast route:** closest editor: Acoustica; free: Audacity; Mac voice work: TwistedWave; restoration: RX; album mastering: WaveLab; Adobe video work: Audition; multitrack production: REAPER. Versions, platforms and vendor pricing references were checked on September 13, 2026\. The table uses regular prices where they're shown and leaves temporary sale prices out. Tax, region and plan terms can change your total, and the WaveLab figures are the publisher’s announced suggested retail prices. ## How I chose these Sound Forge alternatives I treated Sound Forge as a file editor first. Each ranked product had to replace at least one practical job: precise waveform editing, restoration, mastering, repetitive file processing, or recording and finishing spoken-word audio. The order reflects how directly each product replaces that workflow; market share and the length of a feature list didn't factor in. That rule keeps Pro Tools, Ableton Live and [FL Studio](https://flstudiopro.com/fl-studio-editions/) off the direct shortlist. They're capable DAWs, and generic directories often surface them for this query, but their main job is session-based music or post production. REAPER appears because some Sound Forge users discover that tracks, MIDI, routing and automation are the capability they actually lack. This shortlist comes from documentation; there was no controlled audio-quality shootout. The recommendations match published capabilities to file-editing jobs. Try your own recordings before treating a feature list as proof that anything sounds better. ## Best Sound Forge alternatives by use case | Alternative | Best job | Platforms | US reference price · Sep. 13, 2026 | | ----------------------- | --------------------------------- | --------------------- | ---------------------------------------------- | | **Acoustica 8** | Closest all-around file editor | Windows, macOS | $149 Standard / $299 Premium / $449 Ultimate | | **Audacity 4.0.0** | Free recording and editing | Windows, macOS, Linux | Free, open source | | **Adobe Audition 26.5** | Premiere and Creative Cloud work | Windows, macOS | $22.99/mo on annual plan billed monthly | | **iZotope RX 12** | Dialogue and damaged-audio repair | Windows, macOS | $99 Elements / $399 Standard / $1,399 Advanced | | **WaveLab Pro 13** | Album and Dolby Atmos mastering | Windows, macOS | $499.99 Pro / $99.99 Elements | | **REAPER 7.82** | Full DAW and production | Windows, macOS, Linux | $60 discounted / $225 commercial | | **TwistedWave 33.7** | Mac voice-over and batch jobs | macOS, Windows | $9.99/mo or annual plan | The price column gives context. It isn't a score. RX Advanced is aimed at demanding post-production repair, and Audacity is free. Acoustica 8 now comes in three editions, so an older comparison that covers only Standard and Premium misses both the new prices and the Ultimate tier. ## What are you actually replacing? A file editor, restoration suite, mastering environment and DAW overlap, but that overlap doesn't make them interchangeable. Decide which part of Sound Forge currently earns its place on your computer. ![Sound Forge alternatives grouped into file editing, audio repair, album mastering and multitrack production](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/09/job-map-20260913.webp) Match the replacement to the job. Audition suits Premiere audio work; REAPER is the option here for MIDI-based production. **Choose a file editor** if you repeatedly open individual recordings, make sample-accurate selections, run effects or chains, and save the result. Acoustica, Audacity and TwistedWave are the closest category matches. **Choose a restoration suite** if hum, clipping, room noise, mouth clicks or damaged dialogue drive the purchase. RX 12 and Acoustica Premium put more of the budget into repair. **Choose a mastering application** if a release, sequence or album is the unit of work. WaveLab's montage, metadata and delivery model matters more here than similarity to one Sound Forge window. **Choose a DAW** if you need tracks, MIDI, instruments, routing and mix automation. REAPER fits that broader production job. Audition handles multitrack audio and video-related sound work, but if MIDI and instruments are what you need, it's the wrong pick. ## Best Sound Forge alternative for Mac Sound Forge 2026 is Windows software. For a Mac user who wants one current editor rather than a compatibility workaround, Acoustica is the closest overall match. It combines waveform and spectral editing, recording, processing chains, loudness tools, restoration and multitrack work in one Windows and macOS product. TwistedWave is the quicker Mac choice for voice-over, audiobooks, metadata, silence splitting and large folder jobs. WaveLab Pro is stronger for mastering releases, RX for difficult restoration, Audacity for a free editor, and REAPER for a full DAW. The separate [Sound Forge for Mac guide](https://soundforgepro.com/sound-forge-for-mac/) explains why the discontinued Sony Mac edition is no longer a route you can take. ## 1\. Acon Digital Acoustica 8: closest overall paid alternative [Acon Digital Acoustica 8](https://acondigital.com/products/acoustica) is the closest paid replacement here for a file-first workflow. Its three editions share the core editor, spectral selection, recording and multitrack tools on Windows and macOS. Check the edition comparison for processing and channel limits rather than assuming every plug-in is included with Standard. Acoustica 8 lists Standard at $149, Premium at $299 and Ultimate at $449\. The September 13 storefront also showed a launch promotion, and those temporary amounts aren't the table’s reference prices. Standard handles stereo editing with in-app processing. Premium adds deeper dialogue tools and processing plug-ins for other hosts, with up to 7.1.2 channels, and Ultimate stretches that to 9.1.6 and adds processors including DeVerberate and DeFilter. The license is perpetual, and the trial runs 30 days with no card required. **Choose it when:** you want a current Mac or Windows editor with spectral selection and a perpetual license. **Look elsewhere when:** you need WaveLab's release-oriented montage, RX Advanced's post modules, or Linux support. ## 2\. Audacity 4.0.0: best free Sound Forge alternative [Audacity 4.0.0](https://www.audacityteam.org/download/) is the current stable free release for Windows, macOS and Linux. It shipped on September 3, 2026 after the 3.7.9 maintenance release, so production users should review Audacity 4's project-format and feature-availability notes before migrating existing work. Audacity records and edits multiple tracks and supports real-time and rendered effects, and you can still draw samples once you zoom in far enough. But the [Audacity 4.0 compatibility notes](https://www.audacityteam.org/changelog/) explicitly list Macro Manager and the scripting pipe as unavailable. Don't swap a working batch setup for 4.0 expecting your old Macros workflow to carry over unchanged. For ordinary recording and manual file editing, Audacity is a strong free starting point, especially on Linux. For repetitive exports, specific effects or existing projects, check the 4.0 release notes and run a small trial job first. Audacity 4 converts .aup3 projects to .aup4 but can't save them back to .aup3, so keep the original projects. Our [Sound Forge versus Audacity comparison](https://soundforgepro.com/sound-forge-pro-vs-audacity/) covers that narrower decision. ## 3\. Adobe Audition 26.5: best for Creative Cloud workflows [Adobe’s current release page](https://helpx.adobe.com/audition/desktop/introduction/whats-new.html) identifies 26.5 as the September 2026 release. Audition combines a destructive Waveform Editor, spectral display, Multitrack sessions, restoration effects, Match Loudness and a Premiere Pro handoff. That combination is useful when dialogue editing and a video mix belong to the same job. The current US single-app price on [Adobe's Creative Cloud plans](https://www.adobe.com/creativecloud/plans.html) is $22.99 per month on an annual plan billed monthly. Regional pricing and tax vary. The subscription is the main long-term tradeoff. Engineers who deliver physical discs should also know that Adobe [removed built-in CD authoring in Audition 26.3](https://helpx.adobe.com/audition/desktop/introduction/removal-of-cd-authoring.html). CD Layout, CD markers and CD-specific metadata authoring are gone, though you can still extract audio from CDs. Pick Audition for Premiere and Creative Cloud work, and WaveLab when album assembly, ISRC handling and delivery sit at the center of the job. Our [Sound Forge versus Adobe Audition comparison](https://soundforgepro.com/sound-forge-pro-vs-adobe-audition/) covers the editor and subscription tradeoff in more detail. ## 4\. iZotope RX 12: best for damaged audio and dialogue repair [iZotope RX 12](https://www.izotope.com/products/rx-standard) is the specialist choice for damaged recordings and difficult dialogue. Elements costs $99 and contains six plug-ins *including* Repair Assistant. Standard costs $399 and includes the standalone editor with deeper modules. Advanced costs $1,399 and expands the post-production toolkit. For a module-level look, see the [RX 12 review on izotoperx.net](https://izotoperx.net/izotope-rx-12-review/). Edition names matter. Spectral De-noise, Music Rebalance and the standalone editor aren't part of the Elements package, and RX is an expensive answer for routine trimming, recording and conversion. Choose Standard or Advanced when repair quality and module depth are the paid job. The [Sound Forge versus RX comparison](https://soundforgepro.com/sound-forge-pro-vs-izotope-rx/) maps the editions to common failures. ## 5\. WaveLab Pro 13: best for album mastering [Steinberg WaveLab](https://www.steinberg.net/wavelab/) is built around mastering and delivery and still keeps a dedicated Audio Editor. Steinberg’s [WaveLab 13 launch announcement](https://ocl-steinberg-live.steinberg.net/%5Fstorage/asset/913731/storage/master/Press%20Release%20-%202026-01-28%20-%20WaveLab%2013%20-%20EN.pdf) gives suggested US retail prices of $499.99 for Pro and $99.99 for Elements. Check the current regional shop price before you buy. Both run on Windows and macOS, and Elements leaves out some Pro montage, analysis and delivery features. The current [WaveLab 13 release notes](https://www.steinberg.net/wavelab/release-notes/13/) list 13.0.30, released July 22, 2026\. Its Audio Montage, album reports, metadata, batch processor and Dolby Atmos mastering tools make it the better choice when the release is the unit of work. Choose Sound Forge or Acoustica when most jobs remain isolated files. See the full [Sound Forge versus WaveLab comparison](https://soundforgepro.com/sound-forge-pro-vs-wavelab/). ## 6\. REAPER 7.82: best-value full DAW [REAPER 7.82](https://www.reaper.fm/whatsnew.txt) was released October 4, 2026\. It runs on Windows, macOS and Linux and provides multitrack recording, MIDI, instruments, routing, automation, mixing, scripting and custom actions. That is the right move when the missing feature is a production environment rather than a more elaborate file editor. The full evaluation lasts 60 days. A discounted license is $60 for qualifying personal, educational, nonprofit and lower-revenue commercial use; the commercial license is $225\. The [REAPER license page](https://www.reaper.fm/purchase.php) states a $20,000 annual gross-revenue threshold for the discounted commercial route. REAPER can process audio quickly, but opening a project and managing tracks may add friction to hundreds of small file jobs. Many editors keep both categories. Our [Sound Forge versus REAPER guide](https://soundforgepro.com/sound-forge-pro-vs-reaper/) focuses on that division. ## 7\. TwistedWave 33.7: Mac voice-over and batch work [TwistedWave for Mac](https://twistedwave.com/mac) is well matched to voice-over and audiobook editing. Its batch engine handles files or folder hierarchies and can apply Audio Unit or VST effects. Silence splitting and metadata support help with repetitive delivery. Video synchronization and speech recognition are separate add-ons: check the selected plan if you need them. The fully functional demo lasts 30 days. The [TwistedWave release history](https://twistedwave.com/store/changes?platform=mac) lists Mac version 33.7 on August 31, 2026\. The [desktop subscription terms](https://twistedwave.com/store/order%5Fdesktop) offer $9.99 monthly and declining annual pricing. Annual billing grants a fallback license right away, while monthly billing needs 12 consecutive payments first. The fallback covers one specific version and doesn't include unlimited future upgrades. ## Other alternatives worth considering ### WavePad [WavePad](https://www.nch.com.au/wavepad/free-version.html) covers recording, effects, restoration, spectral tools, VST support and batch processing on Windows and Mac. Its free edition is restricted to non-commercial home use. Check the exact paid license and renewal terms before using it for client work. ### Ocenaudio [Ocenaudio downloads](https://www.ocenaudio.com/en/download) cover Windows, macOS and Linux. It is a [lightweight free option](https://soundforgepro.com/ocenaudio-vs-sound-forge/) for opening, trimming and processing recordings. Check the current and legacy Mac builds against your OS. Choose it for simple file work rather than RX-style restoration or album mastering. ### Logic Pro and GarageBand [Apple Logic Pro](https://www.apple.com/logic-pro/) and GarageBand are Mac DAWs, the tools to pick for composing, instruments, multitrack recording and mixing. They solve a different job from a direct Sound Forge-style waveform editor. ## Same owner, different jobs: VEGAS Pro and ACID Pro [Boris FX acquired Sound Forge, VEGAS Pro and ACID Pro](https://blog.borisfx.com/press/boris-fx-acquires-vegas-pro-sound-forge-and-acid-pro) in March 2026, but shared ownership doesn't make the applications substitutes. VEGAS Pro is video-first, and ACID Pro is a loop and music-production DAW. Both can send audio to a file editor, yet neither replaces the day-to-day Sound Forge workflow. Compare [Sound Forge with VEGAS Pro](https://soundforgepro.com/sound-forge-vs-vegas-pro/) or [ACID Pro with Sound Forge](https://soundforgepro.com/acid-pro-vs-sound-forge/) when one of those wider jobs is the real requirement. ## A practical switch test Install the trial or free build, then use one real source file rather than a vendor demo. Time five tasks: open the file, make a sample-accurate repair, run your normal plug-in or chain, export to the required format, and repeat the process across a small folder. Also confirm the audio driver, metadata, channel layout and keyboard commands you rely on. ![Five checks before switching audio editors: originals, plug-ins, export, metadata and listening comparison](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/09/switch-checklist-20260913.webp) Keep the original and run a complete export-and-reopen test before uninstalling the old editor. Before uninstalling anything, save one reference export and a copy of the original file. Record the plug-in format, preset names, sample rate, bit depth, channel layout and metadata fields. Then compare the replacement's render against the reference and reopen it in the destination application. This catches missing tags, channel-order mistakes and plug-in substitutions that a quick listening test can miss. Keep the old editor available until one real job has traveled through the complete replacement workflow. A replacement wins when it removes your bottleneck without creating a larger one elsewhere. If the trial makes routine file work slower, keep Sound Forge and add a specialist only where needed. The [current Sound Forge review](https://soundforgepro.com/sound-forge-pro-review-2026/) explains the jobs it still handles well; the [pricing guide](https://soundforgepro.com/sound-forge-pro-pricing/) gives the cost baseline. For a closer comparison of two candidates, use the [editor comparisons hub](https://soundforgepro.com/tag/comparisons/). ## Frequently Asked Questions ### What is the best free Sound Forge alternative? Audacity 4.0.0 is the current free general replacement for recording, editing, cleanup and export on Windows, macOS and Linux. Review the official Audacity 4 project-format and feature-availability notes before migrating production projects. ### What is the closest paid equivalent to Sound Forge? Acon Digital Acoustica is the closest all-around paid alternative on Windows and macOS. It combines waveform and spectral editing, restoration, processing chains, recording and mastering tools in a general file editor. ### Can Audacity replace Sound Forge Pro? Yes for many recording and manual editing jobs. Audacity 4.0 has sample drawing but does not yet include Macro Manager or the scripting pipe. Check the release notes and test your required effects and exports before replacing a production batch workflow. ### What is the best Sound Forge alternative for Mac? Acoustica is the closest overall Mac alternative. TwistedWave is strong for voice and batch work, WaveLab Pro 13 for album mastering, RX 12 for difficult restoration, and Audacity for a free editor. ### Is REAPER a Sound Forge alternative? REAPER is the better alternative when you need a DAW for tracks, MIDI, instruments, routing and mixing. It can edit audio, but it replaces a broader part of the workflow than a dedicated single-file editor. ### Should I switch from Sound Forge? Switch when a specific missing capability such as Mac support, advanced restoration, album mastering, Adobe integration or full DAW production costs more time than learning another application. Keep Sound Forge when routine file editing is still faster there. Last fact-checked: September 13, 2026. ### Sound Forge Pro 18: Features, Price & Should You Buy It? URL: https://soundforgepro.com/sound-forge-pro-18/ Last updated: 2026-10-09T21:03:11.000Z **Short answer:** keep Sound Forge Pro 18 if your licensed installation, drivers and plug-ins still do the job. It's the 2024 MAGIX release, a different product from today’s Boris FX Sound Forge 2026\. Before you buy an old Pro 18 offer, check the exact edition, upgrade eligibility, transfer conditions and separate plug-in rights, because a low price doesn't mean you'll be able to register the license. *This is a historical version guide. For the product sold today, read the [current Sound Forge review](https://soundforgepro.com/sound-forge-pro-review-2026/) and [current pricing guide](https://soundforgepro.com/sound-forge-pro-pricing/).* ## Sound Forge Pro 18 in one minute MAGIX’s [March 25, 2024 launch announcement](https://www.magix.com/fileadmin/user%5Fupload/Presse/2024/press-release-sound-forge-pro-18-INT.pdf) introduced Sound Forge Pro 18 and Pro 18 Suite. Boris FX [announced its acquisition](https://blog.borisfx.com/press/boris-fx-acquires-vegas-pro-sound-forge-and-acid-pro) of Sound Forge, VEGAS Pro and ACID Pro on March 30, 2026\. The current official product is named Sound Forge 2026; we found no official Pro 19 release in the sources checked. Pro 18 kept the familiar single-file waveform workflow: open or record audio, select a region, process it, then save or render the result. The [original MAGIX launch release](https://www.magix.com/fileadmin/user%5Fupload/Presse/2024/press-release-sound-forge-pro-18-INT.pdf) highlighted Text to Speech through MAGIX Hub, Storyblocks content, plug-in and ARA2 work, 32-channel recording/editing/processing and audio formats up to 64-bit/768 kHz. ## What Sound Forge Pro 18 actually included | Feature or bundle item | Pro 18 | Pro 18 Suite | Evidence limit | | ------------------------------------ | ------------------------------------------- | ----------------------------------- | ----------------------------------------------------------- | | Text to Speech through MAGIX Hub | Yes after rollout; build 21 may be required | Yes | Later moderator evidence qualifies launch-day access | | Storyblocks audio | Documented regionally | Documented regionally | Regional offers may differ | | Ozone 11 Elements and RX 10 Elements | Included in the release offer | Included | Verify the buyer's own installer and serials | | 3D Reverb | No | Suite exclusive | Official MAGIX release | | dynamicEQ oversampling | No | Suite exclusive | Oversampling, not dynamicEQ itself, was the exclusive point | | Melodyne 5 Essential | No | Suite exclusive | Separate third-party entitlement | | SpectraLayers Pro 10 | Not established | Listed in a Japanese regional offer | Not proof of every global bundle | ### Text to Speech: marketed at launch, qualified by build 21 MAGIX marketed Text to Speech through its online MAGIX Hub service. The launch announcement described voiceovers and subtitles in up to 100 languages, and that combined wording doesn't give a confirmed count of spoken voices. In an [October 7, 2024 moderator reply](https://www.magix.info/us/forum/sound-forge-18-voice-for-test-to-voice-question--1337062/), rraud said TTS started out Suite-only and later reached standard Pro 18, possibly needing build 21 or later. The reply names **View > MAGIX Hub** as the historical route. ![Historical Sound Forge Pro 18 Text to Speech route from View > MAGIX Hub to the online service, with rollout and availability caveats](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/10/sf-pro18-text-to-speech-route-v20261005.webp) Historical Pro 18 Text to Speech route through MAGIX Hub. Compare this legacy service with Boris FX’s current workflow. If you own standard Pro 18, check the installed build and the service in your own account. The moderator’s report qualifies the rollout, but it can't promise an old online service still works today, and [MAGIX’s professional EULA, section 8.9](https://www.magix.com/int/eula/professional/), doesn't guarantee that server-based functions stay available. Don't buy a legacy key just for TTS or Storyblocks without confirming you'll actually have access. ### Storyblocks, Ozone and RX The MAGIX launch listed Ozone 11 Elements and RX 10 Elements. [Sourcenext’s May 16, 2024 Japanese offer](https://www.sourcenext.co.jp/pressrelease%5Fhtml/JS/2024/2024051601) documented Storyblocks audio for Pro 18 and audio plus video for Suite. That pins down the regional offer, but every reseller, promotion or purchase date may have come with different rights. Ozone 11 Elements and RX 10 Elements were presented as part of the mastering and restoration offer. Existing owners should still go by their order confirmation, installer list and serial records, since a product logo on an archived sales image can't reactivate a third-party license. ### What the 32-channel and 64-bit/768 kHz claims mean MAGIX described recording, editing and processing for up to 32 channels. That's a channel ceiling; it doesn't mean Pro 18 became a multitrack DAW. Sound Forge still centers work on an audio file or multichannel file rather than a layered MIDI and music-production timeline. The advertised 64-bit/768 kHz maximum is also a capability ceiling; it doesn't make 768 kHz a sensible default for voice, music delivery or archival conversion. The source format, destination specification, converters, plug-ins, storage cost and processing load still determine the working format. Our [sample-rate and bit-depth guide](https://soundforgepro.com/how-to-change-sample-rate-sound-forge-pro/) explains the practical conversion choices. For a legacy workstation, compatibility matters more than the headline maximum. The required driver or plug-in can impose a lower limit than the editor, so check the complete signal path. Test one copy of a real production file through the complete chain before migrating an archive. ## The Pro 18 Suite extras The MAGIX release explicitly marked three additions as Suite-exclusive: 3D Reverb, dynamicEQ oversampling and Melodyne 5 Essential. That oversampling qualifier matters. The claim covers an extra dynamicEQ processing mode and doesn't mean the base editor had no dynamic EQ at all. 3D Reverb was described for surround-capable work from stereo up to 10 channels. Melodyne 5 Essential added pitch and timing tools under its own third-party product entitlement. If either tool still matters to an old project, keep the relevant installer, license account and rendered safety audio before you change hardware. ![Sound Forge Pro 18 Suite 3D Reverb plug-in with the impulse-response view, Room size and decay knobs, Reflections slider and Spatial Balance pad](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/10/sf-pro18-3d-reverb-controls-v20261005.webp) Historical Pro 18 Suite 3D Reverb controls: impulse-response view, Room, Color and Output sections. Sourcenext also listed SpectraLayers Pro 10 in that regional Suite offer. Later reseller listings can name a different SpectraLayers version. Use the order date, installer list and serial record to identify your entitlement rather than treating “Pro 18 Suite” as one unchanging bundle. ## Historical Sound Forge Pro 18 launch prices The figures below are MAGIX list prices from March 2024\. They help you check an old receipt and explain the original Pro-versus-Suite gap, but they aren't current market values or Boris FX offers. Pro 18 launched at $399/€399 for a perpetual license and $199/€199 for an upgrade. Pro 18 Suite was $599/€599, with a $299/€299 upgrade. MAGIX also listed month-to-month and 12-month 365 plans, and the lower 12-month figures were monthly rates under a 12-month commitment rather than annual totals. An old upgrade key isn't necessarily a full license. [MAGIX’s professional EULA, section 2.2](https://www.magix.com/int/eula/professional/), ties an upgrade to owning its qualifying base product and forbids transferring the upgrade on its own. Check the original terms and ask support to confirm the exact order before you pay. Old Pro 18 product cards and prices still turn up in search results and reseller catalogs. On September 15, 2026, the former MAGIX sales URL redirected to the general site, while the [official current product page](https://www.soundforge.com/sound-forge/pricing/) described Sound Forge and Plus. We didn't check a Pro 18 checkout, stock allocation or activation for a newly purchased key, and a surviving listing proves none of those. ## Sound Forge Pro 18 vs Sound Forge 2026 The ownership, naming and bundle structure changed. MAGIX sold Pro 18 and Pro 18 Suite. Boris FX currently sells Sound Forge and Sound Forge Plus with perpetual and subscription choices. The shared single-file editing idea remains, but these are different offers from different owners. The current [Sound Forge product page](https://www.soundforge.com/sound-forge/) describes local Text to Speech processing, while Pro 18 used the online MAGIX Hub route. That's an advertised difference in the service; we haven't tested offline results. Check the current trial, voices and entitlement before you rely on it. For historical compatibility, Sourcenext’s 2024 Pro 18 release lists **Windows 10 and Windows 11, 64-bit**, and the [current Boris FX requirements](https://www.soundforge.com/sound-forge/system-requirements/) list Windows 11\. Keep the two specifications apart: a Windows version on a 2024 list doesn't promise compatibility with every later Windows update, audio driver or plug-in. This guide can't certify a new Windows installation or a native Mac edition. For the present bundle decision, our [Sound Forge versus Sound Forge Plus comparison](https://soundforgepro.com/sound-forge-vs-sound-forge-plus/) separates the shared editor from the four current Plus additions. Don't map the old Pro 18 Suite name straight onto the current Plus tier. ## What Pro 18 users reported Community reports help spot risks, but they don't set product policy. In a [2025 MAGIX forum discussion](https://www.magix.info/us/forum/sound-forge-18-questions-before-buying--1345422/) about buying or upgrading to Pro 18, users described modest changes from version to version, one better ARA experience in a trial and mixed opinions of the available Text to Speech voices. The original poster later called the application mostly fine but found the speech voices unsuitable for professional voice-over work. That evidence is directional; it doesn't prove universal stability, voice quality or compatibility. The useful lesson is narrower: test the actual VST and ARA tools that matter to your workstation, and don't treat a feature list as a substitute for one controlled migration test. ## Should you keep Pro 18, move to current Sound Forge or buy used? ### Keep Pro 18 when the workstation is stable Keep the installation if it's already activated, your interface and plug-ins work, and it completes the jobs you still receive. A stable production machine has value; there's no need to upgrade just because a newer year exists. ### Move when the support path matters Look at the current release when it fixes a compatibility problem you can actually show, or when you need support from the current owner. If the advertised local Text to Speech is what's driving the purchase, check it in the trial. A new PC on its own doesn't mean you need 2026; first see whether the valid Pro 18 license can be reinstalled. Keep the working setup until the interface, plug-ins and exports you need all pass. ### Pause before a used Pro 18 key [Section 7 of MAGIX’s professional EULA](https://www.magix.com/int/eula/professional/) permits transfer of the whole license under conditions: the seller removes installations and backup copies, releases the license slots, and allows the buyer to register it in their own account. Otherwise, express MAGIX consent is required. Section 9 separately applies third-party vendors’ terms. Confirm which contract applies to the exact purchase and have support resolve any account-transfer obstacle before money changes hands. Do not trade account passwords. A [December 2025 Pro 18 resale discussion](https://www.magix.info/us/forum/transfer-my-account-selling-sf-pro-18-acid-pro-11-and-vegas-pro-22--1351096/) shows the practical problem: one respondent reported trouble reaching support, while a moderator described notification and deactivation before resale. That's dated community evidence. It says nothing reliable about today’s response times or whether a specific bundle can transfer. For your own continuing use, keep installers, serials, presets and rendered reference files as far as your license allows. [MAGIX’s download instructions](https://www.magix.com/int/support/technical-support/) point registered owners to **My Products** in the MAGIX Service Center for programs, manuals and serials, and they also describe its Download Center for a valid serial. That's the legacy route, separate from Boris FX Hub, and it can't guarantee a missing entitlement will turn up. ## A safe Pro 18 reinstall checklist 1. **Record the exact build and edition.** Save the installed Pro 18 build number, whether it is standard or Suite, and which online features you actually use. 2. **Check the purchase records.** Confirm the invoice, registered email and serial in your own MAGIX account. Do not post serials or credentials in public support threads. 3. **Separate bundled licenses.** Check the account and entitlement for each promised third-party product. The Pro 18 serial on its own doesn't prove another vendor’s plug-in will activate. 4. **Preserve your working files.** Back up originals, presets and lawful installer copies. Render reference WAV files for work that depends on legacy effects before changing the machine. 5. **Confirm installation rights first.** Check the available license seats and the applicable terms before installing on another physical or virtual computer. Ask support when the account record is unclear, and don't disable your only working setup on a guess. 6. **Run one complete compatibility check.** Once legitimately installed, test interface input/output, the plug-ins you use and an export made from a copy. Reopen and compare the result before retiring the old workstation. Start with the [MAGIX Service Center](https://www.magix.com/us/support/my-service-center/) for Pro 18\. For a move to Boris FX, use our [Pro 18 to 2026 migration comparison](https://soundforgepro.com/sound-forge-2026-vs-pro-18/); the [current installation guide](https://soundforgepro.com/how-to-install-sound-forge-pro/) covers a different installer and account system. Our [Sound Forge buying and setup guides](https://soundforgepro.com/tag/start-here/) connect the version, pricing and system-requirement decisions. ## Frequently Asked Questions ### When was Sound Forge Pro 18 released? MAGIX announced Sound Forge Pro 18 and Pro 18 Suite on March 25, 2024\. Boris FX announced its acquisition of the product line on March 30, 2026. ### What was new in Sound Forge Pro 18? The March 2024 release marked Text to Speech, Storyblocks content and Suite-only 3D Reverb as new. Its other highlights included Ozone 11 Elements, RX 10 Elements, VST/ARA2 support and continuing high-channel-count and high-resolution capabilities; those should not all be read as inventions of version 18\. A later moderator report says standard-edition Text to Speech may require build 21 or later. ### Did the base Sound Forge Pro 18 edition include Text to Speech? MAGIX marketed Text to Speech as a Pro 18 feature. An October 2024 forum moderator reply said it began as Suite-only and standard users might need build 21 or later. Check your build and online account service rather than assuming launch-day access or current availability. ### Did Sound Forge Pro 18 include 3D Reverb? Only Pro 18 Suite included 3D Reverb. MAGIX also marked dynamicEQ oversampling and Melodyne 5 Essential as Suite-exclusive. ### How much did Sound Forge Pro 18 cost? Historical March 2024 list prices were $399/€399 for Pro 18 and $599/€599 for Pro 18 Suite. Upgrade prices were $199/€199 and $299/€299\. These are not current Boris FX offers. ### Is Sound Forge Pro 18 the same as Sound Forge 2026? No. Pro 18 is the 2024 MAGIX release. Sound Forge 2026 is the current Boris FX product with different tier names, a Windows 11 specification and advertised local Text to Speech. Confirm the speech workflow in the current trial rather than assuming it behaves like MAGIX Hub. ### Can I still use Sound Forge Pro 18 in 2026? Yes, if an existing license remains activated and the Windows, driver and plug-in setup is stable. Continued use does not guarantee support after a hardware or operating-system change, so archive installers, serials and presets first. ### Should I buy a used Sound Forge Pro 18 license? Only after confirming the exact license and transfer conditions. MAGIX’s professional EULA allows whole-license transfers under stated conditions, not isolated upgrade transfers. Check the seller’s release of the license and each third-party vendor’s terms before paying. ### Was Sound Forge Pro 19 released? The official current product is Sound Forge 2026\. We found no official Sound Forge Pro 19 release in the sources checked; an old forum prediction is not a release announcement. ### Where can an existing owner download Sound Forge Pro 18? Use the MAGIX Service Center account associated with the purchase. MAGIX’s technical support page directs registered owners to My Products for downloads, manuals and serials, or to its Download Center with a valid serial. Confirm missing downloads with support rather than using unofficial mirrors or shared keys. Last fact-checked: September 15, 2026\. This historical guide uses MAGIX’s launch material, Sourcenext’s regional release, current vendor pages and attributed forum reports. We did not test Windows activation, a used-license transfer, paid checkout or the online speech service. ### Sound Forge vs Sound Forge Plus: Which Should You Buy? URL: https://soundforgepro.com/sound-forge-vs-sound-forge-plus/ Last updated: 2026-10-09T20:58:55.000Z Sound Forge Plus is the same Sound Forge editor bundled with four additional tools: Melodyne 5 Essential, Vandal, VariVerb II and 3D Reverb. The base tier already covers waveform editing, repair, batch processing, multichannel audio and VST hosting. Buy Plus when one of its four extras solves a job you expect to repeat. Otherwise, start with Sound Forge and keep the price difference for a tool you know you need. *Part of the [Sound Forge comparisons](https://soundforgepro.com/tag/comparisons/). For current prices and license terms, use our [pricing guide](https://soundforgepro.com/sound-forge-pro-pricing/) alongside the official Boris FX store.* **Quick answer:** choose **Sound Forge** for editing, cleanup, batch work and export. Choose **Sound Forge Plus** if you need bundled monophonic pitch correction, guitar or bass amp tone, algorithmic ambience, or spatial reverb. There's no point paying for Plus because the name sounds more complete; the editing engine and core workflow are shared. ![Sound Forge and Sound Forge Plus feature comparison showing the shared editor and four Plus extras](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/08/tier-core-desktop.webp) Both tiers use the same Sound Forge editor. Plus adds Melodyne 5 Essential, Vandal, VariVerb II and 3D Reverb. ## Sound Forge vs Sound Forge Plus at a glance The current offer is one core editor, with a larger bundle in Plus. Neither tier is a multitrack music-production DAW. Everything below comes from the vendor's published feature matrix; there's no performance benchmark behind it. | Capability | Sound Forge | Sound Forge Plus | What changes in practice | | -------------------------------------- | ----------- | ---------------- | ------------------------------------------------------- | | Waveform editing, recording and repair | Included | Included | The core editor is the same | | Batch processing and multichannel work | Included | Included | Plus does not unlock a different editing engine | | VST2, VST3 and ARA support | Included | Included | Your existing compatible effects can run in either tier | | Melodyne 5 Essential | Not bundled | Bundled | Basic monophonic pitch and timing correction | | Vandal | Not bundled | Bundled | Guitar and bass amp, cabinet and microphone tone | | VariVerb II | Not bundled | Bundled | Algorithmic reverb and ambience | | 3D Reverb | Not bundled | Bundled | Spatial placement and multichannel room work | ## What both versions already include The base tier isn't a stripped-down trial edition. According to the current [Boris FX feature matrix](https://www.vegascreativesoftware.com/sound-forge/pricing/), both tiers include sample-level editing, recording, meters, coreFX and essentialFX processing, dynamic EQ, VST2, VST3 and ARA support, audio repair, text-to-speech, broadband noise reduction, multichannel audio, automatic record start, batch processing and event-based editing. In practice, the ordinary Sound Forge workflow is all there before Plus comes up. With either tier you can trim a voice recording, cut a bad section, normalize or limit a file, run a compatible VST chain and render a whole folder. Our [current Sound Forge review](https://soundforgepro.com/sound-forge-pro-review-2026/) covers where that single-file workflow is quick and where a DAW or a dedicated restoration suite does the job better. ARA support shows up in both columns too. Plus matters because it ships Melodyne 5 Essential; the integration layer is already in the base editor. If you own a compatible pitch editor, reverb or amp simulator that runs in your setup, check that license before paying for tools you already have. ## What Sound Forge Plus actually adds Plus adds four specialist products, and each does a different job, so weigh them one at a time. One extra you'll actually use can justify the bundle. Four you'll never open can't. ### Melodyne 5 Essential: basic monophonic pitch and timing work Melodyne 5 Essential is the relevant Plus extra for a solo vocal, bass line or other monophonic performance that needs pitch-center, drift or timing correction. Celemony's current [edition comparison](https://www.celemony.com/en/melodyne/melodyne-5-editions) says Essential uses the Main Tool for pitch, timing, duration and note separation and includes pitch, timing and leveling macros. Its Correct Pitch Macro documentation confirms separate controls for [pitch center and pitch drift](https://helpcenter.celemony.com/M5/doc/melodyneEssential5/en/M5tour%5FMacroPitch?env=standAlone). The limit is important. Essential doesn't include Direct Note Access for editing individual notes inside chords. Celemony's [Essential quick-start guide](https://helpcenter.celemony.com/M5/doc/melodyneEssential5/en/M5tour%5FQuickStart%5Fessential) also reserves the larger dedicated toolset, including vibrato and formant tools, for higher editions. Essential also handles percussion and whole-mix transposition, quantizing and time-stretching. That is different from separating and editing individual notes within a chord; it does not provide the full Editor or Studio toolset. **Current vendor wording conflicts.** Boris FX currently advertises Melodyne Essential with “pitch drift and modulation control.” Celemony’s Essential documentation says its drift macro leaves rapid modulation such as vibrato unaffected, while dedicated modulation tools belong to higher editions. If modulation control is the reason you want Plus, verify the exact bundled license and toolset with Boris FX or Celemony before buying. ### Vandal: guitar and bass amp tone from a DI track Vandal is the Plus extra for an unamplified guitar or bass recording that needs an amp, speaker cabinet and microphone chain. Boris FX describes controls for amplifier, speaker, cabinet and microphone choices. That makes it useful when the source is a clean DI track and you want to build or revise the tone after recording. If your work is spoken-word cleanup or batch conversion, Vandal is a thin reason to upgrade. Those routine jobs don't need an amp simulator, though you might want one for deliberate sound design. If you already own one, compare its sounds and license with Vandal before you count the bundle as a saving. ### VariVerb II: algorithmic reverb and ambience VariVerb II supplies selectable reverb types, presets, room-size control and reverb amount. It suits everyday ambience work: giving a dry voice a room, adjusting a reverb tail or placing an isolated sound in a believable acoustic space. Judge it on a dry source against the room or tail you actually need, because a feature list won't tell you how it sounds. Both tiers can host compatible VST effects, so Plus isn't the only way to add reverb. If you already have a reverb you trust, the bundle may simply duplicate it. If you're still learning the processing order, our [Sound Forge reverb workflow](https://soundforgepro.com/how-to-add-reverb-in-sound-forge-pro/) explains how to set the effect by context rather than preset name. ### 3D Reverb: placement, depth and multichannel rooms 3D Reverb is the more specialized spatial tool. Boris FX positions it for virtual three-dimensional rooms, reflection and depth control, source placement and stereo-to-multichannel work. That can matter for sound design, surround delivery and scenes where front-to-back placement is part of the result. For a stereo voice-over or a music file that just needs a small room, VariVerb II or any conventional reverb is usually the shorter path. Reach for 3D Reverb when you have a defined spatial problem to solve. A more advanced-sounding name isn't a reason on its own. ## Choose by workflow, not by the number of plug-ins Start with the file you deliver most often. The table below separates recurring jobs from occasional curiosity. It also keeps one false choice out of the comparison: neither tier turns Sound Forge into a full multitrack DAW with a MIDI arrangement workflow. | Your recurring job | Better starting point | Reason | | ------------------------------------------------------ | --------------------- | ----------------------------------------------------------------- | | Cut, clean, normalize and export individual files | Sound Forge | Those jobs use the shared editor | | Process folders with repeatable chains | Sound Forge | Batch processing is in both tiers | | Correct pitch and timing on solo vocals or instruments | Check Plus | Melodyne 5 Essential is the relevant extra | | Shape DI guitar or bass tone | Check Plus | Vandal is the relevant extra | | Add algorithmic ambience regularly | Compare both | Both tiers host VST effects; Plus bundles VariVerb II | | Place sound in spatial or multichannel rooms | Check Plus | 3D Reverb is the relevant extra | | Mix a layered music session with MIDI | Choose a DAW first | The tier decision does not turn Sound Forge into a multitrack DAW | For mastering a single stereo file, either tier gives you the shared editor and compatible effects. Buy Plus for a processor you'll actually use. This comparison doesn't show any rendering-speed difference, so don't count on one. If the work is a podcast series, a layered music mix or a MIDI composition, settle the host application first. Our [Sound Forge alternatives guide](https://soundforgepro.com/best-sound-forge-alternatives/) compares tools by workflow rather than forcing every job into this two-tier choice. ## Prices and license terms: launch figures versus checkout Boris FX announced these US prices on [March 30, 2026](https://blog.borisfx.com/press/boris-fx-acquires-vegas-pro-sound-forge-and-acid-pro). They're dated launch list prices, and a September 15 checkout quote may look different. Currency, tax, offers and your eligibility can all change the total. On a narrow screen, scroll the price table sideways to compare both tiers and the premium. | License route | Sound Forge | Sound Forge Plus | Plus premium | | --------------------------------- | ------------ | ---------------- | ------------ | | Monthly subscription | $24.95/month | $33.95/month | $9/month | | Annual subscription | $149.95/year | $199.95/year | $50/year | | New perpetual license | $299.95 | $399.95 | $100 | | Announced Upgrade & Support route | $189.95 | $249.95 | $60 | The same announcement gives owners of earlier MAGIX Sound Forge versions a simplified upgrade through December 5, 2026\. Check your eligibility and the final quote before you pay. The upgrade row doesn't mean every customer can renew at that price or step from base to Plus for $60. A subscription buys access for its paid term. Under [Boris FX’s license terms, sections 2, 3 and 5](https://borisfx.com/store/eula/), a new perpetual license includes one year of Upgrade & Support; perpetual use and ongoing update coverage are separate. Renewals are charged at the then-current price. The terms describe annual support renewal, so check the order’s renewal settings and cancellation conditions rather than assuming a one-off payment ends every future charge. The [general Upgrade & Support policy](https://borisfx.com/store/upgrade-and-support-plan/) says a perpetual license keeps working after its support contract expires. It doesn't promise free future versions. Check how your order treats bundled third-party licenses, host use and subscription expiry. Nothing here shows that every Plus component carries identical rights or keeps working after cancellation. ## Windows requirements and older Suite bundles The [current system requirements](https://www.soundforge.com/sound-forge/system-requirements/) list Windows 11 for both tiers. Plus is not a macOS edition. The listed application installation space is 1,100 MB for Sound Forge and 1,400 MB for Plus, before audio files and backups. Check the [full PC requirements](https://soundforgepro.com/sound-forge-pro-system-requirements/) before choosing either license. Don't map the older Pro 18 Suite name straight onto Plus. The current matrix lists the four extras above and doesn't promise Ozone, RX or SpectraLayers. An absent entry doesn't prove that an older license you already own disappears, either. Our [Pro 18 migration comparison](https://soundforgepro.com/sound-forge-2026-vs-pro-18/) separates the historical bundles from a new purchase. ## Three checks before buying ### 1\. Check the exact Melodyne entitlement Don't read “Melodyne included” as “every Melodyne feature included.” Essential is the named bundle edition. In Celemony's own lineup, note-to-MIDI export starts with Assistant, and editing individual chord notes needs Editor or Studio. Those are Melodyne edition differences; buying Sound Forge Plus doesn't add them. ### 2\. Check what the 15-day trial installs The [official Sound Forge trial](https://vfx.borisfx.com/sound-forge-trial) is advertised as full-featured for 15 days with no credit card. That page doesn't clearly promise all four Plus products, so ask Boris FX which extras you can evaluate before treating the editor trial as a Plus trial. This guide doesn't cover paid activation or third-party entitlement delivery. ### 3\. Check the upgrade path before relying on it The current public comparison page shows what each tier contains, but it doesn't state a universal Sound Forge-to-Plus upgrade policy or promise that every bundled product can be purchased later on identical terms. Celemony does describe paid upgrades between its own Melodyne editions, but that's a Celemony license path and says nothing about a Boris FX bundle upgrade. Ask Boris FX for the current route if buying base now and moving to Plus later is part of your budget. ## Is Sound Forge Plus worth it? Calculate the avoided purchase Compare the same license type and billing period. With the announced perpetual prices above, $399.95 minus $299.95 leaves a $100 Plus premium. If a bundled tool replaces a hypothetical $150 purchase you'd really planned, you save $50 before tax. The $150 is an illustration rather than a quoted plug-in price, so redo the sum with the offers actually open to you. **Potential purchase saving = genuinely avoided tool cost − Plus premium.** If you would not otherwise buy a tool, there is no avoided purchase to count. Any remaining justification needs to come from useful features or workflow benefits you can actually demonstrate. Also check whether you already own a suitable VST effect, whether its license covers your current machine and whether the bundled edition has the control you need. A cheap duplicate isn't a saving. One tool that replaces a planned purchase can be. ## Verdict: start with the job For most people buying Sound Forge for precise single-file editing, cleanup, batch processing and export, the base tier is the sensible place to start. It's the same editor, and the shared feature list already covers the work that makes Sound Forge worth having. Choose Sound Forge Plus when you can name the recurring job and the bundled tool that handles it: Melodyne Essential for basic monophonic pitch and timing correction, Vandal for DI guitar or bass tone, VariVerb II for algorithmic ambience, or 3D Reverb for spatial and multichannel rooms. Verify the Melodyne feature wording, trial contents and current upgrade route if any of those details decide the purchase. ## Frequently Asked Questions ### Is Sound Forge Plus a different audio editor? No. Boris FX lists the same core Sound Forge editing features in both tiers. Sound Forge Plus adds four bundled tools: Melodyne 5 Essential, Vandal, VariVerb II and 3D Reverb. ### What does Sound Forge Plus include that Sound Forge does not? Plus bundles Melodyne 5 Essential for basic monophonic pitch and timing correction, Vandal for guitar and bass amp tone, VariVerb II for algorithmic reverb and ambience, and 3D Reverb for spatial and multichannel room work. ### Does the base Sound Forge version support VST plug-ins? Yes. The current Boris FX comparison lists VST2, VST3 and ARA support in both tiers. Plus changes the bundled products, not the core plug-in hosting capability. ### Can Melodyne 5 Essential edit chords note by note? No. Celemony reserves Direct Note Access, which edits individual notes inside polyphonic material, for Melodyne Editor and Studio. Essential can still process percussion and entire mixes for tasks such as timing or whole-signal transposition; it cannot independently edit the notes within a chord. ### Does Melodyne 5 Essential control vibrato? Celemony's Essential documentation says the Correct Pitch Macro can reduce pitch drift but leaves rapid pitch modulation such as vibrato unaffected. Boris FX currently uses broader modulation-control wording, so verify the exact bundled toolset if that feature decides your purchase. ### Are the four Plus plug-ins included in the 15-day trial? Boris FX describes a fully functional 15-day Sound Forge trial but does not clearly define the Plus plug-in entitlement in the public trial wording. Inspect the products offered in Boris FX Hub or confirm the bundle with Boris FX before treating the trial as a test of all four extras. ### Can I upgrade from Sound Forge to Sound Forge Plus later? The current public comparison page does not state a universal base-to-Plus upgrade policy. Confirm the current upgrade route and price with Boris FX before buying the base tier if a later move to Plus is part of your plan. ### Which tier should I buy for ordinary editing and batch processing? Start with Sound Forge. Editing, repair, batch processing, multichannel audio and VST hosting are shared. Choose Plus only when one of its four additional tools solves a recurring job. Last fact-checked: September 15, 2026\. Based on current vendor documentation and published pricing, not a new Windows performance test or an authenticated checkout quote. ### Sound Forge VST Plugins Not Showing? 7 Fixes (2026) URL: https://soundforgepro.com/sound-forge-pro-vst-plugins-not-showing/ Last updated: 2026-10-09T22:08:29.000Z If a [VST effect](https://soundforgepro.com/what-is-a-vst-plugin/) is missing in Sound Forge, check the installed effect build and its folder before reinstalling the editor. In **Options → Preferences → VST Effects**, add the actual folder if needed and click **Refresh**. Once the scan discovers the effect, select its availability checkbox. Then search **All** in **View → Plug-In Manager**. These controls follow the Boris FX Sound Forge 2026 help. Older Sony and MAGIX versions can have different folder controls and plug-in support. A file showing up during a scan doesn't prove Sound Forge accepted it, and an effect showing up in a list doesn't prove it can process audio. Use the [Sound Forge troubleshooting hub](https://soundforgepro.com/tag/troubleshooting/) if your main problem is startup, playback or recording rather than a missing effect. For an incomplete editor installation, follow the [Sound Forge installation guide](https://soundforgepro.com/how-to-install-sound-forge-pro/) first. ## Identify the failure before changing settings - **No entry after Refresh:** check the installed format, actual file, search folder and any scan error. Compatibility or failed initialization remains possible even when the path is correct. - **Entry present but unchecked:** enable its availability checkbox. That still doesn't tell you whether its license or processing works. - **Present in All but not Favorites:** the installation is fine; fix the shortcut or filter. - **Listed but blank, silent or asking for authorization:** discovery has progressed far enough to expose the effect. Investigate its interface, license and processing separately. - **Scan hangs or closes the application:** note the message and the last displayed product, if any. That name is a lead. It hasn't been proven guilty yet. Before testing, save your work, record the Sound Forge edition/build and the plug-in version, format and install location. Keep a short audio copy for later processing checks. Change one setting at a time and record the result. ## The seven-check repair order 1. Confirm that the vendor installed a Windows audio-effect format supported by your exact Sound Forge version. 2. Locate the installed VST2 file or VST3 file/bundle without moving or renaming it. 3. Compare its folder with Options → Preferences → VST Effects and add only the missing, specific search path. 4. Run Refresh, let it finish, then enable the discovered effect. Record errors instead of repeatedly rescanning a failed installation. 5. Search All in View → Plug-In Manager, clear stale search text and inspect the type filters. 6. Separate a rejected or hanging scan from a graphical-editor or licensing problem. 7. If you deliberately hid the effect, use version-matched vendor help or support rather than a general registry or cache cleanup. ## 1\. Check format, architecture and edition You need a Windows audio effect; a standalone program with the same product name won't do. Installing only an AAX or Audio Unit component won't supply the VST effect this list needs. Boris FX documents [DirectX and VST effects in Sound Forge](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/applying%5Fprocesses%5Fand%5Feffects.htm). A DirectX-only legacy effect uses a different discovery mechanism, and adding VST folders won't repair its registration. The current help describes an audio-effect workflow. There's no playable MIDI/VSTi instrument rack. If your missing product is a synthesizer or sampler, use a DAW or instrument host that supports it, render the audio and edit that file in Sound Forge. An instrument and its separately supplied effect version aren't interchangeable. Don't confuse a plug-in's 32/64-bit architecture with an audio file's bit depth. The host build and plug-in build must be compatible, and converting a WAV file to 32-bit float can't fix a binary mismatch. The [historical Pro 12 announcement](https://www.magix.com/int/magazine/music/brand-new-sound-forge-pro-12/) introduced the 64-bit version and full VST3 support in 2018, so today's VST3 instructions don't apply to Pro 11 as if it were the same host. Sound Forge 2026's Manager groups entries by VST generation and 32/64-bit type. Those categories don't guarantee every old binary will load. Check the vendor's supported host/build requirements before you install a legacy bridge or buy an upgrade, and use a VST2 alternative only if the vendor actually supplies a compatible one. ## 2\. Locate the actual plug-in file Read the destination recorded by the vendor installer. On Windows, VST2 plug-ins use `.dll`; VST3 plug-ins use `.vst3`. Steinberg's [Windows VST3 format reference](https://steinbergmedia.github.io/vst3%5Fdev%5Fportal/pages/Technical%2BDocumentation/Locations%2BFormat/Plugin+Format.html) describes the current bundle directory and the older single-file form. Do not extract an internal DLL from a VST3 bundle or rename a DLL to VST3. Steinberg's [VST3 location specification](https://steinbergmedia.github.io/vst3%5Fdev%5Fportal/pages/Technical%2BDocumentation/Locations%2BFormat/Plugin+Locations.html) defines these Windows paths: - `C:\Program Files\Common Files\VST3`: the usual global 64-bit location on 64-bit Windows. - `%LOCALAPPDATA%\Programs\Common\VST3`: the current user's location, described primarily for development use. - `C:\Program Files (x86)\Common Files\VST3`: 32-bit VST3 on 64-bit Windows. The folder existing doesn't make that build compatible with your host. These are specification locations. They don't prove every older Sound Forge version scans every path automatically, so check the actual folder in Preferences. VST2 has no single mandatory folder; examples include `C:\Program Files\VSTPlugins`, `C:\Program Files\Steinberg\VSTPlugins` and `C:\Program Files\Common Files\VST2`. Your installer's destination beats any example. Steinberg's [Windows plug-in installation guidance](https://helpcenter.steinberg.de/hc/en-us/articles/115000177084-VST-plug-in-locations-on-Windows) explains why moving a plug-in can break associated files and installation data. Use the manufacturer's repair or reinstall procedure if the install is incomplete. Preserve presets and check license/reactivation requirements first. Do not move an entire shared plug-in folder or download a replacement DLL from an unofficial site. ## 3\. Correct the specific search path Open **Options → Preferences → VST Effects**. Under **VST search folders**, compare the listed paths with the verified installation folder. Use **Add path** for a missing folder or **Edit path** for a wrong entry. **Remove path** only removes a search location; it won't uninstall a plug-in. The [current VST Effects Preferences reference](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/vst%5Feffects%5Fpreferences.htm) documents these controls and the availability checkboxes. If the effect isn't listed yet, you can't enable it until discovery succeeds. Avoid adding a drive root or the whole of `C:\Program Files`. A narrow, verified folder makes a failed scan much easier to investigate. ## 4\. Refresh, then enable the discovered effect Click **Refresh** in the VST Effects tab and allow the scan to finish. Then select the effect under **Select VST effects to be available as audio plug-ins**. Clear a checkbox only when you mean to exclude that entry. Finish the vendor installation before rescanning. If setup or an authorization prompt asks you to do something, follow the instructions for that exact product. A license problem is one possible failure, but it shouldn't be the default explanation for a missing name. A product can also be discovered before authorization succeeds. If the scanner reports a failure or names a file but never adds it, save the exact message and build details. An effect that never appears has no availability checkbox to enable. The current Preferences reference documents Refresh, but no general blacklist repair sequence. A second rescan after a documented repair is useful. Repeating the same failed scan with nothing changed tells you nothing new. ## 5\. Check All, search text and display filters Choose **View → Plug-In Manager** and select **All**. Clear old search text, then try a distinctive part of the effect name, since a previously renamed entry may not use the vendor's original name. Check **Third Party** for vendor folders and **By Type** for format/architecture categories. In the options view, make sure the relevant effect type isn't excluded. ![Sound Forge Plug-in Manager with numbered folder tree, FX Favorites, refresh button, search field and plug-in type options](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/09/sf-plugin-manager-tree-favorites-options.webp) In the Plug-In Manager, the folder tree is 1, FX Favorites 2, refresh 3, search 4 and the type options 5\. An unchecked type is hidden from the list. The [Plug-In Manager documentation](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/proonly/plug-in%5Fmanager.htm) distinguishes its folder refresh from the Preferences rescan. The Manager's refresh button rereads folder contents; **Preferences → VST Effects → Refresh** is the documented step after a new plug-in installation. Favorites is a custom shortcut layer. If the effect appears in All, use it there or add a Favorites shortcut afterward. Test on your saved audio copy: double-clicking an effect targets the selection, or the whole file if nothing is selected. Dragging an effect to a data window adds it to that window's chain. The [Plug-In Chain guide](https://soundforgepro.com/how-to-use-plug-in-chainer-sound-forge-pro/) covers previewing and committing processing after discovery works. ## 6\. Separate scan, GUI and license failures For a listed effect with a blank or unusable graphical window, try **Generic VST editor** in VST Effects Preferences. Boris FX documents it as an interface fallback. If the generic controls work, the vendor editor or its interaction with the host is the likely suspect. That still doesn't prove every processing function, preset or authorization state is healthy. Restore the previous setting if the fallback doesn't help. If a scan hangs, save the last displayed name and error before changing anything. If a suspect VST2 product has its own separate search folder, note that path before temporarily removing it from the search list. Check the remaining paths without opening or saving projects that depend on the excluded effect, then restore the path. This only tests that location and won't prove which file caused the hang. For a shared folder, use vendor-guided product repair or isolation instead of moving all its files. If the editor cannot open, the [startup-crash troubleshooting page](https://soundforgepro.com/sound-forge-pro-wont-open-crashes-startup/) addresses that broader symptom. Keep this investigation product-specific: do not copy scanner executables between Sound Forge editions, disable antivirus, clear all application caches or delete registry trees. Compatibility can still be the problem after the scan path is right. [Ozone 12 Advanced's current specifications](https://www.izotope.com/products/ozone-advanced), for example, list 64-bit AAX, AU and VST3, with no VST2\. Sound Forge isn't named in the supported-host list checked for this guide. That doesn't prove it never runs, but it isn't vendor certification either. A VST2 reinstall isn't an option for Ozone 12. A [2025 Audio Studio 17/Ozone 11 forum discussion](https://www.magix.info/us/forum/sound-forge-audio-studio-17-doesn-t-detect-ozone-11-standard-vst3--1344763/) describes a file being seen during scanning but never added. It's a historical, build-specific user report and doesn't show that current Sound Forge rejects all iZotope effects. Check the exact vendor requirements and contact support with your edition, build, format, path and error. For licensing, also separate the purchased edition from the delivery channel. iZotope explains that [Ozone Standard supplied through Komplete is activated through Native Access](https://support.izotope.com/hc/en-us/articles/47669754309133-Ozone-Standard-from-Komplete-appears-in-Full-Trial-mode); its Product Portal “Full Trial” label doesn't necessarily restrict an activated installation. Don't stretch that exception to other products or use it to wave away a real authorization failure. ## 7\. Handle deliberately hidden effects separately In the current Manager, **Hide** suppresses a plug-in without uninstalling it. It differs from deleting a Favorites shortcut or excluding an effect type from display. If you remember hiding the entry, use the matching Manager help or contact support after checking the ordinary filters. The 2026 help documents a version-specific `DXCache` registry reset to restore hidden plug-ins. It isn't a general missing-VST fix, and it shouldn't be transplanted to Sony or MAGIX installations. Ask support to confirm the exact scope and recovery procedure before using it, and save the affected settings first. Do not delete parent keys, licensing data or unrelated cache folders. ## Verify that the recovered effect actually works At low monitoring volume, load the effect on a short, noncritical audio copy. Compare bypassed and processed playback with an obvious but safe setting. If the product ships presets, check that they load. Commit the processing with the appropriate effect/chain workflow, save under a new name and reopen the result, because a visible entry alone doesn't show that rendering works. Keep the plug-in version, Sound Forge build and the format/path that worked with your notes. If an update breaks it again, that record lets support compare two known states. ## Frequently asked questions ### Why is the plug-in named during scanning but missing afterward? The scanner may reach a file without successfully registering or initializing its effect. Verify compatibility and any error, then check availability and Manager filters. Repeated Refresh attempts cannot fix an unsupported build or incomplete installation by themselves. ### Does Sound Forge 2026 support VST3 effects? Yes. The current Manager documentation distinguishes VST2 and VST3 effects. Support for a format is not a guarantee for every vendor build, architecture or license state. Test the exact effect on a disposable audio copy. ### Which VST3 folder should I check on Windows? For a typical 64-bit installation, start with C:\\Program Files\\Common Files\\VST3\. Steinberg also defines a per-user location at %LOCALAPPDATA%\\Programs\\Common\\VST3 and an x86 global location for 32-bit VST3\. Verify the installer's actual destination and your host's search settings. ### Why is the effect absent from FX Favorites? Favorites contains custom shortcuts. Search All, clear stale search text and check the type filters in Plug-In Manager. If the effect is there, use it from All and add a Favorites shortcut if useful. ### Can Generic VST editor fix a missing effect? It is an interface fallback for a discovered effect with a problematic graphical window. It does not install the plug-in, repair its search path or guarantee authorization and processing. ### Will a VST instrument appear as an audio effect? Do not expect a synth or sampler to become a playable instrument in Sound Forge's documented audio-effect workflow. Use a compatible instrument host to render audio, then edit the rendered file in Sound Forge. ### Should I delete DXCache or all plug-in caches? No general cache deletion is recommended. The 2026 Manager help documents a specific hidden-plug-in reset, not a universal repair. Confirm the exact version, scope and recovery procedure with support before changing registry settings. ### Should I switch every failing VST3 plug-in to VST2? Only consider a compatible VST2 build when the vendor supplies one for your host. Ozone 12 Advanced, for example, lists VST3 but no VST2\. Preserve existing projects and presets before changing formats; do not assume the replacement restores saved settings. Documentation and source checks: September 17, 2026\. Historical reports are labeled by version and date. ### Sound Forge No Sound? Fix Playback, ASIO & Moving Meters URL: https://soundforgepro.com/sound-forge-pro-no-sound/ Last updated: 2026-10-06T06:54:49.000Z **If Sound Forge has no sound, check the playback route before reinstalling or changing the file.** Play a short stereo file you know has sound in it and watch the playback cursor and the channel meters. Moving meters point you toward the selected driver, the output assignments and the monitor path, though they don't prove the speakers are getting audio. Flat meters call for a different check: is playback running, does the selected section contain sound, and has the audio device actually opened? The current Sound Forge 2026 help puts these controls under **Options > Preferences > Audio**. Select the intended **Audio Device Type**, click **Apply**, then look at the **Playback** channel-to-device assignments. Older Pro versions may label preferences differently, so if the labels don't match, use the help for your installed version. **Before testing:** save your work, leave the original audio unchanged, and turn headphone or speaker volume down before you reconnect cables or change routes. Make one change, play the same test file and note the result. What you're after is a working signal path. A pile of unrelated resets won't get you there. ## Identify which kind of silence you have | Symptom | Next check | Do not assume | | ---------------------------------------------- | ----------------------------------------------------------------- | ---------------------------------------------------- | | Cursor and both playback meters move | Driver, output pair, interface mixer and physical volume | That a moving meter proves the hardware output works | | Cursor moves, meters stay flat | Selected audio section, playback processing and a known-good file | That the original file is necessarily empty | | Cursor does not move or a device error appears | Transport state, selected device and exact error message | That normal playback has started | | Only one side or one file is silent | Compare file channels and routes with a known stereo file | That converting to mono fixes the cause | | Windows and other apps are also silent | Windows output, hardware and driver status | That Sound Forge caused the system-wide problem | | Saved files play, but live input is inaudible | Recording and input-monitoring setup | That playback routing alone configures recording | Watch the playback meters while a file plays; the input meters while you wait to record tell you nothing here. If an existing file plays but a new recording is silent, follow the separate [Sound Forge input and recording checks](https://soundforgepro.com/sound-forge-pro-not-recording-audio/). Hearing a microphone through an interface's direct monitor doesn't prove Sound Forge recorded it. ## Choose the driver that reaches your speakers The [current Audio Preferences help](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/audio%5Fpreferences.htm) lists three driver choices: - **Microsoft Sound Mapper:** lets the Windows Sound Mapper choose appropriate playback and recording devices. Use it as a comparison when you want to test the Windows playback path; still verify the actual output rather than assuming the default reached your headphones. - **Windows Classic Wave Driver:** lets you choose a specific audio device through a classic Wave driver. - **ASIO:** selects a specific low-latency ASIO device. For an interface, use its manufacturer's compatible driver when available and monitor that interface's outputs. Switching the Windows taskbar output won't select the right device inside Sound Forge for you. A session on an interface's ASIO driver can stay routed to that interface while Windows sends browser audio to a monitor, a Bluetooth headset or the laptop speakers. Apply the device choice before you open **Advanced**. If the device is missing, save and close Sound Forge, check that the interface is connected and its manufacturer driver is installed, then reopen the application. Installing an unrelated ASIO wrapper or editing the registry shouldn't be your first no-sound experiment. ## Map both channels to the outputs you monitor Under **Audio > Playback**, the **Channel** and **Device** columns decide which output plays each file channel. Click a **Device** entry to pick a different output, and for a stereo file check both assignments. An interface's outputs 1/2 aren't automatically its headphone mix, and an unused output pair can stay silent at the speakers you're listening to. The same Boris FX help documents another route: click a channel number in the **Channel Meters** window and choose an output port. Use the names your driver actually shows; the port names in the help illustration are only samples. ![Sound Forge Channel Meters with the output-port menu open for the left playback channel](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/09/sf-channel-meters-output-port-menu.webp) Click the channel label above its meter and choose its output port. Driver names and available ports vary by system. If your interface has a software mixer, follow that output into the mixer and on to the physical headphone or speaker socket. [Focusrite's Scarlett 18i20 routing guide](https://userguides.focusrite.com/hc/en-gb/articles/21616151554578-Using-Focusrite-Control-2-with-your-Scarlett-18i20), for example, separates physical outputs from their source, which can be a DAW playback channel or a custom mix. That's one model's layout, and not every interface has that menu. Look for muted software playback, a lowered monitor level or a headphone mix that carries only live inputs. ## Check Windows app volume and the actual endpoint On a Windows playback path, open **Settings > System > Sound > Volume mixer** in Windows 11\. Under **Apps**, check Sound Forge's mute state, volume and output device. If the application isn't listed, start file playback first. [Microsoft's app-audio instructions](https://support.microsoft.com/en-us/windows/hardware/audio/fix-app-audio-not-working-while-system-sounds-work-in-windows) explain that an app's volume and output can differ from the system settings. Check where the cable or wireless connection actually ends up. An HDMI monitor without speakers makes no sound. With Bluetooth headphones, confirm that Windows can play through the connected headset first, then try Sound Forge again on the intended Windows route. Don't expect an interface's native ASIO driver to send its output to unrelated Bluetooth headphones. Windows Volume Mixer is a useful check on the shared path, but it doesn't control native ASIO or exclusive-mode streams. If you use ASIO on purpose, work through the interface driver and its monitored output instead of moving the Windows volume slider again and again. ## Handle ASIO and device-busy errors separately After selecting ASIO and clicking **Apply**, open **Advanced > Configure**. The [Advanced Audio Configuration documentation](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/advanced%5Faudio%5Fpreferences.htm) says this opens the driver manufacturer's configuration applet. Its buffer, sample-rate and clock controls depend on the device. Save and close other audio applications, then reopen Sound Forge and retry the same file. If that changes the result, you've found an access conflict worth investigating, though it doesn't prove every ASIO driver is single-client. Follow the manufacturer's sharing restrictions for your exact driver. In the same way, don't assume one native ASIO session can record through an interface while playing through an unrelated laptop output. For a suspected **Windows endpoint** conflict, open **Settings > System > Sound > More sound settings**, select the intended device on **Playback**, then open **Properties > Advanced**. If it's there, note the original state of **Allow applications to take exclusive control of this device**, clear it temporarily, apply, and restart the affected apps. Set it back if the comparison doesn't help or your workflow needs exclusive access. [Microsoft's exclusive-mode documentation](https://learn.microsoft.com/en-us/windows/win32/coreaudio/exclusive-mode-streams) explains this endpoint control. It won't turn a native ASIO driver into a shared one. Don't change every device or disable unrelated services while you're testing one output. ## When only one file or one channel is silent Open a known-good stereo WAV next to the troublesome file and play both through the same output. If the WAV plays, compare the original's selected time range and channels. A waveform can hold silent sections or a silent channel, and a waveform showing elsewhere in the file doesn't mean the part you've selected has sound in it. Temporarily bypass live playback effects with the [Plug-In Chain controls](https://soundforgepro.com/how-to-use-plug-in-chainer-sound-forge-pro/), then replay without applying processing to the original. If bypass brings the sound back, isolate the effect and its settings instead of reinstalling the audio driver. If earlier processing already wrote silence into the samples, no output change can bring the missing signal back. Go back to an original copy or an available undo state, and save recovery work separately. For one-sided playback, compare both waveform channels, both playback meters and both output assignments. Then check the interface balance and the physical connection at low volume. A [left/right speaker test](https://soundforgepro.com/left-right-speaker-test/) can help you identify the sides, but a browser test uses its own audio route and says nothing definite about your ASIO route. Don't process the source with Channel Converter just to investigate the speakers. An attributed [March 2021 Pro 14 forum report](https://www.magix.info/us/forum/i-can-t-hear-any-audio-from-sound-forge--1271314/) describes moving indicators with silence and a driver change that brought playback back. It's a reason to test the actual driver path. That user's Realtek ASIO choice won't be right for every computer. ## Separate playback gaps from clicks already in the file Clicks don't automatically mean the buffer is too small. Replay the same section with live effects bypassed and compare an untouched source in another player. A click that keeps turning up at the same edit point may already be in the file, and a bigger driver buffer won't repair those samples. Gaps that change with processing load are the ones that point to playback delivery. For ASIO, raise the buffer by one available step in the manufacturer's panel and try again. For the Windows driver path, the Audio Preferences help describes starting **Playback buffering** at **0.25 seconds** and raising it in small steps if playback has gaps. That's the documentation's tuning example. It isn't a guaranteed preset or a sample count to copy into an ASIO panel. Advanced Windows-driver buffer settings also affect how buffering is configured. Don't resample the source just because a rate mismatch seems possible. Check the driver's supported rates and any reported clock error first. Digital connections and external clocking need the manufacturer's setup instructions, since no single clock setting fits every interface. If only one format fails, try conversion on a copy once you've checked the output path. **Interpolate position** and **Position bias** adjust position reporting in Advanced Audio Configuration; they won't fix a general no-sound problem. ## If Windows itself is silent or USB audio has stopped Close Sound Forge and play through the same physical output with Windows or another player. If that fails too, follow [Microsoft's Windows audio troubleshooting steps](https://support.microsoft.com/en-us/windows/hardware/audio/fix-sound-or-audio-problems-in-windows): output selection, connections, mute and device status before any driver changes. Laptop speakers in one app and interface headphones in another aren't the same test. **September 15, 2026 update:** Microsoft's [KB5124008 release note for Windows 11 24H2 and 25H2](https://support.microsoft.com/en-us/servicing/os/windows-11/2026/09/kb5124008-windows-11-24h2-25h2-security-update) lists a September-update issue limited to some USB Audio Class 1.0 devices. Symptoms include no output, unresponsive volume controls and Device Manager Code 10\. The live note says the September 14 out-of-band update **KB5129195** partially resolves the issue for 8-channel or 3D-audio modes; other symptoms remain under investigation. Check the current note and your installed update before attributing a failure to this issue. It is not a diagnosis for all USB or ASIO devices, and uninstalling security updates is not the first step. If a driver change is warranted, use the hardware maker's package for your exact model and Windows version. Record the current driver version and obtain a supported recovery path before replacing a working package. For a failure that began immediately after an update, Microsoft's guide includes **Device Manager > device Properties > Driver > Roll Back Driver** when that option is available. Save your work before restarting, disconnecting or power-cycling an interface. ## A safe final check before escalating 1. Save your work and keep an untouched copy of the source. 2. Lower the listening volume and test the intended physical output with a known-good file. 3. In Sound Forge, select the intended driver, apply it and check both Playback output assignments. 4. On a Windows shared path, check the app's Volume mixer settings; on ASIO, check the interface's software-playback route and physical output. 5. Retest after closing competing audio apps, changing only one setting at a time. 6. If the route still fails, record the Sound Forge version, Windows version, interface and driver version, exact error, file format and results from both playback paths for support. Don't reset all preferences or reinstall just because a meter moves. Those steps can throw away useful setup information without fixing the selected output. Our [Sound Forge troubleshooting hub](https://soundforgepro.com/tag/troubleshooting/) separates playback, recording, installation and plug-in problems so you can carry on with the branch your tests point to. ## Frequently asked questions ### Do moving meters prove that Sound Forge's audio driver works? No. They indicate signal at the displayed playback meter, not successful delivery to the physical speakers. Check the driver, output assignments, interface mixer and monitor volume. ### Do flat meters mean my file is silent? Not necessarily. Check whether playback started, whether the selected section and channels contain audio, whether effects suppress the signal, and whether a device error occurred. Compare a known-good file before changing the original. ### Should I use ASIO or Microsoft Sound Mapper? Use a compatible manufacturer ASIO driver when you need your interface's low-latency path. Microsoft Sound Mapper is a useful Windows-path comparison. Verify the selected outputs in either case rather than treating one driver as a universal cure. ### Why does Windows have sound while Sound Forge does not? The applications may use different devices, output pairs or volume settings. Check Sound Forge's Audio Preferences and the relevant Windows app mixer or ASIO interface mixer. ### Will disabling Windows exclusive mode fix ASIO? It can help test a Windows endpoint conflict, but it does not change a native ASIO driver's sharing design. Close competing audio applications and follow the interface manufacturer's driver-specific guidance. ### Why can I hear my microphone but not the recorded file? Direct monitoring may let you hear the interface input without proving that Sound Forge recorded it. Inspect the recorded waveform and recording-input setup, then test file playback separately. ### Will a larger buffer repair clicks already saved in a file? No. Buffer changes can help playback delivery problems, not clicks already written into the samples. Compare the same section with an untouched source before changing processing or driver settings. ### Should I reinstall Sound Forge first? No. Save the current setup and test the file, driver, output assignments and monitored hardware first. Escalate with the exact error and comparison results if those checks do not identify the problem. Last fact-checked: September 15, 2026\. This guide uses current Boris FX and Microsoft documentation plus an explicitly dated community example. It does not claim a physical Windows, ASIO-interface or acoustic test. ### Sound Forge Not Recording? 7 Input & ASIO Fixes URL: https://soundforgepro.com/sound-forge-pro-not-recording-audio/ Last updated: 2026-09-30T20:14:55.000Z **If Sound Forge will not record audio, check the source, the selected input and the new take separately.** Use the Windows input test for a Windows audio route, or the interface’s physical-input meters for ASIO. Then check the input meters in Sound Forge’s Record Options window. Finally, record into a new, empty data window and inspect the saved take. Hearing a microphone through direct monitoring doesn't prove Sound Forge received it. Save any open work before you start troubleshooting. Keep headphone and speaker levels low, and begin with input monitoring off to avoid feedback. Don't record over a file you need to keep: Sound Forge can [overwrite existing audio](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/record%5Fpunch-in.htm) at the cursor or within a selection, and Normal mode won't protect you from that. This guide diagnoses a missing input, flat meters, a silent take, interruptions and system-audio capture. For first-time setup, use the [Sound Forge recording walkthrough](https://soundforgepro.com/how-to-record-audio-in-sound-forge-pro/). If known-good files also play silently, follow the [playback and ASIO output checks](https://soundforgepro.com/sound-forge-pro-no-sound/). The [Troubleshooting hub](https://soundforgepro.com/tag/troubleshooting/) separates input failures from startup and plug-in problems. ## Start with the symptom, not a reinstall | What you observe | Check next | What it does not prove | | --------------------------------------- | ------------------------------------------------------------------------ | ---------------------------------------------------- | | No input appears in Sound Forge | Connection, driver, selected Audio Device Type and exposed inputs | That Sound Forge itself needs reinstalling | | Device appears; record meters stay flat | Arm state, source, gain, mute and Channel-to-Device mapping | That a larger buffer will restore the signal | | Meters respond; the take is silent | Selected file channels, record status, new waveform and playback route | That you recorded the intended source | | Arm or Record is unavailable | Create a data window; check the selected Mode | That the microphone is broken | | Recording waits or stops early | Automatic method, time selection, Pause and disk-space status | That the driver disconnected | | The take contains clicks or gaps | Source noise, clipping, active buffer, format and sustained workload | That all clicks have the same cause | | You need browser or system audio | A driver-provided loopback input, or separate supported capture software | That a speaker output is an ordinary recording input | Use one known source, such as a spoken count into one microphone. Change one setting at a time and note the result. A short take of about five seconds is just a practical diagnostic suggestion; it says nothing about stability. Once it works, record for as long as the take that failed before. Keep the routes apart. An interface may offer inputs to ASIO that Windows apps never see; [Focusrite documents separate channel exposure for non-ASIO Windows apps](https://support.focusrite.com/hc/en-gb/articles/360010711620-Expose-Hide-Windows-Channels-for-non-ASIO-Windows-apps), for example. So a flat Windows meter doesn't rule out an ASIO input on its own. By the same logic, a moving hardware meter only confirms the signal reached that point in the route. ## Fix 1: confirm the source and microphone access In Windows 11, open **Settings > Privacy & security > Microphone**. Follow Microsoft’s [microphone permission sequence](https://support.microsoft.com/en-us/windows/privacy/turn-on-app-permissions-for-your-microphone-in-windows): turn on **Microphone access**, **Let apps access your microphone** and **Let desktop apps access your microphone** as recording needs. Sound Forge is a desktop application, so there's no Store-style individual switch to look for. These are Windows access controls and don't test every native ASIO driver. For a Windows input, open **Settings > System > Sound**, select the intended device under **Input**, and open its properties. Microsoft’s current [microphone test instructions](https://support.microsoft.com/en-us/windows/hardware/drivers/fix-microphone-problems) use **Start test**, **Stop test** and **Play**. Listen at low volume. For native ASIO, check the interface’s physical-input meter or the corresponding meter in its manufacturer mixer instead. If the source is missing, check power, the connection and the manufacturer’s driver requirements for that exact device. If it's present but quiet, look at mute, gain, the cable and the selected input type, and use microphone, line or instrument settings to suit the connected source and the interface manual. Don't plug and unplug equipment with the monitoring turned up. Switch on phantom power only when the microphone needs it and the connected equipment supports it. Follow the microphone and interface manuals, including their connection order. Shure’s [phantom-power guidance](https://www.shure.com/en-GB/Insights/w/what-is-phantom-power-why-do-i-need-it) explains why phantom power won't fix every flat meter. Once the right input meter responds, leave the source connected. ## Fix 2: select and apply the intended driver Open **Options > Preferences > Audio**. The current [Sound Forge 2026 Audio Preferences](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/audio%5Fpreferences.htm) documents three **Audio Device Type** choices: - **Microsoft Sound Mapper** lets Sound Mapper choose playback and recording devices. - **Windows Classic Wave Driver** lets you select a specific classic Wave device. - **ASIO** uses a specific low-latency ASIO device. Start with the interface manufacturer’s supported ASIO driver when you need that interface’s inputs. A basic USB microphone may work through a Windows path without an ASIO wrapper. Select the intended device type and click **Apply** before inspecting its advanced configuration. Confirm the recording input, not just the similarly named playback output. If the expected ASIO device is missing, save your work and close Sound Forge before you look at the official manufacturer package. Confirm the exact model and its Windows support, keep a known-good installer or rollback route, and follow the vendor’s installation instructions. The [installation and first-run guide](https://soundforgepro.com/how-to-install-sound-forge-pro/) covers the wider setup. Don't install several generic driver wrappers at once, or you won't be able to tell which change helped. ## Fix 3: map the input to the file channel Under **Options > Preferences > Audio**, open the **Record** tab. In the **Channel** and **Device** columns, click a Device entry and choose the intended input. The same official help also documents changing an input by clicking its channel number in **Record Options**. ![Sound Forge Record Options dialog with the channel input menu open and a list of input devices](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/09/sf-record-options-channel-input-menu.webp) Choose the input for the file channel rather than a playback port. Device names in this menu vary by driver. For one microphone, use **File > New** to create an empty mono data window and map its single channel to that microphone’s input. For a stereo source, create two file channels and map left and right on purpose. Recording the same mono source twice won't give you stereo information. The [new-recording documentation](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/record%5Fnew.htm) confirms that the data window caps the number of recorded channels, so a stereo window can't capture six separate inputs. Check which file channels are selected as well as their input assignments. Driver labels won't always match the names printed on the sockets, so compare them with the interface manual. If the interface has direct monitoring, the microphone you hear in your headphones may be skipping Sound Forge entirely. Look for a record meter that responds to your spoken count; any old movement isn't enough, since noise, a loopback return or another input can also move a meter. ## Fix 4: separate Arm, Record and automatic triggers Choose **View > Record Options**. For this test, use the new empty data window, set **Method** to **Manual** and **Mode** to **Normal**. The [Record Options reference](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/recording%5Foptions.htm) says that Normal and Create regions require an open data window for Arm and Record to be available. Creating the empty window explicitly also avoids relying on last-used file settings. Click **Arm** on the main toolbar to prepare the device and check the input meters. Arming is optional preparation and doesn't start a take. Click **Record**, then **Stop** after the short test. Check the record status and elapsed time at the top of Record Options; the status area also shows the attributes and the time left on the drive. If recording seems to wait, check Method: **Automatic: Threshold**, **Automatic: MIDI Timecode** and **Automatic: Time** wait for their respective conditions. If it stops at a repeatable boundary, check for a time selection before blaming the driver. Recording into a selection normally ends at its end; loop recording changes that behavior. Do not diagnose this using an original file you could overwrite. Set **Monitor** to **Off** for the first routing test. The current options are Off, On and Auto, and Auto monitors during pre/post-roll and recording. Clear **Monitor input through Plug-In Chain** while troubleshooting. That chain only affects monitoring; the recorded data stays dry. So a wet headphone sound doesn't prove effects were recorded. Inspect the new waveform at a useful zoom, save the test under a new name and reopen it. If the saved file contains the intended signal but plays silently, investigate the output route. A visible waveform alone could be noise or the wrong input, so compare it with the source and audition through a known-working output. If saving fails, preserve the open take, note the exact error and check the destination’s free space and write access before restarting anything. After capture works, the [voice-over workflow](https://soundforgepro.com/sound-forge-pro-for-voice-over-recording/) covers a repeatable recording setup. ## Fix 5: isolate device ownership and format conflicts Save work in other audio applications before closing them. Close the app that last used the input, reopen Sound Forge and repeat the same test. Don't kill unrelated processes or disable security software. How a native ASIO driver handles sharing depends on the manufacturer, and “works in another app” doesn't show that the other app uses the same driver or input. For a Windows endpoint, its **Properties > Advanced** page may offer **Allow applications to take exclusive control of this device**. Microsoft’s [exclusive-mode documentation](https://learn.microsoft.com/en-us/windows/win32/coreaudio/exclusive-mode-streams) explains that an exclusive stream can block shared streams. Note the original setting before you try it disabled, and set it back if nothing changes. This checkbox won't make every native ASIO driver shareable. If Sound Forge reports an unsupported format or can't open the device, compare the new file’s rate and channel count with the settings the interface supports. With ASIO selected and applied, **Advanced > Configure** opens the manufacturer’s applet, and its controls vary. [Focusrite’s Windows instructions](https://support.focusrite.com/hc/en-gb/articles/208814065-How-to-change-the-sample-rate-and-buffer-size-on-Windows), for instance, put rate and buffer controls in Focusrite Device Settings and warn that other software can change them. Don't copy a rate, channel count or bit depth from another interface as if it applied everywhere. ## Fix 6: distinguish source noise from delivery gaps Clicks already in the source, a loose cable and clipped input aren't automatically buffer failures. If the route carries the intended signal but the recording drops chunks under load, look at buffering and workload next. 1. Save work and clear Plug-In Chain input monitoring. 2. For a Windows path, increase **Record buffering (seconds)** by a small step. Sound Forge documents this as a way to reduce interruptions caused by other tasks. 3. For ASIO, use **Advanced > Configure** and change one available buffer step in the manufacturer applet, if it exposes that control. 4. Pause nonessential sustained work, such as a render or cloud sync, without disabling security protection. 5. Repeat the same source and settings, first briefly and then long enough to cover the usual failure interval. The [Advanced Audio Configuration reference](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/advanced%5Faudio%5Fpreferences.htm) separates the Windows controls from the ASIO manufacturer applet. No sample-buffer value is stable everywhere, and a clean short test says little about long-session reliability. If problems persist, note the driver, rate, channel count, buffer and exact error before comparing the machine with the [Sound Forge system requirements](https://soundforgepro.com/sound-forge-pro-system-requirements/). ## Fix 7: choose a real system-audio capture route Sound Forge’s documented audio-device choices don't include a generic WASAPI-loopback switch. It can record system audio when the selected driver offers a recordable input such as Stereo Mix or an interface loopback return. Microsoft’s [WASAPI loopback documentation](https://learn.microsoft.com/en-us/windows/win32/coreaudio/loopback-recording) describes a separate capture mechanism, and not every application implements it. For a Windows route, open the classic Sound control panel’s **Recording** tab, right-click its empty area and choose **Show Disabled Devices**. If Stereo Mix is there, enable it and choose that input in Sound Forge. This can't conjure up a Stereo Mix device the driver doesn't supply. For an interface, follow the exact model’s loopback routing instructions instead of guessing input numbers. **Prevent feedback before recording loopback.** Keep Sound Forge’s Monitor off, and don't route its monitored capture back into the same loopback mix. Focusrite’s [Scarlett 4th Gen loopback instructions](https://support.focusrite.com/hc/en-gb/articles/13229216604562-Scarlett-4th-Gen-using-Loopback) explicitly warn about this feedback route. Supported models and routing differ, so those instructions won't transfer to every Scarlett or to another manufacturer’s interface. If no suitable input exists, capture with software that explicitly supports Windows loopback, then open its supported lossless output, such as PCM WAV, in Sound Forge. Record only material you have permission to capture. Don't add some random virtual driver just because the speaker output isn't in the recording-input list. ## The safe diagnostic order 1. Save existing work, lower monitoring volume and create a new empty data window for the test. 2. Check Windows microphone permissions and the source on the route you actually use; native ASIO inputs need not appear as Windows endpoints. 3. Select and apply the intended Audio Device Type, then map each file channel to its recording input. 4. Use Manual method and Normal mode with the empty window open; keep Monitor off, click Arm to inspect input, then Record to start the take. 5. Stop, inspect the intended channels, save under a new name and reopen the test; separate capture problems from playback problems. 6. If needed, isolate competing applications, unsupported formats or delivery gaps one variable at a time, retaining original settings for rollback. If the application won't launch, use the [startup-crash diagnostic](https://soundforgepro.com/sound-forge-pro-wont-open-crashes-startup/) instead. For unresolved recording errors, send support the exact Sound Forge version, Windows version, device model, driver, chosen route, format and error text, plus which meter responds. Don't send private recordings unless they're needed and you have permission. ## Frequently Asked Questions ### Why does Sound Forge show no recording device? Check the connection, manufacturer driver and selected Audio Device Type. For a Windows route, verify microphone permissions and the exposed input. Native ASIO channels need not appear as Windows endpoints. Apply the intended device selection, then inspect Record-tab mapping. ### Why are Arm and Record unavailable? In Normal or Create regions mode, the current Record Options help requires an open data window. Create a new empty window with File > New, then use Manual method and Normal mode for the test. Do not use an original recording as the test destination. ### Why do the input meters stay flat? Confirm the device is armed and the source reaches the appropriate Windows or interface input meter. Then check gain, mute and the Channel-to-Device map. Direct monitoring in headphones does not establish that Sound Forge received the signal. ### Why do the meters move but the file is silent? A responding meter does not prove that the intended source and file channels were recorded. Check record status, selected channels and the new waveform. Save and reopen a separately named test, then audition through a working output. Visible data may be noise or the wrong input. ### Should I use ASIO for recording? Use the interface manufacturer’s supported ASIO driver when you need its inputs or low-latency monitoring. A basic USB microphone may work through Microsoft Sound Mapper or Windows Classic Wave Driver. Choose a route that actually exposes the required input. ### Why does recording wait or stop early? An automatic method can wait for a level, timecode or scheduled time. Recording into a time selection can stop at the selection’s end. Check Method, record status and the destination selection before changing drivers; use a new empty window for diagnosis. ### How do I stop gaps and clicks while recording? First distinguish source noise, clipping or cable trouble from delivery gaps. For interruptions under load, change the active Record or manufacturer ASIO buffer one step at a time, clear plug-in input monitoring and retest beyond the usual failure interval. ### Can Sound Forge record browser audio? Yes, if the chosen driver exposes a recordable system-audio input such as Stereo Mix or a supported interface loopback return. Keep monitoring out of that loop to prevent feedback. Without a suitable input, use separate software that supports loopback capture and open the resulting supported audio file in Sound Forge. *Documentation checked September 15, 2026\. This guide is based on current Sound Forge 2026, Microsoft and manufacturer documentation, not a microphone-capture or Windows hardware test performed for this article. Earlier Sound Forge versions may use different recording controls.* ### How to Read Sound Forge Statistics: RMS, Peaks & DC Offset URL: https://soundforgepro.com/how-to-use-statistics-sound-forge-pro/ Last updated: 2026-10-09T20:58:09.000Z **Quick answer:** select the exact audio you intend to judge, choose **Tools → Statistics**, and copy only the fields required by the job. Use the complete program for final LUFS and true-peak verification. Use a short, representative region for noise, DC offset, or fault diagnosis. Process only after you know which measurement failed, then run Statistics again on the same scope. Statistics answers a narrow but important question: what's actually in the region you selected? It can locate sample extremes, report RMS and average value, estimate true peak, and measure program loudness. It won't normalize, limit, repair, or export the audio. *Part of the [Sound Forge mastering guides](https://soundforgepro.com/tag/mastering/). For the processing sequence around these measurements, use the [complete mastering workflow](https://soundforgepro.com/sound-forge-pro-for-mastering/).* ## Run Statistics on the right region The current [Sound Forge 2026 Statistics documentation](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/statistics.htm) says the dialog reports the selected sound-file region. Keep that scope in mind when comparing reports: avoid measuring a short loud passage before processing and the full file afterward. 1. **Open the delivery source.** Open the same sample rate, bit depth, and channel layout that you intend to approve or diagnose. 2. **Choose the analysis region.** Select a noise-only pause for diagnosis, a problem passage for repair, or the complete program for final loudness verification. 3. **Open Tools → Statistics.** Sound Forge builds a read-only report for the selected sound-file region. 4. **Set the display formats.** Choose Ruler Format and Level format only when another time or sample-level representation makes the report easier to read. 5. **Record the fields that answer the job.** Copy integrated loudness, LRA, maximum true peak, RMS, average value, or sample positions according to the actual question and delivery brief. 6. **Copy the baseline.** Use Copy to clipboard for the complete report, or select specific cells and press Ctrl+C. 7. **Process and measure the same region again.** Apply a justified correction, render the result, and compare the same region with the baseline and named delivery specification. ![Three Statistics selection scopes on one stereo file: a noise-only pause, a partial region, and the full program from start to end](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/10/statistics-selection-desktop-v1-v20261006.webp) Choose the region before opening Statistics. A noise-only pause answers a diagnostic question; the complete program is the correct scope for a final loudness check. A quiet diagnostic selection and a complete delivery selection can both be correct, but they answer different questions. Name the region in your notes. If the selection, channel layout, or loudness configuration changes between passes, the before-and-after numbers no longer describe the same test. ## Four useful Statistics checks ### Verify a final program Select the complete program and record integrated loudness, maximum true peak, LRA, and the delivery method named in the brief. Do this on the rendered file rather than only on audio playing through an active effect chain. The render is the asset that will be encoded, uploaded, or handed to the client. ### Measure a noise-only pause Select several pauses that represent the background you actually need to control. Sample peaks help when you're setting a peak-detected gate. An RMS, mixed or sidechain detector can respond differently, so the highest sample won't work as a universal threshold formula. If one pause contains a breath or a passing vehicle, mark it as an exception instead of letting that event define the whole recording's noise floor. ### Investigate DC offset Use Average value as a clue, then inspect the waveform around the zero line. Listen for associated clicks or distortion, not for DC itself. Compare more than one region when the recording changes source or hardware. A confirmed offset can affect headroom and some peak calculations, but an insignificant nonzero average isn't a reason to process an otherwise healthy file. ### Prove what normalization changed Copy a report before normalization, process the intended region, render, and copy the second report. Compare the requested target with the measured output. This catches selections that changed, processors that added gain later in the chain, and files that could not reach a loudness target without exceeding the peak limit. ## Read the report without mixing up the fields The report groups several measurement families in one place, and similar-looking negative numbers don't become equivalent just because they share a dialog. Decide whether you're locating a sample event, estimating average energy, checking peak safety, or measuring program loudness before interpreting a value. | Field group | Use it to answer | Do not infer | | ----------------------------------------- | ----------------------------------------------------------- | ------------------------------------------------------------ | | Minimum / maximum sample and position | Where the stored sample extremes occur | That every extreme is clipping or damage | | RMS level | Average energy in a controlled region or an RMS-based brief | That RMS is interchangeable with LUFS | | Average value | Whether DC offset may need closer inspection | That every nonzero result must be corrected | | Zero crossings | A rough frequency clue for a very simple waveform | Pitch, edit safety, or frequency content of speech and music | | Maximum true peak | Peak safety after waveform reconstruction | Perceived loudness or a universal delivery ceiling | | Integrated / LRA / short-term / momentary | Overall loudness, variation, and loudest short windows | One universal LRA or streaming target | ![Sound Forge Statistics field map for sample extremes, RMS, true peak, and program loudness](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/10/statistics-fields-desktop-v1-v20261006.webp) Read each field for the question it can answer: locate sample extremes, diagnose average level, check peak safety, or compare program loudness with a delivery specification. ### Sample values and positions locate the event Cursor, minimum, and maximum sample values describe stored samples and their locations. Jump to the reported position, zoom in, and listen. A clean transient, a clipped plateau, a click, and an intentional limited peak can all produce an extreme value, so the number is a locator rather than a diagnosis. The same fields help with the [Sound Forge Noise Gate workflow](https://soundforgepro.com/how-to-use-noise-gate-sound-forge-pro/). Measure a representative noise-only pause when you need the highest noise event, but leave out breaths, chair movement, reverb tails and music decay. Those sounds are program material; they aren't a stable noise floor. In the linked gate workflow, check the detector mode and listen to quiet wanted audio before you commit to a threshold. ### RMS and integrated loudness answer different questions Sound Forge defines RMS relative to the RMS value of a maximum-amplitude square wave. Its help also warns that one RMS value becomes less meaningful across a long selection with large volume variation. Use RMS when a client explicitly asks for RMS or when a controlled short region makes it useful. Do not convert a LUFS target into an invented RMS equivalent; the weighting, time behavior, and gating differ. Integrated loudness is the gated program measurement across the selected region. Maximum short-term uses three-second windows; maximum momentary uses 400-millisecond windows. Loudness Range describes variation in LU. [EBU Tech 3343](https://tech.ebu.ch/docs/tech/tech3343v4%5F1.pdf) does not impose one universal maximum LRA, so a broadcaster or delivery contract must supply any path-specific limit. For clips shorter than a minute, LRA is not a reliable acceptance measure: the underlying three-second windows provide too little material. Use the short-form measures requested by the recipient, such as maximum short-term loudness, instead. ### Average value is a DC-offset clue Average value is the sum of the samples divided by their count. A nonzero result can indicate DC offset, but a tiny deviation is not automatic permission to process the file. Inspect the waveform and confirm the fault before using the [DC-offset correction workflow](https://soundforgepro.com/remove-dc-offset-sound-forge/). ### True peak is not the same as sample peak Maximum true peak estimates the continuous waveform at a higher sample rate than the ordinary maximum-sample calculation. Its magnitude can therefore exceed the greatest absolute sample amplitude. For its filtered true-peak field, the help specifies the maximum of the filtered and unfiltered values. It is not simply a lower reading with DC removed; asymmetry and DC offset are reasons to inspect the result carefully. The application help labels these values in dB FS, while EBU and ATSC delivery documents use dBTP. Record the label and value shown in the session, then compare them with the destination specification. Do not silently relabel an application readout or treat −1 dBTP as a universal ceiling. ### Ruler Format and Level format change presentation only Ruler Format controls how cursor and extreme positions are displayed. Level format controls how cursor, minimum, maximum, RMS, and average values are represented as samples, percent, or decibels. These choices change the display, not the audio samples. Pick the representation that matches your notes and keep it consistent when comparing reports. ### Zero crossings are a narrow diagnostic The zero-crossing count is the number of negative-to-positive crossings per second. It can suggest frequency for a simple periodic waveform, but speech, music, and noise contain many simultaneous components. Do not use this field as a [pitch detector](https://soundforgepro.com/pitch-detector/) or as proof that an edit point will be click-free. If the question is which frequencies are present, use the [Sound Forge Spectrum Analysis guide](https://soundforgepro.com/how-to-use-spectral-analysis-tool-sound-forge-pro/) instead. That view provides FFT, sonogram and snapshot comparisons; Statistics gives you a fixed numeric report. ## Apply EBU R128 and ATSC A/85 to the correct delivery case Sound Forge supplies measurements and presets; the standard or contract decides whether the file passes. [EBU R 128 v5](https://tech.ebu.ch/files/live/sites/tech/files/shared/r/r128v5%5F0.pdf) sets program loudness at −23.0 LUFS and states that true peak must not exceed −1 dBTP for linear audio during production. The same recommendation says different distribution systems and data-reduction rates may need a lower permitted maximum. The production guidance gives −2 dBTP examples for MPEG-1 Layer II and Dolby AC-3\. The measurement basis is [ITU-R BS.1770-5](https://www.itu.int/rec/R-REC-BS.1770-5-202311-I), which remains in force. A valid PCM master can still need more headroom before encoding. And the current BS.1770 recommendation doesn't override the measurement method a delivery document specifies, including the distinct ATSC dialogue path below. The July 2026 [ATSC A/85 Annex M quick reference](https://www.atsc.org/wp-content/uploads/2026/07/A85-2026-07-Annex-M.pdf) lists −24 LKFS for content delivered without metadata when the parties haven't agreed on another target, plus a maximum true peak of −2 dBTP. Its streaming guidance recommends picking one consistent target between −23 and −27 LKFS unless the exchange parties agree otherwise. It also separates dialogue-gated and full-program measurement cases, which is why the phrase ‘ATSC is −24’ falls short of a complete delivery instruction. | Reference | Loudness target | Maximum true peak | Scope that matters | | ------------------------- | ------------------------------- | ------------------------------ | ------------------------------------------------------------------------------------------------------------------- | | EBU R 128 v5 | −23.0 LUFS | −1 dBTP | Generic linear audio during production; distribution can require more headroom | | ATSC A/85:2026-07 default | −24 LKFS | −2 dBTP | Delivery without metadata when no other target has been agreed; follow the required dialogue or full-program method | | ATSC streaming guidance | One target from −23 to −27 LKFS | Confirm the delivery agreement | Select one consistent target unless the exchange parties agree otherwise | Selecting the ATSC preset and reading ordinary Integrated LUFS doesn't prove long-form dialogue loudness is compliant. Annex M footnote 31 specifies BS.1770-1 without the relative-level gate added in later versions, combined with dialogue gating over the entire long-form composite mix. That doesn't mean measuring isolated dialogue stems or separate acts. Short-form uses full-program BS.1770-3 or later. The Statistics help doesn't document a dialogue-detection gate, so for that delivery requirement use the recipient’s specified meter and method. This preset can't stand in for them. ## Use a before-and-after check that survives delivery Save a baseline report before changing level. Record the filename, selected region, channel layout, loudness mode, and the fields required by the brief. Apply the smallest processing change that solves the failed measurement, render a new file, and measure the same scope again. Simple gain arithmetic is a useful feasibility check. If a file measures −18 LUFS and about −2 dB true peak, reaching −14 LUFS with gain alone takes roughly +4 dB. That predicts a true peak near +2 dB before codec or sample-rate effects, so the file doesn't have the headroom for a gain-only move. Change the loudness goal only if the brief allows it; otherwise consider controlled dynamics processing or a mix revision. Keep in mind this is a gain-only estimate. Gating, processing and export can all move the final loudness result. For the controls that actually change level, follow the [Peak, RMS, and Loudness Normalize guide](https://soundforgepro.com/how-to-normalize-audio-in-sound-forge-pro/). A requested gain, limiter ceiling or preset tells the processor what to do; it doesn't prove what the render came out as. ## Statistics, Loudness Meters, and Normalize have different jobs ![Statistics, Loudness Meters, processing, and final verification shown as a four-stage Sound Forge workflow](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/08/statistics-workflow-desktop-v1.webp) Use Statistics for a fixed report, Loudness Meters to watch change over time, processing only when the brief requires it, and Statistics again to verify the rendered file. **Statistics** creates a fixed, copyable report for a selected region. **Loudness Meters** show momentary, short-term, integrated, LRA, and true-peak behavior during playback. The [current Loudness Meters help](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/loudness%20meter%20v2.htm) says those values reset when playback restarts. **Normalize** is a processing command that scans and changes level in its selected mode. Use Statistics to document a before or final state, and use the meters to find where behavior changes over time. Neither tool is inherently more accurate merely because one is offline. The algorithm, configuration, measured region, channel handling, and delivery method still control the meaning of the result. The [Sound Forge Loudness Meters guide](https://soundforgepro.com/sound-forge-loudness-meters/) covers the playback view in detail. ## When two loudness readings disagree Check the test itself before blaming the meter. In Options → Preferences → Status, check the loudness settings; the current help uses both “Loudness Configuration” and “Loudness Modus” for the EBU/ATSC choice. A partial selection won't match the complete program, and a meter reset halfway through playback won't match a full-region Statistics report. Six-channel weighting, EBU versus ATSC mode, absolute LUFS versus relative LU display, and dialogue-gated versus full-program methods can all shift the result too. Next, confirm that both tools measured the same file. A live chain can differ from the rendered output, and lossy encoding can change peak behavior after the approved WAV leaves Sound Forge. Keep the baseline, the rendered report, and any post-encode QC result as separate records. If the numbers still disagree after scope and configuration match, document the exact versions and settings before deciding which measurement the receiving specification accepts. ## Check the six-channel preference before comparing results For six-channel files, choose **Options → Preferences → Status** and check **Enable surround processing for files with 6 channels**. With it enabled, the documented measurement weighting adds about 1.5 dB to the left and right surround contributions; with it disabled, the help says all channels contribute equally. It's a measurement preference and doesn't raise the level of any samples in the file. Two reports can differ when this preference isn't matched. Six channels alone don't prove a correct 5.1 layout, so check channel order and LFE treatment with a known channel fixture and a conforming reference before approving multichannel delivery. ## Final Statistics checklist - Measure the exact program or diagnostic region required by the job. - Record the Sound Forge version, loudness mode, channel layout, and six-channel preference. - Compare integrated loudness with the named delivery target. A generic streaming number won't do here. - Compare maximum true peak with the production, codec, or distribution limit that actually applies. - Treat LRA as a descriptor unless the destination publishes a limit. - Use RMS only for an RMS-based brief or a controlled diagnostic region. - Inspect reported sample positions before declaring clipping, a click, or DC offset. - Keep the final report with the approved render. ## Frequently Asked Questions ### Where is Statistics in Sound Forge Pro 2026? Select the intended audio and choose Tools → Statistics. The report covers the selected sound-file region and includes sample values and positions, RMS, average value, zero crossings, maximum true peak, integrated loudness, LRA, and maximum short-term and momentary loudness. ### Does Statistics change or normalize the audio? No. Statistics is a read-only analysis report. Use Normalize, Volume, a limiter, or another justified processor to change the audio, render the result, and then run Statistics again on the same region. ### Does Statistics analyze a selection or the whole file? It analyzes the selected sound-file region. Use a noise-only or problem region for diagnosis and the complete program for final delivery verification. Keep the scope identical when comparing before and after reports. ### What is the difference between sample peak and true peak? Sample peak is the greatest absolute sample amplitude, whether the sample is positive or negative. True peak estimates the reconstructed waveform between samples, so its magnitude can exceed the sample peak. That matters for downstream conversion and encoding. ### Is −1 dBTP the official EBU R128 maximum? Yes for generic linear audio during production under EBU R 128\. Distribution systems and data-reduced codecs can require a lower maximum; EBU production guidance gives −2 dBTP examples for MPEG-1 Layer II and Dolby AC-3. ### What is the difference between Statistics, Loudness Meters, and Normalize? Statistics creates a fixed report for a region. Loudness Meters show changing measurements during playback. Normalize scans and changes level. Measure first, process only when required, and verify the rendered result. ### What are the current ATSC A/85 loudness and true-peak values? ATSC A/85:2026-07 lists −24 LKFS for delivery without metadata when no other target is agreed and −2 dBTP maximum true peak. Its streaming guidance recommends one selected target between −23 and −27 LKFS unless the parties agree otherwise. Long-form dialogue and short-form full-program measurement use different methods. Statistics’ ATSC preset alone does not establish the required dialogue-gated result; follow the recipient’s meter and delivery specification. If a report points to a level problem, move to the [mastering hub](https://soundforgepro.com/tag/mastering/) for the matching correction. If it points to noise, clicks, clipping, or DC offset, use the [audio restoration hub](https://soundforgepro.com/audio-restoration/) before changing loudness. Documentation checked: September 7, 2026\. Sound Forge Pro 2026; EBU R 128 v5 and ATSC A/85:2026-07\. Documented controls are not a substitute for testing the installed meter against the required delivery method. ### Acid Pro vs Sound Forge: What's the Difference? URL: https://soundforgepro.com/acid-pro-vs-sound-forge/ Last updated: 2026-10-09T12:43:29.000Z **Acid Pro is for arranging and mixing music. Sound Forge is for editing the audio file.** Choose Acid Pro when you need loops, MIDI, virtual instruments, tracks, buses, automation, and a multitrack mix. Choose Sound Forge when the recording or mix already exists and needs precise waveform editing, restoration, mastering, analysis, conversion, or batch processing. If the project is video-first rather than music-first, use the [Sound Forge vs Vegas Pro](https://soundforgepro.com/sound-forge-vs-vegas-pro/) comparison instead. Both can record, edit, and export audio. The practical question is whether you still need to change individual tracks or whether you are working on a finished recording. ## Acid Pro vs Sound Forge: feature comparison | Capability | Acid Pro 2026 | Sound Forge 2026 | | ---------------------- | --------------------------------------------------------------- | ------------------------------------------------------------------------------ | | Main job | Create, arrange, record, and mix music | Edit, repair, master, and convert audio files | | Project model | Multitrack DAW timeline | Specialist file editor; not a DAW-style song session | | Loops | Core Acidized-loop workflow with project key and tempo matching | Edits loop audio and ACID metadata; does not arrange a loop-based song project | | MIDI and VSTi | MIDI sequencing and virtual-instrument production | No DAW-style MIDI sequencing or instrument arrangement | | Recording and mixing | Tracks, buses, routing, automation, plug-ins, and a master mix | Records and edits mono, stereo, or multichannel files up to 32 channels | | Detailed waveform work | Clip/event editing inside the production | Sample-level selections and dedicated file tools | | Restoration | Effects and third-party plug-ins in project context | Click, clipping, and broadband-noise tools for the file | | Mastering and metering | Master-bus processing and current loudness meters | File-level processing, peak/loudness metering, and delivery preparation | | Batch processing | Not the central workflow | Dedicated batch workflow for groups of files | | Current minimum OS | Windows 11 | Windows 11 | ## The simplest way to choose Ask what must remain editable tomorrow. - If the answer is tempo, key, loops, MIDI notes, instruments, track balance, routing, effects, or arrangement, use Acid Pro. - If the answer is a selection inside one recording, an isolated defect, a final stereo file, a delivery format, or the same process across many files, use Sound Forge. Sound Forge can process a rendered song, but it cannot restore the original tracks, instruments, and automation from that file. Acid Pro edits audio too. If the file is already in a project, a small repair there may be sufficient; repeated standalone repair and conversion jobs are a better reason to add a dedicated editor. Changing a chorus length, replacing a synth, moving a kick, or lowering a reverb return is straightforward while the Acid project is intact. Once a stereo render reaches Sound Forge, those parts are combined. A file editor can shape the mix, but it can't independently turn down one instrument without a stem or another separation step. For a different job, imagine a tape transfer with one click at 02:14.320: a Sound Forge selection can isolate the defect without asking you to create tracks, set a project tempo, or manage an arrangement. If a loop itself needs a new length or pitch before it enters Acid, the [Sound Forge time-and-pitch workflow](https://soundforgepro.com/time-stretch-pitch-shift-sound-forge/) can prepare the asset; Acid then owns its musical placement. ## What Acid Pro is for The [current Acid Pro product page](https://www.soundforge.com/acid-pro/) describes a full DAW built around loop-based composition, multitrack audio, and MIDI. Correctly tagged Acidized loops can follow project tempo and, when enabled, project key. Live preview lets you audition them against the arrangement before placing them. The timeline also supports recorded audio, MIDI sequencing, VST instruments, routing, submixes, effects, and automation. That makes Acid Pro the better first choice for beats, electronic music, songwriting demos, cues, and any production whose structure is still moving. Its current video workflow includes preview and hit-point tools for tempo maps, so it can also build music around picture. The current package includes nearly 3 GB of royalty-free loop content. Check the included library before buying for particular sounds; a legacy Acid Pro 11 installation will not necessarily have the same content. Use Acid Pro when you need to: - build a song or cue from loops and one-shots; - record and edit several tracks in one production; - sequence MIDI and use VST instruments; - arrange sections, draw automation, route buses, and mix; - score to picture with video preview and tempo/hit-point control; - keep every musical decision editable until the final render. ## What Sound Forge is for Sound Forge is useful when your main asset is a recording rather than a song arrangement. Open a mix, dialogue take, field recording, digitized tape, podcast episode, exported stem, or sample and work directly on that media. Boris FX's [current Sound Forge feature page](https://www.soundforge.com/sound-forge/pricing/) lists sample-level waveform editing, precise peak and loudness metering, VST2/VST3/ARA support, click and clipping repair, broadband noise reduction, automatic record start, multichannel support up to 32 channels, and batch processing. The official FAQ explicitly says Sound Forge is not a DAW. That focus is useful when the job doesn't need instrument tracks, MIDI data, buses, or a song arrangement. Event-based non-destructive editing is available, but the application's main value remains precise work on files. Use Sound Forge when you need to: - reduce clicks, crackle, clipping distortion, or steady noise when the recording contains enough usable information; - trim and assemble a completed recording at waveform level; - inspect the rendered file rather than only the DAW master bus; - prepare alternate sample rates, bit depths, or distribution formats; - run one repeatable process across a folder; - record or inspect a mono, stereo, or multichannel file without creating a DAW project. The [current Sound Forge review](https://soundforgepro.com/sound-forge-pro-review-2026/) covers the whole application. For a defined repair, follow the [clipped-audio workflow](https://soundforgepro.com/fix-clipped-audio-sound-forge/) or the [click-and-pop procedure](https://soundforgepro.com/how-to-remove-clicks-pops-sound-forge-pro/). ## Where the applications overlap Acid Pro may be enough for a self-produced release that needs no detailed restoration or batch work, and an editor who never composes or mixes multitrack music may get by on Sound Forge alone. Buy the second tool only when the handoff becomes a real, repeated stage. Metering is another overlap that needs context. Acid Pro's current loudness meters let you watch the project while changing tracks and buses. Sound Forge lets you inspect the rendered file that will actually leave the project. Neither view excuses checking the written delivery target, and a failed stereo master should return to Acid whenever the root cause is inside the mix. ## Preparing a loop for Acid Pro Sound Forge can also prepare the information Acid uses to play a sample. Open [View → Metadata → ACID Properties](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/metadata-acid%5Finformation.htm). For a repeating clip, choose Loop and verify its beat count and root note. An incorrect beat count changes playback speed; test the saved sample in Acid at the intended tempo before adding it to a library. A drum loop may need Don’t transpose instead of a pitched root note. One-Shot clips do not automatically follow the project’s tempo or key. For a longer Beatmapped file, the available properties include original tempo and downbeat offset. These tags describe playback behavior; they do not repair a click or change the waveform by themselves. ## How Acid Pro and Sound Forge fit in one workflow ![ACID Pro arrangement rendered to a lossless WAV for Sound Forge, with mix problems sent back to the original project](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/09/acid-lossless-handoff-20260912.webp) Render a working copy for file editing; return to the ACID project for mix changes. [Open the full-size workflow](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/09/acid-lossless-handoff-20260912.webp). 1. **Create and arrange in Acid Pro.** Keep loops, recorded tracks, MIDI, instruments, tempo, and section changes inside the DAW. 2. **Mix in Acid Pro.** Set track balance, automation, routing, effects, and the master chain in full project context. 3. **Render a compatible lossless working file.** Use a format both applications and the next delivery stage support. WAV is the usual Windows interchange choice, but compatibility is the rule. 4. **Inspect the render in Sound Forge.** Check boundaries, channels, sample rate, peaks, and the exact defects that justify a file-level pass. 5. **Repair or master deliberately.** If the problem is track balance, automation, or arrangement, return to Acid Pro instead of hiding the mix decision in a stereo file. 6. **Create delivery copies last.** Keep the approved high-quality master and derive distribution versions from it. This is a file handoff, not a shared project. Sound Forge can't open an Acid project and continue editing its MIDI, loops, tracks, buses, or automation. Keep the Acid project and its media so the mix remains recoverable. Before treating the render as a master, compare it with the Acid playback at matched monitoring level and listen across the beginning, transitions, and final decay. A missing tail, wrong solo/mute state, clipped bus, or incorrect channel layout belongs back in Acid. Once the render is approved, the [file-level mastering workflow](https://soundforgepro.com/sound-forge-pro-for-mastering/) covers controlled processing and delivery checks in Sound Forge. ## Choose the handoff format by compatibility “Export 24-bit or 32-bit float WAV” is useful only when both applications and the downstream stage support that exact file. A safer rule is: - choose a lossless format supported by Acid Pro, Sound Forge, and the recipient; - preserve the project sample rate unless the delivery specification requires conversion; - use a working bit depth that the full chain supports; - keep the undithered working master when more processing may follow; - plan [dither at the final integer quantization](https://www.fabfilter.com/help/pro-l/using/dithering), including after floating-point processing; - verify channel layout and file duration after every render. The official [Acid Pro format table](https://www.soundforge.com/acid-pro/system-requirements/) lists WAV, W64, FLAC, AIFF, MP3, OGG, and WMA among current audio formats. The [Sound Forge format table](https://www.soundforge.com/sound-forge/system-requirements/) is broader. Avoid another MP3 or OGG encode between production and mastering. Even when the only source is lossy, decode it and use a compatible lossless working file for the handoff. This prevents another lossy generation; it does not restore information already discarded. ## Current Boris FX versions, licensing, and legacy downloads [Boris FX announced its acquisition](https://blog.borisfx.com/press/boris-fx-acquires-vegas-pro-sound-forge-and-acid-pro) of Acid Pro and Sound Forge from MAGIX on March 30, 2026\. Current product pages use Acid Pro 2026 and Sound Forge 2026 branding, and current trials and purchases are presented through Boris FX. The acquisition announcement listed March 2026 US launch prices for Acid Pro at $12.95 monthly, $69.95 annually, $89.95 for Upgrade & Support, and $149.95 perpetual. It listed Sound Forge at $24.95 monthly, $149.95 annually, $189.95 for Upgrade & Support, and $299.95 perpetual. These are dated launch amounts; the checkout price can differ. Use the live product/store page for region, tax, promotion, and current eligibility. Don't assume a legacy serial has moved into a Boris FX account. Boris FX's [legacy-download guidance updated March 29, 2026](https://support.borisfx.com/hc/en-us/articles/44650730285709-Where-can-I-access-my-existing-product-downloads) says pre-2026 versions of Acid Pro and Sound Forge remain hosted by MAGIX. The [July 20 upgrade guidance](https://support.borisfx.com/hc/en-us/articles/47516909735949-I-m-a-previous-Acid-user-am-I-eligible-for-upgrade-pricing) says an Acid Pro 11 purchase from MAGIX on or after January 1, 2026 qualifies for a complimentary upgrade with proof of purchase. Earlier Acid Pro 11 buyers have a paid upgrade route using the matching MAGIX purchase email and their Acid Pro 11 serial. Existing subscription users should ask support about their account; the page’s relative migration timeline is not a confirmed completion date. The products share an owner, not a project format. The [Sound Forge ownership history](https://soundforgepro.com/sound-forge-history/) explains the legacy names you may see on older installers. ## When to Use Acid Pro, When to Use Sound Forge | Your task | Use | Why | | -------------------------------- | ----------------- | ----------------------------------------------------------------- | | Make a beat from loops | Acid Pro | Acidized-loop and arrangement workflow | | Record and mix a song | Acid Pro | Multitrack recording, MIDI, instruments, buses, and automation | | Compose to video | Acid Pro | Video preview, tempo mapping, and hit-point tools | | Remove clicks from a transfer | Sound Forge | Focused restoration and precise selection | | Repair a clipped word | Sound Forge | File-level repair routes; recovery is not guaranteed | | Inspect or master one stereo mix | Sound Forge | Focused file metering, processing, and delivery | | Convert a folder of files | Sound Forge | Batch processing | | Create and finish a release | Both, when needed | Acid Pro owns production; Sound Forge handles the approved render | ## Do you need both? Most buyers should start with one. Buy Acid Pro first if the missing capability is composition, multitrack recording, MIDI, instruments, arrangement, or mixing. Buy Sound Forge first if work arrives as recorded or mixed audio and the missing capability is precise repair, mastering, analysis, conversion, or batch delivery. If you only convert a couple of files occasionally, try the tools you already own first. A recurring folder workflow is a stronger reason to add Sound Forge. Sound Forge's [Batch Converter guide](https://soundforgepro.com/how-to-batch-process-files-sound-forge-pro/) shows what the second application adds when the same chain, naming rule, and output format must be applied repeatedly. Both make sense when the same person owns production and final-file quality. They can also pay off when Acid Pro's loop workflow is valuable but a library of samples, field recordings, or transfers needs preparation outside the DAW. They don't make sense merely because the names share a product family. If neither workflow matches your work, use the [Sound Forge software comparisons](https://soundforgepro.com/tag/comparisons/) to compare other editors and DAWs before buying. ## Frequently Asked Questions ### Is Acid Pro a DAW? Yes. Acid Pro 2026 is a Windows 11 DAW for loop-based composition, multitrack recording, MIDI sequencing, VST instruments, arrangement, mixing, and export. ### Can Sound Forge replace Acid Pro? No for [music production](https://soundforgepro.com/sound-forge-pro-for-music-production/). Sound Forge does not provide Acid Pro's DAW-style loop arrangement, MIDI sequencing, virtual-instrument production, tracks, buses, and automation. It can replace Acid only for a task that already centers on one audio file. ### Can Acid Pro replace Sound Forge? Sometimes for simple editing and self-produced mixes. Acid Pro can edit audio, use effects, and meter a master bus, but it does not provide Sound Forge's focused sample-level repair and batch-processing workflow. ### Are Acid Pro and Sound Forge owned by Boris FX? Yes. Boris FX announced its acquisition of Acid Pro, Sound Forge, and Vegas Pro from MAGIX on March 30, 2026\. Current 2026 product pages, trials, and purchases are presented through Boris FX. ### Can I open an Acid project in Sound Forge? Not as an editable multitrack Acid project. Render or export a supported lossless audio file from Acid Pro, open that file in Sound Forge, and keep the original Acid project for later changes to loops, MIDI, tracks, routing, or effects. ### Which should I buy first: Acid Pro or Sound Forge? Buy Acid Pro first when the missing stage is composition, MIDI, recording, arrangement, or mixing. Buy Sound Forge first when existing audio needs precise editing, restoration, mastering, analysis, format conversion, or batch processing. *Fact-checked September 12, 2026 against current product and system pages, the ACID Properties manual, March 2026 launch pricing, and July 2026 upgrade guidance. This comparison is documentation-based; it does not report a hands-on test of either current application.* ### Sound Forge in Samplitude Suite 2026: Setup & Workflow URL: https://soundforgepro.com/sound-forge-in-samplitude-suite/ Last updated: 2026-10-09T22:04:32.000Z **Sound Forge 2026 comes with Samplitude Suite 2026, not the standard edition.** It remains a separate Windows application. The current Samplitude 2026 product page says to right-click the clip and choose **Edit with external software > Edit in Sound Forge**; Samplitude then uses the saved audio in the VIP project. If that entry is missing, configure it under **File > Program Preferences > External Tools**. Before the first handoff, enable **Create copy**. Boris FX says this applies the destructive external edit to copied audio so the object edit can be undone. Also keep an untouched backup of irreplaceable recordings. Samplitude's undo path is useful, but it's no replacement for source-media backup. The setup has one important exception: **Convert to Wave before transfer**. It helps when an external editor can't open MP3, FLAC or video-derived media, but Boris FX warns that the converted result won't come back into the virtual project through the normal path. That branch needs a throwaway test and a planned manual import or relink. ## Sound Forge in Samplitude Suite 2026: quick facts | Question | Current answer | | ----------------------------------- | ---------------------------------------------------------------------------------------------- | | Which edition includes Sound Forge? | Samplitude Suite 2026; not standard Samplitude | | Is it embedded in the DAW? | No. Sound Forge opens as a separate application | | How does the handoff work? | A configurable External Tools command passes an audio object to Sound Forge | | Safest normal setting | Enable Create copy before the transfer | | Compressed or video-derived media | Convert to Wave can help, but the result needs a different return plan | | Best Sound Forge jobs | Defined file repair, repeatable waveform work, batch processing, and delivery-file inspection | | Best Samplitude jobs | Arrangement, object processing, comping, routing, automation, mixing, and multitrack mastering | | Operating system | Windows applications; check both products’ requirements, not just the DAW’s | ![Samplitude external-edit paths: save a working copy back to the VIP, or manually import and align a converted WAV](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/09/samplitude-file-return-routes-20260912.webp) Verify the direct return path; plan a manual import when converting to Wave. [Open the full-size workflow](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/09/samplitude-file-return-routes-20260912.webp). ## What Samplitude Suite 2026 includes The [current Samplitude product overview](https://www.samplitude.com/products/samplitude/) places Sound Forge 2026 in the Suite-only feature set. The dated [April 2026 launch announcement](https://blog.borisfx.com/press/reimagined-audio-engine-in-boris-fx-samplitude-delivers-greater-processing-power) describes it as the standalone specialist for individual audio files, with precision waveform editing, repeatable functions, trigger-based recording, and batch processing. Sound Forge is one part of the edition difference. The current Suite overview also lists native Dolby Atmos and ADM support, track-level spectral editing, FX Routing Matrix, Soundly integration, and additional first- and third-party tools. Those extras matter when comparing editions; if your work rarely leaves the Samplitude timeline, the Sound Forge handoff alone shouldn't decide the purchase. | April 2026 US launch option | Samplitude | Samplitude Suite | Suite premium | | --------------------------- | ---------- | ---------------- | --------------------- | | Annual subscription | $145 | $175 | $30 per year | | Perpetual license | $395 | $495 | $100 | | Upgrade & Support | From $185 | From $275 | Eligibility-dependent | The launch table listed no monthly Suite subscription. These are dated US launch amounts; they don't promise anything about today's checkout. Region, tax, promotion, currency, and upgrade eligibility can change the total, so verify the live store before paying. The 2026 overview and launch announcement name Sound Forge 2026 as the included edition. Don't go by the older Suite 2025/Pro 17 FAQ wording when identifying a current purchase. Samplitude lists Windows 10/11 64-bit, while the current Sound Forge requirements specify Windows 11\. For the complete bundle workflow, use a system that meets both applications’ published requirements. ## Check Suite access and install the included editor The [current Samplitude product page](https://borisfx.com/products/samplitude/) confirms that Suite includes Sound Forge 2026\. It also documents where to manage additional first-party tools: find Samplitude in Boris FX Hub, click the arrow on the right, and open **Manage Extras**. Bundle inclusion and the activation procedure are different questions. 1. Sign in to Hub with the Boris FX account that owns the Samplitude Suite license. 2. Confirm that the entitlement says **Samplitude Suite**, not standard Samplitude. 3. Install Samplitude and open **Manage Extras** for bundled items. 4. Check the extras and purchase instructions that came with your Suite entitlement for Sound Forge, and follow the installation and activation instructions for that exact included version. If the product is missing or asks for credentials nobody gave you, stop and ask Boris FX support to confirm the entitlement. The [bundled-software support article](https://support.borisfx.com/hc/en-us/articles/38965048376589-Installation-and-Activation-Third-Party-Software) describes a supplied serial number and MAGIX registration under **MAGIX SOUND FORGE Pro**. Its separate statement about activating inside the host without a separate serial refers to **CrumplePop**, not Sound Forge. Neither passage tells you how every current Sound Forge 2026 Suite entitlement activates, so don't assume activation happens automatically through Samplitude, or that every included copy needs its own key. Confirm your actual license and its instructions before buying another copy. If Suite is there but Sound Forge isn't, capture the account license record, the Hub version and the product screen before contacting Boris FX support. Don't reach for an old MAGIX installer or an unrelated serial, or an entitlement issue can turn into a second activation problem. If Sound Forge installs but won't launch, run the [startup-crash checks](https://soundforgepro.com/sound-forge-pro-wont-open-crashes-startup/) before touching Samplitude's preferences. ## Configure Sound Forge as Samplitude's external editor The word “integrated” on the product page means a configured application handoff. There's no ARA plug-in here and no mini editor embedded in the arranger. The official [External Tools documentation](https://cdn.borisfx.com/borisfx/Documentation/samplitude-suite-2026/en/Content/Externe%20Tools.htm) gives these controls: 1. If Samplitude was open during installation and doesn't detect Sound Forge, save your work and try restarting Samplitude. It's a troubleshooting suggestion; most installations won't need it. 2. Open **File > Program Preferences > External Tools**. 3. Choose **Add**. If Sound Forge is detected, the adjacent menu can create an entry with suitable executable and argument values. 4. Use a clear title such as **Edit in Sound Forge**. 5. Enable **Create copy**. 6. Leave **Release file temporarily** enabled when Sound Forge must write to the transferred file. 7. Confirm the dialog. In the current 2026 interface, right-click the audio object and look under **Edit with external software** for **Edit in Sound Forge**. These controls are documented in the 2026 manual linked from Boris FX’s documentation index. Use the copy test below to confirm the return path in your installed build. ## Run the normal Samplitude-to-Sound-Forge round trip Use this path for WAV or another source format Sound Forge opens directly. Test it once in a disposable project before touching the only copy of a paid session. 1. **Save the VIP and protect the source.** Save the Samplitude project and keep an untouched backup of irreplaceable source media before the external edit. 2. **Select the exact audio object.** Confirm the object, its boundaries, and whether other objects refer to the same source recording. 3. **Send a copy to Sound Forge.** Use the configured external-tool command with Create copy enabled for a file-level edit that must remain reversible in Samplitude. 4. **Repair the identified file-level problem.** Work on the intended range, preserve duration unless the project allows a timing change, and audition the edit boundaries. 5. **Save the transferred file in place.** Use Save on the file Samplitude supplied. Treat Save As as a separate-asset workflow that may require manual import or relinking. 6. **Return to Samplitude and verify the object.** Check playback, timing, fades, channel layout, sample rate, and every object that could share the original recording. 7. **Recheck the mix or delivery file.** Judge the edited audio in the full project context and create a new render from Samplitude if the mix itself changes. The official [Editing Objects Externally page](https://cdn.borisfx.com/borisfx/Documentation/samplitude-suite-2026/en/Content/Objekt%20extern%20bearbeiten.htm) says the edited audio is then available in the VIP. It doesn't promise identical return behavior for every source format, custom command argument, or renamed file, which is why the direct-format and converted-format paths must remain separate. ## Handle MP3, FLAC, and video-derived objects without losing the return path **Convert to Wave before transfer** exists because some external editors can't open MP3, FLAC or audio inside video media. Boris FX says Samplitude creates a Wave file under a different name before opening the editor, and the same help page warns that this stops the file from transferring back into the virtual project the normal way. The [current Sound Forge format list](https://www.soundforge.com/sound-forge/system-requirements/) includes MP3 and FLAC import. The conversion option is meant for a real compatibility problem; it doesn't mean every file with those extensions needs converting. Try direct opening to find out whether the format works. For repeated processing of a lossy source, a WAV working copy is still the better choice, so plan its manual return to the VIP instead of relying on the direct-save route. Before processing a real project: 1. Duplicate a short object in a disposable VIP. 2. Enable **Create copy** and **Convert to Wave before transfer**. 3. Make a harmless edit and save the Wave file. 4. Return to Samplitude and observe whether the object updates in your exact build and preset. 5. If it doesn't, import the saved Wave, place it at the original start, check timing and channel layout, and keep the source object muted or on a backup track. Don't mistake an MP3-to-WAV conversion for quality restoration. The decoded Wave avoids another compressed working stage, but it can't recreate information already removed by the source codec. Direct opening is a compatibility check, not a recommendation for repeated lossy encoding. ## What destructive editing means in this workflow Samplitude's object trims, fades, volume, pitch and object effects can stay as non-destructive instructions, while Sound Forge usually works on the underlying file. The [current Sound Forge feature page](https://www.soundforge.com/sound-forge/pricing/) also documents an event-based non-destructive mode, but that doesn't remove the risk at the handoff: the file Samplitude passes out can still be saved with changed audio data. This matters when several objects use one long recording. A file-level repair can affect every reference to that portion of the source. Use four layers of protection: - enable **Create copy** in the external-tool preset; - save the VIP before transfer; - keep an untouched recording or project backup outside the active media folder; - check every object that may share the source. **Save As is a path-handoff risk, not a documented universal failure.** The public manual doesn't state that every Save As operation breaks every setup. The safer editorial rule is to use Save on the file Samplitude supplied when you expect an automatic return. If you intentionally create a new name or location, treat it as a separate asset and be ready to import or relink it explicitly. ## Stay in Samplitude or open Sound Forge? | Task | Better first choice | Reason | | ---------------------------------------- | ------------------- | ------------------------------------------------------------------------ | | Object boundaries, fades, crossfades | Samplitude | The relationship between timeline objects remains visible and adjustable | | Object EQ, compression, and effects | Samplitude | Processing stays editable in project context | | Comping, routing, automation, mixing | Samplitude | These decisions depend on the multitrack session | | One defined defect in an underlying file | Sound Forge | A dedicated waveform view isolates the file-level problem | | One repeatable process across a folder | Sound Forge | Batch processing works outside a DAW project | | Standalone voice-over or sample asset | Sound Forge | The deliverable is the file itself | | Master while the mix is changing | Samplitude | Revisions stay connected to the source session | | Inspect an approved stereo render | Sound Forge | The exact exported file becomes the subject | Samplitude already offers deep object editing and direct wave editing. Opening a second application for every clip adds switching without improving a timeline decision. Use Sound Forge when the work has a clear file-level boundary. ## Three workflows where the bundle earns its place ### Dialogue or voice-over repair Keep placement, fades, automation, and the surrounding mix in Samplitude. Send a copy when one recording needs precise click repair, a tightly selected replacement, or a standalone cleaned asset. Return to the full mix and listen across the boundaries. An isolated file can sound clean while its room tone no longer matches the next object. ### Sample-library preparation Use Sound Forge when a folder needs consistent trimming, naming, format conversion, or a repeatable process before the assets enter Samplitude. The [Batch Converter workflow](https://soundforgepro.com/how-to-batch-process-files-sound-forge-pro/) covers the file queue, chain, output, and verification. Use Samplitude later for arrangement and mix decisions. ### Printed mix verification Once the mix is approved, export a high-resolution stereo file from Samplitude and inspect that exact candidate in Sound Forge. Check boundaries, channel layout, sample rate, peaks and the delivery formats. If a balance, automation or bus decision changes, go back to Samplitude and print a new source instead of piling file corrections onto an outdated mix. The [Sound Forge mastering guide](https://soundforgepro.com/sound-forge-pro-for-mastering/) keeps file finalization apart from the mix session. ## Which application keeps the multitrack project? Samplitude keeps the VIP project. Sound Forge can record and edit multichannel files with up to 32 channels, but several channels in one file don't add up to a DAW arrangement with independent tracks, instruments, buses and automation. Its FAQ says outright that the application isn't meant to work as a DAW. For a Suite owner, the division is simple: the VIP project owns the timeline and Sound Forge handles selected file work. For other project-to-file handoffs, use the [Sound Forge workflow guides](https://soundforgepro.com/tag/workflows/). If you are comparing standalone tools instead of the bundle, the [Sound Forge versus REAPER comparison](https://soundforgepro.com/sound-forge-pro-vs-reaper/) explains the waveform-editor and DAW boundary. ## If Edit in Sound Forge is missing 1. Confirm that Sound Forge is installed, then set up the external-tool entry below to check the handoff. If Sound Forge shows an activation prompt, resolve it with the instructions for your exact entitlement, since adding a menu entry doesn't give you license access. 2. If you expect the bundled license, confirm that your entitlement is Samplitude **Suite**. Suite inclusion and the existence of a configured external-tool command are separate checks. 3. Open **File > Program Preferences > External Tools**; the command may not exist until an entry is created. 4. Use the preset beside **Add** if Sound Forge is detected. Otherwise select the executable and verify the arguments. 5. Right-click the audio object and check **Edit with external software** for **Edit in Sound Forge**. 6. If Hub never installed Sound Forge, return to **Manage Extras** and verify the account entitlement. Don't confuse Samplitude's own **Wave Editing** command with the configured External Tools entry. If Sound Forge opens but can't play the file, troubleshoot its audio device separately with the [Sound Forge playback and ASIO checks](https://soundforgepro.com/sound-forge-pro-no-sound/). If installation itself is incomplete, use the [Boris FX Hub installation fixes](https://soundforgepro.com/sound-forge-installation-failed/). ## Verify the returned edit - Play the returned object and make sure it uses the edited copy you intended, not a stale or renamed file. - Compare its start, duration, fades and channel layout in the VIP; listen across both edit boundaries. - Confirm the untouched source remains available. If other objects share media, check those references too. - Render a fresh delivery file after a mix change and measure that file against the recipient’s requirements. ## Frequently Asked Questions ### Does Samplitude Suite 2026 include Sound Forge? Yes. Boris FX lists Sound Forge 2026 in the current Samplitude Suite-only feature set and in its April 2026 launch announcement. The standard Samplitude edition does not include it. ### Is Sound Forge built into Samplitude? No. Sound Forge is a separate Windows application. Samplitude passes an audio object to it through a configurable External Tools command, then uses the saved audio in the VIP project. ### How do I open a Samplitude object in Sound Forge? Select an audio object, right-click it, and choose Edit with external software > Edit in Sound Forge. If that command is absent, open File > Program Preferences > External Tools, use Add to create or select the Sound Forge entry, enable Create copy, and confirm it. ### Does Sound Forge overwrite the original audio? It can write changes to the audio data it receives. Enable Create copy so Samplitude makes the external edit on copied audio and can undo the object edit. Keep a separate backup of irreplaceable source media as well. ### When should I use Convert to Wave before transfer? Use it when the external editor cannot open the source format, or when you need a WAV working copy to avoid repeated lossy encoding. Boris FX warns that this converted-file route cannot transfer the result back to the virtual project normally, so test it and plan to import or relink the Wave file manually. ### Why is Edit in Sound Forge missing? The command is configurable. Confirm that Sound Forge is installed, then add it under File > Program Preferences > External Tools. For the included copy, verify the Suite entitlement and follow its version-specific activation instructions if prompted. Configuring the command does not activate a license. The entry appears in the audio object’s context menu. ### When should I stay in Samplitude? Stay in Samplitude when the decision depends on the timeline: object fades and effects, comping, routing, automation, mixing, or a master that is still changing. Open Sound Forge for a defined file-level job. ### Sound Forge and Vegas Pro Workflow for Video Editors URL: https://soundforgepro.com/sound-forge-vegas-pro-workflow-video-editors/ Last updated: 2026-09-30T13:24:26.000Z **Use Vegas Pro for the timeline and Sound Forge for a file-level repair.** In Vegas Pro, set Sound Forge under **Options > Preferences > Audio > Preferred audio editor**. Select an audio event and choose **Tools > Audio > Open Copy in Sound Forge**. Save with **Ctrl+S**, return to Vegas, and review the new active take against picture. If you are still deciding which application owns the job, use the [Sound Forge vs Vegas Pro comparison](https://soundforgepro.com/sound-forge-vs-vegas-pro/) before setting up the round trip. **Open Copy is the safer default for clip-specific work.** It keeps the original as another take. Use **Open in Audio Editor** only when you deliberately want to change the shared source file and every event that references it. ![Audio round-trip diagram: open a copy in VEGAS, edit and save in Sound Forge, then compare the returned take](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/09/vegas-round-trip-steps-20260912.webp) Send a copy, save it without renaming, then compare the returned take in VEGAS. [Open the full-size workflow](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/09/vegas-round-trip-steps-20260912.webp). ## Does the Vegas Pro and Sound Forge round trip still work in 2026? Yes. Current [Vegas Pro 2026 external-editor help](https://cdn.borisfx.com/borisfx/Documentation/vegas/2026/en/content/topics/7-edit/toolsound.htm) still documents the source-file route, and the companion [Open Copy procedure](https://cdn.borisfx.com/borisfx/Documentation/vegas/2026/en/content/topics/7-edit/opencopyeditor.htm) documents the safer copy-and-take route. [Boris FX announced its acquisition](https://blog.borisfx.com/press/boris-fx-acquires-vegas-pro-sound-forge-and-acid-pro) of Vegas Pro, Sound Forge, and Acid Pro on March 30, 2026; the current owner-hosted manual confirms that the handoff remains available. This is an external-editor workflow rather than a shared session. Vegas keeps the timeline, event placement, fades, automation, buses, and picture context. Sound Forge receives a media file. Changes to Vegas envelopes, track routing, video timing, or the rest of the mix won't appear in Sound Forge. The round trip depends on three things: a valid editor path, the correct Open in/Open Copy choice, and saving the file under the name and location Vegas expects. Audio produced by a nested project is a documented exception and must be handled in the source project or rendered to ordinary media first. ## 1\. Set Sound Forge as the preferred audio editor Open **Options > Preferences > Audio** in Vegas Pro and inspect **Preferred audio editor**. The [current Audio tab documentation](https://cdn.borisfx.com/borisfx/Documentation/vegas/2026/en/content/topics/12-preferences/prefaudiotab.htm) says Vegas automatically assigns Sound Forge when it detects the application. If the field is empty or points to an uninstalled version, browse to the current Sound Forge executable. 1. Close any Sound Forge file that could be confused with the test media. 2. In Vegas Pro, open **Options > Preferences > Audio**. 3. Set **Preferred audio editor** to the current Sound Forge executable. 4. Select a short disposable audio event and choose **Tools > Audio > Open Copy in Sound Forge**. 5. Make a harmless change, press **Ctrl+S**, and confirm that Vegas activates the returned copy as a take. A successful launch only proves the executable path works. Check that the saved copy returns as the active take before using the workflow on irreplaceable media. For other application handoffs, the [Sound Forge workflow guides](https://soundforgepro.com/tag/workflows/) separate file editing from the host application’s timeline jobs. ## 2\. Choose Open in Audio Editor or Open Copy | Vegas command | What opens | What Save changes | Use it when | | ----------------------------- | --------------------------------- | ------------------------------------------------------------ | -------------------------------------------------------- | | **Open in Audio Editor** | The event's source media | The source file; every event using it can reflect the change | A source-level repair is intentional for all uses | | **Open Copy in Audio Editor** | A new copy for the selected event | The copy; Vegas makes it the active take | The edit belongs to this clip or needs an A/B comparison | **Open in Audio Editor changes source media.** A camera WAV or extracted audio file may feed several events. Saving that shared file can change every event that references it, including cuts other than the one currently visible. **Open Copy preserves a route back.** Vegas adds the saved copy to Project Media and makes it the active take. The [current takes documentation](https://cdn.borisfx.com/borisfx/Documentation/vegas/2026/en/content/topics/7-edit/take.htm) says **T** selects the next take and **Shift+T** the previous one; the Take submenu can also choose the active version. Open Copy is still a working file; it isn't a backup system. Keep the project and its media in a stable folder and back up irreplaceable recordings before processing. ## 3\. Run a safe Vegas-to-Sound-Forge round trip 1. **Back up source media.** The [current project documentation](https://cdn.borisfx.com/borisfx/Documentation/vegas/2026/en/content/topics/3-projects/projects.htm) says a `.veg` file stores references to source files, so a project copy does not restore media overwritten by an external editor. 2. **Select the exact audio event.** Current help says multiple selected events can open in separate Sound Forge windows. 3. **Choose Open Copy for clip-specific work.** Reserve Open in Audio Editor for an intentional source-wide repair. 4. **Repair the named defect.** Preserve the file's duration unless the timeline edit explicitly permits a length change. 5. **Save without renaming.** Use Ctrl+S on the file Vegas opened. For the Open in route, current help documents that a new name or location prevents automatic detection and requires manual import. 6. **Review the returned take.** Listen across both event boundaries with room tone, music, and adjacent speakers active. 7. **Verify sync and the active take.** Compare the start, end, duration, and picture relationship before continuing the edit. Audio generated by a nested Vegas project cannot be sent directly to a sound editor. The [current nesting documentation](https://cdn.borisfx.com/borisfx/Documentation/vegas/2026/en/content/topics/3-projects/project%5Fnesting.htm) directs you back to the source project. Right-click the nested event and choose **Edit Source Project**. Edit there, or render the required audio from that source project to ordinary media. A nested 5.1 project is downmixed to stereo in the parent project; do not render that stereo output expecting to retain the original 5.1 channels. ## 4\. Keep timeline jobs in Vegas and file jobs in Sound Forge | Job | Best home | Reason | | --------------------------------------------------------------------- | ------------------------------------------------------------------ | ----------------------------------------------------------------------------------- | | Clip gain, fades, track EQ, automation, ducking, buses | Vegas Pro | The decision depends on the complete timeline and remains editable | | Sync, multicamera dialogue, music beds, stems against picture | Vegas Pro | The relationship between tracks and picture must remain visible | | One click, clipped samples, a damaged word, precise waveform boundary | Sound Forge | The defect belongs to one media file and benefits from sample-level access | | Steady hiss or hum in one source | Sound Forge or a suitable Vegas plug-in | Choose by defect, required control, and artifact risk | | Integrated loudness, LRA, and true-peak compliance | Vegas Loudness Meters/log or the meter named by the delivery brief | The current Vegas manual explicitly documents these measurements | | Noise, echo or wind cleanup | CrumplePop plug-ins in Vegas | Apply the appropriate repair while hearing the timeline context | | Stem separation and rebalancing | Standalone SoundApp | Separate parts outside the timeline, then check the imported result against picture | There's no reason to send every event out of Vegas. A track plug-in or envelope is easier to revise when the problem belongs to the mix. Send an event when the fault belongs to its media file and benefits from Sound Forge's [documented waveform repair, restoration, or controlled file processing](https://www.soundforge.com/sound-forge/pricing/). ## 5\. Clean dialogue without processing the performance away Name the defect before choosing a process. Broadband room noise, electrical hum, isolated clicks, clipping, plosives, and harsh sibilance are different problems. One heavy “clean dialogue” chain can soften consonants, pump room tone, or make adjacent shots less consistent than the original noise. Use Open Copy, then audition both a noise-only section and normal speech. If steady noise requires a noise print, exclude breaths, word tails, clothing movement, and transients. Preview quiet words and hard consonants before committing. The [background-noise workflow](https://soundforgepro.com/how-to-remove-background-noise-in-sound-forge-pro/) separates broadband reduction from hum and click repair instead of assigning one amount to every recording. For an isolated defect, follow the [click-and-pop repair procedure](https://soundforgepro.com/how-to-remove-clicks-pops-sound-forge-pro/). A steady tonal fault calls for the [hiss-versus-hum diagnosis](https://soundforgepro.com/remove-hiss-hum-sound-forge/) before any broadband reduction. Both routes keep the processing tied to the audible fault. If clipped dialogue can be recorded again, compare that option before attempting reconstruction. When a new take is impossible, repair a copy and judge the word against picture and the surrounding microphone tone. A rounded waveform isn't proof that the speech sounds natural. Back in Vegas, compare the returned take with adjacent shots. A cleaner file can still fail if room tone collapses at the cut or the speaker suddenly sounds farther away. ## 6\. Prepare voice-over and standalone audio files Voice-over delivered as a standalone WAV fits Sound Forge because the job centers on one file. Preserve the source, then work through the pass: trim approved boundaries, repair audible defects, shape tone conservatively, control dynamics, and measure against the written delivery brief. Once the file is approved, import it into Vegas, or use Open Copy when the narration already sits on the timeline. Avoid fixed high-pass, presence, de-essing, or noise-reduction values. Microphone, room, voice, distance, and performance determine whether those moves help. The [voice-over workflow](https://soundforgepro.com/sound-forge-pro-for-voice-over-recording/) covers recording level, punch-ins, breath editing, and ACX-specific delivery without presenting another narrator's curve as a preset. If the video client also needs isolated narration, music, and effects stems, keep the Vegas session as the mix source. Export the approved stems and inspect each file, preserving alignment and duration across every downstream version. ## 7\. Verify the final video mix as a file Vegas should produce the mix. Render the requested deliverable, then measure the file with the tool that actually reports the required metric. Current [Vegas Loudness Meters](https://cdn.borisfx.com/borisfx/Documentation/vegas/2026/en/content/topics/9-audio/loudness%5Fmeters.htm) document momentary and short-term loudness, integrated loudness, loudness range, and true peaks. In Sound Forge 2026, [Tools > Statistics](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/statistics.htm) explicitly includes true peak, integrated LUFS and LRA. Analyze the complete delivery file across the intended channels, not a short leftover selection. For six-channel surround audio, enable **Enable surround processing for files with 6 channels** on the **Status** tab of Preferences and compare each required value with the delivery brief. The [Sound Forge Statistics guide](https://soundforgepro.com/how-to-use-statistics-sound-forge-pro/) keeps peak, RMS, DC offset, selection length, and standards-based loudness checks in their proper lanes. The [Vegas loudness-log documentation](https://cdn.borisfx.com/borisfx/Documentation/vegas/2026/en/content/topics/9-audio/loudness.htm) makes an important distinction: a log created during rendering is calculated before the codec is applied. Because compression can change levels, Boris FX advises measuring the encoded result. Put that file alone in a clean verification project, preserve its channel layout, use unity gain without reapplying mix effects, select the full file and choose Tools > Generate Loudness Log. This prevents an accidental second measurement of the original mix timeline. Check channel layout, sample rate, duration, integrated loudness, LRA when required, and the specified peak or true-peak limit on the actual delivery media. Don't force every web video onto one inherited broadcast number. EBU R 128 and ATSC A/85 are documented broadcast modes, and they aren't universal upload presets. Use the destination's current written specification. If the file fails because of balance, automation, bus processing, or interaction between tracks, return to the Vegas mix. Use Sound Forge only for a file-level correction that does not hide a decision that should remain editable in the timeline. ## 8\. SoundApp, CrumplePop plug-ins, or Sound Forge? The [Boris FX plan comparison checked September 12, 2026](https://www.vegascreativesoftware.com/vegas-pro/plans-pricing/) lists integrated audio tools in all three Vegas tiers. Vegas Pro Plus adds Sound Forge and CrumplePop VST plug-ins. Vegas Pro Ultimate includes those products and the standalone CrumplePop SoundApp. CrumplePop plug-ins target quick in-timeline cleanup such as background noise, echo/reverb, wind, and speech clarity. SoundApp is presented as a standalone cleaning, separation, and rebalancing tool. Sound Forge is the more direct fit for exact waveform selection, manual repair, a controlled processing chain, file conversion, batch work, and independent file inspection. Choose the least destructive route that gives enough control, then audition the result. AI separation can leave musical noise or alter speech texture; a noise-print process can suit steady noise and still fail on changing traffic. The fault and the delivery requirement decide the tool. ## 9\. Fix common round-trip failures ### Sound Forge does not appear in the Vegas Audio menu Open **Options > Preferences > Audio** and set **Preferred audio editor** manually, making sure the path points to the current executable rather than an uninstalled older version. Repeat the disposable-event test after changing the path. If the old route remains in use, save the project and try restarting Vegas; a restart is a troubleshooting step, not a documented requirement for every path change. ### Vegas does not update after Sound Forge saves For the Open in Audio Editor route, one documented cause is changing the file name or folder with Save As. Save the file Vegas opened with Ctrl+S; if it was renamed or moved, import the new file manually. For Open Copy, confirm that the copy was saved and inspect the active take. Also confirm that the media remains online. ### The edited event changed elsewhere in the project The shared source may have been opened with **Open in Audio Editor**. In Project Media, right-click the file and choose **Select Timeline Events**. The [documented selection command](https://cdn.borisfx.com/borisfx/Documentation/vegas/2026/en/content/topics/4-media/project%5Fmedia.htm) finds events using that media in their active take; it does not inventory inactive takes or other projects that share the file. Restore the source from backup, or choose a take that references genuinely untouched media. A take referencing the same overwritten file cannot undo that overwrite. Then use Open Copy for the clip-specific repair. ### Open in Audio Editor is unavailable Confirm that an audio event is selected, its media is online, and the Preferred audio editor path is valid. Audio generated by a nested project is a documented exception; open the source project or render ordinary media before attempting the external edit. ### The returned take is out of sync Return to the original take and compare file duration, sample rate, event stretch/pitch properties, and the start and end boundaries. These are diagnostic checks, not a guaranteed root cause. Repeat the repair without any process that changes duration unless the timeline is meant to be reconformed. ### Sound Forge opens but playback is silent First confirm that the expected file, duration and channels arrived and that the source is not silent. Compare playback with a known-good file. If the media is correct but output remains silent, keep the returned copy untouched while you follow the [Sound Forge playback and ASIO checks](https://soundforgepro.com/sound-forge-pro-no-sound/). Once Sound Forge plays the file correctly, repeat the save-and-return test. ## Round-trip checklist 1. **Set the preferred audio editor.** Point Vegas to the current Sound Forge executable and complete a disposable test. 2. **Back up source media.** Protect irreplaceable files before any source-level edit. 3. **Open a copy for clip-specific work.** Use Open Copy so the original remains available as a take. 4. **Repair the identified defect.** Process the audible problem and preserve duration unless the edit allows a change. 5. **Save without renaming.** Use Ctrl+S and keep the path Vegas expects. 6. **Review the returned take.** Check the active take, sync, boundaries, room tone, picture, and adjacent clips. 7. **Verify the delivery file.** Measure the rendered or encoded media against the current written specification. ## Frequently Asked Questions ### How do I open a Vegas Pro audio event in Sound Forge? In Vegas Pro, open Options > Preferences > Audio and set Sound Forge as the Preferred audio editor. Select the event, then choose Tools > Audio > Open Copy in Sound Forge for a clip-specific edit. Vegas opens a copy and makes the saved result the active take while retaining the original. ### What is the difference between Open in Audio Editor and Open Copy? Open in Audio Editor opens the source media. Saving it can change every event that references that file. Open Copy creates separate media for the selected event and activates the saved result as a take, so the original remains available for comparison or recovery. ### Why does Vegas Pro not update after I save in Sound Forge? For the Open in Audio Editor route, one documented cause is changing the file name or location with Save As. Save the file Vegas opened with Ctrl+S; if it was renamed or moved, import the new file manually. For Open Copy, confirm that the copy was saved and check which take is active. Also verify the Preferred audio editor path and media status. ### Can I switch back to the original after using Open Copy? Yes. Vegas keeps the original and edited media as takes in the event. Select the event and press T or Shift+T to choose the next or previous take, or choose the active version from the event's Take submenu. ### Should dialogue cleanup stay in Vegas or go to Sound Forge? Keep gain, automation, track EQ, buses, and other mix decisions in Vegas. Send a copy to Sound Forge when one media file needs precise waveform repair or source-specific restoration. Review the returned take against adjacent shots, room tone, music, and picture before accepting it. ### Can audio from a nested Vegas project be opened in Sound Forge? No. Current Vegas Pro 2026 help says audio events from nested projects cannot be edited in an external sound editor. Use Edit Source Project, then edit or render the required audio there. Nested 5.1 audio becomes a stereo downmix in the parent project, so return to the source project when the original surround channels must be preserved. ### Is Sound Forge included with every Vegas Pro plan? No. The Boris FX plan comparison checked on September 12, 2026 lists Sound Forge and the CrumplePop VST plug-ins with Vegas Pro Plus and Ultimate, but not the base Vegas Pro tier. The standalone CrumplePop SoundApp is listed for Ultimate. *Documentation reviewed September 12, 2026\. The procedures follow current Boris FX help; this review does not claim a newly performed VEGAS–Sound Forge round trip.* ### Sound Forge vs Vegas Pro URL: https://soundforgepro.com/sound-forge-vs-vegas-pro/ Last updated: 2026-10-09T21:58:56.000Z **Quick answer:** pick VEGAS Pro for a video edit or a multitrack audio mix, and Sound Forge for detailed work on a single audio file: repair, measurement, processing and delivery. Most projects don't need both. Start with the tools you already own and add the other application when your current workflow can't handle a task comfortably. This comparison sits in the [Sound Forge Comparisons hub](https://soundforgepro.com/tag/comparisons/) and covers the Boris FX 2026 products. The contents of old Sony or MAGIX bundles are a separate story. ## Sound Forge vs Vegas Pro: Feature Comparison The real split is files versus a production timeline. [Sound Forge's product documentation](https://www.soundforge.com/sound-forge/) says outright that it isn't a multitrack DAW, even though it records and edits files with up to 32 channels. Those channels aren't separate tracks with clips you arrange independently. [VEGAS Pro's current feature page](https://www.vegascreativesoftware.com/vegas-pro/plans-pricing/) lists unlimited audio and video tracks, though real project capacity still depends on your computer and media. On a narrow screen, scroll the comparison table sideways. | Task | Sound Forge 2026 | VEGAS Pro 2026 | | ------------------------ | ------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------- | | Main workspace | Individual audio-file editing, restoration and mastering | Video production and multitrack audio mixing | | Detailed repair | Direct sample editing, Pencil and Interpolate | Event editing and effects; an external editor is available for file-level work | | Non-destructive work | Event-based mode alongside default destructive editing | Timeline edits leave source media unchanged; external source edits are a separate risk | | Audio processing | EQ, dynamics, metering, noise reduction and repair; third-party effects support | Track and bus processing for the mix; CrumplePop plug-ins in Plus and Ultimate | | Video | Supports some video formats, but is not a multitrack video NLE | Picture editing, grading, titles, compositing and final video render | | Current editions | Sound Forge and Sound Forge Plus | VEGAS Pro, Plus and Ultimate; Sound Forge included in Plus and Ultimate | | Published OS requirement | Windows 11 | Windows 11 | Both current requirements pages name Windows 11: [Sound Forge specifications](https://www.soundforge.com/sound-forge/system-requirements/) and [VEGAS Pro specifications](https://www.vegascreativesoftware.com/vegas-pro/system-requirements/). Neither lists a current native macOS edition. VEGAS also publishes separate hardware recommendations for 4K and AI work, so a machine that's fine for basic file editing may still struggle with demanding video projects. ## What Vegas Pro Does That Sound Forge Doesn't VEGAS keeps dialogue, music, effects and picture on one production timeline. That's where you arrange a scene, sync sound, automate the mix, grade footage and render the finished video. Sound Forge can open or export certain video formats, but that doesn't turn it into that kind of editing environment. ![VEGAS Pro layout with the video preview, a video track, dialogue, music and effects audio tracks, and the master bus](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/10/sf-vegas-pro-timeline-layout-v20261005.webp) VEGAS Pro's production timeline keeps picture and multiple audio tracks together. The [2026 release notes](https://cdn.borisfx.com/borisfx/Documentation/vegas/2026/en/content/topics/1-before/whatsnew.htm) mark offline Speech-to-Text and Text-to-Speech as **subscription only**. Offline processing does not mean those features are included with a perpetual license. Sound Forge also advertises locally processed Text to Speech; voice generation alone is not the reason to choose a video editor. For cleanup, Plus and Ultimate list CrumplePop VST plug-ins. Ultimate also lists the standalone CrumplePop SoundApp for audio cleanup and stem separation. These are separate components, and none of them is Sound Forge under another name. Run a copy of your difficult recording through them before buying on a promised result, because no cleanup tool can guarantee an undamaged voice or cleanly separated stems. ## What Sound Forge Does That Vegas Pro Doesn't Sound Forge provides direct waveform repair. Its Pencil tool redraws samples; Interpolate bridges a very short damaged selection. Both are meant for an isolated defect. A long passage of missing speech is beyond them. The [click and pop repair guide](https://soundforgepro.com/how-to-remove-clicks-pops-sound-forge-pro/) explains the tool choice and why an over-wide repair can remove useful audio. ![Sound Forge 2026 workspace with the Instant Action panel, a two-channel waveform and channel meters](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/10/sf-2026-workspace-instant-action-meters-v20261005.webp) Sound Forge's file-focused workspace puts the waveform, processing tools and meters together. The [current Sound Forge feature list](https://www.soundforge.com/sound-forge/pricing/) includes broadband noise reduction, click/crackle removal, clipping repair, EQ, dynamics, peak/loudness metering and batch processing in the base editor. You don't need Plus just to get these tools. Restoration can introduce artifacts, though: keep the source and compare the processed copy before committing. For a finished stereo mix, a file editor is a practical place to inspect peaks, adjust processing and check the exported master. That's a workspace preference; it doesn't prove better sound or faster processing. VEGAS can finish a mix through its own processing chain. Use the [Sound Forge mastering guide](https://soundforgepro.com/how-to-master-a-track-in-sound-forge-pro/) when you need the file-finishing steps without a second production timeline. ## The Overlap: Audio Editing in Vegas Pro Both applications can record, edit and process audio. VEGAS supports track and bus routing; Sound Forge supports multichannel files and third-party effects. Noise reduction isn't exclusive to Sound Forge, and sample-accurate timing is a different thing from drawing the waveform's sample values. Sound Forge isn't always destructive: its current feature list includes an event-based non-destructive mode. On the other side, a non-destructive VEGAS timeline won't protect a source file you deliberately overwrite in an external editor. What matters is the command and the save destination, whatever label the application carries. Keep a dialogue cleanup in VEGAS if an available effect does the job. Open a copy in Sound Forge when you need manual sample repair or a separately processed file. A podcast with independently arranged speakers, music and effects belongs in a multitrack environment; Sound Forge helps before or after that session and doesn't replace it. If the real choice is audio-file editing versus music production, read [Sound Forge versus REAPER](https://soundforgepro.com/sound-forge-pro-vs-reaper/). ## How They Work Together **Save the VEGAS project and keep an untouched copy of the source media first.** For an ordinary audio event, the safer external-edit route is [Tools → Audio → Open Copy in \[editor name\]](https://cdn.borisfx.com/borisfx/Documentation/vegas/2026/en/content/topics/7-edit/opencopyeditor.htm). Edit and save that copy. The documented result is a new file set as the event's active take, leaving the original source available. If Sound Forge isn't selected, go to [Options → Preferences → Audio → Preferred audio editor](https://cdn.borisfx.com/borisfx/Documentation/vegas/2026/en/content/topics/12-preferences/prefaudiotab.htm) and browse to the installed editor's executable. Pick the application you actually intend to use rather than guessing a version-specific installation path. The separate [Open in \[editor name\]](https://cdn.borisfx.com/borisfx/Documentation/vegas/2026/en/content/topics/7-edit/toolsound.htm) command opens source media. Saving over it can affect every event that references the same file. If you change the name or location with Save As, you'll have to import the new file yourself. Both external-editor help pages exclude audio events from nested projects, so don't assume the same command works on every timeline item. For a **whole mix**, render an audio file instead of treating an event copy as a complete mix export. The current [VEGAS Pro 2026 rendering help](https://cdn.borisfx.com/borisfx/Documentation/vegas/2026/en/content/topics/10-export/render.htm) uses **File → Render**; older guides call it Render As. Choose a suitable WAV output, confirm the range, sample rate and channel layout, and give it a new filename. A 24-bit PCM WAV can be a working handoff when both applications and the delivery plan support it. It isn't a universal requirement, and it won't bring back detail lost in the source. After processing, keep the original render, import the finished copy and check its start position, duration, channels and sync against picture. Confirm that you are not playing both versions or applying the same processing twice. Listen to the final exported file too: VEGAS documents that its render-time loudness log measures before the codec, so a lossy deliverable needs a separate post-encode check. The [dedicated VEGAS-to-Sound-Forge workflow guide](https://soundforgepro.com/sound-forge-vegas-pro-workflow-video-editors/) covers the handoff in more detail. ## Vegas Pro Tiers and Sound Forge Bundling As checked September 15, 2026, the [current VEGAS tier matrix](https://www.vegascreativesoftware.com/vegas-pro/plans-pricing/) includes Sound Forge in **Plus and Ultimate, not base VEGAS Pro**. It names Sound Forge; Sound Forge Plus isn't listed. Don't assume the separate Plus-only Melodyne, Vandal, VariVerb II and 3D Reverb extras come with it. The [Sound Forge versus Sound Forge Plus comparison](https://soundforgepro.com/sound-forge-vs-sound-forge-plus/) explains that separate edition choice. The [March 30 acquisition announcement](https://blog.borisfx.com/press/boris-fx-acquires-vegas-pro-sound-forge-and-acid-pro) contradicts itself: its Plus description includes Sound Forge, while its table marks Sound Forge only under Ultimate. That alone doesn't show a later bundle change. Go by the current product matrix and the exact purchase offer, and ignore old screenshots or the contents of a Sony/MAGIX-era suite. The same announcement gives these **historical US launch list prices**: VEGAS Pro at $17.95 monthly, $99.95 annually or $219.95 perpetual; VEGAS Pro Plus at $24.95 monthly, $149.95 annually or $299.95 perpetual; Ultimate at $39.95 monthly or $199.95 annually, with no perpetual option listed. Standalone Sound Forge was $24.95 monthly, $149.95 annually or $299.95 perpetual. Currency, tax, discounts, eligibility and the offer's bundle terms can change what you pay. At those launch figures, VEGAS Pro Plus and standalone Sound Forge share the same listed subscription and new-perpetual prices. That makes the bundle worth checking before you buy the editor twice. It doesn't prove today's prices match, or that every included component carries the same rights. Compare the live offer with what you already own. Boris FX offers subscription and perpetual licensing for VEGAS Pro and Plus, and subscription licensing for Ultimate. A perpetual license is not a promise of every future release. The [general Upgrade and Support policy](https://borisfx.com/store/upgrade-and-support-plan/) describes a separate renewable support/update term and says perpetual licenses remain functional after that term expires. It explicitly lists VEGAS Pro under automatic renewals; confirm the terms attached to your Sound Forge or bundle purchase rather than assuming every product has identical renewal conditions. The [Boris FX license agreement](https://borisfx.com/store/eula/) ties the licensed product to the invoice. Check the license supplied with each bundled component before assuming it grants the same use, update or renewal rights as the host. ## Which One First? **Choose VEGAS first** for picture editing or a multitrack mix. Check whether your existing edition already supplies the cleanup tools you need. Buy Ultimate for a specific included application or feature you'll use; the name alone doesn't mean every audio problem calls for it. **Choose Sound Forge first** when the job starts and ends with individual audio files: a voice recording, a transfer, a repair or a finished master. Follow the [Sound Forge beginner workflow](https://soundforgepro.com/how-to-use-sound-forge-tutorial/) to learn the editor. For independent tracks or MIDI composition, investigate a DAW instead. **Use both** when a video production needs file-level repair or a separate audio deliverable. Check the bundle before buying and keep the handoff reversible. ## Frequently Asked Questions ### Is Sound Forge included in Vegas Pro? The current VEGAS matrix checked September 15, 2026 includes Sound Forge in Plus and Ultimate, not base VEGAS Pro. It does not identify that inclusion as Sound Forge Plus. Confirm the exact offer and license terms before paying. ### Do I need Sound Forge if I already have Vegas Pro? Not automatically. Use the effects and mix tools you already own first. Add a file editor when you need direct waveform repair or a separately processed audio deliverable. Ordinary noise reduction alone does not establish a need for another application. ### Can Vegas Pro do everything Sound Forge does for audio? No. VEGAS offers a multitrack production timeline, while Sound Forge provides direct waveform editing and file-finishing tools. Their effects overlap. Choose by the operation, not an assumption that one always sounds better. ### Are Sound Forge and Vegas Pro made by the same company now? Yes. Boris FX announced its acquisition of VEGAS Pro, Sound Forge and Acid Pro from MAGIX on March 30, 2026\. They remain separate applications with different editing roles. ### Which is better for mastering audio: Sound Forge or Vegas Pro? Sound Forge is a practical choice for inspecting and finishing an individual stereo file. VEGAS can process and render an existing mix without an external editor. Neither workspace alone guarantees a better-sounding master; the processing and verified deliverable determine the result. ### What is the difference between Sound Forge and Vegas Pro for voice-over work? Use VEGAS to place a voice against picture and mix it with other tracks. Use Sound Forge for direct file repair or a separate processed voice deliverable. For external edits, prefer a copy, preserve the original and check the returned file's timing. *Fact-checked September 15, 2026 against the current product matrices, Windows requirements, VEGAS Pro 2026 help and the dated Boris FX acquisition announcement. Launch prices are historical figures, not a current checkout quote.* ### Sound Forge Pro for Music Production: 2026 Workflow URL: https://soundforgepro.com/sound-forge-pro-for-music-production/ Last updated: 2026-10-06T06:45:00.000Z **Sound Forge Pro can be useful for music production, but it should not be mistaken for a music-production DAW.** Use a DAW to compose, sequence MIDI, arrange, overdub and mix. Use Sound Forge when the job has become one audio file: a sample, a vocal take, a stem, a stereo mix or a folder of deliverables. For composition and sample preparation, distinguish three things: Sound Forge can record and edit multichannel files, but it doesn't provide a multitrack song session, and the current package does not advertise a general production-sample library. It does have an Explorer for browsing your files and regions; that is different from a bundled sound library. The current [official Sound Forge comparison](https://www.soundforge.com/sound-forge/pricing/) describes it as a specialist editor for a single audio file and explicitly says it is not a DAW. **Recommended boundary:** keep composition and mixing in the DAW. Send only the audio that needs focused editing, repair, mastering or batch delivery to Sound Forge. If your DAW already handles these jobs comfortably, a second editor is optional. ## Can Sound Forge be used to produce music? Yes, in the literal sense. Sound Forge can record audio, cut and rearrange waveform sections, mix clipboard audio into a file, run effects and export a finished result. The current help documents [Edit → Paste Special → Mix](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/mix.htm) for combining audio at the cursor. That doesn't make it a sensible replacement for a DAW. There's no piano roll, virtual-instrument workflow, track mixer, bus structure or arrangement view. Audio quality isn't the difference; a capable DAW and Sound Forge can both produce transparent results. What separates them is how quickly and safely each application handles the job. Burial did make music in Sound Forge: in [his interview with The Wire](https://www.thewire.co.uk/in-writing/interviews/burial%5Funedited-transcript), he confirmed producing the album in it and described working with waveforms rather than a sequencer. That historical example shows what determined editing can achieve; it does not make the current application a conventional DAW. ![Multitrack DAW arrangement beside a stereo file open for detailed waveform editing](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/10/music-production-ui-daw-vs-sound-forge-v2-v20261005.webp) A DAW handles MIDI, arrangement and multitrack mixing; Sound Forge handles work inside one audio file. [Open the full-size workflow](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/10/music-production-ui-daw-vs-sound-forge-v2-v20261005.webp). ## Sound Forge versus a DAW | Job | Sound Forge | DAW | | -------------------------------------- | -------------------------------------------------- | ------------------------------------------------- | | Write with MIDI or virtual instruments | No | Use the DAW | | Arrange a song across many tracks | No multitrack session | Use the DAW | | Overdub while hearing previous takes | Limited backing-channel monitoring within one file | Use for track lanes, comping and full overdubbing | | Edit a sample at waveform level | Strong fit | Also possible; workflow varies | | Repair one damaged take or stem | Strong fit | Possible with suitable tools | | Process a folder consistently | Batch Converter | Depends on the DAW | | Master and inspect a stereo file | Strong fit | Also valid | If you need loop-based composition, MIDI and multitrack recording from the same product family, the [current ACID Pro page](https://www.soundforge.com/acid-pro/) identifies ACID as the DAW. Our [ACID Pro versus Sound Forge comparison](https://soundforgepro.com/acid-pro-vs-sound-forge/) explains the division without treating the two products as interchangeable. ## Where Sound Forge fits in a modern producer workflow Sound Forge works best at the handoff points where a project becomes a file: - **Before the DAW:** trim, repair and format a sample or field recording. - **During production:** clean one vocal take, instrument recording or problem stem, then return it to the session. - **After the mix:** inspect, edit, master and export the finished stereo file. - **At delivery:** create consistent formats and filenames with the Batch Converter. Keep the DAW session as the source of the arrangement. Use a separately named output file for each repair so that you can replace a stem without losing the original. The [Sound Forge workflows hub](https://soundforgepro.com/tag/workflows/) separates these jobs into recording, editing and delivery guides. ## Prepare samples and build your own library The current package does not advertise a general library of production-ready sounds; use it to prepare audio you have recorded or have permission to use. That distinction is useful because “sample library” can mean either content to browse or a folder you are building yourself. 1. **Keep untouched originals.** Work into a separate output folder, especially when the source cannot be recreated. 2. **Audit the files.** Check channel layout, sample rate, bit depth, leading silence and obvious damage before applying any batch action. 3. **Trim and snap deliberately.** The current help places zero-crossing alignment at [Edit → Selection → Snap to Zero](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/selection%5Fsnapping.htm), with **Z** as the shortcut. This reduces the chance of a click, but is not a guarantee: listen across the edit and check both channels of stereo material. 4. **Repair only what is wrong.** Remove an isolated click or unwanted tail without applying the same restoration preset to every sound. 5. **Batch only the shared requirement.** Use **Tools → Batch Converter** for a deliberate output format, naming rule or verified effect chain, then import the results into the sampler or DAW. ![Sample preparation diagram: preserve originals, repair a working copy and verify exports in a separate folder](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/09/music-production-sample-workflow-20260912.webp) Preserve originals, check each working copy, then verify one export before batching shared settings. [Open the full-size workflow](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/09/music-production-sample-workflow-20260912.webp). The [Sound Forge 2026 Batch Converter help](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/proonly/the%20batch%20converter.htm) confirms that one job can combine processing, metadata and multiple export formats. Its Default Template can preserve source attributes when the output format supports them. Test one representative export first: a codec may not accept the source rate, channel layout or sample type, and FLAC cannot preserve floating-point samples. That is safer than converting everything merely to make the folder look uniform. For detailed batch setup, use our [Sound Forge batch-processing guide](https://soundforgepro.com/how-to-batch-process-files-sound-forge-pro/). For resampling decisions, see the [sample-rate guide](https://soundforgepro.com/how-to-change-sample-rate-sound-forge-pro/). ## Record vocals and instruments: multichannel is not multitrack Sound Forge can record a microphone, instrument, stereo pair or multichannel input into one data window. The official [multichannel recording guide](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/recording%5Fmultichannel%5Faudio.htm) says the recorded channel count depends on both the enabled hardware inputs and the channels in the destination data window and explicitly directs full multitrack work to Vegas or ACID. Use Sound Forge when you need a clean standalone take or a simultaneous multichannel capture that belongs in one file. For separate take lanes, comping, arrangement and independent track mixing, use a DAW. There is a narrower Sound Forge option: [Play unselected channels when recording](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/recording%5Foptions.htm) lets backing on channels 1/2 play while you record selected channels 3/4 in the same four-channel file. That is not a DAW session. Our updated [Sound Forge 2026 recording workflow](https://soundforgepro.com/how-to-record-audio-in-sound-forge-pro/) covers Windows permission, ASIO routing, Record Options, the prerecord buffer and test-file verification. It avoids universal buffer and level settings because the safe configuration depends on the interface, driver and session. ## Clean a stem without pretending Sound Forge is a mixer A vocal, drum or effects stem is still one file, so it fits Sound Forge well. Open a copy, identify the actual problem, process it, compare against the unprocessed version and return the corrected stem to the DAW at the same start position and length. Don't run a generic “vocal stem” or “drum stem” preset across every project. Noise reduction, EQ and dynamics solve different problems. A stem with two clicks needs the clicks repaired; a constant noise floor needs a diagnosis. If the stem is already clean, leave it alone. The current [Plug-In Chain documentation](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/proonly/plug-in%5Fchainer.htm) describes the View → Plug-In Chain as non-destructive real-time processing for the data window, applied when the file is saved. For a selection, use **FX Plug-Ins → Apply Plug-In Chain**. The distinction matters when only part of a stem needs treatment. ## Master a finished mix without chasing one magic number A finished stereo mix is the clearest music-production use case for Sound Forge. Trim heads and tails, inspect the file, build a reversible processing chain, compare at matched listening level, then render the formats required by the distributor, client or manufacturing specification. Save the processed result under a new filename, reopen it and check it without an active playback chain. Select the whole file before [Tools → Statistics](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/statistics.htm): the dialog measures the selected region. The 2026 help documents sample peaks, RMS, DC offset, true peaks, integrated LUFS and loudness range. Use the readings requested by the delivery specification, and listen to the start, end and repaired passages. Don’t turn a streaming platform’s playback-normalization reference into a universal mastering target for every release. [Plan dither at the final quantization step](https://soundforgepro.com/sound-forge-bit-depth-dither/) into an integer deliverable, not merely by comparing source and output filenames. The current [Bit-Depth Converter help](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/bit%5Fdepth%5Fconverter.htm) explains that increasing bit depth cannot restore existing quality and documents dither for downward conversion. A 24-bit source processed in floating point may still need a final quantization decision on 24-bit integer export. An unchanged integer copy needs no second pass. Keep a floating-point working master before final integer conversion. Make sample-rate changes before final dither and avoid two dither stages. [FabFilter’s dither guidance](https://www.fabfilter.com/help/pro-l/using/dithering) explains why further processing after dither defeats its purpose; this is a processing-order principle, not a requirement to buy that plug-in. For the complete chain and verification logic, use the [Sound Forge mastering guide](https://soundforgepro.com/sound-forge-pro-for-mastering/) or the shorter [master-a-track workflow](https://soundforgepro.com/how-to-master-a-track-in-sound-forge-pro/). ## Sound Forge versus Sound Forge Plus for producers The current tiers are **Sound Forge** and **Sound Forge Plus**. Don’t use old Pro 18 Suite bundle lists to describe the 2026 product. The official comparison says the base tier includes the core editor, metering, VST2/VST3/ARA support, repair tools, noise reduction, multichannel handling, batch processing and event-based non-destructive editing. Plus adds **Melodyne 5 Essential, Vandal, VariVerb II and 3D Reverb**. It does not advertise a sample-content library, RX Elements or Ozone Elements as part of the current Plus package. Choose Plus only if those specific additions solve a job you actually have. Pitch correction for a vocal editor, amplifier emulation for guitar or the added reverbs may justify it; none of them adds MIDI composition or a multitrack DAW. See our current [Sound Forge versus Sound Forge Plus comparison](https://soundforgepro.com/sound-forge-vs-sound-forge-plus/) before buying. ## A practical DAW-to-Sound-Forge workflow 1. **Create, record and mix in the DAW.** Keep MIDI, arrangement, automation, buses and track interaction in the session designed for them. 2. **Export the required file.** Send a sample, problem stem or stereo mix without inventing a universal headroom target. Preserve the session and source files. 3. **Open a copy in Sound Forge.** Confirm format, channels and file length before editing. Use event-based mode or another reversible path when the job benefits from it. 4. **Edit, repair or master only what the file needs.** Preview, bypass and compare. Don’t process merely because a tool is available. 5. **Verify and deliver.** Check the rendered file, save the higher-resolution master, create required derivatives and return stems to the DAW without changing alignment. This workflow gives every application a clear responsibility and keeps revisions traceable: the DAW remains the source of the mix, while Sound Forge holds focused file-level work and final deliverables. ## Who should use Sound Forge for music production? **Good fit:** Windows producers who regularly edit individual samples, clean isolated recordings, repair stems, master stereo files or deliver many formats. It is especially useful when a DAW’s waveform editor makes short file-level jobs feel heavier than they should. **Poor fit:** anyone looking for their first composition environment, a loop library, virtual instruments, MIDI sequencing, live-performance clips, multitrack overdubbing or a conventional mixer. Start with a DAW. Add Sound Forge only when the file-editing workload justifies a specialist editor. ## Frequently Asked Questions ### Can Sound Forge Pro be used for music production? Yes, for editing samples, cleaning takes or stems, mastering a stereo mix and creating deliverables. It is not a complete DAW, so composition, MIDI, arrangement and multitrack mixing should normally stay in another application. ### Is Sound Forge a multitrack recorder? No. Sound Forge can record several hardware inputs as channels in one multichannel file, but it does not provide a DAW-style multitrack session for overdubbing, arranging and mixing independent tracks. ### Does Sound Forge include a sample library? The current package does not advertise a general production-sample library. Sound Forge can browse your own files and regions through Explorer and can edit or batch-process them. Use a [sampler](https://soundforgepro.com/sampler-software/) or dedicated library manager when you need additional auditioning, tagging or instrument functions. ### Can I make a complete beat or song in Sound Forge? You can paste and mix audio into a single waveform, but the workflow lacks MIDI, virtual instruments, arrangement tracks and a multitrack mixer. A DAW such as ACID Pro, REAPER, [Ableton Live](https://abletonlive.net/ableton-live-12-setup/) or another production environment is the practical choice for a complete song. ### Is Sound Forge good for mastering music? Yes. Its single-file view, Statistics, loudness tools, Plug-In Chain, precise editing and export options suit stereo mastering. The result still depends on monitoring, judgment and the processing choices, not the application name. ### Can I record vocals or instruments in Sound Forge? Yes, for mono, stereo or multichannel files. Sound Forge can play unselected backing channels while recording selected channels within one file. Use a DAW for separate track lanes, comping, full cue mixes and arrangement. ### What does Sound Forge Plus add for producers? Current Plus adds Melodyne 5 Essential, Vandal, VariVerb II and 3D Reverb to the base Sound Forge toolset. It does not turn Sound Forge into a DAW, and no general sample library is advertised. If the project still needs arrangement, MIDI, or independent tracks, compare [ACID Pro and Sound Forge](https://soundforgepro.com/acid-pro-vs-sound-forge/) or see how [Sound Forge fits beside a full DAW](https://soundforgepro.com/sound-forge-pro-vs-reaper/). Once the mix becomes a file-level job, build a tested [Batch Converter workflow](https://soundforgepro.com/how-to-batch-process-files-sound-forge-pro/) for repeatable deliverables instead of rebuilding each export by hand. *Last fact-checked: September 12, 2026 against the current Boris FX Sound Forge, Sound Forge Plus, ACID Pro, and Sound Forge Pro 2026 documentation.* ### Sound Forge Pro vs REAPER URL: https://soundforgepro.com/sound-forge-pro-vs-reaper/ Last updated: 2026-10-09T21:06:10.000Z Sound Forge Pro and REAPER both edit audio, but they start from different objects. Sound Forge opens an audio file for direct waveform editing, restoration and mastering; its default workflow is destructive, with a separate event-based non-destructive mode. REAPER opens a project for multitrack recording, MIDI, routing, mixing and rendering. They overlap, but one is a file editor and the other is a DAW. For other editor-versus-DAW choices, the [Sound Forge Comparisons hub](https://soundforgepro.com/tag/comparisons/) groups the relevant comparisons by application. Quick answer: choose REAPER for multitrack recording, MIDI, routing and mix revisions. Consider Sound Forge when direct waveform repair is the recurring job and you prefer a dedicated file editor. REAPER can also master finished files and process batches, so owning both is optional. Try the same representative job in each before paying for a second application. ## Comparison Table The table compares the current Sound Forge 2026 feature set with REAPER 7.82\. Feature counts matter less than one question: does the work need to stay an editable project, or be finished as an individual audio file? | Task | Sound Forge 2026 | REAPER 7.82 | | ----------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------- | | **Primary role** | Single-file waveform editing, repair, batch work and mastering | Full DAW for recording, MIDI, arranging, mixing and rendering | | **Multitrack project** | No DAW-style arrangement; records and edits files with up to 32 channels | Yes; tracks, folders, buses, automation, takes and project recall | | **MIDI sequencing** | No | Yes; MIDI editing, routing and virtual instruments | | **Waveform repair** | Direct sample zoom, Pencil tool and Interpolate | Item and spectral editing; direct sample redraw is not the standard built-in workflow | | **Restoration** | Click/crackle removal, clipping repair and broadband noise reduction | ReaFIR, spectral edits, stock FX and third-party plug-ins | | **Non-destructive work** | Default destructive processing plus a separate event-based non-destructive mode | Non-destructive project workflow by default | | **Mastering and delivery** | Statistics, loudness metering, file processing, batch export and dither workflow | Master FX, LUFS normalization, true-peak limiting, dither, DDP and render reports | | **Automation and scripting** | Batch processing and file-oriented scripting | Batch conversion/rendering, actions, ReaScript and extensions | | **Platform** | Windows | Windows, macOS and Linux | | **Price evidence: REAPER current; Sound Forge March 2026 launch** | [$299.95 perpetual / $24.95 monthly at launch](https://blog.borisfx.com/press/boris-fx-acquires-vegas-pro-sound-forge-and-acid-pro) | [$60 discounted / $225 commercial](https://www.reaper.fm/purchase.php) | | **Evaluation** | 15 days, fully functional | 60 days, fully functional | ## Where Sound Forge Helps with File Repair Sound Forge provides a built-in [Pencil tool for redrawing samples](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/the%5Fpencil%5Ftool.htm) at close zoom. Its [Repair: Interpolate command](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/proonly/the%5Ftools%5Ftoolbar.htm) rebuilds a short selection from its boundaries. Both can help with a small isolated click, though neither guarantees badly damaged audio comes back. REAPER offers item fades, take effects and spectral edits. The older community discussion linked below mentions sample-redraw scripts, but that doesn't show an included, documented pencil workflow. Don't assume a script from an old discussion works with your current installation. ![Single-file editing and multitrack production connected by an optional WAV handoff](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/10/sound-forge-vs-reaper-ui-handoff-20260802-v20261006.webp) Sound Forge edits a file; REAPER retains a multitrack project. Either can finish audio independently. The [current Sound Forge feature matrix](https://www.soundforge.com/sound-forge/pricing/) promises click and crackle removal, clipping repair and broadband noise reduction in the base application. Those are safer buying criteria than old plug-in names, because bundles and menus changed across the Sony, MAGIX and Boris FX releases. REAPER can clean audio with ReaFIR, spectral edits, stock effects and third-party restoration plug-ins; Sound Forge remains more direct when the job is centered on repairing one file rather than building a project. Sound Forge is built for a pass that starts and ends with one audio file: inspect it, process the waveform, check loudness and peaks, then export. REAPER has serious delivery tools too. Its [render features](https://www.reaper.fm/about.php) include loudness normalization, true-peak limiting, dither and loudness reports, and the [7.81 User Guide’s output-format table](https://www.reaper.fm/userguide/ReaperUserGuide781c.pdf#page=415) explicitly lists DDP. Those are documented capabilities; this comparison didn't test a replication-ready DDP package. When keeping the connection to the multitrack mix comes first, keep mastering inside REAPER. Batch work isn't exclusive to Sound Forge. REAPER has a batch file converter and queued renders, and Sound Forge has its own batch-processing workspace. Compare the operations you actually repeat (naming files, applying a chain, checking results, exporting variants) instead of assuming a DAW needs a new arrangement for every file. ## What REAPER Does That Sound Forge Pro Doesn't For a band session, REAPER keeps drums, bass, guitars and vocals on separate tracks, with takes, routing, automation and later mix revisions. Sound Forge can record and edit a file with up to 32 channels, but that's a different thing from arranging and mixing a DAW project. Its non-destructive event mode doesn't bring REAPER’s multitrack session structure with it. Sound Forge isn't a MIDI sequencer. REAPER supports MIDI editing, routing and instrument plug-ins, which makes it the pick for arranging a song with MIDI parts. Its included basic synthesizer and sampler won't pass for a large orchestral or drum library, so budget separately for any instruments your production needs. REAPER is non-destructive by design: cuts, fades, gain changes and plug-in decisions live in the project until render. Sound Forge still defaults to direct destructive processing, so saving over a source file commits those changes. That said, [Sound Forge 2026 also includes an event-based mode](https://www.soundforge.com/sound-forge/pricing/) that Boris FX describes as completely non-destructive. It helps with file-level revisions, but Sound Forge still doesn't become a multitrack DAW with REAPER's routing, arrangement and project recall. REAPER can combine actions into custom commands and extend its behavior through scripts and plug-ins. [ReaScript](https://www.reaper.fm/sdk/reascript/reascript.php) supports embedded EEL2 and Lua; Python needs a separate installation. Sound Forge supports scripting and batch operations as well. Decide by the automation you need, since neither application is simply the customizable one. [REAPER builds](https://www.reaper.fm/download.php) are available for Windows, macOS and Linux. The current [Sound Forge requirements](https://www.soundforge.com/sound-forge/system-requirements/) list Windows 11\. For a current native application on macOS or Linux, REAPER is the option between these two. ## Licenses, Trials and the Price Difference As checked October 9, 2026, [Cockos lists one REAPER edition](https://www.reaper.fm/purchase.php) at $60 for qualifying discounted use or $225 for a commercial license. Both licenses include updates through REAPER 8.99, and the current download is REAPER 7.82\. [Boris FX's 2026 launch pricing](https://blog.borisfx.com/press/boris-fx-acquires-vegas-pro-sound-forge-and-acid-pro) lists Sound Forge at $299.95 perpetual, $24.95 monthly or $149.95 annually. Taxes, regional pricing and promotions can change the checkout total, so verify both official pages before buying. The [$60 license conditions](https://www.reaper.fm/purchase.php) include an individual’s personal-only use, commercial use by an individual or business with yearly gross revenue no higher than US $20,000, or an educational/non-profit organization. A professional can qualify; this is not a reduced-feature amateur edition. If you need the $225 license, the gap against the $299.95 Sound Forge launch price is $74.95 before tax, not $240. Compare the price you actually qualify for, including tax and any instruments or restoration plug-ins you plan to add. The Sound Forge figures above are historical launch prices, not a checkout verified today. An existing Sound Forge license also changes the decision: keeping a tool you already own need not involve another purchase. For a new studio, REAPER is the rational first purchase when recording and mixing are the immediate jobs. Add Sound Forge later only if direct waveform repair, batch file work or a dedicated file-mastering workflow saves enough time to justify a second application. ## Using Both Together: The Case for the Combination A combined workflow can work well: record and mix in REAPER, then send a copy of a file to Sound Forge only when a specific repair or finishing task calls for it. An [older REAPER community discussion](https://www.reddit.com/r/Reaper/comments/ly0aw4/does%5Fanyone%5Fhere%5Fuse%5Freaper%5Fas%5Fa%5Fcomplete/) describes both approaches, keeping an external editor and staying inside REAPER with actions and plug-ins. Those reports describe preferences. They aren't a controlled comparison of the current versions. The combination makes the most sense when multitrack production and archival file repair happen in the same job. REAPER keeps the session; Sound Forge handles the transfer or damaged file in a waveform-first workspace. Both applications read and write PCM WAV, so a handoff doesn't require a lossy conversion. Keep the project sample rate and choose suitable PCM or floating-point intermediate precision supported by both setups. Avoid lossy MP3 intermediates. A 24-bit PCM WAV is one compatible handoff option. If more processing follows, a supported floating-point WAV can avoid another integer quantization; plan final dither and delivery depth separately. Keep that rendered file separate from the original mix, perform the repair or master in Sound Forge, and export a new delivery file. The [vinyl restoration guide](https://soundforgepro.com/sound-forge-pro-for-vinyl-restoration/) covers capture, click repair, noise reduction and verification when the source is a record transfer. ### Open a copy in an external editor The [REAPER 7.81 guide, section 7.1](https://www.reaper.fm/userguide/ReaperUserGuide781c.pdf#page=123) documents direct external-editor integration. In REAPER, open **Options → Preferences → External Editors**, add Sound Forge and select its installed executable. Right-click the audio item, open the external-editor submenu and choose the option to edit a **copy**. Save that copy in Sound Forge, close the editor and return to REAPER. The guide describes the copy being inserted into the track. Verify that the revised audio is the take you intend to use before continuing. This route edits the item’s audio. A finished master of all tracks is a different job, so use a render when you want the mix bus and its effects included. Never overwrite your only source recording while experimenting. ## Which One First? Start with the next deliverable. Recording guitar and vocals into an arrangement points to REAPER. If an already recorded file needs repair, first check whether your existing editor can fix it. Sound Forge deserves a trial when its direct waveform tools solve a recurring problem. For music production (recording instruments or vocals, arranging, MIDI and mixing), start with REAPER. The qualifying $60 license covers the complete software, the [60-day evaluation is fully functional](https://www.reaper.fm/download.php), and the official user guide plus active forum give you a documented path through the deep configuration options. Add Sound Forge only when file-level repair or batch finishing becomes a recurring job. For stereo mastering or voice-over cleanup, neither application wins just because the source is one file. Try a representative recording in both. Compare the time needed to locate a defect, apply the right processing, revise the result and export the required format. The [Sound Forge review](https://soundforgepro.com/sound-forge-pro-review-2026/) explains the dedicated editor’s strengths and limits. If you can buy only one application for a band or a music-production session, REAPER covers recording through delivery. Add Sound Forge only for a concrete advantage in your own file-editing work. You don't need a second application to make a professional master. ## Frequently Asked Questions ### Is Sound Forge Pro better than REAPER for mastering? Not inherently. Both can process and deliver a finished stereo file. Sound Forge offers direct waveform repair and a file-focused workspace; REAPER offers master effects, loudness normalization, true-peak limiting, dither and render reports. Choose based on the repair and revision workflow you need, not a presumed difference in sound quality. ### Can REAPER replace Sound Forge Pro for audio restoration? For some jobs, yes. REAPER offers ReaFIR, spectral edits and other effects, with optional third-party restoration tools. Sound Forge’s built-in sample-pencil and repair commands may be more convenient for isolated waveform defects. Try the actual damaged material; a feature list cannot predict the quality of a repair. ### Can Sound Forge Pro replace REAPER for recording sessions? Sound Forge can capture multichannel audio, but it does not replace REAPER’s DAW arrangement, MIDI sequencing, track routing and mix recall. Choose REAPER for a production built from separate editable tracks. Sound Forge remains suitable for file-based capture, including narration or a stereo feed from a mixer. ### What is the price difference between Sound Forge Pro and REAPER? As checked October 9, 2026, REAPER costs $60 for qualifying discounted users or $225 commercial; both licenses unlock the same software and include updates through 8.99\. REAPER's trial is fully functional for 60 days. Sound Forge was listed at $299.95 perpetual or $24.95 monthly in the Boris FX 2026 launch pricing, [with a 15-day trial](https://www.soundforge.com/sound-forge/pricing/). Taxes, regions and promotions can change the checkout total. ### Can I use Sound Forge Pro and REAPER together? Yes. You can render a compatible WAV mix or stem, or configure Sound Forge as an external editor in REAPER. Use a copy for destructive edits and retain the project and original media. A second editor is optional, not required for mastering or export. ### Does REAPER run on Mac while Sound Forge Pro doesn't? Yes. [Current REAPER 7.82 builds](https://www.reaper.fm/download.php) are available for Windows, macOS and Linux. Sound Forge 2026 is a Windows application and its current requirements list Windows 11\. On macOS or Linux, REAPER is the only current option of these two. If you need the DAW route, compare this decision with the [music-production workflow](https://soundforgepro.com/sound-forge-pro-for-music-production/). If the work begins with finished files, use the [Sound Forge beginner tutorial](https://soundforgepro.com/how-to-use-sound-forge-tutorial/) and the [file-mastering workflow](https://soundforgepro.com/how-to-master-a-track-in-sound-forge-pro/). For a broader shortlist, continue to the [current Sound Forge alternatives](https://soundforgepro.com/best-sound-forge-alternatives/). *Fact-checked September 12, 2026 against the current Boris FX Sound Forge feature matrix. Rechecked October 9, 2026 against the REAPER 7.82 release notes, Cockos licensing, the REAPER 7.81 User Guide and the Boris FX 2026 launch pricing.* ### Sound Forge Pro Keyboard Shortcuts: Essential 2026 List URL: https://soundforgepro.com/sound-forge-pro-keyboard-shortcuts/ Last updated: 2026-09-27T09:44:52.000Z This guide covers the Sound Forge Pro 2026 default-map commands that matter in day-to-day editing: playback, recording, cursor movement, sample-accurate selection, zoom, markers, snapping, windows and the Plug-In Chain. Every combination below was checked against the current [Boris FX Keyboard Shortcuts reference](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/keyboard%5Fshortcuts.htm), last modified June 9, 2026. Your installation can differ if you imported or edited a keyboard map. Open **Help → Keyboard Shortcuts** inside Sound Forge to see the documented defaults, or **Options → Customize Keyboard** to inspect the active assignments. A shortcut only works in the window that receives it: Ctrl+R records in the waveform context but runs a script when the Script Editor has focus. Use Alt+0 to return focus to the waveform. [![Ctrl+B, Ctrl+T and Ctrl+S actions in the waveform versus the Plug-In Chain](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/09/shortcut-window-focus-20260912.webp)](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/09/shortcut-window-focus-20260912.webp) The focused window determines whether the keys edit audio or control the Plug-In Chain. [Open the full-size shortcut map](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/09/shortcut-window-focus-20260912.webp). ## The 20 shortcuts worth learning first | Shortcut | Action | | ------------------------ | -------------------------------------------------------------- | | Space or F12 | Play or stop in the default mode | | Enter or Ctrl+F12 | Play/pause | | Ctrl+R | Start/stop recording | | M | Place a marker at the cursor | | R | Create a region from the selection; Event tool uses Ctrl+Alt+R | | Ctrl+A | Select all data | | Ctrl+C / Ctrl+X / Ctrl+V | Copy / cut / paste | | Delete | Clear selected data, unless Treat as Cutlist is enabled | | Ctrl+T | Trim/crop to the current selection | | Ctrl+M | Mix clipboard data with the active window | | Ctrl+E | Paste clipboard data into a new window | | Ctrl+Z / Ctrl+Shift+Z | Undo / redo | | Ctrl+Home / Ctrl+End | Beginning / end of file | | Ctrl+Alt+←/→ | Move one sample | | ↑/↓ | Zoom in / out horizontally | | Ctrl+↑ | Zoom to selection; Zoom In Full if none | | Ctrl+↓ | Return to the normal zoom ratio | | Z / Shift+Z | Snap selection / active edge to the next zero crossing | | Ctrl+B | Toggle auto snap to zero crossings | | Ctrl+Alt+0 | Open/focus the Plug-In Chain | ## Playback, transport and recording | Shortcut | Action | | ------------------------ | ------------------------------------------------------ | | Space or F12 | Play or stop in the default mode | | Shift+Space or Shift+F12 | Play All | | Enter or Ctrl+F12 | Play/pause | | Esc | Stop playback or cancel the current action | | Ctrl+Shift+A | Arm for recording | | Ctrl+R | Start/stop recording | | Q | Toggle looped playback | | X | Cycle Normal, Play as Sample and Play as Cutlist modes | | J, K, L | Scrub playback | | F | Seek the cursor during playback | | Ctrl+K | Preview cut with pre-roll | | Ctrl+Shift+K | Play to cursor with pre-roll | | F6 / Shift+F6 | Toggle playback scrolling / smooth scrolling | The [scrubbing instructions](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/scrubcontrol.htm) explain the direction: J plays in reverse, K pauses and L plays forward. Pressing J or L repeatedly speeds playback up, and the Editing preferences set the speed range. X cycles Normal, Play as Sample and Play as Cutlist; it has nothing to do with Plug-In Chainer modes. ## Editing and clipboard commands | Shortcut | Action | | ------------ | ------------------------------------------------------------------------------- | | Ctrl+A | Select all sound data | | Ctrl+C | Copy selection | | Ctrl+X | Cut selection | | Ctrl+V | Paste into the active window | | Ctrl+E | Paste into a new data window | | Ctrl+M | Mix clipboard data with the active window | | Delete | Clear selection without copying; Treat as Cutlist instead adds a cutlist region | | Ctrl+T | Trim/crop to selection | | Ctrl+Y | Repeat the last process, effect or tool | | Ctrl+Z | Undo | | Ctrl+Shift+Z | Redo | | Ctrl+D | Select the normal edit tool | | D / Shift+D | Previous / next editing tool in the documented default map | | S | Split event at cursor when Event tool is selected | | Ctrl+Alt+T | Split selected events at region boundaries | Ctrl+T is destructive in the main data window: everything outside the selection gets removed. In the focused Plug-In Chain, the same keys change tail-data handling. Always check which window has focus. ## Cursor movement and sample accuracy | Shortcut | Action | | ----------------------------- | ---------------------------------------------------------------------- | | ←/→ | Move one screen pixel | | Ctrl+←/→ | Beginning/end of file or previous/next marker, region or loop boundary | | Ctrl+Alt+←/→ | Move one sample | | Alt+←/→ | Move one video frame when video is present | | Home / End | First/last visible sample or selection boundary | | Ctrl+Home / Ctrl+End | First/last sample in the file | | Page Up / Page Down | Move 10% of the current view | | Ctrl+Page Up / Ctrl+Page Down | Move 100% of the current view | | \\ or . | Center the cursor in the waveform | | Num + / Num − | Next / previous sample | | Ctrl+Num + / Ctrl+Num − | Move 10 samples forward / backward | | Ctrl+G | Open Go To | ## Selection and zero crossings | Shortcut | Action | | ----------------------------------- | -------------------------------------------------------- | | Ctrl+Shift+D | Open Set Selection | | Shift+←/→ | Extend by one pixel | | Ctrl+Alt+Shift+←/→ | Extend by one sample | | Ctrl+Shift+Home / Ctrl+Shift+End | Extend to file start / end | | Shift+Num + / Shift+Num − | Extend to next / previous sample | | Ctrl+Shift+Num + / Ctrl+Shift+Num − | Extend 10 samples forward / backward | | Z | Snap selection to the next zero crossing | | Shift+Z | Snap the active selection edge to the next zero crossing | | Tab / Shift+Tab | Move selection through channels in a multichannel file | | < / \> | Shift selection left / right by its length | | ; / ' | Halve / double selection length | | Backspace | Restore one of the previous five time selections | ## Zoom and saved views | Shortcut | Action | | ------------------ | ------------------------------------------------ | | ↑/↓ or mouse wheel | Increase / decrease time magnification | | Shift+↑/↓ | Increase / decrease level magnification | | Ctrl+↑ | Zoom to selection; Zoom In Full when none exists | | Ctrl+↓ | Return to normal zoom | | Num 1 / Num 2 | Display custom zoom ratio 1 / 2 | | Ctrl+Shift+1–8 | Save current view in a numbered cell | | Ctrl+1–8 | Restore a saved view | | Num 5 | Move cursor to the opposite end of a selection | ## Markers, regions, loops and snapping | Shortcut | Action | | -------------- | -------------------------------------------------------------- | | M | Place a marker at the cursor | | R | Create a region from the selection; Event tool uses Ctrl+Alt+R | | Ctrl+Alt+R | Place a region when Event tool is selected | | 0–9 number row | Jump to corresponding marker or select corresponding region | | Alt+L | Create a sample loop from the selection | | Alt+Shift+L | Edit the sample loop in the Sampler Loops window | | F8 | Enable/disable snapping | | Ctrl+F8 | Toggle auto snap to grid | | Shift+F8 | Toggle auto snap to markers | | Ctrl+Shift+F8 | Toggle auto snap to event edges | | Ctrl+B | Toggle auto snap to zero crossings | The shortcut reference gives conflicting window notes for Alt+L and Alt+Shift+L. The rows above follow the dedicated [sample-loop procedure](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/proonly/edit%5Fsample.htm): create the loop first, then open its settings. Confirm custom-map assignments if your installation behaves differently. ## Window and panel shortcuts | Shortcut | Window | | -------------------------- | ----------------------------------------- | | Alt+0 | Waveform display | | Alt+1 | Explorer | | Alt+2 | File Properties window | | Alt+3 | Video Preview | | Alt+4 | Time Display | | Alt+5 | Channel Meters | | Alt+6 | Loudness Meters | | Alt+8 | Undo/Redo History | | Alt+9 | Spectrum Analysis | | Ctrl+Alt+0 | Plug-In Chain | | Ctrl+Alt+1 | Plug-In Manager | | Ctrl+Alt+3 | Script Editor | | Ctrl+Alt+5 | Record Options | | Ctrl+Alt+6 | Instant Actions | | Ctrl+F6 / Ctrl+Shift+F6 | Next / previous data window | | F11 / Shift+F11 / Ctrl+F11 | Toggle bottom / side / all docked windows | | Ctrl+Alt+7 | Remote Record | | Ctrl+Alt+M, then 0 | Regions List | Alt+Enter displays File Properties; Alt+2 shows or focuses its window. The two commands are related, but they work in different contexts. ## Plug-In Chain shortcuts These work when the Plug-In Chain has focus. Current Sound Forge applies the real-time chain when the file is saved, and the 2026 shortcut table no longer lists the old Ctrl+P Preview or Ctrl+Shift+P Process commands. | Shortcut | Action | | ------------ | -------------------------------------------- | | Ctrl+B | Bypass selected plug-in | | Ctrl+Shift+B | Bypass entire chain | | Ctrl+S | Save chain preset | | Ctrl+T | Cycle Ignore/Mix/Insert Tail Data options | | Ctrl+E | Add plug-ins | | Ctrl+Delete | Remove selected plug-ins | | ↓/↑ | Select next / previous plug-in | | Ctrl+D | Show plug-in window | | Ctrl+H | Show/hide effect automation parameters | | Shift+D | Show/hide envelope in the data window | | Shift+E | Enable/disable envelope | | Ctrl+A | Select all plug-ins or automation parameters | The current [Plug-In Chain help](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/proonly/plug-in%5Fchainer.htm) explains the save-time application model and the difference between the real-time window and FX Plug-Ins → Apply Plug-In Chain for a selection. ## Project and file commands | Shortcut | Action | | ------------ | ---------------------------------------------- | | Ctrl+N | Create a new data window | | Ctrl+Shift+N | Create a new window without showing New Window | | Ctrl+O | Open a sound file or project | | Ctrl+S | Save modified sound data | | Alt+Enter | Display File Properties | | Ctrl+W | Close active data window | | Alt+F4 | Exit Sound Forge Pro | Ctrl+Shift+S and Ctrl+P are familiar Windows conventions, but the current Sound Forge 2026 reference doesn't list them as default project-file shortcuts. Check your active map before you rely on them. ## When a shortcut does nothing—or the wrong thing Finish or deliberately cancel any open dialog, then put focus back on the intended window. If a text field has focus, click outside it or use the right window-focus shortcut. In the waveform, Ctrl+B toggles zero-crossing snapping; in the Plug-In Chain it bypasses a plug-in. In the same way, Ctrl+S in the chain saves a preset and leaves the audio file untouched. Stop and check focus before you retry a destructive edit. If the command still behaves differently, inspect its assignment in **Options → Customize Keyboard**. Number-row keys and numeric-keypad keys are listed separately in this guide; on a laptop without a numeric keypad, use the listed arrow-key alternatives for single-sample movement. For punctuation shortcuts, check which key the Shortcut keys box actually receives on your keyboard layout. Back up a custom map before you reset it. ## Customize and back up a keyboard map 1. Choose **Options → Customize Keyboard**. 2. Select the command category and command. 3. Click the Shortcut keys box and press the new combination. 4. Click **Add** to assign it. 5. Choose **Save as** and name the map. Sound Forge 2026 stores custom map `.ini` files under `C:\Users\[user]\AppData\Roaming\BorisFX\Sound Forge Pro\2026.0\`. Back up the current map before importing another. Copy the INI file into that folder, restart Sound Forge, then select the imported entry in Keyboard map and confirm it. To restore defaults, choose **\[Default\]** in Keyboard map and click OK. These current paths and button names come from the [Customize Keyboard documentation](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/proonly/customizing%5Fkeyboard%5Fshortcuts.htm). ## Frequently Asked Questions ### Where can I see the active shortcuts in Sound Forge Pro? Choose Help → Keyboard Shortcuts. That reference reflects the default 2026 map; Options → Customize Keyboard shows assignments in your current map. ### What is the Sound Forge recording shortcut? Ctrl+R starts or stops recording. Ctrl+Shift+A arms for recording, and Esc stops or cancels the current action. ### What does M do in Sound Forge Pro? M inserts a marker when the appropriate Sound Forge waveform context receives the key. If another window or text field has focus, do not assume M reached the editor. During recording, the Remote Record window also provides a Set markers button. ### How do I move exactly one sample? Use Ctrl+Alt+Left Arrow or Ctrl+Alt+Right Arrow. Numeric keypad minus and plus also move to the previous or next sample. ### How do I snap an edit to a zero crossing? Press Z to snap the selection to the next zero crossing or Shift+Z to snap its active edge. Ctrl+B toggles automatic zero-crossing snapping. ### What opens the Plug-In Chain? Ctrl+Alt+0 opens or focuses the Plug-In Chain. Once it has focus, Ctrl+B bypasses the selected plug-in and Ctrl+Shift+B bypasses the full chain. ### Can I export and share custom shortcuts? Yes. Save a map from Options → Customize Keyboard. It is stored as an INI file in the current version’s BorisFX Sound Forge Pro AppData folder and can be copied to the same folder on another installation. Restart Sound Forge, select that map in Customize Keyboard and confirm; copying the file alone does not make it active. For related editing tasks, start with the [Core Editing hub](https://soundforgepro.com/tag/core-editing/). Put the map to work in the two workflows where focus mistakes matter most: the [Cut/Trim guide](https://soundforgepro.com/how-to-cut-and-trim-audio-in-sound-forge-pro/) explains destructive data-window shortcuts, while the [Plug-In Chain guide](https://soundforgepro.com/how-to-use-plug-in-chainer-sound-forge-pro/) covers the same key combinations when the effects window has focus. *Documentation reviewed: September 12, 2026 against the Boris FX Sound Forge Pro 2026 Keyboard Shortcuts, Customize Keyboard and Plug-In Chain documentation.* ### How to Use WaveColor in Sound Forge Pro URL: https://soundforgepro.com/how-to-use-wavecolor-in-sound-forge-pro/ Last updated: 2026-10-09T21:55:28.000Z WaveColor is a waveform display mode in Sound Forge Pro. In its default color view, hue gives a broad pitch cue: red for lower tones, green for the middle range, and blue for higher tones. Vivid color indicates more tonal or harmonic material; washed-out color indicates more noise-like material. WaveColor does not measure loudness, identify an exact frequency, or repair the file. *Part of the [Sound Forge restoration hub](https://soundforgepro.com/tag/sound-forge-restoration-guides/). New to the editor? Start with the [complete Sound Forge 2026 guide](https://soundforgepro.com/).* Its best use is navigation. A long file can reveal a change in pitch range, a noisy section, applause between live tracks, [wind noise](https://soundforgepro.com/reduce-wind-noise-voice-recording-sound-forge/), or low-frequency vinyl rumble before you open a detailed analyzer. A color change is a clue worth inspecting; it isn’t a diagnosis. ![The same passage in Sound Forge as a plain waveform and with WaveColor showing pitch as hue](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/10/wavecolor-ui-frequency-view-v2-1-v20261005-v20261006.webp) WaveColor in Sound Forge: enable the view, then read hue as pitch rather than loudness. ## How to Turn WaveColor On and Off in Sound Forge Pro 2026 Open an audio file and click **Toggle Wave Coloring** in its **Data Window playbar**. The [Data Windows help](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/data%5Fwindows.htm) identifies the on/off button there. Click it again to restore the ordinary waveform. This changes the view, not the audio. Installed interfaces can differ, so follow the documented controls described here. If that button is hard to find, the [Tools toolbar](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/proonly/the%5Ftools%5Ftoolbar.htm) also has an Activate WaveColor control. Don't mix it up with the separate Vocal Activity Display button. WaveColor is part of the waveform view and won't open a frequency-analyzer window. Use the colored view for a fast scan, then switch back whenever the ordinary waveform makes an edit easier to judge. Because WaveColor changes only the display, toggling it is safe before, during, or after an edit. MAGIX introduced WaveColor in [Sound Forge Pro 14 in March 2020](https://www.magix.info/de/forum/release-sound-forge-pro-14-and-sound-forge-pro-14-suite--1239898/). The instructions here follow the current 2026 help, so an older tutorial may show a different layout. ## What the WaveColor Colors Actually Mean The [Wave Coloring help](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/wavecoloring.htm) separates pitch from sound character. In the default preset, follow the hue to compare lower and higher-pitched passages; follow saturation to compare harmonic and noise-like material. If your waveform is black and white, check the preset before applying the red/green/blue legend. The colors are broad categories rather than a calibrated frequency scale. Red doesn’t stand for one fixed Hz value, and blue doesn’t stand for another. WaveColor helps you compare regions across a file; Spectrum Analysis is the tool for a frequency readout and level measurement. Saturation has nothing to do with volume. Waveform height depends on display zoom too, so use level meters or [Statistics for numerical amplitude checks](https://soundforgepro.com/how-to-use-statistics-sound-forge-pro/), and a [loudness meter](https://soundforgepro.com/sound-forge-loudness-meters/) for a delivery loudness target. A pale waveform and a vivid one tell you equally little about whether a file meets a LUFS requirement. ## How to Read WaveColor Without Guessing Start by getting a local baseline. Look at a section that sounds normal and notice its hue and saturation, then scan for sustained changes or short interruptions. Compare each suspect region with the audio just before and after it, because a change of color may be a real edit point, a new instrument, applause, noise or an actual defect. 1. **Enable the view.** Open the file and click Toggle Wave Coloring in its Data Window playbar. 2. **Check the preset.** In the default color view, read hue as a broad pitch cue and saturation as tonal versus noise-like character. In a black-and-white preset, brightness represents only its named property. 3. **Compare neighboring audio.** Scan for a change, then listen across it and compare with the passage immediately before and after. 4. **Inspect the suspected problem.** For a tonal problem, select the passage, open View → Spectrum Analysis and click Refresh. For a possible click, listen and look at the waveform at close zoom; you don't have to take a spectrum measurement. 5. **Choose whether to repair.** Keep the bass, percussion and speech sounds you want. If you confirm damage, keep the original and repair a working copy, since WaveColor itself won't remove anything. A drum hit, a consonant, an edit or an instrument change can look odd simply because it differs from the audio around it. WaveColor doesn't label that interruption as a click. Listen before you remove it; the [click-and-pop repair guide](https://soundforgepro.com/how-to-remove-clicks-pops-sound-forge-pro/) covers the next step once you're sure the transient is unwanted. ## Three Jobs WaveColor Does Well 1\. Find boundaries in long recordings. The official help gives applause between tracks in a live recording as an example. A change in pitch and noise character can make those sections easier to find than a monochrome overview alone. **2\. Locate noise-like sections.** The help gives wind noise and bass-range vinyl rumble as examples. In the default view, a pale patch or a shift toward lower-pitched color is a reason to listen more closely. It doesn't prove a fault. Compare it with a normal-sounding section of the same recording. 3\. Triage before detailed analysis. WaveColor can tell you where the file changes. It can’t tell you whether a noise floor passes a specification, whether a peak is 280 Hz, or whether a click is real. Use it to choose the next section to inspect; approving delivery is a different job. ## WaveColor vs Spectrum Analysis Both tools describe spectral content, but they answer different questions. WaveColor asks, “Where does this file change?” Spectrum Analysis asks, “Which frequencies are present here, and at what level?” Spectrum Analysis examines a selected region in depth. It provides a frequency graph and numeric information for the content you are investigating. Use it to confirm a hum, resonance, rumble, or high-frequency problem that WaveColor helped you locate. The [Spectrum Analysis guide](https://soundforgepro.com/how-to-use-spectral-analysis-tool-sound-forge-pro/) explains the FFT controls and snapshots. Pick the next check based on the suspected problem. A tonal hum calls for a representative selection and Spectrum Analysis, while an isolated click may only need listening and a sample-level look. WaveColor helps you find the passage. Deciding which repair belongs there is still up to you. Mark the questionable passages during the scan so you can inspect them one by one. If listening and measurement confirm a tonal problem, continue with the [EQ workflow](https://soundforgepro.com/how-to-use-equalizer-sound-forge-pro/). For unwanted broadband noise, use the [noise-reduction workflow](https://soundforgepro.com/how-to-remove-background-noise-in-sound-forge-pro/). A naturally different instrument or a clean transition needs neither treatment. ## WaveColor Display Modes and Preferences Open Options → Preferences and the Wave Color settings if the default red/green/blue view isn't the clearest one for you. The [current Wave Color Preferences help](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/wave%20color%20preferences.htm) lists three presets: the default colorful two-dimensional view, Black White - Noise Factor, and Black White - Pitch. The two black-and-white modes show one property at a time: **Black White - Noise Factor** uses brightness for noisiness, and **Black White - Pitch** uses it for pitch. Try them if the combined color view is hard to read. The help gives no calibrated Hz or noise-level scale for either preset, so switching the display won't turn WaveColor into a numerical meter. **Color for Vocal Activity** sets the alternate color for the separate [Vocal Activity Detection display](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/proonly/vocal%5Factivity.htm). That feature estimates where spoken or sung voice is present, which is a different job from WaveColor’s pitch/noise display. Voice detection can take a while to appear because its separate analysis is CPU-intensive. If scrolling feels sluggish, compare the same file and zoom level with WaveColor on and off. That comparison helps diagnose the problem, but it won't prove WaveColor is to blame. For waveform scrolling, the [Display preferences](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/display%5Fpreferences.htm) also suggest setting Peak ratio default for new files below the current zoom ratio. Note the old setting so you can put it back if the change doesn't help. ## Frequently Asked Questions ### Where is the WaveColor control in Sound Forge Pro 2026? Open an audio file and click Toggle Wave Coloring in its Data Window playbar. Click the same button again to return to the ordinary waveform. The Tools toolbar also provides an Activate WaveColor control. ### What do the WaveColor colors mean in Sound Forge Pro? In the default color preset, red indicates lower pitch, green the middle range, and blue higher pitch. Tonal or harmonic material is more saturated; noise-like material is less saturated. Saturation is not loudness. The black-and-white presets instead use brightness for the selected property. ### Can WaveColor identify clicks and pops automatically? No. A click may look different from nearby audio, but WaveColor does not classify defects or mark them as clicks. Treat a color change as a place to inspect, then listen, zoom in, and use the dedicated click-repair tools only after confirming the problem. ### Does WaveColor affect audio quality in Sound Forge Pro? No. WaveColor changes only the waveform display. It does not process samples, change an effects chain, or alter the rendered file. ### Can WaveColor show an exact frequency in hertz? No. The default color preset gives a broad low-to-high pitch cue, but WaveColor has no hertz scale. Use Spectrum Analysis when you need the frequency and level of a peak. ### Can I change the WaveColor display? Yes. Wave Color Preferences offers the default two-dimensional color view plus Black White - Noise Factor and Black White - Pitch presets. It also includes a separate color setting for detected vocal activity. Last fact-checked: September 8, 2026 against the current Sound Forge 2026 Data Windows, Wave Coloring, Tools Toolbar, Wave Color Preferences, Vocal Activity Detection, Display Preferences, and Spectrum Graph documentation. Menu instructions were checked against that documentation. ### Sound Forge Pro for Voice-Over Recording URL: https://soundforgepro.com/sound-forge-pro-for-voice-over-recording/ Last updated: 2026-10-09T21:04:13.000Z Sound Forge Pro 2026 is a strong voice-over editor when the job centers on one narration file: record, punch in a correction, clean the take, measure it, and export. It can also record multiple input channels, but it is not a multitrack DAW with separate timeline tracks and a mixer. That distinction matters more than any generic “professional” label. For a broader orientation, use the [Sound Forge Pro 2026 guide](https://soundforgepro.com/); for other task-specific setups, open the [workflows hub](https://soundforgepro.com/tag/workflows/). Quick answer: use File → New to create a mono file for one microphone, with the sample rate required by the job and 24-bit capture only if your device supplies it. Choose the interface and input under Options → Preferences → Audio, open View → Record Options, choose Manual, test the loudest line, and press Ctrl+R to record. Arm is optional for ordinary recording but starts the prerecord buffer when that feature is enabled. Edit a copy, save the processed result, and verify the delivery file. [![Voice-over copy, selected retake boundaries, whole-file RMS and separate room-tone measurement](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/09/voice-over-workflow-20260912.webp)](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/09/voice-over-workflow-20260912.webp) Keep the original, retake the selected range, then inspect the saved file and representative room tone separately. [Open the full-size workflow](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/09/voice-over-workflow-20260912.webp). ## Where Sound Forge Fits in a Voice-Over Workflow For one narrator, Sound Forge keeps the work close to the file: the waveform, Record Options, regions, plug-in chain, Statistics, and export are available without building a DAW session. That is useful for commercials, e-learning, podcast inserts, auditions, and audiobook chapters. Don’t confuse multichannel recording with multitrack production. The [current multichannel recording help](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/recording%5Fmultichannel%5Faudio.htm) confirms that Sound Forge can capture several hardware inputs into a multichannel data window. It also states that Sound Forge is not a multitrack editor. Use a DAW when each speaker needs an independent timeline track, routing, automation, or later mix revisions. For long-form narration, work chapter by chapter and keep an untouched source plus a processed copy. That avoids turning one large destructive edit history into a single point of failure and matches ACX's requirement for one chapter or section per delivery file. ## Audio Device Setup: ASIO Driver and Input Configuration Before recording anything, set up the audio device correctly in Sound Forge Pro. The driver choice affects latency during monitoring (the gap between speaking and hearing yourself in your headphones), and that matters for VO because performers need to monitor naturally without delay. Go to Options → Preferences → Audio. Under Audio Device Type, choose the manufacturer’s ASIO driver when the interface provides one; the [Audio preferences help](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/audio%5Fpreferences.htm) describes ASIO as the low-latency option. Test monitoring with your actual driver, buffer and sample rate; a driver label alone does not establish the delay you will hear. Set the buffer low enough for comfortable monitoring and raise it only if you hear gaps or glitches. Direct hardware monitoring, when the interface offers it, avoids a software round trip. If no native ASIO driver exists, test the Windows driver first. A generic wrapper can help some devices, but it adds another configuration layer and doesn't guarantee lower latency or lower noise. Confirm the input in the Record tab, click Apply, Arm the device, and check for a moving meter before recording the take. On the Audio preference page, open the Record tab and assign the interface input to the data-window channel. For one microphone, create a mono file unless the client explicitly requires stereo. A stereo file isn't automatically two identical channels; the result depends on routing, so verify the meter and a short test recording instead of assuming. ## Recording Levels: Where to Set Your Gain For unpredictable speech, peaks around −12 to −6 dBFS are a conservative editorial starting range, not a platform rule. Read the loudest line during setup and leave more margin if the performance becomes louder or more animated. Capture margin helps accommodate an unexpectedly loud line, but no initial peak guarantees that later processing will stay below full scale. A simple 2 dB gain increase takes a −3 dBFS sample peak to −1 dBFS, not clipping. An EQ band boost affects peaks differently because it changes frequency balance and phase. Measure after EQ, compression and de-essing, and reduce output gain when needed. Set the interface or microphone’s input gain before the analog-to-digital conversion where the device provides that control. It may be a physical knob or a manufacturer’s software control. Sound Forge’s meter shows the arriving digital signal; turning down a recorded file cannot prevent an overloaded input stage. Inspect the test waveform and listen: analog distortion can remain even when the digital meter never reaches zero. Record a loud and a quiet line before the real take. Listen for noise, [room reflections](https://soundforgepro.com/remove-echo-from-audio/), plosives, cable faults and clipping. A clean test file is more useful than chasing a fixed meter number. Lowering a clipped recording afterwards does not reconstruct the missing peaks. ## The Record Dialog: Key Settings for Voice-Over Open View → Record Options. The [current Sound Forge Pro 2026 Record Options help](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/recording%5Foptions.htm) documents the voice-over path directly: Manual is the general-purpose and punch-in method, while Normal, Create regions, and Create new windows control what happens after a stop or restart. Choose Manual for normal narration and punch-ins. Automatic: Threshold is for sound-triggered capture; Automatic: Time and MIDI Timecode serve scheduled or synchronized jobs. Manual gives the narrator deliberate control and is the method the current help names for voice-over. For a punch-in, use enough pre-roll to hear the previous phrase and match pace and tone. Configure pre-roll, post-roll, and the prerecord buffer from the Record Options Settings control. The right duration depends on the sentence and performer; 2–5 seconds is a practical starting range rather than a requirement. A prerecord buffer retains input after Arm, before you press Record. Enable it under Record Options → Settings and make a disposable test. After recording, choose the Event Tool and slip or trim the recorded event’s left edge to expose the retained buffer; it is not displayed automatically. Confirm the recovered lead-in before relying on it for a session. Normal lets you stop or pause recording. Create regions marks a new region whenever recording restarts or resumes; it does not create independent timeline tracks. Create new windows opens a separate window on restart and disables punch-in recording. If you enable Monitor Input through Plug-In Chain, those effects change monitoring, not the audio being recorded. ## Use Remote Record to Keep the Script Visible [Sound Forge Pro 2026 still documents Remote Record](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/remote%20aufnahme.htm). Open it with the Remote Record button on the Transport toolbar: it hides the main Sound Forge window and leaves the recording controls, peak meter, status, file selector, monitoring and a Set markers control visible. That is the cleanest built-in layout when the script needs most of the screen; View → Record Options remains the place to configure the method, mode and input behavior. If Remote Record does not suit the session, use a second monitor, Windows Snap, or a narrow script window beside Sound Forge. Keep the input meter visible and test keyboard focus before the take; a shortcut sent to the PDF or browser instead of Sound Forge can lose a recording cue. The goal is simple: the script remains readable while record status and peaks remain visible. Use the layout your hardware actually supports and save it as a Sound Forge workspace only after a short test take confirms focus, monitoring, and input routing. ## Marking Mistakes While Recording: The M Key During recording, use Set markers in Remote Record to flag a stumble, mispronunciation, cough or section that needs a retake without stopping the take. The standard Insert Marker shortcut is M, but keyboard focus can change what receives it, so confirm M in a disposable recording before relying on it during a session. The workflow: record a full pass without stopping. At each stumble, misread or cough, click Set markers—or press M only after that shortcut passed the focus test. At the end of the session, confirm that every intended marker exists, open View → Regions List, move through the marked points and zoom in for each retake. This keeps the performance moving and gives the editor a visible correction map. It doesn't remove the retake work: each marker still needs a precise edit, a matched replacement, and a listen across both boundaries. After the test, choose one marking method and use it consistently. A short note alongside the script can identify why a marker needs attention, such as a pronunciation correction rather than a whole-sentence retake. ## Punch-In Recording for Retakes Punch-in records over a specific section of an existing recording without affecting the rest of the file. In SF Pro, place the cursor at the start of the section to replace, or select the region to overwrite. Set Method to Manual and turn Loop Playback off for a single take. Select the exact range when the correction must stop at a defined point; the 2026 help states that recording stops automatically at the end of a selection. Without a selection, recording overwrites from the cursor until you stop. Keep the original file so every punch-in is recoverable after the session closes. Match microphone distance, angle, gain, room, and performance before the punch. Listen across both edit boundaries before processing. Don’t use noise reduction to hide a mismatched retake by default; re-recording under the same conditions is usually cleaner than forcing two different rooms to match. ## EQ for Voice-Over: The Specific Moves Start with the [current Modern Equalizer](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/modern%20equalizer.htm) as a VST effect when you want its analyzer and adjustable bands. Paragraphic EQ is another option through Process → EQ; use the controls documented for the effect you choose. Before reaching for EQ at all, fix the recording and microphone position. From there, make the smallest change that improves intelligibility at a matched output level. Use a high-pass filter only when there is unwanted low-frequency energy. Move the cutoff upward while previewing and stop before the voice loses body. There's no universal 80, 100, or 120 Hz setting, and microphone type alone doesn't determine the correct cutoff. If the low end is already clean, leave it alone. A filter applied to every file by habit can thin voices, remove useful chest resonance, and make chapter-to-chapter consistency harder to maintain. For boxiness or resonance, listen first, then use Spectrum Analysis and a temporary narrow sweep to confirm the frequency. Cut gently and choose a bandwidth that removes the resonance without thinning nearby wanted notes; a narrow ring does not always need a wider cut. A graph peak isn't automatically a defect, and 200–400 Hz isn't a preset for every room or voice. A broad presence boost can improve intelligibility, but it can also exaggerate [sibilance](https://soundforgepro.com/reduce-sibilance-sound-forge/), mouth noise, and fatigue. Compare on headphones, small speakers, and the client's reference. Skip the boost when articulation is already clear. An air shelf is optional. Use it only after de-essing and noise checks because it can lift hiss and mouth noise with the voice. Use the narrator’s recording to choose the curve; an example from another microphone or room is not a ready-made preset. ## De-essing: Controlling Sibilance Check the installed essentialFX plug-ins before buying a de-esser: the [current Sound Forge feature list](https://www.soundforge.com/sound-forge/pricing/) includes essentialFX, and that family has eFX DeEsser and VocalStrip. Availability still depends on the installation and license. A compatible VST2/VST3 de-esser is another option; Dynamic Equalizer can compress a selected frequency band. For a few isolated syllables, reducing their local gain may be enough. A static EQ cut reduces that band for the entire file, including non-sibilant words, so use it only for mild, consistent harshness. For changing sibilance, try a de-esser, gain automation or a compressing Dynamic EQ band. Enable Band Dynamics and set Frequency, Q and Threshold from the actual sibilant passages; compare non-sibilant words as well. Level-match the comparison so a quieter result isn't mistaken for a better one. The [Dynamic Equalizer help](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/proonly/dynamic%20equalizer.htm) documents Band Dynamics, Threshold, Ratio and Attack/Release. Its older Suite-only note conflicts with the current shared feature list, so confirm the installed effect and entitlement before buying an extra plug-in. [Mouth De-click](https://izotoperx.net/izotope-rx-mouth-de-click/) and de-essing solve different problems: one targets mouth transients, the other reduces sibilant energy. Old MAGIX bundles and current Boris FX packages aren't interchangeable, so confirm the plug-in license you actually own, then test it through the Plug-In Chainer before building a repeatable preset. Set the detector and reduction controls on the actual narrator, audition the difference signal if offered, and listen for softened consonants. Controls differ: the [MAGIX manual’s eFX DeEsser section](https://cdn.steamstatic.com/steam/apps/670450/manuals/ACLab%5FEN.pdf?t=1538761776) describes adaptive detection rather than an adjustable threshold. A saved preset is only a starting point when microphone position or performance changes. ## Editing Breaths and Room Tone Breath sounds between sentences divide opinion in VO production. Some clients want all breaths removed; others want natural breathing kept because breath removal makes recordings sound clinical. Know your client's preference before starting the editing pass. Reduce only [distracting breaths](https://soundforgepro.com/edit-breaths-sound-forge/). Select conservatively so the next consonant and the phrase timing remain intact. Lowering gain often sounds more natural than deletion. When a replacement is necessary, use [room tone](https://soundforgepro.com/room-tone-sound-forge/) from the same session rather than digital zero and cross-check both edit boundaries on headphones. Capture room tone at the start of every session without moving the microphone or changing gain. Keep a clean section for edits. For ACX delivery, ACX recommends 1–5 seconds of room tone at the beginning and end of each file and requires the spacing not to exceed five seconds; internal pauses still need natural timing rather than a fixed duration. Don’t batch-delete breaths across an audiobook. The risk is clipped phrasing, digital silence, and inconsistent pacing. [Keyboard shortcuts](https://soundforgepro.com/sound-forge-pro-keyboard-shortcuts/) can speed up reviewed edits, but listen across every cut in context to catch gaps or clicks. ## Save the Processed File and Check the Client’s Specification Agree on sample rate, bit depth, mono or stereo, naming, and raw versus processed delivery before the session. Commercials, auditions and e-learning jobs do not automatically use audiobook specifications. Keep a lossless working master and export the format the client actually requests. If you used **View → Plug-In Chain**, its [real-time processing is committed when saving](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/proonly/plug-in%5Fchainer.htm). Save a separate processed lossless copy and reopen it with the chain empty or bypassed. Do not apply the same effects twice. Select the whole file for [Tools → Statistics](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/statistics.htm) to inspect RMS and sample peaks; select representative room tone separately when checking background noise. Export and inspect the delivery file itself, especially after lossy encoding. ## ACX and Audiobook Delivery Standards For Audible/ACX delivery, master and inspect every finished file against the [current ACX audio submission requirements](https://help.acx.com/s/article/what-are-the-acx-audio-submission-requirements). The official page was updated on April 15, 2026 and is the source of truth if a number changes after this guide is published. ACX currently requires each file to measure between -23 and -18 dB RMS, keep peak values no higher than -3 dB, and keep the noise floor no higher than -60 dB RMS. Submit a 44.1 kHz MP3 at 192 kbps or higher CBR. Use the same mono or stereo format for every file, put one chapter or section in each file, keep each file at 120 minutes or less, and follow ACX’s recommended 1–5 seconds of opening and closing room tone. Its explicit spacing limit is five seconds; the one-second figure is a recommendation, not a separately stated hard minimum. Measure representative room tone, not digital silence. If the noise floor fails, fix the room, microphone position, gain staging, or source recording before aggressive processing. Noise reduction has no guaranteed dB improvement and can create artifacts; use the noise-reduction guide for a controlled pass, then remeasure the exported chapter. Measure the saved, processed chapter across the whole file; select room tone separately for its noise measurement. Adjust level, then check RMS and peaks again. ACX specifies peak level, not a substitute true-peak target. Listen after limiting or gain changes: compliant numbers alone do not establish clean narration. Sound Forge Pro 2026 documents [ACX Check and ACX Export](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/instantactions.htm) in View → Instant Actions. Run ACX Check on the finished chapter, export with ACX Export, then inspect the MP3 itself and use ACX's own audio analysis tool before submission. A wizard result does not replace a full listen-through. ## Frequently Asked Questions ### Can Sound Forge Pro be used for professional voice-over recording? Yes. Sound Forge Pro 2026 can record mono or multichannel audio, edit at sample level, run VST2/VST3 processing, and export delivery files. It is not a multitrack DAW: use a DAW when speakers need separate timeline tracks, routing, or later mix revisions. ### What recording levels should I use for voice-over in Sound Forge Pro? Use the interface or device control to set a strong signal that never reaches 0 dBFS. For unpredictable narration, peaks around -12 to -6 dBFS are a conservative editorial starting range, not a Sound Forge requirement. Record the loudest line before the take and leave more margin if the delivery is dynamic. ### Where are the voice-over recording controls in Sound Forge Pro 2026? Open View → Record Options. Choose Manual for general voice-over or punch-in work, choose Normal or Create regions as the recording mode, select monitoring, then use Arm and Record on the main toolbar. For a script-first layout, open the current Remote Record window from its Transport-toolbar button. ### How do I do punch-in recording in Sound Forge Pro for voice-over? Select the exact range to replace, set Method to Manual in View → Record Options, configure [pre-roll in Settings](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/record%5Fpunch-in.htm), then Arm and record. With Loop Playback off, recording stops at the end of an active selection; without a selection it continues from the cursor and overwrites existing data until you stop. With Loop Playback on, the selected range repeats for additional takes. ### What are the ACX audio standards for audiobooks in Sound Forge Pro? ACX currently requires each file to measure between -23 and -18 dB RMS, keep peaks no higher than -3 dB, and have a noise floor no higher than -60 dB RMS. Submit 44.1 kHz MP3 at 192 kbps or higher CBR, one chapter or section per file, no longer than 120 minutes, with opening and closing room tone: ACX recommends 1–5 seconds and requires that the spacing not exceed five seconds. Sound Forge 2026 includes ACX Check and ACX Export in Instant Actions. ### How do I remove breaths from voice-over in Sound Forge Pro? Don’t remove every breath automatically. Reduce or replace only distracting breaths, keep consonants and phrase timing intact, and use matching room tone instead of digital zero when a cut exposes silence. Follow the client's style guide for commercials, e-learning, or audiobooks. ### Does Sound Forge Pro have a de-esser for voice-over? Check your installed essentialFX effects for eFX DeEsser or VocalStrip before buying another plug-in. The current Sound Forge feature list includes essentialFX, but confirm the actual installation and license. Dynamic Equalizer can reduce sibilant bands dynamically; a compatible VST de-esser or local gain editing is another option. [Mouth De-click](https://soundforgepro.com/remove-mouth-clicks-from-audio/) treats mouth transients, not sibilance. For the next pass, use the [recording setup guide](https://soundforgepro.com/how-to-record-audio-in-sound-forge-pro/) if the meter never moves, the [playback troubleshooting guide](https://soundforgepro.com/sound-forge-pro-no-sound/) if the take records but cannot be heard, and the [hiss and hum workflow](https://soundforgepro.com/remove-hiss-hum-sound-forge/) only when the source actually needs repair. *Last fact-checked: September 12, 2026.* ### Sound Forge Pro for Mastering (Full Guide) URL: https://soundforgepro.com/sound-forge-pro-for-mastering/ Last updated: 2026-10-11T09:54:16.000Z Sound Forge Pro is a good fit for mastering one finished stereo file at a time. It gives you precise waveform editing, EQ, dynamics, loudness and true-peak metering, bit-depth conversion and controlled export. It isn't a substitute for fixing the mix, though, and there's no universal streaming LUFS number that makes a master correct. The job is to preserve the musical decision, meet the actual delivery sheet and verify the rendered file. Part of the [Sound Forge mastering hub](https://soundforgepro.com/tag/mastering/). This full guide covers processing choices, album checks and delivery versions. For a shorter session, use the [five-step mastering checklist](https://soundforgepro.com/how-to-master-a-track-in-sound-forge-pro/). The [current Sound Forge comparison](https://www.soundforge.com/sound-forge/pricing/) lists coreFX dynamics and peak/loudness metering. Its current help also documents [Modern Equalizer](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/modern%20equalizer.htm) and both Wave Hammer versions. The workflow below separates those processors and explains when a real-time chain becomes saved audio. Ozone is not listed in the current offer; treat it as a separately licensed option, not a promised inclusion. **Quick answer:** work through five checkpoints: 1. **Measure:** duplicate the source and save a whole-track, all-channel Statistics baseline. 2. **Correct:** make necessary EQ moves and compare at matched playback loudness. 3. **Control:** use compression or limiting only where the sound or delivery brief needs it. 4. **Verify:** save and reopen the processed copy, check that no extra chain is applied, then measure the complete file. 5. **Deliver:** make the required format conversions, with one planned dither stage at final integer quantization, and check each exported version. If a render misses the brief, revise the high-precision working version. A later gain boost can invalidate the earlier limiter ceiling. ## What to Check Before You Open Sound Forge Start by asking what the recipient needs: a streaming upload, an album master, a CD package or a file for a cutting engineer. Get the requested format and loudness method in writing. Then listen to the mix before building a chain; a buried vocal is a different problem from a whole track that needs a small level adjustment. Bring an unclipped source and leave working margin for the processing chain. There is no universal requirement for its peak to be exactly −2, −4 or −6 dBFS; a recipient may still request a particular margin. A clean gain adjustment changes level without rebalancing the instruments, but it does not remove distortion already printed into the mix. Ask for an unlimited mix when the master-bus limiter was used only to make the preview loud. Keep intentional mix-bus processing when removing it changes the balance or feel, and ask for a second version if the choice is unclear. The mastering stage should not reverse-engineer a mixer's intent from a single flattened file. Keep the mix at its native sample rate and retain the original file. A 24-bit PCM or 32-bit-float working WAV may be appropriate; do not make a 16-bit intermediate just to begin mastering. If delivery needs another rate, use [Process → Resample and the current conversion controls](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/resample.htm) on the processed working copy. Leave **Set the sample rate only** off for normal conversion: that option changes playback rate and pitch without resampling. The [sample-rate guide](https://soundforgepro.com/how-to-change-sample-rate-sound-forge-pro/) provides more background, but older iZotope SRC instructions are not interchangeable with the current dialog. A dense waveform isn't proof of clipping, and a low peak doesn't guarantee useful headroom. Run Statistics, inspect suspicious peaks at sample level and listen. If clipping or unwanted limiting is already printed, ask for a clean export. Turning that file down creates numerical headroom but does not restore the transients that were removed. ## Session Setup: Statistics Before You Touch Anything ![A full mastering pass in Sound Forge: measure the source, build the chain, bypass-check, verify the export](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/10/sound-forge-mastering-measure-chain-verify-v1-v20261006.webp) The Sound Forge mastering chain: measure first, build it deliberately, level-match and bypass-check, then verify the exported master. Open a copy of the mix, select the complete track and all intended channels, then run **Tools → Statistics**. Use **Copy to clipboard** to keep the baseline. The [Statistics field guide](https://soundforgepro.com/how-to-use-statistics-sound-forge-pro/) explains Integrated LUFS, sample extremes, RMS, Average value and the two true-peak fields. The scan describes the selected audio; it does not stand in for measuring an uncommitted mastering preview. Use the baseline to identify questions before processing: is the loudness already near the requested value, is there a suspicious sample extreme, and does Average value suggest an offset worth investigating? After mastering, compare with a fresh scan of the saved result. An unchanged source scan cannot verify a new chain. Save the report alongside the source filename and its file properties: sample rate, encoding/bit depth, channels and duration. Compare the finished render over the same scope. Keep both reports, not just a note saying “passed,” so a later revision can be checked against the correct file. Check for **DC offset** in Statistics by using Average value as the indicator, but don't process a file merely because a rounded display isn't exactly 0.000\. Correct a meaningful offset when it's confirmed in the waveform or affects processing; otherwise leave the signal alone. If correction is necessary, do it before dynamics and limiting, then remeasure. Check both sample peak and true peak. If a processor is overloading, reduce level before that stage and listen again. This can create working margin, but it cannot repair clipping baked into the source. Keep the original untouched for comparison. ## EQ: Fix the Audible Problem Classic equalizers are under **Process → EQ**. For Modern Equalizer, open **View → Plug-In Chain**, click **Add Plug-Ins to Chain**, select it, click **Add**, then **OK**. The [current chain documentation](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/proonly/plug-in%5Fchainer.htm) distinguishes live preview from processing applied on save. Save to a new file, not over the source; a stored chain preset alone is not a rendered master. A correction can be a cut or a boost. Choose it because of an audible imbalance, not because mastering supposedly requires subtractive EQ first. For example, if bass masks the vocal, compare a small low-band reduction with bypass before adding a presence boost. Keep whichever change solves the problem with fewer side effects—or return to the mix. Use the spectrum and reference only to locate a problem; make the decision by listening. A high-pass filter can remove genuine musical low end as easily as rumble. A broad low-mid cut can reduce congestion, but there is no universal 200–400 Hz fix. The same applies to presence and air bands. Start with the smallest move you can hear in a level-matched bypass test, then remove it if the mix does not improve. Use the [audio frequency chart](https://soundforgepro.com/audio-frequency-chart/) to name broad bands and common instrument ranges, then verify the actual problem in this mix by ear and spectrum. Additive EQ is optional. Small, broad moves are easier to justify than narrow boosts, but no gain value or frequency is automatically safe. If a master needs a large correction, ask whether the mix should be revised instead. Always level-match the processed and bypassed versions; louder is otherwise easy to mistake for better. Use Bypass throughout the decision and compensate output gain so the comparison is level-matched. Check the loudest section, the quietest section and a transition; a curve that helps one chorus may thin the rest of the track. The detailed controls are covered in the [EQ guide](https://soundforgepro.com/how-to-use-equalizer-sound-forge-pro/). ## Classic Wave Hammer: Compression and Limiting [Classic Wave Hammer](https://soundforgepro.com/sound-forge-wave-hammer/) is a two-stage dynamics processor. The compressor changes level over time and can reduce dynamic contrast; the Volume Maximizer adds gain while controlling peaks against a user-set ceiling. Both stages can change perceived loudness, so compare them at matched output level. For the compressor, test a low ratio and light gain reduction as a starting point, not a guaranteed setting. Listen for pumping ambience, softened drum attacks and loss of contrast. Adjust attack and release to the actual passage. If the gain-matched bypass is better, skip compression. Use the plug-in’s own help for stage controls in your installed build. A common mistake is using a high ratio because the master looks too dynamic. Compression can increase density, but it also changes transients, ambience and groove. Many streaming contexts apply playback normalization, yet behavior varies by service and device. Compare compressed and uncompressed versions at equal playback loudness; keep the compression only when its character improves the music. Set the Volume Maximizer ceiling with the delivery limit in mind, then measure true peak on the saved output. A ceiling labeled dBFS does not itself guarantee a dBTP result. Increase the maximizer’s contribution only until the required level is reached, or back off sooner if the sound suffers. If the brief cannot be met cleanly, revise the mix or agree a different target; do not silently deliver an out-of-spec file. This describes classic Wave Hammer. [Effects → Wave Hammer 2.0](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/proonly/wave%20hammer%202.0.htm) is a different processor with up to four frequency bands. If you compare them, use the same passage at matched loudness. Listen for changes in transients, pumping and distortion; neither a product name nor a preset proves which is better for this mix. ## Ozone Is Optional — Check the Exact Version Check both the Ozone edition and its compatibility requirements before buying or loading it. [Ozone 12 Elements](https://www.izotope.com/products/ozone-elements) offers Master Assistant and macro controls, but its individual Equalizer, Imager and Maximizer modules are not directly accessible. Standard and Advanced expose more editing. Do not follow instructions for editable modules if your edition only provides the assistant interface. If you own Ozone with editable Maximizer controls, compare it with Wave Hammer on the same difficult passage. Give each version the same delivery brief, verify that both meet the peak limit, and level-match playback. Matching two files to an identical measured peak is not necessary for a fair listening comparison. Do not stack limiters unless the extra stage gives a benefit you can hear. Stereo width is not a routine mastering step. Check mono compatibility and the phase display before changing it. Ozone 12 Standard and Advanced expose the Imager module; Ozone 12 Elements does not. Sound Forge also has native stereo processing, but a broad width change can move vocals, bass and ambience together, so ask for a mix revision when the problem is structural. Ozone 12 Elements' Master Assistant can provide a fast alternative, but it isn’t evidence that the suggested EQ or loudness is correct. Audition the result level-matched against the untreated mix, check true peak after rendering and keep only changes that solve an audible problem. An assistant gives you a second opinion; it doesn’t give you a delivery specification. ## Reference Tracks: Checking Your Work Against Reality Pick references that match the intended sound, not just the genre label. A sparse acoustic recording and a heavily layered production can call for different bass weight and dynamics. Use the reference to catch an imbalance you have become used to hearing, while keeping the artist’s intended sound as the priority. Open a reference with **File → Open**. Compare equivalent passages or complete-track scans consistently; do not match a quiet verse against a full-song LUFS reading. Use working copies for level adjustments and keep the originals untouched. Check each file’s own chain so the reference is not being processed by your mastering effects. Lower the louder comparison when necessary to avoid creating an overload just to match levels. Switch between the master and reference data windows. Listen to bass weight, vocal placement, transient impact and high-frequency texture at the same monitoring level. Recheck a quieter passage after the chorus: an EQ curve that helps a busy section can leave the rest of the track thin. A reference is useful only when level-matched and relevant. Compare tonal balance, transient shape and dynamics across several sections, but forcing the new track into the reference's exact spectrum misses the point. Different arrangements can justify different bass, vocal and high-frequency balances. ## Choose Loudness for the Destination and the Music Many listening services apply playback loudness normalization, but behavior varies by service, device, account setting and album-versus-playlist context. A louder master may be turned down; that does not restore dynamics removed by limiting. Judge loudness as a creative choice, then meet the destination's current technical guidance and audition the encoded result where possible. [Spotify recommends −14 Integrated LUFS](https://support.spotify.com/us/artists/article/loudness-normalization/) with true peak below −1 dBTP, or below −2 dBTP for masters louder than −14 LUFS. Its Normal playback reference is also −14 LUFS, but playback behavior varies: the web player does not use normalization, and album playback differs from shuffled tracks. That is a reason to audition the finished sound, not to copy one number across every service. [Apple Digital Masters](https://www.apple.com/apple-music/apple-digital-masters/docs/apple-digital-masters.pdf) asks for high-resolution sources and at least 1 dB of headroom, with checks of the encoded result. Its brief does not specify a fixed −16 LUFS mastering target. Follow the actual distributor or receiver’s requirements rather than treating a web table as the acceptance sheet. A useful workflow separates creative loudness from compliance. First decide how much density and transient control the music needs, then measure the result and compare it level-matched with relevant releases. Finally verify the rendered file against the destination sheet. [LUFS describes the result](https://soundforgepro.com/lufs-meter/); it doesn't choose the sound for you. Instead of choosing a genre number, make the listening test specific to the arrangement: For a beat-led mix, check whether a louder version weakens kick and snare attacks or makes bass sustain obscure the next hit. If deliberate clipping is already part of the approved production, compare against that approved sound rather than assuming every rough edge is a mastering error. For dense guitars, compare vocal intelligibility and cymbal texture before and after limiting. A setting that makes the chorus feel compact may turn its upper mids into a constant harsh layer. Back off and repeat the level-matched comparison. For an arrangement built around quiet-to-loud contrast, listen through the transition rather than only the loudest passage. Preserve that contrast unless the brief asks for a change. A quieter integrated reading does not, by itself, establish that the master needs more compression. CD audio uses 16-bit/44.1 kHz PCM. That format choice does not settle album loudness, gaps, track markers or the plant’s delivery package. Agree those separately; do not call a WAV “replication-ready” just because its sample rate and bit depth are correct. ## Measuring LUFS in Sound Forge Pro: Statistics and the LUFS Meter Use Statistics for a file scan and the live loudness displays for playback. The focused [Loudness Meters guide](https://soundforgepro.com/sound-forge-loudness-meters/) explains M, S, I, LRA and TP, including the current and older interfaces. Integrated loudness describes the measured program; sample peak alone does not tell you whether two masters are equally loud. In current builds, open **View → Channel meters** and enable Loudness Meters from the right-click menu. The [integrated meter](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/loudness%20meter%20v2.htm) has **Reset** in its context menu. For the older separate **View → Loudness Meters** window, use **Reset Metering Engine**. Select **Absolute (−23 LUFS)** when you need LUFS rather than relative LU. Reset and play the entire track from its beginning without skipping; repeat after changing the chain. Resetting a peak warning alone is not a complete loudness measurement. For an offline check, select the complete track and all intended channels, then open **Tools → Statistics**. Read Integrated under Loudness, minimum and maximum sample values, and both true-peak fields. Use the largest absolute sample amplitude when judging sample headroom. Average value can flag possible DC offset; it is not a separate “DC Offset” field. Keep the measurement scope consistent. LRA needs enough material: [EBU R128](https://tech.ebu.ch/files/live/sites/tech/files/shared/r/r128v5%5F0.pdf) does not recommend it for programs shorter than a minute. In **Process → Normalize**, choosing **Peak** and setting −1 dBFS aims at sample peak, not a particular Integrated LUFS value. Rescan the current selection before applying it. A dynamic recording and a dense one can have the same sample peak and different loudness. The [normalization guide separates Peak, RMS and Loudness modes](https://soundforgepro.com/how-to-normalize-audio-in-sound-forge-pro/). If the delivery sheet calls for loudness normalization, use **Process → Normalize → Loudness** only when its available method matches that brief. Work on the processed, high-precision copy before final dither. Enter the required settings, apply them to the whole program, then save and remeasure. For chain processing, use **File → Save As** for audio or **File → Render As** for a project. Reopen the output and bypass any effects already baked into it before another save or audition. ## Dithering: When It's Needed and When It Isn't [Dither deals with quantization at the final fixed-point conversion](https://soundforgepro.com/sound-forge-bit-depth-dither/). A 24-bit or floating-point working signal becoming 16-bit is the clearest case; float-to-24-bit is also a quantization decision. Follow the destination and processor documentation, plan one dither stage, and put it after the remaining processing. This is not a requirement to add dither to every file copy. For streaming delivery, use the bit depth and file type accepted by the distributor; 24-bit WAV is common, but acceptance is not universal and can change. Never assume every service accepts 32-bit float. If the final render is already the required fixed-point bit depth, do not dither an unchanged copy again. Sample-rate conversion is processing: create the required-rate derivative from the undithered high-resolution master, then apply any final fixed-point quantization and dither once. For a 16-bit CD version, first make the 44.1 kHz derivative if needed. Then open **Process → Bit Depth → Bit-Depth Converter**, choose 16-bit and the planned dithering mode. The [converter documentation](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/bit%5Fdepth%5Fconverter.htm) includes POW-r options and distinguishes conversion from merely changing a file’s playback properties. POW-r modes use different noise-shaping curves. There's no single correct type for every master. Use the manual's intended program guidance, audition at a safe monitoring level and keep the choice documented. The important rules outlast the preset choice: apply dither only at final quantization, only once, and do no processing afterward. To compare dither modes, render the same quiet tail to the final bit depth and audition it level-matched. Don’t boost the result to extreme levels and then treat the amplified noise as normal listening evidence. Keep the undithered high-resolution archive and document the dither used for each fixed-point deliverable. Commit the approved EQ, dynamics and gain to a high-precision working render first. Reopen it and bypass the already-applied chain. Then make any required sample-rate conversion and final integer conversion, with dither last. [The final-stage dither principle](https://www.fabfilter.com/help/pro-l/using/dithering) applies regardless of which brand performs it. Do not dither the unprocessed waveform and then apply the mastering chain on save. Verify the output without further processing. ## Album Checks: Order, Relative Level and Track Boundaries A collection needs another listening pass after the individual tracks sound right. [iZotope’s album-mastering guidance](https://www.izotope.com/community/blog/how-to-master-an-album) separates song sequence and spacing from matching every track to one sonic template. Choose an approved running order and audition the transition from each ending into the next beginning. 1. **Compare relative level.** Does the next song feel unintentionally quieter or louder, or does that change serve the arrangement? Do not normalize every song to identical LUFS by reflex. 2. **Check starts and tails.** Listen for an accidental cut-off, click, doubled gap or lost reverb tail. Recheck both sides of a crossfade, including each separate exported track. 3. **Write down the sequence.** Number filenames and keep a track list with titles, timings and any intentional continuous transitions. Agree who will assemble the final delivery package. 4. **Check the delivered sequence.** Audition the exact exported files in order and, when supplied, the plant’s DDP or reference version. A correct working session does not prove that the last export has the same boundaries. For vinyl, confirm whether the cutter wants one file per side or separate tracks. [MonotypePressing, for example, asks for pauses](https://monotypepressing.com/audio-file-preparation-guide/) to be embedded unless changes have been arranged; visual groove markers do not create silence in the audio. Treat the chosen plant’s instructions as the brief. ## Multiple Deliverables from One Session A single production may need different masters for different contexts: streaming, CD, vinyl preparation, broadcast, each with its own requirements. The efficient approach in Sound Forge Pro is to master from the same source file but export different versions with different processing parameters. Keep the untouched mix, the approved processing settings and a high-precision processed working render when available. Do not reduce the archive to 16-bit solely because one delivery needs CD resolution. If vinyl or another brief requires less limiting, return to the source and settings; lowering a finished loud master does not recover the removed dynamics. **Streaming:** choose the accepted file type and resolution, then check peaks and loudness on the export. Use Spotify’s advice above where relevant; it is not a universal upload rule. If you need an MP3 listening copy, the [MP3 export guide](https://soundforgepro.com/how-to-export-mp3-from-sound-forge-pro/) covers that format. Do not make an unnecessary 16-bit intermediate just to encode it. **CD:** prepare 16-bit/44.1 kHz PCM with the planned final dither. Ask the plant what package it accepts. For example, [MonotypePressing specifies DDP delivery and offers WAV-to-DDP preparation by arrangement](https://monotypepressing.com/audio-file-preparation-guide/). That is different from assuming a Sound Forge WAV export contains all sequencing and CD-Text information needed for replication. **Vinyl pre-master:** ask the cutting engineer before filtering, narrowing bass or changing level. Their brief may specify side files, running times, phase checks and how to handle sibilance. Do not invent a universal −16 or −18 LUFS target. Send the requested high-resolution files with notes on intentional sub-bass or stereo effects, and leave cutting-specific processing to the agreed workflow. **Broadcast:** [EBU R128](https://tech.ebu.ch/files/live/sites/tech/files/shared/r/r128v5%5F0.pdf) uses −23 LUFS program loudness and a −1 dBTP ceiling for linear-audio production; distribution may require a lower ceiling. [ATSC A/85’s July 2026 reference](https://www.atsc.org/wp-content/uploads/2026/07/A85-2026-07-Annex-M.pdf) gives −24 LKFS as the default without metadata or another agreement and distinguishes dialogue from full-program measurement. Confirm the receiver’s method, channel layout and peak limit. A Sound Forge preset name alone does not establish compliance. For each output, record the source/version, file format, rate, PCM bit depth where applicable, channels, duration, Integrated loudness, true peak and dither choice. Reopen and audition it, checking the beginning, transitions and final tail as well as the meter report. Sound Forge’s save-time loudness log is measured before codec encoding; for a lossy copy, [generate a new log from the saved file](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/loudness%5Fmeters.htm). ## Common Mastering Mistakes in Sound Forge Pro Two avoidable problems are treating a meter reading as a processing decision and changing the file after its final check. Use the checks below before delivery. **Assuming an early normalization target remains final.** Initial gain adjustment can be useful, but EQ and dynamics can change the later loudness and peaks. Measure after the approved processing and format conversion. If the result misses the brief, revise the working version and check again. **Confusing peak and loudness normalization.** The Peak mode applies constant gain. Loudness mode uses a chosen loudness method and may involve dynamics. Check which one is selected; a −1 dBFS peak setting is not a −14 LUFS mastering instruction. Dithering to 16-bit and then continuing to process. Further gain changes or processing create a new quantization decision; the earlier dither is not a substitute for handling that final reduction. Return to the undithered high-resolution master, make the revision there and dither once for the new 16-bit deliverable. Applying heavy limiting because a meter is below a platform reference. First test whether clean gain can reach the required loudness without crossing the true-peak limit. If it can, no extra peak reduction is needed. If it cannot, decide whether the destination actually requires that loudness and whether the audible cost of limiting is acceptable. A number does not justify damaged transients. For a fair comparison, bring the louder render down to a common listening level where both versions retain peak headroom. Do not force the clean-gain version up to a loud target that would clip it. Listen for the musical benefit of limiting, not the larger waveform. The [Plug-In Chain guide](https://soundforgepro.com/how-to-use-plug-in-chainer-sound-forge-pro/) explains the preview-versus-save workflow. ## Frequently Asked Questions ### What is the correct mastering chain order in Sound Forge Pro? Duplicate and measure the source, make necessary EQ changes, then add compression or limiting only where needed. Save a processed copy and reopen it with no unwanted chain applied. Measure the complete output, revise if needed, then perform required rate and integer conversion with one final dither stage. Check each delivery file again after conversion. ### What LUFS target should I use when mastering in Sound Forge Pro? Use the destination’s current brief. Spotify recommends −14 Integrated LUFS and true peak below −1 dBTP, or below −2 dBTP for louder masters. Apple Digital Masters does not prescribe −16 LUFS. CD and vinyl preparation still need a receiver’s specification, not a universal music LUFS number. Broadcast requires the specified standard and measurement method. ### When should I use Wave Hammer vs Ozone Elements for mastering in Sound Forge Pro? Classic Wave Hammer supplies the compressor-plus-maximizer workflow described here; Wave Hammer 2.0 is a different multiband effect. Use Ozone only if you own a compatible edition and prefer its workflow. Ozone 12 Elements offers Master Assistant and macro controls, not directly editable Equalizer, Imager or Maximizer modules. Compare saved results at matched playback loudness and check each against the same peak limit. ### When do I need to apply dithering in Sound Forge Pro? Dither when the final render is quantized to a lower fixed-point bit depth, and apply it only once as the last signal-processing step. A 16-bit CD export is the clearest case; float-to-24-bit delivery can also be a final quantization decision. Use the destination format and the processor manual to choose the mode, then do not normalize, EQ or sample-rate-convert the dithered file. ### How do I check the integrated LUFS in Sound Forge Pro? Select the complete saved track and all intended channels, then use Tools → Statistics for an offline Integrated reading. For playback, enable the Channel Meters’ Loudness display and reset it; the older separate window uses Reset Metering Engine. Select Absolute (−23 LUFS), then play the entire track without skipping. Reopen the final export and confirm no extra processing chain is active before checking it. ### What mix settings should I prepare before mastering in Sound Forge Pro? Export an unclipped high-resolution WAV at the original project sample rate, with no dither and no loudness-only limiter. A fixed -2 to -6 dBFS peak range is not required; clean gain can create working margin. Keep intentional mix-bus processing, or provide limited and unlimited versions if intent is unclear. Use Statistics' Average value to investigate possible DC offset and correct it only when meaningful, not merely because a rounded value is not exactly zero. ### Can Sound Forge Pro produce masters for both streaming and CD from the same session? Yes, but save separate delivery versions. Keep the source and an approved high-precision working render, make the requested streaming file and a 16-bit/44.1 kHz CD version with final dither, and verify each output. Ask the plant about sequencing, DDP and metadata; an ordinary WAV export does not settle those requirements. *Documentation checked September 7, 2026 against the linked Sound Forge help, platform guidance and delivery specifications. The menu routes are documentation-based; this update is not a newly recorded mastering test on an installed Windows build.* ### Digitize Vinyl Records on Windows: Restore & Archive URL: https://soundforgepro.com/sound-forge-pro-for-vinyl-restoration/ Last updated: 2026-10-09T21:03:23.000Z **Quick answer:** to digitize vinyl records well, get the playback chain right before opening a [restoration effect](https://soundforgepro.com/audio-restoration/). Clean the record, send the turntable through one correct phono/RIAA stage into a line input or USB converter, capture each side uninterrupted at the converter’s actual resolution—preferably 24-bit for preservation, save that file as an untouched raw master, then repair a copy. In Sound Forge, remove only defects you can identify, place track markers, convert them to regions, extract the tracks, and keep lossless archive files separate from listening copies. The safe order is **clean → capture → raw master → repair copy → split tracks → archive**. Run it backwards and you create problems no “vinyl preset” can solve. A missing phono stage needs a routing fix, not a noise-reduction preset. De-clicking cannot restore samples lost at an overloaded converter, and normalization cannot undo mistracking or physical damage. This guide uses Sound Forge on Windows because a single-file waveform editor fits the job: one side comes in as one long file, defects are repaired at sample level, and regions become separate tracks. The same preservation logic applies in other editors. If capture itself is already working, jump to the [click-and-pop repair workflow](https://soundforgepro.com/how-to-remove-clicks-pops-sound-forge-pro/) or the [track-splitting guide](https://soundforgepro.com/split-long-recording-into-tracks-sound-forge/). This is the complete transfer-and-archive workflow in the [Sound Forge workflow guides](https://soundforgepro.com/tag/workflows/), not a review of turntables or a replacement for the separate repair tutorials. Sound Forge Pro 2026 is the editor used below; old Audio Studio and Audio Cleaning Lab vinyl wizards have different controls. ## Build the Vinyl Transfer Chain Correctly ![The vinyl capture chain: turntable, phono preamp, audio interface and Sound Forge recording](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/10/vinyl-signal-chain-v2-v20261009.webp) PHONO needs one compatible gain and RIAA stage; a built-in preamp uses the LINE route. The 24-bit profile requires a converter that supplies 24-bit audio. A magnetic cartridge doesn't normally produce a line-level, tonally flat signal. Its output is quiet and still reflects the recording emphasis used when the disc was cut. The playback phono stage applies the complementary correction. A phono stage raises that signal to line level and applies playback equalization, usually RIAA for modern LPs and 45s. The official [Audacity equipment guide](https://manual.audacityteam.org/man/how%5Fto%5Fconnect%5Fyour%5Fequipment.html) therefore routes a conventional turntable through a phono preamp or receiver PHONO stage before a computer line input. | Your turntable output | Correct path to the computer | Common mistake | | ---------------------------- | ------------------------------------------------------------------------------------------ | --------------------------------------------------------------------------------------- | | **PHONO output** | Turntable → phono preamp or receiver PHONO input → line/tape output → interface LINE input | Going straight into LINE produces a very quiet, thin, bass-light transfer | | **Switchable PHONO/LINE** | Set the deck to LINE → interface LINE input | LINE output into another PHONO input applies gain and RIAA twice | | **USB turntable** | USB directly to Windows; select the turntable's USB input in Sound Forge | Assuming the USB converter supports every sample rate or has adjustable analog headroom | | **External USB phono stage** | Turntable PHONO output → USB phono stage → Windows | Adding a second phono preamp before it | Match the phono input to the cartridge: moving-magnet (MM) and low-output moving-coil (MC) cartridges need appropriate gain and loading. Check both manuals; a socket labeled PHONO alone does not establish compatibility. On an interface with combined inputs, select LINE rather than instrument gain. A laptop headset jack is not a substitute for a specified stereo line input. If the first test sounds unusually thin and quiet, stop and inspect the signal path. Extremely loud, bass-heavy and distorted points the other way: check for two phono stages in series. Don't “fix” either fault with EQ after capture; the wrong gain and equalization have already reduced headroom and raised noise. Ground hum belongs upstream too. Connect the turntable ground wire where the phono stage provides a ground terminal, keep unbalanced cables short, and separate power bricks from cartridge leads. The [hiss and hum diagnosis guide](https://soundforgepro.com/remove-hiss-hum-sound-forge/) distinguishes 50/60 Hz mains hum from broadband surface noise before you reach for a filter. ## Clean and Set Up the Record Before Capture Physical cleaning is restoration. Dust in a groove becomes an impulse in the transfer, and removing dust before playback is more transparent than interpolating over the click afterward. IASA's [microgroove cleaning guidance](https://www.iasa-web.org/tc04/microgroove-cleaning-and-carrier-restoration) explains that vinyl attracts dust electrostatically and that groove-sized particles cause clicks and frying noise. - Inspect the record, stylus and cantilever under good light. Replace a damaged or unknown stylus before it traces a valuable disc. - Remove loose dust with a suitable anti-static record brush. For wet cleaning, follow the cleaner and record manufacturer's method; do not improvise a solvent on shellac or a rare disc. - Confirm speed, tracking force, anti-skate and cartridge alignment for the turntable and cartridge in use. - Photograph both labels and the sleeve. Record catalog number, matrix/runout, side, speed, stylus and playback chain while the evidence is in front of you. - Play a short test at the beginning, a loud passage and the inner groove. Listen for mistracking, one weak channel, hum, mechanical rumble and obvious overload. A badly worn or mold-affected disc is not a practice record. If the item is rare, cracked, delaminating or historically important, stop before cleaning or playback and use a specialist. Software cannot reverse physical damage caused during the transfer. ## Choose 24-Bit Capture and a Defensible Sample Rate Choose a converter that genuinely supplies 24-bit PCM for a preservation transfer. The extra word length doesn't reveal ultrasonic music hidden in vinyl; what it buys you is recording headroom, and it keeps level changes and repair work comfortably above the quantization floor. IASA's [Key Digital Principles](https://www.iasa-web.org/tc04/key-digital-principles) recommends at least 24-bit encoding for analog materials. Sample rate needs a less dogmatic answer. IASA lists [48 kHz/24-bit LPCM as a minimum](https://www.iasa-web.org/book/export/html/907) and notes that 96 kHz/24-bit is widely adopted in memory institutions. For a serious archive, 96/24 is a defensible default. For a large personal collection where storage and processing matter, 48/24 is still a standards-grounded capture, not a failed transfer. | Use case | Capture | Master format | Why | | ------------------------------- | ------------------------------- | -------------------------------------------------------- | ------------------------------------------------------------------- | | **Preservation or rare source** | 96 kHz / 24-bit PCM | BWF where supported; otherwise WAV plus sidecar metadata | Common heritage profile with room for later analysis and processing | | **Personal listening archive** | 48 or 96 kHz / 24-bit PCM | WAV or lossless FLAC after the raw WAV is secured | 24-bit headroom matters more than chasing 192 kHz | | **CD derivative** | Capture at archive rate first | 44.1 kHz / 16-bit WAV derivative | Resample and dither once after restoration | | **Phone or streaming copy** | Never capture directly to lossy | AAC/MP3 derivative from a verified lossless master | Keeps future exports independent of a lossy generation | Check the hardware before selecting the profile. For example, the [NAD PP 4 specification lists 16-bit/48 kHz USB output](https://nadelectronics.com/products/pp-4-digital-phono-usb-preamplifier). An existing device like this can make a personal listening transfer, but it does not meet the 24-bit preservation profile merely because the editor saves a larger word length. For a rare source, arrange a suitable capture chain before playback; for a personal transfer, preserve the real input resolution and record that limitation in the notes. IASA recommends [WAV or, preferably, BWF WAV](https://www.iasa-web.org/tc04/ingest-format); the BWF headers can carry metadata used to organize and manage the recording. A well-documented WAV is still better than a BWF whose embedded fields you never verify. Keep the original stereo or mono channel structure, and don't collapse channels casually during capture. ## Record One Side in Sound Forge Without Clipping 1. In Windows and Sound Forge, select the intended USB interface or turntable—not the laptop microphone. The [Sound Forge recording guide](https://soundforgepro.com/how-to-record-audio-in-sound-forge-pro/) covers the current device and input settings. 2. Confirm the converter’s actual USB/driver output, then create the file at a supported sample rate, appropriate bit depth and correct channel count. A 24-bit destination cannot turn a 16-bit converter into a 24-bit capture. 3. Run the loudest passage you can identify. Set analog gain so the largest peaks stay comfortably below 0 dBFS; roughly −12 to −6 dBFS is practical headroom for unpredictable discs. 4. Start recording before lowering the stylus. Capture the whole side without pausing, processing or changing gain. 5. Let the run-out finish, then stop. Listen to the start, loud passage, inner groove and end before putting the record away. **Hear the transfer while it records.** Use the interface’s direct-monitor output if it provides one, or configure the monitoring route described in the recording guide. A moving input meter does not prove that your headphone output is routed correctly. Make and replay a short test before starting the full side; avoid listening through two monitoring paths at once. Don’t chase a “full” waveform. With a suitable 24-bit converter, leaving this headroom is preferable to risking an overloaded transient. An analog preamp, USB turntable or interface can clip before Sound Forge's meter reaches zero, so watch the hardware indicators and listen for harshness. If any stage overloaded, lower the gain and capture the side again; de-clipping exists for irreplaceable damage, not as a substitute for a clean second pass. Check channel balance and polarity while you're at it. A large steady imbalance may point to cartridge alignment, cable, connector or preamp trouble. Pitch that drifts is a turntable matter, speed or belt/drive behavior, and click removal or noise reduction won't fix wow and flutter. ## Preserve the Raw Master Before Touching the Audio ![Vinyl digitization end to end: clean, capture, lock the raw master, repair a copy, split, archive](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/08/vinyl-restoration-workflow.webp) The vinyl preservation rule in Sound Forge: lock the untouched side capture, repair a duplicate, then build derivatives from the verified copy. Save the untouched side immediately and make a working copy. A practical folder might contain: - **preservation/​LP123\_​sideA\_​raw\_​96k24.wav** — untouched capture; - **working/​LP123\_​sideA\_​restore\_​v01.wav** — editable duplicate; - **access/​01\_​track-title.flac** — lossless listening track; - **metadata/​LP123\_​transfer.txt** — source, equipment, settings, date and processing notes; - **images/​LP123\_​label\_A.jpg** — label, sleeve and runout photographs. Set the raw file read-only or store it outside the active edit folder. Generate a SHA-256 checksum if the transfer matters, and keep a second copy on independent storage; a checksum only tells you something changed, it won't replace a backup. Re-open the copied file and confirm duration, channels and a few playback points before processing the recording. ✓ **Non-negotiable:** never repair the only copy. A reversible effect chain is not protection against overwriting, disk failure or a bad export. ## Identify the Defect Before Choosing a Tool “Vinyl noise” isn't one problem. Put on headphones, zoom into the waveform and use the [Sound Forge spectral analysis workflow](https://soundforgepro.com/how-to-use-spectral-analysis-tool-sound-forge-pro/) to decide what's actually there. | What you hear | Likely cause | First response | Do not assume | | ------------------------------ | ------------------------------------------------------------ | --------------------------------------------------------------------------- | ----------------------------------------------------------- | | **Single pop or tick** | Dust, scratch, static or splice | Very short manual repair or conservative DeClicker | That the whole side needs the same setting | | **Dense crackle** | Wear, contamination or many small impulses | Clean/re-capture if possible; test DeCrackler on a copy | That broadband noise reduction is the right first tool | | **Steady hiss** | Groove noise, electronics or previous recording chain | Profile cautiously after click repair | That silence between tracks represents only removable noise | | **50/60 Hz hum and harmonics** | Ground loop, cable, power or phono setup | Fix the chain and re-capture; notch only an irreplaceable transfer | That a noise print will remove it cleanly | | **Low rumble** | Turntable bearing, footfall, warp or arm/cartridge resonance | Correct mechanics first; high-pass only after spectrum and listening checks | That every LP should be filtered at one frequency | | **Pitch wander** | Wow, flutter, off-center hole or wrong speed | Correct playback hardware or use specialized time correction | That EQ or de-noise can repair timing | Work from discrete defects toward continuous ones: large clicks can corrupt a noise profile and make later processing pump or smear. Hum gets corrected at the source before you profile hiss, and tonal EQ and level changes can wait until the defects are stable. ## Remove Clicks and Crackle Conservatively Start with the obvious isolated clicks. Zoom to the impulse, select only the damaged samples, and use the smallest Repair operation that works. Sound Forge's current [Repair documentation](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/proonly/repair.htm) covers sample-level Interpolate, Replace and channel-copy choices. A tiny manual fix often protects a snare, piano attack or consonant better than processing an entire side. For repeated clicks, the current Sound Forge 2026 repair help lists DeClicker/DeCrackler under Effects; older classic restoration tools are under Tools. Preview the installed effect on three places: the worst defect, an average musical passage and clean transient-heavy audio. Listen to the removed component if the tool offers that mode. If you can recognize cymbals, percussion, consonants or musical pitch in what is being removed, reduce sensitivity or shorten the selection. If crackle survives a conservative pass, the [RX vinyl restoration workflow](https://izotoperx.net/izotope-rx-vinyl-restoration/) covers the next stage. Use DeCrackler only when the texture is genuinely continuous. One strong pass isn't automatically better than a light pass plus a few manual fixes. The goal isn't a black background between notes; it's fewer distractions without sanding away the performance. ## Reduce Surface Noise Only When It Beats the Original Broadband noise reduction is optional. A clean pressing may need none. A worn speech or historical disc may benefit, but the noise print must contain only the steady unwanted bed: no reverb tail, no room tone that belongs to the recording, no music fading into silence. 1. Repair large clicks first. 2. Find the longest representative noise-only segment available. 3. If the installed noise-reduction effect supports a noise print, capture that segment as its profile; use that effect’s help rather than assuming every de-hisser has a profile control. 4. Preview a low amount across quiet and dense passages. 5. Level-match Bypass. Louder is not cleaner. 6. Stop when ambience breathes, cymbals turn watery, or a metallic/bird-like residue appears. The [background-noise guide](https://soundforgepro.com/how-to-remove-background-noise-in-sound-forge-pro/) explains profiles and artifact checks. There's no honest universal reduction number for vinyl; surface condition, cartridge, music and plug-in edition all move the limit. ## Handle Rumble, Tone and Level After Repair Don’t high-pass by habit. Inspect the spectrum and compare musical bass against the suspected rumble. A warp or turntable resonance may sit below useful content; an organ, electronic bass or orchestral recording may not. Use a gentle filter only when it removes measured unwanted energy without thinning the record. The same caution applies to treble: a dull old pressing isn't a reason to boost it, since that can raise hiss and expose click residue. Use the [Sound Forge equalizer workflow](https://soundforgepro.com/how-to-use-equalizer-sound-forge-pro/), match output level for Bypass, and keep the change only when the music improves at equal loudness. If you used real-time effects, first save their output as a separate lossless restored copy and reopen it with the chain empty or bypassed. Then normalize only if a derivative needs a defined peak or loudness. Peak normalization is a constant gain change and does not repair dynamics. Loudness normalization can also change dynamics when true-peak or loudness-range constraints engage; the [normalization guide](https://soundforgepro.com/how-to-normalize-audio-in-sound-forge-pro/) explains the difference. Leave the preservation master at its captured level and document any change made to restored derivatives. ## Split the Vinyl Side into Verified Tracks ![Four vinyl-side markers define three consecutive regions for separate WAV tracks](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/10/vinyl-track-boundaries-20260912-v20261005.webp) Four boundary markers create three regions. Listen to each start and end before extracting the tracks. **Extract the processed audio, not just its playback preview.** If you used **View → Plug-In Chain**, the [real-time chain help](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/proonly/plug-in%5Fchainer.htm) explains that processing is committed when saving. Save a separate lossless restored side, reopen it with an empty or bypassed chain, and verify the repairs before making track regions. Do not apply a chain twice if its effects were already committed to the audio. 1. On the restored side copy, place a marker at each intended track start and one at the final end. 2. Include a natural amount of lead-in and decay. Don’t cut a quiet attack or trailing reverb just to make the gap look tidy. Listen across the boundary before accepting it. 3. Choose **Edit → Regions List → Markers to Regions**. The current [Boris FX marker-to-region guide](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/proonly/converting%5Fmarkers%5Fto%5Fregions.htm) confirms that regions are built between consecutive markers. 4. Name regions with track numbers and titles. 5. Choose **Tools → Extract Regions**, select the destination and naming options, including prefix or region names, then extract. The current [Extract Regions help](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/proonly/extract%5Fregions.htm) documents the command. 6. Play the first and last seconds of every file. Check count, order, channel layout and gaps before tagging. Automatic silence detection can help on clean, conventionally sequenced albums, but vinyl noise, crossfades and live applause confuse it. Boundaries deserve a human listen. Keep the full-side restored master even after the tracks pass QA; it preserves the exact spacing and gives you a clean source for later exports. ## Archive the Transfer and Create Derivatives ![Untouched vinyl capture, restored lossless master and listening files kept as three separate roles](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/09/vinyl-file-roles-20260912.webp) Duplicate the untouched BWF/WAV for restoration, then export listening tracks from the verified restored side. Keep transfer notes, checksums and independent backups. Keep three roles separate: - **Raw preservation master:** untouched side capture at the converter’s actual resolution and sample rate; use a suitable 24-bit chain for the preservation profile above. - **Restored master:** lossless full-side file with documented repairs, no lossy encoding and no unnecessary bit-depth reduction. - **Access derivatives:** split FLAC/WAV tracks, 16-bit CD files, or AAC/MP3 copies for devices and sharing. An unchanged integer copy needs no additional dither. After floating-point processing, an integer export is a new quantization step even if both source and destination files say 24-bit. Keep a floating-point working file while more processing remains, and handle dither once at the final fixed-point delivery stage, after EQ, level and sample-rate changes; avoid two active dither stages. The current [Sound Forge Bit-Depth Converter help](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/bit%5Fdepth%5Fconverter.htm) notes that the best noise-shaping mode depends on the signal; the [bit-depth and dither guide](https://soundforgepro.com/sound-forge-bit-depth-dither/) covers the decision. Tag access files with artist, album, title, track number, date, label and catalog number. Keep transfer-specific data (turntable, cartridge/stylus, phono stage, interface, sample rate, bit depth, date, operator, software version and processing steps) in BWF fields or a sidecar text/CSV file. Store label and sleeve photographs beside the audio. The [format-conversion guide](https://soundforgepro.com/how-to-convert-audio-files-sound-forge-pro/) covers controlled WAV, FLAC and listening-copy exports. Use the [CHIN digitization workflow](https://www.canada.ca/en/heritage-information-network/services/digitization/how-to-digitize-audio.html) as a model for separating capture, quality review and archiving. For a preservation transfer, listen through the saved side for dropouts or missing audio; spot checks alone cannot establish that the whole capture is intact. Verify the archive from another device or application. Compare file counts, durations and checksums, then keep at least two independent copies. Cloud sync can be one copy, but synchronization alone can propagate an accidental deletion. ## Know When Sound Forge Is Not Enough Sound Forge is a good fit for precise waveform editing, isolated repair, whole-side files, markers, regions and export. It's less comfortable when the job calls for extensive spectral painting, automatic wow-and-flutter correction, azimuth research across historical formats, or hundreds of side-specific restoration decisions. For detailed spectral selection, check a dedicated editor such as iZotope RX against the defect you need to remove; its presence or license is not guaranteed by this Sound Forge workflow. Use a transfer specialist for fragile or unique media. Don’t let tool capability determine how much processing you apply. If the restored version sounds smaller, phasey or less alive than the raw transfer, the quieter noise floor is not a win. Preserve the source, back off, and keep the least destructive version. ## Treat 78 rpm and Historical Discs as a Different Job A shellac 78 is not merely a noisy LP. Groove dimensions, stylus size, material, actual playback speed and equalization can differ. “78 rpm” was not always the exact recorded speed, and pre-standardization labels did not all use modern RIAA playback. IASA's [historical-disc speed guidance](https://www.iasa-web.org/tc04/mechanical-carriers-speed) and [coarse-groove equalization tables](https://www.iasa-web.org/book/export/html/462) show why one cartridge, stylus and curve cannot cover every era. Don’t apply a vinyl wet-cleaning recipe to shellac without confirming material compatibility. For a rare disc, capture flat or with the correct documented playback curve only when you understand the chain, and preserve all transfer notes. If the speed, stylus or curve is uncertain, consult a specialist before the first pass. ## Digitize Vinyl Records FAQ ### Should I digitize vinyl at 24-bit/96 kHz? For preservation, use hardware that actually captures 24-bit audio; 96 kHz is a defensible archive profile and IASA also specifies at least 48 kHz/24-bit for analog material. If an existing USB device outputs only 16-bit audio, retain that original accurately and document the limitation. Saving it in a 24-bit file does not restore converter resolution. ### Do I need a phono preamp to record vinyl? Yes, unless the turntable or USB converter already includes one. A conventional PHONO output needs phono gain and playback equalization before a line input. Never run a LINE output through a second PHONO input. ### Is WAV or FLAC better for a vinyl archive? Keep the raw capture as BWF/WAV when possible because that is the established preservation path and carries PCM without compression. FLAC is lossless and excellent for verified access or listening copies. Whatever you choose, maintain metadata, checksums and more than one storage copy. ### Should I clean a record before digitizing it? Yes. Removing safe-to-clean dust before playback prevents clicks more transparently than software repair. Use a method appropriate to the record material, and do not improvise wet cleaning on shellac, moldy or historically valuable discs. ### What is the best click-removal setting for vinyl? There is no universal setting. Test the worst click, an average passage and clean transient-heavy music. Reduce processing if the removed signal contains wanted attacks, consonants or pitch. Manual repair is often better for a few isolated pops. ### Should I remove all vinyl surface noise? No. Broadband reduction can remove ambience and high-frequency detail with the noise. Keep it only when a level-matched comparison is less distracting without watery, metallic or breathing artifacts. ### Should I record each track separately? Record each side as one uninterrupted file. That avoids repeated level changes and preserves spacing. After repair, place markers, convert them to regions, extract the tracks and verify every boundary. ### Should I normalize before removing clicks and noise? No. Preserve the captured level while diagnosing defects. Repair clicks and continuous noise first, then apply documented EQ or level changes to a derivative. Normalization cannot recover a clipped capture or improve the playback chain. *Last fact-checked: September 12, 2026 against Boris FX Sound Forge 2026 help, IASA preservation guidance, CHIN’s audio digitization guide and the cited hardware and routing documentation.* ## Related Sound Forge guides - [How to Remove Clicks and Pops in Sound Forge Pro](https://soundforgepro.com/how-to-remove-clicks-pops-sound-forge-pro/) - [Remove Hiss From Audio: 50/60 Hz Hum Repair on Windows](https://soundforgepro.com/remove-hiss-hum-sound-forge/) - [Split a Long Recording into Tracks in Sound Forge](https://soundforgepro.com/split-long-recording-into-tracks-sound-forge/) - [How to Record Audio in Sound Forge Pro 2026](https://soundforgepro.com/how-to-record-audio-in-sound-forge-pro/) - [Sound Forge Markers and Regions: Navigate & Export](https://soundforgepro.com/sound-forge-markers-regions/) - [Sound Forge: The 2026 Guide (start here)](https://soundforgepro.com/) - [Open the Sound Forge workflows hub](https://soundforgepro.com/tag/workflows/) ### Sound Forge Pro for Podcast Editing: 2026 Workflow URL: https://soundforgepro.com/sound-forge-pro-for-podcasters/ Last updated: 2026-10-08T09:16:22.000Z **Sound Forge Pro is a strong podcast editor when the episode is already one mono or stereo file.** Use it to tighten dialogue, repair steady noise, shape tone, control dynamics, measure loudness and create the delivery file. If every guest is on a separate track, or music must duck under speech, assemble the show in a multitrack DAW first and use Sound Forge for the final edit and master. That distinction matters. Sound Forge is a precise waveform editor, not a session-based podcast studio. For a solo show or a finished interview mix, you can work directly on the episode waveform. Keep isolated speakers and overlapping music in a multitrack project until their balance is settled; a flattened file makes later speaker-by-speaker changes harder. **Workflow rule:** edit the words before polishing the sound. A perfect EQ curve cannot rescue a slow opening, a repeated answer or 12 seconds of dead air. ![Podcast workflow diagram with edit markers, an effects chain and an export check](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/10/podcast-editing-ui-markers-chain-v2-1-v20261006.webp) Mark edits, review processing, then verify the exported episode. Use the menu paths in the text for the current controls. ## Is Sound Forge Pro the right podcast editor? **Use Sound Forge as the main editor when:** - the recording is one host, one narrator or a pre-mixed interview; - you prefer editing directly on a waveform; - restoration, exact cuts, loudness and export are the main jobs; - you want reusable effect chains or batch conversion for finished episodes. **Use a multitrack DAW or podcast app first when:** - each participant has an isolated track that still needs balancing; - music, ads and ambience overlap dialogue; - you need automatic transcript editing, collaboration or video-first production; - you want to change one speaker without processing the others. Sound Forge can open multichannel files and perform mixes, but those features don't turn it into a clip-based multitrack session. For a complex episode, export a clean mix from the DAW, then finish that mix here. ## 1\. Preserve the recording and prepare the edit Keep the original recording untouched. Open the WAV or other lossless source, then save a working copy before destructive processing. Don’t convert to MP3 at the beginning: every lossy encode throws away information, and another encode at delivery compounds the loss. Confirm the sample rate and channel count before editing, and keep the native sample rate unless the host or production brief requires another one. A spoken-word source doesn't improve because it was resampled to a larger number. For a long interview, play once and press **M** wherever something needs attention: false start, repeated thought, cough, long pause or factual pickup. The current [Sound Forge 2026 marker help](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/insert%5Fmarker.htm) confirms that M inserts a marker during playback; markers can be renamed and reviewed in the Regions List. Use names such as “CUT repeat,” “CHECK name” and “KEEP quote.” Markers are editorial notes inside the working file. They do *not* automatically become chapter metadata in every podcast host, so build listener-facing chapters in the hosting platform or its supported metadata workflow. ## 2\. Edit content, pauses and boundaries Work from large decisions to small ones: 1. remove unusable starts, interruptions and repeated answers; 2. tighten pauses that feel accidental, without deleting every breath; 3. repair obvious clicks at edit boundaries; 4. add short fades where a cut creates an abrupt change in [room tone](https://soundforgepro.com/room-tone-sound-forge/). A podcast should still sound like people speaking. Removing every hesitation can make timing robotic and can expose room-tone jumps between edits. Leave the pause when it helps meaning; shorten it when a listener might think playback stopped. Zoom into difficult boundaries and cut where the waveform and the sound both support the edit. The [cut and trim guide](https://soundforgepro.com/how-to-cut-and-trim-audio-in-sound-forge-pro/) covers selections, zero-crossing snaps, event edges and fades. If a cut clicks, fix the boundary instead of hiding it under heavy noise reduction. ## 3\. Repair noise before EQ and loudness Use restoration only when the defect is audible. Steady HVAC, fan wash and hiss can respond to a clean noise print; clicks need click repair; electrical hum needs targeted diagnosis. One processor isn't the answer to every kind of noise. 1. Select a passage containing only the unwanted steady noise. 2. If your installation includes the classic **Noise Reduction** plug-in, open it from the Tools toolbar and capture a noise print. If it is absent, use the [installed-tool decision in the noise-reduction guide](https://soundforgepro.com/how-to-remove-background-noise-in-sound-forge-pro/) before processing; do not transfer noise-print steps to a different effect. 3. Extend the selection to the material that needs treatment. 4. Preview a conservative reduction against Bypass. 5. Stop when the noise no longer distracts, not when the meter looks empty. Metallic consonants, watery tails and pulsing room tone are reasons to stop and reassess. Excessive reduction or wanted audio in the noise print can cause them, but changing noise or an unsuitable algorithm can also defeat this approach. Back off, compare a cleaner profile, or choose a more targeted repair. The full [Sound Forge noise-reduction workflow](https://soundforgepro.com/how-to-remove-background-noise-in-sound-forge-pro/) separates broadband noise, hum, clicks and installed RX options. A noise gate is optional rather than a required podcast step. Use it only when low-level room tone between phrases is the real problem; a hard-closing gate can clip word endings and make every pause unnaturally dead. The [noise gate guide](https://soundforgepro.com/how-to-use-noise-gate-sound-forge-pro/) explains how to set the threshold from the recording instead of copying someone else’s number. ## 4\. Shape the voice with Modern Equalizer In Sound Forge 2026, add **Modern Equalizer** through the FX Plug-Ins menu or Plug-In Chain. The [current Boris FX help](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/modern%20equalizer.htm) documents up to eight bands, pass filters, shelves, peaking filters, a live spectrum, Output Gain, A/B memories and Bypass. Don't apply a fixed “podcast voice” curve to every speaker. A high-pass filter may help desk vibration or mic-stand rumble, but set too high it can thin a low voice. A cut in the low mids may reduce boxiness in one room and remove body in another, and a high shelf may add clarity or simply magnify hiss and mouth noise. Make one correction at a time. Use the analyzer to locate energy, then decide by ear. Match Output Gain so the processed and bypassed versions are equally loud; otherwise the louder version usually wins the comparison. The separate [Modern Equalizer guide](https://soundforgepro.com/how-to-use-equalizer-sound-forge-pro/) explains filter choice, Q and level-matched A/B without pretending one frequency fits every voice. ## 5\. Control dynamics without flattening speech Compression should make quiet phrases easier to follow and loud phrases less startling. It shouldn't pull breaths forward, exaggerate room noise or make every sentence hit with the same weight. Sound Forge’s [Wave Hammer](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/proonly/wave%5Fhammer-overview.htm) combines a classic compressor with a Volume Maximizer. Treat them as two decisions: - **Compressor:** control the loudest phrases while preserving natural consonants and sentence shape. - **Volume Maximizer:** catch remaining peaks only after the compression is stable. There is no universal ratio, threshold, attack or release for podcasts. The threshold depends on the recorded level; the timing depends on the speaker and room. Watch gain reduction, listen to the loudest sentence and a quiet sentence, then compare at matched output level. If the voice pumps or the room jumps forward between words, use less compression. For a repeatable show, save the tested EQ and dynamics as a Plug-In Chain preset, but keep restoration outside the default chain unless the noise is genuinely consistent from episode to episode. The [Plug-In Chain guide](https://soundforgepro.com/how-to-use-plug-in-chainer-sound-forge-pro/) covers order, presets and safe A/B checks. **Commit the processing before the final loudness check.** A chain opened through **View → Plug-In Chain** changes playback, not the underlying audio; the [real-time chain documentation](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/proonly/plug-in%5Fchainer.htm) explains that its effects are applied when saving. If you used that route, save or render a separate lossless processed file, then open it in a new data window and confirm its chain is empty or bypassed. Normalize and measure that processed file. If you already applied the effects to the audio with **FX Plug-Ins → Apply Plug-In Chain**, do not apply them again. Keep the source project or working copy for revisions. ## 6\. Normalize to the delivery specification Sound Forge 2026 can [normalize directly by loudness](https://soundforgepro.com/how-to-normalize-audio-in-sound-forge-pro/): choose **Process → Normalize → Loudness**, select the ITU‑R BS.1770/1771 option, then enter the integrated loudness, tolerance and maximum true-peak values required by the destination. You don't need to guess a gain change from the meter and push Wave Hammer until the number happens to match. For one authoritative target, [Apple Podcasts recommends](https://podcasters.apple.com/support/893-audio-requirements) overall loudness around **−16 dB LKFS ±1** and true peak no higher than **−1 dBFS**, calculated under ITU‑R BS.1770-5\. LKFS and LUFS describe the same loudness scale here. Use about −16 LUFS for the integrated target and a true-peak reading no higher than −1 dBTP; do not substitute a sample-peak meter for the true-peak check. That isn't permission to label −16 LUFS a law for every host. Check the current requirements of the service receiving the file, and don't repeat the old shortcut that mono must always be −19 LUFS. Apple’s current page gives one overall −16 LKFS recommendation and separate mono/stereo bitrate ranges; it does not state a mandatory −19 target for mono RSS audio. After normalization, select the complete episode, then run **Tools → Statistics** and verify integrated LUFS and true peak. Then save a test encode and check it again, because codec processing can change peaks. Sound Forge can also generate a loudness log during Save As/Render As; its [current Save As help](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/saving%5Fa%5Ffile%5Fas%5Fa%5Fdifferent%5Fname%5For%5Ftype.htm) notes that the render-time log is measured before the codec, so use **Tools → Generate Loudness Log** on the compressed file when you need post-encode values. ## 7\. Export a master and the upload file Save two deliverables: - **Archive master:** a lossless WAV at the approved sample rate and bit depth. - **Upload file:** the format and bitrate required by the podcast host. For RSS feeds, Apple accepts MP3 or AAC and currently recommends AAC in an MP4 container for efficient streaming and accurate seeking. At 44.1 or 48 kHz, its recommended ranges are **64–128 kbps for mono** and **128–256 kbps for stereo**. Those are ranges, and they aren't proof that every spoken-word file needs the maximum. [Spotify for Creators currently accepts](https://support.spotify.com/us/creators/article/publishing-audio-episodes/) MP3, M4A and WAV in mono or stereo for shows hosted there. Your RSS host may transcode the upload or impose its own format, artwork and metadata limits, so the host’s current specification wins. In Sound Forge, choose **File → Save As** for a sound file, or **Render As** when working from a Sound Forge project. Select the format and template, open Custom for codec settings, and preserve metadata only where the target format and host support it. The [MP3 export guide](https://soundforgepro.com/how-to-export-mp3-from-sound-forge-pro/) covers templates, bitrate modes, sample-rate conversion and post-encode checks. ## Podcast delivery checklist 1. Keep the untouched source and a lossless working copy. 2. Edit content and timing before restoration or tone shaping. 3. Repair only the defects you can identify. 4. Level-match EQ and compression comparisons. 5. Normalize from the receiving platform’s specification. 6. Verify integrated loudness and true peak on the complete file. 7. Reopen the upload file and audition its beginning, loudest passage and ending. Listen once outside the editing chair: phone speaker, ordinary earbuds or the device your audience actually uses. The final QA question is not “does the waveform look mastered?” It is “can I follow every word without reaching for the volume?” ## Frequently Asked Questions ### Can Sound Forge Pro edit a complete podcast? Yes, when the episode is one mono or stereo file. It can handle waveform edits, restoration, EQ, dynamics, loudness normalization and export. For separate guest tracks, complex music beds, collaboration or video, assemble the episode in a multitrack DAW first. ### What loudness should I use for a podcast in Sound Forge Pro? Use the receiving platform’s specification. Apple currently recommends about −16 dB LKFS ±1 and a true-peak ceiling of −1 dBFS; a true-peak meter commonly labels that reading −1 dBTP. In Sound Forge 2026, Process → Normalize → Loudness can use ITU‑R BS.1770/1771 targets, followed by a complete-file Statistics check. ### Should a mono podcast always be −19 LUFS? [No universal rule makes −19 LUFS mandatory](https://soundforgepro.com/podcast-loudness-standard/). Apple’s current audio requirements recommend overall loudness around −16 LKFS and publish separate mono/stereo bitrate ranges. Follow the host or client brief rather than an inherited forum number. ### Which EQ settings are best for a podcast voice? There is no universal curve. Remove only problems present in the recording, use Modern Equalizer’s analyzer as a clue, match Output Gain for bypass comparisons, and judge the result by ear. A copied high-pass or presence boost can thin one voice and exaggerate noise in another. ### Should noise reduction come before compression? Usually yes. Compression can raise room noise and make cleanup harder to judge. Edit first, repair identified noise, shape tone, control dynamics, then set final loudness. Keep an untouched source because aggressive restoration is destructive. ### Can markers in Sound Forge create podcast chapters? Markers are excellent internal navigation points for edits and can be named in the Regions List. Don’t assume they become listener-facing chapters automatically; create chapters through the podcast host or its supported metadata workflow. ### Is Sound Forge Pro better than Audacity for podcasting? Sound Forge suits a finished mono or stereo episode that needs file-based editing, analysis and delivery. Audacity can record, arrange and [mix separate speaker tracks](https://support.audacityteam.org/audio-editing/mixing-and-panning-tracks) in a free multitrack project. Choose the project model you need; more complex routing or video integration may justify another DAW or podcast application. For other recurring production jobs, the [Sound Forge workflow guides](https://soundforgepro.com/tag/workflows/) connect podcast editing with related file-based tasks. Once one episode passes QA, turn the repeatable parts into a controlled workflow: use [Statistics to verify loudness and true peak](https://soundforgepro.com/how-to-use-statistics-sound-forge-pro/), follow the [MP3 export and post-encode check](https://soundforgepro.com/how-to-export-mp3-from-sound-forge-pro/), then [batch-process finished episodes](https://soundforgepro.com/how-to-batch-process-files-sound-forge-pro/) only after the chain has been tested on different voices and noise conditions. *Last fact-checked: September 12, 2026 against Apple Podcasts, Spotify for Creators, and Sound Forge Pro 2026 help.* ### VST Plugin Chainer on Windows: Build and Save Chains in Sound Forge URL: https://soundforgepro.com/how-to-use-plug-in-chainer-sound-forge-pro/ Last updated: 2026-10-09T21:33:20.000Z A VST plugin chainer sends audio through several effects in order and lets you recall the setup. For an open audio file in Sound Forge Pro 2026, choose **View → Plug-In Chain**, add effects and compare playback with bypass. Save the result to a new audio file when it is ready. To process only a selection, use **FX Plug-Ins → Apply Plug-In Chain** instead. This guide is about processing recorded files; a live keyboard or guitar rig is a different setup. The built-in chain is serial, with no parallel lanes and no MIDI instrument routing. If you need those, the host alternatives below are a better place to start. For related finishing tasks, the [Sound Forge mastering hub](https://soundforgepro.com/tag/mastering/) groups the EQ, dynamics and measurement guides. The steps follow current Boris FX help; there was no hands-on compatibility test. For exact labels, go by the written menu and control names below. ## Is Sound Forge a VST plugin host? Yes, for effects on an open audio file. The [current Plug-In Chain help](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/proonly/plug-in%5Fchainer.htm) documents a serial rack of up to 32 DirectX/VST effects, real-time preview and saved order/settings. It's a file-processing workflow. It isn't a MIDI instrument rack. In this workflow, the open file passes through one effect and then the next. The built-in rack isn't a modular audio/MIDI router. A compatible wrapper can add routing inside a plug-in, but that's an extra tool; Sound Forge’s chain itself has no parallel-lane control. | If you need to… | Use this type of tool | Where Sound Forge fits | | -------------------------------------------------- | ------------------------------------------ | ------------------------ | | Clean, repair or finish one recorded file | Waveform editor with a serial effect chain | **Strong fit** | | Reuse a VST chain while editing several WAV files | File editor with chain presets | **Strong fit** | | Play VST instruments from a MIDI keyboard | DAW or standalone instrument host | Wrong tool | | Split one signal into parallel effect paths | Modular host, rack or DAW bus routing | Not built into this rack | | Process browser, game or meeting audio system-wide | System-audio router plus compatible host | Not a direct route | A chainer may be a standalone rack or a plug-in loaded inside another host. Here the job is narrower: change the sound of an existing recording, keep the effect settings reusable and write a checked output file. ## Choose the correct Sound Forge chain before adding effects Sound Forge exposes two workflows with similar names. A [MAGIX community question about how to apply a completed chain](https://www.magix.info/us/forum/solved-how-to-apply-plugins-from-plugin-chain-in-sound-forge-pro-15--1342941/) illustrates why the distinction matters. | Job | Command | Scope and commit behavior | | -------------------------------------------- | ------------------------------------- | ------------------------------------------------------------------------------------------------------------- | | Hear and adjust a chain across the open file | **View → Plug-In Chain** | Real-time playback; the waveform stays unchanged while you work; the chain is rendered when you save the file | | Render a chain into one selection or event | **FX Plug-Ins → Apply Plug-In Chain** | Processing dialog for the selected audio; click OK after previewing | The real-time window has no Apply or Process button. Normal playback is the preview. If only one phrase, click or noise burst needs processing, make the selection and use **Apply Plug-In Chain**. Don’t save a whole-file real-time chain just to repair a two-second defect. ## Build a VST effect chain in Sound Forge step by step ![Opening the Plug-In Chain in Sound Forge, ordering effects and comparing the stack against bypass](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/10/plugin-chainer-ui-order-bypass-v4-1-v20261005-v20261006.webp) The Sound Forge real-time rack sets serial order and bypass comparison; render to a new file only after the chain survives the A/B check. 1. **Protect the source.** Make a separate copy of the untreated audio before opening it for processing. Work on that copy; Save As with an active chain is not an untreated backup. 2. **Open Plug-In Chain.** Choose View → Plug-In Chain for the active data window. 3. **Add the first effect.** Click Add Plug-Ins to Chain, select an effect, click Add, then OK to close the chooser. 4. **Open the controls.** Select the effect and click Show Plug-In Window to adjust its parameters. 5. **Preview.** Use Play Normal and loop a representative passage containing both ordinary audio and the problem. 6. **Add only necessary stages.** Add the next processor only after you can identify what the first one improves. 7. **Set the order.** Drag the effect buttons, or use Shift Plug-In Left and Shift Plug-In Right. 8. **Bypass and compare.** Compare the full chain and individual effects at similar playback loudness. Use an output control in the chosen processor to compensate for added gain. 9. **Save the preset.** Type a descriptive name in the Chain box, then click Save Chain Preset. Recheck input-dependent thresholds on the next file. 10. **Render and verify.** Use File → Save As to write a new audio file. Reopen it without adding the chain again; confirm its playback chain is empty or bypassed. Check the start, loud and quiet passages, and ending. For a Sound Forge project, use File → Render As to produce the media file. ![Sound Forge Plug-In Chain with ExpressFX Noise Gate above ExpressFX Chorus and a drop line while a plug-in is dragged](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/10/sf-plug-in-chain-drag-reorder-v20261005.webp) Sound Forge Plug-In Chainer controls: drag an effect block to change which processor receives the signal first. Use **View → Plug-In Manager** if the chooser is crowded. Its category/type filters and search help locate an effect. Dragging an effect onto a data window [adds it to that window’s real-time chain](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/proonly/plug-in%5Fmanager.htm); double-clicking opens selection processing instead. Load saved racks from the Chain list. If an effect is absent, follow the [VST plug-ins not showing checks](https://soundforgepro.com/sound-forge-pro-vst-plugins-not-showing/) before changing configuration files. ## Choose an effect order you can explain Each processor receives the output of the preceding stage. If rumble is driving compression, try filtering it before the compressor, then check that the wanted bass remains intact. Reverb before compression can exaggerate room movement; EQ after limiting can create new peaks. For rhythmic effects, the [tempo-synced delay and reverb timing guide](https://soundforgepro.com/bpm-delay-reverb-time-guide/) converts note lengths to milliseconds. Tempo matching is a creative choice, not a requirement for every reverb. ![Three starting chain orders compared: voice cleanup, restoration and final limiting](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/08/vst-chain-order-guide.webp) Three starting chain orders in Sound Forge, not universal presets: fix the defect, shape tone and dynamics, then control the output. | Source | Useful starting order | Why it starts there | | --------------------- | ------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------- | | Voice-over | High-pass or corrective EQ → de-esser → compressor → limiter → loudness meter | Remove energy that should not drive compression; control peaks before measuring delivery level | | Noisy field recording | Hum/notch repair → noise reduction → corrective EQ → light dynamics → meter | Try cleanup before gain or compression makes remaining noise more noticeable | | Stereo music file | Corrective EQ → gentle compression → tonal EQ if needed → peak limiter → loudness/true-peak meter | Separate correction from polish and measure the signal after the final peak-producing stage | Treat these as diagnostic starting points rather than presets to paste onto every file. On a vocal, moving the de-esser before or after compression can change how hard it reacts; on a restoration job, a severe click may need a local repair before any real-time chain touches it. The [background-noise workflow](https://soundforgepro.com/how-to-remove-background-noise-in-sound-forge-pro/) separates constant hiss and hum from problems a gate handles better, while the [Noise Gate guide](https://soundforgepro.com/how-to-use-noise-gate-sound-forge-pro/) covers pauses and room tone without cutting word endings. ## Bypass at matched loudness, not by first impression A louder processed version can make the chain seem more useful than it is. Pull back any added output gain before comparing, then listen for the change you actually wanted: less rumble, clearer words or better-controlled peaks. Getting louder on its own doesn't count as an improvement. 1. Loop a short passage containing a normal section and a difficult moment. 2. Bypass the full chain and listen to the unprocessed level. 3. Re-enable it and use a processor’s output trim to bring the comparison close in loudness. The control name depends on the plug-in. 4. Bypass one effect at a time. Remove a stage if you cannot identify a useful contribution. Then check a second passage. A chain tuned on the loudest sentence may lift breaths in a quiet paragraph; a restoration chain tuned on a noisy gap may dull the wanted audio. The smallest chain that survives both checks is usually the safer preset. ## Preview, save and verify without damaging the source The View-based chain changes playback; the displayed source samples stay as they were. Saving an audio file applies it. A Sound Forge project works differently: Save As saves the project, while [Render As produces the media file](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/saving%5Fa%5Ffile%5Fas%5Fa%5Fdifferent%5Fname%5For%5Ftype.htm). So a waveform that doesn't change during preview doesn't mean the effect is off. Before delivering the result: 1. Keep the untreated recording separate. 2. Write a new output file with the required format settings. 3. Reopen that output and check it with an empty or bypassed playback chain. Don't load the processing preset onto audio that already has it baked in. 4. Listen to the first transient, loud and quiet passages, and the final decay. 5. Measure the reopened file against the delivery target, particularly after lossy encoding. If you use a [meter plug-in](https://soundforgepro.com/free-metering-plugins/), put it after the processing you want to measure. The [LUFS, EBU R128 and true-peak meter guide](https://soundforgepro.com/sound-forge-loudness-meters/) also covers Sound Forge’s separate metering displays. If Wave Hammer is your final dynamics processor, see the [compressor and maximizer workflow](https://soundforgepro.com/sound-forge-wave-hammer/), and measure its output instead of trusting its settings to prove the file is compliant. ## Process selections and effect tails deliberately Select the region first, then choose **FX Plug-Ins → Apply Plug-In Chain**. Use **Preview** to audition it and **OK** to process it. With no selection, processing can affect the whole file. The [Apply Plug-In Chain help](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/apply%5Ffx%5Fchain.htm) also describes tail handling for reverb and delay. | Tail mode | What Sound Forge does | Practical use | | ---------------- | ------------------------------------------------------------------ | ------------------------------------------------------------------ | | Ignore Tail Data | Stops the effect at the selection boundary | Only when a deliberately hard ending is acceptable | | Mix Tail Data | Blends the decay into the adjacent audio without moving it | Natural first choice for many partial repairs and ambience effects | | Insert Tail Data | Creates room for the full decay and moves later audio to the right | When preserving the complete tail matters more than fixed timing | Right-click the processing dialog to choose a tail mode. After processing, inspect the boundary: Mix can overlap the next word, Insert moves later audio, and Ignore can cut the decay abruptly. Use pre/post-roll to hear the transition, as described in [the processing-dialog controls](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/using%5Fprocessing%5Fdialogs.htm). For the effect settings themselves, follow the [reverb setup guide](https://soundforgepro.com/how-to-add-reverb-in-sound-forge-pro/). ## Save reusable presets without pretending every file is identical ![Plug-in Chain window with Vocals in the Chain box and the Save Chain Preset button highlighted](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/10/sf-plug-in-chain-save-preset-v20261005.webp) Saving a Sound Forge chain preset keeps the whole rack reusable — recheck thresholds and input-dependent settings on every new file. A chain preset stores the processors, their order and their settings. Name it by source and intensity rather than by a vague promise: “Podcast dynamic mic — light cleanup” is more useful than “Perfect Voice.” On the next recording, treat it as a starting point and reset thresholds that depend on input level. Individual effects may offer their own preset files, and those aren't the same as a complete chain preset. The help documents .fxp presets and .fxb banks for VST effects with those controls. Don't assume every VST format or vendor uses them. A chain preset also won't install the required plug-ins or carry their licenses to another machine. Chain presets leave out automation envelope points. Saving a preset during playback captures parameter values at the playback cursor rather than across the timeline. For an automatable effect, use **Show Parameters**: **Show Envelope** controls visibility, while **Enable Envelopes** controls whether automation runs. Hiding a line doesn't disable it. The [automation help](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/proonly/automating%5Feffects%5Fwith%5Fenvelopes.htm) also warns that loading a new chain preset clears current effect automation settings, so don't switch presets casually once you've drawn envelopes. ## Fix stutter, latency and unstable chains from the top down Separate two symptoms. Crackles or dropouts can mean real-time processing can't keep up, while a steady delay may come instead from a plug-in’s look-ahead or other latency. Lowering CPU load won't necessarily remove intentional processing delay. Try the suspect effect on a disposable copy before changing the whole setup. 1. Compare playback with the entire chain bypassed, then with an empty chain on a disposable copy. Bypass alone doesn't prove the plug-ins have nothing to do with a fault. 2. Close unused data windows after protecting any unsaved work. Reintroduce effects one at a time in processing order. 3. If one effect triggers the problem, check its own manual for quality, oversampling and latency options. Change one setting and compare again. 4. In a processing dialog, use a non-real-time preview if its Real-time option is available and playback cannot keep up. Check the preview-length limit in Preferences → Previews. 5. For a local repair, preview and apply a verified selection before moving on. Don't save a lower-quality result just because its preview plays smoothly. Latency matters differently in a file editor than in a live rig. Delayed playback is annoying, but Sound Forge still isn't a low-latency instrument host. If what you really want is to play guitar or a VST instrument through several effects, pick software built around live input, ASIO configuration and plug-in latency management. ## When a standalone or modular VST chainer is the better answer Use Sound Forge when the input is an audio file and the output is another audio file. When the job is routing, performance or portability between DAWs, pick a different host. - **For parallel chains and a commercial wrapper:** [Blue Cat PatchWork](https://www.bluecataudio.com/Products/Product%5FPatchWork/) supports serial and parallel racks, standalone operation and use as a plug-in inside compatible hosts. - **For a modular open-source graph:** [Kushview Element](https://kushview.net/element/) runs on Windows, macOS and Linux and routes audio and MIDI through reusable graphs. - **For a free multitrack editor with a real-time stack:** [Audacity’s real-time effects](https://support.audacityteam.org/audio-editing/using-realtime-effects) can be a better fit when the work already lives in an Audacity project. - **For full production:** use a DAW when the chain belongs on tracks, buses or sends alongside MIDI, arrangement and automation. For a finishing job, the better question is what the chain should achieve. How many effects it can hold matters far less. The [full Sound Forge mastering workflow](https://soundforgepro.com/sound-forge-pro-for-mastering/) covers baseline measurements, EQ, dynamics and delivery checks. ## Fast checks when a plug-in chain does not work ### The effects are audible, but the waveform does not change That is expected during View → Plug-In Chain playback. Save to a new audio file, or use Render As for a Sound Forge project, to produce the processed media. ### The chain changes the whole file instead of the selection You opened the real-time chain. Make the selection and use **FX Plug-Ins → Apply Plug-In Chain**. ### A VST effect is missing Open **Options → Preferences → VST Effects**, confirm the installation folder, click **Refresh** and enable the effect in the list. The [VST Effects preferences](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/vst%5Feffects%5Fpreferences.htm) also provide a generic editor for plug-ins with display problems. Check the installed format and architecture before attempting configuration resets. ### The saved file is clipped even though each effect looked safe A later EQ, saturator or gain stage may have created new peaks. Check after the complete chain, reduce gain before an overloaded stage and render again from the untreated source. If the source itself is clipped, seek a clean original first. The [clipped-audio repair guide](https://soundforgepro.com/fix-clipped-audio-sound-forge/) covers salvage attempts, not guaranteed recovery of the missing waveform. ### A reverb or delay is cut off For a processed selection, inspect the tail mode and the saved boundary. Mix blends into adjacent audio without shifting it; Insert makes room and moves later audio. Neither choice excuses skipping the playback check. ## Frequently asked questions ### What is a VST plugin chainer? It is a host or rack that passes audio through multiple [VST effects](https://soundforgepro.com/what-is-a-vst-plugin/) in a defined order and usually saves the complete setup as a preset. Some chainers are standalone applications; others live inside an editor or DAW. ### Can Sound Forge run VST plug-ins without a DAW? Yes, Sound Forge can host VST effects while editing an audio file, so a DAW is not required for that job. It is not intended to replace a live VST instrument host or modular performance rack. ### How many effects can the Sound Forge Plug-In Chain hold? The current Sound Forge 2026 documentation specifies up to 32 DirectX and VST effects in one chain. ### Where is the Process button? The real-time chain opened from View has no Process button. Playback previews it; saving an audio file applies it. Use Render As to produce media from a Sound Forge project, or FX Plug-Ins → Apply Plug-In Chain to process a selection. ### What is the best VST effect order? There is no universal order. If noise or rumble is causing a downstream problem, try repair before dynamics and compare. Place final peak control after stages that can create peaks, then measure its output. Remove unnecessary effects and compare at matched loudness. ### Does a Sound Forge chain preset save automation? It saves effects, order and parameter settings, but not automation envelope points. During playback it captures values at the playback cursor. Loading a different chain preset clears current effect automation settings. ### Can Sound Forge create parallel VST chains? Not inside the standard serial Plug-In Chain described here. Use a modular host, a wrapper with parallel lanes or DAW bus routing when the signal must split and recombine. ### Should I use Mix or Insert Tail Data? Start with Mix when a reverb or delay tail should blend into adjacent audio without changing timing. Choose Insert when the entire decay must be preserved and moving later audio is acceptable. Checked September 7, 2026 against the linked Boris FX help and host documentation. ### Sound Forge vs WaveLab 13: Which Should You Buy? URL: https://soundforgepro.com/sound-forge-pro-vs-wavelab/ Last updated: 2026-10-09T21:06:39.000Z Sound Forge 2026 and WaveLab Pro 13 can both edit a single audio file. The buying decision changes when the job grows beyond that file. Sound Forge keeps recording, repair, waveform editing and batch work direct. WaveLab Pro adds Audio Montage for sequencing titles, comparing references, managing metadata, analyzing a whole project and delivering DDP or Dolby Atmos masters. **Quick answer:** choose Sound Forge when most jobs begin and end with one file. Choose WaveLab Pro when the deliverable is an album, a set of related titles, a DDP image, a Dolby Atmos master, or a project that must move between Windows and macOS. The higher price doesn't make WaveLab automatically sound better; what it buys is project-level mastering infrastructure. Still choosing between an audio editor, a DAW and a repair suite? The [Sound Forge comparisons](https://soundforgepro.com/tag/comparisons/) cover those different buying decisions. This comparison focuses on file editing versus album mastering. ## WaveLab 13 vs Sound Forge 2026 at a Glance This comparison was rechecked September 12, 2026 against current product pages, manuals and system requirements. WaveLab 13.0.30, released July 22, remains the latest maintenance version on Steinberg's [current WaveLab 13 release-notes page](https://www.steinberg.net/wavelab/release-notes/13/). The table separates documented capabilities from buying judgment. | Decision point | Sound Forge 2026 | WaveLab Pro 13 | | --------------------- | -------------------------------------------------------------- | ------------------------------------------------------------------- | | Primary job | Precise file editing, recording, repair and batch work | Project and album mastering, analysis and delivery | | Editing model | Direct waveform editing plus non-destructive event mode | Audio Editor plus non-destructive Audio Montage | | Album-wide timeline | No documented Audio Montage equivalent | Yes: clips, tracks, references, metadata and output processing | | DDP delivery | Not documented in the current export list | Yes: write DDP from Audio Montage | | Dolby Atmos mastering | No dedicated Atmos montage documented | Yes: Master and Album montages | | Spectral repair | Waveform repair and broadband tools | Built-in Spectrum Editor | | Loudness scope | Precise peak and loudness metering | File, montage, title, clip and reference analysis with reports | | Batch processing | Yes | Pro Batch Processor; not included in Elements | | Platform | Windows 11 | Windows 10/11 and macOS | | Trial | 15 days | 60 days for Pro 13 | | Best fit | Dialogue, transfers, samples, cleanup and repeatable file jobs | Albums, DDP, references, cross-platform studios and Atmos mastering | ## What Sound Forge Pro Does Better Sound Forge stays close to the waveform. The [current Boris FX feature matrix](https://www.soundforge.com/sound-forge/pricing/) documents sample-level editing, familiar cut/copy/paste operations, precise peak and loudness meters, and an event-based mode for non-destructive edits. That is a good fit when the work is a dialogue take, a transfer, a sample, a finished mix or a folder of files rather than an album project. The same matrix documents broadband noise reduction, click and crackle removal, clipping repair, VST2/VST3 and ARA support, and batch processing. Boris FX also states that Sound Forge can record and edit files with up to 32 channels. Those are concrete reasons to choose it for file preparation; they aren't proof that it replaces a multitrack DAW or a montage-based mastering system. For repeated folder work, the [batch processing guide](https://soundforgepro.com/how-to-batch-process-files-sound-forge-pro/) shows the safer preset-and-audit workflow. WaveLab also opens and renders files directly in its [Audio Editor](https://www.steinberg.help/r/wavelab-pro/13.0/en/wavelab/topics/audio%5Ffiles%5Fediting/rendering%5Fmultiple%5Faudio%5Ffiles%5Ft.html); a montage is optional. For a one-file job, compare navigation, repair and export in both editors. Sound Forge’s file-focused design is a buying preference here, not a measured speed advantage. ![A single waveform in Sound Forge beside a WaveLab Audio Montage holding a full album](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/10/sound-forge-vs-wavelab-ui-workflow-20260802-v20261006.webp) Sound Forge keeps the job centered on one waveform; WaveLab Pro 13 adds Audio Montage for album order, metadata and delivery. For exact interface paths, use the linked Boris FX and Steinberg documentation. ## What WaveLab Pro Does Better [Audio Montage](https://www.steinberg.help/r/wavelab-pro/13.0/en/wavelab/topics/audio%5Fmontage/audio%5Fmontage%5Fc.html) is WaveLab Pro's defining advantage. Steinberg describes it as a multitrack and multichannel non-destructive environment. Clips reference source files, so montage edits, clip effects, track effects, fades and automation can remain attached to the project without changing those originals. That scope matters for an album or a group of related masters. Title order, gaps, crossfades, reference tracks, metadata, markers, processing and rendering live together. Sound Forge has non-destructive event editing, but current Boris FX material still presents it as a specialist for one audio file. What separates them is project organization rather than a simplistic destructive-versus-non-destructive split. WaveLab Pro 13 also provides a [Spectrum Editor](https://www.steinberg.help/r/wavelab-pro/13.0/en/wavelab/topics/spectral%5Fediting/spectral%5Fediting%5Fc.html). It is the more capable built-in choice when a fault must be isolated by time and frequency. Sound Forge keeps routine clicks, crackles, clipped peaks and broad noise problems inside its direct waveform workflow; the [noise reduction guide](https://soundforgepro.com/how-to-remove-background-noise-in-sound-forge-pro/) covers that file-centered route. ## DDP, Albums and Dolby Atmos WaveLab Pro 13 has an exact, current [procedure for writing an Audio Montage to a DDP image](https://www.steinberg.help/r/wavelab-pro/13.0/en/wavelab/topics/writing%5Foperations/audio%5Fmontage%5Fto%5Fddp%5Fwriting%5Ft.html): open the Album window, choose Functions > Write Audio CD or DDP, select DDP Image, set the destination and write the package. [Sound Forge's current export-format list](https://www.soundforge.com/sound-forge/system-requirements/) does not list DDP export. That makes WaveLab the defensible choice when a replication plant specifically requests DDP. It doesn't make DDP a universal requirement, though. If the client wants final WAV files for digital distribution, judge the editors by the actual delivery specification instead of paying for an unused format. WaveLab Pro 13 also adds Dolby Atmos Master and Album montages, ADM rendering and dedicated Atmos analysis and album tools. Those features matter only when the input and deliverable are part of an Atmos workflow; they're not generic evidence that a stereo file will sound better. ## Metering, Analysis and Reference Tracks Sound Forge documents precise peak and loudness metering for its editing workflow. WaveLab Pro can [analyze an audio file or a whole montage](https://www.steinberg.help/r/wavelab-pro/13.0/en/wavelab/topics/audio%5Fanalysis/analyzing%5Floudness%5Ft.html), including selected clips, titles, title groups and reference tracks, then return a report. Its [reference-track system](https://www.steinberg.help/r/wavelab-pro/13.0/en/wavelab/topics/audio%5Fmontage/reference%5Ftrack%5Fc.html) supports A/B comparison with up to three stereo references. This is where WaveLab earns its extra complexity. Several titles, their references and their measurements can stay attached to one project. Sound Forge is still sufficient when the delivery is one file and the required values are checked there. For a practical single-file chain, use the [Sound Forge mastering workflow](https://soundforgepro.com/how-to-master-a-track-in-sound-forge-pro/). For broadcast work, [EBU R 128 specifies a program target of -23 LUFS](https://tech.ebu.ch/publications/r128) and treats true peak as a separate measurement. That doesn't turn -23 LUFS into a universal music-streaming target. In either editor, use the values in the broadcaster, label or platform specification you were actually given. ## Platform and System Requirements [Boris FX lists Windows 11](https://www.soundforge.com/sound-forge/system-requirements/) for Sound Forge 2026\. [Steinberg's current WaveLab Pro 13 table](https://www.steinberg.net/wavelab/compare-editions/) lists 64-bit Windows 11 version 24H2 or later, Windows 10 version 22H2 or later, and macOS Tahoe, Sonoma or Sequoia. It lists both native Apple silicon and Rosetta 2 applications. The practical result is simple: a current Mac purchase points to WaveLab. On Windows, test the actual audio driver, plug-ins, display scaling and session files on the machine you'll use. A supported operating system is necessary, but it won't guarantee that every third-party plug-in or interface driver in an old setup behaves correctly. ## Price, Trials and WaveLab Elements For a dated US price reference, [Boris FX's March 30, 2026 launch announcement](https://blog.borisfx.com/press/boris-fx-acquires-vegas-pro-sound-forge-and-acid-pro) listed Sound Forge at $299.95 perpetual, $149.95 per year or $24.95 per month. Steinberg's [WaveLab product listing](https://www.steinberg.net/wavelab/) advertises Pro 13 at $499.99 and [Elements 13](https://www.steinberg.net/wavelab/elements/) at $99.99\. Treat these as reference prices, not a checkout quote: the Steinberg prices were available through its indexed product pages, while the current Sound Forge page did not expose a numeric offer in this check. Compare region, tax, upgrade eligibility and any promotion in the final cart. The [Sound Forge license guide](https://soundforgepro.com/sound-forge-pro-pricing/) explains the plans. WaveLab Elements is not a cheap substitute for every Pro workflow. Steinberg's [current edition comparison](https://www.steinberg.net/wavelab/compare-editions/) marks its Audio Montage as limited and omits DDP support, Project Manager, reference-track automatic loudness compensation, offline loudness reports and the Pro Batch Processor. Elements can be sensible for lighter file and montage work, but those omissions remove several reasons this comparison recommends WaveLab Pro. Don't buy from a table alone. [WaveLab Pro 13 has a 60-day trial](https://www.steinberg.net/wavelab/trial/); Sound Forge offers a 15-day fully functional trial. Use one real source and one real deliverable. In Sound Forge, time navigation, repair, plug-in preview and batch or single-file export. In WaveLab, import several titles, set gaps and metadata, add a reference, run loudness analysis and create the delivery files the client requires. ## Which One Should You Buy? When using both editors, decide the [intermediate precision and final dither stage](https://soundforgepro.com/sound-forge-bit-depth-dither/) before the handoff. A floating-point intermediate can avoid an unnecessary integer quantization between processing stages. **Buy Sound Forge 2026** if most work is file-centric: recording a take, trimming and repairing dialogue, preparing samples, cleaning transfers, finalizing one mix or processing a folder. Its documented perpetual launch price is below the WaveLab Pro reference price; use the trial to decide which editor feels easier for your actual work. **Buy WaveLab Pro 13** if the deliverable is project-centric: an album sequence, shared processing, title metadata, reference comparison, project-wide loudness analysis, DDP, Dolby Atmos, or a workflow that must run on macOS. Its advantage is the managed mastering environment around the files. If restoration is the main job, compare the same damaged passage with [iZotope RX](https://soundforgepro.com/sound-forge-pro-vs-izotope-rx/). If the missing requirement is multitrack production rather than mastering delivery, the [REAPER comparison](https://soundforgepro.com/sound-forge-pro-vs-reaper/) is the more relevant next decision. ## Frequently Asked Questions ### Is WaveLab Pro better than Sound Forge Pro for mastering? WaveLab Pro 13 is the stronger choice for an album or multi-title master because Audio Montage keeps sequencing, crossfades, metadata, reference tracks, loudness analysis and DDP delivery in one project. Sound Forge 2026 is the leaner choice for mastering or repairing individual files. The better tool depends on whether the deliverable is one file or a managed set of titles. ### Can WaveLab run on Mac if Sound Forge cannot? Yes. Steinberg lists WaveLab Pro 13 for Windows and macOS, including native Apple silicon support. Boris FX lists Windows 11 for Sound Forge 2026\. A current Mac workflow therefore points to WaveLab or another supported Mac editor. ### What is Audio Montage in WaveLab, and does Sound Forge have it? Audio Montage is WaveLab's non-destructive multitrack and multichannel mastering environment. It can hold clips, processing, fades, references, metadata, title markers, analysis and project output without altering the source files. Sound Forge has non-destructive event editing, but its current documentation does not describe an equivalent album-wide montage. ### Does Sound Forge Pro have DDP export? The current Sound Forge 2026 export-format list does not document DDP output. WaveLab Pro 13 has an explicit procedure for writing an Audio Montage to a DDP image. If a replication plant requests DDP, verify that requirement before buying and use a documented DDP-capable delivery tool. ### Which is cheaper: Sound Forge Pro or WaveLab Pro? At the documented US reference prices, Sound Forge's $299.95 perpetual launch price is lower than WaveLab Pro 13's $499.99 listing. WaveLab Elements 13 is listed at $99.99 but omits several Pro mastering features. Sound Forge's figures come from the March 2026 launch announcement; these are not guaranteed current checkout prices. Compare the final regional cart and the cost of the license type you need. ### Can Sound Forge Pro and WaveLab be used together? Yes. A sensible handoff is to edit, repair, record or batch-process individual files in Sound Forge, then assemble the approved files in WaveLab for sequencing, shared processing, metadata, loudness reports and DDP delivery. Use an uncompressed PCM or floating-point WAV intermediate that both setups support, keeping the source sample rate unless the project requires conversion. After processing, choose suitable intermediate precision rather than automatically returning to the original integer depth. Plan dither once at the final integer quantization. ### Which has better restoration tools: Sound Forge Pro or WaveLab? Sound Forge 2026 documents broadband noise reduction, click and crackle removal, and clipping repair in a direct waveform workflow. WaveLab Pro 13 adds a Spectrum Editor for frequency-specific repair. Sound Forge is a practical fit for routine file cleanup; WaveLab has the built-in advantage when the fault needs spectral selection or must stay inside a larger mastering project. *Fact-checked September 12, 2026 against current Boris FX Sound Forge pages, WaveLab 13.0.30 documentation and release notes, Steinberg's edition and trial pages, and EBU R 128.* ### iZotope RX 12 vs Sound Forge 2026: Which Do You Need? URL: https://soundforgepro.com/sound-forge-pro-vs-izotope-rx/ Last updated: 2026-10-09T21:04:07.000Z Sound Forge Pro and iZotope RX 12 solve different parts of the same job. Sound Forge is the Windows editor: record, cut, fade, process, batch-convert and deliver a finished file. RX is the [specialist repair toolkit](https://soundforgepro.com/audio-restoration-software/): remove difficult noise, isolate dialogue and repair damage in a spectrogram. If routine cleanup is all you need, Sound Forge may be enough. Test RX Standard when you need to select damage by both time and frequency, or when a specialist module such as Dialogue Isolate solves a problem your current tools do not. Choosing a different kind of editor? The [Sound Forge comparisons hub](https://soundforgepro.com/tag/comparisons/) separates restoration, mastering and multitrack alternatives. **Checked September 12, 2026**[Boris FX acquired iZotope on July 2, 2026](https://blog.borisfx.com/press/boris-fx-acquires-izotope-the-award-winning-leader-in-intelligent-audio-technology), three months after acquiring Sound Forge from MAGIX. Boris says iZotope remains a separate business unit and existing products, licenses and subscriptions remain active. Shared ownership does not include RX with Sound Forge; the current offers are still separate. ## iZotope RX 12 vs Sound Forge 2026 at a Glance This table compares the current Sound Forge 2026 base edition with RX 12 Elements and RX 12 Standard. [RX 12.0.0 was released on April 28, 2026](https://www.izotope.com/pages/release-notes/rx-advanced) and remains the current major release on the official product and release-notes pages checked September 12, 2026\. Older Sound Forge licenses may carry separate RX entitlements, but the current purchase decision should be based on the products listed now rather than on a 2024 bundle. | Decision point | [Sound Forge 2026](https://www.soundforge.com/sound-forge/pricing/) | RX 12 Elements | [RX 12 Standard](https://www.izotope.com/products/rx-advanced?tab=features) | | --------------------------------------------------------------------- | ------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------- | | **Primary role** | Single-file waveform editor | Six repair plug-ins | Repair suite with standalone Audio Editor | | **Routine noise cleanup** | Documented broadband noise reduction | Voice De-noise and De-hum | Spectral De-noise, Voice De-noise, De-hum and more | | **Clicks / crackle** | Documented click/crackle removal | De-click | De-click, De-crackle and Mouth De-click | | **Clipping repair** | Documented clipping repair | De-clip | De-clip | | **Time-frequency repair canvas** | No | No | Yes: [Spectral Repair](https://izotoperx.net/izotope-rx-spectral-repair/) in RX Audio Editor | | **Dialogue Isolate** | No | No | Yes | | **Music Rebalance** | No | No | Yes | | **Repair Assistant** | No | Yes | Yes | | **Standalone editor** | Yes: Sound Forge itself | No | Yes: RX Audio Editor | | **Platform** | Windows 11 | Windows 10 22H2 / 11 24H2; macOS Sonoma, Sequoia or Tahoe—check the exact supported point release | Windows 10 22H2 / 11 24H2; macOS Sonoma, Sequoia or Tahoe—check the exact supported point release | | **USD reference price: Sound Forge March launch; RX checked Sep. 12** | $299.95 perpetual; $149.95/year; $24.95/month | $99 | $399 | | **Free evaluation** | 15 days | 10-day evaluation; RX Standard trial export is disabled | | Check the exact OS build before installing RX. The [RX 12 release notes](https://www.izotope.com/pages/release-notes/rx-advanced) list macOS 14.7, 15.7 and 26.4, while the product page currently lists Tahoe 26.2\. That discrepancy is not a promise that every intervening or newer release is supported. ## Where Sound Forge Fits: Editing and Delivery Sound Forge Pro is a full audio editor. The [full feature list](https://www.soundforge.com/sound-forge/) centers on editing and delivery: it records, edits at sample level, normalizes, runs effect chains, handles batch processing and exports finished files. RX Standard also has recording and monitoring, but its standalone Audio Editor is built around restoration rather than Sound Forge's conventional waveform-editing workflow. For everyday cuts, fades, conversion and final delivery, Sound Forge is the practical home base. ![Waveform-editing and spectral-repair workflow for Sound Forge and RX](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/10/sound-forge-vs-rx-ui-workflow-20260802-v20261005.webp) Edit the file, repair isolated damage, then deliver. RX also supports ordinary editing and export. The [current Sound Forge feature page](https://www.soundforge.com/sound-forge/pricing/) documents broadband noise reduction, click/crackle removal and clipping repair, and the [2026 effects manual](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/applying%5Feffects.htm) also names DeClicker/DeCrackler, DeClipper and DeHisser. These are not reasons by themselves to buy RX. Start by trying the repair tools already available in your installation. Use the [background-noise workflow](https://soundforgepro.com/how-to-remove-background-noise-in-sound-forge-pro/), [click-removal workflow](https://soundforgepro.com/how-to-remove-clicks-pops-sound-forge-pro/) and [clipping-repair workflow](https://soundforgepro.com/fix-clipped-audio-sound-forge/) to test each problem conservatively. Work on a copy or save a new version before destructive processing; no repair tool can reconstruct detail that was never captured. ## What RX Does That Sound Forge Pro Doesn't The decisive gap is spectral repair. Base Sound Forge does not provide RX's time-frequency canvas, where you can select only the damaged band at the exact moment it occurs. RX Standard includes Spectral Repair and a standalone Audio Editor: mark a short squeak, ring, click cluster or other isolated event in the spectrogram, then attenuate or replace that region while leaving more of the surrounding signal untouched. That is a different class of control from applying a broadband process to the whole selection. RX 12 Standard also includes the Spectral Editor ARA plug-in, but the host details matter. The [current RX 12 release notes](https://www.izotope.com/pages/release-notes/rx-advanced) list AU ARA for Logic Pro 10.7+ on Mac in Rosetta and VST3 ARA for Studio One 7 and Studio Pro 8\. Pro Tools has a separate distribution path: Avid documents RX Spectral Editor 11.1 and later for Pro Tools 2024.6 and later, included with paid Pro Tools versions. That Avid-provided ARA integration should not be confused with the AU/VST3 ARA host list in the RX retail release notes. Sound Forge supports ARA generally, but iZotope does not list it as a confirmed Spectral Editor ARA host. Trial the exact workflow before buying. For that Pro Tools workflow, check [Avid’s RX Spectral Editor compatibility table](https://kb.avid.com/pkb/articles/en%5FUS/Knowledge/Pro-Tools-ARA-2-Supported-Plugins) and your Avid downloads. It does not establish compatibility between the retail RX Spectral Editor and Sound Forge. Dialogue Isolate starts with RX 12 Standard. It is designed for speech mixed with changing background sound or room ambience, where a stationary noise profile is the wrong model. Sound Forge's broadband noise reduction is better suited to repeatable noise for which you can capture a representative sample. Neither process is automatic magic: strong settings can damage consonants and room tone, so preview short passages and compare level-matched results. Mouth De-click also starts with RX 12 Standard. Its controls are tuned for lip smacks and saliva clicks in dialogue, while a general De-click tool must cover a wider range of transients. That narrower job can save setup time on voice-over and audiobook sessions, but it still needs auditioning: an aggressive pass can mistake useful articulation for noise. ## RX Elements, Standard, or Advanced? Don’t treat RX as part of every Sound Forge license. A [Japanese Sound Forge Pro 18 release notice](https://www.sourcenext.co.jp/pressrelease%5Fhtml/JS/2024/2024051601) explicitly documented RX 10 Elements and Ozone 11 Elements in that 2024 package. The current [Sound Forge 2026 pricing page](https://www.soundforge.com/sound-forge/pricing/) lists the native restoration tools and Plus extras, but not RX. If you upgraded from a MAGIX-era license, check your account for an existing RX serial; if you are buying now, budget for RX separately unless the checkout page explicitly includes it. RX 12 Elements is a six-plugin pack: De-click, De-clip, De-hum, De-reverb, Voice De-noise and Repair Assistant. It does not include the standalone RX Audio Editor, Spectral Repair, Dialogue Isolate, Mouth De-click or Music Rebalance. Standard is the edition to test if the standalone editor or those specific repair tools are what you need. The [current RX 12 module comparison](https://www.izotope.com/products/rx-advanced?tab=features) reserves Scene Rebalance, Trim Silence, Ambience Match, Dialogue Contour, EQ Match and De-rustle for Advanced, so that edition needs a post-production business case rather than a generic 'more tools' argument. The upgrade trigger is the material, not the feature count. Elements supplies modules for routine clicks, clipping, hum, reverb and voice noise, but confirm that the exact modules scan and render correctly in your Sound Forge build before buying. Choose Standard when you need to draw on a spectrogram, isolate dialogue, repair mouth noise efficiently or rebalance a finished mix. Choose Advanced only if an exclusive module solves a recurring problem; paid work alone is not a reason to upgrade. For a module-by-module split, see the [RX 12 Elements vs Standard vs Advanced breakdown](https://izotoperx.net/izotope-rx-elements-vs-standard-vs-advanced/). ## Price and the Upgrade Decision [Boris FX's March 2026 pricing announcement](https://blog.borisfx.com/press/boris-fx-acquires-vegas-pro-sound-forge-and-acid-pro) lists Sound Forge at $299.95 perpetual, $24.95 monthly or $149.95 annually. Sound Forge Plus is $399.95 perpetual. Those prices do not establish an RX entitlement; the current Sound Forge feature table does not list RX among either edition's included extras. At the list prices checked September 12, 2026, the [current RX edition chart and prices](https://www.izotope.com/products/rx-advanced?tab=features) show Elements at $99, Standard at $399 and Advanced at $1,399\. Elements is plug-ins only; Standard adds the standalone editor and the core spectral/dialogue tools; Advanced adds the deepest post-production set. iZotope's [current RX Standard download page](https://www.izotope.com/pages/product-downloads/rx-standard) describes a ten-day trial with export disabled; after that, Demo mode inserts periodic silence. Use previews to evaluate the standalone workflow rather than expecting a trial export. Sale and upgrade prices change, so compare the live checkout price with the exact module you need. A practical test is cheaper than guessing. Put the worst 30–60 seconds of a real project through the ten-day RX trial and compare previews at matched loudness; the standalone trial has export disabled. If Spectral Repair or Dialogue Isolate produces a clearly cleaner result than Sound Forge's documented repair features, Standard has a defensible job. If the improvement disappears in a level-matched comparison, keep the money. The sensible order is Sound Forge's documented base repair features first, RX Elements only if its six quick-repair plug-ins fill a real gap, and RX Standard when the standalone spectral workflow becomes necessary. For clean music editing and light vinyl cleanup, Standard may be overkill. For recurring location dialogue, podcast rescue or audiobook mouth-noise work, Standard is usually the edition worth testing. Advanced needs a module-by-module business case. ## Using RX as a Plugin Inside Sound Forge Pro [Sound Forge's current VST3 support](https://www.soundforge.com/sound-forge/pricing/) and RX 12's VST3 plug-ins make an in-editor workflow technically possible on Windows. However, [RX 12's confirmed host list](https://www.izotope.com/products/rx-advanced?tab=features) does not name Sound Forge, so this is a test-required path rather than an official compatibility guarantee. Use the RX trial, confirm that the required modules scan and preview, process a disposable copy and verify undo before relying on the combination for deadline work. Keep the simple jobs in Sound Forge. Load De-click, Voice De-noise or Mouth De-click as plug-ins for selection-based passes, then save to a new version. When a repair needs drawing, comparing alternate selections or building a longer module chain, open a copy in the RX standalone editor and return the repaired file to Sound Forge for the final edit and export. Compatibility deserves a test, especially with old RX licenses. A [March 2026 magix.info troubleshooting thread](https://www.magix.info/us/forum/rx-vst-plugin-issues--1352573/) reports RX 10 plug-ins failing in Sound Forge 16 while the same plug-ins worked in the Sound Forge 18 trial. The author’s final update says the plug-ins also began working again in Sound Forge 16, without an established cause. This is a troubleshooting report, not evidence that SF16 is incompatible or that upgrading fixes the problem. Test your exact versions; do not copy executables between installations based on that thread. Use RX standalone for the work that depends on its editor: spectral selections, repeated comparison, module chains and detailed navigation. Use plug-ins for targeted passes that fit inside the Sound Forge edit. This split also gives you a clean rollback point: keep the original, the RX-repaired intermediate and the final Sound Forge master as separate files. If mastering and album delivery matter more than repairing damaged recordings, the [Sound Forge versus WaveLab comparison](https://soundforgepro.com/sound-forge-pro-vs-wavelab/) is the next useful choice. For an RX plug-in workflow inside Sound Forge, follow the [Plug-In Chainer setup](https://soundforgepro.com/how-to-use-plug-in-chainer-sound-forge-pro/) after checking compatibility. ## Frequently Asked Questions ### Does Sound Forge Pro include iZotope RX? Do not assume so. Some MAGIX-era Sound Forge Pro 18 packages included RX 10 Elements; a 2024 Japanese release notice documents that bundle. The current Sound Forge 2026 feature table does not list RX for Sound Forge or Sound Forge Plus. Check the exact checkout offer and your existing account. RX 12 Elements, when bought separately, includes six plugins but not the standalone RX Audio Editor. ### Is iZotope RX better than Sound Forge Pro for noise reduction? Sound Forge's broadband noise reduction is a good first tool for steady noise with a representative sample. RX 12 Standard is the stronger fit for changing ambience, difficult dialogue and repairs that need a time-frequency selection or modules such as Dialogue Isolate and Spectral Repair. Preview both on the same passage; aggressive noise reduction in either product can damage speech and room tone. ### Can I use iZotope RX inside Sound Forge Pro? Sound Forge 2026 and RX 12 both support VST3 on Windows, so individual RX VST3 plug-ins can work in Sound Forge. However, iZotope's current confirmed-host list does not name Sound Forge. Trial the exact versions before buying, verify that the required plug-ins scan, preview, render and undo correctly, and use RX standalone for spectral selections and longer repair chains. ### What does iZotope RX Standard have that Sound Forge Pro doesn't? RX 12 Standard adds the standalone Audio Editor, Spectral Repair, Dialogue Isolate, Mouth De-click, Music Rebalance, Spectral De-noise and a broader module set. Repair Assistant is not a Standard-only advantage because RX 12 Elements includes it too. The biggest gap is RX's time-frequency repair workflow, not ordinary cutting, fading or export. ### Should I buy iZotope RX if I already have Sound Forge Pro? Start with Sound Forge's documented base repair features. Test RX 12 Standard when real projects require Dialogue Isolate, Mouth De-click, Music Rebalance or manual spectral repair. RX Elements is cheaper but has no standalone editor. Ignore old sale-price promises and compare the live price with the module you actually need. Choose Advanced only when a specific exclusive module solves a recurring problem that Standard cannot. ### Is Sound Forge Pro Windows only compared to iZotope RX? Yes. Sound Forge 2026 is Windows-only. RX 12 supports current Windows and macOS versions listed by iZotope. On a Mac, pair RX with a compatible editor or DAW rather than planning a Sound Forge workflow. Always check the current operating-system and plug-in-host requirements before buying. ### Convert Audio in Sound Forge: WAV, FLAC & MP3 (2026) URL: https://soundforgepro.com/how-to-convert-audio-files-sound-forge-pro/ Last updated: 2026-10-09T11:07:34.000Z **To convert one audio file in Sound Forge, open it and choose File → Save As.** Pick the destination format in *Save as type*, choose the output template, give the file a new name, and save. For a folder or a set of files, use **Tools → Batch Converter**, add the sources, add an export format, open **Options** to choose a separate output folder, and run representative test files before the full job. Keep an untouched source and decide what the recipient needs before choosing a template. A file can have the right extension but the wrong sample rate, channel layout or metadata. **Sound Forge 2026 documentation.** This guide follows the current Boris FX [Save As/Render As help](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/saving%5Fa%5Ffile%5Fas%5Fa%5Fdifferent%5Fname%5For%5Ftype.htm), [Custom File Templates help](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/templates.htm) and [Batch Converter help](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/proonly/the%20batch%20converter.htm). Use the controls described below for the 2026 interface; older versions may arrange them differently. Boris FX lists [batch processing as a core Sound Forge feature](https://www.soundforge.com/sound-forge/pricing/) in both the base and Plus tiers. ## Save As or Batch Converter? | Your job | Use | Menu path | | ----------------------------------------- | ----------------- | ----------------------------- | | Convert one open file | Save As | File → Save As | | Convert many files to one or more formats | Batch Converter | Tools → Batch Converter | | Change only sample rate | Resample | Process → Resample → Resample | | Change mono/stereo channel structure | Channel Converter | Process → Channel Converter | Use Save As when a file needs individual attention. Batch Converter is useful when several sources share an output specification; separate files that need different treatment rather than forcing them through one preset. ## How to convert one audio file with Save As 1. Open the source file in Sound Forge. 2. Choose **File → Save As**. 3. Choose a separate output folder and a new filename; check the final extension after selecting the format. 4. Open **Save as type** and select the required format. 5. Choose a **Template** that matches the delivery specification. 6. Save to a new file, not over the source. 7. Reopen the export and verify its properties and playback. ![The Save As dialog in Sound Forge with WAV, FLAC, MP3 and AIFF available](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/10/convert-ui-save-as-v1-v20261006.webp) Converting one file in Sound Forge: the container lives in Save as type, the encoding details live in the selected template. For a normal audio data window, use Save As. If the open document is a Sound Forge project file, the current help says to use **Render As** to commit its edits to a media file. The exact entries in *Save as type* can vary by Sound Forge build and installed components. The current [supported-format table](https://www.soundforge.com/sound-forge/system-requirements/) lists WAV, FLAC, MP3 and AIF export. Check the dropdown and template options in your installed copy for the exact choices. ### WAV: uncompressed PCM delivery Choose WAV when a client, DAW, video editor, archive or mastering engineer asks for uncompressed PCM, and pick an uncompressed PCM template if that's what the recipient wants, since the WAV extension alone doesn't specify a codec. The container doesn't fix sample rate or bit depth either, so check the template instead of assuming every WAV is the same. If the file is going back to a video timeline, use the [Vegas round-trip workflow](https://soundforgepro.com/sound-forge-vegas-pro-workflow-video-editors/) so you edit the intended event or copy and save it back where VEGAS expects it. ### FLAC: lossless compression for compatible PCM Choose FLAC when the receiver accepts it and you want lossless compression. The [official FLAC project](https://xiph.org/flac/faq.html) defines the format as lossless: decoding rebuilds the original PCM data. That holds when compatible integer PCM samples are kept without resampling, processing or bit-depth reduction. FLAC doesn't natively store floating-point samples, so a float WAV won't automatically make a bit-perfect FLAC conversion. Keep the float original. How much space you save depends on the audio. ### MP3: delivery copy, not working master MP3 is the pick when compatibility or a delivery requirement specifically calls for it. MP3 is lossy, so its encoder removes information. Keep the WAV or FLAC source and create the MP3 at the end of the workflow. The [Sound Forge MP3 export guide](https://soundforgepro.com/how-to-export-mp3-from-sound-forge-pro/) covers template selection and final-file checks in more detail. ## What conversion can—and cannot—preserve ![Output-format panel over a Sound Forge waveform: WAV/AIFF uncompressed, FLAC lossless, MP3 lossy; keep the original and export lossy only at delivery](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/10/convert-ui-lossless-lossy-v1-v20261006.webp) WAV, FLAC and MP3 in Sound Forge: lossless conversion preserves the decoded audio; a second lossy encode never restores what the first removed. The figure sums up the format choices. Here's what changes in each direction: - **WAV → FLAC is lossless** when compatible integer PCM sample values, sample rate and channels are preserved. FLAC → PCM WAV can preserve those same samples too. - **MP3 → WAV is not restoration.** The new WAV stores the decoded MP3 as PCM, and whatever the MP3 already threw away stays gone. - **MP3 → MP3 is another lossy encode.** If all you have is MP3, edit it once and make one final export. Don’t bounce through repeated MP3 generations. Saving a compressed source as WAV before editing can make sense as a working file, because later saves no longer add MP3 compression. It doesn't make that source lossless after the fact. Lossless audio also doesn't guarantee that every marker, artwork field or WAV metadata chunk survives a format change, so check those separately. ## How to batch-convert multiple audio files 1. Choose **Tools → Batch Converter**. 2. Under **Files to Process**, review automatically added open files, then use **Add** or **Add Folder** for the rest. 3. For format-only conversion, leave the **Processing** list empty and make sure no Watermark file is selected. 4. Under **Export Formats**, choose the required Renderer and Template; use **Edit** when a custom file template is needed. 5. Open **Options** and choose an output folder separate from the sources plus a safe filename rule. 6. Select only two representative test files, including an edge case if the inputs differ. Uncheck the rest of the queue, then click Run Job. 7. Open and verify the pilot outputs. Then select the remaining intended sources and click **Run Job**. ![Many files queued in the Sound Forge Batch Converter with export templates ready](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/08/batch-converter-2026-processing-export-run-job-v2.webp) The Sound Forge Batch Converter keeps source files, processing, renderer templates and output rules separate — test the job before Run Job. The example above includes a compressor and Normalize in its **Processing** list. Don't copy that chain when all you need is conversion. For plain WAV-to-FLAC or WAV-to-MP3, leave the list empty, and add a process preset only when every source needs the same confirmed operation. Check the Watermark section too: a selected watermark file gets mixed into the output, so it has no place in a conversion that should leave the audio unchanged. The current help also warns that **Add Folder** adds files from the selected folder but skips its subfolders, and **Preserve source subfolders** only shapes the output layout without collecting nested inputs. Sound Forge can produce more than one export format from the same job, which helps when the same sources need a lossless archive and a delivery copy. Set up each export format separately, leave the sources untouched, and inspect one output from each format before you release the batch. For reusable effect chains, naming and bigger production jobs, see the separate [Batch Converter walkthrough](https://soundforgepro.com/how-to-batch-process-files-sound-forge-pro/). It explains how to build and validate a processing chain once conversion alone isn't enough. ## Format, sample rate and bit depth are separate decisions Encoding WAV audio as FLAC changes how it's stored. Renaming `.wav` to `.flac` doesn't convert anything. Moving 48 kHz audio to 44.1 kHz is sample-rate conversion, and going from 24-bit PCM to 16-bit PCM is a bit-depth change. All of these can happen in one delivery workflow, but they're different operations. ![Resampling during conversion in Sound Forge, with the rate-only option deliberately left off](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/10/resample-2026-target-phase-rate-only-verify-v2-1-v20261005-v20261006.webp) Resampling in Sound Forge: change the rate only when the audio needs it, leave rate-only disabled, then choose the delivered container If the delivery spec requires a different sample rate, use **Process → Resample → Resample**. The option to set the sample rate without resampling changes metadata/interpretation rather than converting the audio and can alter playback speed; leave it off for a normal conversion. The dedicated [sample-rate guide](https://soundforgepro.com/how-to-change-sample-rate-sound-forge-pro/) explains that trap. For bit depth, choose an output template that matches the delivery requirement. For a planned reduction to a lower integer PCM depth, configure dither at that final reduction stage using the [Bit-Depth Converter controls](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/bit%5Fdepth%5Fconverter.htm). Avoid adding it again in another stage, and keep subsequent export settings at the intended depth. If the recipient didn't specify sample rate, bit depth and codec, ask instead of inventing a “best” setting. Podcast hosts, video post, broadcast systems, game engines and music distributors can all want different files. Before a large export, use the [audio file size calculator](https://soundforgepro.com/audio-file-size-calculator/) to estimate storage from duration, sample rate, bit depth, channels or bitrate. ## Verify the converted file Before delivery, check the actual saved output rather than just the selected template: 1. Open the converted file as a new document. 2. Confirm the codec, sample rate, PCM bit depth where applicable, and [channel count](https://soundforgepro.com/sound-forge-channel-converter/). 3. Play the beginning, a loud section, a quiet section and the end. 4. Check duration, start/end boundaries and channel layout against the intended result; any channel conversion should be deliberate. 5. Confirm required tags, markers and artwork in the receiving application as well as inside Sound Forge. 6. Keep the original until the destination has accepted the delivery. For MP3, also make sure the exported file opens outside Sound Forge in the player or platform that will actually use it. Check the MP3’s encoded bitrate, and don't mistake the editor’s decoded PCM depth for an MP3 setting. Measure peak/loudness again on the saved compressed file, because the render-time loudness log is generated before the codec and never sees the final MP3\. For a batch, count the expected outputs for each selected source and renderer, and review the Status section for failed or skipped files. ### Keep metadata deliberately In Save As, turn on **Save metadata with file** when you need it. Unsupported metadata may need an external `.sfl` file, and other players may not read that sidecar. In Batch Converter, look at **Metadata** before running: **Overwrite** can replace existing values, and a blank replacement can wipe them. Unsupported metadata types are ignored. Keep the source and check the fields the receiving system requires. ## Common conversion problems ### The required format is missing Check *Save as type* in the current installation, and compare it with the current vendor export list. Don’t download a random codec pack to “fix” a professional workstation; confirm that the format is supported by your installed Sound Forge version or use a trusted dedicated converter for that delivery. ### The converted file plays at the wrong speed The sample-rate value may have been changed without resampling. Return to the untouched source and use **Process → Resample → Resample** with the metadata-only option disabled. ### The batch is overwriting or mixing with sources Stop the job and choose a new output folder. Never troubleshoot a batch against the only copy of the original files. ### The new MP3 sounds worse The source may already have been lossy, or the output template may use a more aggressive encode than the original. Return to the best available WAV/FLAC source. If MP3 is the only source, avoid repeated MP3 exports and make a single final delivery encode. ## Frequently asked questions ### How do I convert WAV to MP3 in Sound Forge? Open the WAV, choose File → Save As, select the MP3 output in Save as type, choose the delivery template, enter a new filename and save. Keep the WAV as the source master. ### How do I convert WAV to FLAC in Sound Forge? Open the WAV, choose File → Save As, select the FLAC output, choose a template that preserves compatible integer PCM samples and the required rate and channels, and save to a new file. Keep floating-point originals: FLAC does not natively store floating-point samples. Check metadata separately from audio. ### How do I convert multiple files at once? Open Tools → Batch Converter, add the files under Files to Process, leave the Processing list empty and Watermark unset for unchanged-audio conversion, choose Renderer and Template under Export Formats, and use Options to select a separate destination. Run only representative pilot files first, verify them, then select the remaining sources. ### Does converting MP3 to WAV improve quality? No. It creates an uncompressed working file from the decoded MP3 but cannot restore information discarded by the original lossy encode. ### What is the best format to convert to? Use the format required by the destination. PCM WAV is useful for uncompressed delivery, FLAC for lossless storage of compatible PCM, and MP3 for a requested lossy delivery copy. There is no universal best format. ### Does Save As change the sample rate? The selected output template can define audio properties, but deliberate sample-rate conversion should be handled and checked with Process → Resample → Resample. Don’t use the metadata-only option for a normal conversion. ### Do I need Sound Forge Plus for Batch Converter? No. Boris FX lists batch processing in both Sound Forge and Sound Forge Plus. The current Plus description includes the base Sound Forge feature set; Plus is not required just to convert files. For the editing steps before export, return to the [Core Editing guides](https://soundforgepro.com/tag/core-editing/). *Documentation reviewed September 8, 2026 against Boris FX’s 2026 help and Xiph’s FLAC specification guidance. This is a documented workflow, not a claim of a new listening test.* ### Change Sample Rate in Sound Forge Without Pitch Shift URL: https://soundforgepro.com/how-to-change-sample-rate-sound-forge-pro/ Last updated: 2026-10-09T21:03:35.000Z Changing sample rate in Sound Forge Pro 2026 is a conversion job, not a metadata edit. For normal work, open **Process → Resample → Resample**, enter the target rate, leave **Set the sample rate only** off, choose a phase setting, and click OK. That preserves the file’s pitch and duration while Sound Forge calculates a new set of samples. The warning matters because Sound Forge can also change only the rate stored for playback. That makes the same samples play faster or slower and shifts pitch with them. It’s useful for a wrongly tagged recording and the wrong tool for delivering a 48 kHz file from a 44.1 kHz master. This guide uses the current [Sound Forge Pro 2026 Resampling help](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/resample.htm), last modified March 4, 2026\. The current dialog uses **Phase Setting** and **Allow aliasing/imaging above 3 dB**. Older tutorials may show an Interpolation Accuracy slider or a separate iZotope 64-bit SRC command. Those controls are not described on this current help page; follow the help for your installed build rather than assuming the old menu is present. ![The Sound Forge Resample dialog, showing the target rate, anti-aliasing options and the rate-only warning](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/10/resample-2026-target-phase-rate-only-verify-v2-1-v20261005-v20261006.webp) Sound Forge 2026 workflow: set the target rate, use Intermediate for normal conversion, leave rate-only disabled, and verify the saved file. ## Change sample rate without changing pitch 1. Open the audio file and note its current sample rate in the status bar. 2. Choose **Process → Resample → Resample**. 3. Enter the required value in **New sample rate**, such as 44100, 48000 or 96000 Hz. 4. Choose **Intermediate**, the setting Boris FX recommends for most uses. 5. For normal downsampling, leave **Allow aliasing/imaging above 3 dB** unchecked so the anti-aliasing protection remains active. 6. Confirm that **Set the sample rate only** is unchecked. 7. Click **OK**, then save the converted result under a new name if you need to keep the source unchanged. If the target comes from a broadcaster, video editor, game engine, sampler or client, use that specification. Don’t convert to 96 kHz just because the number is larger. The [Boris FX 44.1-versus-48 kHz guide](https://borisfx.com/blog/44-1khz-vs-48khz-what-is-the-main-difference/) describes 44.1 kHz as the established CD rate and 48 kHz as the standard for digital video; neither is a universal delivery rule. If the file belongs to a VEGAS project, use the [Sound Forge–Vegas video workflow](https://soundforgepro.com/sound-forge-vegas-pro-workflow-video-editors/) for the round trip and verify the returned file’s sample rate before the final render. ## What the Sound Forge 2026 controls actually do ### New sample rate This is the rate of the converted file in samples per second. A 48,000 Hz file stores 48,000 sample values per channel for each second of audio. A lower rate reduces the available frequency range; a higher rate adds interpolated samples, not information the recording never captured. For uncompressed PCM at the same duration, bit depth and channel count, size changes in proportion to sample rate. Compressed-file size also depends on the codec and its settings. The Nyquist frequency is half the sample rate: 22.05 kHz for a 44.1 kHz file and 24 kHz for a 48 kHz file. Reconstructible signal content must stay below that boundary, with room for a practical filter transition. When downsampling, filtering removes frequencies that would otherwise fold into the new band. ### Phase Setting: Minimal, Intermediate or Linear The current online help describes three phase settings rather than an interpolation-accuracy number: - **Intermediate** is the official recommendation for most uses. It balances transient behavior and phase response. - **Linear** preserves phase relationships more consistently across frequencies, but can place ringing both before and after sharp transients. - **Minimal** keeps pre-ringing away from transients, while phase varies more at lower frequencies. Intermediate is the sensible starting point unless a delivery test or a specific transient problem gives you a reason to compare the other two. “Linear” isn’t automatically better; it’s a different trade-off. ### Allow aliasing/imaging above 3 dB This label is easy to misread. For an ordinary sample-rate conversion, especially when reducing the rate, leave it **unchecked**. Sound Forge then applies the filtering needed to keep frequencies above the new Nyquist limit from folding back into the audible band as false tones. The 2026 help says you may enable the option when you are certain the signal contains nothing above half the target sample rate. That can make processing faster and reduce ringing, but treat it as an exception for known material rather than a default “quality” switch. ## When “Set the sample rate only” is correct **Set the sample rate only** changes playback interpretation without calculating new samples. If a 44.1 kHz file is relabeled as 48 kHz, it plays about 8.84% faster and roughly 1.47 semitones higher. Relabeling 48 kHz as 44.1 kHz does the reverse. That behavior is useful when the audio data is correct but its playback rate was assigned incorrectly—for example, a headerless raw file imported using the wrong rate. Establish the original recording rate before changing it; do not guess from the filename. It can also be used deliberately for tape-style speed and pitch changes. It shouldn’t be used to meet a normal delivery specification. If a conversion unexpectedly changes pitch or duration, undo it and reopen Resample. The first thing to check is this box. Changing the rate through a properties field or status-bar control without resampling can create the same symptom. ## Choose the target rate from the destination | Destination | Practical choice | What to verify | | -------------------------------- | ------------------------------------------------------------------- | ----------------------------------------------------------------------------- | | Audio CD | 44.1 kHz | The authoring workflow also expects the correct bit depth and channel format. | | Video or broadcast handoff | Commonly 48 kHz | Use the editor’s or broadcaster’s written specification. | | Music distribution | Keep the native master unless the distributor requests another rate | Do not infer a platform requirement from a generic web chart. | | Sampler, game or hardware device | Exactly what the device accepts | Check supported rates, channels and sample format together. | | Archive or further processing | Usually keep the source rate | A larger rate does not restore missing bandwidth. | Avoid repeated conversions. If the source is 96 kHz and the final deliverable is 48 kHz, work from the 96 kHz source and make one conversion at the end. Converting 96 → 44.1 → 48 kHz adds another filtering and interpolation pass without adding useful information. ## Upsampling and downsampling: the useful distinction **Upsampling** creates intermediate sample values so the file can run at a higher rate. Use it when a delivery specification or a checked processing workflow requires the higher rate. Upsampling a finished 44.1 kHz file to 96 kHz does not extend its original recorded bandwidth or make it a true high-resolution source. **Downsampling** reduces the number of samples and the reproducible bandwidth. A proper converter filters frequencies that cannot exist at the new rate before decimation. That is why Sound Forge’s aliasing option deserves more attention than any “higher numbers sound better” argument. The underlying interpolation and filtering problem is also described in Julius O. Smith’s [Digital Audio Resampling](https://ccrma.stanford.edu/~jos/resample/) material at Stanford CCRMA. Sample rate is separate from bit depth. Resampling changes the time grid; bit-depth conversion changes how each sample value is represented. If the destination also requires a lower bit depth, perform that conversion once at final delivery and use dither where appropriate. The [Sound Forge conversion guide](https://soundforgepro.com/how-to-convert-audio-files-sound-forge-pro/) covers format and bit-depth decisions. ## Export and batch workflows For one file, the safest audit trail is simple: keep the source, run Resample, then use **Save As** with a new filename that includes the target rate, such as `mix-v7-48k.wav`. Reopen the result and confirm its rate, duration and channel layout. Recheck sample peak and true peak, then listen to transients and the start/end: resampling can change peak levels even when pitch and duration are correct. When many files need the same destination format, use the [Batch Converter workflow](https://soundforgepro.com/how-to-batch-process-files-sound-forge-pro/) instead of repeating manual clicks. Build one preset and test copies of a typical and a stress file, including a source that needs conversion and one already at the target rate where both occur in the batch. Verify rate, duration, channels, format, peak/true peak and sound before running the full folder. That test catches the expensive mistakes: changing only the header, choosing the wrong destination folder or applying a rate intended for a different device. ## Troubleshooting sample-rate changes ### The result is faster and higher, or slower and lower The rate was probably changed without resampling. Undo if possible, then use Process → Resample with **Set the sample rate only** disabled. ### The converted file has high-frequency whistles or roughness Check whether **Allow aliasing/imaging above 3 dB** was enabled during downsampling. Repeat the conversion from the untouched source with it disabled. ### The audio interface changes rate or will not play the file Separate the saved file’s rate from the rate used for playback before changing anything. Check the selected audio driver, hardware-supported rates and clock source. The [File Properties help](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/file%5Fproperties.htm) documents ASIO playback resampling when hardware cannot play the file’s rate, with an italic rate display. That playback conversion is not proof that the saved file is wrong. Do not convert an original merely to match a Windows shared-mode setting. The [recording setup guide](https://soundforgepro.com/how-to-record-audio-in-sound-forge-pro/) covers interface and ASIO configuration. ### I cannot find Interpolation Accuracy or 64-bit SRC You’re probably comparing Sound Forge 2026 with an older manual or screenshot. The current Boris FX Resample page documents New sample rate, Phase Setting, Allow aliasing/imaging above 3 dB and Set the sample rate only. It doesn’t document an iZotope 64-bit SRC submenu. ## Frequently Asked Questions ### How do I change sample rate in Sound Forge Pro without changing pitch? Choose Process → Resample → Resample, enter the target rate and keep Set the sample rate only unchecked. Sound Forge then converts the sample data while preserving pitch and duration. ### Which Phase Setting should I use? Use Intermediate for most conversions. The 2026 help recommends it as the general-purpose balance. Linear preserves phase more consistently but can add pre/post-ringing; Minimal protects transient onset from pre-ringing while allowing more low-frequency phase variation. ### Should I enable Allow aliasing/imaging above 3 dB? Normally no, especially when downsampling. Leave it unchecked so anti-alias filtering remains active. Enable it only when you know the source has no content above half the target rate and accept the trade-off described in the current help. ### Why did changing sample rate change speed and pitch? A likely cause is relabeling the file rate without resampling. Compare with the untouched source, then use Process → Resample with Set the sample rate only disabled. Reserve the rate-only option for correcting a wrong header or for a deliberate speed-and-pitch effect. ### Does converting 44.1 kHz to 96 kHz improve quality? Not by itself. It creates additional interpolated samples but cannot recover frequencies or detail absent from the source. Upsample only when a tested processing or delivery workflow requires it. ### Is 44.1 kHz or 48 kHz better? Neither is universally better. 44.1 kHz is the established audio-CD rate; 48 kHz is common in video. Follow the destination specification and avoid unnecessary conversions. ### Can I change a folder of files at once? Yes. Use Batch Converter and test copies of a typical and a stress file first. Check rate, duration, channels, format, peak/true peak and sound before the full run. Include unchanged-rate and converted-rate cases when present, and keep the originals. If sample-rate conversion is one step in a larger edit, the [Core Editing guide hub](https://soundforgepro.com/tag/core-editing/) connects recording, editing and export workflows. Keep this page for the resampling step; choose the final codec and bit depth from the delivery specification. *Documentation reviewed September 8, 2026\. Menu instructions follow Boris FX’s Sound Forge Pro 2026 help; the rate and pitch example is calculated, not a listening-test result.* ### How to Remove Clicks and Pops in Sound Forge Pro URL: https://soundforgepro.com/how-to-remove-clicks-pops-sound-forge-pro/ Last updated: 2026-10-09T21:01:14.000Z **Quick answer:** choose **Effects → DeClicker / DeCrackler** for repeated clicks or fine crackle, and **Tools → Repair → Interpolate** for one very short glitch that you can isolate. If the click began at a cut, repair the boundary with a zero crossing, fade or crossfade. Before repairing samples, compare the original with a lossless copy exported without effects. A click can come from the playback or plug-in chain rather than damaged source audio. This guide is part of the [Sound Forge restoration hub](https://soundforgepro.com/tag/sound-forge-restoration-guides/). The repair should match the shape of the problem. A declicker can mistake drum attacks and hard consonants for damage. Interpolate can replace useful waveform detail when the selection is too wide. The safest pass uses the smallest suitable tool, a preserved original and a before/after check at normal listening level. For exact control names, go by the current application labels and the linked help. | What you hear | Likely problem | Start here | Do not confuse it with | | ------------------------------------ | --------------------------------------------- | -------------------------------- | ----------------------- | | Separate sharp ticks or pops | Scratches or isolated impulse errors | DeClicker | Steady hiss or clipping | | Continuous fine crackle | Dense low-level impulses, often surface noise | DeCrackler | One large click | | One visible tiny discontinuity | A few damaged samples | Interpolate or Pencil | A long missing passage | | Click at a cut or event edge | Waveform discontinuity | Zero crossing, fade or crossfade | Recorded damage | | Flattened peaks and broad distortion | Clipping | DeClipper workflow | A narrow impulse | | Lip smacks inside speech | Mouth noise | Mouth-click workflow | Vinyl crackle | | Click moves or vanishes on export | Playback, driver or buffer path | Playback diagnosis | File damage | ![A single click selected at sample level in Sound Forge, shown before and after Interpolate](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/10/remove-clicks-ui-select-repair-v2-1-v20261008.webp) Removing clicks and pops in Sound Forge: zoom in, select only the defect, apply the smallest suitable repair, then audition the boundary. ## Confirm the click is actually in the file Play the same short region several times. Damage in the source recurs at the same position, but so can an effect or automation error. Compare the unprocessed source in another trusted player, then a lossless export with the effects chain bypassed. If the source is clean, or the click changes with the player or processing path, investigate the device, driver, buffer and plug-ins before altering samples. An export made through the same faulty effect can print that fault into a new file. Next, zoom in and listen together. A narrow visual spike can be a wanted transient. A click that is obvious by ear may be too small to identify at the first zoom level. Mark the exact time, include a little sound before and after it, then compare the same passage with processing bypassed. For a playback fault, use the separate [Sound Forge playback and ASIO checks](https://soundforgepro.com/sound-forge-pro-no-sound/); this page repairs defects already committed to audio data. Protect the source before destructive editing. Duplicate the file or use Save As, keep the original sample rate and bit depth, and make one repair at a time. A visible change you can't compare with the source is harder to trust than a conservative repair you can undo. ## Remove clicks and pops in Sound Forge: 7-step workflow 1. **Confirm the click is in the file.** Compare the unprocessed source in another player and a lossless export with effects bypassed. A click that repeats doesn't prove the source is damaged, so rule out the playback and plug-in chain before you edit samples. 2. **Preserve the source.** Duplicate the file or use Save As so every repair can be compared with an untouched original. 3. **Classify the defect.** Separate isolated clicks, continuous crackle, a very short sample glitch, an edit-boundary discontinuity, clipping and speech mouth noise. 4. **Choose a representative test region.** Include the defect plus wanted transients, speech consonants or musical attacks that the processor must preserve. 5. **Use the smallest suitable repair.** Choose DeClicker or DeCrackler for repeated defects, Interpolate or Pencil for a tiny visible glitch, and a zero crossing, fade or crossfade for an edit boundary. 6. **Preview and audition what is removed.** Compare Preview and Bypass with surrounding audio. Where available, use Inverse to hear the removed signal; reduce processing if wanted detail is lost. Turn Inverse off before judging the repaired audio. 7. **Process and verify.** For an effects pass, turn Inverse and Bypass off, then apply to the intended area once. Undo a rendered test before including it in a larger pass. Listen through both boundaries and verify a new lossless export. The workflow deliberately separates diagnosis from processing. One clean test passage doesn’t prove that a full vinyl side, interview or music file will tolerate the same sensitivity. If defects are dense, test a quiet passage, a transient-heavy passage and the worst damaged area before extending the setting. ## Use DeClicker for separate defects and DeCrackler for a crackle bed The current [Sound Forge Pro 2026 DeClicker / DeCrackler help](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/proonly/declicker%5Fdecrackler.htm) places the effect under **Effects → DeClicker / DeCrackler**. It describes DeClicker for crackling and single clicking noises typical of scratched records, while DeCrackler is designed for crackling. In practice, start with DeClicker when the defects are individually distinct and test DeCrackler when many quieter impulses merge into a texture. Boris FX lists this as a Sequoia restoration effect in its Sound Forge Repair help. The [Sequoia control reference](https://cdn.borisfx.com/borisfx/Documentation/sequoia-2026/en/Content/DeClicker%5FDeCrackler.htm) documents separate Sensitivity and Mix controls for DeClicker and DeCrackler: Sensitivity controls detection, and Mix controls how hard the repair works on detected areas. Open the effect’s own **?** help if your installed controls look different, and don't carry settings over from a differently named Click and Crackle Removal plug-in. Inverse plays back what the algorithm removes. If you hear snare attacks, pick noise, consonants, room tone changes or pitched material in that residual, lower Sensitivity or Mix. You want the removed signal to be mostly defect; it doesn't need to be perfectly empty. Turn **Inverse off** to hear the repaired recording again, then compare with Bypass. Leave both audition switches off when you apply the effects pass you've chosen. No single sensitivity number holds up everywhere. A clean modern recording with a few digital ticks and a worn record side have very different transient statistics. Start conservatively, loop a short representative region, raise detection until the target click is caught, then back off as soon as wanted detail shows up in the removed signal. The [processing-dialog help](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/using%5Fprocessing%5Fdialogs.htm) explains Preview and Bypass. Right-click that dialog and enable Pre-Roll or Post-Roll to hear the unprocessed audio around the selection. Preview doesn't commit the repair; **OK** processes the selected settings. If you render a small test and later fold it into a larger pass, undo the test first so the same samples don't get repaired twice. For a vinyl transfer, try the larger isolated clicks before deciding whether the remaining low-level crackle needs another pass. That order is an editorial workflow; Sound Forge doesn’t impose it as a rule. The dedicated [vinyl digitization and archive guide](https://soundforgepro.com/sound-forge-pro-for-vinyl-restoration/) covers cleaning, capture, raw-master preservation and track splitting around this repair step. ## Repair one very short glitch with Interpolate The current [Interpolate documentation](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/proonly/interpolating%5Fsound%5Fdata.htm) gives the exact route: zoom in, select the glitch, then choose **Tools → Repair → Interpolate**. Boris FX says the selection should be very small, less than 2 ms in most cases. With no selection, Sound Forge assumes a glitch shorter than 1 ms and treats the cursor as its center. 1. Use View → Zoom Time → In Full, then locate the discontinuity in the surrounding waveform. 2. Select only the damaged samples. Leave the rest of the word, note or transient out. 3. Run **Tools → Repair → Interpolate**. 4. Return to a normal zoom and audition before, through and after the repair. 5. Undo if the join creates a second tick, softens the attack or changes the timing. Interpolate joins the selection endpoints with a straight line, which works when the neighboring samples make a plausible bridge. It won’t rebuild a long missing passage or guess the original performance. The 1.28 ms selection in the figure is an example, not a universal repair limit. What matters is whether a straight bridge between the selected endpoints removes the defect without creating a new one. ## Redraw one obvious sample error with Pencil Choose **Edit → Tool → Pencil**. The current [Pencil Tool help](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/the%5Fpencil%5Ftool.htm) says to zoom into a glitch and redraw the waveform smoothly, and while you hold the left mouse button you can nudge the pencil position with the arrow keys. If Pencil isn't available, zoom in further. Whether it's available depends on the **Pencil tool maximum zoom ratio** setting under Options → Preferences → Editing, and the current help doesn't set one fixed zoom ratio for every setup. Use Pencil when the expected path is visually obvious, such as one outlying sample between two smooth neighbors. Avoid drawing across a complex transient or several waveform cycles. Use the menu route above, or a shortcut you have confirmed in your own keyboard map. Choose Interpolate when a tiny selected span needs a straight bridge, and reach for Pencil when one or two points need manual shaping. If neither produces a transparent result, undo and move to a specialist spectral or de-click process instead of extending a hand-drawn repair. ## Fix cut-boundary clicks without a restoration pass If the click appeared immediately after a cut, the source may be clean and the new boundary may be discontinuous. Running DeClicker across the whole file treats the symptom while leaving the edit decision unexplained. - **Edit → Selection → Snap to Zero** moves both selection edges to zero crossings. - **Snap Edge to Zero** moves only the active edge. - A short fade can smooth a file start or end when moving the edge would remove wanted timing. - An event crossfade can join two different waveforms when a shared zero value still sounds abrupt. The current [Selection Snapping help](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/selection%5Fsnapping.htm) says zero-crossing edits reduce the chance of introducing glitches. It doesn't promise an inaudible join. Two unrelated waveforms can cross zero at different slopes and with different spectral content, so listen through the transition. The [cut-and-trim guide](https://soundforgepro.com/how-to-cut-and-trim-audio-in-sound-forge-pro/) covers boundary placement, and the [crossfade workflow](https://soundforgepro.com/crossfade-audio-sound-forge/) covers overlapping events. ## Route mouth clicks, clipping and steady noise to the right workflow “Pop” can mean several unrelated faults. A vocal plosive is a low-frequency burst of air hitting the microphone, and a mouth click is a small articulation noise in speech. Clipping can leave flattened peaks after overload, though a flat-looking overview alone doesn't prove it; check at close zoom and listen for distortion. Hiss and hum are continuous noise. Treating all four as vinyl clicks wastes time and can damage the signal you want to keep. - Use the [mouth-click guide](https://soundforgepro.com/remove-mouth-clicks-from-audio/) for lip smacks and saliva noise inside speech. - Use the [DeClipper workflow](https://soundforgepro.com/fix-clipped-audio-sound-forge/) for flattened peaks and overload distortion. - Use the [background-noise workflow](https://soundforgepro.com/how-to-remove-background-noise-in-sound-forge-pro/) for steady broadband noise. - Use the [hiss and hum guide](https://soundforgepro.com/remove-hiss-hum-sound-forge/) for a continuous floor or tonal mains interference. Repair the identified defect before heavy EQ, compression or limiting when those later processors would make it harder to hear the original shape. Keep enough headroom for comparison and save an intermediate lossless file before mastering. The order can change when the source demands it, so treat this as a reversible workflow rather than a fixed chain. ## Use iZotope RX when the native repair removes wanted detail The current [Sound Forge Pro 2026 Repair help](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/proonly/repair.htm) says included iZotope RX plug-ins are available through **FX Plug-In**. The current public [Sound Forge pricing comparison](https://www.soundforge.com/sound-forge/pricing/) confirms VST2/VST3 support but doesn't list RX among current plan inclusions. So don't assume the help’s bundle description applies to your purchase; check the license and installed modules before you go looking for RX. Supporting third-party plug-ins isn't the same as including an RX license. iZotope's current [RX 12 Elements comparison](https://www.izotope.com/products/rx-elements) lists six host plug-ins: De-click, De-clip, De-hum, De-reverb, Voice De-noise and Repair Assistant. De-crackle and Mouth De-click appear in Standard and Advanced rather than Elements. Installed [RX De-click](https://izotoperx.net/izotope-rx-de-click-tutorial/) is a sensible escalation when a native pass repeatedly removes wanted attacks, when clicks vary too much for one setting, or when manual Interpolate repairs are impractical. The [RX 12 De-click manual](https://docs.izotope.com/rx12/en/de-click.html) describes Elements as plug-in-only for this module. In Sound Forge, use the host plug-in controls; standalone RX Editor instructions are a different workflow. Compare the Sound Forge and RX result on the same short selection at matched listening level. A more expensive edition or a more aggressive setting doesn’t prove a safer repair. If the click can be fixed transparently with one narrow Interpolate selection, a large restoration suite adds no automatic advantage. ## Troubleshoot a repair that sounds worse or misses defects | Symptom | Likely issue | Next check | | ---------------------------------------------- | -------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------ | | Drums or consonants sound soft | Sensitivity or Mix is too aggressive | Use Inverse, lower processing and shorten the target region | | Click remains after Interpolate | The span may miss the impulse, or a straight-line repair may be unsuitable | Undo, inspect both endpoints and try a different method if the bridge changes wanted audio | | A new click appears at the repair | The straight bridge or edit boundary is discontinuous | Undo; reduce the span or try Pencil, zero crossing or fade | | Fine crackle remains after large pops are gone | Defect class changed | Test a lighter DeCrackler pass on contrasting passages | | Effect or RX module is missing | Edition, license, installation or scan differs | Check current entitlement and the [VST discovery workflow](https://soundforgepro.com/sound-forge-pro-vst-plugins-not-showing/) | | Click is absent from exported WAV | Live playback path may be responsible | Do not render repair; diagnose driver, device, buffer and plug-ins | Always verify at normal level. Extreme looping and high monitor gain can make a benign transition feel larger than it is, while a quiet comparison can make an overprocessed result seem cleaner. Match playback level, leave the repair for a minute, then return and listen through the surrounding phrase or musical passage. ## Sound Forge clicks and pops FAQ ### Where is DeClicker in Sound Forge Pro 2026? Choose Effects → DeClicker / DeCrackler. Current Sound Forge help places both processors in one effect and links its detailed controls through the effect's Help button. ### Should I use DeClicker or DeCrackler? Use DeClicker for separate sharp clicks and pops. Use DeCrackler for a denser bed of fine crackle. Test both on a short passage containing wanted attacks before processing a longer range. ### What sensitivity setting should I use? There is no reliable universal number. Start conservatively on a representative passage, raise Sensitivity until the target defects are detected, and reduce it if Inverse or a bypass comparison reveals lost transients, consonants or tonal detail. ### How small should an Interpolate selection be? Boris FX recommends less than 2 ms in most cases; that is guidance, not a hard limit or a guarantee. With no selection it assumes a sub-1 ms glitch around the cursor. If a straight bridge damages the surrounding waveform, undo and use a more suitable repair. ### Does the Pencil tool have a P shortcut? The current Pencil documentation gives Edit → Tool → Pencil and does not establish P as a default shortcut. Use the documented menu route unless your workstation has a confirmed custom key map. ### Why did a click appear after I cut audio? The samples on either side of the new boundary may not meet smoothly. Move the edit, use Snap to Zero or Snap Edge to Zero, or add a short fade or event crossfade, then listen across the boundary. ### Is iZotope RX included with Sound Forge Pro? Current Boris FX Repair help mentions included RX plug-ins through FX Plug-In, while the current public pricing table does not name RX. Confirm the license and installed modules on that workstation. RX 12 Elements sold by iZotope includes De-click; De-crackle and Mouth De-click require Standard or Advanced. ### Why does a click remain after the waveform looks repaired? Listen to a lossless export at the same timestamp. The selected span may have missed part of the impulse, the new boundary may be discontinuous, or the noise may come from live playback rather than the file. Undo and re-diagnose instead of widening the repair blindly. *Last fact-checked: September 8, 2026 against current Boris FX Sound Forge Pro 2026 Repair, DeClicker / DeCrackler, Processing Dialogs, Interpolate, Pencil and Selection Snapping documentation; the current Sound Forge pricing comparison; the current iZotope RX 12 edition comparison and De-click manual. This is a documentation-based review, not a claim of a recorded repair test on every build.* ### How to Use the Noise Gate in Sound Forge Pro URL: https://soundforgepro.com/how-to-use-noise-gate-sound-forge-pro/ Last updated: 2026-10-10T13:29:48.000Z A noise gate is useful when the unwanted sound bothers you mainly between words or notes. It closes when the signal falls below a level you set and opens when wanted audio rises above it. What it can’t do is remove fan noise, hiss, or hum while speech is holding the gate open. That boundary decides whether this tool will help before you touch a control. Part of the [audio restoration guide](https://soundforgepro.com/audio-restoration/): this page deals with noise between phrases. Broadband denoising and deleting silence from the timeline are separate jobs. Quick answer: select a test passage, choose FX Plug-Ins → Apply Plug-In Chain and add coreFX Gate. With Peak detection and a fully wet mix, use a noise-only pause as your threshold reference, then audition the weakest words. Lower Level if a consonant never opens the gate; shorten Attack if it opens too slowly. Noise you can still hear under speech needs a different treatment, and a higher threshold won't fix it. ## Check whether a gate fits the recording Listen once with the wanted sound active. If the noise is acceptable under speech or music but distracting in the pauses, a gate is a sensible test. When it stays objectionable throughout the performance, gating the pauses only makes the changing background more obvious and cleans nothing in the active material. If you need to remove whole silent sections or trim file boundaries rather than react to level, use [Sound Forge Auto Trim/Crop](https://soundforgepro.com/sound-forge-auto-trim-crop/) instead. The [current Boris FX Noise Gate help](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/noise%5Fgate.htm) defines the processor by this level decision: signal below the specified threshold is removed, which makes it suitable for noise in silent breaks. A gate doesn’t classify a sound as fan, hiss, breath, or voice; it reacts to level. | What you hear | Likely cause | First move | | ------------------------------------------------- | ----------------------------------------------------------- | -------------------------------------------------------------------------------- | | Noise remains in pauses | Threshold, bypass, dry Mix or detector routing may be wrong | Verify the effect and detector, then remeasure before raising Level | | First consonant or transient is missing | Attack may be slow or Level too high | Lower Level if the sound never opens the gate; shorten Attack if opening is slow | | Word ending, breath, or reverb tail is cut | Release is too short, or Level is too high | Lengthen Release, then lower Level if needed | | Gate chatters around quiet words | Wanted audio is hovering around Level | Lower Level and lengthen Release | | Noise vanishes in pauses but returns under speech | The gate is working by level, not identifying noise | Use Noise Reduction or another repair process | | Pauses sound unnaturally dead | Full suppression is too abrupt | Use gentler expansion or controlled room tone | ## Which Noise Gate should you open in Sound Forge? The current documented command is **Effects → Noise Gate**. Sound Forge installations can also expose **coreFX Gate** through the plug-in list. The [current Sound Forge plan comparison](https://www.soundforge.com/sound-forge/pricing/) lists the coreFX Suite, while upgraded or older systems can have a different plug-in inventory. Use the processor that is actually present in your build rather than copying a menu path from another version. The classic Noise Gate and coreFX Gate have different dialogs. The classic page points to its installed **?** help, while the [coreFX documentation](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/dynamic%20effects.htm) describes **Level, Attack and Release** plus shared detector and mix controls. For the selection-based walkthrough here, choose **FX Plug-Ins → Apply Plug-In Chain**, add only **coreFX Gate** and leave it enabled. That route is documented in [Applying a Plug-In Chain](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/apply%5Ffx%5Fchain.htm). Use Peak detection, a fully wet Mix and neutral Out Gain for the first test. Keep the detector on internal input, with Listen off and no deliberate detector filtering. Check Soft and any limiter in the preset so an unrelated setting doesn't muddy the test. Treat this as a starting setup. Switching to RMS or filtering the detector means auditioning the threshold again. If coreFX Gate is missing, follow the installed classic processor’s help instead. ## A seven-step Sound Forge noise gate workflow The reliable setup uses two measurements and two listening checks. You need the loudest representative noise in a pause, the quietest wanted sound that must survive, the transition into that sound, and its ending. 1. **Protect the source file.** Save an untouched copy before adding effects. Select a representative test passage, open FX Plug-Ins → Apply Plug-In Chain and add coreFX Gate with the setup described above. 2. **Measure a noise-only pause.** Use Tools → Statistics on a pause with no wanted sound. Check both minimum and maximum sample excursions; in dB, the larger magnitude is the value nearer 0\. Use this as a reference, not a guaranteed gate setting. 3. **Find the quietest wanted sound.** Listen to the weakest consonant, breath, note or decay you need to keep. A whole word’s peak is not its quietest part. 4. **Audition Level inside the gap.** Start above the representative noise and lower than wanted details. If no setting keeps those details while quieting the pause, choose gentler expansion or another repair. 5. **Tune Attack and Release.** Lower Level when a beginning never triggers the gate; shorten Attack when opening is slow. Lengthen Release for chopped endings, then recheck the pause. 6. **Check chattering and transitions.** Try a lower Level and longer Release on the weakest passage. Check the start and end of the selected range and other sections; stop if useful speech is still being lost. 7. **Compare and commit once.** Preview with and without Bypass at the same listening volume. Turn Bypass off, confirm the time range and channels, then click OK in Apply Plug-In Chain. Undo a rendered test before processing an overlapping range. Save a new output and listen with no extra gate running. ## 1\. Protect the original before gating Direct processing changes the selected audio, and saving over the original can make that loss permanent. Keep an untouched source and work on a copy. In the current [View → Plug-In Chain window](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/proonly/plug-in%5Fchainer.htm), effects run during playback instead and get applied on saving. That window is a different thing from the selection-processing dialog used here, and the [Plug-In Chainer guide](https://soundforgepro.com/how-to-use-plug-in-chainer-sound-forge-pro/) explains both routes. For this test, keep the data window’s other playback effects bypassed so you only hear coreFX Gate once. Quiet syllables lost in a rendered pass won't come back just because you lower the threshold afterwards; undo or go back to the source. ## 2\. Measure a representative noise-only pause Select a pause with the room noise you want to suppress, but no wanted breath, consonant, reverb tail or instrument decay. Choose **Tools → Statistics** and set **Level format** to **Decibels (dB)**. The [Statistics help](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/statistics.htm) recommends the minimum and maximum samples in noisy silence as a gate reference. Compare both extrema: in dB, use the one nearer 0; with signed sample values, compare their absolute magnitudes. A negative waveform excursion can be larger than the positive one. This is a sample-peak reference for the selected audio, and it won't predict every detector setting. Don't swap in whole-file RMS, integrated LUFS or true peak for the pause measurement. Confirm the result by listening, especially if the detector mode, filtering or anything before the gate changes. Measure more than one pause when the background changes. A quiet pause near the start can’t stand in for a later section with a louder fan, traffic burst, or microphone movement. If the noise floor changes materially, process sections separately or fix the varying noise before relying on one gate setting. ## 3\. Find the quietest wanted word, note, or decay Now loop the weakest wanted material in the same section. For speech that means soft consonants, sentence endings, and any deliberately quiet delivery; for instruments, note attacks and natural decays. The gate needs a usable level gap: the wanted sound must rise above the noise often enough to open cleanly. ![Noise gate Level set between a -48 dBFS noise peak and -30 dBFS quiet speech](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/08/noise-gate-threshold-desktop-v1.webp) Measure both sides of the decision. In this example, -42 dBFS suppresses the -48 dBFS pause while leaving the -30 dBFS quiet word above the gate. In the worked example, noisy silence peaks at -48 dBFS, the quietest wanted word reaches -30 dBFS, and Level is tried at -42 dBFS. The order matters more than the exact numbers: values closer to 0 are louder, so -30 dBFS passes while -48 dBFS falls below the gate. These figures describe a hypothetical recording. A word that peaks at -30 dBFS can still have consonants or tails below -42 dBFS, so listen through the whole word before you accept the threshold. ## 4\. Put Level inside the measured gap Start with Level above the noise peak and safely below the quietest wanted sound, raising it only until the pause closes reliably. Then replay the weakest word or note. If that wanted sound disappears, lower Level; forcing the gate harder won't bring it back. A narrow or unstable gap is a warning. When noise and quiet speech occupy the same level range, no threshold can distinguish them consistently. A higher setting removes more wanted audio; a lower setting lets more noise open the gate. That's a limitation of the source, and no secret number will get around it. ## 5\. Tune Attack and Release by the edge you hear Attack sets how quickly the gate opens once the signal crosses Level. First check whether the missing consonant crosses that threshold at all, and shorten Attack only when the gate is opening too slowly. If it never opens for that sound, lower Level and check the pause again. No Attack setting can rescue audio that never triggers the gate. If the opening clicks or snaps, try a slightly slower Attack and listen again. **Release** controls how the gate closes after the signal falls below Level. Lengthen it if phrase endings, breaths, or room decay are cut off. If background noise hangs on too long after every phrase, shorten it carefully and recheck the quietest ending. ![Noise gate Attack and Release fixes for missing starts and chopped audio tails](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/08/noise-gate-attack-release-desktop-v1.webp) Tune the edge you can hear: shorten Attack when starts disappear and lengthen Release when endings are cut off. There is no attack-and-release pair that is correct for every voice or instrument. A useful first audition for spoken word is a fast opening and a release long enough to preserve a complete phrase ending. The waveform, delivery, and room decay decide the final timing. ## 6\. Stop chattering without sacrificing quiet words Chattering is the rapid open-close sound produced when wanted audio keeps crossing Level. Lower Level first so quiet syllables stay above it, then lengthen Release so brief dips don't turn into abrupt closures. Test the weakest passage rather than the average one. If chattering won't go away, check the detector setup and the passage again before you decide the recording can't be gated. Other plug-ins may have a separate Hold control, but the current coreFX Gate help doesn't document one. If no usable setting keeps the wanted sound intact, try gentler expansion or local edits, or deal with the underlying noise. ## 7\. Compare Bypass and apply only the verified range Loop a weak wanted passage and a representative pause, then compare Bypass without changing monitoring volume. Check the first sound after silence, the end of a phrase, a breath, and any reverb or instrument decay. After that, move to at least two other parts of the file. Before committing, turn the plug-in and dialog Bypass off, keep the gate enabled, and confirm the intended time range and channels. The [processing-dialog controls](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/using%5Fprocessing%5Fdialogs.htm) also expose wet/dry gain and fades: an unintended dry blend can leave noise audible. Click **OK** in **Apply Plug-In Chain** only after the test works. If you rendered a short test, undo it before applying to an overlapping longer range. For changing backgrounds, use separately checked selections and listen across their boundaries. Use Save As for a new audio file, or [Render As for project output](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/saving%5Fa%5Ffile%5Fas%5Fa%5Fdifferent%5Fname%5For%5Ftype.htm). Open the output with no additional playback gate and listen through it, including quiet passages and fades. Keep the original. ## Why the noise comes back under speech When speech crosses Level, the gate opens for the whole signal. The voice and the background recorded with it pass through together, which is why a fan can vanish between sentences and come straight back when the speaker talks. A [recording-community discussion of vocal gating](https://www.reddit.com/r/recordingmusic/comments/1ilclb3/when%5Fusing%5Fa%5Fnoise%5Fgate%5Fi%5Fget%5Fa%5Flot%5Fof%5Fnoise/) describes the same practical symptom: gating the gaps leaves the noise under the voice untouched. Read it as a diagnostic clue. It doesn't point to a defect in any particular product. ![Noise Gate, Noise Reduction, and expander decision guide for background noise](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/08/noise-gate-tool-choice-desktop-v1.webp) Choose by when the noise is audible: gate pauses, reduce noise that remains under speech, and use softer attenuation when dead silence sounds abrupt. A gate fits when the unwanted sound is mainly a pause problem and a clear level gap exists. When a steady noise remains under speech, use the [Sound Forge background-noise workflow](https://soundforgepro.com/how-to-remove-background-noise-in-sound-forge-pro/). When the problem is tonal or frequency-specific, [hiss and hum diagnosis](https://soundforgepro.com/remove-hiss-hum-sound-forge/) is the right page. An expander or controlled room tone is usually more natural when complete silence makes every edit obvious. If steady noise is distracting during speech, try denoising first, then decide whether the remaining pauses need any gating at all. Measure again after the noise reduction, since the old threshold may no longer fit. This is a sensible starting order, and you don't have to run both tools. Compare each stage on its own; if the result pumps, sounds watery or loses words, ease off the stage causing it instead of adding more processing. ## Frequently Asked Questions ### Where is the Noise Gate in Sound Forge Pro? Choose Effects → Noise Gate for the documented processor. If coreFX Gate appears in your plug-in list, you can audition that version too. Installed plug-ins can differ between current, upgraded, and older systems, so verify the menu in your own build. ### What Level should I use for the Noise Gate in Sound Forge Pro? With coreFX Gate using Peak detection, internal input and fully wet Mix, measure a noise-only pause and audition the weakest wanted material. Use the noise peak only as a starting reference for Level: a word’s peak does not prove its consonants and tails survive. If the ranges overlap, a hard gate cannot reliably separate them. ### What Attack and Release settings should I use? Check Level as well as timing. If a quiet beginning never opens the gate, lower Level; if opening is slow, shorten Attack. Lengthen Release for chopped endings and recheck the pause. There is no universal millisecond preset that preserves every voice or instrument. ### Why does the gate chatter or stutter? Repeated crossings of Level can make the gate chatter. Verify detector routing and the preset, then lower Level and lengthen Release while looping the weak passage. If no setting preserves it cleanly, try gentler expansion or a different repair process. ### Why does background noise return when I speak? The gate opens for the complete signal when speech crosses Level, so the voice and its background pass together. Use noise reduction when the noise remains distracting under speech rather than raising the gate Level into quiet words. ### Does coreFX Gate have Hold, Floor, or Range controls? The current Boris FX 2026 coreFX documentation describes Level, Attack, and Release for coreFX Gate. Other plug-ins may add Hold, Floor, Range, or Hysteresis, so rely on the controls visible in the processor you installed. ### Can I use Noise Gate and Noise Reduction together? Yes, if they solve different problems. For steady noise under speech, try denoising first, then remeasure and audition a gate only if the pauses still need it. Compare each stage separately; running both is optional, and the old threshold may not suit the cleaned signal. If the result still depends on an aggressive Level setting, return to diagnosis. The [audio restoration hub](https://soundforgepro.com/audio-restoration/) routes clicks, clipping, hum, hiss, and broadband noise to different workflows, while [Spectrum Analysis](https://soundforgepro.com/how-to-use-spectral-analysis-tool-sound-forge-pro/) helps confirm tonal problems before processing. Documentation and the linked community symptom report checked September 17, 2026\. This is a document-verified Windows workflow, not a hands-on test of an installed Sound Forge build; available controls still need checking in your own plug-in. ### How to Use the Equalizer in Sound Forge Pro URL: https://soundforgepro.com/how-to-use-equalizer-sound-forge-pro/ Last updated: 2026-10-11T09:55:10.000Z For a whole-file EQ adjustment in Sound Forge Pro 2026, open **View → Plug-In Chain** and load Modern Equalizer. For the classic Graphic, Paragraphic or Parametric process, use **Process → EQ**. These are different interfaces, and a Paragraphic EQ preset won't translate into settings for Modern Equalizer. This guide belongs to the [Sound Forge mastering hub](https://soundforgepro.com/tag/mastering/). It follows current documentation; there was no hands-on compatibility test. Controls in your installed build may look a little different from the workflow diagram. Start with one audible problem: rumble, a ringing note, [too much bass or a dull upper range](https://soundforgepro.com/audio-frequency-chart/). Add one band, choose its shape and compare the result at similar loudness. Then save a separate processed file and reopen it for a final check. A pretty curve isn't the goal. You're after a useful change that holds up in the comparison. ## Which EQ Should You Use in Sound Forge 2026? Modern Equalizer is the eight-band parametric VST effect documented for the current release. The classic processes remain available for older workflows. If you are following a tutorial, check which EQ its author actually uses before copying settings. ![The Modern Equalizer in Sound Forge with one band adjusted and output level matched for A/B](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/10/equalizer-shape-level-match-bypass-v1-v20261005-v20261006.webp) EQ in Sound Forge 2026: isolate the problem, adjust one band at a time, match output level, then compare with A/B and Bypass. Use Paragraphic EQ when reproducing its own saved settings or working through a direct Process → EQ operation. Open the dialog’s **?** help for its controls. For a new adjustment, Modern Equalizer lets you place bands visually and compare curves; that is the workflow developed below. Graphic EQ uses fixed frequency bands; [parametric EQ](https://soundforgepro.com/parametric-eq-vs-graphic-eq/) lets you choose the frequency and bandwidth. Fixed bands suit a broad tonal change, but they may miss a particular ring. Pick the tool for the job, whichever name sounds more advanced. The older Parametric process is also under Process → EQ. Keep its settings with that process rather than assuming the same numbers produce an identical curve in another equalizer. Dynamic Equalizer is a separate effect. It doesn't turn every Modern Equalizer band into a compressor. Its [help page still says Suite only](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/proonly/dynamic%20equalizer.htm), while the current [Sound Forge product page describes dynamic EQ](https://www.vegascreativesoftware.com/sound-forge/pricing/). Neither page settles what an older license includes, so if it's missing, check your installed effects and purchase entitlement. The [Modern Equalizer reference](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/modern%20equalizer.htm) documents eight bands, a spectrum display and A/B memories. It also explains the channel and output controls discussed below. You don't need to switch on every feature to make a useful correction. ## Modern Equalizer: Add and Configure Bands 1. **Protect the recording.** Keep an untouched source and work on a separate copy. 2. **Open the chain.** Choose View → Plug-In Chain for the active audio file. 3. **Load Modern Equalizer.** Click Add Plug-Ins to Chain, select Modern Equalizer, click Add, then OK. Select the effect and click Show Plug-In Window. 4. **Add one band.** Click Plus, select the band and choose the filter shape for the problem. Start with both stereo channels unless you specifically need channel-selective processing. 5. **Adjust while listening.** Use Play Normal to audition. Set frequency, gain and bandwidth where applicable; stop when the fault is controlled without damaging wanted sound. 6. **Compare safely.** Keep peaks below clipping. Use Output Gain to compensate for added level, then compare at similar playback loudness with Bypass. If necessary, compare separately level-adjusted reference copies rather than raising an unsafe output. 7. **Keep the useful curve.** Use A and B for two alternatives; the arrow copies between their memories. Save reusable settings through the equalizer’s Menu → Save As. That stores a preset and doesn't save any audio. 8. **Save and check the audio.** Use File → Save As with a new name for an audio file, or File → Render As for a Sound Forge project. Reopen the output with an empty or bypassed playback chain so the EQ doesn't get applied twice. Check the full recording and its final peaks. Use Plus when learning the interface. Double-clicking empty graph space can create a band, but **double-clicking an existing colored band area deletes that filter**. Select a band with one click. For a peaking band, drag horizontally for frequency and vertically for gain; the mouse wheel changes Q. For exact entry, hover over a parameter to reveal its number, then double-click that value and type it. Tab moves to the next value. The white line shows the combined response; it isn't an extra band. Add another filter only when the first one leaves a separate problem unresolved. Two overlapping adjustments can cancel or exaggerate each other. A/B compares two settings; Bypass compares processing with the original. They answer different questions. For example, compare a gentle shelf in A with a narrower bell in B, then bypass the winner. If neither helps at comparable loudness, remove the adjustment. ## Filter Types: What Each One Does Choose the shape before searching for a frequency. Peaking targets a band, shelves change an end of the spectrum, and pass filters attenuate outside a chosen range. **Peaking:** boost or cut around a center frequency. A broad bell can rebalance tone; a narrow cut can control an identified resonance. A frequency suggested for someone else’s voice isn't a preset for yours. Listen to the whole phrase as well as the offending note. Ease off the cut if nearby wanted notes lose their body. With a moving resonance, a fixed narrow band may miss the problem elsewhere in the phrase. **Low Shelving:** raise or lower the low-frequency range rather than progressively removing it. Try this when the [bass balance](https://soundforgepro.com/bass-vs-treble/) is too heavy or light. For unwanted rumble below useful content, consider High Pass instead. **High Shelving:** change the upper-frequency balance. A reduction can soften brightness, but enough high-frequency attenuation to hide hiss may also dull speech or cymbals. EQ can't separate noise from wanted sound at the same frequencies. **High Pass:** attenuate below the cutoff. The Modern Equalizer help gives a 6–36 dB/octave slope range. Raise the cutoff while listening, then back off if the voice or instrument loses wanted body. There is no universally safe 80 Hz setting. **Low Pass:** attenuate above the cutoff. Check consonants, cymbals and room detail before accepting the result; 16 kHz isn't an automatic cleanup boundary. **Band Pass:** keep a middle range while attenuating below and above it. This gives you a restricted-band effect. It won't act as a notch that removes just one middle frequency. ## The Q Control: Broad or Narrow For a bell filter, lower Q means a wider affected range and higher Q narrows it. Modern Equalizer’s pass-filter slope is a separate choice under the three-dot control beside the filter-type icon. Don't read a Q value as dB per octave. Don't copy a Q number blindly from one plug-in to another. The [FabFilter explanation of Q conventions](https://www.fabfilter.com/help/pro-q/using/bandcontrols) notes that equalizers can define bandwidth differently. Match the intended curve and listen, since Q 1 or Q 4 won't sound the same everywhere. “Boost wide, cut narrow” is a shortcut. It isn't a rule. Broad buildup may need a broad cut, and a very narrow cut may catch one note while the rest of the phrase stays unchanged. Set the width to the fault you can hear. If you use a temporary boost to locate a resonance, turn monitoring down first and keep the boost modest. Sweep slowly, then return gain to zero before making the corrective cut. Stop if the sweep becomes uncomfortable. ## Applying EQ to a Selection or the Whole File The [View-based chain processes data-window playback](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/proonly/plug-in%5Fchainer.htm), so a selection won't limit that chain to a local repair. For selected audio, choose **FX Plug-Ins → Apply Plug-In Chain** instead, or use a classic Process → EQ command. Protect the untreated source first. For direct processing, select the intended region in the waveform before opening the dialog. Use Ctrl+A in the data window when you mean to process the whole file. Check both the selected time span and the channels; a local edit to one speaker shouldn't quietly turn into an EQ change across the entire recording. In a classic processing dialog, **Preview** auditions the change, **Bypass** lets you compare, and **OK** commits it. The [processing-dialog reference](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/using%5Fprocessing%5Fdialogs.htm) also explains pre/post-roll, which helps you hear the transition into and out of a selected repair. When different speakers need different curves, treat their sections separately and listen across the boundaries. For a chain containing other effects as well as EQ, the [Plug-In Chainer workflow](https://soundforgepro.com/how-to-use-plug-in-chainer-sound-forge-pro/) distinguishes selection processing from whole-file playback and saving. ## EQ and Clipping: Match Level and Keep Headroom Don't wait for a boost before you check peaks. [iZotope’s explanation of EQ and headroom](https://www.izotope.com/community/blog/headroom-how-to-set-levels-mixing-and-mastering) shows why filtering can raise peaks even when frequencies are being cut. Watch the output while previewing, especially if the source was already close to 0 dBFS. Lower Output Gain if the processed signal approaches clipping. Safe output comes first, so don't raise it again just to match a loud reference. Compare at a similar listening level, using a separately adjusted reference if needed. For a direct process without suitable output trim, reduce the working copy’s level before applying EQ. After saving, reopen and measure the result. Modern Equalizer’s peak display doesn't prove the delivery file is true-peak compliant; use the [loudness and true-peak measurement workflow](https://soundforgepro.com/sound-forge-loudness-meters/) for that check. If a fixed-point export has flattened peaks, making it quieter afterward won't rebuild them. Go back to the clean source and render again. EQ after a limiter can create new peaks, so measure after the complete chain. Whether tonal EQ belongs before or after compression depends on what should drive the compressor. The [full mastering workflow](https://soundforgepro.com/sound-forge-pro-for-mastering/) covers that larger decision, and EQ isn't a mandatory stage in every master. ## Using EQ with the Spectrum Analysis Tool The analyzer can help locate energy, but it can't choose a musical balance for you. Listen to the problem passage, inspect the spectrum, make one change and listen again. A flatter-looking spectrum doesn't mean a better recording. A spectrum can help you find a stable hum and its harmonics, narrow peaks or low-frequency energy. How useful it is depends on the selected passage and resolution. The [Spectrum Analysis guide](https://soundforgepro.com/how-to-use-spectral-analysis-tool-sound-forge-pro/) covers those measurements. Just don't mistake a plot for a diagnosis of why the energy is there. ## Channel controls and oversampling: use only what the job needs Modern Equalizer can target both stereo channels, Left, Right, Mid or Side. Keep both channels for an ordinary stereo tonal adjustment. Its Mono Below control attenuates low-frequency Side content; it isn't a brick-wall cutoff that strips bass from the whole mix. Stereo Width changes Side level. Check the resulting balance and mono playback before you keep a channel-selective edit. The gear-shaped **Settings** button opens the dialog with oversampling (up to 8x) and display options. Higher oversampling needs more processing power, and the maximum isn't automatically the best setting or a cure for clipping. If preview struggles, compare a lower setting and check the saved output before delivery. ## Frequently Asked Questions ### Where is the EQ in Sound Forge Pro? Use Process → EQ for classic Graphic, Paragraphic and Parametric EQ. For Modern Equalizer, open View → Plug-In Chain, click Add Plug-Ins to Chain, select the effect, click Add, then OK. Open its controls with Show Plug-In Window. ### Which equalizer should I use in Sound Forge Pro 2026? Use Modern Equalizer for the visual band-editing workflow in this guide. Use Paragraphic EQ when following its own legacy settings or a direct Process → EQ workflow. Do not copy controls from one interface into instructions for the other. ### How do I add a high-pass filter in Sound Forge Pro? Click Plus in Modern Equalizer, select the new band and choose High Pass. Adjust cutoff and slope while listening. Stop before wanted low-frequency content becomes thin; there is no single cutoff suitable for all recordings. ### What Q value should I use in Sound Forge Modern Equalizer? Choose bandwidth by the audible problem, not a fixed number. Lower Q is broader and higher Q is narrower for a bell filter. Check adjacent wanted notes and compare the result at similar loudness. A Q number copied from another equalizer may not describe the same curve. ### How do I apply EQ without clipping in Sound Forge Pro? Allow for peak changes from cuts as well as boosts. Reduce output gain as needed, preview the complete chain and measure the reopened export. Do not sacrifice headroom to match a louder reference. Normalizing an already flattened waveform does not restore the missing peaks. ### Can I use VST EQ plugins in Sound Forge Pro? Yes. The current Sound Forge product documentation lists VST2 and VST3 support, and Modern Equalizer is a VST effect. A third-party EQ still needs a compatible installation and its own entitlement; an old bundled plug-in license should not be assumed to come with a new purchase. ### Should I use EQ before or after noise reduction in Sound Forge Pro? There is no order that suits every fault. A narrow hum filter can precede broadband noise reduction; tonal shaping can follow cleanup. If a denoiser learns a noise profile, capture it from a noise-only section of the audio actually entering that denoiser, including any earlier filtering. Then compare the full result for lost detail, not just a quieter noise floor. The [background-noise removal workflow](https://soundforgepro.com/how-to-remove-background-noise-in-sound-forge-pro/) covers cleanup beyond EQ. For the profile principle, [Audacity’s noise-reduction manual](https://manual.audacityteam.org/man/noise%5Freduction.html) explains why a representative noise-only sample matters; its menu commands are not Sound Forge commands. Documentation checked September 7, 2026\. Workflow and control names were cross-checked against the linked current help. ### Batch Process Audio Files: Convert, Normalize & QA URL: https://soundforgepro.com/how-to-batch-process-files-sound-forge-pro/ Last updated: 2026-10-09T21:35:49.000Z **Quick answer:** to batch process audio files safely, group only files that share the same delivery requirement, test the full chain on representative sources, and write every result to a new folder. In Sound Forge Pro 2026, choose **Tools → Batch Converter**, add files, build the ordered Processing list, add one or more Renderer/Template outputs, set metadata and naming rules, then run a small pilot before the full job. The dangerous part isn't finding the Run Job button. It's assuming that “all WAVs in this folder” are one valid batch. A folder can mix mono and stereo, 44.1 and 48 kHz, clean and clipped files, speech and music, mastered and unmastered levels. One preset can process every file successfully and still produce the wrong result. This guide covers bulk audio processing on Windows, where a batch can combine format conversion, normalization, VST/effect processing, metadata, naming and output QA. It follows the current Boris FX Sound Forge Pro 2026 help. If you only need a one-off format change, the [single-file conversion guide](https://soundforgepro.com/how-to-convert-audio-files-sound-forge-pro/) is quicker. Use Batch Converter when the same verified rule really does belong on multiple files. ## Decide Whether the Files Belong in One Batch A good batch shares a source class, a process and a destination. “All dialogue pickups from one microphone for the same episode” makes a useful group; “Everything the client sent” doesn't. Split files up when their target format, channel layout, loudness standard, repair needs or creative treatment differ. | Source set | Usually safe to batch | Split before processing | | ------------------------- | ---------------------------------------------------------------- | ------------------------------------------------------------------------------- | | **Podcast or voice-over** | Same mic/room, same episode role, same delivery spec | Host, remote guest, ads and archival inserts with different noise or dynamics | | **Game/UI assets** | Same asset class, channel count, loudness rule and engine format | Loops, one-shots, ambience, dialogue and music | | **Sample library** | Same source session and intended peak/headroom policy | Drums, sustained instruments and already mastered loops | | **Archive conversion** | Verified lossless derivatives with no creative processing | Items needing different rate policies, restoration, speed or channel correction | | **Music delivery** | Alternate formats from approved masters | Unmastered mixes, instrumentals and masters with different loudness decisions | Batch processing is strongest when it repeats a decision you've already made, and weak when every file needs a separate diagnosis. Click repair, noise profiles, de-clipping, trimming and creative EQ often vary by source. A converter can run them automatically; that doesn't make the judgment transferable. ## Audit the Input Set Before Opening Batch Converter Create an inventory before processing. Use file properties or a media inspector for codec, sample rate, sample type and channels; use audio measurements for peak, loudness and silence. No single measurement tells you whether a file also has the right metadata or destination format. - **Format and codec:** WAV, FLAC, MP3, AAC or another container/codec. - **Sample rate:** record each source rate. A mixed-rate set can use a verified source-preserving template, or one deliberate target rate; split the job if those policies differ. - **Bit depth:** note integer versus 32-bit float and whether a reduction will require dither. - **Channels:** mono, stereo or multichannel; a stereo template can silently create waste or routing mistakes for mono assets. - **Duration and silence:** unusually short, long or silent files can expose a wrong selection or broken source. - **Peak, loudness and true peak:** identify outliers before normalization. The [Statistics guide](https://soundforgepro.com/how-to-use-statistics-sound-forge-pro/) covers measurement; the [loudness-meter guide](https://soundforgepro.com/sound-forge-loudness-meters/) covers integrated LUFS and true peak. - **Metadata and names:** check whether existing title, artist, track, BWF or project fields must survive. Move questionable files into a review group instead of making the main preset more complicated. A simple job applied to a clean set is easier to test, rerun and explain than one giant preset full of exceptions. ## Choose Two Representative Test Files One test file proves only that one file worked. Use a pair: 1. **Typical file:** normal duration, level, tone and metadata for the group. 2. **Stress file:** loudest peak, quietest useful signal, longest duration, densest transients or most complicated metadata in the group. If the files are speech, include both sustained vowels and consonant-heavy sections. For music or samples, include a clean transient and a dense passage. If the source set mixes rates, include a representative file from each rate the job will handle, and don't resample a file just to manufacture a test case. Two files are where you start, not where you stop; add tests for other channel layouts or metadata requirements. Every output has to meet the specification without unwanted changes, and a format-only conversion doesn't need to sound any different. ![A batch run in six steps: audit the input, test two files, order the processors, choose the output templates, pilot, then sample the output](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/08/batch-audio-processing-workflow.webp) A reliable Sound Forge batch starts with classification and two test files, not a folder drop. Pilot the job, then sample the outputs. ## Batch Process Audio in Sound Forge Pro: 9-Step Safe Workflow ![The Sound Forge Batch Converter with source files, processing order, export templates and the Run Job button](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/08/batch-converter-2026-processing-export-run-job-v2.webp) Building a Sound Forge Batch Converter job: representative files, ordered processors, explicit output templates and a safe destination before Run Job. 1. **Audit the source set.** Group files that can use the same processing and output policy; verify any mixed formats, rates or channels in the pilot. 2. **Choose a representative pair.** Start with one typical file and one stress file; include additional files for other rates, channel layouts or metadata requirements. 3. **Open Batch Converter.** Choose Tools → Batch Converter and remove any automatically included open files that do not belong. 4. **Add and count the inputs.** Use Add or Add Folder, then compare the displayed count with the inventory; Add Folder does not recurse. 5. **Build the processing order.** Add Effect and Preset pairs in signal order and test every plug-in on the representative pair. 6. **Choose output templates.** Add one or more Renderer and Template rows for the required formats. 7. **Set safe output rules.** Choose a new destination, source-subfolder behavior, metadata and collision-safe naming. 8. **Run and inspect the pilot.** Uncheck every file outside the pilot selection before Run Job. Verify format, channels, duration, levels, sound, metadata and names before reselecting the full set. 9. **Run and sample the full batch.** Compare expected counts, inspect every warning and check risk-based outputs from every source class and renderer. Follow the labels in the current application and the [Sound Forge Pro 2026 Batch Converter help](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/proonly/the%20batch%20converter.htm). The help confirms that Add Folder only includes the selected folder's contents. Preserve source subfolders shapes the output layout later; it won't find nested input files. Count before and after: 80 checked inputs and two outputs per input should produce 160 audio files only if every render succeeds and every destination name is unique. Count audio outputs separately from logs or sidecar files. Investigate missing or extra files before delivery. ## Build the Processing List in Signal Order Under **Processing**, selecting an Effect adds it to the end of the list. Choose its Preset next. Use **Edit** to adjust supported settings and Move Up/Move Down to change order. The order is the signal path: the first item changes what the next item receives. | Stage | Typical purpose | Why it belongs here | Batch caution | | ------------------------ | --------------------------------------------------------- | ------------------------------------------------- | ------------------------------------------------------------------------ | | **Repair/correction** | DC offset, verified hum/notch, isolated technical cleanup | Dynamics and level changes can exaggerate defects | Noise profiles and click damage rarely match every file | | **Corrective EQ/filter** | Known high-pass, resonant cut or tonal correction | Feeds cleaner energy into dynamics | Do not high-pass music, speech and effects at one arbitrary frequency | | **Dynamics** | Compression, limiting or expansion | Changes crest factor and later loudness | Long-term loudness can match while short files react very differently | | **Final level** | Peak or loudness normalization | Measures the processed signal | Use the actual delivery target; protect true-peak headroom | | **Render conversion** | Sample rate, bit depth, channels, codec | Creates the destination file after processing | Plan dither at final integer quantization; avoid repeated lossy encoding | Treat this as starting logic. It isn't a universal mastering chain, and some processes deliberately swap order. What matters is knowing why. Build and audition complicated chains in the [Plug-In Chainer](https://soundforgepro.com/how-to-use-plug-in-chainer-sound-forge-pro/) first, then save only settings that stay stable in offline processing. VST batch processing needs an additional test. Confirm that the plug-in appears, that the intended preset loads and that a representative offline render completes correctly. If a processor is missing, use the [VST discovery and Plug-In Manager checks](https://soundforgepro.com/sound-forge-pro-vst-plugins-not-showing/) before adding it to the job. ## Batch-Normalize Audio to the Right Measurement If the brief says “batch normalize audio,” clarify whether it means equal peak ceilings or comparable perceived loudness before choosing the process. Peak normalization and loudness normalization solve different problems. Peak mode gives each file the same highest sample value, which doesn't make speech, music or sound effects equally loud. Loudness mode measures program energy over time, but its target still belongs to a delivery specification rather than to Sound Forge itself. The AES [loudness normalization overview](https://aes2.org/resources/audio-topics/loudness-project/loudness-normalization/) describes normalization as matching file-based content to a target loudness and explicitly recognizes batch use. That doesn't make −14 LUFS a universal setting. Podcasts, broadcast, streaming masters, game assets, voice assistants and internal review files can require different integrated loudness, true-peak and channel rules. - Use **peak normalization** when the specification is about maximum sample peak and you aren't aiming for perceived consistency. - Use **loudness normalization** when comparable perceived level is required across like-for-like program files. - Don’t normalize an album track-by-track when intentional level relationships should survive. - Don’t force very short effects or one-word files through a long-form integrated-loudness rule without testing how the meter behaves. - Measure true peak after lossy encoding when the destination imposes a ceiling. The [Normalize guide](https://soundforgepro.com/how-to-normalize-audio-in-sound-forge-pro/) separates Peak, RMS and Loudness modes. Constant-gain normalization leaves the dynamics alone. Sound Forge's Loudness dialog also offers optional dynamic limiting, while RMS mode has clipping-response options, so check those settings explicitly: turning on dynamics processing can change the sound even when the measured level hits the target. See the [Normalize controls and short-file warning](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/proonly/normalizing%5Faudio.htm): dynamic-range adjustment isn't available for files under 30 seconds. Test short assets separately instead of copying long-program settings. ## Treat Metadata and Watermark as Batch-Wide Edits Metadata fields entered in Batch Converter apply to the outputs in the job. With **Overwrite** off, existing destination values are preserved; keywords are appended. With Overwrite on, existing values are replaced, and a blank batch field can erase the existing value. The official help also warns that a metadata type unsupported by the output format is ignored. That makes shared metadata fine for publisher, copyright, project, album or common comment fields. It's unsafe for track title, episode number, scene, speaker or asset ID unless every file really does share the value. Keep a metadata sample from before and after the pilot, because MP3 ID3, FLAC Vorbis comments, RIFF INFO and BWF fields don't expose identical field sets. The Watermark section mixes a selected audio file into every output. That's audio processing rather than a hidden ownership tag. Check start time, duration, channel layout and level against the shortest and quietest source. An audible ident that fits a two-minute preview can cover most of a half-second UI sound. ## Add One or More Output Formats Under **Export Formats**, choose a Renderer and output template. Add another renderer when the same approved source needs more than one delivery: for example, 24-bit WAV masters plus MP3 review copies. Sound Forge can create multiple output formats in one job. **Default Template** tries to keep source attributes wherever the renderer supports them. It can't make an incompatible codec keep every rate, sample type or channel layout; FLAC, for example, doesn't accept floating-point samples. Check a representative export before running the full batch with it. Choose or build a specific template when every output must share a codec, rate, depth or channel layout. The [FLAC format FAQ](https://xiph.org/flac/faq.html) explains the integer-sample limitation, and no Sound Forge preset can override it. - **WAV/PCM:** suitable for lossless masters, interchange and further processing. - **FLAC:** lossless compression of supported integer PCM for storage or compatible delivery. Keep a floating-point master in its original format; converting it to integer PCM for FLAC must not be assumed to preserve every float sample. - **MP3:** listening or platform derivatives. Make them from the approved lossless source, never from an older lossy file. - **Mono/stereo conversion:** use an explicit channel rule and audition phase/level. The [Channel Converter guide](https://soundforgepro.com/sound-forge-channel-converter/) covers downmix decisions. - **Sample-rate conversion:** choose the destination requirement once. The [sample-rate guide](https://soundforgepro.com/how-to-change-sample-rate-sound-forge-pro/) separates resampling from a header-only playback-rate change. - **Bit-depth reduction:** consider dither at the final quantization into an integer output, including after floating-point processing. The [bit-depth and dither guide](https://soundforgepro.com/sound-forge-bit-depth-dither/) covers 24-to-16-bit delivery. The current [Custom File Templates help](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/templates.htm) says built-in templates cannot be edited. Create a named custom template instead. Custom .sft2 rendering templates live under the user's AppData/Roaming/BorisFX/Render Templates tree and can be copied to another account or workstation; version them with the delivery specification so “Podcast MP3” does not silently change meaning. ## Choose a Safe Output Folder and Naming Rule ![A batch output folder and suffix rule that keeps processed files away from the originals](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/08/batch-output-naming-v2.webp) Sound Forge batch output rules: a separate folder, predictable suffixes, and a verified file count before the full run. Open **Options** for export location and file naming. The safest first run is a new, empty destination outside the source tree. Avoid **Same as source** until collision behavior and filenames have been proven on copies. | Option | Useful for | Risk to check | | ------------------------------ | ---------------------------------------- | ------------------------------------------------------------------- | | **Save files to** | Clean delivery root and easy rollback | Wrong drive, permissions or stale files from a previous run | | **Preserve source subfolders** | Mirroring an already audited input tree | It preserves output structure; it does not add nested inputs | | **Same as source name** | One renderer in a separate folder | Collisions when several renderers share an extension or destination | | **Append to name** | Review suffixes such as -preview or -48k | Duplicate suffixes after reruns and downstream naming limits | Before Run Job, write the expected naming example in plain text: **DoorSlam\_07.wav → DoorSlam\_07-preview.mp3**. Check case, spaces, Unicode characters, duplicate basenames from different folders and maximum path length. If the destination already contains files, move it aside or use a new run folder so the output count remains meaningful. ## Run a Pilot Before the Full Folder 1. Include only the typical and stress files, plus any additional files needed to cover other source properties. 2. Run the complete processing and every output renderer. 3. Re-open the outputs in a fresh Sound Forge window or another trusted player. 4. Compare duration, sample rate, bit depth, channels and metadata with the specification. 5. Measure peak, loudness and true peak where required. 6. Listen to the start, loudest passage, quietest useful passage and end. 7. Check for clipped peaks, truncated tails, missing channels, unexpected noise or non-silent tails, codec artifacts and wrong filenames. 8. Only then restore the full file list and run the job. A progress bar tells you the application finished. It says nothing about whether the output is right. Keep the source inventory and the expected output count next to the job. If one renderer fails, don't assume the other outputs are fine; check the status and rerun only after you've worked out whether the problem was a file, a plug-in, a template, a path or storage. ## Sample the Full Batch After It Finishes ![A QA sampling plan covering the first, middle, last and most extreme files in a batch](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/08/batch-qa-matrix-v2.webp) Batch QA in Sound Forge: count the outputs, sample first, middle, last and extreme files, and inspect every warning directly. For a small job, inspect every output. For a large one, use a documented, risk-based sample. The orange “mandatory” marks in the diagram above flag higher-risk checks in this editorial workflow. - first and last file alphabetically; - shortest and longest duration; - quietest and loudest source from the audit; - at least one file from each source subfolder or content class; - every error, warning or unexpected file-size outlier; - one output from each Renderer/Template combination. Then compare total input count, renderer count and output count, and scan for zero-byte files, duplicate names, missing extensions and outputs with suspiciously small or large sizes. Spot-check metadata in the destination application as well as in Sound Forge. For lossy delivery, audition transients and high-frequency material, because codec artifacts can pass a peak or loudness test; that listening pass is part of quality control. Keep a record of the job status, preset name, template name, Sound Forge version and date with the delivery. A repeatable batch is valuable only when another run can reproduce the same choices. ## Save and Maintain Batch Presets Use **Add** in the preset pane after the pilot passes. Give the preset a purpose and revision, not a vague name: **VO\_review\_MP3\_48k\_v3** tells you more than **Speech**. Folders can group presets by client, destination or workflow. Batch presets can't be edited in place. Before changing one, note its settings and destination so the original job stays recoverable. Load it, make your changes, then use Add to save a new, clearly named revision. Keep the old revision until the replacement passes its pilot; the help's delete-and-recreate procedure is no reason to throw away your only record of a working job. A tested preset can be exposed as an **Instant Action** or under **Sound Forge Pro 2026 Custom Actions** in the Windows Explorer context menu. This is useful for mature, low-risk jobs such as approved review-copy conversion. Never expose an overwrite-capable or creative processing job until its destination and collision behavior are impossible to misunderstand. ## Use Separate Jobs for Different Delivery Scenarios ### WAV to MP3 review copies Start from approved lossless masters. Clear the Processing list and disable Watermark, including any settings inherited from a loaded preset. Add an MP3 renderer/template, preserve names in a separate review folder, and copy only shared metadata. Don’t add normalization merely because the file format changes. The [MP3 export guide](https://soundforgepro.com/how-to-export-mp3-from-sound-forge-pro/) covers bitrate and metadata decisions without assuming one universal setting. ### Voice-over or podcast pickups Group by microphone, room, speaker role and destination, then test noise and dynamics on the noisiest/quietest file plus the loudest performance. Normalize to the actual program or asset specification, and keep editorial trims and content-dependent noise repair out of the batch unless every boundary has been reviewed. ### Game and interface assets Split mono, stereo, loops and one-shots. Confirm engine sample rate, bit depth, channel policy, loop metadata and naming limits. A tiny UI click and a long ambience shouldn't share a loudness or trimming assumption just because both are WAV files. ### Archive derivatives Keep preservation masters untouched. For a conversion-only job, clear Processing and disable Watermark before creating access FLAC or listening copies, preserve source subfolders only after verifying the tree, and compare metadata before and after. A whole-file checksum checks whether a file has changed; a WAV and its FLAC derivative need not have the same checksum. For a lossless-conversion check, compare decoded PCM using the same sample representation, channel layout and rate. Don’t run denoise, normalization or channel conversion unless the derivative policy explicitly requires it. Float peaks above 0 dBFS need level correction before integer export to avoid clipping. [Sound Devices' float-to-24-bit workflow](https://guides.sounddevices.com/sd-utility/) illustrates why this conversion requires a level decision; do not assume Sound Forge performs the same automatic correction. ## Troubleshoot a Failed or Wrong Batch - **Expected files are missing:** Add Folder does not recurse. Add each folder deliberately or prepare an audited flat set. - **Extra files appear:** open Sound Forge data windows got included automatically, or an old destination wasn't emptied. - **VST is missing or fails:** verify plug-in scan, architecture, license and preset in a normal file first. - **Output format is wrong:** check Renderer and Template separately; Default Template still depends on the renderer supporting the source properties. - **Metadata disappeared:** the target format may not support the field, or Overwrite/blank fields replaced it. - **Names collide:** use a clean destination, suffix or preserved source-folder structure. - **Files sound inconsistent after peak normalization:** peak level and perceived loudness are different things; regroup and pick the right measurement. - **A job does not start:** confirm which files are checked and which output templates are set up, then note any error shown. Diagnose that specific message, since failures don't all share one cause. ## When to Use Sound Forge, Audacity or a Script Sound Forge fits Windows audio batch processing when you want an inspectable GUI, ordered effects, renderer templates, multiple formats, metadata, naming rules and reusable Explorer actions. Use it after the same chain has passed representative offline renders and listening checks. For a free fixed-command workflow, [Audacity 3.x provides Macros](https://manual.audacityteam.org/man/macros.html). The [Audacity 4.0 release notes](https://www.audacityteam.org/changelog/) list Macro Manager and the scripting pipe as unavailable, so don't move an established macro workflow to 4.0 without checking it first. For recursive discovery, conditional rules, machine-readable logs or server work, look at FFmpeg with a shell script or a dedicated pipeline. Source protection, path quoting, codec availability and output QA still need deliberate design either way. ## Batch Audio Processing FAQ ### Where is Batch Converter in Sound Forge Pro 2026? Choose Tools → Batch Converter. The current dialog contains Files to Process, Processing, Metadata, Watermark, Export Formats, output Options, preset management, Status and Run Job. ### How do I batch-convert WAV files to MP3? Clear the Processing list and disable Watermark first, including settings inherited from a loaded preset. Add the approved WAV sources, an MP3 Renderer and verified Template, then a separate output folder and naming rule. Leave only the pilot files checked for the first run. Inspect their outputs before selecting the full batch. ### Can Sound Forge batch-normalize multiple files? Yes. Add the appropriate Normalize process/preset to the ordered Processing list. Choose Peak or Loudness according to the delivery specification, test unlike files separately and verify true peak after lossy encoding when required. ### Can one batch create WAV and MP3 files? Yes. Add multiple Renderer/Template rows under Export Formats. Confirm the expected output count and make sure naming and destination rules cannot cause collisions. ### Does Add Folder include subfolders? No. Sound Forge 2026 documentation says Add Folder adds only the selected folder's contents. Preserve source subfolders mirrors output structure for files already in the job; it does not discover nested inputs. ### How do I process files without changing their sample rate or channels? Use Default Template only when the selected renderer supports the source attributes. Verify the sample rate, sample type and channel count in a pilot output; unsupported combinations cannot be preserved by choosing a default. ### Can I edit an existing Batch Converter preset? Not in place. Record the original settings, load the preset, make the changes and use Add to save a separately named revision. Keep the old revision until the new job passes its pilot. ### How many batch outputs should I quality-check? Inspect every file in a small job. For a large job, document a risk-based sample that includes duration and level extremes, first and last files, every warning or outlier, each source class or folder, and every Renderer/Template combination. Documentation checked September 9, 2026\. This is a source-verified workflow, not a report of an in-app batch-processing test. ### How to Use the Spectral Analysis Tool in Sound Forge Pro URL: https://soundforgepro.com/how-to-use-spectral-analysis-tool-sound-forge-pro/ Last updated: 2026-10-09T22:13:44.000Z Sound Forge calls its spectral analysis window **Spectrum Analysis**. Open it from **View → Spectrum Analysis**. The spectrum graph shows frequency on the horizontal axis and level in dB on the vertical axis. The Sonogram adds time, so you can see when a hum, click, resonance, or burst of hiss occurs. Both views measure audio; neither edits it. RX calls the same view a spectrogram; see [how to read the RX spectrogram](https://izotoperx.net/how-to-read-izotope-rx-spectrogram/). *Part of the [Sound Forge restoration hub](https://soundforgepro.com/tag/sound-forge-restoration-guides/). For the editor, pricing, and current Boris FX lineup, start with the [complete Sound Forge guide](https://soundforgepro.com/).* Quick answer: select the passage, open **View → Spectrum Analysis**, choose **Normal Display**, and click **Refresh**. In Settings, start with FFT 4096 or 8192 and one slice. Store a baseline with **Set → 1**. For a static before-and-after comparison, apply the processing to a working copy and refresh the same region. An EQ that's only playing through the Plug-In Chain needs output monitoring instead, because refreshing the unprocessed source won't show the EQ at all. ## Spectrum Analysis, Spectroscope, and WaveColor serve different jobs Sound Forge Pro has three related frequency displays. Their names overlap, but their jobs don't. **Spectrum Analysis** is the detailed FFT window. It can analyze a selection or the audio after the cursor, show precise frequency and amplitude values, switch to a Sonogram, monitor a signal, and store four comparison snapshots. Use it when a decision needs evidence you can reproduce. Spectroscope divides the signal into [frequency ranges](https://soundforgepro.com/audio-frequency-chart/) and displays the level in each band. The [Spectroscope help](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/spectroscope.htm) also documents appearance presets. Use that band-level view for an overview; use Spectrum Analysis for the four-slot comparison workflow below. [**WaveColor**](https://soundforgepro.com/how-to-use-wavecolor-in-sound-forge-pro/) colors the waveform itself. According to the [current WaveColor help](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/wavecoloring.htm), hue represents pitch range and saturation indicates how tonal or noise-like the signal is. It helps you locate suspicious regions before opening the analyzer, though it won't give you a numeric frequency readout. A practical sequence: WaveColor to locate, Spectrum Analysis to measure and compare, then listening to decide. Keep Spectroscope visible when a continuous band-level view is more useful than a stored before-and-after graph. ## A six-step Spectrum Analysis workflow The analyzer becomes useful when every comparison is repeatable. Change one variable at a time and keep the source region and analysis settings fixed. 1. **Select a representative region.** Choose the passage containing the peak, hum, hiss, or tonal balance you need to inspect. Keep its start and end points fixed. Preserve an untouched original before processing a working copy. 2. **Open Spectrum Analysis and refresh.** Choose View → Spectrum Analysis, select Normal Display, and click Refresh for a static reading. Auto Refresh follows selection changes; it won't switch on playback monitoring. 3. **Choose the FFT settings.** Click Settings. Start at FFT 4096 or 8192 for general diagnosis and set Slices displayed to 1 for snapshots. Keep the FFT overlap and smoothing window fixed. Blackman-Harris is a low-leakage option, though it isn't the right default for everything. 4. **Read the axes and cursor value.** Read frequency on the horizontal axis and level in dB on the vertical axis. Hover over a repeatable feature for its frequency and level, then confirm what it sounds like by listening. 5. **Store the baseline with Set and a slot.** Click Set, then snapshot 1, 2, 3 or 4\. Keep the region, FFT size, overlap, window, channel and display range unchanged. Snapshots store curves; they don't back up any audio. 6. **Measure the processed copy and listen.** Apply one EQ or repair change to the working copy, then refresh the same region and compare its graph with the baseline. If the effect is only in the playback chain, use Monitor Output in the spectrum graph and start playback from the Plug-In Chain instead. Level-match processed and original audio before deciding whether the change helps. ## 1\. Select the passage before choosing settings Select a passage that contains the issue without surrounding material hiding it. A sustained hum needs enough time to reveal its tone and harmonics; for a click, begin around the event and include some audio on either side. For mastering, inspect a representative loud or dense passage, then quieter sections separately. Keep an untouched original and make processing changes on a working copy. Open **View → Spectrum Analysis**. Click **Refresh** for a fixed reading. Enable **Auto Refresh** when you want the graph to follow a changing selection. The [current Spectrum Graph documentation](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/proonly/viewing%5Fa%5Fspectrum%5Fgraph.htm) states that when no selection exists, Sound Forge analyzes samples after the cursor. A deliberate selection is safer for before-and-after work because it gives you the same source every time. ## 2\. Read the graph before chasing a peak ![Spectrum graph axes with peak, noise floor, and cursor reading checks](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/08/spectrum-reading-desktop-v1.webp) Read the graph in order: keep the region consistent, inspect peaks and the floor, then use the cursor for an exact frequency and level. The horizontal axis is frequency and the vertical axis is amplitude in dB. A tall peak means the selected passage has more energy around that frequency, which doesn't make the peak a problem. Hover over it for the frequency and level readout, then loop the same passage and listen. If the tooltip is missing, right-click the graph and turn on Show Position. Show Notes gives you the nearest musical note, and Show Statistics toggles the bottom readout. These displays report where the cursor is, which isn't necessarily the source’s fundamental pitch. Treat the low, uneven line between the prominent peaks as context. It isn't a target curve. A speech recording, a cymbal hit and a mastered song shouldn't share one spectral shape, so compare the same source under the same settings. If an improvement only shows up after you change the selection, display range or FFT size, the comparison hasn't told you anything. ## 3\. Choose FFT size for the question Click **Settings** in the Spectrum Analysis window to pick FFT size, overlap, smoothing window and slices. FFT size is the number of samples in each analysis window. Bin spacing is sample rate ÷ FFT size, and window duration is FFT size ÷ sample rate. A larger FFT gives closer frequency bins but covers a longer stretch of time and takes more processing. Close bins don't guarantee you can tell two tones apart, since window shape, leakage and relative levels matter too. The [Spectrum Settings documentation](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/proonly/change%5Fspectrum%5Fanalysis%5Fsettings.htm) explains these controls. | FFT size | Approx. bin spacing at 44.1 kHz | Practical use | | -------- | ------------------------------- | -------------------------------------------------- | | 2048 | 21.5 Hz | Fast refresh and broad movement | | 4096 | 10.8 Hz | General diagnosis | | 8192 | 5.4 Hz | Closer resonances and harmonics | | 16384 | 2.7 Hz | Narrow features when slower response is acceptable | ![FFT size and smoothing window tradeoffs at a 44.1 kHz sample rate](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/08/fft-window-tradeoff-desktop-v1.webp) At 44.1 kHz, a larger FFT narrows the frequency bins but uses a longer time window. Window choice changes leakage and peak shape. Start with 4096 or 8192 for general EQ and noise diagnosis. Drop to 2048 when refresh speed matters more than narrow-bin detail, or go to 16384 when a narrow feature needs a closer look. Treat these as starting points rather than diagnostic presets. At 44.1 kHz, an 8192-sample window spans about 186 ms, which makes it a poor way to pin down the timing of a very short click. Leave **FFT overlap** unchanged for comparisons; raising it makes the analyzer run more overlapping FFT calculations. The smoothing window changes leakage and peak shape. Boris FX describes Blackman-Harris as the lowest-sideband-leakage option with rounded peaks. Rectangle keeps a sharp central peak but produces high leakage, and Hamming and Hanning are common audio windows. Blackman-Harris is useful when leakage would hide a nearby component; it isn't a universal best choice. ## 4\. Set the display without changing the audio Use the arrow beside **Normal Display** to choose Line Graph, Filled Graph, or Bar Graph. The same data can look different as a line, a filled shape, or bars. If real-time refresh feels sluggish, Boris FX recommends trying Line Graph first. Right-click the graph for a **Logarithmic** frequency display, which gives lower octaves more room than a linear axis, where equal distances mean equal differences in hertz. The graph runs up to the Nyquist frequency, half the file’s sample rate: 22.05 kHz for 44.1 kHz audio. **Normalize dB** rescales the vertical view to fit the displayed data and leaves the audio file untouched. For before-and-after comparisons, keep the amplitude range fixed so a rescaled graph doesn't pass for a level change. **Settings → Slices displayed** controls how many successive FFT slices the graph shows. More than one slice disables snapshots. Use multiple slices to inspect movement; return to **1** and **Normal Display** when you need stored overlays. ## 5\. Compare before and after with Set and slots 1–4 In **Normal Display** with **Slices displayed = 1**, click **Set**, then a numbered slot from **1–4**. For a static EQ comparison, process a working copy, select the same passage and click Refresh again, leaving the baseline curve visible over the new graph. If you only tweak a playback-only effect and refresh the unprocessed source, you've just measured the source again. The monitoring section below covers the live chain. ![Sound Forge Spectrum Analysis snapshot workflow using Set and slots 1 through 4](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/08/spectrum-snapshot-workflow-desktop-v1.webp) Keep the audio region and analysis settings fixed, store a slot with Set, make one change, then refresh and overlay. Keep the selection, FFT size, FFT overlap, smoothing window, channel and display range identical, or you'll be comparing different measurements. Slot 1 can hold the original curve, slot 2 a restrained correction and slot 3 another candidate. A different reference recording in slot 4 can help with broad tonal context, but don't treat its curve as a target to copy, because the performance, arrangement and level may all differ. Click a numbered snapshot button to show or hide its curve. **Set** followed by an occupied slot overwrites that snapshot, and **Clear All Snapshots** removes all four. They're measurement curves, not saved audio or an undo history. Snapshots aren't available in Sonogram mode or when Slices displayed is greater than 1. ## 6\. Use the Sonogram when time is part of the problem ![Spectrum graph and Sonogram comparison with monitoring and snapshot limits](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/08/spectrum-vs-sonogram-desktop-v1.webp) Use the spectrum graph for precise frequency comparison and snapshots; use the Sonogram to see when spectral events occur. The Sonogram plots time on the X-axis, frequency on the Y-axis, and amplitude as color intensity. Steady hum can show up as horizontal lines, often around 50 or 60 Hz with harmonics above, and a short click can show up as a vertical streak. Hiss spreads across the band instead of sitting at one frequency. Read these as clues. A sustained instrument also leaves horizontal traces, and useful percussion makes short transients, so listen to the selected event before you pick a repair. The examples in [iZotope’s spectrogram guide](https://www.izotope.com/en/learn/understanding-spectrograms.html) illustrate noise patterns, but its RX repair commands aren't Sound Forge menu paths. Select a passage and click **Sonogram**. The [Sonogram guide](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/proonly/view%5Fa%5Fsonogram.htm) warns that long selections take longer to analyze and blur time detail. If the display looks blocky, open Settings, enable **Set sonogram resolution** and try raising its value toward **200**, the help page’s example. That number counts FFT samplings; it isn't 200 Hz or the FFT size. More samplings sharpen horizontal detail at a processing cost, while a larger FFT deals with frequency detail. Use the menu beside Sonogram to choose Color or Black and White. In Color mode, drag the slider below the graph to change display intensity and read the dB color scale at the lower right. These are view controls; they don't process the selected audio. There are two limits worth knowing. Snapshots don't work in Sonogram mode, and real-time output monitoring is unavailable there too. If you choose Monitor Output, the Sonogram shows a playback-position cursor rather than a live post-processing spectral update. Return to the spectrum graph when you need to watch the processed output or compare stored curves. ## Real-time monitoring: use the graph for processed output Open the arrow next to **Real-Time Monitoring**. **Monitor Input** follows the Record device on the Audio tab of Preferences and works in both the spectrum graph and Sonogram. **Monitor Output** follows the Playback device; use the spectrum graph for its live frequency display. To analyze the signal after processing, the graph help specifically says to **start playback from the Plug-In Chain**. Auto Refresh only tracks selection changes and won't pick up the processed output. If live analysis is slow, try Line Graph, a smaller FFT or fewer displayed snapshots. For a repeatable static comparison, stop playback and measure the original and processed copies over the same fixed region. If the graph seems frozen after you stop, check **Settings → Maintain last monitored view**, which can keep the last live display on screen on purpose. **Hold peaks** adds peak markers, and those markers aren't the current instantaneous spectrum. ## Turn a measurement into an audio decision A spectrum analyzer can locate a repeatable feature, but it can't tell you whether that feature belongs in the recording. For a suspected resonance, loop the passage, read the frequency, make a small EQ move, and level-match Bypass before deciding. The [Sound Forge equalizer workflow](https://soundforgepro.com/how-to-use-equalizer-sound-forge-pro/) covers that correction step. For hum or broadband noise, diagnose the pattern before processing. The [hiss and hum guide](https://soundforgepro.com/remove-hiss-hum-sound-forge/) separates steady electrical tones from broadband noise, while the [background-noise guide](https://soundforgepro.com/how-to-remove-background-noise-in-sound-forge-pro/) explains capture-and-reduction workflows. For final tonal checks, use Spectrum Analysis alongside Statistics and listening in the [Sound Forge mastering workflow](https://soundforgepro.com/how-to-master-a-track-in-sound-forge-pro/). ## What Spectrum Analysis cannot do Spectrum Analysis is a viewer. It won't let you paint out a bird chirp, isolate one voice or redraw a harmonic. The [current ARA integration documentation](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/proonly/ara.htm) describes integrated editing with a separately installed, compatible SpectraLayers VST3 plug-in. The [current Sound Forge plan comparison](https://www.soundforge.com/sound-forge/pricing/) lists VST2, VST3 and ARA support but doesn't include SpectraLayers in Sound Forge or Sound Forge Plus. Check the license for the separate editor before you plan around that workflow. The safest division is simple: Spectrum Analysis identifies and measures, a processor changes the audio, snapshots verify the measured difference, and a level-matched listening comparison decides whether the change is useful. ## Frequently Asked Questions ### Where is the Spectral Analysis tool in Sound Forge Pro? Choose View → Spectrum Analysis. Sound Forge labels the window Spectrum Analysis. Select a short audio region and click Refresh, or enable Auto Refresh while moving the selection. ### What FFT size should I use in Sound Forge Spectrum Analysis? Open Settings and start with FFT 4096 or 8192 for general diagnosis. Try 2048 for faster response or 16384 for narrow features. At the same sample rate, a larger FFT gives closer frequency bins but uses a longer time window and takes more processing. Window shape and leakage still affect whether nearby tones can be separated. ### Is Blackman-Harris the best smoothing window? No single window is best for every measurement. Blackman-Harris has low sideband leakage and rounded peaks. Rectangle produces a sharper peak with high leakage. Choose the window for the question and keep it unchanged during comparisons. ### How do I compare before and after EQ in Spectrum Analysis? Use Normal Display with Slices displayed set to 1\. Measure a fixed region, click Set and a slot from 1–4, process a working copy, then refresh that same region with unchanged FFT size, overlap, window, channel, and display range. For an effect that only runs in the playback chain, use Monitor Output in the spectrum graph and start playback from the Plug-In Chain instead. Level-match processed and original audio when listening. ### What is the difference between the spectrum graph and the Sonogram? The spectrum graph plots level against frequency and supports snapshots plus real-time input or output monitoring. The Sonogram adds time and shows amplitude as color intensity. It supports input monitoring, but not snapshots or real-time output analysis; Monitor Output only adds a playback-position cursor there. ### Does Sound Forge Audio Studio have Spectrum Analysis? Boris FX currently sells Sound Forge and Sound Forge Plus rather than a separate Audio Studio tier. Legacy Audio Studio features vary by version, so check View → Spectrum Analysis in that installation instead of assuming the Pro workflow is present. ### Why is Spectrum Analysis slow or sluggish? Switch to Line Graph, reduce FFT size, or turn off snapshots. If live monitoring still lags, use Refresh on a short fixed selection. In Sonogram mode, reduce the number of samplings or FFT size when processing time is the problem. Last fact-checked: September 8, 2026 against the Sound Forge 2026 Spectrum Graph, Spectrum Settings, Sonogram, Spectroscope, WaveColor, ARA integration, and current plan documentation, with iZotope’s explanation of spectrogram noise patterns. Menu paths here follow that documentation. ### Master a Track in Sound Forge Pro: 5-Step Workflow URL: https://soundforgepro.com/how-to-master-a-track-in-sound-forge-pro/ Last updated: 2026-10-06T07:46:35.000Z To master one finished stereo track in Sound Forge Pro 2026, work through five checkpoints: measure the untouched mix, correct broad tonal balance, control dynamics with Wave Hammer, verify loudness and peaks, then save and reopen the exported file. Keep every comparison level-matched, and if a processor doesn't solve a problem you can hear, remove it. This page is the short execution workflow. The [full Sound Forge mastering guide](https://soundforgepro.com/sound-forge-pro-for-mastering/) covers album sequencing, multiple deliverables and wider platform decisions. Here the job is narrower: finish one stereo file without relying on a preset or a universal loudness number. **Quick answer:** run **Tools → Statistics**, make small gain-matched corrections in Modern Equalizer, use the compressor and Volume Maximizer inside Wave Hammer as two separate decisions, rescan the complete file, convert bit depth only when the delivery format requires it, then reopen and check the saved master. ## The five-step Sound Forge mastering workflow 1. **Measure the untouched source.** Save the whole-track, both-channel Statistics baseline before processing. 2. **Balance the spectrum.** Use Modern Equalizer only for problems that survive a level-matched bypass check. 3. **Control dynamics.** Set Wave Hammer compression first, then decide how much final level the Volume Maximizer can add cleanly. 4. **Verify the result.** Save and reopen the processed file with no extra chain applied, then rescan loudness and sample/true peaks. Make any final integer conversion after the remaining processing. 5. **Export and reopen.** Inspect and listen to the file that will actually be delivered. In the decision map below, the Wave Hammer box contains its two internal processors; the bit-depth branch is conditional rather than a required mastering effect. ![Five-step Sound Forge mastering workflow from Statistics through export verification](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/08/mastering-five-checkpoints-desktop-v1.webp) Measure first, make controlled EQ and Wave Hammer decisions, verify the result, then reopen the exported master. ## Before processing: protect the source and know when to stop Start from the finished stereo mix at its native sample rate and bit depth, and save a copy before touching the waveform. This stereo-file chain changes the combined mix. It does not give you the original vocal, snare and bass faders back; when the multitrack session is available, fix those balances there. Return to the mix when any of these problems is obvious: - the source already clips or has audible distortion; - one instrument or vocal needs a level change that affects only that element; - the stereo bus is already limited so heavily that transients no longer recover; - a narrow resonance moves with the melody and a static master-bus cut damages other notes; - the requested loudness needs more limiting than the mix can take cleanly. A mastering chain should improve a finished mix. It shouldn't stand in for a mix revision that's still possible. ## Step 1: Measure the untouched file with Statistics Select the complete track and both stereo channels, then choose **Tools → Statistics**. The current [Sound Forge 2026 Statistics help](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/statistics.htm) documents the values below. Use **Copy to clipboard** to keep a baseline report with the filename and selection length. The [Statistics guide explains the scan fields](https://soundforgepro.com/how-to-use-statistics-sound-forge-pro/) if you need to inspect a suspicious value. | Readout | What it tells you | How to use it | | ------------------------------------- | -------------------------------------------------------- | ----------------------------------------------------------------------------------------------- | | **Minimum and maximum sample values** | Negative and positive sample extremes | Use the greatest absolute amplitude for sample headroom; one extreme alone can miss an overload | | **Maximum true peak** | An oversampled peak estimate | Check peaks that can appear between stored samples | | **Filtered true peak** | The larger filtered or unfiltered true-peak result | Catch readings affected by asymmetry or DC offset | | **Integrated LUFS** | Weighted, gated program loudness over the selected track | Compare the source, brief and final render | | **Maximum short-term** | The loudest three-second integration window | Locate sections that dominate perceived loudness | | **Maximum momentary** | The loudest 400 ms window | Inspect brief loud passages without treating them as the whole song | | **LRA** | Distribution of loudness through the program | Track broad dynamic change, not a quality score | These numbers describe the selected audio, not an uncommitted effects preview. A peak below full scale does not prove that an earlier clipping distortion has disappeared. Sound Forge labels its true-peak fields dB FS in the help; distinguish those fields from sample peak when comparing with a dBTP delivery limit. For material shorter than a minute, [EBU R128 does not recommend LRA](https://tech.ebu.ch/files/live/sites/tech/files/shared/r/r128v5%5F0.pdf) because too few three-second values are available. None of these readings prescribes a universal music-master target. A quieter track can be healthy, and a louder one can still have useful dynamics. Note what the music is doing before deciding what has to change. ## Step 2: Correct broad balance with Modern Equalizer Open **View → Plug-In Chain**, click **Add Plug-Ins to Chain**, select Modern Equalizer, click **Add**, then **OK**. Loop a dense and a quieter passage to compare settings. The [current Plug-In Chain help](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/proonly/plug-in%5Fchainer.htm) distinguishes real-time preview from the processing applied when you save the audio. Keep the untouched source separately; do not overwrite it while testing. The [current Modern Equalizer documentation](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/modern%20equalizer.htm) describes an eight-band parametric EQ with high-pass, low-pass, shelf, peaking and band-pass filters, Left/Right/Mid/Side processing, Output Gain, A/B memories, Bypass and oversampling up to 8×. Make one broad correction at a time: match the processed level with Output Gain, switch Bypass, and listen again. The focused [Modern Equalizer guide](https://soundforgepro.com/how-to-use-equalizer-sound-forge-pro/) covers the band and channel controls. A broad 1 dB move can be consequential on a stereo mix, and there's no reliable recipe that says every master needs a cut at 200 Hz or a boost at 8 kHz. Use the analyzer to locate energy, then use references and hearing to decide whether that energy is a problem. If the EQ curve becomes a collection of narrow repairs, stop and ask whether the mix or an earlier stem is the better place to work. ## Step 3: Treat Wave Hammer as two decisions inside one plug-in The [official Wave Hammer help](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/proonly/wave%5Fhammer-overview.htm) is explicit: Wave Hammer is one mastering plug-in containing a classic compressor and a Volume Maximizer. This means the classic Wave Hammer, not [Wave Hammer 2.0, which uses up to four frequency bands](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/proonly/wave%20hammer%202.0.htm). Add the classic effect after the EQ in the same chain. Its compressor and maximizer solve different problems; neither must work hard just because it is available. The [classic Wave Hammer guide](https://soundforgepro.com/sound-forge-wave-hammer/) separates their controls and the legacy-interface caveats. ![Wave Hammer as one plug-in containing compressor and Volume Maximizer stages](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/08/wave-hammer-two-decisions-desktop-v1.webp) Wave Hammer is one plug-in: control peaks in the compressor, then decide how much final level the Volume Maximizer can add cleanly. ### First decision: compressor Evaluate the compressor without added maximization first. Use the effect’s **?** help to confirm the stage controls in your build; the current web overview does not document every button. Adjust compression while listening to the loudest sections, transitions and sustained notes. The goal is controlled movement, not a particular ratio or attack time. Reduce the processing when the groove becomes smaller, cymbal decay jumps forward, consonants spit or the low end pumps between kicks, then match the bypass level. If the compressed version wins only while it's louder, the comparison hasn't proved an improvement. ### Second decision: Volume Maximizer After the compressor decision is stable, adjust the Volume Maximizer. Increase its contribution gradually, stopping at the required level or backing off as soon as the sound suffers. Listen for flattened transients, rough vocal edges, narrowed depth and low-frequency pumping. The clean stopping point depends on the mix and delivery brief, so fixed gain and ceiling settings are poor substitutes for a test render. A sample-based ceiling inside the effect is not a promise that the encoded or reconstructed signal will return the same dBTP value. Save and reopen a test, then inspect both true-peak fields in Statistics. A short excerpt can expose artifacts, but only the complete delivery file can pass the final loudness check. If one controlled maximizing pass cannot reach the requested level without damage, revise the mix or agree a different target with the recipient; do not silently change the brief. ## Step 4: Verify loudness and make the bit-depth decision Use **File → Save As** to make a processed audio copy; for a Sound Forge project, use **File → Render As**. Reopen that output, check its own Plug-In Chain, and bypass any effects already baked into the file before auditioning or saving it again. Select the complete file and both channels, then run Statistics. Compare Integrated LUFS, LRA where applicable, both sample extremes and both true-peak fields with the baseline and brief. The [Plug-In Chain workflow](https://soundforgepro.com/how-to-use-plug-in-chainer-sound-forge-pro/) explains why preview, applied processing and saving are different checkpoints. Don't treat −14 LUFS as a universal music-master submission target. [Spotify’s own mastering advice](https://support.spotify.com/us/artists/article/loudness-normalization/) recommends −14 Integrated LUFS with true peak below −1 dBTP, or below −2 dBTP for louder masters. That is destination-specific guidance; its Normal playback reference is not every service’s submission rule. Playback normalization varies by service and user setting, while genre, dynamics, client requirements and the loudest clean result all affect the master. If a broadcaster or client gives a formal loudness specification, follow that document rather than a generic streaming chart. If the brief calls for loudness normalization and the available method matches it, use **Process → Normalize → Loudness** on the processed working copy before final dither. This is conditional processing, not an automatic extra mastering step. The [current Normalize help](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/proonly/normalizing%5Faudio.htm) documents EBU R128 and ITU-R BS.1770/1771 modes, integrated loudness, tolerance, maximum true peak and loudness-range handling. Peak normalization is a different operation: it applies constant gain, so it also changes integrated loudness. The [normalization guide](https://soundforgepro.com/how-to-normalize-audio-in-sound-forge-pro/) separates the modes. For formal delivery, also confirm the required measurement method in the [loudness-meter workflow](https://soundforgepro.com/sound-forge-loudness-meters/); a preset name is not a compliance certificate. ### Finish processing before the final integer conversion If a 24-bit or 32-bit-float source must become a 16-bit deliverable, commit the approved EQ, compression, maximization and gain changes to a working render first. Reopen that render and bypass the already-applied chain before continuing. Do not dither the unprocessed waveform and then apply the real-time mastering chain on save. If the delivery needs a different sample rate, complete that conversion before final dither; the [sample-rate conversion guide](https://soundforgepro.com/how-to-change-sample-rate-sound-forge-pro/) covers the required-rate derivative. Then choose **Process → Bit Depth → Bit-Depth Converter**. The [Sound Forge 2026 Bit-Depth Converter help](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/bit%5Fdepth%5Fconverter.htm) lists Half Rectangular, Rectangular, Triangular, Highpass Triangular, Gaussian and POW-r dither options. Audition the quietest fade or tail and apply dither once. The official help says the best POW-r mode depends mainly on the signal, so there's no defensible type for every track. An unchanged file already at the required integer bit depth needs no second dither pass. A processed 24-bit source may leave a floating-point effects chain before a 24-bit integer export, so matching source/output labels alone does not settle quantization. Check the final processing and export path; avoid two dither stages. [FabFilter’s explanation of final-stage dither](https://www.fabfilter.com/help/pro-l/using/dithering) also distinguishes fixed-point conversion from MP3 or AAC encoding. Keep an undithered high-precision working version when available, and derive each delivery from that version. Do not make a 16-bit intermediate solely to create an MP3. ## Step 5: Export, reopen and check the deliverable Export only the versions the brief needs. In [Save As or Render As](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/saving%5Fa%5Ffile%5Fas%5Fa%5Fdifferent%5Fname%5For%5Ftype.htm), choose the file type and template/custom settings deliberately. Use a filename that identifies the version, sample rate and PCM bit depth where applicable. Check required metadata, too: supported fields depend on the output format. Close and reopen the exported file, confirm no unwanted chain is active, and check it from start to finish. ![Mastering export QA from saving a copy to Statistics and end-to-end listening](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/08/mastering-export-qa-desktop-v1.webp) The deliverable is the saved file: reopen it, rescan it, then listen from the first sample through the final tail. Check the reopened file’s duration, channel count, sample rate and encoding properties; use Statistics for Integrated LUFS, LRA where applicable, both sample extremes and both true-peak readings. The save-time loudness log is measured before codec encoding, so it cannot replace this check of a lossy export. Listen to the first and last seconds, every fade, transitions around edits, the loudest chorus and the quietest tail. Check derived lossy files for clicks, pumping, harshness or codec-related distortion. Finally, compare the export with the untouched source and a relevant reference at matched perceived level. The master should show a clear improvement once the loudness advantage is removed. If it doesn't, return to the last checkpoint that changed the sound instead of adding another processor. ## Stop signs and the next move | What you hear or measure | Likely checkpoint | Next move | | ------------------------------------------------- | ----------------------------------- | -------------------------------------------------------------- | | Low end pumps after loud hits | Wave Hammer compressor or maximizer | Reduce processing and retest the loudest section | | The louder version loses depth when level-matched | Volume Maximizer | Back away from the first audible trade-off | | True peak is higher than expected after saving | Render and verification | Adjust the chain, save a new test and rescan | | The 16-bit fade sounds grainy | Bit-depth conversion | Compare dither on the quiet tail and apply it once | | A vocal or instrument is still too loud | Source mix | Return to the mix or stem instead of forcing the stereo master | ## Five-step checklist - **Measure:** save the whole-track, both-channel Statistics baseline. - **Balance:** use Modern Equalizer with level-matched A/B checks. - **Control:** set Wave Hammer compression, then maximization. - **Verify:** reopen the processed copy without an extra chain, rescan loudness and peaks, then make any required final integer conversion with one planned dither stage. - **Deliver:** reopen the export, inspect it and listen against the untouched source. ## Frequently Asked Questions ### What order should I use for mastering in Sound Forge Pro? Measure the complete source first, then correct tonal balance with Modern Equalizer, control dynamics with Wave Hammer, verify loudness and true peak, convert bit depth only when required, and reopen the exported file for final QA. ### What is Wave Hammer in Sound Forge Pro 2026? Classic Wave Hammer combines a compressor and Volume Maximizer in one plug-in. Wave Hammer 2.0 is a different multiband effect. Evaluate the classic stages separately and verify the saved result with Statistics. ### Does a −1 dB ceiling guarantee −1 dBTP? No. A sample-based plug-in ceiling does not guarantee the same reconstructed true-peak reading. Save a test and inspect maximum true peak and filtered true peak in Tools → Statistics. ### Should I master every streaming track to −14 LUFS? No. −14 LUFS is not a universal submission requirement. Use the destination brief, the music's dynamics and the loudest clean result, and remember that playback normalization varies by service and user setting. ### Should I peak-normalize after Wave Hammer? Only when you deliberately need the resulting constant gain change. Peak normalization changes integrated loudness along with the peak level, so rescan the complete file afterward rather than treating Normalize as an automatic final step. ### Which POW-r dither type should I use? There is no single type for every master. Sound Forge's current help says the best mode depends mainly on the signal. Compare the quietest fade or tail, and apply dither once when the final bit depth is being reduced. ### Is Ozone included with Sound Forge Pro 2026? Do not assume it is included: Ozone is not listed in the [current Boris FX product comparison](https://www.soundforge.com/sound-forge/pricing/). You need a separately licensed, compatible Ozone build if you want to use it as a VST effect. Check that build’s requirements rather than relying on an old bundle description. *Documentation checked September 7, 2026 against current Boris FX help, EBU and Spotify guidance, and the linked dither explanation. These are documented routes and editorial listening checks, not a newly recorded test on an installed Windows build.* ### How to Add Reverb in Sound Forge Pro URL: https://soundforgepro.com/how-to-add-reverb-in-sound-forge-pro/ Last updated: 2026-10-09T21:08:20.000Z To add reverb in Sound Forge Pro, select the audio and choose **Effects → Reverb** for the built-in effect, or **FX Plug-Ins → Apply Plug-In Chain** for an installed reverb plug-in. Start with a room or plate preset, adjust the wet/dry balance, preview against Bypass, and choose how the decay should end before applying it. Keep a dry copy. **View → Plug-In Chain** is a different window: it processes playback across the file rather than committing an effect to a selection. Its active effects are applied when you save. Use **Apply Plug-In Chain** for a selected passage; use the View window to keep adjusting the sound during playback. **Safe starting point:** work on a copy, select a phrase plus enough silence to hear the decay, start from a small room or short plate preset, lower the wet signal until the effect sits behind the source, and compare with Bypass before committing. *Checked against the Boris FX 2026 help on September 12, 2026\. It documents both Effects → Reverb and Acoustic Mirror. VariVerb II and 3D Reverb are separate Sound Forge Plus additions, not the only ways to add reverb.* ## How to Add Reverb in Sound Forge 2026 1. **Open a copy of the source file.** Reverb is easy to overdo and difficult to remove cleanly after it has been rendered. 2. **Select the target audio.** Leave room after the phrase or note so the decay can be auditioned instead of stopping at the selection edge. 3. **Choose FX Plug-Ins → Apply Plug-In Chain.** This opens the processing version of the chain for the selected audio. 4. **Add a reverb.** Click Add Plug-Ins to Chain, choose the installed effect, click Add, then OK to return to the processing window. VariVerb II and 3D Reverb are Plus options; compatible third-party reverbs can also be used. 5. **Start with a preset that matches the job.** A room or short plate is a better diagnostic starting point than a huge hall. 6. **Preview, adjust the mix, and toggle Bypass.** Match perceived loudness closely enough that “louder” is not mistaken for “better.” 7. **Choose the tail behavior and click OK.** Use Mix or Insert Tail Data when the decay must continue beyond the selection; use Ignore only when an intentional hard stop is required. The diagram below separates the menu route from the tail-data decision. The controls inside step 3 depend on the reverb you load. ![Sound Forge 2026 reverb workflow through Apply Plug-In Chain with preview and tail handling](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/10/reverb-apply-chain-workflow-v2-v20261005.webp) Select audio, use Apply Plug-In Chain, preview an installed reverb, then choose the tail behavior before rendering. The official [Apply Plug-In Chain help](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/apply%5Ffx%5Fchain.htm) confirms this split: the command processes the selection or data window, while Preview and Bypass let you compare the result before rendering. ## Which Reverb Is in Your Sound Forge Edition? The [current Sound Forge plan comparison](https://www.soundforge.com/sound-forge/pricing/) places **VariVerb II and 3D Reverb in Sound Forge Plus**. Both tiers support third-party VST2/VST3 effects. For the built-in route, the [2026 Reverb help](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/reverb.htm) directs you to Effects → Reverb; Acoustic Mirror is also documented in the current manual. | Option | Where to look | Use | Check first | | ---------------------- | ------------------------------------------- | --------------------------------------------- | ---------------------------------------- | | Reverb | Effects → Reverb | A direct built-in room effect | Use the dialog’s ? help for its controls | | Acoustic Mirror | Installed effect; current help documents it | Impulse-response coloration | Locate the supplied impulse library | | VariVerb II | Sound Forge Plus | Adjustable reverb types and room size | Plus package installation | | 3D Reverb | Sound Forge Plus | Spatial placement and multichannel rooms | Required channel layout | | Third-party VST reverb | Your installed plug-in library | The spaces and controls that plug-in supports | License, scan path and enable state | If an effect appears in an old screenshot but not in your chooser, check the edition and installed packages first. Don’t reinstall the entire application or download an unknown impulse library simply to match a tutorial written for another version. ## Choose Reverb or Apply Plug-In Chain For the built-in effect, select the passage and open **Effects → Reverb**. For another reverb, open **FX Plug-Ins → Apply Plug-In Chain**, click **Add Plug-Ins to Chain**, select the effect in the chooser and click **Add**, then **OK** to return to the chain. Adjust the reverb before clicking the processing window’s final OK. These are two different confirmations. A [2024 Pro 15 community question about saving chain effects](https://www.magix.info/us/forum/solved-how-to-apply-plugins-from-plugin-chain-in-sound-forge-pro-15--1342941/) describes the same practical confusion. The [current Plug-In Chain help](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/proonly/plug-in%5Fchainer.htm) resolves it: the View window has no Apply button; saving commits its active effects. Do not switch to that window expecting a selection-only render. ### When to select only part of the file Select the phrase or sound effect that should receive reverb. Silence after it can give the decay room, but selecting the next word also processes that word. If the next event must stay dry, end the selection before it and choose whether the tail may overlap or move it. ### When to process the whole file Whole-file reverb makes sense for a deliberately dry sound effect, a mono ambience element, or a complete recording that needs a consistent space. It's usually the wrong repair for a voice recorded in a bad room, though: adding a better reverb doesn't remove the old room, it just layers a new decay over the existing one. Treat or re-record the source first when the unwanted room is the problem. ## Wet/Dry Balance Without a Magic Percentage Dry means the original signal; wet means the reverberated signal. A reverb-only output suits a separate effect stem or a DAW return. For direct processing of a voice file, retain enough dry signal to keep the words clear. There's no universal “20%” or “−12 dB” answer. The correct balance depends on the source, decay, early reflections, pre-delay, frequency content, and whether the reverb plug-in uses a linear percentage or level controls. Use this repeatable method: 1. Begin dry or with a very low wet level. 2. Raise the reverb until the space becomes obvious. 3. Back it down until it supports the source rather than becoming the subject. 4. Toggle Bypass at a similar perceived output level. 5. Listen once on headphones and once on speakers if both are available. The exact controls depend on the plug-in. In [3D Reverb’s Output section](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/proonly/3d%5Freverb/output.htm), Mix balances the original and processed signals, while Wet Level changes the reverb level independently. Lock Mix before comparing presets if you want that balance to stay fixed. Sound Forge also has host-level blending: **More** in a [processing dialog](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/using%5Fprocessing%5Fdialogs.htm) exposes Wet Gain and Dry Gain. The host’s wet path is the plug-in’s processed output, which can already contain dry sound. Check which layer you are changing instead of turning up both blends. Pre-delay can leave space between the direct sound and the reverb onset. If you want a tempo-related starting point, [convert BPM to milliseconds](https://soundforgepro.com/bpm-to-ms-calculator/); do not assume a beat division will suit every voice. The [delay and reverb timing guide](https://soundforgepro.com/bpm-delay-reverb-time-guide/) explains how to use those values without forcing the decay into a rigid formula. ## Tail Data: Mix, Insert, or Ignore Reverb produces audio after the selected source ends. In the Apply Plug-In Chain processing dialog, right-click the dialog and choose how Sound Forge handles that tail. | Mode | What Sound Forge does | Use it when | Risk | | -------------------- | ---------------------------------------------------------- | ------------------------------------------------ | ---------------------------------- | | **Mix Tail Data** | Blends the decay into audio after the selection | Timing must stay fixed and overlap is acceptable | The tail can muddy the next phrase | | **Insert Tail Data** | Creates room for the full tail and moves later audio right | The decay must remain intact | File timing and sync change | | **Ignore Tail Data** | Stops processing at the selection boundary | A deliberate hard end is required | The reverb can sound chopped | The table names each setting and the diagram shows what it does to the waveform. Watch the gray following audio: it stays in place under Mix and Ignore, but moves to the right under Insert. ![Sound Forge reverb tail behavior comparison for Mix, Insert and Ignore](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/08/reverb-tail-modes-v1.webp) Mix overlaps the decay, Insert moves later audio, and Ignore cuts the tail at the selection boundary. Mix is the practical first check for many internal selections, and Insert is safer for the last note of an isolated sound when changing duration is acceptable. Ignore isn't the default “clean” choice; it deliberately discards the decay. The detailed [Plug-In Chainer guide](https://soundforgepro.com/how-to-use-plug-in-chainer-sound-forge-pro/) covers the same three modes and their effect on later audio. ## Real-Time Reverb with View → Plug-In Chain Use **View → Plug-In Chain** to compare settings during playback across the recording. It does not process just the selected passage. Saving applies the active chain, so save a processed copy under a different name and retain the dry original. Reopen that output and confirm the decay, level and duration before delivery. Signal flows through the chain in order. EQ before reverb changes what excites the room; place it after and you're shaping the combined dry and reverberant result instead. Neither is universally correct. If low frequencies make the decay cloudy, filtering the reverb output inside the plug-in is often cleaner than thinning the entire source. The current editor supports third-party VST2 and VST3 effects. If a reverb does not appear, check [VST Effects Preferences](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/vst%5Feffects%5Fpreferences.htm), confirm the scan location or enable state, then refresh. The [VST troubleshooting guide](https://soundforgepro.com/sound-forge-pro-vst-plugins-not-showing/) covers the safe current scan and cache checks. ## 3D Reverb and VariVerb II in Sound Forge Plus **VariVerb II** offers selectable reverb types, presets and room-size adjustment. Try it when you want a conventional designed space; choose the preset by the sound you need, not by the most dramatic name. **3D Reverb** adds virtual-room placement and multichannel spatial work. Check the output channel layout before rendering: a surround-room feature is not a reason to change a stereo deliverable. The [Sound Forge vs Sound Forge Plus comparison](https://soundforgepro.com/sound-forge-vs-sound-forge-plus/) explains the full tier difference. Both current tiers share the editor; Plus adds Melodyne 5 Essential, Vandal, VariVerb II, and 3D Reverb. ## Acoustic Mirror: Convolution and Installed Assets Acoustic Mirror applies an impulse response to give audio the coloration of a room or device. The [current Acoustic Mirror help](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/proonly/about%5Facoustic%5Fmirror.htm) documents both the effect and an included impulse-response library. It is not merely an abandoned Sony-era feature. Locate the installed impulse library, preview a response on a short copy, and use the effect’s **?** help for the controls in your installation. If the assets are missing, check the installed packages rather than downloading an unknown file to reproduce an old tutorial. Menu names changed across [Sound Forge’s earlier versions](https://soundforgepro.com/sound-forge-history/); use the current dialog’s help when an old tutorial differs. A WAV extension alone says nothing about whether a file represents a measured room response. Use an intended impulse response for realistic room coloration; other material is an experimental sound-design choice. ## Selection vs Whole File: Three Practical Cases ### Dry voice that needs a little space Use a short room or plate, restrained wet level, and enough pre-delay to keep consonants clear. Preview several sentences, not one word. If the recording already has strong room reflections, adding reverb is unlikely to make it sound “studio recorded.” ### A sound effect that must ring out Select the effect and its available silence, then use Insert Tail Data if the full decay must extend the file. If sync cannot move, Mix Tail Data may be safer, but confirm that the overlap does not mask the next event. ### A finished stereo mix Reverb at mastering is a special correction rather than a required final step. Use a very small change, compare at matched loudness, and keep the unprocessed master. The [complete mastering guide](https://soundforgepro.com/sound-forge-pro-for-mastering/) explains when ambience belongs in the finishing chain and when the mix should be revised instead. ## Common Reverb Problems - **The effect ends abruptly:** check the selection boundary and tail mode, then test a short render. A plug-in’s own gate or decay setting can also shorten the sound. - **The next phrase becomes muddy:** Mix Tail Data overlaps too much, the decay is too long, or low frequencies dominate the wet signal. - **The voice moved too far back:** the wet level, early reflections, or decay is too strong. - **The reverb is missing:** if the plug-in is absent from the chooser, check installation, scan paths and enable state. If it is inserted but inaudible, check Bypass, wet/dry level and the audio path. - **The output clips:** dry and wet summing can raise peaks. Lower the plug-in output and verify the rendered file; do not solve it by normalizing blindly. - **The old menu does not match:** the tutorial was written for another Sound Forge generation or tier. ## Frequently Asked Questions ### How do I add reverb in Sound Forge Pro? Select the audio, choose FX Plug-Ins → Apply Plug-In Chain, add an installed reverb, adjust the preset and wet/dry mix, preview and bypass-check it, choose Mix/Insert/Ignore Tail Data, then click OK. Sound Forge Plus includes VariVerb II and 3D Reverb; both current tiers can load supported third-party VST effects. ### Does Sound Forge 2026 include reverb? Yes. The current help documents Effects → Reverb and Acoustic Mirror. Sound Forge Plus adds VariVerb II and 3D Reverb, and both tiers support compatible third-party VST effects. Check your installed packages if a documented effect or impulse library is missing. ### What is tail data in Sound Forge Pro reverb? Tail data is the decay generated after the selected source ends. Mix Tail Data overlaps it with following audio, Insert Tail Data creates room and shifts later audio, and Ignore Tail Data discards it at the boundary. ### How do I set the wet/dry reverb mix? Start with the dry source and a low wet level. Raise the reverb until the space is obvious, then back it down until it supports the source. There is no universal percentage because plug-ins, presets, material, and delivery contexts differ. ### Can I use third-party reverb plug-ins in Sound Forge Pro? Yes. Current Sound Forge supports VST2 and VST3 effects. Use Apply Plug-In Chain to process a selection, or View → Plug-In Chain for real-time playback. Saving applies the active real-time chain, so save a processed copy and retain the dry original. If it is missing, open Options → Preferences → VST Effects, verify the search folder and enabled state, then click Refresh. ### What is Acoustic Mirror in Sound Forge Pro? Acoustic Mirror applies impulse responses to give recordings the coloration of rooms or devices. It remains documented in the Sound Forge Pro 2026 help, which also describes an included impulse-response library. Use the installed effect’s help for its controls. ### Should I use reverb to fix a roomy recording? Usually no. Reverb adds another room response; it does not remove the room already captured. Reduce or isolate the unwanted ambience first, or re-record when possible, then add controlled reverb only if the dry result needs a deliberate space. ### How to Normalize Audio: Peak, RMS, LUFS & True Peak URL: https://soundforgepro.com/how-to-normalize-audio-in-sound-forge-pro/ Last updated: 2026-10-09T20:58:31.000Z **Quick answer:** normalize audio only after you know which number the delivery actually controls. Use **Peak level** for a sample-peak ceiling, **Average RMS level** when a client or legacy workflow specifies RMS, and **Loudness** for an integrated LUFS target with a true-peak limit. In Sound Forge Pro 2026, select the finished file or region, choose **Process → Normalize**, set the mode-specific target, preview, apply, then verify both the processed source and the exported file with **Tools → Statistics**. Basic gain-only normalization moves the whole selection up or down by one amount. It won't balance a whisper against a shout, remove room noise or repair clipping. Sound Forge's Normalize dialog also offers optional dynamics processing, and picking that changes more than gain. Decide whether the recording needs a level adjustment or real repair before you apply anything. The detailed steps below use Sound Forge Pro 2026 on Windows. You don't have to buy it just to normalize a file; the short Audacity workflow later in this guide covers a free alternative. In either editor, pick the measurement your destination specifies, then check the exported file itself. The waveform on screen isn't enough. ## Decide Why the Audio Is Too Quiet Play the entire deliverable before changing its level. A file can be quiet for several different reasons, and only some are solved by one constant gain change. | What you hear or measure | Likely problem | Will normalization fix it? | | --------------------------------------------------------- | ------------------------------------------------------- | ------------------------------------------------------------------ | | **Whole file is consistently low** | Correct balance, enough peak headroom, wrong final gain | Usually; choose the measurement required by delivery | | **One transient is near 0 dBFS, speech is still quiet** | High crest factor or an isolated peak | No; peak normalization has almost no room to work | | **One speaker changes level sentence to sentence** | Performance, mic distance, automation or dynamics | No; edit gain and/or compress before final normalization | | **File meets LUFS but clips after MP3/AAC export** | True-peak or codec headroom problem | Not by loudness target alone; lower the ceiling or change dynamics | | **Noise becomes obvious when level rises** | Poor signal-to-noise ratio | No; normalization raises wanted signal and noise together | | **Several songs have the same peak but different volume** | Different density and integrated loudness | Use loudness measurement, while preserving intentional sequence | If the waveform is already clipped, turning it down makes the flat-topped distortion quieter but won't rebuild the missing shape. Use the [clipped-audio repair workflow](https://soundforgepro.com/fix-clipped-audio-sound-forge/) before the final level pass. If hiss or hum is the real limit, clean it up first with the [noise-removal guide](https://soundforgepro.com/how-to-remove-background-noise-in-sound-forge-pro/). Normalization comes once the source is technically and editorially ready. ## Choose Peak, RMS or LUFS by the Delivery Requirement The three modes don't measure the same thing, and matching their numbers doesn't make their results equivalent. | Mode | What controls the gain | Best use | Main failure | | -------------------------- | ----------------------------------------- | ------------------------------------------------------------------- | --------------------------------------------------------- | | **Peak · dBFS** | Largest selected sample magnitude | Technical ceiling, headroom, sample assets, pre-encode safety | One short transient can leave the rest perceptually quiet | | **Average RMS · dB RMS** | Average energy under the scan settings | Client/legacy RMS specification, some audiobook and asset workflows | Not LUFS; aggressive targets need a clipping policy | | **Loudness · LUFS + dBTP** | Integrated program loudness and true peak | Podcast, broadcast and platform-oriented program delivery | A target can require more gain than peak headroom allows | ![Peak, RMS and LUFS normalizing compared, with the verification steps that follow each](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/10/normalize-audio-decision-map-v20261006.webp) Sound Forge normalize modes: Peak sets a sample ceiling, RMS follows average energy, LUFS matches program loudness — measure the export either way. A useful rule is simple: use the meter named in the brief. “Maximum peak -3 dBFS” calls for a peak decision, and “Between -23 and -18 dB RMS” calls for RMS measurement. “-16 LUFS integrated, maximum -1 dBTP” means loudness plus true-peak verification. If the brief only says “normalize the volume,” ask what destination and measurement it means. ## Measure the Finished Selection Before Processing Work on a copy and measure exactly the selection you plan to deliver. Include any intentional room tone at the start and end, and don't measure only the loudest sentence as if it were the whole program. Keep the same selection for the before-and-after comparison. Sound Forge's current [Statistics documentation](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/statistics.htm) separates sample peak from oversampled true peak and reports integrated LUFS, loudness range, maximum short-term loudness and maximum momentary loudness. Short-term uses three-second windows; momentary uses 400 milliseconds. That matters because a file can pass an integrated target and still contain an uncomfortable short section. Copy the Statistics cells to a QA note before processing. A simple before/after record prevents the common mistake of remembering a sample peak as a true peak or comparing RMS from one selection with LUFS from another. The [Sound Forge Statistics guide](https://soundforgepro.com/how-to-use-statistics-sound-forge-pro/) shows how to read those fields when you need more detail. ## Normalize Audio in Sound Forge Pro 2026 ![The Sound Forge Normalize dialog with its peak, RMS and loudness modes and the scan preview](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/10/normalize-ui-mode-verify-v2-1-v20261006.webp) Normalizing in Sound Forge: take the meter from the delivery brief, scan the exact selection, preview, then verify with the same measurement. 1. **Identify the delivery measurement.** Determine whether the destination specifies sample peak, RMS or integrated LUFS plus true peak. 2. **Finish level-changing processing.** Complete edits, restoration, EQ and dynamics before the final normalization pass. 3. **Measure the complete selection.** Select the complete deliverable, use Tools → Statistics, and record sample peak, true peak, RMS and integrated loudness as required. 4. **Open Normalize.** Choose Process → Normalize and select Peak level, Average RMS level or Loudness. 5. **Set the mode-specific target.** For Peak or RMS, click Scan Levels before setting the target; choose an explicit RMS clipping policy if needed. For Loudness, set the normalization standard, integrated target, tolerance and maximum true peak. 6. **Preview and apply.** Audition quiet, loud and transition sections as well as the opening, then apply the process. 7. **Verify the processed source.** Run Tools → Statistics again on the same complete selection. 8. **Export and measure again.** Reopen the actual deliverable and verify loudness, true peak, format and audible quality. For Peak/RMS previews, Boris FX notes that the whole file must be scanned even when previewing a small selection; allow the scan to finish. **Scan Levels** stores the current Peak and RMS values, so you can audition several Normalize to values without rescanning an unchanged source. The 2026 help also documents **Use current scan level** for deliberately applying a stored level from one selection to another. That's a controlled matching tool; it isn't permission to reuse stale measurements after the source or selection changes. ## Normalize Audio for Free in Audacity Select the audio, then use [Effect → Volume and compression → Normalize](https://www.audacityteam.org/manual/effects/volume-and-compression/normalize/) for a sample-peak target. Enter the peak amplitude your brief allows. Check Remove DC offset separately: it recenters the waveform rather than simply changing gain. Leave independent stereo-channel normalization off when you want to preserve the existing left/right balance. For an RMS or LUFS target, use [Loudness Normalization](https://www.audacityteam.org/manual/effects/volume-and-compression/loudness-normalisation/) in the same menu instead. Choose the measurement and the target, and keep independent stereo normalization off so the balance survives. For mono, set Treat mono as dual mono to match the intended playback and final meter configuration, since comparing compensated dual-mono and single-channel readings can open up a gap of roughly 3 LU. Apply, export a new file, then measure the result. Hitting a LUFS number doesn't guarantee a true-peak ceiling on its own, so if the projected peaks are too high, lower the gain or make a separate limiting decision. ## Use Peak Normalization for a Ceiling, Not Equal Loudness Peak normalization finds the largest sample magnitude in the selection and applies one constant gain change so that sample reaches the target. If the highest peak is -7 dBFS and the target is -1 dBFS, the process adds 6 dB to every sample. The difference between quiet and loud passages stays the same. For selected multichannel audio, Sound Forge finds the largest sample magnitude among the selected channels and applies the same gain to all of them. That preserves the channel relationship. Selecting only one channel changes only that channel, which can be useful for a repair but is dangerous if done accidentally on a finished stereo file. The official [Sound Forge 2026 Normalize help](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/proonly/normalizing%5Faudio.htm) warns that peaks near 0 dB can clip during conversion to a compressed format and gives **\-0.9 dB** as a starting point. Treat it as exactly that, a starting point rather than a universal delivery ceiling. A client may require -3 dBFS sample peak, a streaming master may be checked in dBTP, and a game pipeline may define different limits by asset class. ! **Peak-normalized does not mean loudness-matched.** A snare hit and sustained speech can both peak at -1 dBFS while sounding radically different. Use integrated loudness when the listener should perceive program files at a consistent level. ## Use RMS Normalization Only with an RMS Brief Average RMS normalization measures average signal energy and applies gain toward the requested RMS value. It earns its place when a delivery system, audiobook workflow or older asset specification explicitly uses dB RMS. It isn't an older spelling of LUFS, though, and shouldn't be substituted for a loudness target. Sound Forge exposes scan controls because the result depends on what the scan includes: - **Ignore below** removes material below a threshold from the RMS calculation. Set too low, long silence pulls the average down; set too high, the scan may exclude nearly everything. - **Attack time** controls how quickly the scan responds to transient peaks. - **Release time** controls how long transient material remains part of the calculation as it decays. - **Use equal loudness contour** compensates for reduced hearing sensitivity at very low and high frequencies. The Boris FX documentation explicitly warns that RMS normalization above **\-6 dB** can compromise sound quality. A 0 dB RMS target corresponds to the apparent loudness of a maximum-amplitude square wave; it isn't the benign equivalent of normalizing a peak to 0 dBFS. If the requested RMS gain would exceed full scale, choose what happens rather than accepting a hidden compromise. In the If clipping occurs menu, Sound Forge offers **Apply dynamic compression**, **Normalize peak value to 0 dB**, **Ignore (saturate)** and **Stop processing**. The first changes dynamics, the second misses the RMS target, the third clips, and the fourth stops. For a controlled delivery, Stop processing is the safest diagnostic default until you decide which trade-off the brief permits. ## Use LUFS Normalization for Program Loudness Loudness normalization targets perceived program level rather than the single highest sample. In Sound Forge Pro 2026, choose **Loudness** and then the current **EBU R128** or **ITU-R BS.1770/1771** option exposed by the dialog. The norm supplies integrated program loudness, tolerance and maximum true peak. Integrated LUFS is measured across the program; it answers “how loud is this whole deliverable?” True peak estimates peaks between stored samples; use that measurement to decide how much playback/encoding headroom remains. You need both, because a file can be exactly -16 LUFS and still exceed a -1 dBTP ceiling. One number can't satisfy two independent constraints when the source is too dynamic. **Limit dynamics to** turns on loudness-range processing, and most files don't need it. The right loudness range depends on the listening environment and the brief. Sound Forge notes that LRA adjustment isn't available for files shorter than 30 seconds; for those it instead keeps maximum short-term loudness no higher than the integrated target plus 5 LU. That 30-second software rule is separate from the EBU measurement guidance, where R128 doesn't recommend LRA for programs under one minute because there are too few short-term values. If you want to watch the reading accumulate in real time, the [Sound Forge Loudness Meters guide](https://soundforgepro.com/sound-forge-loudness-meters/) explains momentary, short-term, integrated and range displays. For final compliance, measure the complete rendered program rather than stopping when a convenient section looks right. ## Use Current Delivery Targets, Not a Universal LUFS Number The following examples were rechecked against primary sources on September 7, 2026\. They show why the destination comes first. Follow the current contract, broadcaster, distributor or platform page for the specific delivery. | Destination example | Loudness or level | Peak requirement | What to remember | | ----------------------------------- | --------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------- | | **Spotify music · Normal playback** | \-14 LUFS integrated target | Below -1 dBTP; Spotify advises below -2 dBTP for masters louder than -14 LUFS | Normalization is applied at playback and can vary by device/settings | | **Apple Podcasts** | Around -16 dB LKFS, ±1 dB | True peak no higher than -1 dB FS | Apple cites ITU-R BS.1770-5 and recommends preconditioning before encoding | | **EBU R128 file program** | \-23 LUFS, ±0.2 LU for QC | [Maximum -1 dBTP for linear production audio](https://tech.ebu.ch/docs/r/r128.pdf) | Broadcast target; not a generic podcast or music preset | | **ACX audiobook** | [\-23 to -18 dB RMS](https://help.acx.com/s/article/what-are-the-acx-audio-submission-requirements) | Peaks no higher than -3 dB | Noise floor must also be no higher than -60 dB RMS; normalization alone cannot fix noise | Spotify's current [loudness guidance](https://support.spotify.com/us/artists/article/loudness-normalization/) says its Normal playback setting adjusts tracks to -14 LUFS under ITU 1770 and recommends below -1 dBTP, or below -2 dBTP when the master is louder than -14 LUFS. It also says its web player and some third-party devices do not use normalization. Apple Podcasts recommends about -16 dB LKFS with ±1 dB tolerance and a true peak no higher than -1 dB FS in its current [audio requirements](https://podcasters.apple.com/support/893-audio-requirements). The current [EBU R128 recommendation](https://tech.ebu.ch/docs/r/r128.pdf) specifies -23 LUFS for file-based program loudness. These are different delivery systems rather than competing answers to one question. A publisher may set its own production target, but the deliverable must still meet the actual destination's requirements, and an audiobook RMS requirement can't be safely converted into a guessed LUFS number. For spoken-word production around this final measurement, use the [Sound Forge podcast workflow](https://soundforgepro.com/sound-forge-pro-for-podcasters/) for the editing, cleanup and mastering decisions that normalization can't make. ## Calculate Whether Constant Gain Can Reach the Target ![A LUFS gain calculation checked against true-peak headroom before the gain is applied](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/08/normalize-gain-math-v2.webp) Loudness math before Sound Forge normalizes: subtract measured from target, project that gain onto true peak, and see whether both targets can hold Before applying a custom LUFS target, estimate the required gain: **Required gain = target integrated loudness − measured integrated loudness.** Gain and headroom check ### Will constant gain fit the peak ceiling? Enter complete-file readings from Sound Forge Statistics, or [measure the finished file in the free LUFS meter](https://soundforgepro.com/lufs-meter/). This calculator predicts a constant gain move; it doesn't upload or normalize audio. Measured integrated loudness (LUFS)Use the whole finished selection. Target integrated loudness (LUFS)Take this from the delivery brief. Measured true peak (dBTP)Do not substitute sample peak. Maximum allowed true peak (dBTP)Example only: −1 dBTP. Calculate gain and headroom Required gain**+4.0 dB** Projected true peak**−1.0 dBTP** Maximum safe gain**+4.0 dB** The target lands exactly on the selected true-peak ceiling. Remeasure the rendered file. A projection isn't final QC. Codecs, processing order and render settings can all shift the measured result. Say Statistics reports -20 LUFS integrated and -5 dBTP. A -16 LUFS target needs roughly +4 dB, which puts the estimated new true peak at -1 dBTP, so constant gain has just enough headroom for a -1 dBTP ceiling. If the measured true peak were -3 dBTP, the same +4 dB move would land around +1 dBTP, and constant gain couldn't meet both targets. Treat the loudness subtraction as a projection: material near the measurement gate can nudge the integrated result, so the new scan is what decides. That conflict isn't a software bug. The audio needs a different dynamics decision: edit an isolated peak, revise compression, use an approved true-peak limiter, accept a quieter integrated value or change the delivery target if the brief permits it. Then measure the whole file again. The [Wave Hammer guide](https://soundforgepro.com/sound-forge-wave-hammer/) covers limiting as a separate mastering process; don't hide it inside the word “normalize.” ### Hear What a Constant 6 dB Normalization Move Changes These players use the same 64.3-second speech recording, encoded separately as mono 44.1 kHz, 128 kb/s MP3s. The controlled source-level difference was 6.0 dB. Separate lossy encodes don't stay exact sample-for-sample scaled copies after decoding, so compare the rounded measurements and the change you hear. These are controlled gain examples. They weren't exported from Sound Forge and don't benchmark the application. **Before — -30.0 LUFS, -9.8 dBTP**Controlled low-level version of the same speech; mono 44.1 kHz, 128 kb/s MP3. Your browser does not support HTML5 audio. [Download this comparison file](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/media/2026/08/before-minus6db.mp3). **After +6.0 dB — -24.0 LUFS, -3.8 dBTP**Source-level gain is 6.0 dB higher before MP3 encoding; no compressor, limiter or loudness-range processing. Your browser does not support HTML5 audio. [Download this comparison file](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/media/2026/08/after-plus6db.mp3). | File | Integrated | True peak | LRA | | ------ | ----------- | ---------- | ------ | | Before | \-30.0 LUFS | \-9.8 dBTP | 7.3 LU | | After | \-24.0 LUFS | \-3.8 dBTP | 7.3 LU | FFmpeg ebur128 measurements: integrated loudness and true peak rise by 6.0 dB at the displayed precision; LRA is 7.3 LU for both files. The September 7 measurements with FFmpeg 8.1.2 loudnorm and ebur128 agree on rounded integrated loudness and true peak. The table's 7.3 LU loudness range comes from ebur128 for both files, while loudnorm reported 6.9 LU for both. Neither analysis shows a change in range at its displayed precision. The after file is deliberately not labeled podcast-ready, because -24.0 LUFS doesn't meet every delivery target. The reading is “Epitaph on a Sailor” by Robert Duncan Milne, read by Claudia Caldi for [LibriVox Short Story Collection Vol. 106](https://librivox.org/short-story-collection-vol-106/). LibriVox's [public-domain policy](https://librivox.org/pages/public-domain/) identifies its recordings as public domain in the United States. Check the status in your country before reusing a recording elsewhere. ## Normalize Near the End of the Signal Chain Put final normalization after cleanup, EQ and any [compression or limiting](https://soundforgepro.com/compressor-vs-limiter/) you actually need, then export and measure again. You don't need every processor, so skip whatever the recording doesn't call for. EQ can create new peaks, compression changes crest factor, and noise reduction can change measured energy. Lossy encoding can create inter-sample overs on top of that. Any of those after normalization can invalidate the reading that came before it. There's one legitimate exception: early normalization used deliberately as gain staging before a plug-in. That's an input-level adjustment rather than final delivery compliance, so run a separate final normalization and verification pass after the processing chain. The [mastering workflow](https://soundforgepro.com/how-to-master-a-track-in-sound-forge-pro/) keeps those two decisions separate. ## Batch-Normalize Only Compatible Files Peak-normalizing a folder gives each file a shared peak ceiling; it doesn't give the folder shared loudness. LUFS-normalizing every file independently can erase intentional relationships between album tracks, episode segments or game assets. Group files by role and destination before running an automated job. - **Podcast episodes:** normalize whole finished episodes to the publisher's program spec, and leave individual sentences and stems alone. - **Voice-over pickups:** match microphone, room, speaker role and dynamics before one RMS or LUFS rule. - **Music albums:** protect intended track-to-track relationships; platform album normalization may preserve them. - **Game/UI sounds:** separate one-shots, loops, ambience and dialogue; integrated loudness can be unstable or misleading on very short assets. - **Archive derivatives:** leave preservation masters un-normalized unless the archive policy explicitly calls for a changed derivative. Use **Tools → Batch Converter** only after two representative files pass. The [batch-processing guide](https://soundforgepro.com/how-to-batch-process-files-sound-forge-pro/) covers source grouping, ordered effects, templates, safe destinations, pilot runs and output sampling. ## Verify the Export as Well as the Editable Source ![A normalized export measured again for integrated loudness, true peak and delivery format](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/10/normalize-export-verification-v2-v20261006.webp) The rendered file, not the editable Sound Forge source, is what must pass the target meter, final level, true-peak and format checks. 1. Save or render to a new destination; keep the approved source intact. 2. Reopen the actual WAV, FLAC, MP3 or AAC deliverable. 3. Select the complete program and run Tools → Statistics. 4. Compare integrated loudness, true peak, sample peak and RMS with the brief. 5. Confirm duration, channels, sample rate, bit depth/bitrate and metadata. 6. Listen to the quietest passage, loudest passage, strongest transient and ending. 7. Check that no fade, tail or final word was truncated. 8. Record the measured result with the filename and export preset. For MP3 delivery, follow the [MP3 export and verification workflow](https://soundforgepro.com/how-to-export-mp3-from-sound-forge-pro/), and measure the editable source and the finished MP3 separately. If the delivery also drops bit depth, apply the [Sound Forge bit-depth and dither workflow](https://soundforgepro.com/sound-forge-bit-depth-dither/) before the final measurement. A clean reading on the source doesn't guarantee a clean delivery file. ## Troubleshoot the Result Before Repeating the Process - **It is still quiet after peak normalization:** a transient already controls the ceiling. Fix dynamics or use the required loudness workflow. - **The noise floor became distracting:** gain raised noise with the signal. Return to restoration or a better source. - **Sound Forge stops during RMS normalization:** the target requires clipping under the selected policy. Lower the target or make a deliberate dynamics decision. - **The RMS result changes between scans:** verify selection, Ignore below, Attack, Release and equal-loudness contour. - **LUFS is correct but true peak fails:** reduce the required gain, control peaks with an approved limiter or accept a lower loudness if allowed. - **Integrated loudness will not settle:** measure the full program from start to finish. Short loops and partial playback don't represent the deliverable. - **The MP3 exceeds the source peak:** lower the pre-encode gain or peak ceiling to leave more headroom, encode again, and measure the new file. Moving a ceiling from -1 to -2 dBTP, for example, adds 1 dB of headroom, though it still can't guarantee every encoder will stay under the final limit. - **Left/right balance changed:** check whether only one channel was selected before normalization. ## Audio Normalization FAQ ### How do I normalize audio in Sound Forge Pro? Select the finished file or region and choose Process → Normalize. For Peak or Average RMS, use Scan Levels and set the target, with an explicit clipping policy for RMS. For Loudness, set the standard, integrated target, tolerance and true-peak limit. Preview, apply, then check both the processed selection and the exported file with Tools → Statistics. ### What level should I normalize audio to? Use the current delivery specification. A peak ceiling, RMS range and integrated LUFS target are different requirements. There is no universal setting for music, podcast, voice-over, audiobook, broadcast and game audio. ### What is the difference between peak, RMS and LUFS normalization? Peak normalization follows the largest sample magnitude. RMS normalization follows average signal energy under chosen scan settings. LUFS normalization follows perceived program loudness and is paired with a true-peak limit. The three modes can produce different gain changes from the same file. ### Does normalization compress audio? Basic peak or loudness gain normalization is a constant level change and preserves internal dynamics. Dynamics change if you enable RMS clipping compression, loudness-range limiting or a separate compressor/limiter to meet a target that constant gain cannot reach. ### Should I normalize before or after compression? For final delivery, compress first, normalize near the end and verify after export. Early normalization can be used deliberately for plug-in gain staging, but it does not replace the final compliance pass. ### Should I normalize every file to -1 dB? No. -1 dBFS is a common conservative sample-peak choice, and -1 dBTP appears in several delivery recommendations, but they are not the same measurement. Use the unit and ceiling in the actual brief. ### Can Sound Forge normalize multiple audio files? Yes, through Tools → Batch Converter. Group only files with the same role and delivery rule, test typical and stress files first, write to a new folder and verify representative outputs. Never assume a shared peak makes files equally loud. ### Can normalization fix clipping or background noise? No. Lowering clipped audio keeps the distortion; raising quiet audio raises its noise floor. Repair clipping and noise before the final level pass, then normalize and measure again. Last fact-checked: September 7, 2026 against the current Boris FX Sound Forge Pro 2026 Normalize and Statistics documentation, Spotify for Artists, Apple Podcasts for Creators, EBU R128-2023, ACX delivery guidance and Audacity’s current normalization manuals. ### Sound Forge Noise Reduction: Remove Background Noise URL: https://soundforgepro.com/how-to-remove-background-noise-in-sound-forge-pro/ Last updated: 2026-10-10T14:22:09.000Z **Quick answer:** for steady hiss, fan noise or HVAC wash, select a passage that contains only the unwanted sound, open **Tools → Noise Reduction**, capture the noiseprint, then preview a passage containing wanted audio and toggle Bypass to compare it with the original. Before applying, turn Bypass and any residual-output option off. Stop when the noise no longer distracts. If speech turns metallic, watery or dull, or the ambience starts pumping, reduce the processing. **Scope:** documentation checked September 8, 2026\. This is a Windows workflow written from documentation; nobody ran an installed NR-2.0 build for it. Boris FX documents the current tool families online, but the detailed controls of the classic NR-2.0 plug-in still live in the **?** help inside the installed dialog. Follow the seven-step sequence below only when your dialog shows the named controls. This guide covers steady broadband background noise in the [Sound Forge audio-restoration path](https://soundforgepro.com/tag/sound-forge-restoration-guides/). A gate, a hum filter, click repair and source separation solve different problems. Treating every defect with the same denoiser is how a usable recording becomes thin and artificial. ## Identify the noise before processing The current [Sound Forge 2026 product page](https://www.soundforge.com/sound-forge/) highlights a restoration family including DeHisser, DeClicker/DeCrackler and DeClipper. The specific tool matters more than the broad “Noise Reduction” marketing heading. Start with what the defect does over time, then choose the process. - **Steady fan, HVAC or room wash:** use broadband Noise Reduction when you can capture a representative noise-only passage. - **Regular low-level white noise:** compare broadband reduction with DeHisser. The current [DeHisser help](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/proonly/dehisser.htm) names microphones, preamps and transformers as typical sources. - **Clicks and crackle:** use Click and Crackle Removal or DeClicker/DeCrackler. A stationary noise profile is a poor description of a one-off impulse. - **Flattened clipped peaks:** try Clipped Peak Restoration or DeClipper on a copy. Those tools estimate damaged peaks, which a noiseprint can't rebuild. The [clipped-audio workflow](https://soundforgepro.com/fix-clipped-audio-sound-forge/) explains the limits before you commit a repair. - **A stable electrical tone:** inspect the actual fundamental and harmonics before applying a narrow correction. Continue with the dedicated [hiss-and-hum diagnosis guide](https://soundforgepro.com/remove-hiss-hum-sound-forge/). - **Music or another voice under speech:** that's an overlapping-source problem. Classic broadband noise reduction can't reliably isolate changing program material, so [compare noise-reduction software by workflow](https://soundforgepro.com/audio-noise-reduction-software/) instead of forcing the noiseprint. A noise gate isn't broadband reduction. The current [Noise Gate help](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/noise%5Fgate.htm) says it removes signals below a threshold in silent breaks. Noise that sits under speech stays audible, and a poorly set gate can make the floor disappear and return at every phrase. Use the [Sound Forge Noise Gate workflow](https://soundforgepro.com/how-to-use-noise-gate-sound-forge-pro/) when pause attenuation is the actual job. ## Where Noise Reduction lives in Sound Forge 2026 Open **Tools → Noise Reduction** for the classic restoration plug-in, or use its button on the Tools toolbar. The current [Sound Forge 2026 Tools toolbar help](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/proonly/the%5Ftools%5Ftoolbar.htm) lists Noise Reduction separately from Click and Crackle Removal, Clipped Peak Restoration and Audio Restoration. The current [Repairing Glitches, Clicks, and Noise help](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/proonly/repair.htm) places the newer Sequoia DeHisser, DeClicker/DeCrackler and DeClipper effects under **Effects**. Its references to bundled RX plug-ins and a Pro Suite/SpectraLayers package say nothing reliable about your current entitlement. Packaging needs its own check: the live [Sound Forge purchase matrix](https://www.soundforge.com/sound-forge/pricing/) doesn't name an RX edition, an RX module or SpectraLayers. Check the license and installer for your exact purchase before following an RX or SpectraLayers tutorial; this workflow needs neither package. Sound Forge 11 and Audio Studio 12.5 tutorials describe different dialogs. Don't assume those labels, or a MAGIX-era Pro 18 bundle, carry over to a Boris FX 2026 purchase. Use the **?** button in the plug-in you actually opened for its control definitions. ## Capture a clean noiseprint in seven steps A noiseprint is a frequency profile of the unwanted sound. It's useful when the noise is reasonably steady and the sample contains no wanted audio. Take enough noise to represent the passage you'll process, without padding the selection with the end of a word, a breath, a cymbal tail or a transient. Listen to the selection on its own first. The [Audacity manual explains the same profile principle](https://manual.audacityteam.org/man/noise%5Freduction.html): unwanted-only material and representative noise statistics matter, and looping a tiny sample adds no information. Its numeric limits aren't NR-2.0 settings, though. ![A noise-only passage selected in Sound Forge and captured as an NR-2.0 noiseprint](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/10/background-noise-ui-noiseprint-v20261010.webp) Capturing a noiseprint in Sound Forge NR-2.0: select only the unwanted sound, capture the profile, then judge with Preview and Bypass. 1. **Keep an untouched source.** Work on a separate PCM or float copy. Keep the capture sample rate while testing and avoid repeated MP3 encoding; never overwrite the only recording. 2. **Select noise only.** Listen to a representative pause with no wanted speech, breath, music or transient. Keep the same source and recording conditions as the passage you want to repair. 3. **Open the classic tool.** Choose **Tools → Noise Reduction**. Continue only if the installed dialog shows the Noiseprint controls described here. 4. **Capture the noiseprint.** Enable **Capture noiseprint** and preview the noise-only selection. Confirm that a profile was captured before moving to wanted audio; do not keep learning from speech. 5. **Choose the processing target.** Stop preview, retain the captured profile and select the intended time range and channels. Use the dialog’s selection controls or its supported data-window selection; use Select All only when the same noise profile suits the whole file. 6. **Preview a difficult passage.** Listen with the processing active, then toggle Bypass for the original. Check quiet consonants, a note ending, a pause and a louder section at similar listening levels. 7. **Compare and apply conservatively.** Check the removed signal if available, then turn residual output and Bypass off. Apply only when the normal output preserves wanted detail. Save a new file and listen again; undo a rendered test before processing an overlapping larger region. The [current processing-dialog help](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/using%5Fprocessing%5Fdialogs.htm) separates Preview from OK and describes time/channel selection controls. A [Sound Forge 11 capture walkthrough](https://www.moviestudiozen.com/forum/sound-forge/2150-how-to-do-simple-background-noise-reduction-wtih-sound-forge-11) documents the classic Capture noiseprint sequence and the older Select All Data command. That's version-labeled evidence and doesn't confirm every 2026 plug-in dialog. If your controls differ, use its **?** help and check that changing the target didn't throw away the profile. ## Do not copy an NR-2.0 mode recipe Some legacy NR-2.0 dialogs show reduction types named Mode 0 through Mode 3\. The current Boris FX pages checked here don't define those modes or set a default for your installed plug-in, so an old claim such as “Mode 2 for voice” isn't a 2026 specification. If your installed dialog has those modes, read its **?** help and audition each available choice against the same stress-test passage. ![NR-2.0 settings auditioned in Sound Forge through Preview, Bypass and the residual signal](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/10/background-noise-ui-preview-mode-v1-v20261005-v20261006.webp) Sound Forge NR-2.0 residual output is the fastest warning: if the removed signal contains recognizable voice or music, reduce the processing. There is no universal reduction amount. Use the lowest processing that makes the noise stop competing with the content. A number that works on a clean voice-over can damage a cassette transfer; a setting that works on constant fan wash can pump when an air conditioner cycles. If the classic dialog includes **Keep residual output**, use it to hear what would be removed. Recognizable words, notes or wanted ambience in there are a warning sign. They're never a reason to approve the residue as the finished file. Turn the option off and judge the normal processed output, backing off or recapturing the profile if speech, attacks or fades sound damaged. Don't copy values shown in the diagrams as presets: your file and your installed controls decide the settings. ## Match the repair to the defect ![Each Sound Forge repair tool matched to the defect it was built for](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/10/background-noise-ui-tool-map-v1-v20261005-v20261006.webp) Broadband noise, hiss, clicks, clipping and mains tones each need a different Sound Forge tool — diagnose before processing. **Room tone, HVAC and fan wash:** capture one clean profile and preview a conservative broadband pass. If the noise changes after a microphone move or an HVAC state change, use separate selections with representative profiles where you can. Preview across each boundary so the noise floor doesn't jump; a shorter selection on its own won't fix a missing profile. **Tape or preamp hiss:** compare Noise Reduction with DeHisser. Listen to sibilants, cymbals, string texture and ambience. A little stable hiss is usually less distracting than metallic “musical noise” that follows every word or note. **Mains hum:** inspect the recording instead of notching a memorized list. The power system tells you where to look, but the file tells you which fundamental and harmonics are actually there. Open **View → Spectrum Analysis**. Use the [Sound Forge Spectrum Analysis workflow](https://soundforgepro.com/how-to-use-spectral-analysis-tool-sound-forge-pro/) before the narrow correction. **Clicks and crackles:** use the dedicated click tools. For a single glitch, try a local repair first so unrelated audio doesn't go through processing it never needed. The [click-and-pop guide](https://soundforgepro.com/how-to-remove-clicks-pops-sound-forge-pro/) covers automatic and manual verification. ## What if there is no clean noise-only passage? Check the head, tail and pauses between phrases at high zoom before giving up. If every quiet area contains wanted sound, don't teach the classic plug-in a contaminated profile and hope a stronger setting will repair the mistake. - Use smaller regions only when you can get a valid profile for each. A smaller selection can't conjure noise-only material out of nothing. - Try DeHisser for regular low-level white noise; it doesn't need a captured noise sample. Follow the [DeHisser control and residue checks](https://soundforgepro.com/remove-hiss-hum-sound-forge/) instead of the classic noiseprint sequence above. - For changing noise, consider a licensed adaptive denoiser. The [RX 12 Spectral De-noise manual](https://docs.izotope.com/rx12/en/spectral-de-noise.html), for example, describes Adaptive mode and lists the module under Standard/Advanced, not Elements. It can be demanding on CPU and memory. Treat it as an optional alternative: it isn't an included plug-in. The [Voice De-noise vs Spectral De-noise comparison](https://izotoperx.net/voice-denoise-vs-spectral-denoise/) on izotoperx.net shows which module fits a given recording. - For isolated events or overlapping music, consider spectral repair or source separation. If the wanted sound is buried in noise, accept a partial improvement or re-record when possible; no process guarantees clean separation. For a new recording, capture room tone before people move, the HVAC changes state or the microphone position shifts. The [Sound Forge recording guide](https://soundforgepro.com/how-to-record-audio-in-sound-forge-pro/) covers input, monitoring and headroom checks that prevent avoidable noise at source. ## If Tools → Noise Reduction is missing The current purchase matrix lists **Broadband noise reduction** in its Features section, while the current help places the classic commands under Tools. If your application doesn't match that documentation, collect evidence before changing the installation. 1. Record the exact product name, edition and build shown by the application. 2. Check both the Tools menu and the Tools toolbar for Noise Reduction. 3. Note which restoration effects appear under Effects and which licensed modules appear under FX Plug-In. 4. Capture a screenshot of the missing command and the visible restoration list. 5. Send those details to Boris FX support or compare them with your account and installer. Do not try to fix a 2026 packaging mismatch by downloading an old standalone NR-2.0 binary, changing hidden settings or following an administrator-mode recipe written for Sound Forge 11\. Those moves can create a second compatibility problem and still won't explain why the current command is missing. If you have a valid noise-only sample and need a free fallback, the [current Audacity Noise Reduction workflow](https://www.audacityteam.org/manual/effects/noise-removal-and-repair/noise-reduction/) separates Get noise profile from applying the filter to the target. Work on a copy and bring the cleaned PCM file back into Sound Forge. It's a different application, so don't look for it as a menu path inside Sound Forge. ## Artifact check: know when to stop - **Metallic or watery speech:** these artifacts show up when reduction removes wanted detail or can't follow the noise. Compare Bypass, lower the amount and, if needed, try a cleaner profile. - **Dull music or softened consonants:** listen to residual output when available. Wanted high-frequency detail in the residue is a reason to check the normal output for damage, then ease the processing if necessary. - **Pumping or breathing:** changing noise, excessive reduction or an unsuitable profile can produce this behavior. Compare a lighter setting; use separate regions when the noise changes. - **Silent holes between phrases:** check whether a gate is also active. A gate can close abruptly and reopen under the next word. The finish line isn't digital silence; it's a recording in which the noise no longer competes with the content. Stable room tone is often less distracting than processing that announces itself on every breath. ## Repair before final loudness Keep the original, try repairing major clicks or clipped peaks where needed, reduce measured hum and steady noise, and only then set final peak or loudness targets. That's a starting order; you don't have to run every process. Undo any trial that makes a later repair harder. The current [Normalize documentation](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/proonly/normalizing%5Faudio.htm) describes gain applied to reach a target level. A constant gain adjustment raises wanted audio and the remaining noise together, so their ratio stays the same. If the selected normalization mode also limits or compresses peaks, judge those dynamics separately. Preview the full chain before rendering. A denoiser, EQ and limiter can each sound acceptable alone but become too aggressive together. Keep the cleaned lossless master separate from the original and from the [MP3 delivery copy](https://soundforgepro.com/how-to-export-mp3-from-sound-forge-pro/). Listen to the complete export, including region boundaries and fades. If you need final level adjustment, the [normalization guide](https://soundforgepro.com/how-to-normalize-audio-in-sound-forge-pro/) separates constant gain from dynamics processing. ## Frequently Asked Questions ### Where is Noise Reduction in Sound Forge 2026? Open **Tools → Noise Reduction** or use the Noise Reduction button on the Tools toolbar. Current help places Sequoia DeHisser, DeClicker/DeCrackler and DeClipper under Effects, while licensed third-party modules appear through FX Plug-In. ### How do I capture a noiseprint in Sound Forge? Select noise-only audio, open the classic Noise Reduction dialog and capture its profile with Capture noiseprint and Preview. Retain that profile, choose the intended time range and channels, then compare processed audio with Bypass. Turn residual output and Bypass off before applying. If your dialog differs, follow its **?** help. ### What is the best Sound Forge noise-reduction setting? There is no universal setting. Use the lowest reduction that makes the noise stop distracting without changing wanted detail. The current Boris FX pages checked here do not establish legacy Mode 0–3 behavior for your build. Use the installed plug-in help, compare the same test passage and avoid copying pictured values as presets. ### Why does noise reduction make a voice sound underwater? An unsuitable profile, excessive reduction or changing noise can produce watery speech. Compare Bypass, lower the amount and try a cleaner sample or separate regions. Recognizable speech in residual output is a warning to check whether useful detail is being removed. ### Why is Tools → Noise Reduction missing? Record the exact product, edition and build, then check the Tools menu, Tools toolbar, Effects and FX Plug-In lists. The current purchase matrix lists broadband noise reduction, but legacy and Audio Studio interfaces differ. Send the mismatch and screenshots to Boris FX support instead of installing an old NR-2.0 binary blindly. ### Should I remove background noise before normalizing? As a default, repair and reduce noise before final loudness work, while keeping the untouched source. Constant gain alone can come before or after denoising if the profile and processing settings match the resulting signal; it raises wanted audio and noise together. Limiting or compression changes dynamics, so audition that stage separately. ### Can Sound Forge remove background music from speech? Classic broadband noise reduction cannot reliably separate changing music from overlapping speech. That job needs source separation or spectral editing, and the result depends on the source and the licensed tool you use. ### What should I use for clicks, hum or clipping? Use Click and Crackle Removal or DeClicker/DeCrackler for clicks, Spectrum Analysis before a narrow hum correction, and Clipped Peak Restoration or DeClipper for clipping. These are different defects from steady broadband background noise. *Documentation and linked workflows checked September 8, 2026\. Exact plug-in availability and controls still depend on your installed edition and license.* ### How to Export MP3 from Sound Forge Pro URL: https://soundforgepro.com/how-to-export-mp3-from-sound-forge-pro/ Last updated: 2026-10-09T21:08:14.000Z To export an MP3 from Sound Forge Pro 2026, click the data window, choose **File → Save As**, select MP3 in **Save as type**, choose a template whose stated properties match the destination, and click **Save**. Open **Custom** to inspect the settings supported by the selected MP3 format. The current [Boris FX Save As documentation](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/saving%5Fa%5Ffile%5Fas%5Fa%5Fdifferent%5Fname%5For%5Ftype.htm) makes those controls format-dependent, so do not assume every bitrate, sample-rate and channel combination is available. If you are working in a Sound Forge Pro project rather than directly in a media file, choose **File → Render As** to create the delivered MP3\. In a project, **Save As** saves the project under another name or location; **Render As** commits the edits to a media file. That is the current distinction in the [Boris FX Save As/Render As workflow](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/saving%5Fa%5Ffile%5Fas%5Fa%5Fdifferent%5Fname%5For%5Ftype.htm). ![MP3 workflow: Save As, choose an MP3 template, save a separate output and reopen it](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/10/export-mp3-ui-save-verify-v2-1-v20261008.webp) Choose MP3 and the required template, save a separate output, then reopen it. Follow the written steps for the current controls. ## Export MP3 in seven steps 1. **Keep a lossless master.** Finish the edit and retain a WAV or another accepted lossless master. 2. **Select the data window.** Click inside the sound data window you intend to export. 3. **Open Save As or Render As.** Choose **File → Save As** for sound data, or **File → Render As** for a Sound Forge Pro project. 4. **Choose MP3.** Enter the output filename and select MP3 in **Save as type**. 5. **Choose or inspect the template.** Select a template that matches the written delivery specification, or click **Custom** to inspect the format-specific properties available. 6. **Choose metadata handling.** Enable **Save metadata with file** only when the required fields have been reviewed. 7. **Save, reopen and verify.** Click **Save**, reopen the MP3, then check duration, channels, bitrate mode, sample rate, metadata and the audible beginning and end. The current dialog uses a **Template** list and a **Custom** button. Older screenshots may call this area “Format Settings,” and encoder-specific controls can differ. The [current Custom File Templates help](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/templates.htm) tells you to use the Help button inside the selected format’s Custom Template dialog for its exact controls. ## Which export command should you use? | Command | Use it for | Main risk | | ---------------- | --------------------------------------------------------- | --------------------------------------------------------------------------- | | File → Save | Writing the current sound data back to its existing file | A lossy source can be encoded again without creating a separate master | | File → Save As | Creating a different filename and/or format | Overwriting the source if the destination name is not checked | | File → Render As | Committing a Sound Forge Pro project to a media file | Using Save As and ending up with another project instead of a delivered MP3 | | File → Export | Rendering selected open audio files with an export preset | Exporting unintended files or applying settings left in the preset | Keep a lossless working master and create the delivery MP3 from it. Saving an existing MP3 is not a reliable way to select a new delivery bitrate; use an explicit export template and verify the saved file. Editing and re-encoding an MP3 adds another lossy generation. ## Export open files with File → Export For several files already open in the editor, [File → Export](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/proonly/export.htm) provides an export-preset workflow. Choose or prepare a preset with MP3 under **Export Formats → Renderer**, select its **Template**, and use **Edit** if the format settings need changing. Set a separate output folder or filename suffix. Before starting, inspect **Normalization/Conversions**, **Metadata** and **Watermark**. Leave unnecessary processing off and remove any unwanted watermark file. With metadata **Overwrite** enabled, an empty field can erase an existing value. This preset controls more than the MP3 encoder. **All open audio files are checked by default in Export Files.** Uncheck everything you do not intend to deliver, then click **Export**. For files still in folders rather than open windows, use Batch Converter below. Its input list is a separate step. ## Choose bitrate from the destination requirement No single bitrate is correct for every delivery. Read the receiving platform’s current specification first, then choose a template whose displayed properties match it. Bitrate, sample rate and bit depth are different values, and changing one doesn't automatically satisfy the others. - **Music reference copy:** a high-rate stereo MP3 can be convenient, but keep and deliver the lossless master whenever the recipient accepts it. - **Speech:** keep genuinely mono speech mono if the receiver accepts it. At the same CBR and duration, mono does not halve the MP3 file size; size follows the total bitrate. Don’t collapse a stereo production just because it contains voice. - **Audiobooks for ACX:** the current [ACX submission requirements](https://help.acx.com/s/article/what-are-the-acx-audio-submission-requirements) call for 44.1 kHz MP3, 192 kbps or higher CBR, and consistent mono or stereo across the title. These are ACX rules, not universal podcast settings. - **Music distribution:** send a lossless file when the distributor accepts one. Encoding a WAV master to MP3 and then having the service encode that MP3 again adds a lossy generation. CBR writes a constant target bitrate; VBR varies allocation according to the material and quality mode. Compatibility requirements decide between them. If a client or submission portal specifies CBR, choose a template that explicitly reports CBR. If it accepts VBR, verify the exported file rather than trusting a remembered default. A [2024 MAGIX community thread about Pro 16](https://www.magix.info/us/forum/how-to-export-mp3-48khz-192-kbps-with-sound-forge-16--1333601/) confirms the Custom/preset route but also records encoder-specific limits. Treat that as a warning to inspect the current template, not as proof that the 2026 encoder has the same limitation. Sample rate is also destination-led. Don’t convert a 48 kHz video source to 44.1 kHz merely because the output is MP3 unless the delivery specification asks for it. When conversion is required, the [current Sound Forge Resample guide](https://soundforgepro.com/how-to-change-sample-rate-sound-forge-pro/) explains the 2026 phase and aliasing controls. ## Create a repeatable custom template In Save As or Render As, choose MP3 and click **Custom**. Choose an existing custom template or enter a descriptive name, set the properties that the selected format exposes, then click **Save Template**. The [current template documentation](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/templates.htm) also states that built-in templates cannot be edited. Name the template for the deliverable rather than “High Quality”: for example, include the intended bitrate mode, bitrate, sample rate and channels. Sound Forge stores custom `.sft2` templates below the user’s `AppData\Roaming\BorisFX\Render Templates` tree. Before trusting one, export a short representative file and inspect it outside the editor. A saved template repeats settings; it doesn't prove that a new client or platform accepts them. ## Keep or remove metadata deliberately The Save As dialog includes **Save metadata with file**, and the current help lists MP3 among the formats that can store metadata internally. If the selected format cannot store all metadata, Sound Forge can offer an external `.sfl` sidecar with the same base name instead. Decide whether the recipient needs that sidecar before delivery. Review metadata before delivery; a public MP3 shouldn't inherit private notes, an obsolete project title or a local workflow comment. The current [Metadata Windows documentation](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/metadata%5Fwindows.htm) uses **View → Metadata**, followed by the relevant submenu command. Confirm the exported fields in a second player or metadata reader, because applications don't always expose the same fields in the same way. ## Can an SFK file be converted to MP3? No. An `.sfk` file is a peak/cache sidecar used to help draw an audio waveform; it does not contain the source audio. The current [Boris FX glossary entry for Peak Data File](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/glossary.htm) describes the waveform-display information stored in this sidecar. Sound Forge can create an SFK next to a WAV, MP3 or other media file when it analyzes the waveform. Seeing both files doesn't mean the MP3 export failed. If only the SFK remains, you'll need to locate or restore the original media; renaming or converting the cache can't recover the sound. ## MP3 is missing or unavailable 1. Click the intended sound data window so it is active. 2. Use **Save As** for sound data; use **Render As** when the active document is a Sound Forge Pro project. 3. Open **Save as type** and look for MP3 before changing the Template list. 4. Update Sound Forge to the current build available for your license, restart it, and test a new short mono or stereo file. 5. Record the exact edition, build number, active document type and visible file-type list. 6. If MP3 is still absent, send that evidence and a screenshot to Boris FX support before changing hidden preferences or reinstalling codecs. Do not start by deleting registry keys, wiping preferences or using a third-party uninstaller. The current Boris FX documentation does not describe a separate first-use Fraunhofer activation or a universal cache-corruption fix. Destructive resets without evidence can erase useful configuration while leaving the real packaging or installation problem untouched. ## Batch-export multiple files to MP3 Choose **Tools → Batch Converter**. For a format-only batch, first remove unwanted entries from Processing and check that no Watermark file is selected; a loaded preset can add processing or mix in another audio file. Add files or a folder, then add MP3 under Export Formats using **Renderer** and **Template**. Click **Edit** to create or modify the output template, choose the destination and naming rules under Options, and run the job. For input inventory, pilot runs, output naming and sampling rules, use the [dedicated Sound Forge batch-processing guide](https://soundforgepro.com/how-to-batch-process-files-sound-forge-pro/). The current [Batch Converter documentation](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/proonly/the%20batch%20converter.htm) adds several details older guides omit: - one job can produce multiple output formats; - open data windows are added automatically but can be unchecked; - Add Folder includes that folder’s files, not its subfolders; - metadata can be preserved or overwritten when the output format supports it; - output can keep source subfolders and append text to filenames; - a saved batch preset can become an Instant Action or a Windows Explorer context-menu command. Test a batch preset on two files with different sample rates or channel layouts before sending a large catalog through it. Inspect both outputs and keep the lossless sources. ## Check the MP3 after export - Confirm the filename and `.mp3` extension. - Inspect duration, sample rate, bitrate mode and channel count. - Listen to the first and last seconds for clipped attacks, truncated fades or added silence. - Spot-check the loudest and most complex passage for codec artifacts. - Verify title, artist, artwork and other required metadata in a second application. - Keep the WAV master and the exact export requirement with the project notes. - If loudness is part of the specification, use **Tools → Generate Loudness Log** on the saved MP3\. The [current Boris FX guidance](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/saving%5Fa%5Ffile%5Fas%5Fa%5Fdifferent%5Fname%5For%5Ftype.htm) says the log option inside Save As is measured before the codec is applied. ## Frequently Asked Questions ### How do I export an MP3 from Sound Forge Pro? Choose File → Save As for a sound data window, select MP3 in Save as type, choose a suitable Template or inspect Custom, decide whether to save metadata, and click Save. Use File → Render As when the active document is a Sound Forge Pro project. ### What bitrate should I use? Use the receiving platform’s current requirement and verify the exported file. There is no universal best value. ACX currently requires 44.1 kHz MP3 at 192 kbps or higher CBR, while a music distributor may prefer a lossless master instead of MP3. ### Should I choose CBR or VBR? Choose CBR when the destination specifies it or compatibility is strict. Use VBR only when the receiver accepts it. Confirm that the selected template explicitly reports the required mode; available combinations can depend on the encoder. ### Why did Sound Forge create an SFK file? SFK is waveform peak/cache data created alongside media. It is not the exported audio and cannot be converted into MP3 without the original sound file. ### Why is MP3 missing from Save As? Confirm that a sound data window is active, use Render As for a project, update and restart Sound Forge, and test a new short mono or stereo file. If MP3 remains absent, send Boris FX support the exact edition, build, document type and screenshot instead of changing hidden settings blindly. ### Can Sound Forge export many MP3 files at once? Yes. Use File → Export for selected open audio files, or Tools → Batch Converter to add files and folders. Check the MP3 renderer/template, processing, metadata and destination before running either workflow. ### Should the master be MP3 or WAV? Keep the working and archival master lossless, normally WAV or another accepted lossless format. Create MP3 once for a destination that requests it; do not repeatedly edit and re-encode the delivery copy. If the job also changes format, sample rate or bit depth, use the [complete Sound Forge conversion workflow](https://soundforgepro.com/how-to-convert-audio-files-sound-forge-pro/) before encoding the MP3\. If the level needs adjustment, work on the lossless master using the [normalization guide](https://soundforgepro.com/how-to-normalize-audio-in-sound-forge-pro/). Then encode a fresh MP3 and measure that delivery file; a pre-export reading does not verify the encoded result. *Last checked against the linked documentation and delivery requirements: September 12, 2026.* ### How to Cut and Trim Audio in Sound Forge Pro URL: https://soundforgepro.com/how-to-cut-and-trim-audio-in-sound-forge-pro/ Last updated: 2026-10-09T11:07:40.000Z Use Ctrl+X when you want to remove the selected audio and keep it on the clipboard. With waveform focus and Treat as Cutlist off, press Delete to remove it without replacing the clipboard. Use Ctrl+T when the selection is the part you want to keep and everything outside it should go. Those three commands solve different jobs. In Sound Forge, **Trim/Crop means keeping the selected range and removing the audio before and after it**; Cut and Delete do the opposite by removing the selection itself. The table below is the short version; the rest of this guide covers precise selections, zero crossings, [automatic silence removal](https://soundforgepro.com/sound-forge-auto-trim-crop/), multichannel files and event-based editing in Sound Forge Pro 2026. | Command | Shortcut | What remains | Clipboard | | --------------------- | -------- | --------------------------- | ------------------------------------------------------- | | Edit → Cut | Ctrl+X | Audio outside the selection | Selected audio replaces the previous clipboard contents | | Edit → Delete (Clear) | Delete | Audio outside the selection | Unchanged | | Edit → Trim/Crop | Ctrl+T | Only the selected audio | Unchanged | **For a clean manual edit, work in this order.** Use the default shortcuts with the waveform window focused (Alt+0); if you changed the mapping, use the named menus. The defaults are listed in the [current Boris FX keyboard map](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/keyboard%5Fshortcuts.htm). 1. **Select the Edit tool.** Use the regular waveform-editing tool, not the Event tool. 2. **Select the audio.** Drag over the range you want to remove or keep, including every channel that should change. 3. **Set exact boundaries.** Check Selection Start, End and Length; type a value when the edit must land at an exact time. 4. **Check zero crossings.** Use Z or Shift+Z when moving an edge to a zero crossing will reduce click risk. 5. **Choose the correct edit.** Use Ctrl+X to cut, Delete to clear or Ctrl+T to keep only the selection. 6. **Listen and save safely.** Audition the join in context, undo or fade if it clicks, then use Save As when the source must remain untouched. ![Waveform selection showing Cut and Delete remove the range while Trim/Crop keeps it](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/10/cut-trim-ui-selection-v3-1-v20261005-v20261006.webp) Cut and Delete remove the same selected range; only Cut copies it to the clipboard. Trim/Crop keeps the selection. ## Make a precise selection first 1. Select the **Edit tool**. 2. Click and drag across the waveform to mark the audio you want to remove or keep. 3. Check Selection Start, End and Length in the selection status bar. 4. Double-click a status-bar field when you need to type an exact time value. 5. Zoom in and move the edges before committing the edit. The current [Boris FX selection reference](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/selecting%5Fdata.htm) confirms that Selection Start moves the cursor when no range exists, while Selection End or Length can define and edit a selection. Right-click the status area to choose the time format that fits the job: time, samples, frames or another available ruler format. For stereo and multichannel files, dragging inside one channel selects only that channel. Drag across channels, or along the divider/loop bar, to select more than one. The [2026 mouse-selection guide](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/selecting%5Fdata%5Fusing%5Fthe%5Fmouse.htm) also documents Ctrl+click for adding or removing a channel from the selection and the Lock Channel Selection button for preserving the channel set while changing the time range. ## Cut: remove the selection and keep it Choose **Edit → Cut** or press Ctrl+X. Sound Forge removes the selected sound data and copies it to the clipboard, replacing whatever was there before. You can then position the cursor and press Ctrl+V to paste it, or Ctrl+E to paste it into a new data window. Cut is the right choice when you might reuse the removed section. If you just want it gone, Delete is safer since it leaves the existing clipboard alone. The official [Cut documentation](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/cut.htm) also spells out an easily missed multichannel behavior: cutting data from an individual channel leaves silence at the *end* of that channel, because every channel in the file must remain the same length. ## Delete/Clear: remove it without touching the clipboard Select the unwanted audio and press Delete, or choose **Edit → Delete (Clear)**. The selection disappears without being copied anywhere, which makes this the cleanest command for a cough, a false start or a dead section you won't paste back in. There's one special case. If **Edit → Playlist/Cutlist → Treat as Cutlist** is enabled, Delete creates a Cutlist region instead of removing the selection. If Delete seems to do nothing to the waveform, check that mode before troubleshooting the keyboard. That behavior and the same individual-channel end-silence rule are documented on the current [Delete/Clear help page](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/clear%5Fdelete.htm). ## Trim/Crop: keep the selection and discard the outside Highlight the audio you want to keep, then choose **Edit → Trim/Crop** or press Ctrl+T. Sound Forge removes everything outside the selection from the selected channel, and nothing goes to the clipboard. This is the fastest manual way to remove lead-in and tail material from a recording: select from the intended start to the intended finish, listen across both boundaries, and crop. The exact selected-channel scope comes from the [Sound Forge Pro 2026 Trim/Crop reference](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/trim%5Fcrop.htm). On a stereo or multichannel file, deliberately select every channel when you want one coherent start and end; don't assume a single-channel selection will crop the whole file. If the kept audio starts or ends abruptly, undo and move the boundary. If the edge still sounds abrupt, select a short edge region. The [current linear Fade commands](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/fade.htm) are **Process → Fade → In** and **Process → Fade → Out**, and **Process → Fade → Graphic** lets you shape the curve. The right length depends on the source, so keep the initial transient and the natural final decay instead of using one fixed value on every file. ## Prevent clicks at edit points A jump between the samples on either side of a cut can cause a click. Editing close to a zero crossing lowers that risk, but a point that looks quiet isn't automatically a zero crossing. - Press Z for **Edit → Selection → Snap to Zero**, which moves both selection edges. - Press Shift+Z for **Snap Edge to Zero**, which moves only the active edge. - For automatic snapping, check both **Options → Snapping → Enable** and **Options → Snapping → Zero Crossings**. F8 and Ctrl+B toggle those settings, so don't hit them blindly when the options are already on. - Use Home or End to change the active selection edge before an edge-only snap. The current [Enable Snapping help](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/enablesnapping.htm) distinguishes automatic snapping from the manual Z and Shift+Z commands. Automatic snapping requires Enable to be checked; the manual commands move the selection edges when you invoke them. The Editing preferences let you choose positive, negative or any zero crossing. The current [Selection Snapping documentation](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/selection%5Fsnapping.htm) uses the names “Snap to Zero” and “Snap Edge to Zero.” Snapping reduces click risk, but it can't guarantee that two unrelated waveform shapes will join invisibly. Listen across the edit and use a short fade or event crossfade when needed. ## Auto Trim/Crop: remove silence by detection Choose **Process → Auto Trim/Crop** when you'd rather have the edit detected from level than place it by hand. It's handy for repeated recordings with similar silence and noise, but it needs a threshold that separates the quietest sound you want from the unwanted floor. The 2026 dialog has five functions; there's no single generic “remove silence” mode: | Function | What it does | | ------------------------------------------------ | --------------------------------------------------------------------------------------------------------- | | Keep edges outside of the selection | Deletes silence between the selection boundaries and detected sound, but keeps data outside the selection | | Remove edges outside of the selection | Deletes that silence and also deletes everything outside the selection | | Remove silence between phrases (creates regions) | Deletes qualifying silence inside the selection and creates regions between phrases | | Remove data beyond loop points | Deletes material after a selected loop while retaining the specified minimum samples after the loop end | | Remove data from start and limit file length | Deletes a specified amount from the start and caps the converted file length | **Attack threshold** detects the start; **Release threshold** detects the end. Fade In and Fade Out protect the detected phrase boundaries, while Minimum inter-phrase silence determines when the phrase mode creates a new region. These names and functions are verified against the current [Auto Trim/Crop help](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/proonly/auto%5Ftrim%5Fcrop.htm). Start conservatively. Preview or work on a copy, especially with breathy speech, reverb tails, soft instrument attacks and noisy archival recordings, because a threshold that strips room tone can take intentional quiet material with it. For one important file, manual Trim/Crop is often quicker than fixing an aggressive automatic result. ## Zoom to the edit, then verify in context Roll the mouse wheel to zoom horizontally; hold Ctrl while rolling to zoom vertically. With a selection active, Ctrl+Up Arrow zooms to that selection. Use **View → Zoom Time → Normal** for the default time scale, or **View → Zoom Time → Out Full** to see the whole file. The Magnify tool lets you drag around the exact area without losing the selection. At full horizontal zoom Sound Forge can show 24 pixels per sample. That helps with placing an edge, but make the final call by ear at normal scale. The [current magnification guide](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/magnification%5Fand%5Fzooming.htm) documents the complete zoom set. ## Split and trim events without changing the source range A split works on events and doesn't cut sample data the way a cut does. Select the **Event tool**, position the cursor, select the event if needed, then choose **Edit → Event → Split** or press S. With no event selected, Sound Forge splits the events under the cursor across all channels; with events selected, only those get split. Ctrl+Alt+T splits at region boundaries. With the Event tool active, drag an event edge to trim it. An event can't extend past its underlying media, but dragging the edge back can bring back media the trim only hid. Hold Alt while dragging an event to slip its contents without moving the event, and hold Alt while dragging an edge to slip-trim. These behaviors are documented in the current [Splitting Events](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/split.htm) and [Slipping and Trimming Events](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/slipping%5Fand%5Ftrimming%5Fevents.htm) pages. They are the right tools when you need adjustable edit boundaries. For a finished single-file crop, the Edit-tool selection plus Ctrl+T remains simpler. ## Keep a safe way back Ctrl+Z reverses the last edit and Ctrl+Shift+Z redoes it. The [current Undo guidance](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/undo.htm) says that, when **Undo past Save** is enabled in General preferences, history remains available after saving only until you close the data window or exit Sound Forge. Save a Sound Forge Pro project when you need undoable edit history after closing and reopening the work. For irreplaceable recordings, use Save As before any destructive data edit. Undo is handy in the moment, but it's no backup. ## Frequently Asked Questions ### What is the difference between Cut and Trim/Crop? Cut removes the selection and copies it to the clipboard. Trim/Crop keeps the selection and removes everything outside it from the selected channel. Use Cut when the selected material should disappear and may be pasted elsewhere; use Trim/Crop when the selection itself is the finished range. ### How do I crop audio in Sound Forge Pro? Select the audio you want to keep, then press Ctrl+T or choose Edit → Trim/Crop. Check the selected channels before applying it to a stereo or multichannel file. ### How do I remove silence from the beginning and end? For one file, select from the intended first sound to the final decay and use Trim/Crop. For repeatable level-based detection, choose Process → Auto Trim/Crop and use Remove edges outside of the selection. ### Why does a cut click or pop? The new join may contain a waveform discontinuity. Use Z or Shift+Z to snap the selection to zero crossings, listen to the join, and add a short fade or event crossfade when snapping alone is not enough. ### Can I enter an exact cut time? Yes. Double-click Selection Start, End or Length in the status bar and type the value in the active time format. Then apply Cut, Delete or Trim/Crop. ### Does Trim/Crop always affect every channel? No. The current documentation says it removes outside data from the selected channel. Select all required channels deliberately when you need one coherent crop across a stereo or multichannel file. ### How do I split at the cursor? Use the Event tool, position the cursor and press S, or choose Edit → Event → Split. This splits events; it is not a separate destructive split command for raw waveform data. Once the boundaries are clean, decide whether the level needs changing with the [normalization guide](https://soundforgepro.com/how-to-normalize-audio-in-sound-forge-pro/) and create the delivery copy with the [MP3 export steps](https://soundforgepro.com/how-to-export-mp3-from-sound-forge-pro/). For repetitive editing, keep the [Sound Forge shortcut reference](https://soundforgepro.com/sound-forge-pro-keyboard-shortcuts/) beside the editor instead of relying on legacy key maps. *Last checked against the linked Sound Forge Pro 2026 documentation: September 12, 2026.* ### How to Record Audio in Sound Forge Pro 2026 URL: https://soundforgepro.com/how-to-record-audio-in-sound-forge-pro/ Last updated: 2026-10-09T21:06:27.000Z **To record audio in Sound Forge Pro 2026, verify Windows microphone access, select the correct driver, route the hardware input, create a file with the required format, open View → Record Options, arm the input and check the meters before pressing Record.** If the recorded file is silent, check permissions, the selected device and input routing before replacing the microphone. Sound Forge is strongest for recording into one mono, stereo or multichannel audio file. It isn’t a multitrack DAW: several inputs can become channels in one data window, but you don’t get independent timeline tracks for arranging a band or podcast cast. **Use a ten-second test:** stop, play it back from Sound Forge and save it before committing a performance or an entire record side. Check the resulting file’s format as well as listening: a wrong input, missing channel or clipped peak is easier to fix before the full take. For editing after capture, the [Core Editing guides](https://soundforgepro.com/tag/core-editing/) cover trimming, processing and export. ![Recording setup with Windows microphone permission, Sound Forge driver, input routing and armed meters](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/08/record-audio-ui-route-arm-v3.webp) Allow desktop microphone access, select the driver, map inputs, then arm and record. Follow the written steps for the current controls. ## 1\. Allow microphone access in Windows 11 Open **Start → Settings → Privacy & security → Microphone**. Confirm Microphone access and **Let desktop apps access your microphone** are enabled. Sound Forge is a desktop application, so it may not appear as an individual Microsoft Store-style toggle. [Microsoft’s current privacy guidance](https://support.microsoft.com/en-US/Windows/privacy/windows-camera-microphone-and-privacy) documents that Windows 11 path and the separate desktop-app control. If access is already enabled, continue to the driver and input checks. ## 2\. Select the driver in Audio Preferences Go to **Options → Preferences → Audio**. The current Sound Forge help lists three Audio Device Type choices: - **ASIO:** choose the manufacturer’s driver for a supported audio interface and low-latency routing. - **Windows Classic Wave Driver:** choose a specific Windows audio device through the classic driver path. - **Microsoft Sound Mapper:** let Windows choose the default playback and recording devices. For a dedicated interface, start with its current manufacturer ASIO driver when one exists. For a simple USB microphone or built-in input, Classic Wave or Sound Mapper may be sufficient. “ASIO” is not a quality preset: a wrong or unstable driver is worse than a working Windows path. Click **Apply** after changing the device type, then **Advanced**. With ASIO selected, **Configure** opens the interface maker’s control panel. The [Audio Preferences help](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/audio%5Fpreferences.htm) and [Advanced Audio Configuration help](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/advanced%5Faudio%5Fpreferences.htm) document those current controls. There’s no universal 64- or 128-sample buffer worth copying. Lower settings can reduce software-monitoring delay but raise glitch risk; larger buffers can help with gaps, although they will not fix every recording fault. If gaps appear in the recording, raise the interface or Sound Forge record buffer and test again. The safe value depends on driver, sample rate, channel count and the computer. ## 3\. Route the input to the data-window channels Still in **Options → Preferences → Audio**, open the **Record** tab. In the **Channel** and **Device** table, assign each data-window channel to the intended hardware input. You can also change a channel’s input by clicking its channel number in the Record Options window. Enable the inputs you need where the driver exposes an Enable control, then save the routing with Apply or OK. The exact controls can vary with the selected driver. The data window limits what is recorded. A stereo window records two routed inputs; a six-channel window is required to record six enabled inputs. The current [multichannel recording help](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/recording%5Fmultichannel%5Faudio.htm) explains this mapping and explicitly says Sound Forge is not a multitrack editor. For one microphone, create a mono file unless the device intentionally delivers stereo. A mono mic copied to left and right isn’t a stereo recording; it’s just the same signal twice. ## 4\. Create the recording file Choose **File → New** and set sample rate, bit depth, channel count and channel layout for the job. Follow the delivery or preservation specification instead of choosing the largest number in each list. When the interface and workflow support it, 24-bit capture provides [more digital resolution and dynamic range](https://www.izotope.com/community/blog/digital-audio-basics-sample-rate-and-bit-depth) than 16-bit, so conservative recording levels remain practical. It does not add analog input headroom or prevent the microphone, preamp or converter from clipping. Set hardware gain below overload and keep the interface and Sound Forge sample rates aligned. If **Mode → Create new windows** is selected in Record Options, Arm and Record remain available even when no data window is open, and each restart or resume creates a new data window. In Normal or Create regions mode, create or open a data window first. File → New is still the safer choice when sample rate, bit depth, or channel layout matters. ## 5\. Open Record Options and choose the current method Choose **View → Record Options**. Legacy tutorials can blur the distinction between Method and Mode or show labels that are absent from the 2026 help. In the current release, Method controls how recording starts; Mode controls what Sound Forge does after you stop or pause and restart. **Method** controls how recording starts: - **Manual:** general recording, voice-over and recording into a selection. - **Automatic: Threshold:** starts when the input crosses a set level and stops after it remains below the stop condition. - **Automatic: MIDI Timecode:** follows specified incoming MIDI timecode. - **Automatic: Time:** starts at a chosen date/time and runs for the specified duration. **Mode** controls what happens when you stop or pause and restart: - **Normal:** continue the ordinary recording workflow. - **Create regions:** create a new region each time recording restarts or resumes. - **Create new windows:** create a new data window for each restart or resume. The current [Record Options documentation](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/recording%5Foptions.htm) defines those methods and modes. For the first test, stick with Manual + Normal; threshold logic can wait until the basic input works. ## 6\. Arm, meter and monitor With headphone volume low, click **Arm** to open the recording device and load its buffers. Arm is optional, but makes it easier to check the input before the take. Perform the loudest passage you expect to record, without deliberately overloading the microphone or preamp. Check that: - the correct channel meters move; - peaks remain below clipping; - left/right routing is intentional; - headphone monitoring has no feedback or obvious delay; - the interface and Sound Forge agree on sample rate. Set analog gain on the microphone preamp or interface. Turning up a clipped recording later will not restore the peaks lost at the converter. Sound Forge’s [Recording Setup help](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/recording%5Fsetup%5F.htm) recommends a strong signal with no clipping and defers hardware gain details to the device maker. To hear the input through Sound Forge, set **Monitor** to **On**; **Auto** monitors only during pre/post-roll and recording. To hear plug-in effects too, select **Monitor input through Plug-In Chain**. Those effects are not written into the recording. Hardware processing upstream of Sound Forge is a separate matter. If your interface’s direct monitor is already enabled, set Sound Forge’s Monitor to Off for that test. Otherwise you may hear the input twice, with a delayed copy from the software. Focusrite explains this [double-monitoring echo](https://support.focusrite.com/hc/en-gb/articles/207547105-I-m-hearing-an-echo-when-using-Direct-Monitoring). Use headphones at a comfortable level, and stop if speaker feedback begins. ## 7\. Record, stop and verify the file Press **Record** or **Ctrl+R**. Stop with Record or Stop; Pause suspends capture while keeping the device armed. With Loop Playback off, recording stops at the end of the selected time range. With Loop Playback on, it repeats the range for more takes; turn looping off for a single pass. Immediately play back the test from Sound Forge. Don’t rely on direct monitoring: direct monitoring proves the microphone reached the interface, not that the correct file was captured. Listen for dropouts, distortion, a missing channel and the wrong source. Check possible [DC offset](https://soundforgepro.com/remove-dc-offset-sound-forge/) with the waveform and Statistics’ Average value; listening alone does not establish it. Save the raw take before editing. For a new audio file, use **File → Save As**, choose a new filename and an uncompressed WAV format, and check that the template matches the recording’s sample rate, bit depth and channels. If you are working in a Sound Forge project, use **File → Render As** to create a playable audio file; saving the project alone is different. Boris FX documents the distinction in [Save As and Render As](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/saving%5Fa%5Ffile%5Fas%5Fa%5Fdifferent%5Fname%5For%5Ftype.htm). Reopen the saved file and check its start, end, duration and channel content. For voice work, edit mistakes before noise reduction, EQ, dynamics and loudness. For a vinyl side, preserve the untouched high-resolution transfer before restoration. The [voice-over workflow](https://soundforgepro.com/sound-forge-pro-for-voice-over-recording/) and [vinyl restoration workflow](https://soundforgepro.com/sound-forge-pro-for-vinyl-restoration/) cover those different next steps. ## Prerecord buffer, pre-roll and punch-in With Method set to Manual, click **Settings** in Record Options. The [current Creating a New Recording help](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/record%5Fnew.htm) explains that a prerecord buffer writes audio continuously after you arm. When recording starts, the buffered data is committed to disk but may remain hidden beyond the recorded event edge; use the Event Tool to slip or trim the left edge and expose it. Choose a buffer long enough to cover the opening you might miss, then verify that you can reveal the hidden lead-in with the Event Tool. Enable the Prerecord buffer checkbox in Settings and enter the duration you need. Without that option enabled, arming alone does not preserve an earlier opening. Work on a saved copy before punch-in recording: recording into an existing file replaces audio at the cursor or selection. Select the part of that copy to replace, use Manual recording with Normal or Create regions mode, turn Loop Playback off for one take, and configure pre-roll/post-roll if you need context. The current [Recording into an Existing Sound File help](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/record%5Fpunch-in.htm) confirms that recording occurs underneath that roll and that the Event Tool can reveal material beyond the visible edge. It is a cursor- or selection-based workflow, not a separate current “Punch-In” Mode. ## No input signal: check in this order 1. **Windows:** microphone access and desktop-app access are enabled. 2. **Hardware:** the mic/source reaches the correct interface input, phantom power is used only when required, and the hardware meter moves. 3. **Driver:** the intended ASIO, Classic Wave or Sound Mapper path is selected. 4. **Routing:** the input is enabled and assigned on Preferences → Audio → Record. 5. **File:** the data window has the required channel count. 6. **Format:** interface and application sample rates agree. 7. **Arm:** the Record Options meters move before Record is pressed. For computer or system audio, Sound Forge can record only an input exposed by the selected driver. Don’t assume every PC has “Stereo Mix.” Use a loopback input only when the installed interface or driver provides one, select that actual input in Sound Forge and follow the driver maker’s routing instructions. Keep Sound Forge’s input monitoring off while testing loopback so its output is not fed back into the same capture path. For a supported Scarlett, follow the model-specific [Focusrite Control 2 loopback instructions](https://support.focusrite.com/hc/en-gb/articles/13229216604562-How-to-use-Loopback-in-Focusrite-Control-2); input numbers are not universal. If the meters still stay flat after this checklist, use the dedicated [Sound Forge no-input and ASIO troubleshooting sequence](https://soundforgepro.com/sound-forge-pro-not-recording-audio/) instead of changing several settings at once. ## Frequently Asked Questions ### How do I start recording in Sound Forge Pro 2026? Create a file with File → New, route the input under Options → Preferences → Audio → Record, open View → Record Options, choose Manual + Normal, click Arm, verify the meters, then press Record or Ctrl+R. ### Which audio driver should I use in Sound Forge Pro? Use the manufacturer’s ASIO driver for a supported audio interface when you need low-latency routing. Windows Classic Wave or Microsoft Sound Mapper can work for simpler devices. Choose the stable path that exposes the correct input and passes a clean test recording. ### Why does Sound Forge show no microphone signal? Check Windows microphone and desktop-app permissions, hardware input and gain, Audio Device Type, Preferences → Audio → Record routing, the data window’s channel count, sample-rate agreement and the armed Record Options meters. ### What are the current recording modes in Sound Forge Pro 2026? The Mode choices are Normal, Create regions and Create new windows. Method is separate: Manual, Automatic: Threshold, Automatic: MIDI Timecode and Automatic: Time. “Automatic retake” and “Multiple takes” are not the current Mode labels. ### Does monitoring through the Plug-In Chain record the effects? No. Current Sound Forge help states that Monitor input through Plug-In Chain affects monitoring only; the chain is not applied to the recorded data. This lets you hear a comfort chain while preserving a dry take. ### Can Sound Forge Pro record several inputs at once? Yes, when the audio device exposes multiple inputs and they are enabled and mapped to a data window with enough channels. The result is a multichannel audio file, not a multitrack timeline session. ### What does the prerecord buffer do? With Prerecord buffer enabled in the Manual recording Settings, Arm starts buffering the specified duration. Starting Record commits that audio to disk. After recording, use the Event Tool to slip or trim the event’s left edge to reveal the buffered opening. After the take passes playback, continue with the appropriate workflow: [cut and trim the recording](https://soundforgepro.com/how-to-cut-and-trim-audio-in-sound-forge-pro/), choose [peak, RMS, or loudness normalization](https://soundforgepro.com/how-to-normalize-audio-in-sound-forge-pro/) only when delivery requires it, then [export and verify the final MP3](https://soundforgepro.com/how-to-export-mp3-from-sound-forge-pro/) while keeping the lossless master. *Last fact-checked: September 12, 2026\. Instructions checked against the current help; hardware and driver behavior still need a test on your setup.* ### Sound Forge Price 2026: Plans, Plus & Perpetual URL: https://soundforgepro.com/sound-forge-pro-pricing/ Last updated: 2026-10-09T21:06:51.000Z **Sound Forge costs $24.95 month to month, $149.95 per year or $299.95 for a new perpetual license.** Sound Forge Plus costs $33.95 monthly, $199.95 annually or $399.95 perpetual. These are the US list prices Boris FX announced for the 2026 release; tax, currency conversion, reseller discounts and checkout promotions can change the total. If you choose one billing strategy at the start and keep it unchanged, base monthly is cheapest through six months; annual wins from month seven through month 24\. Mixed annual/monthly periods can cost less at intermediate durations. For Plus, annual becomes cheaper one month earlier, at month six. In either tier, perpetual becomes cheaper once continued access would require a third annual payment, as long as the licensed version still does the work and you don't pay for a later upgrade. Plus is worth the higher price only when its four bundled plug-ins replace something you'd otherwise buy. **◆ Price-reference check: September 5, 2026**The amounts below come from the [March 2026 Boris FX launch announcement](https://blog.borisfx.com/press/boris-fx-acquires-vegas-pro-sound-forge-and-acid-pro). The [current plan comparison](https://www.soundforge.com/sound-forge/pricing/) confirms the editions and feature split, but this check did not retrieve a live checkout quote. Use the announced prices to compare billing routes, then confirm the total in your region before paying. ## Sound Forge prices at a glance | License | Sound Forge | Sound Forge Plus | Best fit | | --------------------- | ------------ | ---------------- | ------------------------------------ | | Monthly subscription | $24.95/month | $33.95/month | Base: 1–6 months; Plus: 1–5 | | Annual subscription | $149.95/year | $199.95/year | Base: 7–24 months; Plus: 6–24 | | Upgrade & Support | $189.95 | $249.95 | Eligible MAGIX-version owners | | New perpetual license | $299.95 | $399.95 | Keeping one version beyond two years | The Upgrade & Support prices aren't cheaper new licenses for anyone who reaches the store. Boris FX announced them for owners of any previous MAGIX Sound Forge version, with that simplified legacy offer available through **December 5, 2026**. New buyers should compare the three ordinary purchase routes: monthly, annual and perpetual. Boris FX now markets the current professional Windows editor as **Sound Forge 2026**. Searchers and long-time users still call it Sound Forge Pro. This page uses both names for the current professional product; the old consumer line has its own [Sound Forge Audio Studio comparison](https://soundforgepro.com/sound-forge-audio-studio-vs-sound-forge-2026/). ## Monthly vs annual vs perpetual: the break-even math Six base-plan monthly payments add up to **$149.70**, which is still 25 cents under the $149.95 annual plan. The seventh monthly payment takes the total to **$174.65**. So for a job you know will run one to six months, paying monthly on the base plan costs less than buying a full year up front. If the job runs longer, count the payments you've already made as sunk costs when you compare. Don't assume switching will refund or credit them; confirm any adjustment with the vendor. Plus crosses the line sooner: five monthly payments total **$169.75**, while six cost **$203.70**. Because the Plus annual plan is $199.95, monthly is cheaper only through month five. On the base edition, twelve monthly payments cost **$299.40**, nearly twice the annual price and only 55 cents short of a perpetual license. On Plus, twelve monthly payments cost **$407.40**, already $7.45 more than the $399.95 perpetual license. Monthly is the dearer way to keep a full year of access. Pick it for flexibility or a smaller first payment; it won't give you the lowest annual total. At 24 months, two base annual payments total **$299.90**, five cents less than the $299.95 perpetual price. Two Plus annual payments total **$399.90**, also five cents below its $399.95 perpetual price. If you stop after two years, annual technically wins in either tier. A third year raises the totals to $449.85 base or $599.85 Plus while the perpetual buyer can keep using the licensed version without another access payment. ![24-month Sound Forge cost comparison: monthly plan $598.80, annual plan $299.90, perpetual license $299.95](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/10/pricing-ui-24-month-cost-v1-v20261006.webp) Sound Forge pricing math: at 24 months the annual plan and the perpetual license cost almost the same — ownership only matters after that. | Base plan total | Monthly | Annual | Perpetual | | --------------- | ------- | ------- | --------- | | 6 months | $149.70 | $149.95 | $299.95 | | 12 months | $299.40 | $149.95 | $299.95 | | 24 months | $598.80 | $299.90 | $299.95 | | 36 months | $898.20 | $449.85 | $299.95 | The table compares the same billing strategy from day one, using announced US launch list prices before tax and leaving out discounts or later paid upgrades. It doesn't optimize mixed periods: one base annual period plus one monthly period, for example, comes to $174.90 for 13 months, against $299.90 for two full annual periods. Confirm switching and renewal terms before you rely on that combination. Perpetual means the version you bought stays licensed; it doesn't buy you every future major release. A subscription keeps you on an active plan, while a perpetual buyer decides separately whether a later version is worth paying for. ## What perpetual and Upgrade & Support mean Boris FX's [general Upgrade & Support policy](https://support.borisfx.com/hc/en-us/articles/10334870429709-What-is-the-Upgrade-Support-Plan-What-is-U-S) says a perpetual purchase includes a complimentary 12-month support contract. Upgrades released during that active term are included. When the term ends, the perpetual application continues to function, but access to newer releases and support can require renewal, reinstatement or another purchase. **Check the renewal setting after purchase:** Boris FX says Upgrade & Support renews automatically unless you cancel it in your account. The company says it sends notice 30 days before expiry and processes renewal at least 24 hours before the contract ends. A lapsed contract can incur reinstatement pricing; after more than 36 months, the policy says it is canceled and a new license or subscription is required to access the latest release. That distinction matters to the break-even calculation. The $299.95 perpetual license is cheaper than paying a third annual subscription only if the current licensed version remains sufficient. A future Windows change, driver problem or must-have feature can make a later upgrade worthwhile, but that is a new decision rather than a hidden requirement to keep the purchased build running. The separate $189.95 base and $249.95 Plus Upgrade & Support entries apply to the announced legacy-owner path. If the Boris FX webshop doesn't show an eligible upgrade for your previous MAGIX license, check eligibility with Boris FX sales or support before counting on that number. If [Sound Forge Pro 18](https://soundforgepro.com/sound-forge-pro-18/) is stable on your workstation, compare the actual workflow changes before upgrading. The [Sound Forge 2026 vs Pro 18 guide](https://soundforgepro.com/sound-forge-2026-vs-pro-18/) keeps that version decision separate from this plan comparison. ## Sound Forge vs Sound Forge Plus Plus doesn't swap the editor for a different application. Both editions include the current core waveform-editing, metering, VST2/VST3/ARA, repair, broadband-noise-reduction, batch-processing and event-based editing tools listed in the official feature table. Sound Forge Plus adds four named tools: - **Melodyne 5 Essential** for basic note-level pitch and time correction. - **Vandal** for amplifier, cabinet and microphone emulation. - **VariVerb II** for algorithmic reverb. - **3D Reverb** for spatial and multichannel room effects. ![The base Sound Forge edition compared with Sound Forge Plus and its four bundled plug-ins](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/10/sound-forge-vs-plus-windows-ui-20260802-v20261006.webp) Both Sound Forge editions share the same core editor; Plus adds Melodyne 5 Essential, Vandal, VariVerb II and 3D Reverb. The Plus premium is about one-third across the ordinary monthly, annual and perpetual routes. For spoken-word cleanup, vinyl transfer, mastering, format conversion and routine restoration, the base edition contains the relevant core workflow. Plus makes financial sense when at least one bundled plug-in replaces a purchase you already planned. If Melodyne is the only extra you care about, compare the included Essential edition with Celemony's current standalone editions first. The dedicated [Sound Forge vs Sound Forge Plus comparison](https://soundforgepro.com/sound-forge-vs-sound-forge-plus/) goes deeper into the four add-ons, so this pricing page can stay about money. ## Which Sound Forge license should you buy? ### Buy monthly for a short, fixed job A restoration backlog, audiobook cleanup contract or temporary Windows workstation can justify paying month to month. Monthly also limits commitment while you confirm hardware and plug-in compatibility. Set the project end date before paying: the base plan stays cheaper through six months, but Plus only through five. ### Buy annual for a known longer project For a project whose duration is known before purchase, annual costs less than the same number of monthly payments from month seven for the base edition and month six for Plus. If you have already paid monthly, compare the remaining access you need without assuming a credit for earlier payments. After two annual payments, either tier is still five cents cheaper than its perpetual license. Annual suits buyers who want current releases without the larger upfront payment, or who expect their workstation and workflow to change within two years. ### Buy perpetual for a stable long-term workstation Perpetual is easiest to defend when the current build already works with your Windows version, audio interface and required plug-ins. Keep the installer, account access and a known-good system backup. The license protects continued use of that version; it can't guarantee compatibility with every future Windows, driver or plug-in release. ### Buy Plus for the add-ons, not the label The base application already contains the editing and restoration core. Pay the Plus premium when Melodyne 5 Essential, Vandal, VariVerb II or 3D Reverb has a defined place in your work. “Plus” on its own isn't a reason to spend another $100 on the perpetual option. ## Run the 15-day trial before paying The [official Sound Forge trial](https://vfx.borisfx.com/sound-forge-trial) lasts 15 days, needs no credit card and runs on Windows through Boris FX Hub. Use it to test the exact interface, driver, plug-ins, file lengths and export formats that matter to your purchase. 1. Record through the audio interface and driver you intend to keep. 2. Open one long or multichannel file that represents your workload. 3. Scan and load the VST2/VST3 plug-ins your process depends on. 4. Complete one edit, repair, mastering or [batch-processing job](https://soundforgepro.com/how-to-batch-process-files-sound-forge-pro/). 5. Export the required WAV, FLAC or MP3 delivery and verify it in another application. If the workflow fails, a cheaper plan won't rescue the purchase. The [Sound Forge trial guide](https://soundforgepro.com/sound-forge-pro-free-trial-whats-included-and-how-long-it-lasts/) covers activation, limits and the checks to finish before the 15 days end. ## How the price compares with alternatives Price comparisons are useful only when the jobs overlap. Adobe currently lists [Adobe Audition at US$22.99 per month](https://www.adobe.com/products/audition.html) on an annual, billed-monthly plan. Audition includes waveform, spectral and multitrack environments. Sound Forge is intentionally a specialist editor rather than a multitrack DAW, so its lower annual total doesn't make it a substitute for a layered production session. Audacity is free and covers many basic recording and editing jobs; it's the right baseline for occasional work. Sound Forge has to earn its price through its focused file-editing workflow, metering, batch tools, repair options and perpetual route. The [Sound Forge vs Audacity comparison](https://soundforgepro.com/sound-forge-pro-vs-audacity/) maps those differences to real tasks. iZotope RX is the specialist comparison for difficult dialogue repair and spectral restoration. Sound Forge covers the broader record, edit, process and deliver path. Use the [Sound Forge versus iZotope RX comparison](https://soundforgepro.com/sound-forge-pro-vs-izotope-rx/) to decide whether that narrower focus matches your work before price becomes the deciding factor. ## Frequently asked questions ### How much does Sound Forge cost in 2026? Sound Forge costs $24.95 month to month, $149.95 annually or $299.95 for a new perpetual license. Sound Forge Plus costs $33.95 monthly, $199.95 annually or $399.95 perpetual. Eligible owners of an earlier MAGIX Sound Forge version have a separate $189.95 base or $249.95 Plus Upgrade & Support path through December 5, 2026\. These are the US launch list prices announced by Boris FX, before tax; verify the current checkout for your region and offer. ### Can I still buy Sound Forge as a perpetual license? Yes. Boris FX sells new perpetual licenses for Sound Forge and Sound Forge Plus. The licensed version continues to function after the included 12-month Upgrade & Support term, but the support plan is set to auto-renew unless you cancel it in your Boris FX account. ### Is the Sound Forge subscription or perpetual license cheaper? For the base edition, monthly is cheapest for one to six months; for Plus, one to five. That comparison assumes one fixed strategy from the start: annual is cheapest after those points through month 24\. Mixed annual and monthly periods can change the result for intermediate durations. Two annual payments are five cents below the perpetual price in either tier; perpetual becomes cheaper when a third annual payment would be required, provided you keep the licensed version and do not pay for a later upgrade. ### What does Sound Forge Plus add? Sound Forge Plus adds Melodyne 5 Essential, Vandal, VariVerb II and 3D Reverb. The core editor, repair, metering and batch features are shared with the base edition. ### Who qualifies for the Sound Forge upgrade price? Boris FX announced that owners of any previous MAGIX Sound Forge version could use the simplified Upgrade & Support price through December 5, 2026\. It is an eligibility-dependent upgrade offer, not a discounted new license for every buyer. ### Does a perpetual license include every future Sound Forge version? No. Boris FX's general perpetual-license policy includes 12 months of Upgrade & Support. The purchased version keeps working after that term, but later current releases can require a renewal, reinstatement or another purchase. ### Is there a free Sound Forge trial? Yes. The current Windows trial lasts 15 days, provides full access and does not require a credit card. *Launch-price references, plan features and published licensing terms rechecked September 5, 2026\. This is not a live checkout-price guarantee; confirm tax, region and temporary promotions with the vendor before purchasing.* ### Sound Forge Free Trial 2026: 15 Days, No Card URL: https://soundforgepro.com/sound-forge-pro-free-trial-whats-included-and-how-long-it-lasts/ Last updated: 2026-10-09T11:08:16.000Z The current Sound Forge free trial lasts 15 days, needs no credit card and runs on Windows. Boris FX calls it full-featured and unrestricted. The official trial page doesn't identify a Plus trial or promise the four Plus-only plug-ins, though, so check the exact Hub offer before starting if those extras affect your decision. **◆ Fact-checked September 12, 2026**The [official Boris FX trial page](https://vfx.borisfx.com/sound-forge-trial) currently promises 15 days, no card, unrestricted core access and a Windows-only Boris FX Hub installation path. *This guide is part of the [Sound Forge Pro Start Here hub](https://soundforgepro.com/tag/start-here/). Use it if you need the full order: trial, install, system requirements, review, pricing and legacy Pro 18 decisions.* Don't activate it in a quiet week and hope some use turns up later. Get two real files ready, along with your audio-interface driver, the plug-ins you rely on and one finished delivery target. A focused test can tell you whether the editor fits your main job, though it can't vouch for long-term reliability or every plug-in combination. --- ![Sound Forge trial setup: download Hub, request the trial, install and activate](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/10/sound-forge-trial-official-flow-20260802-v20261006.webp) Download Boris FX Hub, request the trial, install, then choose Start Free Trial. Follow the written steps below for current instructions. ## How Long Is the Sound Forge Pro Trial? The current [Boris FX Sound Forge trial](https://vfx.borisfx.com/sound-forge-trial) runs for 15 days, and it's the authoritative download route for the 2026 product. Search results still surface legacy Sony and MAGIX downloads, so avoid third-party installers whose version, license path or trial terms may no longer match the current release. Activate when your test files and hardware are ready. In the published setup sequence, installation comes before the Start Free Trial button. Boris FX doesn't explain how earlier trials or account history affect eligibility, and it doesn't advertise any pause or reset. --- ## What Is Included in the Sound Forge Trial? The dedicated trial page calls Sound Forge full-featured and says it launches in unrestricted trial mode. The current product table lists the core application and Sound Forge Plus as separate offers, while the trial page names only Sound Forge. So you can count on unrestricted core access, but not necessarily on the Plus-only plug-ins turning up in the trial. The current [Sound Forge feature table](https://www.soundforge.com/sound-forge/pricing/) documents these core areas. Treat the list as a test plan rather than an excuse to click through menus at random: - sample-level waveform editing, cut, copy and paste - precise peak and loudness metering - coreFX, essentialFX and dynamic EQ processing - VST2, VST3 and ARA plug-in support - click and crackle removal plus clipping repair - broadband noise reduction - recording and editing up to 32 channels - prerecord and automatic recording start - batch processing - event-based, nondestructive editing - local Text to Speech Sound Forge Plus currently adds Melodyne 5 Essential, Vandal, VariVerb II and 3D Reverb. The public trial pages do not promise those extras with the core Sound Forge trial. If one of them determines your purchase, confirm the products shown in Boris FX Hub or ask Boris FX support before activation. --- ## How to Download and Start the Trial The current route uses Boris FX Hub rather than a standalone Sound Forge installer. Follow the five steps published on the official trial page: 1. Open the [official Sound Forge trial page](https://vfx.borisfx.com/sound-forge-trial), submit its form and download Boris FX Hub. 2. Sign in to your Boris FX account or create a free account. Boris FX confirms in its [account-access guidance](https://support.borisfx.com/hc/en-us/articles/44650652839181-Do-I-need-to-create-a-Boris-FX-account) that an account is required for its Sound Forge releases. 3. In Boris FX Hub, select the option to request the Sound Forge trial when installation finishes, then proceed to install. This is the request step; you activate the trial separately below. 4. Install Sound Forge through the Hub. 5. Choose Start Free Trial. On the success page, choose Back to App; Sound Forge then launches in unrestricted trial mode. Boris FX says you don't need a credit card to start. If the Hub stalls, the product is missing or the trial control never appears, follow the [current Boris FX Hub installation guide](https://soundforgepro.com/how-to-install-sound-forge-pro/) instead of downloading an old executable from a software directory. --- ## System Requirements Before You Start The current [Sound Forge system requirements](https://www.soundforge.com/sound-forge/system-requirements/) list Windows 11; Windows 10, macOS and Linux are absent from the current page for this release. Check the full [practical requirements guide](https://soundforgepro.com/sound-forge-pro-system-requirements/) before spending trial days on an unsupported or marginal setup. Passing the published minimum doesn't prove your interface, ASIO driver, VST plug-ins or largest source files will behave well. During the trial, record through the interface you actually use, scan the plug-ins your workflow needs, open a representative long file and complete at least one export. --- ## Is 15 Days Enough to Evaluate Sound Forge? Often it is, for one defined workflow. Pick one easy job and one that usually eats your time, and book enough sessions to finish and check both. Complex archives or a large plug-in setup may need a longer evaluation agreed with support, and nobody promises an extension. For voice, podcast or mastering work, use one clean file and one file that normally gives you trouble. Test selection accuracy, the effects you depend on, metering, preview, undo and the final export, then reopen each export in another player or editor. A finished job tells you more than an hour of menu browsing. Restoration and archival work needs copies of real transfers. Try click and crackle repair on several passages, then run a small batch with mixed lengths and formats; listen for damaged transients, look over output names and metadata, and time the whole workflow. Write down the exact Sound Forge build, Windows version, interface driver and critical plug-in versions that passed. The useful result isn't “Sound Forge opened.” It's “this build completed my normal job and produced a file I verified.” --- ## What Happens When the Trial Ends? Boris FX says you have to buy or subscribe to keep using the application after the 15-day period. Its public pages don't describe a grace period, a read-only mode, an export-only fallback or what happens to an open session at expiry, so don't plan a deadline around behavior nobody has documented. Before the trial ends, keep untouched source copies, save the working files you need and export finished deliverables to a standard format such as WAV, FLAC or MP3\. Reopen those exports in another application and check duration, channels, sample rate, peaks and metadata. Do it while you still have the editor, not on the day a delivery is due. Buy only after the workflow passes. The maintained [Sound Forge pricing guide](https://soundforgepro.com/sound-forge-pro-pricing/) compares current subscription, perpetual and Plus choices. Compare the full cost and any ongoing payment commitment before buying. For the broader value decision, use the [2026 Sound Forge review](https://soundforgepro.com/sound-forge-pro-review-2026/). --- ## Sound Forge Trial vs Adobe Audition Trial Adobe's [current Audition trial page](https://www.adobe.com/products/audition/free-trial-download.html) offers the full app for seven days. Adobe says billing begins after the trial and gives a further 14-day full-refund window. Checkout terms and prices vary by region, so read the terms shown for your account before starting. For the Sound Forge evaluation, Boris FX asks for no credit card. You still need to choose and pay for a license if you want to keep using the application after the trial. That makes Sound Forge simpler to sample and gives you eight more trial days. It doesn't make either product the better editor for every job, though. This section compares trial mechanics only; the [Sound Forge vs Adobe Audition comparison](https://soundforgepro.com/sound-forge-pro-vs-adobe-audition/) covers multitrack workflow, restoration depth and long-term cost. --- ## What the Trial Cannot Prove Two weeks can't prove months of stability after Windows, driver or plug-in updates, so save the configuration that passed and repeat a short compatibility test after any major change. The current Sound Forge and Sound Forge Plus feature table doesn't list CrumplePop or iZotope RX as included components. If either matters to your cleanup work, evaluate its features and license separately instead of counting it as part of this trial. Sound Forge is a specialist waveform editor, not a multitrack DAW. It can record and edit multichannel files, but Boris FX says plainly that it isn't designed for multitrack project recording. Use the trial to decide whether its single-file editing, repair, batch and delivery workflow earns a spot next to your DAW. --- ## Frequently Asked Questions ### Is the Sound Forge Pro trial really free? Yes. Boris FX offers a 15-day evaluation without a credit card. You need a free Boris FX account, and you must purchase or subscribe if you want to continue using the application afterward. ### How many days is the Sound Forge Pro free trial? The current Boris FX trial lasts 15 days. Check the official trial page before downloading because the offer can change independently of this guide. ### Does the Sound Forge Pro trial have any limitations? Boris FX describes Sound Forge as full-featured and unrestricted during the 15-day period. The trial page does not identify a Plus trial or promise Plus-only plug-ins, so verify the exact Hub offer if those extras matter to your test. ### Can I extend the Sound Forge Pro trial? The official trial page does not advertise an extension, pause or reset. If installation or activation failed and consumed evaluation time, contact Boris FX support rather than assuming a reinstall will restart the clock. ### Does the trial work on Mac? No. The current Sound Forge trial is Windows-only, and the current system-requirements page lists Windows 11\. It does not document a current macOS edition. ### What happens to my files after the trial ends? Boris FX publicly documents that purchase or subscription is required to continue using the application, but it does not describe post-expiry session or project behavior. Before expiry, keep source copies, save what you need, export standard-format deliverables and verify those exports in another application. ### Is Sound Forge Plus included in the same trial? Do not assume so. The trial page names Sound Forge but does not identify a Plus trial. Sound Forge Plus currently adds Melodyne 5 Essential, Vandal, VariVerb II and 3D Reverb, so confirm the exact Hub offer or ask support before activation if those extras are central to your test. Start with the [current Boris FX Hub installation workflow](https://soundforgepro.com/how-to-install-sound-forge-pro/), verify the machine against the [practical system requirements](https://soundforgepro.com/sound-forge-pro-system-requirements/), and open the [price and plan comparison](https://soundforgepro.com/sound-forge-pro-pricing/) only after the software completes your test. ### Sound Forge 2026 System Requirements: PC Specs URL: https://soundforgepro.com/sound-forge-pro-system-requirements/ Last updated: 2026-10-09T11:08:27.000Z Sound Forge 2026 has a short official requirements list: Windows 11, a 1.4 GHz processor, onboard graphics, 2 GB RAM, and 1.1–1.4 GB for the application. Read that 2 GB line carefully: Microsoft lists at least 4 GB as the [Windows 11 memory minimum](https://www.microsoft.com/en-us/windows/windows-11-specifications). This guide separates the Boris FX application specification, the Windows baseline and practical audio-workstation advice. **◆ Fact-checked September 12, 2026**Sound Forge is now sold by **Boris FX** as Sound Forge 2026\. The vendor specification below is separated from Microsoft Windows 11 requirements and from this site's practical buying advice. This page is part of our [Sound Forge Pro 2026 Guide](https://soundforgepro.com/). *This guide is part of the [Sound Forge Pro Start Here hub](https://soundforgepro.com/tag/start-here/). Use it if you need the full order: trial, install, system requirements, review, pricing and legacy Pro 18 decisions.* Before you start the [official 15-day trial](https://vfx.borisfx.com/sound-forge-trial), gather your interface driver, the plug-ins you rely on and one representative audio file. Then [install Sound Forge through Boris FX Hub](https://soundforgepro.com/how-to-install-sound-forge-pro/) and check that whole setup works. An installer that finishes cleanly is only the first step. --- ## Sound Forge Pro System Requirements — Full Specs These are the [official minimum requirements from Boris FX](https://www.soundforge.com/sound-forge/system-requirements/) rechecked on September 12, 2026: __**Published minimum vs. editorial guidance (checked September 12, 2026)**__ | Component | Boris FX minimum | Editorial guidance | | ---------------- | ------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Operating system | Windows 11 | Use a fully updated Windows 11 installation supported by your interface and plug-ins. | | Processor | 1.4 GHz; multicore or multiprocessor recommended | Prefer a current multicore CPU and test your real effects chain. | | Graphics | Onboard; 1024 × 768 minimum resolution | No dedicated GPU is required by the published spec. | | RAM | 2 GB; 8 GB recommended | Windows 11 itself requires at least 4 GB. Use the vendor-recommended 8 GB as the practical baseline; consider 16 GB for long files, multiple applications, or heavy plug-ins. | | Program storage | 1,100 MB Sound Forge; 1,400 MB Sound Forge Plus | Reserve separate space for source audio, working copies, exports, and backups. | | Audio device | Not specified on the requirements page | For recording, prefer an interface with a current native Windows 11 ASIO driver. | Values labeled “Boris FX minimum” are the vendor specification. “Editorial guidance” contains our buying advice, not additional official requirements. --- ## Windows 11 Is the Only OS Boris FX Lists The current Boris FX requirements page lists Windows 11; it doesn't list Windows 10, macOS, or Linux. That makes Windows 11 the documented baseline for Sound Forge 2026, even if an installer happens to launch somewhere else. I wouldn't buy the current version for a Windows 10 workstation and hope undocumented compatibility holds. Boris FX makes no support promise for that configuration. Run the trial on the exact machine, interface, drivers and plug-ins you plan to keep using. For an older workstation, check the requirements of the exact Sound Forge version you already own, since the 2026 specification doesn't cover earlier releases. Whether your Windows version still gets security updates is a separate question from application compatibility. --- ## What the RAM Requirement Actually Means Boris FX lists 2 GB minimum and 8 GB recommended for Sound Forge. Microsoft separately lists 4 GB or more as the [Windows 11 memory minimum](https://www.microsoft.com/en-us/windows/windows-11-specifications), the only operating system Boris FX lists. That makes the 2 GB figure an application-spec line rather than a viable whole-PC buying target. For a current Windows 11 machine, 4 GB is the OS floor and 8 GB is the Sound Forge vendor recommendation. [Calculate the size of your source audio](https://soundforgepro.com/audio-file-size-calculator/) before you choose storage. Uncompressed 24-bit/96 kHz stereo PCM takes 34.56 MB per minute in decimal units, or about 1.38 GB for 40 minutes, excluding file headers and metadata. That's disk space. It says nothing about RAM use, and the application, plug-ins and other open programs need memory too. **My recommendation: start at the official 8 GB recommendation for ordinary editing.** Choose 16 GB when you regularly keep several applications open, use memory-heavy third-party plug-ins, or handle long high-resolution files. That 16 GB figure is editorial headroom; it isn't a Boris FX requirement or a measured Sound Forge threshold. --- ## Processor: Minimum Spec vs. Your Actual Workload The published CPU minimum is 1.4 GHz, with multicore or multiprocessor recommended. Boris FX doesn't name a processor generation, core count, benchmark score, or a separate CPU target for restoration and batch work. For a useful trial test, open a copy of a file you normally edit, add your usual effects and play the section that puts the most demand on the chain. If you use batch processing, time a small representative batch as well. Record the settings so that you can compare another PC fairly. I'd put a current multicore CPU ahead of clock speed alone. The 1.4 GHz figure is a compatibility minimum rather than a performance rating, and meeting it tells you nothing about how quickly your particular files and plug-ins will process. --- ## Storage: Install Size vs Working Space The 1,100 MB figure for Sound Forge and 1,400 MB figure for Sound Forge Plus cover program installation. They don't cover source audio, working copies, renders, undo data, or backups. A 24-bit/192 kHz stereo PCM file is about 69.1 MB per minute, or roughly 4.15 GB per hour in decimal units, with both stereo channels already counted. Then add working copies, undo data, renders, source downloads and backups. The listed 1,100/1,400 MB covers program installation; a usable project drive needs far more. For the active working drive I'd recommend an SSD, though that's my advice and not a Boris FX minimum. Budget for backups separately, because a faster drive is no substitute for a second copy of your recordings. ![Storage split between the Sound Forge install, source audio, working copies, exports and backups](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/10/sound-forge-storage-workflow-20260802-v20261006.webp) The 1,100/1,400 MB Sound Forge requirement covers the install only — source files, working copies, exports and backups need their own space. --- ## Sound Card and ASIO: What You Actually Need The current system-requirements page doesn't publish a sound-card minimum. The current [Sound Forge 2026 Audio Preferences help](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/audio%5Fpreferences.htm) does document ASIO, Windows Classic Wave, and Microsoft Sound Mapper device types, and that's the right source for audio-device compatibility claims. Sound Forge describes ASIO as the low-latency option, but that doesn't guarantee single-digit latency. Round-trip performance depends on the interface, its native driver, [buffer size](https://soundforgepro.com/audio-latency-calculator/), sample rate, USB or PCIe path, plug-in chain, and the rest of the PC. For recording or input monitoring, check that the interface manufacturer provides a driver for your Windows 11 setup. Try its native ASIO driver if available and check for dropouts at the buffer size you intend to use. For edit-only work, test Sound Mapper or Classic Wave before assuming you need to buy a new interface. ![Audio Preferences in Sound Forge with ASIO and Windows driver options listed](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/10/system-requirements-ui-audio-driver-v2-v20261006.webp) Sound Forge supports ASIO, Windows Classic Wave and Microsoft Sound Mapper — test the chosen driver on the exact Windows 11 machine. --- ## Supported Audio Formats Start with the formats you actually exchange. For less common formats, consult the vendor table and test a sample through editing and export before committing a project. The official format table has two limitations worth knowing: its import row omits WAV, and its export row includes an unexplained “VC” entry. Neither is a reason to infer a restriction or guess a codec. Use the application help and an actual sample file to resolve your case. AIFF, OGG, RAW, PCA and W64 are among the other audio formats Boris FX lists. An extension on its own doesn't guarantee support for every bit depth, channel layout or metadata field. For video work, the vendor lists MPEG-1/2, MOV and MXF among the supported import and export formats. Check the exact codec inside the file; the extension alone won't tell you. If a delivery format is mandatory, export a short test and reopen it in the receiving application. Confirm the channel count, duration and any metadata you need to preserve. DSF appears in both published audio lists, but the table alone doesn't document every processing or conversion step. If DSD is central to your workflow, test one representative DSF file from import through final delivery rather than inferring a fully native path from the extension list. For ordinary editing, WAV, FLAC and MP3 are the useful starting formats. The [current Open-file help explicitly documents WAV](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/opening%5Fa%5Ffile.htm); FLAC and MP3 appear in both import and export rows of the vendor specification. For each, test the required bit depth, sample rate, channel layout and metadata through a complete open–edit–export cycle. The [audio conversion guide](https://soundforgepro.com/how-to-convert-audio-files-sound-forge-pro/) covers that delivery workflow. --- ## Does Sound Forge Pro Run on Mac? The current Sound Forge 2026 requirements list Windows 11 and no macOS version. Don't buy it for a Mac on the assumption that Apple silicon, Rosetta, or a compatibility layer is supported. Use a documented Windows 11 environment, or compare current [Sound Forge alternatives for Mac](https://soundforgepro.com/sound-forge-for-mac/). --- ## Can My Machine Run It? Quick Reference Check the processor and installed RAM in Windows Settings → System → About, then compare the table above with Microsoft’s Windows 11 requirements. Meeting the operating-system requirements doesn't confirm that Sound Forge supports every processor architecture, interface driver or third-party plug-in, so for an unusual setup get compatibility confirmed before you buy. For ordinary single-file editing: go with the official 8 GB RAM recommendation and a current multicore CPU. Run the trial on one real project before purchase; “meets the spec” is not the same as “runs every plug-in chain smoothly.” For long files or batch work: 16 GB RAM and an SSD are sensible editorial upgrades rather than official minimums. Benchmark your own chain, because codec, plug-ins, file count, and storage can all move the bottleneck. For recording with software monitoring: use an interface with a maintained native Windows 11 ASIO driver and choose the lowest buffer that stays stable on your system. There's no universal under-10-ms requirement in the Sound Forge specification. --- ## Frequently Asked Questions ### Does Sound Forge Pro support Windows 10? Boris FX lists Windows 11 as the minimum operating system for Sound Forge 2026\. The requirements page does not document Windows 10 as supported, so treat Windows 11 as the purchase and support baseline. ### How much RAM does Sound Forge Pro need? Boris FX lists 2 GB minimum and 8 GB recommended for Sound Forge, while Microsoft requires at least 4 GB for Windows 11 itself. Use 8 GB as the practical baseline and consider 16 GB when large files, several plug-ins or other applications stay open. The 16 GB figure is editorial headroom, not an official requirement. ### Does Sound Forge Pro work with any audio interface? Sound Forge 2026 can use ASIO, Windows Classic Wave, or Microsoft Sound Mapper devices. ASIO is the documented low-latency choice for recording and monitoring; the result still depends on the interface, driver, buffer, sample rate, and PC. ### What audio formats does Sound Forge Pro support? Sound Forge documents opening WAV, and the current vendor lists include FLAC, MP3, OGG, DSF, RAW, SFA, PCA and W64\. The displayed import table omits WAV and has other ambiguities, so use the current help and test the exact import/export combination rather than treating that table as exhaustive. ### Does Sound Forge Pro need a dedicated graphics card? No dedicated GPU is listed as a minimum. Boris FX specifies onboard graphics with a minimum 1024 × 768 resolution. That is the published compatibility floor, not a promise about every display, plug-in, or high-DPI setup. ### How long is the Sound Forge Pro free trial? Boris FX currently offers a full-featured 15-day trial with no credit card required, and the [official trial page](https://vfx.borisfx.com/sound-forge-trial) labels it Windows-only. Use the [trial guide](https://soundforgepro.com/sound-forge-pro-free-trial-whats-included-and-how-long-it-lasts/) to plan a compatibility test, then recheck the official offer before downloading because trial terms can change independently of hardware requirements. ### Do Sound Forge and Sound Forge Plus use the same minimum requirements? Boris FX publishes one minimum-requirements block for both editions. The listed program-installation space is 1,100 MB for Sound Forge and 1,400 MB for Sound Forge Plus; your audio files and backups need additional space. ### Download & Install Sound Forge 2026 via Boris FX URL: https://soundforgepro.com/how-to-install-sound-forge-pro/ Last updated: 2026-10-09T21:08:08.000Z To install Sound Forge 2026, download Boris FX Hub, sign in and choose either the trial or purchased-license route below. Sony and MAGIX installers belong to earlier releases; their serial-number instructions do not apply to current Boris FX login licensing. **◆ Fact-checked September 12, 2026**Current Sound Forge 2026 installation, trial and login licensing route through Boris FX Hub and a Boris FX account. This walkthrough does not apply to old MAGIX or Sony installers. This page is part of our [Sound Forge Pro 2026 Guide](https://soundforgepro.com/). *This guide is part of the [Sound Forge Pro Start Here hub](https://soundforgepro.com/tag/start-here/). Use it if you need the full order: trial, install, system requirements, review, pricing and legacy Pro 18 decisions.* *Independent walkthrough. The installer and trial are provided by Boris FX.* Allow time for a playback test after installation. Open a known audio file, check the output you actually use and, if you record, test the input too. Download and installation time depends on your connection and PC. --- ![Official Sound Forge 2026 route from the trial page through Boris FX Hub to launch](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/08/install-route-v1.webp) Use Boris FX's trial page and Hub, then sign in, install, launch and verify one file. ## System Requirements: Check These Before Downloading According to the [official Sound Forge system requirements page](https://www.soundforge.com/sound-forge/system-requirements/), the minimum specs are: - **Operating system:** Windows 11 - **Processor:** 1.4 GHz; multicore or multiprocessor recommended - **Graphics:** onboard, 1024 × 768 minimum resolution - **RAM:** 2 GB listed; 8 GB recommended. Windows 11 itself requires [at least 4 GB of RAM](https://www.microsoft.com/en-us/windows/windows-11-specifications). - **Program storage:** 1,100 MB for Sound Forge or 1,400 MB for Sound Forge Plus, plus working space for audio and backups The vendor requirements page does not publish an audio-device or internet line. In practice, the Hub and initial login licensing need connectivity, and recording needs a compatible Windows device or interface. Keep those workflow needs separate from the official minimum block. Windows 10 isn't listed on the current Boris FX requirements page, and an installer launching there isn't proof of supported operation. For a current purchase, treat Windows 11 as the baseline and test the exact interface, drivers and plug-ins during the trial. The current Sound Forge release and its trial are Windows-only. Boris FX doesn't list a current macOS installer, Rosetta workflow or Apple-silicon support, so Mac users need a different editor or a documented Windows 11 machine. --- ## Step 1 — Get the Boris FX Hub For the free trial, open the [official 15-day Sound Forge trial page](https://vfx.borisfx.com/sound-forge-trial) and download Boris FX Hub. If you already bought Sound Forge, sign in to the Boris FX account used for the order and open the Hub. Avoid third-party download pages for the current build. Boris FX Hub is the installer and license manager for the current release. It handles the package download, installation and the handoff to trial or purchased-license activation. Submit the official form, download the Hub installer and run it. Windows may ask for administrator permission. Verify that the download came from Boris FX before allowing it to make changes to the PC. --- ## Step 2 — Create a Boris FX Account (or Sign In) The Hub asks you to sign in when it opens. If you don't have a Boris FX account yet, click **Create Account** and fill in your details. This is where your license is stored, so use an email address you'll actually keep access to. If you already use a Boris FX account for Sapphire, Continuum or Mocha Pro, sign in with that account. Your Sound Forge purchase should appear alongside the other products attached to it. Former MAGIX customers still use a Boris FX account for the 2026 build. Boris FX says the [previous purchase serial must appear in that account](https://support.borisfx.com/hc/en-us/articles/44650911032845-How-do-I-upgrade-from-a-MAGIX-version-to-a-Boris-FX-version) before an upgrade can be purchased. If the old license is missing, stop before checkout and ask support to resolve the account record. Current app activation then uses Boris FX login licensing, not the MAGIX Service Center. --- ## Step 3 — Install Sound Forge Through the Hub For a new trial, first choose "Request an Unrestricted Trial of Sound Forge after installation" in the Hub, as shown in the official trial instructions. Then find Sound Forge and click Install. If your account already holds a paid license, go straight to Install. The Hub downloads and installs the selected Sound Forge package. Leave the Hub open until it reports success; the time varies with the connection, disk, security scanning and the edition or extras selected. After the Hub reports success, launch Sound Forge from the Hub or the Windows Start menu. If installation completed but the app is missing, use the [installation-failed guide](https://soundforgepro.com/sound-forge-installation-failed/) before repeatedly reinstalling unrelated Boris FX products. --- ## Step 4A — Activate the Free Trial (No Purchase Yet) After requesting the trial before installation and letting the installation finish, complete activation below. If the account already holds a paid license, use Step 4B instead: 1. Click **Start Free Trial**. 2. At the success confirmation, click **Back to App**. 3. Sound Forge launches in full trial mode. Boris FX describes the trial as 15 days, full-featured and unrestricted, with no credit card required. The trial page doesn't say the Plus-only Melodyne, Vandal, VariVerb II or 3D Reverb additions are included, so verify any Plus component you need before treating the base trial as a Plus evaluation. Start the trial once your test files, audio interface and critical plug-ins are ready. Boris FX doesn't spell out a pause or extension policy on the trial page, so plan around one 15-day evaluation window. --- ## Step 4B — Activate a Purchased License For a direct Boris FX purchase, [Sound Forge uses login licensing](https://support.borisfx.com/hc/en-us/articles/44687772090253-How-does-licensing-work-for-Vegas-Pro-and-Sound-Forge). Sign in with the Boris FX account tied to the order and choose Use on This Computer. Boris FX explicitly says no activation key is required for this current flow. 1. Launch Sound Forge after installation. 2. Sign in with your Boris FX account when the app asks for a login. 3. Choose Use on This Computer to attach your license to this machine. The first download and login-license activation need internet access, and Boris FX's Sound Forge licensing page doesn't document an offline procedure for the current login flow. If the workstation must stay disconnected, ask support about that exact license before buying; offline key-file instructions for another Boris product or an old Sony release aren't interchangeable. ![Sound Forge 2026 trial activation and purchased-license login paths](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/10/activation-paths-v2-v20261006.webp) Trial users request and start the trial; purchasers sign in and choose Use on This Computer. --- ## Step 5 — Set Up Your Audio Device Installation isn't finished just because the program opens. A wrong playback route can produce silence even while the meters move, and an unstable driver setup can crackle on the first real file. Open [Options → Preferences → Audio](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/audio%5Fpreferences.htm). This Sound Forge page controls the audio-device type, playback routing, recording routing and the application's playback and record buffering. An ASIO interface can also have its own driver control panel for hardware buffer, sample rate and clock. Treat those as two separate layers. Check the route in this order: Playback route: choose the physical output you monitor. Microsoft Sound Mapper follows the Windows default; Windows Classic Wave lets you choose a Windows device; ASIO exposes ports from a compatible interface driver. Play a known stereo file and confirm both the on-screen meters and the actual left/right outputs. Recording route: select the input that carries the microphone or line signal and make a short recording. If the interface vendor supplies a current Windows 11 ASIO driver, test it for low-latency recording. For simple edit-only playback, Sound Mapper or Classic Wave may be adequate if it stays stable on the actual PC. Buffering: if playback gaps, adjust Sound Forge's playback buffer in small steps and retest the same file. If an ASIO interface still crackles or reports a rate/clock error, open the manufacturer's control panel and check its hardware buffer, sample rate and clock. Don't copy one universal buffer value from another device. ![Sound Forge audio routing from device type and ports to the Windows or interface output](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/08/audio-routing-v2.webp) Sound Forge controls routing and app buffering; the interface panel controls hardware buffer, sample rate and clock. --- ## Step 6 — Install VST Plugins (Optional) The [current Sound Forge feature table](https://www.soundforge.com/sound-forge/) documents VST2, VST3 and ARA support. Third-party compatibility still depends on plug-in architecture, authorization and the host features that the vendor supports. Test every critical plug-in during the trial. Open [Options → Preferences → VST Effects](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/vst%5Feffects%5Fpreferences.htm). Confirm the plug-in's installer folder is in the VST search-folder list, click Refresh and enable the effect in the available-plug-ins list. Do not move VST3 files by hand just to match a generic path; use the vendor installer so the plug-in and its authorization components stay together. Open the effect through Plug-In Chainer, load a preset and preview a known file, then render a copy, close it and reopen the result. Appearing in the list only proves that Sound Forge found the plug-in; it doesn't prove the interface, authorization, processing and rendered output are reliable. For a missing or rejected plug-in, check its bitness, VST version, installation folder and license status before reinstalling Sound Forge. The dedicated [VST troubleshooting guide](https://soundforgepro.com/sound-forge-pro-vst-plugins-not-showing/) covers scan-path, cache and plug-in-isolation checks without assuming every legacy effect remains compatible. ![Sound Forge VST plug-in verification from vendor install through render and reopen test](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/08/vst-verification-v2.webp) A plug-in is not verified until it loads, previews, renders and reopens correctly. --- ## Upgrading from Sound Forge Pro 18 (MAGIX Version) If you own Sound Forge Pro 18 or another MAGIX-era version, confirm that the [previous license appears in your Boris FX account](https://support.borisfx.com/hc/en-us/articles/44650911032845-How-do-I-upgrade-from-a-MAGIX-version-to-a-Boris-FX-version) before buying an upgrade. Boris FX [announced the acquisition on March 30, 2026](https://blog.borisfx.com/press/boris-fx-acquires-vegas-pro-sound-forge-and-acid-pro), and that announcement gives December 5, 2026 as the deadline for the stated legacy upgrade offer. The separate support article explains account eligibility, not a promise of an indefinite offer. Recheck the live terms and price before buying or uninstalling your working version. Install the 2026 build through Boris FX Hub as a separate migration step. Before upgrading, export presets where possible, record custom VST paths and keep backups of source audio and application-specific project state. Test copies first; do not assume every old preference, plug-in or project detail transfers unchanged. --- ## Common Install Problems ### The Hub says installed, but Sound Forge does not appear Don’t assume the download was interrupted. Confirm first that the Hub reports a successful install, check the Windows Start menu and the installed-apps list, then restart Windows. If the product is absent or the Hub still shows Install, follow the scoped Hub/setup checks in the installation-failed guide. ### Activation says "serial number not found" A standard 2026 purchase doesn't ask for a serial during app activation; you sign in with the Boris FX account instead. A legacy serial belongs to the account-and-upgrade check rather than the current app login. If the old purchase doesn't appear in your Boris FX account, or the app still asks for a serial, stop and send [Boris FX support](https://support.borisfx.com/hc/en-us) the account email and order details instead of trying unrelated legacy activation screens. ### No sound on first launch Open Options → Preferences and verify the audio device type plus the selected playback device. Play a known file, check Windows output routing and then use the [no-sound guide](https://soundforgepro.com/sound-forge-pro-no-sound/) if meters move but nothing reaches the speakers. ### Crackling or dropout during playback Dropouts can come from app buffering, an ASIO hardware-buffer or sample-rate mismatch, a heavy plug-in chain or competing system load. First increase Sound Forge's playback buffer one step and bypass the chain. If the problem is specific to ASIO, open the interface manufacturer's panel and check its hardware buffer, rate and clock against the file and device. ### VST plugins aren't showing up Open Options → Preferences → VST Effects, verify the search folder and rescan. If the plug-in still fails, check its architecture, VST version, authorization and whether it is supported in Sound Forge. Use the [VST troubleshooting guide](https://soundforgepro.com/sound-forge-pro-vst-plugins-not-showing/) for cache and isolation steps. --- ## Frequently Asked Questions ### Is Sound Forge Pro free to try? Yes. Boris FX offers a 15-day, full-featured Sound Forge trial with no credit card. Start at the official Sound Forge trial page and install through Boris FX Hub; avoid third-party installers that advertise old versions or different trial terms. ### Does Sound Forge Pro work on Windows 10? Boris FX lists Windows 11 as the minimum operating system for Sound Forge 2026 and does not list Windows 10\. Treat Windows 11 as the supported purchase baseline even if the installer happens to launch on an older system. ### Can I install Sound Forge Pro on more than one computer? Yes. Boris FX says a login license can be used on [up to two computers](https://support.borisfx.com/hc/en-us/articles/44746837385485-Can-I-use-my-login-license-on-more-than-one-computer), such as a desktop and laptop, by one user. It is not intended for simultaneous use on both machines. On each computer, sign in and [choose Use on This Computer](https://support.borisfx.com/hc/en-us/articles/44687772090253-How-does-licensing-work-for-Vegas-Pro-and-Sound-Forge). If an old machine is unavailable and you cannot manage the assignment, contact Boris FX support instead of trying a legacy serial-number workflow. ### Do I need an internet connection after installation? Internet access is required to download the Hub and complete initial login licensing. Boris FX's Sound Forge licensing article does not promise indefinite offline operation, so verify the current policy with support if the workstation must remain disconnected. ### How do I install ASIO drivers for my audio interface? Download the current Windows 11 ASIO driver from the audio-interface manufacturer's official support page, install it and restart if requested. Select ASIO under Options → Preferences → Audio, then choose the correct playback and recording ports in Sound Forge. Use the manufacturer's panel for hardware buffer, sample rate and clock; use Sound Forge's Audio preferences for its own routing and app buffering. ### Can I use my MAGIX Sound Forge Pro 18 serial number in the Boris FX version? Do not enter a MAGIX serial into current app activation. Boris FX says the previous purchase serial must first appear in your Boris FX account; from there you can buy an eligible upgrade. The 2026 application then uses login licensing: sign in and choose Use on This Computer. After installation, use the [beginner workflow](https://soundforgepro.com/how-to-use-sound-forge-tutorial/) to open, edit and verify one file. If the Hub or setup fails, follow the [installation troubleshooting sequence](https://soundforgepro.com/sound-forge-installation-failed/); if login licensing fails, use the [activation guide](https://soundforgepro.com/sound-forge-activation-failed/). ### Adobe Audition vs Sound Forge 2026: Which Is Better? URL: https://soundforgepro.com/sound-forge-pro-vs-adobe-audition/ Last updated: 2026-10-08T13:34:15.000Z Choose **Adobe Audition** for a podcast assembled from several recordings, a Premiere soundtrack or detailed spectral repair. Choose **Sound Forge** when you mostly edit finished audio files on Windows and want its analysis, batch-processing tools or perpetual license. Audition edits individual files too, so Sound Forge isn't an automatic upgrade for that job. What you really need to decide is whether you want an adjustable session or a dedicated file editor. If neither fits your budget or workflow, the [Sound Forge comparisons hub](https://soundforgepro.com/tag/comparisons/) separates free editors, multitrack DAWs and specialist restoration tools. This comparison is built on documented features and licensing; there's no measured speed test or blind listening test behind it. The trial checklist below lets you judge both on your own recording. The text and table compare the current releases. [Audition 26.5 is the September 2026 release](https://helpx.adobe.com/audition/desktop/introduction/whats-new.html); version 26.0 introduced native Windows on Arm support in January. [Boris FX acquired Sound Forge from MAGIX](https://blog.borisfx.com/press/boris-fx-acquires-vegas-pro-sound-forge-and-acid-pro) on March 30, 2026\. This comparison uses the current Sound Forge 2026 line. The plug-in bundles sold with older Pro 18 packages are a separate matter. --- ![A Sound Forge file analysis beside an Adobe Audition multitrack session](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/10/forge-vs-audition-ui-20260802-v20261006.webp) Workflow difference: Sound Forge finishes one audio file; Audition keeps voice, music, effects and ambience adjustable in a multitrack session. ## Quick Comparison Table | Decision point | Sound Forge 2026 | Adobe Audition 26.5 | | ---------------------------- | ------------------------------------------------------------------------------------------ | --------------------------------------------------------------------------------- | | Current platform | Windows 11 | Windows 11 24H2, Windows on Arm, macOS Sonoma+ | | Project model | File-first waveform editor; mono, stereo, multichannel files | Waveform Editor plus non-destructive Multitrack Editor | | US price reference | Boris FX launch figures: $24.95/month, $149.95/year, or $299.95 perpetual; verify checkout | $22.99/month, annual plan billed monthly | | Perpetual license | Yes | No | | Trial | 15 days listed by Sound Forge | 7 days; billing begins on day 8 in the displayed US signup flow | | Multitrack arrangement | No | Yes | | Windows audio-driver support | ASIO, Windows Classic Wave Driver or Microsoft Sound Mapper | ASIO or Microsoft Windows Driver Model | | Multichannel capture | Record and edit one file with up to 32 channels | Multitrack or multichannel workflows; count depends on device, driver and mapping | | Spectral selection | No equivalent to Audition's lasso/paintbrush spectral selections | Yes | | Loudness workflow | Statistics, Peak/RMS/Loudness Normalize, meters | Match Loudness, meters, effect racks, analysis | | Batch workflow | Batch Converter | Batch Process and Match Loudness | | Premiere integration | Standard-file external edit/import workflow | Native clip and sequence exchange | | Current plug-in headline | VST2, VST3, ARA | VST/VST3; Audio Units on macOS. Check plug-in architecture. | Adobe version, requirements, US list price, and trial were checked on September 12, 2026\. Sound Forge prices are the Boris FX 2026 launch figures; verify checkout because regional pricing, promotions, plan contents, drivers, and operating-system support can change. --- ## The Core Difference: Multitrack Session vs File Editor Adobe calls Audition a professional audio workstation. It has two distinct environments: a destructive Waveform Editor for individual files and a non-destructive Multitrack Editor for clips, tracks, routing, effects, automation, and mixdown. That makes it suitable for building a podcast, dialogue edit, soundtrack, or other session from multiple sources. Sound Forge is a file-first waveform editor. Boris FX documents recording and editing [one file with up to 32 channels](https://www.soundforge.com/sound-forge/pricing/), but says outright that Sound Forge isn't a multitrack DAW. It's at home with a mix, master, sample, transfer, interview, voice-over or deliverable that already exists as a file. Use Audition when the deliverable depends on the relationship between many clips and tracks. Use Sound Forge when the deliverable is one file and you want its editing, analysis, capture, and batch tools in one Windows application. Audition's Waveform Editor can also finish single files, so Sound Forge must earn the purchase through the exact controls and license model you need. --- ## Platforms and Current System Support [Audition 26.5 requires Windows 11 24H2](https://helpx.adobe.com/audition/desktop/introduction/system-requirements.html) or macOS Sonoma 14 or later. Adobe also lists native Windows on Arm support on Snapdragon X hardware. Check your processor, audio driver and plug-ins against the requirements, because an Intel plug-in isn't automatically compatible with an Arm-native host. [Sound Forge 2026 lists Windows 11](https://www.soundforge.com/sound-forge/system-requirements/), with no current native Mac edition, which settles this pair for a Mac owner. It doesn't mean an older Windows installation can never launch Sound Forge. It means Windows 10 isn't the published support baseline for this release. --- ## Waveform and Spectral Editing Both applications provide detailed waveform editing. Sound Forge emphasizes a direct file view and sample-level operations. Audition adds a spectral frequency display and selection tools inside its Waveform Editor. Neither product page proves that one produces higher-fidelity cuts; the useful difference is how you locate and select the problem. Sound Forge can zoom to individual samples, snap edits to zero crossings, repair short faults, and work directly on a selection. [WaveColor adds a visual layer](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/wavecoloring.htm): hue represents pitch range, while saturation separates more tonal or harmonic content from more noise-like content. It's an orientation aid rather than a spectral-selection tool, and it isn't evidence that an edit is correct before listening. Audition provides [rectangular, lasso and paintbrush spectral selections](https://helpx.adobe.com/audition/desktop/editing-audio-files/selecting-audio.html), plus a Spot Healing Brush. Its spectral display plots time against frequency, with color indicating amplitude. That lets you target a brief whistle without processing every frequency in the same time range. If the whistle overlaps a vocal harmonic, the selection can remove wanted sound too. For a short click between words, either editor may be enough. For a moving whistle under speech, Audition gives you more control over the shape of the selection. After the repair, listen to the consonants and the ends of words as well as the quieter gap between sentences. --- ## Multitrack Recording and Mixing Audition's Multitrack Editor records and arranges multiple tracks, applies clip and track effects, routes buses, automates mix parameters, and exports a mix or stems. The number of simultaneous inputs depends on the audio interface, driver, channel mapping, storage, and system performance. Sound Forge doesn't provide a multitrack arrangement timeline. It can record and edit one file with up to 32 channels, but that isn't the same as independent tracks, clips, buses, and automation. Both programs support ASIO on Windows, so the useful distinction is the project structure: choose Audition or another DAW when the mix must stay adjustable as a session. --- ## Premiere Pro Workflow and Adobe Ecosystem [Premiere can send a sequence to Audition](https://helpx.adobe.com/premiere/desktop/use-premiere-with-other-apps/working-with-other-adobe-applications/edit-premiere-sequences-in-audition.html) with keyframes, effects, Essential Sound settings, markers and other audio metadata, and Audition opens it in the Multitrack Editor. For a single clip, Edit in Adobe Audition opens a rendered audio copy; saving the edit updates the Premiere timeline. Sending a session back uses [Audition’s export-to-Premiere command](https://helpx.adobe.com/audition/desktop/video-and-surround-sound/video-applications.html), with a mixdown or separate track/bus stems. Check how effects transfer on your own sequence instead of assuming every third-party effect will arrive intact. If you don't use Premiere, the integration has no value. Audition still offers multitrack and spectral tools on its own, but it remains subscription-only. Sound Forge offers subscription and perpetual choices; a perpetual license covers the purchased version, while access to future updates follows the current Boris FX plan terms. Audition's Essential Sound panel groups task-oriented controls around Dialogue, Music, SFX and Ambience. That's handy for editors who want a guided starting point, especially when they move between Premiere and Audition. Treat its presets as a first pass, then listen and measure, because a preset can't guarantee a clean or compliant mix. --- ## Loudness, Metering, and Mastering Sound Forge combines peak and loudness meters with [Tools → Statistics](https://soundforgepro.com/how-to-use-statistics-sound-forge-pro/), Peak/RMS/Loudness Normalize modes, coreFX, essentialFX and dynamic EQ. These are useful when a finished file needs analysis and a delivery pass. Peak normalization and loudness normalization solve different problems; use the measurement named in the delivery specification and check the exported file. [Audition's Match Loudness panel](https://helpx.adobe.com/audition/desktop/editing-audio-files/match-loudness.html) scans one or more files and applies a selected standard, target loudness, tolerance and maximum true-peak limit. Audition also has realtime effect racks, meters, dynamics, EQ and analysis panels, so Match Loudness is far from its only mastering method. Automatic correction still needs a final measurement of the exported deliverable. Recall is where the two differ in practice: an Audition session keeps the source clips, routing and mix adjustable, while a processed audio file can't hold all those decisions. If you plan to finish in Sound Forge, keep the session and an unprocessed export, so a later dialogue change doesn't force you to rebuild the mix. --- ## Noise Reduction and Audio Restoration [The current Sound Forge feature list](https://www.soundforge.com/sound-forge/pricing/) includes broadband noise reduction and click, crackle and clipping repair. Don't count an old iZotope bundle as part of a new purchase unless the plan explicitly includes it. For repetitive conversions, the [Sound Forge Batch Converter workflow](https://soundforgepro.com/how-to-batch-process-files-sound-forge-pro/) is useful, though a noise profile that suits one recording may damage another. Audition’s [noise-reduction and restoration effects](https://helpx.adobe.com/audition/desktop/effects-reference/noise-reduction-restoration-effects.html) include profile-based Noise Reduction, Adaptive Noise Reduction, DeNoise, Automatic Click Remover and DeHummer. Its Diagnostics panel adds DeClicker and DeClipper. Noise Reduction is an offline Waveform process; other effects can run in the rack. When available, preview the removed noise in isolation: recognizable words or music mean the settings are taking too much. Audition is the more flexible choice for hand-selected spectral repair, although that doesn't promise a cleaner result on every file. If the whole job is restoration rather than editing, compare [Sound Forge with iZotope RX](https://soundforgepro.com/sound-forge-pro-vs-izotope-rx/) before paying for another general-purpose editor. --- ## Pricing, Trial, and License Terms [Adobe’s US page](https://www.adobe.com/products/audition/free-trial-download.html) lists Audition at $22.99 per month, annual billed monthly, checked September 12, 2026\. This is an annual commitment, not a cancel-anytime monthly plan. Creative Cloud Pro is listed at $69.99 per month on the same billing basis before promotions. Audition is subscription-only. The displayed seven-day trial starts at checkout and converts to paid membership unless canceled; the page says billing begins on day 8 and describes a further 14-day refund window. Read the terms shown for your region before signing up. [Boris FX’s launch announcement](https://blog.borisfx.com/press/boris-fx-acquires-vegas-pro-sound-forge-and-acid-pro) listed base Sound Forge at $24.95 monthly, $149.95 annually, $189.95 for Upgrade & Support, or $299.95 perpetual. Those are launch figures and may not match today's checkout. Upgrade & Support and a new perpetual license are different purchases. The announced legacy upgrade offer runs through December 5, 2026; confirm eligibility, tax and the chosen edition through the [Sound Forge pricing guide](https://soundforgepro.com/sound-forge-pro-pricing/) and vendor checkout. Under the [Boris FX support-plan terms](https://support.borisfx.com/hc/en-us/articles/10334870429709-What-is-the-Upgrade-Support-Plan-What-is-U-S), an owned perpetual version keeps working after support expires, but future updates are a separate question. As a budget example, 36 payments of $22.99 add up to $827.64 before tax. That assumes the rate never changes, so don't read it as a three-year quote. If you already pay for Creative Cloud Pro, check whether your account includes Audition before budgeting for it twice. --- ## Current Version and Known-Issue Check [Audition 26.5 fixes several issues](https://helpx.adobe.com/audition/desktop/introduction/fixed-issues.html), including a Windows crash on quitting after importing media. Adobe’s [known-issues page](https://helpx.adobe.com/audition/desktop/introduction/known-issues.html) still documents Arm effect-window flicker and APE import restrictions, Dolby decoding on fresh Windows 11 24H2 installations, and Sequoia permission prompts. That page is dated March 27, so treat it as a compatibility checklist, not proof that every issue affects your 26.5 installation. Since [26.3 removed CD authoring](https://helpx.adobe.com/audition/desktop/introduction/removal-of-cd-authoring.html), do not choose current Audition for CD Layout, ISRC/UPC entry or pre-gap authoring. Exporting audio for separate disc software does not restore those controls. Before switching editors on a working machine, try a copy of a project with your interface and essential plug-ins. Check opening, playback, processing, export and reopening the result. Keep the original project, media and presets; a supported operating system on its own doesn't validate the rest of that chain. --- ## Who Should Use Which Use Adobe Audition if you need macOS, a multitrack session, spectral selections, Essential Sound, Match Loudness, or direct Premiere clip and sequence exchange. It's easiest to justify when those session and video workflows matter more to you than perpetual ownership. Use Sound Forge if you're on Windows, work mainly on finished files, need to record or edit one file with up to 32 channels, prefer its Statistics/Normalize/Batch Converter workflow, use its ARA workflow, or want a perpetual-license option. Don’t buy it just for ASIO (Audition supports ASIO on Windows too), or for an old iZotope bundle unless the current checkout explicitly includes that product. **Use the trials on one real job.** Open the same source, make the edit you actually need, export it and reopen the result. For a podcast, include a music bed and one later dialogue correction. For restoration, compare the repaired passage at matched playback loudness and listen for damaged speech. For batch work, start with a few copies and inspect every output. Use both applications only if the second saves a specific step that matters to you. --- ## Frequently Asked Questions ### Is Sound Forge Pro better than Adobe Audition? Neither is universally better. Audition is stronger for multitrack sessions, macOS, spectral editing, and Premiere exchange. Sound Forge is stronger as a focused Windows file editor with up-to-32-channel file handling, dedicated analysis and batch tools, ARA support, and a perpetual-license option. Both support ASIO on Windows. ### Does Adobe Audition have a perpetual license? No. Audition requires a subscription. Its US individual plan was listed at $22.99 per month, annual billed monthly, on September 12, 2026\. A single-app subscription does not require buying Creative Cloud Pro, but it is still a Creative Cloud membership. Regional prices and cancellation terms vary. ### Can Adobe Audition open Sound Forge Pro files? Audition can open common audio exports such as WAV, FLAC, and MP3, subject to codec and format details. It cannot open a Sound Forge workspace or reproduce a Sound Forge plug-in chain from the audio file. Export an interoperable audio master and document sample rate, bit depth, channels, and metadata. ### Does Sound Forge Pro integrate with Premiere Pro? Not with Adobe's native Edit in Audition clip/sequence exchange. A Sound Forge workflow normally sends and returns a standard audio file through Premiere's external-edit or import workflow. Audition can preserve and transfer more Premiere sequence metadata because both applications share an Adobe integration path. ### Which is better for podcast editing? Audition is usually the better all-in-one choice when a podcast uses multiple hosts, music, inserts, clip effects, routing, and mix automation. Sound Forge is a good final-file editor and can check or correct a finished episode. Either can meet a delivery spec when you verify the exported file. ### What happened to Sound Forge Pro in 2026? Boris FX announced its acquisition of Sound Forge, Vegas Pro, and Acid Pro from MAGIX on March 30, 2026\. Current Sound Forge 2026 product, pricing, requirements, and documentation pages are on SoundForge.com and Boris FX domains; older MAGIX-era packages must be treated as version-specific. ### Is Audition worth buying as a single app? It can be if you need its multitrack, spectral editing or restoration tools without the other Adobe apps. You do not need to use Premiere to benefit from Audition. Compare the annual commitment with the cost of the Sound Forge edition and any extra plug-ins you need; if you only trim occasional files, a paid editor may be unnecessary. For that occasional-editing case, see [what Sound Forge adds over free Audacity](https://soundforgepro.com/sound-forge-pro-vs-audacity/). If your project instead needs a full DAW, the [Reaper comparison](https://soundforgepro.com/sound-forge-pro-vs-reaper/) covers that different buying decision. ### Audacity vs Sound Forge 2026: Free or Pro? URL: https://soundforgepro.com/sound-forge-pro-vs-audacity/ Last updated: 2026-10-10T12:58:13.000Z Choose Audacity 4 for a free multitrack project on Windows, macOS or Linux. Choose Sound Forge on Windows for detailed work on individual audio files, dedicated batch processing, analysis or ARA integration. Neither is automatically better-sounding: the useful question is which one fits the session you need to finish. For the wider product overview, see our [Sound Forge guide](https://soundforgepro.com/). Need a different kind of editor? The [Sound Forge comparisons hub](https://soundforgepro.com/tag/comparisons/) separates multitrack production, mastering and specialist audio repair. This comparison is built from the documentation for Sound Forge 2026, Audacity 4.0.0 and the older Audacity 3.7.9 workflow. There's no timed benchmark or listening test behind it. Audacity 4 is the current stable release, but some 3.x features are missing, and those gaps matter before you migrate an existing project. --- ![Sound Forge batch tools beside an Audacity project running Macros](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/10/forge-vs-audacity-ui-20260802-v20261005-v20261006.webp) Workflow difference: Sound Forge centers analysis and batch delivery on one file; Audacity keeps a free multitrack project and automates repeatable work with Macros. The Macros workflow shown above belongs to Audacity 3.x. The 4.0.0 release notes list Macro Manager and the scripting pipe as unavailable, so don't plan a 4.0 batch job around it. ## Quick Comparison Table | Decision point | Sound Forge 2026 | Audacity 4.0.0 | | -------------------------------- | ----------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------- | | Cost (Sound Forge launch prices) | Announced from $24.95/month, $149.95/year, or $299.95 perpetual | Free and open source | | Desktop platforms | Windows 11 | Windows, macOS, Linux | | Project model | File-first waveform editor; mono, stereo, and multichannel files | Multitrack AUP4 project; AUP3 converts one way to AUP4 | | Sample-level editing | Yes | Yes, with context-sensitive sample drawing and Repair | | Windows ASIO in official build | Yes | Yes | | Multichannel capture | Up to 32 channels in one file | Depends on interface, driver, exposed channels, and mapping | | Loudness workflow | Statistics, Loudness Normalize, peak/loudness metering | EBU R128 Loudness Normalization; compatible meter plug-ins | | Restoration | Broadband noise reduction, click/crackle and clipping repair in current plans | Noise Reduction, Click Removal, Repair, filters, and spectral tools | | Batch processing | Dedicated Batch Converter | Macro Manager is absent in 4.0; 3.7.9 retains the older Macros workflow | | Plug-ins | VST2, VST3, ARA | VST3; LV2 on Linux and Audio Units on macOS. Nyquist and legacy-format documentation conflict; see the plug-in section | | ACX tools | Built-in ACX Check and Export Instant Actions | Manual or third-party checking workflow | Sound Forge prices are the figures Boris FX announced for the 2026 launch; verify the live checkout because taxes, currency, promotions, and terms can change. Features can differ by operating system, driver, hardware, plan, and plug-in architecture. --- ## The Real Difference: File Editor vs Multitrack Project Sound Forge is a file-first waveform editor. It opens mono, stereo and multichannel files and can [record a multichannel file](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/recording%5Fmultichannel%5Faudio.htm), but Boris FX says plainly that it isn't a multitrack DAW. That makes it a strong fit for editing a mix, master, sample, interview, voice-over, transfer or deliverable once the arrangement already exists. Audacity 4 stores multiple tracks and clips in an AUP4 project. You can record, overdub, arrange and group clips, pan tracks, run realtime effects on tracks or the master, and export a mix. For an interview with separate guest tracks and a music bed, that's the more suitable project model. The 4.0 release has no MIDI tracks or virtual-instrument production, so choose a DAW if you can't do without those. --- ## Platform Support [Audacity 4.0.0 is available for Windows, macOS, and Linux](https://www.audacityteam.org/download/). The official downloads include Windows x64 and ARM64, a universal macOS build for Intel and Apple Silicon, and Linux AppImages for x86\_64 and ARM64\. Audio-device access, package integration, and plug-in availability can still vary by operating system and architecture. Sound Forge 2026 is Windows-only. The [current Boris FX requirements page lists Windows 11](https://www.soundforge.com/sound-forge/system-requirements/) and leaves Windows 10 off; the official product pages show no current macOS or Linux edition. If your editing machine is a Mac or a Linux system, Audacity wins this comparison before features or price even come up. --- ## Audio Editing Depth ### Sample-level precision Sound Forge is built around sample-accurate waveform work. You can zoom to individual samples, place edits at zero crossings, repair short faults and read exact amplitude values. That direct file view is the reason to consider it for surgical cleanup. Audacity supports sample-level editing too. [Audacity 4 removes the separate Draw tool](https://www.audacityteam.org/manual/new-in-audacity-4/audacity-3-to-4-transition-guide/): zoom until individual samples are visible and the pointer turns into a pencil near a sample point. Repair and spectral tools handle other short defects. Both editors can change individual samples, so compare the selection and repair workflow on a copy of your own file. ### Destructive vs non-destructive Audacity mixes destructive and non-destructive operations. Clip trimming remains adjustable, and realtime effects stay editable on a track or the master stack until export. In Audacity 4, [the bundled Compressor, Limiter, and Reverb can run realtime](https://www.audacityteam.org/manual/effects/realtime-effects/); other bundled effects applied from the Effect menu rewrite the selected audio. Save the AUP4 project and keep an untouched source rather than assuming every edit remains live. Sound Forge's default Process commands change the selected waveform when you apply them, while its event-based mode provides a non-destructive editing route. Preview, Undo, plug-in chains, and Save As further reduce risk, but this remains a file-first workflow. Work on a copy and keep the original separately from the processed file. ### Noise Reduction and Restoration Current Sound Forge plans list broadband noise reduction plus tools for clicks, crackles and clipped audio. Older MAGIX bundles sometimes included third-party iZotope products, but that doesn't mean a current Boris FX purchase includes them. Check the [current plan matrix](https://www.soundforge.com/sound-forge/pricing/) before buying. Audacity's [built-in Noise Reduction learns a noise profile](https://www.audacityteam.org/manual/effects/noise-removal-and-repair/noise-reduction/) and is meant for steady sounds such as hiss, hum or an air conditioner. The current manual separates these from one-off sounds such as a door slam. Preview the result and use Noise Only to hear whether wanted speech or music is being removed; watery artifacts mean you should back the processing off. For short clicks, try Click Removal or Repair instead. --- ## Recording: Tracks, Channels, and ASIO Audacity is the better pick here for recording and arranging multiple tracks in one project. The Windows caveat changed in September 2026: [official Audacity 4.0.0 and 3.7.9 builds](https://www.audacityteam.org/changelog/) include ASIO playback and recording. How many inputs you can use still depends on the interface, its driver, the channels it exposes and Audacity's channel mapping, and the ASIO label alone doesn't guarantee a particular multichannel setup. Sound Forge supports ASIO, and the [current product page](https://www.soundforge.com/sound-forge/pricing/) specifies recording and editing files with up to 32 channels. That's useful for a concert, a location recorder or surround capture headed for file-based editing. It still won't give you a multitrack arrangement with independent clips, automation, buses and virtual instruments. Use Audacity for a simpler multitrack edit or a DAW for deeper production. --- ## Loudness, Metering, and Mastering Sound Forge 2026 provides peak and loudness metering, Tools → Statistics, three Normalize modes, effect chains, coreFX and essentialFX processing, and dynamic EQ. Pick the measurement your delivery specification actually asks for; peak level, average level and integrated loudness aren't interchangeable. Audacity has [EBU R128-based Loudness Normalization](https://www.audacityteam.org/manual/effects/volume-and-compression/loudness-normalisation/), realtime track and master effects, a limiter, compressor, EQ, and [third-party meter plug-ins](https://soundforgepro.com/free-metering-plugins/). Loudness Normalization is an effect rather than an export-only switch. Sound Forge exposes more dedicated file-analysis controls, but Audacity can produce a compliant master when you use the required meter, dynamics chain, and final verification. Both export common formats including WAV, FLAC, and MP3\. Current Audacity builds include MP3 support; [FFmpeg is needed](https://www.audacityteam.org/manual/getting-started/export-your-audio/) for additional formats such as M4A. Exact codecs, metadata, bit depths, channel layouts, and dithering choices still differ, so compare the required deliverable rather than a generic “supports audio export” checkbox. --- ## Batch Processing Audacity 4.0 doesn't include the Macro Manager or scripting pipe, so the old Macros batch workflow is gone from the current major release. Audacity 3.7.9 is still downloadable and keeps Macros; its [older manual recommends no more than 500 files](https://manual.audacityteam.org/man/macros.html) in one batch. If automation is essential, try 3.7.9 on copies or wait for the feature to return in 4.x, and remember that an AUP4 project can't be saved back to AUP3. Sound Forge's Batch Converter provides input lists, processing chains, output formats, naming and destination controls. Test a few representative files before processing an archive. For the Windows workflow, follow the [Sound Forge batch-processing guide](https://soundforgepro.com/how-to-batch-process-files-sound-forge-pro/): run a small pilot, check the exported files and keep the originals out of the destination folder. --- ## VST Plugins [Audacity's current launch pages](https://www.audacityteam.org/faq/) agree on VST3, with LV2 on Linux and Audio Units on macOS; [the FAQ and current manual also describe Nyquist plug-ins](https://www.audacityteam.org/manual/tools/nyquist/). The transition guide lists VST and LADSPA but says Nyquist and VAMP aren't supported yet, while the 4.0 changelog lists Nyquist as supported and LADSPA/VAMP as unavailable. Those claims contradict each other. Before migrating, check the exact plug-in in Plugin Manager and run a short processing test on the target build and operating system, because a format listed on one launch page doesn't guarantee compatibility. The [current Sound Forge plan matrix](https://www.soundforge.com/sound-forge/pricing/) explicitly lists VST2, VST3, and ARA support. Audacity supports effect plug-ins but isn't a virtual-instrument production environment, and neither is Sound Forge. ARA is still a meaningful Sound Forge distinction. Before switching, check the exact plug-in version, architecture, user interface, preset recall and ARA workflow you depend on. --- ## Audacity 4.0 Is Stable—and Some 3.x Features Are Missing [Audacity 4.0.0 became the stable release on September 3, 2026](https://www.audacityteam.org/changelog/). It rebuilds the interface on Qt, changes clip selection and editing, adds workspaces, revises recording, includes ASIO in official Windows builds, and saves local projects as AUP4\. [An AUP3 project opens and converts without changing the original](https://www.audacityteam.org/manual/getting-started/save-your-project/), but the converted project cannot be saved back to AUP3. The first 4.0 release does not include Time Tracks, Note/MIDI tracks, Mixer, Macro Manager, the scripting pipe, or play-at-speed, and the changelog warns that some export/render features, analyzers and effects are still missing. That makes Audacity 3.7.9 a reasonable temporary choice when you can't live without a missing 3.x function. Try the migration on copies, list your plug-ins first, and don't expect a converted AUP4 project to go back to the older format. --- ## Pricing and Licensing Audacity is free and open source under the GPL. No paid feature tier stands between you and editing, recording, local plug-ins or export. Optional cloud services sit apart from the desktop editor, and a local project doesn't need them. [Boris FX announced](https://blog.borisfx.com/press/boris-fx-acquires-vegas-pro-sound-forge-and-acid-pro) the base Sound Forge 2026 plan at $24.95 monthly, $149.95 annually, $189.95 for Upgrade & Support, or $299.95 perpetual when the 2026 editions launched. Check the [current product page](https://www.soundforge.com/sound-forge/pricing/) for the purchase options available now. The figures here are launch prices rather than a live checkout quote, and taxes, currency, promotions and terms can change them. The announced legacy upgrade offer runs through December 5, 2026. A perpetual license and an annually renewed support plan are two different things. [Boris FX's Upgrade & Support policy](https://support.borisfx.com/hc/en-us/articles/10334870429709-What-is-the-Upgrade-Support-Plan-What-is-U-S) includes 12 months of upgrades and support with a perpetual purchase and renews automatically, which you can cancel in your account. The perpetual license keeps working when support expires, though reinstating it later can cost more. Check the renewal terms at checkout and use the [Sound Forge pricing breakdown](https://soundforgepro.com/sound-forge-pro-pricing/) to compare the plan types. If you are undecided, use the [official 15-day Sound Forge trial](https://vfx.borisfx.com/sound-forge-trial) on a copy of the same short project you can finish in Audacity. Check selection, cleanup, required plug-ins and export. Buy only if the difference matters to your work, rather than assuming a paid editor must produce better audio. --- ## Which One to Use Use Audacity 4 if: you need Windows, macOS, or Linux support; a multitrack project; free local editing; official Windows ASIO; realtime track or master processing; or a straightforward podcast and voice workflow. Use 3.7.9 temporarily only when a missing 4.0 feature such as Macro Manager is essential, and keep project copies because AUP4 does not save back to AUP3. Use Sound Forge if: you are on Windows and work mainly on finished files, need to record or edit one file with up to 32 channels, want integrated Statistics and Normalize controls, depend on ARA or VST2/VST3 processing, or prefer its dedicated Batch Converter and restoration tools. Check the current plan contents instead of relying on older MAGIX bundle lists. Use both if: you want Audacity for recording and arranging, then Sound Forge for file-based cleanup, analysis, or delivery. Keep the original project and an unprocessed export, document the sample rate and bit depth, and verify the final encoded file. The handoff is useful only when each application has a defined job. --- ## Frequently Asked Questions ### Is Sound Forge Pro better than Audacity? Neither is universally better. Audacity 4 is the stronger choice for free cross-platform multitrack projects and now includes ASIO in its official Windows build. Sound Forge is the stronger choice for a Windows file-first workflow with up-to-32-channel file handling, dedicated analysis, ARA, restoration, and batch tools. ### Can Audacity replace Sound Forge Pro? Yes for many podcast, voice, conversion, multitrack, and basic mastering jobs. Audacity 4 includes official Windows ASIO, but its multitrack project is a different workflow from Sound Forge's single-file editor. ARA and the dedicated Batch Converter are separate reasons to choose Sound Forge. Do not read its 32-channel specification as a claim that Audacity is limited to stereo: Audacity's recording inputs depend on the device, driver, and channel mapping. ### Does Audacity support VST plugins? Yes. Audacity 4 supports VST3 effects and additional formats by platform. Its official pages disagree about Nyquist and some legacy formats, so verify the exact plug-in on your operating system before moving a production project. It is not a virtual-instrument host. ### Is Audacity good enough for podcast editing? Yes. Audacity can record and arrange tracks, edit dialogue, apply Noise Reduction and realtime effects, normalize loudness, and export common delivery formats. Verify the host's current loudness, peak, channel, bitrate, and metadata requirements before publishing. ### Does Sound Forge Pro run on Mac? No current macOS edition is listed. Sound Forge 2026 currently lists Windows 11 as its supported operating-system baseline. Audacity is the option in this comparison if you need a current native Mac build. ### Is Audacity 4.0 the stable release? Yes. Audacity 4.0.0 became the stable release on September 3, 2026\. It uses AUP4 projects and official Windows builds include ASIO, but Macro Manager, the scripting pipe, MIDI tracks, Mixer, and several other 3.x functions are absent in the first 4.0 release. Test migration and plug-ins on copies. ### Which is better for ACX audiobook standards? Both can prepare compliant files. The [current ACX audio submission requirements](https://help.acx.com/s/article/what-are-the-acx-audio-submission-requirements) specify -23 to -18 dB RMS, peak values no higher than -3 dB, and a noise floor no higher than -60 dB RMS. They also require 44.1 kHz MP3 at 192 kbps or higher CBR, with consistent mono or stereo across the book. These are separate checks, not a single loudness preset. Sound Forge 2026 includes [ACX Check and Export Instant Actions](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/instantactions.htm). Audacity workflows use its meters and effects plus optional third-party checking tools, so verify every exported chapter against ACX before upload. ### Does Audacity work well on Linux? Yes. Audacity provides official Linux AppImages. Audio-device access, desktop integration, architecture, and plug-in availability can vary by distribution, so test recording and plug-ins on the target system before a critical session. If Audacity's free multitrack model is right but you need deeper DAW routing, compare [Sound Forge with Reaper](https://soundforgepro.com/sound-forge-pro-vs-reaper/). If the missing feature is spectral repair, use the [iZotope RX comparison](https://soundforgepro.com/sound-forge-pro-vs-izotope-rx/). For a subscription multitrack editor tied to Premiere, see [Adobe Audition versus Sound Forge](https://soundforgepro.com/sound-forge-pro-vs-adobe-audition/). ### Sound Forge 2026 Review: Is It Worth Buying? URL: https://soundforgepro.com/sound-forge-pro-review-2026/ Last updated: 2026-10-09T21:57:16.000Z **Sound Forge is still worth buying in 2026 if your work starts and ends with an audio file.** It is a dedicated Windows waveform editor for precise cuts, restoration, recording, analysis, mastering and repeatable batch jobs. It isn’t a DAW, there’s no current Mac version, and it isn’t the strongest choice for spectral repair. Those limits are clear enough that the buying decision is simpler than the feature list makes it look. **Documentation checked September 9, 2026.** This review covers the current Boris FX Sound Forge and Sound Forge Plus plans, Windows 11 requirements, announced 2026 US launch-price references, the 15-day trial, and the separate July 2026 iZotope acquisition. This is a source-based assessment of features and buying fit. It does not establish editing speed, stability or repair quality on your hardware. | Best for | Windows users editing, repairing, measuring or delivering individual audio files | | ----------------- | -------------------------------------------------------------------------------------------- | | Wrong fit for | Multitrack production, MIDI composition, native macOS work, or advanced spectral restoration | | Current plans | Sound Forge and Sound Forge Plus | | License choice | Monthly, annual, Upgrade & Support, or perpetual | | Trial | 15 days, full-featured, no credit card, Windows only | | Editorial verdict | **4.2/5**: excellent file editor, dated in places, easy to buy for the wrong job | If you are new to the product, read this review before the [full Sound Forge pricing breakdown](https://soundforgepro.com/sound-forge-pro-pricing/). If you already own Pro 18, use the [Sound Forge 2026 vs Pro 18 comparison](https://soundforgepro.com/sound-forge-2026-vs-pro-18/) before paying for an upgrade. ## My Verdict: Buy It for File Work, Not Because It Is “Pro” I would buy Sound Forge for a Windows workflow built around finished files: a stereo mix, a voice-over take, a vinyl transfer, a sample library, an interview, or a folder of deliverables that all need the same processing. The editor keeps selection, playback, meters, processes and file output close together. That directness is what makes Sound Forge useful when a file contains many small editing decisions. I wouldn’t buy it to produce a song, assemble a multitrack podcast, mix dialogue against music or replace a DAW. Boris FX says as much on the [current Sound Forge product page](https://www.soundforge.com/sound-forge/pricing/): Sound Forge works on a single audio file and deliberately doesn't act as a multitrack DAW. It can open and record multichannel files, but the channels inside one file aren’t independent tracks, clips, buses and automation. The second hard limit is platform support. The official [Sound Forge system requirements](https://www.soundforge.com/sound-forge/system-requirements/) list Windows 11, and the trial page says Windows only. If your main machine is a Mac, stop here and pick a current macOS editor; there’s no point building a purchase around a discontinued Mac edition. ![Sound Forge single-file waveform editor compared with a multitrack DAW session](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/10/review-file-vs-daw-desktop-v2-v20261006.webp) Edit and finish one audio file in Sound Forge; build independent dialogue, music and effects tracks in a DAW. ## What Changed After Boris FX Bought Sound Forge? [Boris FX announced the acquisition](https://blog.borisfx.com/press/boris-fx-acquires-vegas-pro-sound-forge-and-acid-pro) of Sound Forge, Vegas Pro and Acid Pro from MAGIX on March 30, 2026\. The sale moved purchasing, trial activation and support into the Boris FX ecosystem and introduced a simpler two-plan lineup: Sound Forge and Sound Forge Plus. The acquisition announcement doesn't amount to a detailed Sound Forge feature roadmap. [iZotope joined Boris FX on July 2, 2026](https://www.izotope.com/community/blog/joining-boris-fx), yet neither that announcement nor the current Sound Forge plan table says RX, Ozone or any other iZotope tool comes with Sound Forge. The honest description is still the 2026 release of the familiar Windows file editor, with a new owner and new plan names. Future integrations may happen, but they're no reason to buy software today. The acquisition notice also says the existing Vegas, Sound Forge and Acid teams joined Boris FX. That’s encouraging continuity, though it proves nothing about future stability, and it doesn’t guarantee an old plug-in, driver or preset will behave identically. If this is production software for you, keep installers and source files and test a copy of a real job before changing versions. ## Where Sound Forge Is Genuinely Strong ### 1\. Direct waveform and sample-level editing This is the core reason to use it. Sound Forge lets you move from a whole-file view to individual samples without changing applications or modes. You can define an exact selection, snap an edit to a zero crossing, repair a very short fault, [create markers and regions](https://soundforgepro.com/sound-forge-markers-regions/), process only part of a file, or keep only the selected material with Trim/Crop. Those controls matter when you need to inspect and change a precise section without setting up a multitrack session. Work on a copy: direct processing changes the audio, and an event-editing mode doesn't make every later render reversible. What the event-based mode does give you is a non-destructive option when direct destructive editing is too risky for the source. ### 2\. Useful analysis beside the audio The official 2026 [Statistics help](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/statistics.htm) says the report works on the selected file region. It lists cursor and sample extrema, RMS, average value for spotting DC offset, zero crossings, maximum true peak, integrated loudness, loudness range, maximum short-term loudness and maximum momentary loudness. Statistics only reports measurements; it won't normalize, limit or repair anything. The habit worth building is simple: measure the relevant region, process it, then measure the same region again. The official 2026 [WaveColor help](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/wavecoloring.htm) says hue maps low, middle and high pitch regions as red, green and blue. Saturation rises for tonal or harmonic material and falls as the material becomes more noise-like. That makes WaveColor a navigation aid; it proves nothing about clipping, repair quality or whether an edit worked. Our [WaveColor guide](https://soundforgepro.com/how-to-use-wavecolor-in-sound-forge-pro/) explains the control and the common misread. ### 3\. Batch Converter and repeatable delivery work Batch Converter is one of the product's clearest advantages over a basic editor. You choose the files, build an ordered Processing list from effects and presets, add one or more export formats, set output and naming rules, then run the job. This is useful for archive copies, sample libraries, podcast deliverables, voice assets and any folder where consistency matters more than hand-editing every file. Pilot the actual source types first: start with a typical file and a difficult file, add cases for different formats or channel layouts, and write results to a new folder. A batch tool repeats mistakes just as efficiently as it repeats good settings. The current [Batch Converter walkthrough](https://soundforgepro.com/how-to-batch-process-files-sound-forge-pro/) explains file selection, processing order, export templates and checks before the full run. ### 4\. Straightforward recording and multichannel-file support Sound Forge supports manual recording, threshold- or time-triggered recording, a prerecord buffer, ASIO, and files with up to 32 channels according to the current product page. That makes it practical for a voice take, transfer, field capture or multichannel source file. Don’t turn “32 channels” into a promise that any laptop can record 32 inputs reliably. The actual limit depends on the interface, driver, storage, sample format, system load and routing. Run a sustained test with the same device and format you will use on the real session. The [recording guide](https://soundforgepro.com/how-to-record-audio-in-sound-forge-pro/) starts with Windows microphone access and input mapping because those are the failures that stop a take before audio quality matters. ### 5\. A practical processing and plug-in environment The base plan lists coreFX, essentialFX, dynamic EQ, VST2, VST3 and ARA support, broadband noise reduction, click and crackle removal, clipping repair, Text to Speech, metering and batch processing. The real-time Plug-In Chain lets you order processors, preview them and compare Bypass before committing the file. Sound Forge Plus adds Melodyne 5 Essential, Vandal, VariVerb II and 3D Reverb. Those extras are specific, and nothing here is a vague “better audio” tier. Buy Plus only if pitch correction, amp emulation or the added reverbs belong in your actual work, because restoration, file editing and batch processing don’t need it. For Melodyne integration, the [current ARA instructions](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/proonly/ara.htm) use Tools → Edit in Melodyne (ARA) with its VST3 component installed; loading it as an ordinary chain plug-in doesn't give you the same integration. ARA support also doesn't hand you a license for every compatible third-party editor. ![Statistics, the Plug-In Chain and Batch Converter open across one Sound Forge session](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/10/review-ui-core-workflow-v2-v20261006.webp) Sound Forge at its best is file-first: measure, process, compare and deliver without pretending the editor is a DAW. ## Where Sound Forge Falls Short ### No multitrack arrangement or MIDI sequencing Nobody forgot a checkbox here. It's where the product ends. You can edit channels in a multichannel file, but you can't keep a song or podcast adjustable as independent tracks and clips. REAPER, Adobe Audition and other DAWs are built for that. Sound Forge is the editor you might reach for before or after the session. It isn't the session itself. ### Windows only The official trial says Windows only, and the current Boris FX requirements page lists Windows 11, with no Windows 10 and no current native macOS edition. For many studios that rules Sound Forge out before features or price even come up. ### Restoration is useful, but it is not RX 12 Sound Forge handles the common faults: broadband noise, clicks, crackle, clipping and short waveform damage. RX 12 Standard and Advanced provide a spectrogram-led editor with Spectral Repair, Dialogue Isolate and Music Rebalance. Advanced adds specialist modules and a high-quality offline Dialogue Isolate mode, so don't assume every RX edition has the same tools. [iZotope's RX 12 page, checked September 9, 2026,](https://www.izotope.com/products/rx-standard) lists Standard at $399 and Advanced at $1,399. For difficult dialogue or location sound, trial the relevant RX edition on the same source before choosing a restoration specialist. If restoration is one step inside recording, editing, analysis and delivery, Sound Forge may be the better all-round file workspace. There is no honest “cleaner” winner without the same source, settings, artifact criteria and level-matched comparison. ### The interface rewards familiarity more than discovery Sound Forge exposes many functions through menus, shortcuts and separate tool windows. A new user still faces a dense collection of processes, effects, tool windows and overlapping restoration families. The direct file-editing model hangs together, but the interface won't explain every distinction between analysis, restoration, processing and delivery for you. Use the full trial on your actual display and workflow. Check scaling, audio-device routing, third-party plug-ins, keyboard assignments and the exact export format you need before buying. A feature list can’t reproduce those compatibility details. An archived community discussion points to the same test. In a 2025 [r/AudioPlugins upgrade discussion](https://www.reddit.com/r/AudioPlugins/comments/1n33laj/updating%5Fsound%5Fforge%5F16%5Fto%5F18%5Fworth%5Fit%5Ffor%5F80/), users praised direct sample editing and large batch jobs while raising high-DPI and upgrade-value concerns. Those reports are about older MAGIX releases, not a confirmed defect in the 2026 build. The thread is anecdotal evidence rather than a benchmark, and it earns its place by naming two checks a generic feature list misses: display scaling, and whether the new plan improves the exact work you already do. ## Sound Forge Price in 2026 In the March 2026 launch announcement, [Boris FX’s announced US price table](https://blog.borisfx.com/press/boris-fx-acquires-vegas-pro-sound-forge-and-acid-pro) lists the base plan at **$24.95 monthly**, **$149.95 annually**, **$189.95 for Upgrade & Support**, or **$299.95 perpetual**. Sound Forge Plus is listed at **$33.95 monthly**, **$199.95 annually**, **$249.95 for Upgrade & Support**, or **$399.95 perpetual**. Prices, tax, currency conversion, promotions and renewal terms can change, so check the [live official pricing page](https://www.soundforge.com/sound-forge/pricing/) at checkout. Boris FX also announced a simplified upgrade offer for owners of earlier Sound Forge versions through December 5, 2026\. That date ends the offer; the perpetual version you bought doesn't expire with it. A perpetual license lets you keep using the purchased version after its included support term ends. Under the [Boris FX Upgrade & Support policy](https://support.borisfx.com/hc/en-us/articles/10334870429709-What-is-the-Upgrade-Support-Plan-What-is-U-S), purchases include 12 months of upgrades and support, with automatic renewal that you can manage or cancel in your account. Keeping the licensed version is different from receiving every future release for free. Check the renewal settings as well as the purchase price. ## The Trial Is the Right Final Test The [official Sound Forge trial](https://vfx.borisfx.com/sound-forge-trial) is 15 days, full-featured, requires no credit card and runs on Windows. Installation and activation go through Boris FX Hub. Don’t spend the trial learning with random files. Use a short checklist built from the work you already do: 1. Open a representative file and complete one precise edit. 2. Run the analysis or restoration step you actually need. 3. Load the third-party plug-ins required by your workflow. 4. Save or batch-export to the real delivery format. 5. Reopen the exported file and verify duration, channels, sample rate, bit depth, loudness and peak as applicable. 6. Close and reopen the application, then confirm presets and device routing survived. That test tells you more than a feature matrix does. It also catches compatibility problems that a generic review can't reproduce on your interface, driver and display. ## Sound Forge vs the Alternatives | Choose | When the job is mainly | Main trade-off | | ----------------------- | -------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------ | | **Sound Forge** | Windows file editing, recording, analysis, mastering and batch delivery | No multitrack session and no current Mac version | | **Adobe Audition 26.3** | Multitrack audio, spectral selection, Match Loudness and Premiere exchange | Subscription-only; some file-only users do not need the session layer | | **iZotope RX 12** | Advanced spectral repair, dialogue isolation and difficult restoration | Specialist restoration pricing; not a full replacement for every recording or mastering workflow | | **Audacity 4.0** | Free, cross-platform recording and general editing | Audacity 4.0 omits Macro Manager and the scripting pipe; check version-specific needs | | **REAPER** | Multitrack production, routing, automation and a customizable DAW | A track-and-item session model rather than a dedicated single-file workspace | [Adobe's current release notes](https://helpx.adobe.com/audition/desktop/introduction/audition-releasenotes.html) identify Audition 26.3 as the June 2026 version, not 26.0\. RX 12 Standard and Advanced include the standalone editor, while Elements is a smaller plug-in collection and shouldn't be compared as if it had the full RX editor. For a free alternative, check the [Audacity 4.0 compatibility notes](https://www.audacityteam.org/changelog/): the September 3 release doesn't include Macro Manager or the scripting pipe. That matters if batch automation is why you're looking at Sound Forge. Audacity still edits audio perfectly well. For the detailed decisions, use our current [Sound Forge vs Adobe Audition](https://soundforgepro.com/sound-forge-pro-vs-adobe-audition/), [Sound Forge vs RX](https://soundforgepro.com/sound-forge-pro-vs-izotope-rx/) and [Sound Forge vs Audacity](https://soundforgepro.com/sound-forge-pro-vs-audacity/) comparisons. Don't buy Sound Forge on the assumption that a DAW can't batch-export: [REAPER documents batch conversion and queued rendering](https://www.reaper.fm/about.php). Compare the same editing and delivery task in both. The decision comes down to workflow, since neither one has exclusive export capability. ## Who Should Buy Sound Forge? **Buy it if** you use Windows, most jobs resolve to one audio file, exact editing and repeatable export matter, and the trial confirms your drivers, plug-ins and display work correctly. It is particularly sensible for restoration archives, voice assets, sample libraries, finished mixes, transfers and delivery folders. **Skip it if** you need macOS, MIDI, track-based production, collaborative sessions, or advanced spectral restoration as the center of the job. Don’t buy Plus for a longer feature list if you will never open Melodyne, Vandal, VariVerb II or 3D Reverb. **Upgrade carefully if you own an older version.** An editor that still launches doesn't mean you need the current plan. Upgrade for a named compatibility fix, tool or support requirement. If your existing build already does the work and the new plan doesn't solve a real limitation, keeping it is a perfectly rational choice. ## What the 4.2/5 Editorial Rating Means The 4.2/5 score is an editorial judgment. It isn't a user aggregate, a measured benchmark or an arithmetic average. It reflects the documented file-editing, recording, processing and licensing options, weighed against the platform and workflow limits. The reasons below explain the judgment. | Category | Editorial assessment | Reason | | --------------------------------- | ------------------------------ | --------------------------------------------------------------------------------------------------------------------------- | | **File editing controls** | Strong fit | Direct waveform, sample-level and event-based editing remain the strongest part of the product. | | **Recording and batch delivery** | Strong fit | Triggered recording, prerecord buffering, multichannel files and Batch Converter cover demanding repeatable jobs. | | **Analysis and processing depth** | Broad tools, specialist limits | Statistics, meters, plug-in chains and common repair tools are broad, though RX remains deeper for spectral restoration. | | **Compatibility and usability** | Platform and usability limits | Windows 11 is the published supported baseline, and the dense interface narrows the audience and makes the trial essential. | | **Value and plan fit** | Depends on plan and workflow | Perpetual licensing and a capable base plan help, but Plus and upgrades only make sense for specific tools or fixes. | | Overall editorial judgment | 4.2/5 | Not an arithmetic average of category scores. | The score is deliberately conditional. A Windows editor who spends all day on individual files may value the first three categories more heavily and rate Sound Forge higher. A Mac user or multitrack producer should stop at the compatibility or workflow boundary instead of averaging past it. ## Bottom Line Sound Forge has passed through several owners without losing its useful core idea: put one audio file in front of the editor, with selection, processing and output controls in the same workspace. Boris FX has preserved the perpetual option, simplified the lineup and kept the current toolset broad enough to cover capture, repair, processing, analysis and delivery. The weak points are just as lasting. It's Windows-only, it isn't a multitrack DAW, it trails RX for serious spectral restoration, and it's easier to appreciate once you already know where everything lives. Those trade-offs underpin the **4.2/5** editorial judgment; there's no equal-weight calculation behind it. For the right user, its dedicated file-editing workflow is a reason to try it alongside a DAW. For the wrong user, it is an expensive detour on the way to the DAW or restoration suite they should have bought first. Use the trial to find out which user you are. ## Frequently Asked Questions ### Is Sound Forge worth buying in 2026? Yes for Windows users who mainly edit, repair, analyze, record or batch-process individual audio files. No if you need a multitrack DAW, native macOS support or RX-level spectral restoration. ### Is Sound Forge a DAW? No. Sound Forge can record and edit multichannel audio files, but it does not provide a multitrack arrangement, MIDI sequencing, independent track automation and the session workflow of a DAW. ### Does Sound Forge run on Mac? No current Mac version is listed. Sound Forge 2026 and its trial are Windows-only. ### How much does Sound Forge cost? Boris FX’s March 2026 announcement listed the base plan at $24.95 monthly, $149.95 annually or $299.95 perpetual, with a separate $189.95 Upgrade & Support path for eligible legacy owners. These are announced US launch prices, not a live checkout quote. Sound Forge Plus costs more; verify the current price, eligibility and tax before paying. ### What does Sound Forge Plus add? Sound Forge Plus includes the base application plus Melodyne 5 Essential, Vandal, VariVerb II and 3D Reverb. The base plan already includes the main waveform, repair, metering, recording and batch features. ### How long is the Sound Forge free trial? The official trial is 15 days, full-featured, Windows-only and does not require a credit card. Installation and activation use Boris FX Hub. ### Who owns Sound Forge now? Boris FX acquired Sound Forge, Vegas Pro and Acid Pro from MAGIX on March 30, 2026. Documentation checked September 9, 2026\. Feature and license claims were compared with the linked vendor sources.