afx

Hi NotMyFault, yes, you are correct. But that is not the point. In your result you show an outer and an inner frame. I expect the outer frame, but often I get the inner one. Of course, the outer frame would need some cloning work, but it would not cut off essential parts. But depending on the mood of Affinity I sometimes get the outer and sometimes the inner frame with the same image set and settings. cheers afx

Hi, sorry for being such a laggard. Here are the files: http://afximages.com/tmp/Set1.zip In the end, they are not worth the trouble, I would cone myself to death with them, but they show the issue nicely. cheers afx

Yes, I also have crashes on the big box with the Nvidia, but as the same workflow crashes on the Laptop with the Intel GPU, me thinks this is a different issue. cheers afx

As I wrote above, this is an Intel 620GPU, not Nvidia. cheers afx

Hi Timo, in this case it is animated GIFs, silly things like yawning or playing dogs. I have done a few so far and perspective never worked, it distorts images. What I absolutely do not understand is why Affinitys behavior is not deterministic. Two stack generations one after the other with completely identical settings deliver different results. This is usually a bug indicator. cheers afx

Both results were generated from the same image set with the same options, that what makes it so puzzling. The result is not consistent. The second one is actually what I want as it is perfectly aligned (I am too stupid to hold a camera straight...), the first one is utter rubbish and unusable as Affinity crops away way too much. On the second the alignment is perfect, I just need to clean up the outside mess and provide a common crop afterwards. cheers afx

Hi, I am using 1.9.2.1035 on Windows. Sometimes when I start a new stack it is cropped tight other times it is just aligned. I use the "scale, rotate and translate" option. This is how cropped looks (with all layers active): If the crop where usable, I would not worry, but it cuts of important parts. This is how aligned looks (with all layers active): In both cases I used the same settings for the stack creation. So am I missing some setting in the background or is this a bug? thx afx

Wow, never ever would I have expected someone calling me polite

Ok, my error. The import button in Macros did not get me a file browser, so I thought I had to rename it to macros and try the library way. Once I had a macro recorded, I also could load the file. The mouse selection is puzzling, but helpful I'll try to recreate manually. Yup, that worked!!! thx afx

Thanks, but I get an error loading it: Unexpected macro format. How do you get that Set current selection into the macro? I thought I need a key for that? thx afx

Thanks, but as the Windows version has no keyboard command to advance to the next layer, the macro solution seems impossible. cheers afx

Yes please. Absolutely needed to work efficiently with stacks and exported Slices. The current way is utterly tedious and time consuming. cheers afx

Yes, it works exactly that way on the ThinkPad. So why not on my big box earlier today? I think I know. The region has to be defined on the source. Using a region that was defined on the target does not work. But I need to define it on the source to make it fit exactly. thx! afx

Hmm, looks like I am missing something, I do not get anything copied.

Thx! That works, especially as the copied layer ends on top, I just need to hit the hotkey.