Jump to content
Our response time is longer than usual currently. We're working to answer users as quickly as possible and thank you for your continued patience.


  • Posts

  • Joined

Everything posted by v_kyr

  1. On Macs you usually don't insert special chars that numerical way. - See also: How to Use Alt Codes How Unicode is supported in macOS ... etc.
  2. They are on Windows and usually one would use the AltGr key hold down and afterwards type the numerical keycode.
  3. As I said above before, if you would enable that option then for ADe then yes. - On your Win box if you have Publisher too, then setup a FrameText with rulers there and copy/paste that over into your ADe and look if that keeps the rulers then showing up! Those tabstops on frame rulers would too be draggable in Affinity apps ... screencast-tabstops.mp4
  4. I don't use Windows thus can't tell you where initial app settings are hidden there or if it's maybe a compressed dat-file there. I also don't know how those set tabstops in a graphical manner, maybe you show some screenshots from those in order for people to see what you mean with "in a graphical user friendly way". Other than that, if you also have Publisher than you can maybe take over textframes with shown rulers over to Designer from it.
  5. Not sure why I would need nowadays to explicitely vectorize QR code bitmaps, if can instead let them anyway be generate (right out of the box) as vectors? In the past I used something like this which generates various QR-codes as bitmaps ... Portable QR-Code Generator v1.14.2 ... then wrote some own tools with the help of some Java frameworks for Bar-QR-codes ... Generating Barcodes and QR Codes in Java ... which then generate directly SVG vectors instead of bitmaps, see therefor as examples ... QR-Code-Generator (GitHub sample in/for several prog languages) Create QR-Code in vector image
  6. Well it's not part of Affinity Photo/Designer and so restricted here to Publisher. Next from what I saw it's nothing I would like to deal with, since it looks to generated thousend of unneccessary nodes here, as it probably converts all single pixels into single curve nodes. Even a good overall finding, it's not that much useful in that/it's curent state, as it's just a sort of non optimized vectorization (aka amount of pixels -> to nodes).
  7. It's easy to do ... select with the rectangle selection tool the shoulder area to copy/duplicate use copy/paste in order make a copy of the selected rectangular area into a new layer select the new layer with the rect portion with the move tool, drag and position the rect image portion to where you want it now perform a flip horizontal operation on the selected layer rect shoulder area (not shown) if you want you can merge together all visiable layers 20230126_144809.mp4
  8. Let's emphasize this here again ... Search engines: It’s easy to underestimate the power of a simple Google search (and it’s apparent that there are many people on online forums who don’t know how to make use of it). It can save you a lot of time, because someone, somewhere, at some point has undoubtedly had the same question you have—all you need to do is find out where they asked it and what answers and problem solutions they got in response!
  9. Think about it, what if you don't have Affinity Photo and so just Affinity Designer? - Then you might be happy to be able at least to do some (even if limited) bitmap/pixel based manipulations too. A bunch of common software can deal with both vector + bitmaps in one package, like for example Photoline and Xara Designer ... etc., so it makes sense to also offer some limited bitmap features in ADe here too.
  10. Seems there's something buggy then in relation to Ventura, you may want to look/search over the forums MacOS related bug reporting sections, if there's something in this context already mentioned as behaving buggy. - If there isn't already such a bug report thread, then you can create one there in decribing the problems.
  11. Yes, first of all meant here are the bitmap-to-vectorization facilities, which often do come along (are build-in) with the big players of vector drawing applications. - Though that also applies a lot to most of the seperate standalone tracing apps, there aren't most top notch too here, so there are all in all huge discrepancies in what certain of those tracers do offer in overall tracing quality and their capabilities.
  12. I don't necessarily want to curb your euphoria, but some people have been waiting for it since 2017/18. Therefore, the wording of being "patient" is meant seriously here and is indeed to be taken literally.
  13. See related now for the new M2 based Mac Mini and MacBook Pro's ... New 256GB Mac Mini and 512GB MacBook Pro Have Slower SSD Speeds Than Previous Models 2023 MacBook Pro SSD has performance drop similar to M2 MacBook Air MacBook Pro und Mac mini 2023: Langsamere SSDs in Basismodellen (DE)
  14. I assume you have already full access rights to that local folder. - Ventura 13.1 ok, seems that certain things don't behave well there for the Affinity apps then when trying to export. Can you instead save or export whole docs there into the same folder location without problems?
  15. Not sure if you mean me here, or the OP? I'm personally not looking after any tracers since I already know most of them already. The one you linked to above is already (for long time) on the list of third party tracer tools ...
  16. Didn't looked if those Silicon hardware related crashes are mostly Metal/hardware acceleration related or not. In the past (v1 times) I've often looked over crash reports etc. in order to analyze where the problems of all evil (bugs) may stem from several people had/have. But to be honest I've gotten bored looking through other people's crash reports and giving advice. Thus I don't do that anymore and instead let the people do it, whose job it is and who get paid for it.
  17. Looks like a reuse of the Potrace algorithm, which has been translated from C into/for a bunch of other prog languages routines too (GitHub is full of such ports). Here's how a default Potrace will trace that, also in B/W (via the DragPotrace GUI for Potrace)... And here's what Vtracer makes out of it ...
  18. Hard to tell without any more explicite informations about how you've setup the slices, what export settings, where do you try to export to (local disk, NAS, cloud drive) ... etc. - Further it always also helps if you name the OS your are working on with the Affinity apps.
  19. I've recently saw on a Win box that certain things there for V2 were now placed into the users home directory (~\.affinity\*), maybe it's for MacOS now the same (check also for hidden dirs).
  20. I pretty much have the same impression here and I'm also judging just from forum thread impressions here, since my operating system is also not supported by V2. I recall that in the past for Win systems and V1, most threads were about crashes due to GPU drivers and OpenCL based hardware acceleration. Now with V2 most Win threads are about MSIX based installments. - For MacOS and V2 it looks like Ventura and Apple Silicon platforms do now give some new additional bugs.
  21. For V1 apps from the Affinity store those were in ... --> "/Users/username/Library/Application Support/Affinity Publisher/user" --> "/Users/username/Library/Application Support/Affinity Designer/user" --> "/Users/username/Library/Application Support/Affinity Photo/user" For V1 MAS apps in ... --> "/Users/username/Library/Containers/com.seriflabs.affinitydesigner/Data/Library/Application Support/user" ... etc.
  22. I've already saw that thread some time ago and it doesn't tell much here about the different tracer apps and vector apps build-in tracers vectorization accuracy/quality. - What I've shown you above is overall the more difficult part for tracers here in contrast to ... Since those tracers I've shown above can do that either way here, as far as you load in those image portions you're interested in. - Further and this applies to all tracers, the better quality and clearer/cleaner etc. an initial bitmap/image pixels & lines are (...so overall the better an input bitmaps quality is), the better can a tracing algorithm also determine what continious pixels to trace here and thus also build overall better vector paths out of that. - Meaning, from a bad blurred and too small input bitmap/image one can't expect wonders from tracers then! And related to Affinity Designer, if they implement and add a tracing facility (...which would be highly welcome), I would expect that one then to give at least the quality results of Potrace and additionally to also support center line tracing. - And on demand sometime then ideally also some node amount generation settings (node optimizations) for the vectorization.
  23. Don't know if Illustrator changed their build-in vectorization tool (... in the past it was a seperate bundled one) and what it produces nowadays for results, but I wasn't much impressed from what I've seen in the past from Illu based vectorizations, those were mediocre, if not to say awkful at best. Further I've not seen much outstanding new tracing algorithms, most things are based on older long time before developed third party things here (like potrace & autotrace) and thus is reused in non-commercial apps. https://vectorizer.ai/ SV2 Vector Magic And here's the initial used JPG test image ... ... now somebody can maybe show what an actual Illustrator versions tracer can make out of this.
  • Create New...

Important Information

Please note there is currently a delay in replying to some post. See pinned thread in the Questions forum. 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.