Jump to content


  • Content Count

  • Joined

  • Last visited

  1. I'm surprised that this thread has been allowed to continue. Serif/Affinity are obviously not in the software business as a hobby - it is a business and no doubt like any business is intended to show a profit. That being the case, there's no doubt in my opinion that the developers will introduce new features, etc on a soon as possible basis as there's every incentive for them to do so. If, although I very much doubt it they manage to find a way of opening INDD files directly with Publisher then so be it although as that file format is constantly, or so it appears to me, to be a moving Adobe target it will be a no go in my book. IDML - well maybe but going on about it day after day isn't going to make it happen any faster. Publisher is what it is and for now that's what it is.
  2. Something not consistent with this error. I've just opened a 495mb PDF file - it was camera ready for the printer. No problems. Also open were 5 other PDF files - all approx 5mb in size. Windows task manager reports 8gb memory being used. My PC has 16gb memory. This is something that needs reporting directly to the Affinity team as obviously mileage is varying.
  3. Really all depends upon circumstances. Although I've purchased Publisher, it was a bargain price I will still be using ID. If/when there is IDML import feature then no doubt I'll be using Publisher more often at that time. For now though, unfortunately I don't think we'll ever see a pure INDD import especially as Adobe manage to keep tweaking the thing at their convenience. Remember how long it took Adobe to overcome QExpress. Was it v4 until InDesign managed to gain some traction and they certainly have far more resources behind them than Serif.
  4. So if like myself you need to occasionally use ID then you may as well use it full time. I like AP and would join in the high fives if it managed to break the Adobe 'monopoly' but for now I cannot see any advantage to changing if I need to fire up ID from time to time. May as well just keep using it. Maybe one day......
  5. Hence I really cannot see at this stage AP making much of a dent in the professional market whatever folks think of Adobe and I'm certainly no fan of them. If you have clients sending you *.indd files they're not going to suddenly change their habits to supply *.idml. After all, they are the clients. So for now AP is for the hobbyist, occasional user or where you can just supply *.pdf. Just my thinking but in the same way that Photoshop is overkill the fact is that it is considered as the market leader and if that's what clients require then unfortunately you have to go with the flow at this stage or risk upsetting those that indirectly pay your rent. Maybe at some stage AP will be fully accepted but for now we're just going to have to bite the bullet unfortunately and in my view I think that's how it's going to be for the foreseeable future.
  6. Yes it would be nice to open *.indd files but in my book that's not going to happen especially with a first release and possibly/probably never. The best anyone can hope for is an import of *idml files which isn't a bad compromise. So for now AP is really just for occasional use and certainly at this stage not ready for the professional market especially where a client uses InDesign. In my opinion to ask them (the client) to supply an idml file is a no go at this stage so it's either continue to cough up those monthly 'rip off' fees for CC or carry on with CS6. I'm reminded just how long it took Adobe to overhaul Quark as those early day InDesign programs simply didn't make much impact. Adobe persevered whereas Quark sat back on their laurels. So we're looking at a few years down the line sadly before AP becomes mainstream. Maybe though Affinity are not after the InDesign market as Adobe would be a big nut to crack.
  7. I have 900+ fonts installed and load time is under 4 seconds.
  8. I never found it was a font issue in my case but an excess of *.icc and *.icm monitor files being loaded. Long winded but the solution I found is detailed about 6 above this post. Hope it helps.
  9. As the Mac Affinity version is fast then effectively it's not the SSD. Out of my depth here but using a VM within Win10 the program speed varies with the memory allocated as often the defaults are far too low unless you are running with say just 4GB. As I have 16GB I always increase the ram available for the VM and that speeds things up considerably. Hopefully someone more knowledgeable than myself will be along shortly.
  10. No Mac expert here I'm afraid but what are you using to get into Win10 - Boot Camp, Parallels, etc? Have you tried running the Mac version of Photo or Designer? - if so was it still slow? Doubt if the SSD has anything to do with it.
  11. Pardon me for hi-jacking this thread and thanks for explaining things Mark. The problem however is over time, potentially as more and more ICC profiles may be installed either by Microsoft or other software vendors then effectively you are back to square one. PS also loads these profiles but it doesn't appear to slow down the start up time. Many of my (refugee) ICC profiles were installed by another design software vendor when I was testing their product. Program uninstalled but ICC profiles left behind. Affinity is a fine product for my purposes and certainly more cost effective than PS although no doubt that is a moot point depending upon individual's requirements. The slow load if/when it occurs is a killer and I would have felt this would have been high on the list for the developers to solve.
  12. At last - a solution my end albeit long winded but had a couple of hours free. Compared the beta log file on my Win10 regular machine with that on the pre-release Win10. Deleted from the regular machine all *.icm, *.icc, etc files from the system that were not listed in the beta log file from the pre-release Win 10 - many were in the Adobe and Adobe Common Files section. Restarted and hey presto, both released and beta versions of Affinity load up within 5 seconds. So that's where the problem is my end. Tested other programs on the system and they are all working as usual. So probably the icm and icc files are just refugees from uninstalled old programs. Maybe a solution for others although as these *.icm and *.icc files do not affect load times for other products then maybe the Affinity developers should look at this issue seriously.
  13. Reporting back (again). Installed Photo Beta - same problem reference load time. Difference is Beta generates a log file (attached) and there are a number of colour profiles that do not apply to my other bits of 'testing' - laptop, Win10 pre-release, etc. For example, the log file shows ScanSnap which relates to the sheet feeder scanner which is not set up to work with the laptop and Win10 beta software. Could these be slowing down the startup process? Possibly of equal importance, how do I go about 'instructing' Photo to ignore these when starting? Any input appreciated. Log.txt **further update. Fired up Win10 pre-release and installed Scansnap scanner software. Started Photo beta and it started within 5 seconds as opposed to 30-40 seconds. Attached further log file for the pre-release installation. Now at a total loss and will need someone more experienced than myself as this is out of my pay grade. Log Win10 pre-release.txt
  14. Thank you Mark. I have uninstalled and reinstalled the program - you never know but made no difference. What I have noticed in Task Manager is the slow allocation to memory whilst opening with relatively little CPU utilization. Other programs seem to grab the memory instantly. Having said that, AP loads ultra fast with the insider Win10 build so it looks as though it's machine specific to me rather than the program. JPG attached. **Installed the Photo Beta on Win7 x64 and initially would not run. Required Aero Theme to be enabled. Once enabled it fired up within 5 seconds**
  • 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.