adding VSSH fourcc support to coreavc [Archive]

View Full Version : adding VSSH fourcc support to coreavc

Koti

11th January 2006, 17:42

Could the 4cc "VSSH" be added as its a x264 vfw option.

Ty

Sirber

11th January 2006, 18:11

@Koti

Why?

Koti

11th January 2006, 18:38

Cause I have a pile of mkv's and avi's made in vfw and I really dont want to remux all of them to native or change the 4cc ( I used "VSSH" as it was the most agreeable in avi and mkv to nero decoder )

Thats why ;)

( and plz no vfw , avi bashing ty :) )

Sharktooth

11th January 2006, 19:57

[)370|\|470!2

11th January 2006, 20:47

Writing code to help you playback something coz you just encoded things the wrong way is not acceptable.

LOL? Took me exactly 2 mins of hexediting and re/registering it, to enable VSSH instead of H264/x264.

Yes, VFW and AVI are EVIL.

:D :logfile: ;)

Sharktooth

11th January 2006, 21:14

Detonator, well, good for you.
Still it's the idea of supporting the bad encodes that's completely wrong and i dont think picard or the other devs would be happy of what you did... as you can see the source is closed...

:D :logfile: ;)
What about of learning to :search: instead of an hex editor?

P.S.:2 minutes!?!? isnt it a bit too much for a "find & replace"?

[)370|\|470!2

11th January 2006, 21:38

What about of learning to :search: instead of an hex editor?

I did :D similar opinion (http://forum.doom9.org/showthread.php?p=741622#post741622)

P.S.:2 minutes!?!? isnt it a bit too much for a "find & replace"?

Ok, forgot to mention that it also includes modifying 4cc in video for testing xD

Sharktooth

11th January 2006, 21:48

Well, if you had used the search function you would have found b.frames are not compatible with AVI and VFW (they were hacked but it has major drawbacks for editing and there are also lost frames...), also multiple reference frames could be another problem, the AVI massive overhead is not a wanted "feature" for who looks for the best compression, etc.
So, spend some time to read and learn instead of doing the pseudo-hacker.

PS:Ok, forgot to mention that it also includes modifying 4cc in video for testing xD
it's still too much:p

Sirber

11th January 2006, 22:39

flamewar!!! :devil:

also you are polluting this thread :sly:

[)370|\|470!2

11th January 2006, 22:50

Sharktooth

Ahem, i've never pretended to be a hacker, especially "pseudo" :)
It was your argument, that adding support for VSSH is a quite piece of coding.

Conserning avi... ok, i'm well aware of all its cons. But you forgot to mention a main
disadvantage of other containers: far less compatibility & flexibility. While an avi
you could convert virtually to anything you like with ease, when it comes to
mp4 or even mkv, here all problems arising. And btw, an opendml avi with
low overhead will be something similar in size to both mkv and mp4.

Tv stations still using field interlacing technology, while it was introduced in 1920
(iirc) and it's basically obsolete. Correct me if i'm wrong.

So the point is: there's no perfect container yet :D so when claiming something
is "evil" is way too far subjective.

videomixer9

11th January 2006, 22:57

only ppl i know that still are totally in love with avi are those that made their mistake of their live by buying standalone mpeg4 players from companies that have no clue about modern media coding, as you see with media itself still using those ancient technologies as long as possible. Of course there's those ppl too that simply refuse to install any software really if it not advertised by some l33t company. Make a million dollar ad campaign for Matroska and ppl would all follow you blindly and install what is neccessary, just associate it with some l33t company.

dragongodz

12th January 2006, 02:27

VFW and AVI are EVIL.
can somebody shoot the next person to post that ? ;)

Still it's the idea of supporting the bad encodes
how is it a bad encode ? what because [)370|\|470!2 said the nero decoder was "more agreeable" with that 4cc ? that doesnt mean its out of sync or corrupt etc etc etc or doesnt play perfectly fine with any other decoder. if it plays fine and he is happy with it then its really not up to anybody else to call it bad.

listen to the reccomendations of ppl that have more experience than you.
theres a difference between a reccomendation and the pushing of "this is EVIL" that seems to be infecting threads recently.

Writing code to help you playback something coz you just encoded things the wrong way is not acceptable.
of course the programmers dont have to add or support whatever they dont want. to call his request for support of an additional 4cc "the wrong way" though incorrect.

also you are polluting this thread
:goodpost: none of this needed to be in this thread.

Koti

12th January 2006, 05:23

That's coz you did things in your way...
Next time DO NOT USE VFW OR AVI if you dont want problems.
Writing code to help you playback something coz you just encoded things the wrong way is not acceptable.
Next time :readfaq: :search: and, above all things, listen to the reccomendations of ppl that have more experience than you.

Repeat with me:
"This is my way, not the army way".

Everytime you use Vdub(mod), AVI, MKV in VFW mode, VFW and x264 repeat that phrase...

Yes, VFW and AVI are EVIL.

Was this really neccesary ? these encodes were made before x264 Cli Gui's were out using Sex264 that syskin released (recall vfw and GK did give x264 alot of initial exposure ) - All I asked was a simple request not a speech about experience and native storage.

Ps , Ya I have a clue about native storage and the limitations of vfw and encode avc outside of vfw since it was reasonably possible. Also I didn't intened to or ever join the army ;) .

Sorry to all for my simple request - yes I added in hex edit too but thought others may find this helpful , it was not all about me .

Have a great day :) , Surf's Up ;)

Doom9

12th January 2006, 09:23

Was this really neccesary ? these encodes were made before x264 Cli Gui's were out using Sex264 that syskin releasedActually... MeGUI was released on the 3rd of January 2005, sex264 on the 5th of January 2005. I just can't let stand if somebody tries to rewrite history. For your reference, here's the backup of that: MeGUI announcement (http://forum.doom9.org/showthread.php?t=87567&highlight=megui) and sex264 announcement (http://forum.doom9.org/showthread.php?t=88095&highlight=Sex264)

Koti

12th January 2006, 16:09

Actually... MeGUI was released on the 3rd of January 2005, sex264 on the 5th of January 2005.

I stand corrected.