That ol' devil "undefined soundfont file" error

  • Thread starter Thread starter AlChuck
  • Start date Start date
AlChuck

AlChuck

Well-known member
Hey all,

Sorry to be asking this hoary old question again, but since I installed SONAR I've been experiencing the "undefined soundfont error" message when I
try to attach any of my sound fonts. I did a search of this site, the SONAR and Cakewalk Pro Audio news server, and of a couple of other web sites, to no avail.

When I first got it they were in the directory that I had used with Cakewalk Pro Audio. So I moved them where the sample ones had been put with SONAR. Then I could attach them... for a while. A few days later I went to do this again and got that message again.

Any clues?

Thanks,

AlChuck
 
This may not help, but after I got sonar I needed to reinstall it. Afterwards, even though I had the shared dxi/plugs etc in the default file, sonar couldn't open them or they showed up as audio plug ins. I understand that sometimes sonar can't seem to find plug ins (or maybe the plug in files) even when not reinstalled. There is a small program for that on the cake website. Don't know if that will help.... I had to do a total reinstall (after cleaning out registry etc. then change some of my monitor functions to get it to work correctly). Supposedly, a lot of this will be fixed in a new patch (a different one than the sonar patch already out).
 
Somebody on the SONAR newsgroup suggested I put them in a less "deep" directory -- apparently the Sound Font Manager has some trouble with pathnames above 60 characters. With my sound fonts somewhere in C:program filescakewalkSONAR 1sample contentsoundfonts, the pathname was just over 60. I moved them to just C:soundfonts. I was able to open them normally after that. We'll see if it sticks.
 
Sounds just like an old DOS holdover from the old days. HEHEHEHE. Nothing longer than 63 characters. How typical that the old dos conventions should still byte us! (pun intended)

Well, I must say that I am not surprised in the least that a path string length issue has reared it's uggly head here. Some things never change do they Mr. Gates?

Best advice to everyone, keep your directory names short and sweet. Defaults suck! Take control of your system and don't let windows tell you what is going to happen. I've said it before and I'll say it again, windows is not that smart!

AlChuck, dude, good to see you man. SD is OK. Take care in CA.
 
Sounds just like an old DOS holdover from the old days. HEHEHEHE. Nothing longer than 63 characters. How typical that the old dos conventions should still byte us! (pun intended)

Well, I must say that I am not surprised in the least that a path string length issue has reared it's uggly head here. Some things never change do they Mr. Gates?

Best advice to everyone, keep your directory names short and sweet. Defaults suck! Take control of your system and don't let windows tell you what is going to happen. I've said it before and I'll say it again, windows is not that smart!

AlChuck, dude, good to see you man. SD is OK. Take care in CA.
 
You must log in or register to reply here.
Back
Top