PDA

View Full Version : Vista 64bit Support


sunrise
15 Feb 2009, 04:46
Will VidBlaster work on Vista 64bit?

Mike
15 Feb 2009, 09:18
Yes.

wiav8r
28 Mar 2009, 16:00
Just for an FYI. VB works fine with Vista 64 bit. But beware of your frame grabber or capture card. I found out the hard way that my capture card DID NOT support 64 bit (Osprey-450e). So I have had to revert back to Vista 32 bit to get my capture card to work.

VB works fine in either 32 or 64 bit for me. running ver 0.42

agilpwc
06 Apr 2009, 00:21
Hey how is the 450e working out for you? It seems like a great way to get 4 cameras into the computer. No problems with vidblaster?

wiav8r
06 Apr 2009, 14:25
Hey how is the 450e working out for you? It seems like a great way to get 4 cameras into the computer. No problems with vidblaster?


Once I load up the cam modules and reset "standard NTSC" on each input. they work great! I currently have to do that every time I start VBS. I think that is a driver issue (see below). I also use the audio input of one of the channels for audio in on VBS from our mixer board. That way my PC sounds don't go out over vidblaster. Price is high but, tech support from osprey is good

BTW the Vista drivers for 32 bit don't work and still in beta. no 64 bit driver available yet. So, I'm using the XP 32 bit driver. That was advised per Osprey support.

wiav8r
27 Apr 2009, 15:55
Hey how is the 450e working out for you? It seems like a great way to get 4 cameras into the computer. No problems with vidblaster?


Works fantastic! Rock solid and you can use the audio inputs also. Be advised card does not have a reliable Vista driver. I am using XP 32 bit driver on a 32 Vista machine. No 64 bit driver for the osprey available yet. I am patiently waiting.

JakobR
07 Aug 2009, 14:01
Ordering my VB-machine on monday. I have an Osprey-card so I guess that means I will go for Vista 32bit.

Does that mean that I canīt use more than 4 GB of memory. The specifications from Vidblaster says 8 GB for HD material.

JAKOB

lill
07 Sep 2009, 16:07
The 4GB memory limit. is a Windows 32bit limit... So if there are non 64bit drivers for hardware... you are stuck with only 3,5GB (4GB RAM installed)

Is the Osprey card the only capture cards on the market ?

Or is it that they have the best price...

GHendershot
17 Oct 2009, 04:18
has anyone else tried VB with Win 7 64 bit yet ???

I am running into challenges with it running on a quad core 2.66 intel with Win 7 Build 7600, 8 gb RAM and a RAID 10 7200 RPM drive setup ... I am using 2xUSB web cams for video in, native motherboard Realtek sound and Nvidia 9800GT for video out against a pair of DVI 16x9 monitors ... figured the hardware to be well suited to the modest tasking I have in mind ... seems all worked pretty well when I had it loaded with 32 bit XP so I don't really think its a hardware issue ...

the problem I get is that the program just flat becomes unresponsive after a short time and can only be shut down with task manager ... its mildly amusing that the preview videos continue to refresh but less than amusing that I can no longer control what is being streamed nor even close the program down gracefully ...

now the fact is, I am often a bad boy and do run other programs at the same time as I run VB ... I might check email, maybe run Adobe Premier to capture and do post production and sometimes might even browse the web, all while VB is running ... I have monitored my resources and can report that I rarely hit more than 50% of available CPU nor exceed 50% of available RAM ... so while I do tend to multitask a bit, it is never at a level that pulls heavily on system resources ... main reason for moving to Win7 was that it is a much cleaner interface and seems easier on system resources than Vista ... reason for going to the 64 bit version was to get past that nasty 4gb RAM problem ... with XP 32 bit, I was commonly pushing at that limit when doing my normal chores ...

I am not easily beaten by such things but at this point I am at a loss ... would appreciate advice from anyone who might have already beaten a similar problem ...

lill
17 Oct 2009, 04:57
Hi GHendershot

I have been running Windows 7 for along time, with allmost no problems... non of the problems you are telling...

Please restart your machine... and donīt do anything else but VidBlaster and see how that is running... you might have CPU performance in % left.

You also have CPU time, (the time that the software needs to wait for its slot in the CPU to do the processing...)

See to it that you have the latest driver to all. You might also check out the Windows Experience Index... snd do a new test (Control Panel\Performance Information and Tools)

I see a lot of slow machine out "in the wild" and at many times.... the only thing you need to do is a new test...

APTV
18 Oct 2009, 18:42
the problem I get is that the program just flat becomes unresponsive after a short time and can only be shut down with task manager ... its mildly amusing that the preview videos continue to refresh but less than amusing that I can no longer control what is being streamed nor even close the program down gracefully ...



I have the same problem on my PC. While testing it out the program just stops responding but will still stream and change cams. I am pulling a fairly high cpu load though when I start the Ustream interface. It gets up to 35% sometimes 50%. My pc is Intel Core 2 quad 2.33Ghz, 6GB o ram, running Vista 64 bit with 2 USB cameras.

APTV
19 Oct 2009, 03:46
I figured out how to correct my problem. Like Ghendershot my program seemed to go flat even though the preview kept going. Reading some of the other post I figured out to hit the tab key then space bar and that gets the mouse and menus working again.

GHendershot
19 Oct 2009, 15:21
I figured out how to correct my problem. Like Ghendershot my program seemed to go flat even though the preview kept going. Reading some of the other post I figured out to hit the tab key then space bar and that gets the mouse and menus working again.



hey, it may not be a fix, but I am all in favor of a known working work around ... will that one a try ... thanks for the tip ...