Bugzilla – Bug 13901
Line In Applet (also make sure line in option appears at startup)
Last modified: 2010-05-27 14:46:37 UTC
When line in enabled: -Override listeners so line-in is used instead of local player -Override now playing to show a fixed line-in -Turn line-in off if local player play state changes to "play"
== Auto-comment from SVN commit #7453 to the jive repo by bklaas == == https://svn.slimdevices.com/jive?view=revision&revision=7453 == Bug: 13901 Description: create a 143x143 line in icon for use in pseudo-NP screen create an icon_linein icon style to the QVGAbase skin alter resize_master_icons script to always create this icon
== Auto-comment from SVN commit #7473 to the jive repo by richard == == https://svn.slimdevices.com/jive?view=revision&revision=7473 == Bug #13901 Add independant capture gain.
== Auto-comment from SVN commit #7482 to the jive repo by tom == == https://svn.slimdevices.com/jive?view=revision&revision=7482 == Bug: 13901 + 12 Fixed Bug: 13863 - full local line-in support - separate line in volume control, line in np screen, pause regular audio on line-in switch, transition to regular playback when local or remote play of regular content is selected, persistent volume, line in playback state, re-enable line in playback state on startup - local only pause on power off to support player sync.
Current Status (ran into a "need Matt Weldon" situation towards the end) Complete: - Manually enabling Line In (after inserting the cable) takes you to a static Line In NP screen, with statusbar. Also, regular playback is paused. You can navigate menus as usual. Any attempt to go to NP or the current playlist will take you to this Line In NP window. - Line In can be paused (actually muted behind the scenes currently) via pause, mute or stop. line in can be resumed via pause play or mute - Playing a regular item via SP or a remote interface like the web UI will cancel Line In playback. - Line in volume and enabled state and play mode (pause, play) are persisted, so that when SP restarts, Line In will restart automatically in the mode that it was in (play pause) when SP was shut down (Note: the auto restart functionality is waiting for bug 13930 to be fixed). This auto-enabling of Line In only occurs if a cable is plugged in. - The statusbar will show the Line In play state, either play or pause - Line In uses a separate volume than regular playback. All volume functions act on the currently active source (line in or "regular playback"). So regular volume can be at different level than line in volume. Uncertain: - Matt, I left the top level "checkbox" to enable/disable Line In. Richard had suggested that this should just be a menu item that enables Line In and shows the NP window, but that gives no means to manually disable the Line In directly. We could have it so that a) pause or stop switches back to regular playback, but then you lose the benefit of being able to quickly stop and resume line in. Also, you can get back to regular playback by playing some regular content, but then you would lose the regular playback playlist that you had prior to selecting line in. For these reasons I think the we need to maintain a manual on/off choice, whether it be a checkbox or some other ui way. - We give the user a showBriefly visual indicator that Line In is plugged in, but give them no clue how to actually start using it. My suggestion is that a) upon insertion, we switch the user to point them to the Line In selection choice, so they immediately see how to enable it. Currently there is just a checkbox item in the home screen. I suggest we make a top level (or under settings) "Line In" home menu item, which inside contains the check box (or radio selector or menu choice) and bring the user automatically into this menu when line in is plugged in.
== Auto-comment from SVN commit #7503 to the jive repo by tom == == https://svn.slimdevices.com/jive?view=revision&revision=7503 == Bug: 13901 +1 Fixed Bug: 13863 - reading line in switch must happen during applet configure stage.
Here is the current behavior for the Boom, FWIW (I needed to catch up, maybe others will find this useful as well): - ALWAYS AVAILABLE: whether a line in is detected or not, the following options are always available in settings -> audio: - line in always active (contains two radio button options: "on" and "off." "off" is the default. If "on," the line in is literally always on, and the boom acts as an audio mixer, so you can have internet radio and line in playing over each other at the same time.) - line in level (default is 50 out of 100 I think) - LINE IN CONNECTED: when something is plugged in to the "line in" jack (it could just be the cable; no audio needs to actually be coming through the jack): - if something else is playing, it stops immediately; - a new menu item named "line in" appears in the main menu (it has one item inside it, which is just a text label named "Line in is active"); - "line in" also appears in the current playlist; - the user is instantaneously taken to the "line in" item in the current playlist; - any audio coming through the "line in" cable immediately starts playing through the speakers. In addition: - the user is free to navigate elsewhere and play something else instead (I was able to go to internet radio and play something else) - returning to the "line in" option on the home menu instantly switches back to "line in" - transport controls do NOTHING. The only on-device audio controls that work when "line in" is being used is the volume.
- on Boom, switching to "line in" happens automatically, not manually. When I plug in the cable, the switch happens. I think this is the correct behavior and we should keep it. (A side effect of this is that we won't need the line-in showbriefly when a cable is connected/disconnected) > Complete: > - Manually enabling Line In (after inserting the cable) takes you to a static > Line In NP screen, with statusbar. Also, regular playback is paused. You can > navigate menus as usual. Any attempt to go to NP or the current playlist will > take you to this Line In NP window. This is correct, but of course I feel it should happen automatically, not manually > - Line In can be paused (actually muted behind the scenes currently) via pause, > mute or stop. line in can be resumed via pause play or mute This is new behavior that the Boom doesn't have, but I think it makes sense. > - Playing a regular item via SP or a remote interface like the web UI will > cancel Line In playback. Yes > Uncertain: > - Matt, I left the top level "checkbox" to enable/disable Line In. Richard had > suggested that this should just be a menu item that enables Line In and shows > the NP window, > but that gives no means to manually disable the Line In > directly. We could have it so that a) pause or stop switches back to regular > playback, but then you lose the benefit of being able to quickly stop and > resume line in. Also, you can get back to regular playback by playing some > regular content, but then you would lose the regular playback playlist that you Let's leave the checkbox (though actually it needs to be a toggle between the strings "on" and "off", not a checkbox). It will be "on" by default as soon as the user attaches a cable. Manually switching it off or playing another audio source will toggle this into the "off" position. ----- Finally, we need to add the "line in always on" and "line in level" options back into settings -> audio settings. ----- So for the most part I like everything we're doing, except that turning on "line in" should be an automatic, not manual, action that happens as soon as a cable is connected (like the Boom).
== Auto-comment from SVN commit #7645 to the jive repo by tom == == https://svn.slimdevices.com/jive?view=revision&revision=7645 == Bug: 13901 - Line-in autoactivates on plugin - Line in doesn't stop on a server restart (which send a stop command on restart) - Don't show line-in icon anymore since we auto-active and jumpt o Line In NP screen
Matt I've made all the changes except: -Finally, we need to add the "line in always on" and "line in level" options back into settings -> audio settings. I'm not sure what "line in always on" means. The checkbox defines whether its on or not. We currently don't have the ability to mix line-in with regular audio, if that's what that means. Also, the regular volume control switches to line in volume mode when you plug in line-in, so do we really need a separate volume menu (for 7.4)?
== Auto-comment from SVN commit #7657 to the jive repo by tom == == https://svn.slimdevices.com/jive?view=revision&revision=7657 == Bug: 13901 - Don't show connecting to server screen when plugging in line-in when server is down.
(In reply to comment #9) > Matt I've made all the changes except: > -Finally, we need to add the "line in always on" and "line in level" options > back into settings -> audio settings. > > I'm not sure what "line in always on" means. The checkbox defines whether its > on or not. We currently don't have the ability to mix line-in with regular > audio, if that's what that means. Yeah, that's what it means. I was asking for it because Boom had it. No problem. > > Also, the regular volume control switches to line in volume mode when you plug > in line-in, so do we really need a separate volume menu (for 7.4)? I could see an argument both ways. Having the persistent volume allows you to lower volume before plugging in audio, but I agree it's an extemely minor feature. We'll see if anyone complains about not having it.
This bug has been marked as fixed in the 7.4.0 release version of SqueezeBox Server! * SqueezeCenter: 28672 * Squeezebox 2 and 3: 130 * Transporter: 80 * Receiver: 65 * Boom: 50 * Controller: 7790 * Radio: 7790 Please see the Release Notes for all the details: http://wiki.slimdevices.com/index.php/Release_Notes If you haven't already, please download and install the new version from http://www.logitechsqueezebox.com/support/download-squeezebox-server.html If you are still experiencing this problem, feel free to reopen the bug with your new comments and we'll have another look.
These bugs have all been marked resolved and belong to a component which is being removed. Therefore they have been moved to the most applicable of the new components.