Modular apporach to creating a VSP
Moderator: Ken Berry
Modular apporach to creating a VSP
Hi,
First, I alway get excellent advise here on this great forum, so I say thanks again.
Now, the question:
I come from many years (probably more than 99.9 percent of the people on this forum), of Computer Industry. Having done it all in the business, I wanted your expert opinions on this.
When I programmed, one concept we tried to follow was modular programming. That is (for the uninitiated), develop code that does specific functions and don't mix functions together. I think they are called snipits now (in the PC world), and I am somewhat aware of the coding infrastructure used now (but I haven't coded in the PC world to much).
I have seen programs (modules), that have 20 lines of code to enter the program, 10 lines of code to exit the program and 1 lousy line of code to do the function! (IBM's MICR system (among others) for any of you dinosaurs)). Now that is modular!
Anyway (and I wont digress anymore), do you ever create small VSPs for specific footage and then insert them into the main VSP.
I did this for one file I am creating now and said hhhmmmmm this may be the way to go.
Anyway, thought I would get your thoughts on Modular VSP's.
Bob
First, I alway get excellent advise here on this great forum, so I say thanks again.
Now, the question:
I come from many years (probably more than 99.9 percent of the people on this forum), of Computer Industry. Having done it all in the business, I wanted your expert opinions on this.
When I programmed, one concept we tried to follow was modular programming. That is (for the uninitiated), develop code that does specific functions and don't mix functions together. I think they are called snipits now (in the PC world), and I am somewhat aware of the coding infrastructure used now (but I haven't coded in the PC world to much).
I have seen programs (modules), that have 20 lines of code to enter the program, 10 lines of code to exit the program and 1 lousy line of code to do the function! (IBM's MICR system (among others) for any of you dinosaurs)). Now that is modular!
Anyway (and I wont digress anymore), do you ever create small VSPs for specific footage and then insert them into the main VSP.
I did this for one file I am creating now and said hhhmmmmm this may be the way to go.
Anyway, thought I would get your thoughts on Modular VSP's.
Bob
-
sunshinegirl690
- Posts: 43
- Joined: Sat Apr 29, 2006 11:24 am
- Location: Hurricaneville Florida
-
sunshinegirl690
- Posts: 43
- Joined: Sat Apr 29, 2006 11:24 am
- Location: Hurricaneville Florida
- Ken Berry
- Site Admin
- Posts: 22481
- Joined: Fri Dec 10, 2004 9:36 pm
- System_Drive: C
- 32bit or 64bit: 64 Bit
- motherboard: Gigabyte B550M DS3H AC
- processor: AMD Ryzen 9 5900X
- ram: 32 GB DDR4
- Video Card: AMD RX 6600 XT
- Hard_Drive_Capacity: 1 TB SSD + 2 TB HDD
- Monitor/Display Make & Model: Kogan 32" 4K 3840 x 2160
- Corel programs: VS2022; PSP2023; DRAW2021; Painter 2022
- Location: Levin, New Zealand
Bob733 -- to get back to your question, yes, you can certainly have 'stock' .vsp's which you can insert in other .vsp's. They are then called 'nested' .vsp's. This was only introduced with VS10.
The one limitation is that while VS will treat a nested .vsp just like an ordinary video clip, you cannot edit the nested .vsp while it is nested. You would have to extract it and edit is separately, then re-nest it. But from your own point of view of using 'stock' .vsp's, I would imagine you would not need to edit them further in any case...
I suppose, though, you also need to be aware that if you nest a project within another, then nest that project in another, the end quality tends to drop off fairly noticeably in the sub-nested parts... if you see what I mean!
The one limitation is that while VS will treat a nested .vsp just like an ordinary video clip, you cannot edit the nested .vsp while it is nested. You would have to extract it and edit is separately, then re-nest it. But from your own point of view of using 'stock' .vsp's, I would imagine you would not need to edit them further in any case...
I suppose, though, you also need to be aware that if you nest a project within another, then nest that project in another, the end quality tends to drop off fairly noticeably in the sub-nested parts... if you see what I mean!
Ken Berry
-
sjj1805
- Posts: 14383
- Joined: Wed Jan 26, 2005 7:20 am
- System_Drive: C
- 32bit or 64bit: 32 Bit
- motherboard: Equium P200-178
- processor: Intel Pentium Dual-Core Processor T2080
- ram: 2 GB
- Video Card: Intel 945 Express
- sound_card: Intel GMA 950
- Hard_Drive_Capacity: 1160 GB
- Location: Birmingham UK
This is one of the strong points of its Big Brother program MediaStudio Pro - especially with its Smart Compositor. That is the good news.
The bad news is that Officially it is not Vista Compatible (Though your current system is XP so you will be OK) plus we do have a work round
This Is How To Install MSP 7 or 8 on Microsoft Vista
I have also received a recent communication from Corel where they have stated that they are concentrating on VideoStudio, MovieFactory and some other products (Other communications I have had would suggest PhotoImpact is included). Should you wish to consider MediaStudio it is of course also possible to Create a Dual Boot Vista/XP System
If we stick to VideoStudio then you would have a bit more work to do using nested VideoStudio Projects. A VideoStudio project nested within another cannot be directly modified and so what you would do is this.
1. Create your collection of VideoStudio stock projects.
2. When you wish to use one you would have to make a copy of that VSP so that you preserve the original.
3. You then make whatever modifications are required to that copy.
4. You then import that copy into your new project.
The bad news is that Officially it is not Vista Compatible (Though your current system is XP so you will be OK) plus we do have a work round
This Is How To Install MSP 7 or 8 on Microsoft Vista
I have also received a recent communication from Corel where they have stated that they are concentrating on VideoStudio, MovieFactory and some other products (Other communications I have had would suggest PhotoImpact is included). Should you wish to consider MediaStudio it is of course also possible to Create a Dual Boot Vista/XP System
If we stick to VideoStudio then you would have a bit more work to do using nested VideoStudio Projects. A VideoStudio project nested within another cannot be directly modified and so what you would do is this.
1. Create your collection of VideoStudio stock projects.
2. When you wish to use one you would have to make a copy of that VSP so that you preserve the original.
3. You then make whatever modifications are required to that copy.
4. You then import that copy into your new project.
the major problem is that nested projects are allways re-rendered, even if by themselves would be smartrendered end-to-end.
this lead to longer rendering time and degrading, specially for HD
it's a pity, i like to edit my fam. clips per event, then is easier to agregate later by keeping the original projects and not the rendered results.
this lead to longer rendering time and degrading, specially for HD
it's a pity, i like to edit my fam. clips per event, then is easier to agregate later by keeping the original projects and not the rendered results.
Seriously??? If this is true, nested VSPs are pretty much worthless. I assumed that since my nested VSP itself is smart-rendered (it's mostly MPEG files), it would be smart-rendered when it is included. I never thought to test it.calinux wrote:nested projects are always re-rendered, even if by themselves would be smartrendered end-to-end.
Rich
-
sjj1805
- Posts: 14383
- Joined: Wed Jan 26, 2005 7:20 am
- System_Drive: C
- 32bit or 64bit: 32 Bit
- motherboard: Equium P200-178
- processor: Intel Pentium Dual-Core Processor T2080
- ram: 2 GB
- Video Card: Intel 945 Express
- sound_card: Intel GMA 950
- Hard_Drive_Capacity: 1160 GB
- Location: Birmingham UK
Have you got some bench mark times that you can share with us?calinux wrote:the major problem is that nested projects are allways re-rendered, even if by themselves would be smartrendered end-to-end.
this lead to longer rendering time and degrading, specially for HD
it's a pity, i like to edit my fam. clips per event, then is easier to agregate later by keeping the original projects and not the rendered results.
