Jump to content
You must now use your email address to sign in [click for more info] ×

Search the Community

Showing results for 'Unsplash'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Affinity Support
    • News and Information
    • Frequently Asked Questions
    • Affinity Support & Questions
    • Feedback & Suggestions
  • Learn and Share
    • Tutorials (Serif and Customer Created Tutorials)
    • Share your work
    • Resources
  • Bug Reporting
    • V2 Bugs found on macOS
    • V2 Bugs found on Windows
    • V2 Bugs found on iPad
    • Reports of Bugs in Affinity Version 1 applications
  • Beta Software Forums
    • 2.4 New Features and Improvements
    • Other New Bugs and Issues in the Betas
    • Beta Software Program Members Area
    • [ARCHIVE] Reports from earlier Affinity betas

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Website URL


Location


Interests


Member Title

  1. I can search and find images on both Pixabay and Pexels as stated by SrPx. I'm running APhoto 2.0.0 on Windows 10 Home. Which brings me to the comment by SrPx: No, you do not have to be logged in to your Affinity account to run Affinity programs or to use the Stock photos feature. The only time you need to log in is to activate the Affinity 2 apps the first time you launch them. With the Universal license, activating one of the apps takes care of activating the others. I wish I could help Zambody with his problem, but I have no suggestions to offer there. I did not find any other reports of this in a quick Internet search. You can always access free images from Pexels or Pixabay by going to their websites. I don't really understand the rationale for including this feature within Affinity products. There were some threads about Stock problems in 2019-2021 and people seemed at a loss to explain it. See https://forum.affinity.serif.com/index.php?/topic/91092-stock-panel-connection-failed/ and https://forum.affinity.serif.com/index.php?/topic/88295-stocks-tab-unsplash-not-working/
  2. I am looking at your signature, and you have the same card than I do, and practically my same Windows. Your CPU is very good. But mine is a generic PC (built by parts), while Dell surely has included special differences in hardware and software configuration. Super random, but do you have your Screen custom scaling (at windows settings/system/screen/custom scaling) at 110%? (I have a wild, crazy theory...). I'm sure future updates of 2.x will make it rather more stable also in less common scenarios, as you should be able to activate OpenCL in most systems. I am reading that those with AMD cards have worse experience ...I was expecting the opposite, as Open CL comes from AMD, kind of. But there are many factors here. Major global upgrades in every software I know (I believe it happened with the first release in Photo, if I remember correctly, but with many versions of Photoshop, etc) have a first stage, first moment, that is hard for early adopters, but for me, it is rewarding due to the massive improvements I am discovering in other matters. The JPG rotation. It's a bit a short in the dark, but I have experienced some apps, some software include certain special tags in the file headers, like in JPEGs (where meta data and certain stuff is stored), related to flipping and rotation. In the past, old apps would do this from time to time, that would flip your image but would display fine in the app that generates this, while once read back by another app, that header tag (a text that is stored inside the file) would be interpreted differently, forcing the rotation or flip. My suggestion is to do this same workflow with a different software as the external application to modify the linked files. And if you don't mind, uploading here a jpg of a non private image (like a free image of pixabay, unsplash or pexels, just modified (even with a brush stroke) in the external app you are using, and exported from there as JPG). So that I can open it here with tools that I have to check the file header of such JPG, see if it has some problematic tag, so that I can test it with or without the tag, and check how it displays in my Aphoto, if rotated or not. If so, then we know the culprit and how to avoid it, surely. In that case, you could even end up using one of these free utilities to clean that header every time (surely can use in batch mode, or do a simple python script for it), if you have a strong need to use such external app, or instead, the easy solution: using a different one (ie, csp doesn't provoke that). For starters, using now a different one would determine immediately if this is what is happening there. The jpg files saved externally, are losing quality due to compression every time you save them as jpg (png/tiff/psd are lossless) in any external application, or in actual Affinity, if you save the entire project as JPG instead of *.afphoto. So, if you modify the jpgs once embedded (ie, made them embedded, rasterized) in Photo, to my understanding, should not lose any quality as afphoto format is totally lossless, and the whole thing is being saved as such. If you keep them linked and only move (or even scale, flip or rotate) the linked object, to my understanding, it is not modifying the original pixels in the file; you are modifying like a reference, a connection point/box. As long as they are linked, only will lose quality if modified again in a external software, in the moment of re-saving there as JPG. And will lose again if exporting the whole thing (the entire aphoto file) as a big JPG, for example. And yep, the loss is cumulative, incremental, with every jpg-save. It is quite less perceived with very high quality settings, but it is still happening, it is in its nature. It is more noticeable with some graphical features (text, etc) than others. But while the JPGs being linked, just for moving them (or even scaling, etc, them), that's like a packet that you put there, that is referenced another file, so, in theory no quality is lost in the original JPG, is not being re-saved in any way. And if you embed or rasterize the linked files, it's all saved as an aphoto, no loss is added. Ehm, I should have explained that with fewer words and more clearly. Glad that I inspired you to give it a second chance. Everything is a trade off... I prefer a bit of complexity if I get a better deal in the long run, very generally speaking.
  3. I think what you are doing is fine with no modifications. It seems the intent of the license is to stop people from just downloading the images and redistributing. Physical product sounds like they don't want you to just create a print of the photos that has no other purpose than being an art print. If you are using the images as background images, it seems very well within the intended use of the photos on Unsplash. All of the above is the reason why when the site was Public Domain, it was tremendously better. No sifting through licensing.
  4. I didn't realize Unsplash was no longer a site for Public Domain images. Apparently that change was made years ago and I never knew. Eh, I guess good things cannot last forever.
  5. It was removed in one of the later V1 versions due to some change in Unsplash that caused some kind of interoperability problem.
  6. I have recently upgraded to Affinity Photo v2. I, too, have the problem of searches in Stock from both Pexels & Pixabay (what happened to Unsplash from v1?) appearing to search but returning nothing and offering no explanation. I'm using Windows 11 and searching in Stock in v1 worked perfectly. I didn't even get the "I understand" dialog check box to confirm(?) in v2 that has appeared in some comments here. I have read through some of the comments and problems regarding this and it appears opinions are somewhat random as to whether it works or not and no definitive answers seem to be forthcoming, so is not really of any help. I feel we can only hope that the appropriate staff at Affinity are monitoring these comments and will come up with an answer. Guess I'll just have to go to the relevant sites to download the media.
  7. Source photo (desert and woman) from unsplash. All structures created in Affinity Photo with shapes, textures, and an assortment of brushes. Planet built using Luna Cell (unfortunately Affinity does not support this plugin).
  8. Hello @onqun, Looks like you are off to a good start. I think the key is to know what you are trying to draw, and that often starts with observation of a reference image. I was inspired to challenge myself, so grabbed a stock photo from Unsplash, and then spent a while trying to recreate all the shapes, hilights, and shadows that I could see. It is easy to make assumptions about what things should look like, rather than see what they do look like. And the real world is also a complex place, so you have to decide how far to push things. Lots of different blend modes, blurs, a bit of stroke profiles. Fairly happy with what I achieved. Which one is the photo? Observed Red Sphere.afdesign
  9. Version: Win 1.8.2.62 1) Pexels is not working..."connection failure". It didn't work in 1.8, then upgraded and it did work, upgraded to newest version 1.8.2.62 and not working again 2. Unsplash - If I have the stock panel on the left side of my screen in a panel container (not a floating panel) where it runs the full length of the screen , I don't have any scroll bars for the Unsplash stock panel (even though I know there are many more images available than what is shown). But if I do a search on Pixabay, I do have scrollbars. If I make the stock panel a floating panel or put it into a smaller panel container on the right side of my screen, then I do get scroll bars with the Unsplash stock viewer. Neither are a major issue but are kind of an annoyance. Although I do wish I could have Pexels search working again.
  10. Continuing with Inktober, day 2 is MINDLESS, so I created this piece and wrote a short little article about it in my world here Image sources via Unsplash: Model: https://unsplash.com/photos/gDG8KSwSAvo Head texture: https://unsplash.com/photos/EXcebySSEMo Smoke: https://unsplash.com/photos/pFB0b8btIfM Cobweb: https://unsplash.com/photos/uer6GAKM53s Swirly Bits: https://unsplash.com/photos/4ZFeOnVwoek
  11. Uninstalling and then reinstalling v1.9.2 from Mac App Store made no difference. Updating to v1.9.3 - no difference. v1.9.4 beta - no difference - Unsplash search still crashes. Temporarily removing my admin rights (remove, reboot, etc) - no difference. Quick recap… Pexels and Pixabay Stock searches work fine. Unsplash crashes Photo (and Designer and Publisher) instead of receiving and displaying thumbnails from a successful search. (No crash if no search results returned.) Reboot into Safe Mode and log in with [shift] held down to produce the 'cleanest' environment possible (eg no third party utilities, etc for possible conflicts) and it still crashes when search results should be returned. Unsplash search works fine when used with a different login account. This is all with fully reset settings in /Users/gary/Library/Containers/Affinity Photo/… It's fortunate that I'm not depending on this functionality - but I don't like being beaten like this. I'm still open to further trouble-shooting suggestions…
  12. I'm pretty sure that the only Assets included in Designer are the iOS 12 ones. And, yes, Unsplash was removed from the Stock tab a while back, I think it was something to do with rights issues, but I'm not sure about that. You can still access the Unsplash website to download items, if you wish.
  13. UPDATE I made several visits to this over the weekend, to see how far I could advance things. The answer is: not very far. 😞 I'm currently stumped and am looking for more suggestions on further trouble-shooting! I tried Onyx, as suggested, no joy. In Big Sur, there seems to be some hidden folder name masking† going on in /Users/gary/Library/Containers, so rather than simply rename folders (and then possibly be confused about restoring old names afterwards), I created a temporary folder on my Desktop and moved all Serif-related folders from both Containers and Application Support out of my Library folder. The end result is the same - when any of the three apps run (I decided to test just with Photo), it's as if they're running for the first time - the appropriate new settings are created afresh. And the same crash problem persisted - as described in my original post at the top of this thread. I can add a little more detail to the original description. If I mistype an Unsplash search term, such that no hits are returned - for example, waterrr instead of water - then it doesn't crash. It's only when hits are found that it crashes. However, it crashes before it displays any thumbnails. On a related note, while successful Pexels or Pixabay searches populate the following folder with files and update the SQLite database with corresponding entries, the app crashes before this happens with Unsplash searches: /Users/gary/Library/Containers/com.seriflabs.affinityphoto/Data/Library/Caches/com.seriflabs.affinityphoto Thinking about it, I'm pretty certain that I recall this no-hits-no-crash aspect from when the original Unsplash problem raised its head back in, I think, 2019. One other minor thing I originally overlooked mentioning: when I tested this with the Test account (and it worked), that was an ordinary account - no admin rights. My regular day-to-day account does have admin rights. I'm going to try to uninstall Photo and reinstall it and will report back, but I doubt it will make any difference. † For example, the "Affinity Photo" folder from Containers is actually called "com.seriflabs.affinityphoto". Rename it in the Finder in the normal manner (for example, to "Affinity Photo (disabled)") and it continues to display "Affinity Photo" - although it is renamed behind the scenes.
  14. Thanks @walt.farrell - that supports some further testing I've just done. I got to thinking that just maybe there was a conflict with something running in the background of my environment (though there's nothing especially exotic). UPDATE I rebooted into Safe Mode. I logged in to a test account - while holding down the shift key to disable login items, etc. I'm 99.9% certain that I had never used any of the Affinity suite in this account before, so the environment was as clean as you could possibly get. I did the now familiar steps from above – and it worked fine. I repeated this with my main account – and it crashed as usual. So rather than a conflict with another app (I had been sceptical) it looks as if there's a dud setting in a Prefs file - or something along those lines - that's causing the Unsplash crash for me. Possibly lurking from the original Unsplash crash (under v1.8?), and carried over when I migrated my account from the old Mac to the my current M1 Mac late last year, for me it was masking the problem everyone else had been recently experiencing. My apologies to the fine team of developers for suggesting that they hadn't managed to fix the crash after all - and apologies also for the corny panto humour! Though I was right that there is another problem. Does anyone know where Unsplash-specific settings might be stored? I don't really want to reset everything back to out-of-the-box defaults if at all possible. (I should also say that this is not a big deal for me - it's more of an academic curiosity.) Thanks also to @loukash, though I think I've now ruled out the suggestion that it's M1 or Bug Sir related.
  15. https://unsplash.com/s/photos/paper-texture https://www.freepik.com/free-photos-vectors/paper-background ... and so on, do a Google search after that topic ...
  16. I can confirm this behaviour for Unsplash. With Pixabay and Pexels it works. What I noticed was a pop-up for the latter two to accept some warning about usage of the images. Didn't see this for Unsplash. Note: I also tested in Designer. Since I hadn't accept the warning for Unplash yet in AD, I saw the pop-up. Further no change; couldn't add the Unsplash image.
  17. Hi, I wanted to pick up on this thread again as I'm experiencing a failure with Unsplash stock to load the images into all three Affinity apps. I'm on a 2017 MacBook Pro running macOS Big Sur 11.2.3 and the latest 1.9x updates to the Affinity products. Pexels and Pixaby are working normally, but Unsplash fails to load the stock. Just wondering if Unsplash have implemented a policy change or whether it's related to the apps? Thanks.
  18. Welcome to the Forums @Rafa Cambra😊 This issue has been reported repeatedly. It is not a bug in Affinity but a change caused by Unsplash. Please refer to the second post above in this category. Also you can refer to Frequently Asked Questions for more information. In the meantime, in the Tutorials Section you can check "Sky replacement" posted by Digitally Fearless yesterday at 11:53 am. He shows a way to bring an Unsplash image into Photo (and it is probably exactly the same for Designer and Publisher) relatively easily. Not as easily as Pexels and Pixabay, but a workaround until Unsplash helps Affinity resolve this. Hope this helps.
  19. Fixed crash when dragging Unsplash images from panel when Unsplash is returning errors Unsplash doesn´t crash but it doesn´t load the images either.
  20. Hi, I have the same unsplash crashes issue after the last update to 1.9 version. Before that it was perfect. Unsplash works perfectly on chrome and other browsers. It's just unsplash. Pixabay and pexels works great. Crashes also happen sometimes when I'm using the warp mesh tool. But this is only sometimes. I don't know if there is any connection here. I'm working on PC.
  21. I was definitely just exploring, and whatever Affinity provided - I would have obviously used. I wasn't even aware of the various countries daring to differ, much less that the US wouldn't be the default But whatever it is provides a window of what might actually be printed, surrounded by black - but with invisible guides that Affinity snaps to for the "bleed". For example - you can download a photo from Unsplash, toss it in there, then resize that photo to snap to those guides - and you're assured that the "bleed" is then covered? Part of it's hidden by the black - but it's obviously still there - 'cuz you see it when you export the version with the bleed. And you're then left with a window, where you can design your card - with the understanding that anything close to the edge is possible to get lost in the cutting process. I sadly do not know what that area is called, but it's odd that Affinity doesn't have a dotted line or whatever representing that "unsafe" area? Again, I've tried creating the "template" myself - entering all of the information correctly - 3.5 x 2, 1/8" bleed, 3/16" margin. The guy at the print shop was even kind enough to provide me an .ai template. BUT - it doesn't obey whichever possibly imaginary rules I was following with the Affinity template? When I export with no bleed, it just cuts into the window of what I can see? And I have no idea why it's doing that - so no clue how to fix it? I liked the bit with the black part that was no man's bleed land - I'd have preferred the hint with a dashed line but there was of course none to indicate possibly unsafe areas? But I could at least guesstimate - designing safely within the window, being careful not to get too close to the edges. Now? I have no clue what it's doing. It just exports whatever it apparently wishes to export. Or possibly the "margin" things are cutting into it - I have no idea? Anyhow - I click to export and I just get a cut off mess that doesn't seem to have any bearing on what I can see on the screen. And that's obviously a bummer. Guessing I'm just doing something VERY wrong - because, formerly with the built-in template, it certainly seemed LOGICAL. Now... I have no clue what it's doing or why? So... LOGICAL - and then I apparently need 4 years of design school? I preferred the LOGICAL approach?
  22. As Unsplash.com has grown quite big up to a point that actually lets you search for specific terms and even find something, I'd love to see it integrated into the Stocks-panel of AP. Why unsplash? Because it would be the only image archive offering license-free images only that you can still use commercially. wouldn't it be nice, thanks guys! ;)
  23. A bit a surreal work with affinity photo. The Nuts are from unsplash.com.
  24. Well, the development of an app costs money as does maintaining a service like Unsplash. So I can understand that they try to earn money. As for Unsplash, I'm a bit torn with this, tho. Their service relies on (free) submissions from photographers. Unless they'll start paying back some money to the contributing photographers, I guess the overall quality of the offered images will decrease. Because I think that most people like to share their images for free, only if others can get them gratis, too. But if a business starts making money of their free works...?
×
×
  • Create New...

Important Information

Terms of Use | 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.