Mitch Gross
Veteran
So what's the status on LUTs? (not in relation to fs700)
Can I input and record a log signal from say c300 and output and view a LUT?
Not yet, but it is definitely something coming.
This is not particularly directed to this question, but to the participants of this thread in general:
We had a very LONG meeting with the engineers today, most of it spent with me wearing them down with the explanations of the many, many requests made on forums like this, at seminars, in phone calls and emails, and in meetings with various facilities and major clients. There's a HUGE list of things we could do, then there's the list of what we should probably do in what order, and then the realistic projections of how long certain functions might take to implement. Adding custom frame lines is a pretty small task compared to completing the work on Multi-Stream Recording, for instance. But does that mean we do what's the easy stuff first to get more features out to clients, or do we concentrate on what is most important to the largest client base? Or potential client base? These are not easy questions or answers. As vocal as members of forums such as this are, while a very important part of our client base you are not the only ones. If we have, say, a major production facility poised to purchase a large number of units but only if they have a certain feature, then we need to weigh that as well.
All of this goes to say that we have a lot of irons in the fire, a huge list of tasks we plan to accomplish, and we are constantly evaluating the order in which we attack them. Understand that this is not a monolithic endeavor. Our engineers often split tasks off to individuals or small groups so that many projects can happen simultaneously. Once completed, each task goes through a bug hunt testing phase. We really don't know the order some of these functions will be completed because they are worked on concurrently and we don't know what problems will crop up until they do. Programming like this is often a large part R&D as well.
Here's an example: It always bugged me that if there was a monitor hooked up downstream of the Odyssey7Q I couldn't use any of the image analysis tools like Focus Assist or the Waveform because it would show up on the other monitors as well. I asked if this could be fixed but the engineers misunderstood and removed it entirely from the monitor outputs, which would piss off any DIT who WANTED the display on a big monitor. So I explained that an on/off control would be ideal and the engineers agreed but didn't think they would be able to tear open that part of the code again for this release. I was dreading the fury of the userbase to discover this function had been temporarilly lostt in this firmware, but then I learned about one day before we released the new firmware that the control did in fact make it in (It's under
[*] --> [OUTPUTS] --> [MONITORING]). Seems someone had a chance to squeeze it in and make sure it didn't break anything. Of course I wanted them to change the name of the function from MONITORING to OVERLAYS, but really I was just glad it's there. And the name change will be in the first patch, already programmed.
I'm sure we are going to learn a lot more from the conversations we have during NAB. And we will constantly be looking at priorities and listening to suggestions. Many of the ideas we discussed today originated with clients, including a number from this forum.