Re: Bitrate query
Thanks for the report.
The problem is resolved in new Asset R7.2 beta-
The long explanation:
UPnP spec requires bitrate to be sent as bytes per second, not bits or kilobits, so 320kbps becomes 40000 bytes/second in UPnP media description.
Asset originally reported bitrate calculated from file size + duration. If your file was 320kbps and had attached album cover, reported MP3 bitrate slightly exceeded 320kbps (or 40000 bytes/second).
It seems that BubbleUPnP assumed that reported MP3 bitrate exceeds 40000 bytes/second, the server is broken and puts bits/second value there, resulting in our 40000 bytes/second being treated as 40kbps.
Asset has been updated no to do this anymore; sends bitrate calculated without the tags which is correctly interpreted by BubbleUPnP.
Bitrate query
Collapse
X
-
Re: Bitrate query
Thanks for the bug report.
Can you please send a sample 320kbps MP3 file from your collection to me ( peter@dbpoweramp.com ) for analysis? I can't seem to recreate this issue with 320kbps MP3 files that I encoded myself. Reported bitrate in bubbleupnp is always what it should be.Leave a comment:
-
Re: Bitrate query
Changing mp3 to "as is single" makes no difference. BubbleUpnP (and also HiFi Cast for Android) still see the four alternatives from QNAP Asset, and is getting a 40kbps version to play. The 40kbps issue is only with 320kbps CBR files.
Note however that everything arriving at BubbleUpNp OR HiFi Cast from QNAP Asset offers four streams, even FLAC files (two FLAC, one each L16 and WAV]. But it is only in the case of those 320kbps CBR files that it mysteriously streams a ~40kbps MP3.
And do note that I just reinstalled Asset on my Windows PC. EVERYTHING on the Android side is the same as on QNAP: 320kbps CBR MP3 stream at ~40kbps, "as is single" has no effect, and every stored FLAC or MP3 file is offered as four streams.Last edited by NormB; December 10, 2020, 07:48 PM.Leave a comment:
-
Re: Bitrate query
I am definitely out of my depth here but think I am getting somewhere.
Looking at the debug logs from playing a 320 kbps CBR mp3 file and a 256 kbps one I see in each case there is a get request for two audio/mpeg files, an audio/L16 file and an audio/wav file. When playing the 256 kbps file through Bubbleupnp this is all disregarded and the original mp3 file is played. However, with a 320 kpbs file Bubbleupnp instead sees these four files and not the original: two roughly 40 kpbps mp3s, a WAV file and an L16 file. I can even play the WAV file, which has a name like this: d-782....... ...forced.wav.Leave a comment:
-
Re: Bitrate query
I doubt it. Asset does offer alternatives for control points, try setting to 'as single' then will not get the other options, however it looks like bubbleupnp is doing the transcoding?Leave a comment:
-
Re: Bitrate query
[SIZE=5][SIZE=6][SIZE=7]OK so I ran a debug as suggested. Requesting one 320kbps CBR file via the Bubbleupnp Android app and streaming just to the local device (a tablet)this is what the log file shows:
[/SIZE][/SIZE][/SIZE]
Content Range: -1 to -1
Opening audio file: /share/Music/Ragtime/Adam Sawnson/Ragtime Revival/01. Waffles.mp3
Streaming File Untouched [5794988 bytes]: /share/Music/Ragtime/Adam Sawnson/Ragtime Revival/01. Waffles.mp3
Serve Entity Set to: audio/mpeg
===========ProcessFileRequest================
=============================================
Content Range: -1 to -1
Opening audio file: /share/Music/Ragtime/Adam Sawnson/Ragtime Revival/01. Waffles.mp3
Streaming File Untouched [5794988 bytes]: /share/Music/Ragtime/Adam Sawnson/Ragtime Revival/01. Waffles.mp3
Serve Entity Set to: audio/mpeg
Seems to be trying to send the original. But that is not what shows up in Bubbleupnp,rather the options two distinct 41kbps mp3 files, a WAV file, and an L16 file. Could "Serve Entity Set to: audio/mpeg" being giving Android a problem?Leave a comment:
-
Re: Bitrate query
Thanks for the quick reply. I'll give that a try. Only in the case of this particular kind of mp3 file, something certainly is in the chain producing four available files for streaming via the Bubbleupnp android app, as I can access any one of them.Leave a comment:
-
Re: Bitrate query
You can enable the debug mode in Asset and that will show how the files are being served, I would not think Asset is changing the file.Leave a comment:
-
Re: Bitrate query
Everything is marked "as is", including mp3. As mentioned, this only happens with 320 kbps CBR files. All other .mp3 files arrive as originals, whether CBR or VBR.Leave a comment:
-
Re: Bitrate query
Perhaps you have configured .mp3 files to stream as MP3 which would transcode them, instead you need them 'as is' on the configuration page.Leave a comment:
-
Re: Bitrate query
I also have this problem. Asset upnp (newest version) running on generally QNAP works fine. However when streaming to several Chromecast Audio devices controlled by the Bubble Android UPNP app via WiFi there is one key exception. Bubbleupnp indicates that it is playing a 40 kbps MP3. Bubbleupnp also shows four streams available, none of which is the original 320kbps CBR mp3 file. Other Android players also show 40kbps, so it is not just a Bubbleupnp issue.
Conversely, another UPNP server on the QNAP sends these along just fine. Windows Foobar plays these files fine too via Asset when hardwired via an ethnernet connection.
FYI any other bitrate CBR other than the maximum plays correctly with this setup, as do all VBR files I have tried. There's no bandwidth issue here (I think) as Asset sends along FLAC files correctly and seamlessly. All 320kbps CBR MP3 files play at 40kbps or so via Asset, including those created by dbpa.Leave a comment:
-
Re: Bitrate query
Some more testing.
This time using MediaMonkey as my upnp server rather than Asset.
Connecting to it from BubbleUpnp for Android via BubbleUpnp server and also from MediaMonkey and Windows Media Player on another PC and they all correctly display 320kbps.
I would test from WMP direct to Asset but for some reason WMP cannot find Asset on my network...
Perhaps I need to rescan in Asset.
I'll also speak to the bubbleupnp author.Leave a comment:
-
Re: Bitrate query
Perhaps, ask the bubbleupnp author to investigate please.Leave a comment:
-
Re: Bitrate query
Ok got it, that shows the bitrate correct.
So maybe its an issue with how both MediaMonkey and BubbleUpnp server speak to Asset then, perhaps some interface problem?Leave a comment:
Leave a comment: