Correct me if I'm wrong, but the nano records 24bit uncompressed WAV. Can't you just unlink the audio from the video in Premiere?

Is the sync off ONLY during playback within the timeline or is the encoded timeline also affected?

OK, Thanks Andy.

What sort of sequence are you running it in? XDcamHD 4:2:2?

Tim - for info re compatability between nanoFlash files and Cineform, please see the DVInfonet Cineform board. Buried in there someplace, as my sometimes faulty memory fixates, one of the two principals of Cineform apparently made the statement that Cineform would not handle nanoFlash data now, nor would it in the future, because of the Sony based codec in nanoFlash - I believe also that the statement was made that the blockage to successful resolution of the issue did not rest with Cineform, but did with Sony......please, though, I could be at least partially mistaken about this......should I run across it again in my meanderings through the Cineform board, I will post a link here.

I have the rights to Cineform Neo4k v5 (recent successor, as you may well know, to Prospect4k). After reading the Cineform post I've just related, I dropped Cineform for the last couple of months until three days ago, and am now running it again - Neo4k v5 with Adobe Premiere Pro CS4 (with the MainConcept plug in). In a project I just started, set up for edit of nanoFlash files (1080x1920 30p 100Mbps Long GOP), thus far all I have done is two days of work in setting up some standard titling (close credits, etc) using the Adobe Premiere titler - I decided to reinstall Cineform in order to export and save all the title work permanently in a really clean way with the Cineform AVI wrapper, at which of course Cineform is so capable. But I haven't attempted to do anything further with it at the moment.

By the way, there is some ranting going on over at the Adobe sponsored board - Premeire CS5 - in a thread I started quite a while ago, inquiring about when we might see a fix to the nano audio issue in Premiere CS5. After a lapse of a week, that thread has suddenly become active. As above in this thread, I was not circumspect in my comments about Adobe and Premiere - if you think I am a bad person for my comments (!) you ought to see what is being posted by someone claiming to be an Adobe employee. And some Adobe customers on that same thread are far more direct than anything I've said about their "displeasure" with Adobe. One fellow indicates that he was "told" by Adobe (I won't use the word he used in place of "told") that Premiere CS5 worked fine with nanoFlash files, paid $2,000 for some version of a CS5 Suite, and now is more than just a bit displeased in finding out that this is not true.

Before I respond to your query about other formats I might have used in nanoFlash recordings, let me say that for the time being I have decided to again become the circumspect, politically correct "nice" guy I always was (past tense!), and not disparage anyone, and just praise those who provide such an great set of products and superlative, outstanding customer service, such as Convergent Designs, Cineform, and BOXX (BOXX, my PC maker here in Austin, Texas - WOW, are they soooo knowledgeable and helpful). But I will report the facts (facts?) as I have experienced them. To wit, as I said above, I have just spent two days creating some titling using Premiere CS4. For me, after some initial bugs were worked out by Adobe, Premiere CS 4 has been as solid as a rock, with two exceptions. The first has been the initial issue of this thread, a problem for which I am probably responsible. But forever, I personally have had problems with runawway RAM and crashes with the Premiere CS4 Titler. Given my again politically correct persona, I will not comment about what I have seen posted all over the place about others' experience with the Premiere CS4 Titler. But personally, instead of the two days I have just spent creating titles, it would have been only a day and a half, except that after a day, the Premiere CS4 Titler unexpectedly (excuse me, isn't ai always unexpected!) crashed, and not only took half my titles, but also or as part of the wipeout, removed the last ten of my twenty "saves", so I started all over. Just the facts....that's what happened, and has frequently happened to me. Let others speak for themselves!

Finally, you inquired about my running 50 Mbps files, ect. At this point I have run nothing but 100 Mbps Long GOP and don't intend to do anything else, even if it corrects the issue with CS5 sound (which according to some on the Adobe PPCS5 board it does not, but again, please see that board) since I am interested in recording close to the best possible picture at less than the top data rate.

In the words of Tiny Tim, "May God bless us, everyone."

Dear William,

I really wish we knew when the audio issue in CS5 would be fixed and a new version released.

But, I do not know when the new version is scheduled to be released.

Does Adobe release any information as to when to expect their next version?

William,

I only asked about other data rates as a troubleshooting question...not to recommend you change your workflow.

Titler...embedding title files in the project was the worst thing that ever happened to project stability in Premiere Pro...period.

...and yeah, I saw the Adobe forum thread. (You may want to revisit it...)

Tim, I have just posted a query about Cineform's HD Link and my faulty memory (and perhaps faulty statements) over on the DVInfo Cineform board, and hopefully, we will be hearing some response from the fellows over there ( maybe even one of the two Davids!) Please go to: http://www.dvinfo.net/forum/cineform...ash-files.html

Tim - one of the David's has now posted a response at the thread I just linked to above. Please see his comments about mxf which I didn't know and found very interesting! Apparently, for HD Link, nano files cannot be handled yet, but evidently Cineform is giving some kind of fix some attention, though it may be toward the back burner.

Dear William,

To elaborate on David's post, in the other thread:

All MXF files are not created equal. By its very nature, MXF was designed as an "Extensible" (extentable) format. There is not "Correct" place for every item.

Even if the actual item (piece of data, or metadata), in the MXF header is identical, it may be in another place.

For example, if we have 10 data items, one could put them 1,2,3,4,5,6,7,8,9,10, whereas someone else could put them 1,2,4,7,3,6,10,8,9,5.

Thus, one has to search and find the data in the MXF header.

Also, there are multiple ways (flavors or formats) to record the audio. thus I understand David's comment that they have to work on the audio.

All of this is perfectly natural and expected.

As a side note, we offer a File Converter. One of the reasons we do so is to convert Apple's MXF format into our MXF format. Inside the nanoFlash, we want to save time by having the MXF header data where we expect them. So, we just re-arrange Apple's version so that it is in the order we want.

Originally, our MXF format was incompatible with Sony's Optical Disk Format. We modified ours to make it compatible.

Yes indeed. The great thing about so many of our standards is that they're so darn flexible...

Now...why Sony decided to wrap EX files as MP4 while the original XDcamHD format is MXF? That's another interesting tale, I'm sure...

I'm glad some of this stuff is turning around. The tone was pretty down...and I knew that this wasn't being ignored by Adobe.

I like the CineForm guys and the work they do as well....and have since "Aspect HD for Premiere 6.5" came out way back when...

Oh yes - I have been wondering the same myself since the moment I learnt the file inside the MP4 (MPEG-4?) container is actually the old, good MPEG-2... Wrapped into MXF by other applications!