Something Close to or at least similar to the announcement at the VIDEO STUDIO forum http://phpbb.ulead.com.tw/EN/viewtopic.php?t=27
ONE STOP, ALLROUND advice
Home baked, Whole Grain Bread (with Nuts) for for nuts like me.
BEST GENERAL ADVICE (summarized) for MSP7
-
jjoshua
BEST GENERAL ADVICE (summarized) for MSP7
Could some of you Lovers of MSP7 post a personal Manifesto of how you use MSP7.
Something Close to or at least similar to the announcement at the VIDEO STUDIO forum http://phpbb.ulead.com.tw/EN/viewtopic.php?t=27
ONE STOP, ALLROUND advice
Home baked, Whole Grain Bread (with Nuts) for for nuts like me.
Something Close to or at least similar to the announcement at the VIDEO STUDIO forum http://phpbb.ulead.com.tw/EN/viewtopic.php?t=27
ONE STOP, ALLROUND advice
Home baked, Whole Grain Bread (with Nuts) for for nuts like me.
As a long time MSP user, forum hoverer and beta tester, I've come to the conclusion that such advice would hinder, rather than help. Why? Simply because two users never seem to have the same methods. The problem is that the software is too versatile and, if I told you to do X, Y and then Z, you would be missing out on many of the fine points that can make a project excellent, rather than simply good.
Just to illustrate this, I recently found a useful feature that had been there for years but I had never consciously realised what it was able to do.
Conversely, some users seem to take delight in making life difficult for themselves. I have constantly advised users to keep things as simple as possible and not try to do things that would intuitively seem to be good, but are, in reality, counter-productive. One example is encoding MPEG. How many times have I come across guys who think that encoding their DV AVI at 8000 kbit/s VBR is bound to be better than 6000 kbit/s CBR? Yet you cannot see any difference on the TV screen, assuming that both will play in a set-top DVD player (and often the 8000 VBR won't). But there may be other cases where a high bitrate multipass encoding can be justified, provided that the high bitrates aren't applied only to the transitions, which is very frequently what happens.
Rather than try to impose on you one person's MO, my suggestions are:
1. absorb the manual like you were blotting paper
2. buy Charlie Hill's "how-to" book (and absorb it)
3. experiment with the conditions which you will be working under (you may need to do things slightly differently according to your hardware, the nature of your input files, even whether you are working in NTSC or PAL etc.)
4. be prepared to spend a lot of time finding out what effects are appropriate for YOUR projects (not mine) etc.
Finally, just as an example of how ridiculous a "standard" MO may be, I could start describing my capture procedure by saying "Open your DVCAM DRV-1000P drive and insert the DV tape you wish to use". I do just that every day, but I'd be quite willing to bet a small sum that there is not one other single Sony DRV-1000P user on this forum.
Just to illustrate this, I recently found a useful feature that had been there for years but I had never consciously realised what it was able to do.
Conversely, some users seem to take delight in making life difficult for themselves. I have constantly advised users to keep things as simple as possible and not try to do things that would intuitively seem to be good, but are, in reality, counter-productive. One example is encoding MPEG. How many times have I come across guys who think that encoding their DV AVI at 8000 kbit/s VBR is bound to be better than 6000 kbit/s CBR? Yet you cannot see any difference on the TV screen, assuming that both will play in a set-top DVD player (and often the 8000 VBR won't). But there may be other cases where a high bitrate multipass encoding can be justified, provided that the high bitrates aren't applied only to the transitions, which is very frequently what happens.
Rather than try to impose on you one person's MO, my suggestions are:
1. absorb the manual like you were blotting paper
2. buy Charlie Hill's "how-to" book (and absorb it)
3. experiment with the conditions which you will be working under (you may need to do things slightly differently according to your hardware, the nature of your input files, even whether you are working in NTSC or PAL etc.)
4. be prepared to spend a lot of time finding out what effects are appropriate for YOUR projects (not mine) etc.
Finally, just as an example of how ridiculous a "standard" MO may be, I could start describing my capture procedure by saying "Open your DVCAM DRV-1000P drive and insert the DV tape you wish to use". I do just that every day, but I'd be quite willing to bet a small sum that there is not one other single Sony DRV-1000P user on this forum.
[b][i][color=red]Devil[/color][/i][/b]
[size=84]P4 Core 2 Duo 2.6 GHz/Elite NVidia NF650iSLIT-A/2 Gb dual channel FSB 1333 MHz/Gainward NVidia 7300/2 x 80 Gb, 1 x 300 Gb, 1 x 200 Gb/DVCAM DRV-1000P drive/ Pan NV-DX1&-DX100/MSP8/WS2/PI11/C3D etc.[/size]
[size=84]P4 Core 2 Duo 2.6 GHz/Elite NVidia NF650iSLIT-A/2 Gb dual channel FSB 1333 MHz/Gainward NVidia 7300/2 x 80 Gb, 1 x 300 Gb, 1 x 200 Gb/DVCAM DRV-1000P drive/ Pan NV-DX1&-DX100/MSP8/WS2/PI11/C3D etc.[/size]
-
MonroePoteet
First, convert your framestore...
I'd have to agree with Devil. I spend a lot of time in MSP integrating with 3D animation packages, which involves a lot of framestore management, image sequence conversions, strange filtering, alpha mask generation and editing, etc. I also do mostly 16:9 anamorphic video using a $700 anamorphic lens for my GL2. Probably not the most general-purpose advice you can get.
The first 70 pages of the manual that came with MSP7 is tutorials ranging from video capture through editing to Video Paint and title creation with CG Infinity. Might be a really good place to start. Then, each of us expands that general overview along the lines of our particular video application.
mTp
The first 70 pages of the manual that came with MSP7 is tutorials ranging from video capture through editing to Video Paint and title creation with CG Infinity. Might be a really good place to start. Then, each of us expands that general overview along the lines of our particular video application.
mTp