Odyssey7 & Odyssey7Q Status Update

hmmm....while the 7Q has a processor and buffer memory for, seemingly, everything, to use whatever resources are available for a VERY limited application, seems to me to be counter-indicated. Whatever correction is applied will reduce the final image resolution. This is a lose-lose product from Sony.
 
Does anybody know a fix for this problem / can't believe it's a defect: Every time I turn the O7Q on, it starts to re-read the SSD1 twice and then asked to re-insert it. After that all is ok until the next time I turn it on. Only SSD1. Swapped them out... same. (Of course I power down the unit off properly)
 
Hi again Mitch, thanks as always for your reply's. Always much appreciated.
I think the crop mode something that you should look into a little more, as I believe more camera's in the future will offer this function. It is something I would pay extra for.
Unfortunately post is not really a viable option in most cases. Especially run and gun and broadcast.
There is a serious shortage of affordable super35 zoom lenses out there that are actually usable. Look at the disappointment that occured with the recent Sony 18-105 'pillow lens'.
As a camo who moved on from Digibeta and XDCam, the broadcast zoom is the thing I miss most. That and the handgrip they offer:)
On an FS700 (or any other future camera's the 7Q supports) a centre crop option with all the 4K sensors that are around, opens up a world of B4 and Super16 lens option.
WHich is essentially recycling. Which is good for the budget and the planet.

Any other takers?

cheers - Tim.

I'm not against it, but really this is something that should be a part of the camera's operation, not the Odyssey's. We would have to dismantle the signal to extract a given resolution crop, and then rebuild the frames in a new structure, all on the fly. Don't forget that it would seriously mess with any RAW deBayering, as the pixels around the edges would be looking for samples that were no longer there (edge sampling for deBayer is a separate function in the algorithms). That's a lot of computation.

Remember, there is no need to do this on the fly if your camera will not. Put up a frame line and do it in post. Not as sexy on set but much more realistic an option.
 
The 7Q could probably correct the pillow distortion on the new Sony lens. It seems to be able to do everything else. Mitch?!
Not gonna happen.

There's a whole lotta telemetry from the lens that would need to be sent through metadata so that we knew what to do, and then there's a bunch of information from Sony on the geometry that we'd need to convince them to share with us. And then we'd have to program it all.

The telemetry isn't sent through, so we have no idea where to start (the geometry changes through the adjustments to the lens). So that's a no-go from the start.

Sony is very unlikely to be willing to share this proprietary info even if we had a way to access the data.

Do you really want us to drop all the other features we're promising to work on this one?

I know it was posted as kind of a joke, but I figured it would be instructive to share the realities of why it couldn't happen.
 
Does anybody know a fix for this problem / can't believe it's a defect: Every time I turn the O7Q on, it starts to re-read the SSD1 twice and then asked to re-insert it. After that all is ok until the next time I turn it on. Only SSD1. Swapped them out... same. (Of course I power down the unit off properly)

A known issue which will be addressed in our next firmware update.
 
Not gonna happen.

There's a whole lotta telemetry from the lens that would need to be sent through metadata so that we knew what to do, and then there's a bunch of information from Sony on the geometry that we'd need to convince them to share with us. And then we'd have to program it all.

The telemetry isn't sent through, so we have no idea where to start (the geometry changes through the adjustments to the lens). So that's a no-go from the start.

Sony is very unlikely to be willing to share this proprietary info even if we had a way to access the data.

Do you really want us to drop all the other features we're promising to work on this one?

I know it was posted as kind of a joke, but I figured it would be instructive to share the realities of why it couldn't happen.
Yes it was a joke in the 'does it make coffee' vein. The lens is of no real interest to me and yes, I'm far more interested in a fully functioning 7Q, which I will be purchasing as soon as it is available and has the features I require.
 
The way things are going, I would not plan on anything until it is released. I have money set aside for a 7Q but I'm not buying one until I see the vaporware turn into reality.
 
well, everybody has to make his own decisions. I for myself see 2K RAW as convincing enough to go for it now and also I have faith enough into C-D's professional skill and experience to get things running as planned. If 4K is your main goal than off course it makes sense to wait.
 
Mitch, what is the status of the LUTs on the 7q? Can I load in something from Davinci and have it shown in the sdi outputs but have the waveform show pre-lut if wanted?
 
Mitch, what is the status of the LUTs on the 7q? Can I load in something from Davinci and have it shown in the sdi outputs but have the waveform show pre-lut if wanted?
Custom LUTs and addressable outputs are coming, but are not currently implemented.
 
I don't have anything solid that can be shared. Things are moving forward but not yet at a stage that can be made public. We had a meeting yesterday where it was agreed that we need to publish a new firmware forecast, but we have to evaluate a few things before we can do that.

I'll get y'all something as soon as I can.
 
Back
Top