Welcome, Guest
Username: Password: Remember me
  • Page:
  • 1
  • 2

TOPIC: Crash loading SFZ exported with discoDSP Bliss

Crash loading SFZ exported with discoDSP Bliss 2 years 3 months ago #2

  • ziyametedemircan
  • ziyametedemircan's Avatar
  • Offline
  • Elite Member
  • Posts: 175
  • Thank you received: 60
The samples you can load into a soundfont can only be 16 or 24 bit.
The problem occurs because your samples are 32 bits.
You need to convert them to at least 24bit.

PS: I converted one of the files you attached.

This message has an attachment file.
Please log in or register to see it.

The administrator has disabled public write access.

Crash loading SFZ exported with discoDSP Bliss 2 years 3 months ago #3

  • Mao
  • Mao's Avatar
  • Offline
  • New Member
  • Posts: 4
ziyametedemircan wrote:
The samples you can load into a soundfont can only be 16 or 24 bit.
I converted one of the files you attached.
Zi - This is interesting because, loading the original files into Wavosaur, they read - in the interface - to be 16 and 24 bit. May I ask what program you used to verify the bit depth? Also, whatever program it was, it did not maintain the embedded loop points but of course, that doesn't matter for solving the question at hand... :) Thanks.
Last Edit: 2 years 3 months ago by Mao.
The administrator has disabled public write access.

Crash loading SFZ exported with discoDSP Bliss 2 years 3 months ago #4

  • ziyametedemircan
  • ziyametedemircan's Avatar
  • Offline
  • Elite Member
  • Posts: 175
  • Thank you received: 60
Audacity
The administrator has disabled public write access.

Crash loading SFZ exported with discoDSP Bliss 2 years 3 months ago #5

  • Mao
  • Mao's Avatar
  • Offline
  • New Member
  • Posts: 4
ziyametedemircan wrote:
Audacity
Appreciate you helping out on this... but I'm still not sure that's the problem.
Audacity is a 32 bit floating point application. Every file loaded into Audacity shows 32 bit in the info next to the track.
Is that what you are referring to? Because I see the same thing with the tracks you saved in Audacity and shared.
I really believe there is a minor meta or header information glitch that's causing the problem and Polyphone is a tad sensitive about it.
Not saying it's Polyphone's responsibility or fault... just saying that's what it looks like. I'm just trying to solve this... Thanks.
Last Edit: 2 years 3 months ago by Mao.
The administrator has disabled public write access.

Crash loading SFZ exported with discoDSP Bliss 2 years 3 months ago #6

  • bottrop
  • bottrop's Avatar
  • Offline
  • Elite Member
  • Posts: 201
  • Thank you received: 37
in Soundforge i see 16 and 24 bit files too, no 32 bit.

in Polyphone the SFZs are imported without any problem.
i still use Polyphone 1.9 though
drive.google.com/drive/folders/1AM7SCyJK...yOn2R8KL?usp=sharing

regards bottrop
The administrator has disabled public write access.

Crash loading SFZ exported with discoDSP Bliss 2 years 3 months ago #7

  • ziyametedemircan
  • ziyametedemircan's Avatar
  • Offline
  • Elite Member
  • Posts: 175
  • Thank you received: 60
I don't know. Perhaps Audacity is guessing wrong.
I opened both files (the original you added, and the one I saved after the bit change) from disk and it looks like this:



Also, the size of the saved ones is smaller than before.
This shows that a change has been made.
I don't know where the problem is, but the files I converted with Audacity can be opened in Polyphone 2.2.
Last Edit: 2 years 3 months ago by ziyametedemircan.
The administrator has disabled public write access.
  • Page:
  • 1
  • 2
Time to create page: 0.070 seconds