This content has been marked as final. Show 19 replies
I have never heard of the "some" codec
First, work through the steps here http://ppro.wikia.com/wiki/Troubleshooting
If your problem isn't fixed, report back with the DETAILS asked for in the 16 questions at the end of that link
For question #1 see the note about the FREE http://www.headbands.com/gspot/
I think it was Dan. Mainconcept sent him some beta materials and he said....
Now that's some codec!
Well fine. I have more data, I didn't follow all of the steps but I tried a different file and it did get the file dialog to display when I attempted to encode it.
So I played around with the original project, made a new project, put my original file in the new project and then the encoder worked just fine.
So clearly the logic path here is:
1. Install software
2. Import some video
3. Try to run media encoder
4. Waste 3 hours of your life messing around and doing research
5. Get wise *** on forums to SHOUT at you even though you did more research than most people would have
6. Play around some more and realize that the broken as always Adobe Media Encoder was just being dumb like it always was in 1.5
7. Abobe, Fail.
Number 2 may be your weak point. Premiere generally works best with certain kinds of media. Many other kinds just don't work very well, as they're not really designed for editing to begin with.
In general, stick to DV video for standard definition work.
Yeah no question. The video in question came straight off the hard drive of my DCR-SR65 as an mpg. So while not a professional source its also not an ancient or out of date source of DV.
It is no DV. It is material meant for watching, not editing.
>its also not an ancient or out of date source of DV.
DV and it's variants are still the standard for SD acquisition and editing. They will be replaced by HD formats, but will likely never be replaced by any SD MPEG variant, despite MPEG cameras being "newer". That's because the GOP structure of MPEG makes editing difficult.
Like Harm says, it works well for watching, but not so much for editing. Pros understand this. Usually it's the consumer who gets into trouble trying to edit MPEG, for which the general recommendations are to switch to a DV camera, convert your video to DV before editing, or use consumer software to edit with (which often handles consumer media better than Premiere Pro).
So given that I've been editing video off and on for 18 years and am quite familiar with PP 1.5 and as such wouldn't consider consumer software, and a new camera isn't in the cards right now, what's the best way to convert to DV and what's the best format?
I assume that simply exporting the mpeg as avi won't cut it "Export > Movie"?
I figured this out out of pure luck!
You cannot export through adobe media encoder with a "/" in your timeline name or probably any other character not allowed by the system file names.
b Adobe, this is a bug because you need to inform to your users with a dialog box that there are characters in the timeline name that are not allowed by the system. Either that or do not allow timelines to contain special characters not allowed by the system naming convention. This simple dialog would have saved me and my clients headache and 4 hours on this unique crash deadline.
This is utter BS! Do you expect Adobe to warn you that you should not perform illegal operations, like throwing your laptop out of a 6-th floor window or washing your workstation in the bathtub with the power cord in the outlet?
i "I reserve the right to call anyone a noob. Especially if you haven't read the f... manual!!"
Cliff, a problem like this is not generally considered a "bug" as such, but a feature request. (I can argue the other point of view, since no error message is generated.) But you can submit it as a bug report or as a feature request.
In any event, since CS4 is out and Adobe will not fix this in CS3, the first question (for someone with CS4) is whether CS4 behaves the same? (I don't have CS4; any taker?)
After Effects used to give you a warning (long time since I have seen it now, maybe in the days of v5.5) that a file name (if one used that fell under the criteria) could give you problems if used on a MAC.
I guess it can't be hard to put in a check on names, and it maybe should be done. People have gotten used to all kinds of naming now a days, like "From my vacation 2006.My mother not happy.jpg" (loooong names with spaces and dots (plural), and almost whatever else).
Anyway, what I think is "utter" wrong, is that the programmers allow naming that's not compatible with the operating system that they certainly use parts of for getting the job done.
Oh gosh how much I miss DOS, every program had to be self-contained with every little driver for everything, well, at least almost.
I have to agree this is more user error than a bug.
First thanks to everyone who has gone before me on this issue. I just ran into this problem for the first time.
I prepared a sequence named "Welcome/Intro" when I tried to use the media encoder I had the same problem discussed here. I do think that at least an error message would have been appropriate here. For the screen to just flicker and return rather than display the "File Dialogue" is really difficult to trouble-shoot. If I hadn't found this post I'd still be baffled. I have used PP for years and have never seen this issue before - I don't recall if I ever read about "forbidden" characters in Sequence Names.
Additionally because you can re-name the files you are exporting once you get the "File Dialogue" it seem that Adobe PP could allow you to progress to the dialogue screen and then allow the windows "invalid file name" error to handle the issue. Well, thanks to everyone again. I have not up-graded to CS4 - yet. I really would be interested to know how it is handled there - not that I'll ever use the "/" in a sequence name again.
If you can't see the file dialog box, that means perhaps the dialog box is out of the windows desktop, you can try to connect a second display if it's possible with your graphic card.
For me, my bug with media encoder appears only when I want to creat a WMV file. Premiere or After effects always crash with this codec and here is the error signature :
AppName: adobe premiere pro.exe AppVer: 220.127.116.11 ModName: msvcr80.dll
ModVer: 8.0.50727.762 Offset: 00008a8c
I have already uninstall and install again all the productive suite(also quicktime), but it changes nothing .
My XP system is 64bits, do I need a 64bits package?
I'll try to find it and tell you back.
thank you for your advice.