Jump to content

kfriis

Members
  • Posts

    42
  • Joined

  • Last visited

Recent Profile Visitors

517 profile views
  1. I have uninstalled my Photo, Designer and Publisher versions on Windows 10 and MacOS, and the Photo and Designer versions were also deleted from my iPads. There is no use for them any more. I don’t think, the licenses will be renewed. Affinity is too slow in its tracks - even making Adobe look like a sprinter at times I keep one ooold Windows installation alive for now, to handle old, existing material, if the need should turn up the next year or so. That machine is barely visited once every six months (purely for keeping the old system up to date and running). Except for maintenance and possible emergencies, it has no future use. Your mileage may vary, and if your needs are covered, good! In my case: Why continue to waste time on maintaining software no longer in actual use on several platforms? Software lacking key features for many if not most of my use cases.
  2. Ah, still looking panicked for any excuse to not… Would you also prohibit the use of pdf file content, where life depends on the content, I.e. an embedded image (embeddable in ePub too), you’d have to ban pdf in all engineering, hospital, airline use. EPub is a file format. Just as pdf. The value is in content reliability and usability. If content has been reliably certified, it is usable. Otherwise even paper copies must be banned. Try to look at things this way: PDF is a special case of the very powerful postscript language packed into one file only. Epub is a special case of the very powerful html language packed into one file only. The latter is vastly more flexible and powerful, but both are logically similar in scope. They deliver a locally available media output packed in one, single and standardized content file. It’s a case of making ALL pertinent and important material available in a reliable format inside a single file locally on the device available for the purpose. Often, nay, nearly always an iPad. Support material in likewise reliable formats. It’s also a case of making additional, optional explanatory material available at the command of the user, if the user deems this important. Interactively, if required. And it is a case of creating a verifiable, interactive checklist of tests performed in an authorized order, to ensure a job correctly done and reliably finished. From “do this” over “how on earth is this connected” ending in “aha” and a final “test” followed by a series of “check”, “check”… followed by “finished”! No need to connect to anything outside the device, you have at hand. A device, that easily holds a very well assorted technical library down to details seldom required, but when they are… pure blessing! With or without media, animation or interactive content 🤪 Why’s that a problem for you? You do not loose the option to restrict yourself to pdf-only, if that’s your wish, but more modern requirements may be served by ePub support too. In large parts, the program will be similar, some parts even identical. Your personal needs may not be representative, and if Affinity plans on long term survival, planned, recent, current and coming requirements for users with widely varied use cases may be pertinent to plan for. epub is “just” a far more flexible output format. Not at all excluding pdf (really only a small subset of ePub capabilities), if that’s the only level required. You could in theory limit all Internet presentations to pdf only, but that would be rather restrictive, so why do that?
  3. Because - for instance - instruction manuals often has to include animations or videos showing approach, placement and tools in a repair/mounting process. In other cases, it’s a html based “widget” controlled by the user, enabling the user to control views on an detail or construct in ways meaningfull to the user in the moment in the actual environment and space available in restricted spaces locally. Paper manuals are still produced today. Seldom used for anything but emergency backups. PDF format manuals or instructions, check lists etc. are widely used, but not always sufficient. If internet can be guaranteed to be available in a sufficiently high speed (!), a link within a PDF document will often do, but try using that from an iPad with mobile connectibility, in central, old parts of Rome (where even less than megabit speeds are often the only thing available, unless you carry a few hundred meters of Ethernet cable to a reliable Cabled connection - parts of that vanishing, before ends are connected, if you do not use “security heavies” to guard the cable run). Large parts of the world - even large parts of Europe - allow only periodical and “symbolic” mobile phone internet connection speeds. In many situations, you actually need to carry “the internet parts” on you (video, audio elements - e.g. playing the sound of to low or too high tension to aid a technician - or “operator controlled explanatory elements” - typically a html based widget). You can of course use “external files”, but now you run into a versioning problem, that worst case can cause loss of life, if files end up in “unintended mixes” or even files not present on a current device recently gone into use. One ePub3 file has the same benefits as one PDF file. The PDF file is one document, with a collection of elements within. Easily version controlled as a whole (no risk, that one image is showing a year old version by end user accident). The same is the case of an ePub file (whether fixed format or not). All elements are “packed” into one, single file, easily allowing reliable versioning, including fonts and whatnot. If you have an unencrypted/protected ePub3 file called “x.epub” and rename it to “x.zip”, you can unpack the content (as you have probably done a few times, if you work with epubs), and apart from a few, central definition and control files, you’re looking at mostly near standard html content, that could be used as an ordinary “website” element (and often is, during widget development). It is actually easy to add an “active element” to a fixed format ePub (in most cases, it looks decidedly similar to a html link in a PDF file A popular description is “to place the active element” within a given frame, similar to the “startup image size”. All the elements could be regarded as one, discrete package, with predefined options for display and control. In effect, it is a “local web presentation object” requiring no connection beyond the device, but as easily integrated into a specific, physically selected “displayframe” on a screen page. The manual, instruction or check list approach is simplified enourmously by using fixed format ePub3 “Books” (using the term book, is like using the term pdf to describe the freedoms of the internet). In most cases, the web widgets are actually constructed in tools, that may target output as a html-page for inclusion into a standard online webpage, a html-widget (with the interface required to be embedded as an ePub element) or simply to a video or audio rendering, if user interaction is not required. In short - seen from the outside - you could view fixed format ePub3 documents as PDF documents with options for embedded sound, video, animation and optional user interaction, if required (“if required” being the operational phrase). Initially Adobe had a simple, embedded flash swf script approach added to PDF’s in mind, but it never cought on (it was exciting news, when I was an Adobe Postscript device driver developer late in the last millennium). Maybe it is even possible to some extend today (haven’t checked within the last ten years), but you’d run into heavy play problems (our modern world use mostly anything but strictly Adobe endorsed tools for presentation html - and the derivative ePub3 - have completely replaced that option in real life. Regards
  4. Pure balloney! Utterly, decidedly uninformed opinion (which you are entitled to have, but that does not make it right per se ;-). Even the very much simpler standard Apple Pages program allows producing fixed format, intricately designed ePub books/documents. Including multimedia content, like audio , video etc. I guess, this several years old extension to the ordinarily office solution, did not turn up on your radar on "what the world uses or can use" to produce more or less standard output for general use world wide. If you assume only "novel type books", you are (mostly) right, but when we're talking instruction material, manuals, safety manuals and vital check lists, embedded video into fixed formatted manuals, can - and will sometimes - do wonders. Pages is not ideal for that, but it can be done, both simply and to a large degree reliably. When lives may be involved, Pages is not the most obvious solution, alas, there are lots of cases, where the fixed format ePub may be the most obvious solution (iPad's are standard reader devices for a lot of professional use cases - including piloting, engineering, electronic or mechanical repairs etc.) Try animate anything in a 200 page PDF manual or in in a 25 page safety check list (exploding into hundfreds of illustrations required to produce a less clear instruction in PDF only, if even an inkling of freely oriented 3D is involved). It doesn't hurt, that you can design for fixed format ePub (which is displayed without any problems on iOS, iPadOS and macOS, as well as the usual contenders for hi-quality Android machinery) and export to PDF, if animations/videos can be linked to multi gigabyte files online, but that's of no use, when e.g. in doubt on how to mount a special gasket on a bespoke emergency solution natural gas switch in a secure, non-lethal way in 50C in the desert somewhere in the Arabian peninsula. A a similar intricate task on the Altiplano between Arequipa and Puno, in large regions above 4km up, topping out at 4.910 meters, with Wonderfull views of the "Vulcan alley" hundreds of kilometers from nearest mobile connection of even the most inferior or unreliable type. You can of course elect to design tools restricted to produce only material targeted for use cases within the confines of the City of London, but the world is far larger, than that If you have no knowledge, it is OK to say so, but just rejecting usability - even critical usability in some cases - due to lack of insight and vision, is really no way forward. Do you speak for Affinity in any official capacity?
  5. Woaaa!! Soon four years and counting! I remember the early days of UK home computers and PC clones. The UK was leading for a few years, then… suddenly… fell off a cliff due to lack of innovations and customer support. They insisted on being the best; even while the world decided otherwise. Now, is Affinity aiming at repeating this old sad state of affairs? Regards P.S. I have practically stopped using designer (nice app, but integrates rather badly with other software). Photo is relegated to handling old material. I’ve returned to using Lightroom Classic and Photoshop again. And as far as Publisher goes, the still lacking support for docx material import (including styles), lack of foot/endnotes support and especially no real export to ePub usage (especially galling, now that Amazon/Kindle seems to be about to make peace with the format). I’ve even used Word as a Publisher replacement in one recent case, since Publisher seems to have become a dead end, and word at least is supported by most serious environments - still! It’s not a case of pricing. It’s a simple case of lack of even the most basic features, supported in most serious environments. Nearing four years of non-solution of significant omissions to the product feature list is rather telling in my view. Your mileage may vary, but all my licenses for iPad, Windows and Mac has fallen out of use the last 12-18 months. Maybe a secondary machine will be relegated to supporting legacy solutions, like Affinity Designer, Photo and especially Publisher. It all looked so enticing many years ago, and look now on all the good will squandered by inaction or persisting non-solutions to relatively basic needs.
  6. I have, and in some cases, I do. Mostly when the material is locally available on one of my Thunderbolt SSD's. I often prefer Previewer, since I have more control over, what is included in the selection from a NAS directory with, sometimes, up to some hundred images. It's not a solid rule, though. The actual approach chosen, is more or less subconscious. If I expect to look into several, maybe well filled, directories, I start by dabbing a bit around in preview, and then maybe, if I discover, that the specific directory has a reasonable number of images, I may use the approach you suggest. The problem is, that even on a 2.5 Gbit network, a usable size thumbnail creation process will take time, where a few "double clicks" leading to "Preview" here, there and few places more, may render a usable outcome far quicker. With better content detail. My initial problem was, that I did not discover a way to prevent, that each double click kicked Publisher into action. I always had to use the right mouse click followed by "Open in", and that drove me quite hot under the collar at times, when I forgot in the heat of the moment! Regards and a big smile
  7. And as I explained (culling), this is correct, but serious image culling takes place in a deliberate and thoughtful process, typically in Lightroom (or whatever tool I deem preferable at the time and for the purpose. I've used many over the last 17 years. When I need to reuse stored material (even if I cannot see the non-destructive processing from a tool), Previewer is still my quickest tool for the purpose (inspection, sorting). If lightroom could read my catalogues directly from NAS, I would use that approach, alas... it can only handle the images stored on NAS, although cross platform use can introduce all sorts of side-effects to adjust at start up. Sigh... Who said life was easy? Not me.
  8. You seem to assume, that I use the Previewer for culling? I do not need to cull historic material, but I very often need to see, if I'm on the right track, when hunting for a 5, 10 or 15 year old image (or set of NAS stored images). Preview is perfectly good at that. Affinity Photo, Designer or Publisher are not tools, I would choose for that task. On my 4k screen, I can even recognise several people, their faces and whatnot (OK, screen is only 8 megapixel, alas so was a lot of my images until around 2008-9)! Or read street signs. I often used photos of signs as location markers, before GPS was easily available for general use on inner-city walkabouts. And I still do this, from time to time, with my big "real cameras" (if I'm not in the mood to stop what I'm doing and fish out my smartphone to take a photo, thereby saving the exact location for later use). Since I do not read traditional or simplified Chinese, Hangul, arabic or Thai etc., it's nice to have an image for later OCR translation into Spanish, English, French or German - whatever works best on the day. Trying to sync GPS data after the fact seldom works in real life, and a constant smartphone GPS tracking in a city over a whole day needs connection to a power bank. Have tried. Not practical. OK, I do use Previewer for rough culling, when traveling. Nothing special. Just the odd accidental images of my shoes in gravel, sand, water, streets etc. (seldom intended), or empty sky, no focus at all, and all the other little accidents, that a trigger-happy finger may lead to. As a general rule, I never, ever delete any images (except the above clear cut cases) while traveling. I have grown accustomed to the fact, that even if I "schlepp" 10.000-15.000 images and 2-300 videos plus loads of sound samples back, I do not get charged for extra weight on intercontinental flights, compared to only returning with the bare essentials in numbers; which I found out early in 2004-2005 seldom was the most optimal solution (since "bare" seldom resulted in "all" the essentials - luckily I always had backups, so... therefore I know for certain Culling is something I do, when I have arrived home safely, and have all my tools, computers and whatnot at hand. The "remains" are stored, backed up to NAS and offline backups, and never, ever "culled" at a later time (no need). Highly preferable to - for example - start culling in a long boat two hours out from Puerto Maldonado "flying" past trigger-happy (so I was told) illegal gold diggers lining Rio Madre de Dios, or on the return flight via Cuzco to Lima, for transfer to a flight to Amsterdam, with a final transfer to my destination. I prefer the more tranquil - and far, far safer - environment of my home for the culling phase. It - somehow - tend to make my judgement more deliberate and thoughtful I still insist on using Previewer for my go-to, quick and dirty hunting tool, in order to find, what I need to find for one kind of use or other. You may have other needs. Fine with me, but do NOT assume or even conclude, the resulting outcome of my approach, without having the basic facts. Regards
  9. It's not, that I specifically want to see, what "things" look like with the Apple RAW Engine, unless, we're talking iPhone ProRAW files, where Apple actually is THEE authority. And anyone experiencing Adobe's wacky, initial implementation of that in Lightroom (Classic) and Photoshop (desktop) know, what I talk about. The reason for selecting the previewer is simply, that it's fast. You can "scream" through dozens of images in "no time" - try that with Affinity (any of them) on material from - let's say - a February 2011, visit to Taiwan. Lightroom catalogs are not present on my local computer, and importing that along with 5-6.000 images from NAS to local disk, is not necessarily the best initial solution. Especially, when it suddenly dawns on you - while skimming through images from Chiang Kai Shek memorial hall and gardens - that you really wanted to look at - again, let's say - a visit to one of the several Palaces in Seoul during your travel through South Korea September the same year. But... where was it now... Again, you don't "just" kick Lightroom Classic along for historical material, that only is stored on NAS (Lightroom Classic STILL cannot read networked catalogues directly) - and of course backed up to several generations of off-line storage. There are third party tools, but most are not really more or that flexible in real life use, and "public domain" RAW support even lets far more to be desired, than Apples RAW implementations ever have. After previewing this, that and the other, deciding on what to include, I can start importing for local use. With roughly 150.000+ thousand RAW images for travel alone (since 2004, plus roughly the same amount of family images) after culling, I appreciate, that I started out with a directory based (sub)project structure including leading "YYYY-MM-DD travel-project" organisation (each top level with it's own Lightroom catalogue). I yet have to need to combine, Day Of The Dead celebrations from Atzompa Cemetery at midnight in Oaxaca in Mexico, with a Chingay Parade in Singapore, Jungle Trek in Peru's Amazonas region, Christmas Carols in the streets of Sydney, Calcio Storico rough and tumble finals in Plaza Santa Croce in Firenze (like rugby and Thai boxing combined) and the Carneval in Santa Cruz de Tenerife etc. so... It's not the Apple RAW Library per se, I crave; it's the speed. Although compared to a lot of the crap released as "RAW" handling solutions (free or not), I'd take Apple's solution any day. There are a few - extremely few - alternatives. Especially since the main use case in this case is mostly "BEFORE editing or use" selection of material, or just refreshing my memory on main content by "dabbing around" within typically 2-4.000 remaining travel images in long time store. Or a hundred or so video snippets to whole "experiences", where it's not really feasible to kick FCPX or Resolve into action, instead of just using Quicktime to very quickly skim through a LOT of videos from - let's say - a long gone Sunday in Paris, where farmers had filled Champs-Elysée completely from near Arc de Triomphe to around Av. Franklin D. Roosevelt with their version of a green future, cowfarts and other "stinks" included. Life (in a twisted way, that only video can thoroughly show in all it's scary details ;-). You've probably guessed by now, that my approach is not ART, but leans more toward travel and reportage in it's widest sense. Numerous images and videos each day of travel and hundreds to a few thousand "recordings" (audio, video, stills) for each event, instead of a few carefully orchestrated landscapes (I don't think I've ever used more than a few seconds on a motif; AFTER the initial quick images and video and/or sound snippets Regards
  10. Maybe, but I want the standard Apple Image Viewer (or whatever it is called locally - in my country it is called "Billedfremviser" (also handles PDF) - as default (as well as I want QuickTime as default for all video files). The reason is simple: Many, if not most Apps use Apples RAW library anyway - I know, there are exceptions - and for quick inspections/sorting/culling etc. I use the "Picture Viewer" (not Photos). If I by accident double click on a CR3 file, Publisher decided to take over, and starting Publisher is even on speedy M1 gear an "acquired taste"; each time you could as well go for a coffee in the kitchen (a few yards away), before you get the option to close the app (and tell it, that you do not want to save... sigh). As I have several applications for all file types (image, video, audio etc. "raw" material), there are no obvious defaults, and most serious work on newly imported media involve a quick view (only exception is really Import into Lightroom), but in many cases, I extract several (sub)directories from my NAS, and a quick preview on historical material, that is not readily present in my mind either, will be in order, BEFORE I select the subset(s) to import to local Thunderbolt SSD('s) including the associated Lightroom libraries (their nature makes any "substantial" copy a test of my patience For videos, it's more a pre-sorting stage, where I decide what to include in a current or newly created FCPX or Resolve video project, often amounting to hundreds of gigabytes of raw footage to be "imported" from an even larger set of available single (sub)project material present in my NAS raw cuttings directory (named to be easily found, based on project name, date and time etc.). You just don't kick a weeks or even more days of raw recordings into your local Thunderbolt SSD's on the off chance, that most of it will find use in a video project The Apple Viewer is actually the fastest initial selection option, I have found for my specific use cases, and since it has full access to all macOS decoding libraries for God knows how many image, video, sound etc. format things really fly, when they have to. Just my personal view. Your milage may vary! But... thank you for your efforts. Your advice was appreciated.
  11. Thank you. That really helped a lot. I should have discovered the option, alas... on my M1 system with the latest Big Sur, the "Open With..." item was not expanded by default; making the option easier to overlook (at least by me - I'm not a good look'er - ahem Regards
  12. How do I prevent/avoid, that Affinity Publisher automatically grabs the "load-task", when I double click on a Canon CR3 file (Mac Big Sur Intel and M1)? I've just recently bought a Canon EOS 90D delivering CR3 files, so... how does Publisher get the idea, that it is the absolutely best application to load a CR3 file? It is not by any measure (it takes for forever to even get started, if it succeeds at all - even on M1 silicon). There are lot's of alternatives that are better suited for the task on my machines. So, HOW do I convince Publisher 1.9.3, that it is NOT my default application for handling these files? Photo would be more appropriate, but the only time where Publisher doesn't kick in, Designer sometimes decides that it simply has to handle CR3 files, which it - obviously - is not ideally suited to either. Those up to around 48 megabyte Canon RAW files scream for more optimised handling. There may be an easy way, if I just knew where to look (dabbing around in System Settings and it's small gazillion of options seems to me to be a sure waste of time
  13. Hi Mark Ingram The problem is, that I cannot reproduce the error (there were many, simple steps involved, prior to the crash). I’ve experienced a similar “sudden death” (hanging/no response, this time running full throttle) on my MacBook 13 (Intel, 4 thunderbolt ports) MacOS 11.2.3 Affinity Photo 1.9.1 (Apple App Shop). Less than an hour ago. There were a lot of operations involved, starting with import from a 16-bit BW TIFF, masking, selecting, altering geometry, converting back to 16-bit color, with several TIFF versions exported on the way. Saving the final version (after export) locked everything, but recovery file made me loose - ahem - “only” the last 10-20 major steps and of course a lot of “fine tuning” (a bit of a problem, still). Crash report sent to Apple. Approach not reproducible, but this kind of behavior can be challenging in the long run. It’s not the same steps to the “sudden death” zone, but...
  14. Recently downloaded and installed 1.9.1.979 becomes unresponsive, when "Channel Mixer" is requested on an old jpg image scan (cropped to 2957x1873 px). Nothing shows up (e.g. the "option" is not opened up). Memory use fixed at 915.6 MB, CPU roughly between 10-18% (total machine use <30% at between <1 GHz to < 3GHz - max CPU "Turbo umpfh" is 4.9GHz), 8CPU, 16GB, 3TB internal NvME SSD. Fully updated Windows 10 Pro 2H20 environment. Only actively used application (besides a browser in the background and the usual processes in a normal system). Killed process after a significant amount of minutes waiting for "recovery". Not good. Work completely lost. Not reproducible, since steps involved cannot be recalled.
  15. When Affinity Photo 1.9.0 and Affinity Designer 1.9.0 (I manipulated the designer link instead with Publisher) discover, that there are new versions available for download, you are offered to be transported directly to download. Alas, your applications - 1.9.0 at least - still use a "http://..." references instead of a "https://...." for download link. I'm quite sure, since:
×
×
  • 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.