Kieran Matthew
Forum Replies Created
-
Hi there,
Could you give us some more info on your set up?
Firstly are you PAL or NTSC? How are you monitoring the outputs, (monitor, deck etc)? Are you using a junction box or a Medusa cable (loads of cables from a single connector)?
You mention that you can’t access the DV output. Media 100’s only output to the firewire port on the card, and only when mastering, and then only if you tell them to. To test this try mastering to tape with the machine control set to none, and with the DV checkbox on the master to tape window on. This should enable that output.
K
-
Hi Bob,
Just a quickie – FCP can run on the HDe hardware so you can have the best of both worlds. and the good news is that it doesn’t work out that much more expensive than buying the hardware alone for FCP.
K
-
Hi Greg,
What exactly does the problem look like? Can you post a short segement?
I assume by jump you mean “one-minute black, next almost full video”, rather than the usual stepping you get from viewing interlaced MPEG2 fades on a progressive computer screen.
Are there any other problems with the video?
K
-
Hi Greg,
Studio RGB scales the levels of Media100i’s legal range (16-235) with black at 16 and white at 235 to meet Apple’s prefered RGB (0-255) range with black at 0. This was crucial when using Media 100i’s codec, but with the other codecs available in HDe I’m not so sure – Perhaps Floh can jump in here?
Using the Studio RGB button on media that is already 0-255 might have clipping effects like you decribe as the early stages of a fade would be crushed to the same level and create a jump. That said, I’m speculating here so experimentation is the key.
I do remember something being said about Media 100 changing the quicktime export to Apple colourspace rather than the usual media 100 colourspace, but I didn’t think that affected “by-ref”.
K
-
Hi Jim,
Is everything OK if you set in and out TCs and batch digitise the media?
I’m a little confused though, you say that it never stops digitising, but then say it stops on timecode breaks – isn’t the end of the tape registered as a timecode break, or is the never stopping then crashing problem a duration related problem?
K
-
Hi Greg,
Which codec are you using and how are you exporting it?
Is the problem evident if you play back the m2v file from bitvice in QT before DVDSP gets hold of it?
Just a thought, when you encode with Bitvice, is “use studio RGB” enabled? If so try encoding without it. I’m wondering if this is a black level clipping issue.
K
-
Hi Greg,
If you can, go for an SDI monitor. Not only is the picture quality better, and less susceptible to interference noise, but it also frees up your component out for your SP machine.
K
-
Plus, you can also run FCP on the new Media 100 hardware giving you the best of both worlds.
K
-
Hi Greg,
The big thing is there are many flavours of HD out there; which one they are planning to use will have a bearing on your questions.
That said the obvious answer is yes you can do the edit (in either M100 or FCP which may handle the multicam better).
Editing in HD will eat disk space and that may be a factor, but as the end product at this stage is SD DVD you could always edit in SD using the downconverts from the deck, keep the timelines etc, and then reconform in HD when the client needs it (by which time the disk space needed costs a lot less than now)
If you are editing in HD, your HDe will downconvert to SD for monitoring. Many people monitor the edit in SD until the finishing stage and then hire a calibrated HD monitor. (I have been looking at the various HD-SDI to HDMI converters as an option for monitoring HD on a domestic LCD HDTV, but at the mo, these seem only to be useful for client comfort viewing)
As for decks, hiring is still IMO the best option. That way you always have the right deck for the job and it is always fully-working and properly set up. Unless you have a need to use a particular format day-in-day-out (HDV springs to mind) I’d avoid trying to buy a deck at this point.
K
-
Hi John,
The drivers for your model are available on the keyspan website
https://www.keyspan.com/downloads/
However OSX 10.1.5 isn’t listed as supported so that might be why Keyspan told you it was too old. You can use OS10.2.8 with your set up if that is the problem, updating to 8.1.1 which is free.
Hope that helps
K