Read the help files or manual on what audio PPRO works with.
Native to Windows systems is .wav (PCM) but PPRO can read and use many others in a timeline. I have never heard of LPCM so you may have a conversion to deal with but I wouldn not know at what part of the work flow. (this could get messy: IMHO)
Update the app. with latest patches ( Why would you not have done so already if you are having an issue?)
1 person found this helpful
It may be an endianism problem. NXCAM is big endian like DVD LPCM, while most PC based LPCM is little endian. If it is being interpreted wrongly then you'll just hear hiss.
1 person found this helpful
I have the same problem trying to work with the NXCAM AVCHD PCM audio, In addition to the hiss you can hear highly distorted audio. This is a very new product so there is not even support on the Sony web sites. Sony does not recognize HXR-NX5U or HXR-128FM as valid Sony model numbers! So the only software available is what came with the camera! But that software plays the sound just fine. It is PPro CS4 that will not decode it. Someone in Adobe needs to talk to someone at Sony to fix the incompatibility. Sony's PPro CS4 workflow writeup does not help.
Did anyone resolve this problem, yet? I'm looking at getting a Sony NXCAM.
Jack - The incompatibility of Premier Pro CS4 with the NXCAM Linear PCM audio still exists. I suspect the next CS4 update will fix it but I have no promise that will be done. Of course it work fine with Sony's Vegas Pro 9 (http://www.sonycreativesoftware.com/vegaspro ). It also work with Apple's Final Cut 7, but importing files is very time consuming. If you have Prow CS4 use Dolby instead of LPCM sound. - Bill
Spot on answer.
I just finished a job where I shot two day's worth of footage using the ACC / dolby audio settings. Came through just fine. Video quality is stupendous.
But I sure hope they resolve the PCM audio issue in the next release.
Interestingly I had the same compatability problems with PPro when AVCHD first came. Some people on these boards claimed "forget about that codec, it's just for consumers." Ah-hem. And that's why Final Cut supported it right out of the gates?
I love PPro. I really do, but Adobe's inability to keep abreast of new file formats / combinations in the same way as Final Cut (I'm not mentioning Vegas because if Vegas didn't support these then there'd be reall issues with this camera), the whole thing makes me scratch my head once a year, asking myself why I don't make the hardware / software leap and use something into which I'll always be able to import something first time out.
I'm pleased you have a solution to this, but I'm surprised that Adobe recommended the installation if a codec pack. For example do a quick search of the forums for "codec packs".
Just did your search. Fascinating. But, as mentioned, the link and recommendation came straight from Adobe support.A little conflicted / schizophrenic in their approach I see.
Also, one important note, even with the codec pack installed the "Import Folder" option, or selecting and importing more than one
file at a time still leads to the audio coming across as high gain hiss. So it's not a flawless solution as I mention earlier.That I got it to import without the hiss -- and very high quality, uncompressed audio -- made me too zealous in my report.
God this pisses me right off! I've tried installing the klite codec pack and imported a file at a time; but no luck - I still get white noise. Time and time again Adobe releases products that don't work 100% - i.e. OMF support - CS4 one big Beta.
Okay enough rant - IS there something I'm not doing right? Is it a setting? I have a deadline and need this working now.
IS there something I'm not doing right?
I've tried installing the klite codec pack
That's it. And it's a biggie.
Does the LPCM audio from that brand-new camera open OK in Soundbooth or Audition? If not, there's zero chance it will work in Pr.
Probably your best move was installing the K-Lite package. Get out your Windows DVD, reformat your disk and install OS & programs again. Make sure to de-activate CS4 first.
Can you post a short clip for me to download and try?
"Good judgement comes from experience, and experience, well, that comes from bad judgement."
Installing K-Lite is in the category bad judgement.
"To err is human, but to really fould up requires a computer with K-Lite."
Sorry, I'm somewhat confused. A previous post said that Adobe support recomended the installation of k-lite - now the last 2 post's say that it was a mistake and the only way to solve the problem is to re-format? The audio wasn't working even before I installed k-lite - "nothing lost, nothing gained so far"
Will K-lite affect CS4's performance? How and why?
First, Adobe TS (Technical Support) is quite good with installation problems or activation problems. When it comes to technical issues, it is often easier and faster to request help here and there is a good chance that the solutions offered here work better. Do not forget that TS works from standardized lists of questions and answers, but hardly ever use the program at all. Their hands-on experience is often severly lacking, and sometimes their English language skills as well, as many complained about.
Second, K-Lite is well known for the havoc it creates on a system and is not effectively able to uninstall. It leaves traces behind that will continue to plague you. With CS3 I have experienced this myself and the easiest, fastest way to get your machine working again, is to reformat and reinstall. Far easier than troubleshooting.
K-Lite is a bag-full of open source, re-engineered freeware that messes up registry entries and priorities without having been fully tested in combination with CS4 and that can lead to all kinds of mysterious errors, hangs, or even BSOD's. After uninstallation, registry entries are not properly restored or removed, so the registry may still contain sources of problems and will remain bloated, reducing performance.
I repeat, give me a link to a small clip that I can download and test for you.
okay, here's a link for a file:
Thankfully k-lite is only installed on my Guinea Pig portable edit suite - my main one is untouched. Klite pack kdoesn't seem to have affected performance yet - everything else seems fine.
I had tried the workaround of opening the audio in Audition 3.0 but as installed with the latest updates it does not recognize AVCHD as a valid video import format (selecting the open audio from video option).
And the recommendation from TS (Tech Support) I received regarding loading K-Lite did not come from a phone call but from a web-submitted support request. I can post the PDF if anyone's interested.
Thanks for the link.
I tried it and no problem. Well, there are some problems, but that is more the way it was taped. Single mono directional mic that picks up a lot of noise from the spectators, overriding the actor, who should have put on a fresh shirt before his performance. Next time, if you can't pin a lav on the actor, at least put a directional mic on the stage, closer to the actor or put a mic on the mic-stand that he is holding (18:17).
Import into your sequence, edit in Audition and the whole waveform is shown and plays back without problem. Same in PR.
I tried all the PrPro CS4 "fixes" without success! I imported your clip into Sony's Vegas Pro 9 and the recorded LPCM audio worked flawlessly. (Next time use the stage mike or lav mike as suggested). The clip also worked in FCP 7. It will probably play OK in PrPro CS5 due out next month. The problem is PrPro CS4! Fixing it will probably slow upgrades to CS5, so nothing is being done by Adobe.
I'm very happy to report that LPCM wrapped inside the M2TS container does indeed work in Premiere CS5. Bravo Adobe!