Using
yum check-update
The following updates are shown:
perl-URI.noarch 1.54-1.fc11
squeezeslave.i586 0.9.155-1
vortexbox.i586 1.3-6
vortexbox-player.i586 0.9-1.fc11
I used Ron Olsen’s instructions to manually install squeezeslave 0.9.155 and SqueezeBox Server (SBS) v 7.5.1 and they work well.
1. Will SBS v 7.5.1 be preserved using the
GUI Upgrade to get VortexBox version 1.3-6?
2. Does vortexbox-player v 0.9-1 fix its inability to synchronize?
Any manual changes "hacking" can cause all knids of problems includeing upgrades not working or thing breaking during upgrades. Make sure you know the ramification of any manual changes to you make to your VortexBox.
JimG said:
Using
yum check-update
The following updates are shown:
perl-URI.noarch 1.54-1.fc11
squeezeslave.i586 0.9.155-1
vortexbox.i586 1.3-6
vortexbox-player.i586 0.9-1.fc11
I used Ron Olsen’s instructions to manually install squeezeslave 0.9.155 and SqueezeBox Server (SBS) v 7.5.1 and they work well.
1. Will SBS v 7.5.1 be preserved using the
GUI Upgrade to get VortexBox version 1.3-6?
yum check-update shows what would be installed if you did an upgrade via the VB GUI or via "yum clean all; yum update". Since you don't see any update to squeezeboxserver, you can be assured that the update won't affect SBS 7.5.1.
2. Does vortexbox-player v 0.9-1 fix its inability to synchronize?
vortexbox-player-0.9-1 is a first attempt at fixing the sync problem. It does work syncing with Logitech hardware players, on FLAC, mp3, and Internet radio streams.
Unfortunately, this version has a serious bug that causes the player to fail when trying to advance to the next track (FLAC and mp3 playback) even when it is not synced. Thus this version of the player is only usable on Internet radio streams and not on local FLAC or mp3 albums. I recommend NOT upgrading vortexbox-player until this track advance problem is fixed.
Also, it appears that you have downgraded to squeezeslave 0.9.133, since the 0.9.155 version is shown in the yum check-update list.
If you want to update everything except vortexbox-player, you can do
[b]
Andrew said:Any manual changes "hacking" can cause all knids of problems includeing upgrades not working or thing breaking during upgrades. Make sure you know the ramification of any manual changes to you make to your VortexBox.
Hi Andrew,
I doubt that you intended your response to be as unsupportive and off-putting as it comes across. It is extremely offensive.
Your use of the term “hacking” is unfortunate and in my opinion demeans the excellent support and advice provided by your expert customers, like Ron Olson, to customers whose supported upgrades cause problems on their VBAs. That assistance is not “hacking” in any generally-accepted context.
The reason for “hacking” in this case was to correct errors in the upgrade from the formally-announced version 1.3 and subsequent bug corrections in VortexBox version 1.3-4 to version 1.3-5. My post asks, “Please list and describe changes in VortexBox version 1.3-6.”
Knowing what files were changed and knowing the reason for those changes will allow your customers, like me, to better-understand if version 1.3-6 may contain corrections to the bugs introduced by version 1.3-5. I performed the two “hack” commands Ron Olson suggested. They fixed the bug. I then posted the results on this forum for all your customers to benefit.
- You did not list and describe changes
in VortexBox version 1.3-6.
- You did not answer if SBS v 7.5.1 be preserved
using the GUI Upgrade to get VortexBox version 1.3-6
- You did not answer if vortexbox-player
v 0.9-1 will fix its inability to synchronize
While you fail to answer the direct question here, you send to those of us who subscribe the notice:
We now have sync support in VortexBox Player. You can sync VortexBox player to hardware players. Please help us test out this new feature. Update your VortexBox using the Update manager. Sync another player to VortexBox player and see if syncing works for you.
By what method may your customer, me, know the ramification of a manual change to VortexBox when you refuse to describe changes in upgrades you post. I know of no significant application, except VortexBox, where there is an upgrade feature on the user control level (the icon) and there is no means whereby the customer can know if using that control will provide an upgrade, what that upgrade contains, or the purpose of that upgrade.
You may not have realized that your response creates the impression that any VortexBox user that uses any command to correct any bug will forevermore be unable to use the GUI Upgrade feature with your assistance. Please either answer the questions in a way that is supportive of your customers, or suggest a means whereby your customers can take advantage of suggestions that restore the functions that have been damaged by previous upgrades.
Alternatively, since I have used Ron Olsen’s “hacks” to restore function to my VBA, and since I want to be able to install future upgrades, if I download the ISO posted here, burn that ISO to a CD, copy all of the media files to another disk, borrow a keyboard and display to attach to the VBA, and re-create the VBA, and copy the media files back to the VBA, what version of VortexBox will I have? Will the VBA then be immune from all kinds of problems including upgrades not working or things breaking during upgrades?
Do you understand that if your customers do not perform the “hacks” suggested by experts on this forum that you will not get the feedback needed for you to fix the bugs in the next release?
Ron Olsen said:
JimG said:
Using
yum check-update
The following updates are shown:
perl-URI.noarch 1.54-1.fc11
squeezeslave.i586 0.9.155-1
vortexbox.i586 1.3-6
vortexbox-player.i586 0.9-1.fc11
I used Ron Olsen’s instructions to manually install squeezeslave 0.9.155 and SqueezeBox Server (SBS) v 7.5.1 and they work well.
1. Will SBS v 7.5.1 be preserved using the
GUI Upgrade to get VortexBox version 1.3-6?
yum check-update shows what would be installed if you did an upgrade via the VB GUI or via "yum clean all; yum update". Since you don't see any update to squeezeboxserver, you can be assured that the update won't affect SBS 7.5.1.
2. Does vortexbox-player v 0.9-1 fix its inability to synchronize?
vortexbox-player-0.9-1 is a first attempt at fixing the sync problem. It does work syncing with Logitech hardware players, on FLAC, mp3, and Internet radio streams.
Unfortunately, this version has a serious bug that causes the player to fail when trying to advance to the next track (FLAC and mp3 playback) even when it is not synced. Thus this version of the player is only usable on Internet radio streams and not on local FLAC or mp3 albums. I recommend NOT upgrading vortexbox-player until this track advance problem is fixed.
Also, it appears that you have downgraded to squeezeslave 0.9.133, since the 0.9.155 version is shown in the yum check-update list.
If you want to update everything except vortexbox-player, you can do
yum update perl-URI squeezeslave vortexbox
to pick up the other packages.
Thanks Ron,
Clear, complete, and very helpful.
I really appreciate your assistance.
Regarding the title of this thread, here's what's new in vortexbox-1.3-6:
1. Improved support for subsonic in the /opt/vortexbox/package-scripts/install-subsonic.sh script.
2. Support for minidlna via the /opt/vortexbox/vbcleanup.sh script.
It should be safe to upgrade to this version without fear of breakage of core functionality.
Hi Jim
I can understand the frustration here, the user experience post sales has been raised in previous threads, the main concerns being
- No way of tracking feature requests
- No bug tracking
- Insufficient documentation on releases/upgrades
- Insufficient Beta testing of new features, again highlighted by the sync feature having issues, this shouldn't come through to the general user group like this and should go through Beta testing.
Ron is heavily involved in keeping the user community afloat and providing a lot of fixes for people, if Ron was to leave this project then I think it would grind to a halt.
Andrew - In terms of "hacking", not sure I follow that through as hacking - you are using open source free software within vortexbox and therefore users are free to look at certain areas (e.g. changing the default folder structure for ripping), people would see these as enhancements rather then hacking, also your customers are looking to do this via this route as they have no mechanism to suggest features/track bug requests - I would be careful on using this term unless you want to lock down your product and not be open source anymore....
Vortexbox is a great product, but it is a commerical product and this user support post sale isn't satisfactory IMO, I for one have held back on providing as much user support/promoting the product in recent weeks for this reason.
ian
Ron Olsen said:
Regarding the title of this thread, here's what's new in vortexbox-1.3-6:
1. Improved support for subsonic in the /opt/vortexbox/package-scripts/install-subsonic.sh script.
2. Support for minidlna via the /opt/vortexbox/vbcleanup.sh script.
It should be safe to upgrade to this version without fear of breakage of core functionality.
Hi,
UPDATE:
I did do the GUI Upgrade because I want to stay current and be able to contribute to VortexBox (VB) testing and development. Before doing it, I noticed that Andrew had pulled VortexBox-Player (VBP) version 0.9-1 and that the VortexBox version remained at 1.3-6.
Because VBP is now an integral part of VB, may I suggest that when VBP changes, the version number of VB should change also, just to allow understanding possible consequences. E.g., some customers may have upgraded to the "-1″ VBP that will not advance from track-to-track, and may be at least confused if they have not read all the traffic on this forum. A change log would also allow customers to understand.
Mostly I report that my GUI Upgrade to VB version 1.3-6 appeared to go smoothly, yet after the reboot, the initial screen, with the icons to the left worked, but clicking the SqueezeBox Server (SBS) icon did not bring up SBS. It was necessary to click the Restart SBS iconto access SBS.
Hope this helps others who may run into the SBS bug or wonder why VBP will not play more than one track from their flac or MP3 albums or playlists.
SqueezeBox Server requires a minute or two for the web GUI to become accessible after a restart; maybe you were running into this.
Are you sure SBS was not running when you tried to access it? Did you do a "service squeezeboxserver status" before clicking the "Restart SBS" button?
I'd be surprised to find that SBS was not started on reboot, or that the startup failed. It's worth looking at your log files (/var/log/messages and /var/log/squeezeboxserver/server.log) to see what was going on when you rebooted. If SBS did fail to start, or crapped out shortly after starting, it's worth trying to figure out why.
A few months ago there was a big thread about documentation and everybody decided we should have a wiki that the community could edit. I spent quite a bit of time putting one together and to date only Ron and myself have posted anything to it.
VortexBox is a community. Unfortunately I don't have time to run the entire project myself. if you want a bug tracker create a page for it in the wiki for one. If you want feature requests create one. If you have some time please update the documentation as much as possible. Thanks.
http://info.vortexbox.org/tiki-index.php
Posting Permissions
Reply With Quote
Bookmarks