Gigiga

I have currently the same question due to a policy change in my company and would like to get a more detailed answer because I guess a little detail in @SFurniss answer is still unclear. At least for me. I hold privately bought licenses of V1 that I use for my side hustle since, covered by the EULA as stated. I have a company owned Mac that I'm allowed to use privately. I am bound by the companies policy to be the only user of that machine. In the past, there were no regulations of privately licensed software in my company at all. Now that changed and to make a clean cut all privately owned software must be either GNU, MIT or whatever free to use for commercial use OR it must be a business license if the software vendor issues a private and a business model OR (which brings me to this specific case) the license terms include the fact that it is not my personal computer BUT I am the only one using it thus I can continue to use affinity products purchased privately for my side hustle. So your answer would still be "Yes you are still allowed to use privatly purchased affinity software on your work computer as you're still the only one using it despite you don't own the machine the software is running on." is that correct?

I cannot belive I found THIS from 2019 in 2023 to be the solution. The more I do side projects with affinity the more I tend to go back to adobe. THIS is so basic it needs to be in the software from the start. What is so hard about that? Most Books are PUR glue bound these days, especially print on demand products. I know how books are bound in the old fashioned way, and sure a software also needs to address this technique but come on guys really?

This bug costs designers money, I’m not really thrilled this is no priority internally.

Is this fixed in 2.0? Looking at you @NathanC

Additonal information to that particular problem. I only had the issue with on file, very simple file nothing complicated. Now I have a similar issue but not quite the same. I have a file with several placed images of on PDF document for printing and cutting a small card game. So far so good. Sometimes now Publisher just decides to freeze and do nothing at all. No restart no nothing, just the rainbow ball of death. Again, nothing fancy. A 54 page PDF placed in 8 A3 pages. I did far more huge files with this in InDesign and never problems. Whole books with 400 pages and illustrations but never ever were the files as simple as this and I had that many problems. EDIT: Fixed it, it was the Live Error Check. Dump this feature if it causes the app to completely stop working.

No Tablet, laptop is in shell mode so no trackpad, mouse wheel is assigned another action. What does everyone working with text and a layout tool have? Right, a keyboard. If only one could make use of that easily... My point is, there is a proven, widely used command for that specific use case around for decades in the dominant tools for designers. Just not in affinity. Why? I'm not working as a designer anymore, but when I work in publisher for example, 20 years of using Quark, Indesign etc. WITH this command lets you do exactly that automatically. Every time my Finger finds the alt key and it does not work as described makes me roll my eyes at this. Some things are so little to implement but have such a huge impact on proven and standarized workflows.

+1 This should be a basic functionality. The way it is now really interrupts the workflow.

I have the same problem with another own file I just created. Nothing fancy, two A3 pages with some text and very simple vector illustrations and two high res images. After re-open I loose the last 6-8 steps and after re-doing everything it crashes again after just a few actions. 10.1.6 on latest Ventura (13.3.1 (a)) Macbook Pro 2018 Please don't do this affinity. I tried the v2 suite it had nothing I needed, please don't start annoying users into buying your latest software.

For everyone that has the exact same problem, here is how you work around that: Don't use adjustment layers over the spot color layer(s) AT ALL!!! It will always change the spot color to CMYK no matter what you change in Export settings. My solution: Instead merge the adjustment layer(s) and the layer you want to adjust with them together (Layers > Merge Down) Solution from this thread Still not the complete solution! When exporting, change the Rasterize option in the export settings to "nothing", Solution from this thread Works now and will send it to the printer again. Again @affinity, these things can kill your reputation as an adobe alternative. I hope you know that.

WTF affinity? I just got a flyer back from the printer that had spot colors on the back and the front. Only the spot color from the back made it in the print because obviously when you have a masked layer over a spot color layer it is also turned into CMYK. Guys that is a basic functionality and I am pissed big time. Exporting the PDF without the masked layer gets me the spot color on the front page. Guys this is really NOT what I look for when working with designer. The Spot Color management ist quirky and I can work my way around it, but stop making the software convert spot colors to CMYK without telling me. At least offer a decent solution for color separation with PDFs so I don't have to rely on Acrobat Pro. 150 bucks down the drain. Thanks for nothing. Back=golden spot color Front=Cyan should be same gold color EDIT: It gets better: Obviously there is a problem with transparencies. When I get rid of the masks and rasterize everything, guess what areas are still in f***ng CMYK? magenta=Spot color or better said whats left of it. This is a nightmare guys. I really consider switching again...

My EXACT state of mind right now. The described use of Bridge and AP is nothing close to what I expected. I could use the Finder to do this. A bit sarcastic I know but basically not what I look for when I want a Lightroom replacement. Would gladly through some money at Adobe for a non-suscription version of Lightroom.

It is impressive how the workarounds gather here in such short time. But please lets not forget, that this shouldn't be the standard! I expect a defined behaviour (spot, overprint) to export without any side effects because a pixel mask is involved or I have a pixel layer which is using the spot color. At least give us a warning like "Dear User, your spot color will be rasterized back to cmyk because the software currently can't render this combination into a X Standard PDF" Again, I had a whole 200€ printjob partly ruined because of this. Yes I could have check the seperation preview but I didn't. That was caused by my trust in this software, bc it worked before and why shouldn't it work now. Plus the software displays everything correct! I thought I was crazy because the document (colors, overprinting etc.) in publisher was completely correct from my PoV but the seperation preview of the printfile said "no it is not!" I am pretty experienced (15 years now) but it took me a while to figure this out. This should never have find its way into any release ever, period. PLEASE FIX THIS ASAP!

I'm pretty puzzled to learn this the hard way by a completely ruined printjob. Same thing with a spot color in a pixel mask. Even a pixel layer in that very spot color with all the correct settings does not export as spot and overprinting but in regular cmyk (I know the spot color works correct, bc the same spot color is used in another path object without mask and that printed correctly) I was just about to get serious with using publisher for regular projects. But now I start to get suspicious again. I really like the workflow, especially the personas in Publisher. Only one app open, what a dream. And then this ruined print job lucky me it was "only" 200€...

I don't think a standalone app is necessary to do what Lightroom and others roughly do. A proper persona in Affinity Photo and a lot of the work I do with Lightroom is possible. Yes virtual copies are nice but personally I don't want to have a catalogue based raw lib ever again. I just need a good integration in a program like Affinity Photo tbh. So yes, please go ahead and start improve the apps you have. For me working with only one app but really in three, like possible in publisher, is THE only thing I ever wanted to do since 1995. It's amazing to just be able to switch personas instead of programs. I believe this is one way that might be the affinity way to solve this demand without creating something standalone like a full DAM.

+1