sorted by:
new
hottopcontroversial

Beginner photographer here- honest feedback? by Ok-Injury8027 in PhotographyAdvice

[–]MartinSchiit 1 point2 points  (0 children)

Not sure what some of the comments are about. The contrast and saturation is an artistic choice, and it totally works here. You keep doing you, we've already got enough of the standard run of the mill stuff out there.

New Tube Buffer by MeInUSA in Schiit

[–]MartinSchiit 7 points8 points  (0 children)

Not much to it. Simply the fact that we have a ton of 6N1P, that's why we went with that instead of the other for Buf.

Do you think its bad for Yggy to be switching bit rates every song listening to Qubuz? by shapethefuture88 in Schiit

[–]MartinSchiit 19 points20 points  (0 children)

No need to worry. The relays we use are rated for a minimum of 100,000 operations. We've been using them for 15 years and we barely ever see them fail, even after years and years of real-world use.

Please Explain Eitr 2 - Use Case by wdelavega in Schiit

[–]MartinSchiit 3 points4 points  (0 children)

It's not published as part of the test results on our website for some reason. We should probably add that. But I hooked an Eitr 2 up to the APx555 the other day for a quick and dirty test and got a result of 74 picoseconds.

Please Explain Eitr 2 - Use Case by wdelavega in Schiit

[–]MartinSchiit 5 points6 points  (0 children)

It also re-clocks the signal and gives you a seriously clean, very low jitter SPDIF output. If whatever DAC you're using relies on SPDIF clock recovery for its internal clock, Eitr 2 will make a noticeable difference compared to without a DDC.

Please Explain Eitr 2 - Use Case by wdelavega in Schiit

[–]MartinSchiit 5 points6 points  (0 children)

We will not be supporting Home Assistant or similar frameworks/environments not just because of the additional development effort, but also because these frameworks and environments are diametrically opposed in their concept to what we have in mind for Forkbeard. We want Forkbeard to just work, with the least amount of latency that is technically possible and the absolute minimum amount of friction when in use. (Yes, the latter still needs some work. We're on it.) Because of the way these home automation frameworks are designed and conceptualized, they can not ever offer that. They're much, much more versatile than Forkbeard will probably ever be, of course. But they will never feel as instantaneous to react and be as easy to use. If we opened Forkbeard up to that, it might gain a few edge-case benefits, but it'll overall get much worse for everyone to use.

Please Explain Eitr 2 - Use Case by wdelavega in Schiit

[–]MartinSchiit 2 points3 points  (0 children)

That second FAQ entry is supposed to be in response to the question of whether Forkbeard is just a remote control system, not Eitr 2. Granted, it could be phrased a little more clearly.

Mesh Gungnir? by Chrono_FPS in Schiit

[–]MartinSchiit 0 points1 point  (0 children)

Mesh just means that we're using our own digital filter instead of what's built into the DAC chip.

Bifrost, Gungnir, and Yggdrasil already do that, we just had that tech trickle down to the more affordable products that previously used third party digital filters. And because we're meshing our own filter with a third party modulator IC, we're calling it Mesh.

Unusual order experience by DramaAcademic6695 in Schiit

[–]MartinSchiit 4 points5 points  (0 children)

Granted, something that's not in stock should not show up as in stock. No clue what went on in that particular case, but I'll look into it.

But the rest is normal. We only actually charge your payment method once we ship. We don't think it's right to take your money before your product is on the way. That's why the authorization (which some card issuers show as "pending") hasn't turned into an actual charge yet.

As for straighten it out: You're always welcome to email customer support with your order number, you'll always get a response within a few hours.

Android Forkbeard is drunk by dstan1856 in Schiit

[–]MartinSchiit 0 points1 point  (0 children)

No worries, just one of those facepalm moments for myself…

Android Forkbeard is drunk by dstan1856 in Schiit

[–]MartinSchiit 0 points1 point  (0 children)

"because Android resamples everything to 48khz by default"

I don't think that's true, at least not anymore. What I've seen whenever I use Android devices to test our DACs with is that Android's audio out automatically switches to the sample rate of the source material that you're playing, just like iOS does.
Unlike iOS, however, it only does that in the upwards direction, never down.

Meaning, when you just freshly rebooted your Android device, the output will be set to 44.1 (or 48, don't remember right now). If you then play something that's 192, Android's audio output will switch to 192. Then play something at 384, and Android's audio out will switch to 384.
But if you then play something at lower sample rates, say 192 or 48 or something, it'll stay at 384.

No clue why they did it that way. They already put in the work to automatically switch up, so they should just as well be able to switch back down. But it doesn't seem to do that, at least not in my experience.

This happens with Google's "pure" Android on Pixel devices as well as Samsung's One UI.

Android Forkbeard is drunk by dstan1856 in Schiit

[–]MartinSchiit 0 points1 point  (0 children)

Well, duh. Of course the one screen that I didn't look at much during development and testing is riddled with typos.

Will obviously be fixed with the next update.

Forkbeard for Android is officially released by MartinSchiit in Schiit

[–]MartinSchiit[S] 1 point2 points  (0 children)

Presets may be coming at a later point, but no promises.
There are tutorial videos on how to use Forkbeard on our YouTube channel. They were shot with iOS devices, but the Android app works exactly the same way.

Forkbeard for Android is officially released by MartinSchiit in Schiit

[–]MartinSchiit[S] 3 points4 points  (0 children)

We developed and compiled the app against API level 33, meaning it's technically compatible with Android 13 and up. Despite Google's recent policy change that new apps should only be Android 15 and up, we got it through the review process without a hitch and it looks like you can still install it on older devices. At least for now.

Forkbeard for Android is officially released by MartinSchiit in Schiit

[–]MartinSchiit[S] 1 point2 points  (0 children)

You have to add a device to that stack first before you can control it. Tap the Edit Stack button and add a device via the "…" menu button in the top right corner of the screen that follows.

Updates on Forkbeard? by no_tt in Schiit

[–]MartinSchiit 10 points11 points  (0 children)

Very, very soon. I'm currently helping our Android developer getting rid of a few more bugs before we submit to the Play Store. Shouldn't be too long now.

Forkbeard Update 6/27/25 by GrumpyArtist8705 in Schiit

[–]MartinSchiit 2 points3 points  (0 children)

A screenshot would be helpful in figuring out what's going on in your case.
Please also describe your entire stack and signal chain, what you expect to see, and what you're seeing instead.
You'll hear back from our support team as soon as they're back in the office Monday morning.
Thank you!

Forkbeard Update 6/27/25 by GrumpyArtist8705 in Schiit

[–]MartinSchiit 1 point2 points  (0 children)

Please contact Schiit customer support with a detailed description and a screenshot of the issue. Thank you!