Jump to content

Christoph Müller

  • Posts

  • Joined

  • Last visited

Recent Profile Visitors

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

  1. Hi, If I have a picture frame with a picture in it and turn on Lock Children and drag or resize the picture frame itself with the mouse, the picture frame jerks when I move it. Before 1.10 this worked smoothly. Greetings, Christoph
  2. In my opinion, it should not make any difference whether I really convert a text to upper case letters, in which case the stylistic set "German Capital Sharp S" works as expected, or whether I use the "All Caps" button to only display a text in upper case letters. The result for the display is the same and should behave the same, right? Or asked the other way round, what reason should there be for it to behave differently?
  3. Hi Sean P, I have uploaded something for you. But please remove it after you have tried it out. Greetings, Christoph
  4. See the screenshot of my initial post. I pressed the TT-Button (All Caps) in typography settings of the text.
  5. I am not sure. I still think it's a bug in Affinity. On the unicode.org page there is actually an FAQ article on this topic: https://unicode.org/faq/casemap_charprop.html#11 Briefly, it says that in German it is historically the case that a small sharp S is converted into a double capital S. That's why it's the standard in Unicode. But it also says that there may be the alternative of converting the small sharp S into a real capital sharp S. In the DIN font, the character "U+1E9E ẞ LATIN CAPITAL LETTER SHARP S" is defined as "SS" by default. Accordingly, converting to uppercase in Affinity Designer from a "U+00DF ß LATIN SMALL LETTER SHARP S" to a "U+1E9E ẞ LATIN CAPITAL LETTER SHARP S" works correctly. If I enter "U+1E9E ẞ LATIN CAPITAL LETTER SHARP S" directly, "SS" is also displayed. This is also correct. But now comes where I think the bug is: Activating the stylistic set "German Capital Sharp S" basically does nothing other than switch an alternative appearance of the character "U+1E9E ẞ LATIN CAPITAL LETTER SHARP S" to the real capital sharp S (ẞ). Thus, whenever a "U+1E9E ẞ LATIN CAPITAL LETTER SHARP S" is displayed with the stylistic set "German Capital Sharp S" activated, Affinity Designer should always display a real capital sharp S (ẞ). It should not matter whether the "U+1E9E ẞ LATIN CAPITAL LETTER SHARP S" was entered manually or was created by a conversion to capital letters. However, it only works when "U+1E9E ẞ LATIN CAPITAL LETTER SHARP S" is entered directly. When converting a lowercase sharp S to uppercase, "SS" is still displayed. Accordingly, I think it is a bug that the stylistic set "German Capital Sharp S" is not applied after converting to capital letters. Possibly this also applies to all stylistic sets. Greetings, Christoph
  6. Hi, Unfortunately I am not allowed to share the font, because we licensed it. Greetings, Christoph
  7. Hi, If I enter a small letter sharp S (ß) and selecting the "All Caps" option in Affinity Designer or Publisher it gets converted into two capital letter S (SS). This is absolutely correct. But nothing changes if I choose the Stylistic Set "German Capital Sharp S", that my font supports. The small letter sharp S (ß) stays a double S (SS). Only if I enter the Capital Sharp S as unicode char directly (ẞ) and turn on the Stylistic Set "German Capital Sharp S" it is even displayed in Affinity and also stays as a Capital Sharp S with "All Caps" on. This is a bit strange. In my opinion with the All Caps option on, Affinity should convert a small letter sharp S into two SS if the option Stylistic Set "German Capital Sharp S" is not set and into a German Capital Sharp S if the Stylistic Set is set. Greetings, Christoph
  8. Hi, On my iMac Pro, since Affinity Photo version 1.9, the brush preview lags badly behind the circle cursor. I have Retina rendering set to "High quality". When I set it to "Automatic", it's okay. On 1.8.5 with "High quality" it was nearly the same performance as setting it in 1.9 to "Automatic". Greetings, Christoph
  9. Hi, I am a professional photographer and sometimes use Affinity Photo for RAW development. But unfortunately RAW development of multiple files is a big weakness of Affinity Photo. I know there are many requests for a complete DAM. But from my point of view, it actually doesn't take that much effort for Affinity Photo to be a very good RAW developer. For example, I prefer to manage my images in the macOS Finder. I don't like photo databases. In the Finder I can use tags and folders and search for tags. So I hardly need a DAM to organize pictures. But I would like to develop multiple images with Affinity Photo. There should be the possibility to open multiple RAWs and display them in an overview. The one or more selected RAWs can be edited together using the sliders. There needs to be an easy way to transfer RAW settings. Single and all settings. Further it would be good if the RAW development settings are not gone after developing. I often change RAW parameters again afterwards. Currently, with Affinity Photo, when you reopen a RAW image, you always have to start from scratch. It would be easy to save the RAW parameters in a parallel file. But what bothers me most about the typical RAW development process in all programs is that an image is developed and then when you want to apply further processing to the image, where an image editing program like Affinity Photo is needed, a pixel copy is created from the developed RAW image that is no longer connected to the RAW image. Here is always a hard cut. Subsequent changes to the RAW parameters no longer affect this pixel copy. Further, the Affinity Photo format is also not supported in many DAMs and is often not even displayed. Suggestion of a RAW layer That's why I would find it most awesome if a special RAW layer is created in Affinity Photo after developing a RAW image. With this layer you can do everything you can do with a pixel layer. Live effects, masks, inpainting brush.I can change this RAW layer with all the development parameters later. The new development parameters will immediately affect the image. It is also conceivable to have more than one RAW layer with different parameters for different development variants. I can also make parameter changes or transfer RAW settings to several marked RAW images in the overview, which then affects this layer. Each of these RAW images can be saved normally as an *.afphoto file. The original RAW could also be embedded in the Affinity file. The ability to have multiple RAW layers in one .afphoto file would also open the possibility for Panorama, Stack, HDR Merge and Focus Stacking to be based on the actual RAW files. So one could select the RAW layer of a part of the panorama and restore the highlights of it for example. That would be really extremely powerful! And actually not so particularly complex to develop. Wish you all the best,Christoph
  10. I am relatively default macOS. The only software that hooks a bit more into the system is VMWare Fusion and Wacom Table Driver. But I also went through completely reinstalling macOS and the first thing I tried before installing any other stuff was testing Affinity Photo and it did not make any difference in performance. Maybe some Serif employee could say something about this? What would be the best Apple machine for Affinity Photo and Affinity Designer?
  11. Oh you are right. I don't know why. This must be a problem of Pica's website. But I have now uploaded the PDF to my post. This should work now 🙂 Pica-Marker_D-GB-F_Katalog_2020_Web.pdf
  12. Hmmm.. In my case it works now. The link before was also a Access denied for me. Maybe try entering the url: https://www.pica-marker.com/de/turnjsmagazine/pica-katalog
  • 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.