Transparent Gradient not-so-transparent

Hey, I'm having troubles with applying a gradient tool to a rectangular marquee in Photoshop CS3 for Mac OS X 5.8.  Instead of getting a black color to fade into the background, I just get the black color.  And I'm click and dragging about 1.5 inches long.  Sometimes I end up covering the entire picture with that color, not just the object (even though the object is selected).  Gradient maps and layer masks don't seem to work.  Help?

Wow, it's been a long time since I used CS3.
But in the Gradient dialog of more current versions, it looks like this:
The Opacity is the top row, and the color is the bottom row. (Note the color for both ends of the gradient is black. Only the opacity changes.)
Hope that helps.

Similar Messages

  • Does anyone have time for this one? photoshop 2014 gradient not working.

    Working on a project with photoshop 2014 updated thursday night using foreground to transparent gradient. The edges of the picture are staying white instead of being transparent over the background or other pictures. I thought I was using the gradient correctly converting the pic to a png file, setting the mask, then applying the gradient to the edges. Is there something I am missing??? Please help.

    below is a snip of the effect i am looking for. i remember it working in the trial version late 2013 photoshop. it was so simple i thought it would be hard to forget how, but i must be missing something. i looked, clicked and checked all around the work space to find a way to change from "background layer" and did not find it. the trial version (lets call it "trial period" because its all the same except paid for now along with updated to ps 2014) did also have the layer change in an easy to find way. i believe it was double click or right click over the currently active layer in the list as in the lower snip pic.
    the pic above did work during my trial period so i know it works somehow. i dont know what i am missing now. right click or double click now does not bring up the layer type selection in the menu like you suggested to change from backgroung layer. also every new picture file i open makes its own new layer. when i make a new layer i havent figured out how to put a pic in it. if you could show me how to create this effect or find my missing step that would be awsome.

  • Opacity mask with gradient not printable?

    I am trying to use a background in Illustrator that is made from a new effect called Opacity Masks in Creative Cloud.
    It groups two layers which can have transparent areas and then gradates them with a gradient. They grow gradually more transparent revealing the surface of the tube below. My printer says I cannot do this on flex press. Will not work in pre-press? Is this true?

    Opacity Masks have been available in AI since at least CS3. CC might have made them easier to work with, but they're not new. They may have to be "flattened" to separate correctly.

  • Gradient not working

    For some reason after the update, the gradient: from color to transparent is not working.
    I select the linear gradient and it shows only as black:
    i click on the editor and it shows like it should:
    Any other gradient works, for instance:
    i am using
    any ideas?

    In the gradient tool options bar, turn on the Transparency checkbox.

  • -webkit-linear-gradient not working with Adobe Air 3.0

    Hi -
    I recently downloaded Adobe Air 3.0 after reading that gradients are now supported (http://www.adobe.com/devnet/air/ajax/articles/air_and_webkit.html), but I have not been able to successfully implement them. For example, I have the following CSS class defined:
    .gradient_test {
         background-image: -webkit-linear-gradient(#68AB34, #3D721B);
         padding: 5px;
         color: #FFF;
    This should (and does in Chrome, Safari, etc) create a linear gradient going from light to dark green. But in Air it just appears as if no background has been applied to the selector. Am I missing some unique way to be able to apply gradients in Adobe Air 3.0?
    Thanks,
    Zach

    I don't know why this hasn't been addressed. I'm seeing the exact same problem. I've tried every permutation, but haven't been able to generate a gradient using any existing standard for webkit or otherwise (even though it's allegedly supported).
    -Matthew
    EDIT: I discovered that when the app is compiled, the gradients work fine. This one is driving my crazy, because I want to be able to test them. I get a mix of CSS support, depending on how the app is run.
    From Dreamweaver CS3 "Preview" - My CSS doesn't show gradients and shows embedded web fonts.
    From ADL - My CSS fails almost entirely, but some if it gets loaded.
    From the compiled AIR file: fortunately, everything seems to display correctly, but it's really a bad scenario for development / testing. Not sure what to do.

  • Color gradients not displaying correctly

    I'm having an issue with my color gradients in type and objects not displaying correctly in the content viewer. For the last app I created, I made sure the colors were RGB and that seemed to fix it. With the current app I'm working on, that dosen't seem to fix the issue. Actually, when I test in the viewer on my iPad, it shows the correct gradient in the split second that it's loading the update but then once it's loaded, it goes to a gray white gradient (the correct gradient is from a yellow to a gray; attached a pict for referrence).
    Anyone know why this is happening? Thanks in advance!
    UPDATE: It seems to view fine if I preview the page via the foilo overlay but when I preview the folio, that's when it's no viewing correctly.

    The Color Picker is unreliable for choosing colors based on what you see because it is not color managed while Color panel and Swatches are.
    In your image, the color that you see in the Color Picker is how your monitor displays R=0 G=255 B=0. The color that you see in the Color Panel represents the same values in the file but the color management sends different values to the video card and thus to the monitor to display a color with appearance in the color space selected for the document. In your image this is a CMYK color space which you can check from the Show popup menu at the bottom left of the document window. To check the different values the video card is using, make a screen capture, save the image, open it in Illustrator and measure the color with the eyedropper. The color translation from the values in the file to the video card allows simulation of color spaces other than your monitor's. This simulation is accurate if you have a monitor profile installed in your system that correctly describes how your monitor displays colors. Such profile is created by using a color measuring device and profiling software. If your monitor profile (color space) installed in the system is the same as the color space of the document then there will be no translation (simulation) which in effects shuts down the color management - then the colors in the Color Picker will be the same as in the document. Many people do not bother to get an accurate profile of their monitor and use a generic sRGB profile for that. In such case working in RGB color mode using the sRGB color space (default in the Color Settings) will give the same colors in the Color Picker and the document. This usually is a sign of using a monitor that incorrectly displays colors.

  • Gradient not drawn correctly in JRC 12.2.212

    Hello,
    I have JRC version 12.2.212 installed in the application, but when I try to generate from Java a rpt with a pie with color gradients, the result is a black rectangle being drawn behind the pie (and over some slices)
    Link for the image : http://imageshack.us/photo/my-images/819/wrongpie.png/
    If I remove the color gradients from the slices (and set them to normal colors), the drawing is OK, but I would need it to be OK with the gradients on too.
    Is this a bug in JRC?
    The former version of JRC that I used (11.8.4.1197) did not have this problem, but had several other major ones which makes it impossible for me to return to that version.
    So is there any way to solve this?
    Database used: Oracle 11g, if useful.
    Thank you,
    Alex
    Edited by: alexpol on Oct 12, 2011 10:35 AM

    If i have data inside the report, i cannot remove the connection to the database unfortunately.
    But it is easy to create such a report:
    - create a new report
    - add a connection to a database
    - insert a simple SQL which brings 3 lines with two columns, e.g.:
    select 'A' as col1, 1000 as col2 from dual
    union all
    select 'B' as col1, 4000 as col2 from dual
    union all
    select 'C' as col1, 5000 as col2 from dual
    - insert a chart of type "Pie chart", on change of "col1", show value sum of "col2"
    - change slices color to gradients (right click on slices, choose "Format Pie Slice" and there choose gradient)
    - generate from Java
    ... and you should see the bug.
    Please let me know if I can remove the connection and if there is any other way to make it easier for you to reproduce this bug.
    Thank you,
    Alex
    PS: I am generating as PDF using printOutputController.export
    Edited by: alexpol on Oct 13, 2011 9:05 AM

  • Large vertical gradients not working like examples

    Hello guys, now this seems to be a very straight forward thing to do and there are loads of tutorials about the subject. None of them are helping me get this right though, and I can't for the life of me figure out what's wrong...
    Im trying to create a simple gui component that has a vertical gradient, simple enough right... I create the sprite, and draw the gradient with beginGradientFill and a matrix with a 90 degree radian angle on it; but it stops working if the sprite has a long width, below is an exmaple of what I mean:
    package
    import flash.display.GradientType;
    import flash.display.Shape;
    import flash.display.Sprite;
    import flash.geom.Matrix;
    public class Main extends Sprite
    public function Main()
    var theWidth : Number = 800;
    var theHeight: Number = 100;
    var shape1:Shape = new Shape();
    var matrix:Matrix = new Matrix();
    matrix.createGradientBox(theWidth , theHeight, Math.PI*0.5, 0, 0);
    var colors:Array = [ 0xffffff, 0x000000];
    var alphas:Array = [ 100, 100];
    var ratios:Array = [ 0, 255];
    shape1.graphics.lineStyle(2,0xa1b0b6);
    shape1.graphics.beginGradientFill(GradientType.LINEAR,colors, alphas, ratios, matrix);
    shape1.graphics.drawRect( 0.0, 0.0, theWidth , theHeight);
    shape1.graphics.endFill();
    addChild(shape1);
    If I change
    matrix.createGradientBox(800, 100, Math.PI*0.5, 0, 0);
    to
    matrix.createGradientBox(800, 100, Math.PI, 0, 0);
    it works fine - but horizontally - why is it that applying 90 degrees the fill does not work?
    Thanks for your help, I really don't know whats wrong with this

    Hi Rob, I'm really confused, if I create a new action script project and use the code i posted I get this:
    As you can see its not going from white to black, but instead it just looks grey - although there is a gradient, it looks like its massive or something :S I don't get it
    Im using flash builder 4, I create a new action script project, in the as file I paste that code into the constructor and run the application.
    ps.. yes i know about the alphas need to be 1, it was a typo when i posted this, setting them to 1 doesn't seem to be my issue. Any other ideas?

  • Gradient (not smooth) has ripples on TV but looks good in Motion canvas?

    Could someone help me fix these ripples in my gradient? I have a gradient color as the background (pink fades to black), it looks smooth on my computer but on my TV monitor it is ripply and choppy as it fades out to black.
    I am working in NTSC DV.
    Thanks
    marco

    When I say render out, I mean exporting your Motion Project as a QT movie.
    I took a look at your project and rendered out a sample in Animation codec 32-bit. I didn't see any visible banding in the bkg peach to black gradient. The yellow circle in the right corner was walking a bit because the edge was harsh, and the yellow was really bright. Also the font is very thin for DV so it will not look that good.
    The font could be thicker, but I was able to address the visual problems with the circle by dropping the Fill Opacity to 90% and to apply a slight feather (4). DV as a codec doesn't like thin lines or sharp edges.
    Again, I didn't see any banding on the bkg gradient though. Even when I rendered out the sample in DV.
    Andy

  • Photoshop CC Shape Layer Gradients Not the Same as CS6

    I'm demo-ing Photoshop CC, and I came across an unexpected behavior when opening a CS6 PSD.
    I have a shape layer that is composed of closed curves which use the path operation "Intersect Shape Areas." In CS6, I added a layer style with a tight gradient that is vertically positioned to show a certain part of the gradient, and the gradient seems to be confined to only the visible intersection of the paths.
    In CC, however, the gradient seems to be applied to the entire region of the paths, and not just the intersection - as if there were no path operation performed. Here's an image to show what I mean:
    The only way I could reproduce the desired effect in CC was to merge the shape components. But, I'd rather be able to keep the shapes editable at a boolean level.
    Is there some setting that I'm missing?

    I don't want to just start a new thread with the same topic so thought I would tag onto this one.
    The behaviour described by K_SEREBY is something which I am also experiencing, and for me is a bit of a deal breaker. For files opened in CC which were created in an earlier version gradient fills/ styles on shape layers do not appear the same.
    The only way to have them appear the same is to do as K_SEREBY says and "merge shape components", which is a completely destructive way of working.
    It isn't something which is consistent either across Layer Styles, gradients behave as described, whereas inner glow, inner shadow and stroke for example all work as they did before, taking into account shape interaction.
    Having said that using the stroke feature of vectors available on the top bar again works differently as shown in the below image. On the left the result of 3 interacting vector shapes with a vector stroke - no stroke visible. On the right the same shape with the same stroke effect but after merge shape components has been done - vector stroke visible.
    It's all very confusing and not very pleasant to use, is there a work around? The video linked doesn't shed any light on the problem at hand, only highlighting something else which doesn't even show up for me when a shape is selected i.e. Live Vector Properties, but that is another story.

  • Fireworks CS6 gradient not working as it did in earlier versions

    I used to be able to let the dropper select colors already used within a gradient and modify those points. Now my only choice is to the select from swatches or settle for #000000 regardless of the color I'm trying to duplicate. Am I missing something here? The functionality is much less efficient now.
    Thanks!

    Hmm, maybe I'm missing something.
    Here's a quick video I created showing how I select colors using the gradient editor. One thing that doesn't show in the video is that as I move the eye dropper over the color ramp, the color selection in the color picker changes. It's very responsive. Now, I am also running Snow Leopard, not Lion, so if you're running Lion, that would be good to know.
    http://jimbabbage.ca/gradient/gradient_editor.htm
    Do you have any other apps running in the background? Wondering if there's a conflict.

  • BUG? Fireworks to DW CSS gradients not consistent across browsers...?

    Greetings -
    I don't know if this is a bug or what, but after watching one of the Adobe TV roadshow videos I generated CSS gradients in Fireworks, selected ALL the browser compatible translations Fireworks provides and then copied/pasted the CSS into my web page in Dreamweaver. Looks good in DW - all seems well...until I view it with Firefox...
    I'm not a Rocket Scientist, but also not a newbie.
    Basically, IE, etc. all work fine EXCEPT Firefox! Firefox maintains the color, but distorts the gradient percentage and reverses the angle of gradient. E.g. if my gradient is going from dark on top to white on the bottom of a box, it all displays fine in the other browsers, but in Firefox the gradient goes left to right, dark to light...
    And yes, I promise I made sure I have the Firefox CSS in addition to the IE, etc. before bothering you all.
    OH! AND I am using the Fluid Grid set up in Dreamweaver...just FYI.
    Am I missing something?
    Do I have to manually update? (i.e., tie a rope around my waist and head on in to the looking glass - code land that is CSS gradients?
    Is there something in DW that needs to be altered after the CSS from FW is added?
    Many thanks for all your help and advice!
    JL

    JLSF45 wrote:
    I don't know if this is a bug or what,
    Yes, it's a bug in the code that Fireworks generates, not in the way that Firefox handles CSS gradients.
    The reason for the problem is that browsers started implementing CSS gradients on an experimental basis long before the W3C standardization process got under way. For some reason, all browsers decided to calculate angles using the polar coordinate system, in which 0 degrees points right and the angles increase counterclockwise. This way of measuring angles appears to be common in geometry, but it's not the way that most people think of them.
    The most common way of measuring angles is to use the compass system: 0 degrees points straight up, and angles increase in a clockwise direction. That's the way the W3C decided angles should be measured in CSS. Because 0 degrees in the polar coordinate system is 90 degrees in the standard CSS syntax, and angles increase in the opposite direction, the only angle that's the same in both systems is 45 degrees.
    Unfortunately, whoever coded the Fireworks panel didn't realize that the standard syntax uses different angles, and nobody picked it up in beta testing. The problem has been reported to Adobe, and I'm told it will be fixed, but I don't know when.
    Until it's fixed, you need to convert the angle in the unprefixed version of linear-gradient().
    Subtract the angle generated by Fireworks from 360.
    Add 90
    For example, if the angle generated by Fireworks is 315deg, 360-315 = 45. 45 + 90 = 135. So change the angle in the unprefixed version to 135deg.
    IE 10 also uses the standard syntax, so the conversion is necessary not only for Firefox, but it will be needed by all browsers.
    This is a rare case of the value for browser-specific prefixes being completely different from the standard syntax.

  • Error Message using Gradients - Not enough solid color

    "This library cannot be used because it does not have enough solid color swatches. Gradients and patterns cannot be used." What does this error message mean when I am trying to use gradient swatches and how to do I stop it?

    Step 1: Click on the Color Guide Dropdown
    Step 2: Select Gradients
    Step 3: Get Error Message

  • Bad gradients(not smooth)

    Hello everyone.
    I am using a Unibody MBP 2.4
    Everything seems fine and I had no issues with it - or the screen.
    But today I noticed a weird thing about the screen. I created a radial gradient on Photoshop, and it seems really bad. Circular lines appear inside the radial gradient, which makes it look not smooth.
    It's like it's missing some colors (If you create a radial gradient then go to System Preferences - Display Settings and use Thousands colors instead of Millions then look at the gradient again you will notice what I am talking about).
    I also tried several calibrated profiles but none seem to have solved the problem.
    Any suggestions?
    Thanks in advance.
    Message was edited by: ZenorGR

    Hello, I have a similar problem with the pix on any web browser. Very bad resolution and everything is gradient. I am wondering if anyone has experienced such a thing... I am very upset. The reseller tells me its a general issue and that I should wait for an update fix.

  • Lock Fill for Gradient Not Working (like it used to)

    This used to work on my last version of Flash (CS5.5):
    I use the brush tool to paint a gradient fill area. I then sample it with the eyedropper tool (either right afterwards or later) and notice that the Lock Fill tool option is now on. So far so good. I then continue painting, expecting the gradient to extend itself, because Lock Fill is now on. Instead, a solid fill color (somewhere between the 2 color stops) is painted. The only way I can extend the gradient is to paint the new fill area, then sample the original gradient fill and use the Paint Bucket on the new fill area. Argh...
    Is this a bug, a Flash setting that I can modify somewhere, or a planned change in the way Lock Fill works? I've tried this on 2 PC's running Windows 7 and get the same result.

    Please see DownloadHelper support for help with their add-on.

Maybe you are looking for