"Import for file type 101 is not possible" errors

dave-b3271 wrote on 8/9/2024, 9:35 AM

I've just installed the new version of Audio Cleaning Lab, after being familiar with an old version for years.
This version seems mostly the same (which is what I hoped), but I'm getting some errors.

One feature I use a lot is the DeNoiser, but now if I click the "Pick" button it seems to do nothing, and when I press the playback button to check, it throws up a warning "Import for file type 101 is not possible!"

I also tried to use the "remove hum" function, which I use a LOT due to a strange problem I have where one of my mics always has 50hz hum and I have to remove it in Audio Cleaning Lab every time, but again I got the file type 101 message but this time it froze the app completely so I couldn't dismiss it.

I tried another way of doing a similar thing (and sadly I can't remember what that was now so I can't replicate it!) but that time the error message was "Error while writing noise sample file".

I'm starting to get really worried! Is there a way of getting this app to work properly again?

Comments

SP. wrote on 8/9/2024, 12:00 PM

@dave-b3271 Yeah, this is a problem in the 64 Bit version of SFACL 4, but to my experience this is only a visual problem. The software tries to create the waveform for the noise profile and then this error comes up. But usually, I can ignore it by simply closing the error message or by disabling the DeNoiser effect, then clicking on the Pick button and then enabling the DeNoiser effect again.

Alternatively, you can use the 32 Bit version of SFACL 4. The error will not appear there.

dave-b3271 wrote on 8/30/2024, 11:53 AM

Alternatively, you can use the 32 Bit version of SFACL 4. The error will not appear there.

It's nearly time for my trial to run out and for me to buy the software, which I'm basically happy to do - I just want to check this isn't going to be a huge problem going forward.

I've tried to install the 32-bit version, and whenever I try to run it I just get an error message:
"The program could not be started. It's possible that the installation folder is damaged.

Reinstalling the program could remedy the problem.
If the error occurs again, please contact support.

Error code: -1"

I've reinstalled it, and that hasn't changed it. Anyone have experience with this? It's starting to feel like they've put barriers up to stop me using this software whichever way I try, but I've been using it for so long now and not found anything else that does the specific one or two things I want to do with it, so I can't just give up!

SP. wrote on 8/30/2024, 12:01 PM

@dave-b3271 Maybe your Antivirus or Firewall blocks it?

dave-b3271 wrote on 8/30/2024, 12:20 PM

@dave-b3271 Maybe your Antivirus or Firewall blocks it?

If so, I don't know enough to find out or stop it. Any tips?

Edit: I said that after twenty minutes trying everything I could think of, I didn't just give up straight away :)

SP. wrote on 8/30/2024, 1:39 PM

@dave-b3271 The easiest way might be, to simply right click on the program icon and then select to run the program as administrator.

Regarding the Firewall/Antivirus, I don't know what you use. I don't have anything special, only Windows Defender, which I can simply disable temporarily via the Windows settings.

dave-b3271 wrote on 8/30/2024, 3:42 PM

@dave-b3271 The easiest way might be, to simply right click on the program icon and then select to run the program as administrator.

Regarding the Firewall/Antivirus, I don't know what you use. I don't have anything special, only Windows Defender, which I can simply disable temporarily via the Windows settings.

Same. Alas, neither of those things worked. Thanks though, definitely worth a shot.

Clifford-Bowman wrote on 1/27/2025, 10:32 AM

Trying to get to grips with Audio Cleaning Lab 4 coming from CoolEdit Pro 2.1 (yes, THAT old) I am coming across the same problems as the OP.

FWIW I get the "Error while writing noise sample file" when trying to change the "Noise Sample" using the demo file "Demo_Denoiser.VIP". It defaults to "50 Hz bright 1" but that error leaps up if I try changing to, say, "50 Hz bright 2". Or, in fact, any of the default samples I have just tried :(

PC: Alienware Aurora R7
CPU: i7-800K @ 3.70GHz
RAM: 32 GB
OS: Video Pro X12 installed on Windows 10 Pro, 22H2, on Samsung SSD 980 (800+GB partition)
OS: Also available, Windows 11, on Samsung SM961 NVMe  SSD (240+ GB partition)
OS : For gaming, Windows 10 on an OCS-AGILITY3 SATA SSD (450GB partition)
Shared Data Storage: Local storage is on a Samsung SSD 870 EVO (3.5TB partition)
Partition sizes approximate.
Display adapters : Intel UHD Graphics on M/B, basically unused
Twin NVIDIA GeForce GTX 1080 Ti (11GB RAM each, SLI linked for "Maximum 3D performance") ). Drivers up-to-date using GeForce Experience. No change except slowing down and more crashes from disabling SLI
Video ProX12 video modes:
Preview in arranger:
Standard mode (Direct3D, hardware acceleration) - NVIDIA GeForce GTX 1080 Ti (changing this to Intel UHD causes majopr crashes)
or
Compatability mode (VideoForWindows))
Preview and playback on analog recording:
Standard Renderer
or
Alternate mode 2 (Video Mixing Renderer9)
Screen: 256 x 1080 @ 60Hz, RGB, SDR (LG)

 

 

SP. wrote on 1/27/2025, 1:27 PM

@Clifford-Bowman You can find the unsatisfying answer in my first comment.

browj2 wrote on 1/27/2025, 1:59 PM

@Clifford-Bowman

Hi,

By all means, please raise a ticket with Magix.

Over 2000 views showing some of the bugs and still Magix does nothing:

The 101 error is still annoying.

John CB

John C.B.

VideoPro X(16); Movie Studio 2025 Platinum; Music Maker 2025 Premium Edition; Samplitude Pro X8 Suite; see About me for more.

Desktop System - Windows 10 Pro 22H2; MB ROG STRIX B560-A Gaming WiFi; Graphics Card Zotac Gaming NVIDIA GeForce RTX-3060, PS; Power supply EVGA 750W; Intel Core i7-10700K @ 3.80GHz (UHD Graphics 630); RAM 32 GB; OS on Kingston SSD 1TB; secondary WD 2TB; others 1.5TB, 3TB, 500GB, 4TB, 5TB, 6TB, 8TB; three monitors - HP 25" main, LG 4K 27" second, HP 27" third; Casio WK-225 piano keyboard; M-Audio M-Track USB mixer.

Notebook - Microsoft Surface Pro 4, i5-6300U, 8 GB RAM, 256 SSD, W10 Pro 20H2.

YouTube Channel: @JCBrownVideos

Clifford-Bowman wrote on 1/27/2025, 2:50 PM

@Clifford-Bowman You can find the unsatisfying answer in my first comment.

Thanks. I'm a little deflated that they seem to care so little. I guess I'm going to have to take a look fir the 32 bit version.

PC: Alienware Aurora R7
CPU: i7-800K @ 3.70GHz
RAM: 32 GB
OS: Video Pro X12 installed on Windows 10 Pro, 22H2, on Samsung SSD 980 (800+GB partition)
OS: Also available, Windows 11, on Samsung SM961 NVMe  SSD (240+ GB partition)
OS : For gaming, Windows 10 on an OCS-AGILITY3 SATA SSD (450GB partition)
Shared Data Storage: Local storage is on a Samsung SSD 870 EVO (3.5TB partition)
Partition sizes approximate.
Display adapters : Intel UHD Graphics on M/B, basically unused
Twin NVIDIA GeForce GTX 1080 Ti (11GB RAM each, SLI linked for "Maximum 3D performance") ). Drivers up-to-date using GeForce Experience. No change except slowing down and more crashes from disabling SLI
Video ProX12 video modes:
Preview in arranger:
Standard mode (Direct3D, hardware acceleration) - NVIDIA GeForce GTX 1080 Ti (changing this to Intel UHD causes majopr crashes)
or
Compatability mode (VideoForWindows))
Preview and playback on analog recording:
Standard Renderer
or
Alternate mode 2 (Video Mixing Renderer9)
Screen: 256 x 1080 @ 60Hz, RGB, SDR (LG)

 

 

Clifford-Bowman wrote on 1/27/2025, 2:53 PM

@Clifford-Bowman

Hi,

By all means, please raise a ticket with Magix.

Over 2000 views showing some of the bugs and still Magix does nothing:

The 101 error is still annoying.

John CB

Thanks John. I rather like your video - it reminds me of the kind of reports I tend to make in the hopes of at least official response, and ideally a fix (note that I am aware that "a fix" is superior to "a resolution"). That they are not actively engaging suggests I should be seeking a refund :(

 

Cliff

PC: Alienware Aurora R7
CPU: i7-800K @ 3.70GHz
RAM: 32 GB
OS: Video Pro X12 installed on Windows 10 Pro, 22H2, on Samsung SSD 980 (800+GB partition)
OS: Also available, Windows 11, on Samsung SM961 NVMe  SSD (240+ GB partition)
OS : For gaming, Windows 10 on an OCS-AGILITY3 SATA SSD (450GB partition)
Shared Data Storage: Local storage is on a Samsung SSD 870 EVO (3.5TB partition)
Partition sizes approximate.
Display adapters : Intel UHD Graphics on M/B, basically unused
Twin NVIDIA GeForce GTX 1080 Ti (11GB RAM each, SLI linked for "Maximum 3D performance") ). Drivers up-to-date using GeForce Experience. No change except slowing down and more crashes from disabling SLI
Video ProX12 video modes:
Preview in arranger:
Standard mode (Direct3D, hardware acceleration) - NVIDIA GeForce GTX 1080 Ti (changing this to Intel UHD causes majopr crashes)
or
Compatability mode (VideoForWindows))
Preview and playback on analog recording:
Standard Renderer
or
Alternate mode 2 (Video Mixing Renderer9)
Screen: 256 x 1080 @ 60Hz, RGB, SDR (LG)

 

 

Clifford-Bowman wrote on 1/27/2025, 4:17 PM

@dave-b3271 

Alternatively, you can use the 32 Bit version of SFACL 4. The error will not appear there.

Alas, while this may be true it's hard to find when, on running the program, I get the error:

 

The program could not be started. It's possible that the installation folder is damaged.

Reinstalling the program could remedy the problem.

If the error occurs again, please contact support.

 

Error code: -1

 

I'm starting to lose my patience with this program :(

 

Cheers,

 

Cliff

PC: Alienware Aurora R7
CPU: i7-800K @ 3.70GHz
RAM: 32 GB
OS: Video Pro X12 installed on Windows 10 Pro, 22H2, on Samsung SSD 980 (800+GB partition)
OS: Also available, Windows 11, on Samsung SM961 NVMe  SSD (240+ GB partition)
OS : For gaming, Windows 10 on an OCS-AGILITY3 SATA SSD (450GB partition)
Shared Data Storage: Local storage is on a Samsung SSD 870 EVO (3.5TB partition)
Partition sizes approximate.
Display adapters : Intel UHD Graphics on M/B, basically unused
Twin NVIDIA GeForce GTX 1080 Ti (11GB RAM each, SLI linked for "Maximum 3D performance") ). Drivers up-to-date using GeForce Experience. No change except slowing down and more crashes from disabling SLI
Video ProX12 video modes:
Preview in arranger:
Standard mode (Direct3D, hardware acceleration) - NVIDIA GeForce GTX 1080 Ti (changing this to Intel UHD causes majopr crashes)
or
Compatability mode (VideoForWindows))
Preview and playback on analog recording:
Standard Renderer
or
Alternate mode 2 (Video Mixing Renderer9)
Screen: 256 x 1080 @ 60Hz, RGB, SDR (LG)

 

 

SP. wrote on 1/27/2025, 4:19 PM

@Clifford-Bowman Do you use antivirus or firewall software or only Windows Defender?

Clifford-Bowman wrote on 1/27/2025, 4:49 PM

Alas, 'tis true - I am the Norton user :(

PC: Alienware Aurora R7
CPU: i7-800K @ 3.70GHz
RAM: 32 GB
OS: Video Pro X12 installed on Windows 10 Pro, 22H2, on Samsung SSD 980 (800+GB partition)
OS: Also available, Windows 11, on Samsung SM961 NVMe  SSD (240+ GB partition)
OS : For gaming, Windows 10 on an OCS-AGILITY3 SATA SSD (450GB partition)
Shared Data Storage: Local storage is on a Samsung SSD 870 EVO (3.5TB partition)
Partition sizes approximate.
Display adapters : Intel UHD Graphics on M/B, basically unused
Twin NVIDIA GeForce GTX 1080 Ti (11GB RAM each, SLI linked for "Maximum 3D performance") ). Drivers up-to-date using GeForce Experience. No change except slowing down and more crashes from disabling SLI
Video ProX12 video modes:
Preview in arranger:
Standard mode (Direct3D, hardware acceleration) - NVIDIA GeForce GTX 1080 Ti (changing this to Intel UHD causes majopr crashes)
or
Compatability mode (VideoForWindows))
Preview and playback on analog recording:
Standard Renderer
or
Alternate mode 2 (Video Mixing Renderer9)
Screen: 256 x 1080 @ 60Hz, RGB, SDR (LG)