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

krbo

Members
  • Posts

    115
  • Joined

  • Last visited

Posts posted by krbo

  1. in addition: just tried to change square brackets shortcut with something else also using AltGr - nothing, no reaction on AltGr chars as shortcuts

    but everything is OK during text input, all AltGr chars are recognized in a text tool - []@{}\|€

     

    as this is an input device malfunction I think it requires immediate action and fix, as markingram wrotes in "why msix" post it should be easy to patch whole suite now?

    tnx for reading!

     

  2. On 11/14/2022 at 4:35 PM, MEB said:

    Hi @krbo, @Mft,
    You can change the shortcut for the Paint Brush Tool, Clone Brush and whatever tools you want in the Affinity Preferences, Shortcuts section. Set the first dropdown to the Persona you want to change the tool's shortcuts and the second to the specific tool you want to customise. The fields you want to change are Decrease and Increase Brush Size.

    hi,

    it's not a question of changing a shortcut, it's a question where they were last 6 years and where they still should be - after that period it's a muscle memory

     

    something is wrong with keyboard interpreting

     

    tnx for info!

     

  3. 54 minutes ago, LuNik700 said:

    Hi Patrick,
    could you please clearify whether the approach of just extracting the affinity-photo-2.0.0.msix to a folder of choice and after that just running photo.exe in the App subfolder is a valid solution in you eyes??? Are the any drawbacks doing so?

    In my option the solution with the batch starter is more complicated for people who are not so familiar with it and some application (like DXO Photo Lab) don't allow bat-files to be selected out of the box for exporting...

     

    Best regards
    Ludger


     

    I will try to answer this.
    Just extracting will work individualy for each app but we don't know are there any interdependencies between each app and windows (dll registration etc)
    What is sure is that no other Serif app will be aware of others (as they are just unpacked to a location you randomly choose) so things like "Studio Link" will not work.
    Some "windows like" updates may not work as apps are not where they should be.

    It's just a hack to give you more comfortable work with your 3rd party software before system solution is done, if any (I strongly beleive Serif will do something)

    Biggest problem is that Serif didn't perform wide customer public beta of version 2, all of this problems will be presented to them during that process.
    There's nothing catastrophic happening, everyone can stil work with v1.

  4. There's a little workaround in installing V2 anyone can try.

    You'll need a msix file and a free packer/unpacker like 7ZIP

    Install 7ZIP and download msix anywhere, right clik on it and instruct 7ZIP from a dropped menu to unpack it in a folder (it can be the deafult name as the msix file)
    After unpacking rename new map as you wish (Photo2) and move it wherever you wont, lets say to a previously prepared "C:\Program Files\Affinity"\  map

    Open "C:\Program Files\Affinity\Photo2\App" map - there is Photo.exe , start it, register it, make shortcut, connect with your 3rd party app...

    that's all - it works but can't be sure is everything ok, something missing or not , but it's easy to try and easy to delete

  5. 10 minutes ago, carl123 said:

    It's looking like the Haze Removal algorithm does not see any haze in the original image

    It only works after you have run some noise reduction on the image which makes it more blurry/hazy - then it sees some 😄

    and then if I reopen RAW as a new work it sees haze from the start

    as there were no other reports of this, let's call it a glitch and forget it for now 

  6. Thanks Ron!

    It was very late so I've tried to find out what happened and went straight to bed :)
    Just tested with few other RAWs and yes, it works!
    Again with original picture I've mentioned and it works!!!
    But I can still provoke it on afphoto, will try to attach it (300Mb) so switch off all layers except background one and try Dehaze - still doesn't work at me but pixel layer above is OK.

    maybe you can dig out something (cheap Nvidia 1030 here and latest drivers)


     

    399023403_amci1.afphoto

  7. May I suggest you to go back to a previous drivers release?
    Intel HD 620 drivers download
    It's a 27.20.100.9168 version - just install it over one you have.

    I'm suggesting this as I'm using HD 630 and latest drivers (9316) are terrible on Win10 20H2 (19042.867) - constantly after each restart repeats partial install and more importantly crashed Topaz AI plugins (some nasty OpenGL2.0 crash) 

    Reverting helped (I've tested that twice to be sure), maybe will do something for you also

     

  8. 1 hour ago, Fixx said:

    True, but required HTML/CSS is relatively simple and need next to none version handling for different platforms.

    precisely

    I will even suggest to concentrate on epub 2.0 leaving version 3 for some future goal as almost all e-readers are 2.0 (millions of Kindle/Kobo devices)

    Hiring authors of free epub software like Sigil editor or Calibre library/converter/editor will certainly speed up process of exporting HTML/CSS from simple text (epub 2 can't be complicated) 

     

     

  9. hi,

    my second PC with old Radeon HD5760 - Win7

    780 starts and dissapears after a "loading fonts" on a logo - crash not reported

     

    Win event says it's a .Net runtime error:

    Application: Photo.exe
    Framework Version: v4.0.30319
    Description: The process was terminated due to an unhandled exception.
    Exception Info: System.Management.ManagementException
       at System.Management.ManagementException.ThrowWithExtendedInfo(System.Management.ManagementStatus)
       at System.Management.ManagementObject.Initialize(Boolean)
       at System.Management.ManagementBaseObject.get_ClassName()
       at System.Management.ManagementClass.GetInstances(System.Management.EnumerationOptions)
       at Serif.Affinity.Application.LoadSystemInfoFromWmi()
       at Serif.Affinity.Application+<>c__DisplayClass64_0.<OnServicesInitialised>b__1()
       at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
       at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
       at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
       at System.Threading.ThreadHelper.ThreadStart()

     

    Dump file included

    767 works OK

     

    a3c7724f-5215-4c39-ab7a-89da93462f4e.dmp

  10. OK, new beta - 1.9.0.767, let's see are there any difference:

     

    - still opens RAW slower with OpenCL (4 to 6sec compared to little more then 1sec) and first RAW after beta start opens like without tone curve, then sits for two seconds more and shows correct picture - this does not repeat until AP is closed and reopened - added two screen grabs of flower to show this

    - fast zooming with mouse wheel is fixed - rendering is faster then witout OpenCL

    - my test aphoto (3 adjustments and 2 filters) exports to jpg slower then without OpenCL (46sec to 37sec)

    - tried to make a focus stack (example attached) - horrible, looong loading and "thinking" times during stack phases, crazy color stripe flasher during final render - bottom fifth of a picture missing (that black bar), strange color bleeding (red is non existent in object1510589277_Trubicamrak.JPG.d1030a07688f07854ad5d54163892acd.JPG)491470857_TrubicaOK.JPG.c01c4db60ebf05db3ebcb5080bf77d58.JPG

    369637452_tortelinlo.JPG.cfdd0e5181365b3e0abd47c75dff22d7.JPG

×
×
  • 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.