View Full Version : March 6th 2.50 beta
sh0dan
6th March 2003, 16:23
Just uploaded a new test version. Follow the second link in my sig.
This is candidate for 2.51. Changes since last CVS version (feb 27):
- Fixed bug in YV12 stackvertical, causing corrupt images.
- Removed all fieldbased/mod 4 checks.
- Restored how fieldbased/framebased works (needs further testing!)
- Added MMX/ISSE version of YUY2 -> YV12 conversion routines (interlaced/progressive). Use converttoyv12(interlaced=true/false).
- Made SwapUV() faster.
- YToUV() now takes an optional third parameter, that contains luma for the final clip.
- Fixed memory exception problem in Blur()
- AudioLength() now returns the size in samples (do however beware of overflows on very long clips)
- Changed chroma weighing to be 25/75 on interlaced YV12 -> YUY2
- Removed startup Box from installer.
- Enabled Steady's much faster BitBlt code.
- Finally: Greyscale inserts value 128, instead of 127. Some users have reported a greenish tint.
Field/Framebased processing should in theory be back to 2.0 functionality. Please report if you find strangeness. If no major bugs are found, this version will be released as 2.5.1 (at the same time as 2.0.8)
Wilbert
6th March 2003, 16:57
Nice! Sh0dan, do you know how this ImageWriter works?
sh0dan
6th March 2003, 17:17
No - you'd have to ask Richard about that - but I think it isn't finished yet, so it's not official a feature yet :)
Richard Berg
6th March 2003, 23:06
Originally posted by Wilbert
Nice! Sh0dan, do you know how this ImageWriter works?
I'll start a thread in the developer forum.
philippas
7th March 2003, 08:07
I had tried avisynth 2.5 a couple of days ago in YUY2 source from a Tv-Capture and the clip was incorrectly recognised as YUV12. Is this fixed in this release?
kilg0r3
7th March 2003, 10:07
can't find the binary at sourceforge
Wilbert
7th March 2003, 10:34
That's because the binaries are not located at sourceforge, but on Sh0dan's homepage.
I had tried avisynth 2.5 a couple of days ago in YUY2 source from a Tv-Capture and the clip was incorrectly recognised as YV12. Is this fixed in this release?
I'm not entirely sure whether AviSource converts them automatically to YV12. But you can always use: AviSource(..., "YUY2")
kilg0r3
7th March 2003, 10:50
Originally posted by Wilbert
That's because the binaries are not located at sourceforge, but on Sh0dan's homepage.
which is located @ ....? :)
Sorry i have only two addresses; the sourceforge-page and the avisynth-alpha page.
Wilbert
7th March 2003, 11:09
Sorry i have only two addresses; the sourceforge-page and the avisynth-alpha page.
The second one (in the sig. of Sh0dan):
Binaries.
Download
Avisynth 2.50 (Mar 6. 2003)
@Richard,
Something changed on http://www.avisynth.org/forum/:
If I try to look into "Core Development section" I got the message: Sorry, but only moderators can read topics in this forum. (I can view the thread in the plugin dev. section.)
sh0dan
7th March 2003, 13:30
@philippas: If you haven't reported it, it probably isn't. Which codec are you using?
unplugged
8th March 2003, 00:53
- Changed chroma weighing to be 25/75 on interlaced YV12 -> YUY2
BTW,
I believe that interlaced YV12 to YUY2 conversion in Avisynth 20030306 is not perfect yet, I have made some comparisons (using PAL interlaced MPEG2 movie) between MarcFD's YV12toYUY2(interlaced=true) and ConvertToYUY2(interlaced=true) and it appears to me the avisynth internal routine misses sometimes chroma values (certain areas/lines at all), there are quite suspicious grey lines that would have been colored for sure.
1st.AVS (2.5)
LoadPlugin("c:\App\Media\Avisynth\MPEG2Dec3.DLL")
LoadPlugin("c:\App\Media\Avisynth\MPEGDecoderYV12.DLL")
mpegsource("e:\Spaceballs\space.d2v") # Nic's latest 2.03a routine
YV12toYUY2(interlaced=true) # MarcFD's convertion routine by MPEG2DEC3.DLL
ResampleAudio(44100)
2nd.AVS (2.5)
LoadPlugin("c:\App\Media\Avisynth\MPEGDecoderYV12.DLL")
mpegsource("e:\Spaceballs\space.d2v") # Nic's latest 2.03a routine
ConvertToYUY2(interlaced=true)
ResampleAudio(44100)
P.S.: despite the movie itself is 25fps progressive, the mastering MPEG2 structure is interlaced (as report DVD2AVI and BitrateViewer), plus certains isolated frames are also combed (and I used them to better test YV12->YUY2 line convertions).
sh0dan
8th March 2003, 01:51
@unplugged: Yes - there does seem to be a problem. Thanks for reporting! (I also noticed some flickering pixels at the bottom - that should also be investigated)
Richard Berg
8th March 2003, 06:46
@Wilbert - I closed the avisynth.org forum when I saw the new AVS Dev forum here. I left an announcement there, but I suppose it's no use if you can't see it :o (I'll go change that) Meantime, I think all the affected people are aware of the new forum already, hopefully no harm done.
philippas
9th March 2003, 16:25
@sh0dan
The source was captured with xvid with the interlaced option selected. If i remember correctly,it was recognised as divx5 YV12 but when i opened it directly from virtualdub it was recognised correctly. I'll try and reproduce it with the latest build of xvid and also with the stable one.
Thanks for looking into it.
sh0dan
9th March 2003, 18:26
@philippas: MPEG 4 (as used by XViD) is YV12. So when you hand YUY2 data to XviD from your capture application it is converted to YV12. This is why it is delivered to AviSynth as YV12.
sh0dan
9th March 2003, 20:47
@unplugged: Would you mind trying the latest CVS binary (march 9.). The issues should be fixed!
Changes since March 6:
- Fixed 4 flickering pixels in ConvertToYUY2, and potential out-of-buffer writes.
- Fixed chroma weighing in interlaced yv12 -> yuy2.
- Added ApplyRange(clip, int startframe, int endframe, String "filter", filterargs)
- Aligned Resize data (slightly faster on some setups).
Any other major issues before the official 2.5.1?
philippas
9th March 2003, 23:23
@sh0dan
Sorry my fault, you are right.
Wilbert
10th March 2003, 10:16
Any other major issues before the official 2.5.1?
A minor one, yesterday I tried
clip.Trim(0,-1) # clip was an xvid clip
which resulted in/reported two frames in Virtualdub instead of one.
jarthel
10th March 2003, 10:43
Let me just say that I'm glad I've made the switch to Avisynth2.5. I really can't discern the difference between Avisynth 2 and 2.5 but I know it's faster.
I'm using Xvid as the encoder.
jayel
sh0dan
10th March 2003, 11:54
@Wilbert: <sigh> Won't we ever get that one right. How many frames do you end up with, if you add Loop(50) ?
@jarthel: Thanks for the positive words! Are you usign VDdubMod?
jarthel
10th March 2003, 12:08
Originally posted by sh0dan
@jarthel: Thanks for the positive words! Are you usign VDdubMod?
Well the positive words are justified seeing how much better 2.5 is over 2.07.
I'm using latest vdubmod with latest .exe. I wish they (Belgabor and group) release vdubmod based on vdub1.5.1. :)
Jayel
Artur
10th March 2003, 13:18
Nice!!
Schlumpf
10th March 2003, 17:11
Newest Avisynth gives me an access violation, when I try to use SwapUV().
Tested with VirtualDubMod on 3 files (Mjpeg,VBLE and Divx).
sh0dan
10th March 2003, 18:36
Confirmed, fixed, new binary up, Thanks!
unplugged
11th March 2003, 00:41
Tested some screenshots with AVS 10/03, well interlacing up-sampling works well (no artifacts) and if my eyes don't fail much it seems pixel to pixel corresponding to MarcFD's routine.
Ummm... reading changelog... and now I'm happy for speed improvements too! :)
Avisynth is going to become very powerful, sh0dan!
love "particular" combinations like
AVS 2.5 -> MPEGDecoder.DLL -> ConvertToYUY2 -> CCE! :p
P.S.: ah, forgot... and a machine with plenty RAM bandwidth :D
Wilbert
11th March 2003, 09:53
@Wilbert: <sigh> Won't we ever get that one right. How many frames do you end up with, if you add Loop(50) ?
Trim(0,-1) --> 2 frames
Trim(0,-1).Loop(50) --> 100 frames
Trim(0,-n) (n positive) --> n+1 frames
I notices another peculiar thing. When I reopen my avs files (containing only
AviSource(some xvid clip)
in VirtualdubMod (or Virtualdub) it closes itself without any warning. I will try it with other scripts.
# I used the binaries of 03-06-'03
litz
17th March 2003, 23:54
Originally posted by unplugged
Avisynth is going to become very powerful, sh0dan!
love "particular" combinations like
AVS 2.5 -> MPEGDecoder.DLL -> ConvertToYUY2 -> CCE! :p
P.S.: ah, forgot... and a machine with plenty RAM bandwidth :D [/B]
I can only second this : I'm using that *exact* combination to crunch HDTV to DVD all in YV12 space, until it's YUY2'd for CCE at the end of the avisynth.
toss the .ts into dvd2avi. toss the .d2v into the .avs, decomb it, resize it, encode it. Doesn't get simpler than that.
VERY VERY slick !
:)
- litz
vBulletin® v3.8.11, Copyright ©2000-2026, vBulletin Solutions Inc.