Category: Blog

Your blog category

  • How to Send Large Audio Files Through Email: Caps and Fixes

    Key takeaways

    • Gmail caps attachments at 25 MB and Outlook at 20 MB, so most lossless WAV masters and stem folders will not fit as email attachments.
    • FLAC or ALAC compresses a WAV to roughly half its size with no quality loss, making it the right format for emailing masters that fit under the cap.
    • WhatsApp and Messenger transcode audio sent as media, so attach files as Documents or paste a cloud link to keep quality intact.
    • Above 100 MB, or for any folder of stems, use a dedicated transfer tool like WeTransfer or an audio portal instead of an attachment.
    • Verify delivery by comparing file sizes or running an MD5 or SHA-256 checksum on the sent and received files.

    You can send large audio files through email up to Gmail’s 25 MB attachment cap, which fits a single MP3 but almost never a lossless master or a folder of stems. For anything bigger, compress to a zip and stay under the cap, or upload the WAV and email a download link from WeTransfer or a dedicated audio transfer app instead.

    What is the maximum audio file size you can email through Gmail and other providers?

    Email providers cap attachments well below the size of a single mix. Gmail allows 25 MB per attachment and automatically switches to a Google Drive link if you go over. Outlook caps at 20 MB. Apple Mail and Yahoo sit in the same range, though Apple adds Mail Drop for larger files.

    That math matters because lossless audio is heavy. A 3-minute stereo WAV at 44.1 kHz/24-bit runs roughly 85 MB, and a folder of dual-mono stems multiplies that fast. No email provider on the list comes close.

    ProviderAttachment capWhat happens over the cap
    Gmail25 MBFalls back to a Google Drive link
    Outlook20 MBBlocks the send
    Yahoo Mail25 MBBlocks the send
    Apple Mail~20โ€“40 MBOffers Mail Drop upload

    The cap is confirmed in Google’s Gmail help documentation, which also describes the Drive fallback.

    For a client who only needs a streaming preview, a link works. For a collaborator who needs lossless masters, you need a transfer route built for audio, such as a branded portal like Audio Portal or a general service like WeTransfer.

    How do you compress a large audio file without losing quality before emailing it?

    ZIP is lossless but saves little on WAV; FLAC or ALAC cut size roughly in half with no quality loss; MP3 and AAC trade quality for size and should only carry previews. Which one fits depends on whether the client needs the master or just an approval.

    ZIP a WAV: when it helps and when it does not

    Zipping a WAV or AIFF keeps every bit intact, but the gain is small. PCM audio is already dense, so a zipped mix might shrink by a few percent, sometimes less. ZIP makes sense for bundling a session folder of stems into one attachment, not for shrinking a single master under Gmail’s 25 MB cap.

    FLAC and ALAC: lossless halving for masters and stems

    FLAC (and ALAC if your client lives in Apple’s ecosystem) compresses losslessly, typically landing around half the original WAV size. A 24-bit/96 kHz master that blows past email limits as a WAV often fits comfortably as FLAC. When you decode it back to WAV, the checksum matches. This is the right format for delivering masters and stems where lossless matters and the recipient can handle the format.

    MP3 and AAC previews: acceptable for approval, never for delivery

    A 320 kbps MP3 or AAC file is a fraction of the WAV size and fine for client approval on earbuds or a car stereo. It is not a master. Send the preview, then deliver the lossless file once the mix is signed off.

    How do you send large audio files through WhatsApp and Messenger when they exceed the size limit?

    Both apps cap media uploads well below the size of a single lossless mix, let alone a folder of stems. WhatsApp compresses anything sent as media, and Messenger behaves similarly. The workaround in both is to stop treating your audio as media and send it as a file, or skip the app entirely with a cloud link. For reference on where email caps sit too, Microsoft documents a 20 MB attachment limit for Outlook (Microsoft Support).

    WhatsApp: document send vs. media send and what it does to your audio

    Sending a WAV as media means WhatsApp transcodes it to a lossy format, which is fine for a rough bounce and useless for a master. Attach the same file as a Document instead and it arrives byte-for-byte. On Android, tap the paperclip and choose Document; on iPhone, use the plus button, then Document, then browse to the file. Stems sent this way keep their original quality, though WhatsApp still applies its own per-file cap.

    Messenger: limits and the cloud-link workaround

    Messenger offers no document mode on most accounts, so a large WAV either fails to upload or gets compressed. The practical route is uploading to Drive or Dropbox and pasting the link into the chat, which keeps the transfer lossless and gives the client a download instead of a streamed preview.

    How do you send large audio files from an iPhone using Mail, iCloud, or a transfer app?

    Mail Drop: what it does above the attachment cap

    iPhone Mail caps attachments at 20 MB. Anything bigger triggers Mail Drop, which uploads the file to iCloud and pastes a download link into the email instead. The recipient gets a link that works for 30 days, and the file itself never touches the mail servers. Note that Mail Drop counts against your iCloud storage, and it needs the upload to finish before you hit send, so a 2 GB master can take a while on hotel Wi-Fi.

    Sharing from Files and Voice Memos without quality loss

    WAVs in Files share fine: long-press the file, tap Share, and pick Mail, Messages, or AirDrop. For lossless delivery, AirDrop to a nearby collaborator beats email outright since nothing gets compressed. Voice Memos defaults to compressed M4A, so open the memo, tap Share, and choose uncompressed WAV if the recipient needs to work from it.

    Sending from a transfer app on iPhone

    Most transfer apps work from Safari, but a dedicated app handles background uploads better: start the upload of a 3 GB stem folder, lock the phone, and it keeps going. This is where a branded portal earns its keep โ€” clients get a link that looks like yours, with folder-level access and preview-only options for mixes.

    When should you use a cloud link instead of attaching an audio file to an email?

    Decision flow by file size and quality need

    Under 20 MB, attach the file. A single MP3 bounce or a short preview WAV usually fits inside Gmail’s 25 MB limit, and the client gets it with zero extra clicks.

    Between 20 and 100 MB, compress to FLAC or zip the WAV, or move to a link. If the recipient needs lossless, a link to the original file beats a compressed attachment every time.

    Above 100 MB, or anything resembling a folder of dual-mono stems, use a dedicated transfer tool. For reference on where messaging caps sit, WhatsApp documents top out at 2 GB per the WhatsApp Help Center on document sharing limits. Email caps are far lower, so multi-gig stem folders never belong in an attachment.

    What generic cloud links miss for audio work

    Dropbox and WeTransfer move the file, but they treat a 24-bit master like a PDF. No streaming previews, no version history across mix revisions, no preview-only links that stop a client from downloading the unmastered rough.

    That gap is why we built RockScience Audio Portal: branded transfers, streaming previews, folder-level access, and collaborators handled in one place. Honest limitation: it is web-based, so it will not help you text a file over WhatsApp.

    Dedicated audio tools such as Filepass, Boombox, Samply, and Audome exist for the same reason. Pick whichever fits your margin, but stop sending stems as email attachments.

    Which app to send large audio files is best for phone users?

    Comparison criteria for audio transfer tools

    Judge any transfer app on five things: how big a file it accepts, whether clients can stream a preview before downloading, whether the page carries your studio’s name, how you handle revisions, and what it costs monthly. Messenger caps attachments at 25 MB, so anything beyond a rough MP3 sketch needs a dedicated tool (Meta Messenger Help). WeTransfer handles the size problem but gives you a generic page and no version history. Filepass, Boombox, Samply, and Audome are built for audio, with streaming previews and client feedback, and each prices for working engineers rather than teams.

    How RockScience Audio Portal holds up against the same criteria, including where it falls short

    The honest rundown: RockScience Audio Portal is a branded portal you run under your own domain, so clients land on your studio’s page instead of a WeTransfer splash screen. You get streaming previews, preview-only links, folder-level access for collaborators, and version history on mixes and masters, which matters when a client asks for “the one from Tuesday.” It handles lossless stems and dual-mono stems without compression, and the Pro tier sits at $9/month, priced for solo engineers billing per project. Where it falls short: there is no native mobile app, so sending from your phone happens through the browser, and the free tier’s limits are tighter than WeTransfer’s. If you only send one file a month, a plain WeTransfer link is cheaper and fine. If you send revisions weekly and want every delivery on brand, the portal earns its keep.

    How do you keep audio quality intact when sending large files from your phone?

    Stop apps from transcoding your WAV on share

    iOS and Android both try to help by shrinking files on share. Mail Drop on iPhone and most messaging apps will offer to compress a WAV or convert it to AAC before it leaves. Always pick “Keep Original” or share the file from the Files app rather than exporting from your DAW’s mobile companion or a voice memo app, which bakes in a lossy export before the transfer even starts.

    Check the sample rate and bit depth before you send. A 48kHz/24-bit master viewed in Files should show the same specs on the receiving end. If your client opens a 128kbps MP3 when you sent a WAV, the conversion happened on your phone, not theirs.

    Verify what arrived matches what you sent

    The cheapest check is file size. Note the exact byte count before sending, then compare against what the recipient sees. If the numbers match, the file did.

    For a proper check, run a checksum. Apps like Hashstream or a terminal on the receiving machine give you an MD5 or SHA-256 hash; matching hashes mean bit-identical audio. For client-facing sends, a branded transfer portal keeps the original untouched and shows the file size on the download page, so verification takes seconds instead of a support email.

    FAQ

    Can I email a WAV file, or do I need to convert it first?

    You can email a WAV if it fits under your provider’s cap, which Gmail sets at 25 MB and Outlook at 20 MB. Most full-quality WAVs exceed that, so convert to FLAC for a lossless half-size file, bounce a 320 kbps MP3 for approval, or upload the WAV and email a download link instead.

    Why does my audio sound worse after sending it through WhatsApp?

    Because WhatsApp treats files sent as media like photos or video and transcodes them to a lossy format before upload. Attach the same file as a Document instead, using the paperclip on Android or the plus button on iPhone, and it arrives byte-for-byte. For anything beyond WhatsApp’s per-file cap, paste a cloud link.

    How many MB is a 5-minute song, roughly?

    A 5-minute stereo WAV at 44.1 kHz/24-bit runs roughly 140 MB, which no email provider accepts as an attachment. The same song as a 320 kbps MP3 lands around 12 MB and fits Gmail’s 25 MB cap easily. FLAC typically cuts the WAV size roughly in half with no quality loss.

    Is WeTransfer free for sending audio to clients?

    Yes, WeTransfer’s basic tier is free and handles files far larger than any email attachment cap, which makes it a workable default for occasional sends. The tradeoffs are a generic download page, no streaming previews, and no version history across mix revisions. If you deliver revisions weekly, a dedicated audio portal is worth comparing.

  • How to Share Mix Revisions With Clients

    Key takeaways

    • Every mix revision should include a labeled bounce, revision number, date, short reference notes, and a stated feedback deadline.
    • Use a zero-padded naming convention like SongName_v03_2025-01-14_vocalup.wav and never overwrite an old bounce.
    • Send streaming preview links for early rounds and reserve 24-bit WAV delivery for final sign-off.
    • Collect timestamped comments in one channel per song instead of assembling notes from texts and emails.
    • State the included revision count and the price per extra round in your quote before the first bounce leaves your studio.

    Knowing how to share mix revisions with clients comes down to one system: a single branded link that carries both a streaming preview for quick listens and a lossless download for final approval, with every version labeled by date and revision number. That replaces the WeTransfer-and-SoundCloud patchwork, keeps feedback in one thread, and makes each round easy for the client to play back consistently.

    What should you include when sending a mix revision to a client?

    A mix revision needs five things: the labeled bounce, the revision number, the date, short reference notes on what changed, and a deadline for feedback. Skip any one of them and you invite a second round that exists only because the client was guessing.

    The revision bundle checklist

    • Labeled bounce in the format your client can actually play, at the quality you agreed on.
    • Revision number and date in the filename: SongName_v03_2025-01-14.wav.
    • Reference notes: three bullet points on what you changed and what you want their opinion on.
    • A feedback deadline, stated plainly, so the round closes instead of drifting.

    Host the bundle somewhere the client can stream it without downloading, with a preview-only link if they are early in the process. A portal like RockScience Audio Portal keeps every round in one branded place, so version history lives with the audio instead of in your sent-mail folder.

    Why a naked MP3 link creates more rounds

    A bare link with no notes forces the client to reconstruct context from memory. They hear one thing, you meant another, and the round produces comments on parts you already fixed. Most streaming apps also normalize loudness, so if your client evaluates on a streaming app, tell them that in the notes. Context in the bundle is cheaper than an extra revision round.

    How do you label and version mix revisions so nothing gets confused?

    The fix is two things: a naming convention both sides use, and one place where every version lives. When a client texts “the chorus one,” you need to know exactly which bounce they mean.

    A naming convention that survives email and text threads

    Use this pattern on every export:

    SongName_v03_2025-01-14_vocalup.wav

    That gives you the song, the revision number (zero-padded so v10 sorts after v9), the date, and a short note on what changed. No spaces, no parentheses, nothing that breaks in a text message or gets mangled by a download manager. When you change something, the number goes up. Never overwrite v02 to make v03; the old bounce is your proof of what the client approved.

    Keeping a version history the client can see

    Your version history can’t live only in your session folder. If the client has to dig through a WeTransfer email chain to find the latest bounce, they will reference the wrong one. Keep every revision in one folder the client can open, newest at top, so both of you point at the same file. RockScience Audio Portal does this with folder-level access and version history under your own branding, and Filepass and Boombox offer similar client-facing versioning. Where a plain Dropbox link falls short is labeling: it shows filenames, not which revision is current, so say “latest is v04” in the message itself every time.

    Which file format and streaming quality should clients use to evaluate a mix?

    Match the format to the stage: streaming previews for rounds one and two, lossless WAV only when the client is signing off. A 320 kbps-style stream is fine for judging balance, vocal level, and arrangement notes, but it hides exactly the things a final approval rests on: cymbal decay, low-level reverb tails, and the top end of a master.

    Preview-only links for round one

    Send a streaming preview link, not a download, for early revisions. Previews stop the client from dragging your mix into their phone’s music library and judging it against commercial masters, and they make it obvious which version is current. Label the link with the revision number so “the one from Tuesday” never enters the conversation.

    Lossless for the final pass

    For sign-off, send a 24-bit WAV at your session’s native sample rate. Uncompressed formats preserve the full signal chain without codec artifacts, which is why most delivery specs name WAV or another lossless format for masters. The point for your client is simpler: the file they approve should be the file you deliver, bit for bit, so nobody approves one bounce and receives another.

    Confirming the client hears the same master you do

    The risk in the preview stage is loudness normalization. Phone players and some browser players turn tracks up or down automatically, so your client may hear a different level than you bounced. Ask them to listen on one consistent setup, note which device they used, and if their notes mention a level problem you cannot reproduce, request a screenshot of their player or a quick call. A separate preview-only link keeps this stage contained instead of leaking full files into every revision round.

    How do you collect consolidated feedback instead of scattered notes?

    Scattered feedback is the fastest way to miss a note. A text at 11pm, a voicemail the next morning, and an email with “also the vocal feels a touch loud in the second chorus” means you’re assembling the revision list yourself, and something always slips. One channel, one song, one list.

    Timestamped notes beat paragraph emails

    Ask clients to comment at the moment they hear the problem, not after. “2:14 โ€“ snare too loud” takes them five seconds and takes you zero interpretation. Paragraph emails force you to scrub the timeline guessing where “that bit” is. A timestamp turns vague notes into an actionable list, and it makes patterns obvious: three comments at the drop means the drop needs work.

    One feedback channel per song

    Pick a single place for notes per song and say so in your delivery message. If the client insists on texting, you transcribe their notes into the channel yourself so the list stays complete. Tools built for this, like Filepass, Boombox, Samply, Audome, or our own RockScience Audio Portal, let clients comment directly on the waveform, so notes land with timestamps attached instead of in your inbox.

    When should you send a bounce versus a full session export?

    Bounces for approvals, sessions for handoffs

    Send a stereo bounce whenever the goal is approval: revisions, mix checks, mastering previews. The client listens and gives notes; nobody needs the raw material. A full session export is for handoff, when another engineer will keep working on the material. If you are the last set of hands on the project, the client never needs the session.

    Stems and dual-mono stems: when they’re actually needed

    Stems earn their place when the client’s engineer will re-balance, edit for picture, or print alternate versions. Dual-mono stems matter for live sound and broadcast delivery, where L and R need independent processing. If the deliverable list does not name stems, do not bounce them; they double your render time and invite unauthorized edits.

    One honest caveat: most client-facing portals, including our own Audio Portal, are built around bounces and streaming previews, not session handoff. For stem bundles, a transfer tool like WeTransfer or a direct portal such as Filepass still fits the delivery step.

    Which sharing method fits which client and revision stage?

    The decision framework

    Match the method to the client and the stage, not to whatever you used last time.

    MethodBest forStage
    Streaming preview linkClients judging balance and level on their own speakersRough mixes, early revisions
    Branded transfer portal (RockScience, Filepass, Boombox, Samply, Audome)Stems, lossless masters, version history, consolidated commentsApproved direction, final delivery
    Generic transfer (WeTransfer)One-off bounces for a hands-off clientAny stage, no feedback needed
    Session exportCollaborators with their own DAWOnly when they’ll actually open it

    Run each row through the same test: does playback stay consistent, is feedback in one place, and is the version label unambiguous? Generic transfer fails all three, which is fine for a client who never sends notes and never confuses files.

    Where a branded portal fits, and where it doesn’t

    Honest take on our own tool: RockScience Audio Portal wins on folder-level access, preview-only links, and dual-mono stem delivery under your own branding, at $9/mo. It does not replace a session export, and a client who just wants an MP3 in their inbox gains nothing from a portal login. For that client, WeTransfer is the right answer, not a compromise.

    How do you handle endless revision requests without scope creep?

    Endless revisions die the moment your quote says how many are included. State a number, state the price per extra round, and put both in writing before the first bounce leaves your studio. Solo engineers absorb the cost of vague terms, because every “one more tweak” lands on a fixed fee. A written deliverable count is the cheapest insurance you can buy.

    Setting the revision count in your quote

    Two or three rounds is the common norm for mix and master work, but the number matters less than the boundary. Write it plainly: “Includes two revision rounds. Further rounds billed at $X per round.” Also define what counts as a round, because a client sending ten notes over three days is one round, not ten.

    A copy-paste revision request template

    Send this with every bounce:

    Round 2 notes, please send by Friday:

    1. Timestamp + what to change
    2. Timestamp + what to change

    This is revision 2 of 3 included in the quote. Additional rounds are $X.

    The template does three jobs at once: it forces consolidated feedback, it labels the version, and it shows the remaining count without you having an awkward conversation. Clients who see “2 of 3” self-police.

    What does a complete revision round look like, start to finish?

    Worked example: one song, three rounds

    Round 1: you bounce v1 at 16-bit/44.1 WAV, label it SongTitle_v1_2024-06-03, and send a preview-only link so the client can stream it without downloading. Feedback comes back consolidated in one place: vocals up 1 dB in the choruses, snare too bright. Round 2: you print SongTitle_v2_2024-06-06, note the changes in your version history, and send it with the same link structure; the client approves the vocal level but flags the low end. Round 3: SongTitle_v3_2024-06-09 fixes the low end and the client signs off. You deliver final masters plus dual-mono stems through the same branded portal, so every version of the song lives under one roof instead of scattered across a transfer service and a NAS. Three rounds, three labeled bounces, zero confusion about which mix is current, and the whole exchange fits in one thread your client can reopen a year later.

    FAQ

    How many mix revisions should I include for free before charging extra?

    Two or three rounds is the common norm for mix and master work. The number matters less than writing the boundary into your quote before the first bounce leaves your studio: “Includes two revision rounds. Further rounds billed at $X per round.” Also define what counts as a round, so ten notes over three days is one round, not ten.

    Is it okay to send mix revisions over SoundCloud private links?

    It works for a quick listen, but you lose control of the details that prevent extra rounds. SoundCloud shows no version history, no revision labeling, and no consolidated feedback thread, so “the one from Tuesday” enters the conversation. A branded portal keeps every round in one place with preview-only links; a private link is fine for a hands-off client who never sends notes.

    What bit rate should a client preview a mix at before final approval?

    A 320 kbps-style stream is fine for judging balance, vocal level, and arrangement notes during rounds one and two. Final approval should happen on a 24-bit WAV at your session’s native sample rate, because lossy streams hide exactly what sign-off rests on: cymbal decay, low-level reverb tails, and top-end detail. The file they approve should be the file you deliver.

    How do I ask a client for feedback on a mix without getting vague notes back?

    Ask for timestamped comments at the moment they hear the problem, not a paragraph email afterward. “2:14 โ€“ snare too loud” takes five seconds and needs no interpretation. Send a short template with every bounce that lists the revision number, the deadline, and how many rounds remain. Pick one feedback channel per song and transcribe anything that arrives by text.

    Should I send stems or a mix bounce when the client wants changes?

    Send a stereo bounce. Revisions are an approval process, and the client only needs to listen and give notes. Stems earn their place when the client’s engineer will re-balance, edit for picture, or print alternate versions. If the deliverable list does not name stems, do not bounce them; they double your render time and invite unauthorized edits.

  • File-Sharing Application Used to Share Audio Files

    File-Sharing Application Used to Share Audio Files

    File-Sharing Application Used to Share Audio Files

    Key takeaways

    • Audio-specific platforms like Filepass, Boombox, Samply, and Audome deliver bit-identical WAV and FLAC downloads with in-browser streaming previews.
    • WeTransfer passes files through untouched but offers no streaming previews, version history, folder-level access, or branded delivery pages.
    • RockScience Audio Portal offers branded delivery on your own domain, preview-only links, and version history at $9/mo on the Pro tier, though it lacks watermarking and a mobile app.
    • Test any tool with your worst-case delivery, a full album of 24-bit WAVs, to confirm files arrive bit-identical and within size caps.
    • A $9/mo plan pays for itself on a single mix revision cycle if you bill per project, while per-transfer pricing suits fewer than one or two deliveries a month.

    If you deliver mixes and masters to clients, the right file-sharing application predominantly used to share audio files is one that handles lossless WAV and FLAC transfers, offers preview-only links, and puts your studio’s branding on every delivery instead of WeTransfer’s. This guide compares Filepass, Boombox, Samply, Audome, WeTransfer, and RockScience Audio Portal on those criteria, with a scoring matrix and an honest look at where each one, including ours, falls short.

    What makes a file-sharing application suitable for audio files specifically?

    Generic transfer tools treat your mix like a zip of photos. They were built to move bytes, not to play a 24-bit WAV back to a client or put your name on the delivery page.

    What generic tools get wrong for stems and masters

    WeTransfer handles big files but gives clients a download button and nothing else: no streaming preview, no version history, no folder-level access per collaborator. SoundCloud previews compress your master. SFTP to a NAS works but looks like a server error page to whoever is paying you.

    The four criteria that matter: fidelity, size, preview, brand

    Judge any file-sharing application predominantly used to share audio files on four things: lossless delivery with no transcode, headroom for full album stems, in-browser streaming previews, and a client-facing page on your own domain. Tools like Filepass, Boombox, Samply, and Audome publish pricing against these criteria, as does RockScience Audio Portal at $9/mo for its Pro tier.

    Which audio file-sharing tools handle large WAV and FLAC transfers without compression?

    Most generic transfer tools re-encode previews or cap file sizes in ways that matter once you’re moving a full album of 24-bit WAVs. The question to ask any tool is simple: does the recipient download the exact bytes you uploaded?

    Format fidelity: what actually arrives at the other end

    Audio-specific tools like Filepass, Boombox, Samply, and Audome are built around lossless delivery: the streaming preview is a convenience layer, and the download stays bit-identical. WeTransfer also passes files through untouched, but it treats a 90MB WAV the same as a PDF, so no playback, no versioning, no context. RockScience Audio Portal keeps downloads lossless too, and streams previews for quick client checks. The honest caveat: preview quality and codec handling vary between platforms, so verify with your own dual-mono stems before committing a client delivery to any tool, ours included.

    Size ceilings and album-scale transfers

    ToolLossless downloadAlbum-scale stems
    FilepassYesBuilt for it
    BoomboxYesBuilt for it
    SamplyYesBuilt for it
    AudomeYesBuilt for it
    WeTransferYesSize caps apply
    RockScience Audio PortalYesYes

    Per-file ceilings differ by plan on every platform, so check the tier you’d actually pay for, not the marketing page.

    How do the major audio transfer tools compare side by side?

    The comparison matrix

    Score every tool on the same five criteria: lossless format fidelity (does it touch your WAV or FLAC?), file size ceiling, preview-only links, version history for mixes, and whether the delivery page carries your branding.

    Filepass, Boombox, Samply and Audome are built for audio, so preview playback and client comments come standard. WeTransfer moves large files fast but renders no streaming previews and puts its own brand on every download page. Before trusting any of them with a master, check the vendor’s own documentation on supported formats and size limits. RockScience Audio Portal scores on the same sheet: your domain, your logo, preview-only links, folder-level access for collaborators, and version history on every mix round.

    The honest scoring matters more than the scores themselves. A tool that passes stems through re-encoding, or caps a session folder at a size smaller than one album’s dual-mono stems, fails before branding even enters the conversation. Run your own worst-case delivery, a full album of 24-bit WAVs, through each tool’s free tier and watch what arrives on the other side. If the file that lands differs from the file you exported, nothing else on the feature list compensates. This single test catches more problems than any feature matrix, because vendors document best cases and you deliver worst cases. Ten minutes of uploading your heaviest session folder tells you more about a platform than an afternoon of reading pricing pages, and it costs nothing on every free tier listed here.

    Where RockScience Audio Portal falls short

    It is a smaller operation than the named competitors, so it lacks some polish you may expect: no mobile app, a lighter review and approval layer, and fewer integrations with your DAW-adjacent tooling. If your delivery depends on timestamped client comments pinned to a waveform, test that flow against Samply or Audome before committing. Where it wins is the part no patchwork stack gives you: every link a client opens is on your brand, at $9/mo on the Pro tier.

    How do pricing tiers compare across audio-focused transfer platforms?

    Most audio-focused tools charge monthly, with tiers split by storage, transfer volume, and whether you can put your own logo on the delivery page. Filepass, Boombox, Samply, and Audome all use this model. RockScience Audio Portal sits at $9/mo for its Pro tier, which covers branded transfers, streaming previews, and folder-level access for collaborators.

    What a solo engineer actually needs to pay for

    If you bill per project, you need three things: lossless transfers without size penalties, preview-only links so clients can’t download a rough mix, and your branding on the page the client opens. You do not need team seats, per-user pricing, or storage you’ll never fill. Anything charging extra for white-label is charging for the one feature that wins repeat clients.

    Per-project cost vs monthly subscription

    Run the math against your project rate: a $9/mo Pro plan pays for itself on a single mix revision cycle. If you deliver fewer than one or two projects a month, a per-transfer option like WeTransfer may cost less, but you give up version history, on-brand delivery pages, and audio-specific previews. Monthly wins once delivery is regular work.

    How do audio transfer tools integrate with review and approval workflows?

    A transfer link that just dumps a ZIP on your client creates the same loop every time: they download, listen somewhere else, email you timestamps, and the revision thread lives outside any tool. Audio-specific platforms try to fix that with previews, comments, and version tracking in one place.

    Streaming previews vs download-only links

    WeTransfer is download-first; the client grabs the file and plays it in whatever player they own. Filepass, Boombox, Samply, and Audome stream your mix in the browser, so a client can approve a master from their phone without installing anything. Some also watermark streamed previews, so if an unapproved mix leaks you can tell where it came from. Check each vendor’s docs before you commit: Filepass documents its watermarking, expiry, and folder-level access features, and the equivalents for Boombox, Samply, and Audome sit on their own sites.

    Version history and revision rounds

    RockScience Audio Portal keeps version history per project, so mix v4 sits next to v3 and the client’s comments stay attached to the right one. Honest limitation: it has no watermarking, so if preview-only leak protection is a must, run a dedicated tool alongside it.

    What security and expiry controls matter when delivering audio masters to clients?

    Expiry and access controls on unreleased material

    Unreleased masters leak through links that live forever. Set an expiry date on every delivery so the link dies after the client has pulled the files, and require a password on anything going to a label or artist before release day. Folder-level access matters too: your client should see their album, not the three other projects sitting in the same directory.

    If you are on SFTP to a NAS today, you already have the security but not the controls. Expiry and per-folder permissions have to be configured by hand, per client, every time.

    Preview-only links before release

    Before a master is approved, the client does not need the WAV. A preview-only link streams a low-latency version and blocks downloads, so rough mixes can circulate to band members without a bounced copy ending up on SoundCloud. RockScience Audio Portal supports streaming previews and download-gated delivery on your own domain; Boombox offers comparable preview flows, so check which one matches how you bill.

    When should a business choose a generic file-sharing app over an audio-specific one?

    When generic tools are fine

    If you send one-off files to collaborators who already live in Dropbox, or you’re moving a quick reference bounce that doesn’t represent your brand, WeTransfer is the faster path. Free transfers, no account setup for the recipient, done in two minutes. The same goes for internal moves: if you’re shuttling sessions between your own machines, SFTP to your NAS costs nothing and stays lossless.

    When the branded portal pays for itself

    The moment a client opens a delivery link, that page is your brand. A generic download page says “this engineer uses the same tool as everyone else.” A branded audio portal with folder-level access, preview-only links, and version history says you deliver masters the way a studio does, not a teenager sending homework.

    RockScience Audio Portal runs on your own domain, handles lossless formats, and starts at $9/mo on the Pro tier per the product page. If you bill per project, one client who rebooks because the delivery felt professional covers the month.

    What is the fastest way to move a full album’s stems to a client?

    A worked example: 10-track album delivery

    Say a 10-track album lands as roughly 80 stems at 24-bit/48kHz WAV, about 12GB total. Set up one folder per song, with subfolders for dual-mono stems, rough mixes, and printed masters. Name files with a fixed scheme: 01_SongName_Kick_L.wav so the client’s DAW session imports in order.

    Upload the folder structure once, keeping it intact, so folder-level access lets the client browse by song instead of digging through a flat list. Then generate two links: a streaming preview link for quick listens on the phone, and a download link for the full lossless stems.

    Run the same check you would on any tool: does it keep WAVs bit-identical, does it cap your 12GB upload, and does the link carry your studio’s branding? RockScience Audio Portal handles that size and branding on the $9/mo Pro tier, though it won’t replace a client’s DAW-side review the way a dedicated feedback tool might. If your current route is zipping the album to WeTransfer, you already know the failure mode: no version history and a link that expires mid-revision.

    FAQ

    Is WeTransfer good enough for sending WAV files to mixing clients?

    It moves WAVs through untouched, so the bytes arrive intact. What it lacks is everything around the file: no streaming preview, no version history, no branding, and no folder-level access. If you send one-off transfers to collaborators who already know you, it’s fine. For regular client deliveries, it looks like everyone else’s download page.

    Can clients stream my mixes without downloading the files?

    Yes, on the audio-specific platforms. Filepass, Boombox, Samply, and Audome all stream mixes in the browser, so a client can approve a master from their phone without installing anything. RockScience Audio Portal also streams previews and can gate downloads entirely. WeTransfer is download-first, so the client grabs the file and plays it locally.

    How much should a freelance mastering engineer spend on file delivery each month?

    If you bill per project, a plan around $9/mo pays for itself on a single mix revision cycle. You need lossless transfers, preview-only links, and your branding, not team seats or storage you’ll never fill. If you deliver fewer than one or two projects a month, a per-transfer option may cost less, but you lose versioning and branded pages.

    Do any audio transfer tools watermark unapproved mixes?

    Yes. Some audio-specific platforms watermark streamed previews, so if an unapproved mix leaks you can trace which client link it came from. Filepass documents watermarking among its features, and Boombox offers comparable preview flows. RockScience Audio Portal does not watermark, so pair it with a dedicated tool if leak protection on previews is essential.

    What’s the cheapest way to share stems with a collaborator in another country?

    For internal moves between your own machines or trusted collaborators, SFTP to a NAS costs nothing and stays lossless, though it lacks expiry controls and looks bare to clients. WeTransfer handles free one-off transfers with no recipient account. Once you need folder structure, version history, or a branded page, a paid audio portal becomes the better route.

  • On the Down-Low: Building a DIY Studio Subwoofer

    On the Down-Low: Building a DIY Studio Subwoofer

    For years I’ve mixed primarily on a pair of Focal Solo6 monitors.


    I love the clarity and detail. They’re excellent speakers with plenty of low end for near field monitors. In fact, I never felt like I needed a subwoofer. Obviously I had a bit of a blind spot in the lowest octave but it really never caused me to do anything too dumb in the low end on my mixes.

    recording studio

    But lately, I’ve been working on a lot of modern Reggae Music with my band, Noetic Sea. This genre features heavy low-end and I found that on some of my reference mixes, I was going a little bit over the top with the deepest tones of the kick and bass. I would only learn that during the car test which is not the most clinical listening environment. I decided I wanted to eliminate or reduce that blind spot and at least get another half octave or so in the studio below where the Solo6 monitors naturally begin to roll off.

    More Rumblings of Change

    The second clue came from a couple of outdoor live recordings of my band.

    The recordings were made from the front-of-house mix and supplemented with a stereo room capture using the built-in X-Y microphones on a Tascam DR-40 (without a windscreen). A small amount of wind created significant low-frequency rumble.

    Back in the studio, I applied filtering and thought I had removed it but out in the car, there was still a massive amount of rumble… way down there.

    Subwoofer Painted

    DIY Subwoofer – Design Goals

    I wasn’t looking for a subwoofer that would shake the room or impress clients. I wanted a subwoofer that would subtly extend the response of the Solo6 monitors a little further into the bottom octave while remaining essentially invisible.

    This project documents the design and construction of a compact sealed subwoofer built around a Peerless XXLS 10″ driver and a DSP-powered plate amplifier.

    My priorities were:

    • Small footprint
    • Sealed enclosure
    • Musical rather than theatrical
    • Very low crossover frequency
    • DSP control
    • Clean integration with the existing monitors
    • Ability to design and build it so I could learn something and have an interesting project.

    Enclosure Design

    The enclosure was designed as a sealed cabinet with approximately 37 liters of internal volume. The external dimensions are 17″ ร— 15″ ร— 14″. The speaker is front facing. Simple.

    Why sealed?

    A sealed box provides:

    • Better transient behavior (not that I care about that in a sub)
    • Simpler construction
    • Much simpler design and avoiding endless trial and error of tuning a port.

    The downside of a sealed box is efficiency, but per my design goals, I am just looking for a very subtle extension of the focals and since the subwoofer would be crossed over very low, efficiency wasn’t a concern. The upside of not having to deal with the complexities and trial/error of tuning a port far outweighed this. 37 liters of volume gave a decent curve in WinISD. In Hindsight, as long as I was going with 37, I might as well have gone to 43 liters. That would have extended the range only a few Hz but when you’re talking about 30 Hz, a “few” is pretty significant.

    Driver Selection

    After experimenting with several drivers in WinISD, I narrowed the choices to:

    • Dayton RSS265HF
    • Peerless XXLS-P835037

    Either would have worked well, but the Peerless was available from DigiKey for about $111 compared to nearly $200 for the Dayton. I’m cheap like that.

    The Peerless XXLS offered:

    • Excellent reputation
    • Long linear excursion (I was going to come close to the limit of either driver)
    • Plenty of Power Handling

    Amplifier

    For the Amplifier, I wanted a plate amplifier with balanced inputs and built-in DSP for setting up filters, etc. The Dayton Audio SPA250DSP was an obvious choice. As of this writing (oct 2026), they are on clearance at parts-express so maybe they won’t be available anymore. It has the power and features I needed and it was about $270.

    The 250 in the name means it’s a 250w, which is plenty.

    The SPA DSP is purpose-built as a subwoofer amplifier. It takes in a stereo balanced signal (xlr or trs), sums it to mono, has some fancy DSP and a twisted pair of wires for the driver. It has built-in DSP for Low and High Pass Filters, Subsonic filter, Parametric EQ and as well as other delay and phase parameters. There is as USB port for programming it with a GUI but I had no luck getting that to work. Fortunately, there is a rotary encoder and LCD display that lets you easily program and store anything you need.

    What I found interesting about this amplifier (as in disappointing) is that the High Pass filter had a minimum fc of 30Hz. The “subsonic” filter only goes to 25Hz (I wanted 10). More on this below.

    Cabinet Construction

    subwoofer cabinet build
    First Test fittings of the pieces

    This cabinet was built out of 3/4″ birch plywood using fairly basic woodworking tools.

    I don’t own a table saw.

    All straight cuts were made using a circular saw and a straight-edge cutting guide

    The driver opening and plate-amp opening were cut using a jigsaw.

    The driver and amplifier were fastened in with M4 tee nuts and Phillips screws

    The cabinet panels were glued together with internal corner supports and secured using an electric brad nail gun.

    I’m a hack. My goal wasn’t a furniture-grade showpiece. My goal was a functional studio tool. Besides, it is mostly hidden under my studio desk anyway.

    Parts List

    • Peerless XXLS-P835037 Driver
    • Dayton SPA250DSP Amplifier
    • 3/4″ Birch Plywood (2 2×4 sheets were enough)
    • Rockwool or similar Insulation
    • M4 Tee Nuts
    • M4 Screws 8mm length
    • Wood Glue
    • Wood Fasteners
    • Paint/Primer or other Finish

    The finished enclosure came out far better than I expected and looks completely at home in the studio.

    Internal Construction

    The enclosure is fully sealed and lined with Rockwool damping material.

    The cabinet volume was chosen based on modeling for the selected driver, resulting in a compact enclosure with smooth low-frequency extension and excellent integration with the main monitors.

    I did not put a stiffening “window brace” in this cabinet as my AI overlord suggested. It would have theoretically damped the box resonance, but it also would have robbed me of some internal volume (and been a bit of a pain to do). In operation, the box feels incredibly “still” and stiff so I think it’s fine for this size enclosure. If I went much bigger, I would probably stiffen it.

    The Result

    The most interesting thing about the finished subwoofer is that it doesn’t really call attention to itself.

    The Focals still sound like Focals.

    I use the Dangerous Music M-Box+ monitor switcher which allows switching in a sub. Turning it on gives the focals just a tiny extra something down there that sounds really nice.

    When the low end is over the top in the car, it’s now over the top in the mix room too and that’s exactly what I was hoping to achieve.

    Studio Subwoofer
    My partially hidden sub blocking the view of The Who album art on my sound panel

    Listening Impressions

    The biggest success of the project is that the subwoofer doesn’t sound like a subwoofer.

    The Solo6 monitors already provide excellent bass. What the sub adds is a sense of scale and weight in the lowest frequencies.

    The deepest tones of the kick and bass can be judged much more accurately now.

    Most importantly, my monitors still sound like the Focals I know and love.

    Cone excursion is well within the 19mm max specified for the Peerless – even at higher than normal listening levels. I’m definitely well within the design limits of the amplifier and driver.


    Measurements

    I’m a by ear guy, I set up REW with my dbx reference mic to take some measurements.

    The graph below shows the low-frequency response of the Focals alone (blue), the subwoofer alone (purple), and the combined system (red).

    Yes, there is a little hump now at the bottom of the Focal’s range, but you can clearly see the extension of about half an octave with the sub engaged.

    The exact shape of the room response is less important than the fact that the sub extends the system by approximately half an octave while remaining well integrated with the Solo6 monitors

    REW Plot studio room

    The Amplifier is set up with a Lo Pass filter at 40Hz with a 24db/Oct slope. I have adjusted the relative volume of the sub to taste and I’m sure I’ll still be tweaking as I do more mixes with this system. My design in WinISD dictated a Hi Pass filter at 10Hz but it turns out that this is not possible with the Dayton amp. The HiPass only goes down to 30. It also has a subsonic filter, but that has a minimum frequency of 25Hz. This seems a bit strange for a purpose built subwoofer amp. I ended up switching on the subsonic filter at 25Hz with a 12db/Oct rolloff. Without it, the sub had quite a bit more cone excursion and the room response was still above 70db below 10Hz.


    Final Thoughts

    This project started as a small experiment and ended up being one of the most enjoyable DIY audio projects I’ve completed. And it was actually a pretty easy project.

    The final result wasn’t a “cheap subwoofer.” Total cost was about 550 USD plus my extremely valuable time. There are several good choice one could buy off the shelf in that price range. This is probably a better subwoofer than those choices but they probably would have been good enough for my purpose.

    The project achieved exactly what I hoped it would. The goal wasn’t to make the studio sound bass-heavy. The goal was to make low-frequency decisions in the studio translate more reliably to other listening environments.

    For anyone curious about loudspeaker design, DSP, or studio monitoring, a small sealed subwoofer is an excellent entry point into the world of DIY speakers.

  • We Don’t Need No Stinking Badges!

    We Don’t Need No Stinking Badges!

    We have a

    I used to dress up the mics with with Laser-Cut Nickel Badges. It looked cool. But if I’m honest: it was also the most stressful, anxiety-inducing part of the whole build.

    Bending, aligning, and epoxying badges was a delicate game of โ€œdonโ€™t screw this up.โ€ One slip and the whole mic body had to be stripped or scrapped. I had bending jigs (various PVC Pipe pieces) for each mic body. The trick was to slightly over bend the badge (but not too much). I was spending way too much time playing arts & crafts when what I really wanted to do was focus on the guts.

    Because the gutsโ€”the capsules, transformers, and circuitsโ€”have always been the point. And that hasnโ€™t changed one bit.

    Enter the Laser

    Starting September 2025, epoxied-on badges are retired. Every RockScience Mic now ships with:

    • A laser-engraved RockScience logo
    • A permanent build configuration code, so youโ€™ll always know whatโ€™s inside
    YouTube player

    A short video of an MXL770 Getting the Logo and Switch Icons

    It took a few ruined mic bodies and hours of testing to dial in laser settings for all the variations of material, color and diameter for all of the mics I work on. But now the process is clean, precise, and consistent. And yes, I look very relaxed in my green safety glasses standing next to the Omtech galvo fiber laser. Those “mistakes” will most likely end up in my mic locker – the same way the mechanic always has the most beat up car.

    Omtech Galvo Laser
    Is that a peace sign or 1/2 Air quotes? Can it be both?

    I spent time dialing in laser settings for black, blue, green paint on aluminum and brass – as well as settings for bare metal for aluminum and brass and anodized aluminum. For most of this, I used scrap pieces of metal to work out the settings. The laser reacts to all of these very differently so it’s a matter of tweaking the power, speed, frequency and number of passes for each variation.

    YouTube player
    YouTube player

    That’s good TV right there


    The Build Config Codes

    This is actually the coolest part for me. I can’t tell you how many times I’ve had to open up a body during a session to remember which mic had which transformer or which was a TL, etc.

    The format is

    [CAPSULE][CIRCUIT].[VARIATION]

    Section Code Meaning
    Capsule Type 47 K47-style capsule
    12 CK12-style capsule
    Electronics TL Transformerless
    TC Transformer-coupled
    Transformer Variation C Cinemag
    A AMI
    3 3U Audio
    N Neutrik (lo-fi)

    Examples:
    12TC.A โ†’ CK12 capsule, transformer-coupled with AMI
    47TL โ†’ K47 capsule, transformerless
    47TC.C โ†’ K47 capsule, transformer-coupled with Cinemag


    About the Finish

    I’ve got the laser looking great on Black, Blue, Green and bare metal. For the painted surfaces, the black shows the graphics with the most contrast – especially on aluminum mic bodies. For black anodized bodies like the 770, I’m suggesting sanding and applying a finish coat of the flat black (this covers up the usually dinged-up switch logos anyway). The laser cuts through the paint and the anodizing and it looks great. The blue seems to work about as well as the black. Green took a bit longer to dial in because it seemed to need a bit more power – but too much power and the metal underneath gets dull. It’s a balance.

    No more Red. Red was always a problem color. It always took the longest to dry and cure and it seemed to be the softest and most easily dinged up color. I did one quick experiment with the laser and the results were not exciting. So it’s off the market for now.

    As for bare metal, we need lots of power to really cut some material. To get the engraving to show up well, we have to actually burn the body a little bit. The trick is to do that just enough to show up but not so much that things get fuzzy. Again – lots of time have gone into figuring this out.


    The Guts Havenโ€™t Changed

    This is important: the electronics, capsules, and mods are exactly the same. The only thing thatโ€™s different is how the mic looks on the outside.

    So if you already own a RockScience mod with a badge or paint, donโ€™t worryโ€”youโ€™ve got the same great guts. You just own a piece of RockScience history from the arts & crafts era.

    The future, though? Itโ€™s laser-etched.


    ๐Ÿ”ง Nerd Alert: The Laser

    For those who like to peek behind the curtain: Iโ€™m using an Omtech 20W Galvo Fiber Laser with a Rotary Chuck to do all engravings. Powered by LightBurn, itโ€™s basically the โ€œDAW for lasers.โ€ Settings have to be tuned for each mic bodyโ€™s finish โ€” stainless, brass, painted aluminum. The diameter and taper of each mic body has to be carefully meassured โ€” and Iโ€™ve wrecked more than a few bodies figuring it out.

    Hereโ€™s a little LightBurn screenshot for the curious. This is the file for a painted 990

    Laser For Hire

    I’m not going into the engraving business, but Iโ€™m considering opening up this laser engraving as a service for other DIY-ers. Got a body you want marked with your logo or config? Let me know โ€” if thereโ€™s enough interest, Iโ€™ll make it a thing.

    Want one of these?

    Every mic I build is laser-engraved with its build code: rebuilds of your mic from $179.00, or custom builds in brand-new bodies from $319.00.

  • MXL 770: Finally it’s a YES

    I never get over feeling excited when an inquiry comes in about a mic rebuild. But a certain number of them turn sad when I realize they are asking about an MXL 770.

    The 770 is an extra tall version of the 990 but the cool thing is that it has switches for Pad and Filter functions. The 770 (like the 990) is a Transformerless Schoeps-style mic with the same (or similar) small capsule as the 990. It also comes with all the same shortcomings.

    mxl 770 transformer converted with K47 and cinemag transformer

    I’ve wanted to do a Transformer-Coupled board for the 770 for a long time. There were two technical hurdles to overcome for me to design the board:

    • Sourcing switches that would fit on the board and extend through the body.
    • With all the room that those switches take up, figuring out where to put the transformer.
    Both sides of the BFM770. The pad and filter switches line up with the holes in the body

    Fitting it all in

    Since the 770 does not have a separate switch board like the Sterling ST55 or MXL 5000, it’s necessary to fit both external switches on the main board with all the other parts. Of course, I also wanted room for the optional pattern switch. The problem is that those switches take up a lot of real estate. The solution was to mount the switches on the bottom and most of the other parts on the top. But that still leaves no where to fit the transformer.

    some tweaks for v1.02 after the initial run. This is ready for production.

    Transformer Daughter Board

    Fortunately, the transformer mounting board that I already had for other common mics fits in the space and already has mounting holes for some stand-offs.

    Production Ready

    The 770 is now fully supported and available for rebuilds (your mic) or pre-mods (my mic) in the store. I’ve managed to find a few bodies on ebay and have built a few up in various configurations. One of them is now my new favorite in the studio for vocals. I am pretty sure that all this will work with a 990-s (s for “switch”) and the 990 “patriot” which also has switches. I’ll keep my eye out for donors and try it out.

    Want this done to your MXL 770?

    I rebuild 770s as transformer-coupled mics with working pad and filter switches, and your choice of transformer and capsule. Hand-built, tested, and shipped within 7 days of your mic arriving.

  • Transforming the MXL 5000: A RockScience BFM Rebuild with Custom PCB & Transformer Options

    Transforming the MXL 5000: A RockScience BFM Rebuild with Custom PCB & Transformer Options

    Introduction

    The MXL 5000 is a sleeper hit in the world of affordable large-diaphragm condensers. With a sturdy metal body, a well-designed headbasket, andโ€”unlike many budget micsโ€”built-in pad and high-pass filter switches, itโ€™s already a solid contender. But what if we could elevate it even further?

    Iโ€™ve been refining the BFM (Big F’m Microphone) circuit, a design inspired by the Neumann KM84, and now Iโ€™m bringing it to the MXL 5000. This isnโ€™t just a component swapโ€”itโ€™s a complete circuit replacement, featuring transformer-coupled output and a custom PCB that fully utilizes the micโ€™s existing pad and filter switches!

    mxl 5000 mod
    The BFM-5000 board

    As usual, I’m offering multiple transformer options (Cinemag, Tab-Funkenwerk, or 3U Audio) and your choice of capsule (CK12 or K47 style), allowing you to fine-tune the micโ€™s character to your taste. This board also has the optional internal Pattern switch to select Cardioid or Omni modes. The body must be opened up to access it, but on those occasions when you want an OMNI, it’s nice to have that trick.

    In this post, weโ€™ll break down why this mod takes the MXL 5000 from “good” to studio-grade exceptional.

    mxl 5000 on stand
    Finished 5000 with CK12 style Capsule and AMI Transformer

    Why Modify the MXL 5000?

    The stock MXL 5000 is no slouchโ€”itโ€™s built like a tank, has a decent k67 style capsule and external switches on its TL circuit. But like many budget transformerless mics, it is over-bright, sibilant and harsh.

    Our BFM rebuild addresses key limitations:

    • Transformerless stock circuit โ†’ Now transformer-coupled for added depth, weight, and vintage vibe.
    • Basic FET amplification โ†’ Upgraded with low-noise, hand-selected transistors for better clarity.
    • Generic capacitors/resistors โ†’ Replaced with premium WIMA, polystyrene, and metal film components for improved signal integrity.
    • Capsule flexibility โ†’ Choose between CK12 (bright, open) or K47 (warm, smooth) styles.

    The Circuit: KM84-Inspired BFM Design

    The BFM board is a refined take on the Neumann KM84โ€”a circuit renowned for its balanced midrange, smooth highs, and natural tonality. There is very little in the audio path in that circuit: FET->Capacitor->Transformerโ€”that’s it!

    Transformer Options: Pick Your Flavor

    As usual, you can choose your transformer, each imparting a unique character:

    • Cinemag  โ€“ Clean, detailed, with a slight midrange push.
    • Tab-Funkenwerk  โ€“ Vintage-style warmth, reminiscent of old Telefunken mics.
    • 3U Audio  โ€“ A modern take with a slightly lighter low end.

    This flexibility lets you tailor the mic to your preferred tonal profileโ€”clinical and accurate? Warm and colored?

    Capsule Choices: CK12 vs. K47

    This build allows a choice of two capsule styles, each suited for different applications:

    • CK12-style โ€“ Brighter, more open, with enhanced presence. Great for vocals that need air or acoustic instruments.
    • K47-style โ€“ Warmer, smoother, with a slight low-mid richness. Ideal for darker voices, electric guitars, or bass-heavy sources.

    Component Upgrades: Whatโ€™s Inside?

    A great circuit is only as good as its parts. Hereโ€™s what weโ€™re using to maximize performance in all of our BFM builds:

    • Polystyrene Capacitors โ€“ Critical for clean high-frequency response.
    • Low-noise metal film resistors โ€“ Reducing thermal noise for a blacker background.
    • Selected FETs โ€“ Hand-biased for optimal distortion characteristics.

    Sound Comparison: Stock vs. Modded

    Stock MXL 5000:

    • Decent clarity but can be slightly harsh in the upper mids.
    • Transformerless circuit โ€“ Lacks low-end weight and harmonic richness.
    • Good features (pad/HPF), but the electronics limit its potential.

    RockScience BFM Mod:

    • Smoother, more balanced highs โ€“ No harshness, just detailed air.
    • Transformer-enhanced lows โ€“ Fuller, more controlled low-end.
    • Lower noise floor โ€“ Cleaner signal for critical recordings.
    • More “pro” vibe โ€“ The KM84-inspired circuit adds a touch of vintage Neumann magic.

    Best Uses for the Modded MXL 5000:

    โœ… Vocals (especially with the K47 capsule for warmth)
    โœ… Acoustic Guitar (CK12 for sparkle, K47 for body)
    โœ… Drum Overheads (transformer helps with punch and depth)
    โœ… Kick Drum – with K47 (get your 47FET mojo)
    โœ… Electric Guitar Cabs (K47. The pad handles high SPL with ease)



    Final Thoughts

    The MXL 5000 has always been a solid platform, but with the RockScience BFM treatment, it becomes a true studio workhorse. Whether you want a vintage-voiced vocal mic (Tab-Funkenwerk + K47) or a detailed acoustic instrument mic (Cinemag + CK12), this mod delivers.

    Ready to transform your MXL 5000?
    ๐Ÿ“ฉ Contact us for pricing and lead times.
    ๐Ÿ› ๏ธ Check out our Mod Services page for more details.


    Whatโ€™s Your Dream Mic Combo?

    CK12 + Cinemag for clarity? K47 + Tab-Funkenwerk for vintage warmth? Let us know in the comments!

    Want this done to your MXL 5000?

    I rebuild the MXL 5000 with my BFM transformer-coupled circuit and your choice of transformer and capsule. Hand-built, tested, and shipped within 7 days of your mic arriving.

  • Avoiding Common Issues Taking AWS Certification Exams

    Avoiding Common Issues Taking AWS Certification Exams

    I just sat for the AWS Certified Cloud Architect Exam. And I even passed!

    Pivoting to the software development side of RockScience, Here are some lessons learned around taking AWS Certification exams.

    You’ve spent weeks or months studying and taking practice exams, building your own practice infrastructure and it’s finally time to sit for the exam. The last thing you need right now is a logistical gotcha. Here are some tips to avoid those.

    Call me Robert

    When you sign up for certifications at https://aws.amazon.com/certification/, you will be asked to create a Builder ID. This is where you set up the account for your certifications. This account info is then propagated to Pearson who actually administers the proctored exams.

    When I did this, as usual my browser auto filled me as “Bob” and I just went with it as usual. MISTAKE!!!! The key here is to enter your name exactly as it appears on the identification document you are going to use (drivers license, passport, etc).

    When I took the Cloud Practitioner exam, the proctor didn’t catch the discrepancy between my account name and the name on my license (Robert). I took (and passed) that exam. When it was time to sit for the Solutions Architect exam, the proctor bounced me because of the name mismatch.

    Here’s the problem – if I didn’t already have any exam history, I would have been able to self-serve the name change in my account. But because the first proctor let me slide, the name could no longer be changed without opening a ticket with AWS. What a pain. On the other hand, it gave me more time to study. The issue was sorted within two days (and lots of back and forth), but it was a real hassle. On top of that, not only could I not use the voucher from the first exam to get half off, I had to pay full price again for the exam. So instead of $75, it was $225! I probably could have fought that, but was too exhausted and stressed by then.

    Running the system check

    DO run the system check! You don’t want any surprise on exam day. I suggest setting up your testing area exactly as it will be (I suggest even doing this for the practice exams). Make sure you have power, good internet and your wireless mouse is well charged up. You can’t have multiple monitors. If you have them, take them away so there is only on on the desk. If you are not doing this on a laptop, make sure your webcam wire is long enough that you can walk around your testing area (they will ask you to do this at check in).

    The system test is going to look for applications and services that shouldn’t be running. Things like Dropbox and other sharing apps will be tagged. You need to figure out how to stop them running.

    On a windows 11 laptop, one annoying one is going to be “tabtip.exe”. What the heck is that? It’s the virtual keyboard that pops up when you are using your laptop as a tablet. If you stop that in the task manager, windows re-launches is immediately. Here’s how to stop it. In settings, set this to “Never”. I burned up a few hours figuring this one out.

    Download the system check each time you want to run it!

    An interesting thing about the system check app, is that you download an instance of it for each time you want to run it. If you go to your downloads folder and just rerun the same instance again, it will almost succeed but will mysteriously fail the network check. That wasted a few panic stricken hours the night before my first exam. The key is to just follow the link from your email and download a new instance if you want to run it again.

    Check in Procedure

    This is fairly straightforward. You can start the process 30 minutes before your scheduled exam and if you get through it quickly, you can start the exam early. Take off your watch (see below)

    You are prompted to take photos of your test area, a photo of your ID document and confirm your system settings (again). When you are done with your mobile phone and your ID, you are told told that from then on, you are being recorded and must follow the exam rules – including that you can not leave the field of view of your webcam. Your phone and ID card have to be out of arms reach, but you also may need them again if there is an issue. So when you are done with the phone, put it out of arms reach but in a place where you can get it while staying on camera.

    Follow all the other rules too. Make sure the space is quiet around you. If they hear any voices (yours or anyone else), they will revoke the test. Schedule your test accordingly.

    The Queue and the Greeter

    You will be shown your position in the queue. It’s not unusual to be 10th-ish in the queue but it goes by pretty quick. Soon you will be Up Next! and a popup message from the greeter will say they are going to call you through the computer. You say OK and a voice chat starts. Here is where they ask you to pick up your laptop (or other webcam) and show the whole testing area once again. Then they’ll be asking you to show on the webcam that you are not wearing a watch. I’m sure that soon, you’re going to have to prove that you’re not wearing any kind of “smart” glasses.

    Within a couple minutes, you are in the test. Hopefully you are ready and pass with a great score.

    Learning Tips

    This post is mostly about avoiding logistical issues, but I have some thoughts on how to study for this too. First of all, I highly recommend the Udemy courses and in particular the ones by Stรฉphane Maarek. But it can’t hurt to buy one of the other instructors’ courses too. They are cheap! I bought two courses and I also bought the set of practice exams from Stรฉphane. In total, I had six practice exams. My suggestion is to take the first one without looking up anything (cheating) to get a baseline. If you do great, then great! If you’re like me, you barely passed. For the subsequent exams, I did them as “open book” and I looked up and learned details right then and there for any questions I had doubts about. I think this made a huge difference for me.

    Are the practice exams realistic?

    This is the big question. I passed every single one… until the very last one (the morning of exam day). That one was massively harder than any of the others and I failed it miserably. That gave me a psychological whammy to deal with. For me, the real exam was maybe just slightly easier than the average of the practice exams. But that’s just my impression and I wouldn’t count on it!

    Good Luck! Build something cool! Hire me to help!

  • SDC Mics: Say hello to my little friends

    SDC Mics: Say hello to my little friends

    I’ve been building Transformer Coupled LDC mics for a while now. My BFM (Big F’n Microphone) circuit is adapted from the Neumann KM-84 (kleines Mikrofon – 84) circuit with very minor differences from the original. I have finally gotten round to building some SDC mics with another adaption of the BFM circuit called the TFM (Tiny F’n Microphone).

    sdc mic mod

    Donor Bodies

    Donor bodies are plentiful for these mics. From MXL alone, there are 551, 991 603s and 840 (and maybe more). The 551s and 991s are usually in a set with a 550 or 990 respectively, but sometimes we can find them alone.

    TFM Circuit

    The TFM really is pretty tiny. There is not a lot of wiggle room on the board – especially when a large chunk of the board is taken up by the Transformer. Fortunately the KM48 and our derivation of it is a very simple circuit and within a few revisions of the board, everything is fitting and working out well. As with the LDC bards, the capsule and FET wiring is off board and using Keystone insulated turrets for the point-to-point wiring.

    sdc mic mod km84

    Transformers and Capsules

    I’ve been building my BFM boards with either CineMag or AMI transformers, but will now be offering the 3U GZT-84 Transformer. The tone is slightly brighter than the CineMag or AMI and it it seems to have a bit more harmonic distortion in the low frequencies than the others. And this is largely what gives transformer mics their sound.

    For capsules, I am offering options from 3U Audio. Their capsules come in several polar patterns apart from the standard cardioid and they sound amazing. Because the capsule is easily field-replaceable, you can get several capsules for your mic and swap in the one that is appropriate for what you are trying to capture.

    Want a KM84-style SDC?

    Send me your small diaphragm mic for a transformer-coupled rebuild from $199.00, or get one built from my stock from $229.00. Hand-built, tested, and shipped within 7 days.

  • New Microphone Footprints Afoot

    New Microphone Footprints Afoot

    Since I’ve been building and rebuilding microphones, I’ve only imported one type of body – the so-called BM800 style body. These are what I’ve been using for the RS/ series mics like the RS/47, RS/12t and RS/47t.

    I’ve been tempted to try some other shapes and sizes that I see on my various suppliers’ websites and I finally acquired a few samples of some new styles. New shapes mean new Circuit Boards and I’ve finished jaSb (just another Schoeps board) transformerless and BFM (Big F’n Microphone) transformer-coupled board designs for both new bodies.

    The Tall Boy Telefunken-ish style

    custom mic build

    When I ordered this thing, the photo didn’t do justice to how huge it is! First impressions are that it’s a nice quality body with a heavy cylinder and a good quality headbasket. The Internal frame is much bigger than a BM-800 style and so the circuit board is nice and big. The jaSb and BFM boards were very easy to design for this mic given all the space. In both cases, all components can fit on one side and in the case of the BFM, there is actually room for the transformer right on the main board!

    The TLM 102 Style

    custom mic build

    I was really excited to find a good source for these. I’ve always loved the look of the “little” Neumanns and I occasionally get asked about rebuilding a TLM mic (or a TLM clone). Until now, I had no circuitry that would fit. The samples arrived and I’m really happy with them. The cylinder is solid and heavy and the headbasket is beautiful.

    In terms of size, this is the extreme opposite of the Tall Boy. These are tiny and the the circuit board layouts were very challenging – especially the transformerless jaSb version which has many more parts.

    Unlike most of my other builds, these mics are not so straightforward to open. The headbasket is fastened to the body with three hex set-screws. For that reason and because of the limited size of the board, I’m not going to fit the optional internal pattern switch in theses. They will be full-time cardioid (or omni if you wanted). The board is round like an MXL 990 but only 47mm in diameter (with some notches cut out) compared to the 53mm diameter of the 990 board. Besides losing the pattern switch, I had to put some components on the bottom side for both boards.

    Want one of these?

    I build custom mics in brand-new imported bodies, transformerless from $319.00 or transformer-coupled from $339.00. Hand-built, tested, and laser-engraved with the build code.