Hi friend!

I'm working on getting this into my project (as it is the missing link to getting working; thank you so much!) and I noticed it's not published to npm. I'll probably work it so I can use it personally as an npm module; do you have any interest in using the UMD format so that your module can be consumed by both Bower and npm users?

Hi, default params with this image: https://www.facebook.com/photo.php?fbid=10107296866472911&l=bb741fb5ef

Generates these results:

It would be nice to auto detect if an image is B&W and only generate a palette on the grayscale.

I'am using vibrant.js with angular 4 , and exprience an issues that the canvas didn't removed from the body and i call it like that `

let v = new Vibrant(changes.toPlayRadio.currentValue.pic);
v.getPalette((err, palette) => {
  var rgb = palette.Vibrant.getRgb()
  this.radioBackground =
  {
    'background' : 'rgb('+rgb[0]+','+rgb[1]+','+rgb[2]+');'
  }
});

`

Hello!

While watching the I/O's "Material now" presentation this year I've noticed that from an album art they got the primary/accent color using Palette.

When I tried to do the same using vibrant.js the colors they got are nowhere to be found.

Is it just a further post processing provided by the player app or should vibrant.js return the right colors using the Material Pelette?

Trying out vibrant.js in the jsfiddle on the webpage fails, returning the follow error: /TypeError: cmap.vboxes is undefined

Edit: just noticed the disclaimer regarding image dropping only working in Chrome. Why is this the case?

hello, i find vibrant.js will set a global variable index

https://github.com/jariz/vibrant.js/blob/master/dist/Vibrant.js#L143

i think this can fix it

// https://github.com/jariz/vibrant.js/blob/master/dist/Vibrant.js#L134-L152
        count: function(force) {
            var vbox = this,
                histo = vbox.histo;
            if (!vbox._count_set || force) {
                var npix = 0,
                    i, j, k, index;  // add index here
                for (i = vbox.r1; i <= vbox.r2; i++) {
                    for (j = vbox.g1; j <= vbox.g2; j++) {
                        for (k = vbox.b1; k <= vbox.b2; k++) {
                            index = getColorIndex(i, j, k);
                            npix += (histo[index] || 0);
                        }
                    }
                }
                vbox._count = npix;
                vbox._count_set = true;
            }
            return vbox._count;
        },

sorry that i don not know coffee js

Currently, the demo site is a pretty good example for this: if you change the size of your browser, the palette will change. This is of course caused by the image size changing, and because of Vibrant not loading every single pixel (only the 5th, each time, by default, as configured by the quality parameter)

For more consistent results, Vibrant should resize the image to a default set max size before getting swatches from it. Maybe even instead of grabbing every fifth pixel, it should grab every pixel when it's downscaled. (unless performance takes a hit)

Palette does this as well.

The current Vibrant release gives an error like this.

Vibrant.js:651 Uncaught (in promise) TypeError: Cannot read property 'map' of undefined
    at new Vibrant (Vibrant.js:651)
    at workList.js:89
    at Array.forEach (<anonymous>)
    at workList.js:86
    at <anonymous>

Where the code calling Vibrant is

const image = new Image(200, 200);
            image.src = item.fields.image.fields.file.url;
            const vibrant = new Vibrant(image);
            const swatches = vibrant.swatches();
            alert(swatches[0].getHex());

This PR addresses https://github.com/jariz/vibrant.js/issues/20 by updating the quantize dependency to point at the most recent version of the github repo (the fix was introduced in 1.0.2, which is not yet published to npm; https://github.com/olivierlesnicki/quantize/pull/1) and rebuilding.

I'm including Vibrant in my project using JSPM. I get the following error Error: Error loading "quantize" at file:/path/to/project/folder/quantize.js

Do you know what might be the issue?

Causes Firefox and Chrome to grind to a complete halt :\

"But why would you hide the image that you're trying to accentuate I don't even what"

I'm doing some dynamic styling in the browser and I was hoping to hide the image element itself, using it only as the source to script in a background-image with background-size: cover and dynamic background/text overlay color values (provided by Vibrant.js)

But that's besides the point, checking the image dimensions or display properties before copying the image to a new canvas element might be a good idea idk

Love the library, ran into this just now, thought I'd say something =)

Muted variations were not being filled if empty, this adds them so they're available from Vibrant. Also, try filling Vibrant from LightVibrant (if available). This fixes https://github.com/ismamz/postcss-get-color/issues/3 and https://github.com/akfish/node-vibrant/pull/51