bugVbrfix - Bugs: bug #6854, In some cases Vbrfix removes the...

 
 
Show feedback again

You are not allowed to post comments on this tracker with your current authentification level.

bug #6854: In some cases Vbrfix removes the Lame Info

Submitted by:  Ryo94 <ryo94>
Submitted on:  Sat 02 Sep 2006 03:32:40 PM UTC  
 
Category: FixerSeverity: 3 - Normal
Priority: 5 - NormalStatus: In Progress
Privacy: PublicAssigned to: William Pye <willwap>
Open/Closed: OpenRelease: 1(beta)-D
Operating System: Microsoft WindowsFixed Release: 

Fri 15 Dec 2006 07:11:45 PM UTC, comment #3:

There are slightly difference between same preset of different versions of lame (mainly in fields like quality, vbr method & lowpass) the option could contemplate lame tag generated by 3.90 to lame 3.97, to the option below could be add this menu:

"chose version of lame"
LAME 3.90
LAME 3.91
LAME 3.92
LAME 3.93
LAME 3.94 (this remanined in beta version so can be ignored)
LAME 3.95
LAME 3.96
LAME 3.97

At time to add the new tag the user could know what codec is the right one using mr. questionman or encspot to detect it before proced to fix.

Ryo94 <ryo94>
Project Member
Fri 15 Dec 2006 06:38:43 PM UTC, comment #2:

Like I mentioned by email time ago this is a problem generated by cue splitter 0.5, cue splitter 0.6 beta12 just create the xing tag without the quality flag and without lame tag.
Although I suggested a fix for this in their forum I doubt that they implement a solution in next versions. So considering that you are working to fix this issue as an option for power users, I'm wondering if would not be better fix this just adding an option that add the qualty field + lame tag according to the most known lame presets, for example like:

"Add missing lame tag for"
--alt preset standard
--alt preset fast standard
--alt preset extreme
--alt preset fast extreme
--alt preset insane

At last most of vbr files are encoded with this presets (just a few people use switches) and the user can guess which to apply by the bitrate of the files.
In this way this will fix the problem generated by cue splitter v0.6 and other programs of its kind.

Ryo94 <ryo94>
Project Member
Tue 05 Sep 2006 07:43:12 PM UTC, comment #1:

This is a problem with identifying the Lame Info position when the Xing tag doesn't have the full flags

William Pye <willwap>
Project AdministratorIn charge of this item.
Sat 02 Sep 2006 03:32:40 PM UTC, original submission:

Although "keep lame info" is setted in option, in some cases vbrfix takes this info as "unidentified data" (probably because the lame info is wrongly located) and it remove it completely. The file to fix was encoded with LAME 3.90 alt preset standard.

VBRfix setting:

Lame Tags: "Keep VBR Tag Lame Info"
Remove Objet Types: "Unidentified data (Any other tag /data)
Xing Frame CRC Protection: "No CRC for Xing Frame"

I attached a little file (1.5MB) with this problem.

Ryo94 <ryo94>
Project Member

 

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -unavailable- added by willwap (Updated the item)
  • -unavailable- added by ryo94 (Submitted the item)
  •  

    Do you think this task is very important?
    If so, you can click here to add your encouragement to it.
    This task has 0 encouragements so far.

    Only logged-in users can vote.

     

    Please enter the title of George Orwell's famous dystopian book (it's a date):

     

     

    Follows 1 latest change.

    Date Changed By Updated Field Previous Value => Replaced By
    Tue 05 Sep 2006 07:43:12 PM UTCwillwapStatusNone=>In Progress
    Show feedback again

    Back to the top


    Powered by Savane 3.1-cleanup