做拍照取圖功能時遇到一個怪現象:上傳後的圖片會自動轉 90 度。測試後發現規律——只要原圖大於 2M,系統就會翻轉照片。
相機拍完直接取出的 UIImage(用 UIImagePickerControllerOriginalImage 取得),其 imageOrientation 為 3,也就是 UIImageOrientationRight。直接使用這張圖不會有問題,但一旦對它進行裁切、縮放等處理,這個屬性會變成 0,此時圖片放到別的地方顯示就會轉向。
麻煩的是 imageOrientation 是唯讀屬性,無法直接改寫,只能繞路處理。
把相機的 allowsEditing 設為 YES,拍照後畫面上會出現一個裁切框。在代理方法中取圖時,不要用 UIImagePickerControllerOriginalImage,改用 UIImagePickerControllerEditedImage。這樣取出來的圖片 imageOrientation 是 0,後續任何裁切縮放都不會造成旋轉。
問題是實務上幾乎一定會做裁切與壓縮,而強制讓使用者裁一刀往往不是產品想要的行為,所以這個方案通常不敷使用。
與其依賴系統屬性,不如自己把像素「正」回來。下面這段ategory 是處理這個問題的經典做法:
+ (UIImage *)fixOrientation:(UIImage *)aImage {
// No-op if the orientation is already correct
if (aImage.imageOrientation == UIImageOrientationUp)
return aImage;
// We need to calculate the proper transformation to make the image upright.
// We do it in 2 steps: Rotate if Left/Right/Down, and then flip if Mirrored.
CGAffineTransform transform = CGAffineTransformIdentity;
switch (aImage.imageOrientation) {
case UIImageOrientationDown:
case UIImageOrientationDownMirrored:
transform = CGAffineTransformTranslate(transform, aImage.size.width, aImage.size.height);
transform = CGAffineTransformRotate(transform, M_PI);
break;
case UIImageOrientationLeft:
case UIImageOrientationLeftMirrored:
transform = CGAffineTransformTranslate(transform, aImage.size.width, 0);
transform = CGAffineTransformRotate(transform, M_PI_2);
break;
case UIImageOrientationRight:
case UIImageOrientationRightMirrored:
transform = CGAffineTransformTranslate(transform, 0, aImage.size.height);
transform = CGAffineTransformRotate(transform, -M_PI_2);
break;
default:
break;
}
switch (aImage.imageOrientation) {
case UIImageOrientationUpMirrored:
case UIImageOrientationDownMirrored:
transform = CGAffineTransformTranslate(transform, aImage.size.width, 0);
transform = CGAffineTransformScale(transform, -1, 1);
break;
case UIImageOrientationLeftMirrored:
case UIImageOrientationRightMirrored:
transform = CGAffineTransformTranslate(transform, aImage.size.height, 0);
transform = CGAffineTransformScale(transform, -1, 1);
break;
default:
break;
}
// Now we draw the underlying CGImage into a new context, applying the transform
// calculated above.
CGContextRef ctx = CGBitmapContextCreate(NULL, aImage.size.width, aImage.size.height,
CGImageGetBitsPerComponent(aImage.CGImage),
0,
CGImageGetColorSpace(aImage.CGImage),
CGImageGetBitmapInfo(aImage.CGImage));
CGContextConcatCTM(ctx, transform);
switch (aImage.imageOrientation) {
case UIImageOrientationLeft:
case UIImageOrientationLeftMirrored:
case UIImageOrientationRight:
case UIImageOrientationRightMirrored:
// Grr...
CGContextDrawImage(ctx, CGRectMake(0,0,aImage.size.height,aImage.size.width), aImage.CGImage);
break;
default:
CGContextDrawImage(ctx, CGRectMake(0,0,aImage.size.width,aImage.size.height), aImage.CGImage);
break;
}
// And now we just create a new UIImage from the drawing context
CGImageRef cgimg = CGBitmapContextCreateImage(ctx);
UIImage *img = [UIImage imageWithCGImage:cgimg];
CGContextRelease(ctx);
CGImageRelease(cgimg);
return img;
}
思路是兩段式:先依方向屬性算出對應的 CGAffineTransform(平移加旋轉),再處理鏡像情況的縮放,最後把底層 CGImage 畫進新的位圖上下文。這樣得到的新 UIImage,其 imageOrientation 自然是 Up,之後無論怎麼裁切縮放都不會再跑偏。
實務建議:拍照回來的第一時間就呼叫 fixOrientation:,後續所有處理都建立在這張「擺正」的圖上,能省掉大量難以追蹤的方向 bug。此外,由於大圖會消耗不少記憶體,最好在修正方向後立即做降尺寸處理。