389 karma · joined January 29, 2017
Every time I look up what Apple's trade-in will be, I have to compare it to eBay to make sure I've not gone crazy.
Keeping with the "unconventional" theme, lips are more sensitive to temperature than fingers, but make sure you don't burn your fingers before you try kissing the chip. With practice, your lips can tell which 0402 passive is getting hotter than others.
Or you can buy a thermal camera.
I'm more impressed by the long-term goal of 500Mbps upload speeds.
I'd say it's one of my most essential pieces of kit that I take with me.
It does not allow you to compile C code to assembly, but you can run example assembly code through the system and observer cache hits/misses, memory access and I/O accesses. It's a really useful educational tool.
You get a different dialog box with an option to open the file and this saves a lot of clicking.
WARNING - This document contains technical data whose export is restricted by the Arms Export Control Act (Title 22, U.S.C., Sec 2751, et seq.) or the Export Administration Act of 1979, as amended, Title 50 U.S.C., App. 2401 et seq. Violation of these export laws are subject to severe criminal penalties. Disseminate in accordance with provisions of DoD Directive 5230.25.
DISTRIBUTION STATEMENT D - Distribution authorized to the Department of Defense and DoD contractors only due to critical technology. This determination was made on 26 June 2000. Other requests for this document shall be referred to Commander, U.S. Army Aviation and Missile Command, ATTN: SFAE-AV-AAH- ATH, Redstone Arsenal, AL 35898 - 5000.
DESTRUCTION NOTICE - Destroy by any method that will prevent disclosure of contents or reconstruction of the document.
You can only hope that the uploader is who they say they are...
Yeah, I know. That was very naieve.
One engineer suggests that they probably defrost the chicken first.
* Create project *and set the frame rate before importing video clips, because you can't change it once you've got clips*.
* Choose "DaVinci YRGB Color Managed" under project settings, Color Managment - this is more flexible for coloring later on.
* Add your media, then choose any clip(s), right-click and and create timeline from it.
* Use NLE functions to make the edit.
* Color grade (and stabilise clips).
- Turn on Scopes -> Waveform (UI bottom right) and set the white balance by dragging the 'dot' in the middle of the Offset wheel.
You want the red/green/blue waves to overlap where there's a region of grey/white in your video frame.
This can be tough if you have no grey/white, but you can copy color settings from other clips.
- Adjust other settings as necessary.
* Deliver/export.I find what I want online (I'm not counting this towards the total time). I go to the store and walk in the exit, through the checkouts to the storage hangar, use the computer to look up which aisle my Knoppflogg (or whatever) is stored, pick it out and go.
I love that the Windows XPRA client gives you a task-bar icon for the applications menu of the Linux host that I'm connected to.
https://blog.xkcd.com/2010/05/03/color-survey-results/
And still, nobody can spell fuchsia.
I don't believe CinemaDNG is affected by Red patents because it's basically just a folder of numerically sequenced '.dng' still images and DNG is an Adobe standard. You see other companies using it.
Note: I am not a lawyer and Red may well have tried to sue somehow, but the basics of CinemaDNG compression go back to JPEG T-81 from the 1990's.
Then I move on to more complex parsing of text in the file.
I try to get this building cleanly and working on Windows, Mac and Linux.
If you want to get an idea of the challenges that modern CPUs face, then this is a very good starting point.
https://en.wikipedia.org/wiki/Timeline_of_arcade_video_game_...
The process is: Raw input pixels (8 or 10 bit) minus predicted pixels (8 or 10 bit) -> residual pixels (8 or 10 bit + 1 sign bit).
You take these residual pixels and pass them through a 2D DCT, then scale and quantise them. At the end of this, the quantised DCT residual values are signed 16-bit numbers - you don't get to choose the bit-depth here; it's part of the standard (section 8.6). For every 16x16 pixel input, you get a 16x16 array of signed 16-bit numbers.
The last step is to pass all non-zero quantised DCT residual values through an entropy coder (usually an arithmetic coder), then you get the final bitstream.
The key point is that it didn't matter if the original raw pixel input was 8-bit or 10-bit; the quantised DCT residual values became 16 bits before being compressed and transmitted. This is also true for 12-bit raw pixel inputs.
This seems impossible; for 8-bit inputs, you've doubled the size of the data (slightly less than double for 10-bits), so you must be making things worse! The key is that after scaling and quantisation, most of those 16-bit words are zero. Those that are non-zero are statistically closer to zero so that the entropy encoder won't have to spend a lot of bits signalling them.
The last part comes when you reverse this process. The mathematical losses from scaling and quantising 10-bit inputs into the transmitted 16-bit values are less than the losses for 8-bit inputs. When you run the inverse quant, scale and iDCT, you end up with values that are closer to the original residual values at 10-bit than you do at 8-bit.
* An array of MEMS micro-mirrors which turn to reflect light, or
* Finisar's LCoS based method, which uses a 1" LCD TV display to display a gradient pattern which literally bends light.
It looks like the undersea cables use Finisar's (now II-IV's) WSS. I think the idea of bending light under software control is pretty cool.
Finisar's white paper showing optical path and other possible uses is here: https://www.amstechnologies.com/fileadmin/amsmedia/downloads...