Welcome to mirror list, hosted at ThFree Co, Russian Federation.

git.blender.org/blender.git - Unnamed repository; edit this file 'description' to name the repository.
summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorPeter Schlaile <peter@schlaile.de>2008-06-03 01:35:57 +0400
committerPeter Schlaile <peter@schlaile.de>2008-06-03 01:35:57 +0400
commitca8aa8c901934dc0e3eb1b65618d40bfb65f9111 (patch)
tree72e3ea5d2f5e224a683e064d34f6ee47eff90c59 /extern/libredcode/NOTES
parent8a5f36219214b4a5b8348b8e200ef5aac2297963 (diff)
== RED one (redcode) ==
This adds redcode (the file format of RED one, R3D) support to blender. Seems to work fine with the footage I found on the web, but keep in mind, that because of the unoptimized nature of libopenjpeg, frame decoding isn't that fast. It is also a rather challenging task, to make 4k-float-footage realtime :)
Diffstat (limited to 'extern/libredcode/NOTES')
-rw-r--r--extern/libredcode/NOTES23
1 files changed, 23 insertions, 0 deletions
diff --git a/extern/libredcode/NOTES b/extern/libredcode/NOTES
new file mode 100644
index 00000000000..39101e0bd63
--- /dev/null
+++ b/extern/libredcode/NOTES
@@ -0,0 +1,23 @@
+This is a redcode decoder written solely by looking at some
+R3D files that are floating around on the web.
+
+This decoder works with the files I tested, but I don't give
+any guarantee (especially, if RED decides to change the
+file format).
+
+That said: I found it a really nice idea of them, to make
+such a clear and comprehensible file layout.
+
+Choosing JPEG2000 as an encoding format and the way, they
+did YCbCr encoding of the sensor data is simply brilliant.
+
+My approach of decoding the sensor data is probably not
+so brilliant, but seems to work rather nicely (and sharply!).
+
+If someone finds a better way and/or RED decides to release
+specification, just go ahead and feel free to change it!
+
+Until that happens: simply enjoy opening RED footage within Blender!
+
+-- Peter Schlaile, June 2008
+