John_Berger
Senior HTF Member
- Joined
- Nov 1, 2001
- Messages
- 2,489
So, what would the purpose be for these? Just possible compatibility for future use?always said:Quote:
So, what would the purpose be for these? Just possible compatibility for future use?always said:Quote:
So, what would the purpose be for these? Just possible compatibility for future use?HDTV is 16:9 but it also has square pixels. I suppose either "1" or "3" could be used for that. The HDTV standards documents show that both are valid, which means HDTV decoders need to know how to handle both. And 1:1 could be used for nonstandard resolutions which are neither 4:3 nor 16:9.
The 2.21:1 aspect ratio could be nifty for putting the "anamorphic squeeze" on HDTV resolutions in the same way that 720x480 which was originally intended for 4:3 is made to do 16:9. But 2.21:1 isn't included in any HDTV standard. Just for kicks I gave it a try with PowerDVD and it just reverted to 4:3 mode.
Exactly. Just a little checkbox that says "I don't care what my sequence header tells you, I'm supposed to be 16:9." Like I said, Sonic Solutions is just way too inflexible.That also doesn't say very much about the various video editing packages, like Media Studio Pro or Adobe Premiere, who still don't offer 16:9 flags. (Then again Premiere can't even handle MPEG-2.)
Looks like I'm going to have to pull my Perl for Dummies book out and dust it off.
(Then again Premiere can't even handle MPEG-2.)Premiere is meant to be a full-frame NLE package, ULead Media Studio is aimed at the amature. Since MPEG does not contain all of the frames, it works totally differently than Premiere is designed to.
Remember, maybe 1 in 6 frames actually exist in an MPEG file. There are 3rd party plugins to let Premiere read MPEG, but I have yet to find something that really works well.
There are 3rd party plugins to let Premiere read MPEG, but I have yet to find something that really works well.That explains some things. Since I don't work with AVIs **shudder** I couldn't get into Premiere.
I really like Media Studio Pro 6.5. I handles MPEG-2 files natively through Ligos without the need for plug-ins.
It does have its quirks, such as it's not too pleased if you mix and match source MPEG-2 files of different bit rates, and it definitely prefers WAV audio as opposed to MPx audio, but when you learn to identify and get around the quirks, it's fantastic. I'm really pleased with it.
If you're having problems with MPEG-2, you should give MSP a shot.
I don't work for them. Really. Just basing it on what I've done so far.
I don't do MPEG until I'm done editing. I capture and edit in DV format.You know, I've tried that and I've found it to be so bad to work with. I've actually had far, far better quality capturing 720x480 MPEG-2 at a nice high bit rate (usually 10,000 video, 224 audio) than raw DV AVI files. Between the blockiness and the enormous file sizes of DV AVI, I gave up and went back to capturing in 720x480 over the S-Video connection on my DV camcorder. I'm much happier doing it that way.
Maybe it's my capture software or something. Are you using a Mac or PC? From what I understand DV on PCs generally use the Microsoft DV drivers, so I'd be surprised if you don't get the same kinds of DV glitches that I do.
Ask any pro, they don't go MPEG until the final stepWell, I'm not a pro, so I'm not going to worry about it. At this stage, I'm a-just havin' fun!
Am I reading right? Are you saying Ulead Media Studio can't encode MPEG-2 with the 16x9 flag set? Because I've done it a number of times (MSP 6.0); it works just fine, and once the flag was set, DVD Workshop imported it without gagging and the resultant .iso image ran as 16x9 (I'll be honest and say I don't have a DVD burner, so I haven't tried that final step).WHAT!?!SON-OF-A-BI**H!!
Even Ulead's own tech support people say that 16:9 is not implemented and is currently a tentative function for MSP 7.0!!
Excuse me while I climb the walls now.
Okay, I'm better.
I will DEFINITELY work on this over the weekend! I'll be very pissed and elated at the same time if this works. Considering that it works with 6.0, I can't imagine that it wouldn't with 6.5.
If worse comes to worst, I still can fire up a Perl script to change the flag like I had been planning on doing, but if that INI change is all that is needed, Ulead will not like the e-mail that they're going to get from me.
Thanks for the info!
I've read that if you want to shoot true 16x9 material on a DV-camera, the camera has to use a CCD with those pixel proportions=a wider CCD than 4:3There may be a practical reason why that is the case, but in theory, you could do what they do for film: use a lens to squeeze/stretch the wider image so it fits on the CCD. If we had a whiteboard, this would be easier
The CCD has 720x480 elements. They are arranged in a grid so that they are 4:3. Note that 720x480 is actually 3:2, so the elements are not in a square grid, they are closer horizontally than vertically. For filming 4:3, the undistorted optical image comes through the lens and strikes the CCD and is recorded.
For 16:9, you could use an additional lens just before the CCD that squeezes/stretches that wider picture onto the same 4:3 CCD.
I say "sqeezes/stretches" because it depends on how the 16:9 mode works on this hypothetical DV camera. If it actually shows more content on the sides, then it would squeeze horizontally. If it crops the top and bottom, it would stretch vertically. But in either case, the full resolution of the CCD (and therefore the DV frame) would be used. ("Fake" 16:9 modes simply mask off pixels on the top and bottom.)
Those light-sensitive elements on the CCD are just like the pixels on the DVD frame. They take the image, 16:9 or 4:3, and divide it into a grid that's 720x480. Either way, the pixels are not square.
//Ken
The fact that you have to go through such a manual rigamarole to get this to work implies that it's either a an unsupported feature, it's buggy, or Ligos forced them to disable it for some reason.I don't care if it's unsupported as long as it works. And if it doesn't work, I can still run it through a quick Perl or shell script to switch the repeating 4:3 flags to 16:9 flags. I can't imagine that Ligos stopped them because this is a flag that is built into the MPEG design and is NOT any kind of proprietary Ligos code.
Of course, that doesn't forgive the people at Sonic who could have just as easily added an option to convert the flag to 16:9 when re-muxing the DVD.
I can deal with the stretched-looking 4:3 frame while working on the video files, as long as I'm sure that the final result when the disc gets popped into the DVD player is the result that I want.
If it actually shows more content on the sides, then it would squeeze horizontally. If it crops the top and bottom, it would stretch vertically.The main gripe that I have with supposed "widescreen" 16:9 functions on DV camcorders is that they actually crop the top and bottom then stretch the image vertically to simulate 16:9. I checked the 16:9 function of at least three different top manufacturers, and all of them were "fake" 16:9. Bastards.
I actually have a Sony 8mm camcorder that does true 16:9 widescreen (more image on the sides), but being 8mm the picture quality is nowhere near as good as DV.
on.I'll be damned! There it is! YAHOOOOOO!!!!
The file was different with mine. It was the msp.ini fies that was embedded in Cocuments and SettingsAll UsersApplication DataUlead SystemsUlead Media StudioPro6.5 . I'm guessing the directory location is because of Windows 2000, but the file is most likely a new MSP design.
But there it was, plain as day. You know, is it so difficult to either mention this sh*t or at least be honest about it when someone asks?! I'll be writing that snotgram tomorrow. There is no reason why this information should be hidden away, particularly when it was available on a previous version as well!
Well, at least MSP can handle MPEG-2 without the need for an unstable plug-in! {coughPremierecough}
Thanks a bazillion, Aaron!