It could be that when you inserted the image in the content area the image resized to 600px to fit the TinyMCE Window?
What happens when you insert the image if you enter 642px in the width box? Does it still resize it
Also as a note to stop SS reducing quality in images you can set the global quality in your mysite/_config.php file by adding this line
// Make all images nice and fancy
By default its about 75 I think so this will increase load times and CPU work that needs to be done therefore it will use more PHP Memory as well so if you are on a slow shared host I wouldnt recommend it! but it will give you crisper images
I run my own server with multiple websites. I have an older client site running 2.2.2 rc3, and uploaded said image I'm testing into that site to test out. Uploaded through that website, it works perfectly and no major quality loss. Only some cause the setting is at 90, but it works as should. Odd.
Does setting the GD quality in the config file make it slower than setting it in the gd.php file? I'm assuming no, and you just mean the memory issue is caused by having higher quality image, just want to be positive.
As for the resized image, as soon as I click the thumbnail image in tiny_mce preview, it maxes out the value at 600px. I can resize it to the proper dimensions before inserting it, and it loads fine in the content area, but this isn't very convenient for clients. Shouldn't be a problem for this site, but in general I'm curious.
*Edit* Just put it in the config, and error was thrown saying called to undefined method. Is this even a setting or did you type it wrong?
I dont think Ive typed it wrong? what version of SS you using?
GD::set_default_quality() calls the function set_default_quality() in the GD class (GD.php) so if you open GD.php (its in sapphire/filesystem?) I think it was renamed from setQuality() to set_default_quality() so try setQuality()