Pixel Mapping - stretched pixels bug?

Hello

I’ve come across unexpected behaviour when using pixels that have been stretched to cover more than one square on the pixel map grid.

Firstly, content isn’t respecting the stretched cells - if you look at the attached video, looking at pixel map preview with the cells overlay -  the white line is the content, but the fixtures only activate when the most central pixel square gets content, not when the content reaches the fixture as laid out in the pixel map.

Secondly, when selecting a stretched pixel to re-number it, every square of the stretched pixel gets broken down and given a new subsequent channel number, rather than it treating the stretched pixel as one channel. 

I suspected this may be an issue using multi-cell fixtures as that’s what it’s affecting here, however I can confirm consistent behaviour when using whole channel numbers and not just multi-cell fixtures.

Running Eos 3.0.1 Build 31.

Thanks,

David

Related