Hi Steve, the behavior is indeed reliable, you only have to look closer whats happening: The image loader provides an image, which can be of any kind, not rendered into an image bitmap buffer yet. The Billboard is consuming this image in the first case the first time through the "Image Resize" patch, which tells the image to render itself into a bitmap buffer of the 3091x4000 pixels (the first image representation). Once rendered it won't change that buffer. If you toggle the multiplexer to display the 612x792 version of the image, it gets rendered into another buffer (another image representation), but using the already rendered 3091x4000 pixel buffer as a source. This might be much quicker than rendering a complex PDF again.
If you switch the inputs at the multiplexer and restart the composition, the same happens again, but the first image representation is rendered at 612x792 pixels. Toggling then, the big resolution will be rendered with the first (smaller) image representation. To proof this, you can swap the "Initial Value" and the "Secondary Value" in the Toggle-Patch and restart the composition again. Now the big resolution is sharp again, even the image path through the multiplexer isn't touched at all. So in this scenario keep in mind, what will happen first. If you want to force a certain resolution no matter what, you can do this with a billboard patch attached to the image loader with a image Resize patch in between. The Billboard patch should have the render level "1" and width and height of "0.0001" also a color with alpha 0.001, so you wont see this but forcing the first image representation to something you want (setup in the Image Resize patch). best, Achim Breidenbach Boinx Software On 08.12.2010, at 20:09, Steve Mokris wrote: >> Pixel resolution is locked-down on PDFs. > > Kinda. The `Image Resize` patch does some magic to resize the image prior to > rasterization, if you attach it directly after the `Image` patch. See the > attached composition — the `Image` patch outputs an image of the PDF that's > 612x792 by default; passing it through `Image Resize` results in a sharp > 3091x4000 image (i.e., not the 612x792 image scaled up, but the vectors > rendered at higher resolution). > > However this doesn't seem to work reliably — for example, in the attached > composition, try swapping the order of the Image Multiplexer's two inputs, > and restart the composition. The resized image will then be blurry (i.e., > the 612x792 image *is* scaled up in that case). > > Steve > > -- > Steve Mokris [ st...@kineme.net ] > http://kineme.net/ > > <twisty.qtz> _______________________________________________ > Do not post admin requests to the list. They will be ignored. > Quartzcomposer-dev mailing list (Quartzcomposer-dev@lists.apple.com) > Help/Unsubscribe/Update your Subscription: > http://lists.apple.com/mailman/options/quartzcomposer-dev/achim%40boinx.com > > This email sent to ac...@boinx.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Quartzcomposer-dev mailing list (Quartzcomposer-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/quartzcomposer-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
