-Brading Software Message Board
+--Forum: Mp3/Tag Studio Support and Bug Reports
+---Topic: Xing headers bug started by newfeauters
Posted by: newfeauters on Oct. 17 2002,00:38
If I strip off both id3v1 & 2, attach a Xing header using mp3ts, then add id3 again, the name and time come up in red, wanting fixing. Take away the id3 tags, and all is OK. And if I repair the xing header using mp3ts of an OK file, without id3 with xing, it adds one frame to the count.
And the "unsynced tags" preset in filters does the oposite for me.
Posted by: Magnus Brading on Oct. 17 2002,23:11
---------------------QUOTE-------------------
If I strip off both id3v1 & 2, attach a Xing header using mp3ts, then add id3 again, the name and time come up in red, wanting fixing. Take away the id3 tags, and all is OK. And if I repair the xing header using mp3ts of an OK file, without id3 with xing, it adds one frame to the count.
---------------------QUOTE-------------------
Please take a look at < this thread > for info about why it turns red (if you read primarily my posts, you will find it pretty soon). And the additional frame is because VBR-headers are stored as an extra frame in the mp3 file.
---------------------QUOTE-------------------
And the "unsynced tags" preset in filters does the oposite for me.
---------------------QUOTE-------------------
Exactly what do you mean? Please explain.
Posted by: newfeauters on Oct. 19 2002,01:45
ok then. What i meant about the unsynced thing was that if i go to the search mp3s option, and choose "unsynced id3v1 and v2 tags" in the filter dialogue either by the preset or manually, it does the same as the "Synced" option.
Posted by: Magnus Brading on Oct. 19 2002,14:40
Ah, strange, I just reproduced it too. I'll look into it, thanks for the report.
Posted by: newfeauters on Oct. 23 2002,18:40
a few more:
again in the filter dialogue, untick everything, gpto the sound ecoding properties tab, tick filter fields then CRC. Click OK, and I get error messages (have't ticked anyjthing....)
the other one i noticed was when i did a direct tag manipulation in preview mode, the oin the preview results speadsheet, i dragged the artist v2 next to artist v1 (on the right side, resulting in a general exception error, but i can still use the prog. same for genre v2.
Posted by: Magnus Brading on Oct. 23 2002,20:35
Thanks for the report.
The column move bug is already fixed in version 3.02 (not released yet), and I will take a look at that other issue.
Posted by: newfeauters on Nov. 26 2002,18:59
I also get "Access violation at address 00403D40 in module 'mp3tag_s.exe'. Read of address 0038C2D9." when I trim any mp3 file, from start or end. Then the file is trimmed, but mp3ts hangs.
BTW this never used to happen..
Posted by: Magnus Brading on Nov. 26 2002,23:30
When you trim any mp3 file you say? So there is not a single file that it does not crash for? Have all these files been processed with a common encoder or tagger program maybe? If you download a totally unrelated mp3 file from somewhere else and try to trim it, does the same thing still happen?
Posted by: newfeauters on Nov. 27 2002,20:56
There is more to it than I thought, it did seem to happen with anyfile, right now I'm doing it with one particular file and it will only crash when I trim from "Start". The file is LAME 3.92encoded, 192kbits/s CBR. It happens even if i strip off the id3v1 and v2 tags. I know it is not corrupted, as I ripped it (EAC) and encoded it myself.
In fact it does seem to be happening for all my files (not just LAME ones, variety of sources etc.), but only when trimming from the Start, which maybe why I never noticed it before.
Posted by: Magnus Brading on Nov. 27 2002,23:13
It is very strange, I have heard before from one or two other users who also claim to have constant problems with the trim tool, just like these. The strange thing is that the majority of users (including myself) don't have any such problems, and can't even reproduce them while performing the exact same operations that produce errors for the others.
If anyone has a clue about what might be causing this, you are very welcome to share it anyway.Newfeauters, if you have any anti-virus program running, please try to deactivate it and test if the problem still remains after this (although that is a real long-shot I have to admit).
Posted by: newfeauters on Nov. 27 2002,23:35
Nope, i keep mcafee disabled totally, only use the on-demand scanner. I've also tried not accessing through right-click edit file... and via the start menu instead, and i just tried closing most other programs.
Im on XP Pro SP1, and like I said, it only happens when trimming from the start of the file
Im not too bothered though, as the file does get trimmed, only mp3ts then hangs.
Posted by: thei on Nov. 29 2002,11:53
Hello,
I have had this problem.
It is caused (in my case) by either lack of freespace, file being accessed by another program, or (most commonly) file being read-only.
I also have had similar problems when processing multiple files with any tool in MP3TS. It doesn't like read-only files.
Posted by: Magnus Brading on Nov. 29 2002,15:00
Normally there should be no problem with read-only files at all. The write-protection is temporarily removed while Mp3/TS is processing the files (although this obviously doesn't apply to files that are locked by other processes, but these should only generate a status message saying that they can't be opened).
Posted by: thei on Nov. 29 2002,16:16
Yes, now that you mention it, I think only files that were locked by other processes, not files marked as read-only, caused the errors I experienced. In single-file modes, a dialog shows (something along the lines of "Can't write tag" or similar...) but in multi-file modes (i.e. processing more than one file at a time) the program will either freeze, quit, or show a dialog and then freeze. I'm not sure if its ever failed politely when doing this, but I've learnt not to do it so haven't actually had a problem in a while
I also use a weird Winamp plugin that has caused a few other (not MP3TS) problems of its own, which could be to blame somehow.And just out of interest, I can't remove the read-only attribute in Windows without freezing up Explorer. A bug in NT5x it seems (occurs under specific conditions which my MP3's cause)...
Posted by: newfeauters on Nov. 29 2002,18:37
Well, it is not space for me, as i have 3GB free, and its not the fact the file is being accessed, becuase it does get trimmed, i always make a copy of a file to mess around with and delete it when testing things like this. And they definitely aren't read only
The onlt connecting thing is the fcat that each time I am trimming from the start of the file... I even tried putting a file on my NTFS drive... (with no luck).
Posted by: newfeauters on Dec. 12 2002,21:21
Another one (maybe i should make a new topic now..): Reproducable for me.
Setup: directory of files with id3v1 only.
Open Browse/Edit Tags & Files, and choose directory and the first file.
Open Advanced id3v2 info box and move to the side, and keep it open! (Suggestion: you should still be able to add id3v2 fields when there is o id3v2 tag, as there is no option to create an id3v2 tag.)
Make changes to file, and choose "Write changes" option
Choose next file, and make changes & write them.
Bug #1 - Produces Access violation at address 00473ED6 in module 'mp3tag_s.exe". Read of address 00000028.
File is not updated, mp3ts "half-hangs" - displays loading mouse icon, but you can still perform operations! (including the one that just made the error..) Then the loading mouse disappears..
Restart mp3ts.
Bug #2 - On reopening of mp3ts, option for "Advanced id3v2 box" is checked, but the box is not visible.
Posted by: Magnus Brading on Dec. 12 2002,23:12
First of all, yes, it is good to start a new thread for each new issue, it makes it easier for other people to find info about any certain subject.
About the bugs, #1 is already fixed in the current version I have here on my disk, it should work in the next update.
I'm also aware of bug #2 (it only happens when opening from the shell extension, right?), and it's on the todo list.
Thanks for the reports.
Posted by: newfeauters on Dec. 13 2002,18:27
" (it only happens when opening from the shell extension, right?), "
Didnt even try that, for me it was only happening if I restart as soon as I get that error message, which you say is fixed so they are both fixed.
Ill start a new topic next time, but i didnt think it would be nice to have five topics all by me either..
Thanks for the acknowledgements & updates on progress..
Posted by: Magnus Brading on Dec. 14 2002,02:54
You can start as many topics as you like, as long as they are about different bugs. It only has advantages to separate different issues in different topics, so don't worry about it at all.
end