We have several users of BRAW Studio experiencing timeline shift after moving their projects between computers. Sometimes it even goes back to the first frame.

If this also happens to you please tell your story in Adobe Community Forums : https://community.adobe.com/t5/premiere-pro/cc-2020-timeline-clips-shifts-after-moving-project-relocating-relinking/m-p/10923880

Happens only with CC 2020 (both 14.0.0 and 14.0.1), both OSX and Windows, all framerate (23.96 fps and 25 fps for example).
Apparently happens with others formats than .braw : https://community.adobe.com/t5/premiere-pro/linking-media-losing-in-and-out-points/td-p/10922669 "I have this problem on every file type I have tried; R3D, BRAW and CRAW"
Attached is a zip with the two .prproj from a user editing with .braw and you can see what's changing inside <MediaFrameRate> and <TimecodeFormat>, also the timecode changes from 01:43:25:03 to 01:43:31:16000

Please investigate and fix this issue it is very annoying and preventing users to edit in good conditions with Premiere Pro it is quite urgent

Thanks,
Antoine

Mac OS 10.15.7, Premiere 2021 (15.2.0 Build 35)

FIX PROJECT MANAGER.

I've been doing a little looking around, wasting valuable billing time trying to make sense of why the Project Manager is such a piece of shite.

So here's what I discovered yesterday...

I attempted to Collect and Copy a problemetic project, which has failed before. And it failed again, but not before I got a glimpse of the stupid way you've coded this routine.

What I did was watch the Finder during the progress of the Project as it was collected and copied to the new location. Premiere began the process by writing the copied files to the location I specified...until it stopped, with the dreaded warning "An unknown error occurred"...yeah, ********.

What I DIDN'T do was click OK at that point, and supposedly Save the project... which also BLOWS AWAY ALL THE "COPIED" FILES!

I left the box open, and copied what was in the partially-collected project over to another drive. SO NOW, I have a record of what might have caused the the routine to hiccup. It seems to get hung up on files with long long long paths, such as found in these infernal multi-part MXF, and other files that bury the actual media under a ton of folders.

So, geniuses at Adobe, you may want to start there and see if there's some limitation in terms of qualified file names when running the PM.

In order to put Adobe in the era of 2021, this is a project that could cost to much for Adobe, but they should definitely try. Work on a new application to create a livestream more easily and efficiently.

• Manage your livestream in the Premiere Live app.
• Connect your feed to Facebook, Instagram, or any social media platform that allows livestreams. Give the possibility to use RTMP/RTMPs or UTP protocol.
• Ingest others videos feed from their phone or webcam through the Premiere Live mobile app or through a dedicated link on the web (ex: live.adobe.com/UserID/CodeOfTheLiveSessionsInAlphaNumericNumbers.prl
• Make the possibility to import from Creative Cloud, .mp3, .mov, .PDF, .ai .png and all other files that could help and create a presentation in live.
• Give the possibility to add custom overlay, to cue in and out a video.
• Make a user-friendly multi view screen.
• Allow 3rd party software.
• Mix it with AR to change the face or the background of your guest.
• Platform should create embed code for website.
• Add Color Lumetri and Lumetri scopes to correct any visual sources.
• Add live audio effect from Audition to remove noise, echo cancelling and any other audio improvements.
• Make a media player that could be cued by the timeline. With in/out option.
• Link libraries with Premiere Live to push instantly a file that just been drop.
• Make a switcher platform that could switch between A/B or Preview/Program.
• Give the access to push social media comment in program screen
• Studio chat (to talk to your guest)
• Media chat (to talk to your listeners - And add option to talk to only one media platform or all).
• Allow screen sharing with users.
• Allow Adobe CC teams to separate task (one at the video, one at the overlay, one on the sound, one managing online comments, etc.)
• You can operate the live online or in the app.
• Add user to manage their windows preferences, ex: Program at top, audio bellow, overlay at left, or anyway that you want to put it.
• Make system info like PCU, cache and stuff that livestreaming tech needs.
• Add transitions and effects or create & import your own
• Add the option to output your feed as a webcam, to use it in Teams/Slack/Messenger or Zoom for educational/business presentation purpose.
• Saves the current live as a project to keep your work inside.
• Put media management to import Adobe files to your session.
• Add live close captions with AI improvement.
• Use GPUs to render it live.
• Allows ISO record sessions to edit each sources later with Adobe Premiere Pro, with an .xml file.
• Allows sessions records for instant playback.
• Add mask, grid, and other logical tool.
• Allow importing Essentials Graphic to change in real-time and render in real-time an animation.
• Allow live responsive reaction between the user blueprint, while he is listening, to reconfigure the source horizontally or vertically.
• Make Python/CSS and HTML5 integration to push a link/webpage or a program in the iframe of the live.
• Make the possibility for user to draw, write in the screen.
• Give option why guest/users to raises hands.
• Allow VISCA protocol trough IP to control camera, iso, iris, white balance of a professional camera.
• Import LUTs and color preferences.
• Allows MIDI and DMX to cue/set/control with custom asset.
• Make simple preset for usual customer.
• Export live at the end, in the codec of your choice
• Allows RTMP pulls links
• Schedule time to push live the event.

And hardly enough, create a new video protocol that splits and allows custom overlay graphic links over a live video feed in real time (like an HTML5/web-base link button over an iframe of a video player but customized to react in real time when the producer want to push it), this protocol could also not send the same overlay between social media/destination and could be responsive thought. The protocol should also send back data for UX/UI, marketing purpose and technical feedback. And make this, the new RTMP.

I'm able to help if this idea is made.

Please include the option to retain folder structure when managing a project via the Premiere Dialogue.

We go through great efforts to maintain an organized project, both within Premiere but also at the Windows Explorer level. It's incredibly frustrating that if we try to move a project, archive a project or just generally manage the project that Premiere takes all the files and dumps them in a messy pile in one folder.

We've stopped using it entirely, instead opting to copy assets manually and re-linking the project to the assets. It's a tedious process and doesn't allow for trimming or transcoding.

I can set a thumbnail for my videos in whichever Bin the asset resides, after a shoot it would be great to be able to print a contact sheet of assets so that the client knows what's all there. Yes I "could" do a screen capture or some other work-around... but contact sheets are standard needs and it make sense to be able to hover over the clip, select the inpoint and use that as the thumbnail. Then allow me just like in Bridge to control the layout and make thumbnails.

*Note You can sort of do this in bridge, but can't change the thumbnail and often times the camera is rolling before the final framing of a shot.

When Reassociating a selected sequence in a project within a Production, currently you have to open one [media] project at a time and for all sequences in each [editing/sequence] project.

What would be nice is if we could open a project full of sequences, select them all and then 'Reassociate Master Clips with All Open Projects". That way we could have open already our media projects (which we can open all at once) and then do a big 'reassociate' all in one go. (open to even more simplified suggestions like 'Reassociate with all projects in the Production' or a function like this at Production panel level - e.g. highlight a bunch of projects and choose 'Reassociate projects with all other projects'

-Additional info:
I'm working on a large documentary with footage shot over several years. The project got too big to handle and there are now two people working on it simultaneously so we broke down the project into a production Sith 7 Media projects and several Editorial projects containing sequences of compilations, assemblies and various iterations of the master edit. Breaking down the original project into smaller parts causes ALL the sequences to lose their associations with media because they think they are still in the original oversized project. If you 'reveal in project' any clip in any of the sequences, it asks for the original project. So you Reassociate Master Clips, in our case, 7 times for each project containing sequences! - you can see why this would be handy to be simplified for anyone making a documentary that grows larger than initially expected - good doco's always do!

Thanks for your consideration.

At my work we export a fair amount of XMLs. When I receive a Premiere file from a coworker and open it on a different computer, it gives me the missing media popup every time I open the project, even if all the other media is online.

The "offline media" is FCP Translation Result .txt files, and the file path is always "/Users/(username)/Documents". There's no "Clip Name" displayed, since they're not stored in the project panel, or anywhere user-facing. This happens anytime the Premiere is unable to locate these .txt files.

It's not a big deal to just Offline All and move on with your day, but it is an annoying and unnecessary step.

Would it be possible to have these missing Translation Results not appear in the Missing Media popup window, or perhaps just have them not linked at all in the Premiere Pro project after exporting the XML?

Media management relinking seems to require that every video file have a distinct name, even when those files are in different directory structures. For instance, many cameras shoot their video files with generic names (C001, C002, C003, etc.). When shooting with the same camera on different cards over multiple shoots, we will often have footage dumps separated in different folders for each day but with the same filenames in the respective folders (e.g. Day1/C001.mov, Day2/C001.mov, etc.). This seems to confuse the Media Management relinking functionality in Team Projects, causing some footage to be ignored (e.g. when all instances of C001.mov only use the Day1 clip and ignore the Day2 version).