Tried with cd player with same results (rca this time); The transporter will not play from SlimServer without complete shutdown, nor will it go back to playing the digital inputs once you have tried to switch back. What good are the digital inputs if it's such a pain to use them? Is it bad for the unit to have to keep killing the power to switch back and forth? Is anybody going to acknowledge this major bug? Only the future will tell.

Another quirk: After a reset from digital in you can switch to internet radio and then to slimserver. From slimserver the unit can be switched back to sp/dif input and that works, but this only works once. If you then switch back to internet radio, it buffers AND the meters move like it is playing, but no sound. The same for slimserver and if you try to get back to digital input also no sound.

Please do not preset targets.

*** Bug 4914 has been marked as a duplicate of this bug. ***

I've seen the same behavior.  I only use the digital input occasionally (RCA S/PDIF from a CD player), but have seen the same thing - the Transporter will not be able to play from the SlimServer after switching the input back, although the display will show the currently playing track.

cc'ing richard, to make sure he's in on the discussion and what it might take to fix.

Just to remind you of that trick which helps me every time
https://bugs-archive.lyrion.org/show_bug.cgi?id=4914#c3

"pause helps when switching from digital-in to networked.
play helps in reversed scenario."

If it wasn't for that I would go nuts because I'm constantly switching to digital in.

Wallace, could you look at this one and try to find a reliable way of reproducing it?

I second this bug report.
With my transporter, the optical input doesn't seem to function at all (digital rca seems to work fine through)
after trying any digital source, switching back to network, networked playback is broken, and need to power cycle to get it back to work.

Add. Info: using FW 31.

Any chance someone can re-evaluate the target of this bug and maybe get a bug fix out for 6.5?  In combination with bug 4580 it effectively renders the digital input features useless for many Transporter users.

http://forums.slimdevices.com/showthread.php?p=221843

Just like to echo what has already been said. It happens every time I switch from digital AES/EBU back to network player. Pausing the digital first works but is a pain to set-up remote to automate.
I'm using FW31. It doesn't happen with FW24 or 27.

Reproducibly I get NO signal on the analog cinch output (the one I use) of my Transporter after certain switches:

1. First playing high-bit FLAC files (like from LINN Records), then trying to move to an M4U (ALAC) or MP3 encoded one, via SS.
2. Using one of the digital-in ports - I use them to have the Transporter do the DAC conversion from my CD and DVD players, and then again moving to SS files.

The only resolution is to take the power off the Transporter (pulling the plug that is) and restart it. Of course this is very annoying.

MacMini CoreDuo, 300 GB of ALAC music -> Black Transporter (via analog & digital out) & HK DVD47 for SACD + DVD-A -> Harman Kardon AVR 8500 & HK PA2200 Signature -> Mission 782 plus 4 x Mission 780SE & 78C & REL Strata III

Wallace, since this bug is already assigned to you, do you think you could try to reproduce Evert's symptoms?  Steven should be able to help if you have any issues.  I'd simply like to make sure they are reproducible on a system in-house.

Evert, while we are looking in to it, a slightly better solution (if it works) to rebooting your Transporter is simply holding down the power button on the remote control until you see it begin its boot process.

Actually, I'll leave you cc'ed on the bug, Wallace, but I'll assign it to Richard for a fix.

Richard, I seem to recall Sean had some information on this bug, or some ideas about a fix.  Does that ring a bell?  Of course you may wish to pass the whole shebang on to Felix.

Adding Felix to the cc'list, since he also works on firmware issues.

My problem went when I upgraded to slimserver 7 (even when it was still using FW1)

Sorry, last post should have read FW31 (not FW1)

I am unable to reproduce this issue. I am using Transporter FW 32 and SC 7.0.

Felix, as I said in my last comments, there is no problem with SC7 and FW32. There wasn't a problem with SS7 and FW32 or FW31 either. The problem was with SS 6.5.4 I think. Earlier versions were ok too. That's my experience anyway. Others might find there is still an issue SC7 but I'm happy the problem has gone.

Is anyone else on the cc list for this bug still experiencing this problem with Slimserver 7?  If not we will mark it resolved.  Thanks for any additional info!

I have checked my player with FW32, server 7.0 13701 -- appears to be resolved -- no sound loss when switching back and forth between digital inputs/internet radio/music. 

However, when switching TO any digital in with sound on, there's a very lound sound outburst which may damage speakers if TP is used like a dac/preamp and connected directly to power amplifier.

Eugene 

re comment 21, see bug 4580

I was just testing this with firmware 34 and now it is seriously broken and completely reproducible for me. I don't know why it works for some people.

However, on the new_audio branch I am working on I do not see this problem. Going to look at trunk and try to identify the root cause of this.

Oh finally! Thanks Sean, I was staring to get really annoyed when the digital input doesn't take and it just makes rumble noise which could damage the speakers if you leave it few seconds to evolve to a louder noise.

Ugh. I spoke too soon. Power-cycled and tried again and now I can no longer reproduce. It works fine now. This is a weird bug!

Dino, can you tell me what exactly you have connected to your Transporter and exactly what sequence of actions you're doing? Give me as much details and possible and I will keep trying to reproduce here.

Here is my first post about this with some important info:
https://bugs-archive.lyrion.org/show_bug.cgi?id=4914#c3

It uses toslink input and xlr or rca analog output. The output doesn't matter since I used it for a few months on RCA and then on XLR.

Most probably toslink sync issue. Could be that some movies are 48khz and songs are 44.1khz and depends on the combination from network playback to toslink input and vice versa.

More testing:

With FW34 this seems to be reproducible on one out of every two power cycles. Interestingly, it seems to get into one o two states:

1) you can switch back and forth as many times as you want

2) the first time digital input is selected is OK, then attempting to play a music file fails, and it does not start to work again no matter how many times you go back and forth. Only a rest can (possibly) get you back.

Once it gets stuck, there are no active signals on the i2s bus, surprisingly not even MCLK.

With the new branch of the firmware I am working on, I am not able to reproduce it at all, and I tried more than 20 resets. Works every time.

Reviewed the logic design and firmware for trunk, did not see any obvious problems. It would be really nice to positively identify the problem, but further debugging is probably not worth it since this stuff has been largely redesigned and the mystery bug does appear to no longer exist.

If you are having this problem please wait a week or two for a new firmware beta that should solve this issue.

Did some tests on trunk:

Did a clean build from trunk and was able to reproduce, again on roughly 1 of 2 power cycles.

**Could NOT reproduce this when runtime debugging was enabled**. This suggests a race condition between the main thread and the audio thread, and also explains why developers may have been less likely to notice.

Tried porting r3503 back from the new_audio branch and this did NOT help.

Noticed that there are apparently two different failure modes. In one case the visualizers are running and the I2S bus looks normalish: clocks are active and data is left aligned, but no sound. Actually the data may have been wrong because it looked like there was always a 1 in the MSB on the i2s bus. Anyway, no sound at all from the DAC which even for garbage input should have produced something. Then I looked at PDN and it is being held low!

In the other failure mode there are no signals wiggling on the i2s, and no visualizer movement.

ech. maybe two threads fighting for the config bus?...

Found probable cause of this: the app thread tries to control the bus when setting volume, but it may be in use by the audio thread as it selects the input. This seems to be a case where we do need to provide access for both threads, so I suppose we need a spinlock. 

This is great news. will this possible fix be included in FW35?
I guess its still waiting for the new implementation of the audio thread you mentioned some weeks ago
For when is FW35 scheduled, if you had to make a guess? a matter of days, or more weeks?

A fix will go in as part of a new firmware release for 7.0.1, with several other Transporter bug fixes. Beta should be out next week.

Fixed in trunk 17060 / firmware 40.

Changing fixed target to 7.1 as FW 40 will be released then, not in 7.0.1

I have tried the F40 and if you reboot the computer and don't touch anything the weird noise will appear on its own. Then you must power off and on.
Also touching the volume control does the same.

So now it's worse than before when it only happened on source switch.

I must say I am surprised for how long you can ignore this issue. It is clear that you have devoted your energy to new products like the Duet but this is plain ignorance.

*** Bug 8378 has been marked as a duplicate of this bug. ***

(In reply to comment #35)
> *** Bug 8378 has been marked as a duplicate of this bug. ***
> 

Still not getting sound when selecting digital inputs without a reset.
£1300 for a device that does not do as it is advertised to?

(In reply to comment #36)
> (In reply to comment #35)
> > *** Bug 8378 has been marked as a duplicate of this bug. ***
> > 
> 
> Still not getting sound when selecting digital inputs without a reset.
> £1300 for a device that does not do as it is advertised to?
> 

Terry - what firmware rev are you running? You need to get V.42.

Hi Sean it's firmware 37 downloaded with SC7.0.1 where do I get firmware 41 from without beta software please?

Terry, I would recommend getting the whole package here: 

http://www.slimdevices.com/downloads/nightly/latest/7.1/

However, if you want ONLY the firmware binary, without updating to the v7.1 server, you can get it by going here:

http://svn.slimdevices.com/viewvc.cgi/7.1/trunk/server/Firmware/

and downloading these two files (right-click on their rev #):

transporter_42.bin
transporter.version

Then place these in the Firmware/ directory in your existing server installation, replacing the existing transporter.version file.

Hold the left arrow key on the remote to disconnect from the server, then re-connect and it will update the firmware.

Thanks for the help Sean.
OK installed the complete package.
If the Computer is running I can switch to digital inputs and back and have sound. turn the computer off I still have sound if a digital input was selected. If the computers was off I cannot switch to digital inputs and get sound without turning on the computer is this correct. I can then turn the Computer off and still have sound through the digital input.

I now have another problem the RH display viewed from the front is corrupt the centre lines seem to be missing.

Terry - I'm glad to hear it's working, but now this discussion needs to be taken to the forums. There are many people CC'd on this bug, and we're veering off topic.

Yes the screen corruption is off  topic for which I apologise, but surely the part about having the computer on to listen to the digital inputs is not? 

Still having the problem with FW 43. SqueezeCenter Version: 7.1 - 21034

Enabled RCA digital input, then couldn't get music.

David, could you please describe the behavior you are still experiencing in detail and the steps you took to reproduce?  It might also be helpful to mention any Transporter settings you are using that are different from the defaults and what equipment you are using for the source might be helpful too.

I have have tried everything I can think of to reproduce and I have been unsuccessful so far.  I did come across a different bug that I don't think has been filed however.

I was able to reproduce this by holding left and disconnecting from SC, selecting input, then re-connecting to SC. At this point I can't get anything to play until I reboot my Transporter. I was not able to reproduce this with the digital input menu while connected to SC. 

I'm running a clean install of SqueezeCenter Version: 7.1 - 21034.

Since it was a clean install all of the settings were defaults. I did password-potect SC, I think that's about it, though.

I have a Panasonic DVD-RP82 running RCA coax to the Transporter.

I select the RCA digital input, and everything works fine (I get sound from the DVD player). When I try to play music, the DVD player continues to play; no music. 

Interestingly, the display on the Transporter does not count down.

In SC, though, it shows that the song is playing, and the counter is counting down. If I hit pause within SC or on the Transporter remote, I stop getting sound from the DVD player (digital input) and get no sound at all. If I hit play on either SC or the Transporter remote I get the DVD player again.

Does this bug still exist?  It seems quite serious to me for a release apparently targeted primarily at Transporter users.

Ross, I hate to pull you away from verifying fixed bugs, but could you have a try reproducing David's symptom?  That is, 

1) connect to SC 
2) use the player UI to select the digital in and play something from the digital it
3) use the player UI to go find a local track and play it.

> 1) connect to SC 
> 2) use the player UI to select the digital in and play something from the
> digital it
> 3) use the player UI to go find a local track and play it.
> 

Not able to reproduce this bug via this means. The only way I was able to reproduce this was via disconnecting from SC and selecting digital input from firmware. Ken or David, mind trying it without disconnecting from Squeeze Center?

Ping Ken & David: Is this still an issue?
\

I'm away until Monday, I'll check then and report back...

7.1 is imminent.  We'll continue to look at any remaining issues for 7.2

Still having problems with no sound when switching to digital inputs with firmware 41 not connected to SC. Have to do a reset for digital inputs to work. Really not impressed with this device. 

Sean: can you take a look?

Please test with firmware 59 in 7.2.

I'm no longer able to reproduce as I described in comment #45 with firmware 59. 

(In reply to comment #47)
> Does this bug still exist?  It seems quite serious to me for a release
> apparently targeted primarily at Transporter users.
> That is, 
> 1) connect to SC 
> 2) use the player UI to select the digital in and play something from the
> digital it
> 3) use the player UI to go find a local track and play it.

I have installed V7.1 (formal release) and I am not able to play anything over the digital inputs of my Transporter. It makes no difference whether selecting AES, BNC, RCA or Optical. The CD player is a Meridian 207.

(PS I never tried the digital inputs on prior software versions so cannot comment whether the problem got worse or better...)

AndrewFG

Do the inputs work when not connected to SC?  Make sure you are listening via the analog outs, too, digital input is not sent to the digital outputs.

(In reply to comment #57)
> Do the inputs work when not connected to SC?  Make sure you are listening via
> the analog outs, too, digital input is not sent to the digital outputs.

The Digital Inputs don't work whether the Transporter is connected to SC or not.

And, of course I am using the analog outputs...

BTW I did also experiment with selecting the Word Clock from the Optical Input (instead of Internal) but a) this did not cause any sound to come from the Digital Input, and b) when switching back to music from the server, it was played veeerry slowwwly. => So maybe the problem is something to do with the Transporter having trouble to sync with the Digital Input bit stream?

Installed firmware 59 in 7.2. immediate results were the transporter froze requiring a power off and reboot.
Not had a problem so far with the digital inputs producing no sound, will monitor as this was intermittent but regular.

Well just tried again no difference!

 It also will not play from squeezenetwork the transport freezes. (some of us do wish to listen without the computer switched on). will return to 7.1 

With firmware 59 I'm able to reproduce this as described, but not consistently. By switching the Transporter between streaming Rhapsody and digital input several times, Transporter gets stuck on the digital input and refuses to play anything else. Holding left to disconnect from SC and reconnect to SC resolves this. 

With F59 I'm also having the muted output sometimes when switching to digital input (toslink) from playing networked music.

At least remote power off and play resumes it, no need for hard-reset like before F40.

Quite weird that you are having this much trouble fixing this basic function.
Don't forget not to use the debug mode, that was the mistake for the first year.

Just a reminder: This needs to be addressed by the end of the week.

Yes it sure does!

Ping, Sean.  Will this be fixed monday for our final candidate?

Sorry, no. I'll talk to Ross about it next week - I need a test case, because I have been unable to reproduce this since v.42.

Here is one test case:

In the F59 switching FROM the digital input to Random Song Mix it just stops with the song title and time, sometimes it continues to play the digital input in the background. Then Power Off and Play and it starts the Random Song Mix properly.

Let me know if you need more info.

QA to give Sean detailed repro instructions

This has proven much more difficult to reproduce, but I managed to finally. Sean I'll chat with you tomorrow if you have time. 

We can not reproduce this bug consistently enough to observe it, much less verify any possible fix. It might take many hours of constantly switching back and for to trigger it - Ross only saw it a few times after a whole day of testing, and Dino's suggested sequence did not trigger the bug for us either. I have also spent many days looking at all the relevant source code and can't find anything that would explain this. There's just nothing we can do with the information we have today. There are a couple ways we can proceed:

- If only a couple customers are experiencing this consistently, it could well be a problem with their particular hardware. If we could RMA one of those units I will personally look at it.

- If we can identify some other variable which causes this bug to become reproducible, then I can look at that case.

Also note this bug was originally opened against firmware version 27, which was long before the big TP firmware overhaul. The historical comments in this bug refer to many different, unspecified firmware revisions and as such are not very helpful, even contradictory. I'm re-targeting and re-prioritizing this bug until new information comes to light. 

Dino how frequently do you see this? As Sean says I try around 100 times or more before I see this. 

Reassigning to QA to monitor feedback and get a reproducible case.

Much less frequent than before the F40. Back then it was every time, I explained it in more details in those posts.

Thing is the device is never turned off and I switch in between PC input and Random Mix 5-10 times a day so it must happen at least once a week.
That's the catch, once a week is like what just happened, why no music. But since now we all tried it and it seems like all devices have it and it is impossible to fix I am fine with it.

I think that device malfunction was ruled out when you fixed 90% of the bugs from F40.I tried it now like 10 times and no hang.

I will be quiet and report only if there is a testable pattern.

With SC off and computer off and switching to digital no sound - reboot Transporter there is sound this happens 3 times in 5. Very annoying I do switch to digital inputs daily.
I am on a MAC running leopard SC version 7.2 
This as been a problem since new 17 months ago.
I like the concept of the Transporter and enjoy the sound the convenience of it and the facilities it offers (if said facilities are reliable). I hate to say this but if I had known it would  take this long to solve this bug I would have rejected it under the UK Sale of Goods Act as not being as described. To cap it all the RH display has now developed a fault.   

SqueezeCenter Version: 7.2 - 22774 @ Wed Aug 20 02:03:28 PDT 2008
Firmware: 62

I can reliably (100% of the time) reproduce this problem with my Transporter:

1. Play some music from my music library; everything works.

2. Select the Optical input; I get sound from my PS3.

3. Try to play some music from my library again; no music, but sound from PS3 continues to play. Counter on Transporter does not count down. Counter in SC web interface and counter on Controller both count down, indicating song is playing, but it's not. If I pause, the counters in SC web interface and Controller stop; if I hit play again, the sound from the optical input resumes, and the counters resume.

Note that toggling the Transporter power fixes the issue. It used to be that a reboot was required to fix the problem, so I suppose this is progress.

Also note that playing music before switching to the digital input is essential to reproducing the problem with 100% reliability; if I power on the Transporter and immediately select a digital input, then play some music, the problem doesn't always happen. (But if I switch back to the digital input, and THEN try to play music, I get the problem).

I'd be happy to send in my Transporter for analysis, as long as Sean promises to rub down the case with some sweat from his brow, as I've heard this can dramatically improve soundstaging, assuming of course that your interconnects are revealing enough... Someone drop me an email.

Could this just be an SC bug?

Big thanks to Terry for the reproduction steps, this is now consistently reproducible. 

1. Stream music from SC.
2. Shut off SC PC.
3. Use firmware to try to stream digital input, it doesn't work this is bug/symptom 1.
4. Reboot Transporter and firmware digital input now works.
5. Turn on SC PC and have Transporter reconnect to it, try to stream local music and it fails, Transporter is stuck streaming the digital input, this is symptom/bug 2. Rebooting Transporter resolves this. 

Again much thanks to Terry!

very good!  we additional noted that after reconnecting to the server, if you first select a digital input and _then_ try to play music, it works.

So this appears to be an issue of the server incorrectly assuming a some initial player state. In that case it should be an easy fix, and is unrelated to the original low-level firmware bug.

I am runnning V 7.3 of Squeezecenter on Vista Ultimate 64 bit and am having the same problem.  I find it very consistent.  When I power up the Transporter in the toslink mode (its usual state), my satellite radio works fine.  When I switch to my library using SC, the display shows the song selected, the meters are lit and not moving and the satellite radio continues to play.  In order to use SC, I have to power the unit on and off from the front panel.  This has been the case through the last few revisions of Squeezecenter and firmware upgrades.

Yeah, I sent in my Transporter for analysis (and it cost me like $60 for shipping, and I was without a Transporter for almost 3 weeks), and the replacement unit exhibits exactly the same problem described in my previous post. :(

Sean says this appears to be not a issue with Transporter hardware or firmware. Issue is in SqueezeCenter. SC makes some incorrect assumptions about the digital connection so when the Transporter is rebooted the player is initialized improperly.

See Sean for more details.

Fixed wrong behavior of TR when after using a digital input without SC and then connecting to SC it would still play from the digital input and not whatever has been selected from within SC. (Symptom 2 from comment 77)

I cannot however reproduce the other issue (Symptom 1 from comment 77).

The fix will be in SC 7.3 r23911 (no fw change needed - checked with TR fw 68).

I close this bug as I think it is resolved now. Please reopen if you still see something wrong, best with some description on how to reproduce. Thanks.

Customer still seeing this issue with 7.3 24108

I just downloaded and did a clean install of SqueezeCenter 7.3 rev 24108.  The problem is still there.  When I use the toslink input to listen to my satellite radio and want to listen to my music library SWITCHING FROM THE REMOTE OR TRANSPORTER FRONT PANEL the following occurs:

The display shows the cut from my library.
The meters turn on but don't react.
The satellite radio connected to my toslink input continues to play.
I power down the Transporter and restart it.
I go to my music library and it plays.

If I switch from my music library to the toslink connection and try to switch back to my library, the above occurs.

If I am listening to my music library and switch to the toslink connection, this works with no problem.  Switching back to the music library causes the problem.

 

Thanks for testing. Hmm, I've just retried your scenario with 7.3 r24117 and was _not_ able to see what you describe. Here is what I did:

1. TP not connected to SC, playing from toslink -> I hear music from toslink
2. Using the remote to switch from toslink to SC -> Music from toslink stops
3. Selecting something from SC music library -> I hear selected music from SC
4. Still connected to SC, I chose toslink -> I hear music from toslink
5. Again selecting from SC's library -> I hear SC music

The fix I added to SC is that when TP reconnects to SC any digital input that might still be selected is cleared. This means in above step 2 the music from toslink stops playing as soon as TP has reconnected to SC.

Could QA please try to reproduce. I obviously must miss something or do something different that I don't see the issue.

Thanks
Felix

I double-checked with SC 7.3 running under Linux, Mac and PC and with all three installations TP stopped playing from the digital input as soon as I connected to SC.

Linux, SuSE 10.2, SC 7.3 r24117
Mac, OSX 10.3.9, SC 7.3 r24106
PC, WinXP, SC 7.3 r24108

(In reply to comment #86)
> I double-checked with SC 7.3 running under Linux, Mac and PC and with all three
> installations TP stopped playing from the digital input as soon as I connected
> to SC.
> Linux, SuSE 10.2, SC 7.3 r24117
> Mac, OSX 10.3.9, SC 7.3 r24106
> PC, WinXP, SC 7.3 r24108

It behaves exactly as I said in comment 84.  When I have the toslink connection engaged and try to switch to my music library, everything switches EXCEPT the signal.  It continues to play music from the toslink connection.  Going FROM the music library to any of the digital connections works fine.  Once I do this going back from a digital input to the music library starts the cycle over again.  One additional thing.  I have found that I CAN switch among the digital inputs even when I can't switch between a digital input and the music library.

Ross: Can you verify this, talk with Felix about the bug if you need assistance.

A few observations switching to and from the digital inputs:

Yesterday: I had big trouble SWITCHING TO the digital inputs. I tried everything (turning off/on, selecting digital input from the built-in firmware menu, Xilinx reset and factory reset). Nothing helped. I just could not get any sound from the digital inputs. Gave up. After perhaps 30 minutes I tried the digital inputs again - and now it worked.

Today: Using the Transporter remote: it seems that I can SWITCH TO the digital inputs with no problems. It also seems that if I select to play an album I can switch FROM digital input to the music. But if I select a single track it continues to play the digital input sound. After trying to play a single track, it will NOT play an entire album, unless I go back and select the digital input again (although it is allready playing). After that I can select the album.

Today: Using the iPeng native on iTouch (digital inputs as favorites): it seems that I can switch without problems to digital inputs. Also I can switch from digital inputs to single tracks and albums with no problems. But if have tried switching from digital to single track on Transporter remote, I can not switch to music from iPeng. I have to select digital input again before beeing able to switch to music.

Tomorrow: who knows, it seems very unstable.........

Running SC Version: 7.3.1 - 24372 on Vista 62 bit.

Ongoing Ticket 080916-004425
Louis Berkman called in to Tier 1 speaking about comment 87.  He is still having issues.

Thanks,

LaRon

Now I can not switch to digital inputs anymore!!!

Ross: can you update the bug with the status of the problem since it's been reopened? Have you been able to reproduce?

I've not been able to reproduce this since comment #77. Louis, Nicolai, _how_ are you switching to digital inputs? Are you browsing to digital input from the home menu while connected to SqueezeCenter, or are you disconnecting from SqueezeCenter and selecting digital input from the player firmware? 

Could you please share the specific steps you follow to reproduce this? 

(In reply to comment #93)
> I've not been able to reproduce this since comment #77. Louis, Nicolai, _how_
> are you switching to digital inputs? Are you browsing to digital input from the
> home menu while connected to SqueezeCenter, or are you disconnecting from
> SqueezeCenter and selecting digital input from the player firmware? 
> Could you please share the specific steps you follow to reproduce this? 

I want to make one point clear.  When I control my  Transporter directly from SqueezeCenter on my computer, switching between the Music Library and Digital Inputs is no problem.  

The problem occurs when I try and use either the remote control or the front panel controls of the Transporter.  If I power te Transporter up in the Toslink mode to listen to my satellite radio, I can not switch into my music library manually.  When I use the remote or front panel controls to do this, the Transporter switches on the meters and says it is playing from my library.  What is actually heard is the radio on the toslink connection.  To make the input change, I need to power down the Transporter after having previously put it in the Music Library mode, power it back up and then using the remote or front panel controls go through music library, artists, song and then hit play.  One thing, when I go through this cycle, whatever song I had originally requested when it wouldn't switch becomes the default when going through the menu.

If I power up the Transporter in the music library mode, everything works correctly.  I can even switch from the music library to digital inputs.  Once I have done this and I try and switch back to the Music Library, I have to repeat the above steps again.

The problem occurs when trying to switch OUT of the digital input mode only.  There is no problem when trying to switch INTO the digital input mode from any other mode.

Am I correct in how I summarize your steps to reproduce this bug?

Precondition: Transporter is in off state, displaying the clock. It was streaming via a digital input before being powered off. 
1. Power on Transporter with either front panel button or remote control. 
2. Attempt to play local music, a file from your computer, via Music Library - Artists/Albums/Genre. 
3. The Transporter appears to be playing what you selected to play, but the audio you hear is actually from the digital input. 

Is this correct and complete?

Finally, when you select the digital input does the Transporter say "TRANSPORTER HOME" above digital inputs, or does it say "Transporter Setup (1 of  ..)"?

Ross, I actually am not using the digital inputs much at the moment, because - as I wrote - often I can not get any sound at all from the digital inputs. Today, or at least right now, I can swith to digital input:

1. Power on Transporter with either front panel button or remote control. 
2. Attempt to play digital input (sometimes I can, sometimes I can not)
Precondition: I hear the digital inputs:
3. Browse (by remote or frontpanel) to Music Library;
-- If I select single track the Transporter appears to be playing what I selected to play, but the audio I hear is actually from the digital input. From here I have to power the Transporter off and on to be able to play/hear the music
-- If I select an album the Transporter switch to play the album and I hear it

When I select the digital input the Transporter say "GETTING STREAM INFO....." until I goes into "NOW PLAYING" state.

I never tries to switch to digital input from the firmware menu (once or twice have tried when I can not hear any digital input at all, but it makes no difference). Also I rarely control my  Transporter directly from SqueezeCenter on my computer. But it seems that I can switch to and from digital input from my computer without problem.

Am I the only one sometimes not beeing able to switch TO digital input? Is this one or two problems/bugs? 

(In reply to comment #95)
> Am I correct in how I summarize your steps to reproduce this bug?
> Precondition: Transporter is in off state, displaying the clock. It was
> streaming via a digital input before being powered off. 
> 1. Power on Transporter with either front panel button or remote control. 
> 2. Attempt to play local music, a file from your computer, via Music Library -
> Artists/Albums/Genre. 
> 3. The Transporter appears to be playing what you selected to play, but the
> audio you hear is actually from the digital input. 
> Is this correct and complete?
> Finally, when you select the digital input does the Transporter say
> "TRANSPORTER HOME" above digital inputs, or does it say "Transporter Setup (1
> of  ..)"?

It says Transporter Home.

(In reply to comment #97)
> (In reply to comment #95)
> > Am I correct in how I summarize your steps to reproduce this bug?
> > Precondition: Transporter is in off state, displaying the clock. It was
> > streaming via a digital input before being powered off. 
> > 1. Power on Transporter with either front panel button or remote control. 
> > 2. Attempt to play local music, a file from your computer, via Music Library -
> > Artists/Albums/Genre. 
> > 3. The Transporter appears to be playing what you selected to play, but the
> > audio you hear is actually from the digital input. 
> > Is this correct and complete?
> > Finally, when you select the digital input does the Transporter say
> > "TRANSPORTER HOME" above digital inputs, or does it say "Transporter Setup (1
> > of  ..)"?
> It says Transporter Home.

I just tried the same thing switching from the digital inputs to an ALBUM in my music library.  This works fine.  The problem occurs ONLY when trying to switch from digital inputs to a specific song from an album in the library.

(In reply to comment #98)
> The problem occurs ONLY when trying to switch
> from digital inputs to a specific song from an album in the library.

Thanks Louis! The song level selection is the reproduction step I needed; I'm now able to reproduce this bug. More specific reproduction steps:

Transporter and SB3 connected to 7.3.2 - 24638, SB3 connected to digital input on Transporter. Play local music on SB3, select digital input from Transporter home menu, it works. With Transporter streaming digital input, browse music library - artist - album - play a song within an album, it fails. Transporter continues to stream the digital input, visualizers hang. 

Sean let me know if you cannot reproduce or if you would like a log. 

I'm still having this problem (can't play music after digital input has been used), and I'm also having the problem that I often can't play the digital input after having listened to music. Just now, when I selected the digital input nothing happened. Tried power cycling, same thing. Weirdly, when I tried to play music, the digital input came on!

This problem is pretty irritating, and has been going on for almost 2 years now. Can the severity perhaps be updated? It's basic functionality that's at issue here (with a $2000 piece of equipment, needless to say).

I completely agree with David. I have (almost or exactly) the same problem, that the digital input (as described earlier) sometime will not play at all. This is a basic functionality not woking proberly yet, and it is definately not a minor problem for me.

Perhaps not beeing able to switch to digital input is a "new" bug? Afterall this thread is about not beeing able to play music after having selected the digital input........

I agree with the last two contributors the severity is not minor.
Slimdevices did exchange my Transporter which I am grateful for as there was another issue, but the fault 
with the digital inputs remain.
This does cause me a great deal of annoyance which I did not expected with a £1300 device. Basically the Transporter does not perform as described.

I agree.

(In reply to comment #103)
> I agree.

Me too!!

Same problem. 
Same degree of severity. 
Same comment (this expensive device ought to work as advertised, and it does not...)

So frustrating. I feel like the problem has gotten worse over time (perhaps newer firmware versions and/or SqueezeCenter versions are making it worse). MOST of the time the digital inputs don't work (i.e., selecting a digital input after playing music has no effect). Sometimes even power cycling the unit doesn't fix it; I'll either have to power cycle several times, or do a full reboot.

Needless to say, this is one of those problems that makes the product completely unsuitable for the average user. I'm supposed to tell my wife that if she tries to watch a DVD and there's no sound, she has to turn off the Transporter (like she knows what this is) and turn it on; and if this doesn't work, try it again, and if this doesn't work, hold down the power button... And repeat if she wants to listen to music after watching a DVD?

It's gotten really embarrassing when company is over to have to fiddle with this thing to get the sound to work. This certainly makes a great advertisement for the product...

This has really gotten ridiculous. One can't help but think at this point that the tech people have given up on this problem. If this is the case, then I think some sort of substantial compensation for Transporter owners would be in order.

This whole thing also makes me feel ambivalent about Sean's participation in the public forums, which until now I have really appreciated and have usually found to be quite entertaining. Perhaps this is an unfair thing to say, but reading some of his posts lately I can't help but think, "Get off the freaking forums and fix your freaking product."

The Transporter is (presumably) Slim Device's flagship product. In terms of functionality you can't get more basic than playing music and switching among digital inputs. This functionality is broken. Please fix it. It's been almost 2 years.

(In reply to comment #105)

I just tried feeding a CD signal from my new Sony BDP-350 Blu-Ray player into my Transporter's Optical Digital Input. And it worked just fine.

But on the other hand, I was never able to get it working with my (rather old) Meridian 207 CD player.

So perhaps the issue is due somehow the age of the source device? I can imagine that older devices a) might support prior versions of the digital signal specifications, b) have slower edges on their digital signals, or c) have lower (or even higher) signal levels.

Did anyone look at this?

FWIW, I'm having this problem with a PS3 (even with the latest PS3 firmware). So I don't think it's the age of the source device that's the problem.

(In reply to comment #107)
> FWIW, I'm having this problem with a PS3 (even with the latest PS3 firmware).
> So I don't think it's the age of the source device that's the problem.

Particularly interesting since it works with a Sony Blu-Ray player but it does NOT work with a Sony Play-Station; -- so it is not even the name of the manufacturer that is at fault :-o

With the newest latest greatest this is how it works; You have to HAVE MUSIC PLAYING to be able to switch to the digital input, if the box is idle nothing happens. The same for switching back, signal must be coming from the transporter or it will lock up and not start playing music. Switching used to work when the music or the digital input was on pause, I liked this better, it was more intuitive to get used to. It still will not go back to playing regular 16/44 recordings after playing 24/96 without recycling, so I think all these issues are related and have to do with different bitrates and depths being in the buffer together and the systems inability to recognize that. Is the buffer cleared each time a new song or digital input is chosen?

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!

For information, I used the 7.2 Slimserver for months with the Transporter firmware 63, which resolved, for me, all issues when switching from or to the RCA digital input.
But I recently installed the 7.3, with Transporter firmware 75, and the problem reappeared, but not as worst as in the early versions. In this version I also have to play music (hitting the play button from the web interface, on the first artist) before hearing something from the RCA digital input. Once I did this, I can switch from or to RCA coax at will, and everything work perfect; I can ever switch off (soft or hard) the Transporter or my digital source (PC). But after switching off my PC and the Transporter (soft), and leaving them along for a day, I have to redo the same procedure as before to hear the RCA digital through the Transporter. Note that a hard reboot of the Transporter does not help.
Maybe something goes out of sync while the Transporter or/and the PC are powered off for a while...

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.

Felix: Can you take a look at this in Sean's absence?

This bug is now two years old and it is very annoying to lose sound when switching from SS to a digital input. One of my reasons for buying a transporter was it's advertised ability to  switch digital inputs. I feel that I have been very patient in wait for a solution.
I consider the unit is not as advertised and is therefore breaking the UK's Sale of Goods Act.

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.

Felix will have a look at this in the very near future

(In reply to comment #111)
> But I recently installed the 7.3, with Transporter firmware 75, and the problem

I finally found a way to reproduce the problem (at least 3 times in a row) for me, where there is no sound when the RCA coax digital input is selected.
There is the steps, all done through the web interface:
 - Play a music file (tested with MP3 or FLAC);
 - Click the pause button;
 - Click the standby button;
 - Wait a few seconds, the time to start playing somthing through the digital input (I do not know if it matter);
 - Select Digital input, then RCA/COAX (without clicking on the standby button): the Transporter is powered and displaying "Playing RCA...", but there is no sound;
 - Play a music file, using the "Play" mini button on the left side of the interface: the file is played correctly;
 - Select back the RCA/COAX: this time it works correctly.

Hope this helps...

Refers to Bug 4834.
I am using the BNC input for my satellite tuner and my DVD/SACD player.
It has worked 2 times (which means that my sources are OK), then nothing.
I have reset many times all that can be reset (Xilink, slimserver, PC).
I have updated the Slimserver to 7.3.3 26751 & the firmware.
I have tried every trick described in the bug report : the "play" button has worked, but only once.
I have uninstalled all the plugins.
Nothing...
Otherwise, WiFi works very fine, equal or better than my CD player.
As one of my reasons to buy a TP was to get a superlative DAC, I feel very disappointed,

"To nobody, except those who will take pleasure here" (Franz Schubert, 1797-1828)

I recently bought a transporter after buying a Duet a few months ago. I was disappointed about this bug, freezing after switching inputs. I decided to use my duet control, and wondered if I might have better luck with it switching rather than using the regular remote. It Works! I did report this to Logitech and they verified it also. They say they now can work toward a solution in an update. If you are lucky enough to have a Duet remote here is what to do. 

From e-mail sent to Logitech;
(I will tell you in detail how to repeatedly get the Duet remote to fire between digital inputs and transporter squeezecenter music everytime. On the Duet remote choose which ever you wish to start with, on the home list. Say music folder, then go into the subfolder until the desired album is shown, or song. Don't push select, (middle button), instead use the right arrow. It will 
start playing. Push the home key and go to digital inputs, right arrow, then say rca coax, then right arrow again. the digital input is then activated. Now home again, music folder, (or whatever), and right arrow when choosing. The secret seems to be selecting with the right arrow instead of the select on the Duet remote. At least this works on my unit. I just went back and forth twenty or more times to make sure I wasn't dreaming this up.)

This really works, and never locks up. Good Luck.

(In reply to comment #119)
Lucky man !
So I'd have to buy a Duet ...?

(In reply to comment #119)
> I recently bought a transporter after buying a Duet a few months ago. I was
> disappointed about this bug, freezing after switching inputs. I decided to use
> my duet control, and wondered if I might have better luck with it switching
> rather than using the regular remote. It Works! I did report this to Logitech
> and they verified it also. They say they now can work toward a solution in an
> update. If you are lucky enough to have a Duet remote here is what to do. 
> From e-mail sent to Logitech;
> (I will tell you in detail how to repeatedly get the Duet remote to fire
> between digital inputs and transporter squeezecenter music everytime. On the
> Duet remote choose which ever you wish to start with, on the home list. Say
> music folder, then go into the subfolder until the desired album is shown, or
> song. Don't push select, (middle button), instead use the right arrow. It will 
> start playing. Push the home key and go to digital inputs, right arrow, then
> say rca coax, then right arrow again. the digital input is then activated. Now
> home again, music folder, (or whatever), and right arrow when choosing. The
> secret seems to be selecting with the right arrow instead of the select on the
> Duet remote. At least this works on my unit. I just went back and forth twenty
> or more times to make sure I wasn't dreaming this up.)
> This really works, and never locks up. Good Luck.

(In reply to comment #121)
> (In reply to comment #119)
> > I recently bought a transporter after buying a Duet a few months ago. I was
> > disappointed about this bug, freezing after switching inputs. I decided to use
> > my duet control, and wondered if I might have better luck with it switching
> > rather than using the regular remote. It Works! I did report this to Logitech
> > and they verified it also. They say they now can work toward a solution in an
> > update. If you are lucky enough to have a Duet remote here is what to do. 
> > From e-mail sent to Logitech;
> > (I will tell you in detail how to repeatedly get the Duet remote to fire
> > between digital inputs and transporter squeezecenter music everytime. On the
> > Duet remote choose which ever you wish to start with, on the home list. Say
> > music folder, then go into the subfolder until the desired album is shown, or
> > song. Don't push select, (middle button), instead use the right arrow. It will 
> > start playing. Push the home key and go to digital inputs, right arrow, then
> > say rca coax, then right arrow again. the digital input is then activated. Now
> > home again, music folder, (or whatever), and right arrow when choosing. The
> > secret seems to be selecting with the right arrow instead of the select on the
> > Duet remote. At least this works on my unit. I just went back and forth twenty
> > or more times to make sure I wasn't dreaming this up.)
> > This really works, and never locks up. Good Luck.

(In reply to comment #119)
> I recently bought a transporter after buying a Duet a few months ago. I was
> disappointed about this bug, freezing after switching inputs. I decided to use
> my duet control, and wondered if I might have better luck with it switching
> rather than using the regular remote. It Works! I did report this to Logitech
> and they verified it also. They say they now can work toward a solution in an
> update. If you are lucky enough to have a Duet remote here is what to do. 
> From e-mail sent to Logitech;
> (I will tell you in detail how to repeatedly get the Duet remote to fire
> between digital inputs and transporter squeezecenter music everytime. On the
> Duet remote choose which ever you wish to start with, on the home list. Say
> music folder, then go into the subfolder until the desired album is shown, or
> song. Don't push select, (middle button), instead use the right arrow. It will 
> start playing. Push the home key and go to digital inputs, right arrow, then
> say rca coax, then right arrow again. the digital input is then activated. Now
> home again, music folder, (or whatever), and right arrow when choosing. The
> secret seems to be selecting with the right arrow instead of the select on the
> Duet remote. At least this works on my unit. I just went back and forth twenty
> or more times to make sure I wasn't dreaming this up.)
> This really works, and never locks up. Good Luck.

This works because the Duet remote is wi-fi based and communicates directly with SqueezeCenter.  When using the Transporter supplied remote, this problem continues to occur because this remote communicates throught the Transporter, NOT wi-fi.

Thanks for posting the workaround with the Controller, which I will try later on.  But as I often like to set this up via the front panel, as I load a CD, then it would be good to get this sorted.

I reported a similar problem to Logitech recently (handled und the title:  digital inputs not through to output ? [Incident: 090602-000055])

The transporter does not pass digital input from the digital interfaces to the digital output.

This was assigned a bug, but later removed from the bug list for unknown (to me).

Meanwhile, I have the same problem as Evert Smith (see below):  Synchronization with my digital cross over does not work, when playing 24/96 files (FLAC format). It works only after pulling the power cord and resetting the Transporter. Switching to 16/44 files works, but back to 24/96 fails => power plug;-(

When are we likely to get this bug fixed? It is most annoying March 2007 when it was first highlighted.

Adding the new director of software engineering to the cc list.

Felix: the current unreleased firmware has a fix for this, is it completely fixed now?

(In reply to comment #127)
> Felix: the current unreleased firmware has a fix for this, is it completely
> fixed now?
- Which version ? 7.3 or 7.4, and build ?
I would like to test on my side.

7.4 r27970 - look for Transporter firmware 80.

Feedback from Gartempe via email as he cannot login to bugzilla.



- Done today , with Version : 7.4 - r28035

It does not work, at least on my BNC input (had worked) : NO sound.

Regards,
Gartempe

Another failure then, is anyone working on this?  I did not spend all this money to have a defective device.
Present UK price £1799!!! 
 I would like to use the transporter as a pre amp for my other digital devices but this is now so painful.
Would you like to buy the device back and allow me to buy something that works?

(In reply to comment #131)
> Another failure then, is anyone working on this?  I did not spend all this
> money to have a defective device.
> Present UK price £1799!!! 
>  I would like to use the transporter as a pre amp for my other digital devices
> but this is now so painful.
> Would you like to buy the device back and allow me to buy something that works?

Same comment from here.

This thread started 2y 6m ago...
I'm afraid that the use of the TP as a DAC is rare, unless it works everywhere except a few of us who meet here ?

Agreed. Logitech has to stop releasing new products and new minor features until the basic functionality of what is supposed to be its flagship product is fixed.

this is an administrative shuffle on priority fields to help make better judgment on the top end of the priority list. P4->P5, P3->P4, and P2->P3.

OK so now the priority has been down graded. 

 I will therefore be taking up this issue with the UK Trading Standards and Consumer Direct. This is not acceptable for a £1700 device. This is a design fault that existed from new and was reported as such.

The Transporter does not do this without a reboot:

From your Manual.

Using Transporter as a Standalone DAC
You can use Transporter as a standalone digital-to-analog converter (DAC) to convert S/PDIF or AES/EBU signals
from a CD player or other digital source to analog for connection to an amplifier or preamp.
When not connected to SlimServer or SqueezeNetwork (you will see Transporter Setup on the top line of the
display), use the remote control or knob to scroll to the digital input you’d like to use then press the right arrow
button, the center of the knob or the PLAY button. That input will remain selected until you choose another or
connect to SlimServer or SqueezeNetwork.
If Transporter is connected to SlimServer or SqueezeNetwork, scroll to the Digital Inputs menu, go right, then press
PLAY to use the selected input.

---It worked---
when Sean Adams was there
and before Slim Devices became eaten by Logitech.
This company does not take care of the TP, although it is still on their catalog and ads.
Too expensive to do that ?
---It worked---

I have a QA engineer working to reproduce this issue currently.  He and our support team are communicating via email with some of you.

The information we're interested in at the moment includes:

* What inputs on the Transporter are you using?  AES/EBU, and SPDIF only?  XLR as well?
* What devices are you feeding the Transporter with?  That is, what's connected to the other end of the wires?
* Are all the streams PCM that you are using the Transporter as a DAC?  Or are some of them digital (AC-3, DTS) and you are using the transporter more like a switch?

(In reply to comment #137)
> I have a QA engineer working to reproduce this issue currently.  He and our
> support team are communicating via email with some of you.
> The information we're interested in at the moment includes:
> * What inputs on the Transporter are you using?  AES/EBU, and SPDIF only?  XLR
> as well?
> * What devices are you feeding the Transporter with?  That is, what's connected
> to the other end of the wires?
> * Are all the streams PCM that you are using the Transporter as a DAC?  Or are
> some of them digital (AC-3, DTS) and you are using the transporter more like a
> switch?

I am using the following digital inputs:  toslink for a Kenwood DT-7000S satellite tuner and coax for Pioneer dvd/cd player.  Both of these are standard pcm configuration.

(In reply to comment #137)
> I have a QA engineer working to reproduce this issue currently.  He and our
> support team are communicating via email with some of you.
> 
> The information we're interested in at the moment includes:
> 
> * What inputs on the Transporter are you using?  AES/EBU, and SPDIF only?  XLR
> as well?
> * What devices are you feeding the Transporter with?  That is, what's connected
> to the other end of the wires?
> * Are all the streams PCM that you are using the Transporter as a DAC?  Or are
> some of them digital (AC-3, DTS) and you are using the transporter more like a
> switch?

1. SPDIF both optical (for tuner) and coax (CD player). No others
2. tuner (digtal TV actually, using radio part) and CD (SACD) player
3. All PCM
Transporter does the D/A conversion, the analog ouputs feed my amplifier.

1. SPDIF only (optical)
2. PlayStation 3
3. PCM only, using (or rather trying to use) Transporter as DAC

- PCM from satellite TV or DVD player
- Only S/PDIF BNC input.
- Only analog output.

DVD player - RCA Coax

Satellite - Toslink

Both PCM

Output - XLR analog

Meridian 208 CD Player
Toslink and/or RCA
PCM using Transporter as a DAC

* I exclusively use the RCA/Coax SPDIF.
* My Transporter is connected to a PC.
* There is only PCM streams (Transporter used as a DAC).

Good lord -- could it really be??? This problem seems to be fixed, for me, with the official 7.4 release and accompanying firmware. Anyone else?

Hey Gordon, thanks for the feedback. It's good to hear it works for you.

I meant "Hi David". Sorry about that.

Looks like we are making progress. I am not closing the bug just yet until we hear more.

Moving target as 7.4.0 is out in the wild.

I just finished installing 7.4 and wonder of wonders, the music library/digital switching appears to work.  I will give it my final blessing after I play with it for awhile.

(In reply to comment #148)
> Looks like we are making progress. I am not closing the bug just yet until we
> hear more.
> 
> Moving target as 7.4.0 is out in the wild.

Unfortunately no improvement here.
Either with 7.4.0 or with 7.4.1/r28791
And firmware upgrade each time.
And reset.
And so on...

Seems to have solved the problem for me.



 From mobile device

On 7 Oct 2009, at 21:40, bugs@bugs.slimdevices.com wrote:

> https://bugs-archive.lyrion.org/show_bug.cgi?id=4834
>
>
>
> --- Comment #150 from gartempe <235lcijmb@orange.fr> 2009-10-07  
> 13:40:48 PDT ---
> (In reply to comment #148)
>> Looks like we are making progress. I am not closing the bug just  
>> yet until we
>> hear more.
>>
>> Moving target as 7.4.0 is out in the wild.
>
> Unfortunately no improvement here.
> Either with 7.4.0 or with 7.4.1/r28791
> And firmware upgrade each time.
> And reset.
> And so on...
>
> -- 
> Configure bugmail: https://bugs-archive.lyrion.org/userprefs.cgi? 
> tab=email
> ------- You are receiving this mail because: -------
> You are a voter for the bug.

Switching to Digital inputs on 7.4 FW80 now works for me although the Transporters volume is automaticaly reduced when switching in my case to -37.5. Not sure if this is why the last respondent is seeing no improvement, indeed I only notice it was playing when using headphones and hearing very faint sound.

(In reply to comment #152)
> Not sure if this is why the last respondent is seeing no improvement, indeed I
> only notice it was playing when using headphones and hearing very faint sound.
It's me.
I have set (and checked) the maximum output level.
Idem for the source.

Not sure if we mean the same thing.
 I mean the actual volume control of the Transporter not the digital source, that is increase the volume on the Transporters Remote. On my Transporter after I have switched to a digital source the Transporters volume has been reduced by about 2 thirds requiring me to increase the volume using the volume control on the Transporters remote. Hope this makes sense and is of help.

(In reply to comment #154)
> Not sure if we mean the same thing.
>  I mean the actual volume control of the Transporter not the digital source,
> that is increase the volume on the Transporters Remote. On my Transporter after
> I have switched to a digital source the Transporters volume has been reduced by
> about 2 thirds requiring me to increase the volume using the volume control on
> the Transporters remote. Hope this makes sense and is of help.

Yes, what you are reporting had happened to me a long time ago (v 7.3?): I had to readjust the TP volume control to make it work.
IMHO we are returning to this state, except it still does not work here in my setup.

Terry: Am I correctly assuming that you are using digital inputs w/o being connected to SC or SN?

If yes, is the volume always reset to -37.5 when switching to digital input or does that only happen the first time? What I mean is when you adjusted digital input volume then reconnect to SC to stream something and then disconnect from SC again and use digital input is the volume reset to 37.5 again or is it at what you left it?

Thanks
Felix

Felix 
With SC running I can switch between streaming and digital inputs without adjusting the volume.
If I last used the TP for streaming then switch the computer (SC) off and later with SC still off change to a digital input  then the volume will need to be reset. Hope this is clear.

(In reply to comment #157)

> If I last used the TP for streaming then switch the computer (SC) off and later
> with SC still off change to a digital input  then the volume will need to be
> reset. Hope this is clear.

That sounds like it could be a SqueezeNetwork (integration) issue.  There are some reports in the forums of unexplained audio adjustments happening to players since the new SN implementation.

Terry: Thanks for the feedback. Volume setting is separated for when connected to SC / SN or when disconnected. So what you are seeing is expected, i.e. volume setting when connected / disconnected from SC are _not_ synchronized.

That said, volume setting when disconnected from SC / SN should be the same when you come back using digital inputs in offline state again.

Are you saying volume is reset to -37.5 every time you use digital inputs when not connected?

Thanks
Felix

Felix

Only if the TP was last left streaming from SC and the SC switch off. The next time the TP is used with SC still off  a switch to digital would mean the volume would drop to -37.5. If it was already switched to digital then there would be no volume reset required. 

I think it is working now as you seem to expect.

(In reply to comment #159)
> Terry: Thanks for the feedback. Volume setting is separated for when connected
> to SC / SN or when disconnected. So what you are seeing is expected, i.e.
> volume setting when connected / disconnected from SC are _not_ synchronized.
> 
> That said, volume setting when disconnected from SC / SN should be the same
> when you come back using digital inputs in offline state again.
> 
> Are you saying volume is reset to -37.5 every time you use digital inputs when
> not connected?
> 
> Thanks
> Felix

Here, when SC is off, volume is reset to -37.5 dB everytime I TRY to use digital inputs. But not even a faint sound, anyway.

(In reply to comment #161)
> Here, when SC is off, volume is reset to -37.5 dB everytime I TRY to use
> digital inputs. But not even a faint sound, anyway.

What is your source and how are you connecting the two? Have you reproduced this with more than one source or via more than one type of cable?

(In reply to comment #162)
> (In reply to comment #161)
> > Here, when SC is off, volume is reset to -37.5 dB everytime I TRY to use
> > digital inputs. But not even a faint sound, anyway.
> 
> What is your source and how are you connecting the two? Have you reproduced
> this with more than one source or via more than one type of cable?

1- Satellite TV tuner, RCA-S/PDIF to BNC.
2- I have just added : DVD/SACD Pioneer, RCA to RCA.
You were right : there was a cold solder joint in a RCA connector (BNC rules, anyway).
Ma

(In reply to comment #163)
> 1- Satellite TV tuner, RCA-S/PDIF to BNC.
> 2- I have just added : DVD/SACD Pioneer, RCA to RCA.
> You were right : there was a cold solder joint in a RCA connector (BNC rules,
> anyway).
> Ma

Not sure I understand exactly, were you able to determine a problem with a cable? As far as I can tell you're the last person still seeing this bug. I would like to resolve this bug if possible.

(In reply to comment #164)
> Not sure I understand exactly, were you able to determine a problem with a
> cable? As far as I can tell you're the last person still seeing this bug. I
> would like to resolve this bug if possible.

Yes : the cold solder joint was on my cable connector. Now it is fixed, and TP works as expected.
BTW it would be interesting to be able to rename the inputs according to the sources, so the TP would look more user friendly.
Best regards.

Awesome! Does anyone out there feel this bug should remain open? If so please share details about your setup. I think most of us agree we would like this bug to come to an end. 

(In reply to comment #165)
> BTW it would be interesting to be able to rename the inputs according to the
> sources, so the TP would look more user friendly.
> Best regards.

Feel free to file an enhancement request bug for any feature you are interested in, they will be evaluated and considered.

Moving these bugs to P4 to make room for moving P1.5 bugs to P2

Administrative move of 7.5 bugs. All P2, P3, P4 being downgraded one level. Will then split P1s.

I take 3 months of silence as a good sign this bug has been fixed (at least for now). Please reopen if you still (again) find an issue regarding switching digital inputs.

Thanks
Felix

This bug has been marked fixed in a released version of Squeezebox Server or the accompanying firmware or mysqueezebox.com release.

If you are still seeing this issue, please let us know!