Tia Lapis
-
Posts
249 -
Joined
-
Last visited
Posts posted by Tia Lapis
-
-
-
AP meaning Affinity Photo (APh) or Affinity Publisher (APu)?
-
I always wonder why no one is using the trial before buying. Would prevent much frustration on all sides...
-
1 hour ago, PaoloT said:
They open separate windows, and can be docked if you like. Even on Mac there are users who can only think to one simple thing at a time.
Paolo
Just rechecked. All three applications (Ver 12.2.1 on macOS Ventura) open new documents on tabs.
-
3 hours ago, fde101 said:
Most document-based applications from Apple do open separate windows for each open document - such as Pages (their word processor) for example.
iWork suite (Pages, Numbers, Keynote) opens new documents as tabs.
-
2 hours ago, GeGr said:
completely agree on this as a macos user.
the seperated mode is a completely basic macos function, immanent to the possible workflow in macos - and as such, programms that are sold for macos, that are lacking this feature, are somehow incomplete regarding the os support.
so please make the seperated mode possible again. thank you
Hate to say it, but macOS development removes this for some time now and moves in the direction of all-in-one windows.
-
Hmm I don't think Serif will implement this as it only supports English and French.
-
What is this? Never heard it before.
-
The problem is that Metal is way better than the available OpenCL implementations for such workloads.
And concerning UMA and PCIE4: As fast as PCIE may become it always need 2 copy operations when cpu had to do something, on UMA the ram is used directly without any slow operation betwenn cpu/gpu access.
Here are current speed rates:
PCIE4/16 - 31,5GB/s
M1 - 66,67GB/s
M1Pro - 200GB/s
M1Max - 400GB/s
M1Ultra - 800GB/s -
-
Is anyone using the demo to test the new version?
-
Strangely Blender is working perfectly fine in the MS Store version...
-
I am pretty sure we see the impact of the copy to and from gpu memory.
-
-
Probably because it would only be useful for the Windows version.
-
Lemme do some comparisons to widen the dataset:
M1 MacMini - 573/2296/678/9348/-/647/9200/-
iPadPro 1 - 224/413/105/1885/-/105/1109/-
Ryzen 5 5600H + RTX3050mobile - 350/1887/300/7524//8616/404/4629/5223
The Apple M-Series chips may not have the fastest gpus but it has one very helpful feature for gfx work: ultrafast unified memory that prevents a lot of waiting and copying.
-
How do you compare the performance between the Win, Mac and iOS versions?
-
-
-
As long as Maxon doesn't buy Serif... I'm still mad about that move and fearful about what happens to my hobby Zbrush.
-
-
7 minutes ago, chessboard said:
But back to the problem with large files: The filesize on the disk is one side (rather less important today). The question is, can the image software handle this large images when they are opened and edited. This seems to be the problem that @JaGold appearently had to struggle with in AP V2.
I would check opening times in V2 on my Ryzen laptop and my Mac Mini, but I don't have anything in this size region to test.
-
53 minutes ago, chessboard said:
BTW, I don't know any lossy file format, that could handle layers.
TIFF should be able to handle that. As far as I remember it supports JPG als codec and multiple layers.
-
45 minutes ago, chessboard said:
That's no problem. Apart from photos, which can use a lot of memory (that starts with using 16bit channels), you can do all kind of print documents in an image editing software. I for example do puzzle illustrations in Photoshop. With A3-Size in at least 300dpi, perhaps CMYK-Mode (I use RGB as long as possible), lots and lots of layers the memory requirements can also get very high. Since clients tend to change their minds about some things, it's always good advise to not flatten layers until the work is really done.
I guess also only lossless codecs for the image data?
Linux user base keep growing !
in Feedback for the Affinity V2 Suite of Products
Posted
Developers hear customer wishes - But a good developer works at HIS program, he can integrate some wishes but many won't fit to the vision of the program so won't be implemented. This is good as without a vision you get a mountain of features without any coherence.