I'm fairly new to both of these applications, but I've had fun learning Video Studio. I just bought 3D yesterday and just begun the tutorials, and some initial fooling around.
One thing I have quite figured out yet is how to make text that can be added to an existing Video Studio project. I'm not talking about a title page type thing, but applying the text (animated) on top of video, like the title feature within Video Studio.
I'd also enjoy hearing how you use 3D to spruce up your Video Studio projects. Any help or guidance will be appreciated!
Video Studio and Cool 3D
-
LGO
- Posts: 173
- Joined: Wed Jan 12, 2005 1:06 am
- System_Drive: C
- 32bit or 64bit: 32 Bit
- motherboard: Intel Corporation D915PBL AAC67720-301
- processor: 3.20 gigahertz Intel Pentium 4
- ram: 3 gb
- Video Card: ATI Radeon X300-X550-X1050 Series
- sound_card: Realtek High Definition Audio
- Hard_Drive_Capacity: 200-750gb
- Location: 3rd Coast USA
You don't say whether you're using C3D or C3DPS, but in this case it really doesn't matter.
Applying a C3D file to a VS project is simple. Just load the C3D file into your video library. Make sure you're in Timeline view, and then just drag the C3D project from the library and drop it into the overlay timeline.
Good luck,
LGO
Applying a C3D file to a VS project is simple. Just load the C3D file into your video library. Make sure you're in Timeline view, and then just drag the C3D project from the library and drop it into the overlay timeline.
Good luck,
LGO
-
CalifDude
-
LGO
- Posts: 173
- Joined: Wed Jan 12, 2005 1:06 am
- System_Drive: C
- 32bit or 64bit: 32 Bit
- motherboard: Intel Corporation D915PBL AAC67720-301
- processor: 3.20 gigahertz Intel Pentium 4
- ram: 3 gb
- Video Card: ATI Radeon X300-X550-X1050 Series
- sound_card: Realtek High Definition Audio
- Hard_Drive_Capacity: 200-750gb
- Location: 3rd Coast USA
I noticed you posted this same query in the VS Forums. Please don't cross-post. Put your questions in one forum or the other as appropriate. Thanks. 
Good luck,
LGO
You have to output to 32 bit AVI file with no compression. Creates a huge file, but if it's something like a watermark then you can make a 2 or 3 second clip and keep adding it to the overlay timeline. You can even fade-in the first clip and fade-out the last clip.. . . but how do you make it without a background color so it can be applied over video footage or a photograph?
Good luck,
LGO
-
Terry Stetler
- Posts: 973
- Joined: Thu Mar 17, 2005 3:34 pm
- Location: Westland, Michigan USA
If you're doing animations for video and not the internet then Cool3D Production Studio is the better choice. It can use video textures, has a GREAT keyframe timeline and can do quite a few things the plain-Jane C3D cannot.
Cool3D tips;
1. C3D of any stripe is a CPU and memory hog which renders slowly, which is pretty much normal for 3D programs in general. Try rendering with 3D Studio MAX, MAYA, Lightwave etc. sometime
2. as such when creating your project work in as low a resolution as practical. I often use half full screen for DV; 360x40, because it reduces the system load by almost 75%. In addtion to this lowering the display quality to DRAFT also quickens its responsiveness. Wireframe is also an option. Once things are "right" I then up the resolution to full size for a final look at quality and for export.
3. Output quality, as in for producing preview playbacks etc., should also be cranked down when you're just positioning objects, adjusting movements, applying textures etc. I only crank up the quality when doing that final look and exporting.
4. another trick is to work not in the 29.970 fps frame rate for NTSC video (25 fps for PAL) but in something more like 12-15 fps. You can always raise it to full rate before export, with a corresponding increase in the nuber of frames in the project. Fewer frames = quicker rendering of previews.
NOTE: when you go from your working frame size/frame rate to a full size/rate Cool3D will make the necessary adjustments, repositioning the keyframes (Cool3D PS) etc.
5. Using C3D project files in either the MediaStudio Pro or VideoStudio timeline results in them having very irregular previews and poor response because of the high CPU load of rendering the C3D content in memory.
I only use this mode of operation for very small things like Bugs (small corner animations on TV), lower thirds (animated titles on the bottom of a TV like on news programs etc.) or other small events.
For larger or highly detailed animation overlays I use two techniques;
a. render as a 32 bit *.avi. This applies an alpha channel (transparency layer) to the animation that can be keyed out by either MediaStudio Pro or VideoStudio, allowing the background video to show through.
b. render as a *.tga image sequence w/transparency turned on. Image sequences are a folder full of *.tga images (1 image = 1 video frame) that can be loaded into either MediaStudio Pro or VideoStudio using the *.uis filetype in the Insert Video dialogs.
Once *.uis is selected clicking on the Options button will take you to another dialog where you define the image sequence. Here you can define the frame rate, number of frames (you don't have to take all of 'em) etc. Once finished define a filename (ex:filename.uis) and save the file.
Filename.uis will be small proxy file for the whole and is what actually gets loaded into the editor. From there you can treat the image sequence as you would any other video file (adding video filters, motion...whatever) and they do play back in realtime on any decent system.
Image sequences are great because the individual images can be edited in Photoshop, PhotoImpact etc. just in case of a few stray pixels or if you want to add something in post (laser blasts, etc.) and not have to re-render the whole shebang.
Cool3D tips;
1. C3D of any stripe is a CPU and memory hog which renders slowly, which is pretty much normal for 3D programs in general. Try rendering with 3D Studio MAX, MAYA, Lightwave etc. sometime
2. as such when creating your project work in as low a resolution as practical. I often use half full screen for DV; 360x40, because it reduces the system load by almost 75%. In addtion to this lowering the display quality to DRAFT also quickens its responsiveness. Wireframe is also an option. Once things are "right" I then up the resolution to full size for a final look at quality and for export.
3. Output quality, as in for producing preview playbacks etc., should also be cranked down when you're just positioning objects, adjusting movements, applying textures etc. I only crank up the quality when doing that final look and exporting.
4. another trick is to work not in the 29.970 fps frame rate for NTSC video (25 fps for PAL) but in something more like 12-15 fps. You can always raise it to full rate before export, with a corresponding increase in the nuber of frames in the project. Fewer frames = quicker rendering of previews.
NOTE: when you go from your working frame size/frame rate to a full size/rate Cool3D will make the necessary adjustments, repositioning the keyframes (Cool3D PS) etc.
5. Using C3D project files in either the MediaStudio Pro or VideoStudio timeline results in them having very irregular previews and poor response because of the high CPU load of rendering the C3D content in memory.
I only use this mode of operation for very small things like Bugs (small corner animations on TV), lower thirds (animated titles on the bottom of a TV like on news programs etc.) or other small events.
For larger or highly detailed animation overlays I use two techniques;
a. render as a 32 bit *.avi. This applies an alpha channel (transparency layer) to the animation that can be keyed out by either MediaStudio Pro or VideoStudio, allowing the background video to show through.
b. render as a *.tga image sequence w/transparency turned on. Image sequences are a folder full of *.tga images (1 image = 1 video frame) that can be loaded into either MediaStudio Pro or VideoStudio using the *.uis filetype in the Insert Video dialogs.
Once *.uis is selected clicking on the Options button will take you to another dialog where you define the image sequence. Here you can define the frame rate, number of frames (you don't have to take all of 'em) etc. Once finished define a filename (ex:filename.uis) and save the file.
Filename.uis will be small proxy file for the whole and is what actually gets loaded into the editor. From there you can treat the image sequence as you would any other video file (adding video filters, motion...whatever) and they do play back in realtime on any decent system.
Image sequences are great because the individual images can be edited in Photoshop, PhotoImpact etc. just in case of a few stray pixels or if you want to add something in post (laser blasts, etc.) and not have to re-render the whole shebang.
Terry Stetler
