07Q Firmware v2.10.141

I found some strange thing while testing 2k RAW Slow-mo mode (200fps) today. It looks like a bug.
Can somebody tell what could it be?
I never met such issues before with using FS700 in a regular buffer-mode.
 
I found some strange thing while testing 2k RAW Slow-mo mode (200fps) today. It looks like a bug.
Can somebody tell what could it be?
I never met such issues before with using FS700 in a regular buffer-mode.
What was your software workflow? I think I ran into an issue like this with some fireworks I shot when running it through Adobe Camera RAW, if I remember correctly.
 
Gentlemen,

I am alerting the engineers to these reports.

I need to point out that I participate on forums such as this to help with information and understanding of the use of our products. But I am not a service technician and I am not the technical support system. We have a system in place and it can be accessed via our website. It is important that whenever you experience an issue that you report it via this system. This way we have proper tracking of all issues and can report back to the client as well as ask for additional information in diagnosing the issue. Feel free to post here but please also use our support desk.

As far as throwing any attitude my way, it will neither help nor hinder the solving of any issues. I am not the one who programs the code.
 
As far as throwing any attitude my way, it will neither help nor hinder the solving of any issues. I am not the one who programs the code.
I respect that and I'm sorry that some users take out their frustrations on you. You just happen to be CD's public face here and thus unfortunately get to be the one who everyone vents to, as unfair as it is.
 
Come on, Mitch is an experienced Marketing & Sales professional, he does not need any Puppies Protection.

There is disappointment in July 2014, as we miss some of the key recording functions, that were promissed in April 2013. There should be consent about CD being late. You might ignore it. More important for me, CD is aware of this delay. And they will work hard to deliver. As soon, as customers receive a stable Firmware Release with those missing options, there will be happiness and joy. That might still be a while away, as we have three major steps: 1080p50/60 ProRes 422, 2160p24/25/30 ProRes 422 and 2160p50/60 ProRes 422.

Until this challenge is accomplished, users will continue to call for their features. You will like it or not - that's part of the business.
 
2160p would be a perfect 4K on my device.
CD may feel free to swap the row and deliver 2160p24/25/30 ProRes 422 first, of course.
:)
 
Hi Mitch,

I have now alerted support as per your suggestion. I have always appreciated Dan (way back to the nanoflash days) and yourself being so open, available and helping us out. You are also an experienced cameraman, who uses this device, your feedback of the issues is often more insightful than technical support. I asked the question here to see what others have to say, as I can't believe I'm having these issues none of which match the firmware support notes. Others have the same issue, I would not neccessarily get that confirmation from support.

One note from my shoot today, which was 4K2HD, no playback issues. They appear to be an issue with Raw record for me, not prores.

thanks- Tim.
 
One note from my shoot today, which was 4K2HD, no playback issues. They appear to be an issue with Raw record for me, not prores.

That makes sense to me - I've not seen any playback issues yet but have mostly been shooting and testing in 4K2HD. I don't often shoot RAW and have only briefly tested the 4K 100/120fps burst mode.
 
For me the glitches were present trying to play back the recently shot clip. No mixing of 2K or 4K. I didn't have any playback issues on the previous version. So for me this is an infinitely worse scenario.
Trying to be confident on set that a clip doesn't have an record issue, isn't something I want to be worried about mid shoot. Constantly reasurring the director that it's only playback, when Im not 100% sure. On every job. Playback needs to be stable. Especially with 4K/2K as it isn't eactly like you can pop the SSD into a computer to verify the files ok.
Ticking and unticking differents clips isn't a fix for me either. Especially when the units goes dead.
Thanks for the tips guys, hoping we can get this addressed as a fix asap.
I'd love to hear from CD.

The new playback controls are a new feature. It's not surprising if they're a little buggy - these will, in all likelihood, be corrected in the next firmware. If you need more stable firmware, go back to the previous one (which is on the website). I had no issues during playback with that. Given the constant complaints about firmware delays I'm really not surprised CD released a firmware with much improved, albeit slightly glitchy, playback features - as long as there are no reported bugs in the final footage (at which point I think they either delay release to fix it, or issue a warning). Honestly, if directors are concerned about buggy firmware they must be pretty green since this has been par for the course since the Red One - if you want solid as a rock firmware, hire an Alexa.
 
I found some strange thing while testing 2k RAW Slow-mo mode (200fps) today. It looks like a bug.
Can somebody tell what could it be?
I never met such issues before with using FS700 in a regular buffer-mode.

That's really odd. I don't see why line skipping would create that - it's a kind of bleed into the neighbouring sensors. Could we have a look at an original DNG from it - there's a chance it' a decoding error with the workflow you've chosen. Were you also recording to the SDHD card, is there anything on that?

cheers
Paul
 
I found some strange thing while testing 2k RAW Slow-mo mode (200fps) today. It looks like a bug.
Can somebody tell what could it be?
I never met such issues before with using FS700 in a regular buffer-mode.

I haven't had this specific error, but I will say more so than any other mode, I've had way more artifacting and just general weirdness with 240fps in AVCHD. I haven't shot a ton of 240fps with the 7Q yet, but internal codec there's regularly something off and I think that's just part of super high frame rates.
 
That's really odd. I don't see why line skipping would create that - it's a kind of bleed into the neighbouring sensors. Could we have a look at an original DNG from it - there's a chance it' a decoding error with the workflow you've chosen. Were you also recording to the SDHD card, is there anything on that?
Paul
Unfortunately this bug comes from DNG:
https://www.dropbox.com/s/nxui25kh8b4187u/CLIP0000127_0000130.dng
So it's not a software issue - this is directly Odyssey's or FS700's issue.

I can't check it doubling on SD card, because it was SlowMo - as you know, in this mode there is no possibility to record both to SDcard (buffered) and to an external recorder. It was my first test of the Odyssey and all the clips, where was strong light, had the same bad things on the edges. Tomorrow I will try to catch this bug again and will also record to SDcard for comparison.
I'm so confused now. I used FS700 for a year before I bought Odyssey and never met such problems as above.
 
I was shooting this with October 2013 Firmware in 2K RAW and I had several of the artefacts
it's changing from frame to frame, that's why I was guessing it's sensor fault cause by line skipping

2KRAW_artefakte.jpg
 
Mitch, is it going to be compressed 4K (ProRes) or compressed 4K raw that 7Q will get with the next update?

Just a little off topic:
Are there any CD plans to release recorder that will have all of the 7Q features (or most of them) but without screen (or very, very small, with basic information)? Something like HyperDeck Shuttle/Ninja Star on steroids, that would take (dual) SSD's, Cfast, SxS, SD UHS II cards? That would be great ultimate run n gun option for C500, FS700 and I think a lot of people would be interested.
 
Let's eliminate the usual suspects...

1. No filter on the lens?
2. What lens?
3. Did you shoot some footage at other speeds that didn't have this issue?
4. Is your sensor clean?

The overlap on the left doesn't look like bleed out from overloaded pixels. It looks like a dirty filter/sensor to me. A small mark on a filter from your finger or similar can cause the light to streak like this. Especially if your are at the telephoto range, a single spec of dirty/dust/oil can do this.

On the right looks like a codec issue. However it took can simply be struggling with the subsampling of the 4K sensor down to 2K.

I find the 2K output from the camera to be lacking. It's never as good as downsampling 4K in post.
 
Some notes:

Many of the issues being brought up are in fact noted in the Release Notes to the new firmware.

Feel free to post issues here to discuss with the community. But to report properly to Cnvergent Design, please use our website.

We are working on compressed 4K video. This means the 4K RAW signal is deBayered and turned into a high quality 4K video signal, and then this is compressed for recording.

We will not discuss future products in this forum before announcing them at their proper time and place. We often but not always take advantage of the scheduling of major equipment trade shows to make such announcements.

Any personal attacks on me or singing of my praises will not alter the course for firmware development. But I will certainly remember you.
 
Back
Top