Bugzilla – Bug 14883
audio_size needed for WAV and AIFF files.
Last modified: 2010-04-29 09:22:48 UTC
Addio::Scan is sets the file_size attribute for WAV and AIFF files. This is then used to set the SIZE tag which in turn sets the Track::audio_size attribute. With 7.3 the scanner would set the SIZE tag to length of the audio in the file, after the header and excluding any trailing tags.
== Auto-comment from SVN commit #484 to the opensource repo by andy == == https://svn.slimdevices.com/opensource?view=revision&revision=484 == Bug 14883, add audio_size info to WAV/AIFF
Looks like this fixed the problem with pops at the end of WAVs. Thanks.
Fixed
I also experience plops at the end of my wave files since 7.4.x. Since I don’t know to which bug report the error belongs to I have also documented it in bug report 14552.
Try doing a full rescan with the latest 7.4.2.
I installed 7.4.2 –r29150, did a full rescan and no more plops. Thanks Andy.
Trevor asked me to contact the engineers on this matter which is happening again with AIFF (but NOT Apple Lossless) files with version 7.5. The burst of static type white noise is very loud and seems that it could damage my speakers or amps. The engineers can contact me directly by phone at 530-474-5193.
Do you also have the problem with WAV files?
Reopening.
(In reply to comment #8) > Do you also have the problem with WAV files? I do not have any WAV files, Andy. I have about 13000 songs in AIFF 52000 in Lossless. So far it happens with all AIFF, no matter what file they happen to be and never does it happen with lossless
OK, I'll check it out.
(In reply to comment #11) > OK, I'll check it out. I'll be gone for a while this AM...back this afternoon.
I can't reproduce this. I tried an AIFF file with an ID3 tag at the end, audio_offset and audio_size are properly read and don't cause any pops. I tried native AIFF as well as AIFF->FLAC. I think I'm going to need one of your files. Can you attach a small one that has the problem?
(In reply to comment #13) > I can't reproduce this. I tried an AIFF file with an ID3 tag at the end, > audio_offset and audio_size are properly read and don't cause any pops. I > tried native AIFF as well as AIFF->FLAC. I think I'm going to need one of your > files. Can you attach a small one that has the problem? Problem is not with the file itself, as I stated, it occurs when in the middle of changing from one song to the next...No way to tell if it is at the end of a file, at the beginning of a file or in that space in between. None of the AIFF of mine were ever FLAC though.
OK, can you send me some file(s) so I can reproduce the problem?
(In reply to comment #15) > OK, can you send me some file(s) so I can reproduce the problem? Yes sure, I can try. How do I do it? I pulled 2 consecutive tunes off an album and have the files on my desktop. I have a Mac.
You could find the smallest files you can and attach them to this bug. Or send them to me via yousendit.com if they are too big.
(In reply to comment #17) > You could find the smallest files you can and attach them to this bug. Or send > them to me via yousendit.com if they are too big. Nuts, they just spent a half hour uploading and I got a message that says Local file uploads must not exceed 20 MB in size. I'll try plan b
(In reply to comment #18) > (In reply to comment #17) > > You could find the smallest files you can and attach them to this bug. Or send > > them to me via yousendit.com if they are too big. > Nuts, they just spent a half hour uploading and I got a message that says > Local file uploads must not exceed 20 MB in size. > > I'll try plan b I need an address to mail them to.
andy@slimdevices.com
(In reply to comment #20) > andy@slimdevices.com 20 minutes of trying to get that yousendit site to work to no avail at all. My browsers both tried to block it, The site itself, after I finally got in, will not allow a file pair that big, it tries to get me to pay 9 bucks, it will not allow me to set a password. Same thing when I try to send just one at a time. We need another way to do this. Can I burn an album to a CD in AIFF and mail it by snail mail to you? If so I need an address. As you can tell I am pretty frustrated. Whatever fix you did to 7.4 when you changed it to 7.4.2 is what worked before when this happened. I suppose that fix does not work anymore? As before. If you can please phone me 530-474-5193 we can quit beating around the bush. I have a vision problem that makes reading a real chore. Thanks
I'm assigning this to QA, maybe they can reproduce it without your files.
(In reply to comment #22) > I'm assigning this to QA, maybe they can reproduce it without your files. OK, will I be in the loop if and when the fix is (re)discovered?
Larry would you be able to enable database.info debugging, do a full rescan, and post a snippet of your scanner.log that shows one or two of your broken files? Specifically I'm looking for the AUDIO_SIZE, AUDIO_OFFSET, and FILESIZE values, it will look something like this: [10-04-23 08:04:48.4926] Slim::Schema::_preCheckAttributes (2171) Report for file:///Users/andy/Music/Slim/wav-aiff/pre-id3.aif: ... [10-04-23 08:04:48.4946] Slim::Schema::_preCheckAttributes (2181) .. AUDIO_SIZE : 38434040 ... [10-04-23 08:04:48.5000] Slim::Schema::_preCheckAttributes (2181) .. AUDIO_OFFSET : 2278 ... [10-04-23 08:04:48.5015] Slim::Schema::_preCheckAttributes (2181) .. FILESIZE : 38436318 This bug was caused by AUDIO_SIZE having the wrong value, and being equal to FILESIZE. Here you can see my test file correctly sets AUDIO_SIZE to the size of the SSND chunk within the file, so no extra bytes are sent to the player when playing the file.
(In reply to comment #24) > Larry would you be able to enable database.info debugging, do a full rescan, > and post a snippet of your scanner.log that shows one or two of your broken > files? Specifically I'm looking for the AUDIO_SIZE, AUDIO_OFFSET, and FILESIZE > values, it will look something like this: > > [10-04-23 08:04:48.4926] Slim::Schema::_preCheckAttributes (2171) Report for > file:///Users/andy/Music/Slim/wav-aiff/pre-id3.aif: > ... > [10-04-23 08:04:48.4946] Slim::Schema::_preCheckAttributes (2181) .. AUDIO_SIZE > : 38434040 > ... > [10-04-23 08:04:48.5000] Slim::Schema::_preCheckAttributes (2181) .. > AUDIO_OFFSET : 2278 > ... > [10-04-23 08:04:48.5015] Slim::Schema::_preCheckAttributes (2181) .. FILESIZE : > 38436318 > > This bug was caused by AUDIO_SIZE having the wrong value, and being equal to > FILESIZE. Here you can see my test file correctly sets AUDIO_SIZE to the size > of the SSND chunk within the file, so no extra bytes are sent to the player > when playing the file. OK, full rescan started now. Are you asking me to play 2 songs in which this glitch happens and then send the Scanner log? Or just send the scanner log after it has done the full scan? FWIW, I have rescanned the library several times and it has not stopped the burst of white noise/static.
When it's done, open scanner.log and search for a file that has the problem, and just copy/paste the bits I mentioned. You don't need to send the whole log.
(In reply to comment #26) > When it's done, open scanner.log and search for a file that has the problem, > and just copy/paste the bits I mentioned. You don't need to send the whole > log. OK, but I may have a hard time finding or seeing it because of my vision problem. If I cannot pick those files out I will copy the whole Scanner log and send it. The rescan will likely take some time. Will send what I can when it completes.
(In reply to comment #27) > (In reply to comment #26) > > When it's done, open scanner.log and search for a file that has the problem, > > and just copy/paste the bits I mentioned. You don't need to send the whole > > log. > OK, but I may have a hard time finding or seeing it because of my vision > problem. If I cannot pick those files out I will copy the whole Scanner log and > send it. The rescan will likely take some time. Will send what I can when it > completes. Got this message when I tried to post the log: Comments cannot be longer than 65,535 characters. My eyes will not allow me to try and read thru that immense log and try to find what you are looking for. Once again your request is is possible to achieve considering my vision impairment and the size of what you want. I can burn the file to a CD (maybe, who knows) and snail mail it to you. Awaiting further instructions. Meanwhile a lot of my art work did not get rescanned in (yet again) so I need to try and rescan to get that back. I have saved the scan log file to my desk top, I have no other idea on how to get this to you.
(In reply to comment #28) > (In reply to comment #27) > > (In reply to comment #26) > > > When it's done, open scanner.log and search for a file that has the problem, > > > and just copy/paste the bits I mentioned. You don't need to send the whole > > > log. > > OK, but I may have a hard time finding or seeing it because of my vision > > problem. If I cannot pick those files out I will copy the whole Scanner log and > > send it. The rescan will likely take some time. Will send what I can when it > > completes. > Got this message when I tried to post the log: > Comments cannot be longer than 65,535 characters. > My eyes will not allow me to try and read thru that immense log and try to find > what you are looking for. Once again your request is is possible to achieve > considering my vision impairment and the size of what you want. I can burn the > file to a CD (maybe, who knows) and snail mail it to you. Awaiting further > instructions. Meanwhile a lot of my art work did not get rescanned in (yet > again) so I need to try and rescan to get that back. I have saved the scan log > file to my desk top, I have no other idea on how to get this to you. OK, I tried to email the whole file...I think it got thru, let me know please.
(In reply to comment #29) > (In reply to comment #28) > > (In reply to comment #27) > > > (In reply to comment #26) > > > > When it's done, open scanner.log and search for a file that has the problem, > > > > and just copy/paste the bits I mentioned. You don't need to send the whole > > > > log. > > > OK, but I may have a hard time finding or seeing it because of my vision > > > problem. If I cannot pick those files out I will copy the whole Scanner log and > > > send it. The rescan will likely take some time. Will send what I can when it > > > completes. > > Got this message when I tried to post the log: > > Comments cannot be longer than 65,535 characters. > > My eyes will not allow me to try and read thru that immense log and try to find > > what you are looking for. Once again your request is is possible to achieve > > considering my vision impairment and the size of what you want. I can burn the > > file to a CD (maybe, who knows) and snail mail it to you. Awaiting further > > instructions. Meanwhile a lot of my art work did not get rescanned in (yet > > again) so I need to try and rescan to get that back. I have saved the scan log > > file to my desk top, I have no other idea on how to get this to you. > OK, I tried to email the whole file...I think it got thru, let me know please. In addition to this problem, I am not able to scan in 3 out of a 4 CD set that is in Itunes and in the proper location on my hard drive. I have tried 3 times to scan in these other 3 CDS and they just will not show.
At this point we really need a file to test it. I'm going to mark this fixed again, but please reopen this bug if you can upload a file that demonstrates the problem. This wiki page has info about an anonymous FTP you can upload large files to: http://wiki.slimdevices.com/index.php/Large_File_Upload