Rodrigo

So in working on a larger/complex M4L device I've noticed a bunch of weird UI artifacts whenever I use the device within Live, whereas in Max it's perfectly fine.

I thought it might have been due to the high CPU use and/or other factors, but after some testing, I have figured out that the glitching only happens when I'm using my retina display set to "more space", so the display is "scaled".

Has anyone else experienced weird stuff like this?

Attached is a video clip showing what I mean, along with the M4L device that does it. What you'll see is a momentary flash of white the size of the UI elements that are moving.

This is the complete code for the device too:

I've reduced the part of my part that does this down to a multislider and a section of audio analysis patch that sends data to it. It does use one of the Alex Harker externals (descriptors), but that's included in the M4L device if you don't have it.

ui_glitch.mov

Untitled Device.amxd.zip

So in working on a larger/complex M4L device I've noticed a bunch of weird UI artifacts whenever I use the device within Live, whereas in Ma

max-for-live--retina-display--glitchy-ui-elements

Yes, I've been seeing this recently. I've also traced it back to the retina settings (13" mbp), but mine is only good on the 'more space' setting and glitches on the others.

I was just ignoring this.. and hoping it would fix itself, so pleased you've brought it up. Happy to provide info to support if that's helpful.

Just to add - I've only been using M4l for a couple of months, so this is not something that has just started.

Interesting that it's flipped on yours. I wonder if it has to do with the relative scaling that happens with Live/M4L then.

And good to know that I'm also not the only one experiencing it!

Have you found any workarounds, or is it just there and that's that?

Interesting though - I just tried to capture it with quicktime screen record and it didn't show up in the video. I also tried your device and had the same issue (on the same settings). The descriptor external failed to load, so I suspect that's not the issue in your case.

It's 32bit only, I should have mentioned. So it needs to run in 32bit Live. The sliders wouldn't move at all without the external, so I doubt anything would happen.

FYI I submitted it as a bug report, so will post here if anything comes of it.

Just to confirm - I see glitches with your patch even without the external loaded or the faders moving.

Ooh, that is very interesting indeed then!

Hey Rodrigo, did you ever get a reply on this?

Nope, surprisingly. They normally send a follow up response fairly quickly asking a question or saying what the issue (might) be.

And in fact, another bug report I submitted after got a response. (When 32bit Max crashes, it reopens as 64bit Max)

That is surprising. My experinence has been the same quick responses.

Here is a video of the problem on my screen: 

You can see how the issue is fixed if I up the retina display.

In case it's useful to anyone my specs are:

MBP 13" Early 2015, Intel Iris 6100, 2.7ghz i5, OSX 10.11.6, Max 7.3.3

Here is a video of the problem on my screen: https://youtu.be/0oNBrzDT2Vg

I suspect (hope) that it's just a bigger issue that they are looking into, as this kind of rendering/scaling stuff is probably quite low level in terms of how the code is laid out(?).

Some others have been asking me about this via the youtube link.

Would be great to hear from anyone at C74 or Ableton about this?

Some others have been asking me about this via the youtube link. 

The tech support people have been in touch (a few weeks ago) and were still looking into it. They were unable to reproduce the problem, is where it was last left (as far as I know).

I'm also happy to provide system info etc too - in case that helps.

Yeah, post it, and I'll relay it to them.

Max For Live + Retina Display = glitchy UI elements?