Skip to main content

Filter by idea status

10000+ Ideas

Philéas
PhiléasKnown Participant

"Restore open sequence when opening project" should also restore timelines in Source Monitor.Open for Voting

Hello ! Context :I'm using Premiere Pro daily with a timeline opened in my Source Monitor to have a similar configuration than the "Toggle Source/Record" from Avid. I find this workflow to be a lot more precise and pleasing than pancaked timelines, as you can anticipate exactly the start and end frame when puttings clips on the program timeline, and use the two monitors efficiently. This way of working in Premiere works actually works, but there are a few annoying bugs and small things missing that are really painful when using this workflow daily. This bug/feature which is here since a long timeline is one of the reasons this workflow sometimes feels painful (see this and this topic). The bug :Open multiple timelines both in the Program Monitor and the Source Monitor through the wheel and "Open in Timeline".Save the project and close Premiere Pro.Reopen the project.The previously opened timeline in the Program Monitor will be reopened, but the previously opened timelines in the Source Monitor will not. Even if the option "Restore open sequence when opening project" is activated from the settings. NoteIt is unclear if this behavior is intended or a bug, but from me, a sequence opened in the source monitor is still a sequence. From that point of view, the setting "Restore open sequence when opening project" should apply too ! The goal of this feature is to start working right after opening a project : everything you were working on is there and ready. So when you use a lot of sequences in the Source Monitor, this is a bit frustrating that you have to manually reopen all of those sequences for a minute or so. It doesn't feel quite right. Recorded on the latest available build : Premiere Pro 25.5.0.

pierstoval
pierstovalParticipant

Linux supportOpen for Voting

Since the team needs a huge bunch of people arguing and voting, maybe “just another request” will do.I can’t afford replacing my whole workstation, I have friends in the industry that don’t have this money either, and they use microsoft only for the Adobe suite (photoshop, illustrator or indesign, mostly).We pay for your product, and our workstation’s OS should not be an accessibility issue.You already support Mac and Windows. Linux is just a few steps further.We’re using Adobe suite mostly because, so far, other products are “not enough” (yet, be aware of that).If you don’t keep up with the pace where it’s going, people will migrate to another tool.I already have some friends that ditched Photoshop in favor of Affinity (and it’s FREE dang it). The change was hard, but they made it. Entire companies did, which is quite impressive too.On my side, I’m planning to work on requesting the Affinity team to make changes that will make it “closer” to how Photoshop works, for now, because it’s the quickest workaround.And Affinity works on Linux.I already use it sometimes, when it’s easy enough.In the meantime, some people have tried to hack into Wine/Proton in order to make Adobe CC installable on Linux. I’ve done my share of research too, but haven’t digged into Wine’s code enough to make relevant changes, but it’s on the way.Check these out:https://github.com/corbindavenport/creative-cloud-linux https://github.com/bottlesdevs/programs/issues/11 https://github.com/bottlesdevs/Bottles/issues/717 https://github.com/ValveSoftware/wine/pull/310 https://gitlab.winehq.org/wine/wine/-/merge_requests/10025If volunteers can do it in their free time, you must be able to do it too.You can do it guys.You’re rich enough to book a small team of 2-3 developers just to support this, and considering the expertise they should have, it can be done as quickly as in a few weeks.And if you don’t do it, well, it means that the loss of market will be somehow deserved, sadly.