The LSX tutorials thread!

Sorry for the delay in questions tonight... I finally got everything configured, running and setup in a presentable location in my house, and decided to just sit back, hit play, turn on the fog, and watch the photons... it was nice.

My projector seems to have arrived pretty spot-on scanner wise, but the colors may be just a tad off - it's always hard tell as color is obviously relative - so assuming my monitor is correct, then my LP is just a tad too red - what I have noticed is that when it should be displaying an nice bright orange, the projector is still quite red. So my next step is to dive into color correction in LSX. Anyone got any tips?

Edit Color Palette (icon along the top menu bar with the vertical color stripes) -> DAC Settings -> Color Mapping / Color Linearity.

Quote:

---

Originally Posted by BlueFang

Sorry for the delay in questions tonight... I finally got everything configured, running and setup in a presentable location in my house, and decided to just sit back, hit play, turn on the fog, and watch the photons... it was nice.

My projector seems to have arrived pretty spot-on scanner wise, but the colors may be just a tad off - it's always hard tell as color is obviously relative - so assuming my monitor is correct, then my LP is just a tad too red - what I have noticed is that when it should be displaying an nice bright orange, the projector is still quite red. So my next step is to dive into color correction in LSX. Anyone got any tips?

---

This was one of my early LSX shows - feel free to have a play but watch your scanners - I am not responsible for meltdowns ;)

This show is one that doesn't scan too well but reducing the source image size and scan size might help. I've done zero optimisation *retardo


Attachment 42060

Keith

Quote:

---

Originally Posted by Galvonaut

This was one of my early LSX shows - feel free to have a play but watch your scanners - I am not responsible for meltdowns ;)

This show is one that doesn't scan too well but reducing the source image size and scan size might help. I've done zero optimisation *retardo


Attachment 42060

Keith

---

Thanks for sharing, Keith! That's really generous of you. The show is a bit point heavy in a few spots from what I can tell, but I am sure it is easily adjusted.

Here's what it looks like on a pj running at 40kpps: https://vimeo.com/85358145

-David

That's OK - you guys have shared plenty with me, so it's only fare to give a little back :)

Thank you for filming this (3 times?) Dk!

I still need to get started with my build(s) but have enquired about some enclosures to save a little time. Looking forward to being able to film them myself but money going in all sorts of directions at the moment (except towards me) - like visiting DutchLEM ;)

Designing blind is a little spurious - it's interesting to see what scans and what doesn't - I still can't understand how the 5 rotating 3D cubes in my Shpongle show scan and yet circles sometimes struggle. I think you are right about reducing points - I guess circles have lots of points which don't always need to be there?

Keith

Quote:

---

Originally Posted by dkumpula

Thanks for sharing, Keith! That's really generous of you. The show is a bit point heavy in a few spots from what I can tell, but I am sure it is easily adjusted.

Here's what it looks like on a pj running at 40kpps: https://vimeo.com/85358145

-David

---

Quote:

---

Originally Posted by solidude

How do you set the global fps of your show?

---

I'm not sure if I did for this show. My lasers are no good at all for this stuff.

When I do shows with LSX I edit scanner optimisations and do adjustments there - As my lasers are pants I haven't looked into scan and show optimisation.

Keith

You can't set global fps.

Quote:

---

Originally Posted by colouredmirrorball

You can't set global fps.

---

Good point - I read that as pps *retardo

You dont want to control fps. Fps is determined by scan speed / points per frame. If your frame has a smaller amount of points, fps will be higher, and vice versa. You want more fps (= less flicker), reduce point count or increase pps.
Imagine you could set fps somehow... frames that take too long to draw would get clipped down, while small frames would display then stop output!

The program is sending out a stream of points rather than a frame. A frame is more of a software thing. When it has sent out all points belonging to a frame, it has displayed a frame, but for the projector it's no more than a bunch of points. It (should) seamlessly move on to the next stream of points, belonging to another frame. When you display a frame with one point at 30 kpps, you get 30 000 fps... so that's the "upper limit".

My explanation completely ingored the existence of "buffers". The software actually sends a frame to the DAC driver, which buffers it and then converts it to a stream of points. But that doesn't change much to the explanation. I could be wrong though, that's just how I think it's done but haven't touched DAC output yet.

The fps window you get when importing is for internal time synchronisation. LSX will stretch out the resulting animation file so it reaches the fps you have set.