Barn doors transition causes crash

Dear Community,
Applied barn doors transition to a project in CS4. Stored that project in 2010.
Opened the project in CS6 CC - and barn doors caused crashes - so I cleaned off the old and applied replacement barn door transitions in CS6 CC.
Once the wipe is applied - its fairly stable - sometime crashes sometimes doesn't.
If I apply a broder colour to the wipe - all ok.
If I then apply a border thickness - crash every time.
System;
Premiere Pro CS6 - 6.0.3 (001 (MC: 264587)) through cloud membership
Updated and current
Win 7 Pro - SP1 - 64 Bit
Source footage SONY EX3 - .mp4 and still image .png's
No error messages - just crash and need to restart PP CS6
Try to apply colour and border to a barn door transition causes the error
This worked before on the smae project when created in CS4
Not running other software at the time
NewBlueFX modules installed but not applied to this area of sequence
i7 - 3.20GHz, 16GB RAM, SSD OS drive, 4 x drive RAID on LSI RAID card, - No I/O hardware
I am using Are you using Mercury Playback Engine Acceleration and CUDA
Problem occurs during normal edit - as soon as I start to adjust the barn doors wipe - I don't get to compression
Thanks
Dave

Doies it help anyone that I just received this from the email address; [email protected];
Hello,
You have received this email because the content you posted below has been rejected by our moderators.
Re: Barn doors transition causes crash
posted Jun 5, 2013 5:15 PM  
Since the original report earlier today - I now just have to put the timeline scrubber over the barn doors transition and PP CS6 closes without an error message and without saving. The unfortunate part here is there doesn't seem to be any record or log of the crashes to be able to disseminate whats going wrong.
  Barn doors worked in CS4 - and the only change in this project is the re-opening in CS6 CC."
Question; Did I put something in there that was defammatory, rude, obnoxious, incorrect or un-helpful?
If anyone here believes I did, I sincerely apologise for the need of moderators to have intervened... and for causing any offence.

Similar Messages

  • Filters/transitions cause crashing - help!

    Does anyone know why every time I try to apply a transition/filter it previews as garbled nonsense then, if I try to apply it, it crashes iM6HD? I do mean EVERY time - this is not an exaggeration.
    I actually can't believe that I have paid for this piece of software: it just DOESN'T WORK. I'm seriously thinking of giving up the hardware; I can't justify it as mere home decor - it has to work!
    Grateful for any insight....
    Ted

    Hi again Karl, Sue,
    In answer to you question/suggestion, the project is around 80 minutes/17.5 GB but that's close to the remaining free space on my internal storage, hence using the external LaCie.
    I haven't installed any plug-ins for iMovie or for QT, so as far as I know I'm running them both clean.
    The only other possible factor is that I'm running a LaCie 20" screen at 1600x1200 off the PowerBook (but not using its screen).
    Looking forward to some more possibilities!
    Cheers,
    Ted

  • Adobe Media Encoder crashes when borders are applied to the "barn doors" effect.

    Pproheadless.exe stops working. End of story. Doesn't matter what kind of clip I try to apply this to. Barn Doors works; Barn Doors with a border doesn't.

    Ah, sorry about that. It's what happens when I post in frustration at 5:00 in the morning. But thanks for the response.
    Windows 7 64-bit
    Premiere Pro 5.5.1
    Combined Community Codec Pack
    K-Lite Codec Pack
    Not sure if Mercury Playback is enabled. The crash only happens when creating a file in Media Encoder. I've isolated the problem to rendering as a DVD-Mpeg with "Render at Maximum Depth" checked. When it is unchecked, the files render without a crash.

  • Photoshop CS4 and graphic cards. Can cause crashing?

    Since upgrading to CS4 I seem to have increased crashing.
    Here are my system specs.
    Mac 2 x 2.66 GHz Dual-Core Intel Xeon
    9 GB of Ram
    250 GB internal dedicated scratch disc
    NVDIA GeForce 7300 GT with 256 VRAM
    After having endless techs look at my machine and upgrading everything. I am beginning to suspect the graphics card.
    With OpenGL can a underperforming video card cause crashing in photoshop especially with massive file sizes ( multilayered CMYK poster sized files the can exceed 7 GB)?

    Did you install the 11.0.1 update?
    Is your OS up to date with patches?
    Have you tried disabling OpenGL in preferences to avoid using the GPU/Graphics card?

  • AutoVue viewer caused crash while viewing .XSLX documents.

    We use AutoVue Desktop Deployment Viewer incorporated in our application (using JNI). When viewing XLSX (Microsoft Excel) documents on Windows 8.1 x64 system it caused crash of application. It's reproducible only on Windows 8 (8.1 or Server2012) systems. If we set compatibility mode (Windows 7) then problem isn't reproducible.

    I would recommend you log a ticket with customer support

  • CC 2014 (18.1.0) | Text Field editing causing crashes (Windows)

    Greetings;
    I've noticed lately that when saving files from CC 2014 to a CS6 format - and having those files edited on Mac, in either CS6 or CC - when re-opening those files text fields have been causing crashes on the Windows client. When that same file is opened and text fields are edited on the Mac client, a prompt will just appear stating "Cannot Edit text" - yet it still allows it.
    This has caused multiple issues for our teams as it has created files we're starting to refer to as "mine fields" - as working with the .ai file is like playing Russian roulette with text fields, you never know which one is going to crash the file.
    I would love to work with a team member from Adobe to help find a resolution to the problem, and I'm willing to provide any additional details that might aid in that process.
    Thanks!

    Hello Pureweb,
    Please upload the crashdumps on some file sharing website say Dropbox and share the link with us by sending a mail to "[email protected]". We will analyze the dump and will suggest you the workaround appropriately.
    In parallel, please check that you do not have any 3rd Party plugins installed in it. Please try to remove them one-by-one and see which one causes the crashes or do reverse i.e. remove all the 3rd party plugins. Or Uninstall Ai and check at following location:
    C:\Program Files\Adobe\Adobe Illustrator CC 2014
    Please verify that nothing is left at above location on uninstalling Ai. Then try a fresh install and see if Ai works.
    Also, verify that you have the updated Wacom drivers on your system. This might be an issue with the 3rd party program as well. One of the user who was having a similar issue reported on the Ai forum that one of the 3rd party Stahl's ImageWorx DTG RIP - a program for printing to a Direct To Garment printer was causing the issue. So, you may check if the similar thing is not happening in your case.
    Regards,
    Dhirendra

  • Photoshop CC Content - Aware Move Tool causes crash

    Does anyone have any ideas why this is happening? Content Aware Move tool causes crash every time so far with tiff and jpegs and its getting frustrating!
    I have Windows 8.1 Pro with 8GB RAM
    NVIDIA GeForce GT 650M Graphics
    Photoshop CC 64 bit

    Thanks for the reply JJMack - I have to be honest, i'm not exactly sure what i'm looking for here!
    Source
    Adobe Photoshop CC 2014
    Summary
    Stopped working
    Date
    06/04/2015 09:45
    Status
    Report sent
    Description
    Faulting Application Path: C:\Program Files\Adobe\Adobe Photoshop CC 2014\Photoshop.exe
    Problem signature
    Problem Event Name: APPCRASH
    Application Name: Photoshop.exe
    Application Version: 15.2.2.310
    Application Timestamp: 5480338c
    Fault Module Name: FaceDetection.dll
    Fault Module Version: 2.2.6.32411
    Fault Module Timestamp: 52e12400
    Exception Code: c0000005
    Exception Offset: 000000000001704d
    OS Version: 6.3.9600.2.0.0.256.48
    Locale ID: 2057
    Additional Information 1: e87c
    Additional Information 2: e87c816cbb2acbf5e54624fc2b1f98cc
    Additional Information 3: 1879
    Additional Information 4: 1879b998534215d47b0a850e45784427
    Extra information about the problem
    Bucket ID: 2dac81db98a57fddf5997edfd40ba6eb (85993531415)

  • HT5704 Hi, Two recent updates for my iPhone have caused crashes (down the white lead via iTunes).I have "fixed" but not sure of the cause?

    Hi,
    Two recent updates for my iPhone have caused crashes (down the white lead) via iTunes.
    I have "fixed" but I don't know the cause?
    Each time the update does n't complete.
    The download does n't happen.
    The computer & internet connection are good.
    It is as if the Apple server does n't complete?
    The phone stays in recovery mode, until you reset and rebuild in iTunes.
    All software is up to date, but I can't find the cause
    ANY IDEAS?
    Regards,
    P.
    <Email Edited by Host>

    No error messages.
    It just fails to complete the download, so recovery mode is the next step.
    This can be over a period of eight hours or more!
    I have so many (original) Apple USB leads that I would n't know if I have been using the same one (if it was faulty).
    Does this sound like a "common" problem?

  • Why Does 3D Reposse cause crashes and work so slow?

    Why Does 3D Reposse cause crashes and work so slow?   I get the pinwheel of death when I use this feature.  It works at a snails pace.  I liked the 3D Type effects in iIllustrator.  Why couldn't Adobe have added all the Reposse features to Illustrator instead of craming all these new features into Photoshop?
    They're worthless if the program needs an hour to process every selection.

    What are your OS specs, your Video Card and your Preferences > Performance settings?
    Why Does 3D Reposse cause crashes and work so slow?
    My guess would be because it has to create a whole bunch of polygons and your computer-set-up may be insufficient for the task.

  • Firefox causes crash when using Youtube explorer does not have the same effect

    firefox causes crash when using Youtube explorer does not have the same effect

    Troubleshooting extensions and themes
    * https://support.mozilla.com/en-US/kb/Troubleshooting%20extensions%20and%20themes
    Check and tell if its working.

  • Access violation (0xC0000005) cause crash

    Access violation (0xC0000005) cause crash. The crash report is as blow. It may be caused by the function IMAQ FillHole. How this function crash?
    Who knows why? Thank you!
    #Date: 2014年8月12日 14:21:51
    #OSName: Windows 7 Ultimate 
    #OSVers: 6.1
    #OSBuild: 7600
    #AppName: 
    #Version: 12.0 32-bit
    #AppKind: AppLib
    #AppModDate: 08/12/2014 06:17 GMT
    #LabVIEW Base Address: 0x30000000
    <LVExec>
    {"a":[
    "vi": "D\\VISION_SYSTEM\\build\\MyProgram.exe\\IMAQ FillHole",
    "ctx": "主应用程序实例",
    "type": "subVI"
    "vi": "D\\VISION_SYSTEM\\build\\MyProgram.exe\\ccd2表面2二值化.vi",
    "ctx": "主应用程序实例",
    "type": "subVI"
    </LVExec>
    <DEBUG_OUTPUT>
    2014/8/12 16:48:15.894
    Crash 0x0: Crash caught by NIER
    File Unknown(0) : Crash 0x0: Crash caught by NIER
    minidump id: 6e35643f-8ff2-49e6-bbde-98bac2ffa48a
    ExceptionCode: 0xC0000005$N
    </DEBUG_OUTPUT>
    0x307277B4 - lvrt <unknown> + 0
    0x30727B38 - lvrt <unknown> + 0
    0x7C37FDB4 - MSVCR71 <unknown> + 0
    0x77CA5A74 - ntdll <unknown> + 0
    0x77C8B3C8 - ntdll <unknown> + 0
    0x00000000 - <unknown> <unknown> + 0
    Solved!
    Go to Solution.
    Attachments:
    ccd2表面2二值化.vi ‏21 KB

    Hi,
    please stick with your original thread! Don't create double posts!
    Best regards,
    GerdW
    CLAD, using 2009SP1 + LV2011SP1 + LV2014SP1 on WinXP+Win7+cRIO
    Kudos are welcome

  • Windows xp, minidump, applemtm.sys caused crash

    hi, my mbp just crashed in windows xp.
    remained minidump said, applemtm.sys caused crash...
    ^^ i know this info is too little figure out the problem...
    but, is there anyone faced like this one?
    -------- minidump -----
    ATTEMPTEDSWITCH_FROMDPC (b8)
    A wait operation, attach process, or yield was attempted from a DPC routine.
    This is an illegal operation and the stack track will lead to the offending
    code and original DPC routine.
    Arguments:
    Arg1: 00000000, Original thread which is the cause of the failure
    Arg2: 00000000, New thread
    Arg3: 00000000, Stack address of the original thread
    Arg4: 00000000
    Debugging Details:
    *** Kernel symbols are WRONG. Please fix symbols to do analysis.
    * Your debugger is not using the correct symbols *
    * In order for this command to work properly, your symbol path *
    * must point to .pdb files that have full type information. *
    * Certain .pdb files (such as the public OS symbols) do not *
    * contain the required information. Contact the group that *
    * provided you with these symbols if you need this command to *
    * work. *
    * Type referenced: nt!_KPRCB *
    * Your debugger is not using the correct symbols *
    * In order for this command to work properly, your symbol path *
    * must point to .pdb files that have full type information. *
    * Certain .pdb files (such as the public OS symbols) do not *
    * contain the required information. Contact the group that *
    * provided you with these symbols if you need this command to *
    * work. *
    * Type referenced: nt!KPRCB *
    * Your debugger is not using the correct symbols *
    * In order for this command to work properly, your symbol path *
    * must point to .pdb files that have full type information. *
    * Certain .pdb files (such as the public OS symbols) do not *
    * contain the required information. Contact the group that *
    * provided you with these symbols if you need this command to *
    * work. *
    * Type referenced: nt!_KPRCB *
    * Your debugger is not using the correct symbols *
    * In order for this command to work properly, your symbol path *
    * must point to .pdb files that have full type information. *
    * Certain .pdb files (such as the public OS symbols) do not *
    * contain the required information. Contact the group that *
    * provided you with these symbols if you need this command to *
    * work. *
    * Type referenced: nt!KPRCB *
    * Your debugger is not using the correct symbols *
    * In order for this command to work properly, your symbol path *
    * must point to .pdb files that have full type information. *
    * Certain .pdb files (such as the public OS symbols) do not *
    * contain the required information. Contact the group that *
    * provided you with these symbols if you need this command to *
    * work. *
    * Type referenced: nt!_KPRCB *
    * Your debugger is not using the correct symbols *
    * In order for this command to work properly, your symbol path *
    * must point to .pdb files that have full type information. *
    * Certain .pdb files (such as the public OS symbols) do not *
    * contain the required information. Contact the group that *
    * provided you with these symbols if you need this command to *
    * work. *
    * Type referenced: nt!_KPRCB *
    * Your debugger is not using the correct symbols *
    * In order for this command to work properly, your symbol path *
    * must point to .pdb files that have full type information. *
    * Certain .pdb files (such as the public OS symbols) do not *
    * contain the required information. Contact the group that *
    * provided you with these symbols if you need this command to *
    * work. *
    * Type referenced: nt!_KPRCB *
    * Symbols can not be loaded because symbol path is not initialized. *
    * The Symbol Path can be set by: *
    * using the NT_SYMBOLPATH environment variable. *
    * using the -y <symbol_path> argument when starting the debugger. *
    * using .sympath and .sympath+ *
    * Symbols can not be loaded because symbol path is not initialized. *
    * The Symbol Path can be set by: *
    * using the NT_SYMBOLPATH environment variable. *
    * using the -y <symbol_path> argument when starting the debugger. *
    * using .sympath and .sympath+ *
    FAULTING_MODULE: 804d9000 nt
    DEBUGFLR_IMAGETIMESTAMP: 47685ec5
    CUSTOMERCRASHCOUNT: 1
    DEFAULTBUCKETID: WRONG_SYMBOLS
    BUGCHECK_STR: 0xB8
    LASTCONTROLTRANSFER: from 80547c4b to 804fbf0e
    STACK_TEXT:
    WARNING: Stack unwind information not available. Following frames may be wrong.
    bacd3c8c 80547c4b 000000b8 ffffffff 00000202 nt+0x22f0e
    bacd3ce4 b7e06569 00000000 00000000 00000000 nt+0x6ec4b
    bacd3d10 b7e4be4a 8a1711d8 00000000 8a451e08 Wdf01000+0x15569
    bacd3d2c b7fcb53b 8a171290 75dc0430 8a23fbc8 Wdf01000+0x5ae4a
    bacd3d4c b7fcb651 75bae3b8 8a00de70 bacd3da8 applemtm+0x53b
    bacd3d5c b7e261b2 760ef150 75dfc680 bacd3d80 applemtm+0x651
    bacd3da8 b7e26253 b7e57a08 8a203978 89f10ea8 Wdf01000+0x351b2
    bacd3dc0 b7dfd5d3 8a00df97 8a203978 00000000 Wdf01000+0x35253
    bacd3ddc b7dfd68d 01f10ea8 8962e450 bacd3e08 Wdf01000+0xc5d3
    bacd3dec 804f280d 8a46c5a8 8a00de70 89f10ea8 Wdf01000+0xc68d
    bacd3e08 804f36b0 8a46c5a8 8a00de70 8962e450 nt+0x1980d
    bacd3e38 b99210d5 8a00de70 88da4980 8a2d3028 nt+0x1a6b0
    bacd3ea0 b9921d47 895bd170 00000000 8a2d37d8 USBPORT+0xa0d5
    bacd3ed0 b9922944 026e6f44 8a2d30e0 8a2d30e0 USBPORT+0xad47
    bacd3f08 b992413a 8a2d3028 80548abc 8a2d3230 USBPORT+0xb944
    bacd3f34 b993224b 8a2d3028 80548abc 8a2d3028 USBPORT+0xd13a
    bacd3f70 b99323c2 8a2d3028 00000001 8a34a834 USBPORT+0x1b24b
    bacd3f8c ba6b8d54 8a2d364c 6b755044 00000000 USBPORT+0x1b3c2
    bacd3fbc 8a34adb2 8a34a310 b993225c bacd3fd0 sptd+0x11d54
    bacd3fc0 8a34a310 b993225c bacd3fd0 80547e6f 0x8a34adb2
    bacd3fc4 b993225c bacd3fd0 80547e6f 8a2d364c 0x8a34a310
    bacd3fc8 bacd3fd0 80547e6f 8a2d364c 8a2d3028 USBPORT+0x1b25c
    bacd3fcc 80547e6f 8a2d364c 8a2d3028 00000000 0xbacd3fd0
    bacd3fd0 8a2d364c 8a2d3028 00000000 00000000 nt+0x6ee6f
    bacd3fd4 8a2d3028 00000000 00000000 b401ff4a 0x8a2d364c
    bacd3fd8 00000000 00000000 b401ff4a 6803fe95 0x8a2d3028
    STACK_COMMAND: kb
    FOLLOWUP_IP:
    applemtm+53b
    b7fcb53b ?? ???
    SYMBOLSTACKINDEX: 4
    SYMBOL_NAME: applemtm+53b
    FOLLOWUP_NAME: MachineOwner
    MODULE_NAME: applemtm
    IMAGE_NAME: applemtm.sys
    BUCKET_ID: WRONG_SYMBOLS
    Followup: MachineOwner
    ---------

    My MBP crashed with exactly the same dump. The crashes occurred during a StandBy operation (My MBP crashed regularly but not reproducably while trying to stand by/sleep).
    Microsoft (R) Windows Debugger Version 6.9.0003.113 X86
    Copyright (c) Microsoft Corporation. All rights reserved.
    Loading Dump File [C:\Documents and Settings\vas\Desktop\Mini070508-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    Symbol search path is: srvc:symbolshttp://msdl.microsoft.com/download/symbols
    Executable search path is: c:\windows\i386
    Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 2600.xpspsp2rtm.040803-2158
    Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
    Debug session time: Sat Jul 5 22:53:49.999 2008 (GMT-7)
    System Uptime: 0 days 22:33:47.814
    Loading Kernel Symbols
    Loading User Symbols
    Loading unloaded module list
    * Bugcheck Analysis *
    Use !analyze -v to get detailed debugging information.
    BugCheck B8, {0, 0, 0, 0}
    * WARNING: Unable to verify timestamp for applemtm.sys
    * ERROR: Module load completed but symbols could not be loaded for applemtm.sys
    Probably caused by : applemtm.sys ( applemtm+53b )
    Followup: MachineOwner
    1: kd> !analyze -v
    * Bugcheck Analysis *
    ATTEMPTEDSWITCH_FROMDPC (b8)
    A wait operation, attach process, or yield was attempted from a DPC routine.
    This is an illegal operation and the stack track will lead to the offending
    code and original DPC routine.
    Arguments:
    Arg1: 00000000, Original thread which is the cause of the failure
    Arg2: 00000000, New thread
    Arg3: 00000000, Stack address of the original thread
    Arg4: 00000000
    Debugging Details:
    CUSTOMERCRASHCOUNT: 1
    DEFAULTBUCKETID: DRIVER_FAULT
    BUGCHECK_STR: 0xB8
    PROCESS_NAME: System
    LASTCONTROLTRANSFER: from 80544c3b to 804f9c12
    STACK_TEXT:
    bace7ccc 80544c3b 000000b8 ffffffff 00000202 nt!KeBugCheck+0x14
    bace7cdc 8054498b bace7d24 88d3b418 bab40120 nt!ScPatchFxe+0x46
    bace7cf0 80502b17 88d3b488 88d3b418 804fad6c nt!KiSwapContext+0x2f
    bace7cfc 804fad6c 00000000 00000000 8a19a4b0 nt!KiSwapThread+0x6b
    bace7d24 b7022569 00000000 00000000 00000000 nt!KeWaitForSingleObject+0x1c2
    bace7d50 b7067e4a 8a0c2a30 00000000 8a37efb0 Wdf01000!FxWaitLockInternal::AcquireLock+0x3a
    bace7d6c b939853b 8a0c2ae8 75e65b78 8a19a480 Wdf01000!imp_WdfWaitLockAcquire+0xc9
    WARNING: Stack unwind information not available. Following frames may be wrong.
    bace7d8c b9398651 75c81210 89eee008 bace7de8 applemtm+0x53b
    bace7d9c b70421b2 764c7c80 7652beb8 bace7dc0 applemtm+0x651
    bace7de8 b7042253 b7073a08 89ad4140 89b38378 Wdf01000!FxRequestBase::CompleteSubmittedNoContext+0x63
    bace7e00 b70195d3 89eee12f 89ad4140 00000000 Wdf01000!FxRequestBase::CompleteSubmitted+0x97
    bace7e1c b701968d 01b38378 88a9ed80 bace7e48 Wdf01000!FxIoTarget::RequestCompletionRoutine+0x195
    bace7e2c 804f053f 8a053350 89eee008 89b38378 Wdf01000!FxIoTarget::_RequestCompletionRoutine+0x35
    bace7e48 804f13e2 8a053350 89eee008 88a9ed80 nt!IopUnloadSafeCompletion+0x1d
    bace7e78 b9843ee5 89eee008 892f5ee0 8a25c028 nt!IopfCompleteRequest+0xa2
    bace7ee0 b9844b57 89bdc4a8 00000000 8a25c7d8 USBPORT!USBPORT_CompleteTransfer+0x373
    bace7f10 b9845754 026e6f44 8a25c0e0 8a25c0e0 USBPORT!USBPORT_DoneTransfer+0x137
    bace7f48 b9846f6a 8a25c028 80545aac 8a25c230 USBPORT!USBPORT_FlushDoneTransferList+0x16c
    bace7f74 b9854fb0 8a25c028 80545aac 8a25c028 USBPORT!USBPORT_DpcWorker+0x224
    bace7fb0 b9855128 8a25c028 00000001 89edc578 USBPORT!USBPORT_IsrDpcWorker+0x37e
    bace7fcc 80544e5f 8a25c64c 6b755044 00000000 USBPORT!USBPORT_IsrDpc+0x166
    bace7ff4 805449cb b3f6362c 00000000 00000000 nt!KiRetireDpcList+0x61
    bace7ff8 b3f6362c 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x2b
    805449cb 00000000 00000009 0081850f bb830000 0xb3f6362c
    STACK_COMMAND: kb
    FOLLOWUP_IP:
    applemtm+53b
    b939853b ?? ???
    SYMBOLSTACKINDEX: 7
    SYMBOL_NAME: applemtm+53b
    FOLLOWUP_NAME: MachineOwner
    MODULE_NAME: applemtm
    IMAGE_NAME: applemtm.sys
    DEBUGFLR_IMAGETIMESTAMP: 47685ec5
    FAILUREBUCKETID: 0xB8_applemtm+53b
    BUCKET_ID: 0xB8_applemtm+53b
    Followup: MachineOwner
    Message was edited by: tourist604

  • How to do a simple "Barn Door" effect?

    Just playing with the tool set and trying to come to terms with things.  How do you you do the following:
    Put an anchor point on the right edge of raster on a full screen piece of video and then rotate the full screen image around that anchor point to have the image swing around it with 3D perspective?  The classic barn door DVE move.  I am having no success doing this with native Premiere tools.
    Thanks,
    Jef

    Hi Jef,
    I remember the DS. Regarding a 3D DVE effect in Premiere Pro, please make a feature request: http://adobe.ly/feature_request
    Jef Huey wrote:
    Hello Kevin,
    I am trying to determine if Premiere will satisfy my client's expectations for effects work within the editing application.  I do realize that some of the things I look for can be more easily dealt with by pushing to After Effects than Premiere.  And I would prefer not to get into a discussion about Dynamic Link here.
    Effects in all NLEs are pretty basic from my experience (Avid, M100, FCP, and now Premiere Pro). That's why editors use plug-ins and compositing applications. The interoperation between Premiere Pro and After Effects is like no other NLE I've used, however. That is a major strength.
    Jef Huey wrote:
    My impression at this point is that many of the effects available in Premiere are based on the legacy development of the product.  Effects that were built as the capabilities of the system increased.  As a result, to MY mind, there are some problems here.  This question I posed is a prime example.  And you can see in an other thread I started, that I point to some of these.
    I understand your frustration. Are you using the Mac or PC version? There are more effects with the PC version, so please check that out.
    My viewpoint comes as someone who creates and maximizes effects within an NLE, so I do know where you are coming from. What I do is max out the capability of the NLE's effects, then move to a compositing app or plug-in only when necessary. I never expect a NLE to have everything I need when constructing advanced effects.
    Jef Huey wrote:
    As a point of example, here is the UI presented when you put a DVE effect on a clip in Avid DS (rest in peace).  This one effect encompasses at least 5 Premiere effects.  There are no render orders to consider to get what you need as I seem to run into with Premiere.  Not to mention you can do what I set out to do in one effect.
    Seems reasonable. I wonder if you'd need 3D capability within Premiere Pro (like AE's 3D layers) to accomplish that? In DS, this effect came from Marquee, which operated in 2.5D space, if I'm not mistaken. Feel free to make that feature request.
    Jef Huey wrote:
    I see great promise in Premiere.  But as with all software, finding a way to leave some legacy tools and thought processes behind can be difficult. Especially when there are potentially competing products in house.
    Legacy "anything" is left in the product to open older project files, as well. Something to keep in mind.
    As far competing products, Premiere Pro and After Effects do share technologies but I do not think that Premiere Pro will ever have all the compositing capabilities that After Effects has. Conversely, After Effects might never be a great tool to edit video with.
    Jef Huey wrote:
    But with the current Creative Cloud model, it would seem that Premiere should not have to "compete" with After Effects for revenue.  Every customer gets both for the same dollar spent.  So tools that would be useful in one should not have to be "reserved" for one of the applications merely to preserve it's market share.  Modern video editors use the DVE tool set more than any other.  At least in our shop.  I find the Premiere methods quite old fashioned and cumbersome.  I can see from my other threads that my view is not universal.
    Looking forward to seeing that feature request. Thanks, Jef.
    Best,
    Kevin

  • Mx.transitions + movieClipLoader + Crashing Flash IDE

    Well I got this code straight from the adobe site and it is
    suppose to show how to use the mx.transition class with a movie
    clip loader. When I look at the code it seems right but the flash
    Ide keeps crashing but before that happens it prompts me that the
    code is causeing the player to be unresponsive like ther is a loop
    or something that won't end. I don't see any loop and would expect
    this code to have been edited on the adobe site if it were
    incorrect especially since it is fore mx 2004.
    and the link to the tutorial on this site.
    http://www.adobe.com/devnet/flash/articles/tweening_09.html

    Bad fla. Copied code and placed in new file work
    perfect.

  • NetAuthAgent causing crash/freeze.....

    I have a problem with my laptop totally freezing whenever I try to connect to an external network drive.
    This post explained the problem:
    http://discussions.apple.com/message.jspa?messageID=6412555#6412555
    I have now discovered it appears to a process called NetAuthAgent causing the crash and I'm getting the following errors posted in a few logs in console:
    22/01/2008 6:19:32 pm /System/Library/CoreServices/NetAuthAgent.app/Contents/MacOS/NetAuthAgent139 CPSGetProcessInfo(): This call is deprecated and should not be called anymore.
    22/01/2008 6:19:32 pm
    /System/Library/CoreServices/NetAuthAgent.app/Contents/MacOS/NetAuthAgent139 CPSPBGetProcessInfo(): This call is deprecated and should not be called anymore.
    Anyone have any idea what's going on?

    I couldn't disagree more - there are many many reports in various forums of people having various problems with using SMB networking under Leopard - all of who report no problems when previously under Tiger.
    Your really don't expect your networking ability to take a backwards step when upgrading to a new version of your system software.....
    it would be one thing if the issue with with some really out-dated legacy product (some ancient tape drive or something), but in this case the majority of problems appear to have been with true network based drives - these are becoming more and more common - heck! - even Apple are now making their own version to run on time machine - this is an increasingly common technology and a major oversight of beta testing to not detect the problem - or even manage to fix it by 10.5.1
    Don't get me wrong - i have been an apple fan since my LCIII and System 7! - I went with them as we migrated to PowerPC chips - and then into unix- and now intel.
    Each software migration has been amazingly good and stress free.
    I currently have several issues with Leopard - all of which that worked fine under Tiger - and only some of which have been fixed with 10.5.2 - I have never been so disappointed. I am also aware that there are many other people who feel jut as strongly about being unofficial beta testers for leopard.
    I have always noticed that whenever Apple took us all on an software upgrade there were always unhappy people - but this time there seems to be more than ever - and even people erasing Leopard and reverting to Tiger again.
    For now I can't face a reinstall - so I will continue to put up with the problems I've been having with Leopard - and thank the lord I don't rely on macs for my daily business - if I had been relying on my computers for an income the nightmares I've had with Leopard (and hours of time lost putting things right) would have been a serious issue.
    So yes - I remain an apple fan - but I think they have to accept criticism when due - and Leopard appears very much to have been released prematurely - and at a time when Vista was attracting sooooooo much bad press I reckon it should have been the A1 top priority to make sure that when Leopard was released it was immaculate (or pretty close to it).
    As it was you had most major mac publications (in the UK at least) and several mac online sites issuing warnings about upgrading for far too many months after release.
    I used to enjoy my listening to windows user bemoaning their lot and complaining they thought Microsoft built-in designed problems to force continual upgrading to ever more complicated and unreliable leaky OS software..... and I could just say - well, I use an Apple mac!
    But this time - it was a real opportunity to spread the apple good news gone begging.
    On the plus side - 10.5.2 appears to be making progress towards redeeming itself!... but there are still some big issues.
    (as a final note - this is another of the many examples where broadband had made sloppy programming acceptable - there was a time when I relied on cover discs on mac magazines to get my software updates since I had no internet access..... or then when I had dial-up and a 100mb update was a really big deal - in those days software had to be right (or pretty much so- FIRST time) - these days you just chuck it out the door knowing that if its all wrong the miracle of broadband and an automated software updater will get you out of problems..... so why bother paying people to test - let them buy the product and dix the problems as they occur!)

Maybe you are looking for