krbo
-
Posts
116 -
Joined
-
Last visited
Posts posted by krbo
-
-
-
just for an info:
as a Topaz Photo AI user I installed yesterday the latest version, one of changes was "latest libraw"
and yes, with that libraw version Topaz reads any RAW from newer cameras, tested GH6, S5II and even my fresh G9II (2 months since release) works OK
but it's not a free public update
-
-
sorry @Dwentzel228 to inform you but we are very far from using our cameras natively in AP (I have a new Lumix G9II)
Strangely but Serif decided to support RAWs by using some free product from the net and LibRaw policy of upgrading for free is very, very relaxed - new versions with new cameras are released from year and a half to a up to a three years period (info you can find on www.libraw.org).
Since latest LibRaw version were released at december 2022. we are far away from a new one.
Can it be different? Probably as LibRaw has a level of support with early access to new features but that is not free one (your camera is already supported in LibRaw's commercial products, mine is too new yet)
So we can forget about editing RAW in Affinity Photo for a long time. -
argh - searched before I wrote, not saw - now with bug tag I see previous one!
-
Noticed this few days ago.
Standard File Open defaults to "All documents" and that is OK but "Add" dialog in "New batch job" defaults only to Affinity sidecars ("Affinity files" for photo, publisher and designer) no any other file format and I must change it every time to "All documents" to load raw, jpg, tiff...
I'm considering it as a bug, please revert it to "All documents" -
I must confess, being dozen of times in shortcuts settings of v2 , I never, ever saw "Apply to All" checkmark there before you mentioned it!
Some brushes don't react well (no live size change until AltGr is released off) but it is a great help!
-
from your workflow you woulnd't be affected even if AP stops to develop any RAW format 😀
yes, Adobe already done everything to support my next camera from ACR, Photoshop, Lightroom to DNG converter. Three weeks before delivery even starts.it's sad my favorite editor will have it after a year or two or more...
-
8 hours ago, AlainP said:
Why don't you just remap it like I've been doing using a French Canadian Kbd.
Settings-Shortcuts-Paint Brush Tool: I just set it to the brackets I see on my keyboard, it inserts other characters but it works.
Some of them I do, but just try to count all types of brushes and multiply it by 4 shortcuts for each one!
If the brushes were grouped so you can fix them all at once it will be almost painless
And then go to Designer and finish with Publisher - square brackets are all over!and 2.2 update were nasty one - it deletes all my remapped shortcuts and left blank entry fields instead
-
Recently this becomes hot topic for me and it looks I'll be forced to say goodbye to AP after being a user and supporter from first Windows beta version.
Why?
I'll soon buy (within a 2 months) a new camera - Lumix DC-G9II and having a new sensor it's RAW are not readable by AP.
Many of us knows that Serif relies on free LibRaw library to support various RAW formats but problem lies in that libraw is free, done by enthusiasts for no money so they couldn't care less to include new formats as soon as possible. If you check their web site you may conclude that it takes up to two years to add "new" camera.
This is totally unacceptable for a product I bought and paid. It's OK when a free app relies on a free product but something commercial???What if LibRaw team says "it's enough, bye people!" ???
Serif, you are shooting your leg!
No, I will not use Adobe DNG converter or any other app for a years until my camera is natively supported!
For example latest Panasonic m43 camera was GH6 launched 22.02.2022. and it's RAW is still not supported so I see what to expect.
(and recently I saw a question what about Sony A6700 support?)
Something should be changed or AP will become known as "nice one for several years old cameras"
oh, would it be useful to mention that LR Classic v13 (and Camera RAW 16) already have RAW support for my new, not even on the market, camera?
I really, really don't want to drop on AP but...
Any thoughts from other users, Serif ???
- Bit Disappointed and Tawny
-
2
-
A bug named AFP-5878 mentioned many times and introduced in v2 is still not fixed, no one outside UK/US keyboard users can use square brackets for brush size control.
And there's a novelty in 2.2 - even not fixing this, Serif added more shortcuts with square brackets.
trivia: out of 28 EU union countries I think only Ireland is using UK/US keyboard
and no, there is no option to replace zillion brushes with 4 shortcuts each to something else in every Serif software (it's not working in Designer and Publisher also)
I'm speechless!
-
there were changes, first betas were completely unresponsive to AltGr so this is a big improvement for me
and now could you explain me when bugs shoud be reported?
during actual work on a code (a beta phase) or after another release when they are left unfixed version after version?
Serif does not publish short, frequent patches so from 2.0 to 2.2 Photo does not correctly interpret input devices, a basic for using any software (never tested rest of apps, have them all). For how many months this is not fixed? Are there separate developer teams for betas and product releases?
Please be real, since 2.0 this is not working for a myriad of users, what shall we do?
-
Hello,
After a very long time during wich we with AltGr key for square bracket were not able to use them for changing brush sizes there is a new situation in first release candidate.
From the box it is still not working but after going to setting shortcuts and changing each [ and ] in the field with same keystroke which it registers AltGR+F and AltGr+G - then it finally works!!!But is very tedious process as there are myriads of brushes in AP!
(not just sizes, it's also brush hardness which should be changed in the same manner)
I've tested several brushes from the ribbon tool left, looks well so far only Clone brush is strange - it does not show size change until AltGr key is unreleased so it's not so easy to set correct size.
I'm hoping that this problem will have more work and fixes until RC2 so we don't have to change each shortcut -
Whatever you do with welcomed additional keyboard brush shortcuts you didn't fixed bug from the beginning for non US/UK keyboard users - interpretation of AltGr so a lot of us with extended characters keyboards can't use square brackets.
Since start of 2.0 it is reporting as big bug and yet no fix in basic area - correct input device interpreting, basic core us software usage
Now I'm starting to think this is deliberate - is it?
-
I really would like to see finally fixed bug with AltGr handling disabling me to use square brackets for brush sizes.
2.0 - 2.1 - 2.2 no change!
thank you!
-
Hi,
sad to report that all brushes sizes still can't be changed with square brackets for us who use AltGr keyboards/languages to access them
Win10 EXE version (the same is with MSIX beta)
(typing a text is OK, brackets are there) -
Beta 2.1 - no change in Portraiture 4 plugin problem.
-
4 hours ago, Pyanepsion said:
😉You will find that it is easier and more consistent to use arrows than open and closed brackets.
hm, will try, you may be right
-
17 hours ago, Patrick Connor said:
Thanks, but the only issues addressed in 2.1.0.1706 are already listed in the post pinned at the top of the forum. There is no need to tell us if something that is not listed is still not fixed. This forum is for reporting bugs that affect the beta but not the release build or to tell us the things we have listed as fixed aren't fixed after all, as your problem is also true of the release build I would politely ask that we keep this forum for new beta specific bugs only.
OK, I was under a wrong impression that all bugs slipped somehow to a new version are qualified to be mentioned so we can have v2.1 as clean as possible.
16 hours ago, Pyanepsion said:Hello @krbo,
However, a workaround is to simply replace the brackets ‘[’ and ‘]’ with one of the 4 arrows in Preference/Shortcuts.
I hope this solution will be useful to you.
yes, it's clear a shortcut can be changed, thanks for pointing, but after a seven years of gaining a muscle memory with some of them it's a real pain. And it's not just one or two brushes - it's dozens of them!
-
Despite many reports, keyboard shortcuts obtained with AltGr still not interpreted correctly so any brush size (except Paint brush!!) can't be changed with square brackets.
-
Just made a test to grab some screens.
This time 50 bmp pictures @50Mb each
Just loading them as sources in Photo:
V2 tooks 7 minutes
V1 tooks 4 minutes (it will be faster but I restarted PC to clear caches and that's why is Eset antivirus hooked to each bmp (ekrn.exe))
and now look screenshots of resource monitor while Photo is loading them
V2 opens just 4 at a time while V1 more then ten. Now compare reading speeds: V2 maxed shortly up to 6Mbit/s while V1 exceeds 15Mbit/s with some instances of photo.exe
-
problem is too low resources (file handles/workers/threads at once) used by V2 in reading files from disk.
I will try to make some screen grabs of resource monitor to better illustrate problem and post here later.
thanks for your efforts Chris!
-
latest Win10, latest V2, latest Nvidia drivers
Focus stacking in V2 is horribly slow compared to V1 - watched Task Manager and Resource Monitor trying to detect why is it so slow
First is disk reading - V2 starts less then 10 instances and read disk very slow - max at 5Mbit/s of only one picture, other threads are much slower - even 40k/sec
V1 starts more then 30 (maybe even 50) instances and reading goes up 20Mbit/s at fastest threads
180 50Mb BMP files V1 reads, I would dare to say, at least 10 times faster then V2 reads 120 of them
I estimate that just loading of 120 BMPs in V2 takes more then a half an hour and then alignment and merge starts (also with much less instances then V1)
In V2 alignment/merge processes are also slow - using also very small number of threads/instances of photo and system.
-
we have a lot of reports of erroneous work using square brackets for brush size adjustment, mostly for german keyboard but it's not working for any localized keyboard which uses right ALT key (called Alt Gr) to engage square brackets.
now I see it is fixed in 2.03 but only for paint brush, not for other brushes (clone, erase...) - still moving through layers instead of changing brush size
please fix that program wide
Future of AP for Windows with LibRaw?
in Feedback for the Affinity V2 Suite of Products
Posted
Yes, S5II RAW works with 2.4 beta, my G9II also (even now old G6) - all tested with sample files.