Apple Silicon / M1 Support
I bet one of the biggest pain points most of us have is slow export times. I've got a JUICED macbook pro and it's still painfully slow.
So - I know this is early (and please don't make me submit a feature request) - but are there plans to get Screenflow to work on the new apple silicon machines?
If so, could you shed light on how hard that would be for Screenflow? Since it's a native app, does it just compile over? Or is there significant work that needs to be done for it to work?
They have touted faster export, and I'd go out and buy a mac mini today if this meant I could speed up my exports.
thanks!
-
Grateful to see y'all working on a fix so quickly!
I've had the M1 Air for a few days and it's a monster, but man do I feel for developers right now.
-
CraigS Thanks for the updates. I'll see you at midnight! 😂
-
Kenny Gioia ⏰
-
-
Adrian Cantrill said:
s it going to be this week?We hope so. We just have to double-check a few key things and get an all-clear.
-
:( -
Hoping the update gets released today :) Its the last Universal Binary update I am waiting for.
-
Kenny Gioia J Craner Very soon. We're testing now.
-
CraigS ❤️
-
-
I'm the same, it's the last part of my workflow to move across. As it also doesn't work under rosetta is the only thing preventing my move across... I get it takes time, but also its frustrating :)
Good luck to the team.
-
Shhhh! (quiet release) but the 🦅 has landed
-
omg omg omg omg *dances*
-
EVERYBODY GET IN HERE!!!!!!!! 😂
-
ok... initial impressions ... so so nice.
My 13 inch MBP M1 is basically as well performing on exports as my 16 inch MBP, 8 core, 64GB ram with the best GPU option - madness.
...and silent.
-
I did a little side-by-side test comparing the export of a 2 minute 29 second Screenflow recording – resolution 2560x1600 (screen size of the 2020 MacBook Air that I used to make the original video).
My M1 Mac mini has 16 GB RAM. The Macbook Air has a 1.1 GHz Core i5 processor, but only 8 GB RAM.
So perhaps not fair in terms of RAM, and certainly not scientific, but... see for yourself:
https://www.youtube.com/watch?v=Y1ERB6wxQ2g
I like the results for the M1.
This is going to make instructional video creation for my students during this pandemic a lot less time consuming.
Thank-you, thank-you, thank-you to the team at Telestream who put the M1-compatible release together so quickly!
-
Hi CraigS thank you for working on it.
The app crashes when I use following configs
- Built in webcam, attached ipad, attached mic
- Built in webcam, no attached ipad, attached mic
- Built in webcam, attached ipad, no attached mic
However it does work with:
- Built in webcam, built in mic
More Diagnostic Info
- mic used: blue yeti 2020
- ipad used: ipad pro 12.9 2020
- mac used: macbook air M1 16gb ram
Please let me know if I can provide any other info that might help in debugging this.
Thank you for working on this!-
Mukul Raina In order to see what is causing the crash you should start with a simple screen recording (no Facetime, Yeti, iPad).
Keep in mind that you have to give ScreenFlow access to Camera, Microphone, Accessibility, Full Disk Access, Screen Recording in Security & Privacy. -
CraigS Hi Craig,
- Simple Recording (no facetime, no Yeti, no iPad) is also crashing
- Recording with just facetime (no yeti, no iPad) worked 3 out of 7 times. Other 4 times crashed
- I can also confirm the app has access to Camera, Microphone, Accessibility, Full Disk Access and Screen Recording
Question
- Screenflow wasn't in the list of options for Full Disk access by default - is that expected?
- I had to add to the list manually - just FYI not sure it matters
-
Mukul Raina Yep I was getting this error also when trying use my yeti mic and Logitech brio 4k webcam, I also tested the LG 5k ultralife Mic and build in webcam to see if i have the same issue and yep same issue. It will record the screen of the LG 5k display but it won't use any other mic or webcam beside ths macbook pro built in mics and facetime cam. If you use any other mic or webcam it will give you a recording error like the one you have. The issue is only on screenflow though if I use OBS there is no issues on an M1 mac. So ScreenFlow needs to get there S$%t together and do a better job and updating their software instead of a rushed half-arsed job.
-
Mukul Raina said:
Screenflow wasn't in the list of options for Full Disk access by default - is that expected?
I had to add to the list manually - just FYI not sure it mattersScreenFlow seems unable to record at all on your system.
If it can't access the disk it may not be able to record.
How did you add it to Full Disk Access?
Perhaps that's the issue.
Please confirm you actually have ScreenFlow 9.0.6 installed and you are on Big Sur 11.1
-
I have an issue that I'm not sure you can solve because it only seems to be happening when the application REAPER is open. Which is what I demonstrate in these tutorials. What's happening is that if you keep the mouse still, all of the "screen recording" features (adjusting the mouse size or turning it off or changing it to another pic) stop working. But if you move the mouse it works fine. You can see it here. Any help would be appreciated. Thanks.
-
Kenny Gioia said:
it only seems to be happening when the application REAPER is open.Is Reaper M1 native yet?
I'm wondering if may it's how Rosetta is handling it if now. -
CraigS said:
Is Reaper M1 native yet? I'm wondering if may it's how Rosetta is handling it if now.It is. And the problem exists for their old version with Rosetta or the new version which is Native. I actually work for (with) them and they said they haven't changed anything. So I'm wondering if it's how M1 handles the cursor compared to how Intel did.
-
Kenny Gioia So you're seeing this in the Native version as well?
We haven't yet seen a report like this with any other apps but it's early days.
Perhaps double-check that all System Preferences Accessibility settings are at their defaults. Make sure you're on the newest Big Sur which is 11.1 (and not the older 11.0.1). Big Sur itself might be playing a roll in this. -
CraigS I'll play around more but I disabled as many things as possible, updated and tried the Intel (with Rosetta) and Native (for M1 Macs) and both have this issue. If the application is open, the cursor functionality is ignored for any application and it works perfectly when those applications are closed. Thanks
-
Kenny Gioia Yet if it only occurs with Reaper then it would seem Reaper is using the graphics differently than other applications. I guess a good comparative test might be with Audacity (which is still only Intel though so would use Rosetta).
According to the Reaper website, the Apple Silicon version is Beta so you may want to report it to them because we may not consider this an issue if it's only impacting a beta version and it's the only program that exhibits it. -
CraigS It works perfectly in Audacity as long as REAPER is not open. If REAPER is open, the cursor functionality is removed whenever the mouse is not moving (for a second or two)
-
