Skybase
![]() |
This is probably the weirdest, and most coolest thing I've seen!! *ahem* It's not cool we have a bug, but this one's really interesting and I feel it's been reported before.... BUT I can't be sure.
What I'm Using: Adobe Photoshop CS5, FilterForge Pro v3.006 Description: Upon applying my filter "Point and Shoot v2" to an image, if you run the filter through Adobe Photoshop CS5, after applying a bunch of weird (and faint) lines appear much as if it was part of the filter. I never put those in the filter and I have no idea where they came from. What's also weird is that several parts of the filter did not render (I added a grimy frame and some light leaks because this filter's supposed to simulate an analoge camera. In some instances those don't render.) Steps 1. Open an image in Photoshop CS5. It's best if you open an image with lots of dark areas, the filter utilizes those areas to apply a bomber effect and it'll be less prevalent in bright images. 2. Then apply "Point and Shoot v2" choose the 2nd preset. 3. Hit apply. Here's an output I screencapped. ![]() And imagery regarding what's not supposed to be there.... ![]() ![]() FilterForge Codex!! This does NOT happen with a direct FilterForge v3 output, only in Photoshop. I attached the version of the filter here.... Hope it can be fixed or it will be. ![]() Point and Shoot v2.ffxml |
|||
Posted: January 2, 2012 8:31 pm | ||||
Andrew B.
![]() |
I tried a photo and then a dark gray solid and didn't see the problem (Win7 64 bit CS5 32 bit). I realize you are having a difference between FF versions, but why not crank up the lightness on the shadows of the unprocessed photo and see if it's in the photo before the filter is run. Maybe one version is bringing this out, and the other not.
Oops. I just looked at your photo again, and realize you are running the Mac version. So maybe my test is not good. |
|||
Posted: January 3, 2012 1:38 am | ||||
GMM
Moderator
Posts: 3491 |
Thanks for reporting, we'll look into this.
|
|||
Posted: January 3, 2012 1:44 am | ||||
Skybase
![]() |
Yeh well I made sure it's not the picture, otherwise I don't make bug posts. ![]() By the way, that's not a photograph, it's 100% fully 3D and fake scenery I generated using Maya and rendered in Indigo Render. Looks real, totally fake. ![]() |
|||
Posted: January 3, 2012 4:46 am | ||||
Morgantao
![]() |
I'd love to see the whole "blueprint" thingy, not just bits and pieces. Looks like a page from DaVinci's diary
![]() |
|||
Posted: January 3, 2012 11:17 am | ||||
xirja
![]() |
I reproduced this in CS3 also, and then through a process of elimination deduced that it is one of those things that I found back in FF1 that made edge detection somewhat doable before FF3:
![]() If Anti-Aliasing is set to 'All Pixels', it should disappear. Due to rounding math the 'glitch' appears when there is a very slight difference between almost identical values. A nice bug? indeed! _____________________________________________________
http://web.archive.org/web/2021062908...rjadesign/ _____________________________________________________ |
|||
Posted: January 4, 2012 4:25 pm | ||||
GMM
Moderator
Posts: 3491 |
We're unable to reproduce this. Could you provide the source file to apply the filter on? What anti-aliasing settings do you have?
|
|||
Posted: January 11, 2012 7:16 am |
Filter Forge has a thriving, vibrant, knowledgeable user community. Feel free to join us and have fun!
33,711 Registered Users
+18 new in 30 days!
153,533 Posts
+38 new in 30 days!
15,348 Topics
+73 new in year!
30 unregistered users.