Michael Hancock
Forum Replies Created
-
Looks like the DSR-1500 (which is the first deck I ever used, I think) can play back DVCam, miniDV, and DVCPro25, but the DVCPro25 cannot playout via the optional SDI board or iLink (which I assume is firewire). For DVCPro25 you may have to run it out analogue–component would be best.
This is where I got that info:
https://www.samysdv.com/dsr1500.htm
Michael.
-
Choose to crop the top three lines in your export settings, or crop in your encoder program.
Otherwise, make a new video track on top of all your other tracks. Add a resize effect to that track and scale it up 1 or 2% or until the lines are gone. Render, export.
Also, if you have mixed resolutions (1:1 or 2:1, etc with DV), you can always do a video mixdown of your entire sequence to DV50 and export it Same as Source. If you do this it should get rid of the black line because it will export in DV frame size.
Michael.
-
-
What resolution? If it’s DV, that’s normal, because DV is 720×480 (NTSC), and Avid is 720×486 (which is the NTSC broadcast frame size).
Don’t forget, if this is going on TV you’ll never see those three lines. They’re way, way out of action safe.
Michael.
-
Nope. It’s been requested a lot (I’ve requested it several times on the Avid Feature Request Forum), but it hasn’t happened yet.
Your options are to lower each one individually, or you can drop them all into a sequence and lower the first one -20db then apply it to the entire track, then either load that sequence into your source monitor and cut from it there, or subsequence each music track out and load them individually into your source monitor.
Hopefully, one day, we’ll be able to globally apply level changes in the bins, but not yet.
Michael.
-
Well, if you’re running 10.5.5 it blows my theory out of the water. Something changed for the worse in Apple’s firewire with the release of Leopard, and it’s been wrecking havoc on Avid’s older, firewire based hardware (Adrenaline and Mojo). The firewire changed so it couldn’t keep up with the demands of the Avid hardware.
10.5.5 fixed these issues, so I thought–if you weren’t on 10.5.5–the firewire bug was biting you with the Sony cam, but I guess not.
Best of luck getting it figured out. Very frustrating when something should work, doesn’t, and there’s no logical reason why.
Michael.
-
What version is your OS?
Michael.
-
If you just want to know which clips are 4:3 and which are 16:9, I don’t believe that Avid tells you that. It assumes clips are 4:3 when your Source/Record monitors are, and 16:9 when they’re 16:9. If you have footage that’s different aspect ratios, Avid expects you to use the Pan and Scan or Resize effect to reformat them, if you want to. One thing Avid doesn’t typically do is make assumptions about your footage, which can be both good and bad.
If you’re having trouble telling if an imported clip is 16:9 or 4:3, check the original file in Quicktime (if it’s a quicktime file). I honestly don’t think Avid flags this.
Michael.
-
Open your Keyboard settings, open the Command Pallete, choose Menu to Button, then go the fast menu of your timeline and map More Detail and Less Detail (which is Zoom In and Zoom Out on your timeline).
The only way to map a key combination like that in Avid is to map the menu command. The key combination is just the default shortcut.
Michael.
-
Are these independent imports each time, or are you deleting the media and batch importing? I ask because a batch import will remember the previous settings unless you change them and choose to override them, but even then I don’t believe it will override the Autodetect Sequential Files command. If it imports it once and thinks it’s a 2 frame movie, it will reimport it as a movie with Batch Capture, regardless of your change in import settings.
Otherwise, this is weird. I’ve never heard of this issue before. Have you made a new user and tried that?
Michael.