Skip to main content

Notice

If you are using a Hotmail or Outlook email address, please change it now, as Microsoft is rejecting all email from our service outright.
Topic: foo_dsp_effect (Read 166922 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Re: foo_dsp_effect

Reply #450
Quote
Question: is it possible to use some portions of your playback rate code and add it easily into Android / mobile version of foobar? I am asking more from technical point of view, as I have no idea about portability of code and your code for this certain plugin.

That is something for Peter to consider, only he has control of the source. SoundTouch should work fine on Android.

If there's any way of porting it to mobile and more specifically Playback Rate Shift I'd be eternally grateful, cheers

Doubt that will happen. Only Peter and some other devs work on foobar2000 mobile. As I said, the SoundTouch library is LGPL and should work fine on Android/iOS.

I cannot port foo_dsp_effect to Android.

Re: foo_dsp_effect

Reply #451
Hi, I updated to a newer version of dsp_effect (0.43) and I noticed a few things with the "Pitch/Tempo/Playback Rate" effect:
1. When hovering over the slider bars, scrolling up makes the percentage go down, while scrolling down makes the percentage go up. This is backwards.
2. Clicking on the slider makes the playback rate jump up or down 30%. This is a lot higher than what I ever use and I was wondering if there was any way to lower it (maybe it would jump up/down 1% or 2% instead?)
3. Is it possible to add a keyboard shortcut to change the playback percentage rates? For example, a keyboard shortcut to make the PB rate go up 1%, one to make it go down 1%, and another to reset it to default?
4. Is it possible to make the component's gui/window smaller, or change the layout somehow?  This is how my foobar looks with the latest version, and a square is not very conveniently shaped (see the screenshot below). It would be ideal if I could somehow only get the PB section and condense it down to be a lot thinner vertically somehow (even if it meant making it longer horizontally).



Please let me know your thoughts on all four of these and if there would be any chance of making them happen. Thank you!

Re: foo_dsp_effect

Reply #452
Quote
1. When hovering over the slider bars, scrolling up makes the percentage go down, while scrolling down makes the percentage go up. This is backwards.

I am using the default WTL class behaviours, not subclassed.

Quote
2. Clicking on the slider makes the playback rate jump up or down 30%. This is a lot higher than what I ever use and I was wondering if there was any way to lower it (maybe it would jump up/down 1% or 2% instead?)

Again, using default WTL behaviour for the slide control. It is possible to change the amount of "pages" so it goes up by one percent each click. (see .SetPageSize). Which means then clicking endlessly to make it where you want, where you could just slide instead or enter the exact value.

Quote
3. Is it possible to add a keyboard shortcut to change the playback percentage rates? For example, a keyboard shortcut to make the PB rate go up 1%, one to make it go down 1%, and another to reset it to default?

Adding a keyboard bind would be possible in the UI element box. Making it configurable would make it an entirely different matter as then I would have to bother with making a full blown bind set configuration system too.

Quote
4. Is it possible to make the component's gui/window smaller, or change the layout somehow?  This is how my foobar looks with the latest version, and a square is not very conveniently shaped (see the screenshot below). It would be ideal if I could somehow only get the PB section and condense it down to be a lot thinner vertically somehow (even if it meant making it longer horizontally).

Doing so would mean a drastic rewrite of the UI element. Personally I don't use the element as a box in the main FB2K view, so I never seen a need to make all UI elements the component exposes have all resizable UI controls. And to me frankly its not happening in the current future.

All the component stemmed from some personal needs of mine, its just a side effect somehow some other people seem to like the stuff exposed in it.  :-\


Re: foo_dsp_effect

Reply #453
I'll gladly make the changes in the source code and compile it just for myself. Could you point me to which files in particular each of these changes would need to be made in? I'm only interested in the Playback Rate element.

Re: foo_dsp_effect

Reply #454
dsp_soundtouch.cpp


 

Re: foo_dsp_effect

Reply #455
Does anyone know what's happened to this plugin? It doesn't seem to be available.

Re: foo_dsp_effect

Reply #456
Thats because I don't want anything to do with it or any of the other stuff I used to code.



Re: foo_dsp_effect

Reply #458
Right now I am too preoccupied with real world happenings to deal with anything remotely coding related. I have to sort out those matters first before I am even feeling comfortable enough to try code publically again.

I suppose I can upload to the uploads forum a copy of the binary and the source code. Thats the least I can do I suppose.

Re: foo_dsp_effect

Reply #459
Right now I am too preoccupied with real world happenings to deal with anything remotely coding related. I have to sort out those matters first before I am even feeling comfortable enough to try code publically again.
Sounds like something really nasty happened =(
Hope that it (whatever it is) works out for you in the end...

And thanks for sharing the code, so that components could live on.

Re: foo_dsp_effect

Reply #460
Just had something physical health related pop-up and I really should deal with that first before doing I am comfortable doing anything else. Nothing overly major or anything, but I have to really look out for myself now way more than I used to months ago.

If it also means giving up programming or something to reduce stress or other things, so be it tbh.

Re: foo_dsp_effect

Reply #461
Just had something physical health related pop-up and I really should deal with that first before doing I am comfortable doing anything else. Nothing overly major or anything, but I have to really look out for myself now way more than I used to months ago.

If it also means giving up programming or something to reduce stress or other things, so be it tbh.

I hope things get better for you, mudlord. Thank you for all the work you've done.

 
SimplePortal 1.0.0 RC1 © 2008-2020