Modification of huffyuv codec for YV12?

[Sigmatador]

@MF
i did exactly what you did except my avs script resized the source in 640x272 (from original 1000x540) and i get no artefact.

[bkam]

Just wanted to thank you a ton... I started capturing only last week, and it is so convenient to be able to adapt what I know of encoding from DVDs to capture since now the colorspace is the same. With HuffYUV I was relearning everything and unable to use my YV12 filters (I guess i could have converted, but that's really slow, right? never tried). Also, the first time I used this one I got about maybe 300 frame drops for a 30 minute cap, the second time I messed with some windows settings and got ZERO. Awesome. Great codec, keep up the good work.

[BoNz1]

Well, it seems the attachments are down and I don't want to bother anybody. But, I just recently formatted my computer and I would like to have this modification of huffyuv again but I can't seem to find any mirrors or anything of it anywhere. marcfd doesn't seem to have it on his site either. Maybe someone would be kind enough to find a mirror for me or possibly even mirror it for me. At any rate, I would be very grateful. Thanks in advance.

[Acaila]

This (http://forum.doom9.org/showthread.php?s=&threadid=53305&highlight=loco) thread has the codec attached as well.

[BoNz1]

Thank you very much Acaila. :)

[SILICON]

Y'm look around for lostless codes for YUV12.
I found :

loco004 by TheRealMoh:
http://forum.doom9.org/attachment.php?s=&postid=312334

VBLE by ????
http://www.cc.jyu.fi/~camneely/vble_video_codec.zip

I read about Mark_fd HuffYUV, but i don´t see any link.

Cand anybody post links for Mark_fd HuffYUV and another codecs?

Thanks a lot.

[Wilbert]

VBLE = Mark_fd HuffYUV

The other links can be found at:

http://www.avisynth.org/index.php?page=Section+1%3A+About+AviSynth#q1.26

and

http://forum.doom9.org/showthread.php?s=&threadid=53305&highlight=VBLE

[Marc FD]

hi,

i played with huffyuv some days ago, i added some yv12 support, tried to add new tables and maybe other stuff (prefiltering for near lossless encoding), if you want to test some alpha stuff (bin only) i can post the stuff here.

[sh0dan]

@Marc FD: Sorry - no exceptions - source HAS to be supplied - otherwise you are violating GPL. Source must be downloadable "from the same place" as the binary - it's in the GPL. I hope you still find it worth the efford to release it!

[Boulder]

And while you're at it, you could consider releasing the sources of your other filters too (if they are GPL). Some people have had problems with some of your filters and the sources would help the other experienced coders to figure out what's causing the issues.

[Marc FD]

lol, no pb i will simply keep it here then :/

i've exams and no time to clean the code, and i hate to release dirty code... that's how i am.

and for my filters, they are not GPL until i'll release the source (under GPL) that's as simple as that.

i've not enough time to code, so i'm not gonna spend time on that stuff ^^;

for huffyuv my work was mean as clean as possible (okay looks like a hack on some aspects ^^) and it was pretty easy to do, so i think i'll release with code when i would have finished beta-testing, it's sad that the guy who did it is gone, i would prefer to give him the code directly. btw i don't think it's compatible at all with ffmpeg's yv12 huffyuv, but it seemed the faster and simple way to implement it :]

bye,
marc

[mf]

Originally posted by Marc FD
i've exams and no time to clean the code, and i hate to release dirty code... that's how i am.

and for my filters, they are not GPL until i'll release the source (under GPL) that's as simple as that.
Dirty code is at least code. If it's out there it's just so much more social for ppl who're having problems with it. I am working on a player mimicking Sasami2K (http://www.sasami2k.com) (planning stage, see my sig :D), because the original has bugs, the author disappeared (has no time for coding anymore because he has a job), and no source was ever released :(. Luckily there is MPC to use as a basis, but still there is going to be some duplicate work. Please consider this, nobody cares about how messy your code is, if ppl want to work on it then they'll accept that. And I think that's a pretty big compliment to a coder.

[Si]

@MarcFD
While people are actively developing GPL code, others don't mind if the source is withheld for a short while although this is against the GPL.

But if a GPL binary is not being actively developed then the GPL source code should be released no matter what the state.

Its how we got to the current position with all the GPL programs available (such as Avisynth itself).

Your only choices are to follow the copyright you agreed to when you released your modfied Huffyuv codec or to violate it.

regards

Simon

[outlyer]

Originally posted by siwalters
@MarcFD
While people are actively developing GPL code, others don't mind if the source is withheld for a short while although this is against the GPL.

But if a GPL binary is not being actively developed then the GPL source code should be released no matter what the state.

Its how we got to the current position with all the GPL programs available (such as Avisynth itself).

Your only choices are to follow the copyright you agreed to when you released your modfied Huffyuv codec or to violate it.

This doesn't seems totally correct reading the FAQs at gnu's site.
As I understood it, you don't need to publish the code as long as you're using it privately so, at the initial development stages, even if it gets stalled, there's no need to publish it.

Of course, if he abandons development, it would be nice to publish the code.

[Si]

As I understood it, you don't need to publish the code as long as you're using it privately so, at the initial development stages, even if it gets stalled, there's no need to publish it.

Agreed.

My comments only apply to published binaries derived from GPL works.

regards
Simon

[MfA]

Originally posted by Marc FD
and for my filters, they are not GPL until i'll release the source (under GPL) that's as simple as that.

So we have an implicit license to incorporate any and all of your code in closed source programs then? :) Anything else would be hypocritical now.

[sh0dan]

Stop this off-topic discussion now! If any software is announced here, that violates any licenses it is in violation of rule 6, and will be treated as such. If you need to discuss moral issues, do it in the general disussion forum!

[Longinus]

I'm having a strange BUG using VBLE. I looked around for any msgs talking about it, but I didn't find any... so I'm posting this..

I'm getting a very strange yellow vertical bar (about 1 pixel long) in the left side of the video. This happens only when I open it in virtualdub. Playing in MP is normal. Some video programs show a white bar, instead of yellow (combustion 2).

Another thing that helps is using an Avisynth script to convert to yuv2 or rgb. But this is probably time-consuming and reduces quality.

I've checked in VirtualDub, and it is using the right decoder, VBLE, so what can it be?

Thanks.

[Kurosu]

That's a very well-known bug in XviD YV12->RGB conversion. You see the line, but it isn't actually there in the raw (YV12) data: if you crop on the left, it will still be there! I think it was fixed, and only available in newest "alpha" builds (less than 2 weeks) of XviD. Or maybe it still isn't yet available. In the end, that's not a problem with VBLE. (Very Buggy/Beta Lossless Encoder? :D)

Offtopic, the more and more I read this thread, the more I think it would fit more in the "New A/V codecs" forums (seeing how VBLE is refered to by pointing at this thread).

[Koepi]

My latest XviD build (26062003-1) incorporates sysKin's fix of the color space conversion. Download & install it, the yellow line will be gone.

Regards
Koepi

[AmiRage]

Originally posted by Koepi
My latest XviD build (26062003-1) incorporates sysKin's fix of the color space conversion. Download & install it, the yellow line will be gone.
You mean 24062003-1? Or where can I find this newer build?

[Koepi]

Sorry, of course i typed wrong there. XviD-24062003-1.exe is my latest build.

Regards
Koepi

[Longinus]

Yep, this helps. Thanks!!

This post, is somewhat off-topic, like kuroso said... But I didn't find anywhere else to ask VBLE questions.

By the way, VBLE is a nice codec. I was using huffyuv to save some rendered 3D animation. But with vble I get the almost exact quality (a little bit darker), and sometimes half the size of Huffyuv. Thanks for it Marc.

[maciek_m]

Same impressions like Longinus. Good job

However, is there a newer version of VBLE (the beta version I downloded has been out for several months now).

And, perhaps a newbie's, problem:
I can't access the config option when selecting this codec in VDub(Mod) in capture mode.

VDub does not let me set the YV12 4:2:0 in the "set custom format". So I have to use YUY2 4:2:2.

Perhaps it has something to do with my capture device Radeon 9000 VIVO?

[Wilbert]

However, is there a newer version of VBLE (the beta version I downloded has been out for several months now).
Nope. The coder is gone, and the source is not available :(

VDub does not let me set the YV12 4:2:0 in the "set custom format". So I have to use YUY2 4:2:2.
You don't want to capture in YV12 with vble anyway, since it has no interlace option. Meaning it assumes YV12 progressive, and you will get chroma upsampling artefacts.

btw, it implies that your capture card can't do the yuy2->yv12 conversion, and hence can't output yv12.

[bill_baroud]

Originally posted by Wilbert
Nope. The coder is gone, and the source is not available :(


i think he's still lurking around here (http://atlas2.tgv.net/~media-video/forum2/portal.php)

dunno if he's still coding or anything, but he could perhaps release the source code :)

[mf]

I guess he'll just use the age-old excuse that his code is too dirty or whatnot to release it. Afaik he's only released the source to 2 of all his filters, so I wouldn't really count on it. Quite unnecessary, cause his filters are quite great actually (oxymoron? quite = relative, great = absolute), and the sourcecode can't be too bad.