Sharing project files

Hi all,
I have kind of a basic question, but I want to make sure I'm doing it correctly so I don't face problems down the road:
I would like to copy my final cut project file and media files onto another drive so that the same project can be worked on by two editors in different locations. What's the best way to copy the media files so that they stay connected when you open the duplicated project file? Should I be using media manager, or can I just clone the video drive?
Also, when the two projects come back together, how do I integrate the two project files? Just by copying sequences?
Thanks

AK-77 wrote:
Also, when the two projects come back together, how do I integrate the two project files? Just by copying sequences?
There's no easy way to do this. Yes, you could simultaneously open both projects (make sure they have different names) and copy material including entire sequences from one to another. But this could get confusing very fast!
Also, if the project uses render files, I wouldn't try to combine the render folders (they'd possibly contain files of the same name). I'd re-render everything.

Similar Messages

In iMovie when I try to share a project to a file on an external hard drive it will work the first time but subsequently it says it is sharing but gives no time and file name and in fact just sits there not sharing the file.

I have iMovie 10.0.4. I want to transfer some old DV tape videos to MPEG 4 files to be stored on a 4 TB external drive. I successfully imported the video to iMovie, created a project by moving all captured files into a project and the first time I shared the project to a file it worked as expected. Every subsequent try to transfer another video would fail to transfer. When I clicked save it gives the warning that it is too big for iCloud, iso I click create on this computer. The progress circle comes up with no indication of progress. The show activity drop down just says sharing to "file" no file name as in the first one and indicates no time remaining. In fact it just sits there apparently doing nothing. I'v tried it a half dozen times, deleted everything and started over. It transfers the first project to file and then nothing on additional tries. What do I have wrong, am I missing something?

In iTunes 11 uncheck the preferences setting in in the iTunes Preferences panel "Advanced > Copy Files to iTunes Media folder when adding to Library"

MS Project Very Slow and Project Files Large when Using Shared Resource Pool

Hello,
We are using MS Project 2010 Professional in our organization and using a shared resource pool so we can easily identify resource conflicts. When we started this process many months ago the resource pool worked great. Now that we have nearly
all of our projects (~40) using the resource pool, it has become essentially unusable. Each project file that is sharing the resource pool is 12 MB or greater in file size, and most of the project files contain less than 100 lines. Saving any file
takes ~4 minutes. As a result, many of the resource managers and project managers are starting to avoid using MS Project which is undermining our original intent.
Any thoughts on what we could try to regain the usability, make the file sizes smaller, improve save times, etc.? Will MS Project Server fix all of these issues?
Thanks,
Josh

If any of your PMs renamed, moved or over-wrote their project file whilst linked to the Resource Pool or a master, then the file may well have corrupted itself or the pool or both. With 40 files, you can guarantee one or more PMs will do one of the above,
so file corruption is a when, not if (2days or 2 years or more).
For 40 projects Project Server or any solution that copies data to a database so the resource data can be consolidated is needed. Project Server is not a simple application, it's a full server and requires proper training and processes to add value. And
it needs configuring by someone who knows what they're doing!
In the mean time try unattaching all project files from the pool, then create a new blank pool and re-attach.You will also need to File, Save as to repair each project file if needed. For bad corruption save as to a .xml format then re-import to a blank
project.
Or, create a new master each time by inserting all projects into a new blank project, but deselecting the Link option. All tasks are then copied and the resource data consolidated. Record a macro to make creating this very quick and easy (provided your network
isn't too slow).
Rod Gill <a href="http://www.project-systems.co.nz/project-vba-book/index.html/">The one and only Project VBA Book</a> <a href="http://www.project-systems.co.nz/"> Rod
Gill Project Management</a>

File permission issues when sharing project

Hi,
We are sharing a project amongst two developers that each have an account on a (Windows 7) machine. They are part of a windows group and don't develop at the same time. All directories and files are in the group and are set to inherit permissions. After one user develops using Labview, all the files that he saved when using Labview have the group permission removed and the second developer can no longer open the files. Our sys admins claim Labview is somehow changing the permissions. Has anyone seen/overcome this?
Thanks,
Steve

Where is the file being saved?
No place special. We have a labview project/ directory under our own directory under C:/ that roots all the Labview project files.
If both users have full access to the directory where the files are being saved, there shouldn't be any problems. I'm sure LabVIEW isn't doing anything to change access rights.
Both users have full access. If I create a new file it has the correct permissions (a local group).
I'm concerned about the comment "part of a windows group"? Most PC's in a corporate environment are part of an actual network domain, and don't use that poorman's excuse for network access rights of a workgroup that Windows seems to want to use for standalone PC's and those not registered onto a network.
I wouldn't be too concerned =) We have a nationwide federated domain. The "group" is a local group on the computer for two people specifically to share this labview project.
Steve

Resource role information from shared resource pool file to a master project file

Hi,
I am using Microsoft Project Professional 2013. We have multiple project managers running their own projects. We are building out a PMO and are bringing all these plans into one master 'portfolio' plan. So
we have one master plan file, subproject 1, subproject 2... and then we have setup a shared resource file where all resources are utilising the same shared pool.
This works well and in the master file we can do resource usage checks. We have also added extra columns such as resource group which gets shown in the master file and we can filter which group (in our
case infrastructure, projects, applications etc) are consuming most resources.
The bit I am stuck on is management also wanted to report on the resource role ie which person is a project manager, business analyst etc. I have created a custom field in the shared resource plan as 'resource role' and populated as per their job role but for
some reason the info added in the shared resource file doesn't get conveyed to the master file as say the resource group does.
Any ideas ?
Thanks in advance

Thanks Dales for helping out. Thats how I originally did it. Went into organizer. At first I had copied the 'Resource Role' custom field to the global template and then in the master file added the same column but nothing showing. Then tried same again
but this time copying directly to the master file but still no joy.
I am seeing 'Resource group' appear as it should. I make a change to a someones resource group in the share pool file and I see the change in the master file but not happening with the custom field resource role.
Terry

Sharing media between two project files

If I have all the media in one project file, and the current sequence in another, shouldn't any changes I make to the media be reflected in both projects? Jpeg files in the media project were re-named and replaced with uprezed versions. The files in the sequence project did not change to match this - they still have their original file names, and were linked to the old files. They are still connected, as I made a copy of the media before I renamed the files. So now each project is referencing different media. Is there a way to resolve this? The only thing I can think of is to go through the timeline and replace the files one by one.
Any advice would be much appreciated! Thanks in advance.
(I know, I know . . . files shouldn't be renamed! I made a mistake last week - I'm already wearing the cone of shame.)
Message was edited by: film_fish

Oops ...
The resolution is to "reconnect" the timeline instances with the new masterclip source media
Select all the offline media in the timeline, then choose File menu > Reconnect Media...
And in the Reconnect dialog press the "Locate" button, then navigate to and select the new file ... if you had/have kept the file names the same then leave "Matched Name and Reel Only" checked and let the app identify and reconnect all those offline files in the same relative path ... but if you have different names for the new source files uncheck the "Matched Name and Reel Only" option and sit yourself down for a long session of manually finding and attaching media
Best
Andy

Adobe project file is hogging shared storage bandwidth even when paused

I have a particular Premiere Pro project, that when opened, completely hogs my Terrablock storage bandwidth. I have inserted a screenshot of the storage servers disk activity even when that project file is paused. I have no other project files open or file transfers going. When I close this project, all disk activity goes to zero. This happens with no other projects and I can open it from other Mac towers with the same result.
Here is an image of the disk activity with that project open and paused.

Hi Mark,
Since my original post, I have noticed at least one other project hogging the storage bandwidth. Both projects are accessing completely different files and have a varying number of sequences.
The first project has about 45 sequences with none of them over about 90 minutes in length. The sequences are referencing .mp4s and are multicammed with two shots and occasionally contain another camera laid on top of the footage. The graphics were exported as Quicktime files and are only included in some of the sequences. This project also contains some title cards along with some png and psd files. The original stringout sequences of the footage were imported into the project using Media Browser.
The second project has 13 sequences and is referencing Quicktime Proxy footage including multicams containing two different shots. Most of the sequences contain only about 10 minutes of footage at the most. There are numerous title cards throughout this project and some of the shots are scaled in a bit. This is a duplicate of the original project (which is not hogging bandwidth) and somehow started causing bandwidth problems during the edit. No sequences were imported either.
I have also noticed that both of these projects somehow make Premiere Pro 2014 unable to close. A force quit is required for both to exit out of the program or open another project.

Why are my photos not as sharp when I import them into Facebook from the Aperture Projects file, compared to when I 'share' them with Facebook within the Aperture programme? There is a noticeable difference and has been spoiling my photos for some time.

Hi all, I take wildlife photos (mostly birds) as a hobby, and have become frustrated with the quality of my photos recently when shared online, particularly Facebook.
I started blaming my camera ( a Canon 7D) as I changed it a few months ago from a Canon 550D, and I soon noticed that the images were not as good. Then I realised it was when I started using Aperture.
I started by using the 'share' option within Aperture but I soon realised that then I have no control over the creation of an album, and the photos start appearing on facebook before I have finished uploading them and given them captions. Plus if I subsequently move them or export them to my back up drive then they disappear from Facebook!
So I started creating albums within Facebook and then importing the photos from the aperture projects file on my computer. Because they are imported I can then delete or move the aperture file and the photos stay on facebook. Otherwise my macbook was becoming completely full.
However to test my theory I have today uploaded the same photo edited in Aperture stored in the same projects folder using the two different methods described above, and there is a very distinct difference between the quality of the two images. The shared ones are very much sharper than the imported ones.
I am a computer novice and don't know how to check what the quality settings are, or how to adjust anything to improve the way the photos go into facebook. I do have a manual but I just cant understand it :-(
I have tried a free sample of Lightroom 5 and my photos look amazing, there is such a difference, but I don't want to give up with Aperture unless the problem really can't be solved.
Sorry for such a long first post, I would be very very grateful for any help you can give me!
Regards
Susan

Generally I would not use Facebook for sharing any photos, it compresses the photos substantially, and when you have shadows and dark colours you get visible "bands" where there should be subtle gradients, ie at sunsets and sunrises.
It sounds like you are using two methods to upload to Facebook:
1. Sharing from within Aperture, which basically syncs Facebook with your Aperture album, so any changes made at either end gets synced, hence the deletions from Albums, although the original file should still be in your library, just removed rom the album. It is like a playlist in iTunes.
2. Exporting pics and uploading to Facebook from the browser.
I am not sure how method 1 gets compressed, but I know that uploading hi-res jpegs to Facebook using method 2 results in poor quality images.
I wouldn't even bother comparing option 1 or 2, and they will both be poor images once you view them on Facebook, as opposed to viewing uploaded images on proper image sharing / hosting sites.
Your problem is not with Aperture, it is using Facebook for showing your work.
If you export pics form Aperture at high res jpegs or TIFFs your images will be fine.
If you insist to use Facebook as your way to share your work, then your workflow should be this:
1. Right click images you want to share.
2. Select Export version.
3. Export as 100% size and ensure the export settings are set at 100% quality.
4. Upload this pic into Facebook.
This will get you the best image size and resolution on Facebook.
See how you go.

Shared Project Workflow Problem: Hitting a Wall with Markers

Hi there,
Apologies in advance for the long note. We're using Adobe CC to edit and finish commercials and are having a significant issue regarding shared project workflow. First, some context:
We often edit projects remotely. When this happens, assistants and other editors who remain in LA will have access to the media on our SAN while the editor and assistant traveling out of town will have their own copy of the media. I know Adobe Anywhere would solve any issue relating to two identical sets of media in use in different cities, but we're a small shop and the hardware and software expense don't make sense for us at this time. Please do not respond to anything mentioned from here on by stating we should just get Adobe Anywhere. Thanks.
What will regularly happen is that the remote editor and assistant will need work done on the project here in LA while they're in session with the clients. Sometimes this work involves marking up clips with comment markers so the editor can more easily locate a specific moment. Here's where the problem arises.
Unlike FCP and Avid, Premiere handles markers within the clip's metadata. So, if I have two separate projects linking to separate but identical instances of media, one of those media instances gets updated with new markers, there is currently no way to get those markers to the other project without also shuttling the new marked-up media. This is not possible when a remote editor needs dailies marked up in a couple hours and is working across the country or abroad.
But let's assume for the sake of argument that it is possible and we apply this workflow. Let's also assume that in the time it takes the local assistant to mark up the clips for the remote editor, the editor has added a couple markers of his own, which is reasonable and happens all the time. Now when the editor links to the newly marked up clips he's received via shipment, he'll wipe out all the markers he's made on his own since giving the order to mark up the footage. That is a significant inconvenience, especially with clients in the room asking stuff like "can we look at the take where the guy says 'good' instead of 'great'?"
So what happens if we just have repeating sets of media, so that every time the clips markers get updated, the editor actually imports those clips, even though the picture and audio data in those clips is completely redundant to what's already in the project. The issues with this are, as I can see it, 1) increasing the amount complexity within the project so that you'd have to scan many bins of dailies to look for a single marker, 2) increasing by orders of magnitude the amount of storage space needed, 3) even if problems 1 and 2 are handled, if you have to go to finish with multiple versions of a cut, and those versions reference separate instances of the same clip from different bins, Premiere's dupe frame detection will not work and you'll need to spend a lot of extra time locating duplicate clips manually before sending your EDL or XML off to final color grading.
At this point, I think it's necessary to interject something: we're talking about markers here. Why is this such a problem? FCP and Avid have no such issues simply by making markers - even clip markers - part of the project metadata. From what I understand, Adobe has chosen to do things differently because of dynamic link, so that After Effects and Prelude, for example, could add markers to a clip and those markers would ripple across all instances of that clip in the different applications. It's a great feature which we take advantage of here from time to time.
So what's the solution?
My workaround in CS6, which does not solve the issue of needing to merge clip markers so that an editor's markers and an assistant's markers can be applied to a single piece of media, was to turn off "write XMP ID to Files on Import." This would generate an XMP sidecar file which could be easily passed along with a project file to the remote editor, who could then overwrite his local XMP sidecars with the new ones containing the new marker info.
However, in Premiere CC that is no longer possible. It appears that if Premiere CC can access the XMP ID on a file, it will not generate a sidecar regardless of what you have set in your media preferences. We use ProRes Proxy as our dailies format (again, please no comments on this, it is not up for debate at this time) and Premiere can get to the XMP ID within the files and will not, no matter what it seems, generate an XMP sidecar.
We could change the company workflow to use DNxHD 36 instead of ProRes Proxy, which would give us XMP sidecars, but that would not solve the issue of needing to merge marker lists between projects non-destructively.
The best solution I can think of would be to have a script or some kind or built-in feature which would allow for the batch export, import and merging of marker lists. This way Adobe could keep its current clip-metadata-based marker workflow while giving professional users needing more flexible marker behavior the ability to have assistants non-destructively modify clip markers without necessitating the creation of extra media or project complexity.
I would really love some input on this and ideas from the pro community out there who has experience with shared project workflows - especially projects being shared remotely. There's not a lot of info out there about this and it would be great to hear what others are doing.
Thanks a million for sticking with this, if you've made it this far.
Best,
Jon

Thanks Jim,
I understand that Adobe Anywhere solves this, but there should be this fairly basic functionality (which exists in Avid and FCP) in a non-enterprise edition of the software. I have submitted a couple different feature requests about this, going back to CS5, so hopefully enough people make similar requests for a fix to be implemented. Adobe Anywhere is really not a solution for our small shop as currently configured/priced, especially when we can have editors working remotely with very affordable USB 3 drives. The only hangup is the markers, which just isn't worth a 5 figure fix. As such it's hard to consider the problem solved for either us or any small shop or post crew.
Best,
Jon

Each edit is taking 5-10 seconds to process in some of my project file's nested sequences. What can I do?

I edit a weekly news show. For this show, I have created a Project File that I re-use as a template every week. It's a highly nested template, with a sequence for every used material (the anchorman’s footage, the news set, the media playing over the anchorman’s shoulder, the lower thirds, etc). It has three different camera angles in a multicam sequence, each sequence sharing the same nested sequences but just resized to look like a different camera angle. To make this easier to understand, here's an episode (explicit):
SKATELINE - Cory Kennedy, David Gonzalez, Jimmy Carlin In Enjoi Oververt and more.. - YouTube
In the past, the template has worked perfectly. However, everytime Adobe has a major update and I update the project file, for some reason, some of the sequences perform very sluggishly. With Adobe's recent update, the sequences for the anchorman’s footage and the media playing behind him are very slow to make edits in. Every action I do takes 10 seconds to process, even moving an image. However, if I work in the master sequence (With everything put together) everything runs perfectly smooth when I make edits.
In an attempt to fix this problem, I decided to recreate the project file from scratch, with the new update, but even then, my "anchorman footage" and "media behind him" sequences are very slow. What's even more bizarre is if I select a piece of footage in the anchorman sequence, my entire program sometimes crashes. I have tried rendering the sequences to help performance, but that hasn't worked. I have tried installing CUDA Drivers to use the CUDA version of the Mercury Playback Engine on my Macbook Pro Retina, but it also still isn’t working.
So why do you think that my sequences are operating so slowly? What could be causing it? Could it be that each sequence is used several times in the multicam sequence? If so, why has it worked smoothly until now? What can I do?

Yes same issue for me also, working in mutli cam nestings
Very Very Sluggish Performance, semi hangs in PP, if you actually wait long enough, or leave it hung whilst you do a post on here, for a few minutes then it may come back to response.
The issue is defo to do with nesting, I have tried turning off audio wave forms, which helps in the multicam nest edit but as soon as you put that sequence into a third nest then the sluggishness is major.
Basically, this looks to be the same issues that have been reported before with the new update.

Premiere Pro CC crashes in opening a project file

I am using Premiere Pro CC since 1.5 years now. No big problems so far but now suddenly a strange one in opening a project file.
Several other project files open up as usual, but the last one I've been working on, suddenly crashes in the middle of loading the media files. An error message like this appears:
"Premiere Pro has encountered an error. [c:\ppro772\releases\2013.10\shared\adobe\mediacore\mediafoundation\api\inc\ " (and the rest of the path I'm not able to see, it's cut.)
I have installed the latest version of the graphics driver today. I have installed Premiere Pro 2014 some time ago but didn't really use it yet. I already tried to open the project in 2014 with no success.
Now I just found out that I can open the project from the one-before-the-last autosave file! Thereafter I saved the project with a different name, but trying to re-open it resulted again in the same error!!
Any idea what the problem could be and what might help?

BUt that's a different error.
I am getting this one aswell.
[c:\ppro772\releases\2013.10\shared\adobe\mediacore\mediafoundation\api\inc
Please fix it.
I really want my Premiere Pro to work :\

Where are the project files located on the hard drive

does anyone know where on my hard drive I can find the imovie project files. In the itunes under imovie it shows two projects but they are not on my ipad in the app. how do i delete them if they don't show up when using the imovie app.
Thanks
Roger

If you see a project in itunes (in the apps tab, and then File Sharing),
you can import it into iMovie iOS from the main screen.
Open iMovie on your device and go to the projects screen, if it isn’t already showing, by tapping My Projects in the upper-left corner above the viewer.
On the screen, tap the Import button , and tap the name of the project you want to import.When the import is complete, the project opens and can be edited like any other project.
Have a read of this helpful manual that explains the in and outs of iMovie iOS:
http://help.apple.com/imovie/ipad/1.2/index.html#
This explains in more detail about getting projects in and out of iMovie iOS.

Can't create shared project in MII

The MII architect is trying to create a shared project in the Workbench and is receiving an error. It looks to me they have something already checked out and thus cannot create the project. Could this be something wrong in the NWDI/MII configuration. Any suggestions on what I can do to find the cause?
Here is the error:
Error while creating the Project hierarchysahad
[EXCEPTION]
com.sap.xmii.contentmanagement.exception.ContentManagementException: Cannot create resource sap.com.miitest1; parent resource is checked out for create in a separate activity
Thanks!

Hi,
The CE/MII system is running NW 7.11 SPS7
The NWDI system 7.0 EHP1 SP3
We are creating a shared project in the MII Workbench within the "File" menu "Created Shared Project".
I'm the Technical BASIS lead here and the MII team is saying this error is a system error. I don't know enough about MII and the development environment to argue this point.
Regards...

Project Files & Saving

There is often confusion between Saving a Project and Exporting/Sharing a Video from that Project.
Let’s look at what a Project file is. In PrE, this is a .PREL file. In PrPro, it’s a .PRPROJ file. These are just XML database files, that define the Project, show where the media used in that Project was located the last time that you had the NLE (Non Linear Editor) program and that Project, open. Then, there are instructions as to what one has done to those media Assets. There is no media, of any sort included in it.
If you open it up in WordPad, or an XML editor, it looks something like this:
<?xml version="1.0" encoding="UTF-8"?>
<PremiereData Version="3">
<Project ObjectRef="1"/>
<Project ObjectID="1" ClassID="62ad66dd-0dcd-42da-a660-6d8fbde94876" Version="20">
<IsProjectVideoTemplate>false</IsProjectVideoTemplate>
<VideoPreviewCompileSettings ObjectRef="108"/>
<NextID>1000000</NextID>
<NextSequenceID>2</NextSequenceID>
<CustomCompileSettings ObjectRef="103"/>
<StillCompileSettings ObjectRef="93"/>
<MovieCompileSettings ObjectRef="88"/>
<ProjectSettings ObjectRef="77"/>
<RootProjectItem ObjectRef="2"/>
<AudioCompileSettings ObjectRef="98"/>
<Node Version="1">
<Properties Version="1">
<MZ.NextSequenceIndex>2</MZ.NextSequenceIndex>
<Media.View.Normal>1</Media.View.Normal>
<ColumnListContents.Version>3</ColumnListContents.Version>
<Project.Sort.Direction>0</Project.Sort.Direction>
<Project.Sort.ColumnIndex>0</Project.Sort.ColumnIndex>
<Project.Sort.Type>0</Project.Sort.Type>
<Project.ListView.Thumbnail.Size>1</Project.ListView.Thumbnail.Size>
<Project.ListView.Thumbnail.State>true</Project.ListView.Thumbnail.State>
<Project.ContentView.LastViewed>1</Project.ContentView.LastViewed>
<Columns.List Version="3">
<Columns Version="1">
Note: in the actual Project file, there will be much indentation, that does not show up above.
There is much, much more, but this should give you an idea. You cannot "play" this file with any media player. Remember, there is zero media in it, only links to that media. Also, there are only two programs that can do anything but allow one to edit the various text lines in a Project file. PrPro can open both types, .PREL’s and.PRPROJ’s, with a few exceptions. PrE can ONLY open .PREL files and will give you an error that "this Project was created in PrPro. Use that program to open this Project." There are no exceptions to this, though who knows if PrE 8 will be able to open .PRPROJ files?
Now that we know there is no media in these files, what good are they? Well, they contain links to the location of the media and also instructions on what one has done to that media. They are the instructions for PrE and PrPro, with descriptions of all edits. They are the working tools of both of these NLE programs. They also must be set up, before one can do anything else in these programs.
As one works with the Project, they will want to Save their Project files, or any edits will be lost. There are basically three ways to this, plus one additional variation.
First, there is Save. It records all operations and instructions to the previously created Project file, overwriting the previous version. I do this often and usually use Ctrl+s for this purpose.
Next, we have Save_As. This does a Save, but with two variations: it allows one to set a new name, or location for this Project file. I use this and increment the Project file’s name, as I go. This does NOT overwrite the existing Project file, but writes another one, with the name, or location that the user assigns. The second part of this, and quite important, is that not only does it Save with the new name/location, but it keeps this new Project open in the NLE. You are now working on the new version, and not the original. To me, this is especially useful, if I want to leave the original version untouched, in case I need to go back to it at some date. After a day of editing, or after some big changes, I’ll make sure to do this, so I have the original, plus this newly edited version. By incrementing by 1, I know that if I am working with [Project Name]_05, it came after [Project Name]_04, so it is newer.
Then, we have Save_As_a_Copy. How does this differ from Save_As? The biggest difference is that it does not overwrite the original, allows one to change, or increment, the file name/location, but it does NOT stay open in the program. You are still working with the original version, and this Save_As_a_Copy version is tucked away, in case you need it at some time. I use this, when I just want a record and a backup of that moment for possible later use. It’s more of a "snapshot" of how things were at that moment.
Last is the "variation" that I mentioned. This is AutoSave. Depending on one’s Preferences, these will be stored in the AutoSave folder in the Project’s hierarchy. By default, one will have five of these and they will reflect that they are AutoSave files. Note: one must do a first Save in an editing session to start AutoSave, which will make an AutoSave copy at the time interval set in Preferences. Also, Premiere is pretty smart. It will NOT just AutoSave every 5 mins (or whatever time interval is set in Preferences), unless some work has been done. This is a good thing, as AutoSave will overwrite the previous files in that folder. If you go to lunch, if it did not keep track of edits being done, one would end up with 5 exactly identical copies of the same file in AutoSave. This would not be that useful.*
Now, because it does overwrite your previous AutoSave files, you need to pay close attention, should you ever need to use an AutoSave Project file. By default, there will be five files, _001, _002, _003, _004 and _005. However, because of that overwriting (basically FIFO), you need to change the View in Windows Explorer to Details, and sort by Date/Time, to make sure that you are getting the latest version. Remember, _003 could well be newer than _005. Watch out for this, and do the Sort on Date/Time to be sure.
Hope that this helps one distinguish between Project files and Video FROM that Project, plus give some tips on Save, Save_As, Save_As_a_Copy and also AutoSave.
Hunt
* It has come to my attention that as of PrPro CS3, things have changed with Auto-Save. One does not need to do an initial Save to start Auto-Save, but if left Open, though no editing is being done, the Auto-Save will keep on overwriting the files at the set interval, say every 5 mins.. What this means is that if you leave a Project Open for 25 mins., have the number of Auto-Saves at the default of 5 and the default of every 5 mins., you will have 5 copies of the same Project file. I do not know what Adobe was thinking here, as Auto-Save should not be active, if no editing is being done. I often have a Project Open, but am working in PS, AI, or Encore, so there is no editing being done in PrPro, but there soon will be. I do not want all previous Auto-Saves being overwritten with the same exact file. With PrPro CS3 or higher, I strongly recommend that one does a lot more Save_As and Save_As_a_Copy, than in previous editions, or they might be in for a rude surprise, if they went to lunch, or just left the Project Open for a half-hour.

There is a special use for the Save, Save_As and Save_As_a_Copy, that might not be readily apparent. As we have discussed how the three differ, I will only cover this use, and the user can then choose which works for them.
Often, an editor will work on a large Project, but need to break out segments of that Project into separate "mini Projects." The easiest way to do this is to make sure that a Save has been done for the full, large Project. Then, just Delete anything not needed in the new mini Project. This could be Clips on the Timeline, Assets in the Project Panel, or Sequences (in PrPro only). When done, just choose Save_As, or Save_As_a_Copy. If more "versions" of that large Project are needed, Open the original, repeat the Deletions, and then do the appropriate Save_As, with another name, or into another location.
Remember, all forms of Save are for the entire Project, and not just elements of it, unless you remove all unnecessary elements.
Hunt

Open project file in signalExpress

Hi, all,
When I tried to open an existing SignalExpress project file copied from another laptop on my laptop, I got the following error message:
Installed component versions are not compatible with the version of the LabVIEW SignalExpress. Please install the latest versions of the following:
1) LabVIEW SignalExpress Shared Tools
I could not find this Shared Tools from the NI website. Any suggestions?
The verison of my signalExpress is 3.0.0.
Thanks a lot.
Cong.
Solved!
Go to Solution.

Hi Cong,
Depending on which version of Signal Express the program was written in, you may need to upgrade your version. Here is a link to all of the signal express downloads available on our website.
Cheers!
TJ G

Sharing project files

Similar Messages

Maybe you are looking for