Broken Pipe Error Message, Sluggish Speed, Aborted Error Messages

[decayedxistence]

Mac OS Seqouia, Intel
DisplayCal 3.9.14
Argyll 3.3
Resolve 19.1

When DisplayCal 3.9.14 was released in October, it was working great and I was able to profile a 3D LUT for Resolve with almost zero issues. I just went back to run a new calibration today and there are a bunch of errors and issues with running the program.

DisplayCal is running very slow in general and when detecting my probe, Constant connection problems in resolve resulting in "Broken Pipe" error messages when trying to connect to DisplayCal via Portrait Displays Calman Network address.

Have tried restarting Resolve as well as the computer, disconnecting and reconnecting the probe and still not working.

I also get this error box that pops up when I choose a different setting like, "3D LUT for Resolve" or if I click on any tab:

[Adam-Color]

Hello, can you go to tools > show log window, go through the errors, and copy the log window into a comment here?

Also, please make sure neither device has a VPN enabled and that they are on the same network.

I'm also curious what you mean by "constant connection issues" in your original post - like does resolve show it disconnecting and reconnecting or is everything just running slow?

[decayedxistence]

Hello, can you go to tools > show log window, go through the errors, and copy the log window into a comment here?

Also, please make sure neither device has a VPN enabled and that they are on the same network.

I'm also curious what you mean by "constant connection issues" in your original post - like does resolve show it disconnecting and reconnecting or is everything just running slow?

Will see if I can pull up the logs and paste them in a new comment.

No VPN enabled anywhere and they are indeed on the same network.

"Constant Connection Issues" - When I go to workspace>monitor calibration and click "connect" (to connect to displaycal) it says, "connecting" on the resolve port window and then says "connection interrupted" and disconnects.

When launching DisplayCal, it takes probably 30 seconds to launch, then if I click the refresh icon on the main page to make sure my probe is detected, that takes around 30 seconds or more. If I click over to the profiling tab or 3d lut tab, I get that error icon box (in the above image) that says "...aborted". If I click on the settings pull down tab, DisplayCal will freeze and not respond.

Getting a different port number in resolve as well - normally it ends in .138

[decayedxistence]

No logs showing up in DisplayCal even though I'm getting error messages in DisplayCal.

I also tried uninstalling and reinstallding DisplayCal as well as ArgyllCMS with no change.

[decayedxistence]

Following up on this thread -- I also sent a support ticket to Blackmagic as when I open Monitor Calibration > Portrait Displays Calman, Resolve will freeze. If I try to connect to the IP address, it still fails.....So, if DisplayCal on Mac Intel is running well for others, it may be a bug in Resolve 19.1.2 that I'm experiencing.

[Adam-Color]

Following up on this thread -- I also sent a support ticket to Blackmagic as when I open Monitor Calibration > Portrait Displays Calman, Resolve will freeze. If I try to connect to the IP address, it still fails.....So, if DisplayCal on Mac Intel is running well for others, it may be a bug in Resolve 19.1.2 that I'm experiencing.

I just tested it with almost exactly your same setup on resolve 19.1 and got no issues. Although some things are indeed loading slower, the calibration part went smoothly for me.

Not much I can do to help without logs... if you are able, can you try to run displaycal -d in a virtual environment after installing it through pypi? (see this)

Adding -d after displaycal with give you the debug statements I need in the terminal.

[decayedxistence]

I have the .dmg package installed and have been using that but I will try uninstalling and installing through pip tomorrow and running it virtually to see if that helps and will send any logs if I can get it up and running.

I really want to try a new calibration with your method to get the correct video levels and 2.4 relative curve instead of my backdoor fix which doesn't give me the right levels.

[decayedxistence]

Alright, got the virtual environment up and running but now I'm getting "dispread" errors where my instrument is not read and the patches don't change.

[Adam-Color]

Alright, got the virtual environment up and running but now I'm getting "dispread" errors where my instrument is not read and the patches don't change.

go into the app about page and make sure argyll cms is on version 3.3.0. Maybe also run a quick tools>detect display devices and instruments.

If this dosen't work, you may need to "unlock" your i1 displaypro by briefly opening the calibrite software, basically just to let your i1 know it's safe to "unlock" itself.

[decayedxistence]

Argyll is correct. Tried opening profiler and still getting dispread error. Also getting a no such file or directory warning. The initial grey measurement box pops up and when I try to start the profiling, it just stays white.

(appreciate all of the help by the way)

[decayedxistence]

Last login: Mon Dec 30 14:48:51 on ttys000
@macbook-pro ~ % displaycal -d
[D] pydir: /Library/Frameworks/Python.framework/Versions/3.13/lib/python3.13/site-packages
[D] dirname(os.path.abspath(sys.argv[0])): /Library/Frameworks/Python.framework/Versions/3.13/bin
[D] pydir parent: /Library/Frameworks/Python.framework/Versions/3.13/lib/python3.13
[D] from sys.path: /Library/Frameworks/Python.framework/Versions/3.13/lib/python3.13/site-packages/DisplayCAL
[D] Data files search paths:
[D] /Library/Frameworks/Python.framework/Versions/3.13/share/DisplayCAL
[D] /Library/Frameworks/Python.framework/Versions/3.13/lib/python3.13/site-packages
[D] /Library/Frameworks/Python.framework/Versions/3.13/lib/python3.13/share
[D] /Library/Frameworks/Python.framework/Versions/3.13/lib/python3.13/share/DisplayCAL
[D] /Users/christopherpiccione/Library/Application Support/DisplayCAL
[D] /Library/Application Support/DisplayCAL
[D] /Library/Frameworks/Python.framework/Versions/3.13/lib/python3.13/site-packages/DisplayCAL
Acquired lock file: <DisplayCAL.main.AppLock object at 0x106d96510>
displaycal 3.9.14 2024-10-15T23:51:58Z
Mac OS X 15.2 x86_64
Python 3.13.0 (v3.13.0:60403a5409f, Oct 7 2024, 00:37:40) [Clang 15.0.0 (clang-1500.3.9.4)]
CA file /Library/Frameworks/Python.framework/Versions/3.13/lib/python3.13/site-packages/certifi/cacert.pem
Faulthandler
wxPython 4.2.2 osx-cocoa (phoenix) wxWidgets 3.2.6
Encoding: utf-8
File system encoding: utf-8
Loading /Users/christopherpiccione/Library/Preferences/DisplayCAL/DisplayCAL.ini
Existing client using port 15411
Connecting to 15411...
Connection to 127.0.0.1:15411 failed: [Errno 61] Connection refused
listening
writing to lock file: port: 54743
Starting up...
[D] Setting ARGYLL_NOT_INTERACTIVE 1
[D] argyll_version [3, 3, 0]
[D] ARGYLL_NOT_INTERACTIVE 1
[D] wrapup(copy=False, remove=True)
SDL2: None
SDL2_mixer: None
Audio module: wx 4.2.2
[D] check_argyll_bin OK
Enumerating display devices and communication ports...
/Users/christopherpiccione/Library/Application Support/DisplayCAL/dl/Argyll_V3.3.0/bin
[D] Setting ARGYLL_NOT_INTERACTIVE 1
[D] argyll_version [3, 3, 0]
[D] ARGYLL_NOT_INTERACTIVE 1
ArgyllCMS 3.3.0
Argyll has virtual display support
...ok.
Initializing GUI...

input_value_clipping_bmp should have been hidden
output_profile_ctrl should have been hidden
<class 'wx._core.Panel'> panel
<class 'wx._core.Panel'> headerbordertop
<class 'wx._core.Panel'> headerpanel
<class 'wx._core.StaticText'> calibration_file_label
<class 'wx._core.Choice'> calibration_file_ctrl
<class 'wx._core.BitmapButton'> profile_info_btn
<class 'wx._core.BitmapButton'> calibration_file_btn
<class 'wx._core.BitmapButton'> create_session_archive_btn
<class 'wx._core.BitmapButton'> delete_calibration_btn
<class 'wx._core.BitmapButton'> install_profile_btn
<class 'DisplayCAL.wxwindows.BitmapBackgroundPanel'> panel
<class 'wx._core.Panel'> tabpanel
<class 'DisplayCAL.wxwindows.TabButton'> button
<class 'DisplayCAL.wxwindows.TabButton'> button
<class 'DisplayCAL.wxwindows.TabButton'> button
<class 'DisplayCAL.wxwindows.TabButton'> button
<class 'DisplayCAL.wxwindows.TabButton'> button
<class 'wx._core.ScrolledWindow'> calpanel
<class 'wx._core.ScrollBar'> scrollBar
<class 'wx._core.ScrollBar'> scrollBar
<class 'wx._core.Window'> panel
<class 'wx._core.Panel'> display_instrument_panel
<class 'wx._core.StaticText'> display_box_label
<class 'wx._core.StaticText'> display_label
<class 'wx._core.Choice'> display_ctrl
<class 'wx._core.StaticText'> display_lut_label
<class 'wx._core.Choice'> display_lut_ctrl
<class 'wx._core.BitmapButton'> display_lut_link_ctrl
<class 'wx._core.BitmapButton'> detect_displays_and_ports_btn
<class 'wx._core.CheckBox'> whitelevel_drift_compensation
<class 'wx._core.StaticText'> instrument_box_label
<class 'wx._core.Choice'> comport_ctrl
<class 'wx._core.StaticText'> measurement_mode_label
<class 'wx._core.Choice'> measurement_mode_ctrl
<class 'wx._core.CheckBox'> blacklevel_drift_compensation
<class 'wx._core.CheckBox'> override_min_display_update_delay_ms
<class 'wx._core.SpinCtrl'> min_display_update_delay_ms
<class 'wx._core.TextCtrl'> text
<class 'wx._core.SpinButton'> wxSpinButton
<class 'wx._core.StaticText'> min_display_update_delay_ms_label
<class 'wx._core.CheckBox'> override_display_settle_time_mult
<class 'DisplayCAL.floatspin.FloatSpin'> display_settle_time_mult
<class 'wx._core.TextCtrl'> text
<class 'wx._core.SpinButton'> wxSpinButton
<class 'wx._core.CheckBox'> ffp_insertion
<class 'wx._core.StaticText'> ffp_insertion_interval_label
<class 'DisplayCAL.floatspin.FloatSpin'> ffp_insertion_interval
<class 'wx._core.TextCtrl'> text
<class 'wx._core.SpinButton'> wxSpinButton
<class 'wx._core.StaticText'> ffp_insertion_interval_s_label
<class 'wx._core.StaticText'> ffp_insertion_duration_label
<class 'DisplayCAL.floatspin.FloatSpin'> ffp_insertion_duration
<class 'wx._core.TextCtrl'> text
<class 'wx._core.SpinButton'> wxSpinButton
<class 'wx._core.StaticText'> ffp_insertion_duration_s_label
<class 'wx._core.StaticText'> ffp_insertion_level_label
<class 'wx._core.SpinCtrl'> ffp_insertion_level
<class 'wx._core.TextCtrl'> text
<class 'wx._core.SpinButton'> wxSpinButton
<class 'wx._core.StaticText'> ffp_insertion_level_percentage_label
<class 'wx._core.StaticText'> output_levels_label
<class 'wx._core.RadioButton'> output_levels_auto
<class 'wx._core.RadioButton'> output_levels_full_range
<class 'wx._core.RadioButton'> output_levels_limited_range
<class 'wx._core.StaticText'> colorimeter_correction_matrix_label
<class 'wx._core.Choice'> colorimeter_correction_matrix_ctrl
<class 'wx._core.BitmapButton'> colorimeter_correction_info_btn
<class 'wx._core.BitmapButton'> colorimeter_correction_matrix_btn
<class 'wx._core.BitmapButton'> colorimeter_correction_web_btn
<class 'wx._core.BitmapButton'> colorimeter_correction_create_btn
<class 'wx._core.Panel'> display_instrument_info_panel
<class 'DisplayCAL.wxwindows.HStretchStaticBitmap'> display_instrument_info_shadow
<class 'wx._core.StaticBitmap'> -1
<class 'DisplayCAL.wxwindows.BetterStaticFancyText'> display_instrument_warmup_info_text
<class 'wx._core.StaticBitmap'> -1
<class 'DisplayCAL.wxwindows.BetterStaticFancyText'> display_instrument_info_text
<class 'DisplayCAL.wxfixes.PlateButton'> button
<class 'wx._core.Panel'> calibration_settings_panel
<class 'wx._core.StaticText'> calibration_settings_label
<class 'wx._core.CheckBox'> interactive_display_adjustment_cb
<class 'wx._core.CheckBox'> calibration_update_cb
<class 'wx._core.StaticText'> observer_label
<class 'wx._core.Choice'> observer_ctrl
<class 'wx._core.StaticText'> whitepoint_label
<class 'wx._core.Choice'> whitepoint_ctrl
<class 'wx._core.ComboBox'> whitepoint_colortemp_textctrl
[D] whitepoint_colortemp_textctrl binds EVT_TEXT to focus_handler
<class 'wx._core.StaticText'> whitepoint_colortemp_label
<class 'wx._core.StaticText'> whitepoint_colortemp_locus_label
<class 'wx._core.Choice'> whitepoint_colortemp_locus_ctrl
<class 'DisplayCAL.floatspin.FloatSpin'> whitepoint_x_textctrl
<class 'wx._core.TextCtrl'> text
<class 'wx._core.SpinButton'> wxSpinButton
<class 'wx._core.StaticText'> whitepoint_x_label
<class 'DisplayCAL.floatspin.FloatSpin'> whitepoint_y_textctrl
<class 'wx._core.TextCtrl'> text
<class 'wx._core.SpinButton'> wxSpinButton
<class 'wx._core.StaticText'> whitepoint_y_label
<class 'wx._core.BitmapButton'> visual_whitepoint_editor_btn
<class 'wx._core.BitmapButton'> whitepoint_measure_btn
<class 'wx._core.StaticText'> luminance_label
<class 'wx._core.Choice'> luminance_ctrl
<class 'DisplayCAL.floatspin.FloatSpin'> luminance_textctrl
<class 'wx._core.TextCtrl'> text
<class 'wx._core.SpinButton'> wxSpinButton
<class 'wx._core.StaticText'> luminance_textctrl_label
<class 'wx._core.BitmapButton'> luminance_measure_btn
<class 'wx._core.BitmapButton'> ambient_luminance_measure_btn
<class 'wx._core.StaticText'> black_luminance_label
<class 'wx._core.Choice'> black_luminance_ctrl
<class 'DisplayCAL.floatspin.FloatSpin'> black_luminance_textctrl
<class 'wx._core.TextCtrl'> text
<class 'wx._core.SpinButton'> wxSpinButton
<class 'wx._core.StaticText'> black_luminance_textctrl_label
<class 'wx._core.BitmapButton'> black_luminance_measure_btn
<class 'wx._core.StaticText'> trc_label
<class 'wx._core.Choice'> trc_ctrl
<class 'wx._core.StaticText'> trc_gamma_label
<class 'wx._core.ComboBox'> trc_textctrl
[D] trc_textctrl binds EVT_TEXT to focus_handler
<class 'wx._core.Choice'> trc_type_ctrl
<class 'wx._core.StaticText'> black_output_offset_label
<class 'wx._core.Slider'> black_output_offset_ctrl
<class 'wx._core.SpinCtrl'> black_output_offset_intctrl
<class 'wx._core.TextCtrl'> text
<class 'wx._core.SpinButton'> wxSpinButton
<class 'wx._core.StaticText'> black_output_offset_intctrl_label
<class 'wx._core.CheckBox'> ambient_viewcond_adjust_cb
<class 'DisplayCAL.floatspin.FloatSpin'> ambient_viewcond_adjust_textctrl
<class 'wx._core.TextCtrl'> text
<class 'wx._core.SpinButton'> wxSpinButton
<class 'wx._core.StaticText'> ambient_viewcond_adjust_textctrl_label
<class 'wx._core.BitmapButton'> ambient_measure_btn
<class 'wx._core.StaticText'> black_point_correction_label
<class 'wx._core.CheckBox'> black_point_correction_auto_cb
<class 'wx._core.Slider'> black_point_correction_ctrl
<class 'wx._core.SpinCtrl'> black_point_correction_intctrl
<class 'wx._core.TextCtrl'> text
<class 'wx._core.SpinButton'> wxSpinButton
<class 'wx._core.StaticText'> black_point_correction_intctrl_label
<class 'wx._core.StaticText'> black_point_rate_label
<class 'wx._core.Slider'> black_point_rate_ctrl
<class 'DisplayCAL.floatspin.FloatSpin'> black_point_rate_floatctrl
<class 'wx._core.TextCtrl'> text
<class 'wx._core.SpinButton'> wxSpinButton
<class 'wx._core.StaticText'> calibration_quality_label
<class 'wx._core.Slider'> calibration_quality_ctrl
<class 'wx._core.StaticText'> calibration_quality_info
<class 'wx._core.StaticText'> cal_meas_time
<class 'wx._core.Panel'> calibration_settings_info_panel
<class 'DisplayCAL.wxwindows.HStretchStaticBitmap'> calibration_settings_info_shadow
<class 'wx._core.StaticBitmap'> -1
<class 'DisplayCAL.wxwindows.BetterStaticFancyText'> calibration_settings_info_text
<class 'wx._core.Panel'> profile_settings_panel
<class 'wx._core.StaticText'> profile_settings_label
<class 'wx._core.StaticText'> profile_type_label
<class 'wx._core.Choice'> profile_type_ctrl
<class 'wx._core.BitmapButton'> gamap_btn
<class 'wx._core.CheckBox'> black_point_compensation_cb
<class 'wx._core.StaticText'> profile_quality_label
<class 'wx._core.Slider'> profile_quality_ctrl
<class 'wx._core.StaticText'> profile_quality_info
<class 'wx._core.StaticText'> testchart_label
<class 'wx._core.Choice'> testchart_ctrl
<class 'wx._core.BitmapButton'> testchart_btn
<class 'wx._core.BitmapButton'> create_testchart_btn
<class 'wx._core.StaticText'> testchart_patches_amount
<class 'wx._core.StaticText'> testchart_patches_amount_label
<class 'wx._core.Slider'> testchart_patches_amount_ctrl
<class 'wx._core.StaticText'> testchart_patch_sequence_label
<class 'wx._core.Choice'> testchart_patch_sequence_ctrl
<class 'wx._core.StaticText'> testchart_meas_time
<class 'wx._core.StaticText'> profile_name_label
<class 'wx._core.TextCtrl'> profile_name_textctrl
<class 'wx._core.BitmapButton'> profile_name_info_btn
<class 'wx._core.BitmapButton'> profile_save_path_btn
<class 'wx._core.StaticText'> profile_name
<class 'wx._core.Panel'> profile_settings_info_panel
<class 'DisplayCAL.wxwindows.HStretchStaticBitmap'> profile_settings_info_shadow
<class 'wx._core.StaticBitmap'> -1
<class 'DisplayCAL.wxwindows.BetterStaticFancyText'> profile_settings_info_text
<class 'wx._core.Panel'> lut3d_settings_panel
<class 'wx._core.StaticText'> lut3d_settings_label
<class 'wx._core.CheckBox'> lut3d_create_cb
<class 'wx._core.StaticText'> lut3d_input_profile_label
<class 'wx._core.Choice'> lut3d_input_profile_ctrl
<class 'wx._core.StaticText'> lut3d_trc_label
<class 'wx._core.Choice'> lut3d_trc_ctrl
<class 'wx._core.StaticText'> lut3d_trc_gamma_label
<class 'wx._core.ComboBox'> lut3d_trc_gamma_ctrl
[D] lut3d_trc_gamma_ctrl binds EVT_TEXT to focus_handler
<class 'wx._core.Choice'> lut3d_trc_gamma_type_ctrl
<class 'wx._core.StaticText'> lut3d_hdr_peak_luminance_label
<class 'DisplayCAL.floatspin.FloatSpin'> lut3d_hdr_peak_luminance_ctrl
<class 'wx._core.TextCtrl'> text
<class 'wx._core.SpinButton'> wxSpinButton
<class 'wx._core.StaticText'> lut3d_hdr_peak_luminance_ctrl_label
<class 'wx._core.StaticText'> lut3d_hdr_sat_ctrl_lum_label
<class 'wx._core.Slider'> lut3d_hdr_sat_ctrl
<class 'wx._core.StaticText'> lut3d_hdr_sat_ctrl_sat_label
<class 'wx._core.StaticText'> lut3d_hdr_sat_ctrl_lum_val
<class 'wx._core.StaticText'> lut3d_hdr_sat_ctrl_sat_val
<class 'wx._core.StaticText'> lut3d_hdr_hue_label
<class 'wx._core.Slider'> lut3d_hdr_hue_ctrl
<class 'wx._core.SpinCtrl'> lut3d_hdr_hue_intctrl
<class 'wx._core.TextCtrl'> text
<class 'wx._core.SpinButton'> wxSpinButton
<class 'wx._core.StaticText'> lut3d_hdr_hue_intctrl_label
<class 'wx._core.StaticText'> lut3d_hdr_minmll_label
<class 'DisplayCAL.floatspin.FloatSpin'> lut3d_hdr_minmll_ctrl
<class 'wx._core.TextCtrl'> text
<class 'wx._core.SpinButton'> wxSpinButton
<class 'wx._core.StaticText'> lut3d_hdr_minmll_ctrl_label
<class 'wx._core.StaticText'> lut3d_hdr_maxmll_label
<class 'DisplayCAL.floatspin.FloatSpin'> lut3d_hdr_maxmll_ctrl
<class 'wx._core.TextCtrl'> text
<class 'wx._core.SpinButton'> wxSpinButton
<class 'wx._core.StaticText'> lut3d_hdr_maxmll_ctrl_label
<class 'wx._core.CheckBox'> lut3d_hdr_maxmll_alt_clip_cb
<class 'wx._core.StaticText'> lut3d_hdr_diffuse_white_label
<class 'wx._core.StaticText'> lut3d_hdr_diffuse_white_txt
<class 'wx._core.StaticText'> lut3d_hdr_diffuse_white_txt_label
<class 'wx._core.StaticText'> lut3d_hdr_ambient_luminance_label
<class 'DisplayCAL.floatspin.FloatSpin'> lut3d_hdr_ambient_luminance_ctrl
<class 'wx._core.TextCtrl'> text
<class 'wx._core.SpinButton'> wxSpinButton
<class 'wx._core.StaticText'> lut3d_hdr_ambient_luminance_ctrl_label
<class 'wx._core.StaticText'> lut3d_hdr_system_gamma_label
<class 'wx._core.StaticText'> lut3d_hdr_system_gamma_txt
<class 'wx._core.StaticText'> lut3d_content_colorspace_label
<class 'wx._core.Choice'> lut3d_content_colorspace_ctrl
<class 'wx._core.StaticText'> lut3d_content_colorspace_w_label
<class 'DisplayCAL.floatspin.FloatSpin'> lut3d_content_colorspace_white_x
<class 'wx._core.TextCtrl'> text
<class 'wx._core.SpinButton'> wxSpinButton
<class 'wx._core.StaticText'> lut3d_content_colorspace_white_x_label
<class 'DisplayCAL.floatspin.FloatSpin'> lut3d_content_colorspace_white_y
<class 'wx._core.TextCtrl'> text
<class 'wx._core.SpinButton'> wxSpinButton
<class 'wx._core.StaticText'> lut3d_content_colorspace_white_y_label
<class 'wx._core.StaticText'> lut3d_content_colorspace_r_label
<class 'DisplayCAL.floatspin.FloatSpin'> lut3d_content_colorspace_red_x
<class 'wx._core.TextCtrl'> text
<class 'wx._core.SpinButton'> wxSpinButton
<class 'wx._core.StaticText'> lut3d_content_colorspace_red_x_label
<class 'DisplayCAL.floatspin.FloatSpin'> lut3d_content_colorspace_red_y
<class 'wx._core.TextCtrl'> text
<class 'wx._core.SpinButton'> wxSpinButton
<class 'wx._core.StaticText'> lut3d_content_colorspace_red_y_label
<class 'wx._core.StaticText'> lut3d_content_colorspace_g_label
<class 'DisplayCAL.floatspin.FloatSpin'> lut3d_content_colorspace_green_x
<class 'wx._core.TextCtrl'> text
<class 'wx._core.SpinButton'> wxSpinButton
<class 'wx._core.StaticText'> lut3d_content_colorspace_green_x_label
<class 'DisplayCAL.floatspin.FloatSpin'> lut3d_content_colorspace_green_y
<class 'wx._core.TextCtrl'> text
<class 'wx._core.SpinButton'> wxSpinButton
<class 'wx._core.StaticText'> lut3d_content_colorspace_green_y_label
<class 'wx._core.StaticText'> lut3d_content_colorspace_b_label
<class 'DisplayCAL.floatspin.FloatSpin'> lut3d_content_colorspace_blue_x
<class 'wx._core.TextCtrl'> text
<class 'wx._core.SpinButton'> wxSpinButton
<class 'wx._core.StaticText'> lut3d_content_colorspace_blue_x_label
<class 'DisplayCAL.floatspin.FloatSpin'> lut3d_content_colorspace_blue_y
<class 'wx._core.TextCtrl'> text
<class 'wx._core.SpinButton'> wxSpinButton
<class 'wx._core.StaticText'> lut3d_content_colorspace_blue_y_label
<class 'wx._core.StaticText'> lut3d_trc_black_output_offset_label
<class 'wx._core.Slider'> lut3d_trc_black_output_offset_ctrl
<class 'wx._core.SpinCtrl'> lut3d_trc_black_output_offset_intctrl
<class 'wx._core.TextCtrl'> text
<class 'wx._core.SpinButton'> wxSpinButton
<class 'wx._core.StaticText'> lut3d_trc_black_output_offset_intctrl_label
<class 'wx._core.CheckBox'> lut3d_apply_cal_cb
<class 'wx._core.StaticText'> gamut_mapping_mode
<class 'wx._core.RadioButton'> gamut_mapping_inverse_a2b
<class 'wx._core.RadioButton'> gamut_mapping_b2a
<class 'wx._core.StaticText'> lut3d_rendering_intent_label
<class 'wx._core.Choice'> lut3d_rendering_intent_ctrl
<class 'wx._core.StaticText'> lut3d_format_label
<class 'wx._core.Choice'> lut3d_format_ctrl
<class 'wx._core.Choice'> lut3d_hdr_display_ctrl
<class 'wx._core.StaticText'> encoding_input_label
<class 'wx._core.Choice'> encoding_input_ctrl
<class 'wx._core.StaticText'> encoding_output_label
<class 'wx._core.Choice'> encoding_output_ctrl
<class 'wx._core.StaticText'> lut3d_size_label
<class 'wx._core.Choice'> lut3d_size_ctrl
<class 'wx._core.StaticText'> lut3d_bitdepth_input_label
<class 'wx._core.Choice'> lut3d_bitdepth_input_ctrl
<class 'wx._core.StaticText'> lut3d_bitdepth_output_label
<class 'wx._core.Choice'> lut3d_bitdepth_output_ctrl
<class 'wx._core.Panel'> lut3d_settings_info_panel
<class 'DisplayCAL.wxwindows.HStretchStaticBitmap'> lut3d_settings_info_shadow
<class 'wx._core.StaticBitmap'> -1
<class 'DisplayCAL.wxwindows.BetterStaticFancyText'> lut3d_settings_info_text
<class 'wx._core.Panel'> panel
<class 'wx._core.StaticText'> mr_settings_label
<class 'wx._core.StaticText'> testchart_or_reference_label
<class 'DisplayCAL.wxwindows.FileBrowseBitmapButtonWithChoiceHistory'> chart_ctrl
<class 'wx._core.Choice'> choice
<class 'DisplayCAL.wxfixes.GenBitmapButton'> button
<class 'wx._core.Choice'> fields_ctrl
<class 'wx._core.BitmapButton'> chart_btn
<class 'wx._core.StaticText'> chart_patches_amount
<class 'wx._core.StaticText'> chart_meas_time
<class 'wx._core.CheckBox'> simulate_whitepoint_cb
<class 'wx._core.CheckBox'> simulate_whitepoint_relative_cb
<class 'wx._core.CheckBox'> simulation_profile_cb
<class 'DisplayCAL.wxwindows.FileBrowseBitmapButtonWithChoiceHistory'> simulation_profile_ctrl
<class 'wx._core.Choice'> choice
<class 'DisplayCAL.wxfixes.GenBitmapButton'> button
<class 'wx._core.CheckBox'> use_simulation_profile_as_output_cb
<class 'wx._core.CheckBox'> enable_3dlut_cb
<class 'wx._core.StaticText'> mr_trc_label
<class 'wx._core.RadioButton'> apply_none_ctrl
<class 'wx._core.StaticBitmap'> input_value_clipping_bmp
<class 'wx._core.StaticText'> input_value_clipping_label
<class 'wx._core.RadioButton'> apply_black_offset_ctrl
<class 'wx._core.RadioButton'> apply_trc_ctrl
<class 'wx._core.Choice'> mr_trc_ctrl
<class 'wx._core.StaticText'> mr_trc_gamma_label
<class 'wx._core.ComboBox'> mr_trc_gamma_ctrl
[D] mr_trc_gamma_ctrl binds EVT_TEXT to focus_handler
<class 'wx._core.Choice'> mr_trc_gamma_type_ctrl
<class 'wx._core.StaticText'> mr_black_output_offset_label
<class 'wx._core.Slider'> mr_black_output_offset_ctrl
<class 'wx._core.SpinCtrl'> mr_black_output_offset_intctrl
<class 'wx._core.TextCtrl'> text
<class 'wx._core.SpinButton'> wxSpinButton
<class 'wx._core.StaticText'> mr_black_output_offset_intctrl_label
<class 'wx._core.CheckBox'> devlink_profile_cb
<class 'DisplayCAL.wxwindows.FileBrowseBitmapButtonWithChoiceHistory'> devlink_profile_ctrl
<class 'wx._core.Choice'> choice
<class 'DisplayCAL.wxfixes.GenBitmapButton'> button
<class 'wx._core.StaticText'> output_profile_label
<class 'DisplayCAL.wxwindows.FileBrowseBitmapButtonWithChoiceHistory'> output_profile_ctrl
<class 'wx._core.Choice'> choice
<class 'DisplayCAL.wxfixes.GenBitmapButton'> button
<class 'wx._core.Button'> output_profile_current_btn
<class 'wx._core.Panel'> mr_settings_info_panel
<class 'DisplayCAL.wxwindows.HStretchStaticBitmap'> mr_settings_info_shadow
<class 'wx._core.StaticBitmap'> -1
<class 'DisplayCAL.wxwindows.BetterStaticFancyText'> mr_settings_info_text
<class 'wx._core.Panel'> buttonpanel
<class 'wx._core.Button'> calibrate_btn
<class 'wx._core.Button'> calibrate_and_profile_btn
<class 'wx._core.Button'> profile_btn
<class 'wx._core.Button'> lut3d_create_btn
<class 'wx._core.Button'> measurement_report_btn
<class 'DisplayCAL.wxwindows.BitmapBackgroundPanelText'> panel
<class 'DisplayCAL.wxwindows.BitmapBackgroundPanel'> panel
<class 'DisplayCAL.wxwindows.BitmapBackgroundPanel'> panel
2024-12-30 15:06:26.829 Python[2640:66132] +[IMKClient subclass]: chose IMKClient_Modern
[D] focus_handler called for ID -31914 whitepoint_colortemp_textctrl <class 'wx._core.ComboBox'>, event type 10200 EVT_TEXT
[D] focus_handler called for ID -31882 trc_textctrl <class 'wx._core.ComboBox'>, event type 10200 EVT_TEXT
[D] focus_handler called for ID -31882 trc_textctrl <class 'wx._core.ComboBox'>, event type 10200 EVT_TEXT
[D] update_displays
[D] get_set_display
[D] display_ctrl_handler called for ID -31974 display_ctrl event type 10009 EVT_CHOICE
[D] focus_handler called for ID -31914 whitepoint_colortemp_textctrl <class 'wx._core.ComboBox'>, event type 10200 EVT_TEXT
[D] whitepoint_ctrl_handler called for ID -31915 whitepoint_ctrl event type 10009 EVT_CHOICE
[D] focus_handler called for ID -31914 whitepoint_colortemp_textctrl <class 'wx._core.ComboBox'>, event type 10200 EVT_TEXT
[D] focus_handler called for ID -31914 whitepoint_colortemp_textctrl <class 'wx._core.ComboBox'>, event type 10200 EVT_TEXT
[D] whitepoint_ctrl_handler called for ID -31915 whitepoint_ctrl event type 10009 EVT_CHOICE
[D] focus_handler called for ID -31914 whitepoint_colortemp_textctrl <class 'wx._core.ComboBox'>, event type 10200 EVT_TEXT
[D] focus_handler called for ID -31914 whitepoint_colortemp_textctrl <class 'wx._core.ComboBox'>, event type 10200 EVT_TEXT
[D] whitepoint_ctrl_handler called for ID -31915 whitepoint_ctrl event type 10009 EVT_CHOICE
[D] focus_handler called for ID -31914 whitepoint_colortemp_textctrl <class 'wx._core.ComboBox'>, event type 10200 EVT_TEXT
[D] focus_handler called for ID -31914 whitepoint_colortemp_textctrl <class 'wx._core.ComboBox'>, event type 10200 EVT_TEXT
[D] whitepoint_ctrl_handler called for ID -31915 whitepoint_ctrl event type 10009 EVT_CHOICE
[D] focus_handler called for ID -31914 whitepoint_colortemp_textctrl <class 'wx._core.ComboBox'>, event type 10200 EVT_TEXT
measurement_report.devlink_profile does not exist: /Library/Frameworks/Python.framework/Versions/3.13/lib/python3.13/site-packages/DisplayCAL/presets/video_resolve.Rec709.B0.0,2.4Gawn65.icc [D] focus_handler called for ID -31812 lut3d_trc_gamma_ctrl <class 'wx._core.ComboBox'>, event type 10200 EVT_TEXT
...ok.
[D] check_argyll_bin OK
[D] lut_viewer_load_lut DisplayCAL calibration preset: Resolve force_draw: False
Ready.
Setting up scripting host at 127.0.0.1:54743
[D] focus_handler called for ID -31910 whitepoint_x_textctrl <class 'DisplayCAL.floatspin.FloatSpin'>, event type 10037 EVT_SET_FOCUS
[D] focus_handler called for ID -31909 text <class 'wx._core.TextCtrl'>, event type 10037 EVT_SET_FOCUS
[D] focus_handler called for ID -31910 whitepoint_x_textctrl <class 'DisplayCAL.floatspin.FloatSpin'>, event type 10037 EVT_SET_FOCUS
[D] focus_handler called for ID -31909 text <class 'wx._core.TextCtrl'>, event type 10037 EVT_SET_FOCUS
Check for application update...
DisplayCAL is up-to-date.
[D] check_argyll_bin OK
ArgyllCMS is up-to-date.
2024-12-30 15:06:30.828 Python[2640:66132] +[IMKInputSession subclass]: chose IMKInputSession_Modern
[D] focus_handler called for ID -31910 whitepoint_x_textctrl <class 'DisplayCAL.floatspin.FloatSpin'>, event type 10037 EVT_SET_FOCUS
[D] focus_handler called for ID -31909 text <class 'wx._core.TextCtrl'>, event type 10037 EVT_SET_FOCUS

[Adam-Color]

Argyll is correct. Tried opening profiler and still getting dispread error. Also getting a no such file or directory warning. The initial grey measurement box pops up and when I try to start the profiling, it just stays white.

did you try launching the calibrite software first, then the displaycal software?

[Adam-Color]

Last login: Mon Dec 30 14:48:51 on ttys000

I think you might have run out of characters for your copy-paste, I don't see any disprd error in the logs at all. If that is what's happening, put it in a .txt and uplaod it

[decayedxistence]

Yes. I opened the software and the probe showed up as Active. TXT Attached.

Untitled document.txt

[Adam-Color]

Yes. I opened the software and the probe showed up as Active. TXT Attached.

Untitled document.txt

Looks like your patches are being read too fast.

Specifically, from the source code:

patch count is higher than patterngenerator sent count

Select "override minimum display update delay" and try higher and higher ms values until you can get a stable connection.

However, it could be something else, too. You're getting more errors:

dispcal: Warning - System command '/usr/bin/env python ./.wait 255 255 255 1.000000 1.000000 1.000000' failed with 32512

and:

env: python: No such file or directory

That last one could mean your virtual environment is deactivated, make sure it's not. The dispcal message is vague but seems to also be related to an issue with the version of python installed on your Mac. Maybe try reinstalling python, and recreating the virtual environment from scratch?

[decayedxistence]

Thanks for checking over the TXT file. I do tend to override and set the minimum display response to 1000ms as that always gives me a better read.

If I try running DisplayCal via the .dmg install, I just get a "connection failed" error from Resolve when trying to connect to the Portrait Displays Calman.

I have never had luck setting up a virtual environment with DisplayCal even with the most recent instructions as when I paste them into terminal, it just results in "command not found"

I forgot at this point how I even got the current virtual environment to run haha.

so, you think just nuke every displaycal and argyll off computer, delete python, and try to start fresh?

Do you have any recommendations on how to install as when I copy and paste the codes in order from here: https://github.com/eoyilmaz/displaycal-py3/blob/develop/docs/install_instructions_macos.md#install-through-pypi

that's where I get the error message of comman not found in terminal.

[Adam-Color]

Do you have any recommendations on how to install as when I copy and paste the codes in order from here: https://github.com/eoyilmaz/displaycal-py3/blob/develop/docs/install_instructions_macos.md#install-through-pypi

copy them line by line, not in chunks. each line is a seperate command and it's a lot clearer what's going on when you dont fire them off all at once.

so, you think just nuke every displaycal and argyll off computer, delete python, and try to start fresh?

yes. There's a chance your original install got messed up. If we're going this route you should try reseting your router as well.

I have never had luck setting up a virtual environment with DisplayCal even with the most recent instructions as when I paste them into terminal, it just results in "command not found"

hmmm, likely you're missing something needed to run a command. What happens when you just run python --version?

also, important to note:

If you close the current terminal and run a new one, you need to activate the virtual environment before calling displaycal:

source ~/venv-diplaycal/bin/activate
displaycal

Thanks for checking over the TXT file. I do tend to override and set the minimum display response to 1000ms as that always gives me a better read.

try not overriding, I personally don't mess with it and have never had issues.

If I try running DisplayCal via the .dmg install, I just get a "connection failed" error from Resolve when trying to connect to the Portrait Displays Calman.

That seems more like a ip issue to me, hence the router reset.

[decayedxistence]

Copy. I'll try line by line and see if that helps.

Just reset my modem and router.

Will delete all instance of displaycal, argyll, and report back soon.

Thanks homie.

[Adam-Color]

Thanks homie.

ofc! need something to do while I'm on break :)

[decayedxistence]

I appreciate it. I have color job to start tomorrow so trying to get this properly done instead of my ass backwards full levels band aid fix...

Router and modem reset. Tried hard line connections and wireless using the .dmg DisplayCal to connect and no luck in Resolve - still a connection failed message.

Deleted everything I could find on my system related to python, displaycal, argyll to start fresh with creating a virtual environment according to steps on here...

When I paste that first Prequisite line to install through brew, I get "zsh: command not found: brew" in terminal.

EDIT NVM I'm a dick and don't think I had homebrew installed.

BUT

When I try to then paste this command in terminal (whether in a chunk or line by line)

cd ~
python -m venv venv-displaycal
source venv-diplaycal/bin/activate
pip install displaycal

I get hit with "command not found or directory not found.

[decayedxistence]

Okay....soooo I used good old chat gpt to figure out where I was going wrong and that seems to have worked on top of I had python 3.13.1 installed and displaycal only works up to 13.13

I didn't have homebrew installed and pip needed to be upgraded. Then I had chat gpt prompt me how to correctly enter the code into terminal to create the virtual environment.

Booted up DisplayCal in terminal and ran a quick test patch and it actually worked and connected and ran the patches and no dispread errors.. So, something somewhere in the mess I had was causing the errors.

What an insane journey!

I still have that connection error with the DMG though. That ran so smooth for me the first month it was out and then stopped.

I'm doing a small test run now of 175 patches with Resolve levels set to video and displaycal left as is for profiling....then will switch to 2.4 relative with black outputoffset to 100 and VCGT Unchecked and create a LUT from there and see if that works for a good calibration and correct levels.

[Adam-Color]

I'm doing a small test run now of 175 patches with Resolve levels set to video and displaycal left as is for profiling....then will switch to 2.4 relative with black outputoffset to 100 and VCGT Unchecked and create a LUT from there and see if that works for a good calibration and correct levels.

Sounds good, glad we could track it down! I just did my major 2,000+ patch calibration.

[decayedxistence]

2.000?! Dam! I appreciate all the help and tackling this with me the last few days.

So the test run worked....verification port is great and I actually wound up with an on the nose 2.4 gamma curve. Previously it was 2.3 and I was noticing my blacks and whites were clipping a bit.

Question....are you sure VCGT should not be checked? I read some say yes and some say no. I know Stuart from Eizo says no but he already calibrates a 1D LUT via colornavigator before using displaycal.

(I also noticed that 3d lut bug where it switches back)

[Adam-Color]

Question....are you sure VCGT should not be checked? I read some say yes and some say no. I know Stuart from Eizo says no but he already calibrates a 1D LUT via colornavigator before using displaycal.

a VCGT is meant to correct for your graphics card, since you are using I/O device you are bypassing your graphics card.

Glad to help!

[decayedxistence]

Copy. That makes sense.

Running a larger patch segment now...

I'm so used to seeing Full levels in resolve that crushed the blacks and over saturated a bit that now a video levels calibration with a 2.4 relative offset 100% instead of 1886 absolute looks WEIRD and too soft.

This monitor is measuring as 3000:1 contrast

[decayedxistence]

Unsure what I'm doing wrong....I calibrated with video levels out from resolve, unchecked "create 3d lut after profiling", profiled my display, canceled the 3d lut calibration, then changed the 3d lut settings to gamma 2.4 relative with 100% blackoutput offset and unchecked vcgt and the black levels on my monitor are still too high...on really dark shots, the monitor lifts them too much....the monitor itself has 3000;1 contrast ration. Any ideas @Adam-Color

[Adam-Color]

Unsure what I'm doing wrong....I calibrated with video levels out from resolve, unchecked "create 3d lut after profiling", profiled my display, canceled the 3d lut calibration, then changed the 3d lut settings to gamma 2.4 relative with 100% blackoutput offset and unchecked vcgt and the black levels on my monitor are still too high...on really dark shots, the monitor lifts them too much....the monitor itself has 3000;1 contrast ration. Any ideas @Adam-Color

Run a verification, attach the file here in a comment (you may have to do a Google Drive link). Unless you're getting artifacts, it's likely the correct gamma, at least on the 3D-lut side of things.

Is your monitor either OLED or Full Array Local Dimming?

Better yet, what is your monitor's exact make and model?

[decayedxistence]

Mo artifacts but I would think with a high contrast ratio, the monitor would at least have some deeper blacks that aren't so lifted. Coming from the ass backwards full levels hack we talked about that I did, that had deeper blacks but was def crushed. The new video levels calibration has way nice gradation and highlights that aren't clipped but the blacks are too lifted....on exterior daylight shots it looks fine, but I was just doing a first pass with a DP and we realized on some dark dark interiors, the blacks were too lifted even when they were getting crushed to death.

Measurement Report 3.9.14 — Resolve — 2024-12-30 20_47_27.pdf

The Monitor is a BenQ EW3270U -- https://www.displayspecifications.com/en/model/973a1165

Could it be that I should have, "black level drift compensation" ticked? I know that's usually for OLEDs but that's the only thing left I can think of.

OR could it be that this monitor only accepts Full levels out of my macbook pro? There is an option to change the levels on the monitor but they are grayed out. (just throwing ideas/options/possibilities out there)

[Adam-Color]

Mo artifacts but I would think with a high contrast ratio, the monitor would at least have some deeper blacks that aren't so lifted. Coming from the ass backwards full levels hack we talked about that I did, that had deeper blacks but was def crushed. The new video levels calibration has way nice gradation and highlights that aren't clipped but the blacks are too lifted....on exterior daylight shots it looks fine, but I was just doing a first pass with a DP and we realized on some dark dark interiors, the blacks were too lifted even when they were getting crushed to death.

Measurement Report 3.9.14 — Resolve — 2024-12-30 20_47_27.pdf

The Monitor is a BenQ EW3270U -- https://www.displayspecifications.com/en/model/973a1165

Could it be that I should have, "black level drift compensation" ticked? I know that's usually for OLEDs but that's the only thing left I can think of.

OR could it be that this monitor only accepts Full levels out of my macbook pro? There is an option to change the levels on the monitor but they are grayed out. (just throwing ideas/options/possibilities out there)

Looking at the measurement report, the gamma is tracking correctly. I think you may just be used to seeing it wrong?

The only other thing I can think of is that your timeline or monitoring settings in resolve are still set to full, breaking the image pipeline (there are multiple settings for this that can be a bit hard to find as they are in different menus). That's the only way you could be getting a good verification but a bad image.

[decayedxistence]

I'm as lost as you at this point haha.

I thought it was maybe me at first as well being so used to wrong levels but if I drag in some jpegs from Shotdeck and check them out, the blacks get really lifted. If I right click them and click clip attributes and change the data levels to video, they look correct.

I was using Davinci Remote Monitor with a DP on a job I started last night (I usually have to set the output color space to Rec 709-A since that looks best and 2.4 looks crushed on phones) and the blacks were super deep and sitting just at zero on the waveform. Then looking at my monitor, they're lifted still. iPhones & Macbooks DO have crazy high contrast comparable to OLEDs where my monitor is a VA with 3000:1 -- so that could be part of it as well so it throws me off.

[Adam-Color]

I'm as lost as you at this point haha.

I thought it was maybe me at first as well being so used to wrong levels but if I drag in some jpegs from Shotdeck and check them out, the blacks get really lifted. If I right click them and click clip attributes and change the data levels to video, they look correct.

I was using Davinci Remote Monitor with a DP on a job I started last night (I usually have to set the output color space to Rec 709-A since that looks best and 2.4 looks crushed on phones) and the blacks were super deep and sitting just at zero on the waveform. Then looking at my monitor, they're lifted still. iPhones & Macbooks DO have crazy high contrast comparable to OLEDs where my monitor is a VA with 3000:1 -- so that could be part of it as well so it throws me off.

There is one old-school way of knowing for sure - generate a SMPTE chart (it's a fusion element in resolve, under the generators tab) and look at it on your monitor. On the bottom row, there are gray, black, and white patches. One of the patches is a long black rectangle with two vertical gray stripes on the right side. The leftmost strip should be extremely difficult to make out or completely invisible, depending on the black point of your monitor. The rightmost stripe should be visible without too much effort, though it will also be a little faint. If you can see the leftmost stripe clear as day, then the gamma is wrong. If you can't see it at all but can still see the rightmost stripe, then the gamma is 100% accurate to what your timeline is set to, in this case 2.4.

[Adam-Color]

To clarify, the gray stripes are INSIDE the long black rectangle.

[decayedxistence]

Copy.

Tossed in the SMPTE chart. Bottom row shows (from left to right)-- grey, black, white, black rectangle, grey

With the current calibration (displaycal with your method, video levels in resolve, and calibration lut)...in the black rectangle, I can't make out the vertical grey stripe on the left but I can easily see it on the right side.

If I switch Resolve to full levels and a full level test lut I ran last night (as well as my old one) then the far right grey vertical stripe completely disappears.

Which means everything is correct then.

I know we grade to a calibrated monitor and once it leaves that environment, it's out of our control....but why would blacks on the calibrated monitor look so lifted then super deep elsewhere? When stills are imported that look like and deep and contrasty on the web, phone, etc but when imported into resolve (resolve interprets them as full) look so lifted?

Just a pain because when monitoring on Davinci Remote monitor, they don't match (reference and phone) even with output settings set to 709-a or srgb (since it's feeding a phone)

(all help and your time greatly appreciated once again - don't think it goes unnoticed)

[Adam-Color]

I know we grade to a calibrated monitor and once it leaves that environment, it's out of our control....but why would blacks on the calibrated monitor look so lifted then super deep elsewhere? When stills are imported that look like and deep and contrasty on the web, phone, etc but when imported into resolve (resolve interprets them as full) look so lifted?

It's the issue of OLED vs. LED technology. I see the same thing with my monitor, which is also LED. Films mastered on LEDs will look best on LEDs (and not necessarily translate well to OLED), whereas films mastered on OLEDs (especially QD-OLEDs) will look best on both. If I were you I would use the phone as a cross-check near the end of a grade to ensure that nothing looks awful on OLED but good on LED, if that makes sense.

[decayedxistence]

Crazy. I think we've exhausted every option there is hahaha.

I would have thought with this much contrast, It'd be a bit deeper in the blacks but is what it is I guess and the bars confirm it is indeed correct levels and gamma.

That's probably what I'll have to do is confirm with phone to check blacks. Doing some more tests now with Davinci Remote Monitor and playing around with different output color spaces in Resolve and I think SRGB is actually better than Rec 709-A. It feels a little more accurate.

Looking to upgrade to a better monitor this year and was contemplating a LG C2 or might wait till ASUS comes out with their PA32UCDM which a lot of people are waiting for - uses the same panels as the FSI XMP310 but FSI has first dibs on them.

[Adam-Color]

Crazy. I think we've exhausted every option there is hahaha.

I would have thought with this much contrast, It'd be a bit deeper in the blacks but is what it is I guess and the bars confirm it is indeed correct levels and gamma.

That's probably what I'll have to do is confirm with phone to check blacks. Doing some more tests now with Davinci Remote Monitor and playing around with different output color spaces in Resolve and I think SRGB is actually better than Rec 709-A. It feels a little more accurate.

Looking to upgrade to a better monitor this year and was contemplating a LG C2 or might wait till ASUS comes out with their PA32UCDM which a lot of people are waiting for - uses the same panels as the FSI XMP310 but FSI has first dibs on them.

I wish you luck! OLED really is a whole different world of contrast. Most QD-OLEDs are >1,000,000:1 contrast ratio

[decayedxistence]

Thanks brother. I really do appreciate all the help and troubleshooting the last week. Enjoy the rest of your break!

[decayedxistence]

Probably driving myself crazy at this point...but you know what's interesting...If I just run Resolve on my macbook to my reference monitor (my macbook has a 2.4 .icc - the reference monitor has deep blacks and it's gorgeous (yes video levels) but once I run the 3d lut in resolve through the decklink, the deep blacks disappear.....

[Adam-Color]

Probably driving myself crazy at this point...but you know what's interesting...If I just run Resolve on my macbook to my reference monitor (my macbook has a 2.4 .icc - the reference monitor has deep blacks and it's gorgeous (yes video levels) but once I run the 3d lut in resolve through the decklink, the deep blacks disappear.....

The decklink might be misconfigured, then... are you using the desktop video application from blackmagic design? If so, what kind of signal is resolve sending it? Also, is it configured correctly in Resolve's "video and audio I/O" settings?

[decayedxistence]

It basically looks like the 3d eats the deep blacks and shadow detail

Yes, I'm using desktop video application. Ultrastudio monitor 3g to the monitor via hdmi.

Thunderbolt > ultrastudio monitor 3g

HDMI from ultrastudio monitor 3g > hdmi on external monitor

I don't think the desktop monitor app matters since resolve overrides it but below is a screenshot:

[Adam-Color]

It basically looks like the 3d eats the deep blacks and shadow detail

Can you do a more detailed verification with displaycal please, use video test patches XL. Also dont send a pdf, I need the interactive HTML

[decayedxistence]

It basically looks like the 3d eats the deep blacks and shadow detail

Can you do a more detailed verification with displaycal please, use video test patches XL. Also dont send a pdf, I need the interactive HTML

Sure thing. What's the easiest way to send the HTML. I couldn't figure it out last time.

I was also reading on one of the DisplayCal forums about my type of panels - VA - even though it has 3500:1 contrast, once calibrated for a pure power law of 2.4 relative and black output offset 100%, the backlight will eat the dark blacks and shadow details....unsure how true that is.

Because if my macbook has an .icc for 2.4 and the reference monitor is reset to factory, that doesn't happen.

[decayedxistence]

Let me know if this works for the HTML:

https://drive.google.com/file/d/1chT3F8G73jtzcoX9UiV5oJ9iDDEEeMvV/view?usp=sharing

(I believe the initial calibration run was 833 patches.

[Adam-Color]

Let me know if this works for the HTML:

https://drive.google.com/file/d/1chT3F8G73jtzcoX9UiV5oJ9iDDEEeMvV/view?usp=sharing

(I believe the initial calibration run was 833 patches.

The only major thing I noticed is that your colorimeter correction is wrong, that CCSS is meant for a spectraval 1511 meter and you are using an i1displaypro-based meter.

There is some odd gamma tracking present here, but not anything extreme. And the colors are unaffected, in fact the lower luminance colors are more accurate than the brighter ones.

Apple is infamous for its inconsistent color management system, perhaps macOS is crushing the blacks on the external display.

[decayedxistence]

Re: Spectral -- that could certainly be a major culprit. I think I misinterpreted wrong something I read a long time ago that someone made that correction and that's the right one to use for my monitor -- when I guess in turn, that's the right correction to use for a Spectraval 1511 that someone made for that monitor.

Welp, giving you that report certainly helped identify that major error.

Looking at displayspecifications.com and seeing what's already bundled into DisplayCal, it looks like I should be using the WLED PFS Phosphor.

Back to the drawing board cries in pain

[Adam-Color]

Back to the drawing board cries in pain

I know the feeling, this is why I'm fixing bugs and developing displaycal (and helping out in these reports when I can). Hopefully one day, I'll understand how it works enough to make it more user-friendly. Or at least make a more user-friendly version of it.

[decayedxistence]

Your hard work is appreciated. Someone should throw up a tip jar or buy me a coffee link on the gitjub homepage for everyone.

I was just talking with another colorist I know up in Canada who broke down and got the FSI XMP310 and he said, "dude...my confidence is through the roof right now with this display"....I said, "For $10,000 USD, it better be!"

[decayedxistence]

Used the correct colorimeter correction after we spoke last night, double checked all settings 02385025 times, etc and ran a 833 patch run.

https://drive.google.com/file/d/1oDMsZs6N3SLS1cnv24iCZge-IvxVkp9R/view?usp=sharing

Checked some footage via the i/o card and reference monitor and a bunch of film stills and well as stills from colorists and the gamma DOES seem to be tracking better. Colors a little better too....I think it's also the nature of this VA panel -- while blacks and whites are really nice compared to an IPS with lower contrast and that IPS panel glow....i think some of the really deep deep blacks do get eaten a bit by the backlight.

Is what it is but at least at this point, we've exhausted every possible outcome and I am finally confident in saying the pipeline is correct and this is the best and most accurate image I can get out of this monitor until I can get a real reference OLED or save for a QD-OLED.