Search results

More things sloppy Where Reelz or Reels, both claim 8.08 Megapixels, yet they both using an Aptina AR0330 sensor, which is only 3.15 Megapixels. The video mode used (likely) on the Aptina sensor is limited to 2304x1296 (ever wondered where the 1296p came from?) So have the marketing is from...

I too very occasionally see the error on the top of the frame (~2% of captures.) That is more baffling, as it might suggest there is no good timing between the motor control and the frame grab. The socket feed is in motion a lot, there is very little time when nothing is happening. a) 100ms -...

I might need help to find the trigger for the motor step function (and/or the frame grab function.) Even on the stock lens and firmware, you will occasionally see some instability at the bottom edge of the frame. This is a rolling shutter artifact, as the frame is being grabbed, at nearly the...

Thank you for the feedback. You should switch to V5.8 as the also fixes the missing full range flag in the video header (more dynamic range without color correction, or it saves you the ffmpeg step.) The crude manual-ish exposure control is still a work in progress. There will be more tweaks...

The cam is not a circle, so the 1.5mm would on the lump side only. You could also only increase the lump only 0.75mm, if you decrease the opposite side 0.75mm, it is the difference in the displacement at different angles that creates the motion path.

I would be interested in any code you have found regarding the motor functions. I didn't see any sprocket movement difference between Super8 and 8mm, even though the there is ~8.5% difference in the sprocket gap (~3.78mm - 8, ~4.1mm - S8). So it is possible that just a cam change for 16mm...

Funny story... It seems I've 99.9% recovered my Type-A. I soldered on the new SD Card connector, but discovered the missing pad is the write protect switch signal. I tried connecting to some of the nearby traces, with no luck, unit would report SD was write protected. However, as the unit could...

You will not gain any resolution either way, without replacing the lens. The new firmware has other advantages (I think anyway), but the resolution can't be firmware changes alone. The stock lens sees area of around 17mm wide (for the readout mode used), the firmware simply removed (mostly) the...

Hi @Gwennia, For some reason I couldn't get the first video to play or download, and I'm curious to see more of that mechanism in action. It seems that all you may need to do is 3D print a new cam (the weird shape plate on the end of the stepper motor), to make the socket move path longer. My...

My Type-A might be now dead, the SD Card slot broke when opened the case. I will get a replacement ordered, but the is now missing pad (from the removal), this might be hard to repair. Think this was just a shield ground, as it doesn't connect to the SD Card pins, but now one of those lines...

@Gwennia This was one of my earlier observations while improving the resolution, the original lens's FOV fully covers what is necessary to scan a 16mm film. It was like the origin optical system was designed for 16mm, not 8mm, even the current light bed is pretty good for standard 16mm. Using...

Good news, I now have Type-A, Type-B and Type-C Reelz/Reels scanners in my possession. While I intend to find additional extensions, I will catch the other units up first. Also have new lenses arrivng today.

Version 5.8 Attached. This version correctly sets the full range flag within the `avcC` MP4 atom. So not a big change, but will save you the workflow steps having to correct the files will FFMPEG after capture. Normally the Novatek SoC gets the 'avcC' data from the compression engine, but...

@ThePhage I didn't think exFAT was ever supported, just like any large cards aren't supported. I just tried at 128GB exFAT card, and it behaved as it was recording, yet not even the folders where created. I did format a 32GB card as exFAT, and that did work. However there would be no advantage...

This my first time a firmware hacking, and I starting with a working firmware update procedure. Without the stock firmware update step, I wouldn't have gotten anywhere. Sorry, I have no idea about the firmware partitioning.

Thank you for the detailed feedback. 1) The new compression rate control algorithm is doing for the best it can, but is still a tad flakly, as can crash the encoder. I get this crash maybe once or twice on a 5" reel. But like you see, I think the result are worth it. 2) I still what to make...

Version 5.7 attached I had to give up on full manual exposure, as you really needed to scan most reels at least twice, to handle under and overexposed scenes seperately. The 8-bit Gamma 2.2 encoding can't handle the potential dynamic range. But I don't like the drifting nature of the stock...

The 18Hz is not changing the exposure timing, only the file's playback frame rate.

@Andreas I have seen that too, about 10% of my captures have it. Although I'm not sure it is due to the 18Hz, as that is only modifying the data written to the header of the MP4. It is a timing issue where the frame is grabbed, just as the motor start/end that frame feed. Notice how it is...

I leveled up on my hacking skills. Here is Reels displaying it own histogram. I'm now compiling C code, and adding it the firmware. Previously it was all hand assembly (brain hurt). This histogram code is not ready to share, as it currently flickers and is only on during capture. This is a...