Created attachment 4525 [details]
Scanner Log

Created attachment 4526 [details]
Server log 1

Created attachment 4527 [details]
Server log 2

Created attachment 4528 [details]
Server log 3

Ticket #081227-001895

Environment:

Windows Vista Ultimate SP1
Symantec Internet Security 2009
iTunes Version 8.0.2.20
SqueezeCenter 7.3.1 running on Vista
Squeezebox Boom
Music stored on Buffalo Linkstation Pro
SqueezeCenter and the iTunes Library XML are on a PC


Symptom:

**Please note that the customer stated NOTHING has changed***

This ran without issue until 22 December.  On 23 December, the Boom stopped working with my iTunes music but continues to work with internet radio via SqueezeNetwork or SqueezeCenter


The Boom and Squeezecenter are communicating and appear to be working normally except:

1.  There is no sound from the Boom

2.  At the end of a track, the display freezes for several minutes before moving to the next track

3.  The progress bar on the boom does not progress, although it tracks normally on SequeezeCenter.

4.  Pressing pause on SqueezeCenter causes the track to start from the beginning.

Occasionally one track will play normally, but always stops at the end of the track and never plays the next scheduled track.

Everything worked fine when I experimentally turned off iTunes and rebuilt the database using WAV files on the NAS

It is only with iTunes (.M4A) files that have this problem

Troubleshooting:

Clean install of SqueezeCenter 7.3.1
Reset Xilinks Chip
Had uninstall/reinstall Itunes
Had perform clean install after Itunes
Had clear library and rescan after this, and the issue still occurs

**At first is sounded like ports being blocked, but the customer converted to WAV and the music was able to play fine--Problem only exists with M4a files**

Please see attached logs

I have now installed iTunes and Squeezecenter on a second PC, using exactly the same configuration (i.e Squeezecenter and iTunes on the PC with the same music files on my Buffalo Linkstation Pro).  This PC operates under Windows XP Pro. This configuration is working correctly.

During this install the iTunes plugin was set "on".  In my previous reinstalls of 7.3.1 on my original PC, this was set "off" by default.  Is this significant?

Since my last posting I have completely unistalled and resinstalled iTunes and Squeezecenter on my original PC with no effect. (I did not remove iTunes libraries, etc as these would be too painful to rebuild)

I have today set up a 10% sample of my music library on my PC's C Drive and built an iTunes library xml file pointing to this.  On rebuilding the Squeezecenter database, this works fine.

I then built the same sample on the NAS with the iTunes Library XML on my C drive.  This failed to work.

The problem appears, therefore, to relate to the use of my NAS Drive.  However, this works on my Windows XP PC and up to 24 December was working fine on my Vista PC.  I am not aware of making any changes to my system.  On 24 December the Boom played three tracks before stopping and has occasionally played a single track since.  I guess there could have been an automatic Vista update around this time.

Regards

David Sandy

Friday 2 January:  

I have discivered that M4A files play correctly when Squeezecenter points directly at the NAS Music folder.

I unchecked iTunes on the iTunes Tab in the Settings screen.  On the Basic Settings tab I entered the location of my Music (M4A) files (on my NAS) and rebuilt the library.  This plays with no problems.  

I guess this is a temporary work-around, although it will not keep in sync with iTunes. I cannot see why it will not run when configured correctly with the iTunes setting.

David, what version of iTunes do you have installed.

Hi James,

My environment is as follows:

iTunes Version 8.0.2.20
Windows Vista Ultimate SP1
Symantec Internet Security 2009
SqueezeCenter 7.3.1 (running under Vista)
Squeezebox Boom 
Music is stored on a share on a Buffalo Linkstation Pro NAS Drive(500GB Drive)
SqueezeCenter and the iTunes Library XML are on a PC
The PC and Buffalo drive are connected via Ethernet with fixed IP addresses, the Boom is connected via wireless using dynamic IP addressing.


Please note:

When I store the music on the C Drive of the same Vista PC, this works.

If I disable iTunes on the Squeezecenter and in "Basic Settings" point the location of my music files to the Buffalo NAS, this also works.

This same configuration (i.e same versions, music files stored on Buffalo NAS, etc) works when run from another PC running Windows XP.

Steven to reproduce.  player.source log would help, too, LaRon.

player.source logging should be set to "debug" in the server logs supplied.  I will re-run and let you have the log.

Please let me know if there are any others you require set.

Created attachment 4550 [details]
server log (see note) 01-05-2009

server log attached.

player.source, player.streaming & plugin.ituness set to "debug".

I have just received an email stating that this issue will be closed as I have not responded within 120 hours.  You will note from the dialog entries below that I last communicated on January 5 (2 days ago).

Please advise me if there is any information you require.

Regards,

David Sandy

Not to worry David, we are still looking at this bug.  The notice you received is from the support system not the bug system.

I was not able to reproduce the exact issues described using SC 7.3.1 on Vista but I did experience some issues around socketwrapper when playing AAC files.  I did not see this issue with the nightly most likely as a result of the changes for bug 10451.

David, could try the latest nightly of 7.3 and see if you still have an issue?  You can get it at http://wiki.slimdevices.com/index.php/Nightly_Builds

Hi Steven,

Thanks for your response.  I installed version 7.7-24549 and there is a partial resolution.  First I proved that I could initiate a random selection from both the Squeezecenter and the Boom.  I stopped the tracks before completion. 

Then I allowed the selection to run through.  The first track of the selection played successfully.  With Squeezecenter open in my browser the track completed and then froze with both the "count-up" and "countdown" timers incrementing!

I closed the browser and a second track played but I could not re-open the browser. A third and subsequent tracks played after a delay of around 65 seconds with the Squeezecenter still locked in "connecting" on the browser. Eventually, the browser reported "Internet Explorer cannot display the webpage" (http://127.0.0.1:9000/). 

Please let me know if you require further information.

Many thanks.

Subsequent to my earlier test, I stopped Squeezecenter and restarted it. I pressed play and it appeared to freeze.  I closed the browser and about 60 seconds later, the track started to play on the Boom.

Alan, do you have any ideas about this one?

Sorry, no. Really we need this to be recreated with appropriate logging in place (usual suspects: player.source=info, network.protocol.slimproto=info).

We are now planning to make a 7.3.3 release.  Please review your bugs (all marked open against 7.3.3) to see if they can be fixed in the next few weeks, or if they should be retargeted for 7.4 or future.

Thanks!

Since there's now a planned 7.3.3 release, bugs which won't make the cut-off are being moved to the next target out.  If you feel that this bug needs to be addressed more (or less) urgently than the 7.4 release, please cc chris@slimdevices.com and leave a comment in the bug to that effect so we can review it.

Thanks.

For some reason Bugzilla did not change the target when I did this yesterday.  Or maybe it was me.  In either case, I'm trying it again.

Is still an issue with 7.3.3?  If so please reopen and add additional comments.

Note that SqueezeCenter was switched from using mov123 to faad with this release.

Hi Steve,

I have just installed 7.3.3 and retested.  I can confirm that this problem now appears to be resolved.

(I didn't install 7.3.3 earlier as I was running on the nightly release you suggested back in January and this was designated 7.4).

Many thanks for your help, I'm happy for you to close this.

Best regards,

David Sandy

Closing resolved bugs - if you feel this bug still exists please first re-test
with the latest SW/FW version.  If you are able to reproduce then feel free to
reopen and attach new logs / steps to reproduce.