1 Reply Latest reply on Sep 13, 2017 10:31 PM by Roei Tzoref

    Rendering PNG Sequence to a Local Drive Causes AE Error

    Benjamin_Markus Level 1

      I recently switched to a Windows machine and now I'm getting this exact same error, in the same order, as shown here on this Creative Cow post, only this happens when I'm rendering to a local secondary drive.  From the look of the Creative Cow post it appears this is a bug.  For now, using AE's "Queue in AME" option is a viable workaround, but it's slow and annoying to set up especially since AME doesn't delete AE's frame padding placeholders, i.e. [#####], and they have to be manually deleted in the AME queue.  It would be great if AME just respected AE's naming conventions.  Anyhow, I'm using this machine in production and rendering via AME is an added step and slows down the pipeline.  Therefore, it would be great to get this fixed.  Thanks.



      Windows 10 Pro 64-bit

      After Effects CC 2017.2 Version Latest Update


      System Core:

      Motherboard: Gigabyte GA-X-99-Designare EX Rev 1.0

      CPU: Intel Core i7 6950X 3.00GHz, Ten Core 25MB 140W

      Ram: Crucial 128GB DDR4-2400 (8x16GB)

      Video Card: EVGA GeForce GTX 1080Ti 11GB

      Sound Card: Onboard sound



      Primary drive: Samsung 850 Pro 512GB SATA 6GB/s 2.5inch SSD

      Secondary drive: Samsung 850 Pro 512GB SATA 6GB/s 2.5inch SSD

      Internal RAID5 Array: 13.6TB (6x Seagate Barracuda 3TB 7200 rpm SATA III 3.5inch (OEM)

      CD/DVD: Asus 24x DVD-RW SATA (black)


      Case / Cooling:

      Case: Fractal Design Define R5 Titanium

      Power Supply: EVGA SuperNOVA 850W P2 Power Supply

      CPU cooling: 2x Noctua NH-U12DX i4

      Additional Cooling: Arctic Cooling MX-2 Thermal Compound Upgrade