At least his credibility didn't take a hit. Same old Harry from start to finish. He ain't your huckleberry.
Upvote
0
tron said:A very nice trick to hide his incompetence. Of course Harry you have no code at all and you didn't want to be ridiculed ;D
So better a liar rather than incompetent (or troll?) ;D
HarryFilm said:...just can't talk right now due to a legally enforceable "Quiet Period Status" ...
Code is worse than bad: Non-existent! Just Trolling and Lies...HarryFilm said:tron said:A very nice trick to hide his incompetence. Of course Harry you have no code at all and you didn't want to be ridiculed ;D
So better a liar rather than incompetent (or troll?) ;D
---
NO TROLLING nor Bad Code...just can't talk right now due to a legally enforceable "Quiet Period Status" ... Just wait for the To-be-sent-to-CanonRumors announcement coming soon....
...BUT...
we DO have another software surprise for you which should be happening right around this coming Wednesday....
mb66energy said:Seeing is beliving or so - so let's wait and see...Give it a chance ...
unfocused said:mb66energy said:Seeing is beliving or so - so let's wait and see...Give it a chance ...
You are joking, right?
Harry is a complete fraud. His story line is weak and contradicts itself at any number of points. I was curious how he might write himself out of the predicament he created for his character. Unfortunately, the end has turned out to be disappointing and trite.
The character is inconsistent. Somehow the genius anti-establishment code writer begging Canon to sue him has now morphed into an insignificant pawn of his overlords, happily selling out his principles to enable his bosses to make a buck.
A better writer might have been able to pull off that transformation. Unfortunately, Harry's fiction writing is no better than his code writing.
brad-man said:unfocused said:mb66energy said:Seeing is beliving or so - so let's wait and see...Give it a chance ...
You are joking, right?
Harry is a complete fraud. His story line is weak and contradicts itself at any number of points. I was curious how he might write himself out of the predicament he created for his character. Unfortunately, the end has turned out to be disappointing and trite.
The character is inconsistent. Somehow the genius anti-establishment code writer begging Canon to sue him has now morphed into an insignificant pawn of his overlords, happily selling out his principles to enable his bosses to make a buck.
A better writer might have been able to pull off that transformation. Unfortunately, Harry's fiction writing is no better than his code writing.
Does this mean that Harry doesn't get his helicopter?
neuroanatomist said:HarryFilm said:...just can't talk right now due to a legally enforceable "Quiet Period Status" ...
You do realize that your previous posts on this forum – including examples of your code and UI – constitute a public disclosure of what you're now trying to claim is material, non-public information, don't you? I expect you'd be hearing from the SEC, if any of this were anything more than you talking out of your butt.
HarryFilm said:neuroanatomist said:HarryFilm said:...just can't talk right now due to a legally enforceable "Quiet Period Status" ...
You do realize that your previous posts on this forum – including examples of your code and UI – constitute a public disclosure of what you're now trying to claim is material, non-public information, don't you? I expect you'd be hearing from the SEC, if any of this were anything more than you talking out of your butt.
---
Actually, I do know that WHICH I WHY I changed that part of the code!
I went with direct hardware assembly on the SOBEL edge detection code
simply because it was so much faster and the User Interface I showed
was a TEST SYSTEM to see if it actually all works....the people we deal
with want to SEE if what we say actually PERFORMS as how we say it does.
They also DO NOT CARE about the UI...they just want the codec itself
to stuff in their hardware and bioses! I've literally had to re-write the
thing in its ENTIRETY to comply with current Intellectual Property (IP)
disclosure issues such as what has been done recently on this forum!
The SEC actually has nothing to do with this as I am NOT dealing with
exchanges, buys or sells of shares or other financial securities....I've
dealt with the SEC enough times to know about what they do and
do not want to see when it comes to corporate dealings.
Any issues are PURELY Intellectual Property related and deal with
what IS and IS NOT considered proprietary and/or open source code.
And the BIGGEST elephant in the room is SOFTWARE PATENTS which
I have PURPOSEFULLY done much due diligence on and have TRIED
to avoid infringing on any patents from MPEG-LA and the major
audio-and-video-specific corporate giants. Since they have
DEEP POCKETS, it is best to AVOID a legal battle if I can.
I do suggest that with 2700 hours of legal deposition experience,
I ALSO think I might have a tad bit of experience in terms of
Canadian AND USA legal systems in terms of IP, securities, and
corporate law.
We are of course ACTIVELY COURTING the majors....
If Canon won't buy us, then Sony, Microsoft, Facebook,
Amazon or Google WILL !!! Even the notoriously secretive
and in-house-only Apple would take a look at something
this impressive technology-wise!
In terms of hardware, Intel, Samsung or Qualcomm
could EASILY put all our code on a CHIP since I wrote it
SPECIFICALLY in a RISC and CISC-instruction set friendly
manner allowing EVERY cell phone, tablet, laptop and camera
to have our fancy codec technology on a very attractive
royalty basis CHEAPER than MPEG-LA and MUCH, MUCH
MORE ADVANCED TECHNOLOGICALLY than HVEC/MP4
since we're charging on a SIMPLE PER CHIP and SIMPLE
PER-ENCODER-SOFTWARE APP basis!
And YUP! We turned around 180 degrees in terms
of being FREE cuz YES we found that YES we ARE
GREEDY and want a share of the world's money pie!
There's nothing wrong with wanting some money
for yourself and family! One must take advantage
of OPPORTUNITY if it presents itself EVEN IF one's
stated position must change in order to do so!
Some people won't do that but I AM !!!!
i.e. changing my position that is!
We shall see what happens in the next two weeks....
---
Anyways there IS A VERY DIFFERENT SURPRISE coming
your way, so keep watching ON THIS FORUM HERE in
the next 5 to 7 days to see what's up on that end!
It's a dooozy of a surprise !!!!!! ;-) ;-)
----
...AND...on another subject...
the recent patent filings by Canon having a VARIABLE
flange distance adapter bodes well on that NEW AND
LARGE APS-C sensor EF-S mount CANON SMARTPHONE
being almost ready !!!!!!!!
You heard THAT here FIRST and I found out that
the front-of-camera photo with the APS-C sensor
EF-S mount that I posted in another forum posting
is in FACT VERY VERY REAL on a WORKING in-the-wild
testing Canon Smartphone! The second photo showing
the rear smartphone screen was purported to be a mere
physical design mockup made for end-user hand-size
usage and button placement evaluation only.
Maybe you will see MY CODEC on that
Large Sensor Canon Smartphone...???
HarryFilm said:Actually, I do know that WHICH I WHY I changed that part of the code!
I went with direct hardware assembly on the SOBEL edge detection code...Since they have DEEP POCKETS, it is best to AVOID a legal battle if I can...We are of course ACTIVELY COURTING the majors....If Canon won't buy us, then Sony, Microsoft, Facebook, Amazon or Google WILL !!! Even the notoriously secretive and in-house-only Apple would take a look at something
this impressive technology-wise!
In terms of hardware, Intel, Samsung or Qualcomm could EASILY put all our code on a CHIP since I wrote it
SPECIFICALLY in a RISC and CISC-instruction set friendly manner allowing EVERY cell phone, tablet, laptop and camera to have our fancy codec technology on a very attractive royalty basis...
AND...on another subject...that NEW AND LARGE APS-C sensor EF-S mount CANON SMARTPHONE being almost ready !!!!!!!!
You heard THAT here FIRST and I found out that the front-of-camera photo with the APS-C sensor EF-S mount that I posted in another forum posting is in FACT VERY VERY REAL on a WORKING in-the-wildtesting Canon Smartphone! ...
...Maybe you will see MY CODEC on that Large Sensor Canon Smartphone...???
unfocused said:HarryFilm said:Actually, I do know that WHICH I WHY I changed that part of the code!
I went with direct hardware assembly on the SOBEL edge detection code...Since they have DEEP POCKETS, it is best to AVOID a legal battle if I can...We are of course ACTIVELY COURTING the majors....If Canon won't buy us, then Sony, Microsoft, Facebook, Amazon or Google WILL !!! Even the notoriously secretive and in-house-only Apple would take a look at something
this impressive technology-wise!
In terms of hardware, Intel, Samsung or Qualcomm could EASILY put all our code on a CHIP since I wrote it
SPECIFICALLY in a RISC and CISC-instruction set friendly manner allowing EVERY cell phone, tablet, laptop and camera to have our fancy codec technology on a very attractive royalty basis...
AND...on another subject...that NEW AND LARGE APS-C sensor EF-S mount CANON SMARTPHONE being almost ready !!!!!!!!
You heard THAT here FIRST and I found out that the front-of-camera photo with the APS-C sensor EF-S mount that I posted in another forum posting is in FACT VERY VERY REAL on a WORKING in-the-wildtesting Canon Smartphone! ...
...Maybe you will see MY CODEC on that Large Sensor Canon Smartphone...???
Oh Harry. You really need to fix this story line. It veers wildly from one topic to another and doesn't have any internal consistency. You need to read what you wrote back in November and note that what you said back then has little to nothing in common with what you are now saying.
You can't expect to hold the readers' attention when your story line is all over the board like this. You started out spinning a yarn about a codec for video and now you are selling this cinema software to chip manufacturers and cell phone companies?
And, while the large sensor cell phone camera is an entertaining diversion, it is so obviously ludicrous that it makes your "Harry" character seem ridiculously gullible. I understand that you have written yourself into a corner here. If you drop the cell phone camera story line, it's an admission that it was a poorly thought-out subplot. But, it does more damage to your main story line to double down on it.
If you want to keep the story going, you will need to start paring it down to the essentials.
One suggestion: You could say that while developing the video codec, you found that it entailed so much other coding and that it was so intertwined with other features, that you realized you were developing new solutions to any number of other issues and since those had to be resolved first to get your video codec working, you found yourself developing a number of new solutions to other issues and it is those offshoots that are the most marketable and intriguing to other industries. That's semi-plausible and might help get your "Harry" character back on track.
Fellow Forum Participants: "Harry" obviously needs help here. If you want to keep the story alive, please submit your own plot recommendations and story suggestions. Also, perhaps we should consider starting a new thread that creates a backstory or origin story for "Harry." Clearly the author is in over his head, but perhaps with all of our help, we can make "Harry" live on.
ethanz said:unfocused said:HarryFilm said:Actually, I do know that WHICH I WHY I changed that part of the code!
I went with direct hardware assembly on the SOBEL edge detection code...Since they have DEEP POCKETS, it is best to AVOID a legal battle if I can...We are of course ACTIVELY COURTING the majors....If Canon won't buy us, then Sony, Microsoft, Facebook, Amazon or Google WILL !!! Even the notoriously secretive and in-house-only Apple would take a look at something
this impressive technology-wise!
In terms of hardware, Intel, Samsung or Qualcomm could EASILY put all our code on a CHIP since I wrote it SPECIFICALLY in a RISC and CISC-instruction set friendly manner allowing EVERY cell phone, tablet, laptop and camera to have our fancy codec technology on a very attractive royalty basis...
AND...on another subject...that NEW AND LARGE APS-C sensor EF-S mount CANON SMARTPHONE being almost ready !!!!!!!!
You heard THAT here FIRST and I found out that the front-of-camera photo with the APS-C sensor EF-S mount that I posted in another forum posting is in FACT VERY VERY REAL on a WORKING now-in-the-wild-testing Canon Smartphone! ...
...Maybe you will see MY CODEC on that Large Sensor Canon Smartphone...???
Oh Harry. You really need to fix this story line. It veers wildly from one topic to another and doesn't have any internal consistency. You need to read what you wrote back in November and note that what you said back then has little to nothing in common with what you are now saying.
You can't expect to hold the readers' attention when your story line is all over the board like this. You started out spinning a yarn about a codec for video and now you are selling this cinema software to chip manufacturers and cell phone companies?
And, while the large sensor cell phone camera is an entertaining diversion, it is so obviously ludicrous that it makes your "Harry" character seem ridiculously gullible. I understand that you have written yourself into a corner here. If you drop the cell phone camera story line, it's an admission that it was a poorly thought-out subplot. But, it does more damage to your main story line to double down on it.
If you want to keep the story going, you will need to start paring it down to the essentials.
One suggestion: You could say that while developing the video codec, you found that it entailed so much other coding and that it was so intertwined with other features, that you realized you were developing new solutions to any number of other issues and since those had to be resolved first to get your video codec working, you found yourself developing a number of new solutions to other issues and it is those offshoots that are the most marketable and intriguing to other industries. That's semi-plausible and might help get your "Harry" character back on track.
Fellow Forum Participants: "Harry" obviously needs help here. If you want to keep the story alive, please submit your own plot recommendations and story suggestions. Also, perhaps we should consider starting a new thread that creates a backstory or origin story for "Harry." Clearly the author is in over his head, but perhaps with all of our help, we can make "Harry" live on.
Harry, it looks like you may have to start hiring some employees! We could make this thing really go off with a bang with all the knowledgeable people on CR.
zim said:So basically one of those big bad ass corporates will buy the codec for mucho mulla, bury it of course and our hero Harry will be seen flying off into the sun set sticking it up to the great unwashed here at CR central. :-*
GuyF said:Spoiler Alert!
As we approach the season finale, our hero finds himself being attacked from every side. Naysayers and trolls goad and mock in an unrelenting assault on plucky Harry. In next week's episode 24 cliffhanger we'll meet a shady lady from Bogota who steals the code, leaving just a broken lipstick as a clue to her identity. What can it mean? Will our gung-ho programmer be able to add a flight-sim easter egg into the code before the beta is released and will he find an antidote to the hallucinogenic mushroom pizza topping that he may have ingested?
Blu ray extras: blooper reel, director's commentary.