reverbel
-
Posts
23 -
Joined
-
Last visited
Content Type
Profiles
Forums
Blogs
Gallery
Downloads
Poweramp Knowledge Base
База знаний Poweramp
Poweramp知识库
Poweramp Equalizer Knowledge Base
База знаний Poweramp Equalizer
Store
Events
Ideas
Posts posted by reverbel
-
-
On 2/15/2023 at 9:14 PM, Fitzian said:
Rather than suggest I use Bing... (odd choice, that) how about you point me in the direction of a reputable digital music retailer selling spatial audio formats.
iTrax.com is such a digital musical retailer:
https://www.itrax.com/
Being the digital retail arm of the AIX Media Group (AIX Records), it is certainly reputable:
https://www.itrax.com/about/
This is an example of album (great music, btw!) that may be purchased either in stereo or in 5.1:
https://www.itrax.com/product/cheryl-bentyne-among-friends/ -
Just now, reverbel said:
UAPP does not allow me to select the sampling rate. Whenever I play a file in UAPP, the actual sampling rate of the file appears in the DAC display. Attached is a photo of the DAC while a 96 kHz file is being played by UAPP.
If I select an output sampling rate of 96 kHz in Poweramp, the DAC display shows 48 kHz. Regardless of the selected output sampling rate (I've tried all the available options), the DAC display shows 48 kHz.
Well, looking further, now I see that UAPP has an option to limit the sampling rate. This option (which I never used) lets you select the maximum sampling rate of the signal sent out to the USB DAC. It defaults to "no limit".
-
43 minutes ago, MotleyG said:
Ya this looks strange. Poweramp is even reporting “No Resampling” yet the DAC shows 48kHz instead of 44.1.
Looks like we will need to wait to hear from @maxmp at this point.
As a separate test, does UAPP have a function to resample to USB? If so, what happens if you select something like 96kHz from UAPP - what does the DAC show then? And what does it show if you tell Poweramp to also resample to 96kHz?
UAPP does not allow me to select the sampling rate. Whenever I play a file in UAPP, the actual sampling rate of the file appears in the DAC display. Attached is a photo of the DAC while a 96 kHz file is being played by UAPP.
If I select an output sampling rate of 96 kHz in Poweramp, the DAC display shows 48 kHz. Regardless of the selected output sampling rate (I've tried all the available options), the DAC display shows 48 kHz. -
28 minutes ago, andrewilley said:
With some music playing and the DAC connected, go to PA Settings=>Audio=>Output=>Hi-Res Output and ensure that 'USB DAC' is enabled. Then tap on the settings icon and adjust the desired Sample Rate and Sample Format. Which options are available may be dependent on the device you are using.
Andre
Thanks for your quick reply, Andre.
I did that. When I set the output sampling rate to be the same of the played track, Poweramp performs no resampling and informs that its output has the selected sampling rate. See screenshots for the case of a file sampled at 44.1 kHz.
Even so, the signal that reaches the USB DAC has a sampling rate of 48 kHz, regardless of the rate I selected, and regardless of what Poweramp says. It appears that Android resamples the Poweramp output at 48 kHz anyway.
-
1 minute ago, reverbel said:
@MotleyGThat is now what I am seeing here. My USB DAC is a Loxjie D30, which has a display that shows the sampling rate of its input signal. It shows 48 kHz even when I set the Poweramp output rate to 44.1 kHz. Please see the first photo attached.
The information on the DAC display appears to be accurate. When I use this DAC with UAPP running on my Android phone (second photo attached) or with the Strawberry player running on a PC, the DAC display correctly shows the sampling rate of the file played.
I wonder if I missed some Poweramp setting... How can I select the actual sampling rate of the signal sent out to the DAC over the USB connection?
-
On 8/2/2022 at 4:19 PM, MotleyG said:
If you set the output to match the file input (44.1 --> 44.1) then there is no resample. But Poweramp does not currently have a way to have the output track to any changes to the file type. So if you have 96kHz files, you would have to manually change the output to match this again. If most of your files are 44.1kHz (most are if you ripped from CD) then I would set it to match and let only the few others resample in those cases.
@MotleyGThat is not what I am seeing here. My USB DAC is a Loxjie D30, which has a display that shows the sampling rate of its input signal. It shows 48 kHz even when I set the Poweramp output rate to 44.1 kHz. Please see the first photo attached.
The information on the DAC display appears to be accurate. When I use this DAC with UAPP running on my Android phone (second photo attached) or with the Strawberry player running on a PC, the DAC display correctly shows the sampling rate of the file played.
-
@maxmp: Thanks also for the observation regarding the cascade mode for the overlapping bands and the max band gain reduction. I see the "Smooth Equalizer/Tone Gains" option in the settings of the Poweramp EQ, but could not find a "Bands Overlap" option there. Found it the settings of the standalone EQ app, but not in the Poweramp EQ.
-
Thanks for your response, @maxmp!
The idea of an optional advanced mode sounds great.
I think it would be sufficient to allow extended parameter ranges in imported presets. REW-generated presets may have quite a few filters (10 or more filters in a preset are common), so it is not very convenient to enter them via the Poweramp UI anyway. It is much more practical to create a json file with the preset and import it into Poweramp. I use a Python script that reads a csv file whose lines are triples <freq, gain, Q> and generates a json file in the format accepted by Poweramp.
Extended gain ranges require a lot of headroom indeed. In some of my presets with high-gain filters (implemented with the "filter pair" trick), the preamp gain is set to a large negative dB value. (One of these presets has Preamp = -12dB!) A lot of volume is lost, but fortunately this tends to happen mostly in presets for small listening rooms, when volume is not an issue.
I've heard that high-Q filters have floating-point issues, but have no idea about how far Q could be increased without resulting in unstable filters. Perhaps 10 or 12 is already a sensible value for max_Q... If this is the case, please ignore the Q part of my request. Having an upper limit on Q is much better than ending up with bad filters!
-
Hello,
Many audio enthusiasts use REW (https://www.roomeqwizard.com/) to generate parametric EQ presets optimized for their listening environments. However, REW-generated filters have
- gain parameters in the range from -20 to 20
- Q parameters in the range from 0 to 20.
Moreover, for low frequency (below 200 Hz) filters, REW-generated frequency parameters may take fractional values. Please see the attached file for an example.
Since Poweramp started supporting parametric EQ, I have been using it with REW-generated EQ presets and am very pleased with the results. However, due to the different parameter ranges accepted by Poweramp EQ (which are smaller than the ranges above), manual changes to the optimized presets are needed.
In order to circumvent the smaller gain range (from -15 to 15) accepted by Poweramp EQ, I replace each filter with gain parameter greater than 15 or less than -15 by a pair of filters with identical frequency and Q parameters, and whose overall gain (i.e., the sum of their gain parameters) is the needed gain.
In order to circunvent the smaller Q range acccept by Poweramp EQ, I replace each filter with Q parameter greater than 10 by a filter with Q = 10, then ask REW to re-optimize the remaining filter parameters. I do something similar to deal with low-frequency filters with fractional frequencies.
Would it be possible to change the accepted parameter ranges of the Poweramp parametric EQ so that is takes gain parameters from -20 to 20 and Q parameters up to 20?
@maxmp: Thanks for the great player!
-
The title says pretty much everything.
A recent update on Poweramp EQ increased the upper limit on the Q parameter. Before this update, the UI enforced the rule "Q less or equal to 10". Now it enforces the rule "Q less or equal to 12". However, Poweramp won't apply any preset that has a filter with Q > 10. Such a preset will be silently ignored.
Poweramp build-939-bundle-play [939004-333c8a71]
Samsung Galaxy S10+
Android 12
To reproduce the bug, pick any working EQ preset, add to it a peaking band filter with, say, Q = 11, and try to apply the preset.
I have various REW-generated EQ presets for my usual listening environments. Each of these presets provides a flat frequency response for a specific room and speaker pair combination. When I saw that the Q parameter cap had been increased, I "improved" my presets to take advantage of the new cap... And the presets ceased to work. :-(
-
On 4/12/2022 at 5:18 AM, andrewilley said:
An "Output Follows Source Formatting" mode would satisfy most of this type of request that I've seen in the forums. People who ask for it often maintain that they would prefer to use PA for all of its other features (such as the EQ) so they clearly are not interested in genuine bit-perfect reproduction which would prohibit any further digital manipulation of the audio path - so no gain/volume, EQ adjustment, crossfade, etc. They more accurately want a no resampling mode.
I also think the resulting issues with crossfade and gapless may be a bit of a red-herring too. Within any given album it's unlikely that the individual tracks would be encoded at different sampling rates or bit-depths anyway, so gapless would still work. The main time it would be an issue is during All Songs shuffle play, and it would be easy enough to add a second option to allow PA to disable the Format Following feature while shuffling random songs (if the user preferred it that way).
Andre
+1 to an "Output Follows Source Formatting" mode that avoids resampling.
Most of the time I use PA with its equalizer, which is very good. However, when listening to playlists with tracks encoded at different sampling rates and/or bit depths, I switch to UAPP, whose equalizer is not nearly as good as PA's (and whose UI is much worse). A "no resampling" mode would allow me to finally ditch UAPP. -
Fixed! Poweramp and Chromecast Audio work together again. Thanks!
-
On 3/14/2022 at 3:50 PM, Berg said:
Hi,
Same here:
* I am able to click "cast" in Power Amp
* Power Amp thinks it is casting (allows to click stop, to control volume)
* But there is no "Ding" connection sound from Chrome Cast audio as usual, and no output from Chrome Cast Audio
* After ~ 30-secs - 1 minute, Power Amp disconnects from Chrome Cast Audio, and Chrome Cast Audio makes a disconnection "Dong".This started happening this morning for me using older Power Amp version. Upgrading to latest Power Amp version (build 925 (925004-e493ac43)) did not help.
Firmware of my Chrome Cast audio is 1.56.281627 (aka 2021 Dec 21 release - I am not sure when it was pushed to my Chrome Cast Audio (I suspect it was pushed overnight, before the failure)).
Can anyone confirm that it worked for anyone with Chrome Cast Audio firmware 1.56.281627 earlier? I am curious if update for all of us reporting here was pushed yesterday.I am on Android 9.
Chrome Cast Audio works itself - I am able to cast media from Google Home app.
Same problem here. Poweramp and Chromecast Audio stopped working together on Sunday (Mar 13, 2022) night. Behavior is exactly as Berg described.
I am running Poweramp build-932-bundle-play [932004-72aa156d] on a Galaxy S10+ with Android 12. My CCA has firmware 1.56.281627. -
10 hours ago, maxmp said:
@andrewilley the autosave/presets editing/accidental changes definitely require improvements. One possibility is preset “locking”. Changing locked preset should be impossible or <default preset> will be changed instead or copy of the preset will be automatically made.
This is the best solution, @maxmp.
Not all EQ settings will be imported from autoEQ, some will still be manually entered. After you went through the work of manually entering an EQ setting, you want to make sure it won't be affected by some accidental change. Preset locking is the way to go! -
20 hours ago, andrewilley said:
@reverbel ... since build 909 the main Poweramp app also supports a Parametric EQ internally too.
@andrewilley: Thanks for mentioning that! I was not aware that the parametric EQ had already been ported to the PA player app.
I have just updated my player to the newest build.
-
3 hours ago, Aller2TeaM said:
It also requires for you to enable MusicFX on volume/tempo/balance tab in PA Player.
@Aller2TeaM: Thanks! I had overlooked that setting. Everything works perfectly now.
-
Hello,
I am a user of the Poweramp Player app. I installed Poweramp Equalizer build-908-arm64-play to use it with the Poweramp Player app, while the parametric equalizer is not ported to the player app.
The parametric equalizer looks very good! @maxmp: Thanks for your great work! I have already purchased the premium version of the EQ app, in order to support further development.
The EQ app works fine with YouTube Music on my phone. However, I was not able to make it work with the Poweramp Player app.
The player and EQ apps are running on a Samsung Galaxy S10+ with Android 11. I have already disabled DVC and enabled MusicFX in Poweramp Player, granted DUMP and Notification Listener permissions to Poweramp EQ, turned on the experimental "Enable Player Tracking" feature of the EQ app, and turned on "Disable absolute volume" under "Default USB configuration" in Android Developer options. Is there something else I should do?
Thanks! -
This feature would be great not only for headphones, but also for speakers. Audio Science Review publishes parametric EQ settings for reviewed speakers (see example in the attached image).
I don't really care for a UI for this. Just being able to select a text file (which could be in CSV format) with (frequency, gain, Q) triples would be fine!
PS: The image is from https://www.audiosciencereview.com/forum/index.php?threads/jbl-stage-a130-review-speaker.18260/
-
I confirm that Poweramp does a license check not only after it is reinstalled, after a system reset (whatever that means), or after a ROM update.
My wife and I are both Poweramp users. I convinced her to purchase the app because I was very satisfied with Poweramp. However, it appears that she was never able to use the app for an entire flight. After some time with the phone in airplane mode, the music player walks out on her saying that the license verification failed. This is not reasonable at all and makes Poweramp look like a scam.
The strange thing is that the failing license checks happen to my wife, but not to me! And our phones are identical: each of us has a stock Galaxy S7. In both phones, Poweramp shows the information "Purchase Verified" and "Store: Play" in Settings->About.
A difference that may or may not be relevant is the app usage pattern. I use Poweramp most of the time. My wife is more like a casual user, who sometimes spends several days without opening Poweramp. But she wants to use it when traveling by plane or by car. And the app in her phone refuses to work in the absence of an internet connection... Yesterday we traveled together, side by side in a plane. I used Poweramp during all flight, but she got a failed license check after half an hour or so.
If the intention is for the license to be "checked once/twice (website/play) and stored forever", then Poweramp has a bug. The problem may not be easy to understand and reproduce, but it exists and shows up in a stock Galaxy S7. If the developer cannot fix the bug, he should at least provide some workaround for the unlucky paying customers that are being bitten by it.
Can we have spatial audio support ?
in Poweramp Feature Requests
Posted
@MotleyG @Fitzian
Apologies for the confusion! I took "traditional multichannel audio" for the new "Spatial Audio", which I didn't even know existed.
It would be a nice thing, however, to be able to stream 5.1 audio from a phone to an AVR and listen to the music "spatially" in all the speakers. Without downmixing the audio to 2.0, of course. Not the highest thing on my list of priorities, but a nice thing anyway.