Runtime error when selecting multiple clips
Hello!
I haven't heard back from Desktop Support for over a month so I thought I'd try my luck here. Maybe the wizardry of CraigS can save the day. :)
I get a runtime error message when selecting multiple clips (on different layers in the timeline). After that I need to restart Screenflow for it to work properly again. I have done a lot of testing on my own - disconnecting monitors, audio interface and so on without finding exactly what is causing this.
What I have noticed though is as soon as I enter the audio tab/section - I don't have to edit the audio or even have a clip selected - the next time I try to select my microphone audio clip together with another clip (audio or video) in another layer I get that error message (screenshots attached).
I have added Screenflow as a trusted source in Mojave and I have started a new project in version 8.2.2.
Earlier I used Screenflow 7 with El Capitan with no issues.
I mostly record Minecraft (yes, I am an adult) but I also have this issue when editing videos where I have recorded other applications.
Specs:
MacBook Pro Retina 13-inch early 2015
Mojave 10.14.3
Screenflow 8.2.2 (not from App Store)
Free space 71 GB
Monitor: ViewSonic VP191s 1280x1024, connected with a DVI to Thunderbolt cable
Resident Audio T2 audio interface (Thunderbolt)
Thank you!
/Daniel
-
Do you have the case number from support? I'll investigate the status for you.
Do you have any audio sources in System Preferences > Security & Privacy that aren't given access by ScreenFlow? Just in case it's scanning multiple audio sources. -
CraigS Yeah sure, it's #00622732
Hmm, not that I can see (it's added to Microphone, Camera and Accessibility). There is an "Automation" option, maybe I should add Screenflow to that as well...?
-
Daniel Johansson Thanks for that. I checked on the status.
They've been able to duplicate the issue. They're still working on fixing and testing. Sorry that it's taking them some time. -
Daniel Johansson Try this although it may seem odd.
Open ScreenFlow Configure Recording and change Record Audio From to the built-in mic (your computer's mic). Close that window. Then go through the process of that would cause the error and tell me if it happens. -
CraigS Thank you for checking! Good to know that it is possible to duplicate the issue.
-
CraigS Tried those steps but the issues remained. I also tried to uncheck "Record Audio From" and also unchecked the others after that, but that didn't work either. It was worth a try!
-
Daniel Johansson Next theory, how are you monitoring sound? Through the audio interface or some other method?
-
CraigS Yes, usually through the audio interface, but I have also tried disconnecting it and using the computers headphone jack instead (and also computer speakers) with same issue.
However, that led me to further testing. If I make a screen recording using the built in mic instead I don't get the runtime error when editing the video. So it seems the audio file created when recording with the audio interface is casing problems (?). I'm using an ADK A-51 microphone connected with XLR and then thunderbolt to computer.
-
Maybe I should also mention that every first time I save a recording to a project (per session so to speak) I am prompted to save the recording twice, and I have noticed it choses the second audio track even if I add the first to the timeline. But I think it did that even in Screenflow 7 and El Captian...
-
(I get 4 tracks is what I mean if that was unclear - two video tracks and two audio tracks - for every first recording)
-
Daniel Johansson said:
If I make a screen recording using the built in mic instead I don't get the runtime error when editing the video.Yes, that's why I was suggesting changing the audio source after the fact (going into Recording Config). I had found a situation where the recording source or monitoring destination might have an impact. It may not be the recording file itself but the setting after the fact. Then again maybe it is the file in this case.
After making the recording, I wonder if you changed both the recording source (as you had tried) AND the monitoring source if that will have an impact. Obviously, this is something we need to investigate but knowing the cause and what the apparent workaround is, can point us to a solution. Thanks for doing this testing. -
CraigS Happy to do what I can on my end! I tried every option, but decided to do them again and be as scientific as I could. The test process was as following:
* Start Screenflow
* Make a new recording directly from the welcome window (desktop, audio and computer audio)
* Save the recording which will create a new project
* - make a change -
* Select both tracks
* Open the audio tab
Tests:
1. Record audio interface mic, change “record audio from” to internal microphone = runtime error
2. record audio interface mic, change “record audio from” to internal microphone + change mac output to headphones = runtime error
3. record internal microphone (Mac output headphones), no change = no issue
4. record internal microphone (Mac output headphones), change Mac output to audio interface = no issue
5. record internal microphone (Mac output headphones), change Mac output to audio interface + change “record audio from” to audio interface = no issue
6. record internal microphone (Mac output audio interface), no change = no issue
7. record internal microphone (Mac output audio interface), change “record audio from” to audio interface = no issue
8. record audio interface mic (Mac output headphones), no change = runtime error
9. record audio interface mic (Mac output headphones), change “record audio from” to internal microphone = runtime error
I hope that helps!
-
One more thing that I just discovered (not properly tested though): If I detach the audio from the video track I can select all three tracks without issues!
-
Daniel Johansson Important bits of info. Thanks for testing all that.
So it seems it's related to audio from the interface (regardless of how monitored) and it's relationship to the video.
Fill out the form and include those details including the specific model number of the interface.
ScreenFlow Support Form -
Daniel Johansson One more thought. Since your interface is Thunderbolt as is your external monitor, can you remove the external monitor entirely and reboot and try recording and testing from the interface and see if you get the runtime error.
-
CraigS I tried removing the monitor, rebooting and conducting the previous test, which gave me runtime error.
The support form, should that be an addition to my previous case number or is it better to start a new inquiry?
My workaround for now will be to always detach the audio from the video file (which I often do anyway, to get smother audio transitions). Because I can then cut, move and trim the three tracks as a group the workflow is up to speed again. So far I haven't had any issues when I do that.
-
Daniel Johansson If you already have a case on the same issue then you can use the case number in an email and send updated information on the tests your trying.
-
Daniel Johansson said:
My workaround for now will be to always detach the audio from the video fileI wonder if there's a slight difference in duration between the audio and video that's causing it. Detaching would make that moot which is why the workaround fixes the issue.
Do you have any USB audio devices? It might be interesting to testing using that as the audio source instead.