Dimension Pro ignores "cutoff" opcode in SFZ files..?

Author
m1cro
Max Output Level: -90 dBFS
  • Total Posts : 12
  • Joined: 2007/10/15 03:26:56
  • Status: offline
2009/06/21 12:13:58 (permalink)

Dimension Pro ignores "cutoff" opcode in SFZ files..?

Hi,

I've converted some soundfonts to the SFZ-format using Extreme Sample Converter (ESC). Some of these soundfonts make use of filters for the samples (e.g. applying a lowpass to the samples for low velocity) and ESC also put these into the SFZ-files by using the "cutoff" opcode.

The SFZ sounds fine when I load it into rgc audio's sfz player, so the conversion from ESC seems to be correct. But when I load the same SFZ into one of Dimension Pro's elements, it doesn't apply the cutoff. The sounds are simply unfiltered. It seems that Dimension Pro (in contrast to sfz player) ignores the cutoff opcode in the SFZ files... which seems strange. Or do I have to make any further settings to get it to work?

SFZ example:

<group>
ampeg_release=3
cutoff=600.1
(...regions with samples for low velocity follow here...)

<group>
ampeg_release=3
cutoff=949.9
(... next regions with samples for higher velocity follow here...)

Greets,
m1cro
#1

2 Replies Related Threads

    b rock
    Max Output Level: 0 dBFS
    • Total Posts : 8717
    • Joined: 2003/12/07 20:31:48
    • Location: Anytown (South of Miami), U.S.A.
    • Status: offline
    RE: Dimension Pro ignores "cutoff" opcode in SFZ files..? 2009/06/21 13:30:24 (permalink)
    Or do I have to make any further settings to get it to work?
    Select a filter type on DimPro's interface, and turn the Cutoff knob fully left (8.2 Hertz).
    #2
    m1cro
    Max Output Level: -90 dBFS
    • Total Posts : 12
    • Joined: 2007/10/15 03:26:56
    • Status: offline
    RE: Dimension Pro ignores "cutoff" opcode in SFZ files..? 2009/06/23 15:23:17 (permalink)
    Thank you for the answer :-)

    That seems to work fine. Wonder why it isn't documented.. (or did I overlook it?)
    And certain velocity levels get muted completely because it apparently applies the 8.2Hz cutoff to it when there's a <group> with no cutoff specified. But I can fix that by editing the SFZs..
    post edited by m1cro - 2009/06/23 15:42:04
    #3
    Jump to:
    © 2024 APG vNext Commercial Version 5.1