(I can send these to you too Bruce if you'd like) I've even put together a FB group to encourage others to submit their own feature requests, and put together several PDFs which I've sent to Adobe. A few Pr team members have reached out to me over the years to get my feedback, but it seems that most of it goes unheard. Unfortunately, in my experience as one of the most active contributors of FRs that actually contain well thought out solutions (rather than just complaints), what I hear more than anything from Adobe is crickets. In this case, what's important isn't just the quantity, but the quality of the individual contributors. I agree with Joseph and I would include myself in that group of passionate and critical editing base. In the meantime, making it so auto save will still run, but not interrupt you, is an incremental improvement we think most editors will really appreciate. Believe me, we have smart people working on that, but there's nothing to announce yet. The only way to do something completely new and different with save and auto save would be to move to a new type of project format. There's just no way around that, with this current project format. Any time the project is changed and then saved, the entire data has to be re-written to disk. Premiere Pro uses a single data file per project, not a database. When working with databases, it is possible to do things like save at each step, though, note that is not the same as auto saving a *copy* of the project. This is why you don't see your Resolve projects as files in your filesystem. Other than what the team already does by putting all new features through beta, making changes and getting user feedback on them before they're integrated into official releases, what else do you think we could do to further undermine the mystery of for the input! When comparing to Resolve's Live Save (save after each keystroke), you have to understand that Resolve can do that because it stores project data in a managed database. >Maybe that can contribute to Adobe being way more transparent in the future? >I think as users we don't care for the mystery of releases. prproj based on how many keystrokes have occurred since the error seems pretty heavy-handed.a "using a bandsaw to slice bread" approach. While that would solve the issue, so would PPro's "Undo", so reverting to a different. prproj from.let's see, the typo is the fourth character from the end of the line, so.5 saves ago!" The first step would be determining whether such behavior would address an actual user problem as noted above, even if such capabilities were available, the usefulness of such a capability is still debatable.Ĭounter-example: "Oh no, I made a typo in that title I added! I'd better close my current. No I mean whats the best course of action to get autosaves every keystroke and action?
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |