Jump to content

Recommended Posts

Posted

304484742_ScreenShot2018-12-09at2_06_51PM.thumb.png.1a0bdcd70c0dabc1758dda36d0dc86fe.pngI have been editing a pdf which I had saved in InDesign a few years ago and which I have saved as an .afpub file.   Everything was going swimmingly    Saved, and Saved As several times.    Today I decided to adjust one of the photographs in Affinity Photo.    Worked just fine.   Imported it into the .afpub document.   Fine.   Saved it.  Made some more adjustments to the photograph.   Placed that into the same .afpub document  replacing the previous image.   Suddenly the placed image automatically grouped itself with the title of the book and my "by" line,  and the type is badly pixellated.  I cannot ungroup this thing.   There is no indication under LAYER>Ungroup that it has been grouped.  I can place a text frame outside the group, but cannot insert text.   Nor can I create a text frame on the desktop and drag it into the page.    So I added a new page to the document just before the page with the mess on it.    I created a text frame, typed a T (for the word "The") and got an enormous T (shown below) but with the text size shown in the context tool bar as 11 points.    Not only that, but the rulers show that the 8-1/2 x 11" page is just over 1 pica wide.   When I used the zoom tool , I got a series of tiny icons on my desktop (even when I zoomed at 800%).    So I used the Control +Open and restarted Publisher - naturally losing all my settings -- gr'r'r'r.

But that has not helped this problem at all.   I have opened other documents which I created in Publisher, and don't seem to have the pixellation problem.   It is also not evident on other pages in the offending .afpub document.    So somehow or other, the .afphoto image must have gummed up the .afpub page.     HELP!!!

!434187683_ScreenShot2018-12-09at2_02_48PM.png.5aac49f6476b0b4368101cb65f0ae367.png1472329459_ScreenShot2018-12-09at2_00_42PM.thumb.png.6a8ca16460a8b97c3fdd2e4fff90ed27.png


24" iMAC Apple M1 chip, 8-core CPU, 8-core GPU, 16 GB unified memory, 1 TB SSD storage, Ventura 13.6.7.  Photo, Publisher, Designer 1.10.5, and 2.5.5.
MacBook Pro 13" 2020, Apple M1 chip, 16GB unified memory, 256GB  SSD storage
,  Ventura 13.6.7.   Publisher, Photo, Designer 1.10.5, and 2.1.1.  
 iPad Pro 12.9 2020 (4th Gen. IOS 16.6.1); Apple pencil.  
Wired and bluetooth mice and keyboards.9_9

Posted

Sorry.   Forgot to add the pixellated type image before I sent the above.   When I edited it to send that too, it appeared at the top of my comment.   Ugh.


24" iMAC Apple M1 chip, 8-core CPU, 8-core GPU, 16 GB unified memory, 1 TB SSD storage, Ventura 13.6.7.  Photo, Publisher, Designer 1.10.5, and 2.5.5.
MacBook Pro 13" 2020, Apple M1 chip, 16GB unified memory, 256GB  SSD storage
,  Ventura 13.6.7.   Publisher, Photo, Designer 1.10.5, and 2.1.1.  
 iPad Pro 12.9 2020 (4th Gen. IOS 16.6.1); Apple pencil.  
Wired and bluetooth mice and keyboards.9_9

Posted

So I solved it.   Rather.   I went back to the original PDF, opened it in Publisher, saved it as an .afpub file, then laboriously linked 66 pages of text frames together -- again.  Page by page.   And then I saved it as an experimental .afpub file.    I then went into Photo, and exported each freshly revised .afphoto image as a .jpeg.   Back into the .afpub file, and placed each new  .jpeg where the old image had been.   Worked.    Saved several times in the process.    Then I permanently trashed the offending .afpub and PDF files.

Whatever caused the problem, I  no longer have it, because the files are gone.   


24" iMAC Apple M1 chip, 8-core CPU, 8-core GPU, 16 GB unified memory, 1 TB SSD storage, Ventura 13.6.7.  Photo, Publisher, Designer 1.10.5, and 2.5.5.
MacBook Pro 13" 2020, Apple M1 chip, 16GB unified memory, 256GB  SSD storage
,  Ventura 13.6.7.   Publisher, Photo, Designer 1.10.5, and 2.1.1.  
 iPad Pro 12.9 2020 (4th Gen. IOS 16.6.1); Apple pencil.  
Wired and bluetooth mice and keyboards.9_9

Posted
16 hours ago, jmwellborn said:

Whatever caused the problem, I  no longer have it, because the files are gone.   

https://xkcd.com/2083/

I saw this comic and wondered if you know Randal (or does he know you?) You get the weirdest problems.

Mac Pro (Late 2013) Mac OS 12.7.6 
Affinity Designer 2.5.7 | Affinity Photo 2.5.7 | Affinity Publisher 2.5.7 | Beta versions as they appear.

I have never mastered color management, period, so I cannot help with that.

Posted

Ver’r’r’r’y funny.   Thanks, fellas!

17 hours ago, Old Bruce said:

https://xkcd.com/2083/

I saw this comic and wondered if you know Randal (or does he know you?) You get the weirdest problems.

Actually, I do seem to manage to get into all sorts of muddles — all related to imported PDF’s!   But since my several 300-500 page books have all been stored as PDF’s, waiting for Publisher so I can revise them, sometimes I am a wee bit not-quite-laughing when I have to manually link the text frame on every page.    All the same, Publisher is wonderful.

Mrs. W.


24" iMAC Apple M1 chip, 8-core CPU, 8-core GPU, 16 GB unified memory, 1 TB SSD storage, Ventura 13.6.7.  Photo, Publisher, Designer 1.10.5, and 2.5.5.
MacBook Pro 13" 2020, Apple M1 chip, 16GB unified memory, 256GB  SSD storage
,  Ventura 13.6.7.   Publisher, Photo, Designer 1.10.5, and 2.1.1.  
 iPad Pro 12.9 2020 (4th Gen. IOS 16.6.1); Apple pencil.  
Wired and bluetooth mice and keyboards.9_9

Posted

Hi jmwellborn

I'm glad you managed to solve the issue, it's a shame you no longer have the original files as it would have been good to try and track down the cause. It could have just been a one off of something you may have not noticed you'd done at some point, but If you come across this again please feel free to let us know

Cheers

Serif Europe Ltd - Check the latest news at www.affinity.serif.com

Posted

"

16 minutes ago, Chris_K said:

Hi jmwellborn

I'm glad you managed to solve the issue, it's a shame you no longer have the original files as it would have been good to try and track down the cause. It could have just been a one off of something you may have not noticed you'd done at some point, but If you come across this again please feel free to let us know

Cheers

Thank you!  The strangest thing was that the imported .afphoto file was used to replace a jpeg which had come in with the original PDF, which had then been saved as an .afpub file.   Somehow, when I opened the saved .afpub file, removed the existing (ungrouped) jpeg and placed the .afphoto, it managed to group itself with the two text frames on the page, rasterized the whole thing, and then would not permit any editing.  Or any changes.  Nor could I create a text frame outside of the entire grouped affair.    Or on the workspace.  I hope it was a one-time issue.    Anyway, I think Publisher is grand!

 


24" iMAC Apple M1 chip, 8-core CPU, 8-core GPU, 16 GB unified memory, 1 TB SSD storage, Ventura 13.6.7.  Photo, Publisher, Designer 1.10.5, and 2.5.5.
MacBook Pro 13" 2020, Apple M1 chip, 16GB unified memory, 256GB  SSD storage
,  Ventura 13.6.7.   Publisher, Photo, Designer 1.10.5, and 2.1.1.  
 iPad Pro 12.9 2020 (4th Gen. IOS 16.6.1); Apple pencil.  
Wired and bluetooth mice and keyboards.9_9

×
×
  • Create New...

Important Information

Terms of Use | 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.