View Full Version : nanoFlash Firmware 1.6.29


Dan Keaton
July 7th, 2010, 11:57 AM
This thread is intended for discussions of nanoFlash Firmware 1.6.29.

We will report here any problems that we find with 1.6.29, and we invite others, if they detect any problem with 1.6.29, to post here also.

So far, we have found no major problems with 1.6.29, which was posted on July 29, 2010.

I was asked today, if MPG, specifically in SD, works. Yes it does.

Since 1.6.29 was released, we found the following small bugs in the firmware.
All of these bugs have been found and fixed, and will be incorported in our next release.

In 720p, with pulldown removal active, the timecode was getting doubled in this mode.

In SD, there is a bug in setting SD aspect ratio.

And we just fixed LTC timecode, (Linear Timecode, external timecode input), to be more accurate.

No major problems, so far have surfaced with 1.6.29.

I will attempt to report any other problems that we find.

George Griswold
July 7th, 2010, 01:00 PM
Can I set the aspect ratio to 16X9 reliably? I use SDX-900 camera and simultaneously record SD on Nano. What is the bug with the menu item?

Dan Keaton
July 7th, 2010, 01:41 PM
Dear George,

I will provide more information shortly. Our engineers are in a meeting.

Dan Keaton
July 7th, 2010, 03:57 PM
Can I set the aspect ratio to 16X9 reliably? I use SDX-900 camera and simultaneously record SD on Nano. What is the bug with the menu item?

Dear George,

When you set the 16x9 option in the nanoFlash menu, in 1.6.29, and most likely earlier firmware releases, we do not properly set the 16x9 bit in the file header.

The video is recorded properly, the header just reports the video as 4x3.

Please feel free to run a test to see if this affects you.

George Griswold
July 7th, 2010, 06:25 PM
Should not be a problem, just check anamorphic in FCP and it would be OK. I will test before next SDX shoot on Tuesday. All oil spill now in New Orleans, all the time. George

Gints Klimanis
July 7th, 2010, 07:55 PM
I've upgraded to the new Firmware, but I haven't used it yet. For 1.5.249, I'm seeing Nano clip start 10-13 frames after the EX1 clip for I-Frame Only at 280 MBps for 1080p30. The Nano also has an extra 12-14 frames appended to the end of the file. Is it possible to make the number of leading and trailing frames for the Nano is consistent when the Recording "PreBuffer" is not used? If so, I'd like a programmable parameter (units=frames) to reduce or eliminate it.

Dan Keaton
July 8th, 2010, 06:09 AM
Dear Gints,

We are making improvements in this area.

We are currently testing a new way to start the recording process, which is significantly faster.

We have this implemented, it just has to go through our testing process before we release it.

This was added after 1.6.29, but you may see some improvements in 1.6.29.

Gints Klimanis
July 8th, 2010, 11:31 AM
Thanks, Dan. An extra 10-15 frames at the end would be useful for takes that were inadvertently cut off. In run-n-gun, I have longed for extra time at the end of a clip. If it is possible to open a parameter for "post-buffer length", I'd like that. I would hate to see this capability disappear completely even though the additional frames (currently the number seems inconsistent) may complicate some editing situations.

Dan Keaton
July 8th, 2010, 11:48 AM
Dear Gints,

That is a very nice idea.

I would recommend that the parameter (menu item) would be in seconds.

As always, things get complicated.

I would imagine, that if the record button or timecode started rolling again, during the "extra time", then we would not stop recording, but close one file and start another.

I think this would be a very nice feature for some.

Standard Disclaimer: As most everyone knows, we are very busy.

Gints Klimanis
July 8th, 2010, 12:11 PM
Dan, that's a good description of what I'm looking for.

George Griswold
July 12th, 2010, 08:01 PM
Please don't turn the NanoFlash into another computer product with so many check boxes that it becomes unwieldy and unreliable. If someone wants to roll longer, then simply delay pressing the roll button to cut the take. Please, please don't add too many more features. Maybe we should have forum votes for any more "upgrades" in the menu.

Ronald Jackson
July 12th, 2010, 10:29 PM
I second George's plea above. Please keep it simple. Just make sure that what the nano is supposed to do it does do as efficiently as possible but don't change it.

I would like to see more by way of a manual, e.g. " A step by step guide to using the nanoFlash with Final Cut Pro".

Ron

Dan Keaton
July 13th, 2010, 05:24 AM
Dear George,

We are very much concerned with feature bloat. We want to keep our menus as simple as possible.

However, this is one of those features that is fairly simple in implement and could be buried near the bottom of a menu. We will listen to more comments before we implement this.

Dear Ronald,

It is difficult for us to produce a manual for Final Cut Pro, even if it just applies to using our footage.

A Final Cut Pro expert, maybe someone on this forum, could produce a concise Step by Step guide.

But, it is like cooking, there are many ways or methods to get to the final result.

Robin Probyn
July 13th, 2010, 09:06 AM
Please don't turn the NanoFlash into another computer product with so many check boxes that it becomes unwieldy and unreliable. If someone wants to roll longer, then simply delay pressing the roll button to cut the take. Please, please don't add too many more features. Maybe we should have forum votes for any more "upgrades" in the menu.

Totally agree.. and have mentioned it before.. its just going to be unending with so any people wanting this and that.. keep to the basic,s... its not an editing add on.. its for recording from a camera.. lest get that air tight first..

Lance Librandi
July 13th, 2010, 09:08 AM
Hello Dan,
Where features are concerned CD must move with market demands and this will lead other features having to be added. Perhaps the time is approaching where the use of profiles may be a better option than a set menu, this way you can make the device as simply or as complex as you want.

Dan Keaton
July 13th, 2010, 09:26 AM
Dear Lance,

We are working on profiles.

We think this will be a wonderful feature as one can rapidly switch from one set of options to another, as the conditions, or shooting conditions dictate,

For example, one could have a profile for over or under-cranking, one for time-lapse, one for 24p (or 23.976), etc.

Or one for Avid, one for Final Cut Pro.

Luben Izov
July 13th, 2010, 09:46 AM
Dear Lance,

We are working on profiles.

We think this will be a wonderful feature as one can rapidly switch from one set of options to another, as the conditions, or shooting conditions dictate,

For example, one could have a profile for over or under-cranking, one for time-lapse, one for 24p (or 23.976), etc.

Or one for Avid, one for Final Cut Pro.

Thank you Dan!
That's a great idea and I welcome it very much. Set it ones and move from/to as need it. Awesome....

John Richard
July 15th, 2010, 08:20 AM
Dan - this idea of "Profiles" is an excellent idea!
Now that the nano and XDR are so feature packed, it is easy to miss something in the heat of the production mode.

The ability to use Profiles would be greatly welcomed!

Ronald Jackson
July 15th, 2010, 09:19 AM
Is the recommendation then to go and instal this new Firmware? Is it "necessary", "essential", "optional" w.h.y.?

Ron

Andrew Stone
July 15th, 2010, 10:24 AM
Dear Lance,

We are working on profiles.

We think this will be a wonderful feature as one can rapidly switch from one set of options to another,

Capital idea Dan. A thought... it might be useful from a "field" perspective to have a very strong indicator that the camera is not set up right to invoke all of the parameters of a particular profile. Something like the LCD display light flashing 3 times in relatively quick succession could be used with a second option being the lettering on the display flashing. Some may not want the display light blinking if they are in an darkened theater with an audience around.

Dan Keaton
July 15th, 2010, 10:50 AM
Is the recommendation then to go and instal this new Firmware? Is it "necessary", "essential", "optional" w.h.y.?

Ron

Dear Ron,

We are highly recommending that everyone upgrade to 1.6.29.

This release is the culmination of great efforts to increase the reliability of the nanoFlash.

Dean Harrington
July 15th, 2010, 05:33 PM
Dear Lance,

We are working on profiles.

We think this will be a wonderful feature as one can rapidly switch from one set of options to another, as the conditions, or shooting conditions dictate,

For example, one could have a profile for over or under-cranking, one for time-lapse, one for 24p (or 23.976), etc.

Or one for Avid, one for Final Cut Pro.

Love this idea ... certainly would make things easier!

Cees van Kempen
August 6th, 2010, 06:19 AM
Dear Dan,

Noticed that the Auto Sleep function is disabled in the last firmware. The manual says this is temporarilly. When is it expected to be fixed?
Going on an expedition with no excess to power sources for charging batteries, so any battery energy is very precious. Thus is the Auto Sleep function. Any advice on to what firmware to downgrade to solve this problem?

Cees

Dan Keaton
August 6th, 2010, 06:24 AM
Dear Cees,

We want to re-enable this just as soon as possible.

This has been a very elusive bug for us.

In our testing, the nanoFlash, with the Power Save enabled, fails to properly come out of Power Save mode, about 1 out of every 250 times. While this is relatively rare, we just do not want this to ruin someone's shoot.

Cees van Kempen
August 6th, 2010, 06:34 AM
Is it 1 out of every 250 shots or 1 out of every 250 nanoflashes? I had no problems with it with the former firmware and it is very important for me to safe every amp of power in the african interior. Do you expect it will be fixed within about 5 weeks? If not, what firmware release do you advise?

Dan Keaton
August 6th, 2010, 06:56 AM
Dear Cees,

It is appproximately one out of every 250 times for each nanoFlash.

This is some obsure timing issue.

We highly recommend using 1.6.29 (or a higher version) as numerous issues were corrected in this release. Our previous releases allow you to use Power Save.

Yes, we hope to have this fixed in five weeks. But, we have to find this elusive problem first.

Julio Veas P.
August 7th, 2010, 08:11 AM
Dear Dan:

Since We don`t have the auto power off function, and the problem is not isoleted yet, is it posible to assign a combination of keystrokes to send it to low power mode and bring it back as needed, meanwhile the next firmware corrects the problem, (Just a suggestion - Question).

greetings
Julio Veas
Valdivia - Chile

Dan Keaton
August 7th, 2010, 09:39 AM
Dear Julio,

We considered that, but in our analysis, it would not help.

The problem occurs when we come out of "Power Save".

It is not obvious that the nanoFlash did not come out of "Power Save" properly, thus you could come out of "Power Save" and not be able to record successfully.

The alternative at this time is to just remove power from the nanoFlash, then reapply it when you are ready. Since the settings are saved, and since the nanoFlash powers up quickly, this procedure may be acceptable, at this time, for some, but not for others.

Note: The currently disabled "Power Save" feature worked by sensing that the HD-SDI signal was missing, thus one had to turn off the camera to go into "Power Save".

With it disabled, one has to turn off the camera and then remove power from the nanoFlash.

We definitely want to fix this as soon as possible since "Power Save" is such a nice feature, but it has to work perfectly to be useful.

Bruce Schultz
August 8th, 2010, 03:25 PM
Gee guys, I'm all for Feature Bloat! Dan and the C-D crew, please keep piling on more and more features that make the Nano Flash one of the truly amazing and versatile HD recorders in the world today. I for one am not having any problems navigating the Nano Flash menus as much as say the menus for a Sony F35 or Arri Alexa cameras.

Cees van Kempen
August 14th, 2010, 03:04 AM
Dear Dan,

You mentioned you are working on profiles. Please do not only include video settings, but also system settings to be set in the profile. I like to be able to switch between profile with LongGop 100Mb/s @ 25P to I-Fo higher bit rates @ 60P as easy as possible (for the purpose of slomo with sound). This requires change of settings in both video and system menu.

Please also keep us informed about restoring the Auto Save option. I desperately need it.

Dan Keaton
August 14th, 2010, 08:51 AM
Dear Cees,

Yes, our profiles will allow one to set all of the settings, just as you would manually in the menu system.

Yes, I will keep you informed of restoring the "Power Save" feature.

Ernie Santella
August 14th, 2010, 07:41 PM
I'm also in need of the Power Save function. That is a must have for me. I'm getting nervous about cable reliability having to plug-unplug all day.

Cees van Kempen
August 15th, 2010, 03:50 AM
I fully agree with Ernie. Spoiled a wonderful shot last week, because I hurried to get my camera on and forgot the power cable of the nano. I am going on an expedition in October and if the option is not restored I will definitely chose for an older firmware, with the auto save option. This is a serious problem for me, on an overall fantastic and very, very valuable device.

Cees van Kempen
September 12th, 2010, 01:14 PM
Dear Cees,

Yes, our profiles will allow one to set all of the settings, just as you would manually in the menu system.

Yes, I will keep you informed of restoring the "Power Save" feature.

Dear Dan,

Any news on the Autosave function? Going on a trip into the African interior next month and desparetly need the autosave option. I am also vey curious about progress on profile settings.

Dan Keaton
September 12th, 2010, 01:32 PM
Dear Cees,

I do not yet have any positive news about the autosave function.

Our engineers have been working on nano3D, the next nanoFlash release, which is currently in quality control testing, and two other projects that we have not announced yet. Both of these projects came up unexpectedly and delayed us find the problem coming out of power-save mode and finishing profiles.

The nano3D is in very good shape at this time.

I will send you a private email.