Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

macbook pro A2442 unable to use software 3.9.14 normally #457

Open
chenp2436 opened this issue Oct 31, 2024 · 6 comments
Open

macbook pro A2442 unable to use software 3.9.14 normally #457

chenp2436 opened this issue Oct 31, 2024 · 6 comments

Comments

@chenp2436
Copy link

software version 3.9.14
Argyll_V version 3.3.0
macbook pro A2442
iShot_2024-10-31_20 38 27

Spyder3 cannot be detected. Click to refresh the device and it freezes after 24 seconds.
The software can only be forcibly closed.
I opened the software again but still couldn't detect Spyder3
Repeating the above operation still causes the software to freeze

@VgerTest
Copy link

Before opening this issue you must check that command line using ArgyllCMS it is recognized. Easyest test is spotread

@chenp2436
Copy link
Author

Before opening this issue you must check that command line using ArgyllCMS it is recognized. Easyest test is spotread

ArgyllCMS does not use the command line, but I can detect Spyder3 using x64.dmg. Although the detection is still stuck, the software will not freeze;

By the way, I am using macos Sequoia 15.1.

Now there is a new problem.
Spyder3 is detected and color calibration begins.
When the last step is about to be completed, an error will be reported and the color calibration process will be exited. This happened several times after testing.

@VgerTest
Copy link

VgerTest commented Nov 1, 2024

Before opening this issue you must check that command line using ArgyllCMS it is recognized. Easyest test is spotread

ArgyllCMS does not use the command line, but I can detect Spyder3 using x64.dmg. Although the detection is still stuck, the software will not freeze;

ArgyllCMS do use command line... it's only command line! DisplayCAL is a GUI over Argyllcms command line single apps.
So as a general rule when a device is not detected, the first step is to check if running basic commandline apps device is detected and measures as expected.

By the way, I am using macos Sequoia 15.1.

Now there is a new problem. Spyder3 is detected and color calibration begins. When the last step is about to be completed, an error will be reported and the color calibration process will be exited. This happened several times after testing.

For that new error you'll have to provide full log so people may find why it crashed.

@eoyilmaz
Copy link
Owner

eoyilmaz commented Nov 3, 2024

Now there is a new problem.
Spyder3 is detected and color calibration begins.
When the last step is about to be completed, an error will be reported and the color calibration process will be exited. This happened several times after testing.

can you send the error message please.

@MStraeten
Copy link

no issues with sequioa 15.1 on m1 max with colorchecker display pro
but protocol window is empty - logs are just available in konsole app

@chenp2436
Copy link
Author

Now there is a new problem.
Spyder3 is detected and color calibration begins.
When the last step is about to be completed, an error will be reported and the color calibration process will be exited. This happened several times after testing.

can you send the error message please.

It appears to be a case of a mix-up. Today, after completely uninstalling the previous displaycal and reinstalling the ARM version of the software, I was able to complete the calibration process.
I suspect the error was caused by a direct overwrite installation in the past.
Currently, there is a lag when scanning devices and switching parameters, requiring a wait for a while, but the entire calibration process can be carried out. The log records are empty, and no errors have been detected.
Thank you to everyone for your attention to this issue; I will continue to test the current version.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants