exporting patch as image
This might sound a bit ambitious idea, but is there any way to export the GUI of a patch as an image?
preferably a high quality image?
I’m not even sure if I should post this here or in the Jitter forum… :)
The Export Image option from the File menu will do this. You can set the DPI using the Export Image Resolution setting under Preferences.
Now all we need is a way to convert the images back to patches. [jit.img2pat] or something? :P
"Now all we need is a way to convert the images back to patches. [jit.img2pat] or something? :P"
haha, not a bad idea!
Back to my question…
thanks Luke.I wasn’t aware of this function since I haven’t used Max since version 4.
However, my ultimate goal is to be able to export a patch image from a standalone application, or even in runtime mode.
Is this possible?
I built an standaolne but doen’t seem to have this option. Neither if I run the patch with runtime.
There’s a message to Max called exportimage:
exportimage message to max with syntax ";max exportimage patchername [pathname] [dpi] [x y width height]" where params in brackets are optional, patchername is a name previously used for the openfile message to max to open a patcherr, dpi is the resolution of the resulting image, and x,y,width,height specify the portion of the patcher to export.
Didn’t test it in a standalone though.
and jit.desktop object
the only problem with [jit.desktop] is when the patch is big enough to have a scroll-bar…
Emmanuel, unfortunately this doesn’t seem to do the trick in standalone and runtime mode..
thanks for all your suggestions. Many different ideas.. :)
Well, what I’m trying to do is to create a patch where the GUI will look like the analogue mixing desk we have at the studio. Ideally we want to save all the parameters on the patch and export (print) it so as it will be the recall sheet for future reference.
Since there’ll be other engineers using the patch as well, I would like to find a straightforward way of doing this
a) because the time is very limited during the sessions and
b) because the other guys are not experienced with max.
Now, the best option would be to purchase a max copy at the studio but I don’t think this will happen since I’m not the one who decides about purchases and I don’t think it’s gonna happen. To be honest I’m not sure it worth buying the software just for this reason.
That’s exactly the reason I want to use either a standalone or runtime.
But wouldn’t it be better to simply use a pattrstorage to save the settings as a preset?
Recall sheets are the way to go in an analog world, it reminds me at my old ARP 2600! But its so old fashioned and ineffective -, though the little differences you do in the hours of recreating a set with a sheet probably makes the difference…;-)
Btw. I use cmd-shift-4 on my Mac to create a screenshot of any window (not only Max patches). I bet there is a way to make a screenshot in Windows as well…
Hi Stefan, yes you are right. Recall sheets is the (old) future :)
Saving the presets it’s not a problem but it’s much easier and faster if you read them from a paper rather than from the screen if yoy know what I mean:)
I’ve thought about printscreen but as I said the patch will have scroll-bar and also I’m not very keen on the quality of screenshots.
Well, a screenshot has exactly the resolution of your screen (You simply can’t get better than that). Guess why…;-)
Forums > MaxMSP