Steve Hull
Forum Replies Created
-
Many thanks for the advice, guys.
-
I did at one point and oddly it also gave me problems. After that I think I just stuck to QT without thinking about it.
As it stands, I still have a problem: although I can make the muxed file and QuickTime plays it perfectly, I still can’t get WMP to recognise it… which is par for the course with WMP in my experience. Any thoughts?
-
Problem solved. Seems to have been interference between two compressors. Exporting uncompressed has cleared it up.
-
Thanks, Kieran. I’ve not noticed the white frame, though it may be there. I’m also not aware of adding any compression markers. However I’ve found a fix (just — test confirmed it about 10 minutes ago). I’d been generically exporting the program as QT, i.e. with a bit of compression. Evidently the M100 compression and BitVice interfered in some way. I changed settings so that M100 exports uncompressed QT and everything seems to work.
-
Thanks very much for your (as ever) quick and comprehensive reply. Don’t you ever sleep?
A question. You said that footage should be interpreted in AE as top field first. Yet in the de-interlacing tutorial (De-Interlacing the Cow), Barend states that DV footage is lower field dominant. Which of you is correct?
Another headache which you may or may not have insight into. I’ve tried rendering a test in AE with field rendering off as you’ve suggested and when I try to encode it in BitVice, as soon as I’ve specified the source file (i.e. even before I hit the Encode button), BitVice crahses. I’ve never had problems with BitVice before. Does this ring any bells? Thanks once again.
steve
-
Sorry for the delayed response — I haven’t looked at messages for a while. I use M100/xr version 7.5.1 on a G4 running OS 9.2.2 (I also have OS X and version 8, but since my After Effects is only OS 9, it doesn’t normally get used). I’d be pleased to hear what sort of stuff you’re doing.
-
Thanks for the quick response, Floh! I should have mentioned that I was able to boot with the Media 100 extensions switched off an the Media 100 board still in the computer, so it definitely seems to be connected with Media 100.
-
It’s rather puzzling: The DWW-A500P doesn’t have anything that’s marked as being RS-422, but it does have a 25-pin connector which is explicitly marked RS-232C. There are 4 other D-type connectors, marked “Control Panel,” “Remote In,” “Remote Out” and “Video Control.” None of these are described in the manual as having anything to do with RS-422, but I wonder if the Remote In might possibly, given that it’s a 9-pin. Any ideas?
-
Thanks very much to both of you for your help! I have one additional question regarding cabling. I have a 9-pin cable running from the Keyspan which I can, I understand, attach an RS-422 to RS-232 adaptor to. I also gather that you can now get USB to RS-232 cables. Wouldn’t that be a better option, doing away with the Keyspan unit entirely? Thanks for the help.