Jump to content

emmrecs01

Members
  • Content count

    580
  • Joined

  • Last visited


Reputation Activity

  1. Haha
    emmrecs01 reacted to R C-R in Publisher did not pass the test   
    I for one am "advanced" enough that I do not need any training to perfect my innate talent for idiocy.
  2. Like
    emmrecs01 reacted to VolkerMB in Expanding Stroke amazing precision   
    @LarrySunshine Well, there are so many options out there in the market: CorelDraw, Illustrator or Inkscape (just to name a few). Feel free to use them as they offer better or more advanced tools to you. Also feel free to point developers at bugs as it helps to improve the software. But please explain to me why you consider me an amateur who has no clue whatsoever (regarding the right toolset for professionals)!  
  3. Sad
    emmrecs01 reacted to LarrySunshine in Expanding Stroke amazing precision   
    As someone said, you are NOT running an open source project. HOW in the world you cannot fix such a CRITICAL bug for over 1.5 years? Let's be honest, AD is nowhere near professional vector editor when such crucial tools are not working and are not being dealt with. It's hard to have sympathy for you guys even though I guess it's not developers fault but managements.
  4. Like
    emmrecs01 reacted to MattP in Expanding Stroke amazing precision   
    I keep biting my tongue and trying not to get involved with all of these discussions that quickly become name-calling. It's disappointing to read and unnecessary. I suspect I shouldn't even be typing this (it's one of the reasons you don't see me as much on the forums nowadays) but I just wanted to stop this thread degenerating further by stating that I have been typing the new code for this feature for the last couple of weeks: It isn't something that is being left unaddressed, its omission is not some "petty revenge" as stated earlier (which is truly a rather paranoid, unsettling notion to try to get my head around why someone would even think that?) Please can we just all be nice to each other? It doesn't take much, and it frequently takes less time than bashing a keyboard to try to upset someone else or lash out to feel better. We're all after the same thing at the end of the day and we'll get there quicker without wasting so much time trying to say how "disgusted" we are at the job the software developers do: We're actual real people and we're doing our best with what we have - end of story. We try very hard indeed (we have many hundreds less developers than Adobe) and some things will take us longer to work out, but we actually do care an awful lot about what we do and we want it to be something we're proud of. If we're taking too long for you then I genuinely am sorry, but what more can I say or do - I'm doing the best I can
    Before someone suggests throwing more developers at the problem is a good way of fixing things we've nearly always found exactly the opposite - they need to be the right developers, and they're very hard to find - if you get the wrong ones then you spend time training them up only to find that the user experience of what they create wasn't as good as you'd want anyway, so have to do the work again so that's even more time lost.
    Like everything in life, Designer isn't perfect, I'm not deluded enough to think it is, in fact I'm usually the first to point out its failings when I meet people, but I genuinely am proud of it because despite its failings, it is also a genuinely powerful creative tool that is more fun and productive to use than the competition for a very good range of tasks. So no, I'm not going to feel "disgusted" with myself or my colleagues and nor should anyone try to suggest that we should. Yes, there are things wrong that we've already said are wrong and we are fixing them. Please let this be an end to the name-calling and disparaging.
  5. Like
    emmrecs01 reacted to MattP in Expanding Stroke amazing precision   
    As I said earlier in this very post, I want an end to the name-calling. It's not helpful. I'm locking this thread now.
    Nobody has any right to decide that someone else is 'obviously' an amateur because they can use the software and enjoy it whereas the poster cannot: This is a really flawed way of thinking and even if you believe it to be true, you gain nothing by saying it other than alienation and being judged by others as arrogant.
  6. Sad
    emmrecs01 reacted to LarrySunshine in Expanding Stroke amazing precision   
    So guess what, just like last time I am not the only one complaining about things. Apparently this has been for at least 1.5 years. At this point I will just assume this will most likely never be a professional vector editor and keep exposing this utter disgusting job of software development to others.

  7. Haha
    emmrecs01 reacted to ynneBBenny in Linux Flatpack Version   
    Thanks Jeff, I have 'plans' to try and convince them otherwise
  8. Like
    emmrecs01 reacted to Seneca in Will Affinity Publisher load PagePlus files?   
    I would continue using PP for all the projects started with PP, if I were you.
    I would employ Publisher for all new jobs, though.
    This is how I would go about it.
  9. Like
    emmrecs01 got a reaction from ynneBBenny in Linux Flatpack Version   
    @ynneBBenny
    Welcome to the Affinity forums.
    This thread is but one of several asking for Linux versions of the Affinity apps.  I see the "official" (Serif) answer there as "we have no plans" to port the apps.
    Jeff
  10. Thanks
    emmrecs01 reacted to mariopasqui in New laptop and setup   
    Thank you so much @emmrecs01 .
     
    that's just what I wanted to know.
    Wonderful.
    Mario
     
  11. Like
    emmrecs01 reacted to CarlM in Affinity Publisher is not a copy of InDesign - no massive fail!   
    It's telling that Serif opted to write the code for their three flagship products from scratch and re-launch them as Affinity. It demonstrates an understanding that now and again you have to take the plunge and start all over again rather than keep patching and increasing bloat in a product to produce something that is future proof.
    It never fails to amaze me how many posters predict the demise of Affinity publisher because two months after it's launch it not only doesn't do everything that ID and Quark do after 20+ years of development but also doesn't do things that 20 other apps that aren't DTP are capable of.
  12. Like
    emmrecs01 got a reaction from Alfred in New laptop and setup   
    Hi @Alfred
    Not being a Mac user/owner I had forgotten that Serif now sell the Mac versions directly.  Thanks for the reminder!
    Jeff
  13. Like
    emmrecs01 got a reaction from John Rostron in before/after   
    Same for me; the History slider is invaluable for this.
    Jeff
  14. Like
    emmrecs01 reacted to Dan C in Canon 6D mk II 2 years now and still no support on .CR2   
    When opening the RAW file directly in DPP4 vs AP, Canons own software is bound to have slightly better decoding and processing for their own RAW files, as Canon have written the CR2 format, they likely have the best knowledge in regards to processing their own files and saving shots such as yours.
    This means you might see faintly see more magenta tones in Affinity Photo, but through mine and other users testing we're not seeing close to the same amount of cast that you provided in your first screenshot.
    In a previous post you're comparing a JPEG to a TIFF file, one of these is lossy and compressed (JPEG) and the other is lossless and uncompressed (TIFF) so an 'apples to apples' comparison cannot be made.
    As emmrecs01 has mentioned above, this appears to be related to the file created by DPP4. Could you provide a copy of your TIFF file after processing through DPP4 please?
    As R C-R has mentioned in his post, there is a lot of colour noise due to the underexposed and high ISO shot. Colour noise appears as magenta (alongside yellow and blue, but these tones aren't as jarring on the image), so the more colour noise, the more magenta the image appears.
    It is likely that DPP4 is automatically applying heavy colour noise reduction to your image, and as standard Affinity Photo does not apply this change to the image - hence the slight colour difference. You'll have to manually tweak these settings when developing the file, following the advice provided previously, to reduce this noise level and therefore the magenta cast.
  15. Like
    emmrecs01 got a reaction from Dan C in Canon 6D mk II 2 years now and still no support on .CR2   
    @Pipit
    I really don't want to prolong this thread because I think we are all going round in circles, but, reading again your earlier posts, it seems that the high level of magenta shows on your earlier screenshot because you took your original RAW into DPP4, exported it as .tiff, imported that into APh and that is when the magenta "appears".  I can't explain why this should be; perhaps there is a wrong setting somewhere in your monitor colour profile or the profile of the .tiff is being read wrongly.
    As shown in my earlier screenshots, if I take your RAW direct into APh, Develop it (using default settings) and then apply a little Brightness and Contrast, I get the result posted in my second screenshot earlier.  Yes, there is some magenta colour-cast there, though considerably less than is shown in your screenshot, but others have suggested how you may attempt to reduce this.
    Why don't you simply open your RAW directly in APh, so bypassing DPP4 completely, and see what results you achieve?  I actually used the latest Beta, which you can download to test from the Beta section of the forum, if you wish.
    Jeff
  16. Thanks
    emmrecs01 reacted to AdamW in Affinity Publisher Customer Beta - 1.7.2.458 [BETA CLOSED]   
    This beta has been superseded by the release of Affinity Publisher for Windows 1.7.2 to the public. Check back on this forum for future betas
    Status: Beta
    Purpose: Improvements, Fixes
    Requirements: Purchased Affinity Publisher
    Windows Store: Not submitted
    Download: Download  (Download link removed as 1.7.2 is now live)
    Auto-update: Not Available
    ---
    Hi,
    We are pleased to announce that an updated customer beta of Affinity Publisher (1.7.2.458) is now available as a download from the link above.
    If this is your first time using a customer beta of an Affinity app please note that the beta will install as a separate app alongside your store version. They will not interfere with each other at all and you can continue to use the store version for critical work without worry.
    The beta is an incremental update to the 1.7.1 store version. We recommend that you use this beta in preference to your store version if you are affected by any of the issues listed below.
    If you have any problems using this version please make a new topic in this forum and we'll get back to you as soon as we can. Please feel free to leave general suggestions and comments in the Discussion Forum.
    ---
    StudioLink
    StudioLink has been updated to improve reliability in this Beta but still requires the latest Beta versions of Designer and Photo to function (and for you to be a customer of those applications).
    ---
    Fixes and Improvements
    Text
    Fixed crash breaking path text curve for open curves Fixed error copy / pasting Text Styles that could cause crash Overlapping text frames now respect Ignore text wrap when wrapping around each other Fix for Optical Alignment ignoring Tabs Text selection highlight no longer includes generated list text Fixed bug that could fail to apply OpenType features near end of line Changing letter spacing now splits ligatures correctly Fix for issue unpinning pinned nodes in pinned nodes Fixed Pinned Node status not updating correctly when changed on Master Page Fixed positioning issues when unpinning nodes Hyphenation fixes (Mac) Fixed further IME issues Import / Export
    PDF Import: Improved Font Substitution suggestions when opening PDFs etc PDF and Vector Export: Fixed issue with Embedded Documents and Adjustments PDF Export: Fixed Bleed not being saved in export profiles PDF Export: Fix for unwanted clipping when text nodes exported 'as selection' PDF Export: Fixed export of non-breaking hyphens PDF Export: Avoid font preflight warnings when embedding TrueType CIDFonts PDF Export: Web preset now embeds all fonts. Many browsers don't support ligatures unless the font is embedded and so render incorrectly. (Win) Fixed occasional crash when printing ---
    Earlier Release Notes Beta 442
    To be notified about all future Windows beta updates, please follow this notification thread 
    To be notified when this Publisher update comes out of beta and is fully released to all Publisher customers, please follow this thread
  17. Like
    emmrecs01 reacted to Ron P. in CR3 Support or Refund   
    I had a quick look/read on Libraw about Canon's new CR3 file format. No wonder it seems like it's taking a long time for Serif's Apps to accept it. When these camera manufacturers make such drastic changes, it takes a lot of time and effort to decode those changes so they can be used. Canon has been using the CR2 Raw file format for years. When a new model was released but still used the CR2 Raw file, there were small changes made so was easier for all these apps to catch up. Not so with the CR3.
    I've read posts on other web boards, people posting just a few weeks after a new model was released having small changes to the Raw file format, why it's not already supported and when it was going to be supported. To start with I think that Canon would rather their proprietary software DPP, would be the only software used by consumers of their cameras. They provide it free to those that own their cameras. Do you think Canon might drag their proverbial feet on releasing any information on the newer Raw File format? Perhaps they do.
    I shoot Canon cameras, and do have a copy of DPP, but just don't use it much at all. Even though it really makes more since to at least convert the Raw files with it, since DPP is written by the same company making the cameras. It should provide the best ability to gain the best results from the Raw files they wrote. For styling, and cut-outs, artistic uses, well use other apps like Serif's. You'll have a much better developed file to bring into AP or whatever app you choose. I think Canon has come along way with their DPP app too.
    So anyway if Serif or any other editing app does not support your Raw file yet, and you have tools like DPP available, I don't see why anyone would think Serif is the cause for slowing them or stopping them. Which this reminds me of a mechanic years ago, when car manufacturers started making front-wheel drive cars. I referred to the engines that had to be used as side-way engines. They were a pain to work on. The mechanic told me, working at a dealership mind you, they had to order a special tool just to do one small function, because common standard tools would not fit. His solution, he already had a tool, just needed a little modification. The cost of the special order tool was outrageous, his cost for his mod $0.00 He was not willing to tell his customers the had to wait on this special tool to fix their cars.
    @grabe122788,
    For an answer to your second question concerning refunds. Here's a quote from Serif's On-line Help and Support
     
  18. Thanks
    emmrecs01 reacted to Grenpara in Move to new install of windows on PC   
    Hello Jeff,
    Thanks for fast reply to my post, i really appreciate it.
    I thought I had to deactivate old versions somehow to reinstall like my adobe software.
    I just wanted to be sure before I do it to avoid fighting like I do with Adobe.
    Thanks for the help
    Gren
  19. Thanks
    emmrecs01 reacted to AdamW in Affinity Publisher Customer Beta - 1.7.2.442   
    Status: Beta
    Purpose: Improvements, Fixes
    Requirements: Purchased Affinity Publisher
    Windows Store: Not submitted
    Download: Download
    Auto-update: Not Available
    ---
    Hi,
    We are pleased to announce that an updated customer beta of Affinity Publisher (1.7.2.442) is now available as a download from the link above.
    If this is your first time using a customer beta of an Affinity app please note that the beta will install as a separate app alongside your store version. They will not interfere with each other at all and you can continue to use the store version for critical work without worry.
    The beta is an incremental update to the 1.7.1 store version. We recommend that you use this beta in preference to your store version if you are affected by any of the issues listed below.
    If you have any problems using this version please make a new topic in this forum and we'll get back to you as soon as we can. Please feel free to leave general suggestions and comments in the Discussion Forum.
    ---
    StudioLink
    StudioLink in this Beta requires latest Beta versions of Designer and Photo to function.
    ---
    Fixes and Improvements
    Spread Setup
    Grids can now be set up independently for different spreads or master spreads. Spread grids now taken from applied master unless overridden.
    Grid Gutters re-instated.
    Tools
    Fixes issues reparenting when dragging selections between spreads
    Fixed issue with Vector Crop tool creating multiple crops under some circumstances
    Fixed possible crash after cancelling multiple image placement
    Fixed performance issues with 'Lock Children' in some instances
    (Win) Fix for issue using drag/drop to open the same file twice
    Text
    Words with soft hyphens can now be added to the spelling dictionary correctly
    Fix for Hyperlinks not exporting if intersecting page bounds
    Fixed text entry issues with US International Keyboard
    (Win) Fix for changing font size if text selection contains a pinned image
    Tables
    Fixes issues resizing table cells from Table Panel
    Fixed layout issues in Table Format panel
    Fixed crash selecting tables on different pages
    Pages / Sections / TOC
    Fixed crash from two differing definitions of default TOC style name
    Fixed document sections drifting when the the document model was changed
    Master pages creation was incorrect after changing the document model to single pages
    Fixed issue updating page thumbnails in some cases
    Resources
    Linked Image previews were not colour managed in Resource Manager
    Replacing a linked image with an embedded document could move the object
    Fix for failure to reload linked resources correctly under some circumstances
    Fix for slower performance with Resource Manager open
    (Win) Allow .icm profiles as well as .icc - they are the same thing
    Import / Export
    Fix for failure to load colour in certain SVGs causing crash
    Export to PDF of a previously opened PDF could channel invert JPEG images
    Fixed 'Preview export when complete' applicable for PDF only
    Added TGA export support
    (Win) Custom print profile not saving/restoring all settings
    ---
    Earlier Release Notes Beta 422
    To be notified about all future Windows beta updates, please follow this notification thread 
    To be notified when this Publisher update comes out of beta and is fully released to all Publisher customers, please follow this thread
  20. Like
    emmrecs01 reacted to walt.farrell in Install method (download vs microsoft store)   
    And it's worth noting that if you want to use Affiniy Photo as an external photo editor for some other application, it will be much easier to do that if you have purchased directly from Serif. Microsoft hides applications that you install via the Windows Store, which makes using them from other applications more difficult.
  21. Like
    emmrecs01 reacted to Gerard O in Windows Store Version: Can we set Affinity Photo as Lightroom's external editor yet?   
    If you look at previous postings from me you will see that I don't think Serif/Affinity is perfect. But it is MS policy to  sandbox any apps downloaded from their store . I too have developed for MS and I can assure I have had no luck in getting MS to change their policies. Obviously you and other developers have been more successful in influencing policy.
    I am not too sure insulting posters here will help you to a resolution. In any event I can be of no more help to you
  22. Like
    emmrecs01 got a reaction from Alfred in Is it possible to convert affinity designer macOS licence to Window OS   
    @prayaam
    Welcome to the Affinity forums.
    Each Affinity app has a separate licence for each operating system, Windows, Mac or iPad.  So, transfer of licences between the different systems is not possible, sorry.
    Jeff
  23. Thanks
    emmrecs01 got a reaction from A bas le ciel in Affinity Photo on mac and pc   
    @A bas le ciel
    Welcome to the Affinity forums.
    Unfortunately what you are asking is impossible.  Each operating system version of the Affinity apps requires its own, individually purchased licence.
    Jeff
  24. Like
    emmrecs01 reacted to Alfred in Color blindness feature would be very helpful!   
    I’m curious to know how you determined that the colour you see when looking at grass is what most people call orange! And if green grass looks orange to you, why doesn’t a green traffic light also look orange (instead of white)?
  25. Thanks
    emmrecs01 got a reaction from StevenS in Pre-purchase questions   
    @RodrigoVWB
    Welcome to the Affinity forums.
    There is no difference between the version sold on the Windows Store and that sold directly by Serif.  If you purchase via the store, your installation is tied to your Store Account and no serial key is needed.  Additional downloads (for other computers which you own/control) will also be possible from your store account.  Updates will be downloadable from the store as they are made available by Serif and Microsoft.
    If you purchase direct from Serif, you will be given a serial key for installation and you will automatically have a Serif Store Account, from which you can redownload your software if you ever need to, e.g. to install it on another computer which you own/control.  Updates will arrive either "automatically" or via download from that store account.
    As to costs of upgrades: all upgrades to version 1 are free.  When version 2 is released, quite likely not for some years yet (based on the length of time - several years - since the first iteration of version 1 was released) it will be a paid upgrade but users will clearly have the option to not buy the upgrade is they do not wish to do so.  Version 1 will continue to "work" for as long as the operating system allows it to, i.e. until Microsoft make some major change which renders version 1 of any Affinity app unusable.
    HTH
    Jeff
×

Important Information

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.