Thomas_A

I have copied the file to the desktop but the crashing continues. By the way, it most likely is related to linked items - the files I try to open and then crash all have linked documents in them. This particular file (the one from the crash dumps) has two layers of linked documents (meaning it contains a linked file which by itself contains a linked file). Just out of curiosity I opened the middle tier file which only contains one linked file and this one opens normally.

Publisher crashes immediately upon opening existing files crash report ...a713.dmp is from Publisher v. 1.10.0.1127 the same problem persists with the latest beta version crash report ...3678.dmp is from Publisher BETA v. 1.10.0.1138 1f8bef8c-ae05-4fc1-9362-e78aad89a713.dmp 6b2f457d-8848-4b13-9468-75d5ed463678.dmp

I have not yet figured out when the crash occurs. Sometimes it crashes after launching the print dialog, some other time it just crashes with just a document open. Crash dumps attached a1259ae5-967f-41c0-bb02-633e6ffc8076.dmp ba1dbcac-6b1f-4910-abbc-312b967f5f9c.dmp

Personally I would not bet on that...probably by the time v2 of Affinity apps ship, Windows 7 is no longer supported by Microsoft (14.1.2020) and I would doubt that a software developer would continue to support an OS that is unsupported by its developer.

I meant .indd, but my comment was rather sarcastic (sorry if I did a bad job at that...). There are so many threads like this one, where someone complains about not being able to "work" on Indesign files and it is usually because they think Serif needs to provide such a feature in APub, otherwise the product will just simply be a failure. I don´t see it that way - and Serif will get my money the day they release Publisher because I personally think that it is a great product. Some sort of interchangeability would be great of course - but then the next problem will be that APub and InDesign will probably not render everything exactly the same - and the complaints will start again.

I personally am sure that Serif will succeed with Affinity Publisher. They will probably not succeed with customers/parts of the pro market that want full Adobe compatibility (read/write indd) without needing to pay for the Adobe software. Adobe products have been adopted at large scale for many years, even decades. They are the 200-pound gorilla in the room and in many regards, Industry standard. I don´t believe that the driving force behind the Affinity range of software is to throw Adobe from the throne but to create modern software that pleases a wide range of customers. Just my 2 cts...

from what I understand, the Affinity range of software was born because Serif wanted to start over with modern 64-bit applications, leaving all the old baggage behind. I don't believe they could/would want to invest engineering time into creating a 32-bit version (literaly going back in time...). Another thing to keep in mind with 32-bit systems is RAM - a typical 32-bit system supports 4GB of which probably 3,5 (max) are usable. If you're lucky, an application on that system is going to have 1,5 GB available for use. Now immagine you start using an application like Publisher...that system would probably be using the page file quite heavily and the whole system would come to a crawl. No need to go back to this in 2018/2019. That Creative suite CS5 was released in 2010 and might still run on Windows 7 which become unsupported in early 2020. I understand that you would like to be able to use a modern application on your system but I don't see any changes that anybody could make a good business case to present to Serif about creating a 32-bit version of their apps. Just my 2cts...

Yes, it is as I descibed. In the HP printer driver, there is only the selection of sRGB, AdobeRGB or None (no ICC prifiles can be selected).

I have an issue with color management printing from AD where the printed color is not what I would expect: The document is set to AdobeRGB, there are some red shapes (RGB 255;0;0) and a small image - printing to an HP CLJ M452. Color management is turned off in the printer driver. In the print dialog under color management, I´ve chosen "Color Handling: Performed by App" and my ICC profile for the paper type in question. The resulting print is shifted to orange instead of the pure red defined in the document. When I print the document by letting the printer driver manage color (and selecting AdobeRGB in the print driver), the result is as expected. I would have do some more tests but from what I see with this document, there seems to be something fishy about the color management handling in AD. The ICC profile is OK - I use it successfully in various other apps (Indesign, Lightroom, Photoshop). Any ideas?

When opening a file without embedded colour profile, the best guess an application can make is assuming it is in sRGB. The profiles you have set in the preferences are not RGB color spaces but your monitors calibration profile. You should set an RGB color space like sRGB,AdobeRGB or ProfotoRGB. The application uses your monitor calibration profile to correctly display the colours on your monitor.

I've had the same question...I though I could create an account first and supply my EU VAT-ID so the purchase could be done without any VAT applied (Intra-Community purchase). Is this possible?

thank you! I was looking in the wrong places for it... :huh: I like the way this is implemented with a softproof layer.

I do a lot of CMYK conversions in PS and use softproofing all the time to tweak the images before converting to a CMYK icc profile. Did I miss this in AP beta or is this feature not there yet?

When I open a RAW file into Photo, or create a panorama from RAWs, the resulting image is always in sRGB. In Preferences-Colour Profiles I have set both RGB colour spaces to ProPhotoRGB. Am I missing some setting along the way (like in CameraRAW where you can set the colour space) or how can this be done? Thanks! P.S. I'm very impressed with this beta version! Please don't ever sell your company so Adobe or so... ;-)