Jump to content

Search the Community

Showing results for tags 'SVG'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Affinity Support Forums
    • News and Information
    • Affinity Support & Questions
    • Feature Requests & Feedback
    • Bugs in Affinity Designer & Affinity Photo
  • Learn and Share
    • Tutorials (Serif and Customer Created Tutorials)
    • Share your work
    • Resources
  • Affinity Beta Software Forums
    • Affinity Designer Beta Forums
    • Affinity Photo Beta Forums
    • Affinity Publisher Beta Forums

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 305 results

  1. Dampsquid

    SVG export problem

    Hi - please take a look at this thread... Post in iPad questions The question was around export of a design to SVG where a curve is a shape compounded from two with the subtract operation. There seems to be a bug here given it's not just me experiencing it. Thanks!
  2. It would be very handy to have an option to include invisible object in export to SVG and PDF. Main purpose for this is to improve exchanging working files with other applications.
  3. Hi all! I am writing you not as the usually nitpicky and potential Affinity-fanboy-who-lives-off-of-Publisher (I do currently live off of InDesign, so it would be only a matter of time, but things just may take a bit of a turn in my career path soon-ish), but as a prospective full-blown professional type designer and current type design teacher with some serious grievances to air; as you may guess, I recommend Affinity apps for most graphic design related tasks, and even though I vehemently tell all my students to familiarize themselves with type design packages (namely Glyphs.app, FontLab, RoboFont, etc.) and start drawing inside them right away, they are all more familiarised with all-purpose vector drawing packages when they begin studying type design, so, for those who may wish to go that route, I also make a point of explaining to them how to properly size their curves/paths in points, in order to correctly import them into Glyphs.app further on. Now, this usually works fine when using Adobe Illustrator, but when doing so with curves/paths drawn in Affinity Designer, some less-than-optimal results occur, as you can see from the enclosed screenshots. The result will always be the same (on both apps, mind you), either if I paste the curves/paths directly or if I export them into .EPS and import them into Glyphs (actually, Glyphs won't even let me try the latter – and gives me the enclosed error message, whereas .EPS content generated from Illustrator, whether pasted directly from the clipboard or dragged into Glyphs, will work just fine). If I export it from Affinity Designer into .SVG I will be able to import it into Glyphs.app without any missing nodes, but the scale will be way off, thus making the whole process needlessly complicated. I happen to be acquainted with Mr. Rainer Erich Scheichelbauer, from the Austrian type design studio Schriftlabor and the Glyphs.app development team, and I can put you guys in contact with him in order to work on fixing this issue. As for the recently released FontLab VI, I don't own it so I can't get into the compatibility with it for the moment in any authoritative fashion whatsoever. I did give their very feature-complete and stable public beta a go, however, and it seemed the interoperability was even more broken, so maybe you should chime in with Mr. Adam Twardoch from FontLab Inc. on that issue as well (though I'm guessing that FontLab's even more advanced curve/path drawing tools and its focus on über-pros – their app is expensive as hell, after all –, combined with their still less-than-elegant usage of – ugh – Qt, may mean that they don't care much about those interoperability niceties and would rather force their users to always draw inside of FontLab from the get-go). As it stands, Affinity Designer in standalone form (I have yet to test InkScape as a bridging app, but… I'd rather not, as it's even more cumbersome than AI) is completely unfit for type design purposes with Glyphs.app and, as such, I can't recommend it to my students at all, which is a pity because the price bracket and the target audience of both packages seem to be very similar. Do you have any insight as to what may be going wrong here (a non-standard/reverse-engineered or even standard and well-documented .EPS and .SVG implementation, just a bit gone wrong, perhaps?) and could you provide us with a tentative ETA for its resolution? Now, for some explanation on what each of these screenshots mean… Here we have the original outlines, all nice and dandy, without duplicate nodes or anything: And here we have the result of copying said outlines and pasting them directly to Glyphs.app and, as you can see, the scale is indeed correct but we're missing one node: Now, if we try to export a file into .EPS using Affinity and import it into Glyphs.app, we get this error message: Surely we'll get better results if we try using Adobe Illustrator, right? By opening the .EPS file in AI and saving it back, also in .EPS format but with a different name, and importing it into Glyphs, here's what we get, and indeed the results are better, as we get the correct scaling and all the nodes (plus some extraneous ones on the same place where Affinity Designer defined the first/main/closing nodes to be): For the sake of it, let's try saving both .EPS files, in their respective apps, into .SVG format instead and import them back into Glyphs.app… The result on the right was from the file generated in Affinity Designer, and the one on the left from the file generated in AI and, as you can see, AD got the scale way off but finally all the right nodes, whereas AI gave us the same result: Interestingly, if we copy the paths from the .SVG file generated in AI from the .EPS file exported in Affinity Designer and paste them directly from AI into Glyphs.app, we get the best results yet: So, all things considered, it seems the best course of action is to export the artwork in Affinity Designer into .EPS format (and not directly into .SVG, because, as I've just found out and pointed out in the thread title, Affinity Designer seems to mess up with the scaling factor when exporting into .SVG), then opening it on Adobe Illustrator, then saving it into .SVG format and, only then, directly copying it and pasting it into Glyphs.app. It's an effective but extremely convoluted process, which forces you to use AI anyway and kind of defeats the whole purpose of switching to Affinity Designer… :\ For your reference and… forensics, I guess, I am also enclosing the files used in the course of this test: p (generated with Illustrator from the EPS generated with Affinity).svg p (generated with Illustrator from the EPS generated with Affinity).eps p (generated with Affinity).svg p (generated with Affinity).eps test.glyphs
  4. I only found this strange effect after quite a bit of chin stroking and hair pulling with something that was confusing the heck out of me. Workflow to re-create the issue (in Designer for Windows): 1. Create a new document containing an artboard (A5 landscape will be fine). 2. Draw a triangle that almost covers the whole artboard (don't go near the edges so you can see the effect better). 3. Give the triangle a Black stroke colour and a thick stroke width (16pt will be fine). 4. Go the the Export persona and export the artboard as "SVG (for web)". 5. View the exported SVG in a browser. All should look just fine at this point. 6. Go back to the Draw persona. 7. Select the artboard layer - NOT the triangle layer (but it does the same thing either way). 8. Change the Opacity of that layer to 90% (this is the thing I did by accident that was producing the strange problem). 9. Go back the the Export persona and export the artboard as "SVG (for web)" again. 5. View the exported SVG in a browser. The image now looks blurred. It's actually an SVG containing a raster of the triangle. You can prove this by editing the SVG in a text editor. Is this expected behaviour? (It took me ages to figure out what I'd done "wrong".) I did a quick search and only found the following related issue: * https://forum.affinity.serif.com/index.php?/topic/63257-texts-rasterized-when-exporting-to-pdf
  5. Looking at the SVG output at the moment SVG's always get a 100% width and 100% height, meaning they always scale up or down to a parent-window (in a browser). But there are a lot of usecases we don't want SVGs to scale on websites and if we do it would be nice if we could set how the responsiveness would behave, so to wich windowborder the image would stick and if we want to keep the aspect ratio while scaling. These are all very simple SVG attributes that only have to be added to the svg when we need it. Browsers are doing the rest. At the moment there is no setting in the SVG settings to turn the auto scaling (100% width/height) behaviour off in the SVG, meaning we have to manually take these attributes out of the SVGs each time we export an SVG if we don't want autoscale. It would be a lot easier, faster and less time consuming if we could just set these settings once inside the SVG export options to save it with our own preset. So what I ask for in the SVG export settings dialog is: - A switch to choose between using document width/height (keep size) or 100% width/height (auto scale) - A listbox to choose the 'preserveAspectRatio' attribute in the SVG so we can set this to: - none, xMinYMin, xMidYMin, xMaxYMin, xMinYMid, xMidYMid (the default), xMaxYMid, xMinYMax, xMidYMax, xMaxYMax (as described here: https://developer.mozilla.org/en-US/docs/Web/SVG/Attribute/preserveAspectRatio) These are important settings for exporting SVGs for Web and not very difficult to add to the dialog cause they only change 3 attributes in the svg tag. But they speed up the process of SVG exports a lot because these changes don't need to be made by hand in a texteditor after each export! Thanks!
  6. Hey everyone. I’m using both Affinity Photo and Designer on iPad Pro 12. I’m also using a Cricut. Does anyone know what the exact SVG export settings are for Cricut Design software compatability? I’m having problems importing files. Getting either blank files or clipping errors. Thank you very much. Screenshot of your exact SVG export setting screen would be extra helpful.
  7. Dear Affinity-Team, I've been working on a logo font where i use mostly bezier curves to define the look and after that expand to strokes... while I'm used to clean expanded strokes/curves... within Illustrator for instance, in Affinity Designer the created points are quite a lot if not messy?! This is even more problematic (also slows down the app considerably) with SVG/EPS Exports. (see attached files) Optimising / simplify curves/strokes could be helpful.. in that case. As well just a better conversation or maybe better conversation control. Other than that is the Affinity Designer pretty nice!
  8. Hello i would like to make suggestions for next release of Affinity Designer. Please forgive if what i ask is already sorted and operational at this stage, be kind to point to where i can be instructed about it please Requests: a- Make more Export profile available. i.e: Export for Web b- Please improve or standardize your SVG output, because those created with ADesigner are black or black when they are opened on other software. c- 3D fx/Emboss fx should be improved too, they are great but they often requires a lot of attention and tuning before it's okay, some standard 3D/Emboss profile/Preset would be of great help for those who like Auto things and the others will keep their By Hand stuffs. d- Clipping mask should be less hard to find or to do but more accessible, adding a button in the bar can be of great help. e- Please improve fonts loading on software start (we are not all using 37 fonts only ). f- the Place tool should be improved, it sometime loose the ration (even shift key pressed doesn't help to maintain it). g- Make it possible for noise to be added into a simple single color, it works on gradient but ... it should also be available for simple color. h- Accessiblity to Compound Path function need to be improved here too, a button in bar when 2 objects are selected should help. i- Artboard tool must show more options and sizes than what we currently have. j- the Pop-Up system used to display the name of a tool or a functionality should be improved to also show a quick description of what the selected tool can do. k- we should be able to round a sharp corners using the corner radius both in/out, sometime it's hard to get the correct curve because the tool make it possible in or out only, both sides should be great. l- Please make the bleed visible (red line or yellow doesn't matter) for with/without Artboard created. m- Color Picker tool should be able to pick gradient too and not just a single color, here couples of small buttons should be added in the bar and displayed when we select the color picker tool, enabling us to select gradient ON/OFF single Color ON/OFF. Well a long list but i've put everything here, those who know how to achieve this or that are welcome. @MEB you know Affinity far better than most of us here, your inputs are welcomed. To all, point me to where solution was brought and i will kindly jump there. Blessings.
  9. I understand that saving export presets is on the feature request list already -- +1. I'm trying to manually produce the same export results. Here're screenshots from both MacOS (latest) and iPad (latest), and the iOS exported image geometry differs from same export on MacOS. How can I replicate my export svg settings from MacOS to iOS so I can export from either with consistent results? Regards, d00d
  10. Searching for a doable workflow I am trying to develop a workflow in which I can create assets in AD (macOS or iOS), export them as SVG, and import them into Blender for animation. I have discovered, after quite a few failed attempts over the course of many months, that this is not as straight-forward as one would imagine. Breakthrough Yesterday, I stumbled across an old post that turned out to be a breakthrough for me. Apparently, while exporting the assets out of AD, a specific setting must be unchecked, as shared by @Dave Harris here: After playing around with the different settings, I settled upon the following combo that seems to work relatively well: This did indeed allow me to get them into Blender, colors and all. However, I did discover another problem. A New Challenge Here is an admittedly silly little project that I created in AD a while, just for fun: And this is what I got when I import it into Blender (after rearranging the layers for visibility): As soon as I saw this, my response was, "Ah yes, it did exactly what I told it to do, even if it was not what I had expected. Duhhh..." What I want to do What I would like to do is to get each of the letters of our names into Blender so I can extrude them into 3D objects and animate them - that is simple enough. But I also want the colors of each letter to go along with them - not so simple. Is there a way that this can be done? It seems that I will need to flatten out or convert the layer masks to something else before exporting them to SVG. This is where I am stumped. Finally... Kudos for the iPad app! I purchased the iPad app the very moment I received the email. The dev team really outdid themselves with this, big time! I truly enjoy using the Mac app for working, but I am actually LOVING it!
  11. When exporting a rectangle to svg without effects the result is as expected: <rect x="420" y="260" width="460" height="200" style="fill:#ebebeb;"/> But when we add an effect, like gaussian blur to that rectangle the svg-exporter automatically generates a wrapper-group around the element just to apply the effect: <g style="filter:url(#_Effect1);"> <rect x="420" y="260" width="460" height="200" style="fill:#ebebeb;"/> </g> This is what I would expect instead: <rect x="420" y="260" width="460" height="200" style="fill:#ebebeb;" style="filter:url(#_Effect1);"/> I understand wrapper groups could be a way to stack effects if we want to use more than one effect on an object (although even then svg allows filters to be chained via their 'in'-attributes), but that's not the case here because we just use a single effect. If we only apply one effect to an object, in my opinion the effect should go directly to the style-attribute of the element itself instead of creating additional groups and with that changing the hierarchy of the layout. Also when having more than one effect applied to an element the first effect should go in the style of the element itself. Adding these additional groups makes the svg output overly complex and large and in Javascript we now need to keep track of/set two different elements when controlling attributes both on the element itself as well as switching the single effect of the group above dynamically. I might be missing something here, but I searched through all of Designer and in the svg-exporter options, but couldn't find any setting to prevent these extra groups to be created on exports. I also tested this in the last Designer beta (1.6.5.112), but it has the exact same behaviour. Please add at least the first effect to the svg-element itself and prevent adding groups as much as possible. [edit] Please put svg effects directly to the graphical element or use svg effects chaining instead. Don't create additional groups/change hierarchy. Leave the structure in svg output 1 on 1 the same as created in Designer. And meant by the designer
  12. When exporting a file to SVG from within Designer, for each layer or group having an opacity set below 100%, Designer automatically adds an extra, redundant, group just to apply opacity to: * Adding a group without opacity set less then 100%: <g id="myID"> <rect x="152.01" y="85.967" width="142.705" height="84.033"/> </g> * But when opacity of the group is set below 100%: <g id="myID"> <g opacity="0.5"> <rect x="152.01" y="85.967" width="142.705" height="84.033"/> </g> </g> This results in larger and more complicated SVG-outputs then necesary, but most importantly: it breaks the structure and hierarcy as meant by the designer causing all kind of problems when using the SVG for styling and javascript usages: interactivity and animations. Because suddenly there is an extra, unexpected level in hierarcy and the ID is on a different level then the opacity. That way webdevelopers can't trust the ID anymore. Instead the opacity should be applied directly to the group like visually done in Designer, keeping the structure the same as in the GUI and so meant by the designer: <g id="myID" opacity="0.5"> <rect x="152.01" y="85.967" width="142.705" height="84.033"/> </g>
  13. No matter what I try some shapes simply go missing, and some remain but change position. Shapes are: just vectors have no layer effect applied - glow, blur etc. Grouped/ungrouped makes no difference. shapes are closed - no un-joined vertices. are not using any overlay modes such as soft light, overlay etc. I've also tried copying the illustration into a new document and exporting. I'm using this software professionally so things need to work. As it stands it looks like I'll need to sub to Illustrator and re-do a lot of my work.
  14. Hi, there is one thing I miss from Illustrator and it's the ability to attach scripts, or some metadata, to elements; layers or groups of layers. It's helpful when creating interactive SVGs. Of course it's possible by naming layer/group and edit the code of the exported SVG but it becomes repetitive when you open the SVG again and the code is stripped of the additional code. So the option to have some extra content in the code of an element and keep it intact on re-opening or saving the document, would be terrific. It does not have to do anything, just a field to type som extra attributes to the element and keep them throughout the workflow.
  15. When drawing elements to be cut on a laser cutter, setting up a document in mm is very helpful. Unfortunately, the common interchange file format for this kind of device is SVG. While the file format supports measurements in defined units, Designer converts to pixels during the export, which means that after import, the dimensions have to be recalculated. Therefore, it would be great to have the option to preserve the units from the document during export, such that a 50x150mm rectangle is exported just as such.
  16. I am trying to export SVG files from Affinity Designer and bring them into a range of programs for generating tabs / notches and then outputting for laser cutting. In Adobe Illustrator it is very simple - you set the document units to mm, design something with specific dimensions, and export your SVG. What comes out will be interpreted by other software, and by the laser cutter at the exact dimensions. With Affinity Designer, I've spent hours troubleshooting and digging through the forums and no matter what I do dimensions seem to vary depending on the DPI and all sorts of other options, and even slices of objects with the same height will export at different dimensions. It makes it practically impossible to predict what size your object will be. (as an aside, I thought DPI was completely irrelevant to vector - why is it even an option in a vector format?!) So is reliable scale something Affinity Designer just can't do? How are people delivering documents for print if they don't know how the printer will interpret the dimensions of their final files? I dumped Creative Cloud, bought the Affinity hoping to replace AI and now am faced with going back to Creative Cloud and getting stung with higher fees as a result of leaving. For my line of work this seems like really simple stuff...
  17. I am using Affinity Designer to create file to upload into Cricut Explore Air2, to draw embroidery designs on fabric. If I export a png file, the image looks perfect but the Cricut treats each line as an object and outlines it - not what I want. I want a line drawing. After hours with Cricut tech support, I discovered that by exporting my file as an svg, the single line problem was solved, however, the image broke apart into single strokes and scattered over the page. I tried grouping elements in layers and then grouping all the layers together and the file arrived partially intact and the rest scattered and chaotic. I am attaching 2 screen shots. the first is the png file that is plotted as an outline by Cricut. The second is the way the file looks when uploaded as an svg file. (I know why some of the circles are filled in and know how to fix that) If anyone can advise me, I would be so grateful.
  18. Derek Pollard

    Ordering of defs element in SVG export

    Hi, I’ve been looking into an issue with parsing SVG files exported from Affinity Designer and have noticed that the ‘defs’ element is consistently exported after the referencing elements. While many SVG parsers assume order independence, it is considered best practice to write the ‘defs’ element before the referencing elements are described in 5.3.2 The ‘defs’ element as follows: “To provide some SVG user agents with an opportunity to implement efficient implementations in streaming environments, creators of SVG content are encouraged to place all elements which are targets of local IRI references within a ‘defs’ element which is a direct child of one of the ancestors of the referencing element.” Could you please let me know if plan to update your SVG export to incorporate this recommendation in a future release? Many thanks, Derek testwithgradient.svg
  19. hansmbakker

    SVG importing bug

    It seems that Affinity Designer can't handle some of the SVG content in the digikam and showfoto logos. Text is lost "Lens glass" has different blur / transparency Shadow / blur around the lens is gone Sources of the files can be found at https://cgit.kde.org/digikam.git/tree/core/data/pics/digikam https://cgit.kde.org/digikam.git/tree/core/data/pics/showfoto logo-showfoto.svg logo-digikam.svg
  20. It looks like Designer cannot import or export from/to the SVGZ format. I understand that it is simply a compressed version of a plain SVG document which I can compress / decompress myself but it would be more practical if Designer could handle that.
  21. this is something I am sure has been brought up about a year or so ago. but could not find it on here. SO this link here is how you can use inkscape to design levels in video games, parsing the SVG data in whatever you are using that can be used for collision, shapes & other such things I really think this would be a fantastic feature for designer, photo, or whatever affinity product that can have SVG output. please look at the link & see how it works & uses the data to build levels. its super awesome & would be even more awesome to have http://www.fierysquirrel.com/post.php?id=705 all the best
  22. Hi! Firstly, I want to thank you for your products. You do amazing work guys and I really enjoy using them! I believe there are more important features to be implemented, but I couldn't find this one here, so let's list it: There is a "new" font format called OpenType-SVG that stores vector or bitmap informations to create colored fonts. Would be great to push the limit :) PS: Links explaining OpenType-SVG/Color Fonts: http://www.colorfonts.wtf/ https://creativemarket.com/blog/color-fonts?utm_source=ownedsocial&utm_medium=social&utm_campaign=blogposts&utm_content=inspiration
  23. I have a situation where I create an svg in affinity designer, and then I have to modify some of the resulting svg plaintext by hand. I would then like to open the exported svg into designer, make some changes and then save it out to the same file. The primary issue I'm having is that if I export a new svg, all of my edits are gone. Is there some way to modify an svg and leave all of the elements I don't touch alone?
  24. Continuing from this post, I think it would be really cool to have a tab added to the export persona that would allow us to attach exportable attributes to layers, so that when we export an svg, all of our attributes for that layer are preserved. This would solve so many of the problems I've had whilst using designer. It would allow us to: Invoke svg filters defined externally Save class names on elements Add interactivity and styles Better yet, it would be cool to also use empty layers to add some svg markup to the final exported document, so we can define our own symbols, filters and the like. This would solve the issue I keep having (and no doubt others have had) while trying to use affinity designed svgs in production. If somebody asks me to change a colour, its always the same workflow: change color -> export -> make text edits -> repeat...
×