KipV
-
Posts
784 -
Joined
-
Last visited
Posts posted by KipV
-
-
46 minutes ago, Jon P said:
II was looking at this file previously for the crashing/zoom bar issue when loading, and wasn't aware it had issues on print.
I may not have listed that problem in the same post. I think my original report said it was crashing on launch and I don't think the beta does that anymore. I can't get the print dialog to show up at the moment.
-
When I try to print my ID badges file (the file I sent in to Affinity for testing) it still crashes when I go to print. Whether the images have been embedded or not makes no difference.
-
Just now, walt.farrell said:
As the Affinity file format remains undocumented, there is no way that Final Cut would be able to have support for opening the native Affinity files. The question would remain whether Affinity can export to some format that Final Cut can read with everything you want transferring over.
I would presume it would work very similarly to the way Photoshop is supported. Somehow Serif needs to get around this completely closed system. It needs to work much better with other products like Capture One, Quark etc. This is especially true for products they don't offer alternative to like video programs. Adobe even has their own video solution and yet they still support Final Cut. For Serif to not offer this option, even though they may never have a video option is nuts. They need to get their act together in this area.
-
Have there been any updates on this topic since 2017? I am think about buying Final Cut but whether or not it has Affinity support would be one of the reasons I buy it or not.
-
-
On 7/15/2019 at 2:04 AM, Jon P said:
If you open it on the MacBook and embed all the resources instead of linking, do you no longer get any crashing behaviour?
I just opened the embedded file on the iMac that has crashing and it stopped crashing!! This goes for both MAS and beta. With this file it may work since I don't swap out the images much/ever but I wonder about other files that may work better linked. Hopefully you can figure out what is wrong with the linking as well. Interesting how easy it is to switch between linked and embedded. I plan to pass this file around between employees, maybe it would be better to give them one big file with embedded images instead of a bunch of linked files. It will use some of the same files over and over again which was why I linked it to begin with.
-
20 hours ago, Jon P said:
Also when moving it over to the macbook and it didn't crash, did you get warned of missing resources?
I have so many different versions of the file at this point I have lost track of which one should be getting the warning message for missing resources.
20 hours ago, Jon P said:If you open it on the MacBook and embed all the resources instead of linking, do you no longer get any crashing behaviour?
It always crashed just on the iMac but did you mean embed everything on the MacBook and then bring it over to the iMac to see if it crashes?
-
1 minute ago, ashf said:
Actual progress of the development is always behind from the plan.
So I assume it would be 1.5x later than that. so 5/6 years.I imagine it's a lot of work to start a new suite of software from scratch.
-
3 hours ago, Jowday said:
Quoting Serif - April 30th 2019, Facebook:
I always figured that once they get through most of the bug fixes this will be the point at which they can then switch over to bigger updates. Given the bugs and crashes I have encountered with Publisher there will most likely be smaller updates for a while. I can see Photo and Designer moving on to bigger updates before Publisher.
-
Interesting, brought the same file over to the MacBook and it open on both mas/beta without crashing. @Jon P
-
@Jon P Back to the crashing again. I decided to open it in the mas version and ever since mas and beta crash immediately upon trying to open the remade file.
-
@Jon P I just did a quick and dirty remake of the file on the iMac using all the same files and things seem to be working so far. Even the zoom bar works and is in the right place. I wonder if the other file an elements copied over from an InDesign file? This file is based on a design from an InDesign file (I was trying to see if I could bring it over to Publisher so I could pass this around to some of the non-designers at my company.) At the moment the only elements that came from another app is the barcode from Printworks and the images were exported from Capture One I think. It seems like if the other file was crashing this would should crash to since it is probably the same exact thing. So anyways I re-linked it like you said.
-
10 hours ago, Jon P said:
I'm still struggling to reproduce a crash with this file, if you re-link the resources in Resource Manager does it help?
One option would be to re-link it on my laptop (which generally doesn't crash) and then try to open that on the iMac. Has this fixed the problems for others? I know others have reported crashes but I haven't followed those threads all that closely.
-
It crashes too quickly to do that usually. I noticed recently when it stayed open the zoom bar works fine on the beta.
-
14 hours ago, Jon P said:
Can you upload Cascade Logo 2010.ai and IGP2951.tiff to the above dropbox folder? I have the other 2 tiff's and re-linked them but want to ensure I have the other 2 images too, as the crash report is crashing in an area of code related to TIFF's, so it might help me reproduce the crash.
I sent those two files to Serif Affinity Support Dropbox.
-
-
16 hours ago, Jon P said:
It might be worth holding down CTRL whilst running the app to reset it, but I'm not convinced it will do anything.
No, it didn't do anything at all. It especially crashes with that Publisher file I sent in for testing. The other Publisher files behave fine I am pretty sure.
-
10 hours ago, Jon P said:
Is the following crash report one that happened when the app ran up, or when it was open for a while?
The crash report was when it crashed on startup. I run this on a 2017 5K iMac at what I am sure is it's default resolution as I don't remember needing to change it for any reason. The bar moves to different places, the left side of picture, the right side, nowhere.
-
2 minutes ago, nwhit said:
I had this problem with 1.7.1 with tall, narrow picture frames. The zoom bar would appear on the middle to lower third of the frame itself rather than under it. However, in the beta 1.7.2, the problem went away both in the same file I had the issue with plus in any new ones.
Interesting, I am just glad that with the beta something at least comes up at all now.
-
10 hours ago, Jon P said:
Hmm, I can't reproduce this on that MacOS, any chance of creating a short video demonstrating the issue?
This is what happens to the slider. At least in the 420 beta it is appearing again although not under the image that, as you can see, has been selected.
-
@Jon P No, they both crash (beta and mas) although sometimes they stay open for a while. I run MacOS Mojave 10.14.5. Attached crash report and screen shot of zoom bar just floating out in space.
-
6 hours ago, Jon P said:
Hi @KipV,
Can you let me know what MacOS version your macbook is on (that you can reproduce this on?)
Thanks
Both the MacBook and my iMac are running 10.14.5.
-
23 minutes ago, walt.farrell said:
For situations like issues with the Studio, you might try View > Studio > Reset Studio. It's simpler, and if it works, you lose less.
Good to know. Thanks
-
I downloaded the Publisher beta and it continually crashes when I try to open it. Sometimes I can get it to stay open for a couple minutes. I checked to see if the zoom bar works but now it doesn't show up at all.
1.7.2.458 still crashes when I go to print
in [ARCHIVE] Publisher beta on macOS threads
Posted
I wouldn't expect much out of an app that is on it's first couple of versions. Designer and Photo had time to fix and mature.