Author Topic: Problem running Soundshaper on Windows 11  (Read 1286 times)

ratoci

  • Newbie
  • *
  • Posts: 3
    • View Profile
Problem running Soundshaper on Windows 11
« on: April 22, 2024, 11:59:43 AM »
Hello, thanks for keeping the community alive.
I'm teaching CDP as part of my Electroacoustic Composition course in Mantova Conservatory (Italy). Actually Soundshaper works very fine on WINESKIN port for MAC but I have problem with a student with a Windows PC.
After installation, which goes without any problem, running any Soundshaper command brings out a glitched interface with many incoherent sliders with strange parameter names (DLbl1, etc.) and the error "SCROLLBAR PROPERTY OUT OF RANGE".
Also on subsequent re-opening of Soundshaper I get "-----SOUNDSHAPER SETUP PROBLEM...." with missing folders like when CDPR folder is unaccessible (but I swear, it's there, unmoved)

Robert Fraser

  • Sr. Member
  • ****
  • Posts: 94
    • View Profile
Re: Problem running Soundshaper on Windows 11
« Reply #1 on: May 03, 2024, 03:52:29 PM »
Thanks for your bug report. The parameter pages are clearly not loading for some reason. Not sure at this stage whether this is genuinely a Windows 11 problem or not. I'll test the program on Win11 and report back.

Robert Fraser

  • Sr. Member
  • ****
  • Posts: 94
    • View Profile
Re: Problem running Soundshaper on Windows 11
« Reply #2 on: May 03, 2024, 05:19:48 PM »
I've done a fresh installation on my wife's Windows 11 laptop. So far, everything seems to run as it should (except for F keys which are presumably set to Windows things).  I did have to get past Windows and the security software not wanting me to run the installation program, but hacked round this.

So far I've tested with modify speed, followed by repitch transpose (to test spectral auto-conversion).

Because of the vast number of CDP processes, Soundshaper reads parameter data from a text file CmdData.txt which must reside in its \BAT sub-folder. Any issue with reading the appropriate setup data from this file will give strange results and messages as you report. So that's the problem - the file is easily replaced if corrupted somehow...  Can your user test first if the file is there, in the correct place?  Have they installed Soundshaper/CDP from fresh or just copied files from someone, which might mean the setup is not right?

It may be necessary to correspond directly to get to the bottom of the issue. Your student is welcome to send me emails in Italian and I can use Google Translate to understand and reply. Email is found here: http://www.ensemble-software.net/links.html

Robert F.

Robert Fraser

  • Sr. Member
  • ****
  • Posts: 94
    • View Profile
Re: Problem running Soundshaper on Windows 11
« Reply #3 on: May 04, 2024, 05:49:28 PM »
"Soundshaper works very fine on WINESKIN port for MAC"
This could be very important for MAC users - I looked up Wineskin, but found different versions and I'm not sure which to download. Any help you can give on this, and how to use etc., would be hugely appreciated. 

Robert Fraser

  • Sr. Member
  • ****
  • Posts: 94
    • View Profile
Re: Problem running Soundshaper on Windows 11
« Reply #4 on: May 06, 2024, 05:20:20 PM »
When you mentioned the "SETUP PROBLEM" message, it's a pity you didn't list the apparently missing folders. The message means that the value (folder-name) assigned to each of these listed folders is invalid - the folder does not exist.  Several of them are read in from the textfile Soundshaper.cfg - I'm wondering if your student copied an old Soundshaper.cfg file from somewhere and the program is looking for the wrong folders? (It's impossible to tell without the list of missing directories.)  However the one that could be faulty here is actually a fixed one: namely Soundshaper's \BAT sub-folder. If that were wrong for any reason, Soundshaper couldn't read the CmdData file and therefore the parameter pages would show junk instead of proper labels or ranges, exactly as you report.

ratoci

  • Newbie
  • *
  • Posts: 3
    • View Profile
Re: Problem running Soundshaper on Windows 11
« Reply #5 on: Today at 03:55:17 PM »
"Soundshaper works very fine on WINESKIN port for MAC"
This could be very important for MAC users - I looked up Wineskin, but found different versions and I'm not sure which to download. Any help you can give on this, and how to use etc., would be hugely appreciated.

Dear Robert! I'm actually very happy too being able to port Soundshaper 6 to MacOs (ARM Based!!!) using Wineskin! I still think it's non optimal compared to a native Mac version because, given the concept and structure of wineskin bottle I still can't figure out how to connect a browser or pdf reader to open help directly from Soundshaper.
Anyway here the build I did on my ARM M2 Mac : (In another machine I have builds for Mac Intel, if you need I can send)

https://ln5.sync.com/dl/696565420/c7k9sk2b-94x6e6v6-iimcqf3z-9dgh85xg

I'm using this version of Wineskin:

https://github.com/Gcenx/WineskinServer
that I install via Homebrew

Let me know If I can give further assistance,
Alessandro

ratoci

  • Newbie
  • *
  • Posts: 3
    • View Profile
Re: Problem running Soundshaper on Windows 11
« Reply #6 on: Today at 03:59:44 PM »
Dear Robert,
I was not able to send a screenshot with detailed error message cause apparently the image embedding on the forum did not work, I'm sending you a mail.
Thanks again,
Alessandro

When you mentioned the "SETUP PROBLEM" message, it's a pity you didn't list the apparently missing folders. The message means that the value (folder-name) assigned to each of these listed folders is invalid - the folder does not exist.  Several of them are read in from the textfile Soundshaper.cfg - I'm wondering if your student copied an old Soundshaper.cfg file from somewhere and the program is looking for the wrong folders? (It's impossible to tell without the list of missing directories.)  However the one that could be faulty here is actually a fixed one: namely Soundshaper's \BAT sub-folder. If that were wrong for any reason, Soundshaper couldn't read the CmdData file and therefore the parameter pages would show junk instead of proper labels or ranges, exactly as you report.