Vu meter on fx mixer in the red, bad ?

[Gps]

also, find out which part of the spectrum contribute most to the clipping. You can then try to use a EQ and precisely aiming to lower those part of the spectrum.
For that i can recommend blue-cat-spectrum-analyzer BUT
You may newer!!! leave it in your project, because it will freeze the project at re-open (as does ALL blue-cat plug-ins // a las)
It is however an awesome plug-in, with a load of super nice presets for sound visualization.

I did not hear any clipping in my song, that's were my confusion started. ( and I think I have a good ear for clipping)

I have made progress though. Master channel does not go into the red anymore.
The choir track does, but when I listen to that on its own, its sounds fine.

Learning again a lot from this track, and I will look for spectrum analyzing tools.

[musikbear]

well its called overdrive in danish too => overstyring
Same word is used for bad car handling and bad audio-recording, but we are a poor country, so we could properly not afford a special word for both situations..

[StakeoutPunch]

When I use the site TecDic it gives me, three options.
Overdrive, overload and ship.

well its called overdrive in danish too => overstyring
Same word is used for bad car handling and bad audio-recording, but we are a poor country, so we could properly not afford a special word for both situations..

That's interesting, so you are saying that the same word translates to both overdrive and oversteer? In English they mean different things, hence my initial confusion.

For that i can recommend blue-cat-spectrum-analyzer

I personally prefer Voxengo SPAN and it doesn't crash on loading the project.

I did not hear any clipping in my song, that's were my confusion started. ( and I think I have a good ear for clipping)

I have made progress though. Master channel does not go into the red anymore.
The choir track does, but when I listen to that on its own, its sounds fine.)

This is why a lot of confusion about clipping occurs, inside the program only the loudest overdriving will cause clipping. However, in the render it normally would show up. Its something about how LMMS internally handles sound.

[Gps]

well its called overdrive in danish too => overstyring
Same word is used for bad car handling and bad audio-recording, but we are a poor country, so we could properly not afford a special word for both situations..

LOL

Dutch and Danish have a lot in common. I had on msn a friend from Denmark.
If we did not know the English word for something, we just used the Dutch or the Danish word, which worked most of the time.

In Dutch overstyring = oversturen. which like in danish, is used for bad car handling, and bad audio recording.

[Gps]

I did not hear any clipping in my song, that's were my confusion started. ( and I think I have a good ear for clipping)

I have made progress though. Master channel does not go into the red anymore.
The choir track does, but when I listen to that on its own, its sounds fine.)

This is why a lot of confusion about clipping occurs, inside the program only the loudest overdriving will cause clipping. However, in the render it normally would show up. Its something about how LMMS internally handles sound.

I had already noticed that bass (drum) sounds are more likely to cause clipping, then high pitched sounds.
No idea if this has to do with our ears or how LMMS handles sound.
Its not different from using the bass knob on an amplifier though, or the equalizer of programs like winamp.

I also noticed it does makes a difference, although small, if I put a plugin directly on the instrument, or through the FX mixer.
At least for this track, putting the bass booster on the master channel sounds better, then putting the bassbooster on every instrument in the beat and bassline editor.

[Gps]

Now I am gonna search for Voxengo SPAN and blue-cat-spectrum-analyzer.
lets see if these work on Linux.

Edit:
I found both, but I also have a problem, they are not .dll files but .exe files.

I will report back if I got it working on linux.

I did find something interesting for linux, on their site.

For VST, VST3 plug-ins on Windows platform:
You should execute the downloaded setup file, select plug-in types you would like to install, and for VST plug-ins specify the VstPlugins folder location, the one which is connected with the audio application you are using and where this application expects VST plug-ins to reside (the "Voxengo" sub-folder will be also created there). VST3 plug-ins are always installed into the standard "Common Files/VST3" folder.

(the installed Voxengo plug-in DLL files can be moved around freely)

[Gps]

I got Voxengo working in lmms.

For other Linux users, no garantees, but run the exe file with wine. Find the dll file, and insert this into lmms through vestige.

Edit:
I am afraid it wont work, I can load it in lmms, but I am not seeing any graph.

[Gps]

I got Voxengo working in lmms.

For other Linux users, no garantees, but run the exe file with wine. Find the dll file, and insert this into lmms through vestige.

Edit:
I am afraid it wont work, I can load it in lmms, but I am not seeing any graph.

Edit2:

it seems I can load both programs into lmms, but there is no graph.

I have at the moment, no idea, if they just wont work on Linux, or that I have to change some settings.

[StakeoutPunch]

I had already noticed that bass (drum) sounds are more likely to cause clipping, then high pitched sounds.
No idea if this has to do with our ears or how LMMS handles sound.
Its not different from using the bass knob on an amplifier though, or the equalizer of programs like winamp.

I also noticed it does makes a difference, although small, if I put a plugin directly on the instrument, or through the FX mixer.
At least for this track, putting the bass booster on the master channel sounds better, then putting the bassbooster on every instrument in the beat and bassline editor.

It's actually the physics of sound waves. Lower frequencies are lower energy waves, and on top of that the frequency spectrum isn't linear. That means that if you were to try and play a low frequency sound and a higher frequency sound at the same "volume", the low frequency noise would sound quieter to you. In other words, to perceive bass tones at the same volume, you have to increase their energy. This is why spectrum analyzers may tell you that two sounds are the same dB, but they don't sound such. Obviously as a result, we crank the bass up to hear it, and if handled wrong the program complains in the form of clipping.

I wouldn't recommend boosting the bass on the master. Actually, I don't recommend boosting anything - cutting frequencies and raising the gain accordingly typically offers cleaner results (sloppy boosting/done wrong/etc can result in distortion, while cutting frequencies is non destructive).

I did find something interesting for linux, on their site.

For VST, VST3 plug-ins on Windows platform:
You should execute the downloaded setup file, select plug-in types you would like to install, and for VST plug-ins specify the VstPlugins folder location, the one which is connected with the audio application you are using and where this application expects VST plug-ins to reside (the "Voxengo" sub-folder will be also created there). VST3 plug-ins are always installed into the standard "Common Files/VST3" folder.

(the installed Voxengo plug-in DLL files can be moved around freely)

I can't help you much there, but I would suggest looking for the VST2 version of the Voxengo VST. VST3 is not supported by LMMS, if I recall correctly.

[caLRo]

I wouldn't recommend boosting the bass on the master. Actually, I don't recommend boosting anything - cutting frequencies and raising the gain accordingly typically offers cleaner results (sloppy boosting/done wrong/etc can result in distortion, while cutting frequencies is non destructive).

Definitely good advice. I used to boost stuff too often and too much, nowadays I'm trying to do what you recommended instead.