Roman Flute
Forum Replies Created
-
Yeah – I ended up backing up to an older version of QT. A new update had been put on it. Very Irritating. But up and running again!
RF
Roman Flute
Motion Graphics/Multimedia Developer
http://www.romanflute.com
roman@romanflute.com -
This has just happened to me starting about an hour ago. I was able to import this morning and now nothing. I am checking to make sure nobody has updated Quicktime or something. But I am trying to find a solution
Roman Flute
Motion Graphics/Multimedia Developer
http://www.romanflute.com
roman@romanflute.com -
There are a lot of options… Some of my clients want QT files – generally AVID Codecs of some sort – depends upon client. Some I deliver on DVCAM and others on Digibeta.
Big thing – you need to make sure your levels are good. Read up on “broadcast safe” and “ntsc legal”. There is a good tutorial somewhere around here. Also you need to expirement with field rendering. But you have to watch your input video as well.
There are lots of places where you can create issues for yourself.
Ask – what format, what codecs if it is a file – and what field order for those files.
Also – the DV Codec on your computer screen looks nasty – take it to tape and watch on a broadcast monitor from your deck.
Some stuff requires softening too – as the other post mentions.
Good luck!
RF
Roman Flute
Motion Graphics/Multimedia Developer
http://www.romanflute.com
roman@romanflute.com -
How did you record it straight to hard disk?
Have you tried to open the footage in another package – maybe an editing package?
I think your cam is the GL2 (NTSC version) – which I have – so I usually come in firewire off of tape. But was wondering about the aquisition…
I have experienced exactly what you are describing with MPEG2 files. Mainly – because true MPEG2 streams are not individual frames- but averages. I have found that AE sometimes flakes out on those. It gets worse if you start mid stream – more errors. So I just want to make sure you actually got a DV stream rather than an MPEG2 stream.
For instance – one work around – my Final Cut box does not have the issue with those files. So I run it through there and then move it over to my PC for use in AE. Haven’t ever tried Premiere ( if this is your issue… ) – but you might look there – and see if another app has the issue. If not – re-render out from that app and test… It might solve your problem for the time being even if it is a DV file.
Hope you find the solution…
RF
-
Make sure you comp is in a 16×9 pixel aspect ratio – use widescreen for you pixel aspect in your comp. Your comp setting – you can go and turn on aspect ratio correction and your squishiness will disappear. Now if you are going smaller and outputing somethign that doesn’t really support that aspect ratio – make a 16×9 sqaure size – thing 864×480 or something like that if you are going to output from AE – size it down for WMV and stuff like that. Sorenson has a preserve aspect ratio deal that you can use. I usually output QT DV 16×9 and then convert in sorenson squeeze for web…
RF
-
Near plugin. You would be ok if everything was hard cuts – but crossfades… Auto interpreting that… hmmm.
But back to the subject..
Been stuck in this as well – just get it in peices and do your magic. And send it back to them in the same manner.
If you have fades – make sure they give you enough for the handles on each end… Know that is ABC – but I have had that happen as well where I didn’t get enough footage!!!
RF
-
Lighting is going to be your most important thing – doesn’t matter what back you are using. Also – go to the color/telecine session – I have had great blue screen until somebody gets a wild hare and decides to adjust the color on the talent – you can do that for them later in post. But bad lighting / bad transfer will make your days turn into nights… The main keyers out there are great – so usually the only problem I run into is what I am getting. And if you get bad keys – there are still some tricks… We look at stuff on a waveform shooting HD and Video – and check out levels by that. Film – you need to depend on your lightmeter readings.
RF
-
Check your settings – I bet your defaults are for 8-bit. And also I think there has been some sort of update for 10-bit QT files.
RF
-
They are kinda expensive – I know they have several flavors. But who are you getting the video in? Those cards would let you do component video, composite video and/or SDI. You could encode straight from the video source- you current card might be able to do it – coming in s-video or something. There are a lot of these cards out there. I just know these work real well and are very simple.
In all honesty – the progamming for what you want to do would be minimal. Most likely the whole thing would be easy to layout in something like encore or something.
Go to adobe – and you can download a working trial. Just depends one how much fire power and what type of budget you have… But being able to hardware encode will be the fastest way to speed up your process.
Roman
-
You are going to have to encode your AVIs to MPEG2 for the authoring process. How is your video coming in? For speed – and depending upon your setup – the faster you can get your encode in – the better – so a card might be good. Also – what is your platform? Then of course – what is your budget! It all goes to : fast vs quality vs cost. You can have 2. So fast and quality mean expensive and fast and cheap mean lesser quality. If you have AVI – I am assuming you are going to be PC. Digital Rapids makes some nice cards on the PC side and use something like Encore. If you just want to throw some files on there and burn – that might be an option…
RF