Windows 10 Issues & Unable to open WAV's

NCRS wrote on 1/3/2020, 11:24 AM

I work for a non-profit radio reading service. We have SF 13 on a PC running Windows 10. SF will periodically not play audio. I can see the wave form on the screen, but there is no audio coming out. A reboot of the machine will sometimes fix this problem. Any thoughts? Secondly, Our service runs a piece of broadcast automation software called Audio Vault Flex. It's primary audio format are WAV files. SF will not open any WAV files created in Audio Vault. I could play the file from Audio Vault recording it into SF. Unfortunately, this is not a preferred way of getting around this as we have programs running between 30 and 60 minutes. I'd appreciate any help on this matter also. I haven't been able to get any help from MAGIX because they say my copy is too old, and they won't allow me to buy a voucher. To reiterate, we're running SF Audio Studio 13, (Purchased & installed in September, 2019), on a Windows 10 PC. Thanks in advance for any help.

Comments

rraud wrote on 1/3/2020, 6:04 PM

Can you post one the files on Dropbox, GoogleDrive, OneDrive or elsewhere. I don't recall problems with PCM files, except for soundcard settings.. locked to an incompatible sample rate for instance. Are getting an error message?

You can contact Magix technical support online. You will need to log-in with your Magix account UN and PW.

There are several queries about phone support (or lack thereof). Sorry, I cannot help you there. I am not an employee of Magix.

NCRS wrote on 1/8/2020, 10:41 AM

Hi rraud. I'm sorry it's taken a while to respond. Today is the first day I've been back in the office. Thanks for the info. I've tried contacting tech support, but they tell me my service window is out of date and I need to purchase a voucher to get help. I have uploaded one of our promos to dropbox. Here's the link: https://www.dropbox.com/s/b68y27jk67etuut/NCRSBL.WAV?dl=0 . I really appreciate any help you can provide. I also have one of our engineers researching this problem as well. Thanks again.

johnebaker wrote on 1/8/2020, 11:37 AM

@NCRS

Hi

A MediaInfo analysis of the audio file shows Audio Vault is encoding MPEG 1 Layer 2 audio (MP2) within a WAV file - this 'unusual' combination is, AFAIK, not supported by SF.

For SF support the encoded audio must be in a mp2 container file or encoded as LPCM (the most common WAV format) for use in a WAV file format.

The LPCM encoding is preferred as it is a lossless format.

HTH

John EB

 

Last changed by johnebaker on 1/8/2020, 11:37 AM, changed a total of 1 times.

VPX 16, Movie Studio 2025, and earlier versions 2015 and 2016, Music Maker Premium 2024.

PC - running Windows 11 23H2 Professional on Intel i7-8700K 3.2 GHz, 16GB RAM, RTX 2060 6GB 192-bit GDDR6, 1 x 1Tb Sabrent NVME SSD (OS and programs), 2 x 4TB (Data) internal HDD + 1TB internal SSD (Work disc), + 6 ext backup HDDs.

Laptop - Lenovo Legion 5i Phantom - running Windows 11 23H2 on Intel Core i7-10750H, 16GB DDR4-SDRAM, 512GB SSD, 43.9 cm screen Full HD 1920 x 1080, Intel UHD 630 iGPU and NVIDIA GeForce RTX 2060 (6GB GDDR6)

Sony FDR-AX53e Video camera, DJI Osmo Action 3 and Sony HDR-AS30V Sports cams.

NCRS wrote on 1/8/2020, 12:05 PM

Thank you for the info. I am going to forward this on to our tech committee, and see if they have any suggestions. Otherwise, it sounds like we may have to go back to Cool Edit. Thanks again. CS.

rraud wrote on 1/8/2020, 5:02 PM

As @johnebaker stated, it is not a PCM WAVE file. It is a compressed (lossy) format with a <.wav> extension. Apparently SF (and Vegas) does not have this codec, so you may very well have to go back to Cool Edit (Adobe renamed it "Audition" after the acquisition of Syntrillium in 2003).

NCRS wrote on 1/9/2020, 10:22 AM

Thanks. I had just about come to that conclusion as well. I'm glad we didn't purchase the SFPro. We are a non-profit so our budget is pretty small. Our older Cool Edit Pro still hanging in there. The longer we can go without purchasing the Audition annual subscription, the better. I do want to send a big thank you to everyone who participated on this issue. Thank you.