![]() Since this has been around for a while, I do think it's something that is enharrent in your system as opposed to an issue with Bridge. So, let's go back to the beginning: what is your OS (and what release) what kind of monitor do you have, what is your video ram, etc. On the other hand, the one aspect of software is if the thing that's visually broken would require 30 minutes to fix and the crash will take a week but someone has the extra 20 minutes, it can be squeezed in.īut again, like when you take your car in for a really annoying squeek but it doesn't squeek for the mechanic, they can't fix it. Also, software fixing is not too much different than medical triage: someone who's been shot gets priority over someone with a broken arm, and someone who's program is crashing gets priority over a visual glitch. Nonetheless, it's not likely for this to be "fixed" if the engineers are not witnessing the issue. Far from that, you're seeing this and it's something that should not be there. That doesn't mean no one else has seen it, I've not noticed it being commented on.Īll that said, I'm not saying you should be willing to just ignore it. ![]() Īlso, while I do prowl these forums a lot as an Adobe Community Expert, I do not recall anyone commenting on this issue before. Second, this issue is not showing up with your image on my computer in either the current Bridge Beta or in the release 13.0.4.755. Wonderful ballance of light, and you captured the woman's innocence and power at the same time. Hi, a couple of things: First off, great photo.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |