greenkiwi
1000+ Head-Fier
No if only we could get some info on the headphone amp
I had not been given any purview to post as a LH employee, so I did not disclose it. The opinions are my own, as a LH backer, and should be viewed as such.
Until last night I had done a good job of not commenting on “hot button” topics, however that one elicited the response it did.
I no longer own his case, so I do not know where it stands. However, he should have emailed into the case asking for an update if he had concerns, and waited for a new replacement unit before posting a “first impressions” video.
Tickets do not auto close. I do not know if they did before I started, but I know they do not now.
I was not around for the issues with the Geek Out, and his issue is not firmware related, which makes the GO reference irrelevant.
To move on, I think $22 for the chip upgrade is quite a safe investment. If there's noticeably better measurables, whether or not perceivable, I think we can trust LHL to implement it perfectly. I'm no expert on technical stuff, but I've experienced the infamous Sabre glare in a couple of DACs before. The GO was the best of the lot. Treble never became harsh. I think it's safe to say Larry knows what's best for all things hardware. Most of the upgrades I'll think twice with regards to value, but $22 makes for an easy decision
Try LHLabs' geek force forum. I recall there was a thread on it.
I had not been given any purview to post as a LH employee, so I did not disclose it. The opinions are my own, as a LH backer, and should be viewed as such.
Until last night I had done a good job of not commenting on “hot button” topics, however that one elicited the response it did.
I no longer own his case, so I do not know where it stands. However, he should have emailed into the case asking for an update if he had concerns, and waited for a new replacement unit before posting a “first impressions” video.
Tickets do not auto close. I do not know if they did before I started, but I know they do not now.
I was not around for the issues with the Geek Out, and his issue is not firmware related, which makes the GO reference irrelevant.
Your opinions are indeed your own and not indicative of LHlabs views on the matter, but why do you insist your views be viewed as that of a LH backer? (rather than that of a LH employee, which you apparently are).
Is there some apparent disadvantage for you to have your opinions to be viewed as coming from an LH employee?
I've been experimenting with the Pulse, changing tracks (from DSD to WAV to DSD again), no issue at all. One thing though, LHL should beef up their FAQ section with help on how to get Foobar (or any other player) configured to play DSD tracks and such. To draw from an experience I'd had with iFi, I have the Micro iDSD, I couldn't get Foobar to play nice with the Micro iDSD, I'd posted my frustrations with setting it up, their local rep answered within a day with a step-by-step guide to configuring Foobar......now, that's excellent service. Yes, I do understand that LHL doesn't have local reps in the various countries, so having a clear guide to using the Pulse in the FAQ/Guide section would help. I'd gotten Foobar to play nice with the Pulse after some anxious minutes configuring Foobar while, at the back of my mind, wondering if the unit was defective. A good online guide would definitely alleviate some of the initial anxiety with any new product, especially one that has been plagued with such bad press.
Yeah actually that would be nice. It took me quite some time to figure out how to set up DSD properly on Foobar for the Geek Out.
Basically:
- Install the LH Windows drivers (http://lhlabs.com/downloads/LightHarmonic_DriverSetup_v2.23.zip)
- Install Foobar2000 (http://www.foobar2000.org/download)
- Install the ASIO add-on for Foobar (http://www.foobar2000.org/components/view/foo_out_asio just double-click on the .component file and it'll open in Foobar)
- Install the SACD Decoder add-on for Foobar (http://sourceforge.net/projects/sacddecoder/files/foo_input_sacd/ just unzip the folder, double-click on the .component file, and it'll open in Foobar)
- Open Foobar
- Go to Foobar preferences (Ctrl + P)
- Click on the Output listing after expanding the Playback settings on the left
- Select ASIO: foo_dsd_asio in the Device list
- Adjust the Buffer length slider to your liking (I don't know if these settings do anything so I just set it to 50 ms)
- Click on the ASIO listing after expanding the Output settings on the left
- Check the Use 64-bit ASIO drivers option
- Check the Run with high process priority option
- Double-click on foo_dsd_asio under the ASIO Drivers list
- Select Light Harmonic ASIO under the ASIO Driver dropdown list
- Select DoP Marker 0x05/0xFA under the DSD Playback Method dropdown list
- Select None under the DSD to DSD Method dropdown list
- Select None under the PCM to DSD Method dropdown list
- Select 0 ms under the DSD/PCM Transition dropdown list
- Close that window
- Click on the SACD listing after expanding the Tools settings on the left
- Select DSD under the ASIO Driver Mode dropdown list
- Click on Apply and OK
- Open the Light Harmonic Control Panel
- Go to the Buffer Settings tab
- Adjust the USB Streaming Mode and Asio Buffer Size options to your liking (I still don't understand what these options do, but I have Minimum Latency and 128 samples respectively)
- Go to the Volume tab
- Click on Output ...
- Adjust the volume to your liking (I would recommend setting the master volume to -70 dB just to be safe)
- Open a DSD file in Foobar and play it
Hopefully this will help someone else. It only took me a long time to figure it all out.... -_-
You skipped the part about getting an unmaimed goat, slaughtering it and sacrificing it to the gods of audio...![]()
I think we should give Jody a break as well. It's clear he will have a greater propensity to be aggrieved than most since it's his own blood and sweat being put into the CS front. I can empathize because he's simply taking pride in what he does, and his job isn't exactly easy. Keep in mind that he proactively seeked a solution to his woes (and for others as well), and at heart he's essentially a backer like all of us.
To move on, I think $22 for the chip upgrade is quite a safe investment. If there's noticeably better measurables, whether or not perceivable, I think we can trust LHL to implement it perfectly. I'm no expert on technical stuff, but I've experienced the infamous Sabre glare in a couple of DACs before. The GO was the best of the lot. Treble never became harsh. I think it's safe to say Larry knows what's best for all things hardware. Most of the upgrades I'll think twice with regards to value, but $22 makes for an easy decision
I can't recall what I'd done, only that I'd changed this or that setting when Foobar prompted an error message about 'unable to query frequency rate' or some malarkey to that effect. Furiously reset this and that and was rewarded with Foobar playing the track......but no sound! After a few more adjustment, I'd gotten it to work........WHEW!:blink: All that just to get the Pulse to play nice with Foobar, and all that time I was wondering if my unit was faulty since Foobar was playing the tracks, but no audio. Seriously, LHL should post a config setting for Foobar and any other major player so that we can feel at ease configuring Foobar and Pulse. I'm keeping your post in mind as I'll be getting a Nano iDSD to go with my Lyr, I'm gonna compare the Lyr + Nano iDSD stack against the Pulse Standard and the winner (in my opinion based on my somewhat shoddy hearing) would be my main audio rig with the 2nd place audio setup going to my 2nd rig.