Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[mwillems]

@mwillems, my Axiom Speakers have shipped (long way from Canada to Oz but should be here in a week or so).  Is there anything I should do when I first get them (eg dump the contents of it's SD Card if you want to see what is on it etc)?

Thanks
Nathan

I would advise making backups before you do any tinkering 

But, once you do that, I'm most curious how well it works.  But... if you can (consistent with the EULA of course) conveniently put an .iso up somewhere, I'd be interested to take a look at the guts 

[jmone]

No probs in making it avail, as from their Web Site they say it is Open Source (but they have yet to post it on GitHub):

AxiomAir utilizes the Raspberry Pi – a micro-computer about the size of a credit card – as the ‘brains’ behind the speaker, and we chose to make the programming open source. What that means is outside developers can write apps for the Raspberry Pi.

I'll make an copy of the contents of the Pi before I even power it up.

The thing is I'm a relative newbie to all things Linux.  I'm competent enough to use Putty/SSH/SCP to get into stuff but really then just follow advice on what to do.  I'm wondering if I should either:
- Have a couple of builds - eg the one that comes with the Air + one that is just MC, or
- Try to have one build with both at the same time

Thanks
Nathan

[mwillems]

No probs in making it avail, as from their Web Site they say it is Open Source (but they have yet to post it on GitHub):

I'll make an copy of the contents of the Pi before I even power it up.

The thing is I'm a relative newbie to all things Linux.  I'm competent enough to use Putty/SSH/SCP to get into stuff but really then just follow advice on what to do.  I'm wondering if I should either:
- Have a couple of builds - eg the one that comes with the Air + one that is just MC, or
- Try to have one build with both at the same time

Thanks
Nathan

It will depend on how they've implemented their setup.  It will undoubtedly be easier to set them up separately, but it may be possible to get both running at once.

[bob]

Have any of you pi users found a way to use the audio device selection in MC to control output to hdmi vs analog vs optical (pi3) instead of using the raspi-config ?

[mwillems]

Have any of you pi users found a way to use the audio device selection in MC to control output to hdmi vs analog vs optical (pi3) instead of using the raspi-config ?

I haven't, although it can easily be set with a script/programmatically by editing the config.txt if need be.

[bob]

I haven't, although it can easily be set with a script/programmatically by editing the config.txt if need be.

That's what I resorted to. Working on the Id Pi. Haven't tried it with a pi3 and the optical output yet...

[nichilds]

I'm trying to configure Raspbian on Raspberry Pi 3 for MC21, but ran into a roadblock on the "Quick Start" instructions.  I keep getting a 404 error when entering the following command: sudo wget http://dist.jriver.com/latest/mediacenter/mediacenter21nativelist -O /etc/apt/sources.list.d/mediacenter21.list

I'm able to connect to dist.jriver.com (216.14.187.181:80), but that directory is not found.  Any ideas?

[mwillems]

I'm trying to configure Raspbian on Raspberry Pi 3 for MC21, but ran into a roadblock on the "Quick Start" instructions.  I keep getting a 404 error when entering the following command: sudo wget http://dist.jriver.com/latest/mediacenter/mediacenter21nativelist -O /etc/apt/sources.list.d/mediacenter21.list

I'm able to connect to dist.jriver.com (216.14.187.181:80), but that directory is not found.  Any ideas?

You have a typo in the command you've posted (there should be a period between native and list in the url as shown below); was the typo present in the command you ran?

Code: [Select]

sudo wget http://dist.jriver.com/latest/mediacenter/mediacenter21native.list -O /etc/apt/sources.list.d/mediacenter21.list


[jmone]

Has anyone got Bluetooth working as an input device?
Thanks
Nathan

[mwillems]

Has anyone got Bluetooth working as an input device?
Thanks
Nathan

Bluetooth as an input?  How do you mean?  The pi 2 doesn't ship with integrated bluetooth, but the pi 3 does.  Is the idea that you'd play something on your phone and it would cast to MC on the pi via bluetooth?  If so, MC for Linux doesn't really support any inputs to speak of; there's no loopback or anything like that with MC for Linux (which is what's required to do that on Windows).  If you mean outputting to a bluetooth speaker using MC as a source, I haven't tried it on a pi, but I expect it would work once the pairing is done.

At the moment the only way to get an arbitrary input into MC for linux is via upnp/DLNA.

[jmone]

Sorry - I meant if I added a BT USB Adapter to the Pi (Axiom Air) that will then allow a phone to stream to the Audio Subsystem (ALSA??? if I've got that right). 
Thanks
Nathan

Note: I can add a BT --> 3.5mm device easy enough to it's Analogue port but I thought the above would be "neater" if possible

[mwillems]

Sorry - I meant if I added a BT USB Adapter to the Pi (Axiom Air) that will then allow a phone to stream to the Audio Subsystem (ALSA??? if I've got that right). 
Thanks
Nathan

Note: I can add a BT --> 3.5mm device easy enough to it's Analogue port but I thought the above would be "neater" if possible

It's entirely possible, but not using MC for the reasons I mentioned, if that makes sense.  I've done very little tinkering with bluetooth on Linux, but I can try and take a hack later this week.  I can't see any reason that it wouldn't work, and there's some promising instructions here: https://gist.github.com/joergschiller/1673341

[jmone]

Thanks - no rush.  My son was using the Air at a party and some of the guests were trying to connect to it from their phones.  I know that it is Volumio's list of ToDo but It's not there yet.

[bob]

It's entirely possible, but not using MC for the reasons I mentioned, if that makes sense.  I've done very little tinkering with bluetooth on Linux, but I can try and take a hack later this week.  I can't see any reason that it wouldn't work, and there's some promising instructions here: https://gist.github.com/joergschiller/1673341

I've messed with this a bit previously and saw the article you linked.
It seems pretty flaky. I was hoping if we waited a while the support would get better...

[Slim_Fishguttz]

An "HDMI Doctor" style dongle wouldn't provide any remote administration options, and isn't really necessary on Linux in any case: if you don't care about remote administration there are ways to force the XServer to start without a monitor attached, but I didn't outline them above because they're not particularly useful (you wouldn't be able to interact with it at all without plugging in a monitor).  There's also no guarantee that such a dongle would work particularly well with Linux at step one, whereas the VNC solution has been extensively tested.

So I would advise against using such a dongle on the Pi, but if you try it, I would be interested to hear how such a dongle works with Linux (just out of curiosity).

Thanks for your follow-up.  The dongle works on the Pi, and in fact , has worked on any system that i have, for various reasons, tried it on.  As for remote admin, I use Jump Desktop connecting to TightVNC.  Jump Desktop connects to my Mini, 2 PCs, 3 Pis, a Ubuntu server, and a virtualized Win10 and a virtualized FreeNAS, both running under Ubuntu.  Top shelf program; couldn't function without it.

Since I have your ear - it seems that Linux MC has no server?  Is this true?  Consequently, I run the MC server in the Win10 vm.  MC runs and connects to my NAS without any problems.  However, I can't connect to the MC server, running in the vm machine, from another MC.  I use the access code that the MC server supplies and the MC client uses it to try to connect, but it can't find the MC server, although it seems to know its address.  I can't positively confirm this since the message addressing this is truncated in the MC messagebox.  Guest connecting to outside world - OK; outside world connecting to guest - not so much.  I know it has to due with the fact that while my network ip is 192.168.0.xxx, the vm guests run on 192.168.122.xxx.  This is recognized by the MC client, but it can't connect because it seems to be a different network.  This can be addressed, but requires some research on my part.

I struggle with Linux, any suggestions would be helpful.

Thanks

[mwillems]

Thanks for your follow-up.  The dongle works on the Pi, and in fact , has worked on any system that i have, for various reasons, tried it on.  As for remote admin, I use Jump Desktop connecting to TightVNC.  Jump Desktop connects to my Mini, 2 PCs, 3 Pis, a Ubuntu server, and a virtualized Win10 and a virtualized FreeNAS, both running under Ubuntu.  Top shelf program; couldn't function without it.

Since I have your ear - it seems that Linux MC has no server?  Is this true? 

I'm not sure I understand what you mean?  In terms of actually functioning as a server, Linux MC works as a media server and has almost similar server functionality to the windows version (that's an area where it's close to feature parity, except for live TV).  It doesn't have a tray widget if that's what you mean, but that's just cosmetic.  If you start the linux instance with the "mediaserver" flag, it will start minimized, use less memory, and not throw any modal dialogs that would hang the UI.  It just won't give you a pretty tray icon, but works perfectly as a server.

Consequently, I run the MC server in the Win10 vm. 

Unless you need live TV, you don't need to do this, see above.

MC runs and connects to my NAS without any problems.  However, I can't connect to the MC server, running in the vm machine, from another MC.  I use the access code that the MC server supplies and the MC client uses it to try to connect, but it can't find the MC server, although it seems to know its address.  I can't positively confirm this since the message addressing this is truncated in the MC messagebox.  Guest connecting to outside world - OK; outside world connecting to guest - not so much.  I know it has to due with the fact that while my network ip is 192.168.0.xxx, the vm guests run on 192.168.122.xxx.  This is recognized by the MC client, but it can't connect because it seems to be a different network.  This can be addressed, but requires some research on my part.

I don't know what kind of virtualization solution you're using or how you've configured it, so I can't give very detailed advice, but it sounds like the problem is that you're using "NAT" style VM networking.  With NAT networking, the host for the VM acts like a router/firewall for the VM, so the inability of programs outside the VM to reach the VM is by design.  It's not just that it's on a different subnet, the host is actively blocking traffic to the VM unless you enable port-forwarding or address translation deliberately.  Most VM solutions offer other networking modes than the "NAT" mode;  for example, virtual box offers a "bridged" mode which effectively just makes the VM another "box" on your home LAN.  It can then see and be seen by everything else on the LAN, etc.  That kind of configuration is better if you're uncomfortable doing port forwarding.

But you really may not even need the VM; the linux version works fine as a server.  Just leave the program minimized, or start it with the mediaserver flag.

[Slim_Fishguttz]

If you start the linux instance with the "mediaserver" flag, it will start minimized, use less memory, and not throw any modal dialogs that would hang the UI.

Aha - There's a mediaserver flag?  Where is this documented? Is it in the Wiki, I can't find it there.  I thought there was no linux server because it wasn't in the startup options, which I guess work differently under linux.  From my forum reads, it seems MC under linux is unstable.  I think I will keep my underlying server relatively clean and run things virtualized, but I'll try the server mediaserver flag (out of curiosity).

..... it sounds like the problem is that you're using "NAT" style VM networking.

Aha - NAT vs. port forwarding vs. bridging.  That's what I need to research.  Thanks for the finger pointing.

My regards.

[JimH]

I think that the command you need is in this section of the DevZone:

http://wiki.jriver.com/index.php/The_Command_Line

[mwillems]

Aha - There's a mediaserver flag?  Where is this documented? Is it in the Wiki, I can't find it there.  I thought there was no linux server because it wasn't in the startup options, which I guess work differently under linux.  From my forum reads, it seems MC under linux is unstable.  I think I will keep my underlying server relatively clean and run things virtualized, but I'll try the server mediaserver flag (out of curiosity).

It's

Code: [Select]

/mediaserver
 If you look at the posts at the top of the thread some o the code examples use the flag.

[Spresti]

So I have successfully installed MC21 on my raspberry pi 3. I activated the license via the terminal and everything was work working great! But after a few boots about the fourth time I opened MC21 I got a message indicating that my trail has expired, even though I already activated it. So I clicked apply license and entered my code. It thinks for a second and then pops up saying that it could not connect to the license server. I am connected to the internet and my code is valid. I have tried reinstalling MC21 but at first start it said my trail was expired and still would not let me apply my license saying it could not connect to the license server. PLEASE HELP ME!!!

[mwillems]

So I have successfully installed MC21 on my raspberry pi 3. I activated the license via the terminal and everything was work working great! But after a few boots about the fourth time I opened MC21 I got a message indicating that my trail has expired, even though I already activated it. So I clicked apply license and entered my code. It thinks for a second and then pops up saying that it could not connect to the license server. I am connected to the internet and my code is valid. I have tried reinstalling MC21 but at first start it said my trail was expired and still would not let me apply my license saying it could not connect to the license server. PLEASE HELP ME!!!

You should open a separate thread for this; I'm just a user so I can't help with license issues.  Your issue will be more visible to the devs as a separate thread

[Spresti]

You should open a separate thread for this; I'm just a user so I can't help with license issues.  Your issue will be more visible to the devs as a separate thread

Thank you

[PrinterPrinter]

Hello People,
I wanted to confirm that JRiver 21 works flawlessly with RPI3 (Hifiberry digi+ board) so I can go ahead and upgrade my kit?

Thank you

[mwillems]

I haven't used it with the hifiberry digi, but MC21 appears to work the same with a Pi3 as it does with a Pi2 in my testing,

[PrinterPrinter]

I haven't used it with the hifiberry digi, but MC21 appears to work the same with a Pi3 as it does with a Pi2 in my testing,

Thank you, so just follow this guide with the RPI3 and it should all work?
Are there any noticeable sonic benefits to the RPI3 vs the RPI2? I imagine the onboard wifi vs a dongle is less noisy? (in an audiophile way...

[mwillems]

Thank you, so just follow this guide with the RPI3 and it should all work?

Yes

Are there any noticeable sonic benefits to the RPI3 vs the RPI2? I imagine the onboard wifi vs a dongle is less noisy? (in an audiophile way...

No differences that I've noticed other than more responsive UI.

[PrinterPrinter]

Cool,
I've done the upgrade and it all went smoothly.

I think it sounds a little better (supposedly onboard wifi less noisy than a USB dongle) - it runs faster and smoother indeed.

I wonder if convolution will now work better?

[mattd008]

Great guide. I'm using a pi 3 with Raspbian and MC 24. All are up to date. I have been very successful with audio that is less than 3 minutes but longer tracks buffer then play for 2-5 seconds and buffer again. I did the thing to 'Setting Thread Priorities for Improved Performance'.

What should I look at and what other information would be helpful?

Also, I'm planning on adding a HiFiBerry Digi+ board.

Thanks for your help on this.

[Awesome Donkey]

You're not using memory playback, right? Memory playback won't work very well on a Pi.

[mattd008]

You're not using memory playback, right? Memory playback won't work very well on a Pi.

I don't think so. I just validated that in options : Audio : Settings : Memory Playback (not zone-specific): is set to 'No memory playback'.

The audio files are on a USB3 memory stick.

[mwillems]

I don't think so. I just validated that in options : Audio : Settings : Memory Playback (not zone-specific): is set to 'No memory playback'.

The audio files are on a USB3 memory stick.

Did you change your buffer settings at all?  Also have you tested to see if the same issue happens with the files on the sd card?  Lastly, what kinds of files are they?

[mattd008]

Did you change your buffer settings at all?  Also have you tested to see if the same issue happens with the files on the sd card?  Lastly, what kinds of files are they?

I had not done anything to buffer settings but I just went back and forth with the following setting:
tools : options: media network: disable audio buffer to disk (for low powered systems) --I didn't see any difference.

I also just tried to put one of the files on my SD card and I'm seeing the same issue.

Files are FLAC

[mwillems]

I had not done anything to buffer settings but I just went back and forth with the following setting:
tools : options: media network: disable audio buffer to disk (for low powered systems) --I didn't see any difference.

I also just tried to put one of the files on my SD card and I'm seeing the same issue.

Files are FLAC

To be clear by "buffer settings," I meant the settings under "device settings" or "prebuffering" in the options-->Audio dialog; even if you haven't changed them it might be worth raising or lowering them to see if there's a combination of buffer settings that does work.  Write down the default values first.

Do the files in question play fine on other players?  What is your output device?

Also, this is the MC21 for Pi thread, we should probably move this discussion over the to the MC24 for Pi thread (assuming you are running MC24).

[mattd008]

To be clear by "buffer settings," I meant the settings under "device settings" or "prebuffering" in the options-->Audio dialog; even if you haven't changed them it might be worth raising or lowering them to see if there's a combination of buffer settings that does work.  Write down the default values first.

Do the files in question play fine on other players?  What is your output device?

Also, this is the MC21 for Pi thread, we should probably move this discussion over the to the MC24 for Pi thread (assuming you are running MC24).

OMG. should I be running 21 on the Pi (is it typically a better fit)? I will look for a similar thread on version 24.

The audio is over HDMI (through my tv) and then to an optical out that goes into a KECES (DA-131) DAC then to an Emotiva USP-1 preamp (with LP going to an M&K Sub) and an JLB UREI 6260 power amp...there are some speakers too. Tomorrow evening I will be getting my HiFiBerry Digi+ board and then I will probably go headless and cut out the HDMI stuff.

I have had success with these same files on an old iMac but I want a tiny footprint.

Thanks so much for your help so far.

[mwillems]

OMG. should I be running 21 on the Pi (is it typically a better fit)? I will look for a similar thread on version 24.

No, 24 is probably the best place to start; there's a similar thread to this one over there.

The audio is over HDMI (through my tv) and then to an optical out that goes into a KECES (DA-131) DAC then to an Emotiva USP-1 preamp (with LP going to an M&K Sub) and an JLB UREI 6260 power amp...there are some speakers too. Tomorrow evening I will be getting my HiFiBerry Digi+ board and then I will probably go headless and cut out the HDMI stuff.

I have had success with these same files on an old iMac but I want a tiny footprint.

Sorry, I meant do the files play well with other media players on the raspberry pi (i.e. can the pi play them if you open them in vlc or something).  If they don't play in other players on the pi that points to a different set of problems if you see what I mean.

[mattd008]

No, 24 is probably the best place to start; there's a similar thread to this one over there.

Sorry, I meant do the files play well with other media players on the raspberry pi (i.e. can the pi play them if you open them in vlc or something).  If they don't play in other players on the pi that points to a different set of problems if you see what I mean.

I'll check for the 24 thread. files play great with VLC. I'm totally out of my depth but having fun.

i installed the Digi+ board and can't figure that out either. 

[mwillems]

I'll check for the 24 thread. files play great with VLC. I'm totally out of my depth but having fun.

i installed the Digi+ board and can't figure that out either. 

Also, make sure you're using the latest version of MC24, there was a version a few back that had some buffering issues if I recall.