Forum Replies Created

Page 4 of 22
  • Shane Chadder

    March 25, 2006 at 11:05 pm in reply to: Editing DVCPRO 50

    No thoughts…but wondering how you get DVCPro50 into your system? Does Mainconcept support capturing to it’s codec in PPRO?

    We use pro50 but capture with Decklink uncompressed since nothing on the Windows side supports native pro 50 capture.

    Shane

  • Hi

    Is there a “setup” option in decklink to turn setup on and off? In NTSC setup is used on the Y channel raising the green level 7.5 units, but not r-y or b-y. That could through the component level out either direction depending on which side of the atlantic you work.

    Shane

  • Shane Chadder

    March 25, 2006 at 1:52 am in reply to: Blackmagic on XP

    It depends on your workflow. If you work only in 10 bit it should be great for you.

    In 8 bit SD there are some issues with Pro 2 and AE 7 so you need to stay with AE 6.5. Nothing subtle about this, AE crashes if you try and load an 8 bit clip. It seems like the bug is Adobe as 8 bit Targa 3k files do the same.

    Again if you stay in 8bit with AE 6.5 it should be great for you.

    If you are NTSC and need to mix DV and uncompressed I’m finding renders go slightly soft because some footage is 486 lines and others 480. Something is resizing is my guess. (you need a dell with an HDLink to see it). I’m not sure who to blame, no one has acknowledged the problem. Maybe its just our 4 systems 😉

    Oh, and firewire captures don’t work in PPro 2.0 with BM drivers but I’ve heard that is fixed for the next release of drivers. We keep 1.5 on the system just for firewire.

    So they are getting there. If you know the limitations and choose your workflow it is a great product.

    Shane

  • Shane Chadder

    March 23, 2006 at 9:25 pm in reply to: NTSC DV Source Monitor Bug

    Sorry Adrian, I haven’t been editing this week. You are right. In a BlackMagic DV job the source monitors don’t play out to the Decklink card.

    Shane

  • Shane Chadder

    March 20, 2006 at 7:43 pm in reply to: NTSC DV Source Monitor Bug

    Are you using 5.4.2 drivers?

  • Shane Chadder

    March 17, 2006 at 2:24 am in reply to: project trim error

    Trimmed projects crashes can be tough to troubleshoot. I find it most often relates to Premiere having trouble trimming certain codecs or files, and sometimes the larger the project the more finicky it seems to be.

    What I do is….

    1) Start the trim process as normal
    2) Open the folder the files are being written to and leave it open on top of Premiere.
    3) When premier chokes DON’T click on the OK. First write down the name of the file it last tried to write.
    4) Now click OK.
    5) Set that file it choked on as “offline” in the bin and restart the process.
    6) Once you get the trim to work manally copy the problem files over and relink them in the trimmed project.

    Right now in version 2.0 I find that if I use *.psd files as logos in titles a large project will choke during trimming. Small projects are ok.

  • Hi

    Check your decklink settings in the control panel. If you set decklink to output black while you are capturing you can’t monitor while you capture.

    Shane

  • Shane Chadder

    March 15, 2006 at 5:44 pm in reply to: Cross converting from Decklink?

    I did this once with a HD 25P job by just exporting the final *.avi in 25P, then creating a new 23.976P job in Premiere and importing the 25P *.avi as 23.976P to print to tape.

    You end up with a program that is 4% longer, but the video should be perfect frame for frame. I dont’ know about 50i and 60i tho.

  • Shane Chadder

    March 10, 2006 at 8:26 pm in reply to: HD Pro and PPro 2.0 Big Problems!

    Same problem on our systems with HDPro single link.

  • Shane Chadder

    March 10, 2006 at 7:23 pm in reply to: HD Pro and PPro 2.0 Big Problems!

    Hi Andrew

    It is very easy to reproduce….I’m on an SDplus card at the moment, I’ll try the HDPro single link in a minute.

    1) Make a new BM-8bit ntsc timeline.
    2) Import an NTSC DV (firewire captured) clip and place it on the video track.
    3) Make a title and place it over the clip.
    4) In real time it looks fine. Now Render the title and you will see the resolution drops and the video shifts down a line at the cut point.

    It seems like any rendering causes the softness. Even just placing a transparent clip over a frame and rendering that frame you will see the difference. Especially with an HD-LInk and 24″ Dell where softness problems are easily identified!

Page 4 of 22

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy