Chord Mojo(1) DAC-amp ☆★►FAQ in 3rd post!◄★☆

[SomeGuyDude]

BTW, does anyone get periodic clicks with Mojo.
When mine is plugged into Windows laptop i get ever so slight ticks every now and then. Actually annoying.

Does it sound like a very small static shot, and only in one ear?

 

[Mython]

Who's stopping by the Chord Electronics stand at CanJam London?

I can't speak for Chord, but I wouldn't be at all surprised if there'll be a Mojo-Poly or two, to audition.

 

[SomeGuyDude]

Who's stopping by the Chord Electronics stand at CanJam London?

I can't speak for Chord, but I wouldn't be at all surprised if there'll be a Mojo-Poly or two, to audition.

A what now?

 

[LIVE_EVIL]

Does it sound like a very small static shot, and only in one ear?

No, in both ears and it is of very short duration.

 

[GreenBow]

Do you have the proper ASIO driver for Mojo?

If yes, you can try to increase buffer size in Cubase.

If no, it is all about drivers. You need to install the correct ASIO driver supplied by Chord.

Yeah I have the Chord driver installed because I use them for music enjoyment. However in Cubase I get no sound with the Chord driver. I tried a completely new project with the Chord driver to start with, added some audio, but no sound. The same on my older projects if I switch to Chord driver. It's not just me either, because someone in another thread was asking the same thing.

I will look over the settings. There is ASIO guard or something which I should explore. It might well be the answer, but I think I already checked it. Anyway I'll check buffer, and anything else. I did google but nothing really comes up about Mojo and Cubase. Maybe I should just google Cubase clicks.

 

[Deftone]

Speaking of the new creators edition driver's, what's the benefit of it considering the old driver works fine on Windows 10 CE?

 

[SomeGuyDude]

Speaking of the new creators edition driver's, what's the benefit of it considering the old driver works fine on Windows 10 CE?

None.

 

[captblaze]

well the old adage you cant go home again took one in the back side tonight. I was an early Mojo adopter and at the end of last summer in my zeal for greener pastures sold my Mojo thinking another device would take its place. fast forward to this summer. I have been chasing my tail trying to fill the void that Mojo filled in my mobile audio arsenal. I'm not a one size fits all person and that is has become more evident as time goes by. I have an awesome desktop setup and a few very good DAPs, but was missing a device that would allow me to connect my phone, tablet and laptop and be able to have a listening experience beyond what Apple or Microsoft offered. That's when it occurred to me that I never should have sold Mojo. So, when I had an opportunity to get one recently I jumped at it. I now have come full circle and feel I have a good enough balance of audio gear to allow me to vary what I grab based on the situation I find myself in at the time. so for me it is lesson learned and yes... you can go home again.

@Deftone - I installed the original driver package for Mojo and it functions as expected and then installed the CU driver over top with no issues. I don't notice any change in sound quality, but perhaps there is something that was needed to play nice with the new way the O/S deals with audio.

 

[almarti]

The creators driver version doesnt work with Mojo.

So, how have you got Mojo working with Windows 10 Home updated to last version (64-bit)? Thanks

 

[SomeGuyDude]

Just use the Chord driver. I'm fully updated and it works.

Also, definitely bummed that the button-side output is so messed up. Not because it matters in the abstract (I can just use the other one), but because it's just something that doesn't work right.

 

[George Chronis]

For those of us trying the new iOS Betas on our iPhones, my latest experience is below.
iPhone 6S+, Mojo with accessory pack, SW24, Encore U IEM.

iOS 10.3 Beta 3 has now changed to hopefully ensure that any lightning cable "should work as intended".
CCK now works fine with my iPhone 6S+
Lavricable does not work still and this has been the case for a while now. I know it could be sent back for a "fix", whatever that is, however I think I have spent enough on it already to further spend more money to get it to do what it should be doing anyway! I don't see why I should spend more to get it to work.
I am using the Mojo with accessory pack so will stick with that. This is and probably always will be a settee set up for me anyway.

Happy listening all

I'm sorry to bring this back from the dead, but has anyone with a Lavricable been able to make it work with iOS and Mojo recently (10.3.2 iPhone 7)? I've been searching all over and the last threads I can find are from January.

 

[435279]

I'm happy to report, a bit of solder reflow work on my Mojo's RHS headphone socket to PCB connections has fixed the audio drop-outs I was experiencing. I can share my audio again. Yay.

 

[almarti]

Just use the Chord driver. I'm fully updated and it works.

Also, definitely bummed that the button-side output is so messed up. Not because it matters in the abstract (I can just use the other one), but because it's just something that doesn't work right.

Yesterday night I got, I had to restart my Windows 10 laptop in special startup mode to disable Windows to work only with checked digital certificates drives and now all is OK.

 

[loghead]

Hello, I just got the mojo and I need some help.

My goal is to connect the mojo to my Galaxy s7 edge in order to listen to Tidal streaming. Is this not possible? Is there a work around?

When I connect the OTG cable I bought, the power button lights up blue. But when I start playing the file in tidal, theres no sound.

Do I need a 3rd party app? Is there anyway to listen in offline mode?

I assumed mojo would play nicely with my s7 edge based on reviews I read but it seems my targeted use (Tidal) may be more trouble than it's worth.

 

[karmazynowy]

It should work. Show us your otg cable.