Black magic help?? I hope.

david-ruby wrote on 6/2/2009, 3:40 PM
I am using Vegas 8.0c and intensity pro. I only wish to use it as a preview card to our 42 inch lcd. What I get when viewing from the time line is a jagged edge picture. But when I click on the same file in the explorer window in vegas. It is perfect. I am also running a vista 64 bit machine so I have both vegas 8c and vegas 8.1.
Is there something I am doing wrong here? Also I only see aja and Deck link and OHCI compliant avaliable under preview device. No Intensity pro.
HELP!! : )
Thank you.

Comments

jabloomf1230 wrote on 6/2/2009, 4:09 PM
I can't help you with the display problem, since Intensity Pro support in Vegas 8 is a bit shaky. The IP does show up as "Blackmagic Design Decklink (TM)", though, not "Intensity Pro". There is no IP support for 64 bit Vegas at all, at least I've never seen the option.
david-ruby wrote on 6/2/2009, 4:22 PM
Thank you for your reply.
Is there any other solution for a card in the $200 price range that does work with Vegas?

David
TimTyler wrote on 6/2/2009, 5:21 PM
> What I get when viewing from the time line is a jagged edge picture.

What's your source/project resolution. If you're stretching SD to an HD monitor it's not going to look good.

If not, use the Intensity Control Panel app to set Output Processing to match your display monitor.

Then adjust the preview window in Vegas to "Best" quality.
david-ruby wrote on 6/2/2009, 5:46 PM
Hello Tim. The footage is HDV 60i. 1440 X1080.

David
newhope wrote on 6/2/2009, 6:02 PM
If not, use the Intensity Control Panel app to set Output Processing to match your display monitor.

Have you selected the correct output setting in Vegas when you selected the Intensity Pro (as a Blackmagic Decklink card) in Vegas /Video Preview?

I have an Intensity Pro and it works for me in both SD and HD BUT I have to correctly select the output format in Vegas to suit the project. I'm certainly not getting jagged lines in either if the settings are correct but it will look terrible if they aren't.

What type of connection are you using to your monitor?
You should use HDMI or Component, but NOT use composite or S-Video for HD material.

New Hope Media
david-ruby wrote on 6/2/2009, 7:45 PM
Hello. I actually did get it to finally work. I needed to have vegas match the media for the properties and all went well. Only problem now is I add a New Blue fx to a file and the playback on the external comes to a halt. Freezes up.
Do I need an accelerator break out box like a matrox??
My machine is as fast as I can get it with an I7 runnin the show. LOL
Ideas?
David
newhope wrote on 6/3/2009, 4:14 AM
No you just need to 'selectively render' your files with transitions and FX, like New Blue FX.

Obviously hardware accelerators are a great benefit but selective rendering, which shouldn't take a long time, will cure the stutters or freezes on FX that won't play, un-rendered, in real time.

Real time replay is limited and the more filters, FX and transistions you stack up the less likely it is going to play smoothly, which is why the 'selective render' option exists. A point to note is that your 'selective renders' will disappear if you add new tracks etc so they may need to be re-rendered occasionally during an edit session.

Make sure you choose to render in the correct format for your project.

New Hope Media
Leopardman wrote on 6/3/2009, 1:00 PM
I also use the Intensity Pro card and have not yet encountered any problems with it, e.g. I do not need to prerender any transitions or FX when previewing. I use 2 Philips 19" monitors for editing porposes, the secondary one contains the Vegas preview window and then I use a Samsung HD LCD via HDMI for preview as well. To me it is rather a function of the processing capability. I have 2 sets of Raid0 drives that contains the HD or HDV video footage, 2 SATA work drives (i.e. rendered files and projects) and C drive also SATA. 4gig of RAM, Vista 64 as O/S, Preview ram set to 750MB, I have yet to get Vegas to use more than 3.2 gig ram, even "hammering" it with HD rendering. Currently I render HDV equal to the duration of the project, HD varies 5 to 15% more.

The only issues I have encountered thus far are as follows:

1. If the Intensity Pro drivers were installed prior to a Vegas installation, then the Intensity Pro dll's have to be copied to the appropriate Vegas folders. This applies to the Intensity Pro 32 bit and 64 bit drivers. I use the 64 bit drivers.
2. Vegas 9 64 bit does not "recognise" these dll's and therefor does not display it in the options as a "preview device". However the Intensity Pro 64 bit drivers work with Vegas 9 32 bit. I don't know if this is an issue that has to be resolved by Vegas or Intensity Pro, neither has come up with a solution yet. Thus currently I'm using Vegas 9 32 bit and Intensity Pro 64 bit.

Eddie
Spotted Cat Productions
david-ruby wrote on 6/7/2009, 10:59 AM
Hello Cat and all.
A few questions.

So the dual raid drives help with your graphics being run from the time line? What do you run your preview in vegas at? Best full? Can you add a glow or intensive fx to a track and get no stutter at this preview?

David : )

jabloomf1230 wrote on 6/7/2009, 11:51 AM
Vista x64 needs 64 bit device drivers or no software will find the device. The Intensity Pro driver is Intensity.sys and comes in both 32 and 64 bit versions.

Vegas Pro needs a DLL (DeckLinkVegas.dll) to interface with the driver. There is no 64 bit version of this DLL available, at least as far as I can tell. That's why the 32 bit versions of Vegas "see" the driver, but the 64 bit versions don't.
Leopardman wrote on 6/7/2009, 11:53 AM
Hi David,

The raid0 configuration definitely helped with the preview imho to previous experience, Video Preview setting is Auto in preview window. I aslo played around with the RAM Preview settings, values between 0 and 1024MB, did not really notice any significant difference. Currently have it set at 750MB.

What I did find interesting, these specific shoots were done for a music DVD, is where the singer/artist moved around fast, camera remained stationary, on Vegas Pro 8 and 9 32-bit, the preview frame rate would drop from 25 frames/sec (i shoot PAL) to 20 -21 frames per second. When movement is slower it went back to 25 frames/sec.

With Vegas Pro 9 64-bit no degradation in frame rate was experienced.

I've tested FX using the standard glow FX, i.e. white soft, white intense, and green highlights, each one seperately using this footage. I got the same results as without glow, both in Vegas Pro 9 32-bit and 64-bit. In my opinion, where I did get stuttering in the 32-bit version was as a result of a fast moving object (no panning!!) as described above. Thus on my configuration applying FX did not degrade my performance. At this point I am quite satisfied since I made my hardware changes the stuff I've been working on did not require any prerendering.

Eddie
Spotted Cat Productions
david-ruby wrote on 6/7/2009, 12:43 PM
Thanks Eddie.
Is your preview set at (best full) or just (preview full)?
Is your video a lil blurry if at preview full?Not as crisp as it is at best full?
Sorry. Just want to clarify. I appreciate all the help everyone as well. ; )
David
Leopardman wrote on 6/7/2009, 1:12 PM
Hi David,

Using the drop-down list on the preview window, mine is normally set to Preview>Preview>Auto

Tested it now using Preview>Best>Full and also Preview>Best>Auto. I can't notice any change or degradation in the quality of the video displayed in either modes, displayed size remains the same on my 2nd (dual monitor) as well as the frame rate.

Eddie
david-ruby wrote on 6/7/2009, 2:13 PM
WOW. I must have the wierdest set up ever. Both my machines show a difference from auto to full. Full is better quality.
Hmmmm?
Leopardman wrote on 6/7/2009, 11:23 PM
Hi David,

My setup is as straightforward as can come. I have 2 Philips 19" LCDs connected to my graphics card (512MB DDR2, Nvidia GT8500 chipset) configured as dual monitors (not spanned). The primary monitor is used for workspace/edit windows whilst the 2nd monitor contains only the Vegas Preview window. In addition to that I use the Intensity Pro HDMI card with a HD LCD as external monitor.

I tend to agree with you on a difference in quality between the preview settings, however that was before I upgraded my hardware. Now with it running so smoothly I honestly cannot detect any significant difference in quality. Previously I used to get a lot of "cadence", that is completely eliminated now.

Having worked in the IT industry for 28 years, if there is one thing that makes Vegas superior to other NLE's, is the fact that its core "engine" is hardware independent. Having used Premier before and getting highly frustrated at times, FCP was not an option either even though I think Apple is a good platform. Tried Avid as well, I decided on Vegas and do not regret it at all, started with Vegas 7. I currently have a number of friends having looked at my setup, that have moved to Vegas from Premiere and Avid.

Eddie
david-ruby wrote on 6/8/2009, 9:59 AM
Hello Eddie. I agree. I love the Vegas. I have been lucky enought o have been her since the first product Sound Forge by sonic Foundry. : )
Yeah way back. Then came Vegas as we were all working with SAW STUDIO. Vegas won us all over. Great tech team back then of Dave and the boys. Miss them on here dearly.

With the praise said.

I might have to look at a dual raid then.
Renders on one setup and editing files on the other eh?
Is this set up as raid 0s I assume?
Thank you Eddie for the great conversations. ; )
David
Leopardman wrote on 6/8/2009, 10:39 AM
Hi Dave,

The 2 Raid 0 drives are used solely used to capture to and thus contains my source files for editing purposes. I have 2 additional Sata drives that I use as "work" drives. The one is primarily used to render to, whether it be intermediate or final. Obviously Raid to Raid rendering will be faster as I/O is much faster. Primary reason for using multiple drives is to avoid buffer or disk I/O contention to enable faster rendering. Also swap file location is important as this may also cause I/O and buffer contention. Swap file is on 2nd "work" Sata which I primarily use for backup, project definitions etc. O/S or system drive is also a seperate Sata drive. With my current configuration I get little swap if any at all.

Keep well.

Eddie