Moving to a new machine from X8 to X9

[OBB]

Ok, so once again I've come to the end of the line with my main machine, I seem to have a knack for burning up machines in under 5 years...

I want to make sure I'm bringing my libraies & backed up projects into the new one. I know the one location (the roaming APP 18.0 data file that I will backup & move over but beyond that are there any other locations that VS might hide other user settings and/or other miscellaneous data that I should also check for other user files?

90% of my finished projects & most of my 'still in progress' projects I do save the main file as well as back up with smart package but my question is once I move them over to the new machine, will the smart packagae still contain ALL of the media files that I used per project & open fully intact? ...or will I be endlessly re-linking media files afterwards... The only reason I ask this, is when I went to from my other retired machine I copied & moved those smart package saves from my VS6 machine to this soon to be retired VS8 machine & while I thought the files should have all been there many seemed to be missing or no longer linked anymore and spent days manually hunting down & re-linking mountains of files... I'm hoping I won't have to do this again when I move from this VS8 machine to the new VS9 machine...

And since I use smart proxy, is there anything I would need to move from those locations as well...

I hope someone can give me some insight so I can do it this time without having to go thru the mess I went thru when I did this 4 years ago....

[Scubbie]

Smart Package copies all the files used in a project into the one folder. That folder can then be copied to any drive.

When you open the associated .vsp file (in the new folder), it should automatically find all the associated files in that same drive & folder. At this point if you start making changes and save those over the original .vsp file, then they must always be where you were editing them.

I hope that all makes sense.

[asik1]

I think that Smart Package doesn't includes fonts and raw filters files so not 100% fool proof.

[Scubbie]

Good point with the fonts, and yes you are correct.

The only way around that is to ensure that you have all the fonts available on both computers.

[OBB]

I hope that all makes sense.

Yes, makes total sense... And always since moving to vs8 I've had zero issues transferring vs8 projects from the main to the mobile machine (or vice versa)... The only time I had the issue was when I backed up vs6 projects and then reopened in them vs8... All of the files would show up in the projects smart package folder, not a single file in them was linked upon opening one and it was a PITA re-linkiing them...

And I still go back to revisit some smaller vs6 projects from time to time & I still run into this... so not sure why it happens with the vs6 smart packaged ones only...


And yes I know about fonts...have been using the same ones for years as well as my custom made ones as well...

Hmmm... about the raw filters... would that cause media to become un-linked in a bundled project?

[Scubbie]

I'm not sure about the raw filters. I guess it depends on which ones you are using. Perhaps asik1 can help?

What I would suggest though is to set up the new machine first. Transfer as much as you can across, test and test again. Then once you're happy you can look at decommissioning the old PC.

As a tip, if I'm not too late, it might be worth organising the new PC so that specific content is kept on different drives. Keep as much of the video, photos, etc., for your projects on any drive other than C drive. Then organise any computer in the future in a similar manner, keeping the drive letters the same. (i.e. pictures on D, music on E, Videos on F, G, H...). I've assigned fixed drive letters to my external drives as it makes it safer for some projects on my laptop. It helps.

[asik1]

I meant actual FX's vft files.

Regarding re-linking I wonder if you ever had to relink such project with more than 200 files over ~500clips

looks easy? well not if the files original names are in different language that your system can't decipher,
but after several hours I got them all.

[lata]

Hi

I would think the X6 issue may be associated with the 32bit version, just a thought?
X7 was the first to use 64Bit.

Some ideas…
1 / When you create the Smart Package, tick the option to include all trackers, maybe the description is a little deceiving, but worth ticking.

2 / When you re- install Video Studio make sure you install to the same version as the old version.
For-instance if you are running 2018 SP3 and install 2018 SP2 you may have problems opening the projects.

3 / Smart Proxy is not gonna work so you would have to create those files again, there is no option to re-link to Smart proxy files.

4 / Mercalli stabilisation filters may require rescanning.

5 / part of video editing is a matter of good house-keeping, creating a separate folder for each project, importing video from camera to those folders, basically you are manually creating a smart package.
But as your workflow seems to include working with Smart packages you should not have any problems,
Well not any serious issues

6 / nesting…… is a process where we add a vsp to the timelines, recently discussed on the forums.
Adding VSP to timelines can be done by mistake.
The point being we cannot create a Smart proxy if the project has nested VSP files inserted to the timelines.
You have not mentioned not being able to create the Smart Package, so no problems, just worth knowing.

[OBB]

Hi

I would think the X6 issue may be associated with the 32bit version, just a thought?
X7 was the first to use 64Bit.

Hmmm... The machine I was using VS6 in (and actually still use for other work) is an ASUS ROG G74SX which is 64bit. And a long time ago when I got hit by win10 free upgrade, it drove me bonkers as the ASUS & the existing V6 installation was unaffected when Corel ended use of 6 (unknowingly at the time) I found later after I went to install 6 into a newer Dell XPS (8300 I think) Studio desktop VS6 would not start or run after install (which was why I went up to VS8)... but it's funny as 6 is still running to this day in the ASUS machine & unaffected (though I no longer use that machine for video work, only mobile audio recording)

1 / When you create the Smart Package, tick the option to include all trackers, maybe the description is a little deceiving, but worth ticking.

Yep, this I know and has always been ticked... From 8 anyway...

2 / When you re- install Video Studio make sure you install to the same version as the old version.
For-instance if you are running 2018 SP3 and install 2018 SP2 you may have problems opening the projects.

When you refer to 2018 sp1, sp2 etc... are you refereeing to OS sp-x? ...Or to VS sp-x?
--- Will there be updates available for VS9 when I install? ...I was going to go to VS2018 but since I have 9U still sitting in a box new I didn't see a big need to drop another $100, So I'm only moving from X8 to X9...

3 / Smart Proxy is not gonna work so you would have to create those files again, there is no option to re-link to Smart proxy files.

Yes, this I know this... I will need to manually setup & direct my proxy folders...

4 / Mercalli stabilisation filters may require rescanning.

..Yep, I found that when I need to simply move from mobile to desktop (or vice versa)

5 / part of video editing is a matter of good house-keeping, creating a separate folder for each project, importing video from camera to those folders, basically you are manually creating a smart package.
But as your workflow seems to include working with Smart packages you should not have any problems,
Well not any serious issues

Project folders are always as neat as a pin Video/Audio/Media as well as scanned hand written notes... My partner calls me anal.

6 / nesting…… is a process where we add a vsp to the timelines, recently discussed on the forums.
Adding VSP to timelines can be done by mistake.
The point being we cannot create a Smart proxy if the project has nested VSP files inserted to the timelines.
You have not mentioned not being able to create the Smart Package, so no problems, just worth knowing.

Can you elaborate on nesting VSP's for me? I think I know what you are refereeing to but just want to make sure I'm on the same page here... ...I've never had an issue making or saving a smart package fpr a project, just want to be aware.

[lata]

Hi

Service Patches, SP2 etc I was referring to Video Studio
When you install X9 it should update by installing a service pack, I think that will be 19.5
There are two more updates SP4 and 5 that may or not auto install, they did not auto install for me, you can download from Corel, link on this post
viewtopic.php?f=1&t=58892
Personally I normally allow the program to auto update rather than doing it myself.

Nesting by mistake

If you save your project files VSP in the project folder along with the video files, it is easy to import those to the library.
Inadvertently importing a vsp, it looks like a video and can be added to the timelines.

also
There is a process called Time Remapping, using that will also add a vsp to the timelines.
Adding a VSP to the timeline is known as nesting and cannot be Smart Packaged
As you have not had an issue creating Smart Packages then you have never nested a VSP

[OBB]

All moved over & done! ... went as smooth a "cherubs bare wet ***" (Liz Phair... go, Google her & supernova)...

(will need to update my profile for machine specs when time allows me... So much going on right now, aint no time)

[lata]

Hi

Good to hear, thanks for the update.........