Welcome to Doom9's Forum, THE in-place to be for everyone interested in DVD conversion. Before you start posting please read the forum rules. By posting to this forum you agree to abide by the rules. |
20th September 2006, 03:02 | #21 | Link |
easily bamboozled user
Join Date: Sep 2002
Location: Atlanta
Posts: 373
|
I would never have imagined something could be wrong with that, but it seems you're right. A ConvertToRGB32() at the end fixes it. I first noticed it when the Crop came before some filters, so I assumed the chroma shifting was happening at the Crop.
The width was mod 4 (which I'm pretty sure has always been fine for raw YV12 before), but if I replace what I posted with Crop(4,58,0,-60,align=true), the chroma shifting isn't there anymore. What could possibly be wrong with my YV12 codec, and how might it have happened? edit: Nevermind, the chroma shifting IS still there with Crop(4,58,0,-60,align=true), but the effect is much smaller. That doesn't make the problem not confusing as hell, though. Some kind of pitch error I guess. My memory might be bad, but I'm certain I've looked at scripts with mod 4 width before in VD without problems. Last edited by Prettz; 20th September 2006 at 03:13. |
21st September 2006, 04:05 | #22 | Link |
Avisynth Developer
Join Date: Jan 2003
Location: Melbourne, Australia
Posts: 3,167
|
@Prettz,
In VDub make sure Options/Preferences/AVI/"Directly Decode YCbCr (YUV) Sources" is turned on. The YV12 to RGB converter in some DivX and XviD version is known to require mod 8 or even 16 width to work correctly. |
21st September 2006, 18:48 | #25 | Link | |
easily bamboozled user
Join Date: Sep 2002
Location: Atlanta
Posts: 373
|
Quote:
I know Xvid installs a YV12 codec; doesn't Avisynth install one as well? |
|
21st September 2006, 19:31 | #27 | Link |
AviSynth plugger
Join Date: Nov 2003
Location: Russia
Posts: 2,183
|
you can become this member
__________________
My Avisynth plugins are now at http://avisynth.org.ru and mirror at http://avisynth.nl/users/fizick I usually do not provide a technical support in private messages. |
22nd September 2006, 02:47 | #30 | Link | |
Moderator
Join Date: Feb 2005
Location: Spain
Posts: 6,915
|
Quote:
DirectShowSource(), with ffdshow, accept audio streams of type WAVE_FORMAT_IEEE_FLOAT in v2.5.6. And also with header WAVE_FORMAT_EXTENSIBLE. WavSource() accept audio streams of type WAVE_FORMAT_IEEE_FLOAT in 2.5.7 Btw, what is the problem to accept WAVE_FORMAT_EXTENSIBLE? |
|
22nd September 2006, 06:23 | #31 | Link |
Avisynth Developer
Join Date: Jan 2003
Location: Melbourne, Australia
Posts: 3,167
|
@tebasuna51,
Yes it should be "... accept raw audio streams ..." I am not aware of problems accepting WAVE_FORMAT_EXTENSIBLE please elaborate. This stuff is difficult to test due to the lack of stable sources of data to test against, so simple examples of faults with a logfile are very helpfull. |
23rd September 2006, 00:32 | #32 | Link | |
Moderator
Join Date: Feb 2005
Location: Spain
Posts: 6,915
|
Quote:
Code:
Starting job 16_in_ex.wav->16_in_ex_.wav Error: BeHappy.AviSynthException: No compatible ACM codec to decode 0xFFFE audio stream to PCM. at BeHappy.AviSynthClip..ctor(String func, String arg, AviSynthColorspace forceColorspace, AviSynthScriptEnvironment env) at BeHappy.Encoder.encode() Also Bepipe don't work but the error message is less sophisticated: Code:
bepipe --script "WavSource(^D:\16_in_ex.wav^)" > output.wav ... ERROR: Can't find audio stream! |
|
23rd September 2006, 11:11 | #33 | Link |
Errant Knight
Join Date: Oct 2004
Location: St Louis, M0 US
Posts: 364
|
@tebasuna51
you asked, "Btw, what is the problem to accept WAVE_FORMAT_EXTENSIBLE?" Code:
0x0001 WAVE_FORMAT_PCM PCM 0x0003 WAVE_FORMAT_IEEE_FLOAT IEEE float 0x0006 WAVE_FORMAT_ALAW 8-bit ITU-T G.711 A-law 0x0007 WAVE_FORMAT_MULAW 8-bit ITU-T G.711 µ-law 0xFFFE WAVE_FORMAT_EXTENSIBLE Determined by SubFormat WAVE_FORMAT_IEEE_FLOAT, is a valid format outside of WAVE_FORMAT_EXTENSIBLE.Hope that helps. |
23rd September 2006, 11:57 | #34 | Link |
Registered User
Join Date: Dec 2004
Location: Melbourne, AU
Posts: 1,963
|
I can think of one problem: it's always possible to convert a wFormatTag to a Subformat GUID, but not the other way around. So I'm not sure how you'd go about handling a GUID which didn't convert easily to a corresponding wFormatTag, without some sort of look-up table for known types (for instance there's about half a dozen different GUID definitions for AC3, while most acm codecs which support AC3 via waveformatex use wFormatTag 0x2000).
|
23rd September 2006, 15:20 | #36 | Link |
Registered User
Join Date: Dec 2004
Location: Melbourne, AU
Posts: 1,963
|
My point was it's not just as simple as saying, "Oh it's a WAVE_FORMAT_EXTENSIBLE structure, I'll just convert the SubFormat GUID to a wFormatTag and go looking for an ACM codec to handle it..." since it's not always possible to get a wFormatTag from a GUID. In some cases it's possible, but not always.
|
23rd September 2006, 18:53 | #38 | Link | |
Moderator
Join Date: Feb 2005
Location: Spain
Posts: 6,915
|
Quote:
Code:
KSDATAFORMAT_SUBTYPE_PCM 00000001-0000-0010-8000-00aa00389b71 KSDATAFORMAT_SUBTYPE_IEEE_FLOAT 00000003-0000-0010-8000-00aa00389b71 KSDATAFORMAT_SUBTYPE_DRM 00000009-0000-0010-8000-00aa00389b71 KSDATAFORMAT_SUBTYPE_ALAW 00000006-0000-0010-8000-00aa00389b71 KSDATAFORMAT_SUBTYPE_MULAW 00000007-0000-0010-8000-00aa00389b71 KSDATAFORMAT_SUBTYPE_ADPCM 00000002-0000-0010-8000-00aa00389b71 KSDATAFORMAT_SUBTYPE_MPEG 00000050-0000-0010-8000-00aa00389b71 But if SubFormat is unknown inside AviSource-WavSource we can do nothing. Thanks. Edit: If we have access to wav header is really easy (if we plan reject anything than PCM or FLOAT) change wFormatTag for this first two bytes of SubFormat. Is used in Aften. Last edited by tebasuna51; 23rd September 2006 at 19:04. |
|
23rd September 2006, 20:42 | #39 | Link |
Errant Knight
Join Date: Oct 2004
Location: St Louis, M0 US
Posts: 364
|
@ tebasuna51,
I am, again, sorry. You may call a pig a cow, but I may not understand. Others will not either. I didn't mean to suggest that you didn't know your way around the data types, especially the really big ones. My suggestion is that you did not understand why AviSynth(WavSource()) would load WAVE_FORMAT_IEEE_FLOAT and not load WAVE_FORMAT_EXTENSIBLE. Again I am assuming that your asking a question and you would like the answer. Sorry I has incorrect. done. |
24th September 2006, 22:57 | #40 | Link |
AviSynth plugger
Join Date: Nov 2003
Location: Russia
Posts: 2,183
|
It seems, there is some bug in Avisynth smart cache impementation,
see MVTools thread http://forum.doom9.org/showthread.ph...682#post867682 I discovered, that backward and forward vectors clips sometimes swapped after 12 frames. Version 2.5.5 and v2.5.6beta3 (with not smart cache) works fine with MVDenoise. I try to find workaround with some SetCacheHints, but some problem still exists. Also I remember similar problem with Restore24. |
Thread Tools | Search this Thread |
Display Modes | |
|
|