lightspace CMS

[Matthias Helldoppler]

Hey,

How can i setup resolve to playback a dpx sequence so that every frame is displayed for 3 seconds. i need that for calibration. any other tips for LUTs and lightspace along with the i-display-pro probe would be great

thank you

Matt

[Paul Sage]

Are you wanting a single frame out of a sequence to play for 3 seconds?
In the conform page, park on the frame that you want to freeze and cut the sequence to create a clip, then use the speed change setting to slow the clip down to 0 frames per sec. This will freeze the frame at the head of your new clip. Then just trim it to 3 seconds.
Repeat this for the next frame that you want to freeze and so on..

Or just step through the sequence frame by frame while you calibrate. Less work. :)

[jake blackstone]

Are you wanting a single frame out of a sequence to play for 3 seconds?
In the conform page, park on the frame that you want to freeze and cut the sequence to create a clip, then use the speed change setting to slow the clip down to 0 frames per sec. This will freeze the frame at the head of your new clip. Then just trim it to 3 seconds.
Repeat this for the next frame that you want to freeze and so on..

Or just step through the sequence frame by frame while you calibrate. Less work. :)

Neither one of the solutions will successfully work.
There are couple of hundreds patches for 3D profile, so doing it your way is not practical. Beside, it has to happen automatically in order for Lightspace successfully profile the display. I don't use Lightspace, I use Cinespace, but the principal is the same. You just need to apply the speed change to the whole timeline of the patches. I can't quite recall the exact settings for speed, but I think, it's something like .125 speed.

[Matthias Helldoppler]

Neither one of the solutions will successfully work.
There are couple of hundreds patches for 3D profile, so doing it your way is not practical. Beside, it has to happen automatically in order for Lightspace successfully profile the display. I don't use Lightspace, I use Cinespace, but the principal is the same. You just need to apply the speed change to the whole timeline of the patches. I can't quite recall the exact settings for speed, but I think, it's something like .125 speed.

I´ve already changed the fps of the whole dpx sequence (4913 frames) to 0,125fps but after approximately 1 minute the timeline got out of sync.
I'll give it a second try tomorrow maybe I did something wrong.

[Rob Ruffo]

Use an NLE to convert a very low resolution timeline to make sure there are no hickups. Since the slides are just full color screens, it doesn't matter. A 1080p DPX sequences can easily lose a frame of synch here or there. I would use 300p

Lighspace is capable of outputting this sequence, based on your probe (but it assumes you can playback DPX sequences at full speed.). The trick is to downres Lightspace's output to something more realistic for most systems.

[jake blackstone]

I´ve already changed the fps of the whole dpx sequence (4913 frames) to 0,125fps but after approximately 1 minute the timeline got out of sync.
I'll give it a second try tomorrow maybe I did something wrong.

No, I'm sorry, the timeline can't go out of sync. There is nothing there to go out of sync. What you need to find out from Lightspace is the correct timing for their software and your probe to read the patch. Cinespace does it in about 3 seconds per patch with Hubble i.e. .125 speed. The timing is different with Minolta or Klein (it's faster). The software detects the patch, reads it and resets automatically for the new patch after it's done reading the patch. When the new patch comes in it is ready for the new readout. The timing doesn't have to be precise at all. I have done this a few times with Hubble, Cinespace, DaVinci and Plasma and I never had this issue with "timeline going out of sync". In you case, Lightspace, as incorrectly pointed out by Rob, doesn't output any signal. The signal comes from DPX patches played by DaVinci. Lightspace just reads them.

[jake blackstone]

One more thing to keep in mind. You haven't specified your probe and not every probe is even capable of assisting with output independent profiling. You'll need at least Hubble or something better. I wonder if the X-rite i1Display Pro works for OIP. It's great probe at great price. Cinespace 2.9 (I think) supports it now.
Correction:-)
I see, that you did specify the probe. You may be out of luck. Check with Lighspace, if they recommend using your probe for OIP.
The bummer part is Decklink used to be capable of displaying the desktop. In that case you didn't even need to bother with patches, but, I think, on version 6 they stopped providing this capability due, they say, to Apple changing something in OS:-(

[Nick Shaw]

The bummer part is Decklink used to be capable of displaying the desktop. In that case you didn't even need to bother with patches, but, I think, on version 6 they stopped providing this capability due, they say, to Apple changing something in OS:-(

They have now put it back as of v9, to support SDI output from FCP-X

[jake blackstone]

They have now put it back as of v9, to support SDI output from FCP-X

Which means you still have to use OIP patches out of FCPX instead of Resolve. In the old days you could output Mac desktop through the Decklink, so you could just use desktop patches from LightSpace or CineSpace.

[Steve Shaw]

First, the i1 Display Pro does indeed work in Display (output) Independent Profiling (DIP) mode.

And you can also use the desktop display capability via Decklink using the Network interface Java App that comes with LightSpace.
This plays the LightSpace output directly on the desktop, so no sync issues, etc.

DIP mode is very easy - but the DI system time-line MUST play real-time guaranteed, with each patch being held exactly for the duration set within LightSpace.
If the Resolve system in use can't guarantee real-time playback it will never work - but as suggested try lower resolution patches. The colour value must be identical, but resolution is not an issue (unless profiling Plasmas when a small patch size IS required - NOT full screen!).

The sync between the time-line playback can be within +/- quarter to half a second (so don't have to play both exactly aligned), but must not slip from that initial sync value.

I have been trying to help Matthias, but an not a Resolve user, so was not sure how to accurately set a patch repeat to exactly 3 or 4 seconds...
In some systems I use an edl to build the time-line, but I've been told this doesn't work with Resolve???

Hope this helps.