Jit.movie with hap engine - unique parameter not working?

    Dec 14 2016 | 4:48 pm
    I have my own media server that I've written in Max, and I'm trying to integrate the hap engine into this in order to boost playback performance. This is working well, but I have one problem. In some instances, I want to load still image files - jpegs, PSDs, etc - into my jit.movie, and I get a bad performance hit when I do this. It seems that with the engine set to 'hap' the jit.movie doesn't respond as I would expect to the 'unique 1' parameter, so even with a still image loaded, it is loading the file from disk and onto the GPU on every bang. I guess that because the still images aren't in a hap encoded file, this is hitting the CPU hard. Is there any way around this? Or do I have to encode all my still images into a HAP format if I'm going to use the same jit.movie for stills and video?
    Thanks in advance for any insight!

    • Dec 14 2016 | 4:53 pm
      I have discovered that the problem isn't consistent between file types. PSD and JPEG files read by the jit.movie @engine hap DO work as expected, but PNG files don't. This provides a workaround for me for the time being (avoid PNG!) but still seems like an odd behaviour: I expect it's something to do with PNG files which is beyond my understanding...
    • Dec 14 2016 | 6:28 pm
      mac or windows?
    • Dec 14 2016 | 6:51 pm
    • Dec 14 2016 | 7:40 pm
      i can't reproduce, please provide a patch
    • Dec 14 2016 | 8:16 pm
    • Dec 14 2016 | 8:18 pm
      Ah, couldn't post the PSD file equivalent for the test - here is is:
    • Feb 24 2017 | 11:45 am
      I'm raising this again as it's causing me some problems and I think I've narrowed down the issue: it may be to do with image sizes. Here is an example patch with two jpegs - both from the same source, but with different dimensions. When I choose the 1024x768 image, the 'unique' parameter behaves as expected, with the jit.movie only outputting the frame once. With the slightly larger image, the jit.movie produces output on every bang. Seems only to be a problem with @engine hap.
      I'm working on Max 7.3.2 on OSX 10.12.3
      Many thanks
    • Feb 24 2017 | 4:51 pm
      hi Tom W. yeah this looks like a bug. i'll see if i can get it fixed up, but in the meantime it looks like your best option is to create some logic that disables automatic mode when a still image is loaded (e.g. framecount == 1).
    • Feb 24 2017 | 4:55 pm
      Thanks Rob, much appreciated. I'll use the frame count trick in the meantime, good plan.