Herojas93 Posted April 21, 2023 Posted April 21, 2023 Hi guys, I have noticed, after update to beta 8, that Studiolink doesn't work. I think could be because the version number of the APP's with the new betas only shows 1769, no 2.1.0.1769 as publisher do. This can make publisher don't recognise photo and designer. Quote
Staff Patrick Connor Posted April 21, 2023 Staff Posted April 21, 2023 Really sorry, we will sort this Quote Patrick Connor Serif Europe Ltd Latest V2 releases on each platform Help make our apps better by joining our beta program! "There is nothing noble in being superior to your fellow man. True nobility lies in being superior to your previous self." W. L. Sheldon
tudor Posted April 21, 2023 Posted April 21, 2023 30 minutes ago, anto said: I can't open projects. You can still open any file in any of the three apps, just not via StudioLink. Quote
Staff Pauls Posted April 21, 2023 Staff Posted April 21, 2023 @anto - which ICC profiles ? If you imported any into publisher regardless of the persona you will also need to import those into Photo/Designer Quote
Staff Pauls Posted April 21, 2023 Staff Posted April 21, 2023 you will need to import the ICC profile into photo also Quote
Staff Sean P Posted April 21, 2023 Staff Posted April 21, 2023 2 minutes ago, anto said: WAN-Ifranewspaper26v5. Publisher and Photo Persona have it. Photo does not has. Had you used Import ICC Profile inside Photo Persona's File Menu? Does this profile appear in Photo if you create a CMYK document? Quote
Staff Sean P Posted April 21, 2023 Staff Posted April 21, 2023 8 minutes ago, anto said: I'll try to do it. I don't remember how I did it for Publisher. Currently using Import ICC Profile on the File Menu is importing them into an App specific folder instead of a group folder shared amongst all Affinity apps. So if you had done that, then that would be why Photo standalone is unable to see then. We'll get this logged. Quote
Staff Affinity Info Bot Posted April 26, 2023 Staff Posted April 26, 2023 The issue "StudioLink fails to work on macOS" (REF: AFB-7653) has been fixed by the developers in internal build "2.1.0.1781". This fix should soon be available as a customer beta and is planned for inclusion in the next customer release. Customer beta builds are announced here and you can participate by following these instructions. If you still experience this problem once you are using that build version (or later) please reply to this thread including @Serif Info Bot to notify us. Quote
Recommended Posts
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.