madVR - high quality video renderer (GPU assisted) [Archive] - Page 487

Gagorian

5th March 2014, 20:15

Madshi, can i know why do you prefer 7xxx series over the new series?

THX-UltraII can i know how much NNedi32 chroma upscaling neurons can you set, without dropped frames, with your r8? And with image doubling? Naturally i am talking about bluray 1080 24p material. Thank you

The 'new' cards i.e. r7 250x, r7 260(x), r7 265, r9 270(x) and r9 280(x) are rebranded 7xxx series GPU's.

Personally I see the r9 270 as the sweet spot for HTPC usage, but opinions might differ. The r9 270 can easily run Jinc3 AR for scaling, Error Diffusion and Debanding with maximum quality settings. If you want NNEDI32 doubling combined with those, you might need a more powerful GPU (unless madshi/AMD manages to reduce OpenCL interop costs :D).

flashmozzg

5th March 2014, 20:21

I don't think it is, considering DC options require a DX11 card.
When running on older cards, it just silently falls back to ordered dither, afaik.

Well, it just that madvr is dx9 and for openCL dx9 interop was used.

Shiandow

5th March 2014, 20:25

I'm not 100% sure about the exact cause of the blinking problem, either. I *think* it's just the irregular interval at which the dithering pattern changes, but I'm not totally sure...

I just succeeded in recreating the 'blinking' effect by just replacing the video with noise. As far as I can tell it is a limitation of the screen. In my case I suspect my screen takes too long to get to full brightness so the frame that is shown longer gets brighter. In theory this shouldn't happen with screens with particularly low latency, like projectors or CRTs. Smooth motion should also help, but that doesn't seem to be the case.

DigitalLF

5th March 2014, 20:33

This question is asked a lot, and there's no simple answer. It all depends on which algorithms you want to use, which input/output resolutions need to be supported and which movie framerate and display refresh rate etc. Just as an example: If you need support for 60p, the GPU has to be almost 2.5x as fast as it would have to be if you limited yourself to 24p. So that shows clearly how much all of this depends on your exact requirements.

AMD and NVidia have their own set of advantages and disadvantages, so I can't give a clear recommendation for either one, either. If you decide to get something from AMD, you should definitely get a 7xxx series GPU.

well the new projector is a Sony VPL-VW500ES 4k projector.. so for me to get the best picture.. what card should i use?

would i still get a 7xxx or should i get a 280x/290/290x?

most source material is 1080p24 so i honest don't know what i should buy.. i will spend alot of time testing everything out later on but my knowledge around it all is very limited so i will be back :) i will get it ISF calibrated and i will probably use some filters and pre/post processing...

huhn

5th March 2014, 21:09

Kinda strange, it seems like randomly that 120fps file huhn posted wants to playback @ double speed in FSE + Smooth Motion (CTRL+E a few times in FSE with MPC-HC), but only when using a 60hz refresh rate. Probably the same thing causing iSunrise's issue.

i can reproduce this with 87.5 and older version.

seiyafan

5th March 2014, 21:23

I will test a R9 290x later to see what's the top of the line AMD card can do with MadVR. :D

Meanwhile can someone with Titan/Titan Black/780Ti put up some numbers too?

leeperry

5th March 2014, 21:27

w00t new build, :thanks:

I was wondering if any of this info can or should be used in the device calibration settings for gamma
I don't think you can trust what its EDID says due to the panel lottery and the white point is prolly wrong as I would guess that you didn't run a proper calibration, I would measure them with a sensor.

One thing you could do is input those figures in this script (http://www.avsforum.com/t/912720/) and if you're lucky the gamut coordinates wouldn't be too far off.

would i still get a 7xxx or should i get a 280x/290/290x?

Two things come into play IMHO:

1) It's often better to be one generation late with computer parts, much higher bang/bucks most of the time and due to Moore's law improvements aren't quite giant steps anymore.

2) the new line-up is mostly rebranded chips, I believe they only bring Mantle to the table and AMD is well aware that they kill nvidia in raw OpenCL performance so street prices are pretty high now.

I see 2GB 7870's sold for 99€ shipped around here and 3GB 7950's for 125€, these boards will make your day in mVR at 1080p. No idea about 2160p but if you wanna crank 64x NNEDI, you will need something faster than a 7950 IMHO.

jaju123

5th March 2014, 22:02

w00t new build, :thanks:

I don't think you can trust what its EDID says due to the panel lottery and the white point is prolly wrong as I would guess that you didn't run a proper calibration, I would measure them with a sensor.

One thing you could do is input those figures in this script (http://www.avsforum.com/t/912720/) and if you're lucky the gamut coordinates wouldn't be too far off.

Two things come into play IMHO:

1) It's often better to be one generation late with computer parts, much higher bang/bucks most of the time and due to Moore's law improvements aren't quite giant steps anymore.

2) the new line-up is mostly rebranded chips, I believe they only bring Mantle to the table and AMD is well aware that they kill nvidia in raw OpenCL performance so street prices are pretty high now.

I see 2GB 7870's sold for 99€ shipped around here and 3GB 7950's for 125€, these boards will make your day in mVR at 1080p. No idea about 2160p but if you wanna crank 64x NNEDI, you will need something faster a 7950 IMHO.

I have 2x AMD R9 290s and I can't even use NNEDI doubling :( Too many dropped frames...

JonnyRedHed

5th March 2014, 22:05

Hello,

A long time lurker, since the first post. I try and follow the thread best I can but am not very technical.

I've just updated to v0.87.5 and tried image doubling default values and get a mostly black screen when on full screen, with some reds and blues showing.

I read the line in the changelog:
* error diffusion now uses DirectCompute (DX11 GPU needed) instead of OpenCL

Does this mean NNEDI3 image doubling now works with Nvidia gpus. Mine is a GTX 670

Win7 x64
Zoom Player 8.7 b33
Lav filters 0.61 (DXVA2 - native)
NV GTX 670 (drivers 331.82)
Plasma 50 inch via HDMI

Playing 99.9% MKV 1080p and 720p TV shows/movies but was just trying the image doubling out for the first time on a 720x476 mkv (Star Trek Voyager)

Usually use:

Chroma Jinc 4 (AR)
Image upscaling Jinc 4 (AR + SLL)
Image downscaling Catmull-Rom

I did change image upscaling to Lanczos AR as Madshi suggested some pages back when NNEDI3 was introduced.

Do I have to wait until Nvidia fix something in the drivers, or do I need to change some MadVR settings in this new release to get image doubling to work. Seems what ever I do, once I go full screen its just black with some reds and blues showing. Then crashes zoom player.

Could I ask for guidance here please.

huhn

5th March 2014, 22:07

image doubling is buggy with newer nvdia driver you have to use older ones or wait for a fix

laverdure

5th March 2014, 22:10

Hello,

A long time lurker, since the first post. I try and follow the thread best I can but am not very technical.

I've just updated to v0.87.5 and tried image doubling default values and get a mostly black screen when on full screen, with some reds and blues showing.

I read the line in the changelog:
* error diffusion now uses DirectCompute (DX11 GPU needed) instead of OpenCL

Does this mean NNEDI3 image doubling now works with Nvidia gpus. Mine is a GTX 670

Win7 x64
Zoom Player 8.7 b33
Lav filters 0.61
NV GTX 670 (drivers 331.82)
Plasma 50 inch via HDMI

Playing 99.9% MKV 1080p and 720p TV shows/movies but was just trying the image doubling out for the first time on a 720x476 mkv (Star Trek Voyager)

Usually use:

Chroma Jinc 4 (AR)
Image upscaling Jinc 4 (AR + SLL)
Image downscaling Catmull-Rom

I did change image upscaling to Lanczos AR as Madshi suggested some pages back when NNEDI3 was introduced.

Do I have to wait until Nvidia fix something in the drivers, or do I need to change some MadVR settings in this new release to get image doubling to work. Seems what ever I do, once I go full screen its just black with some reds and blues showing. Then crashes zoom player.

Could I ask for guidance here please.

NEEDI doubling works with nVidia with driver 327.23 and below. Downgrade you nVidia drivers for NEEDI.
Error diffusion is fine on any nVidia driver

JarrettH

5th March 2014, 22:12

I forget what the answer to this is, but how does LAV's dithering options interact with madvr's? Thanks for the new release :)

nevcairiel

5th March 2014, 22:14

I forget what the answer to this is, but how does LAV's dithering options interact with madvr's? Thanks for the new release :)

It doesn't, unless you screwed up LAVs configuration.

In general it won't need to dither anything when madVR is used, as long as you didn't disable any output formats in LAV.

JonnyRedHed

5th March 2014, 22:17

Buggy on current NV drivers, ah I see. Thank you both.

Downgrade to driver 327.23, ah that's not so easy when your main computer is your games rig as well as your video-hdmi player.

I'll have to wait for a fix then. Has Nvidia acknowledged the problem yet and given a time frame for fixing NNEDI3.

nevcairiel

5th March 2014, 22:19

Has Nvidia acknowledged the problem yet and given a time frame for fixing NNEDI3.

Acknowledged yes, but you will never get a time frame out of big companies like that.

JonnyRedHed

5th March 2014, 22:21

I see, thank you.

MistahBonzai

5th March 2014, 22:32

Try it and thank me later. ;)
I updated the code, so be sure to copy the 1.4.1 version

Thanks - I had been using 1.3.10 (also have 1.3.12 but it is flawed and crashes MPC-HC) 1.4.1 works just fine - I have it enabled as a "post resize shader". BTW: Anyone expecting obvious razor sharp results need to look elsewhere - this shader is very subtle using the defaults when applied to good quality 720P being upsized to 1080P.

ryrynz

5th March 2014, 23:17

MadVR, LAV and XySubFilter updates all at once, it's like they plan these things :)

Q-the-STORM

5th March 2014, 23:54

any way to manually install an old nvidia driver on a new card?
Got a GTX 780 Ti, but it came out after 327.23, which means the driver is refusing to install...

MistahBonzai

6th March 2014, 00:15

.
.
.

I have tinkered with a calibration setting of pure power curve of 2.5 gamma and pure power curve 2.35 in the gamma correction... but I wasn't happy with the results. I have also tried other combos, and currently have both set at disabled (again not happy with the results). I don't have access to calibration gear, but thought maybe I could get better results if I understood what my TV's gamma is (pure pc, bt.709, etc. etc.) and what the target should be for gamma correction.

I have included screen shots of the two settings in question if there is any confusion about what I am talking about :)

http://i.imgur.com/gBt908q.png

http://i.imgur.com/53KeFtd.png

Thanks in advance,

QB
It's my understanding - and I might be wrong here - that if you are not actually utilizing an external calibration file (yCMS or 3DLUT) you don't "disable the GPU gamma ramps" - I have done extensive display level correction utilizing test patterns but have not used yCMS or 3DLUT.

Under "Color & Gamma" I don't "enable gamma processing" because I hadn't selected "disable the GPU gamma ramps" under "Calibration".

It seems to me that with both selected you may well be working one against the other..no?

cyberbeing

6th March 2014, 00:16

any way to manually install an old nvidia driver on a new card?
Got a GTX 780 Ti, but it came out after 327.23, which means the driver is refusing to install...

NVIDIA drivers use a unified architecture, so any driver which at least supports Kepler (and maybe even prior) should work on a GTX 780 Ti with an inf mod.

Here (https://www.mediafire.com/?7tbms5fxmqaes4e) I've uploaded a modified nv_disp.inf (English) & nv_dispi.inf (International) x64 which adds support for GTX 780 Ti to 327.23.

Overwrite the inf file in C:\NVIDIA\DisplayDriver\327.23\Win8_WinVista_Win7_64\[International|English]\Display.Driver\ and install as normal using the Setup.exe one directory up. Inf mods such as this strip WHQL certification, so standard rules apply for installing non-WHQL drivers on 64-bit Windows.

JustinChase

6th March 2014, 00:19

I really would love to use a sharpen filter but I use JRiver and can't find a way to do it. Madshi did mention one or twice that he could add a means to include a filter ...

Maybe sooner or later, but not in the next build.

Perhaps Nevcariel can help with this, considering his new position with JRiver. Just thinking out loud.

Regardless, thanks Madshi for all that you do for us, and how well you manage all the various opinions and personalities that participate in this thread. I'm constantly amazed at your calmness and rationality!!

Keep up the good work! :)

madshi

6th March 2014, 00:29

Congratulations on dithering options design. You made it comprehensible for casual users.
Thanks!

Bug #167 "dithering produced dithering noise on pure black areas" still exists.
This bug was only apparent when 3DLUT or yCMS where active, unlike the dithered Whites (even without 3DLUT) with ATI card which is a different (real) bug altogether.
Bug #167 also occured without 3DLUT/yCMS, but only with ordered dithering. That part is fixed.

Does this build sync dithering to the video framerate now to prevent flickering? I didn't see it mentioned in the release notes.
Nope. That would noticeably increase rendering times, and the flickering only seems to occur with rather low bitdepth settings.

I know that you're not taking feature requests, but would it be possible to have a keyboard shortcut toggle "disable GPU gamma ramps" ?
No, sorry. I'm afraid of side effects. The whole gamma ramp stuff is quite complicated.

Is DC done by dx9<->dx10/11 interop? If so, how high overhead is?
Yes. The overhead is relatively small. Very very small compared to dx9<->opencl interop (with AMD GPUs).

Madshi, can i know why do you prefer 7xxx series over the new series?
The 'new' cards i.e. r7 250x, r7 260(x), r7 265, r9 270(x) and r9 280(x) are rebranded 7xxx series GPU's.
^

I only meant to say you should *not* get a 6xxx generation AMD GPU or older. Get a 7xxx generation GPU or newer.

I just succeeded in recreating the 'blinking' effect by just replacing the video with noise. As far as I can tell it is a limitation of the screen. In my case I suspect my screen takes too long to get to full brightness so the frame that is shown longer gets brighter.
Yes, that could be an explanation. It's a weird effect, to be sure. Fortunately this is really only a problem with very low bitdepths, where the dithering dots differ a lot from one frame to the next. The higher the bitdepth, the less changes the screen has to do.

well the new projector is a Sony VPL-VW500ES 4k projector.. so for me to get the best picture.. what card should i use?
As I said, it all depends. There is no simple answer. I would have to ask you a hundred questions about which algorithms you want to use and which formats and framerates you need support for before I could give you a good answer. And I don't have the time for that.

most source material is 1080p24
Yes, most. But not all. Take any interlaced source, after deinterlacing it becomes 60p, after scaling to 4K it becomes 4kp60 which is very GPU power consuming.

It's often better to be one generation late with computer parts, much higher bang/bucks most of the time
Maybe, but stay away from AMD 6xxx and older, because 7xxx has brought several important improvements (much faster copyback speeds, better compute performance, just to name 2).

I have 2x AMD R9 290s and I can't even use NNEDI doubling :( Too many dropped frames...
That's too broad a statement. With which source resolution? With which framerate? Only luma doubling or also chroma doubling? With how many neurons? Which algorithms for the other scaling operations? All of this will have an effect. FWIW, I can do luma doubling for 24p content just fine with my HD7770, which should be much slower than your GPU. But this is only with 24p content. For 60p luma doubling my GPU is too slow.

MadVR, LAV and XySubFilter updates all at once, it's like they plan these things :)
The madVR and XySubFilter updates were actually planned to come together. The new LAV release was not coordinated, though.

thanks Madshi for all that you do for us, and how well you manage all the various opinions and personalities that participate in this thread. I'm constantly amazed at your calmness and rationality!!
Thanks!

6233638

6th March 2014, 00:54

Nope. That would noticeably increase rendering times, and the flickering only seems to occur with rather low bitdepth settings.Quite a few people mentioned that they saw this effect in 8-bit when the dither pattern was changing every frame - perhaps it would be a worthwhile "trade performance for quality" option, rather than using static dither patterns as a low quality workaround?No, sorry. I'm afraid of side effects. The whole gamma ramp stuff is quite complicated.Well I can toggle it on and off without any issues right now, the problem is that I have to bring up the config window to do it. I was just hoping for a quick way to change the setting. But I suppose it might introduce unforeseen problems that you don't want to deal with right now.

madshi

6th March 2014, 01:17

Quite a few people mentioned that they saw this effect in 8-bit when the dither pattern was changing every frame
As far as I understand what they saw in 8-bit was not flickering, but a higher noise floor. The higher noise floor is independent of whether the movie framerate matches the display refreshrate or not. I can see the higher noise floor even if framerate and refreshrate match. The flickering only occurs if there's a framerate/refreshrate mismatch. So these 2 things have different causes. Which means that changing the dither pattern for every VSync refresh at 8-bit would neither help reduce flickering (because flickering doesn't exist at 8-bit in the first place) nor would it reduce the noise floor. So it would serve no purpose.

Shiandow

6th March 2014, 01:32

Oh, so the dither pattern didn't actually change every frame when smooth motion was enabled? Well, that solves the mystery of why enabling smooth motion didn't actually help to prevent 'blinking'. Anyway I agree that this 'flickering' probably doesn't occur with 8-bits, and if it does then I can't say for certain whether changing the dither pattern every vsync will actually help. Although it would make all frames equally wrong.

seiyafan

6th March 2014, 01:37

Here's the result of R9 290X

http://s14.postimg.org/dygyleoa7/madvr4.png

This is the result of upscaling to 1440 with a H.265 encoded video, rendering time is 10-30% longer with bluray, ouch! If you are upscaling to 4k expect the time to be even longer. I also tried to "maxed out" MadVR with 256 neurons in both luma and chroma doubling, as you can see, it answered my question of why madshi decided to stop at 256 and not go higher. :P

If graphics card performance doubles every two years, then in 5-6 years you can upscale to 1440 with 256 neurons without frame dropping, for 4k maybe in 7-9 years? Maybe in eight years the high end will be 8k instead of 4k, who knows?

Asmodian

6th March 2014, 02:30

* fixed: #170: Overlay mode sometimes unnecessarily cleared GPU gamma ramps

Nice new version! Thanks a lot for this fix. And everything else too of course. :D

seiyafan

6th March 2014, 02:40

Does "use OpenCL to process DXVA NV12 surfaces(Intel, AMD)" do anything? In my test it reduced rendering time from 38.36ms to 38.24ms.

cyberbeing

6th March 2014, 02:52

Impending Doom (http://blogs.msdn.com/b/directx/p/directx12.aspx) :devil:

Anime Viewer

6th March 2014, 03:16

Just want to double check, in MPC under LAV video decoder, what's a good hardware decoder to use? Is it none?

There are quite a number of things you could take into consideration when deciding if you should use a hardware LAV video decoder, or choose none.

As has been mentioned before on this board using LAV hardware acceleration can lead to faster ms rendering times.

Do you like, or use Smooth Motion with madVR? During my testing of using different LAV video hardware decoder options I found that I'd get dropped frames somewhere along the way (in some cases not until 6 or 7 minutes of video played) if I had Smooth Motion enabled in madVR and any of the hardware decoding options selected in LAV. I've concluded that my video playback is smooth enough without Smooth Motion enabled on my system, and that I'm not a fan of the blur effect that smooth motion adds to some moving objects when its enabled. If you like using Smooth Motion then you should probably set the LAV hardware decoder to none.

Next thing to consider is the power of your CPU and GPU. The more powerful your GPU the more benefit you may see from selecting a hardware decoder. If you have a strong GPU and weak CPU then using hardware acceleration may be the better choice. On the other end of that if you have a strong CPU, but a weak GPU then you may be better with none selected as software will be used, and thus more of the load will be passed to the CPU.

Some Nvidia users seem to prefer to go with one of the DXVA2 options over NVIDIA CUVID because they say CUVID turns the GPU on for 100% of the time CUVID is being used while DXVA2 can fluctuate the GPU usage. If your using a laptop/notebook and viewing your videos while running on the notebooks battery then you'll probably want to run it with one of the DXVAs (or None) instead of CUVID. If you have a noisy fan or cooling system then likewise you may want to choose DXVA2 or None. If you're watching your videos while plugged into an electrical outlet, and you have a quite fan/cooling system then why not let the GPU kick up to full power.

I found in my testing of watching one video with CUVID set to do LAV Video hardware decoding that I had a consistent 5.51ms rendering and 1.51ms present while viewing. While running with the DXVA2 and none options I saw it steadily creep up from 5.56ms to an ever increasing number as video playback continued (22+ms 2 and a half minutes into viewing with DXVA2, and 16+ms at the same point with None selected ... a bug in the readings perhaps...). If you're using a system that is using an AMD or Intel then you don't even need to consider CUVID.

Like most people on this board you'll probably want to experiment and see what gives you good speed while also providing stability and freedom from glitches during video playback. What works best on one system may not be the best settings on others.

ryrynz

6th March 2014, 03:22

Just wondering if maybe we should have 'Delay playback until render queues are full' enabled by default, not having it enabled shows multiple drops frames on playback of the next file in the playlist for me.

seiyafan

6th March 2014, 04:00

Are most of you using MPC-HC or BE? I just tried BE and couldn't figure out how to get MadVR to work.

Asmodian

6th March 2014, 04:03

While running with the DXVA2 and none options I saw it steadily creep up from 5.56ms to an ever increasing number as video playback continued (22+ms 2 and a half minutes into viewing with DXVA2, and 16+ms at the same point with None selected ... a bug in the readings perhaps...).

This is the declocking you mentioned, since madVR only needs a new frame every 33-41ms on 30-24fps content the GPU can declock until if feels it is only fast enough for its workload.

Just wondering if maybe we should have 'Delay playback until render queues are full' enabled by default, not having it enabled shows multiple drops frames on playback of the next file in the playlist for me.

But is that worse then a longer startup time for most users? A few dropped frames right at the start of the video is hard to notice.

Are most of you using MPC-HC or BE? I just tried BE and couldn't figure out how to get MadVR to work.

Zoom Player here. ;)

cyberbeing

6th March 2014, 04:10

Are most of you using MPC-HC or BE? I just tried BE and couldn't figure out how to get MadVR to work.

Options -> Playback -> Output -> DirectShow Video -> MadVR

If you don't see an entry for madVR, you probably downloaded the 64-bit version by mistake. madVR is 32-bit only.

ryrynz

6th March 2014, 04:27

But is that worse then a longer startup time for most users? A few dropped frames right at the start of the video is hard to notice.

Well we do want to avoid dropped frames right? Half a second of longer start up time is hard to notice also.

iSunrise

6th March 2014, 04:35

But is that worse then a longer startup time for most users? A few dropped frames right at the start of the video is hard to notice.
Indeed, that reason alone is debatable.

However, I found out that when you don´t enable this, I couldn´t view some still images, where I just got a black screen instead. If I enabled that option, madVR then filled up the queues (since it´s a still picture, it doesn´t have consecutive frames) and that solved the problem. That was with 0.87.4, however, and all the subsequent test builds.

Now, with 0.87.5 and after I had changed my queues to higher values I suddenly have a black screen all the time and I am not sure what´s the problem. Enabling that option suddenly doesn´t help anymore.

Here´s a test file, which always shows as a black screen for me:
BWRamp.tif (http://www.mediafire.com/download/61mqvls5s20yx1b/BWRamp.tif)

I´m not sure how to solve this "problem" with 0.87.5, yet. If we can reproduce this, this should maybe be reported as a bug?!

MistahBonzai

6th March 2014, 04:35

Here's the result of R9 290X...

This is the result of upscaling to 1440 with a H.265 encoded video, rendering time is 10-30% longer with bluray, ouch! If you are upscaling to 4k expect the time to be even longer.

I really appreciate the performance data you have captured in an easily to digest form. Your dedication is to be commended regardless of public recognition (or not). Others have attempted to simplify the MadVR option choices based on pure performance (objectivity) but eventually became frustrated with the ongoing complexity (never ending exceptions) of the task, not to mention the subjectivity involved in making those choices.

My next upgrade will be a '4K' display - most likely a Sony 55" XBR-55X850A. I currently am using a Sony KDL 40W3000 (for the past 6 years through out numerous PC upgrades) and have been *very* satisfied by how well it has served as an arms-length 'PC monitor'. I've never viewed 'TV' on it... I firmly believe 4K will be of more use to me than most folks intending to use it for 'entertainment' purposes.

Therefore I view your AMD/MadVR/MPC-HC findings with great interest. Don't get discouraged if you think your hard work is going unrecognized - you are learning a hellava lot about how it all plays together (or doesn't) in your bench-marking exercise. Thanks again :-)

cyberbeing

6th March 2014, 04:42

"Delay playback start" unfortunately is not bug free. In the past there have been reports of playback failing to start at all with certain filter combinations, and I even have a couple bugs [1] (http://bugs.madshi.net/view.php?id=104) [2] (http://bugs.madshi.net/view.php?id=5) opened about other quirks with it. This is one of those options which is best left to users to enable themselves, until madshi stabilizes the implementation a bit more.

Here´s a test file, which always shows as a black screen for me:
BWRamp.tif (http://www.mediafire.com/download/61mqvls5s20yx1b/BWRamp.tif)

I´m not sure how to solve this "problem" with 0.87.5, yet. If we can reproduce this, this should maybe be reported as a bug?!

No issue here. Are you sure it's not this bug (http://bugs.madshi.net/view.php?id=142) I reported which is causing your issue?

MistahBonzai

6th March 2014, 04:54

Now, with 0.87.5 and after I had changed my queues to higher values I suddenly have a black screen all the time and I am not sure what´s the problem. Enabling that option suddenly doesn´t help anymore.

Here´s a test file, which always shows as a black screen for me BWRamp.tif (http://www.mediafire.com/download/61mqvls5s20yx1b/BWRamp.tif)

I´m not sure how to solve this "problem" with 0.87.5, yet. If we can reproduce this, this should maybe be reported as a bug?!

Hmmm... Same here. I was viewing images with MadVR earlier today prior to the upgrade from my 'patched' 87.4 to the 87.5 release. Your image displays when launched in a small window but the screen goes black when going full screen. Also the status text appears very large/low rez in the windowed display. Do you intend to log a bug report or should I?

False alarm!! I had a Avisynth script active in FFdshow as an external filter. Disabling ffdshow (avisynth script processing) fixed the issue. Supported images (including BWRamp.tif) display properly. While on the subject of MadVR image viewing..is there a simple way of incrementing through images in a folder? I googled and came up empty...

ryrynz

6th March 2014, 05:12

"Delay playback start" unfortunately is not bug free. I even have a couple bugs [1] (http://bugs.madshi.net/view.php?id=104) [2] (http://bugs.madshi.net/view.php?id=5) opened about other quirks with it.

Are those bugs still there when tested with the latest versions?

JonnyRedHed

6th March 2014, 05:35

I seem to be getting a madvr 0.87.5 crash (it then sends a report - when I can fill out the details before zoom player crashes) and then next time its zoom player that crashes. When I am full screen and click the control bar 'Next track' when at the end of a file. Or use my mouse shortcut button.

Just seems to be whilst in full screen with this new 0.87.5. I'd never seen the madvr crash reporter before today. Very rarely have zoom player crashes, never mind madvr crashes.

Reverting back to default release 0.87.4 fixes the issue.

0.87.5, either clicking next track or letting the video change to the next video on its own whilst in full screen this seems to either crash madvr and brings up the crash reporter, but it then stops the crash reporter as I'm going through its steps, with a zoom player crash. So I rarely get a chance to fill out the madvr crash reporter.

I did lower the cpu queue to 20 and gpu queue to 12 - no effect on the crashing. But reverting to 0.87.4 does fix things as I mentioned.

Zoom Player 8.7 b33
madvr 0.87.5
LAV 0.61.0.0
Win7 SP1 x64
i5 2500k
16 GB ram
NV GTX 670 2GB