Jump to content

Jedi Master

  • Posts

  • Joined

  • Last visited

1 Follower

About Jedi Master

Profile Information

  • My cameras and kit
    Sony A6500

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Jedi Master's Achievements

Active member

Active member (3/5)



  1. Not bigger than Apple, but there are plenty of companies much bigger than RED (and Nikon+RED).
  2. It'll be interesting to see if the new patent holds up in court. There will be several companies with deep pockets fighting to invalidate it.
  3. It'll all be moot in a few years anyway when RED's patent expires.
  4. Here's an interesting article related to the Nikon Z9. Nikon is developing a derivative of the Z9 for use by astronauts on the moon. https://www.theverge.com/2024/3/1/24087610/nikon-nasa-hulc-handheld-universal-lunar-camera-artemis-moon-mission
  5. The FX30 is on sale today at B&H for $50... Alas, it's a mistake in the ad copy and when you go to the site, it's actually $1798.
  6. I think it's mainly tradition and what people are used to. Kind of like asking why more people like red than blue or why some people prefer LP sound.
  7. All UNIX, and UNIX-derived, systems hide files with names starting with "." from directory searches. You can see these using ls on the the command line with "ls -a" (or "ls -al" if you want more detail).
  8. Beyond Compare is what most people where I work use. There's a Mac version available.
  9. Interesting. I wasn't aware of Resolve's logs--I'll have to check it out. In my case, the errors I was seeing didn't involve Resolve because I was copying files using Windows Explorer, not Resolve. The two types of error I saw, file mis-compares, and missing files, did not show up in any Windows log (as viewed in Event Viewer). Many Windows applications create temporary files with prefixes and/or suffixes added to the eventual permanent file name when doing certain operations on files, so perhaps Macs do something similar and that file you saw beginning with ._ was a temporary file that was later removed.
  10. I didn't think FORTRAN was too bad back when I used it. The alternative (at the time) was BASIC, which was quite popular, but I never cared much for it. Yes, punch cards were a real pain! The basement of the computer center had about a dozen IBM card punch machines, and they were always in use during the day, so lots of people, including me, did our work at odd hours to avoid the rush. The biggest fear we had was dropping a card deck and having to put all the cards back in order. The first design I worked on after university was a custom bit-sliced CPU. It was microcoded and I wrote the microcode assembler in FORTRAN on a Data General Eclipse minicomputer. FORTRAN is still pretty popular among the scientific crowd, who use it for things like modeling dynamic systems.
  11. I learned FORTRAN in high school. It was the first high-level language I learned. At university, the first CS class that every CS major had to take was a FORTRAN programming class. I was an EE major, but I took it anyway as I could see that's where the industry was headed. The work was done on a CDC 6400 mainframe using punched cards. The second CS course, which I also took, used Pascal, which was a big improvement over FORTRAN, although even some of the CS majors just couldn't get their heads around the concept of pointers (they seemed natural to me). After that, everything was in C, which is the language that I use to this day when working on microcontroller projects (as a hobby). My professional work mostly revolves around working with hardware description languages, primarily SystemVerilog, and the various tools used for simulation and verification.
  12. This has got me curious enough to dig deeper. I'll try with several other computers running various operating systems, different cables, etc. Hopefully I can identify the root cause of the miscompares.
  • Create New...