dolodobendan wrote:
> I did a restart and now with the official release it updated to 7.9.2.
> The nightly 7.9.1 (April) -> official 7.9.1 (March) -> nightly 7.9.2
> (April) routine is a bit confusing (having to run the updater twice due
> to the "official detour"). But it worked, that's what mat
Michael we can not thank you enough, for al the great work.
So i make a deep bow for you're work and effort.
Thanks you make a lot off people very happy.
mherger wrote:
> Today I released Logitech Media Server 7.9.1 as the stable community
> release. It's full of small tweaks and bug fixes to im
it a few minuts, before you try to access
the webgui through http://X.X.X.X:9001!
So i you can see, it does run the upgrades correctly.
But as Michael wrote here, there is a problem on the LMS side.
digimaster wrote:
> Oké have to look into this. And try to
dolodobendan wrote:
> I restartet QLMS, but it did not install 7.9.2 despite
>
> >
Code:
> >
> UPDATE=1
> NIGHTLY=1
>
> >
>
> >
Code:
> >
> [22:09:26 19-04-2018] Stopping LogitechMediaServer [4153] in the Backg
dolodobendan wrote:
> I restartet QLMS, but it did not install 7.9.2 despite
>
> >
Code:
> >
> UPDATE=1
> NIGHTLY=1
>
> >
>
> >
Code:
> >
> [22:09:26 19-04-2018] Stopping LogitechMediaServer [4153] in the Backg
Oke try this, logon to you're Qnap by ssh shel.
Then do [ cd /share/*/.qpkg/LogitechMediaServer ], [
./LogitechMediaServer.sh stop ]
Now do [ mv SlimServer/Cache SlimServer/Cache-org/ ], [ chmod -R 0755
SlimServer/ ], [ chown -R squeezeboxserver SlimServer/ ]
And then [ ./LogitechMediaServer.sh re
dolodobendan wrote:
> Yes, but I bookmarked the 'changelog page'
> (https://www.qnapclub.eu/nl/qpkg/releasenotes/545). There's no download
> button there and no (simple) way to get to the main page with the
> download button. The bread crumbs are broken. But of course, nobody
> forced me to bookm
dolodobendan wrote:
> I don't think there was one. But I sometimes check 'here'
> (https://www.qnapclub.eu/nl/qpkg/releasenotes/545). For some reason
> there's no easy way to get the download links there (bread crumb (Home
> -> QLogitechMediaServer) does not work) or get to the 'main site'
> (htt
It now has support for i*86 also, so should work now !
janus wrote:
> Sorry I didn't check with uname -m and it appers that my QNAP is not
> supported by your package... ;-( Maybe can you make it available in the
> future? Thank you very much!
*
maintainer of QLogitechMediaServer, QOptware-N
The latest version is v1.07.4, which has a lot off fixes regarding
serval issue's.
'QLogitechMediaServer v.107.4' (https://www.qnapclub.eu/nl/qpkg/545)
If you still have trouble, try this
Logon to you're Qnap by ssh shell.
Then do [ cd /share/*/.qpkg/LogitechMediaServer ], [ chown -R
admin:admin
QDon wrote:
> Did a Teamviewer session with QNAP this morning. They removed the 'root'
> user rebooted and Q'center now works. It connects to itself and my other
> QNAP NAS. After they disconnected the session I reinstalled LMS. Guess
> what? LMS is working, Q'center is working, and there is no '
KeBul wrote:
> I've only ever installed QLogitechMediaServer V1.07.1 on my TS-451+ so
> another possibility is if an earlier version of QLogitechMediaServer
> enabled root user, but then I would have thought digimaster would know
> about that.
>
> Rattling around in
Just checked on my Qnap ts-453a, and yes there is a root user.
But it deactivated, i can not use it.
I would suggested do as they ask, make a backup from you're Cache en
prefs directory from the SlimServer directory.
Put them some where save, like in the download share.
Then remove QLogitechMedia
QDon wrote:
> The latest response from QNAP is as follows:
>
> -*Qlogitechmedia creats a root user on the QNAP when it is installed,
> which is causing the problem we just need to remove the root users and
> the issue with qcenter should go away. The developers failed to tell me
> that we would
No you done something in the SlimServer/ directory.
Do the chmod -R 0755 SlimServer/, and chown -R squeezeboxuser:everyone
SlimServer/ from the .qpkg/LogitechMediaServer/ directory.
Keep in mind when you in the structure off LMS ( the SlimServer/
directory ), to always do that before restarting LM
Mnyb wrote:
> When you setup LMS the playlist directory and music directory should not
> be the same and the playlist dir should not be in the path of the music
> dir .
>
> Then having only read permissions on the music dir and having read/write
> on the playlist dir is no problem.
>
> And ofco
At startup, the script will set the rights for the playlist which is set
in LMS.
So that this is the only one, where squeezeboxuser can write.
And don't know about you, but i'm very careful with my music
collection.
And when writing is set, it could corrupted you're music files.
earthbased wro
earthbased wrote:
> But squeezeboxserver needs writing permission for creating Playlists.
> What's the danger in granting this?The Playlist is set at startup.
Send from my mobile Phone
*
maintainer of QLogitechMediaServer, QOptware-NG and QAutoSub.
Qnap TS-453a, with LogitechMediaSever 7.
tigrr wrote:
> Hi digimaster,
> First, a big thanks for taking care of the QLMS package.
>
> I have a problem with setting up the QLMS, after enabling advanced
> folder permissions in Shared folder settings, the QLMS can't see the
> Multimedia folder when setting th
Thought so as QLogitechMediaServer is based on the QNap Software.
So if it was causing a problem with QCenter, there would be a fault is
there own software.
Must say could get a bit angry, regarding there messages to you say
this.
But i think they where think about the SSODS/SSOTS error, where it
problem.
But i don'' t think it will solve it.
The only thing which could be a conflict, is if the use poort 9001.
So keep me posted.
QDon wrote:
> Hi digimaster,
>
> I have been having problems getting Qcenter working. I opened a ticket a
> few weeks ago and they did a remote
*
'QLogitechMediaServer_V1.07.4 for Qnap x86/i386/i686/x86_64 with QTS 4.2
or higher !' (https://goo.gl/dFtK6Q);)
= QLogitechMediaSever version 1.07.4
14-03-2018
+ Minor adjustment in the script, ./LogitechMediaServer.sh status was
not always giving correct status
earthbased wrote:
> So why didn't my QLMS update LMS to March 11th 2018? I am still on Feb
> 22nd 2018.Logon to the Qnap by ssh shell, go to the LogitehMediaServer/
> directory
and then ./LogitehMediaServer.sh restart. If it works would do the
upgraded.
Send from my mobile Phone
*
maintain
earthbased wrote:
> I did the 'touch .update' and it executed with no errors. I then
> stopped QLMS from the QnapClub My Apps icon. I then started QLMS again
> to force check for LMS update. Icon indicated running but command line
> said not running. Here are the command I had to do to ge
funio wrote:
> I got this error message, I'm not good at this, so I need some help:
> TypDatumTidAnvändareUrsprungligt IPDatornamnInnehåll
> Fel2018/03/0916:08:01System127.0.0.1localhost[QLogitechMediaServer] Perl
> can not run on this system, fix this error! LogitechMediaServer is not
> started
.
jasell wrote:
> Hi Digimaster,
> I just want to report the the upgrade QLMS 1.07.03 went smooth on my
> system, without any hick-ups.
> It took a longtime though, I think this was due to an update of the LMS
> nightly as well.
> -It might be a good idea to add a INFO note
Also, Charles Parker (Spicefly fame) was investigating if a community
> database of fingerprints might be possible.
>
> So.. Digimaster - many thanks for your hard efforts. It works well.Nice to
> read that it works well. Especially as on you're system was
giving trouble, but as I un
HB64 wrote:
> The webgui is working and in the mmm.ini file api must be set to 1 so
> all that looks good, on the LMS side I can set filters in both Sugarcubu
> and MusicIP nothing wrong it seems but still the message that the API is
> not working.But now I realize that I have experienced this be
HB64 wrote:
> Spoken a little bit to early, MusicIP is running but when I'm trying to
> start a mix with sugarcube i get the message that MusicIP's API is
> disabled although it's up and running and I believe that this is caused
> by the fact that Musicip must start before LMS.Musicip starts befo
HB64 wrote:
> Spoken a little bit to early, MusicIP is running but when I'm trying to
> start a mix with sugarcube i get the message that MusicIP's API is
> disabled although it's up and running and I believe that this is caused
> by the fact that Musicip must start before LMS.Can you acces the w
Oke found it.
At my Qnap ts-453a, QOptware-NG is actief.
And the missing shared libaryś are in there.
So install and set actieve a Optware like QOptware, then MusicIPServer
will work.
Gone try and have a look, if i can make a work around on this.
yeomanspc wrote:
> Still cannot get it to work.
yeomanspc wrote:
> Still cannot get it to work.
> Here is a copy of the SSL session with all the commands
> And an error...
> Same error on both machines..
>
> >
Code:
> > [~] # cd /share/CACHEDEV1_DATA/.qpkg/LogitechMediaServer
> [/share/CACHEDEV1_DATA/.qpkg/Logitec
.
yeomanspc wrote:
> Hi Digimaster,
> I have tried this on both my QNAPs, and can't get it to work on either
> :(
> Which is really frustrating when I see for others it works first time.
> I ran the update, did the [touch MUSICIP] (which seems to create an
> empty file ca
Nice to read it works, and it seems to be doing things a bit faster.
Happy to read that MusicIP, also is running now.
HB64 wrote:
> MusicIP is running and I forgot the backup prefs and cache folders so no
> idea if that works.
> Scanning is faster than the old SSOTS there it took more than 45 m
Could you both check, if the latest release works proper.
Should be as its based on the input you and blackbite give me.
Also in the latest release MusicIP is included, just logon by ssh shell,
and in de .qpkg/LogitechMediaServer do [ touch MUSICIP ].
Then do [ ./LogitechMediaServer.sh restart ].
Oke great, musicip also running now ?
And pur out off interested , did you copy old setting in the SlimServer/
directory ?
HB64 wrote:
> That did the trick, thanks.
*
maintainer of QLogitechMediaServer, QOptware-NG and QAutoSub.
Qnap TS-453a, with LogitechMediaSever 7.9.1 ( with spotty and y
dolodobendan wrote:
> Works great here, thank you!
>
>
>
> :)Great how about Musicip?
Send from my mobile Phone
*
maintainer of QLogitechMediaServer, QOptware-NG and QAutoSub.
Qnap TS-453a, with LogitechMediaSever 7.9.1 ( with spotty and youtube )
Several raspberry with hifiberry amp+ an
Oke there could be some things giving trouble.
First i would suggest to install it, without copy back old settings.
Still getting errors, try following.Logon on to you're Qnap by ssh
shell, do [ cd /share/*/.qpkg/LogitechMediaServer ]
[ /bin/chown -R squeezeboxserver:everyone SlimServer/ ], [ /bi
*
New release of QLogitechMediaServer V1.07.3 for Qnap QTS 4.2 or higher
with x86/i*86/x86_64 ( 02-03-2018 )
MDS5 check [ 8a64dd079748324cbaf15f4fd490ac78
LogitechMediaServer_1.07.3.qpkg ]
'QLogitechMediaServer_V1.07.3 for Qnap x86/i386/i686/x86_64 with QTS 4.2
or higher !' (https://goo.gl/dF9yn2
.
Hope will keep running without any maintaince on the installation.
Looked a lot on the source and the way ssots/ssods was made, and trying
to learn from it.
But then without all the the addon off extra commands/programs.
blackbite wrote:
> Hi Digimaster,
>
> First I have updated to 1
Yes a strange thing, because from command line it works good.
Question do you install it now from the QNapClub appstore or manuelly ?
New release coming up this weekend, with MusicIPServer included.
blackbite wrote:
> Perfect,
> thanks for the quick reply. Was just wondering, because until now,
yeomanspc wrote:
> If I install (activate) Optware then I have Sudo I think? Is Optware
> incompatible with LMS?
>
> But not clear to me why I need it. If all the mip stuff is owned by and
> run by the LMS ID, then surely it is okay .
>
>
> Sent from my iPhone using TapatalkQOoptware-NG runs
yeomanspc wrote:
> I have a 569pro and a 670pro. Both run QTS 4.3.4. The 569 has your
> Optware installed. SU was present on that. I disabled Optware through
> the app centre and SU comes back command not found. Optware never
> installed on the 670 and I get command not found there also. So
dolodobendan wrote:
> And here I thought I could give you some break and do some research
> first before bothering you again. It's "good" to hear it's not just me.
> And nobody has noticed this before? Strange.
>
> Then I'm patiently awaiting your update again, thank you very much!And as you
>
Great a expert on musicip i understand.
I'm not so after a lot off googling and read could get it work on my
Qnap.
First thing i first need to know, in you're qts is the command su there.
To test it make sure there is no optware solution actieve and the do
which su, if so should show something lik
yeomanspc wrote:
> Hi Digimaster,
> Yes - that worked fine. I've not been able to reboot the QNAP because
> it is in use for other things, but I disabled LMS from the appstore
> screen and restarted all fine. Will reboot in the morning.
> Also been though many LMS res
Well that sound good, now we have to wait on yeomanspc.
If there is also runs with now errors, this issue is fixed.
And iḿ ready to release v1.08 which includes MusicIPServer for
those how loves it.
blackbite wrote:
> Hi Digimaster,
>
> from here it looks good. Did all the tests
Bad Boy, peaking insid emy script, to revail it already v1.08.
Ha ha ha yes, there it already says v1.08, because iḿ in the
middle of preparing v1.08
But now i need some testing from you both, because up till now, you two
are the only ones with the issue.
Here i set a link to a zip file, in it
Oke strange, do i understand correctly.
It will start in safemode ( failsafe ).
If so tried from ssh shell in the logitechMediaServer directory.
[ chown -R squeezeboxserver:everyone SlimServer/ ] and [ chmod -R 0755
SlimServer/ ]
Followed by [ ./LogitechMediaServer.sh restart ]
Still errors. let
yeomanspc wrote:
> The scanning is a one-time thing (or when you add new music). When I
> did this for my 35k tracks, it took a week maybe, but it was background
> and I was at work. Rebuilding / checking my raid can take almost that
> so for me that is not an issue. I would be really interest
s.
Will be included in next release.
So thanks adjust.
Next release will be out soon, working on to included the options for
MusicIPServer.
blackbite wrote:
> Hi Digimaster,
>
> the problem ist the use of /bin/pidof in the LogitechMediaServer.sh.
> /bin/pidof ist symlinked to busybox (n
blackbite wrote:
> Hi Digimaster,
>
> With 1.07.2 I can no longer get QLMS to work. 1.07 and 1.07.1 did fine.
> I did a fresh install (like always). It installs ok but it doesn´t start
> the LMS. Something went wrong...
> But the Error-File shows no error. It just states that
Oke effen better got it to work.
But must say understand the overhead. it takes for ever to scan.
And no there is no website to reference to. ( as for as i can find )
But a lot off my music already been having a fingerprint through beets.
( Which if i understand correctly, uses the same way to fin
*
And then another tip off the day, for the advanced user.
In stead off editing the .QLMS.conf file, there is for a lot off
commands a other way to set them.
If you're in the .qpkg/LogitechMediaServer directory, you can do touch
UPDATE or NIGHTLY.
Which will set it to do a check on startup for a
*
After pointing to musicip and musicmagicserver, been playing around a
bit with it.
And it works on the QNap.
But no idea how many want to use it, or how it is used in combination
with LMS.\
So the question is, is there any intressed to add it to
QLogitechMediaServer ?
Let me know, and maybe so
As i write in the instruction, best way to make it install from the
appstore.
Do the backup Cache/prefs, then uninstall and reinstall through the
QnapClub appstore.
And if installed and running, follow instructions how to set youŕe
setting back.
Then you could a clean installations, and the updat
Oke tried it here, and it runs.
Remember to set chown/chown.
But from there dont know any thing more about musicip.
So maybe tell me more, so i can have a look, to either included it or
make a separeted QPKG for it.
But to do so, need a lot off info ?
yeomanspc wrote:
> So I installed Optware an
Looked at the status option, and there is still the old command which
give trouble on old QNap systemsn.
So if its running, but status says not, ignore it. A other way to check
do a ./LogitechMediaServer.sh start, if running will display it with
pid.
In the next release this will also be fixed.
Follow the instructions, how to install it through the AppCenter.
http://forums.slimdevices.com/showthread.php?108702-QLogitechMediaServer-for-Qnap-with-QTS-4-2-or-higher-and-x86_64-I686-X86-support-!&p=907082&viewfull=1#post907082
earthbased wrote:
> I added QnapClub EU Repo and then I got the
digimaster wrote:
> Status could not work.
>
> Send from my mobile PhoneSo ignore the status check in you're case. If it's
> running without any
errors Problem solved. The status option still needs to be adjust to
also work correctly on systems like yours.
Sen
jasell wrote:
> I just tried the upgrade from within QNAPstore.
>
> The update went smooth, no errors/warnings.
>
> When I checked "status" from command prompt I got the message QLMS was
> not running. The slimserve.pl process was and web GUI was there.
>
> So I killed the process and started
earthbased wrote:
> Can I install 1.07 over 1.05? And should I get it from the EU
> QnapClub?Yes you can, and yes you should.
Send from my mobile Phone
*
maintainer of QLogitechMediaServer, QOptware-NG and QAutoSub.
Qnap TS-453a, with LogitechMediaSever 7.9.1 ( with spotty and youtube )
S
jasell wrote:
> QLMS is paddeling along fine since you sorted things out.
>
> I have only a few lines in the sevrer log, some from what seems to be
> related to the QTS environment, and some other from Spotty.
> >
Code:
> >
> [18-02-18 13:44:25.3110] main::init (387)
Oke sure, there will be away.
But has to be on the roadmap.
For the moment there are other thing, which are hiher on the list.
HB64 wrote:
> In the past i have tried several ways to start MusicIP on boot with no
> luck, yes it will start but every reboot the m3lib file is gone due to
> the fact
*Here a tip for the advanced users.
Install 'Qoptware-NG v2.05' (https://www.qnapclub.eu/nl/qpkg/550), then
follow the instructions on how to un install and reinstall
QLogitechMediaServer with backup off youre settings. Also look in the
QnapClub appstore and install 'sortmyQPKGs'
(https://www.qn
If you install QOptware-NG, it will set a file in the lib directory of
the QTS system.
This is responsible for the 32bits handling, so all proggies which look
for it will find it again.
After installing QOptware, follow the instructions on how to backup, and
them un install and install QLogitechM
yeomanspc wrote:
> I tried going the upgrade route by changing the qpkg.conf file (against
> your good advice).
> It did indeed pick it up and show on the apps menu with an upgrade
> option, but on trying to upgrade it still comes back with the error that
> the 'the internal name of QLogitechMedi
Then first off all, thanks for al the great work and support.
Here on a Qnap nas systemen working perfect, installed version
7.9.1-1518987734
And works great, feels faster.
mherger wrote:
> > Will this also be the case, for the Logitech Media Server: Unix
> Tarball
> > (i386, x86_64, i386 Free
Will this also be the case, for the Logitech Media Server: Unix Tarball
(i386, x86_64, i386 FreeBSD, ARM EABI, PowerPC).
As i maintain the installation for the QNap, curious to check if it
works.
mherger wrote:
> I'm in the process of migrating the build environment for Logitech Media
>
> Serv
earthbased wrote:
> Hi, been running 1.05a fine and dandy. If this is the case, is there
> any reason to upgrade to 1.07?Yes in v1.07 auto update is fix a.m.
Send from my mobile Phone
*
maintainer of QLogitechMediaServer, QOptware-NG and QAutoSub.
Qnap TS-453a, with LogitechMediaSever 7.9.1
*
To look if QLogitechMediaServer, will also work QNap nas systems with
QTS lower then 4.2.
I am looking for people how have a QNap, to test if it also works on
those !
So if you have a QNap system with the right architecture with QTS 4.1 or
lower send me a pm?*
*
maintainer of QLogitechMediaS
Send you a pm.
jasell wrote:
> --> in .QLMS.conf I changed #HTTPPORT="" to HTTPPORT="9050" but this
> doesn't seem to work propely, this is what i get in the log
> It looks like the start command is not using any port all instead of
> using 9050
> >
Code:
> > [15:32:1
[And again, many thanks - you have breathed new life into LMS on QNAP -
in fact, better than it was under SSOTS (aside from QNAP killing 32bit
MusicIP]
There is away of making a QNap x86_64 with QTS 4.3 work with 32bits
programs again.
You first need to install QOptware-NG v2.05, then follow the
The twice starup error comes from within LMS, it can only claim a poort
once.
The second time will give a error.
So or there is a command, not working proper like SUDO/RENICE or one
from busybox.
Or there is already something running which is using 9001.
Another thing to try is, in the .QLMS.confi
*
I am getting a lot off qeustion regarding how to upgraded earlier
QLogitechMediaServer installations before V1.07.
So here will try to enplane how you could make it upgraded through the
AppCenter from Qnap.
There are two ways you could try, the first is to get a nice clean
installation. ( Which
If you do the backup Cache,Prefs directory backup to save place,
uninstall and reinstall with place back the directoryś.
You got a very clean installation, and from then on Upgrades go through
the AppCenter, so you don need to do this after this.
Another way to completly preserve you're QLogitech
jasell wrote:
> I'm sorry to say but i cannot get the "official" 1.07.1 from qnap club
> to run.
>
> I made a clean install.
> -I stopped QLMS (1.07.0), made sure no left over process was running.
> -Remove QLMS from appcenter
> -Made a system reboot
> -Then add the QNAP club repo to appcenter (
blackbite wrote:
> Sorry,
> misunderstood...
> When you're already on your qpkg v 1.02 or like me 1.06f, Is it safe to
> just upgrade to final 1.07?
> ThanksYes it's.
You can upgrade.
But the simplest is to do it from qnapclub appstore. Another way is to
add the store line in the /etc/config/q
blackbite wrote:
> I think he ment remove and re-install or install over the existing
> version of the qpkg...Oké depends on what you wants. Best most simplest way.
> Copy the prefs
and Cache directories to a save place. Remove, Uninstall the old version
through the Qnap appcenter. Then install
yeomanspc wrote:
> What is the best way to upgrade this as new releases come out.? Do I
> have to do a complete remove, and re-install?
> Any idea when it will be in the QNAP app store.?It's in the qnapclub
> appstore.
Send from my mobile Phone
*
maintainer of QLogitechMediaServer and QOpt
dolodobendan wrote:
> I don't think this will cause me sleepless nights. :)Ha ha don't think it
> will cause any sleepless night here either.
Happy it's working well after weeks off testing.
Send from my mobile Phone
*
maintainer of QLogitechMediaServer and QOptware-NG.
Qnap TS-453a, with
No idea, its handled by QNap it self.
dolodobendan wrote:
> 1.07 runs smoothly, thank you!
>
> Just cosmetics: In qpkg.conf there's no empty line between QLMS and the
> following entry.
>
> >
Code:
> >
> ...
> Visible = 2
> Enable = FALSE
> Official = 0
> [
jasell wrote:
> When I start playing using connect I get another Spotty process (as
> expected) this one is owned by admin, should they all be owned by
> squeezeboxserver?That's normal.
And normally the script should check on ownership. So no you should not
do the chmod chown thing everyone. Afte
Qnapclub repo was down, due to trouble.
At the moment they rebuild the repo, should it should be fixed soon.
jasell wrote:
> [ kill -9 17982 ] works, must have been that the later part in your
> command gave nothing, so [ kill -9 ] gives error...
>
> Didn't know about qnapclub, however after si
Oke nice that it seems to work now.
Which version do you use now.
And yes maybe there was some thing wrong in the nightly build, we have
to keep in mind its a nightly build so for testing only.
But a strange thing you write thats kill -9 give you a error, this
should work if you put a pidnumber f
Very strange behavior, but what i read out off all the logs is, that
there already is a copy off LMS running.
And it can be started twice, with out errors.
[ FATAL: There is already another copy of the Logitech Media Server
running on this machine. (Address already in use)]
So before you start QLo
jasell wrote:
> When I stop and start QLMS from app center I get 2 slimserver.pl
> process... this can't be right.
> After a while one of them disappears.Yes that can be right, as it starts
> children process.
Send from my mobile Phone
*
maintainer of QLogitechMediaServer and Qnap-Optware-N
jasell wrote:
> I tried a system reboot.
> slimserver.pl i running but [ ./LogitechMediaServer.sh status ] says
> LogitechMediaServer is not running.
> see log files, I cleared them before the reboot...
>
> Web GUI loads but with no content...
>
> Seems like this version of QLMS tries to start
jasell wrote:
> OK, I'm doing a clean install.
> Stopping everything, removing QLMS app from appcenter, system reboot.
> Manual install from appcenter...
>
> same install behaviour.
> -First quickly up to 45%, wait for a moment
> -Then quickly up to 75%, wait for a moment
> -Then up to 100%
>
>
*Due to the support change, made a new thread!
So for future information, and support go to
http://forums.slimdevices.com/showthread.php?108702-QLogitechMediaServer-for-Qnap-with-QTS-4-2-or-higher-and-x86_64-I686-X86-support-!&p=906561#post906561*
*
maintainer of QLogitechMediaServer and Qnap-O
*QLogitechMediaServer for Qnap x86_64/i686/x86 with qts 4.2 or higher
Here you can always find the latest version of LogitechMediaServer for
Qnap x86_64/i686/x84 and mixed X86-64 systems with QTS4.2 or higher.
At the moment only support for x86_64/i686/x86. Before installing do
login with ssh shel
Oke new release is out, where it should be fixed.
'QLogitechMediaServer V1.07 QTS 4.2 or Higher and x86_64/x86/i686'
(https://www.dropbox.com/s/vjvlqx8f2y08lxs/QLogitechMediaServer_V1.07_QTS-4.2_or_Higher_x86_64-x86.zip?dl=0)
So please try this version ?
jasell wrote:
> Complete log file?
> Wh
jasell wrote:
> Complete log file?
> When QLMS launched ok and I installed spotty, spotty did not work.
> There were several entries from spotty in the log file, but not time
> stamp.
>
> To investigate this I stopped QMLS from the command line, then deleted
> log-file to get a fresh log file to
jasell wrote:
> this is very strange... I saw that spotty did not work with connect from
> the spotify app, I had some error in the log file, but no time stamp.
> So I stopped the QLMS form command line, cleared the log file, and then
> tried to start QLMS.
> But failing as before
>
> But my
jasell wrote:
> I'm using a QNAP TS-439 Pro II+ which is running QTS 4.2.6 build
> 20171208 (the latest version for this model).
>
> I have only the Download app running apart from QLMS.
>
> I used to run SSOTS-LMS, when getting Spotty to work I had to install
> the PERL app which in turn insta
yeomanspc wrote:
> OK, going to take the plunge on my backup 569 pro with QTS 4.3. and give
> this a go.
>
> So to be clear.
> > >
- Remove LMS and SSOTS
- restart NAS
- Install this qpkg
-
> > >
> Nothing else to add or do? Do I need to manually delete SSOTS if it
> is still lu
jasell wrote:
> I tried the above, doesnt start clean.
> I too have been on vacation I will come back with log-files
>
> On this qnap I run only the download app and QLMS, used to run
> SSOTS-LMS. I tried to start QLMS with all other apps stopped but same
> result.
>
> Do you need the log
blackbite wrote:
> Hi there,
> any news about the planned release of the qpkg? It´s very silent here
> atm.
>
> GreetingsJust back from a holiday. And waiting on some reactions, how it
> works on
other Qnap systems. Especially those who use QTS 4.2 and i686, x86
systems. Before I release the ne
dolodobendan wrote:
> I'll give it a try, thank you! Do you think a rescan is required after
> these changes?No think it has more to do with the search.
Send from my mobile Phone
*
maintainer of QLogitechMediaServer and Qnap-Optware-NG.
Qnap TS-453a, with LogitechMediaSever 7.9.1 ( with spo
You could try playing around with
export LC_ALL=en_US.UTF-8
export LANG=en_US.UTF-8
export LC_CTYPE=en_US.UTF-8
Because if i understand it right, is used for a search with in Linux.
dolodobendan wrote:
> That's annoying, but I guess I have to live with this, then. I so do not
> want my interf
501 - 600 of 738 matches
Mail list logo
