Thank you for your donation!


Problem: mconnect problem with aac files
#1
Hello
I have a raspberry with the latest moode and a second system on the second sd volumio card and in both I have a problem with the mconnect application for listening to Tidal.
Well, the problem is that in the mconnect application listening to, for example, my favorite any list (especially older recordings), if it ends, the program randomly selects its other list of similar songs and plays it beautifully but until .....
When the song appears, the file in aac format the raspberry device stops and does not play this song (I will add that on the phone with the adroid mconnect plays the aac format), you have to manually jump to the next song which is in the flac format, it is tiring enough because in the selected randomly by mcoonect there are several such songs.
I also have bubleupnp installed but using it, the look of the mconnect application itself is sensational for me and I want to stay with this program.
E.g: in mconnect after choosing Perfect - Autobiography shows as many as four different covers from albums of this recording (of course one of them is the unfortunate aac format) and in bubleupnp there is only one to choose from which indicates that bubleupnp has somehow a smaller search resource tracks versus mconnect, although both are search through Tidal.
The question is, can you somehow force the raspberry to play this aac file in mconnect?
This is a bit strange because aac internet radios are played but I read somewhere that there are different aac formats and maybe someone has some codec to install in the raspberry to get it started.
Thank you in advance for any help
Regards
Evan3535
Reply
#2
(02-06-2020, 07:52 PM)evan3535 Wrote: Hello
I have a raspberry with the latest moode and a second system on the second sd volumio card and in both I have a problem with the mconnect application for listening to Tidal.
Well, the problem is that in the mconnect application listening to, for example, my favorite any list (especially older recordings), if it ends, the program randomly selects its other list of similar songs and plays it beautifully but until .....
When the song appears, the file in aac format the raspberry device stops and does not play this song (I will add that on the phone with the adroid mconnect plays the aac format), you have to manually jump to the next song which is in the flac format, it is tiring enough because in the selected randomly by mcoonect there are several such songs.
I also have bubleupnp installed but using it, the look of the mconnect application itself is sensational for me and I want to stay with this program.
E.g: in mconnect after choosing Perfect - Autobiography shows as many as four different covers from albums of this recording (of course one of them is the unfortunate aac format) and in bubleupnp there is only one to choose from which indicates that bubleupnp has somehow a smaller search resource tracks versus mconnect, although both are search through Tidal.
The question is, can you somehow force the raspberry to play this aac file in mconnect?
This is a bit strange because aac internet radios are played but I read somewhere that there are different aac formats and maybe someone has some codec to install in the raspberry to get it started.
Thank you in advance for any help
Regards
Evan3535

Hello,
I have same problem experienced today. Using mconnect on an iPhone and allo UsBridge sign.
As I'm a new user of moOde on a new Allo USBridge it was the first time today, that streaming from Tidal did not work.
After a bit of trouble-shooting nothing helped and I finally could reproduce the problem, it always happened with AAC titles from Tidal.

 Could we get an answer please?

Thx.
Reply
#3
Why do you think this is a moOde issue?
Reply
#4
well, I thought there are only 2 possibilities where the problem could be: 1-moOde or 2-Mconnect

checked so far everything I can think of, but ... no luck so far.

AAC from my library can be played, but not from Tidal ????
Reply
#5
(02-24-2020, 07:40 PM)Manni Wrote: well,  I thought there are only 2 possibilities where the problem could be: 1-moOde or 2-Mconnect

checked so far everything I can think of, but ... no luck so far.

AAC from my library can be played, but not from Tidal ????

Tidal's AAC content works fine for me on Moode, I'm using BubbleUPnP as the UPnP client.

Edit: I've tried the mconnect lite app on Android and yes, the problem is with the app which doesn't appear to be as stable or featureful as BubbleUPnP, reading the reviews on the Google Play Store doesn't inspire confidence in the app.
Just use the better app.
Reply
#6
Tested today streaming from my MacBookPro with Audirvana 3+ and Audirvana remote app with plugin Tidal via WLAN to my router via LAN the Allo USBridge Sign. with moOde and I could play the same AAC file from Tidal, which does not play using mconnect light app.

Using the route via MBP and Audirvana as well let one play Tidal MQA with a first unfold. 
So my Chord Mojo DAC gets a MQA file in either 24/88kHz or 24/96kHz. 

Using the mconnect app I can play the Tidal MQA files, but the Chord Mojo receives only 16/44kHz, even the mconnect app shows 16bit/48kHz.

The AAC file from Tidal, which does not play from the mconnect app is shown in Audirvana as a AAC 16bit with only 96kbit. Maybe this "low" bitrate (even lower than the poorest 128kbit MP3 or AAC quality) will not be processed - ?? 

Sound quality from Tidal seems to be more crisp with MBP/Audirvana/moOde/Mojo compared to Mconnect/moOde/Mojo, but as well a bit brighter and more fatiguing.
I know, it should be no difference as bits are bits, but thats what I hear.

May have a look at the BubbleUPnP - thanks for the feedback. However, I think, that BubbleUPnP is not for IOS/iPhone ???
Reply
#7
(02-25-2020, 06:55 PM)Manni Wrote: ............................. snip ................................. The AAC file from Tidal, which does not play from the mconnect app is shown in Audirvana as a AAC 16bit with only 96kbit. Maybe this "low" bitrate (even lower than the poorest 128kbit MP3 or AAC quality) will not be processed - ?? ........................................... snip ..............................

Could it be that the actual 'reading' is AAC 16 bit/96 KHZ rather than 96kbit...?... not so poor in comparison with any MP3...
Reply
#8
No, the file format is AAC 16 bit / 96 kbps
Reply


Forum Jump: