Pimsilveira
Head-Fier
Ok thank you. I see what you meanFrom post #3:
Ok thank you. I see what you meanFrom post #3:
https://penonaudio.com/blue-micro-usb-to-lightning-cable.html?search=lightning%20cable
Does this cable 'play nice' with ios 11.2.6
Question for Rob.
Rob, please, I'd need you shed some light.
In the Support forum of JRiver Media Center I created a thread because I do know you said these words:
"It is always better to give Mojo bit perfect files and let Mojo do the work, as the processing within Mojo is much more complex and sophisticated than a mobile or PC.
So when you have an app that has a volume control, and no bit perfect setting, then set it to full volume on the app on the assumption that this will keep the data closer to the original file.
The volume control function on Mojo is much more sophisticated than the PC as I employ noise shaping and I do the function at a very high internal sample rate. Hopefully using the volume set to max on the app will mean the volume coefficient is 1.0000000... so it will return the original data."
Actually I did notice an audible difference when I disabled any volume Handling from within the app.
I stressed out that Mojo (and Hugo as well) does need to be fed by a bitperfect stream AND to handle itself volume.
But that app by default outputs every PCM as 32bit by means of padding: i.e. 16bit and 24bit are padded on the fly by that app to 32bit.
I was told that the audio content is just the same but I replied that if this may help lower grade DACs by avoiding delays in mode switching, it is no longer feeding Mojo in bitperfect mode.
I need your point of view about that, please
Thanks in advance
Yes actually all USB data is 32 bit - even if the file is 16 bit - but the 16 LSB's are simply zero. So nothing to worry about there, they just simply extended the bit's by adding zeros.
Such claims have been made successfully in the past.Does anyone know if I would be able to make a warranty claim within 1 year against broken usb/headphone sockets if they give? My mojo is barley 2 weeks old and the headphone sockets are making creaky sounds when the jack is taken in and out. I'm being really careful taking anything in or out but they seem fragile. I know some have made claims on battery failure but are broken sockets also covered?
Such claims have been made successfully in the past.
My advice is to be honest with Chord when you describe how you use the Mojo.
There was one famous case on this thread, where the owner stated that he was very careful with his Mojo, but then posted photos showing the usb sockets completely ripped from the circuit board - and that would have taken some force.
Understandably @Mojo ideas was not amused, but I think the repair was eventually sorted out ok.
Anyone ?Maybe unlikely but has anyone compared the Graham Slee Bitzie to the Mojo?
Is there any plan to release a new version of the mojo within the next two years? I'm in the process of saving up for an upgrade and don't want to purchase the mojo only for the mojo 2 to be released soon after.
I think that you are in the right ballpark there.Personally I think the mojo will have a minimum 5 year run before it’s updated and then after that we might see something with specs close to Hugo2 in Mojos size and then obviously soon after Hugo3 would follow to push the portable benchmark even higher.
If so I'll upgrade, currently very happy with Mojo in my portable rig.Personally I think the mojo will have a minimum 5 year run before it’s updated and then after that we might see something with specs close to Hugo2 in Mojos size and then obviously soon after Hugo3 would follow to push the portable benchmark even higher.