• Content count

  • Joined

  • Last visited

About v_kyr

  • Rank
    Dedicated User

Recent Profile Visitors

953 profile views
  1. You can assign under OSX which of the apps that can deal with NEF raw files and should open these as default. If you perform a right click on a NEF file the finder menu, it's "Open with..." submenu shows you as the top most entry, which app is actually associated here to be the one which will get the file passed over to open as default. But that it also listes below other apps which can deal with that NEF extension (aka open them) and you can always select another one to open these. - So as said before I assume that Affinity Photo might be setup on your side as the default app to open these. You can change that to Apples Preview.app or one of the Nikon apps (NXView, Capture NX-D) if you have those installed. However, just copying selected NEF files from inside the Finder from the cardreader over to some other folder location on your SSD/hard disk doesn't alter or change these NEF files by Affinity or whatever app might be the associated as the default app to open these. In your case it's only indicated that Affinity will be here the default app which then opens those if you perform a double click on one of those NEFs. - Further you can change that behavior and the app which should open NEF files as default app. See for example: How to change the default application for a file type How to set default apps on Mac 2 Ways to Change the Default Application to Open Files With in Mac OS X ... and so on, Google will tell you ...
  2. I assume you are running High Sierra, since that is what I would expect an actual Mac to come today preinstalled with. - However, on my system (El Capitan) the default behaviour when using an USB cardreader is, that the device is automounted and that the Apple Photos app starts/pops up and if desired let me import the images from the cardreader ... ... though you can but don't have to import via Apple Photos here. So if you switch instead over to the finder you will see the cardreader mounted (here in my case as a NO NAME device) ... ... and can navigate into the DCIM folder and copy the NEF raw files from there where ever you decide to place them on your filesystems. - NOTE that for me those NEF files aren't shown up as Affinity associated/related files, instead they are listed as plain DSC_XXXX.NEF files.
  3. If that's the lowest common denominator (?). - Yes as we all know even PDF isn't always treated the same everywhere and can have issues here and there, thus taking just over a plain unicode text representation and then reformat that might be your best option here (as far as one still has the apps and can extract the text).
  4. Good question, probably there are only few things of the PS Plugin interface supported at all (like only some filter related functions and transfer interoperation connections) and the majority of the PS Plugin interface isn't actually adapted and bridged over.
  5. Well the top toolbar is a button bar and no menu bar per se, so the widgets/components used for that are different and button related and thus not the same as the top menu items. - So since there aren't actually any equivalent button representations of those menu items, you can't customize or add these there.
  6. Probably the NEF file extension has now been associated with Affinity as a default app for openning these from the Finder. If you can see your card reader mounted in the console and copy files from there over it shouldn't bother at all. On OSX usually Apple Photos kicks in if you connect and transfer files over from a card reader to the OSX images folders, it recognizes this and as default asks to read those in and store in it's image locations. - Do you have and use Nikon's transfer app installed? However, never had the fact that Affinity kicks in in that image raw files transfer process and I doubt it will do anything here to the raws as default. Take a look which app is associated with NEF raw files on your Mac. Personally I use a two windows file manager like TotalCommander (good old habits) on Macs too here for any file related management operations (mark/compare, copy, move, delete, change... etc.). It's more comfortable for performing such and other tasks.
  7. The macro recording in it's current state doesn't support opening/saving file operations and several other things, thus you have to see if you can combine certain macro recordable features with batch processing here. When batch processing files you can apply recorded macros to be excuted together during the processing of batch tasks. "Δοκίμασε αν μπορείς να λειτουργιες τα macro από το batch processing".
  8. That Brother model is a mobile pocket scanner isn't it? - It's Scan resolution (optical) is up to 600 x 600 dpi according to Brother specs, so that's the physical (optical) max resolution it scans. -- See the following more detailed explanations to get an idea: 1. What does interpolation mean? Interpolate means that between real, scanned pixels the software will set those whose color value is an average of the neighboring pixels. This gives a scan in a higher resolution than the max. possible optical resolution of the scanner. However, the file does not contain any additional information: details that can not be captured at the highest optical resolution will not, if interpolated! For example, if a scanned pixel has the value 202 and the next scanned pixel has the value 206, then the interpolated interpolated pixel is calculated to be 204 [1]. At this point, therefore, there is no information that would be taken from the template. A problem arises in the following case: On the template is a black field with a very thin white line that goes through the field. Put the case, the scanner detects at its max. optical resolution respectively left and right of the line the outermost edge of the black field. When interpolating, he will then also set the intermediate pixel black, since the average of two black pixels again results in a black (interpolated) pixel. This thin white line will therefore not be present in the scan because it was not optically detected. NOTE: details that can not be captured at the highest physical resolution will not work if interpolated! 2. What exactly is the "optical" resolution? If this is the case, your scanner has a maximum optical resolution of 600 x 600 ppi. This means there are 600 CCDs per inch horizontally scanning your original. That's the maximum, which is optically possible. He really can not scan anything more. The same applies to a 600 x 1200 ppi scanner. However, it looks a bit different with the vertical resolution, which is not limited by a number of CCDs. Here, the resolution is controlled by a step motor, d. H. a motor moves the car gradually. The more steps per inch, the higher the resolution. Scanning with 1200 x 1200 ppi also results in a problem here: Since there are only 600 CCDs horizontally and interpolated to 1200 ppi, the following happens: Horizontally, every second pixel is scanned and the intermediate interpolated. Vertical is scanned 1200 steps per inch. However, since the CCDs have a diameter of one-sixth of an inch, the scanned pixels overlap each by 50%, which somewhat distorts the result. That's why the maximum optical resolution of a 600 x 1200 ppi scanner is 600 ppi! The phrase "1200 ppi" means only that the motor can make 1200 steps per inch. More details than 600 ppi can not be scanned with it. The advantage of 600x1200 ppi scanners over 600x600 ppi is that if a stepper motor is capable of 1200 steps per inch, it probably works very well at 600 steps. 3. Why is interpolation mostly not useful? Interpolating is therefore not useful because increasing the resolution potentially increases the amount of data without including additional information. The doubling of the resolution corresponds to z. Eg a quadrupling (2 squared) the amount of data. So you get partially extremely larger files without any benefit. If you have a max. optical resolution of 300 ppi and interpolate to 600 ppi, this means that about 75% of your data did not result from the template, but were calculated. 75% of the data do not contain any additional information! With an interpolation to 1200 ppi 93.8% of the data are already without additional information! The following graphic serves as an example. The black boxes symbolize the pixels that were actually scanned. Since it was interpolated to twice the resolution, every second pixel is horizontally and vertically an interpolated pixel, here shown in gray. For a scanner with 300 x 600 ppi, the 2nd line would not be interpolated, but scanned, but due to the overlap, this line is still an average of the 1st and 3rd line. The result is the same. For example, with a 9 x 13 cm color photo, this example (1200 ppi) would give you a file about 74.7 MB in size, with all the consequences mentioned. And only about 4.7 MB contain "real" information. Around 70 MB are interpolated data! You can now calculate for yourself how high the proportion of "real" data is at an interpolated resolution of 9600 ppi, which is advertised so often. Incidentally, this file would be about 4.7 GB in size. How many of them do you bring back to your hard drive? And how do you want to print this file? How do you want to open them in your application? So why do you want to waste your memory space with this superfluous, informal MByte (or GByte)? Apart from the fact that these amounts of data can slow your computer to a standstill, at the latest when it comes to printing. Since, as explained in the previous chapter, when scanning lower resolutions are sufficient than many scanners optically possible, I keep interpolating i. d. R. does not make sense. You only get more data that your printer can not handle. 4. No rule without exception: when is interpolation still useful? However, it is not the case that interpolating is completely meaningless. For example, it may be necessary if the calculated scan resolution is the opt. Resolution of the scanner exceeds, z. For example, if you want to greatly enlarge the scan. Although this does not give you any additional information, it reduces the effect of stairs because there is a larger number of pixels. This is likely to occur when scanning line originals, as you are scanning at higher resolutions than with grayscale or color originals. In spite of the lower color depth, you will get larger files than when scanning as a gray level and then anti-aliasing, but the gray tones would have to be rasterized! Also, interpolating may be necessary if you are scanning slides or negatives and the necessary resolution can only be achieved by interpolating. Basically, with line drawings, it may be useful to interpolate when the opt. Resolution of the scanner is not enough. For grayscale and color charts, it's usually not a good idea and usually not necessary. Interpolation never reaches a higher information content! The maximum interpolated resolution of a scanner is therefore the least important technical feature of a scanner. Only it can be advertised so well ... By the way: If your scanner is max. "optical" resolution 300 x 600 ppi indicates you can only scan with a resolution of 300 x 300 ppi [2], if you want to avoid interpolation. At a resolution of 600 x 600 ppi, it has to interpolate in one direction (the maximum resolution of 300 ppi resolution) to 600 ppi, otherwise the image would be compressed. To prevent stretching or upsetting, the horizontal and vertical resolution must always be the same. In the case of vertical resolution, as already mentioned, the pixels overlap, which amounts to an interpolation. ---------------------------- [1] This example describes the "Linear Interpolation". In addition, there are also the "square" and the "cubic interpolation". Although they require more computing time, they deliver better results. Nevertheless, the pixels thus calculated without correspondence on the original. [2] The statement is only correct for resolutions higher than the optical resolution. However, there are also cases where interpolation is performed although the optical resolution has not yet been reached.
  9. Well the overall problem is you never know what level of computer and software (IT) experience certain users have and thus if they will understand at all what you are trying to explain them. So that they afterwards don't have any fear to try out these things. Further as a developer you usually tend to use other more technical and domain specific terminologies, since you know the guy next to you is a dev too or at least a sysadmin etc., who has knowledge about those things and thus understands mostly right out of the box what you are talking about. - However the difficulty here is often to explain certain things then to people without any deeper IT background in a way they can follow and understand. As a dev you somehow sadly unlearn this over time, since you tend to do many things automatically without the need of much thinking about it, or how to explain certain for yourself and colleagues easy to follow steps now to others, which maybe don't have any clues about all those things and terminologies.
  10. Related to OSX and writing to NTFS filesystems you would need at least to enable Apple's experimental support for writing to NTFS drives which as default is disabled. However it's more or less a crippling task to set it up and it's also not that stable and performant than other third party driver solutions here. Thus I recommend instead better to use a third party driver like Tuxeda NTFS or Paragon NTFS here which are better and also more foolprove. - NOTE that some hard disk vendors (like Seagate, Toshiba etc.) offer and bundle Mac NTFS drivers for their drives, for example I once got an external Toshiba one which was NTFS preformated and came together with Tuxeda NTFS OSX drivers so that it could be used under OSX too. Seagate offers similar things here but instead the Paragon NTFS drivers. However one of the best ways to exchange data between Win and OSX is to use always devices which are formated with the exFAT filesystem, since exFAT can be natively read/written by all OS and also doesn't have the 4 GB file size limitation of the older FAT32 here. All USB sticks I use between the different OSes are usually formated this way, since every system here Win/OSX/Linux can read/write with no problems that format.
  11. Yes the whole slice entry (rect area) has to be highlighted otherwise the menu entry won't be enabled. - The way only one subentry is highlighted in Phils above first posting top image doesn't work, the whole "You Flexi Thing 4 Cover" has to be clicked and highlighted so that all including subentries are highlighted too together there with that one. - In my case that checkbox toggle altering seems to had the effect to changed the highlighting for the whole here, maybe I didn't hit and meet it right one time correctly.
  12. If something is not available at all it's not a bug but an feature omission or functionality absence. - A bug is some error or misbehaving in an implemented functional code or an coded algorithm, so some code which behaves intensional faulty when it is executed.
  13. No not really, had to toggle the checkbox on/off once to get the menu updated (make an actualisation at all) on OSX, see below screenshot. Maybe it behaves on Windows too this way and shows that menu entry always disabled until you toggle the above checkbox off/on again and revisit the menu (?). - So yes it has to do with activated selections.
  14. Not sure which one you mean, since there are several threads about that Win Aero theme available on the forum. - But maybe you meant this one here? Well if it's that one you mean, it tells to use --no-dwm-warning on the command line as an argument to start the app. So something you usually would do from inside a DOS or Win cmd shell as ... "C:\Program Files\Affinity\AffinityDesigner\Designer.exe" "--no-dwm-warning" However this suppresses just the non Aero error blabla message dialog ("Windows aero is not activated. This leads to rendering problems and slow speed. Please choose an Aero desktop theme.") during app startup, but of course wouldn't fix any possible real runtime problems then if such would occur on your Win7 system. - But you can give it a try and see how the app behaves then on your system. And since you usually don't want to make a batchfile which you have always to startup more in a console/shell like fashion, you can alter the applications desktop icon accordingly, so that when it is double clicked it will perform then the application startup with that above ""--no-dwm-warning argument option supplied. To do that, you have to right click on the Affinity Designer desktop application icon and look under it's properties (Target?) settings where it lists the applications call entry, aka ("C:\Program Files\Affinity\AffinityDesigner\Designer.exe") then you edit/change that one into ... "C:\Program Files\Affinity\AffinityDesigner\Designer.exe" "--no-dwm-warning" So far so good, this now should allow you to start the Designer application then without poping up that Aero message window. But if you double click any associated "*.afdesign" file the startup method for that extension does still not take that argument option into account. In order to overcome with that too, you would have to change/alter a Windows registry entry which is associated with that file extension. Since I don't know if you know how to work and change and add entries to the Windows registry, I think it's better to wait for some demand from your side here for this one then! (BTW I'm actually not on a Windows system, otherwise would have made some visual explanatiory screenshots for you, which might be here more meaningful and helpful for you.)
  15. You have to purchase (buy) them for every OS (Mac, Win, iOS) separately.