Forum Replies Created

Page 1 of 2
  • Yes. Same issue I bumped into and I am so mad…

    https://www.onethyme.com

  • I have the same problem. So far I have spent a day on it or so and finally decided to give up. Whatever drop shadow I apply (with AE dynamic link from AE or drop shadow from Premiere itself) with GPU acceleration it looks soft (less shadow). If i turn it off to software only, then it is ok before rendering, after rendering the shadow is gone (almost). Now I just use GPU for the faster editing, then I export from AME instead of exporting from Premiere. So some of the shadows at least come back… If anyone knows a solution to this problem, please let me know. Thanks.

  • I have the same problem… Is there any solution to this at all? Thanks

  • Attila Kovarcsik

    May 16, 2014 at 4:56 pm in reply to: Suggestions for AVCHD green screen workflow.

    Hi guys.

    I have a same problem, I have done a decent chroma key out of AVCHD and with dynamic links to AE. But a 20 minutes video takes 6-12 hours export from Premiere using AME (1 pass VBR). Is there any way I can speed it up? I mean converting the original source material to MOV or anything else with Adobe Prelude first then rejoining the clips. Will it give any quicker export times compared to AVCHD files?

    Also even if I enable CUDA or OpenCL engine on the timeline with my 2012 Macbook Pro I still cannot play the video in real time. It is choppy and a bunch of frames are dropping. That is even a bigger problem for me.

    And third, sorry if it is off topic, but you can guide me to the right forum if there is any, I am having problems with the export video itself. For now I turned off Mercury engine and I use only software. But on the export one of the drop shadow, created by AE dynamic link is missing. Clearly it is there on Premier’s Program monitor. Any idea why it is not there?

  • Thanks. I just sent them en email as well. Too bad. It should not be that hard to implement and such a useful effect. I basically would like to morph into my extruded text logo. Anyway thanks.

  • Same here. Any solution?

  • Attila Kovarcsik

    October 17, 2013 at 9:07 pm in reply to: Audio track mapping problem

    I am using Premiere CC. It is so strange how it works compared to CS 5.5.

  • I think the Audio mapping part behaves really weird in PP CC compared to CS 5.5.

    In CS 5.5 I could easily import and change my 1 recorded stereo audio source (AVCHD solution for 2 mono channels) to normal mono channels. Then when I placed it on the timeline, I could unlink them and I ended up with two separate audio channels BALANCED to centre (which means that if I delete one of them the other one stays centred).

    In CC whatever I do, either I have 2 mono channels duplicated on the timeline (which does not make any sense), or with some specific custom setting I end up with two separate audio file, but once I delete one of them I realize that it is balanced to one side. So It is still not FAKE stereo what I want after all.

    I tried to apply a Fill right/left effect but did not work as it does not enable to drop it on for some reason.

    Any advice to get back the original working workaround? Thanks

  • Attila Kovarcsik

    July 27, 2013 at 1:01 am in reply to: Relay Recording with NXCAM

    Thanks a lot. For now I had to shoot in FH intead of HX. but still would be ood to know what the right way is.
    I googled and learbed tht first I neeed to register the folder where I would like to import the files. But after when I click on the Import buton it gives me some error message. I tried hundred times already. Maybe the install of the CMU software was not good. Or it is just the virtual PC on my mac. I will try it later again. Thanks

  • Attila Kovarcsik

    April 11, 2012 at 6:02 am in reply to: Sony NX5U Log & Transfer – timecode issues

    CS 5.5 do recognize timecode from NX5 I use it all the time. Though earlier versions did not support it.

Page 1 of 2

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