Jump to content

Mokara

Members
  • Content Count

    311
  • Joined

  • Last visited

About Mokara

  • Rank
    Frequent member

Recent Profile Visitors

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

  1. Playback does not involve rendering. It is just decoding, the data is not being transformed. Usually when you encounter issues like this it is a case of the software doing the decoding rather than hardware. Since software decoders vary considerably in efficiency, some will give smooth output while others will stutter. In this case since the issue seems 10 bit centric, my guess is that various software is treating those files very differently as a result, which is causing the performance issues.
  2. Mokara

    Framerate

    It is not an artistic brain, it is a Pavlovian response to the fact that movies have traditionally been shot at 24p while ignoring the fact that nobody outside of a cinema (or a BluRay/DVD disc on a TV) views anything at 24p. You see stuff you admire and try to emulate it without understanding WHY things are shot like that. There is a difference between 24p and 25p. Because of frame mismatch there will be a stutter twice a second (unless you are viewing in a cinema or from a BluRay/DVD disc).
  3. Mokara

    Framerate

    The people who tell you to shoot at 24p because that is what movies are shot at don't know what they are talking about. Shoot at the framerate you expect it to be displayed at. 24p works for movies because movie projectors display 24 fps. But if you try to display that on a device operating at a different frame rate then expect problems unless you do sophisticated interpolation (and if you are going to do that, you might as well shoot a the proper frame rate to begin with - far fewer problems later on). If you are not shooting footage for cinema distribution, shoot at 25/30 - 50/60 fps (depending on where you live) if it is for commercial TV distribution, or 30 - 60 fps if for anything else. Flat panel TV sets (but not CRT panels) automatically adjust their frame rate to match the input (cell phones probably do this as well), but computer monitors and on-line video hosts do not - they run at 60 fps (or whatever you have manually selected the frame rate to be), anything else will have frames duplicated or removed which can result in serious visual artifacts. Broadcast TV sources use a fixed frame rate and any content shot with a different frame rate has to be re-rendered using sophisticated interpolation to generate something that is watchable. As a general rule of thumb, shoot at 30/60 fps and you should be ok for most viewing devices if you are not shooting commercially. For broadcast TV shoot at the PAL or NTSC standard, depending on where you live.
  4. Well, that is perfect subject matter for the camera test - back packing cats!
  5. Graphics cards on laptops are not the same as the ones in desktops in terms of capability. That is likely your problem. A laptop is NOT a replacement for a desktop when video editing is concerned. If a hardware decoder is being used it won't show up in tools since the work is not being done in the processor cores. That is why it doesn't look like they are being fully utilized (when they probably are, at least in so far as the hardware decoder is concerned).
  6. It is a Canon. The colors are lovely. Of course you will!! I think the intended customers are children.
  7. That is absolutely NOT how Mr. Jobs would have done it. He was all about control and squeezing competition out, that means proprietary everything. That was his thing. Steve Jobs believed that he knew what the consumer wanted better than what they knew they wanted (he said so himself). You got what he gave you, he packaged it as "hip" and got opinion leaders to buy in to an elitist image knowing that the sheep would follow. That, together with absolute control over the ecosystem, was his business plan. It was NOT a consumer friendly business plan, consumers were gullible chumps there to be exploited by sophisticated marketing. You mean like Russian Doll?
  8. 95 MB/s is the read rate. Burst write rates are usually a lot less and sustained writes even lower. Keep in mind that your effective write speed is going to be determined by the lowest write speed, actual write rates fluctuate during a recording, sometimes wildly. What you see in a burst spike is not necessarily what you are going to get if you are recording for a period of time. It will be the minimum write speed, not the maximum. Also, write times can vary considerably depending on the capacity of the card.
  9. Is that a possibility? What will happen to cat videos if the app wipes them out? How will new cameras be tested properly in the absence of cats?
  10. As a general rule of thumb, most stuff that costs under a few hundred dollars should be treated as disposable. It is too expensive to fix, and if the manufacturer does not provide you with a prepaid RMA, too expensive to exchange. A warranty is pretty much worthless if it costs almost as much as a new one to ship it back to them. Just go and buy a new one.
  11. CinemaDNG is an open format, but BM was using a modified extension of it. It was likely those modifications which ran foul of other people's IP, not cinemaDNG itself.
  12. Right. Your dynamic range could be a foot or it could be a mile. ADC bits are the "ticks" on those scales when those distances are converted into a digital code. A bit in itself has no inherent size. A 12 bit tick on your foot ruler does not represent the same quantity as a 12 bit tick on your mile ruler.
  13. A ADC converts a analog signal into digital code. If your sensor can measure 1000 stops of dynamic range (as in, be able to accurately measure a low non zero quantity and a high quantity, the difference between which is your dynamic range), your ADC will convert that analog response into bits covering that range. An individual bit does NOT correspond to a stop of DR range. It could be the equivalent of 10 stops or it could be 0.1 stops. It is completely arbitrary. You could use a 12 bit ADC for your 11 stop DR sensor, or you could use a 256 bit ADC for it, or you could use a 4 bit ADC. The only thing that would change is the size of the steps between the highest and lowest analog value your sensor can detect. If your sensor had a 1000 stop DR, your 12 bit ADC would generate a digital version of that analog signal with 4096 possible values. The size of those 4096 steps will vary depending on what the dynamic range of your sensor actually is. If it 4 stops, those 4096 steps will correspond to small increments of the response, if it has 1000 stops, those 4096 steps will correspond to large increments of the response.
  14. You clearly don't know what ADC is. Your 12 bit ADC can cover 1000 stops of DR if necessary. There would just be big steps instead of little steps.
  15. But maybe guarantees invites from other companies! ;)
×
×
  • Create New...