StudioLink doesn’t work

[XaTha]

Hi,

when trying to use StudioLink in Publisher I get this error message (see below). How do I get it to work properly?

FYI:

• I do have all three applications licensed and installed (version 2.0.3)
• Im working on Windows 10
• I used the *.msix files for installation
• I tried reboot, reinstall and opening Designer and Photo before opening Publisher
• upgrading to 2.1 is currently no option

Can anybody help me?

Thanks
X.

[walt.farrell]

40 minutes ago, XaTha said:

upgrading to 2.1 is currently no option

Why is it not an option? (Also, even 2.0.3 is downlevel. 2.0.4 was the last update to 2.0.)

Also, please use Help > About or the Account dialog, and show us exactly what version of each of the three applications you have installed. They must all be 2.0.something, or 2.1.something.

[XaTha]

We can’t upgrade yet, because 2.1 would not be available for everybody at our company right now and because you can’t open files created in 2.1 in 2.0 (we need to be able to work on the same d ocuments t ogether).

 

[walt.farrell]

1 hour ago, XaTha said:

We can’t upgrade yet, because 2.1 would not be available for everybody at our company right now

Thanks. I'm still a bit confused, as anyone who has 2.0 can freely update to 2.1. But you're right about compatibility between 2.1 and 2.0 being problematic if you don't have everyone update at the same time.

 

Still, in my opinion it would be better to have them update to 2.0.4, which is fully compatible with 2.0.3. And in your case it may be required. One of the fixes in 2.0.4 allowed StudioLink to work for users who installed using Business licenses, rather than Personal licenses.

As you've mentioned having a number of users in your team, I'll guess you do have Business licenses, and you'll probably need 2.0.4 to make StudioLink work.

Release Notes for Publisher 2.0.4:

https://forum.affinity.serif.com/index.php?/topic/179728-affinity-publisher-2-for-windows-204/

 

 

[XaTha]

16 hours ago, walt.farrell said:

Thanks. I'm still a bit confused, as anyone who has 2.0 can freely update to 2.1. But you're right about compatibility between 2.1 and 2.0 being problematic if you don't have everyone update at the same time.

 

Still, in my opinion it would be better to have them update to 2.0.4, which is fully compatible with 2.0.3. And in your case it may be required. One of the fixes in 2.0.4 allowed StudioLink to work for users who installed using Business licenses, rather than Personal licenses.

As you've mentioned having a number of users in your team, I'll guess you do have Business licenses, and you'll probably need 2.0.4 to make StudioLink work.

Release Notes for Publisher 2.0.4:

https://forum.affinity.serif.com/index.php?/topic/179728-affinity-publisher-2-for-windows-204/

 

 

That did it!!! Thank you, Walt 😍!!!

[walt.farrell]

You're welcome. Glad it worked  

[Gerald Lee Wall]

I am getting the same error message when trying to link from Publisher 2.30 to Photo 2.30. All my versions are 2.30 and MSIX files. They use to work. now they dont?? I also reloaded, reupdate, and reinstall but still can not link. What the heck??

[walt.farrell]

@Gerald Lee Wall: have you run each of the applications since you upgraded to 2.3? 

[Gerald Lee Wall]

Yes. I saw I accidently hit the shortcut key to "Hide studio" That fixed it but I had reloaded Publisher 2 and now could not connect to the photo persona from publisher. I saw that I had t copies of Photoshop installed and  i deleted the older one and now the photo persona works  but for some reason Liquify persona is missing. The only personas I have in all three ore Designer, photo and publisher. No Liqufy or any others? Any clue?

[Old Bruce]

3 minutes ago, Gerald Lee Wall said:

... now the photo persona works  but for some reason Liquify persona is missing. The only personas I have in all three ore Designer, photo and publisher. No Liqufy or any others? Any clue?

In Publisher you have access to the 3 applications Publisher, Designer, and Photo. Not the "sub" personas which are available in Designer*, and Photo**. To access those you have to use the Designer or Photo applications.

 

* (Pixel and Export)

** (Liquify, Develop, Tone Mapping, and Export)

[Gerald Lee Wall]

So switched to Photo from Publisher but the Liquify does not appear.

 

[walt.farrell]

10 minutes ago, Gerald Lee Wall said:

So switched to Photo from Publisher but the Liquify does not appear.

 

Switched to the Photo application (File > Edit in Photo...) or simply switched to the Photo Persona in the Publisher application?

If you're in the Photo application, you should have the Liquify Persona available there:

[R C-R]

18 minutes ago, Gerald Lee Wall said:

So switched to Photo from Publisher but the Liquify does not appear.

Did you switch to the Photo Persona in Publisher or to the actual Affinity Photo application, for example by using File > Edit in Photo... in Publisher?

Ha! Walt beat me to it by a few seconds.

[Gerald Lee Wall]

Yeah I can edit it but I thought for sure I use to use liquefy from the phot persona!

[R C-R]

3 minutes ago, Gerald Lee Wall said:

Yeah I can edit it but I thought for sure I use to use liquefy from the phot persona!

AFAIK, there has never been a Liquify Persona in any Affinity app besides Affinity Photo. Same for the Develop & Tone Mapping Personas. Also Affinity Publisher lacks the dedicated Export Persona that both Affinity Photo & Affinity Designer provide.

Are you maybe thinking about some of the Filters > Distort options in APub's Photo Persona?

[walt.farrell]

13 minutes ago, Gerald Lee Wall said:

Yeah I can edit it but I thought for sure I use to use liquefy from the phot persona!

You can use a Liquify Live Filter from the Photo Persona of the Photo application.

And there was a time when, in the Photo Persona of Publisher, you could also use the Liquify Live Filter, which is similar to using the Liquify Persona in the Photo application. But that was a bug because the Liquify Live Filter requires the Liquify Persona, which is only in the Photo application, and that bug has been fixed.

For more,