Welcome to Doom9's Forum, THE in-place to be for everyone interested in DVD conversion. Before you start posting please read the forum rules. By posting to this forum you agree to abide by the rules. |
28th July 2018, 15:31 | #22961 | Link |
Registered User
Join Date: Aug 2016
Posts: 1,348
|
any way to test whats going on here, I also have a pair of arctis 7's plugged in, they also work over a wireless dongle, they work, however i'm getting too much latency on those so i'm probably going to send them back and keep the Sony's as I dont want to constantly have to change latency settings.
!!! caution, off topic !!!! - finding some wireless headphones just for movies is a total nightmare, none of them seem to be able to do everything well |
28th July 2018, 19:46 | #22963 | Link | |
Registered User
Join Date: Mar 2009
Location: Russian Crimea
Posts: 335
|
Why you so sure?
I'm not sure you've tried ffplay.exe -vf weave,yadif=1 "Zee TV20180716-203544.ts" because only blind man not see the difference between ffplay and any players on ZEE TV logo - with ffplay it's normal but in players vertically stretched x2 it flickers like old Bob deinterlacing on ordinary SD MPEG2 or H264 interlaced streams. Quote:
Last edited by VictorLS; 28th July 2018 at 19:49. |
|
28th July 2018, 19:50 | #22964 | Link |
Registered Developer
Join Date: Mar 2010
Location: Hamburg/Germany
Posts: 10,346
|
I'm so sure because I actually know how LAV and FFmpeg works. I could entirely repeat the previous post, but it would not make a difference. FFmpeg needs to properly support HEVC interlaced without custom filtering to fix it, there is nothing for LAV to do. I will most definitely not implement work-arounds that are slow and also just don't work with hardware decoding.
__________________
LAV Filters - open source ffmpeg based media splitter and decoders Last edited by nevcairiel; 28th July 2018 at 19:53. |
28th July 2018, 21:49 | #22965 | Link | |
Registered User
Join Date: Mar 2009
Location: Russian Crimea
Posts: 335
|
This is more clear - as I understand correctly you don't want do anything with it while ffmpeg not improved for correctly Zee TV20180716-203544.ts decoding without any "external" filters like weave?
Quote:
May be implementing -vf function with automatic turning off hardware acceleration [i.e. rectangle where people can write any working ffmpeg filter (or comma-separated filters) in with check near it to activate and prefer it over other settings] in LAV Video Decoder will solve present (and may be many future various) issue? Last edited by VictorLS; 28th July 2018 at 22:15. |
|
29th July 2018, 07:00 | #22966 | Link | |
Angel of Night
Join Date: Nov 2004
Location: Tangled in the silks
Posts: 9,559
|
Quote:
|
|
29th July 2018, 08:07 | #22967 | Link |
Registered User
Join Date: Mar 2009
Location: Russian Crimea
Posts: 335
|
foxyshadis
How much time I have to say it's from SAT so I and many SAT amateurs need decoder (not player) - to watch such streams in maximum possible quality directly from SAT - not record from SAT (as it was with "bad streams")? And so h265 becomes standard de facto (SAT providers use it for ~ two times less bandwidth with comparable quality in h264) and not support interlaced streams in right way like h264 but SD and HD from SATs still interlaced for a long time ( so support such Zee TV streams (there is more than 20 channels from several Russian SAT providers and it grows up day by day) is question of the time. Besides it's very easy (compared to NVIDIA CUVID 10bit support was implemented too as I said but for Win7 and newer) to implement - "history is just spiral" ) As I told give people choice and they choose best. Last edited by VictorLS; 24th February 2021 at 18:35. |
29th July 2018, 10:25 | #22969 | Link |
Registered User
Join Date: Oct 2016
Posts: 896
|
Victor, you just don't understand nev's position, do you?
LAV has to 'just work', and this exceptional case would not be compatible with that without a lot of work that is beyond LAV development philosophy, which is to just use ffmpeg 'as is' for software decoding. While a lot of stuff used interlacing with AVC, including Blu-rays, interlaced HEVC is just too rare and for a reason because it's less efficient as it cannot use the interlace optimised coding tools AVC had. This is a mistake from your SAT provider, just because something is technically possible does not mean it is recommended, sometimes it's just an inefficient dirty trick, which this is. I doubt they're really getting the same quality for half the bandwidth with those interlaced-as-progressive HEVC streams. So go ask ffmpeg to make the changes so that their HEVC software decoder outputs this particular case of HEVC as 1080i50 instead of 540p50, and then it will 'just work' with LAV in software decoding. The ideal way to broadcast material that originated in 1080i50 with HEVC is to deinterlace it to 1080p50 before broadcasting it. You can ask your SAT provider to fix this. Edit: here's the ticket you're interested in: https://trac.ffmpeg.org/ticket/5514
__________________
HTPC: Windows 10 22H2, MediaPortal 1, LAV Filters/ReClock/madVR. DVB-C TV, Panasonic GT60, Denon 2310, Core 2 Duo E7400 oc'd, GeForce 1050 Ti 536.40 Last edited by el Filou; 29th July 2018 at 11:06. |
18th August 2018, 00:47 | #22970 | Link |
Registered User
Join Date: Nov 2012
Posts: 32
|
Pin Info bug, decoding bug, o my mistake??!?
Hi folks!
Maybe I'm writing something stupid but, or I found a bug in LAV Video decoder and/or Pin Info, or I didn't understand how it works and I'll be glad if someone would explain to me. On Windows 10 64 Bit I'm using MPC-BE with LAV Splitter/Video/Audio Decoder, madVR and (only for SD and HD resolution) FFDshow by SmoothVideo Project for frame rate conversion. The output resolution is 1920x1080@59.970 that madVR automatically change to 3840x2160 in case of UHD files. Playing an HEVC 3840x2160@23.976 file with DXVA D3D11 in hardware decoding, the Pin Info shows the correct resolution both for input (from LAV Splitter) and output (to madVR). Changing to software decoding, the output Pin Info shows a resolution of 4096x2160@23.976 (that means 4x1024 and not 2x1920) to madVR. I made the same try with a 1920x1080@23.976: Pin Info shows the same correct input/output resolution in hardware decoding, in software decoding the output file passed to FFDshow (using the frame Rate conversion of SmoothVideo Project) become 2048x1080@23.976 (2x1024 and not 1920x1080@59.970). Without the frame rate conversion, the Pin Info shows an output file resolution of 1024x1080@23.976. Seems that in software decoding the output file is based on multiplies of 1024 instead of 1920 (or the Pin info shows it). Am I wrong? P.S. Sorry for the bad english and the possible mistakes (I'm not translating with Google, but learning to write). Best Regards. Leo!
__________________
Best Regards! Leo! |
18th August 2018, 13:49 | #22972 | Link |
Registered User
Join Date: Nov 2012
Posts: 32
|
The images on video are ok, I have not problems.
But I was wondering (if what outpin shown it's true) why madVR have to do an extra unwanted scaling for everything that comes at 1024 (or multiplier) to 1920 (or multiplier), expecially when sources and display matches (i.e. blu-rays at 1920 and UHD at 3840). I though that LAV should leave the resolution untouchedÂ… Another question, if you can help me: assuming that madVR does the resize and color space conversion in the best way it's possible (at least that's what I understood from madVR thread), what color space output I should set in LAV Filters to avoid multiplies conversions? I mean, I would like that everything goes to madVR untouched (both resolution and color space) and it does it's magic!
__________________
Best Regards! Leo! |
18th August 2018, 16:34 | #22973 | Link |
Registered Developer
Join Date: Mar 2010
Location: Hamburg/Germany
Posts: 10,346
|
There is no scaling. Its just a technical detail on how the image is transported to madVR.
__________________
LAV Filters - open source ffmpeg based media splitter and decoders |
18th August 2018, 18:55 | #22974 | Link | |
Registered User
Join Date: Oct 2012
Posts: 7,925
|
Quote:
|
|
20th August 2018, 22:50 | #22976 | Link |
Registered User
Join Date: Oct 2012
Posts: 7,925
|
madVR doesn't support deinterlancing with d3d11 native and that's why i personally say don't use it.
the benefit of headless mode is you can use a GPU that is not correct to a display(headless) like a iGPU this is not possible with dxva. |
23rd August 2018, 14:25 | #22978 | Link | |
Registered User
Join Date: Aug 2007
Posts: 1,430
|
Quote:
|
|
23rd August 2018, 16:07 | #22979 | Link | |
Registered Developer
Join Date: Mar 2010
Location: Hamburg/Germany
Posts: 10,346
|
Quote:
I would recommend trying a different audio renderer.
__________________
LAV Filters - open source ffmpeg based media splitter and decoders |
|
Tags |
decoders, directshow, filters, splitter |
|
|