FS7: Issues I've noticed with the FS7 this far, questions you may have the answer to!

I'll keep an eye on what I'm doing and if it locks up again, can hopefully find the combination of actions that led to it.

I'm testing a Rokinon F2.0 12mm prime lens today. Now I'm beginning to get a taste of what 2000 ISO can do. 12mm is wide enough on this camera.

I have an F .95 35mm prime on order too. 2-4 weeks delivery time.

The Rokinon was cheap, is not clickless and the focus is logrithmic and takes practice to find where 10' 20' 60' and so on are on the lens barrel, between markings. Going to load up the footage in the NLE to view on the 4K monitor...
 
Doug Jensen said:
You can definitely mix all frame rates and codecs on a card.
Click to expand...

Will that cause a problem for ShotPut Pro?

I recently mixed codecs on a card and when I went to transfer ShotPut Pro informed that it couldn't complete the transfer.

Just making sure here- It is NOT possible to shoot slo-motion when in MPEG422, correct? ( S&Q is non-operative when in MPEG422 ).
 
corycross said:
I have looked at others whom have posted the same issues but after following their answers, I was still not able to see waveform.
Click to expand...

What did you find out about the waveform monitor from Sony? There are cases where the screen says, "Cannot Proceed" when trying to turn it on. That I understandable and can be fixed. What is broken is when it is appearing and then, without making any settings changes at all, it will just stop working after power cycling the camera. It doesn't complain or say "Cannot Proceed", it just doesn't appear.

The only fix for this is to either reset the entire camera -OR- restore all of the settings again.
 
Waveforms cannot be displayed when HDMI is outputting any of the 4K resolutions, and/or when a LUT is applied.
They work only if the SDI is operating and 1080P is output and no LUT applied to the monitor. A rather unfortunate limitation, but hardware-based.
 
This camera sure is quirky. I was using it with the Shogun earlier to record something and powered everything off. This evening, I turn both the FS7 and the Shogun on, but the FS7 refuses to output signal on either the HDMI or the SDI ports. I tried changing the output format several times, tried toggling to SDI, tried power cycling the Shogun... nothing would produce picture on the Shogun.
Finally, I power cycled the FS7 and the HDMI port came back to life.

Sony has some bugs to work out of this camera still. In the meantime, I recommend extra setup time to work through these unexpected behaviors. This camera is not 100% reliable.
 
Was trying to make the waveform appear on the VF, but darned if I can figure it out..

I turned off MLUT (didn't make any difference in the VF unless a LUT other than S-Log was selected) and I set the output format to 1080 on the SDI port. That stopped the 'cannot proceed' messages when I press the assigned button for waveform to appear, but nothing happens.

And what's going on with the MLUTs? It seem like one cannot turn off the S-Log 2 LUT when in S-Log 2 mode in Cine EI. I can select REC709 and others, and toggle the MLUT on/off and see the change in the VF, but setting to S-Log makes the display darker, but it stays darker when MLUT is set to OFF. It gets brighter in the midtones and shadows when other LUTs are selected. But the S-Log should look washed out, as it does on my Shogun and in the editor without a LUT applied or without grading.

Very counter intuitive!
 
basspig said:
Was trying to make the waveform appear on the VF, but darned if I can figure it out..

I turned off MLUT (didn't make any difference in the VF unless a LUT other than S-Log was selected) and I set the output format to 1080 on the SDI port. That stopped the 'cannot proceed' messages when I press the assigned button for waveform to appear, but nothing happens.
Click to expand...

I believe that when you have everything set to the way it is supposed to be to get the waveforms to appear then it no longer says "cannot proceed" on the display when you try to turn them on. They just don't appear.

They only way that I have been able to get them to appear is to reset all settings. Set everything up the way I want it including turning on the waveforms (which appear now). Then, I save ALL SETTINGS to the SD card. Then when the waveforms decide that they don't want to appear anymore I can restore ALL SETTING from the SD card and then they work again.

And...there is definitely a bug somewhere because I can run with waveforms and NEVER make any changes to the settings and eventually they won't appear anymore after turning on the camera. Very frustrating. This is a bug.

Plus, now hard could it be to display the reasons why the camera 'cannot proceed'? For every setting or display that you want to use that causes 'cannot proceed' to appear, couldn't they just tell you the offending setting? Seriously.
 
ohtheview said:
I believe that when you have everything set to the way it is supposed to be to get the waveforms to appear then it no longer says "cannot proceed" on the display when you try to turn them on. They just don't appear.

They only way that I have been able to get them to appear is to reset all settings. Set everything up the way I want it including turning on the waveforms (which appear now). Then, I save ALL SETTINGS to the SD card. Then when the waveforms decide that they don't want to appear anymore I can restore ALL SETTING from the SD card and then they work again.

And...there is definitely a bug somewhere because I can run with waveforms and NEVER make any changes to the settings and eventually they won't appear anymore after turning on the camera. Very frustrating. This is a bug.

Plus, now hard could it be to display the reasons why the camera 'cannot proceed'? For every setting or display that you want to use that causes 'cannot proceed' to appear, couldn't they just tell you the offending setting? Seriously.
Click to expand...
And all they have to do is to make it consistent and give some clear text explaining what you have to do, not just simple "cannot proceed" :/ That is like 2 days of programming for one person (latter part).

One more thing: Sony, please. Repair all the quirks, give as NR in Cine EI, center scan and maybe one more thing extra ;) and we will be extremely happy owners!
 
Last edited:
Are they ever going to fix the magnification button to move around the image? This is completely unacceptable for a company like Sony to keep doing this with their cameras.. After the FS100/ 700 took a while to get the firmware to do that... and the FS7 they didn't learn that its best just to keep that possibility in there?
 
So it's a bug.. and this is firmware 2.0.

I did notice that when I switched to 1080P so that I could enable 180FPS overcrank, the scope mysteriously appeared.

Thankfully, I have a good scope on the Shogun, else I'd be guessing a lot about exposure.
 
Hello

I am struggling as well with the WFM. Of course I have it when Mluts are all on or off, and sdi is ON. But when I set the hdmi out to 1080p, the waveform disapears. I'm shooting 4K DCI, cineEI, Slog3.
I read you should be on 1080i, but there is no such possibility.
Is it the typical behaviour ? Is there a way to shoot 4K DCI and have hdmi turned on with the wfm ?

edit : I just discovered that mlut does not work for hdmi ourput. No matter if I turn SDI2/HDMI Mlut on or off. BUT if I turn SDI1/Internal ON, it changes the hdmi output and applies the LUT. Should I reset the cmera ?
Thank you
 
Last edited:
I did some shooting with the MPEG422 CODEC last night, and noticed that the scopes (which had not appeared for much of the week) were magically there again.
This issue needs to be worked on. I'd like to have them internally, because I won't (hopefully) always have to run & gun with Shogun recorder on the hotshoe. There are too many iterations of possible configurations that don't allow WFM to appear, and I, too, haven't found a reliable process for getting them back on. All week, I didn't get the 'cannot proceed' error when I pressed the assigned button for WFM, but I didn't get the WFM either. Now when I switch CODECs, it's working again. Sure feels like a bug in the operating firmware.
 
You must log in or register to reply here.
Back
Top