So, the details.
Situation: a class tutoring the use of 2018, and a student reports she cannot now (but could previously) capture a voiceover: her system gives a "cannot find wave in device" error. On the tutors laptop (mine, basic detail above) fault is replicated - using the always-on microphone built into the device, always with a vsp loaded, and all but once with no files in an empty, new project timeline space. Could not resolve in class, more testing at home.
So, repeat testing in a similar environment - same laptop, same HDMI connection to a large HD display with HDMI inputs, and all in the condition where - once - capture detected the micorohone on the laptop. For tutoring reasons, the laptop has 3 VS versions installed: x9, X10 and 2018 - all 64bit and patched to the current version. Successively loading 2018, x10 and X9 with an empty timeline space, I clicked on the record/capture icon, and then clicked again on the microphone icon labelled voiceover. These are the results I got with the HDMI connection live and working:
- 2018
I even tried plugging a known working external headset (mic/earphones combo) to the audio connectors on the laptop, and repeated the 2018 test: again, fail - no wave in device detected.
It's pretty clear that 2018 is the base cause of this - 2 prior versions of VS both detect the wave in device correctly and do the level test (in the panel selecting the voiceover microphone source should display) OK - and I know I've used the voiceover capture with 2018 earlier this year, but probably not for several months. What changed 2018 then? Well, SP3 came out in late july.
The question: has anyone else experienced this? Is there a fix, or is this yet another 2018 bug?
If there is no fix available, what sort of work around is there available for a student relatively un-versed in video editing and now finds that adding a voice commentary to a 2018 project is beyond (cannot do) the up-to-date software?
Help please.
