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

Nik Collection will not work since today.


Recommended Posts

As I said, if you have a Fusion drive, you should be using only Core Storage aware tools like Apple's Disk Utility to repair your startup drive's GUID partition table. If the partition table becomes corrupt & Disk Utility reports that it cannot repair it, the recommended procedure is to reformat the drive using Disk Utility, which of course will write a brand new partition table to it & make any existing data on it inaccessible by normal means.

 

That means you must always have a backup of your user data (minimally your document files) stored on another physical drive or on remote storage so that you can restore it from that source after reformatting the drive & reinstalling the OS (or OS's) & applications, ideally from sources known to be uncorrupted (like CD/DVD installer disks and/or fresh downloads from the software maker's servers).

 

Specifically, running anything that touches the GUID partition table of the startup drive while booted from a Windows partition is not supported by Apple & should be avoided if at all possible.

All 3 1.10.8, & all 3 V2.4.1 Mac apps; 2020 iMac 27"; 3.8GHz i7, Radeon Pro 5700, 32GB RAM; macOS 10.15.7
Affinity Photo 
1.10.8; Affinity Designer 1.108; & all 3 V2 apps for iPad; 6th Generation iPad 32 GB; Apple Pencil; iPadOS 15.7

Link to comment
Share on other sites

I have deltet all Files and Partitions and Used the Internet Recovery Mode to reinstall OS X. No old installation are on my drive now. All Files are installed without using a backup. So I doesn't understand, while the plugins not working with Affinity Photo. The Computer is like a new bought one.

Link to comment
Share on other sites

By delete do you mean that you reformatted the drive using Disk Utility's Partition function, or something else?

All 3 1.10.8, & all 3 V2.4.1 Mac apps; 2020 iMac 27"; 3.8GHz i7, Radeon Pro 5700, 32GB RAM; macOS 10.15.7
Affinity Photo 
1.10.8; Affinity Designer 1.108; & all 3 V2 apps for iPad; 6th Generation iPad 32 GB; Apple Pencil; iPadOS 15.7

Link to comment
Share on other sites

Jetzt wird es mir zu umständlich auf Englisch zu antworten. Ja ich habe auf der Festplatte mit dem Clean Befehl den Partitions-Status aufgehoben — Konkret wurde der Schreibschutz der Recovery Partition beseitigt. Diese Option gibt es bei dem Festplatten Dienstprogramm nicht. In meinem Fall wurde der Bereich der Festplatte ab der Windows Partitionen ausgebaut dargestellt. Selbe das Löschen der Partition geht in diesem Fall nicht. Das waren bei mir 512 GB Festplattenspeicher der nicht mehr erkannt wurde. Durch den Clean Befahl könnt die Festplatte im Verbund wieder hergestellt werden (Fusion Drive). Danach habe ich die Festplatte (3 TB) Formatiert und danach das Betriebssystem (OSX 10.11.4) neu eingespielt (Externe Festplatte brotfähig mit mit OSX 10.10.x). Somit war die Festplatte im gleichen Zustand wie bei einem Neukauf. Anschliessend habe ich die Programme neu installiert. Vorhergehende Sicherungen mit der Time Machine habe ich nicht genutzt um einen Clean Install zu erreichen.

Daher kann ich nicht nachvollziehen, wieso die Plugins nicht funktionieren.

also im Schnelldurchgang:

 

Festplatte von seiner PArtitionierung befreit mit Discoart -> Clean

 

Start über die Internet Recovery Partition. Start des Computers mit gedrückter Tastenkombination  [CMD] + [ALT] + [R] und Ethernetkabel

 

 


Festplatte mit Festplattenutility - Wiederherstellung des Fusion Drive Verbandes.

 

Festplatte mit dem Festplattendienstprogramm neu Formatieren.

 
Start von externen Festplatte mit OSX 10.10 um OSX 10.11 zu installieren (Internet Recovery bietet nur OSX 10.10 bei meinem Rechner).
 
Neu einrichten des Computers und installation der Programme über die Installations DMG's oder den App-Store.
 
Time Machine Backups wurden nicht einbezogen und gelöscht.
 
Danach habe ich Die Plugins installiert und anschliessend Affinity Photo.
 
Die Plugins werden im Demo Modus gestartet obwohl das Full DMG zur Installation verwendet wurde.
 
Wie nun weiter - bitte nicht noch einmal die Fragen über die Löschung der Festplatte. Das hilft mir nicht weiter.
Link to comment
Share on other sites

Hier mal was zu Discpart

 

 

DiskPart

Disk Administration, Partition a disk. This page documents the Windows 7/8/2008/2012 R2 version of Diskpart. 

Syntax
DISKPART

Commands you can issue at the DISKPART prompt:

ACTIVE Set the current in-focus partition to be the system partition.

ADD Add a mirror to a simple mirror
ADD disk=n [align=n] [wait] [noerr]

ASSIGN Assign a drive letter or mount point to the volume with focus.
If no drive letter or mount point is specified, the next available drive letter is assigned.
ASSIGN [{LETTER=D | mount=path}] [noerr]

ATTACH Mount a virtual hard disk (VHD) so that it appears on the host computer as a local hard disk drive.
ATTACH vdisk [readonly] { [sd=SDDL] | [usefilesd] } [noerr]

ATTRIBUTES Display, set, or clear the attributes of a disk or volume:
ATTRIBUTES DISK [{set | clear}] [readonly] [noerr]
ATTRIBUTES VOLUME [{set | clear}] [{hidden | readonly | nodefaultdriveletter | shadowcopy}] [noerr]

AUTOMOUNT Enable or disable the automount feature:
AUTOMOUNT [enable] [disable] [scrub] [noerr]

BREAK Break a mirror set
BREAK disk=n [nokeep] [noerr]

CLEAN Remove any and all partition or volume formatting from the disk with focus, 'all' will Zero the disk.
CLEAN [all]

COMPACT VDISC Reduce the physical size of a dynamically expanding virtual hard disk (VHD) file.

CONVERT Convert a disk from one disk type to another:
CONVERT basic [noerr]
CONVERT dynamic [noerr]
CONVERT gpt [noerr]
CONVERT mbr [noerr]

CREATE Create a volume, partition or virtual disk:
CREATE partition efi [size=n] [offset=n] [noerr]
CREATE partition extended [size=n] [offset=n] [align=n] [noerr]
CREATE partition logical [size=n] [offset=n] [align=n] [noerr]
CREATE partition msr [size=n] [offset=n] [noerr]
CREATE partition primary [size=n] [offset=n] [id={ byte | guid }] [align=n] [noerr]

CREATE volume raid [size=n] disk=n,n,n[,n,...] [align=n] [noerr]
CREATE volume simple [size=n] [disk=n] [align=n] [noerr]
CREATE volume stripe [size=n] disk=n,n[,n,...] [align=n] [noerr]
CREATE volume mirror [size=n] disk=n,n[,n,...] [align=n] [noerr]

CREATE vdisk file=filepath {[type={fixed|expandable}] | [parent=filepath] | [source=filepath]}
[maximum=n] [sd=SDDL] [noerr]

DELETE Delete a partition, volume or a dynamic disk from the list of disks:
DELETE disk [noerr] [override]
DELETE partition [noerr] [override]
DELETE volume [noerr]

DETACH Stop the selected VHD from appearing as a local hard disk drive (Win7/2008 R2 only).
DETACH vdisk [noerr]

DETAIL Provide details about an object:
DETAIL Disk
DETAIL Partition
DETAIL volume

EXIT Exit Diskpart

EXPAND Expand the max size (in MB) available on a virtual disk (Win7/2008 R2 only).
EXPAND vdisk maximum=n

EXTEND     Extend a volume or partition with focus and its file system into free (unallocated) space on a disk.
EXTEND [size=n] [disk=n] [noerr]
EXTEND filesystem [noerr]

FILESYSTEMS Display current and supported file systems on the volume (Use 'Select Volume' first)

FORMAT Format the system or pertition:
FORMAT [{fs=<ntfs|fat|fat32>] [revision=x.xx] | recommended}] [label=label]
[unit=n] [quick] [compress] [override] [duplicate] [nowait] [noerr]

GPT Assign attributes to the selected GUID partition table (GPT) partition:
GPT attributes=n

HELP [command]

IMPORT Import a foreign disk group into the disk group of the local computer:
IMPORT [noerr]

INACTIVE Mark a system/boot partition as inactive [don’t boot], (use 'Select Partition' first)

LIST Display a list of objects:
LIST Disk
LIST Partition
LIST Volume
LIST vdisk (Windows 7/Server 2008 R2 only)

MERGE Merge a child disk with its parents. depth=1 will merge with parent. (Windows 7/Server 2008 R2 only)
MERGE vdisk depth=n

OFFLINE Take an online disk or volume to the offline state, use 'Select Disk' first)
OFFLINE disk [noerr]
OFFLINE volume [noerr]

ONLINE Take an offline disk or volume to the online state.
ONLINE disk [noerr]
ONLINE volume [noerr]

RECOVER Refresh the state of all disks in a disk group, attempt to recover disks in an
invalid disk group, and resynchronize mirrored volumes and RAID-5 volumes that have stale data.

REM (remark/comment)

REMOVE Remove a drive letter or mount point from a volume:
REMOVE letter=E [dismount] [noerr] (Remove drive letter E from the in-focus partition)
REMOVE mount=path [dismount] [noerr] (Remove mount point from the in-focus partition)
REMOVE all [dismount] [noerr] (Remove ALL current drive letters and mount points)

REPAIR Repair a RAID-5 volume with a failed member by replacing with a specified dynamic disk:
REPAIR disk=n [align=kb] [noerr] (align = KB from disk beginning to the closest alignment boundary.)

RESCAN Locate new disks and volumes that have been added to the computer.
RETAIN Prepare an existing dynamic simple volume to be used as a boot or system volume.

SAN Display or set the SAN policy for the currently booted OS.
SAN [policy={OnlineAll | OfflineAll | OfflineShared}] [noerr]

SELECT Shift the focus to an object:
SELECT Disk={ n | diskpath | system | next }
SELECT Partition={ n | d } (Volume number or Drive letter)
SELECT Volume={ n | d } [noerr] (Volume number or Drive Letter)
SELECT vdisk file=fullpath [noerr]

SETID Change the partition type for the partition with focus (for OEM use):
SET ID={ byte | GUID } [override] [noerr]

SHRINK Reduce the size of the selected volume:
SHRINK [desired=n] [minimum=n] [nowait] [noerr] (Reduce the size of the in-focus volume)
SHRINK querymax [noerr]

UNIQUEID Display or set the GUID partition table identifier or MBR signature for
the (basic or dynamic) disk with focus:
UNIQUEID disk [id={dword | GUID}] [noerr]

Commands to Manage Basic Disks:

ASSIGN MOUNT=path (Choose a mount point path for the volume)

CREATE PARTITION Primary Size=50000 (50 GB)
CREATE PARTITION Extended Size=25000
CREATE PARTITION logical Size=25000
DELETE Partition
EXTEND Size=10000
GPT attributes=n (assign GUID Partition Table attributes)
SET id=byte|GUID [override] [noerr] (Change the partition type)

Commands to Manage Dynamic Disks:

ADD disk=n (Add a mirror to the in-focus SIMPLE volume on the specified disk
see 'Diskpart Help' for more.)
BREAK disk=n (Break the current in-focus mirror)
CREATE VOLUME Simple Size=n Disk=n
CREATE VOLUME Stripe Size=n Disk=n,n,...
CREATE VOLUME Raid Size=n Disk=n,n,...
DELETE DISK
DELETE PARTITION
DELETE VOLUME
EXTEND Disk=n [size=n]
EXTEND Filesystem [noerr]
IMPORT [noerr] (Import a foreign disk group, use 'Select disk' first)
RECOVER [noerr] (Refresh disk pack state, attempt recovery on an invalid pack,
& resynchronize stale plex/parity data.)
REPAIR disk=n [align=n] [noerr] (Repair the RAID-5 volume with focus, replace with the specified dynamic disk)
RETAIN (Prepare an existing dynamic simple volume to be used as a boot or system volume)

When setting up a new drive, create in this order: Create Partition, Format drive, Assign drive letter.

The diskpart commands can be placed in a text file (one command per line) and used as an input file to diskpart.exe:

DiskPart.exe < myscript.txt

When selecting a volume or partition, you can use either the number or drive letter or the mount point path.

The Windows GUI interface can also be used to assign a mount-point folder path to a drive. In Disk Manager, right-click the partition or volume, and click Change Drive Letter and Paths, then click Add and then type the path to an empty folder on an NTFS volume.

The Windows Recovery Console, includes a simplified DISKPART command. It only provides functionality for adding and deleting partitions, but not for setting an active partition.

Always back up the hard disk before running diskpart.

Examples:

SELECT DISK=0
CREATE PARTITION PRIMARY
SELECT PARTITION=1
FORMAT FS=NTFS LABEL="New Volume" QUICK
ASSIGN LETTER=E
EXIT

The default SAN policy in Windows Server 2008 / R2 is now VDS_SP_OFFLINE_SHARED for all non boot SAN disks.
This means that the disks will be offline at server startup (even if the drive contains a paging file).

This Disk Management error message indicates that the drive is offline:

"the disk is offline because of policy set by an administrator".

Query the current SAN policy to see if it is Offline Shared

DISKPART.EXE 
DISKPART> san 
SAN Policy : Offline Shared

To manually bring the disks online: 
Computer Management > Storage > Disk Management, right-click the disk and choose Online.

If these are not part of a cluster, than an alternative is to make a SAN policy change, select the offline disk, clear its readonly flag and bring it online:

DISKPART> san policy=OnlineAll
DiskPart successfully changed the SAN policy for the current operating system.

DISKPART> LIST DISK
Disk ### Status Size Free Dyn Gpt
-------- ------------- ------- ------- --- ---
Disk 0 Online 80 GB 0 B
* Disk 1 Offline 20 GB 1024 KB

DISKPART> select disk 1
Disk 1 is now the selected disk.

DISKPART> ATTRIBUTES DISK CLEAR READONLY DISKPART> ONLINE DISK
DiskPart successfully onlined the selected disk.

“Divide et impera” ~ Latin saying (Divide and conquer)

Link to comment
Share on other sites

Onlymac,

 

My German is so poor that I must rely on the (quite imperfect) Google translation of your post, but as I understand it you used the DiskPart CLEAN command to remove all the partitioning & volume data from your Fusion drive. As I understand it, you did this in part to remove a Windows partition of 512 GB, & possibly to remove the OS X Recovery partition and/or its write protection. This was to make all of the drive's 3 TB available for a new installation of OS X. To do that, since the OS X Recovery partition was no longer usable you had to use Internet Recovery for the installation. Since Internet Recovery will only install the original OS version that came with the Mac, OS X 10.10.x was installed & you then had to upgrade that to 10.11.x.

 

This was perhaps not the easiest or most straightforward way to repartition the drive (everything could have been done with Internet Recovery's Disk Utility & Install OS X functions) but as long as the currently installed 10.11.x Disk Utility's First Aid command run on the drive itself (not the volume indented under that in the list on the left) completes with the green checkmark (the details should show "The partition map appears to be OK"), I think we can safely assume that a partitioning issue is not the cause of your issue with the Nik collection.

 

It might be a good idea to run First Aid on the OS X partition as well, just to make sure there are no problems with its volume format, but aside from that, I promise I will not ask any more questions or make any other suggestions about the health of your drive.  :)

 

I'm not sure about this but your issue might have something to do with order in which you installed the apps & plugins after reinstalling OS X. Normally, the plugins should be installed after installing the apps that can use them, so at the least Photoshop CC 2015 should have been installed before installing the Nik collection. If you installed PS first, the Nik installer should have automatically detected the PS plugin folder & added it to the list of install locations.

 

If you added an extra install location to the list using the installer's plus button, one for a previously created folder in Applications, not only would the plugins be installed in that folder in a subfolder named "Google," the installer would have created stand alone application versions of the plugins & an Uninstaller app. If you did not do that, it might be helpful to uninstall the collection using the Uninstaller app included with the DMG download & then run the installer again, adding the extra install location to get the stand alone apps installed. That folder's contents should look like this:

post-3524-0-97793100-1462359105_thumb.jpg

 

If you do that & then run one of the stand alone apps on a photo file (they should be listed as "Open with" alternatives if you right-click on a photo file in Finder), as a troubleshooting aid it would be useful to know if you still get the Demo splash screen or not.

 

You can also change the Affinity plugin search folder from the Photoshop one to this folder added to Applications, which will isolate that set of plugins (& their companion configuration files) from the set used by Photoshop. Presumably, this will tell you if somehow something to do with the installed version of PS is causing the problem.

All 3 1.10.8, & all 3 V2.4.1 Mac apps; 2020 iMac 27"; 3.8GHz i7, Radeon Pro 5700, 32GB RAM; macOS 10.15.7
Affinity Photo 
1.10.8; Affinity Designer 1.108; & all 3 V2 apps for iPad; 6th Generation iPad 32 GB; Apple Pencil; iPadOS 15.7

Link to comment
Share on other sites

You do not need to use FileBuddy or anything else other than the Nik Uninstaller to remove the files that would have any effect on running the Nik installer again after running the Nik Uninstaller. The files in your last list have nothing at all to do with Nik or plugins of any sort. None of the ones in /System/Library should be tampered with; a number of them are part of the default OS X install, & some are necessary if you use any Google services.

 

You are making this much more difficult to troubleshoot than is necessary. I strongly suggest just running the Nik Uninstaller & then running the Nik Installer app, optionally adding the extra install folder to get the stand alone apps, which can be used both for troubleshooting & whenever you do not want to launch any other app.

All 3 1.10.8, & all 3 V2.4.1 Mac apps; 2020 iMac 27"; 3.8GHz i7, Radeon Pro 5700, 32GB RAM; macOS 10.15.7
Affinity Photo 
1.10.8; Affinity Designer 1.108; & all 3 V2 apps for iPad; 6th Generation iPad 32 GB; Apple Pencil; iPadOS 15.7

Link to comment
Share on other sites

You don't have right. After using the deinstaller - Google update, Keystone and other Files are on the computer. Same vor Launch deamons and Launch agents from Google. The Uninstaller works not for a clean Drive without Google files.

Link to comment
Share on other sites

  • Staff

There's no need to create a custom folder in the Applications folder if the latest version is already installed in the Photoshop Plug-ins folder (it just creates a duplicate of what's inside the Photoshop/plug-ins folder). Affinity is able to detect and work directly with the plug-ins installed in Applications/Adobe Photoshop (version)/Plug-ins. 

 

A custom folder is only necessary when the user doesn't have Photoshop (or other host excluding Aperture which uses a different file format for the plug-ins) installed on their system. The uninstaller is always placed in the Nik Collection folder along with the stand alone versions inside the Applications folder no matter where you decide to install the plug-ins files.

 

I believe the issue here is related with a previous/older/individual installation of the plug-ins which isn't being removed completely/correctly.

 

- download the latest version (it includes an uninstaller) and double-click it to open the dmg. Make sure you don't have a previous downloaded installer file with the same name in your downloads folder just to ensure you are running the file you have just downloaded (i'm not sure if they changed its name when provided the plug-ins for free).

 

- run the uninstaller to uninstall the old version Make sure you check Remove Preferences

 

- delete any remaining files of Nik Collection from the following locations if necessary (i'm assuming you don't have any other hosts installed other than Photoshop):

  • Applications/Adobe Photoshop CC 2015/Plug-ins
  • Applications/Nik Collection
  • Macintosh HD/Library/Preferences/Google

- run the installer. It should detect your version of Photoshop

- install using the default settings

- make sure you've the correct path set in Affinity Photo Preferences, Photoshop plug-ins section: /Applications/Adobe Photoshop CC 2015/Plug-ins (assuming you have this version of Photoshop)

 

 

This is the about screen using the latest version on my systems:

 

post-59-0-70328800-1462374428_thumb.png

Link to comment
Share on other sites

I have done this some times. But it won't work. I'm not stupid.

 

post-7002-0-35624100-1462375983_thumb.png

 

Left Image is the File I downloaded by google after being a license. This file was never installed after the Clean install of my Mac.

Mid File is the Image I used for Install the Plugins. Downloaded by Google. Image Name is:

 

nikcollection-full-1.2.11

 

Right Image is the Image from your Link:

 

nikcollection-full-1.2.11-2

 

The Image has the exactly thew same Size as mine. The -2 shows, that a file with the same Name existed in the Download folder. Both Images have the same download path: https://dl.google.com/edgedl/photos/nikcollection-full-1.2.11.dmg

 

What now! Please don't repeat what I have done. This helped me not.

Link to comment
Share on other sites

You don't have right. After using the deinstaller - Google update, Keystone and other Files are on the computer. Same vor Launch deamons and Launch agents from Google. The Uninstaller works not for a clean Drive without Google files.

That is because none of these other items have anything to do with the Nik collection. The Nik Uninstaller application removes only the files installed by the companion Installer app (both of which are in the downloaded DMG) & these are the only files that need to be removed before running the installer again.

 

Your "cleaning" efforts are not needed & just unnecessarily complicate sorting this out. They may even cause other problems -- for example, File Buddy has not been updated since 2014 & the download page only claims version 10 to be "compatible with Mac OS X 10.6 Snow Leopard – 10.9 Mavericks." The value of running any of the third party "cleaning" apps is dubious to begin with -- they have been known to remove things they should not & to remove things when removal has no practical benefit other than as a marketing gimmick -- & running one that does not specifically claim to be compatible with the currently in use version of OS X is ill advised regardless of any "and later" verbiage on their web sites that may now be years out of date.

 

If nothing else, please consider that no one else has reported having to use any of these "cleaning" techniques to get the Nik collection plugins compatible with Affinity Photo to run without problems.

All 3 1.10.8, & all 3 V2.4.1 Mac apps; 2020 iMac 27"; 3.8GHz i7, Radeon Pro 5700, 32GB RAM; macOS 10.15.7
Affinity Photo 
1.10.8; Affinity Designer 1.108; & all 3 V2 apps for iPad; 6th Generation iPad 32 GB; Apple Pencil; iPadOS 15.7

Link to comment
Share on other sites

  • Staff

Hi Onlymac,

I was editing my post to include more info while you replied.

Please don't take me wrong. I was only trying to ensure you were using the latest installer/uninstaller. It wasn't intended to offend you. Sorry if it sounded that way.

I really don't know what else to suggest other than the steps i've already outlined above.

Maybe i'm missing some detail here...

Link to comment
Share on other sites

That is because none of these other items have anything to do with the Nik collection. The Nik Uninstaller application removes only the files installed by the companion Installer app (both of which are in the downloaded DMG) & these are the only files that need to be removed before running the installer again.

 

Also, ich arbeite seit nunmehr 23 Jahren mit Macs. Mit Computern habe ich seit 1978 zu tun. Etwas auf den File Buddy zu schieben, nur weil er nicht als 10.11 ausgegeben ist, ist für mich nicht  nachvollziehbar.

Der File Buddy zeigt mir nur den Inhalt der Ordner, im Gegensatz zum Finder aber auch versteckte Dateien. Order und Dateien mit besonderen Zugriffsrechten werden entsprechend markiert, und können nicht gelöscht oder bearbeitet werden. Dafür komme ich ohne Probleme direkt zu den Dateien, indem ich von File Buddy den Pfad geliefert bekomme und diesen per Mausklick in ein Finderfenster umwandeln kann. Dabei wird nichts beschädigt oder zerstört. Dateien aus dem Library wie z.B. Die Deamons und Agents werden von mir nur in den Papierkorb befördert. Erst nach einem Neustart werden die Dateien gelöscht. So wird das System nicht korrumpiert. Was soll also dieser Post.

Ich bin erfahren genug im Umgang mit Computern und habe in den 80-90igern selber programmiert (C C++, Pascal, Assembler für 8 bis 32 Bit Computer) Nach der Jahrtausendwende habe ich mich aber aus deer Szene verabschiedet.

Ich weiss wann ich ein Programm nutzen kann und wann nicht. Wenn ich mein System mit Apple eigenen Mitteln prüfe sind keine Fehler zu finden. Daher sollten Sie bei Ihren Bewertungen von Programmen wie File Buddy sich etwas zurück halten.

Hier hätte ich eher Hilfe erwartet, die Konstruktiv ist. Aber davon bin ich nicht mehr überzeugt. Gerade durch Ihre Kommentare.

Hilfreich wäre eine Programmversion die ein Debugging Protokoll generiert. So wäre es möglich, die Ursachen für die Probleme zu finden.

Bedenken Sie dies bei Ihrem nächsten Post als Advanced Member

 

​Besten Dank für die Nicht Hilfe 

Link to comment
Share on other sites

There's no need to create a custom folder in the Applications folder if the latest version is already installed in the Photoshop Plug-ins folder (it just creates a duplicate of what's inside the Photoshop/plug-ins folder).

 

That isn't entirely true, at least on my Macs. The Nik installer did not install any of the stand alone application versions into the Photoshop Plug-ins folder.

 

Also, while it should not normally make any difference, in each plugin install location each of the plugins is installed along with a duplicate but independent companion ".config" file. Using the custom folder for Affinity instead of 'sharing' with the PS one should allow the Affinity compatible plugins to run using these unmodified config files even if for some reason the config files in the PS folder are modified or damaged.

All 3 1.10.8, & all 3 V2.4.1 Mac apps; 2020 iMac 27"; 3.8GHz i7, Radeon Pro 5700, 32GB RAM; macOS 10.15.7
Affinity Photo 
1.10.8; Affinity Designer 1.108; & all 3 V2 apps for iPad; 6th Generation iPad 32 GB; Apple Pencil; iPadOS 15.7

Link to comment
Share on other sites

  • Staff

That's not what i said. I was referring to just the plug-in files in that sentence: the folder you choose when you click the plus button in the Compatible Host screen. The stand alone versions are never installed inside the Photoshop Plug-ins folder or any other custom folder (unless you change the default destination path which comes later in the installation). Please read the whole post:

"A custom folder is only necessary when the user doesn't have Photoshop (or other host excluding Aperture which uses a different file format for the plug-ins) installed on their system. The uninstaller is always placed in the Nik Collection folder along with the stand alone versions inside the Applications folder no matter where you decide to install the plug-ins files."

Link to comment
Share on other sites

Ich habe den Uninstaller aus dem Nil Collection Ordner genutzt. Ein anderes Mal den Uninstaller vom DMG File. Egal was ich nehme und was ich mache — am Ende lädt die Collection nur im Demo Modus. Affinity hat Probleme beim erfassen der Freischaltung. Da ich nicht weis, welche Datei für die Freischaltung benötigt wird habe ich keine Chance hier etwas zu tun. Die Rechte kann man ja Dank Apple nicht mehr reparieren. Aber genau so ein Problem liegt hier wohl vor. Wie also weiter?

 

Bitte nicht alles von Vorn herbeten, das bringt nichts. Ich benötige hier echte Hilfe ohne Gebetsmühlenartiges Herbeten von 0815 Sachen. Ich verzweifle langsam an dem Service und bin mir nicht sicher ob Sie mir überhaupt helfen können, wenn Sie ständig mein Handeln in Frage stellen. Ich bin kein Laie und auch kein Amateur, werde aber so behandelt.

Link to comment
Share on other sites

Onlymac,

 

In a previous post you asked, "Is there any File that must be deleted?" My comments about cleaning files were in response to that.

 

Regarding File Buddy in particular, it is not needed to remove any file associated with the Nik collection & it does make it possible to confuse unrelated items with those files. It should be sufficient (& much simpler) to run the Nik uninstaller, per the instructions Google provides here.

All 3 1.10.8, & all 3 V2.4.1 Mac apps; 2020 iMac 27"; 3.8GHz i7, Radeon Pro 5700, 32GB RAM; macOS 10.15.7
Affinity Photo 
1.10.8; Affinity Designer 1.108; & all 3 V2 apps for iPad; 6th Generation iPad 32 GB; Apple Pencil; iPadOS 15.7

Link to comment
Share on other sites

Schön und Gut, aber die Deinstallierei und Installierei ändert nichts an dem Ergebnis, das die Plugins nicht richtig funktionieren. Es wird Zeit mal etwas besseres zu bieten als dies.

Ich wollte weg von Photoshop - nun muss ich einsehen, dass das nicht geht. Probleme mit Programmen können auftreten, aber ein Produkt ist nur so gut wie sein Service. Letzterer ist hier leider nicht in der Lage zu helfen. Also muss ich den Kauf von Affinity Photo als Fehlkauf einschätzen. Nicht, weil das Programm schlecht ist, sondern weil man Probleme nicht erkennen will und keine sinnvolle Strategie zur Suche und Beseitigung von Problemen zu haben scheint. Das ist traurig wird aber im App Store für andere Kunden hinterlegt werden.

Link to comment
Share on other sites

That's not what i said. I was referring to just the plug-in files in that sentence: the folder you choose when you click the plus button in the Compatible Host screen.

I know that. It is just that there seems to be a lot of confusion about what is installed where, so I wanted to point out the differences, & why for some users it might be desirable to use a custom folder for Affinity rather than sharing with the PS plugin one.

 

I did that both to get the stand alone apps & so that I could delete from the custom folder the plugins that are not compatible with Affinity. That prevents the unusable ones from cluttering up the Affinity plugins menu & the frustration my accidentally selecting one of them due to my sloppy mouse-work sometimes causes.  :wacko:

 

Yet another potential benefit of doing this is if at some time in the future some of us decide to uninstall the PS (or in my case the PSE) app completely from our systems, it won't matter if the PS plug-ins folder is deleted along with the rest of the PS baggage.

 

It is just a personal choice, but in general wherever possible I try to avoid different apps sharing any of the same support folders, particularly if they come from different developers. The downside of that is of course more file space will be used but I have lots of unused file space available so for me that is not a concern. For others it might be.

All 3 1.10.8, & all 3 V2.4.1 Mac apps; 2020 iMac 27"; 3.8GHz i7, Radeon Pro 5700, 32GB RAM; macOS 10.15.7
Affinity Photo 
1.10.8; Affinity Designer 1.108; & all 3 V2 apps for iPad; 6th Generation iPad 32 GB; Apple Pencil; iPadOS 15.7

Link to comment
Share on other sites

Onlymac,

 

At this point all I can say is the three Nik plugins known to be fully compatible with AP (Analog Efex Pro 2, Color Efex Pro 4, & Silver Efex Pro 2 all work without any issues on my Macs running OS X 10.11.4, & the partially compatible HDR Efex Pro 2 plugin works to the extent MEB explained in the Google Nik Collection is now free for everyone news topic.

 

The same seems to be true for most other AP users. When it has not, following the troubleshooting steps discussed in detail there & in several other discussions seems to have resolved the issue for almost everyone, all without having to resort to any of the measures you have tried.

 

I have made my best effort to understand what might be different about your system & on that basis suggested what I think might help resolve this issue for you, but if you do not want to try that there is nothing else I can think of to contribute. I hope you are eventually able to resolve this by some other method & if so, that you will post it so we all can learn from it.

All 3 1.10.8, & all 3 V2.4.1 Mac apps; 2020 iMac 27"; 3.8GHz i7, Radeon Pro 5700, 32GB RAM; macOS 10.15.7
Affinity Photo 
1.10.8; Affinity Designer 1.108; & all 3 V2 apps for iPad; 6th Generation iPad 32 GB; Apple Pencil; iPadOS 15.7

Link to comment
Share on other sites

Things I kn ow today is. Help can't find here. Only deinstall and install is no help. The Plugins work as Stand Alone and with Photoshop. The Color Efex known as useable brings only the buy or Demo mode. I Think the problem is not the Plugin, the problem is Affinity Photo and the Handling from Plugins. I want to leave Adobe and Photoshop bau the reality is, that Affinity Photo in the actual version is no replacement for Photoshop. So I'll write in the App-Store. Users should know about the quality from the service. The application is so good like the service, and the service is bad.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • 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.