Alpha channel ?
I want to export files without unused space / pixel. - How can I consider transparency / an alpha channel when exporting?
Keyboard shortcuts
Generic
| ? | Show this help |
|---|---|
| ESC | Blurs the current field |
Comment Form
| r | Focus the comment reply box |
|---|---|
| ^ + ↩ | Submit the comment |
You can use Command ⌘ instead of Control ^ on Mac
Support Staff 1 Posted by Frederik De Ble... on 29 Oct, 2013 08:43 AM
PNG export should have transparencies. As far as I know, movies always have an alpha channel, so if you want to export movies, you should use "Export Range".
2 Posted by thoolb on 29 Oct, 2013 02:41 PM
Indeed, both PNG and PDF export with Alpha/transparency. Thanks you for your quick response!
Unfortunately on PNG/PDF export the document property of canvas size is ignored. Instead every frame gets exported with its max. used rectangle (which might vary from frame to frame). A workaround would be to export huge areas/ files, even though a part of it is needed only. – May be I could subtract any geometry around the canvas setting size, could I? For this I'd need to know the max. used space within the render frame range, right? How could get this max rectangle dimensions 'automatically'?
The two screenshots below illustrate the issue: They show different max used areas (hight: 1460 vs. 2549 px). The black rectangle shows the desired render area but it does not keep its position in the upper left corner (because the moving geometry rotates around it).
(green marks the successfully alpha ;)
Any suggestion as workaround for this?
Support Staff 3 Posted by Frederik De Ble... on 29 Oct, 2013 02:55 PM
This is a known issue:
https://github.com/nodebox/nodebox/issues/350
I'll fix this in the coming weeks.
4 Posted by thoolb on 29 Oct, 2013 03:02 PM
Sounds good! Thank you!
Support Staff 5 Posted by Frederik De Ble... on 02 Dec, 2013 10:28 AM
Hi, you can now set
canvasWidth,canvasHeight,canvasXandcanvasYin document properties. This means NodeBox will no longer look at the bounds of the shape but will always use these settings. You can also preview the bounds by checking "bounds" in the viewer pane header.All of this is available in 3.0.37.
Hope this helps,
F
Frederik De Bleser closed this discussion on 02 Dec, 2013 10:28 AM.
thoolb re-opened this discussion on 05 Dec, 2013 02:05 AM
6 Posted by thoolb on 05 Dec, 2013 02:05 AM
well done, thanks! The bounds checkbox is very helpul, too!
p.s.: please, would you switch in this option window the order of Height and Width according to X and Y (like 'some' global usage): Horizontal first, vertically at second. (If I do type it the window won't remember.)
p.p.s.: to pimp it again: a ruler + checkbox would support us as well. (unfortunately: it would need to be 'responsive', related to module/window-size AND view-zoom related.)
Support Staff 7 Posted by Frederik De Ble... on 06 Dec, 2013 09:28 PM
You're right, the document settings panel is rather spartan at the moment.
We probably want to add a more user-friendly way to set the document size.
Best,
F
On Thursday, December 5, 2013, thoolb wrote:
8 Posted by thoolb on 06 Dec, 2013 09:39 PM
ah, thx!, – might even consider to totally move the doc size setting into the export setting, cause NB does not need any document size setting at all (! / let me know if I miss sth) – Instead the export dimensions are very relevant.
9 Posted by Hannes on 11 Dec, 2013 05:09 PM
Is it possible to export without the docsize settings, with the export automatically choosing the size of the image, like it used to? Because now I'm stuck with manually changing the docsize to match the size of my image.
10 Posted by thoolb on 11 Dec, 2013 07:30 PM
I do agree. This would be useful in the export options window:
• to have a checkbox for (de-)activating document size
• and, luxury version, to additionally set the export size in the export window
Momentarily I workaround with both releases (v.3.0.36 & v.3.0.37). Fortunately the .ndbx files appear to be compatible.
@ Hannes, the previous version 3.0.36 is here for a while: https://www.dropbox.com/s/vhuaopilymn4gpn/NodeBox-3.0.36.zip
@ Frederik, please don't hezitate to let me know if you'd prefer me to delete the file in this download link !
( @ Frederik, you might want to consider a download/releases archive in the time being. I do appreciate the access to NB 1 and 2 – appearently even more detailled release steps are worth for download.)
Support Staff 11 Posted by Frederik De Ble... on 11 Dec, 2013 07:42 PM
I'll add support for using the bounds for export in the next version (and remove the transparent border as well). I think it's useful to be able to set the document size (instead of specifying it on export) so you can see the bounds in the viewer.
To download any previous version of NodeBox, modify the download link for the current version. For example, the 3.0.36 version is available here. A GUI would be more practical, I agree. We'll probably add it to release notes page.
Best,
F
12 Posted by thoolb on 11 Dec, 2013 08:36 PM
Do this two '>'-thoughts need to be directly related, indeed?
• The document size does not limitate the design and script-running process at all. – Correct?
• If document size influences export only, why not placing its GUI in the export options window?
• 'Bounds' (in preview window): Would be useful to see it in foreground, on top of any scenery. Color/opacity might help to identify them.
•• What if the user creates objects larger than the docSize? Would need to adjust the docSize before export, and, need to alter docSize according to the frames dimensions the export should include each time?