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

General Disarray

Members
  • Posts

    22
  • Joined

  • Last visited

Recent Profile Visitors

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

  1. Well, if you start your post with "Apparently, on Mac, Affinity apps simply offer the OS which file types they are capable of opening." that's one thing. But the way you started it, it seemed to me that you knew this to be a fact. But if you don't know this and are just guessing, then what is the point? Because if you're just guessing, it's no different than me saying that the installer associates the file extensions. The real problem is that software companies keep doing this over and over in both macOS and Windows. So I've had to waste a lot of accumulated time (sure, one time is not a problem, it's the sum of all the times for 30 years that I've had to do the same crap over and over) setting that file extension association to what it was before. And I had no error, perhaps Publisher can open RW2 just fine, I simply force quit it because I wasn't too happy that a raw file was opening with a program that is not even the right one for camera raw files. No, you got it backwards. Loukash said that it wasn't the installer that forced these associations, but it was macOS that was changing them because the installer was simply letting macOS know what file types it could open. Well, that's an easy fix. Take out of that plist all the extension that are photo related, like what are .jpg, .psd, .tiff etc, etc doing in that list??? Again, if you're working on a magazine for example in Publisher, and you want to bring in images, whether pixel or vector, you import them, use Place, drag and drop, whatever you want. But why is a camera raw format in that list? And that's all the time I have for this.
  2. Do you know this as an absolute fact? I'm not saying you're wrong, but the internet is full of people guessing things and posting them, that's why I'm asking. And if this is 100% accurate, then Serif has to change the installers so that in any case, if it tells the system what file types they're able to open, to not include file types that are obviously compressed, uncompressed or raw image formats in the Publisher installer. I'm familiar with a lot of the extensions in that list, but not all of them. But of the ones I'm familiar with, several of them are not for the Serif equivalent of Adobe InDesign. At the most, .ai, which should be associated with Designer unless you also have Illustrator (I don't), but the rest are for Photo. So Serif should take a lot of formats off that list in the Designer and Publisher installers, and maybe include them in the Photo one, but I wouldn't include most formats for even Photo, at least not the ones that open with Preview in a snap. Then if the user still wants to associate them with Photo, it's very easy. One of the main advantages of macOS as opposed to Windows is the ability to use Finder as a photo browsing app, which is fast even on older Macs and you can press the space bar for a quick preview, then if you want to learn more about the file, like DPI, dimensions, metadata, etc, you can click the Open in Preview button. Or you can just double click and open in Preview. So files that open in Preview should not be associated with any of the Affinity apps unless the user wants to, or like I said, offer a choice, a simple step in the installer listing all the file associations and a checkmark for those you want to associate with the app being installed.
  3. I love the Affinity Suite. Had it for about two years and recommend it to everyone. Affinity Photo is way better than Photoshop. Designer is way better than Illustrator. And I haven't used InDesign for decades but Publisher, for as little as I have used it, seems great. But Serif has this nasty, narcissistic habit that all software makers have: they override the OS's associations with their software. I don't get it. 30 years using computers, both Mac and PC, and still don't get it. Why does every software maker thinks their software is better than everybody else's? And why do they assume that if so far I was opening image files instantly in macOS Preview, now I want to wait several seconds looking at their icon bouncing up and down while their software opens??? Especially, if it's the wrong software for it. I found an old SD card, put it in my Mac, and it had a file with the RW2 extension. Those are photos from my Lumix G7 camera that I haven't used in ages. So I double click on it and preview doesn't open. Then I see that the icon for Affinity Publisher is bouncing up and down, up and down, up and down and I realize that the installer decided to associate itself with .RW2 files. That's extremely rude. So I force quit Publisher, because even on a Mac Studio Ultra M1 with an internal drive that tops at 7 GBps, the Affinity suite is slow to open, at least after a boot or reboot. Second time it's just a couple of seconds. But I force quit it, opened the file info, and setup RW2 files to associate with Preview as they should. Then if I want to edit that photo, all I have to do is right click and choose Affinity Photo from the menu. Which many times, I do. So please tell me why you think that I want to wait several seconds to open this photo, not even in the correct program in the suite, because a photo is supposed to open with the... with the... Photo app!!! Correct! Yes, you can open it in Publisher, and Designer too, doesn't mean that it's the right program to do so. Unless you're working on some document in those two apps and you need to import a photo. At least you could put a step during installation that asks the user for their choices on associations. Some installers have been doing that for at least 25 years. I remember installing Winamp in the late 90's and having a step that was about setting associations. Then why do you think that your software is the only one in the world and all files should open with it? And why do you not even associate them with the correct program? Even more, you have your own file type. It wouldn't occur to me to associate .afphoto files with Preview or Pixelmator Pro, which probably can't even open them anyway. There's a right program for every file type, and sometimes there are several, but it's up to the user to make that choice, not the software maker, except when it's their own file type, like .afphoto. Please stop being so narcissistic. Please stop changing file associations. Thank you.
  4. Yeah, that's the main problem for me. Apple used to have a very nice photo catalog program called Aperture, I don't know why the hell they stopped working in it. They kept working on Logic Pro X, Final Cut Pro X, Motion, Compressor, Pages, etc. Why kill Aperture? It's absurd. It could be another one of those apps you buy for $200 and then never pay for an update again.
  5. Well, I bought ON1 and I'll probably ask for the refund. I took some photos with my old DSLR, a Canon EOS 60D, so probably a lot less megapixels than new cameras, and just a few photos, less than 50 for a project my wife is working on. And it's slow as hell. So as soon as I get a chance I'm going to ask for a refund and then look for something better, whether it's free or more expensive, but something I can buy and not lose one day if I lose my job (which can happen to anyone at anytime) and can't afford the subscription anymore.
  6. I bought the Affinity suite back in December, and I love it. I use Photo all the time, and the other two every once in a while. I think this suite is far better than the Adobe products it competes against, especially Photoshop, which is a dinosaur that they keep slapping things on top of. I haven't paid for the Adobe Cloud subscription in years, although I use it often in my work laptop. And I definitely don't want to go back to pay for it. But while the Affinity suite does an excellent job replacing Photoshop, Illustrator and InDesign, the thing I'm having trouble finding a good replacement for is Lightroom Classic. Slow as it is, it's great for managing large amounts of photos, and to easily change settings for large batches. I hope Serif comes up with a good replacement in the near future, which I'm sure will be better than Lightroom, but in the meantime I wanted to get a feeling for what the rest of the Affinity community is using. I bought On1 Photo a couple of days ago. It's not bad, but it's kind of slow at times (on a Mac Studio Ultra, so nothing should be slow), and some menus look like all the commands are piled up with little space between them. On the other hand, it's only $100, while others are more expensive. The good thing is that you can return it within 30 days if you don't like it. So what are most people here using as far as a Lightroom alternative for large amounts of photos?
  7. So I had not included that in my post because it was already a bit long, but I had done the soft proofing. What I see on the screen when I apply that layer has nothing to do with the printed photo. Either Affinity Photo is sending the wrong gamma, or the printer driver is.
  8. Thanks Lee, but it says there those are profiles to be used with their PrintFab product, which costs $49. Definitely not going to pay more than these overpriced cartridges. This machine should give me a near perfect print without external software. I'll watch the video later, thanks!
  9. Few things in this world are more aggravating and frustrating than photo printing. If you don't do it all the time, you typically buy a new printer every few years, print a few useless prints until you find the right settings, and move on. Then years later that printer stops working, you buy another one, and here comes another set of wasted paper and ink, except that this time, it's the very expensive ink from Epson, so I want to put my hands around Joe Epson, shake him and tell him: "Stop ripping people off with this overpriced ink, damnit!!!" So my good old Canon Pixma MX922, which I bought for $80 in 2016 gave me many years of good photo and Blu-ray prints on cheap ink, but eventually gave me the B200 and decided to die. Since I still need disc printing, and that seems to be, along with discs, a thing of the past, I had to spend over $200 on one of the few remaining consumer printers with that ability, an Epson XP-7100, for which generic ink is sold but voids the warranty, so for the first year I'm forced to use their insanely expensive ink. And I wouldn't really mind a lot if at least the prints were excellent and very similar to what I see on the screen, obviously with the difference between photo paper and a self lit medium like a screen. But no, the printed photos have the gamma all messed up, or something else, but they look way darker. And I'm sure it's something that I did wrong, but the Canon always gave me decent prints if I did things this way. So I would like to show whoever's nice enough to help me and knows about this stuff, all the steps. This is a RAW CR2 from a Canon EOS 60D DSLR, as I see it when opened in Affinity Photo 2 (updated to the latest version): This is after having developed it in AFP, which as you know, opens in the Develop module when loading a RAW photo. I didn't do much to it, but this is what I ended with, and more or less what I would like to see in the printout. As you can see in the info pane at the bottom right, I converted it to the Epson XP-7100 Photo Glossy color profile to see on screen something as close as possible to the final print. This is how I setup the print options that matter to quality: When I print that, I get a photo that is much darker than the source. And not because I'm comparing a print to a screen, I've seen photo prints before with many printers and I know what the difference is supposed to be. So just to give you an idea, I scanned the printed photo, and then adjusted it to look as close as possible on screen to what I see in the printed photo: As you can see, it's much darker, but I guess I left the Epson scanning app to some auto thing, but Epson software is aggravating, and I was lucky to get anything at all because it would freeze and do nothing at all. If you see the curve I applied to get it to match the photo, I believe I brought down the gamma quite a lot. Another thing worth mentioning is that because I thought the Canon printer was going to last much longer, at one point I bought a lot of 6x4 Canon Photo Paper Plus Glossy II. I doubt this has anything to do, it's not the first time I print to photo paper from another company, and usually it's about the same. So I'm sure those of you who know about these things found about ten different things I screwed up, so if you know a lot about this (not wild guesses please because this ink is insanely expensive), then please tell me what did I do wrong, and how to make it so I can get the best prints I can with this machine. I really don't want to start printing photo after photo trying out different things because I will be down $100 before I know it. Thank you!
  10. I know, like I said in my post, I did this, but as soon the update for Designer finished doing its thing, it forced the OS to set the association back to Designer. The Designer installer shouldn't be programmed to associate Designer with photo formats, especially ones that are raw formats meant to be developed. Even more, after the user forced the association of all DNG files or whatever the format, to open with Photo, Designers updaters shouldn't revert that.
  11. I don't know if this is a bug exactly, but I had to open a DNG file today, which is a raw photo format, and obviously should open in Aff. Photo, but it's set to open in Designer, and it opens, but it's not the right program. Even further, after this I closed the file in Designer, I changed the association to Photo and made sure it was done for all files, but Designer had an update. So when the update installed, it reverted my manual change of association back to Designer for DNG files. I can't remember what formats, but this is not the first time it happens for formats that are mostly photo based. Might be a good idea to check the installers and see what they tell the OS to associate with.
  12. Forgive me if this is a dumb question, but why do none of Affinity's apps have a line tool like most design apps in both vector and bitmap formats? I know I can use the rectangle tool, but it seems a bit odd to create just a simple line. Unless I missed it somehow, but searching for line in the menus and then the shapes tool, usually where that sits at, there's no line. Sure, a line is not a shape, but it's normal convention to put it there.
×
×
  • 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.