Resolume Forum

Hi all,

No crash, but certainly a problem.

After working for several hours on a composition, stacking pngs and recording them within the composition to DXVs for playback, the record button suddenly stopped working.

If I open the composition INTO a different (empty) deck it works. But if at any point the deck containing most of my images loads, it will kill the record functionality unless I save while looking at an empty deck, so upon reload I can record again.

I assume it has something to do with Resolume getting overloaded with content in the deck?

Also, if I try right clicking Record to File, I see "ABORTED" in red next to it in the queue. Any ideas? Are PNGs so terrible that even having them present in a deck will kill the record function eventually?

Latest and best i9, 64GB Ram, 4080, etc

I'd say you might have ran out of disk space, or loading the lots of png-s fills up the RAM, so there is no more room for the recording.

I'd recommend using Alley to convert the pngs to DXV, that way you get 1 frame DXVs which use a lot less space on disk.

Totally. That makes sense. But I have ample Disk Space and Ram available.

The only reason I like using PNGs in certain cases is because that's the delivery I might get from my client. So my workflow is

• Map the environment.
  Sit down with the director and load in the images
  Assemble images in looks (in a separate NON SHOW deck)
  Record looks
  Move DXVs into the SHOW DECK

Adding Alley adds only an additional thirty seconds, but in some professional environments, thirty seconds of the Director's time matters. And adds up.

I didn't have this problem in the last build. Is it possible the new one is somehow a bit more vulnerable to PNGs?

Thank you!

If it happens again, check the resources, also the VRAM.
Clip rendering might also be of help, you could convert the pngs to DXV inside Resolume with that.
https://resolume.com/support/en/clip-renderer