Sopel - Comments

From my part the priorities look something like this - normal, singular requests are more important because a) most of them are easy and b) you're minimizing the size/rate of another mixpacks. Singular is the moving traffic, packs are the clog that isn't moving anywhere so they can be finished anytime. The only problem with that is how long the packs sit there - if someone would like to cut out a request from 2016 it's most likely already is obsolete.
I'm excited about the redesign I still think that a system in which while uploading a pack you'd have to simply choose ID of the faces inside or even better - link each photo to the ID. Then if someone makes another request with that ID it would be one of these options a) redirect to the already requested pack b) when the individual would be cut a photo from the pack would be automatically removed c) the new upload would be added to the pack as another version for that ID
It would be a self-controlling system, cutting down on the redundant requests. Or (came to me while writing) a system in which you upload a pack and link them to their ID, but every singular photo creates its own request - a pack is - in theory - being completed by various cutters, but is eventually completed and the photos are always up to date. Also, since the requests are tied to the ID a possibility to filter based on nationality/league would be probably useful for cutters who are mostly cutting faces from their own league/country (understandably )

Well, you got me, I misjudged my time again and what's more, I completely forgot about it, I'm going to unassign myself now
Real life is piling up, I've learned my lesson to not go all gung-ho on the requests so now I don't take any and just upload them when I finish them, I hope this is the last time you have to remind me, sorry mons

@maquino I hope this will be good enough

If anything I think this photo is actually older than the current one (I think it's from the days he was playing in Piast Gliwice)
Here's modern photo from Palermo but I can't find a bigger resolutiion.

https://palermocalcioit.cdn-immedia.net/upload/giocatori/files/999,-1,16619/26-o.png

I searched around and yep, you were right - the file that caused my problem was FMInside's Update, in case you'd have someone with a similar problem to mine, thank you for your help!

Hmm, so claassen's then? I don't have any other files that touch upon Dutch or Northern Ireland leagues. And the polish leagues are made by a polish creator so I don't see any reason as for why would he change that.
Well, anyways, maybe there is some pesky file left by some dutch creator, who knows, thanks for the help anyway

Hmm, and what types of files could cause this? Before my current save I had different fix that didn't cause such problems but I carefully removed it and installed yours following every step. Where should I look, in .lnc files?

Hi after starting the game I came across some weird name changes that seem to be... in Dutch? Most notably "Northern Ireland" in my game is "Noord-Ierland". Also, 4th level competitions in Poland are named "III liga Groep #" - 'Groep' instead of 'Grupa".
Is this in any way connected to this file or should I look elsewhere?

@mons Oh wow, this is actually great. Admittedly, it's not better than some fine work of some cutters out here, but it's still remarkable. It struggles a bit with dark hair (except dreadlocks as these are always simple, imo) and of course in dark/grainy pics but for the general use of some one-off, decent quality pics it may be truly a gamechanger - whilst taking literally seconds it keeps the details and notices the single hair strands. Thanks for sharing!

Eh, yeah, that source would be a tiny bit better but I won't cut it. The general lighting on the picture is bad and the cut won't be ideal anyway. I'd let it stay like this for now, maybe in the future there will be a better picture of the player

Is this decent enough?

Hey @mons, could you re-open the request for a quick moment? Since nobody took it I took matters into my hands and cut it, I want to upload it

You should upload it, I don't think credits on such things are important, but also I insist that you should upload it as your version is the definitive one

Request Completed: Pending missing images mixpack 4 [25 requests] - Download

@mons @krissmed

Why was it set again to "waiting", what was wrong with my cut?

But does that mean it should get a pass though? If there is no good pic then it should not be included - the guy is literally a kid on this pic, not even 16, probably not even 12.
I don't know about you, but for me, it would a bit odd/creepy/inappropriate? to include a cut-out like this in the pack, it's not like it's urgent to create a cut at all costs from whatever source that fits the resolution.

@mons I think this picture is way too old to be representative in any way...

When I was creating this the photo you posted was different, I went with the originally requested one because it had better lighting and was easier for me to cut
As for me, I think the cut turned out quite alright, up to you guys if you want to rework it.

Maybe since my post has been singled out I'll post my idea for the solution - the "no packs" way.

In the current system the request the process goes like this:
Someone makes a request, the request goes uncut, @mons moderates the request after ~a month, does a round-up and creates a mixpack, requester can post another request

What I've been proposing:
Someone makes a request, the "timer" for the request starts, the request goes uncut, ~a month passes, "timer" stops, the request stays on the list, requester can post another request

What it accomplishes is a situation in which the mixpack section is for the teampacks, etc, not a burial ground for many.
The request list gets longer, but is more accessible and it becomes easier to asses what's in there (due to the preview option).
That way cutters can choose what they want to cut, when they want to cut, they decide the quantity of the cuts, the whole process becomes less of a chore.
Think of it this way - someone who wants to do a missing/improvement mixpack wants to take on a pack 20 pictures - various variety, quality, size, etc. That may be off-putting, that may be discouraging.
In this solution, someone who wants to make 20 cut-outs can filter the list, find images that suit them and create the ones that will be the easiest for them and possibly providing the best quality that they can give.
It's basically a choice between working with what you get vs cherry picking what do you want to work with.
Because - from my experience - some very easy cuts just escape me, I wasn't around when they were posted and could easily get them done. But they have been already moderated and I won't take on the whole pack and get them done. Sure, I could just take one picture and when I'm done just leave the comment on the mixpack "X has been cut", that's an option. But that just shows that the nature of mixpacks is flawed - some cuts have been already requested again an cut, the numbers of files are misleading, there may have been better sources since when the pack was uploaded etc.

My solution came with other ideas that would improve the whole request process f.e. a new, duplicate request instead of creating another page could just add the new photo to the original request; duplicate requests from unique requesters would give the request a "bump" or a "like" as a sign of popular demand; a mandatory need for every photo in the teampack to be assigned to a ID from the database, which would allow a control on the contents of the teampack and singular requests.

More can be read in the original discussion, I just wanted to showcase my idea for this in a less rambling manner

I forgot to add to the previous message - expect those two packs to be done in July when I'll be able to allocate some time into them

As for our discussion:
The round-up mixpack solution isn't that close to what I'm suggesting - I mean, it works on similar rules but the execution is different. /
What we have now: someone makes a request, the request goes uncut, you moderate the request after ~a month, do a round-up and create a mixpack, requester can post another request
What I've been thinking: someone makes a request, the "timer" for the request starts, the request goes uncut, ~a month passes, "timer" stops, the request stays on the list, requester can post another request

What it accomplishes is a situation in which the mixpack section is for the teampacks, etc, not a burial ground for many
The request list gets longer, but is more accessible and it becomes easier to asses what's in there (due to the preview option)
That way cutters can choose what they want to cut, when they want to cut, they decide the quantity of the cuts, the whole process becomes less of a chore. Think of it this way - someone who wants to do a missing/improvement mixpack wants to take on a pack 20 pictures - various variety, quality, size, etc. That may be off-putting, that may be discouraging. In this solution, someone who wants to make 20 cut-outs can filter the list, find images that suit them and create the ones that will be the easiest for them and possibly providing the best quality that they can give. It's basically a choice between working with what you get vs cherry picking what do you want to work with.
Because - from my experience - some very easy cuts just escape me, I wasn't around when they were posted and could easily get them done. But they have been already moderated and I won't take on the whole pack and get them done. Sure, I could just take one picture and when I'm done just leave the comment on the mixpack "X has been cut", that's an option. But that just shows that the nature of mixpacks is flawed - even on this very mixpack! Some are cut, the numbers of files are misleading, etc.

Also, one thing I forgot to mention - although it would be a bigger chore put on the requesters, but if every mixpack could at least contain the info of the IDs of the players.
It would come hand-in-hand with my previous suggestion - someone uploads a teampack, is asked to assign an ID/Surname to the img file (just like in the request form) when all is set and done they can upload the teampack. Later someone else wants to make a request for a player that is in the said teampack - the request isn't made, the person is directed to the teampack where they can "bump" the request or write a comment. This would also help in catching the unnecessary duplicates but I know that it would put a bit more emphasis on the requesters (which can be dealt with, many of those packs are already named as the game ID's, a simple "Filename is ID" option would solve many problems"

As for the cutters - you misunderstood me, I love the fact that people like marrtac or maxtod77 or others are doing - they ware working - I'd call that - in a preventive manner, they create cuts before anyone considers requesting them I also have no hard feelings towards people who work only on the major teams - most people will probably only ever see those cuts, so they obviously need to be of the best quality and updated annually or even more often, I get that. And I'm not about forcing anyone to cut anything - this is a hobby, no one is getting paid for this and everyone has their time limits
I'm only saying that the piling mixpacks are discouraging for everyone - from seasoned cutters to those who start. The cuts just come and go, it's kinda sad when you know that the source is good, on solid, light background and it would just take a few minutes for someone with Photoshop to cut it - but it will just pass and wait in the limbo the mixpack category is. If it was available at all times maybe someone with the right skills and a few minutes to kill would simply pick it up and create it, just like that - 1, even tiniest cut a day is better than 20 once a year or so Sorry if I sounded salty in the previous message - my intent was to say that it's a community effort and those work better when everyone can give even the tiniest contribution then when it's all on the shoulders of "those who can cut" who either have to create their works regularly or in heaps.

As for the ID's - I know that they are in the URL but I'm asking if they could be visible on the player infor tab and in the team info tab, for a quick acces to them.
Maybe I'll explain where I come from with this - when I find a player without a cutout (news, game, browsing the database) I ofc put his name into the google search and find a photo. But when I want to save the photo I like to save it with the ID, especially when the name/nickname/surname is common. But in order to get to the ID I need to search for the player in the database, find him, open a new tab with his profile and copy the ID from the URL. Or other - if I'm saving the whole team I have to click on the profile of every single player in order to get their ID from the URL. That all just unnecessary clicks that could be solved just by adding a one new column in the search database or in the team page or in the player's page - ID. That's all - small thing but a very big quality of life change

Well, the system is flawed anyway as those packs clutter the list anyway. - I took those two mixpacks as I knew they are in my skill capability range so it matters to me that it's left untouched and so I can work on it later.
Packs in general are flawed - every cutter has some set of skills and whatnot and every cutter chooses what he can do - some don't want to work around shitty quality and work only with HQ, some specialise in shitty quality as it hides their imperfect skills (hey, that's me), some take only the easy ones and some cut only the bald ones. Someone - if willing - will eventually find something that suits them, but these packs imo besides clearing the log (in a illusive way) only discourage people as if you take the whole pack you have to deal with stuff you're not a fan of. Also, it's just painful to wade through this all - there are many images that I could simply do in less than 5 minutes but I won't take the whole pack for it. My solution would be to stop bundling the pictures and just set a "timer" for requests - someone makes a request, the timer starts, it stays uncut, after the time passes (month or so) the timer stops, the requester has an option to make another request. Yes, it clutters the log, but honestly who really cares, I doubt that anyone besides the cutters shift through them anyway. What it does is freeing the images so they can be cut at any moment, by anyone willing, due to your request system based on the database the duplicate request shouldn't be possible (if possible - a new duplicate request instead of creating a one or giving an error could just add the new photo to the original request; duplicate requests from unique requesters would give the request a "bump" or a "like" and that would be signified so it would be known that more than one person wants it cut) I think that my solution, - while making a bigger mess - opens up the request list and possibly makes the workflow a bit better when anyone can simply pick one photo they can do - one is better than none.
But it all comes to us, the community in the end - I spend a lot of time in the requests section and I see that most of the time people are rather concentrated on their own projects and no one really wants to answer people's requests

Also, if I'm rambling about suggestions - could it be possible to display player/clubs/nations ID in every place possible? (f.e. player's ID's in the club panel, in the player's panel) That would be helpful a few times, especially while working with the database.
Also - could staff and players be merged into one section "People" ?

Ahh, it all came out longer than I thought, sorry for rambling, it just has been on my mind for a long time

Yes, someday it will be done - it's not like people are fighting over this, right?

Yes, someday it will be done - it's not like people are fighting over this, right?

@mons @Baja @klajton The player has signed his contract just yesterday, maybe it's better to simply wait for an official photo that probably will be much better in the pose, quality, and the most recent than any other currently on the internet?

@mons duplicated request, can be closed

https://sortitoutsi.net/graphics/request/26330

These are all fantastic news to me as the method that I use to create cuts hits the quality of the cut really hard when I resize it too much so 250x250 will definitely help me create a better quality cuts, I'm very happy to hear that the site allows this resolution now

@Baja is this one saved in the right resolution?

Oh, sorry, is this a new rule or something?
Must have missed that, I've been away from the site for a while
I hope it's not a problem, I'll remember to do it next time

@mons This one also should be an improvement