AVS Forum banner

JVC Calibration Software V6 For 2015 Models (X9000,X7000,X5000,RS400,RS500,RS600)

562K views 5K replies 364 participants last post by  Dominic Chan 
#1 · (Edited)
JVC Calibration Software V6&V7 For 2015 Models (X9000,X7000,X5000,RS400,RS500,RS600)

As the new version of the software only works with the new models, I decided to create a new thread. I will try to organize it better later as I'm running out of time right now.

DISCLAIMER: When you save the first calibration, the software creates two files: one is a backup file before any changes are made, the other is a your first calibration. Make sure that you save the backup file (with INIT in the name) in a safe place, as restoring that file is the only way to go back to factory settings. A factory reset in the service menu doesn't reverse the autocal changes. These changes are PERMANENT. The only way to go back is to restore a previous calibration file, and restoring the init file is the only way to go back to factory settings. I know that I say to read the manual, but if you don't and corrupt your projector, please don't complain here! This software makes some LOW LEVEL changes, everything in this thread is done under your responsibility. If you don't want to take the risk, hire a professional or don't run this software.

IMPORTANT NOTE: please don't PM me about any of this, post in the thread, there are many other contributors to this thread, you will get a faster answer and it will benefit everyone. Also, please read all the documents linked above (user manual, original thread for V5) and at least the recap posts below as well before asking a question. Chance is that one of these will contain the answer. Thanks!

Supported meters:
At the moment (21 December 2015), the only supporter meters are the Spyder 4 Pro and Elite. A user confirmed that the Spyder TV also worked, at least for the V6 version of the software. JVC have announced they intention to support the Spyder 5, but we don't know when this will happen, or which models will be supported. [EDIT: New version 7 supports the Spyder 5 (Elite/Pro/Express), in addition to the Spyder 4 (Elite/Pro) with V6, link below updated].

Here are a few useful links:

If you're looking for the JVC Autocal Software and calibration thread for the new native JVC 4K models (RS1000/2000/3000/NX5/NX7/NX9), please google "JVC Autocal Software V11" or "JVC projectors Autocal Software V11" and click "show more results" at the bottom of the page if the page on the JVC Autocal V11 doesn't show up.

See posts 9 and 10 for HDR and SDR BT2020 settings and calibration, and this post for an updated procedure: https://www.avsforum.com/forum/24-d...-x5000-rs400-rs500-rs600-62.html#post53734897

See posts 11 and 12 for a comparison between one Spyder 4 Pro and one Spyder 5 Pro https://www.avsforum.com/forum/24-d...000-x5000-rs400-rs500-rs600.html#post39729554

Info on HDR settings, official BT2020 colour profile and f/w update: http://www3.jvckenwood.com/english/...0r_xc6890r_xc5890r_rs600_rs500_rs400_uhd.html

JVC download page for V6 and V7 (2015 models) software & user manual NEW SOFTWARE VERSION V7 with Spyder 5 support, V6.01 still has to be used with Spyder 4: http://www3.jvckenwood.com/english/...0r_xc6890r_xc5890r_rs400_calibrationsoft.html

JVC download page for V5 (2014 models) software & user manual: http://www3.jvckenwood.com/english/...80_xc5880_rs67_rs57_rs49_calibrationsoft.html

Screen adjustment mode table: http://www3.jvckenwood.com/english/projector/screen/

Initial thread for V5 / 2014 models (lots of useful info as the software is very similar): https://www.avsforum.com/forum/24-d...00-usd-msrp/1493203-jvc-auto-calibration.html

Some specific posts in that thread:
Harry's recap: https://www.avsforum.com/forum/24-d...3203-jvc-auto-calibration-3.html#post24486923
Manni's recap: https://www.avsforum.com/forum/24-d...3203-jvc-auto-calibration-7.html#post35130186

How to set-up the HD Fury Linker to disable HDR auto-detection in the JVCs and have the option to enable the dynamic iris in HDR (also without having the PJ forcing Gamma D or a specific user preset when HDR is detected)
https://www.avsforum.com/forum/24-d...000-x7000-owners-thread-704.html#post50839617

Decoding the HDR metadata information for each title using the Linker or the Integral:
https://www.avsforum.com/forum/24-d...000-x7000-owners-thread-768.html#post51600913

Using the HDFury Vertex to switch automatically between SDR and different HDR calibrations on 2015/2017/2018 models (initial release V1.0)
https://www.avsforum.com/forum/24-d...000-x7000-owners-thread-909.html#post55097696

Using the HDFury Vertex to switch automatically between 3D, x.v.color, SDR, HLG and different HDR calibrations on 2015/2017/2018 models (latest release V3.1)
https://www.avsforum.com/forum/24-d...000-x7000-owners-thread-559.html#post55408090 (includes latest Dolby Cinema Emulation and HLG curves)
[EDIT 02-02-18: this is also where to get the latest Dolby Cinema Emulation curves, as well as a brighter and a darker set and a separate version implementing BT2390 in the low end for brighter shadow details.]

Quick How To to control the JVC Projectors from MadVR:
https://www.avsforum.com/forum/24-d...-x5000-rs400-rs500-rs600-55.html#post55519234

Other links and FAQ:

VARIOUS
Cine4home JVC Autocal review: http://translate.google.com/transla...rierung/JVC_X-Serie_Autokalibrierung_X500.htm

What is the INIT backup file, what does it save and what are the other backup files:
https://www.avsforum.com/forum/24-d...-x5000-rs400-rs500-rs600-21.html#post44964306

JVC Autocal with Spyder vs external 3D LUT (eecolor, radiance) and i1d3: https://www.avsforum.com/forum/24-d...0-x5000-rs400-rs500-rs600-2.html#post40044458

How to check the accuracy of a Spyder followed by discussion about meter accuracy:
https://www.avsforum.com/forum/24-d...203-jvc-auto-calibration-12.html#post39218994

@Chad B's method and tools for creating a custom gamut to correct the errors of your specific Spyder unit and improve the Autocal results (needs a more accurate meter, at least an i1d3/C6, preferably an i1pro2 or better spectro):
https://www.avsforum.com/forum/24-d...-x5000-rs400-rs500-rs600-49.html#post50950289

Slightly modified Chad B method to Autocal SDR Rec-709 and HDR BT2020:
https://www.avsforum.com/forum/24-d...-x5000-rs400-rs500-rs600-53.html#post51480801

Modified Chad B method to Autocal HDR BT2020 and create custom targets for BT2020:
https://www.avsforum.com/forum/24-d...-x5000-rs400-rs500-rs600-63.html#post53770137

Resolving the mystery of the fluctuating brightness after running an Autocal, and how to optimize brightness:
https://www.avsforum.com/forum/24-d...203-jvc-auto-calibration-14.html#post40263266

Why you need 45mn warm-up time before calibrating:
https://www.avsforum.com/forum/24-d...011-new-range-jvc-2014-a-53.html#post23924726

How to position the meter in pictures (thanks to @Dr. Spankenstein):
https://www.avsforum.com/forum/24-d...-x5000-rs400-rs500-rs600-82.html#post55057468

GENERIC GAMMA
Adjusting color temp using the manual gamma controls in the PJ (3-bands) or with the JVC software (11 points): https://www.avsforum.com/forum/24-d...0-x5000-rs400-rs500-rs600-5.html#post42145897

Using the manual "old style" 11 point parametric gamma controls in the JVC software vs using the 3-band gamma controls in the projector after an autocal: https://www.avsforum.com/forum/24-d...-x5000-rs400-rs500-rs600-10.html#post43480434

Saving the gamma curve after modification using the JVC software: https://www.avsforum.com/forum/24-d...-x5000-rs400-rs500-rs600-12.html#post43587882

HDR GAMMA / BT2020

HDR 101: Quick Summary on the state of HDR on the JVCs by Stevenjw and Stranger89 as of Feb 21 17:
https://www.avsforum.com/forum/24-d...000-x7000-owners-thread-716.html#post50943577

Do you need to rerun the gamma autocal for the BT2020 profile?
https://www.avsforum.com/forum/24-d...-x5000-rs400-rs500-rs600-10.html#post43424994

Do I need to rerun a gamma calibration for gamma D?
https://www.avsforum.com/forum/24-d...-x5000-rs400-rs500-rs600-10.html#post43424994

More info on the Rec-2020F/NF and Rec-709F/NF custom profiles (see below as well):
https://www.avsforum.com/forum/24-d...0-x5000-rs400-rs500-rs600-3.html#post40573498 and https://www.avsforum.com/forum/24-d...-x5000-rs400-rs500-rs600-21.html#post45042946 as well as https://www.avsforum.com/forum/24-d...000-x5000-rs400-rs500-rs600.html#post39729530

PQ GAMMA Calibration

[EDIT 02-02-18: most of the information below is obsolete. The only curves of mine that I recommend using are those included in the JVC Macro Pack for the Vertex. Of course feel free to use curves provided by others if they work better for you]

HDR Calibration on the JVCs using a multiplier to scale the charts:
https://www.avsforum.com/forum/24-d...000-x7000-owners-thread-685.html#post50601673

Creating a custom gamma calibration for PQ Gamma to replace Gamma D: https://www.avsforum.com/forum/24-d...000-x7000-owners-thread-685.html#post50609353

How to import a custom gamma profile:
https://www.avsforum.com/forum/24-d...000-x7000-owners-thread-686.html#post50609841

Screenshot of layout used to calibrate a custom PQ Gamma in Calman and calibration report:
https://www.avsforum.com/forum/24-d...000-x7000-owners-thread-687.html#post50651417

Explanation of the various options to deal with Gamma in HDR and report on what's needed from JVC (as of 02/11/17): https://www.avsforum.com/forum/24-d...000-x7000-owners-thread-688.html#post50666657

More details on shaping the PQ Curve and explanation of the custom gamma file name convention:
https://www.avsforum.com/forum/24-d...000-x7000-owners-thread-691.html#post50703857

Details about the new curves in low lamp and quick calibration steps (how to create a custom curve):
https://www.avsforum.com/forum/24-d...000-x7000-owners-thread-693.html#post50732729

Details on adjusting the roll-off
https://www.avsforum.com/forum/24-d...000-x7000-owners-thread-699.html#post50801481

A details on highlights clipping and adjusting the roll-off
https://www.avsforum.com/forum/24-d...000-x7000-owners-thread-742.html#post51278577

Wookii's quick start guide on using Arve's tool (master branch):
https://www.avsforum.com/forum/24-d...000-x7000-owners-thread-718.html#post50960289

New parameters for Arve's tool and three new curves:
https://www.avsforum.com/forum/24-d...000-x7000-owners-thread-745.html#post51341121

Quick explanation of some parameters of Arve's tool:
https://www.avsforum.com/forum/24-d...000-x7000-owners-thread-804.html#post52585441

Zombie10K's screenshots to explain the parameters in the wip branch (thanks Jason):
https://www.avsforum.com/forum/24-d...000-x7000-owners-thread-749.html#post51382465

Latest thoughts on latest curves and low-res version for 130-135nits peakY (800nits max brightness virtual):
https://www.avsforum.com/forum/24-d...000-x7000-owners-thread-748.html#post51376393

Setting brightness in HDR, avoiding a raised black floor and resolving the DI mystery
https://www.avsforum.com/forum/24-d...000-x7000-owners-thread-745.html#post51346873

Using the clipping highlights feature in Arve's tool (wip branch) (thanks @lovingdvd !)
https://www.avsforum.com/forum/24-d...000-x7000-owners-thread-749.html#post51379057

More details on setting brightness in HDR and details regarding the requested testing
https://www.avsforum.com/forum/24-d...000-x7000-owners-thread-749.html#post51385929

Javs' screenshot comparison SDR BT2020 vs Standard HDR vs Custom Gamma
https://www.avsforum.com/forum/24-d...000-x7000-owners-thread-752.html#post51410633

Dolby Vision Cinema Emulation curves (peakY at 107nits for those who can target 95-115nits peak brightness) included in the Vertex JVC Macro pack (the Vertex is only necessary to switch between the curves automatically according to content, you can use the curves by themselves
https://www.avsforum.com/forum/24-d...000-x7000-owners-thread-559.html#post55408090

Projector black floor vs content black floor in HDR
https://www.avsforum.com/forum/24-d...000-x7000-owners-thread-755.html#post51435529

@lovingdvd 's setup guide to create a custom curve (wip branch) Thanks Ric!
https://www.avsforum.com/forum/24-d...000-x7000-owners-thread-759.html#post51467921

Using the new bbi/bbo parameters (wip branch only) and parameters for a slightly updated 800nits curve:
https://www.avsforum.com/forum/24-d...000-x7000-owners-thread-762.html#post51507889

Hard clipping at 4000nits vs hard clipping at 2750nits: what difference?
https://www.avsforum.com/forum/24-d...000-x7000-owners-thread-763.html#post51536881

Changes and explaining the plot info in the threaded branch (supersedes the wip branch):
https://www.avsforum.com/forum/24-d...000-x7000-owners-thread-773.html#post51663985

HDR High Lamp vs HDR Low Lamp calibrations and impact on color volume
https://www.avsforum.com/forum/24-d...000-x7000-owners-thread-836.html#post53730585

Custom Gamma Curves to download:

EDIT 02-02-18: I've deleted all the old curves as they were really old. The only curves I still prove are those in the Vertex JVC Macro pack.

I'm using the jvc tool to create custom curves provided here by Arve (thanks a million Arve, you're a star!). Details in this post: https://www.avsforum.com/forum/24-d...000-x7000-owners-thread-701.html#post50819409

Anyone who wants proper custom curves, learn to use Arve's tool or ask a competent calibrator to do it for you.

Wookii has made a great quick start guide on using Arve's tool: https://www.avsforum.com/forum/24-d...000-x7000-owners-thread-718.html#post50960289

@Dominic Chan has generated manual curves follwoing BT2390. They are targeting 86nits and 130nits. Very good shadow detail.
https://www.avsforum.com/forum/24-d...000-x7000-owners-thread-575.html#post55640884

To install the provided custom curves you need to use the import/export option from the main menu of the JVC Autocal, select gamma data (*.jgd), select the custom gamma profile you want to import the file into, click on "import", select the file you want to load and once the file is loaded, select start

To enable them, select the same custom gamma profile you imported the custom gamma file into, then select "import" as correction value. All the usual gamma settings (picture tone, dark gamma, bright gamma) are locked and greyed out. This is normal. It's a limitation of the custom gamma curves.

It is highly recommended to run a JVC Autocal (gamma+color) at the lamp/iris setting you are going to use so that the RGB balance is done for your HDR mode. This won't correct your custom gamma curve, but as the custom curves below only change white, the RGB balance remains untouched.

PLEASE DO NOT PM me about all this, I don't have the time to answer. Read all the posts linked in the section, and if you still have questions ask them in this thread (I don't participate anymore but there are lots of competent users to help) or in the JVC Owners thread for the RS500 (Which I follow when I can). Others will help there as well.

Good luck!

MORE HELP
You've done your homework, read the manuals, the first posts and all the links above, but still don't get good results. Here are a few tips that might help: https://www.avsforum.com/forum/24-d...-x5000-rs400-rs500-rs600-24.html#post46040009

POTENTIAL ISSUES WITH AUTOCAL
Potential raised levels issue near black after a JVC Autocal when targeting a power gamma curve: detailed report here https://www.avsforum.com/forum/24-d...-x5000-rs400-rs500-rs600-26.html#post46081417

Second report and solutions for the potential raised levels near black with a power gamma calibration: https://www.avsforum.com/forum/24-d...-x5000-rs400-rs500-rs600-28.html#post46137081

Why I stopped contributing to this thread as much as I used to, courtesy of Andreas21: https://www.avsforum.com/forum/24-d...-x5000-rs400-rs500-rs600-28.html#post46172857


Color profiles to download:

[EDIT: note that JVC have now provided an official BT2020 profile, identical to the Rec2020F below. Check the links for the new software at the top of the post to download the official BT2020 profile].

[EDIT 12/09/17: I've attached all the color profiles in a ZIP at the end of this post as the Dropbox links are dead.]

1) Rec-709NF (the profile I've used for my first calibration below):
This is a standard rec-709 profile (with standard coordinates and without the filter), but you get much better results calibrating this custom profile once uploaded to the projector than calibrating one of the existing presets, even fairly good ones like natural.
For example, standard after a JVC autocal will still be oversaturated and won't track perfectly.
This rec-709 profile, once uploaded into a custom profile slot and after an autocal should be very close and should also track very well.
You only need to create custom colour profiles with custom targets to compensate for possible errors in the meter. Otherwise a custom profile with standard targets is all you need.
Here is a version with the filter enabled for those who would like to try to see if the filter allows them to get better black levels:
Rec-709F:

2) DCI/P3: these profiles were made using the standard coordinates provided for DCI in the JVC Software. When you import it in a custom profile slot, make sure you select the filter version if you have one on your model. It also works with a model without a filter, although of course it doesn't reach as far. [EDIT: there is no consumer content using DCI. All UHD consumer content use the BT2020 container therefore should use a BT2020 profile.]
The profile with the filter will engage the filter automatically when a user profile with this colour profile is called.
DCI-P3F (with filter):
DCI-P3NF (no filter):
On my X500, I get around 85% of P3 with the DCI-P3NF custom preset, and it tracks very well up to 75% sat.
Like the rec-709 profiles, this profile tracks better if you autocal it after importing it.

3) Rec2020: these profiles were created using standard rec-2020 coordinates, as rec2020, unlike DCI-P3, isn't an option in the software. [EDIT: there is now an official BT2020 profile from JVC, see link to HDR settings and f/w update at the top of the post. It should be identical to mine but I haven't checked yet.] [EDIT2: confirmed, they are identical]
Same, pick up the version you want to use depending on whether your model has a filter or not. You can also select a version without the filter to use in a model with the filter if you want to try to reach as far as possible without losing too much brightness.
REC-2020F (with filter):
REC-2020NF (no filter):
I haven't done extensive tests with this one but it seems to be working fine.
Like the rec-709 profiles, this profile tracks better if you autocal it after importing it.
 

Attachments

See less See more
#2,655 ·
Depends on which version of Autocal you use. Good news is that the same page where you download Autocal will also have info about which meters are compatible.
 
#2,657 ·
Clarifying question...for basic (non expert lol) testing of black clipping using Arve tool, bbo function and the black clipping track from Ryan Masciola, I should set bbo so that line 77 is perfectly black and faintly see 81? I know there are more technical discussions going on but is this a good start?
 
#2,659 ·
Yes, that is the best practice/most common recommendation, IIRC, with the Arve tool.
That might change though as we're doing tests at the moment to figure out 1) if there are only a couple of 0.005nits titles with raised blacks (Lucy and Oblivion led us to think it was the majority, but in fact it might just be a few poorly mastered early masters) and 2) if clipping black at 77 instead of 64 leads to any significant black crush or not.

We're discussing this in the main 2015 models thread, so I suggest anyone interested follows that.

Otherwise, the recommendation is the same as always: if you want to do it correctly, black is 64 and you resolve down to 68 (legal curve). If you want avoid raised black in some titles (not sure how many, it might be just a couple, so far less than initially expected), then black at 77 and resolve down to 81 (illegal curve), knowing that it might/will cost you a minor loss in shadow details (similar to clipping level 17 in HD).
 
#2,658 ·
Yes, that is the best practice/most common recommendation, IIRC, with the Arve tool.
 
#2,660 ·
Everest is another title with the black issue. Seems it was only a handful of initial Universal titles that had the black issue.
 
#2,664 ·
Alright all, so I screwed up my last autocal, lost probably at least 10% of my Lumens, not exactly sure how much as I didn't note the before/after.

So now the question is, how do I get it back. I know I've seen Manni reference losing brightness after autocal, do I have to reload my INIT file and start over?

I don't recall seeing much discussion on correcting a "bad" autocal.
 
#2,665 · (Edited)
There is no need to restore the INIT file, as this will reset all your autocals, not just the last one you "screwed", provided you run more than one during each session (one for different modes, i.e. SDR, HDR, etc). If one Autocal isn't satisfactory, just run another one over it without changing the iris/cmd/filter settings until you get good results and keep going. If you want to get back to your last autocal results, it's much better to restore the last backup (the one saved after your last autocal of your last mode/combination of settings at the end of your autocal session). That means you'll get back to what you had just before your "screwed" autocal session, for all your calibrations. You won't get back to what you had after your last successful one, due to lamp, panel, filters drift etc.

Each backup file, saved when you save the Autocal, saves the PJ state just after the Autocal session just saved, for ALL the calibrations. The INIT file is exactly the same, except it's BEFORE you've run any calibration. It's just the state of the PJ for ALL calibrations BEFORE you run the first one. Due to lamp/panel/filter drift, it's only exceptionally useful to go back there and almost never a good idea to restore it, except when the PJ is new/almost new.

First thing to check is the meter. If it has drifted it could be the reason for the brigthness loss. The Spyders have plastic filters so they do drift after a while if you don't keep them in Peli-case with dessicant, which slows down the process but doesn't entirely prevent it.

Is your brightness loss right after the autocal, or after you correct the gains at 100% white?
Have you selected the correct screen (especially if your screen isn't color neutral)?
Have you corrected the errors of the Spyder with a matrix using a reference meter?
Have you checked during the autocal that the log didn't show any zero gamma measurement near black?
Which measurement is wrong? The P3 filter and the panels can drift too, so there are things against which there is little you can do: poor saturation tracking in BT2020 due to filter drift, gamut shrinking due to panel drift, brightness drop due to lamp aging.

If you tell us what is "screwed" it will be easier to diagnose if it's the meter, the user, the PJ, the lamp or a combination these. Hopefully, you measured your "before" state with another software and a better/reference meter before running the Autocal, so you know what's caused by the Autocal and what's not. If you haven't, it's highly recommended to do so to be able to identify possible issues due to PJ drift (lamp/filter/panel) that might not be autocal related even if you only notice them after the autocal.
 
#2,667 ·
Hey guys,..working with Ryan Masciola to get his test pattern files to work on ATV4. He sent me the black clipping 2 file to test and it works on ATV4 in 4k as it's saved in my itunes library!!!! See attached, for the first few seconds, the 81 and higher flash grey then black, grey then black and then after the first few seconds, it seems all of them start flashing as in the pic below. Meaning at 64 you can see a very very faint hint of great but definitely can see at 77. Assuming people have used this same file burnt on 4k DVD, do you wait until all the bars are flashing (like after a few seconds) and bbo to make 77 not flash (black)?

Sorry in advance if the file is HUGE...can't figure out how to shrink it down....
 

Attachments

#2,668 ·
I don't know the answer to your question but it is WAY awesome if we are going to see patterns compatible with the ATV4k. I have the soft copy files and the UDH Disk, and this would help me ensure that my ATK4K is outputting the same signal as the UHD player. Thanks!
 
#2,679 ·
Ya, I ordered the package and took some time to download, extract and place in my itunes library on main computer. When I did that, all titles were created in the itunes library but only 64 would show on Apple TV in my library. Was stumped so worked back and forth with Ryan and he finally figured out what was wrong....that is the great news. Bad news is it's a whole rewrite of his pattern files for it to work on ATV4....for the time being I just wanted the Black Clipping and that is what I have now.

Still stumped on why the first few seconds only above 81 flashed grey then for the remainder of the track all above 64 show a bit of grey. Someone on here must have used this same file to dial in bbo so was hoping I could get some input before I do that.
 
#2,677 ·
Manni said above (bold is mine):

You can't simply use BT-2020NF and run the color autocal because whatever gamma you have was calculated either with the right gamut but with a filter (reference) or with the wrong gamut but without a filter (standard). There is no reference-NF preset, so we can't run an autocal for BT-2020NF. I need to run some tests and do measurements to see what the best factory color profile should be used to achieve the best possible calibration with BT2020-NF. It's something I ran into a while ago but completely forgot about, and recently Asharma brought it up (see recent posts) and we said he had to wait until I could find the time. So either you have the time to run all the experiments, or you'll have to wait too. At this stage, I can't make any recommendation regarding how to calibrate with BT-2020NF.
I suspect I'm missing something here, as per Posts 9 and 10 in this thread, providing detailed recommendations for JVC Autocalibration, a Color only Autocal was advised for BT2020-NF, following the Gamma+color Autocalibration using a standard Color Profile and 'normal' Gamma (for each combination of lamp, iris, CMD state, etc.).

This seemed to be an established procedure. Is this now being called into question?

I didn't quote Manni in the usual way, as I don't mean to take him away from whatever he's working on, but there are others here who seem to understand these procedures quite well.

Am I missing something fundamental here, or is a change in the basic Autocalibration procedure for the Color Profile aspect of HDR now underway?
 
#2,678 · (Edited)
Manni said above (bold is mine):



I suspect I'm missing something here, as per Posts 9 and 10 in this thread, providing detailed recommendations for JVC Autocalibration, a Color only Autocal was advised for BT2020-NF, following the Gamma+color Autocalibration using a standard Color Profile and 'normal' Gamma (for each combination of lamp, iris, CMD state, etc.).

This seemed to be an established procedure. Is this now being called into question?

I didn't quote Manni in the usual way, as I don't mean to take him away from whatever he's working on, but there are others here who seem to understand these procedures quite well.

Am I missing something fundamental here, or is a change in the basic Autocalibration procedure for the Color Profile aspect of HDR now underway?
Thanks for not quoting me, appreciated :)

The initial recommendation was correct at the time (probably still the best way to use BT2020NF, although I haven't double-checked that) but that doesn't work with the enhanced method provided by Chad initially and adapted for HDR-BT2020 later, because we don't have the equivalent of a reference-nf profile to correct the meter errors and to calibrate gamma with a gamut that is not entirely different. I guess Chad's original method, that interpolates the corrections from the rec-709 measurements could be used, but I'm not making any recommendations because I need to run some tests to define the best procedure and haven't had the time to do so. I'll do it as soon as I can but right now, I don't want to say anything because the last time I looked at BT2020-NF was a long time ago and our best practice recommendations have changed since, at least if you have a better meter than the Spyder to correct its errors.

If you only use the Spyder, the procedure described in posts 9 and 10 is likely the best way, but I can't guarantee it as I haven't revisited it in a long time.

Of course, if anyone has run the measurements with a reference meter and is able and willing to provide some info in the meantime, they are welcome to do so.
 
#2,682 ·
Where can I find Chad B's fine tuning procedures?
Am very innocent on the error calculation things
 
#2,685 ·
I get error making color calibration - it runs through the calibration but shows no result just error message.
And cant find the reason. Where to look?

Some elements in JVC page 6 (v9 1.1 on a spyder5 on x5500) manual i dont understand:

"After turning on the power of the projector, set to picture mode for calibration" ?

And

"calibration does not work when Color Profile have been set to Off or X.v.color" ?

On my pc running 4k60Hz i can only select rgb 8bit depth- no 10/12 bit is possible - is that good enough?
 
#4,177 ·
I get error making color calibration - it runs through the calibration but shows no result just error message.
And cant find the reason. Where to look?
I am getting the same error messages and 000 results when I try to calibrate with my new spyder 5 elite. The computer and jvc calibration tool seems to recognize the spyder fine.
Did anyone find a solution to this? Or is my spyder defective?
 
#2,687 ·
Hi Guys,

I hope all are well. I am attempting to download some of the custom curves posted as well as utilize the Spyder I purchased to run Auto Cal. I am having a MAJOR problem getting my Ethernet connection from my laptop to my 620 to communicate. I have tried 2 laptops and keep getting “IP Address configuration error”. Can I cannot via an RS-232 to accomplish this, similar to a software update procedure? I would appreciate any feedback. Thank you!

Keith
 
#2,699 ·
I will give it a try! Much appreciated for the suggestion.

Keith
 
#2,694 ·
I just bought a used X550r and I am a little confused about calibration? I have Calman 5 and an i1 Display Pro Colorimeter along with a Lumagen Radiance 2144 which I usually use to auto calibrate the grayscale and 3d Lut. I assume I will use one of the HDMI inputs for the Lumagen and that I can just calibrate as I usually do for HD? The second input I will go right to my Oppo UDP-203 for 4k content, is there anything I can or should do with Calman and the i1 or should I just upload the 2020 profile plus one of the gamma curves that are posted here?
 
#2,695 ·
Calibration Confusion

Hi


Confused on a few things. Reading thru all the posts the Spyder is very accurate, but its the only thing u can use to auto cal. So what I would like to know, if I want to get a good cal. done would I buy the Spyder do the auto. Then what would I need to make this a better cal. Both software and color meter that isn't going to break the bank


Thanks I hope this made sense
 
#2,696 ·
Yes, ideal workflow:

1. Spyder + Autocal = gets close (usually)
2. other meter + other calibration software = fine tune step one.
3. arve tool, to create custom HDR gamma
 
#2,698 ·
I am not an expert in what the best bang for the buck or easiest or most accurate tools are. Personally I use a ColorMunki + HCFR because that is what I already had on hand.

If I was to start from scratch, I'd probably buy a Calman package.

But I am far from an expert in what is easiest or best or the best value.
 
#2,701 · (Edited)
JVC Control with MadVR part 1

Here is a quick How To regarding selecting the relevant calibration in the JVC from MadVR.

This is part 1, I'll post more information regarding the best calibration settings especially when using MadVR's HDR to SDR conversion when I have the time.

I used Stanger89's code from Arve's tool as a starting point to create a python file and a batch file for each user mode [EDIT 20-01-18: now a single batch file with the user mode as an argument]. All the details are in the PDF in the attached ZIP.

With these, you can ask MadVR to select a specific SDR-BT2020 calibration in the projector when playing HDR BT2020 content using its pixel shader math HDR to SDR conversion, and select the SDR REC709 calibration when SDR content is next played. [EDIT 20-01-18: the external command implementation is still flaky in MadVR, but hopefully this will be corrected soon).] [EDIT 18-04-18: this is now fixed in V1.3]

This is NOT a step-by-step guide for newbies. It's just to share the knowledge with advanced users so they can help others and make a guide for newbies if they have the time and inclination.

I won't have the time to provide support for this, but it's probably better to keep the discussion in this thread so that we don't hijack the owner's thread with technical posts.

I wrote this very quickly, so please forgive typos etc.

Changelog:

V1.1 Jan-18-2018
  • Minor cosmetic correction in JVC_USER5.PY for all models
  • Added support and extended timeout value from 5 to 15 seconds for DLA-X770R, X7500, RS520, X970R, X9500, RS620 in jvc_command.py.
V1.2 Jan-20-2018
  • Created a unique JVC_COMMAND.BAT accepting the user mode as an argument so there is only one batch file to edit. Syntax is, for example to select the USER1 calibration: JVC_COMMAND.BAT USER1. It accepts any user mode as argument (USER1-6).
  • Corrections to documentation, change of custom profiles (now using the calibration tab to make it possible to select different calibration settings for HDR and SDR) and external commands and new screenshots.
V1.3 Apr-18-2018
  • Added a delay in the JVC_COMMAND.BAT file to make sure the command isn’t sent while the JVC is performing an HDMI sync. Set by default to 20 seconds, feel free to adjust it. 15-18 secs should work fine for most, but with anything lower than that some commands might get lost. Others might need up to 25 secs. This is similar to the delay implemented on the Vertex.
  • Minor corrections to the documentation.
 

Attachments

#2,704 · (Edited)
Here is a quick How To regarding selecting the relevant calibration in the JVC from MadVR.

This is part 1, I'll post more information regarding the best calibration settings especially when using MadVR's HDR to SDR conversion when I have the time.

I used Stanger89's code from Arve's tool as a starting point to create a python file and a batch file for each user mode. All the details are in the PDF in the attached ZIP.

With these, you can ask MadVR to select a specific calibration in the projector when playing SDR BT2020 content using its excellent pixel shader math HDR to SDR conversion (see JVC 2015 owner thread for details), and select the SDR calibration once the HDR content is played.

This is NOT a step-by-step guide for newbies. It's just to share the knowledge with advanced users so they can help others and make a guide for newbies if they have the time and inclination.

I won't have the time to provide support for this, but it's probably better to keep the discussion in this thread so that we don't hijack the owner's thread with technical posts.

I wrote this very quickly, so please forgive typos etc.
Thanks.

Manni FYI, User 5.py prints user 1 not user 5 to the screen in the code.

To others, this doesn't work with the later JVC models besides the XX00 series due to a model number mismatch in Arves code. Right now I am getting an unknown model error. I did some digging and was able to fix it. You need to have the command prompt open to see the unknown model number error in order to find out the model number of the projector, once I had that I went into jvc_command.py and edited the following code lines to include the newer model, so those of you with a JVC model later than the RS600/9000 series you will need to do this, those with the RS640/9900 series will either need to let me know your model number you are getting in command prompt or edit the code yourself to add a new line once again with your model.

'ILAFPJ -- XHR3' is the model number for the RS620/9900 year model projector line. And there is only one model number for the entire line that year, so people with the RS640 and 9900 you will need to attempt to run the batch file inside a command prompt window to find out what your model number is when you see the error and add the new line.

Code:
class Model(ReadOnly, Enum):
    """Projector model code"""
    DLA_X550R_X5000_XC5890R_RS400 = b'ILAFPJ -- XHP1'
    DLA_XC6890 = b'ILAFPJ -- XHP2'
    DLA_X750R_X7000_XC7890R_RS500_X950R_X9000_RS600_PX1 = b'ILAFPJ -- XHP3'
   [B] DLA_X770R_X7500_RS520_X970R_X9500_RS620_PX1 = b'ILAFPJ -- XHR3'[/B]
Save the file, you will now have your model recognised and the picture mode switching will work. P.S there is no user 6 on the newer models either, so I reccomend you just delete those user mode files as they will do nothing.

Now to fix the time out issue reported by manni for selecting picture modes, notably those which include the filter then switching to a mode which does not include the filter, we need to increase the timeout from 5 seconds to 15 seconds in the same jvc_command.py file.

For me, once I had included the new line with my model number, you will need to edit the following value to 15 (in bold). starting at line 561 in the code.

Or more simply, You can just search the file for the term timeout and you should be in the right place.

Code:
def set(self, cmd, val, verify=True):
        """Send operation command"""
        cmdcode, valtype = cmd.value
        assert not issubclass(valtype, ReadOnly), '{} is a read only command'.format(cmd)
        val = valtype(val)
        assert(isinstance(val, valtype)), '{} is not {}'.format(val, valtype)
        try:
            if issubclass(valtype, BinaryData):
                self.conn.cmd_op(cmdcode, sendrawdata=val.value)
            else:
                self.conn.cmd_op(cmdcode+val.value, [B]acktimeout=15[/B])
        except CommandNack as err:
            raise CommandNack('Set: ' + err.args[0], cmd.name, val)

        if not verify or issubclass(valtype, NoVerify):
            return

        verify_val = self.get(cmd)
        if verify_val != val:
            raise CommandNack('Verify error: ' + cmd.name, val, verify_val)
Save again, and all should be well. Mode switching should no longer throw errors.

p.s. There also seems to be a bug with 0.92.11 where for some people the 'Command line to execute when this profile is activated' does not work, unfortunately its not working for me either. Some others may experience the same thing.

There is a bug submitted by another user here: http://bugs.madshi.net/view.php?id=210

I also did download the test build submitted by @madshi on that link, but its still not working for me, it wont even open a text document on my desktop. So I will patiently wait for madshi to resolve it.

I guess I could roll back and see if an earlier version works.
 
#2,705 ·
Hi,

I've been reading in this forum for a long time, especially about the ARVE tool. But this is my first post here.

Last summer while a calibration workshop I met a nice guy from switzerland who showed me the ARVE Tool and helped me with the custom curves.

Then I saw a thread about madVR and the upscaling of Blurays für 4K on facebook from Anna&Flo. Since December I can play 4k content with dynamic HDR.

I made a lot of comparison to my gamma curves and I am as enthusiastic as Manni !

I calibarated my JVC RS-500 to BT.2020. My madVR goes out with BT.2020 Gamma 2.2 12 Bit RGB 4:4:4, no matter what source I have (if it is 24p).
I never have to switch user modes in the jvc. And a great advantage : I don't have the long black screen the jvc's have when you switch modes.

I wrote a short introduction in madVR in german : www . partyfotos . de / madVR /

Greetings from Germany

Bernd
 
#2,706 · (Edited)
Yes but unless you have less than 50nits actual PeakY you are compromising SDR for HDR, or HDR for SDR if you keep the same BT2020 calibration for SDR and HDR. You need to select a different baseline for each otherwise you are raising the black floor and killing your on/off contrast in SDR if you use the best calibration for HDR (high lamp, iris open, filter on), or you are killing the highlights in HDR if you are using the best calibration for SDR (lowest iris setting to get 50nits, usually low lamp, no filter).

It works great if you don't mind the compromise.

I'll soon post recommendations to get the best for all content, based on the JVC control posted here.

I've updated it to V1.1:

Changelog:

V1.1 Jan-18-2018: minor cosmetic correction in JVC_USER5.py, added support and extended timeout value for more recent models. The issue with MadVR not sending the command on exit is still there, included with the latest test build. I have no problems with the commands when I launch the .bat files directly, or if I send them in MadVR on start-up. It's only from MadVR that the batch that should run on exit doesn't run. Will investigate in MadVR's thread and update here when fixed. Full change log in the PDF. There is no need to update from V1.0 to V1.1 if you don't have a more recent model.
 
#2,707 ·
I narrowed down the issue to Kodi not being able to execute python scripts, no matter how many .bat files its buried under at the end of the day its still the Kodi app which is executing them, it seems because Kodi has its own Python installation, it seems to be attempting to run it from that and its encountering errors.

One I figured out to chain bat files thanks to @madshi for troubleshooting if MadVR was the cause (it is not) then I finally got some dos output on what's actually going on.



Still troubleshooting this, but I am assuming this issue is going to affect all Kodi users attempting to do these MadVR user mode switching scripts.
 
#2,708 ·
It's probably a matter of PATH settings or something like that. If you figure it out, you should be able to fix it by manually setting the PATH (or some other SET variable), working directory etc in the batch file before running the python file. Or alternatively do "C:\CorrectPythonPath\python.exe some.py" to force the right python version to be used.
 
#2,709 · (Edited)
Hi Madshi,

I was about to post in the MadVR thread but let's do it here if you prefer.

No it's not a path issue, at least here.

I've done more testing with the external commands, using only MPC-BE to rule out possible issues with MCE/MyMovies.

If I launch my .bat files directly from the desktop, they all run fine.

If I launch them from the external command when the profile is enabled, they run fine too.

If I swap the one that should run when the profile is disabled with the one that runs fine when the profile is enabled, it runs fine too.

So as far as I can see, the external command works fine when the profile is enabled, but not when the profile is disabled.

I always add a pause command to batch files when I do testing, and as far as I can see there is no command file launched at all on profile disable.

I tried the test build and it doesn't change anything.

I'm not sure this calibration thread is the best place to discuss this, so please let me know where you'd like to take the discussion.

Thanks!
 
#2,717 ·
Solved the issue with MadVR on custom profile disabled, will explain in next version when I post a revision but the gist is that the command on disable in only launched when the content changes, i.e. when you start another video calling a different profile. It makes sense and it means the Vertex should pick up the change the next time content is played if not HDR. It's just not possible to get SDR 709 back for the interface after playback of the HDR title. No big deal. Moving on to calibration/settings now that it's possible to call the correct calibration automatically.

I've asked Madshi to see if he could find a way to use a custom API to report SDR BT2020 so that the Vertex can pick it up and we wouldn't need the JVC Control from MadVR at all if we have a Vertex. This would be better for iRule users (or anyone using IP control to control the JVC, as this is not compatible with MadVR IP control in parallel) who are forced to use a universal IR remote (as RS-232 is used by the Vertex).
 
Top