Reply to thread

Message: <blockquote data-quote="henso" data-source="post: 1153190" data-attributes="member: 119106">Good to hear from you! <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite2" alt=";)" title="Wink    ;)" loading="lazy" data-shortname=";)" />I was also thinking about how this would be possible with all the DLNA specific headers and such.My initial idea was also to have support for different transcoder binaries just like MPExtended. The VLC transcoder never really worked for me though (heavy pixilated video) so I settled on the ffmpeg binaries instead.TranscoderBinPath and TranscoderArguments were meant for user to experiment with other transcoders and/or transcoder arguments. {input}, {subtitle} and {output} are placeholders that could be used in the argument string to be replaces by the actual values. I was aiming for the community to create new DLNA  device profiles, just like Serviio does.Don't think about it. It's no issue for me. I will look you a bit over the shoulders though, to check if you remove something I think is important. <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite7" alt=":p" title="Stick Out Tongue    :p" loading="lazy" data-shortname=":p" />I know what you mean. I will try that when I find time.I will try to minimize my changes to that file, to minimize you merge burden. Actually I was confronted with you changes at my last sync and the merge dialog made no sense to me. It also appeared as if I had changed almost everything in the solution and had to commit a lot of changes somebody made. I ended up cloning the repository, merging my changes with WinMerge and then commiting. Any merging tips for Git noob?What type of source media were you using?The DLNA.ORG_FLAGS specifies seeking capabilities, maybe that's your problem? See DlnaForthField.cs.On a side note I tried compiling a ffmpeg version with QuickSync and NVENC support and succeeded. My development machine only supports NVENC for a H264 codec (no QuickSync). So I played a little with that. Seems NVENC is a little more picky about encoding parameters than SW encoding is but the speed was good and quality wise I saw no big difference. But it was a small sample so this does not really say anything about the quality.</blockquote>

Verification