Jit.movie with hap engine – unique parameter not working?
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!
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…
mac or windows?
i can’t reproduce, please provide a patch
----------begin_max5_patcher---------- 671.3ocyWEsaaBCE8YxWgEOmEAlFftm59NllhbB2PcDXSsujjtp9uOaCzx1n jzlLVERfr803y4bubr4oYd9qkGAsO4qjuS77dZlmmqKaGdss87KYG2Tvztv7 EvA45c9yaFBginqajr1bAJlF5FSTWJqwB.cSLpsWM9XA3lRWbMAgOVAM3veM Sj6O+0mMuUxOZiuhgatmKxWofMXyTBCSVDLmDRSsOhcMnzEAuLGdlaIMH+Kg o8.HWzguPaeOOal817KSK1wwE4EKTfHCTjCgCKHz2ufLpFjdyhkFI3Vpk7o2 NpDjLERvAtHSdXh4OMZoi+gix+3qF+WWinTLLCCemLbL1QoANFcSZyit6CRu kSTE9ddFHqJXBvjkI2gJlPuUpJM3VCH4xS7l0YUICU7imL8GlFY0jHZale7B .5USgJAslkC+kDo.V1EWVLdIQ7xdldM08uIgCFjvzO.gs49sU57Z9EmdOYRk ljzqpOMninCQwWr02JEnfU1r1eSwYE8GYKaiajfAK.5Enl+SWfgFI858kyCk .pjDZv+dKitMECbxV7n0GIWsxCTlmW.WL63B7bHWbvosCewruhoLkEHnVAB1 5hQJCttNkkx8bfbWlhc.kNmRPjyMll2ypH2YndUMtxNiZEPLiVK3OTC+WrOa O9PTbzXUKQmz8zMK+BCI+iCW5VZa++tTpk0pMcvtsfj75ZmAZjKXH2rU6qwX OIWuftmmkAh9I0Lt1lmc.e3ugOW3DeFvIYxPSzYflzOUnwdjjOSvgNYvwUjF dB7DMsv4jxSxzhG5mH7DbF5yGMc03Jxpp1CJc6qzgDyVI6jJayj4tlbQSS2e MaNK4ddW7t8P8YJiANZbuMaY3rkOl1rMmeoz7SmBygyZbjMq7yy9ED0EpVB -----------end_max5_patcher-----------
Ah, couldn’t post the PSD file equivalent for the test – here is is:
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 1024×768 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
----------begin_max5_patcher---------- 512.3ocsUssaiBCD8Y3qvxOyFggzFz9T1uiUUQFvg3Hvl0WRoaU+2W6AHMsP UKIceAiGNdlybXlwOGFfykcLMF8SzuQAAOGFD.l7FBF1GfancE0TM.CmaMFo .G0+IgsQZM0LC7QxfUdI.Ule7GqGQpMOUy.yiV5On4oVVe7w4TQEF8vqtlKd umaolhCbQ0NEqvzeLRZ5p3HTR5cvx5wmnG7G4kvP+inuX1IXO5X8HCMrNHH3 ibypGkp5RzVlflWyPj4UfzoJ.YyBj.bzfL3VuBoHaPJt2uPH86RtRsngo0zJ 1DwPwnke4++j3kj8ymwIeZFSRi8KCk.WaB6+KuuUWY4iLbuTX1SK.9EOaJmb ARM+u.Rhi.SUhrKcpf1zqE+Rwo0Kr.Y4EFoIYqt6bgQ1Yw56tGoQdhy78HUb ACcf1h15xfVqYmGlU45aPasB9ervaTqQ1PM7hOpcJYpLlt.wxQocN+q3c2T+ DICFpjtgLa4E3VbsKie2fTvid6uUL0RqpXjhCoDJ9L4JYZCW3TE2T1Wwr9MX NvKKYhKqJK4Z+boxKsIUkLEHiy9W96jdY2B8huI54mv7o7KcI76+tZ4uR35k KxjZOZa6IlRODDfZtV1iR.9lHXKWzuEtgxMC+DeDOzjgoJW0uwU565Rgtpt6 6u6F2HcAV3FJ1GaWjeI7efRJle. -----------end_max5_patcher-----------
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).
Thanks Rob, much appreciated. I’ll use the frame count trick in the meantime, good plan.
Forums > Jitter