Korg Poly800/EX800 Users group photo

Yahoo Groups archive

Korg Poly800/EX800 Users

Archive for korgpolyex.

Index last updated: 2026-03-30 01:10 UTC

Thread

tif patchsheets

tif patchsheets

2001-11-13 by creekree@gmx.de

hi!

perhaps you have noticed that i replaced the jpg-patchsheets with zips
containing tiffs. now the patches are of half the size.
they were scanned in b/w at 200 dpi with 1bit per pixel in the
tiff-format and then i put them into photopaint (i don´t have
photoshop) and saved them as tiff with ccitt4-compression. (my twain
doesn´t support tiff-compression)
i chose these procedure after playing around with the settings for
half an hour.
olgu posted that tif-images would be about only 10% the size of jpgs,
that might be true but unfortunately it seems that i can´t do this
while at the same time keeping the files readable.

this is why i posted the settings that led to the images: someone
around with good knowledge of graphicsoftware? tell me which settings
to use to get the same quality but a smaller file.....
personally i don´t really care about the size of files (have dsl) but
there seem to be some people around that surf the web the 14k-way...
so it would help them a lot!

ok, so long

christian

Re: [korgpolyex] tif patchsheets

2001-11-13 by Alex Theakston

I'm pretty graphic literate (to say the least :D), you should be
using JPGs really, just bring the quality down a bit.
I can do it for you, if you show me where the files are: I'm
a photoshopper.
Alex

Re: [korgpolyex] tif patchsheets

2001-11-13 by OlGu

Hi,

once again for TIFs. I would suggest:
- scan with greyscale, choose dpi resolution to get a file size of about 11
MBs (approx. 4000 x 3000 pixels 8bit).
- save as tif or bmp
- open in photopaint
- best is to adjust levels to get "white" instead of light grey tones and as
much black as possible, before you convert it to b/w
- perhaps you find an adjustment for threshold or so
- avoid to use "dithering" or so
- save it as tif ccitt4
- you can try to use ACDSee's converting (right mouse click menu)
- you're right it will only compress to 15%...20% of jpeg and sometimes it's
white on black

And: it's not only a question of download time, but also of memory space on
the group site

Olaf (don't know why sometimes "olgu" appears....)

PS:
Many many thanks for all those patches.
Tried some patches and they sound very good, but who can edit all those
parameters completely?????

Isn't it NECESSARY to develop a software tool according to Lee's idea?



----- Original Message -----
From: <creekree@...>
To: <korgpolyex@yahoogroups.com>
Sent: Tuesday, November 13, 2001 12:53 PM
Subject: [korgpolyex] tif patchsheets


hi!

perhaps you have noticed that i replaced the jpg-patchsheets with zips
containing tiffs. now the patches are of half the size.
they were scanned in b/w at 200 dpi with 1bit per pixel in the
tiff-format and then i put them into photopaint (i don´t have
photoshop) and saved them as tiff with ccitt4-compression. (my twain
doesn´t support tiff-compression)
i chose these procedure after playing around with the settings for
half an hour.
olgu posted that tif-images would be about only 10% the size of jpgs,
that might be true but unfortunately it seems that i can´t do this
while at the same time keeping the files readable.

this is why i posted the settings that led to the images: someone
around with good knowledge of graphicsoftware? tell me which settings
to use to get the same quality but a smaller file.....
personally i don´t really care about the size of files (have dsl) but
there seem to be some people around that surf the web the 14k-way...
so it would help them a lot!

ok, so long

christian




To unsubscribe from this group, send an email to:
korgpolyex-unsubscribe@yahoogroups.com



Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/

Re: tif patchsheets

2001-11-13 by creekree@gmx.de

hi!

well... for those patchsheets: i think they are ok by now, as they
total to less than 2mb now, the biggest file having 249kb....
if someone still feels that they should be smaller and is willing
and able to do it i offer to send him an email with a plain greyscale
jpg of each single sheet (i scanned each of them at least two times
now and did not save the jpgs (what for? after all i got them on paper
already; so i would have to scan them again)). then they may be
modified, compressed, edited and whatever... oh yeah: of course
uploaded ;)
but that would be no prob, i´d do it. but only if necessary.....
opinions please?

christian

Re: tif patchsheets

2001-11-24 by darrell@palancar.net

> well... for those patchsheets: i think they are ok by now, as they
> total to less than 2mb now, the biggest file having 249kb....
> if someone still feels that they should be smaller and is willing
> and able to do it i offer to send him an email with a plain
greyscale
> jpg of each single sheet (i scanned each of them at least two times
> now and did not save the jpgs (what for? after all i got them on
paper
> already; so i would have to scan them again)). then they may be
> modified, compressed, edited and whatever... oh yeah: of course
> uploaded ;)
> but that would be no prob, i´d do it. but only if necessary.....
> opinions please?

I think these are okay - the best option would be to scan them at
*very* high resolution and run them through an OCR program to convert
them to text.

Better yet - I'd think the best solution is to get them entered into
the Poly or EX and save them as SYX, as those take up almost no
space. Has anybody transcribed all of these into theirs yet (before
I consider attempting such an undertaking)?

Darrell
http://www.palancar.net
darrell@...

Re: tif patchsheets

2001-11-26 by Oscar

I've been trying to take a higher-resolution version of the first
patch sheet and convert it to text with OCR. The first try didn't
work very well. I'm going to try again with the gridlines taken out
by hand, to see if that helps.

The sysex idea is a good one, but I'll leave that work to some other
brave soul. Besides, my mkII sysex wouldn't work on a regular Poly-
800, would it?

--- In korgpolyex@y..., darrell@p... wrote:
> I think these are okay - the best option would be to scan them at
> *very* high resolution and run them through an OCR program to
convert
> them to text.
>
> Better yet - I'd think the best solution is to get them entered
into
> the Poly or EX and save them as SYX, as those take up almost no
> space. Has anybody transcribed all of these into theirs yet
(before
> I consider attempting such an undertaking)?