Dear Friends,

Our latest Public Beta for the nanoFlash is 1.6.245 and we have a Flash XDR version out also, 1.5.92

We are requesting feed back on these releases.

In 1.6.245, with certain Delkin 450x cards, our MPG does not work properly.

We have made a change to support these cards in MPG mode.

In general, we are very pleased with these releases.

But, we need feedback from those who are using or have tested these releases.

We are very close to releasing a Production Level release, but we just want more feedback.

Any feedback will be greatly appreciated, if only to say "It works for me".

The nano has been velcro'ed to the wall next to me, running off it's AC adapter, recording standard 1080i 29.97 the past week. 100Mb Long GOP to Transcend 64GB 400x cards, and one 32GB 400x Transcend card, which I've been using at 280Mb IFrame. SDI in and out. Embedded audio, sometimes 2 channels, sometimes 8 channels. Timecode is generated locally (in the nano), set to free run, synced to time of day and drop frame. Recording into mov containers. Primarily as a record machine, but some playback as well, mostly to check clips after the fact. Nothing plugged into the nano accessory port; everything is done from the front panel. (I still want you to put in a delay when pushing the stop button while the nano is recording, but that's for another thread). No timecode triggering, no cranking of any kind, no progressive segmented frames, embedded or otherwise.

The Transcend cards (32&64GB 400x) seem to hold up just fine at 280Mb, by the way, in both record and playback. I'm only using the 280Mb IFrame for the test signals card I carry with the nano (which turns it into a great test signal generator).

It all seems to be working as advertised. When recording, the "close file by pressing record once" works, as does the "skip to next card by pressing record twice". I have not had a chance to test hot swapping while in record yet. There was one time when one of the 64GB cards I inserted wasn't recognized, but a power cycle "fixed" things. I think this only happens when I'm first powering up the unit and putting both cards in almost simultaneously. I think the nano may be busy figuring out what just got put into slot one, and misses that something was also just put into slot two. Or not. I think it happened to me once before eons ago (over a year ago).

Billy

I'm using my nanoFlash with the latest Beta release. Signal from a Sony EX3 using Transcend 64GB cards. I've tested 50Mbps and 100Mbps L-GOP and 220Mbps and 280Mbps I-frame. No problems so far.

I do want to test it with a Canon HV20 using the HDMI input but haven't gotten around to that yet.

Cheers and thanks for the great work,
-Garrett

Dear Billy and Garrett,

Thank you both for the detailed feedback.

Pushing two CompactFlash cards in simultaneously may cause problems.

We just recommend putting in one card at a time, one does not have to wait long, just push one in, then the second one.

I have just installed 1.6.245 and I am having audio sync problems there is a 3 to 4 second delay

I have an EX-1 set to 24p , I am monitoring audio from the nano and getting little to no delay, it is only

when I record that the delay happens

should I roll back to an older update

Dear Rob,

Where do you see the delay, in the headphones while recording
or in the files when you take then into a Non-Linear Editor?

We will attempt to duplicate this in our lab.

Thanks for posting the details: EX1 in 24p mode.

Could you please create a settings file for us:

Format a card, then navigate to

System|Create Settings.txt

Then press the right arrow, then press Ok.


Then email the files to CDSupport (at) convergent-design (dot) com

We will check out your settings, and test in our lab.

Hi Dan,

I have only played it back from the nano to my IKEAN monitor .

I have not put it through my NLE yet.

Could this be the problem.

Dear Rob,

I am very surprised that the audio is out of sync in playback from the nanoFlash.

Yes, you can go back to a previous release.

If you are using Delkin 450x cards, you will need to stay on one of our latest releases, 1.6.245 or higher.

I have alerted our labs.

Dan,

I just played the clip on my Mac and there was no delay

so it must be only on play back from the nano

I shot this clip at 18mbs longop

and why I have you I just got the remote trigger and I was wondering what the proper procedure was

because the trigger starts the recording fine, but when I try to stop recording I find I have to hold the button

down for about 3 seconds before it stops the recording.

Is this normal

Dear Rob,

The 18 Mbps may be a clue to the audio delay problem.

The remote control works like this (in normal mode):

Press the Remote Control button, the nanoFlash starts recording and the Tally Light comes on.

Press and hold the Remote Control button for 1 to 2 seconds, then release, then the nanoFlash stops recording.

This prevents any accidental depression of the Remote Control button from stopping a recording.

I still want you to put in a delay when pushing the stop button while the nano is recording.

We are trying to work in your request.

I am thinking that 1/2 second would be long enough to tell the difference between an accidental press of the Stop Button versus the intentional stopping of the recording.

Hi Dan,
I'm using the Delkin 32GB 450X CompactFlash Pro Cards in my NF version 1.6.245 recording mxf at 35Mbps and all, as far as I see is working well.

Is there a problem with the Delkin 450X cards with this beta version 1.6.245?

Thanks in advance.

Dear Anthony,

No, the Delkin 420x and 450x cards work fine in the nanoFlash, with 1.6.245 in MOV (Quicktime) and MXF modes.

Only in MPG mode is there a problem.

And we have already modifed our code to work with the Delkin's in MPG mode, we just have not released the new version yet on a widespread basis.

having audio sync problems there is a 3 to 4 second delay

I have an EX-1 set to 24p , I am monitoring audio from the nano and getting little to no delay, it is only

when I record that the delay happens

should I roll back to an older update

Hello Rob,

When you experienced the audio delay were you recording 24psf out of the EX1 or were you recording 60i pull down 24, via the nanoFlash 3:2 Removal?

Also note for everyone you can insert two Compact Flash Cards Simultaneously because of HOT SWAP support :)

Best Regards

Dear Anthony,

No, the Delkin 420x and 450x cards work fine in the nanoFlash, with 1.6.245 in MOV (Quicktime) and MXF modes.


OK, thank you Dan.

We are trying to work in your request.

I am thinking that 1/2 second would be long enough to tell the difference between an accidental press of the Stop Button versus the intentional stopping of the recording.

Thanks! I'm thinking that a 1/2 second is not quite long enough. Though I would prefer two seconds, I feel that a one second delay is probably more appropriate to prevent accidental stoppage while not causing users to think that the stop button isn't working. Say "one thousand one" to yourself and see if you feel that's too long.

My concern is that 1/2 second is still short enough that when one accidentally presses the stop button and feels the click, that reaction time to release the stop button may take longer than a half second delay allows for.

The reason I brought this up in first place is that I use my nano as a stand alone recorder, not attached to a camera, and when I don't have it velcro'ed to a wall, picking it up and moving it a little while it's recording is a bit difficult. There aren't two opposing sides without "stuff" on them. You don't want to pick it up holding the right and left sides, as the CF cards are on one of those sides. You don't want to pick it up holding the top and bottom, because the cables are on one of those sides. You don't want to pick it up holding the face and back, because the control buttons are on one those sides. So however you pick it up, you have to be careful.

I certainly wouldn't mind a setting that turned "stop button delay when recording" on and off, if you feel that a delay would confuse and annoy as many people as it helped...

Billy

Hi Andy
I was using the 24sf out of the camera at 18mb

Dan thinks it was the 18mb that was causing the problem.

and since it was only when playing back from the nano to the field monitor

I really not as concerned as I first was.

I going to do more test now and I will get back with results

Dear Dan,
On the delay subject once you introduce a delay factor I am concerned that this now prevents the Nanoflash from been controlled by other devices that issue a momentary on or off sequence such as GPI outputs found on many video switchers DVD recorders etc. Perhaps a menu option to select a pre-set delay or no delay may be the way to go. Please do not prevent the Nanoflash from been machine controlled I really do think that the Nanoflash now needs user profiles as it's going to be very difficult to please everyone.
Thanks

Dear Lance,

The nanoFlash has a special Trigger Mode, "Remote Level" designed specifically to work well with machine control.

In this mode, if the switch is closed, or the relay is activated, we record.
If the switch is opened, or the relay released, we stop recording.

Thus, there is no conflict.

This mode also has some applications when using our wired remote control.

Press and Hold the Switch and we record, release it and we stop.

Thanks! I'm thinking that a 1/2 second is not quite long enough. Though I would prefer two seconds, I feel that a one second delay is probably more appropriate to prevent accidental stoppage while not causing users to think that the stop button isn't working. Say "one thousand one" to yourself and see if you feel that's too long.

My concern is that 1/2 second is still short enough that when one accidentally presses the stop button and feels the click, that reaction time to release the stop button may take longer than a half second delay allows for.

The reason I brought this up in first place is that I use my nano as a stand alone recorder, not attached to a camera, and when I don't have it velcro'ed to a wall, picking it up and moving it a little while it's recording is a bit difficult. There aren't two opposing sides without "stuff" on them. You don't want to pick it up holding the right and left sides, as the CF cards are on one of those sides. You don't want to pick it up holding the top and bottom, because the cables are on one of those sides. You don't want to pick it up holding the face and back, because the control buttons are on one those sides. So however you pick it up, you have to be careful.

I certainly wouldn't mind a setting that turned "stop button delay when recording" on and off, if you feel that a delay would confuse and annoy as many people as it helped...

Billy

Dear Billy,

Thanks, we will try to program it as you have requested.

But, I am not certain when we can work it in, but we do want to do it.

I wouldn't want this to delay the release of the current beta firmware (1.6.245). There is so much stuff in this beta that is much more significant than "long stop press". I'm one of those people that would rather you test, verify, and release a solid firmware before asking you to add features.

I have a few "requests" that I plan on asking for (or asking for again) once 1.6.245 is deemed production level. ;)

Billy

Hello Rob,

Thank you for your post, We were able to replicate the Issue here in our Lab, The Issue only occurs with 18Mb Playback out of the nanoFlash, the audio that is recorded to the files is fine. Also It is not Format dependent (1080psf24) but Only Occurs with 18Mb LG Quicktime and MXF, We also tested various other bit rates and formats and had no issues, Including MPG,

If you actually count in front of the camera you will see that playback actually jumps around, rather than being 3-4 Seconds off,

But Our Engineer's are currently putting in a Fix for the Full release.

Best Regards

Hi Andy,

this concurs with my findings also, I did several tests last night and found

the problem only happened at 18mb.

Thanks

I'm getting in late to comment on Dan's thought of 1/2 second delay (versus the 2 second one now). I FULLY agree with half a second and suggested it a couple of months ago.

2 seconds is TOO long for a fast moving production (as I usually work). So I've accidentally left the recording on THINKING I had held it long enough to stop. Quite irritating.

Half second is indeed long enough to be "different" from an accidental push.

I'm talking about the front panel stop button, not the remote control button. Right now there is NO delay when pressing the stop button, and no ability to turn on a delay. Dan asked if a half second was enough, and I mentioned that while two seconds would be what I preferred, one second would enough.

I still feel that a half second is NOT enough for the front panel stop switch, for the reasons I mentioned in my message above. When one picks up the nano from a table, or moves it from one position on the table to another, it's easy to accidentally hit the stop button. When one feels the "click" of the button, it takes more than a half second to realize and release the button.

I don't use a remote on/off button, so I have no experience with it, and I wouldn't presume to tell you what your usage should be, in any case.

Billy