Jump to content

igolem

  • Posts

    16
  • Joined

  • Last visited

  • Country

    country-ZZ

Retained

  • Member Title
    Newbie
  1. No worries. They are shipping to Canada, I didn't see any place to specify shipping methods.
  2. Done. I ordered another rendu in your sale today too.
  3. Thanks. Is there a URL you can provide me? Is t there an image i can download or will you ship me a physical card? Much appreciated
  4. Hi Forehaven, Thank you for your reply. Yes I've tried multiple times both on my existing network and the temporary network I created for trouble shooting.
  5. Hi All, I think this is the right place to come for Sonore Microrendu support, if not forgive my post and point me in the right direction if you know it. My system was working great, Roon Rock -> Microrendu -> Schiit Yggy, last night when I fired up Roon I saw there was an update. I chose to update all (as I typically do) but didn't check the details this time, so I'm not sure what got updated. After the upgrade I could not see any audio devices in Roon, specifically, the Microrendu wasn't seen by Roon. Further, I could not hit the management URL for the Microrendu nor could I ping it at it's last known IP address. Everything else on my network is working fine. As an experiment, I created a small closed network to see if the Microrendu could boot and get connected to it. Ethernet lights are flashing but my DHCP server is not seeing a request and hence the rendu never becomes visible on the network. At this point, I'm not sure where to go next in terms of troubleshooting. Any help or insights would be greatly appreciated.
  6. @agillis, can you tell me some more about the modifications you've made to MPD? HAve you contributed those changes back to the project?
  7. If the OSS guys would return email / phone calls it would be a good start. Mind it's only been a day I dd contact Lynx today and they do offer and SDK so I think I may take this project on myself. In the meantime I will continue to lobby OSS (it seems likely they could get there the fastest) and if you can help lobby as well, please do so!
  8. Very stable so far, nice work guys. Still no joy on getting my Lynx AES16e recognized, which is unfortunate, and a show stopper for me. Hats off to those who say they have it working, any help would be greatly appreciated. agillis - have you looked at susstudio.org perchance? It may be an interesting way to package and distribute vortexvbox.
  9. Thanks Jesus, I would have avoided OSS like the plague at any rate but it's good to know the card is not supported. (Lynx AES16e - PCI express to be completely clear). 4front list it as a supported card -- until you read the release notes -- nice. So I'm at a bit of a loss then. What kernel module are you loading to get ALSA and Pulse working for the Lynx AES16e?
  10. Chris, OSS huh? Thanks for the head's up that's quite helpful. Too bad though, OSS is effectively dead to me. ALSA is every bit as capable and I don't quite cotton to the OSS business model (personal pref but with a long history behind it). Clearly, I'd love to see Lynx AES16 as a supported card under ALSA. Jesus, to answer your earlier question - The other machines are macs
  11. Took your advice Jesus, and took it for a test drive. It installed quite seamlessly and only took a minor but of fiddling to get the onboard sound card working. (there are 2 in the box -- an nvidia on the MB and a Lynx AES16e). It did not recognize the Lynx card and I've had no joy thus far in getting it working. All tips and hints welcome here. Ideally I'd like to have both cards running. The ripping aspect worked very well, and I think from that perspective alone there will be some voretex in my future, even if it is as a dedicated ripping station connected to a NAS.
  12. and it seems like the Vortexbox player is coming along. I may install that for giggles if I can free up some hardware. Might be interesting to try running Vortexbox itself as a VM. Jesus R, I noticed in your sig that you seem to have a Lynx AES16 running under Linux. I was unaware that there was a Linux driver and didn't think it was a supported card under ALSA. Any tips to get it running?
  13. So niceness is the Linux/Unix concept of how much time the kernel dedicates to tasks in a multiuser/multitasking environment. Some tasks by their very nature run at a higher priority than others. Typically to have a smooth end user experience those apps run at a higher priority than say routine maintenance tasks. File conversion/encoding tasks can typically run at a lower priority than say a web browser. Every process that runs on a system has a niceness value associated with it. In essence reflecting how "nice" that process is playing with others, in terms of CPU resource demands. The higher the value the nicer the process is, the fewer resources it consumes. nice and renice are the commands that are used to set this value for a process. nice sets it when the process is first started, renice changes it for processes already running. The values range from -20 (highest priority, least nice) to +20 (lowest priority, most nice) with 0 being typical default. You can do this by hand in a terminal window: First get the process ID for coreaudio: ps -axl | grep -i coreaudio | grep -v grep 0 209 1 4000 0 97 0 86688 7264 - S < s 5a93060 ?? 116:03.67 /usr/sbin/coreaudiod Don't worry about all the crap on the line, just a few parts are relevant (btw you will see different values) The 2nd value '209' is the process ID (you will have a different value -- make note of it). The current niceness value is shown by the '0' following the 97. We will change that value with the following command: (note you will need administrator password for the following) sudo renice -5 209 This command tells the kernel to set the niceness value of process 209 (coreaudio) to -5 (more greedy) Executing the first command again shows the result: ps -axl | grep -i coreaudio | grep -v grep 0 209 1 4000 0 97 -5 86688 7264 - S< s 5a93060 ?? 116:03.67 /usr/sbin/coreaudiod If that doesn't solve the problem you could try the 2nd command again using -10 or-15 until the dropouts go away Sorry for all the command line stuff, I'm sure someone has written a nice GUI to do this. i just don't know of one and I'm kind of old school that way HTH
  14. I hope your right on the iTunes pass through and responding to better sample rates. There's no reason I can think of that this shouldn't be easily doable. There's no reason in software architecture to tightly couple these things. In standard SW architecture terms. iTunes should only be the view. CoreAudio the controller. Allowing the end user to swap either of these pieces at their whim I'm very satisfied with the sound quality. I've not compared it to an XP based system but knowing how difficult it is in general to separate XP from drivers from applications, I think I'd happily trade off a small quality drop for improved stability. I don't want to be in the position of saying, "this would sound great if I could get it to stay up for any length of time" iTunes certainly is a joy to work with, it's a killer app and now that it can be remote controlled from the iPhone or iTouch, it's just endeared itself to me that much more. Out of curiosity, are you running your BADA directly to you poweramp, or running through a pre? Have you tried 'renicing' the coreaudio process to tell the kernel to give more CPU to that process and it's threads? I've not had the same issue you're experiencing but this should help. I'm traveling at the moment, but when I get home I'll try the reverse (lowering CoreAudio's priority to see if I can induce this behavior).
  15. PGA, Excellent advice, your checklist exactly matched mine. Bit perfect as it were, except for one part: Restarting iTunes, and I know better than that . Everything is working great now. Thanks for the help!
×
×
  • Create New...