INTERACT FORUM
More => Old Versions => JRiver Media Center 19 for Windows => Topic started by: fitbrit on January 30, 2014, 03:01:30 pm
-
For quite some builds now, I have seen that starting a video file results in audio only playing, with video taking up to a minute or more to appear. Switching to RO Standard fixes this. I can provide a log later when it happens next if it's deemed useful. It's much more likely to happen on the first attempt to play video after a long period of user inactivity in MC.
-
What GPU? HW Accell On or OFF?
-
There's another similar report on the main Windows board.
-
Are you using the 111 build?
-
I'm somewhat inclined to turn hwaccel for AMD GPUs off again, its apparently a stability nightmare, and even worse, one I cannot reliably reproduce.
In any case, try turning off hardware accel decoding.
-
What GPU? HW Accell On or OFF?
(nVidia) 450GTS
HW; Acceleration on. (i3 530 CPU, so not that great).
I'll try HW Accel off.
-
Do you have any feeling when it started? Before 107, which updated LAV?
The recent hwaccel changes wouldn't have affected NVIDIA setups.
Plain RO HQ i imagine, not manually updated madVR or something like that?
-
Do you have any feeling when it started? Before 107, which updated LAV?
The recent hwaccel changes wouldn't have affected NVIDIA setups.
Plain RO HQ i imagine, not manually updated madVR or something like that?
Yes, before 107, I believe. It's been about since mid December, I think.
Not manually updated madVR.
-
I'm somewhat inclined to turn hwaccel for AMD GPUs off again, its apparently a stability nightmare, and even worse, one I cannot reliably reproduce.
In any case, try turning off hardware accel decoding.
It doesn't need to be on by default (and probably shouldn't), but don't disable it entirely. It's a pain to have to have an external LAV Video filter on the filter chain just to be able to enable DXVA2. I haven't had a single issue watching a video with DXVA2 enabled in the 2-3 years I've been using DXVA2 on my AMD GPUs.
Adding a "Warning, can cause stability issues" to the use hardware accelerated decoding option might be helpful so that it discourages users from enabling it just to enable it because it sounds like something that is beneficial. That way only people who really understand what it is and know for sure that they want it enable it.
-
Are you using the 111 build?
I thought I was. Have updated, and will monitor.
-
Do you have any feeling when it started? Before 107, which updated LAV?
The recent hwaccel changes wouldn't have affected NVIDIA setups.
Plain RO HQ i imagine, not manually updated madVR or something like that?
On my side I've faced the same kind of problem with an ATI 5670, everything was working fine until 19.0.108. I've watched a movie (on BRD) last week-end where there were a lot of slow down in the image stream.
After having checked the configuration I finally switched off the HW acceleration and everything is working smoothly now.
-
On my side I've faced the same kind of problem with an ATI 5670, everything was working fine until 19.0.108. I've watched a movie (on BRD) last week-end where there were a lot of slow down in the image stream.
After having checked the configuration I finally switched off the HW acceleration and everything is working smoothly now.
Just to add that few days before I've updated the ATI driver to the most recent delivery, maybe a side effect. I not yet investigated more than that.
-
It doesn't need to be on by default (and probably shouldn't), but don't disable it entirely.
Its not default, but many people apparently just enable it without thinking too much about it.
-
Its not default, but many people apparently just enable it without thinking too much about it.
Well, if a fast computer is a good thing - accelerating it has to be good too. ;)
-
Have you changed the queue sizes in the madVR configuration? Is it set to "delay playback start until render queue is full" ?
-
sounds a similar problem that i am having using nvidia hardware
http://yabb.jriver.com/interact/index.php?topic=86935.0
-
I'm curious why anyone would think that reducing load on a CPU would be a bad thing - i.e. turning off HW Accel on any card - why would you spend £££'s on a card with Gigs of memory and a super fast GPU - then do the some of the video processing in a CPU is just plain crazy.
I've had many issues with stutter, delays and hangs but all have been eliminated over time and were a variety of search indexing, background process's, refresh rates, driver versions and outright interference by the operating system, even AV amplifier issues.
What is your playback chain ??
I know this is going to upset some but have you tried things like Media Player via Shark 007 Codecs - does it behave the same - have you checked out what your CPU is doing at the time, does it do it when windowed or only when full screen etc? I guess what I'm saying is does the behaviour exist in other players / codec / playback chains?
-
Have you changed the queue sizes in the madVR configuration? Is it set to "delay playback start until render queue is full" ?
The option is unchecked.
CPU queue size: 12
GPU queue size: 8