Recent content by Joe90

Hi @domb84 I think what you want can be achieved using the GUI. The following workflow seems to work: 1. Unpack the firmware partitions using Quick unpack (taking note of which file is Partition 0 and Partition 1) 2. Make your changes 3. Compress Partition 0 using full compression (mode c) 4...

Hi @domb84 I was messing with the firmware you dumped last night and noticed that after repacking the firmware partitions and merging them, like you have done, that the first 2,296 bytes of the original file are not reinstated. What they are and whether or not some of them need to be updated...

Hi @domb84 Thanks very much for dumping and sharing the firmware. There are some other filenames that appear in the smaller partition: LDDV180N.BIN FWDV180NT.BIN FWDV180NC.BIN You may end up using the programmer anyway, but one of those names might work. Best, Joe

Apart from the Kodak machines they all look very similar but some have different hardware (e.g. LCD panels). If you can get a copy of the firmware using a chip programmer, I'll happily make you a firmware image with the modifications you want from the forum here. You'd also be helping a user on...

Hey @domb84 I just saw your post now. The Kodak Reelz firmware won't be flashed by your machine because, as you correctly figured out, it's looking for a different file name. Please don't attempt to flash your M127 machine with any Reflecta/Somikon/Wolverine firmware. Although the M127 is made...

No problem. Here's a QP30 A and B firmware. Let me know how it goes. EDIT: Uploaded QP40 images also.

It's the QP being low and the amount of motion in The Black Hole clip (I think). That's a good idea. Thanks for doing all the testing! Here's Firmware A and Firmware B with QP20.

I love that film!! It looks great. Love the music by John Barry. It looks like the same timeout as before. So just the odd frame is timing out with QP10. Here's QP11 for you to try. I'll upload QP12 in a few minutes. EDIT: I see what you mean now about it "getting upset" it's gone and encoded...

Yes, that's exactly what the problem is. The scanner only has 500ms to get a frame scanned and on to the SD card. So, we need to go in the opposite direction. To make it easier for the scanner to encode on time we need to increase the QP to 11 or 12. There is another way, we could, in theory...

Thanks very much for doing that comparison! No, it's not a "night and day" difference like I saw with the Somikon scanner. However, you can see all of the film grain with the QP10 firmware and with your standard firmware the grain is causing tiny rectangular shapes which are taller vertically...

That's brilliant. I'm glad one of them worked. I'm looking forward to seeing the comparisons.

Ah that's really interesting. It looks like the encoding takes too long with that setting.

Thanks, I downloaded the Java app from the link in your first post. I made the modification again but this time I used Tobias' Java app to unpack and repack. The checksum needs to be calculated twice when you're using the console app :-0 I've attached the firmware images I've redone so far.

You're correct QP0 is max quality. It might be the checksum that's not correct? I'm using Tobias' command line tools rather than the Java app.

That's weird. I used the 1440p HBR Firmware B from your Proton drive.