Odyssey7 & Odyssey7Q October 2014 Firmware Update

Thanks for the info. A client I did a shoot for a few weeks ago insisted on XAVC 4K S-log3/cine. I recorded a safety 1920x1080 ProRes proxy on my 7Q with a lut baked in, but they didn't want it since they thought it would be an issue for MC without transcoding and would have preferred DN-xHD. It was their first project in 4K and the editor ended up asking me to email a few frame grabs of the ProRes files for a grading reference. IMHO, they should consider using Davinci Resolve to grade and then import into MC. I use PPro CC which can basically take any codec, but I have heard the earlier versions of MC could be fussy if the codec wasn't recognized.


http://andersonvideoproductions.com/ Sony F5, PMW-500 XDCAM, Canon C300, BMCC and Panasonic HD
 
Jim Anderson said:
Mitch, any updates yet on the DNx-HD capability option on the 7Q? My clients are increasingly requesting 4K XAVC (usually S-Log2 or 3) and a backup proxy with the LUT baked in. The ProRes flavor has been okay, but DNx-HD would save them having to convert the proxies (for Avid). Hoping the release of the new 7Q+ won't delay the firmware version upgrade for the trusty 7Q owners. http://andersonvideoproductions.com/ Sony F5, PMW-500 XDCAM, Canon C300, BMCC and Panasonic HD
Click to expand...
We continue to be committed to bringing DNxHD recording to the Odyssey line of monitor/recorders. Such an introduction would be made for all of the available Odyssey devices and at the same time.
 
Hey Mitch,

I know you've mentioned it elsewhere, but I can never find anything on here. When is the planned release for custom LUT support? Do you have any details on the LUT support itself?
 
I don't want to publish a planned release date for the programmable LUT functions in case we hit a snag and have to change things. That always ends up biting us, and by us I really mean me. But I will say that we are very actively working on it and it is a priority.

I have posted a lot of details on it in the past so you might want to do a search for just my posts and you should find some info. The current goal is to base everything on standard 3D-LUT Image Cubes like one would generate in Resolve. Several LUTs could be stored in the Odyssey7Q or 7Q+ internal memory. LUTs have up to six possible destinations for application and one would be able to decide where the LUTs would be utilized: SDI A Out, SDI B Out, HDMI Out, OLED screen, Image Analysis Tools (waveform, etc.), baked into ProRes recording. There is the possibility that we will have to lock in or gang together some of those as processor space may get filled up, but that's the general idea.

Does that answer your question?
 
Thanks Mitch! That more than answers my question. I sure do look forward to the release of that option whenever it does happen!
 
Pgale said:
I'm still seeing the zoom bug where lines from the top of the screen are shown at the bottom. These increase the more you zoom in and out. I've reported it again to support (many weeks ago) but no response.
Click to expand...

I never had this issue before and now I do. Great job on fixing the bug with FW. Just started today out of the blue and continued after repeated rebooting. Jeez, I wonder if the 7Q will ever have a stable FW release?
 
Prendi said:
I never had this issue before and now I do. Great job on fixing the bug with FW. Just started today out of the blue and continued after repeated rebooting. Jeez, I wonder if the 7Q will ever have a stable FW release?
Click to expand...
This is addressed in our soon to be released update.
 
yes it's been very quiet for a while - a bug fix to sort some of those niggling bugs would be very welcome.
 
We actually had a firmware update ready to go a few weeks ago, and then discovered a file corruption issue had cropped up. Tracking that down poved to be a rather painful task.

One of these days I'm going to ask the engineers to more clearly explain exactly how this happens. They do some work in one area, something like generating custom frame guides, and somehow it interacts weird with a bunch of code in a completely unrelated area and corrupts a file when recording. But it might only corrupt in some singularly obscure way, say when recording 60i over HDMI from a Canon DSLR. Won't effect SDI, won't effect non-Canon DSLRs, won't effect Canon cameras that aren't DSLRs but are still coming in over HDMI at the same frame rate. It's maddening I tell you!

Whenever we develop new code there is an extensive series of tests, and frankly these tests have gotten considerably longer and more complex as we have added more and more features. We have one group of engineers working on new firmware, another on testing and then another on figuring out why something went wrong in whatever test. They are all interacting all the time so as to be as efficient as possible and help both prevent issues as well as hunt them down once they are discovered. It would drive me insane.

So all that is to say that new firmware is definitely on the way. Don't know how long it will be until we can release it though. It's really impossible to say until they complete these endless tests. It takes three solid days to run through the permutations when they DON'T find any problems. And they ALWAYS find problems.

I can only pity the fools at places like Microsoft.
 
You must log in or register to reply here.
Back
Top