The Joys of using Pangolin

[andy_con]

after i uninstalled the fb3s and got them working livepro wouldnt work with my midi. when i went into the midi options in livepro, the midi was showing up but not working. thats not a computer problem

[norty303]

Well, they're all computer problems 'per se' Andy, its running on a computer...

[White-Light]

after i uninstalled the fb3s and got them working livepro wouldnt work with my midi. when i went into the midi options in livepro, the midi was showing up but not working. thats not a computer problem

If your Live Pro installation or settings files have become corrupted it is. It's amazing how many times Windows manages to screw up installed programmes. I've lost count of the number of non functioning programmes I've re-installed only to have them work perfectly for years in exactly the same configuration once re-installed. However, its all speculation. It could be Live Pro or it could be the pc. I would have just expected it to re-produce itself regularly if Live Pro. Programmes that have bugs don't usually just fault the once. Anyway, glad you got everything sorted with the driver er-install and re-jig.

[catalanjo]

Well, they're all computer problems 'per se' Andy, its running on a computer...

Ahh the voice of wisdom ! .. LOL
But don´t forget the external hardware !
Cheers

[buffo]

Anybody ever yank out a USB thumbdrive without first going through the "remove device safely" step in Windows, only to have the thumbdrive get corrupted? (Even if you weren't copying files to it at the time?) OK, I know I've had that happen plenty of times, and I'm sure many of you have as well.

Now, when that happens, do you blame the company that made the thumbdrive, or do you blame Microsoft for writing a shitty OS that allows this to happen?

Andy's problems with the FB3 are similar. I'm not saying that the FB3 is perfect, but Microsoft's implementation of USB is a lot less perfect! Chances are very, VERY good that this is an issue with the OS, not the FB3 hardware OR the Quickshow software (or LivePro, for that matter).

This is why Bill tells people to check the computer first. For every genuine bug Pangolin manages to find in either their hardware or software, there are HUNDREDS of problems that are not caused by anything they sell. And yet they still get blamed for them all. Just because the FB3 driver got screwed up doesn't mean Pangolin's software did it. More likely it was the host OS that screwed the pooch. That sort of puts Bill's frustration into a new light, doesn't it?

If you really want to try an unstable laser show software package, go download the demo version of Phoenix and see how far you get. (My record is 6 minutes before it crashed.)

And I'm sorry to say this, but if you're doing a paid show, the computer you use should never be connected to the Internet. If you want to surf, do it on your phone or bring another laptop to play with. Mission critical hardware stays off the Internet - period. That's just good business practice.

Adam

[Things]

I experienced this same sort of thing a few months ago at the school musical. We had a matinee show the next day, however Quickshow was up and running fine the day before. Get in the next day, fire everything up, and Quickshow starts complaining about a corrupted workspace file. Had to rush home, re-download quickshow, nd made it back 30 mins before the start Of course, I hadn't done anything to bring this on, it's just the way Windows works I suppose.

[flecom]

hah, I just had something similar happen to me tonight when I was doing a demo for someone... turned on my laptop, opened QS and it was telling me that it had to update the firmware on my FB3... huh? so I say ok and it said my FB3 had firmware v.0.0 ummm? then it kept saying the FB3 was unplugged, then reattached, over and over... so I gave up, restarted, and it was like if nothing happened... weird/????

[White-Light]

hah, I just had something similar happen to me tonight when I was doing a demo for someone... turned on my laptop, opened QS and it was telling me that it had to update the firmware on my FB3... huh? so I say ok and it said my FB3 had firmware v.0.0 ummm? then it kept saying the FB3 was unplugged, then reattached, over and over... so I gave up, restarted, and it was like if nothing happened... weird/????

That is weird. I have my FB3 permanently connected to my desktop PC, its never ever off unless I intentionally unplug it for reason. Despite probably switching my pc on or off around 10 times a day, I've never had any kind of issue in the 2 years or so its been connected.

[andy_con]

so how come my normal every day laptop which i usee to surf and do everything on works just fine. after i do windows updates none of the software stops working, i dont have to uninstall the printer for example and reinstall it very time windows updates.

my camera software works fine after a windows update
my phone software works fine after a windows update


yet people seem to be suggesting every time windows updates on my laser laptop i should get problems with the pangolin software and need to reinstall drivers or whatever. yet thats a computer problem not a pango problem.

i love my fb3 and livepro i wouldnt use anything else (i think ;-) ) but people keep banging on about its not pango its the computer i thnk are wrong.

[White-Light]

If it Pangolin software then it should be re-produce able. Software bugs don't just appear then disappear. If something disppears on a re0install never to re-appear then that suggests corruption on the PC rather than a software problem per se.

QS and Beyond both capture crashes to logs.

If you have something that' reproduce able but not being captured as a crash automatically, then force intensive logging, re-produce it and send the logs along with an explanation as to how to reproduce it and any screenshots along to Pangolin.

To force intensive logging:

Settings > Configuration > Log System tab > Force Intensive Logging Button.

Restart QS - it will then intensively log the next 3 QS start ups including the current re-start.

Only use if you can reproduce the problem.

The log files are timed and dated and depositied in the root Log Folder ie C drive: QS2 > Logs

Also, would be helpful if people could post a build number to see if there's anything in common although as I said, I suspect PC over software and that's not being pro Pangolin just going off the fact that it doesn't seem to be reported as reproduce able for most.