Two million pixels

Hi. After uploading my ePub file using iTunes Producer, I got an email from apple:
Your book, vendor ID: ... , could not be delivered. The following images are larger than two million pixels and must be resized:
I had a look at all my images that I'm using inside my ePub. No one is even close to two million pixels. Anyone has an idea what could be the problem?
I'm using the latest version of Pages to create the ePub file.
Thanks!

Your image at 1100 x 1676 ( W x H =) calculates around 1,845,000 pixels - so within the 2mill limits.
Sorry I actually explained things badly. The informations can be found in the iBooks Asset Guide which you can download from the main page in your iTunesConnect account.
Apple are not always good at changing their systems/methods and then letting people know.
In real terms, you are correct about the Cover image. During upload the main images for them are the cover and screenshots. After the Retina Display came out - images needed to be better.
Apple iPad Retina specifications on the stores sales info shows the resolutions to be 2048 x 1536 @ 264 DPI or PPI (Pixels per inch) or 3.1 million Pixels. (Anybody resizing images should remember to set the PPI before adjusting the image dimentions and really 150 is enough.)
I only use iBookAuthor, but I am aware that other use InDesign and other applications to create ePubs and publish to the iBookstore. For simplicity, I use either Photoshop or PS Elements to do a multi file process and convert my selected images to Landscape 2048 width and Portrait 1536 width. The cover I deal with as previously explained.
In effect as you found, basically any combinations of sizes - when using the above equation fall under the 3.1 M pixels, should be acceptable to the review team.
I think that when a new iTunesConnect account is opened, if Apple sent out an auto confirmation email which included links to the asset guide and other relevant information.. it would save a lot of confusion!
Hope your book is a great success....

Similar Messages

My ipad3 has two struck pixel, what should I do? may I replace a new one, I just brought it before half year

my ipad3 has two struck pixel, what should I do? may I replace a new one, I just brought it before half year

they replaced my ipad3 by a new one. I gave the ipad3 to them and asked them to check, they said it's one dot only, I said it's not one dot, there are may dots merge together, so they replaced my ipad3 by a new one. thanks a lot

What are the pixel dimensions for creating an Apple ibook book cover?

I'm trying to create a book cover for Apple ibooks, what are the pixel dimensions requirements?

Thanks again.
Apple seems to have made it more confusing than it should be.
As an aside, the Apple documentation contradicts itself.
Cover art (also known as a marketing image or jacket) should be at least 1400 pixels along the smaller axis and must be a JPEG or PNG file in RGB Color mode.
This clearly says the shorter side must be at least 1400 pixels. The next sentence says this:
For an average trade paperback, this could be 400 x 1400 minimum size, as the books are generally taller than they are wide.
That doesn't make sense, seeing that the shorter side is supposed to be at least 1400 pixels, meaning it should say "1400 x 4900" for the same aspect ratio.
...I did notice this too.
So, if as you say, that the Cover Art and Cover image terms are the same and the 2 million limit does not apply, then it is unclear to me why Apple sent this message to me about cover file being rejected
"Action Required: Your book could not be delivered to the iBookstore.
The following images are larger than two million pixels and must be resized:
Full ePub: Cover_xyz.jpg "
I'll probably need to have the cover file in epub and Cover Image for Asset in iTunes Producer be named differently (but be copies of the same file) so I can understand which one is the "problem" file.
And finally, why does Apple refer to Cover Art twice here and then end in last sentence with Cover Image if they are the same ( and if they are the same why not state "this cover image").
"Cover art (also known as a marketing image or jacket) should be at least 1400 pixels along the smaller axis and must be a JPEG or PNG file in RGB Color mode. For an average trade paperback, this could be 400 x 1400 minimum size, as the books are generally taller than they are wide. For best results, deliver the largest pixel dimensions possible. When possible, match cover art to the cover contained in the book file. The 2 million pixel maximum does not apply to the cover image".

2 Milllion Pixels

Hi. After uploading my ePub file using iTunes Producer, I got an email from apple:
Your book, vendor ID: ... , could not be delivered. The following images are larger than two million pixels and must be resized:
I had a look at all my images that I'm using inside my ePub. No one is even close to two million pixels. Anyone has an idea what could be the problem?
I'm using the latest version of Pages to create the ePub file.
Thanks!

It's the total of the pixels, so multiply width and height, and that's what your pixels are at.

Definitive cover size for books on iPad?

My iTunes Producer uploads keep failing and I get this "support" message:
Your book, vendor ID: XXXXXXXXX, could not be delivered. The following images are larger than two million pixels and must be resized:
Full ePub:
/OPS/CoverDesign.jpg..."
This contradicts an earlier "error" trying to upload the book when it told me my dimensions were too small at 1200 x 1920, and that I should make the width 1400 pixels.
Can anyone provide a definitive size - or at least a maximum width or height?

Minimum WIDTH for a cover is 1400.
If you use an image editor which allows allows adjustments of width and height and "constraint" or any option that locks the two dimension undo and select only width at 1400 at 72 ppi/dpi what ever you get back - is OK.
For what its worth I create the cover in iBA, zoom out so I can see all the corners and do a screen grab using Snagit. I edit that with Snagit or Adobe Fireworks as above.
You can get more information in the iBooks Author Asset Guide - download it from your iTunes Connect page

Action Required: Your book could not be delivered to the iBookstore

Hi Everyone,
I had a book up on iBooks without any problems but an editor found a couple of corrections that needed to be addressed. Those are now corrected but the problem I am running into now is right after the package is delivered, I get an email telling me that the book could not be delivered to the iBookstore. The message tells me that two image files are too large (larger than two million pixels). This is perplexing to me in a couple of ways; 1.) I did not edit any of the image files, only text and 2.) the filenames mentioned in the email are no where in the original Pages document.
If anyone has some suggestions, I'd greatly appreciate it!!
Many thanks

You think it's a book?
's going to approve?

Pixel VS DPI - Need to have a quick question cleared up!

Hello Adobe Forums!
I would consider myself an experienced designer, but I have a question that might seem rather mundane. To be completely honest, I just think I have overthought/overanalyzed it to a point where I confused myself!
In Photoshop, I have a 300 DPI psd image, that image size is 2"x1" and is 600x300px.
Now, my question is: is there a way to reduce the DPI in an effort to increase the pixels?
My goal is to have a larger amount of pixels at 72dpi for a web image. The theory makes sense in my head, but when put into practice, my image loses its quality. I need it to be sharp.
Aside from all of this, if I do have to end up resampling, are there other programs that resample more effectively than Photoshop?
Thanks in advance!

Exactly. Web images have no PPI, only the pixel dimensions. Your image is 600px x 300px; ignore the 300 PPI, ignore the 2" x 1". Focus only on the 600px x 300px. When you use this image in a web layout, it will take up exactly 600px x 300px. Whether or not that size works for what you're trying to do is up to you, it is what it is. But the image is not 72 PPI or 300 PPI or any other PPI, since you're not printing it.
In fact, even images destined for print don't have a specific PPI until you set the size at which they will be printed. Photoshop provides the PPI of the image based on a particular output size for convenience, but the only true measure of the resolution of a digital image are the pixel dimensions, period.
Here's a short article I wrote for our customers w/ digital cameras, to explain digital resolution and print resolution:
WHAT IS RESOLUTION?
The resolution of a digital image is the number of pixels it contains, plain and simple. If you open an image into Photoshop and go to Image > Image Size, the top section of the dialog box shows you the total number of pixels in your image. This is the actual resolution of the image, independent of the size you plan to use it.
For example, a photo taken with a Canon Digital Rebel XSi might have a resolution of 4272 x 2848. This means there are 4272 pixels across, and 2848 pixels down, that make up the image.
Most digital cameras are rated as a certain number of "megapixels." A megapixel is one million pixels, and camera manufactures calculate the megapixels by multiplying the maximum width by the maximum height that their camera can capture. In the example above, the Digital Rebel XSi is a 12 megapixel camera (4272 times 2848 = 12,166,656 pixels).
HOW BIG IS A PIXEL?
A pixel has no size of its own, it is simply the smallest single "unit" in a digital image. In fact, the word pixel derives from the term "picture element." If you zoom in close enough in Photoshop you can see all the individual pixels that make up an image. (In Photoshop CS4 there is also a pixel grid that you can enable to make it easier to see.)
SO WHAT ABOUT PPI?
You've probably heard a lot about pixels per inch (PPI) or dots per inch (DPI), but what does that actually mean?
Pixels per inch is a relative measurement of resolution, that takes into account the size you're going to print the image. Now there's a mouthful! Don't let that confuse you, though, it's actually really simple to calculate: take the total number of pixels and divide by the size you plan to use it.
So for example, if you take that 4272 x 2848 image I mentioned earlier and print it 10 inches wide, the resolution would be 427.2 PPI (4272 divided by 10).
For optimum print quality, we look for 300 PPI at print size, and a similar calculation will tell you how big you can print your images. Using that same image, take 4272 and divide by 300. The result is 14.24, so you can print that image as large as 14.24" without the image looking low-res or pixellated, or without doing any resampling in Photoshop.
Oh, and the proper unit of measurement for the resolution of a digital image at a particular print size is PPI. The proper unit of measurement of the resolution of an output device is DPI. The two are not synonymous nor interchangeable -- images never contain dots, only pixels, and printers never print with pixels, only dots.
OK, SO YOU'RE SAYING RESOLUTION AND PPI ARE NOT THE SAME THING?
Right. They're related, but not the same. The easy way to think about this is that PPI is the "print resolution" of the image.
Let's look at another example: say you have an image that is 1500 pixels x 1500 pixels, and you print it at 5" wide. 1500 divided by 5 is 300 PPI. If you print the same image at 10" wide, 1500 divided by 10 is 150 PPI. The print resolution has changed because you're using the image at a much larger size, but the actual resolution of the image (1500 x 1500) has not changed.
CAN'T I JUST INCREASE THE RESOLUTION IN PHOTOSHOP?
You can, but it's not the same as if the image had the correct resolution to start with.
If you ask Photoshop to increase the resolution of an image, it needs to calculate how to add all those new pixels you're asking for. It uses some pretty complex algorithms to do this, but it's still "inventing" pixels that were never there. There is a limit to how much you can artificially increase the resolution of an image without it being visible (either as blurriness or jaggedness). And don't forget: a low-resolution original doesn't contain as much detail as a high-res image. Photoshop can only interpolate from the data that exists in the file, so it won't magically add in all that missing detail.
A good rule of thumb is if your image would be less than 225 PPI or so at the size you want to use it, you would be better off retaking the photo than upsampling in Photoshop. Anything less than that and it will almost certainly appear low-res when printed, and you would see artifacts if you upsample it.

Only writing Integer pixel array to a .txt file,or showing in Frame

Sir,
I want to write integer values (range:0 to 255) to a .txt file .Actually after manipulating a .jpeg/.gif image I have gotten a 2D pixel array and a 1D pixel array that can be easily shown in console but I want to write this pixel array into a .txt file. Using of writeInt() is not working. Actually after using this faction the created file contain information which is non-alphanumeric /alphanumeric characters......
following is error free the code: Plz. See only and only into the �class TestImage�and plz look after line marked by //�my_problem_to_be_resolved.�It is just few lines of code .I promise you will not be bothered.Plz��..
import java.awt.*;
import java.io.File;
import java.io.FileWriter;
import java.awt.image.*;
import java.io.*;
import java.util.*;
import javax.imageio.*;
import javax.imageio.stream.*;
import java.awt.image.Raster;
import java.awt.image.WritableRaster;
class Image {
protected int width,height;
// 'samples' stores the image pixel values.
protected int[][] samples;
// Constructor: Reads the image from the
// specified file name.
public Image(String filename)
throws Exception { read(filename); }
// Returns the pixel width of the image.
public int getWidth() { return width; }
// Returns the pixel height of the image.
public int getHeight() { return height; }
// Reads the image from the specified file
// name into the 'samples' array. Throws an
// exception if the image is stored in an
// unsupported file format (currently only
// .GIF, .JPG, and .PNG are supported by Sun).
public void read(String filename)
throws Exception {
// Extract the file name suffix.
String ext = filename.substring
(filename.indexOf('.')+1);
// Create a file object for the file name.
File fileImage = new File(filename);
// Get a list of ImageReaders that claim
// to be able to decode this image file
// based on the file name suffix.
Iterator imageReaders = ImageIO.
getImageReadersBySuffix(ext);
ImageReader imageReader;
// Grab the first ImageReader in the list.
if (imageReaders.hasNext())
imageReader = (ImageReader)
imageReaders.next();
// If we get here we cannot decode the image.
else throw new IIOException
("Unsupported image format");
// Create a file input stream object to
// read the image date.
FileImageInputStream imageInputStream =
new FileImageInputStream(fileImage);
// Tell the ImageReader object to read data
// from our file input stream object.
imageReader.setInput(imageInputStream);
// Get the width and height of the image.
width = imageReader.getWidth(0);
height = imageReader.getHeight(0);
// Read the image from the file input stream,
// and close the input stream when done.
BufferedImage bufImage =
imageReader.read(0);
imageInputStream.close();
// Get a raster object so we can extract the
// pixel data from the BufferedImage.
WritableRaster wRaster =
bufImage.getRaster();
// Create our 'samples' 2d-array.
samples = new int[height][width];
// Extract the image data into our 'samples'
// array.
for (int row = 0; row < height; row++)
for (int col = 0; col < width; col++)
samples[row][col] =
wRaster.getSample(col,row,0);
// Write the image stored in the 'samples'
// array to the specified file. The file name
// suffix should be a supported image file
// format (currently either .JPG or .PNG).
public void write(String filename)
throws Exception {
// Extract the file name suffix.
String ext = filename.substring
(filename.indexOf('.')+1);
// Create a file object for the file name.
File fileImage = new File(filename);
// Get a list of ImageWriters that claim to
// be able to encode images in the specified
// image file format based on the file name
// suffix.
Iterator imageWriters = ImageIO.
getImageWritersBySuffix(ext);
ImageWriter imageWriter;
// Grab the first ImageWriter in the list.
if (imageWriters.hasNext())
imageWriter = (ImageWriter)
imageWriters.next();
// If we get here we cannot encode the image.
else throw new IIOException
("Unsupported image format");
// Create a file output stream object to
// write the image data.
FileImageOutputStream imageOutputStream
= new FileImageOutputStream
(fileImage);
// Tell the ImageWriter to use our file
// output stream object.
imageWriter.setOutput
(imageOutputStream);
// The ImageWriter.write() method expects a
// BufferedImage. Convert our 'samples' array
// into a BufferedImage.
BufferedImage bufImage =
createBufferedImage();
// Encode the image to the output file.
imageWriter.write(bufImage);
imageOutputStream.close();
// Draws the image stored in the 'samples'
// array on the specified graphics context.
public void draw(Graphics gc,int x,int y){
BufferedImage bufImage =
createBufferedImage();
gc.drawImage(bufImage,x,y,null);
// Converts the 'samples' array into a
// BufferedImage object. Students do not have
// to understand how this works.
private BufferedImage
createBufferedImage() {
// Create a monochrome BufferedImage object.
BufferedImage bufImage = new
BufferedImage(width,height,
BufferedImage.TYPE_BYTE_GRAY);
// Create a WriteableRaster object so we can
// put sample data into the BufferedImage
// object's raster.
WritableRaster wRaster =
bufImage.getRaster();
// Copy the 'samples' data into the
// BufferedImage object's raster.
for (int row = 0; row < height; row++)
for (int col = 0; col < width; col++)
wRaster.setSample
(col,row,0,samples[row][col]);
// Return the newly created BufferedImage.
return bufImage;
} // End of Class Image
class TestImage {
public static void main(String args[])
throws Exception {
// Create a frame to display the image.
Frame frame = new Frame("Test Image");
frame.setSize(1024,768);
frame.setVisible(true);
Graphics gc = frame.getGraphics();
try {
// Read the image from the file.
Image img = new Image("C:/lilies.jpg");
int height=img.getHeight();
int width =img.getWidth();
//�my_problem_to_be_resolved.�
     File image_object_arry=new File("C:/Image_array.txt");
     FileOutputStream image_object_arry_stream= new FileOutputStream(image_object_arry);
     DataOutputStream int_image_object_arry_stream=new DataOutputStream(image_object_arry_stream);
//Conversion of two dimensional pixel arrry into one dimensional array
int intPixels1[] = new int [height * width];
int k = 0;
for(int i = 0; i <= width; i++) {
for(int j = 0; j <= height; j++) {
intPixels1[k] = img.samples[i][j];
int_image_object_arry_stream.writeInt((int) intPixels1[k]);
// System.out.println(intPixels1[k]);
k = k+1;
import java.awt.*;
import java.io.File;
import java.io.FileWriter;
import java.awt.image.*;
import java.io.*;
import java.util.*;
import javax.imageio.*;
import javax.imageio.stream.*;
import java.awt.image.Raster;
import java.awt.image.WritableRaster;
class Image {
protected int width,height;
// 'samples' stores the image pixel values.
protected int[][] samples;
// Constructor: Reads the image from the
// specified file name.
public Image(String filename)
throws Exception { read(filename); }
// Returns the pixel width of the image.
public int getWidth() { return width; }
// Returns the pixel height of the image.
public int getHeight() { return height; }
// Reads the image from the specified file
// name into the 'samples' array. Throws an
// exception if the image is stored in an
// unsupported file format (currently only
// .GIF, .JPG, and .PNG are supported by Sun).
public void read(String filename)
throws Exception {
// Extract the file name suffix.
String ext = filename.substring
(filename.indexOf('.')+1);
// Create a file object for the file name.
File fileImage = new File(filename);
// Get a list of ImageReaders that claim
// to be able to decode this image file
// based on the file name suffix.
Iterator imageReaders = ImageIO.
getImageReadersBySuffix(ext);
ImageReader imageReader;
// Grab the first ImageReader in the list.
if (imageReaders.hasNext())
imageReader = (ImageReader)
imageReaders.next();
// If we get here we cannot decode the image.
else throw new IIOException
("Unsupported image format");
// Create a file input stream object to
// read the image date.
FileImageInputStream imageInputStream =
new FileImageInputStream(fileImage);
// Tell the ImageReader object to read data
// from our file input stream object.
imageReader.setInput(imageInputStream);
// Get the width and height of the image.
width = imageReader.getWidth(0);
height = imageReader.getHeight(0);
// Read the image from the file input stream,
// and close the input stream when done.
BufferedImage bufImage =
imageReader.read(0);
imageInputStream.close();
// Get a raster object so we can extract the
// pixel data from the BufferedImage.
WritableRaster wRaster =
bufImage.getRaster();
// Create our 'samples' 2d-array.
samples = new int[height][width];
// Extract the image data into our 'samples'
// array.
for (int row = 0; row < height; row++)
for (int col = 0; col < width; col++)
samples[row][col] =
wRaster.getSample(col,row,0);
// Write the image stored in the 'samples'
// array to the specified file. The file name
// suffix should be a supported image file
// format (currently either .JPG or .PNG).
public void write(String filename)
throws Exception {
// Extract the file name suffix.
String ext = filename.substring
(filename.indexOf('.')+1);
// Create a file object for the file name.
File fileImage = new File(filename);
// Get a list of ImageWriters that claim to
// be able to encode images in the specified
// image file format based on the file name
// suffix.
Iterator imageWriters = ImageIO.
getImageWritersBySuffix(ext);
ImageWriter imageWriter;
// Grab the first ImageWriter in the list.
if (imageWriters.hasNext())
imageWriter = (ImageWriter)
imageWriters.next();
// If we get here we cannot encode the image.
else throw new IIOException
("Unsupported image format");
// Create a file output stream object to
// write the image data.
FileImageOutputStream imageOutputStream
= new FileImageOutputStream
(fileImage);
// Tell the ImageWriter to use our file
// output stream object.
imageWriter.setOutput
(imageOutputStream);
// The ImageWriter.write() method expects a
// BufferedImage. Convert our 'samples' array
// into a BufferedImage.
BufferedImage bufImage =
createBufferedImage();
// Encode the image to the output file.
imageWriter.write(bufImage);
imageOutputStream.close();
// Draws the image stored in the 'samples'
// array on the specified graphics context.
public void draw(Graphics gc,int x,int y){
BufferedImage bufImage =
createBufferedImage();
gc.drawImage(bufImage,x,y,null);
// Converts the 'samples' array into a
// BufferedImage object. Students do not have
// to understand how this works.
private BufferedImage
createBufferedImage() {
// Create a monochrome BufferedImage object.
BufferedImage bufImage = new
BufferedImage(width,height,
BufferedImage.TYPE_BYTE_GRAY);
// Create a WriteableRaster object so we can
// put sample data into the BufferedImage
// object's raster.
WritableRaster wRaster =
bufImage.getRaster();
// Copy the 'samples' data into the
// BufferedImage object's raster.
for (int row = 0; row < height; row++)
for (int col = 0; col < width; col++)
wRaster.setSample
(col,row,0,samples[row][col]);
// Return the newly created BufferedImage.
return bufImage;
} // End of Class Image
/*class TestImage {
public static void main(String args[])
throws Exception {
// Create a frame to display the image.
Frame frame = new Frame("Test Image");
frame.setSize(1024,768);
frame.setVisible(true);
Graphics gc = frame.getGraphics();
try {
// Read the image from the file.
Image img = new Image("C:/srk.jpg");
// Display the image.
img.draw(gc,10,40);
// Flip the image upside down
//img.flipX();
// Display the flipped image.
img.draw(gc,20+img.getWidth(),40);
// Write the new image to a file
img.write("HorseNew.jpg");
} catch (Exception e) {
System.out.println
("Exception in main() "+e.toString());
class TestImage {
public static void main(String args[])
throws Exception {
// Create a frame to display the image.
Frame frame = new Frame("Test Image");
frame.setSize(1024,768);
frame.setVisible(true);
Graphics gc = frame.getGraphics();
try {
// Read the image from the file.
Image img = new Image("C:/lilies.jpg");
int height=img.getHeight();
int width =img.getWidth();
File image_object_arry=new File("C:/Image_array.txt");
FileOutputStream image_object_arry_stream=new FileOutputStream(image_object_arry);
     DataOutputStream int_image_object_arry_stream=new DataOutputStream(image_object_arry_stream);
//Conversion of two dimensional pixel arrry into one dimensional array
int intPixels1[] = new int [height * width];
int k = 0;
for(int i = 0; i <= width; i++) {
for(int j = 0; j <= height; j++) {
intPixels1[k] = img.samples[i][j];
int_image_object_arry_stream.writeInt((int) intPixels1[k]);
// System.out.println(intPixels1[k]);
k = k+1;
catch (Exception e) {
System.out.println("Exception in main() "+e.toString());
catch (Exception e) {
System.out.println("Exception in main() "+e.toString());
}

My Friend, you need to put your code within CODE tags
And I suspect if anyone would go through your code this way.
Assuming your problem is to write pixel values to a file you may use this,
      try{
        // Create file
        FileWriter fstream = new FileWriter("out.txt");
        BufferedWriter out = new BufferedWriter(fstream);
        for(int i =0; pixels.length() ; i++)
          out.write(pixels[i]+"\t");
       //Close the output stream
       out.close();
       }catch (Exception e){//Catch exception if any
      System.err.println("Error: " + e.getMessage());
    }

24' Cinema Display with Dead Pixel

I just exchanged an LED Cinema Display under AppleCare for the blinking/cord problem. Got the new one set up and see that it has a dead pixel. Is there a fix for these, especially being brand new, or do I have to exchange this one too?
Running tests it is very visible on a black background, then blue, and slightly on a green background. Red and white backgrounds make it so that the pixel is not a visible problem.

When I chose my LED Display, I refused two monitors because of dead pixels (green pixels on full filled white background). All of them I tried to order in on-line shops.
When I found out that Apple use LG panels for the LED Display and I understood that I have to go to the off-line shop and choose the display by myselfl. I met 2 years ago with usual LG TFT displays on my work - they all had dead pixels. (IMHO, LG is not good).
I came to one shop and there were 2 Apple LED displays - one at the exposition and one in the storehouse. Of course I wanted new one from storehouse and let manager know beforehand about not going to buy if dead pixels. He brought up the display from storehouse, unpacked, plugged and I personally start to check. I changed the background to whole white and pointed into two green pixels. "***", - I said to the manager - couldn't believe that the display costs crazy money (in Ukraine - $1400-1500) and everyone with dead pixels!
I also have 20" NEC display with perfect IPS panel that I bought 3 years ago for $800. And I should leave the buying of the Apple LED Display and back to my favourite and proven NEC it could be the right decision as you'll see below .
But the manager offer me to check the exhibition example - he assured me that exhibition one is also absolutely new and stood only 5 days in the shop. We plug it, set the background to white and ... "O, miracle! No dead pixels! After three checked displays! Can't belive!" - and this one was really total perfect.
So I forgot about to buy new NEC instead of Apple display. Brought Apple LED Display to home, connected to my brand new MBP 13, compared to my old NEC - everythnig was perfect, colors and overall picture are better than old NEC.
I was happy ... BUT JUST FOR ONE WEEK! It started to blink/flash/blackout - this is the known problem as I found out later: http://discussions.apple.com/thread.jspa?threadID=1902288&tstart=0
I'm very disappointed because I realize that if I give it for guarantee service and they offer me to change it - I'm sure that I'll got the display with dead pixels and I don't want it! So I hope that it the software/firmware trouble and it'll be fixed in the next MacOS update. If no - it'll be the disaster because I'll not be able to return the display and give my money back from the one hand (under Ukrainian laws the money back period of goods is 14 days), and I don't want to give the guarantee replacement with dead pixels!
Sorry for large text I had to to unburden myself!

How to deal with different Pixel Ratios?

Hi, I have a project in which I use two different pixel ratios (0.9) and (1.2). Now of course, they both look squished, and not only that but the exporting of the file is completely messed up, with black bars and still some squishiness. Does anyone know any easy way to fix this? I have hundreds of files which are of different pixel ratios. If they need to be the same ratio going in, how is it that I can BATCH convert them to the same one? Since it would be such a pain to do them individually. Thank you so much for your time!

First decide on your output format, 16x9 or 4x3. Once you have made that decision, create a sequence in that format and use scale to frame size in the preferences before importing those clips. Do not scale up to lose the black borders, unless you don't care about the quality.

Dead Pixel

I purchased the I pod 4g 32gb during x-mas week from Future shop and reticently I discovered that there were two dead pixel on the screen. I noticed it when booting the device, the two white dotes popped right out of the black background. I have never dropped the ipod and it is generally in very good condition with the limited time that I had it for.
So now I'm wondering...
1. If I can exchange the ipod for a new one/ refurbished or will they repair the defect.
2. Do I go to Future shop or the Apple store for the exchange/ repair (might have lost the receipt)
3. Do I take the original packaging with all items provided.

- Apple may or may not replace your iPod with a refurbished one. See:
http://support.apple.com/kb/HT4044
(About LCD display pixel anomalies for Apple products released in 2010 and later)
- You normally do not need a receipt. See the following or warranty coverage:
https://selfsolve.apple.com/agreementWarrantyDynamic.do
- Contact Apple for what specifically to return.

Draw line between black pixel : coordinates of selected pixels ?

Hi
I want to build a script which can check a Photoshop file and :
- find black pixel
- for each black pixel, look for another black pixel within maximum distance of 5 pixels
- then draw a line between the two black pixels.
I wrote this script below (my first script ...), but it's VERY slow (and my final image is VERY big), I think because I test the colour for each pixel of the image.
So another solution would be to first select black pixel with magic wand, then the script save all coordinates of selected pixels, then my script wil test only this pixels (less than 1% of the pixels are black in my image).
Is it possible with JavaScript ?
Thank you for your response !
Marc
function main(){
var startRulerUnits = app.preferences.rulerUnits;
app.preferences.rulerUnits = Units.PIXELS;
var myHeight = app.activeDocument.height;
var myWidth = app.activeDocument.width;
// Find black pixel
for(var i=5; i<myWidth; i++) {
for(var j=5; j<myHeight; j++) {
   activeDocument.colorSamplers.removeAll()
   var sampler = activeDocument.colorSamplers.add([new UnitValue (i, 'px'), new UnitValue (j, 'px')]);
   if (sampler.color.rgb.hexValue === "000000") {
// For each black pixel, search another black pixel below left up to 5 pixels
    for (var m=i-5; m<i; m++) {
     for (var n=j+1; n<j+5; n++) {
      activeDocument.colorSamplers.removeAll()
      var test = activeDocument.colorSamplers.add([new UnitValue (m, 'px'), new UnitValue (n, 'px')]);
      if (test.color.rgb.hexValue === "000000") {
// Then draw a black line between the two black pixels
       var FillColour = new SolidColor;
       FillColour.rgb.hexValue = '000000';
       var ad=activeDocument;
       ad.selection.select([[m,n],[i,j],[m,n+1],[i,j+1]], SelectionType.REPLACE, 0, true);
       ad.selection.fill(FillColour);
       ad.selection.deselect()
// For each black pixel, search another black pixel below right up to 5 pixels
     for (var m=i+1; m<i+5; m++) {
      for (var n=j; n<j+5; n++) {
       activeDocument.colorSamplers.removeAll()
       var test = activeDocument.colorSamplers.add([new UnitValue (m, 'px'), new UnitValue (n, 'px')]);
       if (test.color.rgb.hexValue === "000000") {
// Then draw a black line between the two black pixels
        var FillColour = new SolidColor;
        FillColour.rgb.hexValue = '000000';
        var ad=activeDocument;
        ad.selection.select([[i,j],[m,n],[m,n+1],[i,j+1]], SelectionType.REPLACE, 0, true);
        ad.selection.fill(FillColour);
        ad.selection.deselect()
main();

The first alert should have shown the first pathPoint.anchors for all the subPaths in the path.
The xyArray is just something I added for the alerts. The array 'myPathInfo' should have all the info extracted from the path.
myPathInfo.length will tell you how many subPaths are in the Path.
myPathInfo[index].entireSubPath.length will tell you how many pathPoints are in that subPath
myPathInfo[index].entireSubPath[index].anchor will tell you the position of that pathPoint.
The indexes start with zero.
The bounding box of the entire subPath can be hard to work out just from the pathPoints. Unless all the point are corner points the path may extend beyond the anchors. One think you can do is create a new path from just one of the subPaths, convert by to a selection, and then get the bounds from the selection. You can make a new path from a subPath using the 'myPathInfo' array from above.
app.activeDocument.pathItems.add("myPath1", [myPathInfo[0]]);
That line will make a new path from the first subPath. Change the index to use a different subPath.
Some other info that may help.
app.activeDocument.histogram[0] will tell you how may black pixels are in the document. But its no help determining where they are. If that returns 0 there are no black pixels.
If you don't have any luck working with converting the original color range selection into a path and need to go back to searching with the colorSampler it may help to use a grid approach. For example make a square selection, the size depending on how scattered the black pixels are, say 25x25px. Then use color range to select black. With an active selection it will only select pixels in that selected area( if any). You could then check to see if there is a selection. If not make another same size square to the right edge of the last area. If there is a selection, the solid property will tell you if more than one black pixel was selected( unless they are right next to each other ). If solid == true the selection bounds will tell you where the pixel is. If false you have to then search that square. But if there are areas where there are no black pixels checking a square range of pixels at once should be quite a bit faster than checking every pixel. And checking the historgram first will let you know if you should bother searching to start with.

2 dead pixels near bottom after 2 months. replacable?

In addition to the two new dead pixels near the bottom edge of my screen, i also have these two LCD issues with my MB:
http://discussions.apple.com/thread.jspa?threadID=942825&tstart=0
and
http://discussions.apple.com/thread.jspa?threadID=940945&tstart=0
I've already taken it in to try and get a replacement for the lines, but they said it was normal. I havent taken it in for the spots on the black background yet since I had doubts that they'll warrant the replacement since it's only noticeable on a black screen with little light in the room.
i now have two dead pixels near the bottom and am starting to think i should take it in to try and get a replacement. I do have the 3 year applecare plan as well.
What do you think? Anyone had their MB's replaced for bad pixels after a few months of use? Thanks.
Ryan

in the dozens of MB's i've seen in stores, i did notice that only a few had the lines issue that i have. the lines just seem like it's on the coating of the screen.
i think i will take it over to the store and see what they say. i'm not going to get a refund because, i love this macbook, even if it does have flaws, though i wouldnt mind a free replacement :-D thanks.
Message was edited by: rpeters83

Dead pixel on MacBook Pro?

I'm getting really upset about this. I bought a 13" MacBook Pro w/ Retina about three or four months ago. Now I have dead pixels. The guiness at the Apple Store informed me that one or two dead pixels was within the quality control standards. He then proceeded to let me know that he could replace my screen, but there may or may not be more dead pixels on that screen and eventually they would cut me off because it meets Apple's "standards."
So I guess I actually have a few questions:
Is this a problem with all Mac displays? Or is this specific to the Retina display?
Should I get it fixed now, or wait for more and more pixels to die?
Are there any "at home" remedies? (Other than massaging the screen, because I already tried that)
I know Apple will replace products, but would they let me exchange it for a Pro without Retina if this is a retina specific problem?
This may all sound petty, but this computer was extremely expensive and I'm really not happy about this issue.

1) All displays. Retina display is no different in terms of composition, it simply has a higher pixel density. It is still an LCD display. Perhaps the fact that more pixels are being crammed into the same surface area would raise the probability of a pixel failure. But, it would be safe to say, no.
2) Now. This is an anomoly, not a major issue. There would be no advantage in my opinion to wait. See below for Apple's 'standards' regarding dead pixels.
3) Not applicable / No. Apple's warranty only covers your model. There is no exchange program. They will service your display free of charge within the one year warranty period. During this period, you can opt at any time for an extended warranty (Applecare), which would extend hardware coverage for two subsequent years.
4) Not petty, extremely legitimate. Expensive machine that should work as intended. This is why Apple's warranty coverage is more extensive than any other major CPU manufacturor. You are paying for a top of the line product, and the servicing needs to be commensurate with the price.
<Edited By Host>

I have an iPad 3rd gen it was bought in the US but I am in india and I have come to notice a dead pixel on the screen . Does my warranty cover that ? Can I claim it in india ?

It was bought in may of 2012 can I claim my warranty ?

The iPad (3rd generation) have 3.1 million pixels.
You want to claim warranty because of 1 dead pixel; doubt Apple will entertain your request.

Two million pixels

Similar Messages

Maybe you are looking for