Screen Studio 4.0 and Loom Problems in October and November 2026: How to Fix Each One
Failed exports, quiet microphones, missing recording controls and higher Loom bills, from public reports in October and November 2026. What is fixed, what is still open, the workarounds users and vendors posted, and the most reliable fix: switch to ScreenKite.
Short answer: the most reliable fix is to switch to ScreenKite. Screen Studio 4.0 shipped on October 1, 2026. The changelog lists updates through 4.1.0, build 5005, dated October 21. No entry in those notes names the audio-parts export error users posted in October. 4.1 adds a Loud microphone mode after users reported quiet recordings. Loom users posted higher bills after billing moved to Atlassian, and LOOM-1051 still lists recording controls that do not appear. If you came here to finish a video today, record it in ScreenKite. If you want to keep your current tool, every reported problem and every sourced workaround is below.
ScreenKite is free to use. Every editing feature is free. Free exports carry a watermark and an outro. One payment of $99.99 removes them, covers 3 devices and never renews. Native macOS and native Windows. Try ScreenKite
The quick list
| Problem | Reports | Status on November 7, 2026 |
|---|---|---|
| Screen Studio: export fails with an audio error | A Hub thread with a second user, plus a post on X, all in October before 4.1 | No changelog entry names this error |
| Screen Studio: long or overnight batch exports fail | Two users on X, before 4.1 | Export fixes in 4.0.2, 4.1 and build 5005 do not name overnight batches |
| Screen Studio: microphone too quiet in 4.0 | Two users on X in October, before 4.1 | 4.1 adds a Loud mode. Those reports are not named as fixed |
| Screen Studio: gray preview on Intel Macs with AMD graphics | Confirmed by the team on October 10 | Fixed in 4.1 |
| Screen Studio: microphone audio behind the video | Listed by Screen Studio | Fixed in 4.1 |
| Screen Studio: split moves the cut back | One user, November 3 | Open. No changelog fix |
| Loom: bill jumped after the Atlassian move | Many users on X | Atlassian says you cannot keep the old price |
| Loom: recording controls do not appear in the new desktop app | Atlassian bug LOOM-1051 | Short Term Backlog. The ticket says a fix is being deployed |
| Loom: audio missing from a finished recording | One post on X and one Capterra review | Not marked fixed |
| Loom: videos over 30 minutes download heavily compressed | Atlassian suggestion LOOM-1042 | Gathering Interest. The ticket describes this as current behavior |
Screen Studio 4.0 problems
Screen Studio 4.0.0 shipped on October 1, 2026, followed by 4.0.2 (October 5), 4.0.3 (October 6), 4.0.4 (October 7), 4.1.0 (October 21) and build 4.1.0-5005 (October 21), per the Screen Studio changelog. Several of the problems below have a fix in one of those releases, so the first step for any of them is to install the latest version.
Export fails: "Something went wrong while trying to put together the audio parts"
What happens. The export stops with an error about the audio. On the Screen Studio Hub, Alexander Komanov reported on October 7, on version 4.0.4: "Can't export due to the following error: Something went wrong while trying to put together the audio parts" (Hub).
How widespread. A handful of public reports, all before 4.1. A second user added to the same Hub thread on October 20, and @lantianlaoli posted the same error on X on October 15.
Status. The 4.1 changelog fixes a case where "An export could stall or fail while Screen Studio was still analyzing your recording" (changelog). Build 4.1.0-5005 says "Fixed exports getting stuck at the start of some recordings." Neither entry names the audio parts error. The Hub status for this report is In Review.
What helped. The second user on the Hub thread wrote: "also have this issue trying 4k studio exports, getting it after restarting the app and computer etc, HD works ok but not 4k." If you can deliver in HD, that is the one export setting a user reported working.
Long exports and overnight batch exports fail
What happens. Longer exports fail where short ones finish.
How widespread. Two users on X, both before 4.1. @HariBonda wrote on October 7: "Since v4, parallel batch exports frequently crash/fail overnight, unlike stable v3."
Status. Screen Studio 4.0.2 "Resolved export issue with decoding frames", and 4.1 fixed exports that could "stall or fail" while the app was still analyzing the recording. Build 4.1.0-5005 fixed exports getting stuck at the start of some recordings (changelog). None of those lines names overnight batch exports. Update to the latest version.
What helped. The same day, @lantianlaoli reported: "I reduced the time duration from 15 minutes to 7 minutes, and the export was successful" (X).
4K exports show the background above the recording
What happens. In 4K exports the background could appear on top of the screen recording.
Status. Fixed in 4.0.4: "Fixed a bug that caused a background to appear above screen recordings in 4K exports" (changelog). Update to 4.0.4 or later.
Export quality looks worse than Screen Studio 3
What happens. One Hub post from October 9 compares the same project exported in 4.0 and 3.7.5: "On these same settings, the quality of the video output differ drastically" (Hub).
How widespread. One public report. Its Hub status is In Review. No fix is listed in the changelog.
The microphone records too quietly
What happens. Voice comes out quieter than system audio after the move to 4.0.
How widespread. Two users on X reported low volume in October, both before 4.1. @HariBonda wrote on October 4: "v3.7 had enhanced mic volume v4.0 mic volume is low compared to system volume, it is not being enhanced or normalized during export." A third user, @direwolfram, asked on October 8: "Was the Improve microphone audio removed in the latest version?" That question is about a missing control, not a third report of low volume. The same account that posted the October 17 quiet-audio note had described a MacBook Air M5 on October 2 (X), so that report is not an Intel Mac report.
Status. No changelog entry says those low-volume reports were fixed. 4.1's notes add two microphone modes: "Loud boosts your voice to a consistent, loud volume. Off plays your microphone as recorded." The same 4.1 changes say: On an Intel-based Mac, "Microphone audio mode" now appears with Standard, Loud, and Off (changelog). The Screen Studio 4 page says: "Microphone audio mode" replaces "Improve microphone audio." It also says: "On an Intel-based Mac, or with macOS 13 or earlier, Microphone audio mode doesn't appear." The page and the 4.1 notes do not describe Intel the same way.
Microphone audio plays behind the video
What happens. In new recordings the voice lags the picture, and the waveform drifts around cuts.
Status. Fixed in 4.1: "Microphone audio in new recordings played slightly behind the video." and "The audio waveform drifted out of place, and playback glitched around cuts." (changelog). Update to 4.1 or later.
The screen or camera does not record, or the preview is gray on an Intel Mac
What happens. On October 6, Daniel J. Lewis asked whether others saw only audio and zoom ranges recorded, with no screen or camera.
How widespread. A few users. On October 10 a Screen Studio team member replied to another user: "Please try the latest beta. We've had an issue with Intel Macs that have an AMD GPU" (X).
Status. Fixed in 4.1 for the preview the notes name: "The preview was gray on some Intel-based Mac computers with AMD graphics" (changelog). The same release notes say: "Camera cutout requires a Mac with Apple silicon and macOS 15 or later." The October 6 report, only audio and zoom ranges recorded, is not the gray-preview line the 4.1 notes name. Daniel J. Lewis also wrote that he had already emailed Screen Studio's team.
Recording stops by itself, or the camera stops after pauses
What happens. @JourneymanChina wrote on October 13 that a recording sometimes stops on its own, and called it a fatal problem for a screen recorder. @imaadmalikk wrote on October 2 that "it crashes mid recording takes 3 tries to export."
How widespread. Individual reports on X.
Status. 4.1 fixed one specific case: "The camera could stop recording after you paused a recording many times" (changelog). No entry covers a recording that stops for no stated reason.
Saving fails or a project is damaged
Status. Fixed. 4.1 lists "Saving failed when you renamed or deleted a project while it was being saved" (changelog). The Screen Studio 4 page lists as fixed "A project could be damaged when a save was interrupted." and "A new project replaced an existing project with the same name."
Split at the playhead moves the cut back
What happens. On November 3, @muneeb_builds reported an error and added: "split on current time moves the cut about 2 to 3 seconds back."
How widespread. One report. Kaya Gorczyca, in Screen Studio support, replied the same day and offered a DM or an email to [email protected] so the team could look into it. No fix is listed in the changelog.
Going back to Screen Studio 3
@HariBonda asked on October 16: "Is there a way to roll back to v3?" Before you try, read the Screen Studio 4 page: "Projects you save in Screen Studio 4 don't open in Screen Studio 3." and "Zooms in projects from Screen Studio 3 might show a different part of your recording." It also lists three removed settings: "Snap to edges", "Always keep zoomed in" and "Advanced motion blur settings".
One-time licenses are no longer sold
Screen Studio's FAQ answers "What happens if I purchased a one-time license in the past?" with three statements: "Your license is of course still valid." "If your access to the latest updates and features is expired, you can still renew your license at any time to restore your access to the latest updates and features." "Note: purchasing one-time licenses was possible in the past, but is no longer available for new purchases." (screen.studio)
One user described the expired-update case. On October 13, @JourneymanChina wrote that he checked for an update, found his license had expired, and would have to pay again to upgrade.
ScreenKite is one payment of $99.99 for 3 devices and never renews. More on the 4.0 pricing change in Is Screen Studio 4.0 Worth It If You Don't Want a Subscription?
Loom problems
The bill jumped after the move to Atlassian
What happens. Loom accounts were moved onto Atlassian billing. Atlassian's support page says: "The Creator Lite role is discontinued; Creator Lite users are upgraded to full Creator seats (with a grace period before you're billed)." and "Existing customers are moving to current Loom list prices" (Atlassian Support).
How widespread. Users posted about higher bills through October and early November. Other posts on X: @kevinschrage "Went from $15 to $96/month without warning" (October 6), @suganthan "Thanks for this 228% price increase" (October 13), @Rpaulindaigle "from $60/mo to $634/mo" (October 26) and @JoshJDurham "auto added my whole company and autocharged me without consent" (November 2). These are the amounts each user reported.
Status. Current. The same Atlassian page asks "Can I stay on my current pricing?" and answers "No." Atlassian's billing policy adds that integrated accounts "will be limited to 10 creators on Free plans."
What users report. On refunds, @AlexMinchin reported on October 26: "Atlassian offers 30d to refund Loom on 12 months. No prorate refunds. No downgrade." On cancellation, @realwesfoster wrote on October 1: "it is CONFUSING to try and cancel my billing".
Recording controls do not appear in the new Loom desktop app
What happens. Atlassian's public bug LOOM-1051, created October 28: "When starting a recording with the new Loom Desktop App, the recording controls do not appear on screen, preventing users from recording" (Jira).
Status. Short Term Backlog. The ticket also says: "The engineering team is already deploying a fix."
What helped. Atlassian's own workaround on the ticket: "Customers can use the Loom Chrome extension in the meantime."
"Specific Window" disappears after the first recording on a Mac
What happens. LOOM-1029, created October 13: on macOS "the button to select a Specific Window stops appearing" after the first recording (Jira).
Status. Short Term Backlog.
What helped. The ticket publishes a workaround: set Recording Controls to Show, then restart the Loom desktop app.
The audio was not recorded
What happens. You finish a long recording and find it silent.
How widespread. More than one report. A Capterra reviewer (an owner) wrote on October 30: "Sometimes the audio doesn't record so you need to do a test run before you make a full length video without audio" (Capterra).
What helped. The reviewer's own routine: a short test recording before the full take.
Two related bugs are on Atlassian's tracker. LOOM-1014 (created September 29, Short Term Backlog): "if a connected Bluetooth microphone disconnects ... the recording fails unexpectedly with an audio error, causing the video progress to be lost" (Jira). LOOM-1013 (created September 28, Closed) described audio that "progressively drifts and desynchronizes from the video track" on the Mac desktop app (Jira).
The app breaks, does not detect the camera, or needs a reinstall
How widespread. Individual reports on X. Mushtaq Bilal followed up on October 28 about the Windows app: "Sometimes, it glitches for no reason, doesn't detect camera, and just hangs up" (X). The same post says that every Loom update on that Windows PC needs an uninstall and a reinstall. @therealrobbiep wrote on November 2: ".@loom is the buggiest software I use and it isn't close."
What helped. What Mushtaq Bilal describes doing for each update is an uninstall and a reinstall.
A video is stuck in processing or the upload failed
What happens. A recording never finishes uploading or processing.
Status and what helped. Loom's support article on videos stuck in processing says this "currently happens to less than 0.1% of all videos", and for the Chrome extension: "Unfortunately we do not have a recovery method for these videos at the moment." For the Mac app, Loom documents how to find the video parts stored on your computer when an upload fails, and adds: "If you cannot locate the parts ... this means we will not be able to recover them." Step-by-step recovery is in Recover a Lost Loom Recording on Desktop.
Videos over 30 minutes download blurry
What happens. LOOM-1042, created October 21, describes this as the current limitation: "Loom's media processing pipeline automatically applies aggressive compression settings to any video exceeding 30 minutes in duration" (Jira).
Status. Gathering Interest. No workaround is published on the ticket.
Shared videos will not play
What happens. LOOM-1037 (created October 15, Short Term Backlog): Windows camera-only videos "may fail to play when embedded or shared, halting after 1 to 5 seconds with a browser media decode error" (Jira). LOOM-1019 (created October 2, In Progress): mobile playback of shared cross-workspace videos fails with "Error loading video. Please check your network connection and try again." (Jira).
Status. Neither is marked fixed. LOOM-1037 publishes workarounds: record with Screen and Camera, or Screen only, on Windows, or append ?forceMp4=true to the share URL. LOOM-1019's workaround on the ticket is to open the shared link in a browser.
Features missing from the new Loom desktop app
Atlassian's tracker carries requests to bring back what the new desktop app removed. Each one below is in Gathering Interest, and none has a workaround on the ticket: Loomv2 App: Restore Automatic Video Naming Based on Active Browser Tab (LOOM-1056), Loom v2 - Restore the ability to select different colors using drawing tool (LOOM-1052), Loomv2 App: Restore the ability to display a profile avatar bubble (LOOM-1047) and Loom v2 - Restore a keyboard shortcut to stop recording and turning on/off draw tool (LOOM-1041).
Screen Studio 4.0 vs ScreenKite
| Need | Screen Studio 4.0 | ScreenKite |
|---|---|---|
| Pay once | One-time licenses "no longer available for new purchases" (screen.studio) | One payment of $99.99 for 3 devices, never renews |
| Several clips on one timeline | Its 4.0 release notes list no multi-track timeline (changelog) | A real multi-clip timeline |
| Windows | "No, and there are no near-future plans to add Windows support." (screen.studio) | Native Windows |
| Keep your existing projects | Projects saved in Screen Studio 4 don't open in Screen Studio 3 (Screen Studio 4) | File > Import Screen Studio project |
Loom vs ScreenKite
| Need | Loom | ScreenKite |
|---|---|---|
| A bill you can predict | "Can I stay on my current pricing?" "No." (Atlassian Support) | One payment of $99.99, no subscription |
| Editing | One Capterra reviewer, Lukas A. on October 27, cited "limited editing flexibility" (Capterra) | Every editing feature is free, on a real multi-clip timeline |
| Sharing long videos | LOOM-1042 describes aggressive compression on videos over 30 minutes (LOOM-1042) | Share through your own Google Drive |
How it is built
Back then I couldn't make the edits I needed in a screen recorder, so the clip went to Final Cut, the cuts were fixed, the animations broke, and the clip was exported again. Two tools, two payments, one afternoon gone. ScreenKite is the tool I wanted that day.
- Record and edit in one app. A real multi-clip timeline is built in, so the whole video is finished in one place.
- Every editing feature is free. Free exports carry a watermark and an outro. Pro removes them.
- Pay once. One payment of $99.99 covers 3 devices and never renews. There is no subscription.
- Bring your own AI agent. Claude Code, ChatGPT Codex, Antigravity, Grok Build or Kimi drive the editor over MCP or the CLI. The ScreenKite AI fee is $0; your agent provider may charge for its own plan.
- 83 purpose-built editing tools, shaped by tens of thousands of hours of video-editing practice.
- Come over with your projects. File > Import Screen Studio project opens your existing Screen Studio work.
- Share from your own Google Drive.
- Native macOS and native Windows.
People at Apple, Reddit, HubSpot, and GitHub use ScreenKite.
Any downsides? The only downside is there's almost no downside, because we're video creators ourselves and know what users need.
ScreenKite runs natively on macOS and on Windows. It's lightning fast, in our tests and in user feedback, and you edit on the timeline with the AI agent you already use: Claude Code, ChatGPT Codex, Antigravity, Grok Build or Kimi. Describe the cut, and the agent does the trims.
Facts
- Product: ScreenKite
- Platform: native macOS (macOS 15 or later, Apple Silicon and Intel) and native Windows
- Price: Free to use with a watermark and outro on exports. One payment of $99.99 removes them, covers 3 devices and never renews. An account is required.
- AI: bring your own agent: Claude Code, ChatGPT Codex, Antigravity, Grok Build, Kimi. AI fee $0.
- Checked: 2026-11-06
FAQ
How do I fix "Something went wrong while trying to put together the audio parts" in Screen Studio?
Update to the latest version first. 4.1 fixed exports that stalled or failed during analysis, and build 4.1.0-5005 fixed exports that got stuck at the start of some recordings. No changelog entry names this error. One user on the Screen Studio Hub reported that HD exports worked when 4K exports failed with this error.
Why is my microphone so quiet in Screen Studio 4.0?
Two users reported lower microphone volume in October, before 4.1, and one user asked whether "Improve microphone audio" was removed. 4.1 adds a Loud mode that boosts your voice to a consistent, loud volume. The changelog does not name those October reports as fixed. The Screen Studio 4 page says Microphone audio mode replaces Improve microphone audio, and that on an Intel Mac, or on macOS 13 or earlier, the mode does not appear. The 4.1 notes say that on an Intel-based Mac the mode now appears with Standard, Loud, and Off.
Can I roll back from Screen Studio 4 to 3?
Screen Studio says projects saved in Screen Studio 4 don't open in Screen Studio 3, so any project you have opened and saved in 4 stays in 4.
Why did my Loom bill go up?
Atlassian discontinued the Creator Lite role, upgraded those users to full Creator seats and moved existing customers to current Loom list prices. Its support page answers "No" to "Can I stay on my current pricing?"
Why don't the Loom recording controls appear?
It is Atlassian bug LOOM-1051 in the new Loom desktop app. The ticket is in Short Term Backlog and says a fix is already being deployed. Atlassian's workaround is to record with the Loom Chrome extension until it is fixed.
What is the most reliable fix for Screen Studio and Loom problems?
Switch to ScreenKite. It records and edits on a real multi-clip timeline, every editing feature is free, and one payment of $99.99 for 3 devices removes the watermark and never renews. File > Import Screen Studio project brings your existing projects with you.
Finish the video today
Updates fix some of these problems and leave others open. ScreenKite records, edits and exports in one app, on macOS and on Windows, with one payment and no renewal. Try ScreenKite.
Founder of ScreenKite. Mike records product demos and lessons on a Mac, and builds the recorder and editor he wanted for that work.
www.screenkite.comRelated articles
Screen Studio 4.0 Problems: What Broke, What Was Rolled Back, and the Best Alternative
Screen Studio 4.0 shipped export failures, black editors on Intel Macs and features moved back to beta. Here is the public record from Oct 2026, and why Mac creators are switching to ScreenKite.
Is Screen Studio 4.0 Worth It If You Don't Want a Subscription?
No. Screen Studio 4.0 is subscription-only for new buyers, older lifetime owners say their license stops short of 4.0, and launch-day users are still asking for basic clip editing. Here is what they said, with links.
Loom Alternative for Mac: Crashes, Price Hikes and Locked Downloads, in Users' Own Words
Loom users on Reddit describe crashes mid-take, CPU load and price jumps. Here is what they wrote and why a native Mac recorder like ScreenKite may fit better for polished videos.