
Unacceptable latency with Telestream Audio Capture
I m trying to capture a live performance from the Facetime camera on my iMac while playing playing and singing along to a Logic Pro X track. Ion order to capture all of it I have to switch the audio output preference in Logic Pro to Telestream Audio Capture but as soon as I do, the latency when I play the keyboard is just too much to keep time.
-
Dennis Maille I don't doubt it's real but the problem may exhibit itself differently with different programs, Mac, operating systems. Apple made hardware changes to their computer starting with the iMac Pro so sound is handled differently. So we need to see the details for OS (High Sierra vs Mojave) and computers (Macs with T2 chips and Macs before the T2 chip was introduced). Macs with T2 chips can't use the old driver at all. Also different programs (DAWs) may be handling this differently so so this is why we need details.
Here's the refund link but it really helps for us to know the specifics of your DAW, your OS, you computer and the kind of latency you're getting. -
Dennis Maille For what it's worth, I've been using Screenflow 7.2 to capture and it works perfectly. Then I quit and use 8.xxx to do my editing. It's a PITA but it works.
-
I'm also experiencing this same problem. It's been happening for me since the release of Version 8 for ScreenFlow. I've been talking with support since then. Here is what I was told yesterday via email from support:
"The entire ScreenFlow team including our director of engineering as well as the product manager are aware of this issue. Apple is also aware of the issue, via at least one radar bug that we filed years ago, I assume folks like Soundflower, Camtasia etc have inquired as well.
I will see if I can track down the Radar Bug number for you."
Abdul
Telestream Desktop Support -
CraigS said:
The only version of 7 we make available is 7.3.2. If you believe it should be publicly posted please do fill out the form and request that.That seems like a strange thing for us to ask. It's a service to your customers. "We" think you should fix Screenflow 8 to give us the option to capture audio the old way and the new way. As some sort of preference I guess.
For now, capturing seems to work in 7.2 and editing works in 8.xx. But asking us to ask you to give other people a link to older software that we already have is an odd ask from you. With all due respect.
Our request is that you fix the problem. Making the older version available is just a temporary fix that Telestream should provide. -
Kenny Gioia We have 7.2 available in the ScreenFlow FAQ under Audio Driver Issues.
You can certainly request that we give it more visibility but this is where it's been decided to place it.Kenny Gioia said:
Our request is that you fix the problem.The issue is with Apple. They've made changes and have not yet provided an API for developers to use to make changes given the new hardware. Apple is aware of the issue. We have to wait patiently for their action at this point.
-
CraigS How will we all be notified that you have the API? Once you have it, how long will it take you to either fix the driver and test it for release in Screenflow 8 or are you all planning to scrap the driver and start over? Just trying to see how long the process will take? This could be a year before we see a fix?
-
Any fix yet? I just purchased the latest ScreenFlow 8.2.4 and I cannot do my work due to this latency issue :(. What I don't understand: it works fine on my machine (MBP 13" 2017, Catalina) in ScreenFlow 6, so why don't you just let us choose the old (version 6) computer audio recording path in version 8?
BTW I tried to route audio various ways:
Anytime my music software is not routed to the Telestream output, I cannot record computer audio in Screenflow 8 (but 6 works fine). If I pick the Telestream output in my music software, I get a huge latency, no matter to which monitoring device my system audio is routed (so it's bad with internal speakers as well as USB audio interface).
Please, while Apple and you are fixing the problem, give us the option to choose the old (version 6 or early 7) audio path to record computer audio in version 8. -
Matthias Orgler Apple has not provided an API as of yet. Please Read.
Apple no longer wants developers to use .kext drivers. Apple has to provide development tools to change. The issue is not specific to our products. -
Hey CraigS - I am a Screenflow user for years now. I had the same issue with my older MPB (Mid 2010) so I downgraded to SF 7.2 - fine. BUT now I got a new MBP 16" 2019 running Catalina, so I tried SF8 again but getting a latency which doesn't work for the kind of audio/DAW tuts I m producing. I tried downgrading to 7.2 here as well but as expected I m getting no audio at all. So what are my options? Thx Tobi
-
Tobi The old driver will not work with Macs that have the T2 chip at all. As per the linked Knowledge Base article, unless/until Apple has an API that can address this there's not much we can do. You can try some third party products and see if they'll help such as Rogue Ameoba Loopback or Dante Via.
-
As a crude workaround I now create videos with the following method:
- I launch Logic Pro X with an audio track and start recording
- I record only video and microphone in Screenflow (NO computer audio)
- At the recording is running I hit a key on my (musical) keyboard four times to get a "sync signal" (like the "clap" in Hollywood :P)
- After recording I export the audio track from Logic Pro X and drag it into Screenflow
- I manually sync the four keyboard hits with the visual I see in the video (tedious and not exact, but best I can do)
This process works, but it makes recording videos much more tedious :(. Also the syncing is hard to get perfect, which I sometimes only notice after cutting – and after cutting it is even more tedious to adjust the audio/video sync.
So yes, the workaround works. But it is frustrating, costs time and seems unworthy of such a screencast solution like Screenflow.
-
Martin Wolfinger Loopback could work.
We're hearing of issues with Via and Catalina.
It would be easy enough to download the free trial of Loopback and test.
Matthias Orgler said:
But it is frustrating,As per the KBase I linked to Apple would have to create an API for us to use. To date, they haven't.
-
CraigS said:
As per the KBase I linked to Apple would have to create an API for us to use. To date, they haven't.And we both know that Apple probably never will.
Please tell the development team to create a workaround that doesn't involve us using two versions of your software or using a third party application that is designed to do what your product claims to do.
Figure out what Loopback or Dante Via is doing and please do that.We can blame Apple all we want but that doesn't make the customers happy. If I build a car that drives poorly on the road, I can't blame the road. I have to fix the car.
This has gone on for over a year and I think the solution needs to come from Screenflow.Thanks.
-
This is very poor service from Telestream. We are left stranded and no way back! How do I find posts from Loopback and Dante Via? I like the Dante handle. Which circle do Telestream have us trapped in?
does this mean that I have to move back to 7? How do I do that, do I get a refund and what happens after that you Apple and Telestream have settled their standoff?
Thanks for your reply.
-
Ron Bailey This should help you if you do decide to try Loopback:
https://youtu.be/eDIE3vYpOJY -
Keep in mind that given there are utilities such as Loopback, developing what already exists in the market means resources to develop other areas of the program move back in priority.
We're hearing from some that Dante Via has issues with Catalina so the development of such utilities is not without opening another set of issues.
There are additional utilities that may work and are free, worth trying such as Blackhole and IShowU. Both may involve going into Apple"s Audio Midi Setup and creating an aggregate device.
All these are workarounds, all would take development resources away from other things. All are being developed by other developers who are devoting their resources to such issues.
These issues are not specific to ScreenFlow. It impacts all screen recorders that would normally use system sound capture.