Asser82
-
Posts
141 -
Joined
-
Last visited
Posts posted by Asser82
-
-
Thank you for your answer, but my problem is to cut for selecting an half of the picture in the diagonal.
Diagonal, so that you have two triangles afterwards?
-
Here it is told that there should be no diffrence:
https://forum.affinity.serif.com/index.php?/topic/34079-aphoto-release-15154/
But on the other hand it is reported, that it starts up much faster, see thread above and here:
https://forum.affinity.serif.com/index.php?/topic/34090-ap-151-release-startup-time/
-
Is the file going to be inspected? A statement is much appreciated.
-
@Mark: To round it up
I have produced here a (2x2) pixel 8 bit afphoto file, without history and snapshots. It is 7,23 MB now. But I could produce any size on those 4 pixels:
-
So it is 4500x6000 points, with 4x1 Byte (A, R, G, B ) per point. So without any sort of compression it is 108,000,000 Bytes / 1024 = 105,468 KB
What is stored in the other 1.1 GB if there is only one layer and no history neither snapshots?
Btw. did you try to delete all snapshots? I mean, it never helped me, but perhaps it works in your case. Check your View -> Studio -> Snapshots panel.
-
in computer science the relation between size and performance can go in different directions. on the one hand you can get slower if you need to traverse large data sets. on the other hand you can get faster if you can cache calculation results, so that you do not need to recalculate.
how many dots are there per inch and how many bits per channel?
-
Hmm,
0x80004003 means E_POINTER = invalid pointer. Two possibilities:
1) You have broken or missing dlls somewhere so that a reference cannot be resolved
2) Affinity uses an interface into native code like CLI and trys to call methods which are not there.
Is it reproducible or a "sometimes bug"?
-
issue has been reported in other threads, the obvious problem of steadily growing file size has never been confirmed. It does NOT help to clear snapshots and history. Even if you open a 16bit tiff file, save it as afphoto and convert it to 8bit, the size is growing, instead of becoming half as big.
The only thing which might help: export it as bitmap and create a new afphoto file from it.
see: https://forum.affinity.serif.com/index.php?/topic/33262-afphoto-files-are-getting-bigger-and-bigger/
-
Typical problem with UpdateSourceTrigger = PropertyChanged. We have similar scenarios in our tool, there we force an explicit binding source update on the focused element before the relevant commands are executed, to not make the user think.
-
Arghh. I like the software but my god i've never used anything that crashes so often. I installed the .51 beta because i was getting the crashes whenever i pressed help (as well as a lot of other random crashes). I've just been working for 20 mins and lost it due to another random crash. I will install the .52 beta now but this is really unacceptable how unstable this software is.... Hope it gets better.
Hi,
there were other posts about crashing too often. The problem there was solved by reducing the amount of memory the software is allowed to use in the preferences. I think, he had only 4GB of ram or so and it helped to reduce the threshold to 3GB in the preferences. Try this out.
-
Hi,
for those of you, who want to read Affinity Photo for Windows Help on your smartphone/tablet sitting on the couch and drinking tea, here is the instruction how I achieved it. After loosing hours trying to convert the help to epub with poor results, my way to go now is:
1) Create a directory HELP for example on your desktop
2) To HELP copy from <Affinity Install Directory>\PhotoHelp\Contents\Resources:
- <Your Language>.lproj
- shared
3) In HELP\<Your language>.lproj\scripts directory replace files by the files in the ZIP archive.
4) Upload the HELP directory to your device via DropBox or comparable
5) On your device open HELP\<Your language>.lproj\index.html with your browser
Chrome works very good here. The topic menu is in the top left corner.
The script changes basically fixed the help to display Windows specific parts and Shortkeys instead of trying to derive the platform from the environment it runs in. Otherwise a MAC help would be displayed.
-
Thank you! As a Mac user, I was only too happy to switch from PE Elements (8) to Affinity, but one thing PE did have was an extensive selection of crop shapes. I have to confess I only got around to using a couple of them before I made the switch to Affinity, but now that I actually understand layers, the possibilities are quite intriguing.
Hmm,
why aren't you using the pen tool to create the shapes you need on a crop layer and put the image to crop inisde that crop layer? Just search for "Layer clipping" in affinity help.
-
Hi MEB,
I looked into the ebook and the problem with it is, that the modifier keys and mouse buttons are broken there. The reason for this is that the Help contains OS dependent parts, which are resolved through java script, which do not seem to work correctly in the epub. Yesterday I created my own epub through calibre, which has a better quality looked in calibre at the PC. But if I move it to android, the readers there are still not capable to display these parts.
I always read my books and manuals on mobile devices on the couch. So if it is to complicated to create some mobile formats, would it then be possible to put the help online? I mean, it is a HTML help already. So put it on a server, provide some links, and let google know about it. This way I can read it in firefox or chrome and on the other hand Affinity gets more publicity through google results. If someone searches for "layer mask", Affinity would be much more represented. It is like microsoft does it with its MSDN help.
At the top right corner or so, there could be two dropdowns for language and OS. This way I could read the german help for windows on android or ios.
Here some Adobe online help examples:
-
If it is a bug, try to find a reproducible way for this. Otherwise the developers cannot do anything about it, if they or the testers cannot reproduce it after trying for some time.
More information like available layers, selections, brush settings would certainly help also.
-
Hi Sean and Harry,
yes I thought so, see title. Sean as you say, it feels wrong and it does not allow to restore the complete selection in certain situations. Thx for reporting it to the development.
-
From user's perspective the commands "Mask Layer" <-> "Selection From Layer" should be symmetrical. If I can draw that selection, I want it to be restored.
-
Hi,
there seem to be a bug:
1) File-> New
2) Add Pixel Layer
3) Elliptical Marquee Tool -> Drag Eliipse
4) Mask Layer
5) Deselect (Ctrl+D)
6) Ctrl+Left Click on Layer Mask
=> History shows "Selection From Layer" but no selection appears.
Now:
1) File-> New
2) Add Pixel Layer
4) Paint brush tool -> Draw a curve
3) Elliptical Marquee Tool -> Drag Eliipse partially overlapping the curve
4) Mask Layer
5) Deselect (Ctrl+D)
6) Ctrl+Left Click on Layer Mask
=> The created selection consists of the intersection of the former mask with the created pixels of the pixel layer.
-
Btw. rotation like in the "Option1.png" seems to be fixed in Beta 1.5.1.52. Problem with the thirds overlay still persists.
-
-
Because there is no reaction so far, it would be something to start with, if it just could be possible to create a selection from an available mask. Is that possible?
Then I would ignore the "Edit Mask" command and use:
1) Create selection from mask
2) Quick mask
3) Mask layer
4) Delete old mask
-
Hey,
I wanted to propose a symmetric architecture for selection and mask handling. Today I am missing the following things:
1) Once a layer mask is created from a global selection, I cannot overwrite the mask through a new global selection
2) If I have a layer mask, I found no way to convert the mask to a global selection
3) I have found no way to display a layer mask as a red overlay like the one displayed in refine mask or in quick mask mode.
4) There are some smaller inconsistencies: Refine is available in all selection toolbars except the flood selection toolbar. The button tooltip for quick mask is "Toggle Quick Mask [Q]", where the menu displays a "Edit Selection As Layer" command without a shortcut.
Why can I create more than one layer mask for a pixel layer, how are they combined? What is the use case?
The whole thing feels kind of asymmetric. So here is an architecture which would improve my workflow and my understanding where I am currently in the editing process (see screenshot). There are no dead ends:
- A layer mask can be replaced through a new selection
- A selection can be restored from a layer mask
- A layer mask can be edited and refined as quick mask (with different overlay modes)
- The context of the quick mask mode/ refine mode is clear, so no output combo box is needed in the refine dialog
- It is possible to enter quick mask mode from refine mode, even if the user selected refine mask/selection in the first place
This way a global selection becomes a temporary mask template which is not applied to a content layer. What do you think about it?
-
Hey,
move as you wish. Would just be happy if your/my tool is improved.
-
Hey Chris,
what do you mean with "image open". I have created a new document, hence an image is open. Or do you mean a floated "placed" image? Then I do not understand what the rotation cursor outside the crop box should tell me.
From Lightroom I am used to rotate/move the background under the crop rectangle, instead of rotating/moving the crop rectangle. Because I do not have any further layers other than the background layer, I have expected that the background layer is rotated under the crop rectangle. I hope that Adobe does not have a patent for it, but it would be nice, if the crop rectangle could optionally size itself to remove the transparent areas automatically. I have done some screenshots. -
I think you forgot to press the 'Attach This File' button. ;)
Thx
No idea any more ... Painting problem
in Pre-V2 Archive of Affinity on Desktop Questions (macOS and Windows)
Posted
I would try to move the pixel layer on top of the stack, just to test, that the adjustment layers are not applied.