Skip to main content

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

0 Members and 1 Guest are viewing this topic.
  • marc2003
  • [*][*][*][*][*]
foo_dsp_effect
Reply #200
foobar did a similar thing as well. it went from 1.1.9 to 1.1.10.

  • MusX
  • [*][*][*]
foo_dsp_effect
Reply #201
Hello,
is it possible to edit source of the plugin? can you guide me a little how to do that?

I'm interested of 3 decimal places in "Pitch Shift". There are already only two.
You may consider this as feature request

Regards
  • Last Edit: 17 January, 2014, 06:07:24 AM by MusX
my last.fm profile:
http://www.last.fm/user/MusX

  • mudlord
  • [*][*][*][*][*]
  • Developer (Donating)
foo_dsp_effect
Reply #202
Source code is on svn.mudlord.info/foobar2000
you will need a SVN client.

you need WTL with MSVC2008 SP1 to compile. from there, its a simple matter of modifying the relevant source files to increase the granularity of the sliders.

foo_dsp_effect
Reply #203
Hi mudlord. I can't seem to find the non-demph version of your plugin. Anywhere to get it?

Thanks!

  • mudlord
  • [*][*][*][*][*]
  • Developer (Donating)
foo_dsp_effect
Reply #204
Non-demph?


  • EpicForever
  • [*][*][*][*][*]
foo_dsp_effect
Reply #205
Yes, without deemphasis routine implemented. There was such version linked here in this thread.

foo_dsp_effect
Reply #206
Non-demph?


Yes, you posted a version early without de-emphasis as to not conflict with foo_deemph.

  • mudlord
  • [*][*][*][*][*]
  • Developer (Donating)
foo_dsp_effect
Reply #207
Oh, looks like I have to redo that.
Currently I am rewriting some things in foo_dsp_effect, so no ETA.

  • Ello
  • [*]
foo_dsp_effect
Reply #208
Thank you. <3

  • mudlord
  • [*][*][*][*][*]
  • Developer (Donating)
foo_dsp_effect
Reply #209
I'm somewhat happy that this piece of horseshit is appreciated.

  • EpicForever
  • [*][*][*][*][*]
foo_dsp_effect
Reply #210
I managed myself to have lengths of tracks displayed with Playback Rate Shift applied  But it works ONLY when tracks have PRS altered via foo_dynamic_dsp using TRACKDSP tags formatted as for example 102 for +2% PRS change or for example 98 for -2% PRS change. Here it is:
Code: [Select]
%playback_time%[ / $if($meta_test(trackdsp),$div($div($mul(%length_seconds%,100),$meta(trackdsp)),60):$num($mod($div($mul(%length_seconds%,100),$meta(trackdsp)),60),2),%length%)]

which gives for example "7:57 / 8:12", where 7:57 is current playback position and 8:12 is total lenght of track altered by Playback Rate.

Dear mudlord, after inventing that single line of code I have a feature proposal for DSP Effect plugin: adding variables. Variables like %rateshift%, %temposhift%, %pitchshift% etc. I haven't analyzed if any other than %rateshift% would be useful - I got a scenario for this one. If I have %rateshift% variable with values like 100 (for normal playback), 97 (for PRS -3%), 107 (for PRS +7%), etc. I could perform similar division as with values taken from TRACKDSP tags  . Could you be so kind and develop at least %rateshift% ?

  • mudlord
  • [*][*][*][*][*]
  • Developer (Donating)
foo_dsp_effect
Reply #211
Not sure if I am bothered to implement feature requests to be honest. :<

  • EpicForever
  • [*][*][*][*][*]
foo_dsp_effect
Reply #212
I understand that, as I am aware that we are relying on your free time and good will
Anyway for someone who isn't programmer it doesn't look that time consuming. Plugin knows proposed %rateshift% value anyway, as it uses it to its regular operation. There is a question if sending this value to new variable is time consuming task when we talk about implementing it... That's something that you should judge and take into consideration
I think that possibility of displaying track duration after its alteration via playback rate shift is quite attractive option

  • mudlord
  • [*][*][*][*][*]
  • Developer (Donating)
foo_dsp_effect
Reply #213
Yeh, its easy to add.
Problem is, sometimes I am busy with my two jobs or just am too lazy to add stuff.

  • dhromed
  • [*][*][*][*][*]
foo_dsp_effect
Reply #214
Quote
I'm somewhat happy that this piece of horseshit is appreciated.

You are a saviour of the human race, in a pineapple, under the sea.

Not sure if I am bothered to implement feature requests to be honest. :<

I imagine this depends on the request?
I do have one or two, but I don't know if it's productive to just dump it here.

  • mudlord
  • [*][*][*][*][*]
  • Developer (Donating)
foo_dsp_effect
Reply #215
Nah, I just don't bother to implement feature requests to be honest.
It might be best not to dump them here, as I might never be interested in implementing them.

  • hifih66
  • [*]
foo_dsp_effect
Reply #216
Nah, I just don't bother to implement feature requests to be honest.
It might be best not to dump them here, as I might never be interested in implementing them.


I'm a brand new member and don't expect any consideration but would be grateful for the parameters used in your RIAA De-emphasis filter in the IIR section as I need to create the inverse filter for use on the input of my restored 1971 Grundig Radiogram input (which already has the de-emphasis on board) and sounds very bassy (and very loud) when fed directly from foobar.


I've used this in the standard equalizer which doesn't sound too bad but would appreciate a more accurate filter

55Hz -14dB
77Hz -11dB
110Hz -9dB
156Hz -7dB
220Hz -5dB
311Hz -4dB
440Hz -3dB
622Hz -2dB
880Hz -1dB
1.2kHz 0dB
1.8kHz 1dB
2.5kHz 2dB
3.5kHz 3dB
5kHz 4dB
7kHz 6dB
10kHz 8dB
14kHz 10dB
20kHz 13dB

Any help would be appreciated.

  • Last Edit: 24 May, 2014, 04:27:22 AM by hifih66

  • hifih66
  • [*]
foo_dsp_effect
Reply #217
Nah, I just don't bother to implement feature requests to be honest.
It might be best not to dump them here, as I might never be interested in implementing them.


I'm a brand new member and don't expect any consideration but would be grateful for the parameters used in your RIAA De-emphasis filter in the IIR section as I need to create the inverse filter for use on the input of my restored 1971 Grundig Radiogram input (which already has the de-emphasis on board) and sounds very bassy (and very loud) when fed directly from foobar.


I've used this in the standard equalizer which doesn't sound too bad but would appreciate a more accurate filter

55Hz -14dB
77Hz -11dB
110Hz -9dB
156Hz -7dB
220Hz -5dB
311Hz -4dB
440Hz -3dB
622Hz -2dB
880Hz -1dB
1.2kHz 0dB
1.8kHz 1dB
2.5kHz 2dB
3.5kHz 3dB
5kHz 4dB
7kHz 6dB
10kHz 8dB
14kHz 10dB
20kHz 13dB

Any help would be appreciated.


Found this RIAA curve in the page below, which gave these values (approximately +/- 1dB)

And they sound great on my equipment.

http://www.stereophile.com/features/cut_an...p_equalization/

55Hz -17dB
77Hz -15dB
110Hz -13db
156Hz -11dB
220Hz -8dB
311Hz -5dB
440Hz -3dB
622Hz -2dB
880Hz -1dB
1.2kHz 1dB
1.8kHz 2dB
2.5kHz 3dB
3.5kHz 6dB
5kHz 8dB
7kHz 10dB
10kHz 13dB
14kHz 16dB
20kHz 19dB

foo_dsp_effect
Reply #218
I find this plugin highly useful, thanks for the great work so far, OP!
I was wondering if there's a way to display my current DSP preset anywhere within foobar interface using title formatting variable or something like that?
I tried %dsp_preset% and %__dsp_preset% but obviously that didn't work out :)

  • mudlord
  • [*][*][*][*][*]
  • Developer (Donating)
foo_dsp_effect
Reply #219
decided to add a bugtracker at http://bugs.mudlord.info/.

Source code is at: http://svn.mudlord.info/foobar2000

  • mjb2006
  • [*][*][*][*][*]
foo_dsp_effect
Reply #220
I registered at the bugtracker but it doesn't let me submit anything.

I'm consistently getting crashes when I try to play files tagged with PRE_EMPHASIS 0. They work fine in safe mode, and they work fine with PRE_EMPHASIS 1. The crash reports start out like this:

Code: [Select]
Illegal operation:
Code: C0000005h, flags: 00000000h, address: 6AB4FB8Dh
Access violation, operation: read, address: 00000000h
Last win32 error: 8

Call path:
playback_process entry=>input_decoder::run

Code bytes (6AB4FB8Dh):
6AB4FB4Dh:  8D 04 C8 8B 00 56 8B 75 08 52 50 E8 D3 04 00 00
6AB4FB5Dh:  5E 5D C2 08 00 CC CC CC CC CC CC CC CC CC CC CC
6AB4FB6Dh:  CC CC CC 55 8B EC 53 33 DB 38 5D 0C 56 0F 95 C3
6AB4FB7Dh:  33 F6 39 77 08 76 23 8B 47 04 8B 0C B0 8B 45 10
6AB4FB8Dh:  8B 11 8B 52 0C 50 8B 45 08 53 50 FF D2 84 C0 74
6AB4FB9Dh:  03 83 CB 02 46 3B 77 08 72 DD 5E 5B 5D C2 0C 00
6AB4FBADh:  CC CC CC 56 8B F0 8B 07 8B 50 1C 8B CF FF D2 50
6AB4FBBDh:  8B 07 8B 50 10 8B CF FF D2 50 8B 07 8B 50 18 8B

Stack (0C60F284h):
0C60F264h:  00000000 045B5AB0 045B5AB0 045B5924
0C60F274h:  00D14EDC 00000000 7729890D 6AC016D5
0C60F284h:  00C1C1E0 00C1C380 0C60F2B0 6AB4F581
0C60F294h:  00C1C380 00000000 04C9B7D8 00C1C1E0
0C60F2A4h:  0C60FB64 00C1C1D8 00C1C1D8 0C60F2DC
0C60F2B4h:  6AB4F2B8 0C60FB64 04C9B7D8 04C9B7D8
0C60F2C4h:  0C60FB64 04C9B818 6D4C2836 007D8450
0C60F2D4h:  00D75678 00000012 0C60F2F0 6AB4EFD5
0C60F2E4h:  0C60FB64 00000000 04C9B7D8 0C60F314
0C60F2F4h:  00D212DB 0C60FB64 04C9B7D8 04C9B818
0C60F304h:  00000016 0C60FBE0 00D4333D 00000000
0C60F314h:  0C60F340 00CA6651 04C9B998 0C60FB64
0C60F324h:  04C9B7D8 04C9B7D8 04C9BA20 04C9B778
0C60F334h:  04C9BA20 04C9B778 01005A14 0C60FBEC
0C60F344h:  00CA85D8 04C9B818 04C9B7D8 00000000
0C60F354h:  04C9B778 04C9BB94 00000000 00000000
0C60F364h:  00000000 00000000 00000000 1A873F01
0C60F374h:  0C60F228 00000000 0C60F3EC 772D71F5
0C60F384h:  61CF762D FFFFFFFE 77290098 7728FD4F
0C60F394h:  00000001 00000001 00000000 0C60F418

Registers:
EAX: 04C9B7D8, EBX: 00000000, ECX: 00000000, EDX: 000000A9
ESI: 00000000, EDI: 00C1C3B0, EBP: 0C60F28C, ESP: 0C60F284

Crash location:
Module: foo_input_std
Offset: 1FB8Dh

This is with foo_dsp_effect 0.12 in foobar2000 1.3.3 on Win7/64-bit. I also have the waveform seekbar 0.2.4045, if that matters. Let me know what other info you need. I can put sample files somewhere for you if you want.
  • Last Edit: 09 October, 2014, 02:38:34 AM by mjb2006

  • mudlord
  • [*][*][*][*][*]
  • Developer (Donating)
foo_dsp_effect
Reply #221
Going to look at that bugtracker problem.
edit: try now.
as for this problem, tried posting on the tracker now?
  • Last Edit: 24 October, 2014, 05:34:37 PM by mudlord

  • mudlord
  • [*][*][*][*][*]
  • Developer (Donating)
foo_dsp_effect
Reply #222
I managed myself to have lengths of tracks displayed with Playback Rate Shift applied  But it works ONLY when tracks have PRS altered via foo_dynamic_dsp using TRACKDSP tags formatted as for example 102 for +2% PRS change or for example 98 for -2% PRS change. Here it is:
Code: [Select]
%playback_time%[ / $if($meta_test(trackdsp),$div($div($mul(%length_seconds%,100),$meta(trackdsp)),60):$num($mod($div($mul(%length_seconds%,100),$meta(trackdsp)),60),2),%length%)]

which gives for example "7:57 / 8:12", where 7:57 is current playback position and 8:12 is total lenght of track altered by Playback Rate.

Dear mudlord, after inventing that single line of code I have a feature proposal for DSP Effect plugin: adding variables. Variables like %rateshift%, %temposhift%, %pitchshift% etc. I haven't analyzed if any other than %rateshift% would be useful - I got a scenario for this one. If I have %rateshift% variable with values like 100 (for normal playback), 97 (for PRS -3%), 107 (for PRS +7%), etc. I could perform similar division as with values taken from TRACKDSP tags  . Could you be so kind and develop at least %rateshift% ?



I was in the mood to fix some things in dsp_effect, and thought about this. But according to Case, it seems DSPs cannot broadcast titleformat syntax variables D:.

edit: here is the non deemph build, build fresh from SVN. pondering about rlsing 0.15....
  • Last Edit: 01 November, 2014, 07:15:07 AM by mudlord

  • EpicForever
  • [*][*][*][*][*]
foo_dsp_effect
Reply #223
Well, OK, not your fault
Thanks for updates anyway

  • Nisto
  • [*][*]
foo_dsp_effect
Reply #224
Having problem applying echo and reverb DSPs while playing back this track (it stutters): https://dl.dropboxusercontent.com/u/4845446...ass%20Pulse.wav

A picture tells a thousand words, so I'll just post the waveform of it: