Re: Getting this each time Beta opens...

MMeguro · ‎Aug 30, 2023

Thank you for reporting this. This issue should be fixed on the next Beta build.

MMeguro · ‎Jul 14, 2021

Please note that the potential fix is in the beta version now. It means the fix is coming to the release version in very near future.

MMeguro · ‎Jul 14, 2021

Under the new caption model, a sidecar file is treated as a data file whereas the old model treated it as a video file (this is why the old model placed captions in video tracks). Once a sidecar file is drag and dropped from the project panel onto timeline and captions are placed, captions in timeline becomes independent from a sidecar file. This is the reason why captions in timeline is not affected even if you remove a sidecar file from the project panel. The encoding process looks at captions in timeline, not a sidecar file in the project panel.

MMeguro · ‎Jul 13, 2021

Do you happen to export a media in a different frame rate than the sequence, or change the sequence frame rate via the sequence settings? This could be an issue that got fixed in the Beta version so far (and gets pushed to the release version in near future). If you are interested, you can install via Creative Cloud app > Beta apps.

MMeguro · ‎Jul 13, 2021

The fix is in the 15.4 beta as well 🙂 You can install it via the "Other versions" menu.

MMeguro · ‎Jul 13, 2021

The fix is now in the beta version. If you are interested in, it’s available via Creative Cloud Desktop under “Beta apps” section.

MMeguro · ‎Jun 07, 2021

We are looking into this. This is likely related to audio waveform drawing. Please try one of followings to workaround this issue. - Disable the waveform drawing in timeline (at the timeline wrench icon > disable "Show Audio Waveform"). - Render Audio (Sequence menu > Render Audio)

MMeguro · ‎Jun 07, 2021

We are looking into this. This is likely related to audio waveform drawing. Please try one of followings to workaround this issue. - Disable the waveform drawing in timeline (at the timeline wrench icon > disable "Show Audio Waveform"). - Render Audio (Sequence menu > Render Audio)

MMeguro · ‎Jun 07, 2021

We are looking into this. This is likely related to audio waveform drawing. Please try one of followings to workaround this issue. - Disable the waveform drawing in timeline (at the timeline wrench icon > disable "Show Audio Waveform"). - Render Audio (Sequence menu > Render Audio)

MMeguro · ‎Jun 07, 2021

We are looking into this. This is likely related to audio waveform drawing. Please try one of followings to workaround this issue. - Disable the waveform drawing in timeline (at the timeline wrench icon > disable "Show Audio Waveform"). - Render Audio (Sequence menu > Render Audio)

MMeguro · ‎Jun 07, 2021

This is likely related to audio waveform drawing. Please try one of followings to workaround this issue. - Disable the waveform drawing in timeline (at the timeline wrench icon > disable "Show Audio Waveform"). - Render Audio (Sequence menu > Render Audio)

MMeguro · ‎Jun 18, 2020

Try launching Premiere Pro while holding Shift key. When asked, say yes to clear the plug-in cache. If this doesn't help, try holding Shift+Cmd (Mac) or Shift+Alt (Win) and launch Premiere Pro. Note: the second option clears your preference settings. You may need to set your preference settings again.

MMeguro · ‎Apr 18, 2019

We just released Premiere Pro 13.1.1 to fix this issue. In AME, please uncheck Preferences > General > "Import sequences natively" to take advantage of this fix. If you are using GPU rendering, you can skip this step.

MMeguro · ‎Apr 11, 2019

Thank you for reporting here. Yes, we identified the problem and possible cause. We are currently looking into the solution.

MMeguro · ‎Apr 10, 2019

We want to know some more detail on this issue. I sent you a private message.

MMeguro · ‎Apr 08, 2019

Thank you for reporting the issue. I could reproduce this issue as well. But, I needed to set the speed higher than 5000% to reproduce this bug, instead of 500%. Could you tell me your source audio format (such as frequency, sample rate, duration, and bitrate) that you used to reproduce this bug with 500% speed change? I reported this to our bug database, but I would like to have better understanding of this bug. Meanwhile, I found a workaround of this issue. Please add Volume effects from Effects panel to all clips you would like to change their speeds. You can keep Volume effect to 0dB so there is no actual change in audio. I could encode with this workaround. Hope this workaround works for you as well.

MMeguro · ‎Dec 13, 2018

Since you are using older version of AME than Premiere (13.0 vs 13.0.1), there could be some changes in this area that AME doesn't have, but Premiere does. You may want to update to the latest. The latest version of AME and Premiere is 13.0.2.

MMeguro · ‎Dec 12, 2018

Besides nVidia driver update, I was told that Intel GPU driver may need to be updated as well if you have Intel Graphic enabled. You can check this from Device Manager > Display adapters. If Intel Graphics is listed there, please try updating its driver as well. This also need to be from Intel website directly, not from Windows Update or any other 3rd party. For some detail, please refer to Important Information on GPU and GPU Driver Requirements | Adobe Blog

MMeguro · ‎Dec 12, 2018

This option utilizes Intel CPU acceleration. Some CPUs are supported, while others are not. Not sure why you see this option is enabled in Premiere, but not in AME. Are you checking this option in Premiere and AME on the same machine? And are both Premiere and AME the same version? Currently, the latest version is 13.0.2.

MMeguro · ‎Dec 12, 2018

Regarding the latest driver you mentioned, I just want to make sure it's from nVidia, not from another source, like Windows Update or the computer vendor website. For your nVidia GPU, the latest driver is version 417.35 https://www.geforce.com/drivers/results/141171 When you are installing the driver, you may want to try the custom install option and use the "Perform a clean installation" option.

MMeguro · ‎Dec 12, 2018

Before starting encoding, can you open the Export Settings dialog of the job from AME and make sure "Hardware Encoding" is selected under the Video tab > "Performance"?

MMeguro · ‎Dec 11, 2018

So, did this problem start after updating to 13.0.0 (version2019), and no issue with 12.1.2(version2018)? I see you are trying to export into H.264. Does this problem happen with other formats as well? Could you try changing Media Cache Files and Media Cache Database (Edit menu > Preferences > Media) to somewhere on a local drive with plenty of free space and see if it helps? Also, could you see if changing the option "Import sequences natively" (Edit menu > Preferences > General) makes any difference? Please note that this option change takes place next time you import a project. Please import a project after changing this option.

MMeguro · ‎Dec 11, 2018

This may be related to Unable to import long scenes into Premiere? You may want to try the suggestion from Dan. "At the moment, I think the main answer is to use several shorter scenes. I'm not sure if ranged exports of the existing scene will work since the run-up rendering of ranges later into the scene will likely still accumulate the same memory so it gets consistent results that can be spliced together."

MMeguro · ‎Dec 10, 2018

We just released AE 16.0.1 and AME 13.0.2. These latest versions should fix this issue.

MMeguro · ‎Dec 10, 2018

We just released AE 16.0.1 and AME 13.0.2. These latest versions should fix this issue.

MMeguro · ‎Dec 07, 2018

How did you try to create an ingest preset? Have you tried the followings? - From Media Browser, click "+" icon > Create Ingest Preset - Preset menu > Create Ingest Preset

MMeguro · ‎Nov 06, 2018

Sounds like AME didn't get licensed properly. It went to 30 days grace launch and expired after 30days. Could you go to Creative Cloud app and launch AME by clicking "Open" button? If you don't see the "Open" button, please wait for a moment till Creative Cloud app communicates with the licensing server. This should license AME.

MMeguro · ‎Nov 05, 2018

Hi Chris, Yes, I could reproduce this beep sound when I queued AE comp to AME. It looks a new issue to CC2019. I will report this as a bug.

MMeguro · ‎Nov 04, 2018

Glad it worked!

MMeguro · ‎Nov 04, 2018

This could be caused by mismatch languages between OS and AE/AME. If they are not currently matching, could you try switching OS language to the language set for AE/AME to see if this helps?

MMeguro

MMeguro

Activity

Re: Getting this each time Beta opens...

Re: Issue with captions

Re: Issue with captions

Re: Issue with captions

Re: Moving a clip is not visible in timeline.

Re: Moving a clip is not visible in timeline.

Re: No display of the clip while moving them in th...

Re: Moving a clip is not visible in timeline.

Re: Premiere 15.1 UI issues

Re: Bug: Nested Sequence = Timeline Freeze / Invis...

Re: Premiere Pro 2021 Bugs Unacceptable

Re: Premiere wont open - gets stuck on "Loading Al...

Re: AME is crashing at the end of encodes

Re: AME is crashing at the end of encodes

Re: AME is crashing at the end of encodes

Re: Cannot export with any clips that are sped up ...

Re: Adobe Media Encoder Software encoding

Re: Media Encoder (CC2019 Problem) - hangs/freezes...

Re: Adobe Media Encoder Software encoding

Re: Media Encoder (CC2019 Problem) - hangs/freezes...

Re: Adobe Media Encoder Software encoding

Re: Media Encoder (CC2019 Problem) - hangs/freezes...

Re: help me guys please ???!!!

Re: AME CC 2019 shows test pattern when export HEV...

Re: Doesn't recognize HEVC/H.265 video layers expo...

Re: Create Ingest preset not functioning as expect...

Re: Adobe Media Encoder: Grace period has expired;...

Re: Minor Annoyance - AME 2019 beeps and boops at ...

Re: AE will not transfer to AME

Re: Media Encoder 2019 won't connect to Dynamic Li...