User talk:Slick
|
[edit] Convert all interlaced JPGs
Hello, can you by any chance give a look at this bot work request? Thanks, Nemo 10:39, 26 November 2012 (UTC)
[edit] utf-8 fix?
Hey, kannst du bitte schauen ob es mit meinem Vorschlag läuft? (siehe Commons:Bots/Work_requests#Convert_all_interlaced_JPGs) --McZusatz (talk) 22:07, 18 January 2013 (UTC)
[edit] File:USMC-11396.jpg
Your bot's photo, File:USMC-11396.jpg, was uploaded without any information about the subjects (also, the source link is dead). It would be difficult to use this image without knowing who the civilian is who is posing with GWB. Thanks. --rogerd (talk) 19:52, 8 January 2013 (UTC)
[edit] Picture of the Year voting round 1 open
Dear Wikimedians,
Wikimedia Commons is happy to announce that the 2012 Picture of the Year competition is now open. We're interested in your opinion as to which images qualify to be the Picture of the Year for 2012. Voting is open to established Wikimedia users who meet the following criteria:
-
- Users must have an account, at any Wikimedia project, which was registered before Tue, 01 Jan 2013 00:00:00 +0000 [UTC].
- This user account must have more than 75 edits on any single Wikimedia project before Tue, 01 Jan 2013 00:00:00 +0000 [UTC]. Please check your account eligibility at the POTY 2012 Contest Eligibility tool.
- Users must vote with an account meeting the above requirements either on Commons or another SUL-related Wikimedia project (for other Wikimedia projects, the account must be attached to the user's Commons account through SUL).
Hundreds of images that have been rated Featured Pictures by the international Wikimedia Commons community in the past year are all entered in this competition. From professional animal and plant shots to breathtaking panoramas and skylines, restorations of historically relevant images, images portraying the world's best architecture, maps, emblems, diagrams created with the most modern technology, and impressive human portraits, Commons features pictures of all flavors.
For your convenience, we have sorted the images into topic categories. Two rounds of voting will be held: In the first round, you can vote for as many images as you like. The first round category winners and the top ten overall will then make it to the final. In the final round, when a limited number of images are left, you must decide on the one image that you want to become the Picture of the Year.
To see the candidate images just go to the POTY 2012 page on Wikimedia Commons
Wikimedia Commons celebrates our featured images of 2012 with this contest. Your votes decide the Picture of the Year, so remember to vote in the first round by January 30, 2013.
Thanks,
the Wikimedia Commons Picture of the Year committee
Delivered by Orbot1 (talk) at 10:20, 19 January 2013 (UTC) - you are receiving this message because you voted last year
[edit] Non-interlaced something or other
Hello, an image I uploaded was altered because of bug #17645, something about being a non-interlaced image. Is there something I ought to do while creating files to ensure that I don't create extra work for anyone? Thanks, mr.choppers (talk)-en- 06:49, 20 January 2013 (UTC)
- This depends on you image processing program. Make sure to disable "interlaced"/"Progressive" or to enable "Baseline" in the settings. --McZusatz (talk) 10:26, 20 January 2013 (UTC)
- Small request: link the bug with the interwiki bugzilla:17645 when you have a chance to, please. Thanks, Nemo 10:44, 20 January 2013 (UTC)
- Another request:(If possible) Link to any page which makes clear how to save jpeg correctly. There are multiple request (1, 2) --McZusatz (talk) 15:23, 20 January 2013 (UTC)
- I've created one at Help:JPEG#Progressive JPEGs, thanks for the screenshot. --Nemo 16:38, 20 January 2013 (UTC)
- A link to a seperate (explaining) page is possible, but this should be a "static link", not pointing to a user discuss page. If there is a static link/page, please post here and I will add (in future files). --Slick (talk) 16:45, 20 January 2013 (UTC)
-
- Der Help:JPEG link ist doch statisch. --McZusatz (talk) 14:48, 21 January 2013 (UTC)
- Sorry, überlesen. I add the link to summary on converted images. --Slick (talk) 15:58, 21 January 2013 (UTC)
- Thanks for the help - however, I have hitherto only ever used the "Baseline (standard)" settings when saving. There is also a "Baseline optimized" and a "progressive" setting. I use Photoshop CS5. I just uploaded this image using the "Baseline optimized" setting, any difference? Also, there is a slider that allows one to choose which quality to use. I have always moved it to 12 (maximum), figuring that only the best is good enough for Wikipedia - is this where the problem lies? Cheers, mr.choppers (talk)-en- 01:19, 21 January 2013 (UTC)
- This last image is ok, imagemagick reports no interlacing and exiftool agrees: "Encoding Process : Baseline DCT, Huffman coding"; there's also "Photoshop Quality : 12 / Photoshop Format : Optimised / Progressive Scans : 3 Scans" as you say but none of this is a problem, there's no reason to degrade images with excessive compression (I don't know if that's too much). --Nemo 07:13, 21 January 2013 (UTC)
- Therefore the "Baseline (standard)" seems not to be baseline. Unfortunately I can't test this because I have no access to Photoshop right now, but this should be mentioned on Help:JPEG#Progressive JPEGs. (screenshot appreciated). --McZusatz (talk) 14:59, 21 January 2013 (UTC)
- I took a screenshot of the save box, with the settings I have used for all of the photos I have ever uploaded here, most of which seem to fall afoul of this bug. Cheers, mr.choppers (talk)-en- 16:24, 21 January 2013 (UTC)
- I test with a old Photoshop 7.0. The window looks like the same, and the first two format options create a 'Baseline DCT, Huffman coding' and the third create a 'Progressive DCT, Huffman coding'. --Slick (talk) 17:11, 21 January 2013 (UTC)
- So where is the bug? Mr.choppers says he always used the first button (which should produce baseline). But taking a look at some of his old upload reveals that they are
Progressive DCT, Huffman coding
. Photoshop is buggy? --McZusatz (talk) 17:20, 21 January 2013 (UTC)- @ Mr.choppers, please link some samples images (that was converted?) so I can check again. All other converted images can watch @ Special:ListFiles/Slick-o-bot, so feel free to compare the before and after. (but maybe beware of your browsers cache) --Slick (talk) 17:37, 21 January 2013 (UTC)
- This one for instance. I got CS5 on April 27, 2012, so any images of mine which were converted after that date are a mystery. Photoshop defaults to "Baseline (standard)" and I had never been aware that there were options until now, most certainly never changed that setting. Here are a few more:
- @ Mr.choppers, please link some samples images (that was converted?) so I can check again. All other converted images can watch @ Special:ListFiles/Slick-o-bot, so feel free to compare the before and after. (but maybe beware of your browsers cache) --Slick (talk) 17:37, 21 January 2013 (UTC)
- So where is the bug? Mr.choppers says he always used the first button (which should produce baseline). But taking a look at some of his old upload reveals that they are
- I test with a old Photoshop 7.0. The window looks like the same, and the first two format options create a 'Baseline DCT, Huffman coding' and the third create a 'Progressive DCT, Huffman coding'. --Slick (talk) 17:11, 21 January 2013 (UTC)
- I took a screenshot of the save box, with the settings I have used for all of the photos I have ever uploaded here, most of which seem to fall afoul of this bug. Cheers, mr.choppers (talk)-en- 16:24, 21 January 2013 (UTC)
- Therefore the "Baseline (standard)" seems not to be baseline. Unfortunately I can't test this because I have no access to Photoshop right now, but this should be mentioned on Help:JPEG#Progressive JPEGs. (screenshot appreciated). --McZusatz (talk) 14:59, 21 January 2013 (UTC)
- This last image is ok, imagemagick reports no interlacing and exiftool agrees: "Encoding Process : Baseline DCT, Huffman coding"; there's also "Photoshop Quality : 12 / Photoshop Format : Optimised / Progressive Scans : 3 Scans" as you say but none of this is a problem, there's no reason to degrade images with excessive compression (I don't know if that's too much). --Nemo 07:13, 21 January 2013 (UTC)
- Der Help:JPEG link ist doch statisch. --McZusatz (talk) 14:48, 21 January 2013 (UTC)
┌─────────────────────────────────┘
Could you please save one JPG for each option (three in total) and upload them? (content does not matter) --McZusatz (talk) 18:11, 21 January 2013 (UTC)
- All five images above were in 'Progressive DCT, Huffman coding' before converting. So I guess there is a bug in PS. And yes, please add sample images as requestet by McZusatz --Slick (talk) 18:24, 21 January 2013 (UTC)
- Here you go, a is Baseline (standard), b is Baseline progressive, and c is Progressive.
- Congee 1a.jpg
- Congee 1b.jpg
- Congee 1c.jpg
mr.choppers (talk)-en- 19:03, 21 January 2013 (UTC)
- Simply the first and the last are the same and are progressive. So PS has a bug and this is important to know. This may explain a lot of progressive images here. I suggest you contact the support of Adobe if possible. I will post it on the Commons:Village_pump, to confirm our tests by others. --Slick (talk) 20:01, 21 January 2013 (UTC)
- Hm - and also, some sort of bot recognized that 1a and 1c were the exact same file (hash values?). Interesting. I will use option b from now on. I would contact Adobe as well but since I honestly don't know what I am talking about I would prefer if one of you kids did it. Thanks, mr.choppers (talk)-en- 06:28, 22 January 2013 (UTC)
- Here you go, a is Baseline (standard), b is Baseline progressive, and c is Progressive.
- In case you don't know: the bot stopped about 6 hours ago. Also, would getting a Toolserver or labsconsole: account help making it faster? :) --Nemo 11:37, 22 January 2013 (UTC)
- The bot is sleeping because of this. I am not sure it can make trouble when keep it running. I think there is no need to do it faster, is there? But I think about to rent a rootserver to save my bandwidth at home for this large project. (And I dislike to depend on others, i.E. Toolserver) --Slick (talk) 16:20, 22 January 2013 (UTC)
- Ah, ok. I guess you can wait for a day. I don't know at what extent you dislike depending on others, but for instance Wikimedia Labs don't even require approval and the addition to the bot instance would be almost automatical. They currently don't lack CPU or memory and of course bandwidth is not a problem because you'd be inside the cluster (probably connection pmtpa<->eqiad costs the WMF less than bandwidth to wherever your server would be). --Nemo 17:08, 22 January 2013 (UTC)
- Ok, I red about the Labs, but I am to lazy to learn more about. The bot is working fine and there is no need for more speed or RAM ... IMHO. So, thank you, but I am not interested at the moment. Maybe later. More important is to find a solution for uploadet progressive files in future. --Slick (talk) 19:40, 22 January 2013 (UTC)
- Ah, ok. I guess you can wait for a day. I don't know at what extent you dislike depending on others, but for instance Wikimedia Labs don't even require approval and the addition to the bot instance would be almost automatical. They currently don't lack CPU or memory and of course bandwidth is not a problem because you'd be inside the cluster (probably connection pmtpa<->eqiad costs the WMF less than bandwidth to wherever your server would be). --Nemo 17:08, 22 January 2013 (UTC)
- The bot is sleeping because of this. I am not sure it can make trouble when keep it running. I think there is no need to do it faster, is there? But I think about to rent a rootserver to save my bandwidth at home for this large project. (And I dislike to depend on others, i.E. Toolserver) --Slick (talk) 16:20, 22 January 2013 (UTC)
[edit] Photoshop CS5?
Hi, so I just came across Help:JPG and read that Photoshop is buggy. I wasn't sure what version of Photoshop, but you linked to this discussion in your edit summary (much appreciated). Seems like it's CS5 that's buggy? I save all my work Baseline "Standard". I'm not sure how to go about using the magick tool to test a JPG I've uploaded, but I'll give it a whirl. Is this bug for certain though? Slick-o-bot hasn't been up and running since February, and it's never touched any of my previous-to-sleeping uploads. – Kerαunoςcopia◁galaxies 07:14, 11 March 2013 (UTC)
- I am sure CS5 has the Bug too (see above the "Congee*.jpg" Test, this images was saved by CS5.1 on Mac). If you save with the first option ("Baseline Standard") it is the same as option #3 ("Progressive"). You can tell me some images I can test for you. I am sure PS 7.0 do not have this bug. I am unsure with all versions greater than PS 7.0, less than CS5. Slick-o-bot converted progressive JPGS (>5 MB, some less than 5 MB) as requested. But the newer consents is only to convert images with broken thumbnails (large progressive JPGs, ~ >25 MB), this will be done by a new Bot User:Thumbnails Check Bot (currently in development). --Slick (talk) 07:34, 11 March 2013 (UTC)
- You wouldn't mind checking two images for me? That'd be great. I looked into imagemagick and it's not available for my OS (10.5), or if an older version exists, I couldn't easily find it. Here's a larger image and a smaller image. Both were saved at level 12, Baseline "Standard" JPG. – Kerαunoςcopia◁galaxies 07:58, 11 March 2013 (UTC)
- I just add a hint on Help:JPEG#Progressive_JPEGs how to test for progressive JPGs with a online tool, so you can simple test by yourself. Ok? --Slick (talk) 08:00, 11 March 2013 (UTC)
[edit] File:Haus Automatik ISO 1600 01-LF.JPG
Diese Bearbeitung war nicht verlustfrei. Nur so als Hinweis. --McZusatz (talk) 14:47, 21 January 2013 (UTC)
- Ok, aber ich habe auch keine bessere Idee als bereits diskutiert. Verbesserungsvorschläge welcome. --Slick (talk) 15:42, 21 January 2013 (UTC)
[edit] your bot
hello :) can you say me what your bot have make on this file? [1]? thank you --Pava (talk) 11:40, 22 January 2013 (UTC)
- Convert the image because it is affected by bugzilla:17645. There is more information or see above ↑. --Slick (talk) 16:27, 22 January 2013 (UTC)
[edit] Converting File:Torshammare i silver fr Sandby kyrkogård, Torna hd, Skåne (Antiqvitets Akademiens Månadsblad 1882 s103).jpg
As the original uploader of the file I wonder why Slick-o-bot converted File:Torshammare i silver fr Sandby kyrkogård, Torna hd, Skåne (Antiqvitets Akademiens Månadsblad 1882 s103).jpg to a non-interlaced jpeg, since both my scanner and my Photshop-program should always be set to save JPEGs in baseline mode. Was my file really saved with interlaced/progressive compression? If Slick-o-bot converted a file that didn't need conversion there is no harm done. I am asking just to learn to avoid future mistakes from my side. / Achird (talk) 09:43, 30 January 2013 (UTC)
- Replied on his talk. --Nemo 11:08, 30 January 2013 (UTC)
[edit] Bot request
Hättest du Zeit und Lust einen Bot laufen zu lassen, der bestimmte GIF/JPEG Dateien in PNG umwandelt? Betroffende Dateien wären dann in einer Kategorie oder ähnlich markiert. Der Bot müsste dann:
- Eine neue PNG Datei hochladen und den Beschreibungstext der alten Datei größtenteils kopieren
- Ursprüngliche Markierung bei der JPEG Datei entfernen und neue Markierung (speedy?, superseded?, duplicate? [noch unklar]) hinzufügen
- Nutzung ersetzten (selber oder über CommonsDelinker anweisen die Dateien zu ersetzen oder ...?)
- Manuell (für admins): Ursprüngliche Datei löschen, weiterleiten oder mit superseded belassen. (Abhängig vom zweiten Schritt)
--McZusatz (talk) 16:29, 2 February 2013 (UTC)
Prinzipiell hätte ich da durchaus Lust dabei zu unterstützen, allerdings klingt das erstmal nach einem recht komplexem Programmablauf und ehrlich gesagt verstehe ich ab Mitte Punkt zwei fast nurnoch Bahnhof. Ich tue mich etwas schwerr da aktuell zuzusagen, da ich aktuell nicht beurteilen kann wie komplex das werden würde. Du kannst das ja gern mal irgendwo konkreter ausformulieren und wenn ich abzeichnet ich könnte das hinbekommen, schau ich mir das mal unverbindlich an. Also meine Antwort zusammengefaßt: Erstmal Nein, u.U. Ja. Aber ich will da nix versprechen. --Slick (talk) 18:24, 2 February 2013 (UTC)
- So eventuell:
for all files in Category:PNGbyBotblabla{ download file convert file.ext file.png get raw_text of file add "category:files processed by bot" to raw_text upload file.png with raw_text get raw_text of file add "category:files converted by bot" to raw_text update raw_text of file }
- Die Fragen haben sich inzwischen geklärt. Sagt mir Bescheid wenns los geht ... --Slick (talk) 11:02, 10 February 2013 (UTC)
[edit] PC
Ah, I hadn't noticed the machine you run the bot on, it's wonderful. :) I run my bots on my daily-work desktop, but it's an AMD E350 so it doesn't consume more than 30–38 W. --Nemo 18:13, 2 February 2013 (UTC)
Currently I rent a rootserver to run the bot(s). The thinclient is just for testing and play around now. These thinclients are very cheap here (in germany) and you can get by ebay for less than 20,-€ incl. shipping. --Slick (talk) 18:30, 2 February 2013 (UTC)
[edit] File:1706 Frankfurt (Oder).jpg
This edit is lets say interesting. The box your bot is adding says "Large JPEGs are problematic ...." - a file of 550 × 347 (55 KB) ...Sicherlich talk 08:52, 3 February 2013 (UTC)
- Sure. It doesn't say that it's a large JPEG: ;-) --Nemo 11:47, 3 February 2013 (UTC)
[edit] Notification about possible deletion
Page deletion warning | Some contents have been listed at Commons:Deletion requests so that the community can discuss whether they should be kept or not. We would appreciate it if you could go to voice your opinion about this at their entry. If you created these pages, please note that the fact that they have been proposed for deletion does not necessarily mean that we do not value your kind contribution. It simply means that one person believes that there is some specific problem with them, such as a copyright issue. |
Affected:
Eleassar (t/p) 08:31, 6 February 2013 (UTC)
[edit] Featured Picture Nomination
The image File:Defense.gov News Photo 110609-N-XD935-137 - U.S. Navy Petty Officer 3rd Class Bryan Myers maneuvers around a ship s propeller looking for an inert training explosive under a Barbadian coast.jpg, which was produced or uploaded by you, has been nominated for featured picture status at Commons:Featured picture candidates/File:Defense.gov News Photo 110609-N-XD935-137 - U.S. Navy Petty Officer 3rd Class Bryan Myers maneuvers around a ship s propeller looking for an inert training explosive under a Barbadian coast.jpg. Good luck!
[edit] File rename
Hi. You just renamed "File:Flag of Serbia (1941-1944).svg" to "File:Flag of the Government of National Salvation.svg": http://commons.wikimedia.org/wiki/File:Flag_of_Serbia_(1941-1944).svg As file uploader, I do not agree with this move because there is no source which says that this was "Flag of the Government of National Salvation". Source from which I took this flag says that it was flag of Serbia. Can you please rename file back to original title? PANONIAN (talk) 08:29, 17 February 2013 (UTC)
- I just rename this as requested by user DIREKTOR that looks ok for me (but I am not a expert in Serbia history), see [2]. I suggest, please talk to this user and if there is a consent, please fill in a new rename request, maybe with a link to the discussion. --Slick (talk) 10:11, 17 February 2013 (UTC)
[edit] FBI pics
Hi Slick wärst du evtl dabei wenn ich beim FBI mal eine Anfrage mache ob die uns Files zur Verfügung stellen? Denn so viel haben wir ja von denen nicht.--Sanandros (talk) 20:14, 23 February 2013 (UTC)
- Was verstehst du unter dabei sein? Wenn damit gemeint ist beim herunter- und hochladen von den Pics zu unterstützen -> ja. Wenn es darum geht mit die Anfrage zu stellen bzw. hierzu irgendwie organisatorisch tätig zu werden -> nein. --Slick (talk) 07:45, 28 February 2013 (UTC)
- Nein es geht in erster Linie nur um darum die files zu laden. Entweder werde ich dort ein mal anrufen oder eine E-Mail schreiben. Vlt werden die uns auch files über Mail schicken und ich würde dir dann die Materialien weiter schicken. Denn bei ihren files sehe ich leider nicht wer sie erstellt haben bzw in wessen Auftrag sie erstellt wurden und daher wollte ich die Urheberrechtlichen Details klären. Aber schon jetzt vielen Dank für dein Angebot der Hilfe.--Sanandros (talk) 17:45, 28 February 2013 (UTC)
[edit] Renaming files to English
Hello! Here you enabled a file renaming under the requester’s pretense that the original filename was «meaningless». However, this was simply a case of translating a filename from whatever language into English — something the requester did in the past several times, and now just one time too many. I could agree that abbreviated filenames should be avoided, and I could accept the argument (although never agree with such silliness) that filenames must be verbosely descriptive and includes spaces — but this is just an excuse for blatant anglification of Commons, indeed against Commons accepted policy. Therefore I ask you to reconsider this renaming under #2 of Commons:File renaming#Which files should not be renamed?, and ask the renaming requester for a new filename which may fix any percieved meaninglessness but not change the original uploader’s language choice. -- Tuválkin ✉ 13:29, 26 February 2013 (UTC)