У нас вы можете посмотреть бесплатно Pushing the Envelope #2: Program Settings & Project Locking или скачать в максимальном доступном качестве, видео которое было загружено на ютуб. Для загрузки выберите вариант из формы ниже:
Если кнопки скачивания не
загрузились
НАЖМИТЕ ЗДЕСЬ или обновите страницу
Если возникают проблемы со скачиванием видео, пожалуйста напишите в поддержку по адресу внизу
страницы.
Спасибо за использование сервиса ClipSaver.ru
In the second episode we examine: -A number of things I customize within the application preferences, like the media cache settings and project locking options. -How to keep our work and our application settings in sync with other editors. These settings are saved in the user document folder and that file can be shared to other systems to keep your settings consistent. On PC it is located in: Document/Adobe Premiere Pro/[your version]/[your profile name]/Adobe Premiere Pro.Prefs. This file when copied to other systems will keep all of your preferences consistent. The one thing that needs to be changed when sharing that way is the User Name for project locking. -Project locking is entirely based on that User Name value and won't work properly if two systems have the same User Name. So it is important to change that name immediately when sharing preferences to another system. -I always enable project locking even when working by myself just to prevent any issues from forgetting that it is not activated. When project locking is enabled, Premiere places a tiny lock file next to every project that you have open in the application. This has the same name as the project file, locking it but with a .prlock extension. -That locking functionality can also be taken advantage of to create lock files for systems that don't exist, to effectively make certain projects read-only to all users. To do this, set a temporary username like Read Only or No Changes. Open a project and copy the resulting lock file elsewhere. Set the username back and now wherever you copy and rename that lock file, it will render the matching project file read only. Manually removing the lock file allows the project to be edited as usual. -Using these techniques will help large productions being worked on by multiple editors flow much more smoothly.