LMMS • Forums

Hey guys, I'm trying to export my lmms piece and am having a several issues.
1. Everything I export is higher than it should be (musically). For some reason all the tracks have all been transposed.
2. All the tracks have some silence on the end.

I have tried exporting with and without using "Enable Loop points" to trim off the silence at the end. Sadly it didn't work.

I'm exporting individual tracks so I select "Export tracks..." and export with these settings
File format: wav-file
Sample Rate: 48000 Hz
Bitrate: 320 KBit/s
Depth: 32 Bit Float
I left interpolation and Oversampling at default
"Export as loop" is checked

I have a suspicion that it may be an issue with the VST that I am using. I've had problems while writing my piece with the VST only playing music in the left channel. Problem is I can't find a decent VST to replace it, and that might solve my problems. I'm using Cellofan and would like to use a cello vst, or perhaps violin if none can be found.

Oh, also I'm using lmms 0.4.15 on a windows 7 (64-bit) laptop, if that helps.

Ok I tried exporting with all default settings. That fixed the transposing issue, (any ideas about what caused that? I want to export with better quality) but I still have the issue of silence at the end of each track. I really want to have to avoid trimming these manually in audacity since I want to preserve the timing perfectly for some looping fun.

seeshi wrote:Ok I tried exporting with all default settings. That fixed the transposing issue, (any ideas about what caused that? I want to export with better quality)

Are you using VSTi's by any chance?

I've noticed that some VSTi's (not all) only produce 44.1 kHz sound, no matter what rate you render in. This doesn't happen with all VSTi's and never on native instruments. I don't know if it's a problem with the VSTi's themselves, or something in Wine or LMMS's VSTi host. (edit: I now notice you said you use Windows, so it seems the problem isn't with Wine.)

As a workaround, I've taken to rendering those tracks separately, then resampling them in Audacity. The quality won't be as good, but it's better than nothing, and if it's only one or two instruments, it probably won't be noticeable.

but I still have the issue of silence at the end of each track. I really want to have to avoid trimming these manually in audacity since I want to preserve the timing perfectly for some looping fun.

Loop mode export seems to be broken in the latest version. Seems like a code regression, worked fine in the one before... same thing with oversampling, doesn't work at all, just a heads up.

If you need to export loops, it's trivial to calculate the target length, if you have a stable bpm. The function is 60 / bpm * number of beats, where number of beats = 4 * number of bars, if you're using 4/4 time. If not, then it's something else. The result is in seconds.

So let's say you have a single bar beat, 4/4 time 140 bpm, the length of the loop should be 60 / 140 * 4 = 1.7142857142857142 seconds. If you want to be really accurate, you can multiply that with your sample rate, and get the exact number of samples you need for your loop, but usually just entering the time in milliseconds is enough.

Loop mode export seems to be broken in the latest version. Seems like a code regression, worked fine in the one before... same thing with oversampling, doesn't work at all, just a heads up.

Sweet. I downloaded 0.4.14 and that worked fine for me. I suppose I'll just have to export everything at a lower rate. Sucks, but it's not a huge deal.

seeshi wrote:

Loop mode export seems to be broken in the latest version. Seems like a code regression, worked fine in the one before... same thing with oversampling, doesn't work at all, just a heads up.

Sweet. I downloaded 0.4.14 and that worked fine for me. I suppose I'll just have to export everything at a lower rate. Sucks, but it's not a huge deal.

Well, if you only have problem with some VSTi's, you can only export those at a lower rate, and export everything else at a higher rate. It's what I do. Just switch the tracks you have problems with to solo (remember to switch automations for the track on though, otherwise they'll be ignored too) and then export with lower rate, then invert the track selection (switch the problem tracks off, everything else on) and export with a higher rate. Then mix the two tracks together in Audacity (you can also resample the lower-rate track there, it may help the quality somewhat but will not remove aliasing).

Also, you said something about VSTi's that only play sound on the left track: apparently, this is because the VSTi's only output mono sound, which is interpreted by LMMS as everything being in the left channel. Since it's mono sound anyway, you can fix it easily with the stereophonic matrix plugin.

Holy fckn shit!!!

I have been rendering 16 bit masters directly from LMMS , but without the over sampling on... The difference is astronomical!!! So obvious to hear.... The rendered versions with oversampling sound like they have been mastered in a 200K studio by comparison. I swapped to rendering 16 bit because i kept getting bugs for some tracks @ 96khz 32 bit, never thought that it would be easily hear able .... 8X always from now on!!!

This is with VSTi's and VST's as well, having great success!


*edit** funnily enough, now I am getting bugs on 16 bit 44khz renders, but not on 96khz32bit with oversampling on... lol... I just have to find the right specs for each track and i get a good render Fairly sure this is a Windows vsts crash artefact... the bug is the arpeggiator crashes & then notes go missing..... sometimes the solution is to shift the whole song 10 seconds along the time line & render again... or maybe this is just observed correlation ... either way, it is making me WORK like a mofo to get the results...but hey, at least I dont have to boot into my windows partition... **shudders**

Franny23dmt wrote:Holy fckn shit!!!
The difference is astronomical!!! So obvious to hear....

So you export with x8 oversample?
Could you make a screenshot of the actual export settings selected.
Theres been quite a discussion about the value of oversample, and one of the variables in the mix, is ofcause file size..

musikbear wrote:

Franny23dmt wrote:Holy fckn shit!!!
The difference is astronomical!!! So obvious to hear....

So you export with x8 oversample?
Could you make a screenshot of the actual export settings selected.
Theres been quite a discussion about the value of oversample, and one of the variables in the mix, is ofcause file size..

I have had some success with oversampling, sometimes on 8 times, sometimes it works on 4 or 2. Sometimes it can have detrimental effects.. my main issue is an arpegiator in my main synth crashing during render.
It makes the mix feel like it has way more room, and this can sometimes reveal the poorly chosen channel mix gain levels.... Unfortunately because LMMS doesnt playback at this quality when you are writing, it is hard to always have the mix right with oversampling on... yesterday I rendered a track about 20 times adjusting levels... was really weird.. one rhythm melody had to be turned down by more than 6db... could barely hear it when playing back in LMMS, but after 96Khz32bit 8X oversampling it was very clear & present, still a wee bit loud almost, but I gave up trying to get better.

Sorry for no screen capture, I dont have an IMGUR account etc

Interesting. I believe our oversampling mostly creates huge files with distortion, but there may be something in actually pulling dB down.. Wont do anything for file-sizde ofcause :p

Franny23dmt wrote:
Sorry for no screen capture, I dont have an IMGUR account etc

np.

It is funny, it was only the first 5 or 6 tracks that I rendered with oversampling that didn't get issues. I only started rendering 16 bit files because 96khz 32bit was having issues, and I tried 16 bit to see if I could at least get a wav mixdown without parts missing. I am now only having success with rendering 96khz 32bit with no over sampling. I have stopped over working the arpergiator & it seems to have solved my issues. I hope the new version solves this