50Mbps 4:2:2 from ClipBrowser 2

megabit wrote on 7/16/2008, 12:24 AM
Using the new ClipBrowser 2. 0 (http://www.sony.ca/xdcamex/software.htm)
- one can export to the XDCAM HD, 50 Mbps, 4:2:2 format. While the clip will open in Edius, Vegas does not recognize it at all - or am I missing sth?

AMD TR 2990WX CPU | MSI X399 CARBON AC | 64GB RAM@XMP2933  | 2x RTX 2080Ti GPU | 4x 3TB WD Black RAID0 media drive | 3x 1TB NVMe RAID0 cache drive | SSD SATA system drive | AX1600i PSU | Decklink 12G Extreme | Samsung UHD reference monitor (calibrated)

Comments

farss wrote on 7/16/2008, 1:40 AM
I doubt you're missing anything. As I pointed out here sometime ago Vegas cannot encode mpeg-2 at 4:2:2 so it's no surprise that it cannot read it. It's not like Sony announced their plans for XDCAM HD422 a couple of days ago either.

Bob.
megabit wrote on 7/16/2008, 3:32 AM
Bob,

Sorry I didn't quite get the meaning of your last statement. I guess the 50Mbps 4:2:2 has been long awaited; do you think Vegas will be supporting it soon - or did SCS indicated to the contrary?

AMD TR 2990WX CPU | MSI X399 CARBON AC | 64GB RAM@XMP2933  | 2x RTX 2080Ti GPU | 4x 3TB WD Black RAID0 media drive | 3x 1TB NVMe RAID0 cache drive | SSD SATA system drive | AX1600i PSU | Decklink 12G Extreme | Samsung UHD reference monitor (calibrated)

rs170a wrote on 7/16/2008, 4:41 AM
Bob, when doing an MPEG-2 encode from Vegas, if you select "High Profile" in "Profile" on the Video tab, you then have the option of selecting 4:2:2 as the sampling format in the Advanced Video tab.
I'm totally clueless about this though so I could just be babbling incoherently :-)

Mike
farss wrote on 7/16/2008, 5:34 AM
Sort of.
Not at 1920x1080 50Mb/sec High Profile.

I suspect what we need is the Studio Profile which goes to 100Mb/sec.

Piotr,
what I meant was Sony have had this HD422 @ 50Mb/sec XDCAM planned for over a year. So it should be in Vegas already.

Then again looking at how the limitation works in the encoder settings it could well be a licencing issue. If it's not then a bit of work went into implementing the limitation for no good reason.

Bob.
megabit wrote on 7/16/2008, 6:24 AM
Thanks Bob for the clarification. This worries me, in the context of the Flash XDR /NanoFlash 50 or 100Mbps HD422 output :(

AMD TR 2990WX CPU | MSI X399 CARBON AC | 64GB RAM@XMP2933  | 2x RTX 2080Ti GPU | 4x 3TB WD Black RAID0 media drive | 3x 1TB NVMe RAID0 cache drive | SSD SATA system drive | AX1600i PSU | Decklink 12G Extreme | Samsung UHD reference monitor (calibrated)

owlsroost wrote on 7/16/2008, 11:12 AM
I just succeeded in creating a 1920 x 1080, High Level/High Profile, 4:2:2, 50Mbps MPEG-2 encoding template in VP8.

It seems you have to change the settings in the correct order - I picked a 1920 x 1080 Blu-Ray template as a base, then changed (Video tab) Profile -> High, Level -> High, (switch to Advanced Video tab) Sampling format -> 4:2:2, VBV Buffer size -> 1194 (guessing here), (back to Video tab) Bitrate can be set up to 80Mbps!!

Playing back something encoded with the template, the FFDshow MPEG decoder OSD reckons it's 1920 x 1080, 422 colour space @ 50Mbps so it appears to encode correctly (and loads on the the VP8 timeline too...)

Tony
megabit wrote on 7/16/2008, 11:33 AM
Yes, I managed to encode a HDD422 from an EX1's HQ mxf as well.

But - due perhaps to some single, stupid flag or lack thereof - the same format created by the Clip Browser v2 is not understood by Vegas!

AMD TR 2990WX CPU | MSI X399 CARBON AC | 64GB RAM@XMP2933  | 2x RTX 2080Ti GPU | 4x 3TB WD Black RAID0 media drive | 3x 1TB NVMe RAID0 cache drive | SSD SATA system drive | AX1600i PSU | Decklink 12G Extreme | Samsung UHD reference monitor (calibrated)

PeterWright wrote on 7/18/2008, 12:40 AM
Just started a new thread (now deleted) before I spotted this one.

The best new features for me are the abilty to set in and out points and renaming clips before exporting to MXF.

edit - Well I thought that was possible, but exporting to MXF changed the name back to the original name - maybe I've missed out a step - can't see the point of renaming in Clip Browser only.
megabit wrote on 7/18/2008, 1:00 AM
Well I thought that was possible, but exporting to MXF changed the name back to the original name - maybe I've missed out a step - can't see the point of renaming in Clip Browser only

Same with user's comments to clips - they never make it to NLE (not Vegas at least). Also, the Media Markers don't display the RecStart label...

AMD TR 2990WX CPU | MSI X399 CARBON AC | 64GB RAM@XMP2933  | 2x RTX 2080Ti GPU | 4x 3TB WD Black RAID0 media drive | 3x 1TB NVMe RAID0 cache drive | SSD SATA system drive | AX1600i PSU | Decklink 12G Extreme | Samsung UHD reference monitor (calibrated)

ForumAdmin wrote on 7/22/2008, 8:29 AM
XDCAM 422 will be supported in the next Vegas update, 8.0c.

If you are shooting/importing from the EX, there is no point in converting to 422 MXF- just choose MXF and don't change the bitrate- all the shooting modes of the EX will open in Vegas 8.0b.

megabit wrote on 7/22/2008, 8:39 AM
If you are shooting/importing from the EX, there is no point in converting to 422 MXF- just choose MXF and don't change the bitrate- all the shooting modes of the EX will open in Vegas 8.0b

Sure thing - I just wanted to test the HD422 format before I start using the Convergent Design's nanoFlash recorder...

Good to know Vegas 8.0c will support this - thanks!

AMD TR 2990WX CPU | MSI X399 CARBON AC | 64GB RAM@XMP2933  | 2x RTX 2080Ti GPU | 4x 3TB WD Black RAID0 media drive | 3x 1TB NVMe RAID0 cache drive | SSD SATA system drive | AX1600i PSU | Decklink 12G Extreme | Samsung UHD reference monitor (calibrated)