Jump to content

Daniel Höpfl

Members
  • Content count

    8
  • Joined

  • Last visited

About Daniel Höpfl

  • Rank
    Newbie

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. More or less that's what I'd do now: Delete all but the first two pages of each chapter (to not loose the chapter head but keep the page with the content master), fix the frame positions on page one and two of the chapter, add enough empty pages, auto-extended the second page, remove unused empty pages. Repeat for each chapter. BTW: "auto-extend" is a manual process. I'd like to mark text frames as truely "auto-extending", so that changing the line height by 5% does not force me to check every chapter. Might already be possible: Odd-page masters: Any page that has an odd-page -master assigned (chapter head) automatically gets its spread extended by an empty even side if the previous non-empty page is on the odd side.
  2. Using the latest Publisher Beta, I set the page size to 135mm x 215mm, 3mm bleed on all sides, two pages per spread. Then exported to PDF (using presets Print and Export), all Pages. Preview.app's info shows that the PDF pages have 141.1mm x 221.1mm. Setting the bleed to 2.9mm results in 140.9mm x 220.9mm. While this difference does not matter for any practical purpose other than overly strict format checks, I'd expect the PDF dimensions to match those in Publisher.
  3. I just finished a 132 page (very) simple text book … I'm not a pro, using LaTeX would probably have been faster in my case. You don't have to create textboxes for every page: You can Shift-Double-Click the next column triangle to autopopulate pages. BUT: This auto-fills empty pages (Well, I wanted to have that empty left side before the next chapter), even if non-consecutive (WHUT?), and if there are no empty pages left, creates new pages at the end of the document. (Maybe I did not understand this but that's what it looked like to me). When I had set up all chapters, I decided to use a different page size. That's when I had to touch each and every text frame. Then I did not like the borders on the new page size. Had to touch each frame (again).
  4. I, too, do not like the new icons. They fail the HID "Consider giving your app icon a realistic, unique shape". The (now) old icons had the very distinct triangle shape that helped me a lot. Maybe if you removed the top left corner on macOS, they would regain that shape factor. (BTW: Until now, I did not realize that the icons show an aperture, a pencil, and ... sheets/book? Correct?)
  5. I'm aware multi-master is already implemented. Software developer here, too: I do not avoid inheritance when it is useful. Master pages are very similar to paragraph styles. Publisher has inheritance there too: Changing the font in the standard style also changes it in all derived styles (unless overridden there). I would like to have the same for page masters.
  6. @MEB please consider this message as a +1 for good master pages support starting with version 1.0. By “good support” I mean something very similar to how it is done in Apple's Keynote. I also agree with what @Seneca said, it seems like your devs envisioned Publisher as a “Leaflet-designer”. I will rarely (if ever) use Publisher for a leaflet but I would like to do things like (family) photo books. For this, I'd like to see great master pages with multi-master support and tree-like masters in future versions (v2.x): Background Master (Some fancy boxes in the background, pages numbers, etc.) Green Background Master (based on Background Master but changes color of boxes to greenish) Red Background Master (based on Background Master but changes color of boxes to redish) … Images Master (Contains 4 image placeholders but these are marked inactive/hidden) 1 Image no Text (Unhides one image placeholder, makes it fill the page, other placeholders still hidden) 1 Image, Textbox (Like 1InT, but different size/position and adds a text box) 2 Images (you get the idea) I'd like to be able to assign any number of masters to a page. Publisher should be smart enough to understand that Green and Red contain the same objects thus only one of them can be assigned at any time. But “Green” and “2 Images” do not share any objects thus they can both be active simultaneously. Of course, switching between “1 Image” and “2 Images” would reuse the first image but re-position it (as it works in Keynote).
  7. First of all: This is my first post, so Hello to all of you. I'm neither a pro designer nor a pro photographer. I'm a software developer that likes good design and that owns a DSLR. Serif’s tools Affinity Designer and Affinity Photo ended my search for good tools in their respective field. Whenever I have to draw an icon, I do so in Affinity Designer. If I need to do compositions, I do so in Affinity Photo. I love well designed things because it is my strong believe that these things make the lifes of the users easier. And better. If it is in the Affinity price range, I will buy Affinity Publisher, not only to support Serif’s great work but als because I'm sure it will fullfill my needs for designing documents. Initially, I collected the thoughts in this post to send them to Serif by mail but then I found that this Forum would be the better place to post it. It is an open secret that Serif also looked into the field of digital asset management. Apple having pulled the plug on Aperture, Adobe having killed the boxed version of Lightroom, I sense there is a void that many people want to be filled. I have high hopes in Serif’s solution. For me, a Lightroom and Aperture successor has to combine two important functions: Management of files on disk Non-destructive image manipulation function I hope that Serif’s solution will cover both: Editing as required by photographers (stripped down to their needs, not a complete Affinty Photo clone) combined with powerful metadata management. In this post, I'll focus on one specific part of metadata management: Faces. Lightroom’s faces support is alien. Faces are a kind of special keywords, but they are no real metadata class. Aperture was better in that it handled faces as a metadata class on its own. Still both tools did not get it right (in my opinion). Do you want to mark faces in images? I don’t. I want to mark people in the picture. Having a neural network that finds faces is a good start but it does not solve my requirement. Imagine you took pictures of a wedding. One of the picture is the bride walking down the aisle. We see her from behind. Her in a white dress, buttons perfectly lined up from the neck down. Flowers in the background. If you are thinking “faces”, you would not mark her in that image. Wouldn't you want to mark her? I surely would. So, here are a few things you might want to consider when implementing a “faces” metadata handling: You need to have a great import from Lightroom. This includes import of faces. The Aperture importer that Lightroom has is terrible, it does not know about faces, it simply imports them as keywords, loosing all position information. I wrote my own importer but I would prefer not to have to do that again for my next DAM. It's not about faces. It's about people. For some this might include animals. Think about someone that does tons of riding competitions. These people like to keep track of the horses, too. “People” might not be a perfect name but it is better than “faces”. Make your AI work on people, not faces. I know it's hard but todays machine learning knows to detect arms, legs, etc. Use that information. Stress the I in AI. Your AI detected my daughter with 95% confidence? Your AI sees a 51% similarity between the boy next to her and one of my colleages I have 5 images of but only 49% similarity with my son that is in 4000 pictures my daughter is in, too? It doesn't take too much intelligence to decide that the 51%-colleague should be 99%-son. Don’t handle images separately, use information gained from other images: Which persons tend to be in one image? There are lots of simple rules you could follow: One possible matching person has been confirmed in a picture taken a few minutes before or after? Guess who's this boy in the red sweater, who's the girl in the pink dress, I confirmed in 50 other pictures? If you detect the left arm with the same sweater in the picture taken a minute before, it is quite licely that it is the same person. Use the location data of images: 50% of all pictures of this person are within 100m of this picture's location - it's more likely that it is her than the other person you never took a picture of within 100km around that position. How likely is it that the same person is in one picture twice? Let aside framed pictures in the background and mirrors, if I label a person, use this information to reevaluate the confidence score of all other persons detected in the same image. If I have to add a person manually, don’t make me drag a rectangle around the face. Just let me click the person/face, then rerun your person detection AI with that information. If your AI was 30% confident there is a face and it gets told it is 100% a person, why not use the size information the AI had? Worst case? The rectangle is too big/small and I will have to resize it. 99% case: One click, person is detected correctly. Don’t make it a rectangle. Detect the outline. (See this paper - especially figure 5a/c) Let me repeat: Don't limit it to faces. People do not always look into the camera. I do tag pictures where you only see a hand or foot of a person. (Think about martial arts: Just a foot breaking a stone. I want to label that foot because I care who mastered it.) It's people, not keywords. Marking a person means that this person is visible in the image. Attaching a keyword means that this image is related to the keyword. (I tag all images that are related to one of my children with a keyword of their name. This will make it easy to export all images they might want to take when they move out. On the other hand, I want to have a simple way to search for images one of the children can be seen in.) So far for my thoughts on faces/people. I know I'm not the photo pro that uses Lightroom to make a living but given the price tags your other applications had, I guess lots of hobby or family shooters are looking in your direction right now. Bye, Daniel PS: Regarding the Lightroom import: Please do import the edits, too. I know it is not possible to match it 100% but 90% (or 75%) would be enough for my needs.
×