I'm new to trying to get colorspace for FSI LTE to work with Resolve to calibrate my FSI BM211 with a ColorChecker Display Pro (i1D3?)
I'm on a Mac (OS 14.7.2) and am running ColorSpace on Paralles Windows 11 Home
I tried previously and was able to connect with resolve fine but apparently was using the wrong profiles for the probe and the results were way way off.
But the process of using Color Space to make a 3D LUT worked.
So I sent my probe to FSI and had bpd files made for it .
However when trying just now to connect Resolve to ColorSpace the Monitor Calibration "Lightspace Calibration" is failing to connect to the IP address which i'm seeing as "10.211.55.7" Port is "2002"
It worked previously but I seem to recall a different IP address though I didn't write anything down . (At that time I was using OS 14.1.1)
I'm getting this address from the network ethernet settings on Parallels windows Windows 11 Home

So what's the problem ?

A related question is what's the difference between using these bpd files or "correlation files" for my FSI monitor ?
Unfortunately i don't see any correlation files for my BM211 , only for the DM211.

I suspect you have a Parallels issue with the IP address. I would talk to them regarding the issue.
We test on Parallels and VMware, and there are no issues with ColourSpace itself.

And for the FSI provided .bps file you will need to talk to FSI, as they provided them.
However, Correlation files are spectral data, while the .bps is a Probe Match file.
As neither were actually generated on your specific monitor, neither will be perfect.

Steve

Steve, Thanks for responding so quickly .
I confess to feeling a little overwhelmed by the apparent complexity of this calibration business and in retrospect wish I had purchased an FSI monitor that had the Auto Calibration feature. Unfortunately I didn't know it was available. Might Have cost less in the long run and been simpler for sure.
Nevertheless here I am and I wish there was a simple tutorial about some of these concepts. If there is please provide me with a link.
For example I have no idea what the difference is between bpd files and correlation files or whether I need to know it.
Are they both used in the calibration process or are they 2 different ways to get an accurate calibration .
FSI sent me 2 files created with my colorchecker :
[C2-22.B-02.024834.11] WIDE GAMUT WHITE LED - I.bpd
[A00199] WIDE GAMUT WHITE LED - SPECTRO.bpd

What does it mean when you say they won't be perfect ?
Are these sufficient to get me an accurate calibration on my BM211?
If not what do i have to do ? And if its not possible for me within a reasonable budget why the heck did I buy ColorSpace for FSI LTE ?
Am I just wasting my time?

Thanks

Lenny

The problem with FSI monitors with inbuilt calibration is there is no way to validate the actual calibration, other than using an external calibration system - so you would still have to use something like ColourSpace to check and verify the calibration.

It is all the same in the end, as you must be able to verify any calibration.

And as said, you will need to ask FSI about the .bpd files they have sent you - we obviously have no idea what they have provided, especially as sending 2 different files makes no obvious sense.

But both Corr. Files and .bps files perform the same thing - differently. Both are for Probe Matching. You would never use both simultaneously.

Steve

Steve, I don't understand a few things in your reply:
You said above "sending 2 different [bpd] files makes no obvious sense."
However The FSI calibration guide for i1/Lightspace/Resolve v1.3 says :
"For Active Probe and Reference Probe import the I1 and Spectro (e.g.PR670, CR300, etc.) .bpd files delivered with your probe from the folder that corresponds to the panel type of your monitor ... Use the I1 .bpd file for the Active probe and the Spectro .bpd file for the Reference Probe.
Doesn't that explain why they sent 2 different files ?

I get what you said about verifying the inbuilt calibration system but it doesn't matter to me since I don't have it anyway.

However you didn't reply to whether I'm wasting my time altogether since you say my bpd files won't be perfect anyway .
Do I need to be perfect ? How imperfect will these be - again am I wasting my time?

meanwhile I am trying to contact both Parallels and davinci re the IP address but that is another can of worms of course.

Lenny

Ah - they have performed Probe Matching of both probes on their monitor.
Kinda makes sense, but as that was not your actual monitor it is impossible to define the expected accuracy.
Same with any Corr. File.
But, they will likely be 'better than nothing'.
I would use the Probe Match flies.

The IP address issue is unfortunately not something we can help with.
But, we test ColourSpace on an M1 Mac via both Parallels and VMware, and both work if configured correctly.

Steve

Thanks again for your response.

How bad though is "better than nothing" ?
You don't seem to want to answer whether i'm just wasting my time with this.
I'm just a small time guy trying to start getting work as a colorist in a home studio with a relatively inexpensive Flanders.
(BM211 is only 8 bit but the color is good and I have a larger 10 bit Mac XDR to see other problems)
But i still need to be accurate.
Am I better off sending my Flanders to FSI every year ?
Seems like an expensive PITA, but if it will be substantially more accurate....
God I've already spent countless hours trying to figure it all out and just getting the software to work.

Lenny

It's not that I don't want to answer, it that I can't.
It is impossible to say how well any Probe Matching or Corr. File will work on a monitor that the file were not generated on.
The only way to be certain is to perform Probe Matching on your own monitor with your own probes.
This is explained in the User Guides.

And no, you would not better of sending you monitor anywhere for calibration, as all monitors drift, and calibration should be verified and re-done as needed every few weeks.

But it seems the only issue you have is getting a network connection between the ColourSpace and Resolve systems.
That is a seperate IT issue, and not specifically related to the calibration workflow.

Steve

Well I am getting clearer but Confused again:
Should I be performing "Probe Matching on [my] own monitor" ?
Is that instead of having sent my probe to FSI?
Is that something I can do myself and will that make my calibration more accurate?

Can you send me a link to that User guide. I don't recall seeing anything about that .

I just want to be as precise as I can within my limited budget - that makes sense doesn't it?

Lenny

No - you would need a good spectro to perform Probe Matching on your monitor.
https://lightillusion.com/probe_matching.html

So without spending a lot on a spectro, or finding somewhere to borrow/rent one, there is little you can do.
You just have to live with the accuracy of a Corr. File or the FSI remote matching.
You can see the 'potential' errors on the 1iD3 User Guide.
https://lightillusion.com/forums/display-calibration-8/i1d3-probes-correlation-file-accuracy-1309.html

Steve

Thanks Steve, I think i have a better grasp of all this now and will check out that link tomorrow. Long past time for bed now.

Lenny

IP problem is not solved. Parallels tells me nothing is wrong and to go back to my software - that's you or Resolve .
Resolve forum is no help .
This used to work fine before I upgraded my Mac OS and Resolve .
Are you sure I don't need a different IP address.
The FSI calibration manual told me to get the IP address by starting ColorSpace , but I don't see where that is in ColorSpace.
Can you direct me?

Sorry, are you not following the Network Server & Resolve User Guides?
How to see the correct IP address is explained in detail.

• Select Connect, and the IP address and Port details of ColourSpace will populate the info boxes within Network Server Options

Steve

My apologies for wasting your time Steve ( not to mention my own ). Operator error. I just didn't read far enough into the manual .
I guess since I did it before i thought I knew what I was doing . Anyway i'm embarrassed to say it connects fine.
I'll try a new calibration later tonight with the bpd files I from from FSI.
Fingers crossed.

Lenny

I realize that the problems I've been having all resulted from jumping the gun in the order of the instructions since I had done it before successfully .
Most of us get impatient with manuals - so its probably common.
Actually i think it would be great if the instructions started off with a directive:
"Be sure to carry these instructions precisely in the order below. Don't jump the gun with anything . "
- My first mistake was entering the IP address and hitting connect too soon, even though I was using the correct IP address.
That led me down a rabbit hole about why the IP address didn't work.
-Then last night I kept getting an error message because I started off with my probe plugged into the computer .
When I waited till instructed in the manual it worked.

BTW - One thing missing in the manual is that on a Mac a pop up window immediately asks if I want the probe to attach to parallels or to the Mac OS .
Of course I chose Parallels but who knows what someone else might do.

Thanks again for your patience.

Lenny