Hi Dan

just wondered if you are going to bring out any firmware upgrades for the nano in the near future

As there seems to be alot of new boys on the block now ninja samuri ect

Dear Ian,

Yes, we are working on a new firmware release.

There will be multiple new features.

Here are two:

1. Ability to extract timecode from the HDMI Input for the Sony FS100 and FS700 cameras.

2. The ability to detect the HD-SDI Record Packet.

Certain cameras, such as the Sony F3, Canon C300 and other cameras put out a signal in the HD-SDI steam that indicates every time the camera record button is pressed.

We will detect that signal and start/stop the nanoFlash accordingly.

This is a great new feature as one can use continuously running timecode as opposed to using Record Run timecode to start the nanoFlash.

And other features will be added.

Dear Dan,

Two questions: -

1. Will last clip delete be reactivated?
2. Any news on the NanoFlash and the Nikon D800. I realise this was asked in a previous post but this seems to be a good time and site to ask again.

Thanks

Thanks Dan

will this upgrade have any benifits for users of the EX and 320/350 cameras

Thanks
Ian

And elimination of the "card full" consequence of a too rapid double hit of the record button.


Ron

1. Will last clip delete be reactivated?
2. Any news on the NanoFlash and the Nikon D800. I realise this was asked in a previous post but this seems to be a good time and site to ask again.



Dear Alister,

1. Yes, this is in our plans. In fact, it is already fixed in our code and will be included in the next release.

2. I have tried to engage Nikon on this issue, but I have not been successful.
I will try again.

Will this upgrade have any benifits for users of the EX and 320/350 cameras


Dear Ian,

I will need to check if the HD-SDI record packet is available on these cameras.

It may be on the PMW-320 and PMW-350. If so, then this helps greatly when doing multiple camera shoots, as one can jam-sync the timecode (and have it running continuously) while also using the camera record button to start and stop the nanoFlash.

I do not know if the HD-SDI record trigger is on the EX1/EX1R/EX3 series or not.

And elimination of the "card full" consequence of a too rapid double hit of the record button.


Dear Ron,

This is a very useful feature and it makes our Hot Swapping much more useful.

For example, if one is covering breaking news, and the footage needs to be put on the air, while simultaneously continusing to record, Double Pressing of the record button causes the nanoFlash to stop recording on the CompactFlash card currently in use, while immediately switching to the other card.

Thus, one can then remove the first CompactFlash card so the footage can be immediately used.

Thanks Dan

the nano has been out for a while now how is it competing with the likes Atomas ninja/ Samurai is it holding its own as the Atomas products are good priced

Dear Ian,

I will need to check if the HD-SDI record packet is available on these cameras.

It may be on the PMW-320 and PMW-350. If so, then this helps greatly when doing multiple camera shoots, as one can jam-sync the timecode (and have it running continuously) while also using the camera record button to start and stop the nanoFlash.

I do not know if the HD-SDI record trigger is on the EX1/EX1R/EX3 series or not.

It's worth investigating for the EX series, because detecting advancing timecode may not be beneficial if you accidentally bump the "Rec Review" button and then the Nano starts recording during reviewing footage from a SxS card.

Dear Jack,

We have tested the EX3 that we keep in our lab, and we did not find the HD-SDI record packet present.

It could be that there is a menu setting that enables it, but a careful reading of the manual has not uncovered it yet.

if you accidentally bump the "Rec Review" button and then the Nano starts recording during reviewing footage from a SxS card.

Change your trigger to "last TC" and reviews will not be recorded on the nano!

Dear Ian,

Yes, we are working on a new firmware release.

There will be multiple new features.

2. The ability to detect the HD-SDI Record Packet.

This is a great new feature as one can use continuously running timecode as opposed to using Record Run timecode to start the nanoFlash.

And other features will be added.

Is there a beta version yet? or when will you release this firmware?
can't wait ;-)

Dear Ron,

Sorry, but we do not have a Beta version ready yet.

We will keep you in mind when we are ready to test this upcoming firmware release.

Hi Dan,

I am glad the new firmware is being prepared - please do not forget (apart from the features you mentioned):

- to fix the error that currently prevents cranking in the MXF format
- to give us an MXF concatenation utility like the one for MOVs
- probably asking too much, but how about mixing the embedded audio with analog inputs?

TIA

Piotr

Dear Piotr,

Thank you for your suggestions.

I can send you a utility that, using a PC, takes our MXF files and combines them, producing ".MOV"s.

This tool requires some software from Calibrated Software, and Quicktime Player Pro. Thus, there is some cost to using the tool that we provide for free.

There are PC Non-Linear Editors that work fine with ".MOV's".

Misunderstanding,, Dan - what I need is a utility to concat spanned MXFs into a long, one-take, MXF (not MOV).

I'm aware I can put all the spanned chunks on my NLE timeline, but when you edit a multicamera track consisting of takes, it's much more convenient to start with complete takes rather than chunks.

Since such a tool exists for MOV files, I thought we the PC/MXF users might ask for one, too :)

Piotr

Dear Piotr,

I understand.

We do not have such a tool right now.

This is exactly my current issue with the NanoFlash, meaning I would have to record MOV for cutting interviews in Final Cut elsewhere because that is the only file format that can be stitched.

I have also not heard from other Sony Vegas users whether joining 2 MXF files would introduce any complications. I therefore don't have the confidence to use the NanoFlash on long shots or interviews.

I have also not heard from other Sony Vegas users whether joining 2 MXF files would introduce any complications. I therefore don't have the confidence to use the NanoFlash on long shots or interviews.

I use Vegas Pro to pull in my nanoFlash MXF files that span several files. I just finished shooting several dance recitals and ballets where the longest takes spanned 12 files. They pull in seamlessly and without problems. These are multicam shoots and I have no problems dragging and dropping several files and they line up and chain together automatically.

As a question for Dan though, why can't you come up with a program that will concat the MXF files? Sony's Clip Browser program will create one mxf file when you have the native files from the SxS cards that span several files.

Thanks,
Garrett

Thank you Garrett. Did you have to undo the autofades for the audio on import?

Thank you Garrett. Did you have to undo the autofades for the audio on import?

Yes, I set it so that Vegas wouldn't automatically fade them. Other than that, it's just a matter of highlighting all of the files you want to bring in and just dragging and dropping to the track. very easy and I haven't had any problems with dropped frames or audio issues. I've been doing this since I got my NF so it's a very reliable and easy process. I have to say it does speed up the workflow since I no longer have to convert the mpg files from my EX3 to mxf's.

-Garrett

Thank you very much Garrett. This is what I wanted to hear.

On a side note, Vegas 10+ can import direct EX MP4s that are not spanned. Spanned MP4s still need to be re-wrapped to MXF.

Dear Ian,

Yes, we are working on a new firmware release.

There will be multiple new features.

Here are two:

1. Ability to extract timecode from the HDMI Input for the Sony FS100 and FS700 cameras.

2. The ability to detect the HD-SDI Record Packet.

Certain cameras, such as the Sony F3, Canon C300 and other cameras put out a signal in the HD-SDI steam that indicates every time the camera record button is pressed.

We will detect that signal and start/stop the nanoFlash accordingly.

This is a great new feature as one can use continuously running timecode as opposed to using Record Run timecode to start the nanoFlash.

And other features will be added.

Wow Dan,
Great future updates. That record packet is sure to be a real winner.
To let you know RED has added some new firmware to allow external recording w/o recording to the SSD cards. If you and your engineers need my Scarlet for testing please let me know.
Jim

1. Ability to extract timecode from the HDMI Input for the Sony FS100 and FS700 cameras.

It would be great if it would also work on the NEX VG-20

Dear Ian,

I will need to check if the HD-SDI record packet is available on these cameras.

It may be on the PMW-320 and PMW-350. If so, then this helps greatly when doing multiple camera shoots, as one can jam-sync the timecode (and have it running continuously) while also using the camera record button to start and stop the nanoFlash..

That would be a great thing Dan...I really need that with my PMW-350
thank you for your effort and time
Samer

Dear Piotr,

I understand.

We do not have such a tool right now.

And all this could have been avoided if CD had opted for a proper EX or XDCAM directory structure a la Sony and JVC cams. Its a Sony engineered codec and chip missing the corresponding Sony workflow which would have made it instantly compatible with all the major NLE's. Instead of support problems you'd have been able to say - just use XDCam Browser or AMA in Avid or import Sony XDCam in FCP - no more broken clips.

Don't get me wrong - you guys are one of the most responsive companies out there when it comes to tech support but lack of this simple structure seems to have caused Dan a lot of headaches! Isn't 20/20 hindsight a marvellous thing..

Dear John,

Thank you for your suggestion, advice and kind words.

To the best of my knowledge, AMA, at least in it's current form, did not exist when we started to design the nanoFlash.

While we do break clips into manageable sizes, there are at least some advantages.

1. Each clip stands alone and there is no directory structure or associated files to deal with.
If one wants a individual file, it s easily used.

2. Having smaller files is sometimes a great bonus if there is every a bit-error or corruption in any one small file. The rest of the files are still very useable. I was in a meeting of NBC Executives and they pointed out that this fact is very important to them.

We have the following tools available right now:

We can combine individual MOV clips into one large MOV clip during the transfer process.

We can combine individual MXF clips into one large MOV clip during the transfer process.

We just, at this time, cannot combine individual MXF clips into one large MXF clip.


And we will be adding, in an upcoming firmware release, a new feature.

One will be able to assign a "Tag", which can included letters and numbers), to each clip.

Then one will be able to shoot various clips and our software will be able to combine them together, by searching for all clips with the same tag.

And of course, we will make it easy to switch from one tag to another before recording a clip.

For example, for a news gathering organization:

A news crew goes out in New York city and shoots clips around the city.

And while there are out, they shoot clips for another news segment interspersed among the clips for the first segment.

If they assign a tag to all of the clips for the first segment and a separate tag for the second segment, then our software will combine all of the clips of the first segment into one clip and the same for the second segment.

Then the network can load the complete segments into their editing system.

Thanks for this information, Dan - looking forward to the new firmware :)

One thing in your message is not quite clear to me - how can we "combine individual MXF clips into one large MOV clip during the transfer process"?

Are you talking about Mac users only, or am I missing something (I'm a PC/ Vegas Pro user).

Dear Piotr,

This is a PC based program that we have developed.

..and some link, please?

;)

Hi Dan

1. Each clip stands alone and there is no directory structure or associated files to deal with.
If one wants a individual file, it s easily used...

2. Having smaller files is sometimes a great bonus if there is every a bit-error or corruption in any one small file. The rest of the files are still very useable. I was in a meeting of NBC Executives and they pointed out that this fact is very important to them..

There seems to be a certain lack of knowledge here on how the BPAV structure works. Sony still splits files into 2GB in an identical fashion to the Nanoflash and of course you can still access the individual clips in exactly the same way as you can access the individual clips on the CD cards - just another 2 folders down. It just uses an XML database and a folder heirarchy so that the editing program or XDCam browser can display contiguous clips as one large clip - eg a 2 hour continuous shoot like a conference or concert is actually stored on the SD card, SxS Card or optical disk as a bunch of individual 2GB clips, but the BPAV folder structure allows the editing program to present it as one seamless clip to the editor - this is done "on the fly", no copying or concatenating or any other silly stuff required.

We have the following tools available right now:
We can combine individual MOV clips into one large MOV clip during the transfer process.
We can combine individual MXF clips into one large MOV clip during the transfer process.
We just, at this time, cannot combine individual MXF clips into one large MXF clip.

I don't think anyone would dispute that using a bunch of third party tools (one that uses quite an expensive plug in) that require processing, re-wrapping and copying all the media manually is a better solution than the plug and play BPAV folder structure which is cross platform and compatible with all the major NLE's. Moreover you get XDCam browser free which is quite powerful for metadata tagging and combining clips of different cards into one folder.

The MediaPro.xml file contains the information on all the clips recorded and how they stitch together while the xml files within the CLPR folder contains the relevant information on the clips themselves which also reside there (each in their own subfolder).

I'm just wondering if your engineers ever even looked at this as an option?

And we will be adding, in an upcoming firmware release, a new feature.
One will be able to assign a "Tag", which can included letters and numbers), to each clip.
Then one will be able to shoot various clips and our software will be able to combine them together, by searching for all clips with the same tag.
And of course, we will make it easy to switch from one tag to another before recording a clip.
For example, for a news gathering organization:
A news crew goes out in New York city and shoots clips around the city.
And while there are out, they shoot clips for another news segment interspersed among the clips for the first segment.
If they assign a tag to all of the clips for the first segment and a separate tag for the second segment, then our software will combine all of the clips of the first segment into one clip and the same for the second segment.
Then the network can load the complete segments into their editing system.

The tagging sounds very interesting and a cool feature. As usual well done when we see this feature pop up.

I love the Nano - it's great especially with consumer cameras with decent chips but no decent recording option but I still wish it had better workflow options :) It isn't really a problem except when it doesn't work as in my current issue with LongGOP media 100Mbs on Avid breaking the AMA plug.

http://www.dvinfo.net/forum/convergent-design-nanoflash/509719-100mbs-long-gop-avid-generates-errors.html

No way around it that I've worked out so far. I tried converting all the mxf clips to mov using Sorenson and that would have worked except it broke timecode.

Hope all that clears up a few misconceptions - cheers Dan

John

Dear Piotr,

We do not have a link up for this software at this time.

I will ask our team to put up a link as soon as practical.

Dear John,

Thank you for your suggestions.

I will discuss this with our engineers.

Dear Ian,

Yes, we are working on a new firmware release.

There will be multiple new features.

Here are two:

1. Ability to extract timecode from the HDMI Input for the Sony FS100 and FS700 cameras.

2. The ability to detect the HD-SDI Record Packet.

Certain cameras, such as the Sony F3, Canon C300 and other cameras put out a signal in the HD-SDI steam that indicates every time the camera record button is pressed.

We will detect that signal and start/stop the nanoFlash accordingly.

This is a great new feature as one can use continuously running timecode as opposed to using Record Run timecode to start the nanoFlash.

And other features will be added.

Dear Mr. Keaton. We are 5 months further. When will these functions be implemented?
Thanks, Ron

Don't know what you all think but are you getting a funny feeling that alls not well? Dan use to be on here like a flash if someone had a prob or needed support and now hardly comes on here and no news of the upgrades to the nano that were promised!!

Hope Iam wrong because they were a first class company

Nanoflash with CF cards was/is great, but it's done. They're probably on to making a new compact 4K recording system with SSDs. If they made some smaller ones for POV cameras for < $1k, I'd be in for a few.

My only gripe was the lack of BPAV file structure, meaning that (at least for Sony Vegas) you have to manually stitch together on your timeline any spanned files.

CD has not (and by now, will not) make a MXF to MXF stitcher and a fix for the illegal black record kill switch on HDMI might never see the light of day.

...and a fix for the illegal black record kill switch on HDMI might never see the light of day.
I'm fairly new to nanoflash. Jack, would you mind explaining just what "illegal black record kill" is? Are there cams that generate an illegal black that kicks the NF out of record? Yes, I'm using HDMI. Thanks in advance.

I am getting the message that many people have moved on, or would like to, or are mad at CD for not supporting/extending/updating the NF, but for me, it is still a pretty good life-extender for my HDV camera, and I look forward to seeing how it works on a Canon C100, too.

***edit***
Never mind. I did finally search on the right terms and found this thread: http://www.dvinfo.net/forum/convergent-design-nanoflash/504607-different-signal-detection-options-nano.html , which explains the issues Jack has experienced using the Nanoflash as a screen recorder.

Some POV cameras also output illegal blacks when the camera is covered. This causes the Nanoflash to completely stop recording.

dear ian,

yes, we are working on a new firmware release.

There will be multiple new features.

Here are two:

1. Ability to extract timecode from the hdmi input for the sony fs100 and fs700 cameras.

2. The ability to detect the hd-sdi record packet.

Certain cameras, such as the sony f3, canon c300 and other cameras put out a signal in the hd-sdi steam that indicates every time the camera record button is pressed.

We will detect that signal and start/stop the nanoflash accordingly.

This is a great new feature as one can use continuously running timecode as opposed to using record run timecode to start the nanoflash.

And other features will be added.


when will that happen?????

Just got my regular e-mail from Convergent Design re yet another firmware update for their "Gemini"but not a dicky bird , again, about the "nanoFlash".

Seems us nano owners are now ancient history.


Ron

You should be a Flash XDR owner!!

Speaking of that, since the XDR has been completely abandoned, how about open sourcing that device's firmware code? an OpenXDR firmware initiative would mean newer bugs would be fixable.