Frame Rate, Resolution of Media Content

I'm looking for some recommendations on maximum parameters on pixel maps. I understand there's a 16,384 pixel limit per map, which works out to 128x128 pixels if done in a square. Could this potentially be done in other shapes which fit into a rectangle, like 2x8192, or are there other maximums there?

I'd also like to create some media content in video generation and editing software. What is the standard or recommended framerate of video content? Some larger (HD720p, H264) videos seem fairly choppy on the Pixel Map Preview. Will the output be choppy as well? Should I aim for lower resolution, is this a frame rate thing, or is the processor for output, or just the hardware video card for preview just struggling?

Is image resolution limited as well to an extent? How does high resolution images or video affect the output or the preview? For example, a 1000x800 pixel image in a 32x32 map

Parents
  • There is a complicated answer and a simple answer 

    Simple Answer - Dont do HD video, crop your source files down to something more manageable. The closer you make them to your true output size the happier your processor will be.   I use Quicktime Photo J-Peg for my files - but only because I do a bit of M Box stuff as well.  I tend to make them 200 to 320 pix wide at 30 FPS

    Complicated Answer -

    Output takes priority over GUI refreshes - so laggy Pix Map Preview doesn't always equate to laggy output.   There is no way to determine if the lag you are seeing is in the GUI or in the actual playback of the clip without something to output to.

    If this is for your ION show - be careful.  Ion has been around a long time and the older Ions are the bottom of the ETC processor barrel.

    All the screen content goes through the processor - so keeping your screens simple can drastically reduce processor load.  Pix Map Preview, Big Magic sheets of dynamic content, Channel displays zoomed way out showing 1000's of channels running FX - these kinds of things are good to avoid if you are having processor problems. 

    Now all those warnings aside - I have maxed out an ION 2k running LED pix map stuff in the past and it rocked.  There is something very pleasing in being the only guy at the party busking video straight from the desk without all the server delay.   Just don't get cavalier with the 1080p or you can (and will) crash your desk.

     

     

     

Reply
  • There is a complicated answer and a simple answer 

    Simple Answer - Dont do HD video, crop your source files down to something more manageable. The closer you make them to your true output size the happier your processor will be.   I use Quicktime Photo J-Peg for my files - but only because I do a bit of M Box stuff as well.  I tend to make them 200 to 320 pix wide at 30 FPS

    Complicated Answer -

    Output takes priority over GUI refreshes - so laggy Pix Map Preview doesn't always equate to laggy output.   There is no way to determine if the lag you are seeing is in the GUI or in the actual playback of the clip without something to output to.

    If this is for your ION show - be careful.  Ion has been around a long time and the older Ions are the bottom of the ETC processor barrel.

    All the screen content goes through the processor - so keeping your screens simple can drastically reduce processor load.  Pix Map Preview, Big Magic sheets of dynamic content, Channel displays zoomed way out showing 1000's of channels running FX - these kinds of things are good to avoid if you are having processor problems. 

    Now all those warnings aside - I have maxed out an ION 2k running LED pix map stuff in the past and it rocked.  There is something very pleasing in being the only guy at the party busking video straight from the desk without all the server delay.   Just don't get cavalier with the 1080p or you can (and will) crash your desk.

     

     

     

Children
  • Thanks Patrick, that makes a lot of sense, and yes, this will be on the ION 2k, so I'll do my best downsample to keep resolution relatively matched or close enough hopefully not to choke the processing too hard. 

    And I just checked sizing maximums, a 2x8192 map is totally doable, but looks like only a tiny portion of it will show up on the pixel map preview. Guessing that loading content that size might be a little dangerous for the poor processor, but could work. I'll not tempt fate until I actually need to try this, which won't be for this project. 

Related