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:
[Citation required] :-P
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 :-)
Hey there Jessie,
Are you still running into this issue?
Couple of questions/requests:
What is the video codec for the footage?
What is the codec for the audio?
Could you post a screenshot of your Sequence Settings dialog box?
Could you also post a screenshot of your timeline?
This is really just to see if anything is jumping out.
If you render the timeline (video and audio), do you still get the audio drop outs?
This issue seems to be really intermittent here. We'll randomly have it work, and will have no idea why it suddenly decided to.
This happens on both Windows and Mac systems (all running the latest Premiere release - 13.1.5).
My shortcuts originated from an FCP template, and "go to in/out" is "Shift I" and "Shift O", respectively. You could always modify these to better suit your needs.
Yeah, not quite what you were after, but it definitely saves grabbing the mouse.
OS maximise/minimise controls for the second screen in Windows would be fantastic!
Agreed! This would be really useful to have. It's especially helpful when passing projects to other editors - tracks can be easily differentiated without having to look at the track name.
For example, Video Tracks 1-3 (coloured blue), could be for one particular thing, and 4-8 (orange) could be for something else. The editor can quickly spot the colours, and will know that there is some relation between the like-coloured tracks.
Quick and dirty example, I know, but it would get used quite a bit in our office,
What you’re suggesting would lead to a full on revision of the feature – therefore I’d like to ask a couple of additional questions:
what kind of footage do you usually try to stabilize with the Warp Stabilizer? And how much tweaking of the settings do you do on average?
@Jon Haile - Oh man, that sucks. We haven't spotted it on the Macs here, but it's definitely throwing a wrecking ball into the Windows system, so I was kind of wondering if it was just limited to Windows. I guess not.
If I find any other workaround, I'll post it here.
Is anybody else running into the issue where, when you apply Warp Stabiliser to a clip that is a different resolution to the sequence, and then hit play, the clip shrinks down, revealing any clips on the timeline below the WS clip, but as soon as you stop playback, it returns to normal size?
This is on our Windows systems. Essentially we still need to nest, or else WS is broken.
@Michael Gyori - Absolutely agreed that the footage and sequence resolution shouldn't have to be identical. Currently it's a massive pain with the nesting, and is way more of a chore than it needs to be.
Yup, pretty much. I don't think using it in the way we've described is particularly unique either.
Oh well, hopefully when the constant crashes are fixed, and the other ridiculous bugs (hello audio effect reset) are taken care of, WS can be addressed.
Currently 99% of our projects are output at 1080p, but we're shooting at anything up to 4.6k.
The footage itself will vary from project to project. Sometimes it's all handheld, and we're stabilising to make things a bit smoother. Other times, we might be on tracks, or steadicam, and are just wanting to get that extra bit of stabilisation.
The tweaking within the plugin will vary significantly depending on the shot. Sometimes the default settings are great, but more often than not we're doing anything from minor to major adjustments.
But the big point is that having to nest the "non-sequence res" shots before stabilising is a pain, and frustrating when you're making adjustments to the edit.