Jump to content
Zbigg

Images linked or embedded?

Recommended Posts

As I posted elsewhere on this forum, there is an interesting twist that I hadn't seen coming.

Because of StudioLink, I have found I don't need to link a folder full of PSD files. That's an older way of looking at it, which is not always necessary now. A JPEG stock image can live in the Publisher file, with all live effects applied, and may therefore not increase the file size that much. I haven't fully tested this but I'm just putting this comment here because Affinity are going in a whole new direction.

I still think full linking without massively increasing the file size should be an option, because that is the way people are used to working. But I'm starting to rethink my approach.

Share this post


Link to post
Share on other sites
3 hours ago, OzNate said:

Because of StudioLink, I have found I don't need to link a folder full of PSD files. That's an older way of looking at it, which is not always necessary now. A JPEG stock image can live in the Publisher file, with all live effects applied, and may therefore not increase the file size that much. I haven't fully tested this but I'm just putting this comment here because Affinity are going in a whole new direction.

I'm not sure exactly what you mean by the image "living in" the Publisher file.

I wouldn't say that a linked image is "in" the file. An embedded image is certainly "in" the file, and if it's a JPEG I suppose it may not increase the file size as much as a PSD would.

But then I'm unsure what you mean by "with all live effects applied." Yes, all the effects are applied, but as it's a JPEG they are no longer "live".

Also, I find it unfortunate that Serif does not allow editing of an embedded image file. You can still edit an embedded document file (PDF, PSD, .afphoto, .svg, etc.) and have access to all the layers, and make changes that are local to the Publisher document. But once you embed an image file (JPG, PNG, TIFF) you have a flattened copy, and the only editing you can do is via editing the Publisher page. You can't get the embedded image into its own tab for full (even if local) editing.


-- Walt

Windows 10 Home, version 1903 (18362.356), 16GB memory, Intel Core i7-6700K @ 4.00Gz, GeForce GTX 970
Affinity Photo 1.7.3.481 and 1.8.0.486 Beta   / Affinity Designer 1.7.3.481 and 1.8.0.486 Beta  / Affinity Publisher 1.7.3.481 and 1.8.0.499 Beta

Share this post


Link to post
Share on other sites
20 hours ago, walt.farrell said:

I'm not sure exactly what you mean by the image "living in" the Publisher file.

Sorry, I should use precise language. Yes, I meant embedded.

21 hours ago, walt.farrell said:

Also, I find it unfortunate that Serif does not allow editing of an embedded image file.

I see what you mean. It would be useful to be able to create an embedded document file out of an embedded image file.

Anyway I am further experimenting with embedding JPEGs and using the basic functionality. With Photo persona you can pretty much do anything you want.

Share this post


Link to post
Share on other sites
On 7/8/2019 at 7:51 AM, walt.farrell said:

I'm not sure exactly what you mean by the image "living in" the Publisher file.

The affinity file format, which is universal across all 3 apps, allows full editing of all raster and vector items from directly within the document you're working in. .afdesign, .afpub and .afphoto are actually all the same format, the only reason there are separate extensions is so the OS knows which app to open when the file is double clicked. They're completely interchangeable.

Back in the dark ages of adobe, if you needed to mask an image to make some alpha transparency, you'd have to go into photoshop and add the mask, then link the photoshop file in your indesign layout... because you CANT do that in inDesign. If you needed to adjust your mask, you'd need to edit the linked file and adjust the mask, then save, update links in indesign and keep working...

Affinity's shared file format and studiolink simply embed the raster files directly into your document so you can actually make those edits inline. You don't need to link a vector logo to your page layout anymore because you can actually make all the vector edits directly on your layout with a full suite of tools from Designer. You don't need to link a photo with 5 non-destructible effects and a mask to your document anymore because those effect layers can be done directly within the page layout layer set and remain fully editable while you work. 

In Adobe, there is zero real cross compatibility across your apps. The ONLY WAY to add a photoshop file to illustrator or indesign would be to link it or embed it, because you have to edit it externally, the layers cannot carry over. There's simply no other option, you have to link to maintain editability. 

In affinity, if you create a 6 layer document in photo, and open it in publisher or designer, it just opens... all layers/effects/masks/vectors/rasters/text boxes and literally everything carries over between apps. The exact same layers, no conversion, no loss, no STUPID SMART OBJECTS. There isn't a need for linking anymore because your edits can all be done in the same file across all apps. 

And at the end... you still either have a 7mb indesign file with a 500mb packaged file folder, or a 507mb AfPublisher file.

I personally hate linking, I work from a shared dropbox as a department and every time somebody opens a file, they relink all the files to their local computer and it breaks all the links the next time I open the file (since adobe doesnt use adjacent linking, UHG!)... or somebody modifies a logo with their own tagline and saves over the original... or somebody changes the file name of an image and it breaks across a hundred different files.

Linking is a mess, it's a product of an old way of thinking and from an era when hard drives only had a few gigs and transferring online was done in kbps. I can upload a 500mb document in about 15 seconds on my work connection, everyone has 2 tb hard drives... for most pro's space and bandwidth are no longer issues. It's time for linking to DIE! That's just my opinion, but im a forward thinker.

Share this post


Link to post
Share on other sites
On 7/8/2019 at 7:51 AM, walt.farrell said:

But once you embed an image file (JPG, PNG, TIFF) you have a flattened copy, and the only editing you can do is via editing the Publisher page. You can't get the embedded image into its own tab for full (even if local) editing.

Try this, drop an image into your publisher document, then click the PHOTO studiolink icon on the top left of your app window (assuming you own all 3 apps). All your tools will inline turn into Affinity Photo, no app switching, full AfPhoto tools directly in your page layout file... now work with the image. Erase some pixels, make a mask, add some color adjustment layers, use the clone stamper.... Now click the PUBLISHER studiolink icon to get back to page layout to continue working. The layers don't flatten, you don't lose editability. 

You have all your editing tools in one app with studio link, full editing capability without the need for app switching, linked files or all the convoluted extra steps. you don't need a separate afPhoto file for an image because the full editing capability is available directly in your layout.  Its a whole new way of working and thinking about how a layout app can work.

Share this post


Link to post
Share on other sites
1 hour ago, TonyO said:

Try this, drop an image into your publisher document, then click the PHOTO studiolink icon on the top left of your app window (assuming you own all 3 apps). All your tools will inline turn into Affinity Photo, no app switching, full AfPhoto tools directly in your page layout file... now work with the image.

Oh, I know that, Tony.

But you are working on the Publisher page, not just on the photo itself. If you could get it opened into its own tab as you could if it was linked, and as you used to be able to do in the Publisher beta for embedded images, it would be easier.

There would be no chance of messing up the rest of the page content.


-- Walt

Windows 10 Home, version 1903 (18362.356), 16GB memory, Intel Core i7-6700K @ 4.00Gz, GeForce GTX 970
Affinity Photo 1.7.3.481 and 1.8.0.486 Beta   / Affinity Designer 1.7.3.481 and 1.8.0.486 Beta  / Affinity Publisher 1.7.3.481 and 1.8.0.499 Beta

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×

Important Information

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.