Jump to content
Our response time is longer than usual currently. We're working to answer users as quickly as possible and thank you for your continued patience.

Frank Jonen

  • Posts

  • Joined

  • Last visited

Everything posted by Frank Jonen

  1. Right now we just get the floodgates from the config.ocio. Would it be possible to get it more towards how other OCIO tools handle it (using the hyphen as menu separator)? Specifically the grouping so it's quicker and easier to get to the transform you need.
  2. Maybe Linux would be viable if the price for the Linux version would be significantly higher so a dedicated developer could work on that alone?
  3. I turned Metal back on and the images now work. The Colour Wheel still looks a bit odd in 32-bit mode. How do you plan to handle that? Derive colour picking transform from the config.ocio or set it separately?
  4. Honestly, you'd be more productive in Clip Studio for that type of stuff. There the line follows what you draw. Its nodes are reasonably clean as well in case you want to bring the lines over to Affinity.
  5. Not necessary anymore. The Metal compute was the culprit for the EXR problems and some Jp2 issues. For a file to crash Photo you can refer to @walt.farrell's post.
  6. Yup, that's a very efficient crash here too. Just tried it.
  7. That was it. I disabled Metal compute (now the app is really slow) and the image now renders in the canvas. Jp2s also open now without crashing the app. While you work on the OCIO stuff anyway… how about a direct path from one model to the others? It'd be nice not to have to go through the Terminal each time I need to go from and OCIO output sRGB view (ACES) to an ICC sRGB output for the web or image print.
  8. It happens with all of my EXR files. I have the non-destructive 32-bit settings on btw since I need to work with these files. Jp2 files open for you? I have to batch them through ImageMagick to regular 16-bit PNGs. Do you have a link where to upload them? EDIT: Just tried enabling the destructive EXR settings one by one. Doesn't make a difference.
  9. Yes it does. It's also quite annoying to go into a destructive step just to mask a layer. Dragging a layer into the layer mask slot and use the luminance information to mask it would be much better.
  10. Last few betas had the same issue, since EXR is my main format I just stopped using the Photo betas and forgot about posting about it again. Some EXRs show up in the navigator (Quixel's do) but aren't rendered in the Canvas. Regular EXRs from Nuke don't render anywhere. ACES compliant EXRs don't render either. This bug is new to the 1.7 betas. The retail version still works fine with EXRs. Same goes for Jp2. You open a JP2 and both Navigator and Canvas stay blank. With the exception that Jp2s crash the retail version.
  11. You really make an effort to not get this. See screenshot here, no checkbox. Click the image to see the image bigger. This is of the full window toolbar area. Final list before I let this topic go for good. Groups had the option to 'Lock Children' - I used it extensively I saved the file I opened the app later on, the same day The updater suggested a new beta I installed the current beta I opened the file again I clicked on the group to resize it once again like I did hours before The checkbox was gone Either it gets fixed or it doesn't. If it doesn't get fixed, I just won't use Groups anymore and nest everything in Sub Objects. Not worth going on and on and on in a Forum about.
  12. Maybe. But the people here made an effort to misunderstand it to a point of not reading at all what I wrote and thus I stopped caring about it and found my own solution around it. Case closed for me.
  13. The option was there before with the exact same file. With the new update it isn't. I don't care anymore, I recreated the file in the retail version where it still works.
  14. Same file, new beta. The Lock Children option that was previously there is now gone. If you're on Windows, the Windows beta has another area, this area is for the Mac beta.
  15. It's not where it always was. Only the Artboards have it now, for Groups it's gone.
  16. Absolutely. The current approach is extremely imprecise. It needs a way to control the offsets properly. I was hoping this would come with the clone/step&repeat tool though.
  17. Pretty self explanatory. An essential function was removed and now groups are pretty much useless as you constantly distort your work.
  18. This bug has never been addressed, but with Publisher being, well… for desktop publishing, now would be a good time to do so. Since the beginning placing PDFs didn't work right. The formatting was broken and fonts were incorrectly replaced (Times should be replaced with Times New Roman, not Arial). As a reference on how it should work, look at Pages, Keynote, Preview, InDesign, Quark XPress… EDIT: Right now the only way we have in the Affinity suite is to rasterise each page of the document to our output device. For offset printing that would be the point where outlines are lasered on film. We're now talking about several 1200dpi CMYK files.
  19. It only works with a single specific piece of hardware despite being easily adapted to other input devices via key+scrollwheel functions.
  20. Yeah the canvas rotation bug doesn't ever seem to get fixed. It's highly annoying that on a normal working setup you're crippled with step-rotation. Why it doesn't have a key combo that you can hold while dragging to rotate is beyond me.
  21. This may sound daft at first, until you give Publisher to social media marketers (not just but it's a good example). It's so easy to get the images ready for the various platforms in one single document (and much faster than in Designer thanks to linked assets which can be updated in place). Letting us name the pages (i.e. Facebook: Banner) and unfolding the sections and pages upon export to `/facebook/banner.png` would be a great way to speed up production of more complex assets that need to be prepared (re-arranged to optimally fit) in a plethora of sizes.
  22. When you work with teams, it's now increasingly through cloud services. In addition to the already suggested Markdown, an option to map JSON data to text styles and tables would be a welcome addition that'd save us from round-tripping through parsers. A pulled update would just require a refresh in Publisher. It'd be quite helpful for magazine workflows (i.e. manage each issue's articles in a database, then export for layout), data-based brochures (e.g. annual reports) and similar often tedious tasks. Adobe is selling you some behemoth apps that don't work right to get the editorial workflow managed but they're so great that that people who should be using them keep using other apps and copy/paste into the Adobe apps, creating a mess for versioning. Quark has Quark Author which is quite overwhelming and not exactly enjoyable to use. Having a way to IDGAF import serialised data would open it up wide for a variety of use cases. Write together in Jira, Cockpit or custom tools (that the users already know and are comfortable in), export sections to JSON and have that work right away in Publisher would be a great advantage. It's a rather clean format for structured data and easy to manually fix should an exporter have the hiccups.
  23. Didn't you say this was fixed already? Did it make a comeback or is it slated for next release?
  • Create New...

Important Information

Please note there is currently a delay in replying to some post. See pinned thread in the Questions forum. These are the Terms of Use you will be asked to agree to if you join the forum. | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.