Just to get this out of the way early, I have two questions:
Did you Copy the full folder structure from the camera's card, to your HDD, or just the video files?
Did you allow the Conforming and Indexing process to complete 100%, before dragging the files to the Timeline? This ARTICLE goes into more detail.
A spanking new CS6 Project with new assets, not common to both versions. I tried the new assets in a new CS5 Project when CS6 didn't import the audio. That's how I discovered the new assets function normally in CS5. And the trouble in CS6 is only with these particular assets, which is why it's maddening. Other video assets in the same CS6 Project -- GoPro files and video from a Nikon DSLR -- function normally!
Again, thank you for the clarification.
OK, I am rather out of ideas on the cause.
Let's do one more Q & A session please:
With MediaInfo, or similar, what are the specs. (especially the Audio Stream) on the files that do not Import properly, and also some of those that do? Any glaring differences?
The DD AC3 (2-channel) should not normally be an issue, but if we can find a difference, that might be helpful.
Hope that someone else has something to offer you, like Trent, and good luck,
I am also concerned by this issue as I have a Sony A77 camera (among others that create .mts files) and am considering an upgrade from Premier 5.5 to CS6(.1) but in my testing I have not been able to get the audio for file imports working either.
I have tried;
- various project setups, defaults and with Audio 5.1 selected etc
- Drag videos to the project window, open through the browser both from a copied file and from the source (camera) and from a copied from camera to temp dir in it's entirety (ie with additional meta data files).
- Adobe Media Encoder wont open and convert the vids with audio either, nor will bridge
- Changing the device (camera) to record (lower quality) mp4 files import to Premier in any manner I wish to try, all with no audio problems
- The video files play fine (with audio) in Windows Media Player, VLC and Even Lightroom 4.1
- These same video files import with audio fine into CS5.5, but not in 6.
So my questions are...
- Does Adobe recognise that there is a problem here? That some, many, most .mts AVCHD video files are not loading into CS6 Premier Pro properly?
- Is there a workaround/solution? (that is established and please nobody please suggest a re-install of the app again)
- Is there a simple converter or way of modifying the mts file that works and is free? (anything from a rename to a re-encode that is tested)
There is way too many people talking about this problem for it not to be ignored and in cases where people are finding that it worked fine in 5.5 and now doesnt in 6, this is not a user problem, it is a technical problem specific to the CS6 app range, either with a codec support (ac3) not properly functioning or a related glitch and it needs to be fixed or resolved soon please.
Just to add:
VLC reports the video file properties as;
Video: h264 - mpeg-4 avc (part 10) (h264)
Audio: A52 Audio (aka AC3) (a52)
Sample Rate 48000 Hz
Bitrate 256 kb/s
Here are screen shots of the info panel for the same short clip opened in CS6 (darker) and CS5 (lighter). Note that the clip has no audio info at all in PrPro CS6, and does have audio in PrPro CS5, where it functions normally. I hate mysteries. Is this helpful at all? And Mr. Hunt, I'm deeply grateful for your guidance and assistance, by the way.
As Rexel99 points out above, it DOES seem that something in CS 6 is not functioning, as it did in earlier versions. Why? I have no idea.
Is Adobe working on a fix? I cannot say, and await Wil, Todd, or another Adobe employee to comment on that.
The screen-caps that post are interesting. Not sure what they tell us, beyond CS 6 not seeing the Audio Stream, but that is what I am inferring from those images.
Yes, a mystery, and cannot even think of any more questions to ask. Maybe others will quickly see something that I am missing here.
Good luck, and thank you for all of the info.
Great info, thanks for adding that.
It seems that this is working for some people, although nobody has confirmed the reason for this - another third party app, driver or codec that exists may fix the problem. But in my tests I am using a clean Win7 (64 bit) with office, cs6 suite and Sony PMB. I have tried adding Sony's image/data converted plugins (which are mostly raw related) and a few extras such as Lightroom, VLC...
The suspicious thing is that 5.5 reads it on the same systems that cs6 does not.
A discussion at http://forums.dpreview.com/forums/readflat.asp?forum=1045&message=41597098&changemode=1 indicates the issue with Photoshop (although why this person is doing video in photoshop I am not sure) and that getting Premier Pro /Master collection will include the codecs and enable the AC-3 decoding (which is otherwise blocked) required for this video format - referring back to comments here http://forums.adobe.com/message/4284091#4284091 - maybe the ac-3 codec is still just block/disabled for some reason?
I cant find the other thread/conversation i also saw that mentioned about Pro including the full dolby codec that would help make it work...?
Is there a (simple) way to test perhaps if the codecs that are used/employed to do it are in fact installed and working? - I have played with codecs/muxers etc in the past, even when doing it though I was confused by what was happening...
I'm using PrPro CS5 & CS6 on a 27-in iMac with OS X 10.7.4 and 16gb of maxed-out memory, 13 of which is dedicated to the CS products when open. My Big Giant Mystery is that CS6 opens other HD assets shot the same way in the same camera both before and after the session currently not importing audio. CS5, on the other hand, opens these silent assets and they function normally. So, in my case, only this one mute session is affected. I hate mysteries!
Are you saying that office IS a problem? Is there some specific cause that the office suite contributes to this issue?
I have never seen Office cause issues around audio decoding, and if it did, and that IS the cause then I think it should be identified and resolved. I am just being open about my environment and whats running here so if we can count that as a cause I would happily remove it.. if it's not an identified problem then at best it's a guess and at worst its unhelpful.
Sorry to be a bit abrupt there, but I have read through about 30 threads regarding this problem and most responses are left-of-field guesses which dont actually point to a cause or identify a reason - which is what i would like to get to the bottom of.
BTW, CS5.5 is importing the video file 'with' the audio on the same machine so the other apps installed wouldnt be my first thought on a cause. It might be office, it may be MS Security essentials, it may be live (with ms movie maker that comes installed now) it could be one of the 600 MS updates, it could be Firefox... so lets find the cause in respect to CS6 please.
Are you saying that office IS a problem?
I'm saying it has been in the past, and it may be here as well.
It might be office, it may be MS Security essentials, it may be live (with ms movie maker that comes installed now)
Yep, best to get rid of them all on a production rig.
it could be one of the 600 MS updates, it could be Firefox
Far less likely.
You keep talking of these production rig environments, although the software is designed for IBM based 'PC' computers which invarably have other programs installed. For one reason or another a PC is no longer setup for a single specific task, so environment wise, these things (unless specified) should work with other programs. Should a production rig environment not run the corporate Outlook email system, should it not be able to open the word based running sheets used within the business environment?
I am aware of things like office, or SP updates causing issues for apps like Finance1 that use specific level OBDC drivers, fine, bad programming or whatever but an identified conflict that can be avoided. For the CS suite however, I cant find or see that conflict - even if it has been a past issue I see no remarks that it is a concern now. Also removing an app (or provided windows tool) doesnt clean or avoid a problem like that, things that can not be undone. So if Adobe formally say that removing a part of the win install prior to the install then great, dont install office prior to premier, all well and good - but so far this has not been the case.
I came and commented on this forum for some idea of definitive solutions, even acknowledgment from Adobe would be nice before i commit to buying this significant upgrade from 5.5. At this point I can not see that Premier CS6 works with Sony .mts files and I cant tell why - so i wont be getting the upgrade or investing in the educational services for this (I am told) better product until I see that it is possible that it will work in my environment.
Just to add as a note,
Sont Vegas (understandably) works fine in the same enviroment and loads (the audio of) mts files (that dont work in CS6) quite ok. Adding extra software like this doesn't appear to fix or even help with CS6, so i am expecting their codec paths and logic work independantly of windows in general, do their own thing and thus the problem is within the app and configuration itself and less a related codec/app/patch/windows concern.
I have the same problem. . MTS H264 50fps with AC3 audio (Panasonic SD90). AfterEffects CS6 has exactly same problem with audio in this format. I read and tried all the recommended things, but no result (AVCHD structure, media cache, reinstal, antivirus...). CS5 and CS5.5 absolutely no problem. Please help. Thank you
Just following up with what we know so far about this:
It appears that these various failures with AC3 audio and MPEG-based video formats are related to a common cause: These codecs are unlocked for use by the activation system, which can fail for a few different reasons. The best way to restore the use of these codecs---which works in many but not all cases---is to manually deactivate your CS6 software (Help > Deactivate), then quit and restart your CS6 software, and then restart and re-activate, then create a new project and a new sequence.
If this doesn't get your activation back into the right state, we can try some other things. The experts on the activation system hang out on this forum:
... so you may get better help regarding activation issues there.
Sorry to dig up what seems to be an old question, but I've recently made the move to PPro after upgrading my PC in order to run it. However, I'm having the same issue with my .m2ts files and audio.
My rig: Win 7 Ultimate 64bit
120gb Intel SSD/1tb Samsung HDD
8gb RAM/ GPU GForce GTX560
My camara: Hitachi DZ-HD90
Audio bit rate 256kbps 2channel stereo 48kHz
The camera records in .m2ts files and the Hitachi software bundle can convert those files to h.264 (which are still .m2ts files, I think) or MP4 files which are heavily compressed and not usable.
I've tried all the suggestions above, but there's one thing I'm not really sure about, and that's the file tree structure that I'm supposed to save my footage in. I saw a screen shot of an example somewhere, but I'm not completely sure I've done it correctly.
It would be nice if I could just import the files directly off my camera though. The problem is, PPro only imports the video and not the audio track. I've copied the complete file structure from the camera itself to my PC's HDD and still, no audio.
Here's a screen shot.
Leo's information is far from accurate. Plenty of folks are using MPEG based footage inside of PP without issue. (In todays world of media, I'd even venture to say the vast majority are using some kind of MPEG footage.)
Now it would be fair to say that there are a number of people having issues with GoPro footage, which often doesn't conform to any established standard. You might try a forum search for GoPro and take a look at what others are doing.
M2V. M4V. M2T, M2TS and other Ms, exept MXF(Material Transfer File), this M formats, is variations of MPEG2 format , implemented by dedicated hardware, inside the cameras, and the video is encoded on the fly. The same occurs using AVC. But MPG is better.
Here we bougth CS6, bougth Rovi Totalcode,and other plugins, ( we spent about Us$3000) because CS6 do not have full support natively for MPEG2. we got very serious problems because of it.
After some months of sadness and frustrations, we return do CS5.5. Fortunately the plug-ins worked in 5.5.
Now we producing fast and well. No more CS6 here. In fact , in PP CS6 WITH ROVI TOTALCODE INSTALLED, MPEG2 works, but still have problems in dinamic link, in AA6 that do not import MPEG video directely, Encore have many issues... no no... Its terrible . ! We have so many problems here . No more CS6 for us.
In the future, maybe a CS7 version , returns with MPEG fully implemmented like CS5.5.
I know what i´m talking about.
I can not speak of many other people as you speak, because I do not know many other people who are happy and producing well with CS6, I can only speak for myself and my team. CS6 and MPEG format are to separated entities.
We work with post production, we have here 6 top notch machines ( four dual 16core opterons,128GB ddr3 ram, tesla and quadro running Windows8 pro and Two quad 16core Operons- 64cores, 256Gb ddr3, for 4K editting,running Windows server enterprise, converted to workstations becouse of 4P motherboards) and CS6 did not work well in none of machines. CS5.5 returns and is doing a great job.
So is not hardware issue. MPEG do not work well in CS6 , and CS6 is unstable in any configuration . We here use to say tha CS6 is still a Beta software with unsolved problems, that wont be solved.
Thanks Jim, but as I mentioned above, I've had no problems editing my GoPro footage.
My only concern is the .m2ts shot with my Hitachi camcorder. Even since my screen shot above, I've since tried moving all my media to my :c systems drive, but that hasn't worked either. Still, no audio tracks are appearing after importing.
because CS6 do not have full support natively for MPEG2
Actually CS6 does fully support standardized MPEG2 formats like XDCAM EX, XDCAM HD, HDV and Canon'x MXF files. I've even thrown quite a few Internet downloads into it without issue, including some with 5.1 audio.
This doesn't mean that every MPEG2 file will work, but the standardized camera formats should work just fine, no plug-ins required.
.m2ts shot with my Hitachi camcorder.
I couldn't find any standards associated with that camera, so it's possible it's shooting non-standard video. That could be an issue. If you want to upload a clip, I can check it's behavior here.
M2TS is a filename extension used for the Blu-ray Disc Audio-Video (BDAV) MPEG-2 Transport Stream (M2TS) container file format. It is used for multiplexing audio, video and other streams. It is based on the MPEG-2 transport stream container.This container format is commonly used for high definition video on Blu-ray Disc and AVCHD.
So M2TS is a stantard MPEG2 video file, better epeaking , the most recently MPEG2 implelentations . The full article discribing this specifications is here : https://en.wikipedia.org/wiki/.m2ts
In fact CS6 really needs of a MPEG codec suite, to be installed, to loan full MPEG support, furnished by Rovi.
We know seriously about this, because we passed trougth this storm last year. We spent a lot of money, the problem was resolved , returning to CS5.5.
OK OK OK ! Everyone is rigth . Here we´re wrong. Hitachi corporation is wrong, makiing the hayabusa´s camera that produces a MPEG2 file that CS6 "hate" ! The 40K dollars Sony camera we have , make a .MPEG file that CS6 "hate" , and yet these two companies decided to use non-standard file on purpose, so that users had problems many problems, to cause, delays, losses, hassles and all sorts of trouble with clients, losses contracts . miss schedules and so on. A jerky and flaw Encore to do not generate the DVDs, many PGC problems, and so on. OK.
OK. ADOBE is that it must be right, and the whole world wrong. Thank you. I know well what we here suffer with this CS6, and user Hayabusa knows what he is passing trough his CS6 do not recognises audio. The CS6 he have installed in his machine maybe other tha "hates" his audio files.Tje software "hates" us is the only explanations.
We do not try to use CS6 anymore. We knew what we being trough. many monts of sadness, frustrations, many many many redo jobs...
Maybe in the future a new version CS7 will solve problems and return with MPEG2 fully supported, as occurs today in CS5.5.
An editor who works here, once said, that seems to be "The curse of the even number"! Explaining : The CS3 version was very good. The CS4 came full of problems and unstable, as occurs today with CS6. The CS5.5 came and solved the problems of CS4.
Thus, the CS7 will come OK, no problems and everything is working to solve the problems of CS6 !
and yet these two companies decided to use non-standard file on purpose
It happens. But if you want to list the model numbers I can probably tell you if the media should work or not.
ADOBE is that it must be right, and the whole world wrong.
Well, not the whole world. Just you, or rather, your system. (Or you really are using non-standard media that PP just doesn't play nice with. But that's unlikely since you claim it works in 5.5.) For most folks, CS6 works just peachy with standardized MPEG media, no plug-ins necessary. Now the upside to that fact is that it may be possible for us to help you correct whatever is wrong with your system.
Maybe in the future a new version CS7 will solve problems and return with MPEG2 fully supported
It doesn't need to 'return' because it never left. CS6 supports at least everything CS5.5 did, possibly even more. There is a problem with certain spanned media clips that is new to CS6, but I suspect this is not what you're talking about.