MultiCam - Didn't save Only XML file (X10)

[alex350]

Hello there, I hope someone may be able to help me with the Multi-Camera function.

I'm currently using X10, but I did have similar issues with X9 (but now it seems to be more frequent)
When I save a Multi-cam project, every so often I will Save as, close the project & when I go to re-load up the Multi-Camera project, it doesn't appear. (I instantly think "oh no, all that time spent is lost, I must have forgotten to save it)
when I then look in windows explorer into the MultiCam folder I can see an XML file (named exactly the same as what I named the project file)

I suppose my question is, is there a way to get X10 to read the XML file (as it somehow has saved my data)?
Also is there any reason why it may have saved as an XML rather than the VSP (like it usually does)?

thank you kindly for any help and guidance,
Alex

[lata]

Hi Alex

I have just run a quick test using Multi Cam Editor, for me it appears to be saving two projects, one automatically named MultiCam_01 etc. and one as I use Save As, I would not expect the first file if I use Save As. Hmmmm confusing????
However all vsp’s are saved to the default folder here.

C:\Users\UserName\Documents\Corel VideoStudio Pro\X10.0\MultiCam

Ok after you have imported your files to Multi Cam do not “save as”, closing the MCE will save the VSP as MultiCam01 etc., at least you will only get the one file reducing any confusions.


Ok this is what I do

1 / create a new library page and insert my video to be used in MCE
2 / set the project properties to match my video files….(Camera one file.)
3 / Shift click the first and last clip in library to select all camera files, right click selection for Multi Camera Editor, this opens the MCE Source Manager, clips already selected, click OK, opens MCEditor
4 / Audio Sync then select my camera angles.
5 / Click ok will save the VSP as MultiCam.vsp, returns to the edit timelines, VSP is placed in library.
6 / If I need to edit further in MCE I double click the VSP to open MCE.
7 / Drag VSP to timelines to continue editing, Please note you are now editing a new project, File Save As to give the project a meaningful name.

Oh
Your Project Properties should be set correctly as in 2 above, the frame rate should match the first MCE video files frame rate, same as MCE timeline.

[alex350]

Thank you for your speedy response,
to explain further, I get to step 5 (click ok) & this is where I get my issue. Its not loading into the timeline/library (it sometimes does....and sometimes doesn't)
but on on each occasion I 100% get an XML file in the MultiCam folder but sometimes get the VSP file you mentioned above.

I would say my multi-cam works properly roughly 1 in every 3 attempts (I was just curious if anyone knows why, or if its possible to use the XML files...i'm assuming my data is saved, just not in the VSP file)

*to add a bit more
I'm just starting again on the multi-cam & on the 3rd attempt it saved/imported to the timeline.
oddly i've done nothing differently on each attempt (basically followed your above steps - twice nothing (but I get an XML file and the final time i get to the timeline (and both XML & vsp files)))

[lata]

Hi Alex
VSP = Video Studio Project

I have managed to replicate the problem by using VSP files in the MCE and not video files.

Using VSP files is causing the problem for me.
The thumbnails in the library or Source Manager has the name at the bottom.
Do not add VSP’s to your MCE

If I add all VSPs then no project file is saved, only XML
If I add a mix of VSP and Video then the new VSP is saved to the folder but does not show in library
Only when I use video files only does the MCE perform ok. And show in the library.

So are you by mistake using VSP’s in the MCE?

I have to say the I think the program should not allow the use of VSP, with a warning to use video files only?

[alex350]

hmmmm, interesting discovery, but i'm afraid I am using 4 channels of video files (to be precise though, 9 different videos across 4 channels, 6 files being gopro video files)
- wow i made that sound complicated.

the thing that's odd though, it works....when it wants to. Its not like it "doesn't ever work" as I have successfully used & saved a Multi-Cam "Corel VideoStudio Pro Document (.vsp)"

[lata]

Hi

and you are sure you are not adding VSP files to the MCE as camera angles?

[alex350]

100%,
I have literally imported the video files into the library, then click "multi camera" & go from there.

I can't stress enough, it works...usually, just once in a blue moon it won't.

my new strategy is to load the clips in first, attempt to save the project (before doing anything), ensure i see a VSP file & then edit it from there (& then save from that point onwards)

It would be great if someone knows a way to use that XML file that's created (mine is 3mb, which implies it definitely holds some useful data)

[lata]

Hi

As I said the only way I could replicate the problem was to use a VSP in the MCE.

When the vsp did not show in the library but I was able to see in the folder.
Double clicking that opened the file in the timeline where I could see the clip type, and yes I had a vsp in the timeline.

I don’t know about xml files, I assume they are files used by the process, saving the edits etc. they should be hidden from the user, I think, a bit like a cashed file working in the background.

[Ken Berry]

Alex -- can we assume you realise that vsp files are NOT video files. They are merely small text files which tell Video Studio what video is included in a project, where it is stored and what editing has been done to it. Over the years Corel has built in the ability to use vsp files in some editing functions. But as Trevor has pointed out above, they have apparently not worked out all the complications when it comes to another new feature in VS like MCE.

[lata]

Hi Ken

I am sure it worked better with CVSX9 up to the SP9.5 and only saved the one VSP, so when we did Save As it replaced the default MultiCam vsp.
Creating two projects for the same MCE session only causes confusion.

Not sure when adding VSP’s was first allowed, probably all the time, certainly I never tried using a VSP before.

I think I will pop a note on Bugzilla….

[alex350]

I can't stress enough, I am importing video files
(I'm almost offended that it might have been assumed I didn't know the difference - but its best to check)

I was hoping there was a way to use the XML file, the program/feature does work....just not every time

[lata]

Hi Alex
Our questions were not meant to offend but sometimes the simplest things get missed.

We did not ask what type of video files you are using?
From the library right click your video clips and choose properties, what are they?
If you wish you can create an image of that panel to attach to your post.
and if I have similar types I can try again.
I have used MTS, DV.Avi and MP4 types and cannot replicate the problem, only by using VSP files do I create the effect you have described.

Certainly saving two MCE.VSP for the same session is wrong, I am certain that did not occur with the original X9 version?

XML files, not really sure what they are for other than retaining the MCE edits/ camera angles.
You can open the XML files in notepad to view the edits showing the timecode cuts. Maybe you can make sense of those?

[asik1]

Unfortunately while XML file is text and can be very handy in many times, VSP is not a text file and any peeping can cause problems.
It will be most handy to have a VS utility that will "translate" to and from the two.

[dikkevette]

Hi there,

It does not matter if you use "save"or "save as" to create a VSP file. These saving functions only change the name of the mce session.

The action that creates the VSP is by clicking OK on the bottom of the screen. My mistake was to "save" project and then click the X top right...

Hope this helps!

[dikkevette]

The saving functions in MCE will only change the name of the MCE session. The actual VSP saving is done by clicking OK on the bottom of the screen. I made the mistake to "save"and "save as" and then click X top right and had the same issues.