Resolume Forum

If you forget to stop mapping osc before loading a new comp, resolume may crash. It happened a few times.

Are you sure it's caused by the mapping mode being active? Or could it also be that you're still sending OSC?

I was editing a TouchOSC template so sending wouldnt have been possible. The composition was 3240x1080 and was only running at 15fps with PNG files. I'll try to replicate the issue. Is there anything you'd like me to do when I test it again?

3240x1080? Were the PNGs that resolution as well? How many did you have? I think that's more a likely culprit than the OSC mapping mode.

A lot of people tend to throw in stills, thinking that they're not as heavy as video files ( because, you know, it's just a still, right? ). Turns out that every still image has to be loaded in its entirety into memory. Depending on the compression used, for your files that could run up to 13MB per image. Toss in 50 and you've used up more than a sixth of the total RAM Resolume has available to it.

It sucks, but we're still running a 32 bit system ( thanks to Quicktime ), which was fine when 20 files of 1024x768 was a lot. But now people are throwing in hundreds of 2K files without batting an eye.

Res 5 will have to be 64 bit, because being able to throw in hundreds of 2K files is awesome. But for now, when working with these type of resolutions, really keep an eye on what amounts of data you're actually pushing, and try to keep deck sizes down as much as possible.

There are around 50 png's that are 1920x1080. I know I'm pushing Resolume but we're still building this project. The final version will be a 1920x1080 comp. Each layer will be routed to its own screen using the Adv. Output and all images will be converted to DXV.

I was unable to reproduce the problem. Maybe one of the other apps I had open the other day was causing the issue.