INTERACT FORUM
More => Old Versions => JRiver Media Center 19 for Windows => Topic started by: JimH on May 28, 2014, 01:32:56 pm
-
(http://wiki.JRiver.com/images/d/de/NUC2820.jpg)
We've just released our new network media player, the JRiver Id. It can act as a DLNA Renderer, DLNA Server, or as a stand-alone Portable Media Player.
The introductory price is $295.
If you would like to order one, please see the wiki (http://wiki.JRiver.com/index.php?title=Id§ion=7#Ordering).
If you do purchase an Id, please use this thread (http://yabb.jriver.com/interact/index.php?topic=91344.0) for any questions.
Description (http://wiki.JRiver.com/index.php/Id)
Install Guide (http://wiki.JRiver.com/index.php/Id_Install_Guide)
Ordering (http://wiki.JRiver.com/index.php?title=Id§ion=7#Ordering)
-
reserved
-
I have received my unit. Initially, though not a shred of doc was included, all the hardware connections were obvious and it came right together and booted.
1. I'm not entirely sure what the purpose of the two text modes are (headless and HDMI) as there seems to be very little in them to get things actually working.
2. #4 menu item doesn't seem to do anything.
3. When you change audio output methods the one you just chose doesn't show default or selected after the reboot.
4. I don't use the default port 52199 on my other MC's, so it was necessary to go into the GUI mode to set that.
5. Yes, the GUI mode is pretty flaky, but usually you can get through it...
6. But while I can see the hex-id of the renderer on other clients, if I select it, it will either go away or actually select. Then while attached to that zone, attempting to play anything either just steps through songs, or disappears (the id/connection disappears).
7. So taking a different approach I attached the Id to my main server library. It accepts the data, but when I try to select it, 'Load Library' is greyed out. It does ask for that servers id and password. Everything 'seems' normal up to that point.
That's it so far. Am I doing something stupid?
--Bill
So far I haven't heard a peep out of Id, no matter what. It is showing the correct device for audio, and network view shows a good DHCP address. But nothing having to do with DLNA or remote libraries seem to work. I have no interest in creating a library of songs on Id -- that wasn't why I was interested in it.
I've been over and over the setups and end up with the same results every time. Also, after a reboot, the port assignment and library information is back to default.
After one reboot (about 15 reboots in) I got a message that trial mode had expired, so I requested an extension code, got and entered it, but MC still was complaining about the expiration. After another reboot it came up running.
-
Finally, something. I found after another reboot into the GUI mode, that selecting the main server library name actually does select it, even though the highlighting of the Loading... display button stays gray. I was then able to load a playlist and play a song.
But sending to it as a renderer still does the same thing from the originating MC -- the songs advance about every four seconds. As they do, on Id the album picture briefly flashes in the Display window (lower left) and for every song that is attempted, a message saying "Something went wrong with playback. [OK]" shows.
--Bill
-
After one reboot (about 15 reboots in) I got a message that trial mode had expired,
That is a showstopper problem. If it isn't licensed, it won't run at all. I'm sorry about that. It's possible though that the message is a red herring.
If you have an HDMI monitor or display attached, choose option 10 from the text menu.
Option 4 should save whatever settings you've done in the GUI mode so they aren't lost on a reboot. But we discovered yesterday that it was broken. It was fixed today.
But while I can see the hex-id of the renderer on other clients...
You should see something like "Id-EA.........". It's the Mac address.
Can you give us access via Internet?
My guess is that the licensing is the problem.
Is the Server mode on? If so, turn it off.
Can you e-mail me the Mac address? It's at the top of the text menu. jimh at jriver. Thanks.
-
As shipped the Id is a renderer only.
If one is using the HDMI output there are 2 text mode defaults, one headless which means the Id will boot without an attached monitor. The other initializes the HDMI. That should only be necessary if the audio device requires initialization.
The server toggle enables the Id to serve files, and it will then show the access code at the main menu.
The license problem comes from a problem with the user mode as the Id was shipped. If you choose one of the defaults, analog or hdmi for example the licensing will return. Any changes you make afterward are saved when you choose the user mode. Next time booted in user mode the license will be there.
When you choose the user mode item from the main menu, it saves the current settings across a reboot.
-
4. I don't use the default port 52199 on my other MC's, so it was necessary to go into the GUI mode to set that.
For testing purposes, it would be good to use 52199 if possible.
-
bblue's e-mail:
I have periodic segmentation faults when in the GUI.
How do do the updates, traditional method with update channels set for Latest, or Beta? Or some other way?
I'm changing port numbers on the rest of my gear now.
--------
If you're talking about the license failure, I haven't seen that one again lately. Not sure if it was my adding the extension code, or something else.
-
bblue's e-mail:
I have periodic segmentation faults when in the GUI.
How do do the updates, traditional method with update channels set for Latest, or Beta? Or some other way?
I'm changing port numbers on the rest of my gear now.
--------
If you're talking about the license failure, I haven't seen that one again lately. Not sure if it was my adding the extension code, or something else.
The segmentation fault error may have been fixed this morning. We'll have an update available in a few minutes.
Updates aren't the same as the normal MC updates and aren't controlled from the GUI mode program. It's an option on the text menu.
Until we get this up and running, just use the text mode (option 10). Don't use the server mode. Use port 52199. (and make sure your firewall allows it). Just use the renderer feature.
Try playing from another PC. Try using Gizmo or JRemote to control.
-
There is an update to address the segfaulting.
Run option option 6 from your Id menu (with the Id having a path to the internet).
It will update and reboot.
-
I have received my unit. Initially, though not a shred of doc was included, all the hardware connections were obvious and it came right together and booted.
...
2. #4 menu item doesn't seem to do anything.
The intended purpose of the GUI mode is to allow one to set their own parameters. Once set, choosing menu option number 4 saves those as the user defined profile so it can be used across a reboot. The user-defined parameters profile is the only one that is saved across a reboot.
Once the user defined parameters are set the way one wants you'll likely want to reselect the text mode boot (with or without HDMI initialization depending on your setup).
...
6. But while I can see the hex-id of the renderer on other clients, if I select it, it will either go away or actually select. Then while attached to that zone, attempting to play anything either just steps through songs, or disappears (the id/connection disappears).
Stepping though the songs and the connection disappearing are likely related to an incorrect output device in the ALSA configuration in MC's configuration.
The menu choices for analog and hdmi are tailored specifically to the ID and should always work regardless of what kind of audio material you push to the ID.
The USB DAC menu choice is tailored to a Dragonfly USB dac.
If you have a different USB DAC you'll need to use the user defined parameters profile and set it up under the Audio Options -> ALSA -> device settings.
If you have material with a lot of different sample rates / bitdepths / channels you'll have to configure DSP studio to handle formats outside of the range of your DAC.
(don't forget to select menu option 4 after making changes to the user defined profile).
-
Right, it flat won't work on a port other than 52199.
Is there a way to reset the configuration to as it was received, and ignore any changes made in the GUI? I had changed the GUI port to 52199 and turned off server mode, and was able to use Id as a renderer. But after I returned to text mode w/hdmi it is no longer seen by any machines listening on 52199. I'm highly suspect that the GUI mode has left something in a strange state that isn't getting corrected or perhaps correctly utilized in text mode. Yes, I did use option 4 after the changes in GUI when it was working.
I did the update, no issues. Went very quick and smooth. But since it was specific to the segmentation issue, it made no difference to text mode not allowing it to be a renderer. I'll go back now and check what GUI thinks.
--Bill
-
As shipped the Id is a renderer only.
If one is using the HDMI output there are 2 text mode defaults, one headless which means the Id will boot without an attached monitor. The other initializes the HDMI. That should only be necessary if the audio device requires initialization.
The server toggle enables the Id to serve files, and it will then show the access code at the main menu.
The license problem comes from a problem with the user mode as the Id was shipped. If you choose one of the defaults, analog or hdmi for example the licensing will return. Any changes you make afterward are saved when you choose the user mode. Next time booted in user mode the license will be there.
When you choose the user mode item from the main menu, it saves the current settings across a reboot.
Guys, it seems to me that a preliminary release documentation (one page would do) which at the very least contains the points mentioned by Bob and Jim a few messages earlier and contains a reference to the URL of this thread for more breaking information. Something like:
- As currently shipped the Id is a remote renderer only, and operates on port 52199 only. It will also play locally with a local or remote library but only in GUI mode.
- If one is using the HDMI output for audio there are 2 text mode defaults, one headless (#9)which means the Id will boot without an attached monitor. The other (#10) initializes the HDMI device. That should only be necessary if the audio device requires initialization.
- The #5 server toggle enables the Id to serve files, and it will then show the library access code at the main menu. The same code is used for the DLNA renderer ID.
- When you choose the #4 user mode item from the main menu, it saves the current settings across a reboot. Use this after making changes in GUI mode that you want to have carried over to the next boot in text mode.
- Refer to the thread http://yabb.jriver.com/interact/index.php?topic=89498.0 (http://yabb.jriver.com/interact/index.php?topic=89498.0) for up to the minute changes and updates.
...or some variation.
--Bill
-
I'm glad it's working and thanks for the suggestions. The Installation Instructions are linked in the first message of the two Id threads. It has a link to this thread.
Those links will be on a slip included in the packages we ship now.
A link to both was sent by e-mail this morning. We didn't send one to you since you're already online.
Your tips belong in the Installation Instructions, in my opinion, but here are my comments on what you've written:
•As currently shipped the Id is a remote renderer only, and operates on port 52199 only. It will also play locally with a local or remote library but only in GUI mode.
The restriction to 52199 would be news to us, but we were testing it when I left work. It does work as a DLNA Server.
•If one is using the HDMI output for audio there are 2 text mode defaults, one headless (#9)which means the Id will boot without an attached monitor. The other (#10) initializes the HDMI device. That should only be necessary if the audio device requires initialization.
I believe that's in the instructions.
•The #5 server toggle enables the Id to serve files, and it will then show the library access code at the main menu. The same code is used for the DLNA renderer ID.
This isn't right: "The same code is used for the DLNA renderer ID."
•When you choose the #4 user mode item from the main menu, it saves the current settings across a reboot. Use this after making changes in GUI mode that you want to have carried over to the next boot in text mode.
That's correct.
•Refer to the thread http://yabb.jriver.com/interact/index.php?topic=89498.0 for up to the minute changes and updates.
Already linked, but easy to miss.
Your "preliminary release documentation" should, in my opinion, be just a link to the Wiki. It's confusing to have docs in multiple places. The wiki can be changed on the fly so that things we learn are available quickly.
Thanks for your help and for your patience in solving the problem. I've modified the Installation Instructions.
-
Regarding ports, Bob realized that ports below 1024 can't be set without root privileges. So that may be what happened. It prevented networking from starting.
-
My alternate port for MC media is 52190. But at this moment everything is on 52199 and I'm getting the same behavior as yesterday. In GUI mode, No rendering, but the ID# of the renderer does show up in Playing Now, and I can select it. But when I try to play something, the artwork appears briefly in the Id's display screen (lower left) and four seconds later, the artwork for the next track plays, on and on. No audio. I checked the obvious audio parameters and tried a couple of variations that shouldn't make any difference...they didn't.
I issued #4 and did a reboot to GUI. Shortly after it init'd the HDMI port, the whole system locked up with a blank screen. I had to hard-power it off. When it rebooted to GUI mode, it had started again with the "Trial period has expired" messages. Second reboot, same thing. Then I tried two text reboots (one headless and one with hdmi) and no DLNA Renderer showed up in my other MC's, but no trial period messages visible.
On the plus side, there hasn't been any segmentation fault errors during or just before reboot as there were.
Back to GUI once more, and this time it's NOT complaining about trial expiration, and the renderer ID shows up in my other MC's, but it's still not playing with the same behavior as described above.
Is there a way to reset the shipped defaults? I'm comfortable in the Unix world if that is of any help.
--Bill
-
Bill,
sent you a PM.
Bob
-
It looks like Samba isn't turned on unless the server mode is set on the Id. Then you can use Windows networking to copy files to the Id. I put them under Media, but they may need to be in a directory called Music under Media. I had to import them manually.
When I tried playing from the server to my phone (using the Access Key that is displayed on the Id's text menu), they wouldn't play. They are APE files and I think it must have been trying to convert them to MP3, or maybe because the phone doesn't support APE.
When I tried the same thing on my laptop, using the phone as the controller, they played. I could also play them to my HTPC.
-
It looks like Samba isn't turned on unless the server mode is set on the Id. Then you can use Windows networking to copy files to the Id. I put them under Media, but they may need to be in a directory called Music under Media. I had to import them manually.
Samba should always be on. The server mode switch doesn't affect that. Will check the import settings. Perhaps it doesn't work with a symlink. In user mode you could set /export/media as a watchfolder.
When I tried playing from the server to my phone (using the Access Key that is displayed on the Id's text menu), they wouldn't play. They are APE files and I think it must have been trying to convert them to MP3, or maybe because the phone doesn't support APE.
Yes, it's probably missing lame for conversion. Will catch that in an update.
When I tried the same thing on my laptop, using the phone as the controller, they played. I could also play them to my HTPC.
Probably because they aren't being converted in that case.
-
Split Linked Zones Questions (http://yabb.jriver.com/interact/index.php?topic=89695.0)
-
Maybe this is a little early for bugs in the GUI area of Id, but I had been running the GUI version for a couple of days, and this morning found this on the screen.
-
On the Options menu regardless of where it appears, make the #6 Check for Updates, actually check for updates! If there are no updates DON'T reboot!
Allow renaming of the renderer. It can be a bit confusing recalling MAC addresses if multiple renderers are in use throughout the house.
When Id or another renderer reboots (regardless of reason) and it is currently being fed by a server, have the initiating end recognize when it's back, reconnect and continue the play where the server is presently. Especially in the case of linked DLNA zones, the only way to get that missing renderer back up and playing currently is to manually stop and start the Server play list in progress.
I imagine these are already in the consideration list, just saying...
--Bill
-
Another question or two now that i have ordered mine and it will be on its way soon:
Does buying an Id automatically grant us a licence to the Linux version of MC too?
If so, may I clone the drive and put it the clone in my existing NUC?
-
Maybe this is a little early for bugs in the GUI area of Id, but I had been running the GUI version for a couple of days, and this morning found this on the screen.
I'm not sure that's related to the GUI but it's possible.
There is one Intel Bios update available for the NUC you have. It's on rev 34 now.
Two fixes might affect the Id. There was something changed in the USB2/3 firmware and the Wireless (which of course only affects people using that).
-
On the Options menu regardless of where it appears, make the #6 Check for Updates, actually check for updates! If there are no updates DON'T reboot!
Yes, this will be done.
Allow renaming of the renderer. It can be a bit confusing recalling MAC addresses if multiple renderers are in use throughout the house.
It can be renamed in client MC's. The presentation page might be changed to do that as well.
When Id or another renderer reboots (regardless of reason) and it is currently being fed by a server, have the initiating end recognize when it's back, reconnect and continue the play where the server is presently. Especially in the case of linked DLNA zones, the only way to get that missing renderer back up and playing currently is to manually stop and start the Server play list in progress.
I imagine these are already in the consideration list, just saying...
--Bill
This is probably somewhat more difficult, perhaps Matt has a comment?
-
Another question or two now that i have ordered mine and it will be on its way soon:
Does buying an Id automatically grant us a licence to the Linux version of MC too?
If so, may I clone the drive and put it the clone in my existing NUC?
Thanks for your order. You have mail at your forum account.
We don't have the ability to make Id's remotely and we have our hands full right now. Maybe in the future we'll find a way.
In the meantime, you can use the Id with any compatible DLNA Server, including MC.
-
I'm not sure that's related to the GUI but it's possible.
There is one Intel Bios update available for the NUC you have. It's on rev 34 now.
Two fixes might affect the Id. There was something changed in the USB2/3 firmware and the Wireless (which of course only affects people using that).
Ok, I've updated the BIOS to rev 34.
Then I got stuck behind the Trial version dialog each time I tried to boot to GUI. That seemed pretty consistent, until I booted into HDMI mode, and then into GUI. No more trial version dialog. I don't know if that sequence will always clear it, but going into headless mode and then to GUI mode didn't change anything.
One other peculiarity of note. The first boot after the BIOS update I just let it come up in what was my previous default, headless mode. The system came up and was running, but there was no display at all. So assuming the Options menu was actually 'there', I blind-entered a reboot command into the headless mode (my default then). On that boot everything worked normally. Maybe the newer video drivers are also needed in the next build? Probably only an issue (if it is) for early adopters.
--Bill
-
The 139 software update for Id seems to be working fine here.
-
I got the Id the other day and now pretty much got it working without too much problem with my DAC, everything syncs up with libraries, control from the GUI or my android phone, all fine but the audio from the MC server is always MP3 ( files are all PCM and DSD ) , no matter what I change in the server DNLA settings, or at the Id, I get MP3 and then converted to 44.1 in the Id for playback via USB to the DAC. and ideas for me to check?
-
I got the Id the other day and now pretty much got it working without too much problem with my DAC, everything syncs up with libraries, control from the GUI or my android phone, all fine but the audio from the MC server is always MP3 ( files are all PCM and DSD ) , no matter what I change in the server DNLA settings, or at the Id, I get MP3 and then converted to 44.1 in the Id for playback via USB to the DAC. and ideas for me to check?
When connecting from MC to MC, the conversion options are specified on the CLIENT MC under Options->Media Network->Client Options.
-
The 139 software update for Id seems to be working fine here.
I guess I spoke too soon.
I had Id 139 running all night in GUI mode with no issues. In order to do some testing on the originating MC, I unlinked Id from the local player. Id kept playing from the playlist it had in memory, so I pressed the stop button on Id to stop. I left the room for an hour or so, and when I came back it had crashed. Here's a snap of the screen.
-
finally got it playing off the server correctly, had it all going fine, did a restart after moving things around, now is asking for a license key, I got one for extended trial again, put the code in, said Ok, then nothing happened on the GUI, restarted it and now its stuck on trail expired and no way out
-
Reset the mode. Try GUI, then text. Someone else reported the same problem (maybe in this thread).
-
just tried it 3 times, to HDMI and back but no go.
-
When connecting from MC to MC, the conversion options are specified on the CLIENT MC under Options->Media Network->Client Options.
I asked Bob to expand on this. Here's what he said:
When MC is pushing to any other MC, the receiving MC appears as a DLNA Renderer. Conversion, in this case, is controlled by the DLNA server settings on the "pusher". This is under "Add or Configure DLNA Servers".*
When MC on the Id is pulling from another MC (using the Id in GUI mode, and connecting to another MC's library server), the conversion is set in the Id's Media Network Client Settings.*
* Both of these are in the Media Network section of MC's options.
-
thanks for the explanation, once I got the MC at the server set right it was no longer converting, I did not know where to find the correct settings at the server side.
-
Reset the mode. Try GUI, then text. Someone else reported the same problem (maybe in this thread).
Yeah, that was me. It's pretty much phase of the moon at that point. Sometimes powering completely off for a while and coming up cold makes a difference, but not always.
--Bill
-
its dead now, I gave up for now, I tried power off, rebooting many times its stuck in wanting a key,
-
It crashed on the shutdown?
Might be a kernel issue (though I've not been able to duplicate it).
-
its dead now, I gave up for now, I tried power off, rebooting many times its stuck in wanting a key,
Try running menu option 77 (not shown), restores original settings.
Then run an update.
-
thanks for the explanation, once I got the MC at the server set right it was no longer converting, I did not know where to find the correct settings at the server side.
If you have other DLNA devices that require conversion you can create multiple servers and right-click on the zone then "associate with DLNA server" to choose what groups of settings that will be used with which renderers.
-
what I mean is it gets no further than asking for the key, I tired to do an update, no change. so all boots up but the MC app does not start as its asking to pay for it or supply a key.
-
later on I can try to select the 77 and update, but for now I had to reconfigure everything and its out of the system so I can play music.
-
No update today. Unrelated focus issues.
-
I did the 77 reload, and reset all parameters and now have it back working, headless mode and playing again with control from my android phone, so back to where I left off.
-
No update today. Unrelated focus issues.
A couple more buglets from the last Id update.
1. In the GUI mode if you click on the Audio button (right side in group of three buttons), then Playback Options, then Audio Device->Device Options, MC will disappear. No messages or anything. The watchdog is no longer working, so the only way back is to reboot. In the scrolling text one of the first things you see is a reference to a segmentation fault.
2. Please bring back shell access from the desktop in GUI mode.
-----------------
3. Not from the last update, but in general, there's a sync up problem when DLNA Id is linked to an ongoing play list. It doesn't start playing most of the time, and if/when it does it isn't synced with the playlist. I've waited for a new song to see if that wakes it up, but it doesn't. The only thing that gets everything going correctly is on the DLNA server, stop the playing in progress and start it again.
4. Also, on the library server, the id-<macaddr> appears and disappears predictably when Id is up or down. But a reference to it from another MC (There: id-<macaddr> doesn't follow. It always stays showing once it has appeared there. As a result, the library server will sometimes display a dialog window complaining about a directive from the remote MC that it can't communicate with id-<macaddr>. In that state it will not recover until an operator hits OK on the server.
--Bill
-
There is an update available, MediaCenter updated to 19.0.141.
This fixes several of the issues listed (based off of a timer problem) and adds a call to keep the screen alive.
The HDMI screen switch is enabled also.
-
There is an update available, MediaCenter updated to 19.0.141.
This fixes several of the issues listed (based off of a timer problem) and adds a call to keep the screen alive.
The HDMI screen switch is enabled also.
It worked fine for me.
What is the "HDMI screen switch"? The initialization?
-
It worked fine for me.
What is the "HDMI screen switch"? The initialization?
4. NEW: Screensaver control enabled (turn on hdmi screen option under Audio).
It appears that when a track starts playing the screen time is reset independently though it's possible that long tracks could outlast the timer in which case if you are using HDMI you might want to try the switch mentioned above.
-
Prior to updating to 141, I had been running Id in GUI mode with software 139 for a couple of days, full screen. While it was still rendering, I was not able to bring it out of full screen or close it. The commands simply did not function. I brought the options menu to the top and it ignored the first few attempts to reboot, but finally did with option 2 (headless text). But it came back up in GUI mode that time. Next attempt took it to Headless Text, from which I successfully (?) installed the update.
Rebooting to GUI mode I was presented with "The trial period has expired." message. Subsequently rebooting to Headless Text or Text with HDMI both completed, but the software must have still thought it was in trial mode because no renderer ID number showed up on any MC, in any mode. I waited for ten minutes each time.
I can ping its network address no problem.
What to do next?
--Bill
-
Prior to updating to 141, I had been running Id in GUI mode with software 139 for a couple of days, full screen. While it was still rendering, I was not able to bring it out of full screen or close it. The commands simply did not function. I brought the options menu to the top and it ignored the first few attempts to reboot, but finally did with option 2 (headless text). But it came back up in GUI mode that time. Next attempt took it to Headless Text, from which I successfully (?) installed the update.
Rebooting to GUI mode I was presented with "The trial period has expired." message. Subsequently rebooting to Headless Text or Text with HDMI both completed, but the software must have still thought it was in trial mode because no renderer ID number showed up on any MC, in any mode. I waited for ten minutes each time.
I can ping its network address no problem.
What to do next?
--Bill
Try running 77 to restore the Settings (including the license).
I'm thinking that you are having enough trouble with it that I can't explain that it might be better to swap it out so we can get a look at what's going on with yours.
-
Try running 77 to restore the Settings (including the license).
I'm thinking that you are having enough trouble with it that I can't explain that it might be better to swap it out so we can get a look at what's going on with yours.
That's your call, Bob. I'm happy to exchange it if needed.
77 restored the licensing ok and it's working now. However, on the other MC's, it's showing as id-<macaddr> on all of them, instead of only on the fileserver, and There: id-<macaddr> on the others as it has been doing before. I can force each client MC to display correctly by completely restarting it. Plus, the server MC cannot send to it as a renderer. It just tries each song, then in four seconds or so, skips to the next, and on and on. The server was completely restarted as well. Settings on Id for DLNA use seem correct. I just tried restarting Id again to GUI, but same results. One last Id reboot to HDMI text, still no op as a renderer.
--Bill
-
bill, you might try to check your settings in your GUI play options for what outputs are assigned from the Id to your DAC, I am using USB out to an XMOS device and found that when I did the 77 reload for the same reason, it changed these to back to the default, it actually worked once but when i rebooted it changed and no longer worked so i had to reselect it. I find that with my DAC i need to select the frontCARD=X20 for out to the DAC, if not i got playback jumping from track to track as you note, i think it does not see a device to play to and skips around, took me a while to figure out why this happened when i first got it.
-
Bob, I had suspected something along those lines, but the first thing I did in the GUI was to set the audio device to front mosquito. Last night I just gave up and turned it off (which I don't usually do) from HDMI Text mode. This morning I turned it on to HDMI Text mode, did another 77 and this time it came up and just worked -- except it was using the HDMI audio channel. So I rebooted to GUI and changed the playback device appropriately, and now it's working fine. Go figure.
--Bill
-
Finally the Id has arrived.
However I was unable to view the GUI or text menus on my plasma by HDMI. the plasma is connected via my AVR, though connecting it directly made no difference. Oddly using MC on my PC and JRemote I was able to use it as a renderer actually play music out through it to the AVR.
So, any ideas how I get to the GUI screens, and could I get access via something like VNC?
Regards
-
Did you update the software?
If you can't see it, the menu is shown in the instructions on our wiki.
You might try a direct connection to the TV.
-
Couldn't display anything. Tried connecting it directly to the TV. No display. No text screen, no GUI.
It's clearly running and MC can 'see' it from my PC, and as I say JRemote connects.
But without the display running I can't change any of the settings, upgrade or anything. Will try and connect it to a monitor tonight. However it would be useful to be able to remote into it from another device.
-
Even though it should always show its menu once a screen is connected, you can try to reboot it into GUI mode.
To do that, boot it up and give it a bit to be ready, then simply enter "1" (only the number one) and press Enter, which is the menu command for GUI mode. It'll reboot shortly after and hopefully come up with an image for you.
-
Try the update. It's option 12. Type 12 and hit enter.
-
So, having taken the id into the study, I find it can output to a monitor fine, but not the Panansonic Plasma.
Worked first time against the monitor. Of course the limitation of this is I can't set it up against the AVR or Belcanto, because they're next to the hi fi and the monitor is in another room.
I'm a bit stumped now.
Wondering about being able to telnet or VNC onto it.
Any ideas ?
-
Sounds like your TV just doesn't support the low resolution that is used in text mode.
You could boot it in GUI mode and then try it on the TV again.
-
So with the Id now working, and upgraded, how do I go about playing tracks from my DNLA server.
I see it listed but each time I try and load the library it hangs.
-
Loading a DLNA library can take a long time.
-
Are you using a phone as a Controller? iOS or Android? That's the easiest.
Try it first by using a Windows or Mac machine. Play anything in MC to your Id. This should be described in the instructions. If they are unclear, let me know
-
All very odd, however
A quick look before coming to work, showed the synology DNLA 'library' loaded.
Firing up JRemote on my ipad, displayed the various albums. loading the album thumbnails appeared a bit slow, but I assumed this was because it was the first time loading.
I'll have a better play this evening.
A couple of random questions:
1. Adding new tracks to the server, will I need to reload the 'library'.
2. I guess the MC playlists available on my PC/MAC won't be available on the DLNA server.
3. Is there any real point in running it headless? If I simply remove the keyboard and mouse, wouldnt that be enough?
4. I'd still like to run VNC. Presumably I just need to find a way to install it
-
There isn't any way to install VNC. It's meant to be a CE device, not a Linux computer.
You could remove the keyboard and display to try it.
-
All very odd, however
A quick look before coming to work, showed the synology DNLA 'library' loaded.
Firing up JRemote on my ipad, displayed the various albums. loading the album thumbnails appeared a bit slow, but I assumed this was because it was the first time loading.
I'll have a better play this evening.
A couple of random questions:
1. Adding new tracks to the server, will I need to reload the 'library'.
2. I guess the MC playlists available on my PC/MAC won't be available on the DLNA server.
3. Is there any real point in running it headless? If I simply remove the keyboard and mouse, wouldnt that be enough?
4. I'd still like to run VNC. Presumably I just need to find a way to install it
Not all DLNA servers are created equal! ;) MC19 and Id as DLNA server work much faster than the lite DLNA versions running on many devices out there in the market.
Many of the appliance DLNA servers (like the synology) are based on miniDLNA which has to reindex everything after a NAS reboot. MC19 and Id running MC19 don't have this issue, 1. because they have more processing power, and 2. because of the way they work, MC19/Id has a fast database engine so it's an "instant on" DLNA server, where as many other DLNA servers, after a reboot, you have to wait and wait and wait... before you can access information from another DLNA renderer. That's the main reason for me switching from the Seagate Wireless drive to direct USB drive. The seagate runs the same miniDLNA as the Synology and would take upto 3 hours to reindex the DLNA database after a reboot which meant MC19 and the Id would take a while to update it's library when connecting.
The first time you access the Synology DLNA server from MC19 or the Id it will be slowish until its cached the images and data. It depends on the DLNA Server it's not a fault of MC19 or the the Id. A fast DLNA server on a fast network will show almost no delay. MC19 to Id, and Id to MC19 is very quick.
1. Adding new tracks to the server, will I need to reload the 'library'.
Not sure if the auto-update works for DLNA but I select the original Id library and then reload the DLNA library to update it.
2. I guess the MC playlists available on my PC/MAC won't be available on the DLNA server.
Yes as per my PM - You can get around this a number of ways. I'll go into this another time in more detail as its a lengthy answer.
The way to get full playlists is to mount the NAS on another PC in the house that runs full MC19 and run the Id connected to the library of that machine.
It means an extra machine running, but it's pretty straight forward and actually how I run the Id now at home since I have a media server/HTPC on 24/7.
Any changes I make on my main HTPC library are also accessible from the Id, including playlists because its loaded the HTPC library instead of its own local library.
You can also export your MC19 playlists to a folder on the NAS and the Id will import them over DLNA.
When I'm in the car I run the Id local library with an attached 2TB USB drive that I sync from my HTPC using a portable profile for the USB drive. The sync profile for the drive also dumps my playlists which I can import on the Id when it's connected to the USB drive. I'll post some instructions up when I have more time, its pretty simple once you understand how the Id and MC libraries work.
3. Is there any real point in running it headless? If I simply remove the keyboard and mouse, wouldnt that be enough?
Running it in text mode is currently more stable but there's no reason you can't use a wireless keyboard/mouse (not Bluetooth) in GUI mode. You can unplug the keyboard once it's booted into either text mode or GUI mode if you're not using a wireless keyboard, and just control it via JRemote/Gizmo or another MC19 device.
I currently use a mixture of iPhone, iPad and Surface Pro 2 tablet depending on what I'm doing. I usually use JRemote on the iPhone as a remote, JRemote on the iPad for browsing/remote, and the surface pro 2 tablet for anything more heavy duty using the full MC19 to remotely control the Id.
For music the Id does everything my dedicated HTPC does, and it operates identically with all the above devices. That's the beauty of it!
4. I'd still like to run VNC. Presumably I just need to find a way to install it
That might be possible at some point, but that's a lot of work to get it working for non Linux users in an easy way and reliably.
Once the Id is setup, you should be able to do almost everything you need to do with JRemote or Gizmo apart from Library management, which is why I recommend loading up a library from another machine.
The whole concept of the Id is that it's a high quality plug and go music appliance that leverages all the goodness of MC19 but without being a PC. It's not trying to be a PC, and it's not really meant to be a media server. It will do it for audio, but there are far better ways to do that at this time using MC19 on another machine.
Bob's adding configuration controls from a web browser, which may be the way forward for everything in the future. When they get video working, it starts to become a better proposition as a server, but the CPU is really only powerful enough for rendering video locally.
-
The whole concept of the Id is that it's a high quality plug and go music appliance that leverages all the goodness of MC19 but without being a PC.
For music the Id does everything my dedicated HTPC does, and it operates identically with all the above devices. That's the beauty of it!
Well said. Thanks.
We're aiming at making it easy to set up and run. People who want it to do more than it does may choose to run the standard JRiver Media Center for Linux, but that's a lot more technically demanding.
-
A bit of a update with my use of the Id. all in all it is all working quite well now for about 2 weeks, I have a Win 7 PC with MC19 as the server now moved to another part of the house, and the Id at my DAC in my listening room, all connected with Cat5 to the router, run it all from my android phone with Gismo, library is on the Id too, syncs up if i make changes at the server, plays everything and hi resolution including DSD, so once its up and going it works great and really does what i want it for, which is not to have the PC in my listening room.
The problem is getting it to consistently come up. When I first got it, I setup with the GUI, then changed to running it as headless as the reason to use this is not to have a PC as such in my listening room, but this proved to be problematic as i would have to repeatedly restart the Id, and in the end connect the monitor to shut it down or reboot with 98 or 99 which it seemed to like better than pushing the power button on the Id, and then it might come up more consistently. I gave up on that and now leave it in GUI and turn off the monitor, that way i see it boot completely first. A lot better but even then it will not always boot the MC app, or stop and tell me that the license will expire in 20 days, so i have to clear that then it going. the issue is not it booting the OS, but it appears that it does not start the MC app completely, or that's what seems to be happening in the headless mode and its left hanging. this is really the only issue i have using it, is there a fix for some of this?
-
Thanks for the report. Did you try updating?
-
not since a week ago when I had an issue with the license before, I can do an update now and see if that improves things.
-
We've fixed a licensing problem in the last couple of days, but it may not be in the Id version yet. You could read about it on the Linux board. Sorry for the problem.
Expect the experience to get steadily better. We appreciate your patience.
-
I just did an update, after which when I re-started. The screen went black and I had to pull power to get it to boot again. It does that when you change from headless back to GUI sometimes too and the only way out it pull the plug. Got it going, just for testing i did a 98 reboot, same thing had to pull the power to get it going. now i set it to headless and did a restart with the on off button a few times, so might be behaving a bit better for headless operation but then again i still have the monitor connected to see what's going on as there seemed to be some correlation with it starting up in the past if the monitor was connected, so just did a hard button restart with the monitor off and it came back up again. , i will run for a few days and let you know how it goes, and in a few days i'll do another update, btw sounds great too.
-
I just did an update, after which when i re started it, screen when black and i had to pull power to get it to boot again ...
It was probably still working on the update. We need to message that better.
btw sounds great too.
Thanks.
-
It was probably still working on the update. We need to message that better. Thanks.
For some reason the shutdown doesn't always complete after an update. Working on that.
-
So finally up and working.
My setup is currently
The Id.
A Marantz AVR
A Bel canto 3.5 via a Vlink USB/Spdif
A Synology NAS running the DLNA server
JRmote on an ipad
Other Stuff
A PC managing ripping, meta data management, which nowadays is rarely used
A Mac Mini, currently in the lounge, which i'd hope the Id will replace.
A Sonos network
Things that I've noticed.
1. Mixing tracks of different bit depths occasionally trips the Id up, but all bit rates up to 24/196 via the Bel Canto work fine.
2. Unplugging the keyboard/mouse doesn't seem to bother the Id, making me wonder if there's any value in the headless setting.
3. The bigger limits of a DNLA server seem to be around the meta data offered up by the server than anything else, plus some issues around thumbnails
4. Can't spot any SQ difference between using the Id and a Mac Mini, which is a good thing, though more testing is needed.
5. Identifying the USB DAC within MC required a bit of trial and error.
6. JRemote works well, though thumbnail image loading is a bit sluggish.
7. International postage is a night mare :)
Things I'd like to see
1. Network drive access, rather than the DLNA servers.
2. Remote access to the id from a PC, thus saving the need to hook up a monitor, keyboard and mouse.
3. More time to listen to music !
Anyhow the adventure continues.......
-
Got my Id up and working without drama, so thank yous for all the effort to make that the case.
I do have a question, though. It seems I am not able to turn off repeat mode, am I missing something? Repeat is checked in the menu in GUI mode, but grayed-out and unselectable. I'd prefer for playback to simply end when it finishes a playlist--this is possible, right?
-
If you're using it as a Renderer (playing to it from another machine), then the setting that matters is on the other machine. The same is true if you're playing to it by controlling it from a phone.
Nice to hear that it went well. Thanks.
-
My Id has been cutting out after playing about 4 tracks.
At first I thought it was losing the network connection to my PC library (JRiver 19 windows).
It would play again if I manually used a mouse to click on play again.
But it would stop again after a few more songs.
Then it started displaying a "could not play with this audio device" message.
After a lot of investigation (and numerous reboots) it appears that the Id no longer will recognize my USB DAC.
It plays back fine using HDMI audio settings (through the Sony TV and optical out to the DAC - Leema Elements).
There are now DAC options being displayed in audio settings (worked fine through DAC last week).
the main reason I purchased the Id was to be able to utilize USB audio.
-
My Id has been cutting out after playing about 4 tracks.
At first I thought it was losing the network connection to my PC library (JRiver 19 windows).
It would play again if I manually used a mouse to click on play again.
But it would stop again after a few more songs.
Then it started displaying a "could not play with this audio device" message.
After a lot of investigation (and numerous reboots) it appears that the Id no longer will recognize my USB DAC.
It plays back fine using HDMI audio settings (through the Sony TV and optical out to the DAC - Leema Elements).
There are now DAC options being displayed in audio settings (worked fine through DAC last week).
the main reason I purchased the Id was to be able to utilize USB audio.
Im sure we can help get you going again.
I assume you meant it doesn't show up under audio devices anymore?
Things to try if you haven't already.
I know you've probably done this but just for completeness.... Check your playing back in the right zone.
Reset all the DSP output settings to 48000hz.
Update the Id.
Try the DAC on your computer to see if it still works.
If the DAC has any cables, check the cables and try different cables if possible.
Try a different USB port.
Unplug any other USB devices from the Id.
Try starting in both the other txt modes 2 & 3 and then back in gui mode 1.
When testing in txt modes above, check in a web browser http://Your-Id-IP-address:52199/WebRemote/audiodevice.html and see if the DAC shows up in the list. (use your Id IP address) select the DAC if it shows up and then test.
2 last resort things to check - your choice which order you do them in but I would check the bios first.
Check Bios settings and that the usb ports are active.
Resetting the Id with option 77 will delete all your settings and you'll have to re-import your library but its the absolute last resort.
If all this fails then you might need to try borrow another DAC to see if it works before sending the Id back to be checked.
-
I am clearly doing something wrong. I managed to play from the Id for one evening, using MC19 on my Mac (mini) where the Id appeared under Playing Now. It took 3 hours of futzing around to get there because it didn't work as suggested. The sound was, however, extremely good.
After closing the system down, and re-booting each day since, the Id doesn't appear anywhere in MC19 on the Mac. I can see it everywhere on the Network on all Win & Mac machines but not in MC19 Mac.
If I switch to GUI mode, it appears as Id-XXXXX (Library Server) in the Mac's MC if I load the local Mac machine's MC library on the Id, then I can control the Id with JRemote but this is not what I want. I want the Id to simply be a renderer of the MacMini's MC19 library, over HDMI at fixed 24bit/48kHz, controlled from the Mac as a linkable zone. The Mac has Media Server enabled but not Library Sync. Switching modes 1, 2, 3 has no effect on this, nor does reset 77. Possibly I'm confused between Id MC19 settings in the GUI and running headless. The Id streams to a Smyth Realiser A8 over HDMI.
Other puzzlements:
Frequently the Id fails to initialize the HDMI from mode #3. The one time it worked as a renderer the volume was maxed and the volume options pertaining to System, Internal, Disabled didn't appear on the serving Mac's MC19. I can control volume other ways so that isn't a bother, just different to playing through, say, Apple TV using Airplay.
On the first page of this thread there are references to options #4, #5, #6, #10. I have none of these. I have only 1, 2, 3, 11, 12, 77, 98, 99.
Bob mention "server toggle" what or where is that?
Does #12 update both the Id OS AND it's MC19 or do I update MC through the GUI? It's 148 currently, which surprised me.
Marty
-
OK, sorry, I got this partially figured out: Dumbo here had unticked some advanced options in Media Center. The Id now appears in MC on the Mac and it plays (wonderfully) but how do I control the volume?
New problem - this appeared: -su line 1: 3231 Segmentation fault mediacenter19 /mediaserver > /dev/null 2>81
What should I do?
Marty
-
I think your getting confused with server mode, streaming and rendering.
Lets confirm first how your Id is connected.
From my understanding:
Mac Library Server > Id Renderer > Smyth Realiser A8 HDMI for audio.
Just saw your reply below as I was typing.. Looks like you sorted it.
-
Im sure we can help get you going again.
I assume you meant it doesn't show up under audio devices anymore?
Things to try if you haven't already.
...
Have done all that without much success.
USB cables are fine, settings checked, reset output to 48000hz.
Makes no difference as to what USB port is used.
All USB ports enabled in bios.
I had already done both upgrades when first installing the Id as I had a problem with the Linux license not registering (as per direct email with JimH).
Id bios will not update online, giving a message about cannot find identification number (or something like that).
The Id will recognize my Cambridge Audio Dac Magic in audio devices, but not the Leema Elements DAC.
It previously offered 2 DAC audio options when connected to the Leema Elements DAC.
The Leema Elements DAC works fine through USB audio in Windows (JRiver19) on my PC *Windows 8.1).
I haven't had time to try out the text modes option.
I don't understand exactly what you mean by "When testing in txt modes above, check in a web browser http://Your-Id-IP-address:52199/WebRemote/audiodevice.html and see if the DAC shows up in the list. (use your Id IP address) select the DAC if it shows up and then test."
Probably because I haven't tried it yet.
Sending it back for testing is a PITA (and expensive) as I am located in Australia.
-
Please see the "Audio Devices" section of the instructions here:
http://wiki.jriver.com/index.php/Id_Instructions
-
Other puzzlements:
Frequently the Id fails to initialize the HDMI from mode #3. The one time it worked as a renderer the volume was maxed and the volume options pertaining to System, Internal, Disabled didn't appear on the serving Mac's MC19. I can control volume other ways so that isn't a bother, just different to playing through, say, Apple TV using Airplay.
Marty
It looks like the when you switch between push/pull rendering and serving the MC DLNA get's itself in a knot.
After testing all the below and going back and forth I managed to create a situation where the volume control wouldn't work and the Id wouldn't serve media, the remote renderer said it couldn't play the media too. After restarting the remote renderer though it was fine. So it may just be a limitation of DLNA or it could be a bug in the Linux versions. It worked fine for all of the tests below until the last one.
It should work reliably as long as your not switching from server to renderer and from push to pull media.
----------------
From a windows MC19 client and also my windows HTPC server I can control the Id volume from both. Doesn't matter if im using internal or system volume on the Id they both control volume on the Id as a renderer just fine. Also JRemote controls the volume too.
The setup I just tested to verify the above is as follows.
I have all my MC19 systems and the Id set as DLNA Servers, DLNA Renderers and DLNA Controllers in the media Network settings.
Push audio from HTPC Library server > Id as Renderer to external DAC with internal Id library loaded (controlled from HTPC/JRemote and another Windows MC19 instance)
Pull audio from HTPC Library server > Id as Renderer to external DAC with HTPC library loaded (controlled from HTPC/JRemote and another Windows MC19 instance)
In all the above cases the volume control works just fine from any device.
This one wouldn't work though until I restarted the MC19 client.
Push audio from Id Library server > MC client as Renderer with its own local library loaded (controlled from HTPC/JRemote and another Windows MC19 instance)
Other puzzlements:
On the first page of this thread there are references to options #4, #5, #6, #10. I have none of these. I have only 1, 2, 3, 11, 12, 77, 98, 99.
Bob mention "server toggle" what or where is that?
Does #12 update both the Id OS AND it's MC19 or do I update MC through the GUI? It's 148 currently, which surprised me.
Marty
The options available now are what you have in your Id, the earlier threads are now not accurate as Bob changed a few options to simplify things.
Option 12 will update both Id OS and MC19 if it needs to, but most updates at this stage are just MC19 updates. I think there was an OS update when Bob updated the menu options recently though just as an example.
The GUI update wont work, all updates are done from the text menu.
-
OK, sorry, I got this partially figured out: Dumbo here had unticked some advanced options in Media Center. The Id now appears in MC on the Mac and it plays (wonderfully) but how do I control the volume?
New problem - this appeared: -su line 1: 3231 Segmentation fault mediacenter19 /mediaserver > /dev/null 2>81
What should I do?
Marty
Still some bugs being worked on. Just restart it.
-
Have done all that without much success.
USB cables are fine, settings checked, reset output to 48000hz.
Makes no difference as to what USB port is used.
All USB ports enabled in bios.
I had already done both upgrades when first installing the Id as I had a problem with the Linux license not registering (as per direct email with JimH).
Id bios will not update online, giving a message about cannot find identification number (or something like that).
The Id will recognize my Cambridge Audio Dac Magic in audio devices, but not the Leema Elements DAC.
It previously offered 2 DAC audio options when connected to the Leema Elements DAC.
The Leema Elements DAC works fine through USB audio in Windows (JRiver19) on my PC *Windows 8.1).
I haven't had time to try out the text modes option.
I don't understand exactly what you mean by "When testing in txt modes above, check in a web browser http://Your-Id-IP-address:52199/WebRemote/audiodevice.html and see if the DAC shows up in the list. (use your Id IP address) select the DAC if it shows up and then test."
Probably because I haven't tried it yet.
Sending it back for testing is a PITA (and expensive) as I am located in Australia.
Boot the Id into text mode 3 and follow the link Jim posted above to check if the DAC shows up.
The other thing you could try is plugging the DAC in AFTER the Id has booted. (give it a minute to detect it)
I just read the manual for your DAC and its a UAC2 DAC. It may have loaded in USB1.1 compatibility mode on the Id before when it was working.
Have you changed any settings in the DAC or the Id Bios? The USB ports must be in high speed USB 2 mode or the DAC wont work.
Where abouts in Australia are you? Maybe I can help you out. Im on Sydney's north shore.
-
There are also some differences between the front USB port on the ID and the rear ports. The front is USB3 the rears are USB2 and they are on different controllers IIRC. You might try changing those.
The segfault indicates MC died in text mode for some reason. After 60 seconds it is automatically restarted.
If you run in GUI mode, you can check the device settings for your USB DAC.
You should leave it plugged in during boot if possible or else when you go into MC settings the device will set to default if your DAC isn't there.
Whenever you run 77 you are resetting all of the saved parameters in MC and you'll have to reselect your USB DAC in MC.
-
Boot the Id into text mode 3 and follow the link Jim posted above to check if the DAC shows up.
The other thing you could try is plugging the DAC in AFTER the Id has booted. (give it a minute to detect it)
I just read the manual for your DAC and its a UAC2 DAC. It may have loaded in USB1.1 compatibility mode on the Id before when it was working.
Have you changed any settings in the DAC or the Id Bios? The USB ports must be in high speed USB 2 mode or the DAC wont work.
Where abouts in Australia are you? Maybe I can help you out. Im on Sydney's north shore.
Morning:
Thanks Hiltonk,
I'm in Ipswich Queensland.
The Id initially did not boot when first installed.
This was traced to the SSD dive not being firmly located into the connector (knock in transit?).
It initially took several boots for the Id to recognize the Leema Elements DAC.
It was good for a few days, then the DAC display changed after I updated the Id (to fix the license issue).
After the update the Leema Elements DAC changed it's sample rate input display from USB Async 44.1KHz No data (see http://www.leema-acoustics.com/documents/manuals/USB%20Driver%20Installation%20Windows%208.pdf) to USB Async 192 kHz No data.
The display on the DAC normally reports back the Sample Rate, ASYNC and FB< I > .
Two days later the Id started cutting out after playing a few tracks.
I have not changed any settings in the DAC or BIOS.
I have checked the audio devices via a web browser.
It only lists the default settings (see below).
WebRemote JRiver
Playing Now
Library
Audio Device
Devices
The list of audio output devices available to the Player zone.
The currently selected device is highlighted.
Null Output
default:CARD=PCH [ALSA]
front:CARD=PCH,DEV=0 [ALSA]
hdmi:CARD=PCH,DEV=0 [ALSA]
surround40:CARD=PCH,DEV=0 [ALSA]
surround41:CARD=PCH,DEV=0 [ALSA]
surround50:CARD=PCH,DEV=0 [ALSA]
surround51:CARD=PCH,DEV=0 [ALSA]
surround71:CARD=PCH,DEV=0 [ALSA]
sysdefault:CARD=PCH [ALSA]
Plugging in the DAC after the Id had booted made no difference.
When I plug in the Cambridge Audio Dac Magic it displays these settings:
WebRemote JRiver
Playing Now
Library
Audio Device
Devices
The list of audio output devices available to the Player zone.
The currently selected device is highlighted.
Null Output
default:CARD=PCH [ALSA]
default:CARD=Set [ALSA]
front:CARD=PCH,DEV=0 [ALSA]
front:CARD=Set,DEV=0 [ALSA]
hdmi:CARD=PCH,DEV=0 [ALSA]
iec958:CARD=Set,DEV=0 [ALSA]
surround40:CARD=PCH,DEV=0 [ALSA]
surround40:CARD=Set,DEV=0 [ALSA]
surround41:CARD=PCH,DEV=0 [ALSA]
surround41:CARD=Set,DEV=0 [ALSA]
surround50:CARD=PCH,DEV=0 [ALSA]
surround50:CARD=Set,DEV=0 [ALSA]
surround51:CARD=PCH,DEV=0 [ALSA]
surround51:CARD=Set,DEV=0 [ALSA]
surround71:CARD=PCH,DEV=0 [ALSA]
surround71:CARD=Set,DEV=0 [ALSA]
sysdefault:CARD=PCH [ALSA]
sysdefault:CARD=Set [ALSA]
This is the same menu that used to be It is the iec958:CARD=Set,DEV=0 [ALSA] audio device setting that I previously used to load the Leema Elements DAC.
It's definitely not the Leema Elements DAC that is causing the problem.
I tried a creative fix this morning. I plugged the DAC Magic back in a selected the iec958:CARD=set,DEV=) [ALSA] audio device setting and then unplugged the USB from the DAC Magic and plugged in the (powered on) Leema Elements DAC.
Eureka, it worked! For how long I don't know. ;D
The Leema is displaying the correct 44.1KHZ Sample Rate, ASYNC and FB< I > .
The Id is also back in Network "Computer" on my main PC (having disappeared when the fault arose), although it was always displayed there in "Media Devices" (No conversion) and "Other Devices" as a media server.
I have noticed that with the Leema Elements DAC connected there are two DAC audio options.
Should I stay with the iec958:CARD=DAC,DEV=0 [ALSA] or use the front:CARD=DAC,DEV=0 [ALSA]
WebRemote JRiver
Playing Now
Library
Audio Device
Devices
The list of audio output devices available to the Player zone.
The currently selected device is highlighted.
Null Output
default:CARD=DAC [ALSA]
default:CARD=PCH [ALSA]
front:CARD=DAC,DEV=0 [ALSA]
front:CARD=PCH,DEV=0 [ALSA]
hdmi:CARD=PCH,DEV=0 [ALSA]
iec958:CARD=DAC,DEV=0 [ALSA]
surround40:CARD=DAC,DEV=0 [ALSA]
surround40:CARD=PCH,DEV=0 [ALSA]
surround41:CARD=DAC,DEV=0 [ALSA]
surround41:CARD=PCH,DEV=0 [ALSA]
surround50:CARD=DAC,DEV=0 [ALSA]
surround50:CARD=PCH,DEV=0 [ALSA]
surround51:CARD=DAC,DEV=0 [ALSA]
surround51:CARD=PCH,DEV=0 [ALSA]
surround71:CARD=DAC,DEV=0 [ALSA]
surround71:CARD=PCH,DEV=0 [ALSA]
sysdefault:CARD=DAC [ALSA]
sysdefault:CARD=PCH [ALSA]
It has been an extremely time consuming and frustrating exercise.
What concerns me is that I still don't know what went wrong and of more concern, will it do it again ?
Early Evening:
Well, my elation was short lived!
I played an entire album without any problems.
I had to go out for a while, so shut everything down.
When I rebooted the Id, the Leema Elements DAC displayed a sample rate of 192KHZ.
When I played the first track of an album, the display rate reverted to 44.1KHZ.
The Id stopped after only playing 1 track.
The Id is no longer displayed in "Network" under "Other Devices" (No media Server).
The iec958:CARD=DAC,DEV=0 [ALSA] setting is still displayed in audio devices.
So where do I go from here?
Is the return freight to JRiver covered by them under warranty?
-
I found the reason why the Id often does not initialise HDMI in mode #3. Since I run headless I don't see this during boot:
"The following are warnings that were detected during this boot.
These can be viewed in Setup on the Event Logs Page.
WARNING: Processor Thermal Trip
Press the Enter key to continue."
Connecting a keyboard and actually pressing Enter at this point sends the Id into a state where it is active as a renderer (visible in MC on Mac) but not having intialized HDMI. That requires shutdown and another reboot.
It does appear that I can't run without a monitor and keyboard attached. The warning must surely be erroneous?
-
I found the reason why the Id often does not initialise HDMI in mode #3. Since I run headless I don't see this during boot:
"The following are warnings that were detected during this boot.
These can be viewed in Setup on the Event Logs Page.
WARNING: Processor Thermal Trip
Press the Enter key to continue."
Connecting a keyboard and actually pressing Enter at this point sends the Id into a state where it is active as a renderer (visible in MC on Mac) but not having intialized HDMI. That requires shutdown and another reboot.
It does appear that I can't run without a monitor and keyboard attached. The warning must surely be erroneous?
I've seen this a couple of times. I'm starting to think it's a bios bug.
Is this on a cold start or reboot?
-
Pegasus59, the device name is ALSA suggestion.
I don't have your device however from what I've seen you might be able to use either.
You should try the different USB ports and perhaps a different cable.
As we all know, USB can be touchy at times.
There is an update coming which will bump the kernel version that may be helpful to you.
-
I've seen this a couple of times. I'm starting to think it's a bios bug.
Is this on a cold start or reboot?
I see this too, on every boot, warm or cold. I'd not be concerned except for the 'press a key to continue' gets in the way. Probably bios as you say since the unit runs very cool.
--Bill
-
Pegasus59, the device name is ALSA suggestion.
I don't have your device however from what I've seen you might be able to use either.
You should try the different USB ports and perhaps a different cable.
As we all know, USB can be touchy at times.
There is an update coming which will bump the kernel version that may be helpful to you.
I have tried both rear USB ports and two different cables without any change in the performance (or lack of it).
As the Leema Elements DAC worked fine before the software upgrade, I can only surmise that something in the software upgrade is causing the USB recognition problem.
-
I see this too, on every boot, warm or cold. I'd not be concerned except for the 'press a key to continue' gets in the way. Probably bios as you say since the unit runs very cool.
--Bill
Yep, cold or warm. Headless isn't possible whilst this persists.
-
Bob. You might try Intel.
-
I don't get it on mine though. Im on Bios 34.
-
Looking on the NUC community board it seems this is a known issue. The bios settings for the thermal trip points are a bit awkward. Here is the thread comment and what to try changing them to:
Update 2014-06-28:
I looked in the bios settings for the fan and observed that the 3 temperature points look awkward:
- critical temp 88 degrees
- control temp: 80 degrees
- full fan temp: 88 degrees
It looked to me that full cooling only kicks in when critical temperature is reached (too late), so I changed the temps to:
- critical temp 88 (the same)
- control temp: 68
- full fan temp 78
Now the thermal trip did not occur during the last 10 reboots.
Maybe this can help others.
It looks to me like this needs to be done for both the memory temp and ambient temp settings.
-
There is an update coming which will bump the kernel version that may be helpful to you.
When will this update be available?
-
When will this update be available?
Hopefully Friday afternoon our time.
-
It's up.
This is mostly a OS kernel update.
It's also adds some low level support for future expansion.
-
Ultimately, the update went fine, but the first attempt to reboot after the update (from GUI) didn't switch to HDMI mode mid-way through boot, and at the end of audio init, came back with something like " can't start X-Server", then fell back to text mode, but running. I selected a reboot to GUI (#1) and everything went fine that time. Just FYI.
--Bill
-
Ultimately, the update went fine, but the first attempt to reboot after the update (from GUI) didn't switch to HDMI mode mid-way through boot, and at the end of audio init, came back with something like " can't start X-Server", then fell back to text mode, but running. I selected a reboot to GUI (#1) and everything went fine that time. Just FYI.
--Bill
Thanks for the feedback!
-
Upgraded while in text mode 3. Worked flawlessly.
Cheers!
-
Bob, see attached. A little over three days since last update, and on latest hardware. Was on a constant render loop, mixed speed FLAC's. Was also noticing occasional drops and buffer replays on higher bit-rate files (176k, 192k).
--Bill
-
I assume that killed the Id?
I don't think MC at the user level can do that, the apic interrupt suggests trouble with a hardware device to me.
What were you using for an output device at the time?
-
I assume that killed the Id?
I don't think MC at the user level can do that, the apic interrupt suggests trouble with a hardware device to me.
What were you using for an output device at the time?
That was with the Audioquest Dragonfly and GUI mode. It's the exact same test I was running constantly on the other Id hardware, which was the subject of three (at least) similar crashes. Just letting it run.
Anything you'd like me to try or change?
--Bill
-
Which USB port?
I'll try to duplicate it here...
Edit: Also, your DSP studio settings would be good.
-
Which USB port?
I'll try to duplicate it here...
Edit: Also, your DSP studio settings would be good.
Ok. The mouse/keyboard are plugged in to the rear USB jacks, and the Mosquito in the front.
When I tried to reboot from that crash, I got the thermal trip 'any key to continue' message. Rebooted into the bios to check my thermal settings. The current memory temp is 42, current MB temp 47. Temp. Thresholds for both, per your recommendations of 88,68,78. I believe that at the conclusion of a crash dump, the OS will be in a 100% CPU loop, if so, the box temperature might have been higher and then cooled down quickly once I started rebooting and looking at the bios.
DSP: Audio Device: front:CARD=DragonFly.DEV=0 [ALSA]
Device Settings: default
Output Format: reset to default, not what I had: < 44k=44k, 44k=44k, 48k=48k, 88k=88k, 96k=96k, 176k=176k, 192k=192k,352.8k=192k, 384k=192k, >384k=192. The files being played were 44k, 48k, 96k, 176k and 192k. The particular song that was playing at the time of the crash was 192k.
Volume Leveling: checked
All other boxes: unchecked
No Output Encoding, Channels: Source number (all stereo)
Can't remember if clip protection was on or off, but it was on after reboot. I usually run it off.
Bitstreaming: off
Play files from mem: off
Disable display from turning off: on
It still had the old render playlist on hand so I just started it up to resume testing. No actual server connection in place.
--Bill
-
Thanks Bill,
The playlist was originally pushed from one of your windows PC's I assume?
-
Yes, from 'Audio' through 'Bserve', my usual.
-
It's up.
This is mostly a OS kernel update.
It's also adds some low level support for future expansion.
Upgrade went okay. Had to reboot twice.
Id now recognizes Leema Elements Dac.
But my Elements DAC still only displays a 192kHz input when connected to USB audio (JRiver Id, running Linux).
I have tried changing the settings in DSP, but it made no difference.
It is fine with Windows 8 (compatibility mode), showing 44.1 kHz.
Have you come across any problems with Dac recognition and Linux?
I again point out that this problem only occurred after the previous update.
I have tried several USB cables, which made no difference.
-
Upgrade went okay. Had to reboot twice.
Id now recognizes Leema Elements Dac.
But my Elements DAC still only displays a 192kHz input when connected to USB audio (JRiver Id, running Linux).
I have tried changing the settings in DSP, but it made no difference.
It is fine with Windows 8 (compatibility mode), showing 44.1 kHz.
Have you come across any problems with Dac recognition and Linux?
I again point out that this problem only occurred after the previous update.
I have tried several USB cables, which made no difference.
We've got about a dozen USB DAC's here which are all recognized.
It's possible there is some odd interaction between the bios on the NUC and your DAC however as Hilton noted that could be tested by plugging it in just as the NUC is booting (when the information is scrolling on the screen before it gets to the menu).
Is there a reason why it shouldn't show 192k when nothing is playing? That is the top sample rate of the DAC from what I see at quick glance at the manual.
I'd then expect it to go the the sample rate of the material when it's playing.
To prevent sample rate changes, the DSP output format in MC should be off and the option under Audio->Advanced->Auto-config ... should be unchecked.
-
Hi Bob,
Since the last crash three days ago, I've seen one complete lockup two days ago (screen, keyboard, mouse frozen) cold restart required, and early AM today another crash. This was a real-time rendered from a server playlist, song #268 (starting from #1), 96k. I've attached a screen shot.
Took two reboots to come back up clean (first time, just quit responding after a few minutes). I've changed DSP processing to output 96k for all input speeds to see if that makes any difference with this Mosquito DAC. I have three other DAC's, the Grace Designs which is in use all the time, a M2TECH HiFace and a Mytek Stereo192-DSD DAC, but there doesn't appear to be working support for the latter two.
I could possibly reconfigure it as a server and let it push to another renderer for long period of time to see if it still crashes, or try a Null output device to bypass the Mosquito as a candidate. Any other suggestions?
--Bill
-
Hi Bob,
Since the last crash three days ago, I've seen one complete lockup two days ago (screen, keyboard, mouse frozen) cold restart required, and early AM today another crash. This was a real-time rendered from a server playlist, song #268 (starting from #1), 96k. I've attached a screen shot.
Took two reboots to come back up clean (first time, just quit responding after a few minutes). I've changed DSP processing to output 96k for all input speeds to see if that makes any difference with this Mosquito DAC. I have three other DAC's, the Grace Designs which is in use all the time, a M2TECH HiFace and a Mytek Stereo192-DSD DAC, but there doesn't appear to be working support for the latter two.
I could possibly reconfigure it as a server and let it push to another renderer for long period of time to see if it still crashes, or try a Null output device to bypass the Mosquito as a candidate. Any other suggestions?
--Bill
Hi Bill,
Mine ran for 2 days. I probably don't have as varied material as you.
I was pushing all FLAC and 44.1/16 48/24, 88.2/24, 96/24 and a single 192/24 in a repeat loop.
Also, I was using a dragonfly, I don't have a mosquito (is there a difference)?
The Mytek unfortunately requires some firmware files from windows and a hacked device drive to get it to work with USB2.
The HiFace is disabled by default in the kernel, I don't know why. I could turn it on though I suspect there is a reason it's off.
-
Hmm, I don't recall where I got Mosquito... Mine says DragonFly right on it.
This crash is the first I've seen associated with a lower-than 176k file, and I think you once mentioned that one of the crash shots I sent looked like it might be related to audio i/o. All freqs are now hard set to 96k in DSP so we'll see if that makes any difference.
Perhaps you could post your list of compatible DAC's at this point?
--Bill
-
We've got about a dozen USB DAC's here which are all recognized.
It's possible there is some odd interaction between the bios on the NUC and your DAC however as Hilton noted that could be tested by plugging it in just as the NUC is booting (when the information is scrolling on the screen before it gets to the menu).
Is there a reason why it shouldn't show 192k when nothing is playing? That is the top sample rate of the DAC from what I see at quick glance at the manual.
I'd then expect it to go the the sample rate of the material when it's playing.
To prevent sample rate changes, the DSP output format in MC should be off and the option under Audio->Advanced->Auto-config ... should be unchecked.
The guys at Leema suggest making adjustments to the linux config files. Could you tell me how to open a Terminal Window to run Sudo etc.
-
There is no terminal access to the Id. It isn't possible. Sorry.
Please share what adjustments you think are needed.
-
There is no terminal access to the Id. It isn't possible. Sorry.
Let's be honest about it. Terminal access is easily possible. It just isn't allowed. Unlike MC running in Windows (or Linux natively) as an open system, the Id with MC running in Linux is a completely closed system. A decision I can understand how some would believe to be a 'better' idea, but I'm not one of them. I suspect the issue of support is a big consideration, but also probably the idea of more user added processes running on the anemic hardware under which Id runs (the particular Intel NUC hardware model) would make the whole product potentially more unstable.
I realize the goal for the Id was to be a totally turnkey accessory for MC, but I for one would have rather paid a little more for an open implementation.
Don't get me wrong, I Love MC. It's an amazing product and quite turnkey up to a point (considering its complexity and capabilities. It mostly 'just works' and quite well at that). I'm just disappointed with Id's apparent design goals and limitations (not referring to the current software issues which I'm sure will be fixed).
--Bill
-
We may make a more open version in the future. Our goal right now is more focused.
-
We've got about a dozen USB DAC's here which are all recognized.
It's possible there is some odd interaction between the bios on the NUC and your DAC however as Hilton noted that could be tested by plugging it in just as the NUC is booting (when the information is scrolling on the screen before it gets to the menu).
Is there a reason why it shouldn't show 192k when nothing is playing? That is the top sample rate of the DAC from what I see at quick glance at the manual.
I'd then expect it to go the the sample rate of the material when it's playing.
To prevent sample rate changes, the DSP output format in MC should be off and the option under Audio->Advanced->Auto-config ... should be unchecked.
DSP output format was "on" and Audio etc was already unchecked.
I rebooted twice and it made no difference - Dac still displaying 192kHz no data..
A friend from the Queensland Audio Society brought some equipment over to do a comparison Friday afternoon.
We tried the same spec NUC, but it is running Windows JRiver 19.
The Linux version was audibly superior in my setup.
We then tried a Keces Dc-116 power supply.
With this connected instead of the supplied wall mart the DAC read the correct outputs (and sounded noticeably clearer).
The Dac still initially displays 192kHz no data, but then displays whatever sampling rate (44.1kHz or 96kHz for HiRes downloads) when the tracks are playing.
Which leads me to suspect that the wall mart is not supplying the correct power and/or this is interfering with the USB connection.
Leema (UK) had this to say about my sampling error problem
"Linux does not switch sample rate automatically like Windows. To change sample rate, you have to edit a protected config file. I normally set my Ubuntu pc to 176.4kHz, which is a good oversample rate for 44.1k material.
I use J River on PC, but have not tried the Linux version. The J River guys may have more up to date info on this. They are very responsive to questions."
As to future upgrades, I would like to see the ability to support an external USB storage device and also to enable theater view.
-
We've got about a dozen USB DAC's here which are all recognized.
It's possible there is some odd interaction between the bios on the NUC and your DAC however as Hilton noted that could be tested by plugging it in just as the NUC is booting (when the information is scrolling on the screen before it gets to the menu).
Is there a reason why it shouldn't show 192k when nothing is playing? That is the top sample rate of the DAC from what I see at quick glance at the manual.
I'd then expect it to go the the sample rate of the material when it's playing.
To prevent sample rate changes, the DSP output format in MC should be off and the option under Audio->Advanced->Auto-config ... should be unchecked.
Looks like I spoke too soon. This morning I get a sample rate display of 96kHz (which was the last files it was playing last night).
Unlike yesterday, it isn't going to the sample rate (44.1kHz) when the files are playing. I tried playing both 44.1kHz and 96kHz tracks, but no difference, the display shows 96kHz no data.
-
Normally a DAC will initially sync to its highest sample rate when being scanned at startup and then each track will reset the sample clock to what ever it needs to play the track. It will retain the last played sample rate until you give it a new track to reset the sample rate clock.
Your DAC is a UAC2 DAC so it may have some non-standard settings that make it flaky above 96k.
There are also some UAC2 DACs known to be problems in Linux so they are either excluded from the Kernel and don't work at all, or they need customised .asoundrc config files so they sync at the right sample rates. Sometimes this means loosing bit perfect playback in order to get a "nearest" sample rate that the DAC supports.
MC19 has settings that influence this too, so you need to use GUI mode to make sure that any sample rates that you know your DAC wont support, are set to multiples of, or the nearest supported sample rate.
With the Id, if you try playback something that MC19 cant sync a sample rate with the DAC, it will usually default to 48k for everything until you reset it again with the GUI in DSP settings.
I recommend carefully testing various sample rate tracks in GUI mode and checking your DSP settings after each track to ensure its not resetting the DSP to 48k. When you find a problem format or track, try manually resampling using the DSP, to the nearest supported sample rate, or if your an absolute purest, a supported multiple of the sample rate that's a problem.
-
I found another handy capability of running JRemote with the Id in the car, and I don't know why I didn't think of this sooner. :)
You can use Siri on the iPhone to do voice to text in the search dialogues in JRemote on the iPhone.
I found Im using this alot now in the car to find artists, albums or songs with just a couple of taps and swipes and asking siri to search and find it.
I'll record a demo video as its a pretty handy capability!
Cheers
Hilton
-
Is the Id *really* capable of handling 96k+ flac files in real time when rendering from DLNA? Or in all cases, even?
When I originate a DLNA stream from my server to Id it does a lot of what sound like buffer drops (a few seconds of audio) or sometimes short skips/drops. Every once in a while it will stutter, repeating a few seconds that it just played. This problem appears to be worse if Play from Memory is enabled. Almost like something is interrupting the audio in/out ring buffer pointers randomly. Most of the time I see it on FLAC files that are 176k or 192k, sometimes 96k, and seldom on 44k or 48k (but it does occasionally happen). It doesn't seem to happen in the same places on the songs, it's much more random than that.
I've changed the audio device output to DragonFly to a fixed 96k, but it makes little difference. Currently I'm trying it on HDMI audio with the DragonFly removed. So far nothing has changed.
Now, if I have the Id load my Server's library directly, and play from there, the same playlists, the symptoms lessen greatly, but still happen once in a while. Especially track re-starts after 20 or seconds of play. Also, premature jumps to a new song before the current song is done. And little burples in the audio, tiny skip here, tiny skip there... subtle but present.
My internal network is a switched GigE (1Gb), wired, and all devices are in the same /24 subnet. There is no packet loss at all. The same library server sending via DLNA to another MC on a regular computer works with no loss of any kind, and other machines attached to the server library or sharing files on the same filesystem (the same path designation on each computer) have no issues whatsoever. From the same server I can feed video or audio anywhere in the house with no issues at full bitrates (highest is BluRay at just shy of 50Mbit/sec).
So that takes it back to the Id as far as I can see.
Other lingering issues include:
System freezes (hardware lockup),
software freezes (hardware still responding) but only a reboot will start it working again.
If songs have stopped playing, the HDMI display still goes off even though the Disable Display from turning off option being checked. As long as tracks play the screen will stay on.
The first reboot after a crash will not run correctly most of the time. It's confused about the library it was on (asking for credentials for a library it has not connected to), or will start to play and then just disappear, or other nonsensical behavior. Next reboot it seems fine.
Opening Tools->Options->Audio->Audio Device->Device Settings while a song is playing will blow away MC completely, but it will restart by itself in about 20 seconds (watchdog restart?). Accessing Device Settings seems ok if nothing is playing.
I have not yet tried to duplicate any of this with a local library on the Id.
Could all these erratic behaviors have a common denominator? Such as a fault in this particular Intel NUC model motherboard? Either a design problem, or just not enough CPU to start with?
--Bill
-
Bill, I'm not having any trouble playing high bitrate flac files.
Are they being DSP'd on your configuration?
I added the ability to fix the output format in the latest update (just out).
Can you see if that helps with any of your issues?
The Dragonfly is S24_3LE
-
Id update released.
This is a MC update. The changes are listed at the top of this thread:
http://yabb.jriver.com/interact/index.php?topic=90535.0 (http://yabb.jriver.com/interact/index.php?topic=90535.0)
-
Bill, I'm not having any trouble playing high bitrate flac files.
Are they being DSP'd on your configuration?
I added the ability to fix the output format in the latest update (just out).
Can you see if that helps with any of your issues?
The Dragonfly is S24_3LE
Still doing the same stuttering, Bob. New download installed. However, I've narrowed the problem down to the Track Change section in Playback. What you select there has dramatic impact on stuttering. I had it on gapless (not sure why, as I normally don't use that) and in that mode it chops ending, stutters at beginnings and has little random burps throughout songs. I'm now set to Gapped Fade 1s, Do Not Play Silence and Use Gapless for Album Tracks are off. So far, on both using it on my remote server library directory, and separately as a DLNA renderer, it's doing pretty well. I've heard a couple of little gurgles but none of the gross stuff. I'll keep monitoring in DLNA mode as that was by far the worst.
It's important when you're listening for these kinds of issues, that it's not as background music. It's very easy to miss some of this behavior if you're not really listening, and to familiar material.
Other items of note, Disable Display From Turning Off still isn't working if music has stopped. In that case, once the screen goes off, you can't get it back without rebooting. Same thing occurs if you don't respond quickly after a reboot. It will eventually time out the screen forcing a reboot.
No, the files are native FLAC at varying speeds up to 192k, no DSD and nothing converted from DSD in this case.
Also, Input/ Output speed settings in DSP->Output Format->Sample Rate doesn't seem to stick across re-boots.
Also, also, a right click on the output field (that sets everything to the designated speed) seems to lock up, forcing a reboot. As soon as you rt-click, it's done. It does, however, keep playing a current song if one is playing. After that, nothing.
Hope this is helpful.
--Bill
-
Normally a DAC will initially sync to its highest sample rate when being scanned at startup and then each track will reset the sample clock to what ever it needs to play the track. It will retain the last played sample rate until you give it a new track to reset the sample rate clock.
Your DAC is a UAC2 DAC so it may have some non-standard settings that make it flaky above 96k.
There are also some UAC2 DACs known to be problems in Linux so they are either excluded from the Kernel and don't work at all, or they need customised .asoundrc config files so they sync at the right sample rates. Sometimes this means loosing bit perfect playback in order to get a "nearest" sample rate that the DAC supports.
MC19 has settings that influence this too, so you need to use GUI mode to make sure that any sample rates that you know your DAC wont support, are set to multiples of, or the nearest supported sample rate.
With the Id, if you try playback something that MC19 cant sync a sample rate with the DAC, it will usually default to 48k for everything until you reset it again with the GUI in DSP settings.
I recommend carefully testing various sample rate tracks in GUI mode and checking your DSP settings after each track to ensure its not resetting the DSP to 48k. When you find a problem format or track, try manually resampling using the DSP, to the nearest supported sample rate, or if your an absolute purest, a supported multiple of the sample rate that's a problem.
According to Leema, " Our DACs only support high-speed USB2.0. They have now 1.1 compatibility mode as they are high speed only. This works fine with our Windows driver and with MAC, but Linux is not great with high rate high-speed USB.
I have only ever managed to get 96kHz, but that will work reliably as long as you edit the config file. The start-up default will always be what you set in that file.
The DAC will not start at the highest rate available. It has a conversation with the OS to find out what rate the OS is set to at switches to that rate.
You can prove this with Windows. Whatever rate you set will appear on the DAC when you hot plug the USB cable.
I should also say that all Linux builds are different and support audio in a range of different ways and sample rates. Different flavours of Linux will behave differently depending on what options have been included in their build and as such, we don't support Linux specifically. "
So the question remains, how do i edit the config file?
-
According to Leema, " Our DACs only support high-speed USB2.0. They have now 1.1 compatibility mode as they are high speed only. This works fine with our Windows driver and with MAC, but Linux is not great with high rate high-speed USB.
I have only ever managed to get 96kHz, but that will work reliably as long as you edit the config file. The start-up default will always be what you set in that file.
The DAC will not start at the highest rate available. It has a conversation with the OS to find out what rate the OS is set to at switches to that rate.
You can prove this with Windows. Whatever rate you set will appear on the DAC when you hot plug the USB cable.
I should also say that all Linux builds are different and support audio in a range of different ways and sample rates. Different flavours of Linux will behave differently depending on what options have been included in their build and as such, we don't support Linux specifically. "
So the question remains, how do i edit the config file?
If the file is specific to that particular device you can send it to me and I'll add it to the next update.
-
I have an odd thing happen, I have been using the Id with my server PC all on MC 19, all wired to the router and running it so as to push the data to the Id. so I would use Gismo to set the source as the server and play to the Id. this all seemed fine, played all sample rates to 352.8 and DSD 128, outside of boot up issues with Id all worked great, until I took the laptop PC I use as a server to the Capital Audio Fest and tried to get it working there for our show demo with gismo to control it and my wi fi router. well that did not work as found out I needed to be on the internet and ended up using the hotel wi fi to run MC and gismo for the show. Got back here and now in the same configuration it will not play DSD ( DoP ) and seems to just convert to 176 pcm. I have made no changes at all and everything is set to not convert or best I can tell. I can get it working by playing from the Id so as to pull data off the sever instead of pushing to the Id so when set that way it all works again. any ideas?
-
I have an odd thing happen, I have been using the Id with my server PC all on MC 19, all wired to the router and running it so as to push the data to the Id. so I would use Gismo to set the source as the server and play to the Id. this all seemed fine, played all sample rates to 352.8 and DSD 128, outside of boot up issues with Id all worked great, until I took the laptop PC I use as a server to the Capital Audio Fest and tried to get it working there for our show demo with gismo to control it and my wi fi router. well that did not work as found out I needed to be on the internet and ended up using the hotel wi fi to run MC and gismo for the show. Got back here and now in the same configuration it will not play DSD ( DoP ) and seems to just convert to 176 pcm. I have made no changes at all and everything is set to not convert or best I can tell. I can get it working by playing from the Id so as to pull data off the sever instead of pushing to the Id so when set that way it all works again. any ideas?
The configuration for what file format to push is on the MC PC doing the pushing under the DLNA server configuration.
You can specify a particular DLNA server configuration to use by right-clicking on the ID zone under playing now and choosing the "Associate with DLNA server" option.
The ID shouldn't care about being connected to the internet. It does however need to be able to get an IP address (usually via DHCP).
-
the situation in DC did not have the Id in the setup, just my laptop and phone, just when I got it back here and setup again I some how changed things. well now I found it, and know how it got changed, thanks and its working both ways push and pull. plays dsd correctly. only problems I have with the Id is boot up and the only way it will start up is to have it set to GUI mode and have a monitor connected just incase it asks me that it has x days left on the license key. I just did an upgrade and I have not seen it come back so I might be able to go to headless mode which I want to do and never worked. but I will try that later.
I have found a problem since upgrading the Id Friday, with DSD tracks it might get to the very end then loop the last few seconds of the track and not continue on with the play list, or with 44.1 PCM make sort of a distorted fade out. never had this before. some settings get changed I should check on?
-
the situation in DC did not have the Id in the setup, just my laptop and phone, just when I got it back here and setup again I some how changed things. well now I found it, and know how it got changed, thanks and its working both ways push and pull. plays dsd correctly. only problems I have with the Id is boot up and the only way it will start up is to have it set to GUI mode and have a monitor connected just incase it asks me that it has x days left on the license key. I just did an upgrade and I have not seen it come back so I might be able to go to headless mode which I want to do and never worked. but I will try that later.
I have found a problem since upgrading the Id Friday, with DSD tracks it might get to the very end then loop the last few seconds of the track and not continue on with the play list, or with 44.1 PCM make sort of a distorted fade out. never had this before. some settings get changed I should check on?
I think that issue might have gotten fixed recently. I'm trying to get out another update asap..
-
today I can not get it working at all, no license key it timed out and now no boot up. I just tried checking for updates. I can not use my key from 19 that I have as there is no way to enter a key so that will not work.
I just did a request for extension and got a new key emailed so its back up again. will this go away?
-
today I can not get it working at all, no license key it timed out and now no boot up. I just tried checking for updates. I can not use my key from 19 that I have as there is no way to enter a key so that will not work.
I just did a request for extension and got a new key emailed so its back up again. will this go away?
The key is stored in the backup configuration.
You can do a 77 to get that back.
I don't know why you are losing your configuration.
There will be an update before 6:30 CDT.
PM me your serial number and I'll email you the key.
-
The update to 19.0.160 is out.
Amongst other things it fixes the cutting of the end of some tracks.
-
I have never used JRiver Media Center before and I have just started my new JRiver Id but I have no idea how to configure it. It's sais that I can use the text menu to configure audio output but I can't find anything there to configure, The only place I can find any audio devices are in the GUI.
I can't find where I point to my DLNA/UPnP server that is a MinimServer. It's not possible to configure/change audio output via a web browser, nothing happens. I have been using Squeezebox server for many years and am used to remote configure everything via a web browser, isn't it possible to do the configuration via a web browser?
It's the first time I am using DLNA/UPnP so maybe I am doing this the wrong way.
-
Are there plans to support convolution on the Id?
Right now, the Browse command to select a convolution file is non-op, and externally via Samba the only hierarchy available for transfers starts at the 'media' directory level.
.160 seems to be doing ok so far. A couple of days ago the previous version locked up, no response to any keyboard or mouse clicks, but the mouse itself was working and could switch windows. When I exited that mode to restart it displayed a segmentation fault had occurred. Besides that one event it had been stable for over a week.
--Bill
-
Just received my Id. I have it running pretty well as a renderer. It plays everything my MC19 server sends to it including 192K PCM files. Rather nice. What doesn't play ? ..... some radio stations.
e.g. RadioParadise AAC 128K wont play at all. This is odd because MC19 on Windows plays that radio URL and all the others that I have perfectly.
I have a 10 or so radio stations in a playlist and maybe half of them will play on the Id.
I'd love to fix the radio problem
Dave
-
Can somebody tell me the secret to getting the Id to function 'standalone' .. no monitor, no keyboard, HDMI audio output.
My Id will happily work in mode 1) GUI or 3) text with HDMI init ..but only with a monitor and keyboard attached.
Mode 2 hasnt yet worked for at all
I'm probably doing something wrong
-
Can somebody tell me the secret to getting the Id to function 'standalone' .. no monitor, no keyboard, HDMI audio output.
My Id will happily work in mode 1) GUI or 3) text with HDMI init ..but only with a monitor and keyboard attached.
Mode 2 hasnt yet worked for at all
I'm probably doing something wrong
There is a bit of a catch 22 here related to how linux handles hdmi.
To run headless we need to not initialize the HDMI but some audio equipment seems to require hdmi initialization.
-
Oh dear
-
There are some HDMI devices that might help. I haven't tried any, but take a look at what people say about HDMI Buddy and similar. The forums at AVSforum might be a good place to look.
My Id is connected to a receiver that is connect to a TV, both by HDMI. I can use it without problems with both turned off (playing to Gizmo on an Android) or with just the receiver on (playing through its speakers). When the TV is turned on, it also works until the TV sleeps, then the playback to the receiver pauses unless I turn the TV off. Go figure. I've learned how to work around it.
I've bought, but haven't tested, the Kinivo 5011BN HDMI Switch (http://www.amazon.com/Kinivo-501BN-Premium-wireless-adapter/dp/B0049SCB2Y/&tag=wwwjrmediacen-20) which I've read about. I'll try to test it soon and report back.
-
OK, but what is HDMI Buddy ?
-
Thanks Jim .. I'll take a look at the Kinivo. Presumably you're thinking that it might do the HDMI initialization that Bob was referring to.
I have a setup similar to yours ... the Id connected to a receiver (Yamaha Rx471) which is connected to a 1080p TV. Mode 1 (GUI) and 3 (Text with HDMI) work fine provided the TV is on. In these modes, if the TV is off, the Id will seg fault during boot (that's probably fixable). I can see the seg fault by switching the TV on.
In mode 2, with the TV on or off, the Id just doesn't initialize properly .. it appears that even the network isn't up (just a guess) .. Ethernet lights are on but not flashing.
As a datapoint, I have other renderers (WDTV for example) that are Linux-based and will happily output HDMI audio without a TV.
-
Just to be clear .. as an audio DLNA renderer, the WDTV is a child compared with MC and the Id. It has only one trick that the Id can't yet do .. run headless HDMI audio to my receiver.
-
I may split the radio discussion to a new thread.
Does the station offer an MP3 version?
-
Can somebody tell me the secret to getting the Id to function 'standalone' .. no monitor, no keyboard, HDMI audio output.
My Id will happily work in mode 1) GUI or 3) text with HDMI init ..but only with a monitor and keyboard attached.
Mode 2 hasnt yet worked for at all
I'm probably doing something wrong
I double checked this on the stock unit here and it worked.
What do you get when you boot in mode 2 with a monitor attached? Where does the boot process stop??
-
Sorry, but my earlier post about mode 2 not initializing the network properly was the result of a mis-observation.
Here's what I see for all the modes..
Modes 1 and 3: Monitor on .... OK
Modes 1 and 3: Monitor off ... seg fault during boot, no network
Mode 2: Monitor on or off ... boot completes and network comes up and (if monitor is turned on) menu displays
The receiver reports that its HDMI input port is in "DVI" mode, which seems understandable given the purpose of Mode 2.
(conversely, in Modes 1 and 3, the receiver reports that its HDMI input port is in "HDMI" mode)
So, in Mode 2 the Id is up and alive, responds to menu requests, and network pings, there's just no audio coming from the receiver.
If there's some diagnostics that I can collect, then do let me know.
Dave
P.S.
the seg fault during boot for the no-monitor Mode 1 and 3 case seems odd because there is indeed an HDMI device attached (the receiver).
-
There are some HDMI devices that might help. I haven't tried any, but take a look at what people say about HDMI Buddy and similar. The forums at AVSforum might be a good place to look.
My Id is connected to a receiver that is connect to a TV, both by HDMI. I can use it without problems with both turned off (playing to Gizmo on an Android) or with just the receiver on (playing through its speakers). When the TV is turned on, it also works until the TV sleeps, then the playback to the receiver pauses unless I turn the TV off. Go figure. I've learned how to work around it.
I've bought, but haven't tested, the Kinivo 5011BN HDMI Switch (http://www.amazon.com/Kinivo-501BN-Premium-wireless-adapter/dp/B0049SCB2Y/&tag=wwwjrmediacen-20) which I've read about. I'll try to test it soon and report back.
I just started testing and posting results here:
http://yabb.jriver.com/interact/index.php?topic=91115.0
-
Radio on the Id split (http://yabb.jriver.com/interact/index.php?topic=91116.0)
-
OK, but what is HDMI Buddy ?
I was wrong. It's the HDMI Detective (http://www.amazon.com/Gefen-EXT-HDMI-EDIDP-HDmi-Detective-Plus/dp/B001RIMZUW/&tag=wwwjrmediacen-20) from Gefen. It's $129. But I'm testing a Kinivo that is $59 and it seems to solve my problem. It may not solve yours.
http://yabb.jriver.com/interact/index.php?topic=91115.0
-
Can I use this instead of my laptop? I currently run JRiver on an Asus laptop with all my flac files on the computer. The laptop is our family computer and has to be disconnected from my stereo if we need to use the computer.
I control the music via my iPad using JRemote. I have a Peachtree Audio 220SE integrated amp with USB dac.
The Id has about 100gb of storage so if my library is about 150 gb can I connect a NAS or some other storage to the id?
Also, will I be able to send music via music apps (Songza, Spotify, etc) on my tablet to the id wirelessly or connect it somehow. Or connect the id to a monitor via the hd I and use the web based versions?
Thanks in advance,
Mark
-
Can I use this instead of my laptop?
Yes. The laptop could still serve files, and you could use a phone or tablet to play from it to the Id, assuming they are both on the same network.
I currently run JRiver on an Asus laptop with all my flac files on the computer. The laptop is our family computer and has to be disconnected from my stereo if we need to use the computer.
I control the music via my iPad using JRemote. I have a Peachtree Audio 220SE integrated amp with USB dac.
The Id has about 100gb of storage so if my library is about 150 gb can I connect a NAS or some other storage to the id?
Not directly, but if the laptop has imported the files, you can play them. We may offer a larger drive in the future, and you can also play directly from the Id.
Also, will I be able to send music via music apps (Songza, Spotify, etc) on my tablet to the id wirelessly or connect it somehow.
Not at this time.
Or connect the id to a monitor via the hd I and use the web based versions?
You can connect the Id via HDMI, but it won't play web audio.
You can get a limited version of this by adding individual stations to separate playlists on the laptop, then playing the playlist on the Id. Please start a new thread if you need help on that.
-
Video should be coming by the end of the year:
http://yabb.jriver.com/interact/index.php?topic=91188.0
-
Please use the new Questions thread (http://yabb.jriver.com/interact/index.php?topic=91344.0) now.