ok ok ..i had a pop up blocker on and i have allowed pop ups and now successfully downloaded the file.
i have followed your instructions (had to type in 'cd.. ' twice...first time went to documents and settings...second time got me to where i should have been!!) typed in 'cd thumbs' all went well then went to next step ithmbconv(replace with my filename).ithmb and it says 'this is not recognised as and internal or exoternal command, operable program or batch file Thats as far as i have got :) says 'this is not recognised as and internal or exoternal command, operable program or batch file With command-line programs (such as this one) the program must either be in a system path or in the current directory you are in. So, you should put ithmbconv.exe into: C:\Windows or C:\Windows\System32 or the directory you are going to CD to (e.g: where the ithmb files are). or you must type the exact path to wherever you have saved ithmbconv.exe to - so that if you've saved ithmbconv.exe to D:\MyProgs, the ithmb files to D:\MyIpod\ithmbs\F00, and the file to convert is T114.ithmb, then you would type (on one line): D:\MyProgs\ithmbconv.exe D:\MyIpod\ithmbs\F00\T114.ithmb ----- The easiest is to copy ithmbconv.exe to C:\Windows If there is a space character in any path like in, for example, C:\Program Files\ithmbs\T114.ithmb then you must enclose the path in double quotes: "C:\Program Files\ithmbs\T114.ithmb" ----- The format for the command-line is: ithmbconv.exe ithmbname.ithmb (which will convert a specific ithmb file to 4 PPM files) or ithmbconv.exe ithmbdir (which will convert all ithmbs in a directory and sub-directories to 4 PPM files for each ithmb file found in that directory or sub-directories) Be careful with files named: F1019_1.ithmb F1015_1.ithmb F1024_1.ithmb F1036_1.ithmb as these are container files for ithmb pictures. They can potentially hold hundreds of pictures in them and when you do the conversion you will get 4 files for each ithmb picture - so watch your disk space! Hope that helps ;) ithmbconv exe *Download Zip* https://1tacawunge.blogspot.com/?nu=2wIpt6 Question - is that hard to modify ithmbconv so it would do 2-ways conversion - from ITHMB -> PPM and PPM -> ITHMB? Or maybe just somehow resize those HUGE ITHMB files that lame iTune creates from small JPGs? The reason I'm asking is that it's just a big waste of space copying JPGs to iPhone. I wanted to put all my pics (reasonably downsized to 1024x768) to the device - about 5500 files 800 MB total and realized it eats full 3.5 GB as ITHMBs!!!! That's not good, isn't that? 8-) Question - is that hard to modify ithmbconv so it would do 2-ways conversion - from ITHMB -> PPM and PPM -> ITHMB? The actual ithmbs are just 16bit-raw picture files (no compression) - that's the reason for their "extreme" size. With that ithmb converter all that it is doing is basically splitting up the file into it's components and then converts them to 24bit, then to PPM. Some parts of the ithmb though are in reversed byte order so a little extra "hacking" is done to reverse it back before the 24bit conversion. PPM is pretty much a raw picture file too with just a header that allows a "paint" program to make sense of the file and how it it structured (width, height, and colour depth). This then allows the "paint" program to be able to edit it or allow you to create batch operations on them such as converting to other file formats. Or maybe just somehow resize those HUGE ITHMB files that lame iTune creates from small JPGs? iTunes needs to use this format (raw) for it to work on the various screen sizes without necessarily performing any computing on them. That's why you have 4 images of the same picture at different resolutions. I'm guessing that the processor on those things aren't too powerful or economic (yet). Any time spent converting the pictures from jpeg (or other) to raw (which is what the actual screen would use) would drain the batteries due to the extra computing overhead required by the processor - especially if you viewed the pictures one after the other. So the problem is that ITHMB format doesn't support compression No. The ITHMB is compressible. It's just that Apple decided not to use it that way. As I said, one of the reasons being in the extra computing power needed to decompress the picture from, say, jpeg->raw so that it can be displayed on the screen. This would increase power consumption of the batteries when it came to displaying the picture. Perhaps the processor is not fast enough to do on-the-fly decompression of JPEG's - which would detract from the "experience" of flipping through your image files on the iPOD (there would be a delay between each image shown). could it be a solution in reducing stored images resolution? You and I can see that it would be true - that's the logical assumption. But there must be a practical reason why they didn't. Even the "thumbnails" they show when playing a song are stored in the "raw" format. I believe that iPhone screen is 320x480 and this shouldn't take 650 Kb, even BMP file in that size is smaller! That is correct. But the ITHMB image format is made up of the four images of the original image in four sizes. Here's part of the C header used in ithmbconv: #define TVWIDTH720 #define TVHEIGHT480 #define G4_SIZE794040// Size of 4G iPod iThmb file #define G4_TVSIZE(TVWIDTH*(TVHEIGHT/2)*2)// one frame in YUV 4:2:2 TV output (2 frames need to be read) #define G4_FSSIZE(176*220*2)// Full Screen picture in 16bit RGB 5:6:5 (needs byte-swap too!) #define G4_PBSIZE(42*30*2)// Photo Browser picture in 16bit RGB 5:6:5 #define G4_SPSIZE(130*88*2)// Slideshow Preview picture in 16bit RGB 5:6:5 #define G4_TVOFFSET0// Offset of TV output in file #define G4_FSOFFSET691200// Offset of Full Screen picture in file #define G4_PBOFFSET768640// Offset of Photo Browser picture in file #define G4_SPOFFSET771160// Offset of Slideshow Preview picture in file //-------------------------- #define G5_SIZE871780// Size of 5G iPod iThmb file #define G5_TVSIZE(TVWIDTH*(TVHEIGHT/2)*2)// one frame in YUV 4:2:2 TV output (2 frames need to be read) #define G5_FSSIZE(320*240*2)// Full Screen picture in 16bit RGB 5:6:5 #define G5_PBSIZE(50*41*2)// Photo Browser picture in 16bit RGB 5:6:5 #define G5_SPSIZE(130*88*2)// Slideshow Preview picture in 16bit RGB 5:6:5 #define G5_TVOFFSET0// Offset of TV output in file #define G5_SPOFFSET691200// Offset of Slideshow Preview picture in file #define G5_FSOFFSET714080// Offset of Full Screen picture in file #define G5_PBOFFSET867680// Offset of Photo Browser picture in file Note the Gn_xxOFFSET positions. These represent the locations of the (4) different sized images of just one ITHMB image file. Notice that the Gen5 ITHMB is even bigger than the Gen4? Unfortunately this is how the iPOD's OS works with it's hardware : [edit: If you want the source-code (in 'C') to the latest ithmbconv, which handles the multiple images in one huge (xxxMBytes) ithmb file, just let me know and I'll put it up somewhere] Well, I believe iPhone has enough processing power to rescale JPG in real time, at least that's what it does with pictures on web sites, so it looks like Apple's design decision - they didn't want to spend too much time adopting JPGs in iTunes when Ithmb were already supported there. What if you compress images in ithmb file to see maybe iPhone would accept them? This app would be a HUGE thing because iPhone is really good at showing pictures but wasting 4 Gig's instead of 800Mb, that just makes me crying.... and I think I'm not alone.... Or here is another idea (if the compression algorithm is too complicated) - what if you remove 3 out of 4 images in ithmb, saving just G5_FSSIZE (320x240)? Or maybe replace them with small 'dummy' images if the device doesn't accept ithmb with G5 only... By the way the latest ithmbconv (maybe with sources, as I'm C++ developer too, just a way too lazy :-)) would be nice to have as the last time I tried to extract images from ithmb I got this error - "File type is unknown: 671600 bytes." What if you compress images in ithmb file to see maybe iPhone would accept them? Well, I'd try if I had an iPhone... I don't even have an iPod (or access to one)! iThmbConv was created blindly by getting the info off the internet about the format and some testing by the users here on Whirlpool. I'd need to find out some more info about the iPhone's image format(s) :( Or here is another idea (if the compression algorithm is too complicated) - what if you remove 3 out of 4 images in ithmb, saving just G5_FSSIZE (320x240)? Or maybe replace them with small 'dummy' images if the device doesn't accept ithmb with G5 only... The iPod won't recognise anything other than it's correct format. iTunes actually resizes and formats the image before sending it to the iPod. By the way the latest ithmbconv (maybe with sources, as I'm C++ developer too, just a way too lazy :-)) No problems... I'll put it up on QuickShare.com after I post this post ;) the last time I tried to extract images from ithmb I got this error - "File type is unknown: 671600 bytes." Ah! That'll be because it was expecting a file of exactly G4_SIZE or G5_SIZE (see my previous post) in bytes. Back in a tick with that link to QuickShare.com... I have uploaded real ithmb file here rapidshare.com/files/467...T1016.ithmb.html so you could test it. Tested - it's not a format recognised. Is it a iPod or an iPhone ithmb, and which version (generation)? Which directory did you get this file from (e.g: /photos/iPod Photo Cache/F00). I might be able to track down the format and add it to my program. Well, I'm getting the same error. If you read the information on this page by Jesse Hollington (first post) you will see the breakdown of the various formats and sizes that ithmbconv for iPods supports (except Album Artwork) . This is where I got the info from that ithmbconv uses. The file you put up on RapidShare is not even the size of a 720x480 16bit picture which is the first part of a G4 or G5 iPod ithmb file and it's way to big to be a Nano iPod ithmb file! And that file name suggests it's not part of an ithmb "Photo Library" file. Are you sure it's not corrupted? eebf2c3492 -- You received this message because you are subscribed to the Google Groups "Dubai Property Trading Society" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/dubaitrading/3d584b73-097e-466d-8e56-a300253e927an%40googlegroups.com.
