Cutting off end of tracks - Sound Forge Pro v11 Windows PC

jeffrey-sward wrote on 10/23/2017, 7:37 PM

Sound forge pro v11 Windows PC is cutting off a small amount of time, including the sound, from the end of tracks whenever an edit operation is executed (graphic dynamics, normalize).  The amount of time is usually less than one second.  On open, the full track is present both graphically and playable.  After the edit operation, music is truncated, and a silence appears both graphically and through playback. Many classical tracks run the sound to the very end of the track with no silence.  Editing these music-to-the-end classical tracks is untenable, making the tool useless for this purpose. 

A similar problem was logged in the archive http://forum-archive.magix.info/showmessage.asp?messageid=840079 for previous versions. 

Since this problem persists for several versions, the conclusion is that fixing this issue has insufficient priority. 

 

Comments

emmrecs wrote on 10/24/2017, 4:10 AM

Hi, welcome to the Magix forums.

I wonder whether this thread might offer a clue as to why you are experiencing this? I realise removing the metadata from the edited file is nothing more than a clumsy workaround and a real solution is needed but I would be interested to know if it works for you.

Jeff

Win 11 Pro 64 bit, Intel i7 14700, 16 GB RAM, NVidia RTX 4060 and Intel UHD770 Graphics, MOTU 8-Pre f/w audio interface, VPX, MEP, Music Maker, PhotoStory Deluxe, Photo Manager Deluxe, Xara 3D Maker 7, Samplitude Pro X7 Suite, Reaper, Adobe Audition 3, CS6 and CC, 2 x Canon HG10 cameras, 1 x Canon EOS 600D, Akaso EK7000 Pro Action Cam

rraud wrote on 10/24/2017, 3:54 PM

Check your snapping settings in Options. As well as setting the fade type to a linear X fade in the FX 'more' window.

jeffrey-sward wrote on 10/29/2017, 8:37 PM

Thanks for both suggestions.  Unfortunately, neither worked.   Details:

Audio Studio and Sound Forge Pro are significantly different applications.  There is no meta data folder or files in My Documents\ including sub folders nor under C:\Users\xxxx\AppData\Local\MAGIX\Sound Forge Audio Studio\10.0\ nor under C:\Users\jxxxx\AppData\Local\MAGIX\Sound Forge Audio Studio\11.0\, or other obvious locations. 

Changed the default fade (snapping) from 0.10 seconds to 0.00 seconds in the master options and under the "more" window in all of the associated individual tools.  The fade type was already "X" in all locations.  No change.  Still truncating the actual music. 

The amount of music removed is 0.461 seconds. 

 

emmrecs wrote on 10/30/2017, 4:27 AM

Hi. Thanks for the update.

Since the file must contain metadata, in the case of your files it is clearly contained within each file, rather than being stored separately. So, does SFPro 11 allow you to access and read that data when the file is open?

I don't have SF but the (non-Magix) audio editor I do use gives me access to all the metadata stored within it and I can read that data. I can do this via its XMP>File Properties>Duration setting. Does SF offer anything similar? Is the total playback time for the file correct or is it your 0.461 seconds shorter than it should be?

If the data is incorrectly stored you need to raise this as a definite bug with Magix. OTOH (and I have NO experience of how well this may or may not work, you do this at your own risk) I see there are various programs, many free, that claim to be able to allow you to edit metadata.

HTH

Jeff

Win 11 Pro 64 bit, Intel i7 14700, 16 GB RAM, NVidia RTX 4060 and Intel UHD770 Graphics, MOTU 8-Pre f/w audio interface, VPX, MEP, Music Maker, PhotoStory Deluxe, Photo Manager Deluxe, Xara 3D Maker 7, Samplitude Pro X7 Suite, Reaper, Adobe Audition 3, CS6 and CC, 2 x Canon HG10 cameras, 1 x Canon EOS 600D, Akaso EK7000 Pro Action Cam

johnebaker wrote on 10/30/2017, 5:43 AM

Hi

Like Jeff I do not use Sound Forge, however I have seen similar issues which were caused by the audio source file having a variable bitrate instead of a constant bitrate.

You can use MediaInfo to analyse the source audio to see if it is variable or constant bitrate.

HTH

John EB

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.

rraud wrote on 10/30/2017, 10:04 AM

Like Jeff I do not use Sound Forge, however I have seen similar issues which were caused by the audio source file having a variable bitrate instead of a constant bitrate.

You can use MediaInfo to analyse the source audio to see if it is variable or constant bitrate.

HTH

John EB

If this is the case (and it may be) SF Pro 11 has the option to build PCM proxy files for lossy formats. "Options> Preferences> General> Always proxy compressed formats"

jeffrey-sward wrote on 11/5/2017, 6:19 PM

Thanks for the additional suggestions. 

Additional information:

The total time of the track does not vary.  Before an operation is performed the last 0.461 seconds of the track contains sound.  Alter an operation is performed, the last 0.461 seconds contains silence, with the total track time the same and the sound before the last 0.461 seconds remaining. 

This is a definite bug.  Unable to find any method for reporting bugs, only found this forum site.  Suspect Sound Forge Pro 11 is an orphaned product which is not actively supported considering the history of company buy-outs.  If someone knows how to report a bug, I will be happy to report one. 

I use Tag and Rename as my meta data tag editor.  This is licensed software.  This is a versatile meta data tag editor which operates on individual files or groups of file.  I have used this product for years with no issues, on over 16,000 tracks.

I use flac and mp3 file formats only.  Generally I covert from an oem flac download or cd rip flac to mp3 after compression.  Both flac and mp3 contain header areas which store meta data tags.  I generally change the meta data tags to values which correspond to my own classification scheme.  The meta data tags are used by my android device player to select specific groups of tracks. 

All downloaded and ripped flac files contain oem meta data tags.  Sound Forge pro 11 truncates the end of tracks regardless of whether the original oem meta data tags or my edited meta data tags are present.  Completely removing the meta data tags is impractical as the tags would have to be manually entered twice after conversion, once on the flac files and once on the mp3 files. 

Flac is a lossless compressed file.  Unlike mp3 files, the concept of bit rate does not apply to flac.  The standard (CD quality) sampling rate for flac is 44100 hz, which is not a bit rate.  Flac will compress sections of each track as possible, while keeping the audio lossless. 

When I check the box "always proxy compressed formats" flac files will not open at all, generating the message "an error occurred while creating a proxy file for a stream.  The application does not support this file type."  Flac files open with the "always proxy compressed formats" box unchecked. 

 

noisywan wrote on 10/26/2018, 6:53 AM

Hi there!

I have managed to recreate this bug on SoundForge 11 with simple steps, even without using any external audio file.

Here are the steps I followed;

1) Created a new file  (44.1k mono 16bit)
2) Created audio content using `Insert / Synthesis / FM / Out There (preset) ` 
3) Saved it as FLAC (default template) and closed the file.
4) Opened it
5) used `Process / Volume` and reduced volume by -1 dB 

Result:

File content gets deleted and you can't undo it because undo function doesn't take back the faulty process.

In step 2, if you set duration to 8 secs, you can see truncation at the end of file as reported in OP.
 

OS: Win 7 Pro SP1 64bit
SF Pro 11 b.299

rraud wrote on 10/26/2018, 10:14 AM

I cannot recreate this behavior with SF Pro-10 or 12 (WIn 10 PC). I'll try this with SFP-11 when I can. (on a PC at a different location)..

qwerty95 wrote on 2/10/2019, 10:33 AM

I've had the same problem and I've figured out, that if I delete all ID3 tags from the mp3 file BEFORE I open it in Sound Forge, the end of the track is OK and the track can be edited without loosing its end.