Odyssey7Q February 2014 Firmware Update
- Thread starter Mitch Gross
- Start date
Not sure they were exaggerated as such in terms of what it can eventually do - they are obviously a good company with great people and love their products but are so excited about them that they tend to over promise on delivery dates etc - I've heard that before about their other previous products.
They did say the same a couple of weeks ago!!Thanks for the info
cuervo
Veteran
yeah, you're right. they are good people. It's too bad I was misled, as were a lot of other people. I don't think it was intentional; and, eventually this product will mature to be very useful. I just hope it's sooner than later, and that this doesn't become a chronic mode of behavior.
Prophetmatt
Well-known member
As far as operating the 7q in raw as of now, what are some tricks to do so to make it the best it can be. I think I saw one ssd at a time for anything other than 240?
Is one ssd enough for 120 fps?
Mitch Gross
Veteran
With the new firmware different frame rates and different formats can be recorded without swapping drives.
Mitch Gross
Veteran
Yes.
Mitch Gross
Veteran
On LUTs:
When the question came up about the recording of LUTs, it was in regard to the future functionality of programmable LUTs. I also stated that the decision had not yet been made, and that it was a current debate within Convergent Design as to how we should implement programmable LUTs.
Currently, LUTs are only used for monitoring RAW recordings. On all Convergent Design products up to this moment we have never alterred the image, but instead faithfully recorded what was output from a camera. So this is something that as a company we are deciding how best to implement.
Our point is not about limiting functionality of a product, but instead protecting the end user. We want to make sure that you do not accidentally record one way when you intended to record another way. Some argue this is an interface issue, others argue that it is a "purity of design" issue which could over-complicate the use of the device. Remember, not everyone wants to spend their time being intimate with the functions of a device like the Odyssey7Q. It is a means to an end for them and they just want it to work without having to think too much about how it is set up. We are very cognizant of this.
Programmable LUTs are a pretty great thing, but there are a lot of ways to use them and one has to be careful not to make a mistake in the use. We have many outputs possible from the LUT stage: we could apply to the OLED panel, to the exposure tools, to SDI output #1, to SDI output #2, to the HDMI output, and lastly to an internal internal recording. It can be great to make them all selectable but that's a lot of choices and it can get quickly confusing. We would hate to make a system where it could be easy to accidentally record with a LUT baked in when you intended to record a Log image. So it is something we have to design carefully.
With all that said, our initial release for 4K-to-HD recording is designed only for Slog-2. If you send a REC709 signal from the camera the colors will be messed up. That does not mean that we do not intend to make it fully functional for REC709 and other functionality in the future, only that this is what we have designed the first release to do.
When the question came up about the recording of LUTs, it was in regard to the future functionality of programmable LUTs. I also stated that the decision had not yet been made, and that it was a current debate within Convergent Design as to how we should implement programmable LUTs.
Currently, LUTs are only used for monitoring RAW recordings. On all Convergent Design products up to this moment we have never alterred the image, but instead faithfully recorded what was output from a camera. So this is something that as a company we are deciding how best to implement.
Our point is not about limiting functionality of a product, but instead protecting the end user. We want to make sure that you do not accidentally record one way when you intended to record another way. Some argue this is an interface issue, others argue that it is a "purity of design" issue which could over-complicate the use of the device. Remember, not everyone wants to spend their time being intimate with the functions of a device like the Odyssey7Q. It is a means to an end for them and they just want it to work without having to think too much about how it is set up. We are very cognizant of this.
Programmable LUTs are a pretty great thing, but there are a lot of ways to use them and one has to be careful not to make a mistake in the use. We have many outputs possible from the LUT stage: we could apply to the OLED panel, to the exposure tools, to SDI output #1, to SDI output #2, to the HDMI output, and lastly to an internal internal recording. It can be great to make them all selectable but that's a lot of choices and it can get quickly confusing. We would hate to make a system where it could be easy to accidentally record with a LUT baked in when you intended to record a Log image. So it is something we have to design carefully.
With all that said, our initial release for 4K-to-HD recording is designed only for Slog-2. If you send a REC709 signal from the camera the colors will be messed up. That does not mean that we do not intend to make it fully functional for REC709 and other functionality in the future, only that this is what we have designed the first release to do.
Prophetmatt
Well-known member
Thank you on the 120 on one drive!!! That's awesome!!!
sunnyjimfilms
Well-known member
I can understand people making mistakes if there are a ton of different LUT options but a simple 'record LUT' function wouldn't be that confusing would it? Anyway, hopefully it's something you can consider. My main frustration along with everyone else is the firmware update, though I accept this is pretty much out of your hands. Cheers for the info as ever.
Ted Herod
Active member
Yes, I think if there were a LUT submenu after you select 4K -> PopCodec, in that same menu tree, that would be good. And once you've set that LUT in record, the monitor also shows and outputs ONLY the LUT you're recording in (if it's anything other than SLOG). This way you can be sure that when you're recording PopCodec, what you see is what you get.
Mitch Gross
Veteran
Sounds easy, but you must remember that we need to implement a procedure that will also work when using Log video from other cameras, not just RAW, and will have a repeatable workflow for every implementation. And what happens when you pick up the device again after a few days and turn it on? Do we make you select the LUT again or do we save the previous setting? Different people have different opinions.
I do agree on the idea that if you decide to record the LUT, then the ability to switch off the LUT anywhere else is locked out. Really no point in looking at a Log signal anywhere if this is not what you are recording. And if you do want the option to get to that Log signal, then you'll just have to record the LUTted image elsewhere.
This isn't a game of "if" but "how best". The idea of not doing it is really if we cannot determine a safe How Best.
I do agree on the idea that if you decide to record the LUT, then the ability to switch off the LUT anywhere else is locked out. Really no point in looking at a Log signal anywhere if this is not what you are recording. And if you do want the option to get to that Log signal, then you'll just have to record the LUTted image elsewhere.
This isn't a game of "if" but "how best". The idea of not doing it is really if we cannot determine a safe How Best.
paulcurtis
Veteran
How about
- Press the LUT button to see a list of available LUTs (the window you see now)
- Pressing a LUT name changes the display behind to show the LUT (without dismissing the window, pressing outside the window will)
- Then have some additional buttons that act like on/off checkboxes in this window 'RECORD' and 'WFM', you can turn these on and off and they choose whether you record with the LUT and/or change the exposure tools (i'm sure there's a better name than RECORD and WFM)
- The only remaining thing to do is to change the colour of the red recording strip when a LUT is being used, or at least add a label to the screen displaying the name of the LUT in operation if it's being recorded.
Is that too simplistic?
Personally i don't think i'd ever need to record with a LUT (but can see why some would) but it would be super useful to be able to upload LUTS for various display reasons. Exposure being one of them.
cheers
Paul
- Press the LUT button to see a list of available LUTs (the window you see now)
- Pressing a LUT name changes the display behind to show the LUT (without dismissing the window, pressing outside the window will)
- Then have some additional buttons that act like on/off checkboxes in this window 'RECORD' and 'WFM', you can turn these on and off and they choose whether you record with the LUT and/or change the exposure tools (i'm sure there's a better name than RECORD and WFM)
- The only remaining thing to do is to change the colour of the red recording strip when a LUT is being used, or at least add a label to the screen displaying the name of the LUT in operation if it's being recorded.
Is that too simplistic?
Personally i don't think i'd ever need to record with a LUT (but can see why some would) but it would be super useful to be able to upload LUTS for various display reasons. Exposure being one of them.
cheers
Paul
Yeah ! Getting tired of having to take the SSD out and reinserting. Mitch said that is a known problem and that it will be fixed in the update.
rejdmast
Well-known member
How about just fixing the bugs and getting 4K.
Arrrgghhhh!!! I thought that the 4K-to-HD would be REC709 - that sucks
I really don't want to have to shoot SLOG2 for most of my productions. I guess that'll be another 4-5 months then before this happens in REC709! Stuart Keasley
Well-known member
200 fps also requires two drives for RAID, anything below that can be written to a single drive