Resolume Forum

Hi There,
It's just something that keeps nagging me since I have to do a lot of slicing and mapping with al the creative stage designs this summer
Why is it that when I receive a pixelmap from the Screen rental I always have to add half the screen size in X and Y to get the slice on the right spot?
Why not start with 0,0 but with 0(+half the size in pizels), 0(+half the size in pixels)?
Is there some Resolume handy thought behind this that I haven't figured out?

Then today I made like 32 slices for a festival next weekend on my Windows machine, transfered it to my Mac and I could start over again because all the numbers where absolutely wrong compared to what I've saved on my Windows machine, so I re enterd all the right digits and it was done, but I still don't understand why this happened?

I do a lot of led mapping too, and the 0,0 xy would make my life easier as well.
I have had a similar problem when moving between computers, the best explanation has to do with edid sync issues, sometimes power cycling the processor forcing a resysnc will clear it up.

Is there some Resolume handy thought behind this that I haven't figured out?

Not really. Since the output slice can be rotated around its center, it would make sense to have this center as the position for x and y.

Since most LED providers tend to think from the top left, for LED pixelmaps this can be confusing. To make it even more fun, on the input side, Resolume does take top left as the position for x and y.

On Res 5, both input and output will have both center and top left as input options for x /y position.

numbers where absolutely wrong compared to what I've saved on my Windows machine

If the resolution received from the system has changed, Resolume tries to maintain the mapping as best as possible.

We try to scale the mapping to the new resolution. For projection mapping this makes sense. If your output transformations were made at 1920x1080, they will still align when you set the new resolution to 1280x720. Any changes here will be reflected in the numbers shown in the Advanced Output.

Since LED pixelmaps are pixel exact, you need to make sure that the output resolution is the same as when you created it. When you load a previously saved output setup, and the numbers have changed, your output resolution is set different. In these cases, simply setting the output resolution correctly will fix the issue.

Btw, you can create pixelmaps using a dummy output, which lets you circumvent this problem.