Matthew Skeris
Forum Replies Created
-
I’m with Kevin on this one. I think his library of free tutorials are truly excellent. And there are other great free online lessons, just a Google/ YouTube search away.
Avid books are fine, but tend to be costly.
I have found some Avid books available online from my local public library and I have requested others.
Books = good. Public Libraries = better. Free Public education from teachers = Amazing.
-
Matthew Skeris
March 18, 2009 at 12:05 am in reply to: Reliable way to view list of all clips used in a sequenceZach,
Here it is online.Still not sure it does what you need, but check it out.
-
Matthew Skeris
March 17, 2009 at 1:51 am in reply to: Reliable way to view list of all clips used in a sequenceThere is a new feature on MC v3 that displays a complete catalog of elements in your sequence. It’s added to the Composer Window/Right-Click tools.
I used it today to help locate a set of tiny EQ AudioSuite FX that were buried in my sequence- I had to remove them prior to a mix.
The new feature may do what you want, outputting results to Console or a Log file.
-
Hi Michael, I don’t remember eactly or have access to my Avid for a few days, but in general it all made sense once I realized that SS5 is capable of producing hi quality 1920×1080 QT files with DNxHD codec from Avid-Exported QTref files. I thought SS only made web-quality movies, but I was pleasantly surprised. The key setting is 1:1 frame and Keyframe every 1 frame.
I really like that I can run SS5 in the background while continuing to edit normally with Avid.
Once finished, I imported my 1920×1080 QTref render back into my Avid HD project, it looked indistinguishable from a video mixdown which looks indistinguishable from original footage,imo.
At that point I explored SS5 using an imported SD QTref, using SS5 filters for Crop, Sharpness and perhaps another. I took the time to tweak every parameter incrementally (some of which behaved counter-intuitively) and convinced myself that the result was great. YMMV, but as an SS5 customer, I got immediate, free phone support at SS to explain each setting on the filters… it made all the difference and I saved a preset. Good luck.
-
OK Bob, no reading or spending until I get back to work. I think they call that deflation, btw. 🙂 fact is I don’t know from HD vtrs, but wanted my DNxHD 220x renders to play out to tape slower than 30fps, but without pulldown because it is animation and I somehow got it in my head that it will be smoother at true 24 or 23.98. maybe I’ll just forget it and get more drives. I should’ve just clicked the camera shutter faster to begin with, but that’s life. Thanks for offering your help.
-
Matthew Skeris
January 17, 2009 at 12:12 pm in reply to: panasonic AJ-HD 1400, 23.98 DX Avid ProjectThanks for your thoughtful reply, Dino. I have been working at 1080i in Avid Composer 3.0, but my frames are actually progressive as rendered from AE into DNxHD qt files. They are animations from stills. I want to edit from clean progressive frames, but with a slower look though not 15fps which I tried and didn’t like inside the 5994 project.
Your suggestion to use HDCam is gold. I will try that next in an Avid 23.98 HD Project, using that Console command. Then I want to edit its 24fps on a real monitor, not just the Composer LCD screen… this may not be possible on my current program LCD monitor.
Avid: Yes, yelling gets results… enjoy the battle. I do love the DX gear, it seems great- but I can’t really compare.
I don’t know what I can do to answer your other question about 720, I’ll have to gain a bit more experience before trying. I know I will refer to your post again when I am given my first Varicam tape for am edit. thank you for all the explanations.
I finally made peace with 5994 once i realized that it was the same fps as 2997- at least now when I see or hear 5994 I know we’re probably talking HD.
be well.
-
Matthew Skeris
January 16, 2009 at 11:49 pm in reply to: panasonic AJ-HD 1400, 23.98 DX Avid ProjectThanks so much, Tim. That’s a great clue and I appreciate the Z-link.
-
Loui, I am subscribed to this entire thread via email.
I was waiting here patiently for a reply about the Uprez AVX after emailing a requested screenshot and describing in detail what looks like the same issues that brought you here. Not every fix is quick or a priority and I certainly get that. The Boris collection is wonderful, but I’ve moved on. I now use Squeeze5 to Uprez SD NTSC to 1920×1080 after doing many experiments with its built-in Sharpening filter.
Perhaps your post is going unnoticed- you may want to start a new thread so that it will appear at the top of a list sorted by thread.
-
OK- I just sent one as an attachment from my yahoo acct.
-
Hi Peter, thanks for your help. I’m using Composer DX Nitris v3.0 and the Boris BCC that comes with it. I’ve followed the guidelines as to source pixel aspect ratio = square pixels, Source Size = ntsc D1 720×486 and the Fill Frame (Crop) pulldown as described in your notes. however, I still have the same issues.
My media is SD footage from beta tape captured at 1:1 inside a 1080i project- AvidHD can capture this format by setting its Project/Format tab to 30i for capture, then putting it back to 1080i to resume editing in HD.
The SD footage appears stretched when seen on the 1080i 16×9 timeline- this is normal. However, using Uprez, I can’t achieve a proper aspect ratio on the zoomed-in SD footage without enabling Geometrics and increasing just Scale Y by eye.
I further tested this just now by creating an SD title with a white background showing a perfect circle inside a perfect square. Only after increasing Geometric’s Y to 125 did I achieve a perfectly round, albeit zoomed in circle image to fill the 16×9 frame in HD.
The Transform value for the above was 37.40.
I also tried using Sharpness on the original SD footage and could not see a real difference between the zero setting and the 100 setting, all the while using Magic Sharp.
If you can have someone try this on an Avid system like mine it would be even more helpful and I look forward to any ideas you might have.