We’ve marked this Under Review, see comment.
This perfectly sums up UserVoice as a whole:
"August 07, 2018 - We've marked this Under Review" - It's now February 3rd, 2020.
@ Jonah Lee Walker
Absolutely! I know how to make a keyframe. If I want to make one, I'll make one.
Normally I'm all for making something a preference option, but this is one of those weird times where I have to ask: Is it really worth spending the time adding a preference option for this?
I don't know. The auto-keyframing for opacity being on just strikes me as weird right from the word go.
Maybe that should just be the default starting point: Auto-keyframing off. Across the board.
*Tries to think of a place where default auto-keyframing wouldn't be frustrating. Fails.*
Yup, across the board.
Thanks for all the feedback. It’s pretty clear that we’ve got to look into the workflow using this format more closely, there are enough reports about gaps at this point to reopen this item. I’ll post more info about next steps shortly. In the meantime, a couple of questions are easy to answer:
- The plugin is designed for Premiere Pro. It currently doesn’t provide support for After Effects.
- It does work with AME, so if you want to use it for batch processing, that’s very doable
- If you’ve started a project with Autokroma, there’s no easy way to transfer it to be running with the new plugin.
Hey there Melissa,
Sorry to hear that you're running into this as well. I really do wish that I could say that I've figured out some work around, but nope, things are just as broken as they were before.
Yup, I think a lot of people feel very similarly. Premiere Pro, and Adobe support as a whole, tends to resemble a dumpster fire way too often, and the idea of just cutting ties with Creative Cloud and Adobe is super-tempting, but then there's After Effects, Illustrator, PS, Lightroom Classic, etc, and it becomes a bit more complicated.
Rock, meet hard place.
[Citation required] :-P
Agreed! I came here to pop in a feature request for this exact thing, and then saw your post. Vote added.
That's so bizarre! I don't know why they would heavily limit access to older versions. In CC, when I click the "looking for older versions link" I get sent to a page for 2017 versions of Illustrator, InDesign, and Photoshop...no Premiere, or any other video applications.
Kind of hoping that this is just some weird oversight.
Sorry man. If I come across any way of getting to the older versions of Premiere, I will let you know.
Hey Jón Kristinsson,
Sorry to hear that you're running into this as well. So far the only workaround that we've found is to drop back down to 13.1.3, and don't upgrade until whatever was broken with the updates gets fixed. Yeah, I know, that's hardly a workaround at all, but it might save a bit of misery for the time being.
In the screenshot you can see an example from System B.
This is the audio bin in Premiere, which shows the clip "DX_JAPAN_020.WAV". When the project started, we were using the file JAPAN_020.WAV, but I eventually ran that file through external software for noise reduction, and saved it as a new file, "DX_JAPAN_020.WAV". This was saved in a new folder, as part of my brute force testing to get around this bug. I then used "Replace Footage" to change out the original JAPAN_020.WAV in the project.
This was all performed on System A.
The project was then opened on System B, and this is where the screenshot comes from. I've brought up the Properties for the clip, and although it is showing as being correct in the bin itself, you can see that it is linking to the incorrect file. For what its worth, it's also linking to the incorrect folder as well.
Just found someone else with what appears to be the same issue:
Adding some more detail:
One thing which I haven't previously mentioned is that this wasn't happening before the most recent update.
We've tried testing with Shared Projects as we were advised that this could help, but we had no luck, and ran into the same issues.
We also tried brute forcing our way around the issue, but unfortunately failed again. I'll explain, using the music example again.
When replacing demo music, instead of putting the licensed file into the same folder as the demo track, create a new folder, and put the licensed track in there. Within Premiere, use the replace footage command to link to the licensed track in the new folder. This should make Premiere look for 1) a new filename, and 2) a new folder.
No luck, unfortunately.
As it stands, we can't use Replace Footage. Any help is greatly appreciated.
I just remembered another bizarre bit of behaviour:
When we replace the footage, save, and close, and then open on OS B, the timeline will show the updated filename, but will definitely be using the wrong file.
If we reveal that clip in project, it shows the correct file in the bin, however if we reveal in Finder/Explorer, it takes us directly to the incorrect file.
So, yeah. Weird. Premiere will be showing that it's using the correct file, but heading to the actual file shows that things are not right in Denver.
Could you elaborate?
I just realised that I didn't mention that we would be reconnecting to files with different names, or different extensions (eg: Replacing watermarked music tracks with final licensed versions) or sometimes both.
I'm not really sure how the file path would come into play here, as shouldn't it be looking for a wholly different file at this point?
So, instead of "watermarked_tunes.mp3", it would be "final_tunes.wav".
Happy to fire through more information if you need it, but something is definitely weird here. Much like what Ryan mentioned back in 2017.
Hey there Kristofer,
We're running into this exact issue as well. Have you had any luck/success in figuring out a workaround? Some folks suggested Shared Projects, and we tried that route, but no luck.
I'm really hoping that you found something? I've started a discussion here:
And I also posted a UserVoice bug, but as you can imagine, that's been a ghost town:
Could you clarify what you're saying here?
Are you trying to put a full clip (so every second of that clip, from beginning to end) on the timeline, and then put another full clip straight after it, and then apply a transition between the two?
Yes, that could be correct. To be honest, I have been behind the wheel on the Mac operations that I've been comparing to, so I might have missed some of those details. It was more a "hey, has anyone else noticed this? No? Nuts." type scenario :-P
Good suggestion on the workaround. I shall give that a go!
Same thing happening here. For us it really only appears to be on Windows systems, as the Macs don't seem to show it (or at least not as badly).
Essentially here, as soon as you hit play on a stabilised clip that is a different resolution to the sequence, it shrinks down. Stop playback and it goes back to normal.
Basically WS is currently unusable on the Windows systems without the old nesting trick.
Hey there Christiaan,
Random question: Are you in Windows? If you get Prem to the point where it looks as though it has hung, and you wander away for five or ten minutes and come back, has the situation changed?
I ask because I sometimes see similar things here, but only in Windows. If I leave things alone for a good few minutes, everything suddenly progresses. It almost seems as though it occasionally decides to lock me out until it has generated the peak files.
Hey there Szasz-Fabian,
You can select the effect, and hit "backspace", or "delete". Either work.
Make sure to use the delete key by the dedicated "insert", "home", "end", etc, keys, and NOT the one by the numerical keypad on the far right of the keyboard - that one will behave as a "0", and won't get anyone very far :-)
Also, in the context menu which you showed in your screenshot, "clear" is the equivalent of delete/remove, so you can click that, and you will remove your effect.
If you want to remove effects from several clips in your timeline, you can highlight them, and use Remove Attributes from the context menu.
Hopefully that helps :-)