Search the Community
Showing results for tags 'stability'.
Found 3 results
Seems others have been having this issue. I have also experienced this in the past. Update to newest version (today) did not fix it. Brand new build computer, installed 2 weeks ago as part of build and worked fine. Then suddenly it started again. Have followed all previous fixes suggested and have updated all significant drivers (mainly video) and it still happens. Being that this is a very new PC, there is minimal content installed and there has been zero file installs in the last week - ie Publisher and Designer functioned properly since last install of any other applications for at least 1 week. This seems to be a recurring issue and leads to question the stability of the applications.
More than once I encountered problems with the stability of publisher. It started in the time Publisher still was a beta product. Then some form of recovery was added and sometimes it works. But now, working on a book with 300 pages and needing to add 1 page and next removing 1 page again Publisher just quits. With a limited number of pages it works fine. Then when carefully adding pages it still works fine. And starting to use master pages, changing etc the problems appears again. When using the last saved version, I find that the problem is saved with the file so, falling back to the previous version is no option. It makes me feel very unsafe. It also made me think how to make a publishing program that is really stable, whatever size. Thats's part 1 I also use a program called RightNote. It is stable can contain an awfull lot of notes in very many formats Excel like, Word Like, copies of internet pages. I don't say the program never fails. But the data is always correct. They use SQLite for storing there information. SQLite runs on Windows, Mac, iOS and more... As far as I know the systemdatabase of Apple is also based on SQLite, which means it has to be very stable. That's part 2 Putting the parts together: I want to have an extremely stable publisher program. And I love Publisher, as a rose with thorns... My suggestion is not a small one, and I don't know how Publisher works internally. But wouldn't it be a good idea to change the way of working and let it work with on a SQLite datbase? With at the core 3 tables: Pages Spreads Resources When starting from scratch creating a SQLite database file When opening it again first making a copy of the database and then opening this session database If each time a page is changed and the page is abandoned, saving the page to the database When changing the spread (reference between 2 (or more) pages) saving that record. When adding/changing internal or external resources changing that table (with either the link or the content) saving it to the resources table. If the program crashes: almost everything will be saved. If it would crash om an update to the database: SQLite has enough recovery tools I think. You could have a construction to make extremely large documents (terabytes they say). And even add lots of internal resources. You could also make a separate repository file for the resources (and share them with Designer, Phote or a PDF reader)...
Hi there, I guess I start to sound like a broken record. Well, although I love Affinity, I have to call your attention to this crucial topic once again. I'm working in a new place and I decided to install the trial on a blaze fast machine. Here are the specs: Dual Intel® Xeon® CPU E5-2650 v4 @ 2.20GHz, 2201 Mhz, 12 Core(s), (RAM) 64.0 GB Dual NVIDIA TITAN X Samsung SSD 850 EVO 500GB Windows 10 Pro On this box I'm running Cinema 4D 18 with Octane, Adobe After Effects CC 2017 (and all the CC suite), plus other 3D programs (for 3d Tracking, also Blender 3d and so on) and it's a nice and smooth experience. Unfortunately, coming to Affinity Photo, I was sadly surprised to notice the same issues I've at home (where I use both the final and the latest beta). As soon as the work gets deeper with multiple layers, masks, adjustments, Affinity Photo becomes slow, even with random moments where it freezes, up to the point it randomly crashes. At first, I was excited to have the trial on this box as I hoped to show off Affinity to my colleagues (and maybe convince them to give it a try and buy it). But now I feel I won't proceed in that direction. The type of work we do requires fast turnarounds, sometimes we have very tight deadlines or new requests comes out of nowhere and need to be done by yesterday. Photo will remain my little gem at home where I can take advantage of a different pace. But I seriously hope you will realize how important is to give priority to this two crucial weakness. I know you are working to improve it, and you are working hard. Just wanted to share my experience and hope that Photo will be fast and, for the most part, as bug-free as possible soon. Probably for many users in this forum, this is not an issue, at least that's the feeling from my other threads in the past. It's either because they don't have the same issues on the Mac, or because most the users here don't make heavy use of layers, large documents, and so on. I believe that if Serif is serious about pushing its products, they need to aim to a more intense usage of Photo and Designer and listen to the users here who are trying to implement Affinity in their VFX, Motion Graphics workflow. Best, Andrew