Reducing file size?
- This topic is empty.
-
Posts
-
Hi all, I just completed my latest custom and I was wondering why the file size is so large? It’s only a 5 minute song but the con file is 80mb. All my other customs have been around 10-25 mb, but this one is huge.
The wav files are 50 mb each, but that seems pretty normal when compared to my other customs.
Here’s a link to the custom:
http://customscreators.com/index.php?/page/index.html/_/walking-disaster-r16269
Typically a custom file size should only be 80mb if you are using multi track audio. When compiling in Magma, the .wav audio file should only be used in the backing section of the Magma audio tab. All the other sections in the audio tab of Magma you should be using a blank audio file.
You could try reducing the quality of the .wav file to an .mp3 when compiling and that might reduce the file size.
Did you turn up the audio quality setting in magma? This will increase file size quite a bit if you turn it up too much.
So I rendered the muted song file to mp3, which is only 4mb in size. But now when I drop it into Magma it automatically creates a new .wav version which is once again 50mb. Weird
I recommend using Audacity which is a free program in which you can convert the .wav to a .mp3.
But the problem with that is that you have to download a DLL to be able to convert it to an mp3, and it’s not very easy to find.
You were likely using the same audio that you backing track should have been for everything in Magma. Magma comes with blank audio files to use for the instruments assuming you don’t have a multitrack. The actual song audio should just go in the backing track.
Just use the blank files provided with Magma.
I strongly encourage this as it is the most ideal and best method of keeping your file size down.
EDIT: I’ve analyzed your latest custom.
You claim it as a single-track audio setting, but all your tracks have audio in it. If you’re using the same audio on all of them, that is a very bad thing to do! Consider rebuilding this custom with just one audio file on backing and blank on the rest as others have advised.
And if you’ve been doing this on all your other customs, too, you should be considerate of other users and rebuild those customs with those same audio settings, too. Size matters. So does sound.
Nice to know I’ve been doing this wrong for a year now
I thought I had to use a specific length audio file, which is why I’d been rendering blank ones this whole time. This actually makes my life easier by cutting out an unnecessary step.
Size is the least of your worries, free drum fills and whammy bar action are the real issues.
Que?
Thanks for the help everybody. I guess I’ll be re-uploading all my customs in the next week or so lol
Nice to know I’ve been doing this wrong for a year now
I thought I had to use a specific length audio file, which is why I’d been rendering blank ones this whole time. This actually makes my life easier by cutting out an unnecessary step.
Que?
Thanks for the help everybody. I guess I’ll be re-uploading all my customs in the next week or so lol
Customs 101: we don’t have separate stems for most songs, we use a single track. When you whammy your notes on guitar or bass or you vibrate your notes on keys, the game applies an effect to the instrument’s stem. Official songs have separate stems, so guitar/bass/keys gets properly distorted. Customs have single tracks, so the entire song audio for the guitar track gets distorted. Same goes for anything that affects individual stems like effects, drum fills, etc.
Customs 101: we don’t have separate stems for most songs, we use a single track. When you whammy your notes on guitar or bass or you vibrate your notes on keys, the game applies an effect to the instrument’s stem. Official songs have separate stems, so guitar/bass/keys gets properly distorted. Customs have single tracks, so the entire song audio for the guitar track gets distorted. Same goes for anything that affects individual stems like effects, drum fills, etc.
Ahh yes of course, I wasn’t sure what you were referring to. Thanks m8
- You must be logged in to reply to this topic.