Welcome Guest ( Log In | Register )


Important

The forums will be closing permanently the weekend of March 15th. Please see the notice in the announcements forum for details.

Pages: (5) 1 [2] 3 4 ... Last » ( Go to first unread post )
0055 The Problem That Wont Go Away., compression: (unknown tag 0055)
« Next Oldest | Next Newest » Track this topic | Email this topic | Print this topic
Belial
Posted: Nov 7 2005, 04:48 PM


Advanced Member


Group: Members
Posts: 402
Member No.: 6667
Joined: 8-October 03



There's a few things to try.One,just d/l wmp10,then unpack,and copy the l3codecp.acm to system32 folder(I did this on win2k,and it works fine).Second,sometimes files need to be demuxed(direct stream processing only),then remuxed to work properly.Also,you can try tmpgenc to save/recompress the wave or whole file(File,output to file).
 
     Top
farcus
Posted: Nov 8 2005, 03:08 AM


Unregistered









I recently cleaned out my system of all excess codecs and installed wmplayer 10. This put your suggested file in my system32 folder. However, it has not helped with the problem.

You are right about using tmpgenc. It works fine but is significanlty slower than virtualdub - particularly when downcoverting the sample rate.

still looking for a solution here??
 
  Top
banny69
Posted: Nov 11 2005, 07:28 PM


Unregistered









Farcus, I too have this problem and I agree with you comments re nandub.

I have installed/deinstalled/reinstalled the 'missing' codec to no avail.

I have, according to gspot, 5 codecs that can handle the audio, but still it won't work.

I will keep searching and post a solution here if I ever find it!

Banny
 
  Top
Belial
Posted: Nov 11 2005, 09:13 PM


Advanced Member


Group: Members
Posts: 402
Member No.: 6667
Joined: 8-October 03



Have you tried virtualdubmod to demux the audio,without converting?Then you can use another app to convert the audio.
 
     Top
farcus
Posted: Nov 12 2005, 01:33 AM


Unregistered









QUOTE (Belial @ Nov 12 2005, 06:13 AM)
Have you tried virtualdubmod to demux the audio,without converting?Then you can use another app to convert the audio.

Yes, of course this works ok.
Directshow mp3 codecs will let the file be converted/accessed but the acm codec that virtualdub uses will not.
Demuxing and then using besweet or something else works just fine.

Also, TMPGEnc will let you seperate the audio out from the avi as it uses the directshow codec and not the acm codec - but TMPGEnc is very slow at changing the sample rate.

It really would be nice to find what the problem is and a solution within virtualdub / codecs etc though.
 
  Top
squid_80
Posted: Nov 12 2005, 05:58 AM


Advanced Member


Group: Members
Posts: 594
Member No.: 13813
Joined: 22-January 05



I actually had this happen for the first time ever today with an avi file given to me. Opened it in virtualdub, got the message about a VBR audio stream, went to file information to check compression: Unknown (tag 0055). So I opened the file in virtualdub's hex editor to check the WAVEFORMATEX header and wBitsPerSample was 16, which seemed odd for a compressed format. I changed it to 00 and now the Fraunhofer codec accepts it and everything works.
 
     Top
farcus
Posted: Nov 12 2005, 12:06 PM


Unregistered









QUOTE (squid_80 @ Nov 12 2005, 02:58 PM)
I actually had this happen for the first time ever today with an avi file given to me. Opened it in virtualdub, got the message about a VBR audio stream, went to file information to check compression: Unknown (tag 0055). So I opened the file in virtualdub's hex editor to check the WAVEFORMATEX header and wBitsPerSample was 16, which seemed odd for a compressed format. I changed it to 00 and now the Fraunhofer codec accepts it and everything works.

could you explain how you found WAVEFORMATEX wBitsPerSample using the hexeditor.
I opened up one of my files in the hex editor but wasn't sure what I was looking for.
I did a search for WAVEFORMATEX but it didn't give me any results.
 
  Top
squid_80
Posted: Nov 12 2005, 01:10 PM


Advanced Member


Group: Members
Posts: 594
Member No.: 13813
Joined: 22-January 05



In the hex editor search for "auds", then a little bit further on there should be "strf". Scroll the cursor through the following bytes until the hint at the bottom of the hex editor window says you're at the wBitsPerSample field. (Make sure Enable AVI field assist is turned on under the edit menu.)
 
     Top
farcus
Posted: Nov 12 2005, 04:05 PM


Unregistered









How do I edit in the hex editor? I don't seem to be able to change any values.
The blue bar at the top shows (read only)
 
  Top
farcus
Posted: Nov 12 2005, 05:37 PM


Unregistered









QUOTE (squid_80 @ Nov 12 2005, 10:10 PM)
In the hex editor search for "auds", then a little bit further on there should be "strf". Scroll the cursor through the following bytes until the hint at the bottom of the hex editor window says you're at the wBitsPerSample field. (Make sure Enable AVI field assist is turned on under the edit menu.)

scratch my last post. I worked out that I needed to uncheck the read only option in the open dialogue of the hex editor.

Thanks so much for this - the solution works perfectly.
I'm seeing a range of different numbrs from file to file but setting them to zero corrects the problem and they then work 100% in virtualdub.

Why do you think this is happening to some files?
Nandub error?
 
  Top
squid_80
Posted: Nov 12 2005, 11:16 PM


Advanced Member


Group: Members
Posts: 594
Member No.: 13813
Joined: 22-January 05



Ah, so that's where the read-only box is. I just loaded it into another hex-editor program. wub.gif
What kind of range are you seeing? Because even if it were uncompressed audio, the values should only be 0x10(16, for 16-bit audio) or 08 for 8-bit audio (yuck). Anyway it means nothing for compressed audio formats and should be 0. I guess the directshow codec just doesn't care about it.
As for what's responsible for creating these files, I'm not sure - nandub, vdubmod and avi_mux all didn't reproduce the error when I tried muxing a vbr mp3 with video.
 
     Top
farcus
Posted: Nov 13 2005, 01:33 AM


Unregistered









QUOTE (squid_80 @ Nov 13 2005, 08:16 AM)
Ah, so that's where the read-only box is. I just loaded it into another hex-editor program. wub.gif
What kind of range are you seeing? Because even if it were uncompressed audio, the values should only be 0x10(16, for 16-bit audio) or 08 for 8-bit audio (yuck). Anyway it means nothing for compressed audio formats and should be 0. I guess the directshow codec just doesn't care about it.
As for what's responsible for creating these files, I'm not sure - nandub, vdubmod and avi_mux all didn't reproduce the error when I tried muxing a vbr mp3 with video.

I'm not too savvy with the hex editor but found the part that you were talking about. Most of my files that give me trouble have a value of 10 00. I changed this to 00 00 and everything is sweet.

When you tested with nandub what mp3 encoder did you use. As far as I can tell the problem is usually occurring when used with lame - whether that be in conjunction with something like besweet or just nandub directly.
 
  Top
squid_80
Posted: Nov 13 2005, 05:46 AM


Advanced Member


Group: Members
Posts: 594
Member No.: 13813
Joined: 22-January 05



I tested muxing an mp3 file created with besweet. I'll try again using the encoder from within nandub later (capturing a movie right now).
 
     Top
squid_80
Posted: Nov 13 2005, 06:31 AM


Advanced Member


Group: Members
Posts: 594
Member No.: 13813
Joined: 22-January 05



I can't get nandub to process audio at all. It won't show any formats in the compression selection window without turning on show all formats, and even then when I save the avi the audio is left out (samples processed remains at 0 the whole time). So I'd suggest not using nandub at all.

EDIT: If I open the broken avi file given to me and choose Set text information from virtualdub's file menu, the Software field contains "cant touch this". I have no idea where this would come from, probably just someone's tag but it would be very interesting if your files have the same.
 
     Top
farcus
Posted: Nov 13 2005, 01:36 PM


Unregistered









QUOTE (squid_80 @ Nov 13 2005, 03:31 PM)
EDIT: If I open the broken avi file given to me and choose Set text information from virtualdub's file menu, the Software field contains "cant touch this". I have no idea where this would come from, probably just someone's tag but it would be very interesting if your files have the same.

I do indeed see the same thing in the software field - 'can't touch this' on many of the problem files. Other problem files simply contain 'nandub 1.0rc2.'
 
  Top
1 User(s) are reading this topic (1 Guests and 0 Anonymous Users)
0 Members:
72 replies since Oct 24 2005, 05:09 AM Track this topic | Email this topic | Print this topic
Pages: (5) 1 [2] 3 4 ... Last »
<< Back to Codec Discussion