Kieran Matthew
Forum Replies Created
-
Hi Chris,
Apologies, I have just returned from a break. Do you still need info on this?
K
-
Hi John,
Do you have any more info on the portable media 100 system? I remember seeing a photo of it back in the day (cardbus expansion chassis and laptop?) but haven’t been able to find any info about it!
K
-
Hi Ajmetz,
The problem is interlace noise as you suspected. It can be solved by engaging the “1:2:1 deflicker” option in the local project settings of the Boris Preferences pane. The picture gets a little softer but you lose the flicker.
In some cases I find the softening actually improves the feel of the picture.
Hope that helps
K
-
Hi Chris,
Apologies if this is old news, but if this is your first time mastering to a deck via SDI and you’ve previously only used the analogue component cables, then the only issue to watch out for is legal levels.
The analogue outputs clamp the video to legal range effectively legalising the output. The SDI connection is full range so you can output illegal levels very easily. If the master is for broadcast you can either legalise in the software, use an outboard legaliser, or as I have done on many occasions, connect the digibeta deck via the component output.
Obviously if the master isn’t for broadcast, or the client doesn’t have the requirement, then as Floh says the Digibeta is just another deck.
K
-
Hi Chris,
Could the cameras be expecting HDV instead of SD DV through the firewire ports?
K
-
Hi Jack
I don’t know about Avid, but FCP is certainly compatible with the AJA card. The only issue is the FCP & Media100 drivers conflict so you can’t have them installed at the same time. You get around this by making your system dual boot, with a separate OS install for each config.
K
-
Hi Bruce,
Are your CG titles rendered? You have to force render the titles before they form part of the exported file. Go to Media – Render… Force Render All.
Hope that helps
Kieran
-
Hi Greg,
Yes, put the original HD in the second bay. If it boots sucessfully then the cabling is OK, if it doesn’t then there’s something about the connections in bay 2.
Otherwise bung the OSX CD in and boot from that. You can then either attempt an install onto the new HD if it can see it, or you can access Disk Utility from there and see if it can see the new HD.
K
-
Hi Greg,
Regarding the SATA drive, did you manage to locate the power cable for it? Your previous posts suggest that you only had the data cable in the bay. If you have, check that both cables are correctly seated in their sockets on the motheboard/psu loom.
As a more extreme test, you could swap the data connections to the two drives (the factory installed boot drive & your new one) and try booting. If the machine boots but doesn’t recognise the new drive as before then it is a problem with the drive itself. If it doesn’t find the boot disc/boot normally then it is probably a problem with the leads etc. Also if it doesn’t boot, reboot from the OSX install CD/DVD and use disc utility from there – it will at least verify if the machine can see the drives.
As for the Airport card – I have no idea. Does system profiler/”about this mac” see the card? Does the network utility allow you to configure airport, or is it greyed out?
K
-
Hi Tim,
Daft question, but is your media drive full? (or at least the drive designated for effects) This has happened to me before with titles and had me scratching my head for hours before I realised.
K