Adrian Sancho
Forum Replies Created
-
Unfortunately YouTube is a moving target. There used to be information that would allow you to make an .flv file that would load directly into YouTube without re-encoding, but I believe that information is no longer valid.
Your best bet is to make the least compressed file you can make that still meets the 1 gig file size limit and upload that. Don’t forget your audio compression. Don’t set it too low or you may wind up with decent imagery but ratty audio. I’d try 224k or higher if you can afford it (file-size-wise). 1280×720 is YouTube high def format, so encode to that size.
It doesn’t have to be an .flv file either. Whatever format you can make that YouTube will accept that gives you the best overall quality will do.
-
Make sure your fields settings are correct. If you use the wrong one you will get jerky video. It will probably be exaggerated by the MPEG compression.
I’m still at a loss as to why I’m getting it with 30fps progressive footage tho.
-
Well, it may be free, but what’s it going to cost you to get capture gear? If you have to go out of your way for it, it may be cheaper to get a cheap DV camcorder.
Actually, one simple solution is if you already own an SD Mini-DV camcorder. Most of these have the ability to digitize analog signals on to Mini-DV tape. I would say if you already have one of these, or have readily available access to one, then all you need is a Fire wire or USB 2.0 interface (depending on the digital camera) on your computer and you’re in business.
Under good lighting conditions the signal can be useful. I once did a 3-camera shoot where one camera was a C-VHS unit and the other two were SD Mini-DV camcorders. I digitized into one of digital cameras and sync’d everything up for the timeline. While anyone who works in video can see the differences, most viewers usually won’t (and didn’t, on this project I was involved in).
So if you can make use of it for next to zero investment costs, then I say go have a blast with it.
-
Man, Adobe really screwed this program up, didn’t they?
-
I used to have a similar problem exporting mpeg files in quicktime pro to either an .mov or other format. Some other programs wouldn’t see it either. I believe it has something to do with the way the audio is multiplexed with the video.
My solution was to use TMPGEnc mpeg encoder to extract the audio from the mpeg file and save it as an uncompressed .wav.
If you think you might want to go this route, you can get a free version of the encoder here:
https://www.tmpgenc.net/en/download.html
This version needs no installation. Unzip to it’s own folder and run.If you need to read a quicktime file into TMPGEnc, you’ll need to install this plugin for it here:
https://www.moviecodec.com/downloads/363d.htmlUnzip the QTReader.zip file and put it in the TMPGEnc folder.
Load in your mpeg file into TMPGEnc and click ES (Audio only) in the STREAM TYPE. Click the SETTINGS tab and choose Linear PCM. OK that, set your output destination, and hit the START button.
I’ve placed a screen grab below to show you. You may need to click it and possibly expand it’s viewing box to see sufficient resolution. This is a screen grab of both the main program window on the left and the audio settings on the right.
After writing all this I didn’t think of whether you are on a MAC or not. Hopefully not. 🙂 Well, hope this helps.
-
I’m seeing that in 30 fps progressive pans made from stills. I see it after the footage is compressed. I’m making h264 quicktimes. Something in the GOPs, maybe. What is you final output medium?
-
I guess that’s all fine and well if you work strictly with the CS3 suite, but I have a multitude of programs, audio, video, 3D, compositing and multi media support software, and there’s no way in hell I’d be reinstalling all that just for a program upgrade. I don’t work with a “suite”, so I guess if you do so, then such an option may be viable.
I don’t have any problems with my system or any of my other programs. The problem for me lies strictly with this Adobe Encoder. Even Premiere itself works fine, save for some comical legacy dysfunctions. Some things will never change in Premiere. As you’ve mentioned, the Adobe Encoder is version 1.0, so perhaps in the future it may actually work, but it doesn’t work now. At least not for me.
Adobe must know this program is dysfunctional, because they’ve gone out of their way to leave the internal renderer in AE. AE is far more professionally used than Premiere, and they know they can’t afford to cripple it’s rendering pipeline. At least AE has been spared the agony of this beta code. Otherwise combustion would probably render faster! That would be an embarrassment they could never live down. 😀
-
>>Yes, there’s a link to codec settings on each file listed and should open on a new window. << Oh it's there alright, it's just grayed out, along with the keyframe settings. >>If not, it sounds like you are having some serious software issues…<< Well, with the Adobe Encoder, yes. The rest of my programs work perfectly fine. >>…and might need a fresh OS and Adobe install, which should be done for every new version.<< With all due respect, where did you ever get this advice from? I've never heard of anything so drastic. Install the system from scratch just to install a new version of a program? You do this for every new version of a program that you update? Hopefully I can find a version of Premiere CS3 I can perform some tests with. Otherwise I need to look at alternative editors. It's too bad because I'm pretty satisfied with this latest version of Premiere. Hopefully the CS3 version will be fairly close in capability. I'm not impressed with this Encoder, to say the least. I could care less about it batch rendering processes. You can probably get a Python, Perl, or VB script written that can do a far better job of it. >>…I still think they should leave the old export as well, just like After Effects…<< So are you saying that AE CS4 can bypass this mess? That would be very hopeful, at least for AE.
-
This entire Adobe Encoder idea is one sad fiasco. The more I use it, the more I hate it. I just discovered is doesn’t allow access to codec settings. I went to create a Quicktime file and realized I had no access to audio and video codec quality settings. No access to setting keyframes either.
My only option was to render a full uncompressed Quicktime file (which is huge, needless to say) that I then open and finally export in the Quiktime Pro player using the proper target codec settings for audio and video.
I would like to know WTF Adobe was thinking about when they created this thing. Useless crap.
-
>>I’m afraid premiere isn’t the best with the way it handles graphics/photos but then maybe that goes for other nle’s as well.<< That hasn't been my experience. However, all of you are getting thrown off-base by the fact that I'm using higher-than-project res stills in this particular project. I did an earlier project with SD DV video and SD res stills, the stills were not scaled or panned, and that render was just as choked. The problem, as far as I can tell, is the encoder. As I've said earlier, I've done similar projects on much slower machines using earlier versions of Premiere and other NLEs and I have never seen such system choke. Ever. I will check out that XML setting to see if it makes a difference. I'm not exactly sure where it is, but I dig around. Thanks for the tip.