[Eric Pelletier]

Here it is :

https://forums.creativecow.net/readpost/4/862276

[Eric Pelletier]

In fact, the 720 format is what’s called NTSC 601. 640×480 don’t really complies with the standard. On it’s Website, Media 100 states the following :

«
A Note About Mac OS X 10.6.8
Apple released the Mac OS X 10.6.8 update in June 2011. A bug in this update disables playback with the Media 100 i Codec in NTSC 601 format. We are working with Apple to find a solution but the eventual outcome is unknown. We recommend that you not install the 10.6.8 update if you have existing i Codec media.
A Note About Mac OS X 10.7 “Lion”
Apple released the Mac OS X 10.7 update in July 2011. A bug in this version disables playback with the Media 100 i Codec in NTSC 601 format. We are working with Apple to find a solution but the eventual outcome is unknown. We recommend that you not install the 10.7 update if you have existing i Codec media.
»

I understand you’re using 10.5.8, but if you updated your Qt version, this one broke the M100 NTSC 601 codec.

I kind of remember Floh posting a solution to downgrade to previous QuickTime version…

[Eric Pelletier]

If I may,

NTSC or PAL PSF Program.

Let’s say I put in a progressive file (that I know is progressive and PSF fast imported in a bin) that mixes (fast dissolve) with an interlaced file (fast imported).
Add on top a Boris title, in which I import a logo (simple white logo with a 75% opacity, fixed position and fixed scale). Save. Back in M100, real time logo looks fine. Render it, even uncompresssed, and jagged edges show up. Obviously, square logos are not affected but the ones with curves suffer.

I could do the same thing in 601 Program, with nice rendered results.

Basically, in my version, it seems that Boris just doesn’t understand PSF or Progressive titling…. but as I said before is PSF/Progressive SD program a standard? As far as I know, it’s not. I might be from the «old school» but SD is interlaced with 4×3 or 16×9 anamorphic. Nerver experienced such problems with HD, though I always work interlaced 1080i.

Thanks for reading us.

[Eric Pelletier]

Good question for FCP or After Effects Boris users, i guess. I’m not a Boris user outside M100.

Maybe this PSF type of Timeline (Progressive Segmented Frame) is not compatible with Boris.

In media 100, PSF Program doesn’t make your footage progressive. You could put any progressive or interlaced footage in a PSF or 601 Program, as long as you stick to NTSC or PAL with proper frame rate, aspect ratio, etc. In this case, progressive footage aired from a 601 timeline will look strange (not to say broken) as well as interlaced footage interpreted as progressive in a PSF timeline. This being said, in Suite 1.1.3, Boris doesn’t always let the user specify how the media should be handled (Progressive, PSF or interlaced-601). I can’t tell for latest versions, though.

But I think it doesn’t really matter as long you going along with standards to broadcasters. The problem is for computer outputs, where your end results should be de-interlaced. And since you may have Progressive AND Interlaced footage in the same Program, well, you can imagine.

[Eric Pelletier]

I applied a comp layer, put some animated movs in the background and logos & text in the foreground, like a thousand times before. Looks good in RED, looks good in Media100 before rendering.

One thing I realized over time – if it can help – BORIS does not really work in Progressive, is your timeline progressive? Honestly, I don’t know RED5, never worked with that. I work SD and HD on 1.1.3 – still – and my progressive videos look nice SD or HD in the timeline. I often put a logo overlays or text in BORIS. They look fine unrendered. But as soon as I render these titles or comps, the edges are not crisp, not anti-aliased. My workaround? No matter what my sources are, I work interlaced (not progressive). But it also depends what your Broadcast support is, but for me, going on TV, progressive material IN BORIS is nice only when interlaced.

Maybe you want to try changing project or files settings you use in BORIS into progressive, if needed.

[Eric Pelletier]

I’ve been dealing with this for a long time now, even in earlier v.8.

One thing you can try, is to place (position value) this text at a «rounded value» (no decimals) on the odd or even field (depending, probably, on your format PAL or NTSC). I think, if I remember, NTSC would require and odd value on the vertical (y) (ex. Position y : 399.00). You can also be aware of codec compression. Is your title fine when you look at it unrendered? Try uncompressed to see if it doesn’t help.

[Eric Pelletier]

I think I’ll go first with v2 trial on second computer.
But still, if Mr. Slenker succeeds with 1.1.2… There is something wrong with mine. Or maybe it depends on the source.

Better work around though now (quality wise), I bought Calibrated softs MXF Importer AND DVCPRO HD Decoder.
That allows me to drag and drop files onto a bin and set import settings to 1080p29,97 as DVCPRO HD, small upconvert but still good quality.
I could not read MXF wrapped (?) DVCPRO HD from the source without the Calibrated Decoder. And could not import complete files without buying the MXF option.

Still I thought it would help M100 P2 Importer feature, but nope.
I’ll send you a file if no success with v2.

Thanks

[Eric Pelletier]

Maybe I can help.
But recovering the data and viewing it in Quicktime doesn’t mean it could automatically be relinked to Bins and Programs.
I might be wrong but I think that Media Index has to be recovered as well.
I guess it’s worth trying but most likely, without the Index, the program would have to be rebuilt manually.

Eric Pelletier
ericpelletier@dynamikmedia.ca

[Eric Pelletier]

Exporting . yes 🙂

By the way SMIQuickTimeExportComponent.component appears to be installed along with Sorenson Squeeze. Just installed it recently. Doing a search in Google about this extension and found out about problems with Producer 13.x and Final Cut Express…

Took it ouI but don’t know how it will affect Sorenson behaviour.

More fun to come.

[Eric Pelletier]

I found something very interesting.

Export File Crash topic
brought up in this Forum by Gregg Michaels on Jan. 28 2010.

Media 100 found out about SMIQuickTimeExportComponent.component causing a problem.

Today I can reconfirm this.