Jump to content
You must now use your email address to sign in [click for more info] ×

ErikA310

Members
  • Posts

    14
  • Joined

  • Last visited

  1. Thanx @Hangman@walt.farrell, for pointing out my mistakes with respect to unit conversion and positioning/alignment. After correction this looks much better (see Zoom3.png). Nevertheless the zoom issue still persists, or is this also my mistake/misunderstanding of the app's behaviour? At some level of zooming in the stroke is not painted as expected. Please refer to attachment Zoom4. The glitch is also showing some variance. Zooming in. via cmd+ and zooming out via cmd- does not necessarily mean. Glitch visible, glitch invisible. Sometimes I have to zoom out two times to get the 'correct' visual representation back. Any idea about this? Thank you and best regards, Erik
  2. Good morning, I have some issue with stroke precision and and stroke display when zooming in. I have a (rounded) rectangle positioned on y=5mm and specified 6mm inner aligned stroke (calculated by app to 17.01pt). Calculating back from pt to mm this computes to 6,00075mm. So the stroke should end at 11.00075mm. Looking at attached image Zoom1 you will find that the end is rather displayed at 11.05mm instead. I assume there is some rounding issue. When you further zoom in either the calculation is showing a different issue or a redraw problem, please see Zoom2.png. Shape ends now above the 11mm guide Can you please have a look? Thanks and best regards, Erik [MacBook Pro M1 Max 16", Metal enabled, Sonoma 14.0]
  3. Here is also a replay of my measurements Hardware changes: None, Software changes: AP 2.0.0 MacOS Ventura 13.0.1 (Converstion to text format is attached as well AP 2.0.0 Benchmark.txt)
  4. Contributing again from Apple universe. Macbook Pro 16" 2ec 8pc CPU; 32c GPU; 32GB (AP 1.10.4, MacOS Monterey 12.1)
  5. I have noticed the same on my MacBook Pro 16" M1 Max (2ec, 8pc, 32c GPU, 32GB); MacOS Monterey 12.1; AP 1.10.4. All files where read and written from and to the internal SSD. The macro I'm applying consists of 9 steps. Setting the units to mm, Document resizing (lancos 3, separable), setting the document margins and adding/moving 3 guides. It looks like that only 2 performance cores are fully utilized during the execution of the batch job. All other cores and GPU only show minor utilization. I added two screenshots, 'Before' and 'During' the processing. 'Hardware acceleration' in 'Performance' settings were check marked (Apple M1 Max (Metal)) as well as 'Parallel processing' was enabled in the batch job definition. Not sure if the behaviour is expected or if it is rather an issue/bug.
  6. Sorry @Chris B. I missed your request in your last reply. I don't know exactly what type of screenshot would give you the right overview in DiskUtility; please let me know. Instead I will share already a view using the System Information view. CRBS/Data/Developer are partitions on the external drive (connected via USB 3.1 Gen 1). System HD is the internal SSD with 2 Logical Volumes (System HD - Data and High Sierra) Regards, Erik
  7. Thank you for the recording Chris B! This is comparable to what I do, but with an external drive with 3 logical volumes. Please let me know what you would require in terms of more technical details for the exchange with the dev team. Type of connection, Paritioning info... jada jada. Should I record how it looks like on my end and share? Considering Old Bruce's input... is it possible for me/you to change the topic of this thread? Best regards, Erik
  8. Yes. I do have an external drive partitioned into 3 logical volumes separating regular documents, software development projects and one with a local build and integration infrastructure. It ia a 1TB m2 samsung ssd in an icybox exernal case IB-1817M-C31. Fast enough for my needs and no RAID needed.
  9. Hi Chris B, yes. The app is installed via MacOS App Store into main drive of my Mac. Data/Images are only stored on an external drive. Hmm... still not sure how to apply this correctly. It only works if I select a location. And Affinity Photo even looses the authorization between two session. If I close and re-open I have to authorize the same location/volume again. That is pretty strange. Cheers, Erik
  10. @Chris B I just performed a retest, failed: Affinity Photo is not listed at all in the Security & Privacy > Privacy preference panel (Files/Folder | Full disk access) Affinity Photo is installed via Mac OS App Store Selected the images from the source location Selected 'Output' to be 'Save into original location' Used "Authorize..." and selected the 'logical' volume on my external drive, which hosts the files Button 'OK' is not being enabled Not sure how to authorise the entire HDD... if it is split up into 3 logical drives.
  11. Thx. I'm aware of the button. If the label is (placed) correct it manages only the authorization for the output directory. One info might be missing. I wanted to use the Output option 'Save into original location'. With this option set I used the Authorize... button and specified the directoy where the files are coming from and should be stored in. This didn't help. So, after playing around, I found a workaround. In Output section I set 'Save into: <directory>'. I select the same directory from where the files are coming as the output directory. For the sake of completeness I used 'Authorize...' on the output directory 'OK' button becomes enabled and the batch job could be run. It still sounds like a glitch/bug to me that the 'Save into original location' does not enable the 'OK'. Do I have to file this officially as a bug or will someone from support/devs will pick this from here? Thx and best regards, Erik
  12. Yepp... I'm on MacOS (11.6). I actually authorized Affinity Photo to have access to the whole (ext) drive. Thanks for the heads-up. Will try again and experiment with 'authorization' again.
  13. Hi there, I'm trying to apply a macro to a set of PNG files. Unfortunately, even though selectable in the file selector, the wizard will not enable the OK button if I select a set of PNG files. The Affinity Photo Help does not list any limitations wrt the supported file formats. So I'm asking into the round, is PNG not supported as file input for batch jobs, is it a known, current limitation or even a bug? Or is the user the problem Any help is appreciated, Thx and best regards, Erik
×
×
  • Create New...

Important Information

Terms of Use | 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.