OmicronNeon

My "favorite" is when I get customer's asking me to do something we don't or calling in to have me get into one of their accounts or phone as if I have instant access. When they cannot understand why I cannot, I then have to explain to them that these things are not actively open for security and their privacy. At this point, some of them have hung up in a huff.
A recent instance involved a guy (I was working at AT&T advanced technical support at this point) who called in to have his email fixed on his phone. For starters, his iPhone didn't have the right password saved and his email was an outlook email which I did not have access to (nor could I pull it up online because our location blocked most sites they considered "out of scope"). In short, he wanted me to fix the password and then push the fix to his phone while he was at work and expected me to do this without him having do anything and insisted that we could do. The trouble is, we had no access at our location for remote access to iPhones (which requires iTunes to do) and outlook wasn't an email we serviced. If someone had done this for him in the past, it wasn't us. He said he keep calling back until he got someone who could help him.
 
My truly favorites are the ones who came to me about their phone making no sounds (iPhone) and they failed to check the silent switch on the left-hand side. At least these ones didn't get mad at me, they just acted embarrassed.

Customer walks into the IT shop I worked at. She looks around (Computers and gadgets everywhere) . She walks to the counter and asks me if we sell clothes.

My "favorite" is when I get customer's asking me to do something we don't or calling in to have me get into one of their accounts or phone as if I have instant access. When they cannot understand why I cannot, I then have to explain to them that these things are not actively open for security and their privacy. At this point, some of them have hung up in a huff.
A recent instance involved a guy (I was working at AT&T advanced technical support at this point) who called in to have his email fixed on his phone. For starters, his iPhone didn't have the right password saved and his email was an outlook email which I did not have access to (nor could I pull it up online because our location blocked most sites they considered "out of scope"). In short, he wanted me to fix the password and then push the fix to his phone while he was at work and expected me to do this without him having do anything and insisted that we could do. The trouble is, we had no access at our location for remote access to iPhones (which requires iTunes to do) and outlook wasn't an email we serviced. If someone had done this for him in the past, it wasn't us. He said he keep calling back until he got someone who could help him.
 
My truly favorites are the ones who came to me about their phone making no sounds (iPhone) and they failed to check the silent switch on the left-hand side. At least these ones didn't get mad at me, they just acted embarrassed.

I thought you were smarter than that. Apparently you can't get past calling names and discussing unknown strangers instead of ideas.
 
Your point was that some intelligence activities, to be effective, need to be secret. My point is that, once something can't be known, it can't be judged, and therefore those involved in "intelligence matters" become accountable only to themselves. A risky thing to do, and a strange one for a democracy.
 
Now go back to play amateur internet psychologist if you want.

FTFY

My "favorite" is when I get customer's asking me to do something we don't or calling in to have me get into one of their accounts or phone as if I have instant access. When they cannot understand why I cannot, I then have to explain to them that these things are not actively open for security and their privacy. At this point, some of them have hung up in a huff.
A recent instance involved a guy (I was working at AT&T advanced technical support at this point) who called in to have his email fixed on his phone. For starters, his iPhone didn't have the right password saved and his email was an outlook email which I did not have access to (nor could I pull it up online because our location blocked most sites they considered "out of scope"). In short, he wanted me to fix the password and then push the fix to his phone while he was at work and expected me to do this without him having do anything and insisted that we could do. The trouble is, we had no access at our location for remote access to iPhones (which requires iTunes to do) and outlook wasn't an email we serviced. If someone had done this for him in the past, it wasn't us. He said he keep calling back until he got someone who could help him.
 
My truly favorites are the ones who came to me about their phone making no sounds (iPhone) and they failed to check the silent switch on the left-hand side. At least these ones didn't get mad at me, they just acted embarrassed.

My "favorite" is when I get customer's asking me to do something we don't or calling in to have me get into one of their accounts or phone as if I have instant access. When they cannot understand why I cannot, I then have to explain to them that these things are not actively open for security and their privacy. At this point, some of them have hung up in a huff.
A recent instance involved a guy (I was working at AT&T advanced technical support at this point) who called in to have his email fixed on his phone. For starters, his iPhone didn't have the right password saved and his email was an outlook email which I did not have access to (nor could I pull it up online because our location blocked most sites they considered "out of scope"). In short, he wanted me to fix the password and then push the fix to his phone while he was at work and expected me to do this without him having do anything and insisted that we could do. The trouble is, we had no access at our location for remote access to iPhones (which requires iTunes to do) and outlook wasn't an email we serviced. If someone had done this for him in the past, it wasn't us. He said he keep calling back until he got someone who could help him.
 
My truly favorites are the ones who came to me about their phone making no sounds (iPhone) and they failed to check the silent switch on the left-hand side. At least these ones didn't get mad at me, they just acted embarrassed.

My "favorite" is when I get customer's asking me to do something we don't or calling in to have me get into one of their accounts or phone as if I have instant access. When they cannot understand why I cannot, I then have to explain to them that these things are not actively open for security and their privacy. At this point, some of them have hung up in a huff.
A recent instance involved a guy (I was working at AT&T advanced technical support at this point) who called in to have his email fixed on his phone. For starters, his iPhone didn't have the right password saved and his email was an outlook email which I did not have access to (nor could I pull it up online because our location blocked most sites they considered "out of scope"). In short, he wanted me to fix the password and then push the fix to his phone while he was at work and expected me to do this without him having do anything and insisted that we could do. The trouble is, we had no access at our location for remote access to iPhones (which requires iTunes to do) and outlook wasn't an email we serviced. If someone had done this for him in the past, it wasn't us. He said he keep calling back until he got someone who could help him.
 
My truly favorites are the ones who came to me about their phone making no sounds (iPhone) and they failed to check the silent switch on the left-hand side. At least these ones didn't get mad at me, they just acted embarrassed.

Honest Answer Time: I've no fucking clue
 
All I know is that GPU accelerated encoding has historically added more artifacts and quality reductions compared to a similar "quality level" CPU encode. I always figured it had something to do with the basic architecture of a GPU (simple parallelization vs complex instructions structure of a CPU)
 
@AshleyAshes you seem to know an unhealthy amount about video encoding - do you happen to know the answer to this question?