Jump to content

Ulysses

Members
  • Content count

    91
  • Joined

  • Last visited

About Ulysses

  • Rank
    Member

Recent Profile Visitors

417 profile views
  1. Regardless of the differences in viewpoint on this, I’m glad to see this conversation taking place. My needs for Designer are usually extremely simple (most of my tasks could be cared for in Photo alone, but sometimes I want the benefits of vector-drawn graphics and fonts). Often there are new concepts than what I’m accustomed to in a pixel editor such as Affinity Photo and Photoshop. The way Designer handles the Canvas vs the Document is one of them. And then controlling them between the desktop version and the iPad version is somewhat different as far as the interface goes. So please keep up the discussion! It helps everyone.
  2. I initially thought the same, too. Text transmission of ideas is sometimes difficult. But despite difference in overall workflow, we're probably asking Serif for similar things. My hope is simply that they deliver a tool that's at least as capable and flexible as those in the Affinity suite of software. Despite my current use of Bridge CC 2019, I'm eager to move away from even that little bit of connection with Adobe. In my case, other than as a simple file browser, it does little else for me. And since I haven't updated to Photoshop CC, I can't use Adobe Camera Raw anyway. As for Lightroom v6, this was the last standalone version offered by Adobe, but it will not recognize native raw files from newer cameras. I could convert to DNG and pull them in that way. I have nothing at all against DNG. But missing native RAW support would continue to be a bummer. Another reason I moved on to Capture One Pro, which is overall superior in a number of ways, albeit not so much as a DAM. All of that to say: I'm eager for Serif to deliver on their own DAM. But Adobe's 20+ years of history in this department shows just how tough it can be to deliver something polished. We may be in for a longggg wait for something with which most of us are happy.
  3. Ohhhh yeah! I remember conversing with you about that approach. I do find it intriguing. Even though I don't see us moving over to that approach, I can understand why the workflow works for you. How are you able to process the latest batch of RAW data from newer cameras without updating to the Creative Cloud versions of Adobe software? With an Adobe workflow, the tasks are split between Photoshop, ACR, and Bridge. A Lightroom user essentially combines ACR and Bridge into a single program (but only partly since Lightroom can't do everything that Bridge can). My current workflow is similar in that I now split my tasks between Affinity Photo for pixel-level editing, Capture One Pro for RAW processing, and Photo Mechanic for keyboarding and metadata management. It's easy enough, although not as elegant as the integrated Adobe solutions. But when I ran away from Adobe, I knew it would also take time until the Serif solution is as fully integrated. Overall, though, I'm more content than if I'd stuck with Adobe's Creative Cloud.
  4. Sorry about this tangential point. But here's why it's not simply academic FOR ME: If you want to maintain access to all of that capability, you need to follow where Adobe is going to lead you. And that means being led to their Creative Cloud. Many of us have less than ZERO desire to go there. Allow me to explain what I'm trying to say: I stopped upgrading Photoshop at CS6. I stopped updating Lightroom at version 6. I opted to avoid renting software from Adobe and having my data potentially held hostage. I also didn't like the costs for their cloud storage options. However, I recently updated to the latest Adobe Bridge CC 2019 as well as the latest version of Adobe Camera Raw; after all, they're both FREE, so why not. I was hoping that I would now be able to process RAW files from the latest cameras from Nikon, Canon, etc. But I can't! Why not?? Because of the the message attached here. Photoshop isn't what's handling your RAW images. It's Adobe Bridge and Adobe Camera Raw. BUT apparently without a qualifying version of Photoshop, Adobe won't allow you to access any of that. This arbitrary limitation is merely one of the reasons I needed to walk — or rather RUN — away from Adobe. And it's why I hope Serif will treat users differently.
  5. Photoshop on its own is simply a pixel-level image processor. In order to integrate RAW and DAM-like capabilities, it needs at least two other components: Adobe Camera Raw (ACR) for supplying RAW handling tasks, and integration with Adobe Bridge to care for DAM-like tasks. Photoshop on its own doesn't offer either of those tasks, but you have to give it to Adobe for providing a very well integrated suite of tools that behave (mostly) seamlessly together. But it needs to be recognized that these are distinct tasks. On its own, however, Photoshop and Affinity Photo are pretty much the same type of image processors. What we're asking Serif to do is provide another app that does something like what Lightroom AND Bridge can do. Digital Asset Management is about the ability to manage many different sorts of media, file-types, metadata, etc., and making all of that information accessible. It's not simply about handling RAW files.
  6. Here's my consistent take on it: Lightroom is not a DAM, although it has DAM capability. Lightroom is a relatively full-fledged RAW processor packaged in an easy-to-access interface (with Capture One Pro being more advanced in most regards). Affinity Photo (if that's what we're talking about when we say "Affinity") is a stand-alone pixel-level image processor with minor RAW processing capability. It's much more akin to Photoshop than it will ever bear a resemblance to Lightroom. I purchased Affinity Photo with the goal of replacing Photoshop. For that purpose, it has excelled perfectly, even though it's not always perfect. For better than 90% of the tasks I need to do, it does at least as well as Photoshop, and is often easier and more effective. For this purpose I have adopted Affinity Photo full-time for where it performs best — as a replacement for Photoshop. With v1.7 things are going to get even better, from what I can tell so far. Part of the problems with all the answers in this thread is that there are so many conflicts with what a DAM actually needs to do. A majority of the answers are that "it needs to be like Lightroom," when a full-fledged DAM needs to be able to do much more in the way of digital asset management than Lightroom is capable of. It will need to have the cataloging capability of Lightroom, while having the cross-application access of Bridge, along with other features and talents. I'm sure Serif has their own out-of-the-box ideas on what a DAM needs to be for their use with their own Affinity applications that include Photo, Designer, and Publisher.
  7. Is your installation of Mojave an upgrade from an older macOS version? Or is it a brand new installation?
  8. Thanks very much, @R C-R. It was reported there a day or so ago. (NOTE: When I originally started this thread, it wasn’t clear that this is a bug in the software. I later edited the title to flag it and see if anyone else had come across this behavior. I have now removed "BUG" from the title.)
  9. Even after carefully doing this, I'm not entirely happy with the way things are turning out. I believe the developers may have a deeper problem here than they might realize. This is NOT a hugely big deal for what WE normally do in our studio. It's only this specific project that revealed the problem at all. And I suppose if I was to start a project in sRGB and stay there, I might not run into this at all. (key words: "might not") For now I can make do, but hope the developers are listening and can resolve this at some point in v1.7 development. It's an issue that runs across the entire suite — Photo, Designer, and Publisher. So I hope they visit this one sooner than later.
  10. I came across this while caring for this project. Although I didn't really need it at the time, I was really impressed to see this sort of depth here. Related side note: The iPad versions of Photo and Designer likewise carry a similar depth. While not precisely as detailed as the desktop versions, it's easy to see the iPad versions being completely usable for detailed and even some large projects.
  11. Lots of us agree! The current icons are pretty cool, dramatic, and different. They're very distinguished from other icons in the dock. But compare with currently shipping icons with the ones that seem to be proposed in the beta. I'm not as crazy about them. Are you? They're a bit flatter, less colorful, and just not quite as interesting (sincere apologies to the team who designed these... no personal harm intended) No, they won't make the software run better or worse, but it would be nice to see icons we like. P.S. — Affinity Team, it looks like the Designer app icon is a little bit different from the rest in that it doesn't have the little bump-out on the top side the way the other two do. If this icon design is where it's headed, at least make them consistent with the bump-out. Give us a little STYLE!
  12. @>|<, thank you very much for bringing this to their attention (and thanks for the workaround, too. I'll try it and let the group know if it covers my needs). Was I one of the first to discover this one? Kinda fun to help contribute in a small way to seeing things improved for future versions. BTW I note this same bug in the retail versions on my Mac OS X 10.12.6 (Sierra) Affinity Photo 1.6.7 Affinity Designer 1.6.1
  13. @>|< I will go research this in the "Bugs" section of the forum. But is there any indication this bug will be dealt with for v1.7?
  14. First of all, DING-DING-DING!! I knew there had to be a bug here! Thank you very much @>|< for verifying and recalling info about this. It doesn’t sound like a difficult correction to make — just a tiny hassle. I will attempt this later tonight or early tomorrow and report back on how things went. Secondly, a huge thank you goes out to each of you who responded so quickly. I’m fairly decent with Affinity Photo, but learning about things like this adds even more to my background of knowledge with this software. Much appreciated, everyone. BTW, I suppose this same error was happening on the iPad version because the base code is the same as the desktop version? Correct?
  15. Affinity Team, is it possible that this is a bug? or are there any other suggestions? My goal is simple: I want to recall a small group of color swatches without having to recreate them over and over again. The Recent swatches isn't really the best option because this can change as I fool around with other colors throughout a project. Thanks in advance for any insight that might be offered.
×