| So I've used this software extensively in the past (about 2 years ago) and I decided to start using it again and I have a weird issue I don't remember having before. Basically right after I record a vocal track (haven't even tried instruments or imported files) and I go to replay it I don't hear anything. I can visually see something was recorded, and at the bottom of the screen right above the tempo bars I can see the two bars right next to the '120.00' go up and down as the tracks play. And if that's not enough I even exported the file to a .wave and I can hear myself. So I'm definitely being recorded, but I can't hear myself when I immediately play it back. EDIT: So I just imported a .wav file and the audio from there doesn't work ether. And I know it's not my headphones because I can hear myself when I talk into them. |
Feb 24, 2012 I've tried running my Axe-II through Garageband for the first time via USB connection. I've started by importing an audio backing track which was no fuss, but when I play back the project I can't hear anything over my computer speakers, yet I can see the level meters going in the track pane and the track's definitely not muted.
| I still haven't solved this issue. Any help would be much appreciated. I can also provide more information if needed. |
| I have a similar problem, can anyone shed any light on this? |
| Still have this issue... |
| ryanpounce wroteStill have this issue... I had this problem for the first time this morning (Eastern Australian time), after I upgraded Studio One to version 2.6.5.30360. Have spent ages before I found it; but check and see whether this works for you. All previous upgrades have left the Audio I/O Setup unchanged, and it looks to me like this upgrade overwrites the output setup. Navigate to Studio One > Preferences, and bottom left select the Song Setup button. Top left, select the Outputs tab. For the Main row, ensure that there are entries showing in the Output 1 and Output 2 columns. In my case, they were blank. I clicked once in one of those columns, and suddenly L and R (in nice blue boxes) populated the spaces. Then click OK to close the dialog, and try again. I got sound at this point (through my laptop speakers, to be sure nothing else in the output chain was interfering). Hope this helps. |
| I have the same problem as you. I just started using Presonus today and I see things that could help BUT I DONT KNOW WHERE THEY ARE! Can anyone help?!? |
| To hear audio go to your studio one options -> audio setup tab -> at audio device click control panel -> make sure exclusive mode box is unchecked. That is what i did |
| same problem here ? plz update |
| I found that you need to press the S (for stereo) and Un-press the record button. Then only the S should be showing. That worked for me. |
Garageband I Can' T Hear Anything Like
| A couple minor issues: Welcome to the forum! Lots of very helpful people here. By default, 'S' is for Solo, and doesn't have anything to do with Stereo. You don't need to unpress the Record button (AKA 'Arm'). By default, all tracks which are NOT Muted will play sound. (If the M is on - bright red, it won't play.) That means 'S' is not required to play tracks, although if you want to play one, you could solo it. Additionally, this is a thread where the original message is over 4 years old and the last message before yours is around 2 years old. Most have found some solution a little earlier. (And a non issue for most... Unless they muted all their existing tracks...) Don Studio One v4.x Professional - latest version PreSonus Studio 26 Eris E5s iZotope RX7 Advanced Windows 10 Pro x64-16 GB RAM MacOS High Sierra (10.13.6) iMac i5 w 8 GB RAM FB group for Studio One Users - Audiobooks, VO and Podcaster focused: https://www.facebook.com/groups/StudioOneNarrationVO/ Studio One and iZotope RX Tutorials for Narrators/Podcasters/VO/Dialog: https://www.youtube.com/user/RedBaarnsAudio |
Who is online
Users browsing this forum: elRey, rodshort and 9 guests
If you want to export your songs out of Garageband without normalizing all of the tracks, you’re in luck, because it’s actually a pretty simple process that requires only a few clicks. Here’s what you do:
1) With Garageband opened up, click on the “Garageband” button on the top left of the toolbar.
2) Then click on “Preferences.”
3) Click on “Advanced.”
4) Next to the box that says, “Auto-Normalize,” you’ll notice it says “Export Projects at Full Volume.”
5) Uncheck the box so it looks like what you can see in the image below:
I’ve never had the “Auto-Normalize” function turned on since I first learned how to use the Garageband software, not to say that it’s not useful, but it hasn’t been for me thus far.
I think the option might be there just so that when beginners to the program want to export tracks, they’re guaranteed a way of exporting their music and other audio files without clipping or distortion.
I believe the purpose of it is to provide a simple way of “optimizing” the export that way you don’t have to think so much about what you’re actually doing.
Chances are, if you’ve arrived at this article, you’re probably wondering how to get your Garageband exports to sound louder and higher quality as well.
In addition to turning off the auto-normalize function, there are other things you can do to increase the total volume as well.
I’ve written another article about how to increase the volume of your songs using a variety of tactics, which you can read more about in the article linked here.
More on Auto-Normalization And Other Tips
As I just mentioned, having the auto-normalize function turned off in Garageband’s ‘Preferences’ is going to be what allows you to export your tracks at the desired volume.
However, because you’ve eliminated the setting which acts as a fail-safe, you have to pay closer attention to your music, including the VU meters, the number of plug-ins and so on, otherwise, you’re going to have distorted and clipping tracks.
An additional tip for normalizing audio in Garageband is to avoid setting your VU meters above +0.0dBFS. “dBFS” means: Below Digital Full-Scale.
+0dBFS is the point in decibels, where if you were to go any higher, it would be too much for the software. It’s basically the ceiling, it’s the limit.
It’s kind of like the standard unit of measurement that we use to describe the limit that you can’t go past when making digital recordings.
We’ll talk more about dBFS in a second.
In the digital world, anything above ‘0dB’ is considered clipping.
For this reason, it’s important to make sure that you leave a lot of “headroom” in your mixes.
For instance, if you’ve mixed your music and some of the tracks are going above the 0dBFS maximum, there will likely be some problems when the final tracks are cut to mp3, CD, or vinyl.
By headroom, I’m suggesting that when you’re mixing tracks before you’ve even started the process, you should drop down all of the VU meters to at least -3.0dB or perhaps even a little bit more, like up to -6.0dB.
You can see what “Headroom” looks like in the image that I’ve provided below:
You might be kind of confused as to why it matters that a track exceeds 0dB in the DAW.
Truthfully, “0dB” on its own doesn’t actually mean anything, because there has to some kind of reference point for it to mean something.
In other words, a decibel is a ratio that is comparing one signal to the other.
If you’ve stated that your signal is 0dB, without providing some kind of reference point, you’re just saying that the signal is equal to something, but not really communicating what that “something” actually is.
Without the reference point, “0dB” is essentially meaningless.
For instance, when looking at the Garageband interface, there are other symbols which provide a larger context for what the dB is actually measuring and comparing to.
From what I understand, “+5dB” means that we’re 5 times whatever 0dB is, and if we’re at “+3dB,” we’re 3 times whatever “0dB” is, and so on and so forth.
“-3.0dB” means we’re half of what “0dB” is and “-6.0dB” means we’re 1/4 of what “0dB” is.
Audio software – DAWs and Garageband included – are typically different in terms of how much signal and power they can actually handle without clipping and distortion.
This limit of what the DAW can actually take is called dB Full-Scale, or more commonly referred to as dBFS.
Like I mentioned above, the dBFS scale is kind of like a system of comparison or a standard by which people are measuring something.
For example, a speaker system might be able to generate 50 W without blowing a speaker, while another one might be able to go to 200W.
For that reason, it makes sense to have a full-scale system that way we can communicate how much fits between each system.
If this is confusing, I’ll try to explain it simply.
If Person A’s speaker system has a maximum of 50 W, and Person B has a speaker system that can put out 200 W, each person has a different idea of what their dBFS (their audio ceiling) is.
For Person A – (This person has a maximum of 50W) – an output of 50W equals = 0dBFS.
For Person B – (This person has a maximum of 200W) – an output of 50W equals = -6.0dBFS
If Person A turns up their wattage to 200W, the meter will say that it’s +6dBFS, which means that it’s going above what it can handle and it’s going to blow.
The reason behind this system of measurement is that it provides a standard for people to compare to because trying to remember the maximum amount of watts for each system would be a pain to recall.
If you’re anything like me, then all of this stuff might take a little while to sink in, so we’re going to try and explain it again another way.
As I mentioned above, decibels on their own don’t actually really mean anything, they’re just ratios, and they’re comparing two different signals to each other.
In the case of digital sound processing, “0dB” is considered to be 100%.
10% would mean “-10dB” and “+10dB” would mean we’re at 1000%, which is far beyond what that system can handle, whatever system it is that you’re using.
Garageband, for example, communicates how much it can handle with the same meters.
The VU meters and the Master Volume Fader are telling you how much it can handle with not only the “Red” clipping signal but also with the numerical values on each of the VU meters.
Garageband I Can't Hear Anything Go
Now, let’s use the example of human hearing.
If “0dB” is the quietest sound a person can possibly hear, that means that, obviously, “-10dB” is so quiet that we can’t hear it, because – think about it – “0dB” is the quietest sound we can hear, so, therefore, anything below that is too quiet for a person to hear.
On the other hand, if 0dB is the quietest thing we can hear, then that means that 20dB is 100 times as loud as the quietest thing we can hear.
As another example, if “0dB” is the volume of a jet airplane taking off, then the quietest sounds that a human can hear would be “-118dB” and “-98dB” would be way louder than “-118dB.”
A jet-airplane taking off would be near the very top of this chart.
Essentially, decibels are just a system of ratios that we use to compare different sounds.
Garageband I Can't Hear Anything
YouTube Video
Conclusion
Garageband I Can't Hear Anything Video
To wrap it up, remember that once you turn your auto-normalize function off, you have to keep a little bit of headroom on all your VU meters. Don’t go above +0dB.
This is going to ensure that you don’t have any unnecessary clipping or distortion in your music, which is obviously what we want.