rlaphoenix

> > > But there can still be a confusion. The YUVRGB_Scale is not intended to signal the range of the input video, but rather how to scale when converting...

It would also be problematic to unflip the value if people are unaware this change occurred and were used to the flipped methodology. As in, they may have gotten used...

By the way, I *still* don't see **any** difference in the dubhater example. At all. None. I even made interactive before/after comparisons to quickly switch between them to try and...

> > > There's one more point I'd like to make here. In the DGIndex tools the YUVRGB_Scale option only affects the YUV->RGB conversion performed by vfapi. But vfapi is...

> I'm just saying, get rid of that and simply set _ColorRange depending on what you think about the source video. You can put the prop set line in your...

> > > Now the scale is simply ignored and _ColorRange is unset. I'll leave this open for a bit in case someone has a better idea later but it's...

> > > Ha! I had time to look. It is not specified in the MPEG2 syntax. But NVDec returns some fields for video signal description (one of which is...

> clip = core.d2v.Source(d2v_file_indexed_by_d2vwitch_with_defaults) if loading m2t video using d2vwitch and using defaults, which is --index-range "limited", indexing it, rgb colors are washed out and vapoursynth shows _ColorRange 0 which...

The model isn't matching the architecture, your probably using an `old-arch` created model on the current arch. (or the other way around) Try run [transfer_RRDB_models.py](https://github.com/xinntao/ESRGAN/blob/master/transer_RRDB_models.py) on the model

By the way, I did a LIST "" % and it did in fact list the "INBOX" mailbox