Cannot record audio in 7.3

One notable improvement is that I can now use my AirPods when Skyping—which is awesome. Also, Skype  automatically switches to the Telestream driver, after the initial setting. 

Benjamin Boyce Thanks for noting that. Ultimately the audio based improvements around the driver will help in several situations. Use of Bluetooth audio should be getting better.

CraigS Hi Craig, I can't seem to record audio from a WebEx but yes, browser audio works. I used to be able to but can no longer. Any idea why?

Justin Young Does WebEx allow to direct output to speakers for example? If you start ScreenFlow capture you may then be able to go in and change it to Telestream Audio Capture. I have a screenshot showing it in Skype in this linked post but you should be able to do the same in WebEx.

Has anyone who having audio issues brave enough to upgrade to 7.3.1 and if so is it improved? I assume it still "hijacks" your audio output and causes a weird delay if you're doing something using a daw and trying to talk, but I hope that's not the case.

DBW Productions We're still working on improving things. 
See 7.3.1 Read Me file for improvements so far.

DBW Productions I haven't risked it yet!

Macbook Pro 2012- OS 10.12.6 - I have the same issue as most people above, with Screenflow 7.3 I can record audio from Youtube but not from a Zoom.us webinar. After reading all the posts, I went back to 7.2 and everything came back normal.

Jean Claude SOLEIL Apple is making changes that may eventually break the audio as you are using it. We had to develop a new driver and a new way to use it. My post from 1 month ago (as I write this) links to the explanation and how to use the new driver. If you eventually upgrade your OS (or your Mac) you will need to update ScreenFlow.

CraigS Hi Craigs

I appreciate the fact that you came up with a new audio driver and a new way for using it. Keep in mind, however, that not every Screenflow user is a professional graphic artist and many of use only the features that we need for a given job. This is true for many softwares (I.E Excel). When upgrading to a new version of Screenflow, one does not expect to re-learn how to use it, especially if it takes a lot of search  time to discover the availability a "patch".  I believe that every new paid version of a software should allow the user to do the same as before plus more... When developing a new version is it reasonable to favor the few lucky owners of a new Imac and force the many current users to change their workflow? Why not have a check box for selecting the new driver when required?

Jean Claude SOLEIL One can always revert back to 7.2 which we continue to make available on our download said. Again, Apple is making changes and we need to maintain compatibility. One can always "freeze" to an old OS and an older version of ScreenFlow but Apple's changes necessitate that we make changes as well. It's certainly presents some inconveniences and we are working to make things easier but the changes really are a must for us.

Hi Craig - 

Changes being necessary… part of life these days.

However, the dialog pop-up in 7.3.1 when enabling the new driver should be a lot more explicit and emphatic in that you must have SF up and running for the driver to be available.

My experience this evening was this:

Begin a tutorial using Pro Tools. Enable "Record Computer Audio". Get the dialog about the new driver. Sure, go ahead, do that. Set Pro Tools' playback engine to output to the new driver. That was fine.

Had to restart Pro Tools to switch drives. Without any warning or alert, the playback engine reverted to the main AVID hardware.

Since there was no outward indication of this happening, I proceeded to do a 50-minute tutorial on Pro Tools for which the audio was not recorded.

OK well… this happened so I spent the rest of the evening doing other work. Before signing off for the night, I opened Pro Tools to see what was up with the playback engine… and of course Telestream Audio Capture was no longer there.

It's not made nearly clear enough that:

*Screenflow has to be up and running for the driver to be available

*Once the driver is enabled, one must not exit the DAW (and I assume any other app that uses audio outputs). If you do, you must re-assign the driver before continuing.

I admit to being a little irritated about losing an hours' tutorial work. But a change in workflow that has this failure as a potential pitfall should be announced in neon, bold, and with exclamation points. It's not nearly obvious enough and is inconsistent with the behavior of the other audio drivers in my system.

Can you not create a driver that can live natively in MacOS and not need a process to be running to be available? I would classify the current behavior as a bug.

Thanks for your attention to this.

Hi,

My personal case is closed. I have upgraded to Screenflow 8.0 and the audio issue is gone.

Thanks

John Whynot said:
However, the dialog pop-up in 7.3.1 when enabling the new driver should be a lot more explicit and emphatic in that you must have SF up and running for the driver to be available.

 Please download ScreenFlow 8 and see how that works. We've improved audio related pop ups.

Jean Claude SOLEIL Thanks for noting that. ScreenFlow 8 has improved things on the audio front. We're examining further improvements of course.

CraigS Alrighty! 

John Whynot We're working hard to deal with these changes while improving the audio user interface experience.

Screenflow 8.0 (haven't tried 8.1 yet) does allow me to choose the driver without first hitting record first. Thanks for that. Unfortunately, your driver makes it impossible to do any performances in an audio program because the latency is quite high. So I'm capturing in 7.2 and editing in 8.0 for now. Hopefully this gets fixed eventually. Thanks.

Kenny Gioia Please try 8.1. Apparently there may be noticeable latency depending on the source. Please make sure you've reported to support. It's the only way they measure the priority for fixes and improvements.

CraigS I downloaded 8.1 and I will report back. The latency issue in 8.0 only exists if I'm performing live during the video. So if I engage a MIDI track to perform a piano part, it's way to late to play the part using the new driver. I'll report back ASAP. Thanks.

CraigS Just circling back to say that 8.1 is working fine but the latency while recording to a DAW with the new driver is still too late (latency) to use. For those following along, I'm still capturing in 7.2 (for now) and editing in 8.1. Thanks.

Kenny Gioia Please do report the comparison in latency but do understand we're using different technology. ScreenFlow Support Form

I have updated the latest version also upgraded from 7.2. Nothing is changed. Being a DAW tutor and using Screenflow was great once. Not anymore. 

There is no way to change 48khz sample rate on telestream audio and I don't work at 48khz I work at 44.100 on my DAW. Also you click to play and there is latency you see between audio and video sync. It's just useless. I don't understand why something that is worked before not working anymore. Why don't I just select my soundcard like i used to before and continue. Telestream audio drivers are not great.

This is the latency issue with new driver. It's not even sync:able with post processing as video and audio won't line perfectly. 

Emrah said:
t's not even sync:able with post processing as video and audio won't line perfectly. 

That would probably require subframe adjustment my guess. We understand the issue but the problem is Apple made hardware changes as well as OS changes that required a change for compatibility. 

For example, on any new Mac with the T2 chip (all new Macs) the old driver doesn't work at all. We're continuing to examine how to improve this. Please use your case number and send an email to support asking for a status update and include a screenshot of your example.