Re: Overlay Error reoccurring
Hi Ted, Thanks for responding, The /k tells the cmd.exe to display all output in the command window. Not sure about the *, I've not seen it in the code anywhere. Not sure what you mean by removing the "output pad label and the explicit stream mappings". It just seems strange, that it works when written directly in the command window on windows, but not when I send it through my Visual Basic 2019 application. Any more clues? John On Wed, 21 Oct 2020 at 08:59, Edward Park <[email protected]> wrote: > Hi, > > > I am not sure if I have the overlay code in the correct position or > should > > I be adding it to the "-filter_complex "[0:a][1:a]amerge=inputs=2[a]"" > as > > an additional Item. > > I think that would be the cleanest way, separated by a semicolon. And you > could get rid of the output pad label and the explicit stream mappings. I’m > not sure if you can mix simple and complex filters, maybe putting the -vf > after the gdigrab input is valid too? > > > The overlay runs correctly on its own using windows cmd. > > > Is that the actual command you type what does \k and * do in windows > command line?? > > Regards, > Ted Park > > _______________________________________________ > ffmpeg-user mailing list > [email protected] > https://ffmpeg.org/mailman/listinfo/ffmpeg-user > > To unsubscribe, visit link above, or email > [email protected] with subject "unsubscribe". _______________________________________________ ffmpeg-user mailing list [email protected] https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email [email protected] with subject "unsubscribe".
