I´m following this thread, Deleechious, you may be a lifesaver

I just deleted all old prefs and started form scratch, and that, as always I guess, worked. Thanks! The "Deck/Layer setting is important to remember, yeah.

Hi, yes, I have no Midi notes assigned to any column in either Application or Composition midi map. No DMX, OSC or keyboard either, for that matter, just to make sure

Hi! Pretty sure this question is valid, even if it may intersect somewhere with Novation support. I have a column trigger via MIDI problem. I have removed the MIDI trigger for Column triggering. (but no clips ignore column trigger when mouse clicking). But Arena will trigger the column anyway, when ...

Changed the comp and content to 2400x4800 (vertical), with the same (advanced) output at two times 2560x1440. 4 slices to each screen, but Arena starts warning me as soon as I move mesh points back and forth. If I´m too fast with my fingers, i.e. rapid arrow keyboard action, Arena.exe stops working ...

I´ll have a look at the system tomorrow, and look at memory usage. Thanks for testing!

Thanks for the feedback,
I tried making a new comp w. one layer 6000x3000 and slice stuff up that way.
Same problem with low memory warning.
File is encoded to DXV3 on a mac, btw.

No fx, disabled global rendering. Fps @ 59/60 steady

Thats correct. I was adviced by Resolume support staff to avoid large canvases, and rather pipe things with layers to different slices

Updated to 5.0.2, same thing happens.

Windows 8.1 64bit, 32GB RAM, Xeon 3.50 GHz, Arena 5.0.1 (updating to .0.2 as we speak) 7 layers of 1920, with one 6000x3000 video in each layer, DXV3 Outputs 2x 2560x1440 to 2x Datapath x4 Mesh warping 4x4 on all 7 slices in output. LOW MEMORY warning Crashes (...has stopped working) New to windows,...