Andrew Weaver

@pjotrek-b, does running `pkg-config --print-errors x264` give you any useful output?

Hi @a7med12h - thanks for reporting this problem! This error usually occurs when something has gone wrong with either device detection or mapping. I've taken a look and found a...

Hi @a7med12h, a new version of Vrecord has just been released that might help clear up this issue - try updating vrecord and hopefully this will sort itself out!

@a7med12h - it looks like something isn't working correctly on your system with compiling FFmpeg with Alsa support - do you have `libasound2-dev` installed?

@a7med12h - seconding @retokromer's comment that that is not normal. Are you still running Ubuntu in its trial mode from a USB stick?

Hi @lavidtech-1, one way to quickly test the branch in #770 would be to download it's ZIP from github at https://github.com/amiaopensource/vrecord/tree/updates-on-handling-recorders via the 'Code' tab and then to run that...

Hi @a7med12h, to find the specific failure issue, I'd suggest taking a look at the contents of that logfile that @kieranjol noted - it looks like it is called 5k_mediaconchreport.xml...

@marshalleq the audio passthrough mode started by running `vrecord -a` is basically just a quick way to get vrecord to fire up into the "Audio + Video" preview window -...

Thanks for clarifying! The vrecord preview window uses ffplay, so it is limited to the [commands available](https://ffmpeg.org/ffplay.html#While-playing) to ffplay. Using `m` during passthrough seems to be working for muting on...

Ah - you are running in 'Quality Control' view - that's actually a bit different from how the other views work. QC View uses mpv rather than ffplay for the...