Kieran Matthew
Forum Replies Created
-
Hi Dave,
Apologies for my tardy reply.
Thanks for the info. Problem is I just seem to get green when I do the Boris as a filter thing.
Any ideas?
K
-
Hi Greg,
Does the video play OK if you render the title?
K
-
Hi Bob,
I don’t know if it qualifies as the best, but you could always export out as Quicktime with the codec set to ‘None’. This should open in anything – but be prepared for big files.
One thing though, you will never really escape Media100’s colourspace (the thing that gives the odd levels in FCP) and field order unless you use a tool like Boris, AE or Cleaner to change the, as you convert the Media 100 file.
HTH
K
-
Hi Bmoneymedia,
I doubt that the issue here is set-up as that is something in the analogue rather than digital domain. It is more likely that the encoded video needs to be within a specific RGB range to look right.
The Media 100i codec uses the RGB range of 16-235 for legal video with black at 16. Apple generally uses 0-255 for legal video with black at 0. A big difference, and one that will result in milky, low contrast images if the playing system was expecting 0-255. There is also gamma to contend with, and field dominance might rear its ugly head.
The adjustments you need are best achieved either, as Gary mentions, by doing a level adjust within Media 100 using colour Fx or Boris FX, or when you encode in Episode.
Anyway. What would really help here is if you could actually list the DG Fast channel spec/requirements so we can best advise how to correct for them. Post a link to a web-page if necessary.
K
-
Hi Gary,
Off the top of my head, there are two ways you can get around this,
1. render a title over the top of your video with the render codec set to one of the DV codecs. You can then export by reference without the colourspace jumps, in a form that compressor likes. Chapters can then be enabled in the usual way.
2. Export by ref and use QT to strip out the chapter points as a text file. After a quick touch-up in text-edit to change .’s to :’s, this file can be imported into DVD SP to add chapter points to a track made from the chapter-less QT file.
There are other ways, but I can’t think of any at the mo.
HTH
K
-
Hi Floh,
Thanks for that, I’ll give it a go
K
-
Hi Bmoneymedia,
It really depends what you want the media file to be.
If you want the media stored in a cross-platform, high-quality form that can be used for anything, then you could try exporting out as as an uncompressed Quicktime file (compression set to ‘none’) – though this will result in a big file that has media 100’s colourspace locked into it. Of course you could always just keep it in the Media100 codec by exporting out as a self-contained file.
If you want a high-quality but small file that can be played on the desktop to show clients, or FTP’d somewhere then I would suggest QT7’s H264 MPEG4 codec. If PC usage is important and you don’t want to depend on clients installing QT, then try WMVs.
I do think though that a one-size-fits-all approach may not work, and you may end up with different versions for different tasks. I always seem to end up keeping the media, a self-contained export, an MPEG1 (my clients love them for some reason), a WMV, a QT and more often than not an MPEG2. I am hoping MPEG4 will replace most of these though.
HTH
K
-
Hi David,
[David C.] “It’s important to note that this release does not work with Apple Computer’s Leopard OS or QuickTime 7.3.”
Leopard asside, does QT7.3 break v11, or is it just v12 that’s affected?
K
-
[Floh] “Which analog outputs are you using?”
The XLR outputs for testing, Phonos for monitoring. With -18 db tone running, the PPMs show +5 rather than +4. Lowering the tone (or bus) by 4db brings the PPMs to +4 again.
Also testing the Firewire audio out. about -10 tone reads at about -6 on my DSR-40 which doesn’t give you control over input levels over firewire. This has to be taken with a pinch of salt as there is no common graticule between Media 100 and the DSR-40 and the 40’s level meter is very crude.
Thanks again for your help
K
-
Hi Floh,
OK, I’ve done some more tests and I’ve made a mistake on one of my claims. The -18 db tone does not read -18 in STP or other apps, so you are right in that Media 100 uses a different definition of zero db than say FCP or STP. Apologies.
That said, it does still seem to get louder when exported out of media100, plus the audio starts to clip on the media 100 timeline at lower than 0db – around 3-4 db lower (which equates to 0db in STP), so there does seem to be something amiss here.
Any further thoughts?
K