About: FAQ:Why is animating stills so sluggish?   Sponge Permalink

An Entity of Type : owl:Thing, within Data Space : 134.155.108.49:8890 associated with source dataset(s)

|I have a 3.0 GHz P4 that is hyperthreaded with 1 GB RAM. I loaded and animated a 6-layer .psd file that was 1748x2480 as a sequence. When I started to animate the layers, performance was very slow.BUT, and this is a very big *BUT*, that was only when I had the Playback Quality settings to High or Automatic. As soon as I set PQ to Draft, response in the timeline was almost instantaneous. Here's a rundown on what the PQ settings mean:1. High - Playback and still frame are shown at full resolution (in this case, 1748x2480).2. Automatic - Playback is shown at Draft quality resolution and still frames are shown at full resolution. (This will explain why RT playback of these huge images performs better than just jumping from frame-to-frame.)3. Draft - Playback and still frames are shown at 1/4

AttributesValues
rdfs:label
  • FAQ:Why is animating stills so sluggish?
rdfs:comment
  • |I have a 3.0 GHz P4 that is hyperthreaded with 1 GB RAM. I loaded and animated a 6-layer .psd file that was 1748x2480 as a sequence. When I started to animate the layers, performance was very slow.BUT, and this is a very big *BUT*, that was only when I had the Playback Quality settings to High or Automatic. As soon as I set PQ to Draft, response in the timeline was almost instantaneous. Here's a rundown on what the PQ settings mean:1. High - Playback and still frame are shown at full resolution (in this case, 1748x2480).2. Automatic - Playback is shown at Draft quality resolution and still frames are shown at full resolution. (This will explain why RT playback of these huge images performs better than just jumping from frame-to-frame.)3. Draft - Playback and still frames are shown at 1/4
dcterms:subject
abstract
  • |I have a 3.0 GHz P4 that is hyperthreaded with 1 GB RAM. I loaded and animated a 6-layer .psd file that was 1748x2480 as a sequence. When I started to animate the layers, performance was very slow.BUT, and this is a very big *BUT*, that was only when I had the Playback Quality settings to High or Automatic. As soon as I set PQ to Draft, response in the timeline was almost instantaneous. Here's a rundown on what the PQ settings mean:1. High - Playback and still frame are shown at full resolution (in this case, 1748x2480).2. Automatic - Playback is shown at Draft quality resolution and still frames are shown at full resolution. (This will explain why RT playback of these huge images performs better than just jumping from frame-to-frame.)3. Draft - Playback and still frames are shown at 1/4 resolution. Performance is great at this setting.My recommendation - animate these huge images in Draft to start with, fine tune as necessary from time-to-time in Auto or High, and don't expect the final render to be done during the new episode of Spongebob. |}
Alternative Linked Data Views: ODE     Raw Data in: CXML | CSV | RDF ( N-Triples N3/Turtle JSON XML ) | OData ( Atom JSON ) | Microdata ( JSON HTML) | JSON-LD    About   
This material is Open Knowledge   W3C Semantic Web Technology [RDF Data] Valid XHTML + RDFa
OpenLink Virtuoso version 07.20.3217, on Linux (x86_64-pc-linux-gnu), Standard Edition
Data on this page belongs to its respective rights holders.
Virtuoso Faceted Browser Copyright © 2009-2012 OpenLink Software