New nanoFlash (Vr 1.5.31) / Flash XDR (1.5.25) beta firmware was posted this afternoon. Below is the long list of the enhancements / corrections. Please use with caution as this code is still in beta. Please report any bugs to cdsupport (at) convergent-design.com

Here's the long awaited list of updates, available as a free update:

Video Enhancements / Corrections
• Added Variable Frame Rate (Over/Under Crank) option. See the latest user manual for full details. In brief: one can select the base rate “_” as 24, 25, 30, 50, or 60 (this will be the recorded rate), and the crank (preserved) rate as the number of frames per second to preserve from the incoming video. (Video->Crank) Support for 720p24/25/30 (typical crank formats) is limited - see note below. Also note that audio is muted in crank mode, and that crank mode is I-Frame only.
• Added Loop Record. In this mode, the nanoFlash will record continuously from card 1, then to card 2, then back to card 1 (overwriting previous contents), then back to card 2 (again overwriting previous contents), etc till stopped. Do not use this mode unless you are willing to have older material overwritten by newer material in a record session.
• Added bit rates in SD for MXF or QT (System->File Format) recordings: 30, 40 Mbit options, in addition to the 50 Mbit option. (Video->Bit Rate->CF SD Rate)
• Added option to select width for 35 Mbit QT or MXF recordings: Video->35 Mb 1080 Width. Choices are: 1920 (for 35 Mbit 1920x1080 4:2:0 XDCAM EX) or 1440 (for 35 Mbit 1440x1080 4:2:0 XDCAM HD). This setting only applies when Video->Bit Rate->CF HD Rate is set to 35 Mbit. Bit rates of 50 Mbit and above are always 1920x1080 4:2:2 (for 1080 sources).
• Added support for 720p 24 / 25 / 30. NLE support is limited at the time of release for these video formats with our files. Final Cut Pro supports decode at all bit rates, most (if not all) PC based NLE's support these formats (as MXF files) at 35 Mbit only. Please test with your NLE first before using.
• Improvements in .MPG file playback, including file skipping bug fixed.
• Minor Improvements in HDMI signal disruption detection and recovery.
• Added support in QT mode for true frame rates (true 24, true 30, true 60).
• Repaired compatibility with the nanoFlash SDI output to a number of SDI monitors, which had been lost in version 1.1.154 .
• Fixed 720p60->24 pulldown removal.
• Added bit rate / codec display in MXF files. This will appear in the product / version fields of file metadata (which can be seen, for example, in the XDCAM Viewer software player View->Metadata option).
• Added XDCAM Optical Disk compatibility with nanoFlash SD MXF files.
• Added 80 Mbit HD bit rate option

Audio Enhancements / Corrections
• Added 8 channel audio support with 0, 2, 4, or 8 audio channel selection. (Audio->Audio Channels Recorded)
• Repaired audio / video sync in SD recordings.
• Added audio channel selection for monitoring on headphones out, audio level meters: Channels 1&2, or 3&4, or 5&6, or 7&8. (Audio->Channel Monitoring)
• Added headphone tones pattern for recording / stopping. Start record gives 2 beeps (with increasing volume), stop record gives 2 beeps (with decreasing volume).
• Fixed intermittent audio phasing bug (where the 2 channels would lose sync with respect to each other).

User Interface / Menu Enhancements
• Unit ID may now include alphabet letters. (Unit ID is used as the 1st 2 letters / digits of the file names in the recorded files).
• Added: Delete last recorded clip on currently inserted card which was last recorded to. Press and hold the Stop key, then press left arrow key, to delete last clip.
• Added Record Duration option. If used, the nanoFlash will record for the specified duration in a given record session, then stop.
• Changed remote tally flashing light behavior during record to indicate record time remaining. Tally light flashes once a second during normal record, twice a second during record with less than 5 minutes total record time remaining, 4 times per second with less than 1 minute total record time remaining.
• Changed System->Trigger-> “None” option to “Remote Play”. With this option, the Remote tally becomes a start / stop mechanism for playing, rather than recording. Press Remote button once to start play, again to pause, again to play. Press twice in succession to stop play.

Miscellaneous Updates / Corrections
• Added CuePlay. When used, press remote tally once to cue to selected timecode + 1 in the play file, press “Play” again to continue playing. Available via Remote Tally only. Additionally, set Trigger to “Remote Play” as mentioned above.
• Repaired System->Power Saving->Auto Sleep bug, in which the nanoFlash would not always wake up in the event of a renewed video input.
• Added System->Create Settings.txt, this will dump all current settings out to a file Settings.txt . This is primarily a diagnostic tool for technical support assistance as needed. ( This file should ideally only be created on a formatted blank CF card. )
• Repaired timecode bug in 720p60 / 50 during long records.
• Slot 2 card recordings will now continue on slot 2 card until the card fills up, regardless of whether a card with space is placed into slot 1. Previously, the nanoFlash always looked to slot 1 first for new recordings.
• The first 7 characters of the Volume name of the CF card are now preserved during format. (You will need to set on a PC/MAC). If you set the last 4 characters are set to 0000, then they will be auto-incremented with each format operation. (Example Name: London-0000, becomes London-0001 after the first format). This will allow you to name each card uniquely and will also keep track of the number of times the card has been formatted; helpful for determining the remaining life of the card.
• Timecode trigger will now only trigger if the timecode seen by the nanoFlash is greater than the last recorded timecode. This will help prevent small unintended clips in timecode trigger mode (System->Trigger), which were caused in the past by the camera unexpectedly moving the timecode back and forth during power up or when adjusting the camera's internal media, for example, and sending the nanoFlash into record mode briefly.
• Jam sync repaired with 1080p24 input.
• Eliminated rare “DMARd:2200” CF card communication errors.
Known issues (1.5.31) :
• 720P24 / 25 / 30 playback from the nanoFlash is not supported at this time. NLE support for these video formats is also limited – please test before using.
• Playback of MPG from nanoFlash loses audio intermittently.

Best-

• Added Loop Record. In this mode, the nanoFlash will record continuously from card 1, then to card 2, then back to card 1 (overwriting previous contents), then back to card 2 (again overwriting previous contents), etc till stopped. Do not use this mode unless you are willing to have older material overwritten by newer material in a record session.

Bad idea! This is going to cause a lot of grief for when someone forgets the option is on and loses irreplaceable footage. Please make sure we can turn it off permanently so it cannot be turned back on. Especially not by accident, or as a "practical" joke.

I know that all new features are driven from user demand but I have to wonder, which users are requesting loop record. Are people using nano for their security cameras?

this is great news. 80 mbit/sec recording and being able to use names for recording. all great stuff!

Have to agree on the sentiment on this one. Apologies to CD team that works so hard to give Everyone what they want, but this is risky for many. Don't know how to make this option harder to access or harder to change.
Reminds me of the "format card after transfer" in Shotput..... WHOA! Should be in a deep preference setting, not on main panel.

Never the less, all these changes and update are superb. Now I can nano with my SDX-900 next week and won't have to digitize. Nifty SD camera is now a file based workhorse... Love My Nano!

Bad idea! This is going to cause a lot of grief for when someone forgets the option is on and loses irreplaceable footage. Please make sure we can turn it off permanently so it cannot be turned back on. Especially not by accident, or as a "practical" joke.

Hi Adam-
When you selection loop record you will see a continuous flashing message on the LCD screen that says: Loop Record. We think this should be sufficient warning for most users.

We are planning to add user defined profiles in the near future. This PC/MAC program will allow users to define all operational values (bit-rate, crank rate, audio, etc) and to lock-out any selection from menu changes (on the nano/XDR). You can define up to 8 profiles and upload to the nano/XDR via a file on the Compact Flash card. You can also define a default profile that loads on power-up.

In truth, the nano/XDR are becoming very sophisticated recorders, with lots of program-ability / functionality. We do go to extra lengths to make sure users can not select illegal combinations in the menu. We also post warning messages on the LCD when certain modes are selected, such as, loop record and time lapse.

BTW, loop record was added for earthquake monitoring.

Best-

Loop Record message on screen should do it... and to think we doubt you guys!

Only glitch I saw (with mine) was when I used the "Storage.txt", I'm not even sure what this is for, but when I would power up the Nano, it would not recognize the G-Monster 32G card no matter which slot I put it in. If I reformatted it with the Nano it didn't seem to have any more problems with not being recognized unless I used the Storage.txt function again. It only seemed to upset the G-Monster Card. The Delkin 64G was not affected.

Also I'm hooked to the accessory D-tap of a Sony PMW350, so I don't know if there is a handshake race taking place between the SDI signal and powering/initializing the Nano when I switch the cam on.

Anyway, that's the only glitch I saw, and it seems to be okay by just avoiding using the Storage.txt function, I believe that's what it's called. It's late and I'm tired. Good night.

I think it's called settings.txt. The purpose for this is described in the manual and in Mike's post above too. It's a standardized way of getting your recorder settings to support if you need to contact support.

Dear Tom,

Thank you for your report.

We would like to know more about the "handshake race" that you described with your nanoFlash and the PMW-350 during power on of your camera.

When your wake up, and it is convenient for you, could you please provide some more detail. I will send you my phone numbers.

I didn't have time to test the new firmware thoroughly yet, so forgive me this quick question: can we record a mix of both embedded and analog audio channels? Like for instance,with the EX1 camera: 2 embedded channels, plus one analog straight to the nano?

Dear Piotr,

No, not yet.

We decided not to delay the Public Beta any longer.

This feature, "+2 Channel Audio", is close, we expect to add this fairly soon. I expect this to be in our next release.

With the 'loop record' feature, is it possible to turn off whilst still recording and still record to the end of the card it is currently on at that point in the loop.

Dear James,

I will check.

I think your suggestion is a great idea.

I will ask for this option to be added to our loop recording feature.

Waow what a big update! Nice done!

However, it seems that I have the same issue than Tom Roper. When I create the settings text file on an Extreme 32BG CF card, the message "Unknwon CF" appears. If I erease the .txt file on my Mac, the CF card is still not recognized by the NanoFlash. I have to format the card in the Nano to recover it. That's not a problem, but this "settings.txt" feature is a good idea to keep in minds the settings of a shooting with a specific camcorder for instance.
For this test, the Nano wasn't connect to any video source.

Dear Ronan,

Thank you for the confirmation of the problem.

The Settings.TXT file is intended for us to use as a diagnostic tool, so we can see exactly how the nanoFlash or Flash XDR is setup. This allows us to duplicate the exact conditions for any troubleshooting in our lab.

When creating this file, we recommend using a freshly formatted card, then after the file is saved, we recommend reformatting the card.

(I do not know why this is the way it is, we may be able to correct this later.)

Dear Dan,

Please forgive me if this comment is a little OT, but as you might remember, I also have had problems with nanoFlash recognizing the card that had anything written to it other than what formatting in the nano does.

To be more specific, I was hoping to speed up my uploads using an CF/expresscard adapter. That proved impossible, even though in the official Manual, you state:

Compact Flash Readers
1. Lexar FW-800
2. Delkin
3. PCI Express CF Readers


Perhaps now CD will look deeper into it, and get rid of incompatibility between the nano-written information (FAT, etc.) and what a computer OS might choose to write on the card the moment it's inserted?

I'd be very happy if I could use my CF/expresscard adapter, as at the moment, I'm limited to the USB speed of the CF reader supplied with my nanoFlash... And I purchased the expresscard adapter specifically for nano-recorded clips transferring to my computerm, basing on your official documentation on the compatible devices!


I am aware this is a long shot, but still... :)

Piotr

New nanoFlash (Vr 1.5.31) / Flash XDR (1.5.25) beta firmware was posted this afternoon.
• Jam sync repaired with 1080p24 input.

Best-....Hi Mike. Wow ! This is indeed a HUGE update ! Thank you and Tommy & the team at CD for all the hard work you've put into the latest public beta. I have a question regarding the Jam Sync 24p. Does this fix also cover the Canon 24 F (23.98 frame removal mode) ??

Hi Adam-

We are planning to add user defined profiles in the near future. This PC/MAC program will allow users to define all operational values (bit-rate, crank rate, audio, etc) and to lock-out any selection from menu changes (on the nano/XDR). You can define up to 8 profiles and upload to the nano/XDR via a file on the Compact Flash card. You can also define a default profile that loads on power-up.

Best-

Mike,
This idea is brilliant.
Changing setting in the camera and after in the NANO is often a complication.
To have few presets in the nano would be great.
Rafael

Dear Mark,

Thank you for the kind words.

Yes, this is a big update.

I thought we fixed all reported problems with jam sync with 24p.

Could you test your Canon 24F (23.98 frame removal mode) to see if it works for you.

Dear Piotr,

As far as I know, some are using the Sonnet ExpressCard 34 CompactFlash card readers.

Yes, we expect Mac's to write to our CompactFlash cards when the card is inserted.

We do not like it, but there is not much we can do about it, but attempt to work around it.

Could you please send me a private email with the details of your tests with our latest release, using your ExpressCard 34 card reader?

Please include lots of detail so we can investigate the problem.

I use several eFilm Express Card 34 CF adapter (the older white ones) on several Macs and they work great. I have never had a problem with the NanoFlash or any other CF device.

I use 10.6.2 on a couple MBP 2009's.

The shots below show the invisible files my macs put on the cards. They don't seem to cause any problems for me. I do reformat cards in the NF every time after transferring. Am I just lucky?

Olof,

I wouldn't say you are "just lucky", as most expresscard CF readers should work; I'd say it was me who was NOT lucky buying mine :)

Dan,

Thanks again for your helpfulness; of course I'll write an email to you with all details - in the meantime, here is the thread where we had discussed it already:

http://www.dvinfo.net/forum/convergent-design-nanoflash/469062-got-my-nanoflash-question-pcie-adapter-cf.html

Cheers

Piotr

Now that's a firmware update !! Loop Record and Multi-Channel audio !

For Loop Record, I'd like to use it as an extension of the PreBuffer Record with a user-defined file length in seconds. For wildlife videos, I usually need an additional 15-30 seconds of video before I hit the record button. I suppose this could be implemented as a "ping-pong" record to two different files with an incrementing file name, deleting the first when two have completed. Pressing the Record button on your source camera or the Nanoflash would stop the recording. I recall Dan Keaton's comments on the restrictions of file creation at the higher bitrates.

Great firmware updates CD!
Will there be a Date and Time stamp Burn-In feature added soon?

Dear Trell,

I am sorry, but we do not have the ability to add Date and Time code burn-in to the image area.

The Date and time code are assoicated with the file, but not as a burned-in image.

I looked up those files and found an article quoted here with link under that:

.Trashes, .fseventsd, and .Spotlight-V100

Merely plugging a removable drive into a mac (when it has write access) makes OS/X think it can take the liberty to write a lot of hidden garbage onto that disk. If you want to stop this from happening, you have to put some special files on that disk before you plug it in.

To stop OS/X from doing Spotlight indexing, you need a file called .metadata_never_index in the root directory of the removable drive.

To stop OS/X from making a .Trashes directory, you need to make your own file that *isn’t* a directory and call it .Trashes

To keep it from doing logging of filesystem events on the drive, you need to make a directory called .fseventsd and inside that folder put a single file named no_log

The contents of these files don’t matter, so you can make them empty files using touch. Even better, you could make it a text file with a link to this post, so that you (or someone else) wandering across the files will know what they’re for.

Apple’s choice to do this is incredibly self-serving and shameful. At bare minimum, hidden files and features like these should be off by default for any non-mac-only filesystem formats. They should only be enabled when the user has been made aware of them.
----------end quote----------------
from: .Trashes, .fseventsd, and .Spotlight-V100 (http://hostilefork.com/2009/12/02/trashes-fseventsd-and-spotlight-v100/)
-----------------------------------------------------------------------------------------------
So we are not alone here and this article if correct suggests some ways to prevent some card add-ons. I hate to be the first one that suggests adding these blocking files to the format routine in a future firmware release. I will look into this more, maybe there is a way to prevent these unwanted card writes.

------------------------------------
I use several eFilm Express Card 34 CF adapter (the older white ones) on several Macs and they work great. I have never had a problem with the NanoFlash or any other CF device.

I use 10.6.2 on a couple MBP 2009's.

The shots below show the invisible files my macs put on the cards. They don't seem to cause any problems for me. I do reformat cards in the NF every time after transferring. Am I just lucky?

Should we bump this topic to a new thread since it does not pertain to the firmware release?

Also it may be problems if these hidden files are not written? They are designed for system stability at first glance, but I leave that for greater computer minds.

Dear George,

Thank you for providing this very valuable information.

At first glance, it certainly seems reasonable for us to add these files when we format the CompactFlash card.

In the meantime, we recommend:

Before using a CompactFlash card for the first time, format it in the nanoFlashs or Flash XDR. We made the format process very fast so this is really painless. It just takes us about 2.5 seconds per card to perform the format.

Record your files.

Upload your files to one, preferably more than one, other storage system, such as a Nexto or laptop or other computer system.

Reformat the card, in the nanoFlash or Flash XDR, prior to using the card again. (I prefer doing this at the start of the shooting day.)

These days, with 64 GB cards being relatively economical, it certainly is feasible to have a full days worth of cards available on hand.

We are having great results with the Delkin 64 GB card. While this card is currently limited to 220 Mbps speed at this time, we hope to increase this card's performance to 280 Mbps in the future. (This is not a guarranty, just one of our goals and this is in our plan.)