Skip to main content

Topic: foo_dsp_effect (Read 123527 times) previous topic - next topic

0 Members and 1 Guest are viewing this topic.
  • mudlord
  • [*][*][*][*][*]
  • Developer (Donating)
Re: foo_dsp_effect
Reply #275
everything should be in release on the upload, i might have got the date wrong on the upload.

the component for deemph should be named foo_dsp_deemph. so it shouldnt conflict.

  • EpicForever
  • [*][*][*][*][*]
Re: foo_dsp_effect
Reply #276
Hi,
Some time ago I asked for Playback Rate Shift to perform simple pass-through (with no processing) when value is set to "0%". I can't find now any change log that would tell me in which version it was introduced AND more importantly - if this is done only in PRS effect or also in Tempo Shift and Pitch Shift. Could you please tell me if all these 3 effects use passing through for 0%/0 semitones etc. setting?

  • mudlord
  • [*][*][*][*][*]
  • Developer (Donating)
Re: foo_dsp_effect
Reply #277
the most recent versions should have it, cant remember when i first added it. all 3 effects you mentioned should have it.

https://github.com/mudlord/foo_dsp_effect/blob/master/dsp_soundtouch.cpp

  • EpicForever
  • [*][*][*][*][*]
Re: foo_dsp_effect
Reply #278
OK, great, thanks!

  • mudlord
  • [*][*][*][*][*]
  • Developer (Donating)
Re: foo_dsp_effect
Reply #279
It shouldn't be too much trouble to add it for the other DSPs. In fact it should be easier as the other ones just modify samples in place and do not change sample pipeline length. I am just wondering if it would be worth the effort.

Question about Tempo Shift changes
Reply #280
Hello there and thank you for continuing to support this great "tool set" for my favorite audio player.


I have one negative point (at least for me): Why can the new Tempo Shift only be cranked up to 75% and not 100% anymore?

Call me crazy but I am now used to listen to podcasts at 100% the speed (two times). Besides all the improvements on other effects that one thing is a KO criteria for me and so I have gone back to 0.16 for now.

Are there plans to put the "double playback speed" (without mickey mouse voice) feature back in?

  • mudlord
  • [*][*][*][*][*]
  • Developer (Donating)
Re: foo_dsp_effect
Reply #281
Willing to try 90%?

It seems the rubberband library has a bug when doing a 100% increase in tempo, but not 90%. Weirdly, slowing down by 100% is fine.

Re: foo_dsp_effect
Reply #282
so if i already use effect dsp for cd pre-emphasis do i need the seprate component or not ?

  • mudlord
  • [*][*][*][*][*]
  • Developer (Donating)
Re: foo_dsp_effect
Reply #283
use the seperate component.

Re: foo_dsp_effect
Reply #284
Willing to try 90%?

I guess. Better than 75% ^_-

But jokes aside now I know that it is a technical limitation and not just an internal change in settings/variables.


I guess offering the old algorithm next to the two new ones as a third option isn't possible anymore?

If so I don't see a reason not to offer the maximum possible in your next update, so 90%.


If the library you are using gets updated in the future you can keep that in mind, maybe we can even go to 200% then... not that I would use that but could be funny :p

  • mudlord
  • [*][*][*][*][*]
  • Developer (Donating)
Re: foo_dsp_effect
Reply #285
Next version should have -95% - 95% for tempo.

I want to add effects from DirectX like chorus, its implementation of reverb, and its gargle effect. (assuming I know enough of DirectX COM to do DMOs in threads) Vibrato and tremelo would be nice too. I suppose I can put out a interim build in the meantime to fix the tempo situation you had.

Re: foo_dsp_effect
Reply #286
I swapped my dll file  with the new 0.20.5 and this is pretty good. No noticeable difference.

You can imagine that I am using that feature primarily to save time so I can listen to more podcasts but the three minutes per hour I am not saving now are acceptable as long as it sounds good ^_^


Just joking this is an awesome plugin. The other features too I am using for listening to music (with normal speed!).