Jump to content
Our response time is longer than usual currently. We're working to answer users as quickly as possible and thank you for your continued patience.

Garden-User

Members
  • Posts

    39
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I mean they have there Reasons, but come on. They should explain it. I mean it is there decision to break compatibility with V1. Yeah and they should either use the Beta-Feature OR look what the competition makes: Make a Checkbox that says "Compatibility with V1" and then the NEW Features of V2 will be converted to a Pixel-Form so that V1 Users can open the File. For icing on the cake they can make it that V1 gets the Pixel-Form of it while V2 can still be Edit the new Feature. I mean Even now the Photoshop CC can export an psd-File all the way down to CS2...
  2. This is a joke right? What is so difficult? If an only V2 Feature is used, the flag for not opening in V1 will be set. If not then NOT. It is the same File-Type. They should change this to afphotov2 or something else because now you can BREAK your template files in the evaluation time.
  3. Hello, you can Run both Affinity Programms at the same Time. But keep in Mind, that any saved V2 File can only be opened in the V2. Even when you are not Using any of the new V2 Stuff. The File can NOT be opened in V1 in any way. To get this Function back, you must open the File in V2, copy everything and in V1 you must select "New from Clipboard" then you get the file. Save any V2 Files under a new Name or else you can´t open them with the V1 Version. Maybe this will get fixed in the near future.
  4. Ok but it should not happen, that Affinity 1 refuses to open the same file but with the only difference that the HSL color is -10.4 and not -12. I mean yes there may be more differences but then Affinity should have a Checkbox like Photoshop that says "Basic Compatibility with preview Versions of Affinity". This should also not happen, either it should not copy this filter or it should give you a Warning that you try to paste a non-compatible Filter. I simply mean, that the same Feature in Version 1 is the same in Version 2 and should work in both directions.
  5. Hello People, I think I found a critical Bug in the Photo 2 Application: We are currently Testing Affinity Photo 2. Since BOTH 1 and 2 use the same file Format we assumed, that they are compatible with each other. That is sadly not the Case. We have opened a afphoto file in Photo 2 and edit the HSL Color, what both 1 and 2 support, saved the file and tryed to Open it with Photo 1 expecting it to open just fine, because well NORMAL behavior. Nope We get the nice Error: "The file includes features from a later version of Affinity." WHY is there NO WARNING in Photo 2 that the file will not be usable in Version 1 even if you don´t use any of the new Features? This should NEVER ever happen. There should be either: A: Totally new file format so that you can´t render Affinity 1 Files useless. B: A Message in Affinity 2 when saving that says "This file includes features that are not compatible with Version 1. Do you wish to save under a new Name?" or maybe something similar (can be disabled in the options) C-> Let Affinity 1 open that File and let it open what it can read with a Warning. I mean I can open a Photoshop psd file and have edit functions so why not the same? Because FUN FACT, IF you copy the entire File (the Layers) in Affinity 2 and in Affinity 1 click on "New from Clipboard" ALL Layers will be copied and with full edit mode on them like they are on Affinity 2 even with the modified HSL Color. So there is clearly an Error here. Hope that this bug / error will get fixed soon and this Topic will then be useless
  6. The Fun part is, that your Adobe Product AND Affinity has the PANTONE Color usable. Adobe Creative Cloud Users must pay 15 $ per month for them or else they are gone including older Files. Those PANTONE Colors will be converted to black when you don´t have a subscription. I mean don´t get me wrong but Adobe does NOT reduce the Price on the sub but they cut a Feature? On Affinity... Well I have a payed Software that just works and does not need an Internet Connection. I think also that most of the critic here is, that also NEW Customers get the 40 % Discount. I mean why would you be angry about it? Yes you supported Affinity in V1, like us but please look at the Alternatives: - Adobe CC: 743,40 € per Year + 90 $ for the PANTONE Color - GIMP: No CMYK so no. - Corel Suite: The 2021 is the Buy one Version. The New Version is also subscription based. - Other Programs? Yeah exist but mostly subscription or they only have a "Photoshop" Clone, no Vector Program or Publisher. I mean from the Adobe CC yearly Subscription you can nearly get 7 times the Affinity Suite. YES Adobe offers more but 7 times more? Don´t think we are a "fanboy" here, because we are also frustrated at some thinks, like the lack of a good Camera Raw Plugin. But hey it will come.
  7. Is it just me or why do I don´t get the Problem here? I mean Adobe CS2 runs fine under Windows 10 and I will assume that Affinity 1 will also run fine under future Versions of Windows. Regarding Security: Critical Errors will still be fixed I assume but I don´t think there are any. Let´s think so: Thanks to Inflation the Affinity Suite is getting more expensive BUT we have a 40 % Discount for like what? Another 4-5 Years until Version 3 comes? The ROI is very very high here. You can get the Single-User Version for 120 € and you know what? for EVERY Platform. So you can run Photo on your Desktop Windows PC, on your Mac Laptop and your iPad without any additional costs. Yeah yeah not at the same time, but you have all 3 Programms on all 3 Platforms. And the BEST Part is: you pay ONCE and use them forever your Mac / iPad Support them, because let´s face it: On Windows there will always be a way to run old Apps. Now let´s compare the single User Price, 120 €, to the same Package from our lovely "friends" Adobe Affinity 2: 120 € purchase with Updates for X Years. Adobe CC: 61,95 € per Month = 743,40 € per Year. Stop paying = no Software. You own nothing. That alone means that after 2 MONTH of Adobe CC you have 1 FULL Affinity Package. But hey there is another Option: Use the Adobe CC MONTLY Plan for only 92,94 € per Month... Yes I love Adobe Photoshop... Ok I love the CameraRaw Plugin. But for that Price? Nope nope. For me current Affinity 1 Users should have the 40 % Discount forever like @iNfeRnO mentioned. But here is maybe a Problem with the Mac Store because I don´t know if that is Possible.
  8. Hello Lee D, thank you for the answer. I have checked the source files. They are all there. when I doubleclick on the file, the "afphoto" File will be opened. It looks like that Affinity Photo "forgets" to load the Image. Because when I export the "blurry" preview the picture is like it should be (sharp, crisp). I mean when I forcefully rename / move one linked file, Affinity tells me that when I open the File. It says "Missing Resource(s)". So it seems that Affinity checks the Resources and everything is fine but it don´t load them fully. I mean this bug is only in the Edit, when you export the Picture it is as it should be. Annoying bug in this file. Because our Template for our Online Shop with over 30+ Linked files does not have this bug (The difference are: The Template has some embedded Texts and Art. Size: 180 MB. Linked Files are on another Network Drive. The "Buggy" File (Size: 31 MB and no Texts / Art, just Linked Images) is located on the Same Network drive as the Source Files.)
  9. Hello People, We use Affinity Photo 1.10.5 with Windows 10 21H1. I have the Problem that I have created a File, 2000x2000 Pixel as a Template for our Online-Shop, our Partners etc. In this File I place the Affinity Files of our Products (Product Shots) and also the "Mood Pictures" / Atmosphere pictures. They are linked because I can Edit the Source Affinity File and the changes are applied to every File. So this works Perfect in our Front Page Template (180 MB) and this File contains mostly Linked Resources 30+. The Loadtime is longer, sure it needs to load every Resource. The new File, 2000x2000 Pixel Product Shots, will sadly load a lot faster (ok only 5 Linked Resources at the moment), because the Pictures are blurry. When I click on the Image I can open the original and it is sharp. But to get this Sharp Image in the new File, I must zoom in / out and the Picture is sharp. Hope this Bug will corrected. I assume that Affinity wants to load the File as fast as possible and large / big linked Resources will be stored with a small Resolution so Affinity can load the full Resource in the Background. I mean I know why Affinity does this, like 100 Resources with 150 MB each will make a huge load on the Network Traffic. But maybe add a Toggle that says "Load all Resources in the File at Full Resolution. WARNING: Will result in much longer Loadtimes and more Network Traffic."
  10. They are all stored on the NAS for easier Backup. Sure I will prepare the Sheet for you. Edit / Update: The Error get away when I link the images on my local PC (SATA SSD). Funny Thing is, that the "missing" File was not even the large one. Is is "only" 10 MB large and files like 50 MB are not reported missing. "Funny" is when you SEE the Picture in Question in the Preview, was missing, and Publisher still says "missing Resource". But hey good news: You can replicate the Error the following way: 1. Create a Publisher File with an Excel sheet linked 2. Place the Picture-Frames / Fields on the Publisher file 3. In the Excel Sheet link the Pictures to an Network-Share (Either \\nas\... or if mounted in Windows "H:\...") 4. The Linked Pictures are afphoto Files. Those Files contain Linked, NOT embedded, Images for Position correction. (They can be afphoto files or psd Files) 5. Save the Excel File. 6. Refresh the Publisher Data merge with Preview mode. 7. You should now see the Files and some of them should be marked missing in the Checklist. This will work. Our NAS is one from Synology and it is "slow" so only 50-80 MB/s read / write. But we don´t need more. Because the "Error" is not present in the export File (or when the files are local), I assume that there must be a "timeout" when Publisher checks the file.
  11. Yeah that is stange. The File is an Excel sheet not a csv File. The Pathes are all valid Widnows 10 Pathes. The "old" ones have pathes like "\\nas\folder\product\file.afphoto" and the new ones "J:\Folder\product\file.afphoto" But hey when the Export works I´m happy. Maybe this will be fixed in some later Patch.
  12. Yes you do understand me correctly. When the picture field is empty it will return a "0" in the Cell. But When I click on the missing Resource it points me to existing Pictures.
  13. Hello, I have now finished our new and fully modular Product Catalogue. It works with an Excel sheet that has every Information needed. Sadly Publisher can´t recognize an empty field. It is very bad, when you have a Listing. But you can also use another Method. But anyway. Here is my "Problem": In the Document that has the Data merge active there are no Errors. When I let Publisher create the whole thing it works but the Checklist gives me a huge List of "missing resource" errors. When I check the "manage resources" there are no Problems. Funny thing is, that the "missing resource" is there and Publisher can even open the file (there are all afphoto files). When I export the Catalogue to PDF it will warn be about the missing resources but when I ignore it and export it and check, everything is there and nothing is missing. Question: Has Publisher Problems to check for the resources? I mean the whole Excel sheet has, if fully loaded, 2350 Datas that needs to be read. Most of them are Text but 250 are Pictures (most of them 4k or 8k and in afphoto). Maybe there should be a longer delay to check if everything is there because this "Error" is simply not one.
  14. Sadly only complete manually. Affinity Photo can Read the dng File fine, but it needs some fine tuning. The White Balance must be corrected and the Temperature should be corrected if the Lights are not true White. An don´t change the Slider just down below it: Tint (Tönung in German). The Slider will only go to 50 % IF you change it by hand. The pre-defined 80 % are fine (but there should be an override to 100 % if wished). For the Lens Correction: No you can´t use the P20 Pro because the Sensor is not compatible. Other Corrections like Chromatic Aberration can be done. Keep in Mind that the 40 MP raw File of the P30 Pro needs some work to look really good. Lightning is the Key (low ISO!). And shoot in "Pro Mode" if you have focus Problems and adjust it by hand. For us it works good. We had an old Canon EOS 500D, yes it is 12 Years old, and the P30 Pro has the Advantage of the 40 MP. Sure The Sensor on the Canon is Huge but 15.1 MP is still "only" a 4770 x 3178 px Picure compared to 7296 x 5472 px. The size does not matter but when you correct Details it does matter. We have seen that the Canon "blurs" more and even with turned down ISO the Picture gets some Grain Effect. The P30 Pro has the Color "Problem" that you can correct in the development. Hope I could help you.
×
×
  • Create New...

Important Information

Please note there is currently a delay in replying to some post. See pinned thread in the Questions forum. These are the Terms of Use you will be asked to agree to if you join the forum. | 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.