Visualisers - Windows 10

[snagrat]

Just upgraded a site to Windows 10 and having issues with their 2 models of visualisers

 

One is a AVer 300AF and the other a Genee GV6100.

 

Anyone had any luck with these? Seems the generic installed driver does not work and struggling to find a Win10 64bit driver anywhere

[snagrat]

So the Genee seems to work OK but not the Aver 300af

 

Has anyone managed to use one of these with Windows 10?

[DrBeaker]

How old are the devices?

[3s-gtech]

Many of our older Aver models (e.g F30) just stopped working with Windows 10 1903, where they worked with 1703. Camera app and Sphere2 can’t connect to it, yet the driver is there.

 

I bought a couple of new ones instead.

 

The Aver U15 still work though.

 

You may find that it works on an older build or LTSC.

[snagrat]

10 years I would say.

 

I know it’s old but thought these would just be classed as cameras now. Shows a legit driver but just seems to think something else is using it

[3s-gtech]

I get exactly the same, the software thinks it’s in use, camera app doesn’t see it. My testing indicates it’s game over for them but I’d love to be wrong.

 

I did test with the very latest software which was out this month I think - no different. Worth a try for you though.

[DrBeaker]

10 years I would say.

 

I know it’s old but thought these would just be classed as cameras now. Shows a legit driver but just seems to think something else is using it

 

 

10-years - I think the school has got their money's worth then.

 

I speak from experience when trying to get some old Canon Scanners working under Windows 7 x64 years ago. I did a bit of research and came across this post on a forum https://www.sevenforums.com/drivers/46741-canoscan-lide20-64bit-driver.html where Canon advised "Canon cannot guarantee the future compatibility of our products ad infinitum." so basically "tough, buy a new scanner".

 

Rightly or wrongly it's planned obsolescence, not much we can do about it as IT people. Same reason why people buy a new iPhone every year.

Edited September 30, 2019 by DrBeaker

[mikeprice]

seems to me that Microshaft publisise a 'proper way to do things'

 

if device makers stick to the rules then the device should keep working forever

and with a bit of forward thinking design you would make everythng as close to the basic Windows drivers as possible

 

 

but it never seems to work out so that it just keeps working - either the device driver contravenes the unwritten laws or Microshaft change the laws of the universe and it all goes West

 

 

so we end up as the Evil IT demons and need to spend £2.50 of precious school funds that should be used to spend £5000 on some new literacy initiative with the words cloud and probably leverage in it

and will last 1 year before that SMT member moves on and some new young over promoted prospective SMT member comes 'on board' and 'reinvents the vision of literacy in the $somethingorother'

 

 

errr - might have gone overboard there

or maybe not

[Jobos]

I found the Aver visualisers we have stopped working after updating to 1903 but after the September Windows updates they started working again. MS must have realised the error and patched it.

[snagrat]

What model do you have?

[Garacesh]

Try as I might I can't get our oooold CP130's and CP135's working with Windows 10 1903.

They worked on LTSB 2016 (1607) but there must've been enough changed that it's a no-go now.

 

And since they're proprietary, you can't just use ditch A+ (or Sphere) and switch to FOSS software, 'cause it can't interpret the camera feed.

 

We gave up and bought a bunch of HUE Visualisers, which work over uPnP so you can just use whatever software you feel like.

(We actually ended up using IPEVO's software since we own some of their visualisers, too. I can only assume they're uPnP too)

[jthompson]

We had a HUE HD camera in the office the other day that worked okay on 1709 but not on 1903. The HUE software CD installed amcap.exe. On 1903, amcap just showed a black image when you selected the HUE as the camera device. An earlier version of amcap (8.11) does work with it on 1903, however. Go figure.

[3s-gtech]

I found the Aver visualisers we have stopped working after updating to 1903 but after the September Windows updates they started working again. MS must have realised the error and patched it.

I've been delaying patches due to 1903 rollout, but I'll push that out and see.

[old_n07]

We use our HUE visualisers with VLC media player, it saves us having to install extra software and the staff are already familiar with it.

[snagrat]

Yes it’s worked for me! The latest update seems to have made them all work.

[Garacesh]

We use our HUE visualisers with VLC media player, it saves us having to install extra software and the staff are already familiar with it.

 

Aye, we thought about that at first.

But they have microphones in them that VLC (quite understandably) picks up on.

 

Echo..Echo..Echo..Echo..Echo..Echo..ECHO..ECHO..ECHO..ECHECHECHECHEHCHBWWWWRWRWRRRRRWRRWRRWR

 

Not a pleasant experience

I know you can tell VLC to stop picking up the input, or just turn the volume off, but that's just extra faff, and we already had software that was specially meant for visualisers with freeze/rotate/side-by-side/timelapse/etc functions built in, so made sense to just use that.

Edited October 2, 2019 by Garacesh

[Jobos]

What model do you have?

Several different models but the one in front of me is the CP150. The others models are better and have lasers dots outlining the field of view but are around the same age.

[3s-gtech]

You legend @Jobos. My old Aver F30 works again on Windows 10! I was ready to rage quit them, but they're working.

 

If you have them set up correctly, they shouldn't just work with Sphere2 alone - mine works with SfB and VLC (but not with Camera, meh).

Edited October 2, 2019 by 3s-gtech