Forum Replies Created

Page 4 of 13
  • Craig Ricker

    June 4, 2013 at 5:44 am in reply to: Dodgey way to switch HD SDI

    Thanks for the reply. Yeah its not even a device really. Like i’m imagining inside a RCA switch is just a physical switch moving (physically) between one pair of contacts and another. So that kinda makes sense to me why it would work.

    Mac Pro 2 x 2.4Ghz, 16GB RAM, GTX 660

  • You need a couple of cameras (if doing live presentations), some pre made content with a playback device such as a black magic hyper deck, switcher, a live streaming encoder, an account with a CDN, and a website that has a built in player that can accept a live stream feed.

    All doable for about $60k setup.

    $1.70 per GB for CDN costs there abouts. That includes every user downloading and you uploading.

    Mac Pro 2 x 2.4Ghz, 16GB RAM, GTX 660

  • Im getting the same issue. Premiere keeps crashing on exit from my project. Its only on this specific project. I have dynamic links going to 1 AE project.

    This is the crash log

    Process: Adobe Premiere Pro CS6 [1500]
    Path: /Applications/Adobe Premiere Pro CS6/Adobe Premiere Pro CS6.app/Contents/MacOS/Adobe Premiere Pro CS6
    Identifier: com.adobe.AdobePremierePro
    Version: 6.0.2 (6.0.2)
    Code Type: X86-64 (Native)
    Parent Process: launchd [226]
    User ID: 501

    Date/Time: 2013-05-13 10:49:35.685 +1000
    OS Version: Mac OS X 10.8.3 (12D78)
    Report Version: 10

    Interval Since Last Report: 5606 sec
    Crashes Since Last Report: 1
    Per-App Interval Since Last Report: 4977 sec
    Per-App Crashes Since Last Report: 1
    Anonymous UUID: 117B489B-FDB6-253E-2253-C992C67974DA

    Crashed Thread: 0 Dispatch queue: com.apple.main-thread

    Exception Type: EXC_BAD_ACCESS (SIGSEGV)
    Exception Codes: EXC_I386_GPFLT

    Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
    0 com.adobe.premiere.frontend 0x000000010c72b74b FE::Application::AttemptPanicProjectSave() + 21
    1 com.adobe.premiere.frontend 0x000000010c78327c UnixInterruptSignal(int) + 44
    2 libsystem_c.dylib 0x00007fff8bdde94a _sigtramp + 26
    3 libsystem_kernel.dylib 0x00007fff927c30fa __psynch_cvwait + 10
    4 libsystem_c.dylib 0x00007fff8bdf4fe9 _pthread_cond_wait + 869
    5 com.adobe.dvacore.framework 0x00000001001ebee4 void boost::condition_variable_any::wait(boost::unique_lock&) + 140
    6 com.adobe.dvacore.framework 0x00000001001e97a8 dvacore::threads::Gate::PassThrough(int) const + 496
    7 com.adobe.dvacore.framework 0x00000001001e5a4c dvacore::threads::(anonymous namespace)::SubExecutor::Flush() + 232
    8 com.adobe.Backend.framework 0x000000010165cf0a BE::ShutdownMediaRelinking() + 58
    9 com.adobe.Mezzanine.framework 0x00000001053e2673 MZ::(anonymous namespace)::MLInitializer::~MLInitializer() + 15
    10 com.adobe.Mezzanine.framework 0x00000001053e29ca MZ::(anonymous namespace)::FullInitializer::~FullInitializer() + 182
    11 com.adobe.Mezzanine.framework 0x00000001053ebd15 MZ::Initializer::PrivateImpl::~PrivateImpl() + 29
    12 com.adobe.Mezzanine.framework 0x00000001053e1b98 MZ::Initializer::~Initializer() + 22
    13 com.adobe.premiere.frontend 0x000000010c778fb3 FE::(anonymous namespace)::FullInitializer::~FullInitializer() + 49
    14 com.adobe.premiere.frontend 0x000000010c779d25 FE::Initializer::PrivateImpl::~PrivateImpl() + 29
    15 com.adobe.premiere.frontend 0x000000010c778f4a FE::Initializer::~Initializer() + 22
    16 com.adobe.premiere.frontend 0x000000010c783d45 AppMain + 453
    17 com.adobe.premiere.startup 0x000000010c8f41d7 Run + 247
    18 com.adobe.AdobePremierePro 0x00000001000038b7 main + 647
    19 com.adobe.AdobePremierePro 0x000000010000361c start + 52

    Thread 1:: Dispatch queue: com.apple.libdispatch-manager
    0 libsystem_kernel.dylib 0x00007fff927c3d16 kevent + 10
    1 libdispatch.dylib 0x00007fff915f4dea _dispatch_mgr_invoke + 883
    2 libdispatch.dylib 0x00007fff915f49ee _dispatch_mgr_thread + 54

    Thread 2:
    0 libsystem_kernel.dylib 0x00007fff927c30fa __psynch_cvwait + 10
    1 libsystem_c.dylib 0x00007fff8bdf4fe9 _pthread_cond_wait + 869
    2 com.apple.CoreServices.CarbonCore 0x00007fff8e067210 TSWaitOnCondition + 108
    3 com.apple.CoreServices.CarbonCore 0x00007fff8e0673e7 TSWaitOnConditionTimedRelative + 132
    4 com.apple.CoreServices.CarbonCore 0x00007fff8dfc9b14 MPWaitOnQueue + 252
    5 com.adobe.ASLFoundation.framework 0x00000001005c0770 ASL::(anonymous namespace)::TaskProc(void*) + 160
    6 com.apple.CoreServices.CarbonCore 0x00007fff8e03e7e0 PrivateMPEntryPoint + 58
    7 libsystem_c.dylib 0x00007fff8bdf07a2 _pthread_start + 327
    8 libsystem_c.dylib 0x00007fff8bddd1e1 thread_start + 13

    Mac Pro 2 x 2.4Ghz, 16GB RAM, GTX 660

  • Thanks for the help guys!

    Mac Pro 2 x 2.4Ghz, 16GB RAM, GTX 660

  • Craig Ricker

    February 19, 2013 at 1:11 am in reply to: Laptop advice to use with Premiere Pro CS6

    Could consider the Retina Mac Book Pro 15 inch. I use 1 and premiere works flawlessly on it. I edit natively GH2 .mts files without any slow downs what so ever.

    Price is a joke though. Good screen and very fast SSD’s is a huge plus though.

    Mac Pro 2 x 2.4Ghz, 16GB RAM, GTX 660

  • Craig Ricker

    February 18, 2013 at 3:56 am in reply to: Ensure Premiere CS3 broadcasts color safe media?

    Spewing it was such a good question and I wanted to know the answer 🙁

    Mac Pro 2 x 2.4Ghz, 16GB RAM, GTX 660

  • Craig Ricker

    February 18, 2013 at 2:14 am in reply to: Australia broadcast luma and chroma limits

    So I had a read through that document. Didnt discuss DV Pal, rather it was in regards to HD broadcast, but assuming they wish to have the same levels I found this to be what they said.

    So assuming I am reading this correctly, the levels for broadcast are not 0-255, but rather 16-235 for luminance.

    Could not see what chrominance values are supposed to be?

    I have heard to not go over 75% on the vector scope, though would like to know what values that means so I can simply apply the video limiter effect and set it up right.

    Mac Pro 2 x 2.4Ghz, 16GB RAM, GTX 660

  • Craig Ricker

    February 11, 2013 at 1:10 am in reply to: Painting on a text layer

    Is there not a way to do what the OP asked though? I too would like to use paint tools to reveal a text layer. Would of liked to be able to paint in the text layers alpha channel. Like you can do in a video or picture layer.

    The other option is to create a solid and paint on it, and then use as a track matte, but i’d love to know if anyone has a good way of doing this whilst being able to see the text layer at the same time. Like how to paint on the solid and ensure your painting over the text layer precisely.

    At the moment I have a layer and composition window open to help guide me, but its still guess and check.

    Mac Pro 2 x 2.4Ghz, 16GB RAM, GTX 660

  • Craig Ricker

    February 5, 2013 at 10:24 pm in reply to: playback in premiere is choppy h264

    I can usually edit go pro H.264 footage without any problems. Its certainly not as smooth as a less intensive CPU codec, but besides the odd slow scrub here and there its almost perfectly seamless for me.

    Thats editing on a macbook pro retina 2.6Ghz i7.

    Mac Pro 2 x 2.4Ghz, 16GB RAM, GTX 660

  • Craig Ricker

    February 4, 2013 at 11:05 pm in reply to: playback in premiere is choppy h264

    Magic bullet looks can only use 2 cores in premiere as far as i’m aware. That would be the slowdown I believe

Page 4 of 13

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