User talk:Bmbdelhi

From Wikimedia Commons, the free media repository
Jump to navigation Jump to search
Welcome to Wikimedia Commons, Bmbdelhi!

-- Wikimedia Commons Welcome (talk) 11:21, 3 June 2017 (UTC)[reply]

Has been deleted, and you were blocked for a short time. The file uploaded was 34,047,685 bytes in size and our automated systems found that the file ended at 6,803,353 bytes - and then declared the remaining 28MB as embedded data in the file. After discussion we think that there is a possibility that you unwittingly uploaded a corrupted picture. You can upload the image again if you have a good version - please check the image first. Ronhjones  (Talk) 14:38, 3 June 2017 (UTC)[reply]

@Ronhjones: I restored the file because it doesn't contain embedded pirated software. However it is corrupted due to a bug in Samsung's software – some programs can read it (e.g. IrfanView) and some can't (e.g. GIMP, Firefox, jpegtran, probably all based on libjpeg). You may find more information here and especially here (see bcyrill's post). Pinging @Zhuyifei1999 who also might want to see these pages. --jdx Re: 21:12, 3 June 2017 (UTC)[reply]
@Jdx: Well there's a turn up for the book. I have python installed, so I tried the program on https://gist.github.com/bcyrill/e59fda6c7ffe23c7c4b08a990804b269#file-fix_eoi-py-L1, sadly it just spat out "Unknown Samsung trailer version". PhotoShop CS6 is happy to read the file and when saved at max quality is only 9MB is size - should I replace the image with the cleaned version? Ronhjones  (Talk) 22:02, 3 June 2017 (UTC)[reply]
@Ronhjones: Not yet – I have posted a request on the script's page. Let's wait a while. BTW. When saved from IrfanView with option "try to save with original JPEG quality" (which is 96%) the output file has size smaller than 6.5 MiB. --jdx Re: 23:57, 3 June 2017 (UTC)[reply]
That seems to be two issues: the samsung & adobe threads point to an issue in which the non-marker '\xff' are not escaped as '\xff\x00'; the gist points to some sort of "samsung trailer", and missing EOI markers (which should be optional anyways). --Zhuyifei1999 (talk) 06:52, 4 June 2017 (UTC)[reply]
Force ignoring (comment out line 55) that version mismatch (the jpeg has a version of 103, and the script expect 101), and then dumping the data, shows these files:
$ file Nako_view_point*
Nako_view_point_Image_UTC_Data:          ASCII text, with no line terminators
Nako_view_point.jpg:                     JPEG image data, Exif standard: [TIFF image data, little-endian, direntries=12, height=2176, manufacturer=samsung, model=SM-G935F, orientation=upper-left, xresolution=210, yresolution=218, resolutionunit=2, software=G935FXXU1DQBO, datetime=2017:03:24 18:35:59, width=11872], baseline, precision 8, 11872x2160, frames 3
Nako_view_point_Motion_Panorama_Info:    8086 relocatable (Microsoft)
Nako_view_point_Motion_Panorama_MP4_000: ISO Media, MPEG v4 system, 3GPP
Nako_view_point_pano.jpg:                JPEG image data, Exif standard: [TIFF image data, little-endian, direntries=12, height=2176, manufacturer=samsung, model=SM-G935F, orientation=upper-left, xresolution=210, yresolution=218, resolutionunit=2, software=G935FXXU1DQBO, datetime=2017:03:24 18:35:59, width=11872], baseline, precision 8, 11872x2160, frames 3
Nako_view_point_Panorama_Shot_Info:      ASCII text, with no line terminators
Nako_view_point_Motion_Panorama_MP4_000 is an actual MP4 file displaying the video of the panorama before it is rendered into a single image, and task up the majority of the rest of data.
$ du -h Nako_view_point_Motion_Panorama_MP4_000
26M	Nako_view_point_Motion_Panorama_MP4_000
$ ffprobe Nako_view_point_Motion_Panorama_MP4_000
ffprobe version 2.8.11-0ubuntu0.16.04.1 Copyright (c) 2007-2017 the FFmpeg developers
  built with gcc 5.4.0 (Ubuntu 5.4.0-6ubuntu1~16.04.4) 20160609
  configuration: --prefix=/usr --extra-version=0ubuntu0.16.04.1 --build-suffix=-ffmpeg --toolchain=hardened --libdir=/usr/lib/x86_64-linux-gnu --incdir=/usr/include/x86_64-linux-gnu --cc=cc --cxx=g++ --enable-gpl --enable-shared --disable-stripping --disable-decoder=libopenjpeg --disable-decoder=libschroedinger --enable-avresample --enable-avisynth --enable-gnutls --enable-ladspa --enable-libass --enable-libbluray --enable-libbs2b --enable-libcaca --enable-libcdio --enable-libflite --enable-libfontconfig --enable-libfreetype --enable-libfribidi --enable-libgme --enable-libgsm --enable-libmodplug --enable-libmp3lame --enable-libopenjpeg --enable-libopus --enable-libpulse --enable-librtmp --enable-libschroedinger --enable-libshine --enable-libsnappy --enable-libsoxr --enable-libspeex --enable-libssh --enable-libtheora --enable-libtwolame --enable-libvorbis --enable-libvpx --enable-libwavpack --enable-libwebp --enable-libx265 --enable-libxvid --enable-libzvbi --enable-openal --enable-opengl --enable-x11grab --enable-libdc1394 --enable-libiec61883 --enable-libzmq --enable-frei0r --enable-libx264 --enable-libopencv
  libavutil      54. 31.100 / 54. 31.100
  libavcodec     56. 60.100 / 56. 60.100
  libavformat    56. 40.101 / 56. 40.101
  libavdevice    56.  4.100 / 56.  4.100
  libavfilter     5. 40.101 /  5. 40.101
  libavresample   2.  1.  0 /  2.  1.  0
  libswscale      3.  1.101 /  3.  1.101
  libswresample   1.  2.101 /  1.  2.101
  libpostproc    53.  3.100 / 53.  3.100
Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'Nako_view_point_Motion_Panorama_MP4_000':
  Metadata:
    major_brand     : 3gp5
    minor_version   : 0
    compatible_brands: 3gp5isom
    creation_time   : 2004-02-09 18:16:14
  Duration: 00:00:12.97, start: 0.000000, bitrate: 16779 kb/s
    Stream #0:0(und): Video: h264 (Baseline) (avc1 / 0x31637661), yuv420p, 1920x1080, 16777 kb/s, 30 fps, 30 tbr, 90k tbn, 180k tbc (default)
    Metadata:
      creation_time   : 2004-02-09 18:16:14
So here's a question: this is not piracy, but MP4 is not an allowed format on Commons. How should such data be treated? --Zhuyifei1999 (talk) 07:09, 4 June 2017 (UTC)[reply]
@Zhuyifei1999 and Ronhjones: An answer has appeared so I have modified the script and it works as expected! I have uploaded a new version of the file – first fixed using the script and then optimized using jpegtran. --jdx Re: 01:38, 30 June 2017 (UTC)[reply]