Inaccurate Fader levels

I remember reading about this on some forum somewhere....
The fact that the fader levels jump several number values instead of in perfect sequencial order.
For example, wanting to go to -11db, the fader will only go either -10.9 or -11.2.
Even if I try and type in the exact number (-11), it'll just show up as -10.9
Why is this? Is this a bug? A 'feature'? Is there something in the prefs that allows for better accuracy?
Thanks

Sampleconstruct wrote:
It´s due to the subdivision of the fader into 128 Midi steps.
This is partially correct. The numerical issue is simply display rounding to 128 steps. The actual volume automation data is full 10 bit, 1024 steps. As has been mentioned, you can access this resolution by controlling the numerical field on the track header. It's also available if you have a Logic/Mackie Control surface.

Similar Messages

Controller volume fader changes all fader levels

Hi,
I'm using an M-Audio KeyRig 49 controller.
I set up a whole concert and it worked fine. I set up the keyboard's only fader to control the master volume. But now whenever I touch the keyboard's fader to adjust the master volume each channel's level jumps to the fader level - throwing off all my levels.
I'm new to MainStage (and Logic). How do I separate them so the volume fader only controls the master volume and I can set the channel levels once and leave them?
I have to have it up and running by this weekend.
Thanks!

I may have answered my own question. Seems that when I record with the master fader on a lower level the problem is resolved.

Saving Fader Levels

Hi
Lets say I've recorded all my tracks in Logic and I have all the fader levels set nicely, and then I need to record something again. I need to change the fader levels to suit my headphone mix while recording again, so is there a way I can save the 'bounce' version of my fader levels (and all of the control strip settings), then after messing about or whatever reload the previous 'bounce' levels. I don't really want to get into writing automation levels for each fader or using the 'save as' facility to make separate Logic projects.
Thanks!

Impressive indeed. However, as with all extensive Environments that are directly cabled to Channels, it prevents you from using the new and nifty Automatic Channel Strip Management, which takes care of creating and duplicating Channel Strips as and when you need them.
I think we have commented that many times with you Christian... But this is quite new prototype of a whole complex Environment tool and as I mentioned the Song template supports 32 Audio, 32 Instr and 32 Aux tracks. I think it is quite enough as beginning... The "Snapshot Console" is organized as one "Master" and a few slave ( have a look at the "Link" buttons next to 'Save and "Load". Any SC can be Master or Slave depends of the "Link" buttons modes. My idea was when hit "Save" on the Master all other to "save" as well, same with load. So you can copy the SC and add more tracks.Honestly I have not tested with more then these 96 channels yet, but it must work...
In addition I forgot to mention that there are a few SC tracks in the Arrange. The user can draw or record Program change messages ( it supports Program Names according your Presets names ) on any of these "Snapshot Automation" tracks to control separately some given sectors of the Logic Mixer, or to draw or record Program Change massages on the "Master Console" global "Snapshot Automation" track, to control the whole Logic mixer using one program change message only etc...
Regards,
Ivan
!http://img59.imageshack.us/img59/4967/aglogo45.gif![www.audiogrocery.com|http:/ /www.audiogrocery.com]

Fader levels and mixing

Coming from years of analogue recording I've been used to riding fader levels quite high (slamming the tape, etc.) However, I've noticed that in the DAW world this is actaully NOT such good practice!
I was wondering, though, if it was typical to have fader levels at such low levels. Sometimes my levels are at -18db or more!!? However, everything sounds good and the final mix comes out fine with some mastering tools. But I have found that lower fader levels allows for better mixing..its just odd, for me, to see such small scaling in the tracks' VU meters!
Am I doing something incorrectly here. Is there some kind of calibration that I am not aware of that raises the amount of fader play?
Thanks.

Clem et al,
This information was helpful as I too want to record in the -12 -18 range for tracking, but I'm struggling a bit with gain-staging, etc at the Tracking, Mixing and Mastering stages. My goal is to record as cleanly as possible and maintain headroom as I move between these three stages to a finished product. If you know of a good website that covers these fundamentals that would be also be helpful.
Here's what I'm currently doing on a typical song (I'm doing this all myself due to current budget)
TRACKING STAGE: Record each audio part (typically vocals, guitar & bass) at -12 to -18 in 24 bit / 44.1 kHz (44k to save disk space...I can do 96 on my Apogee Duet if that offers significant benefits. Note that this is the *recording level* - not where the vocal/bass/guitar sits after pulling back the track fader).
- Issues at this stage: When I record at this level I have to crank my Duet headphone output up to 100% and it still is occasionally hard to hear the part vs the backing material I've already recorded. When I track at a higher level and then pull back the fader for the mix this is not a problem.
- My Summit 2BA-221 pre appears to be barely working to get this -12 to -18 in Logic arrange window.
- Main question: What should be corrected in the above? Should I record the track at a higher level to "work" the mic/pre and add more tube "warmth" etc. or go some other route. If I track at this level does that match up more closely with Logic's default compressor/limiter, etc. plug settings? Also I notice that if I use an aux/send for drums, etc. that the level coming from that aux can also add up after a enough tracks are sent to it.
- I want strong vocals, but don't want to then hear the backing track drop (due to compresssion) when the vocal levels jump higher.
MIXING STAGE: I have heard from more experienced musicians/engineers on other websites that I should mix down (bounce) to a stereo track prior to mastering and keep this to -3 -4 prior to mastering. Is this target level correct. Should I be using a buss/mix compressor here for "glue" and/or EQ here or wait until final Mastering stage?
MASTERING STAGE: Currently I am using Ozone 4 for this...any basic guidelines or pointers you can offer are very much appreciated.
I realize that much of this is subjective and an art, but I'm looking for basic building blocks that I can work from...to that end any related info you can provide is very much appreciated. I realize you could respond with a book to the above but I'm primarily interested in correcting my gain-staging approach as related to the original tracking level discussion here.
Thanks in advance for any assistance you can offer!

Playhead freezes during playback and no fader levels (Logic 8)

during playback on my powermac g5, it's a legit version from a studio.
playhead freezes and stops moving all together untill i pause and press play to refresh position.
This is happening with some but not all projects;
happening on a reasonable sized project, it contains 22 tracks overall, 16 are audio tracks (without excessive plugins) the rest of the tracks are various synths.
(i have checked the core overload and neither core is overloading and i am using the audio channel trick for the VSTs to balance it out between cores.)
got 10 bus sends but again nothing huge on them, just reverb here or there and basic FX and group EQ.
finally nothing on the master channel bar a EQ that is just analysing Freq.
I'm also not getting any fader levels at all during playback, this might be from the same issue?
the software isn't lagging at all just no playhead movement and no repsonse from faders, i've most probably pushed a button since i've recently moved over to logic from ableton on a PC.
let me know if i'm the moron or if it's a bug/something
Version No. 8.0.2

Actually, I must make correction, it is not the core audio error, it is the disk too slow error.

Inaccurate battery level

Here and in other places, I have seen several complaints about lack of a correct battery level indicator. This seems to be the case with more than one phone model. Considering short battery life, it is a real problem that battery level cannot be checked with any accuracy. I sometimes have 7 bars when I turn off my 6220 classic, and 4 when I turn it on again after a short while. This shows that the firmware checks battery level very seldom or that the procedure has very little precision. Checking with PhoNetInfo or NSysInfo gives the same result. They seem to reflect the firmware's reading.
It cannot be so difficult to make the firmware check more often. Why has this not been done?
Is there no software that is capable of doing its own direct check?

it's not difficult to have the software or firmware that check batt level more... pool more but:
- The more you do, the more batt it's used... therefore shorten your batt life again.
- The batt has IC chip built in, and the batt after you use a while capacity is less and less and your chip may malfunction, which may give you incorrect value and batt life shorts.
Even if you turn off your phone it still used the battery as if you set alarm and turn off, it will turn on and sounds.
This is a feature too that ppl want...
Hope this helps

Levels and pre-fader metering

In the past I had always presumed the channel fader controlled the volume level of a softsynth. I know now that it obviously does not. It simply acts as a "faucet," so to speak. Meaning that increasing the fader level simply allows more of the synth's signal to pass.
So my question is this: Understanding that it is the instrument itself which is actually generating the signal (and consequetly the db's) should I keep all my faders at 0.00 on my audio instrument tracks and adjust the instrument levels instead when I mix? It would seem to make sense.
And in keeping with this method, as far as automation is concerned, would I be correct in assuming track volume should be automated via the instrument level?
I'm trying to keep all of this in the context of how it would be done in a studio with "real" instruments. Where the volume level is the volume level and if you want it louder you play harder or you turn up your amp. You want it softer you play your instrument softer.
I should add that this whole question/conundrum came up after I started recording with pre fader metering enabled and was quite surprised to see just how easy it is to clip a track (remembering of course that as long as no clipping is occuring at the master output I'm NOT actually clipping).

I don't know where all this "fader fear" is coming from.
In DSP terms, making something louder or quieter is simply a really simple DSP calculation. It doesn't matter whether you turn you softsynth down 3dB, or turn the fader down 3dB, the end result is exactly the same.
The faders are there for easy controlling of levels. It's why mixers were invented and designed this way.
I think these days someone reads a post on some esoteric audio forum about how their mix was so much better when they left the fader at 0dB in some obscure DAW back in the 90's, and translate that into "I must never use faders" or "I must never EQ" or "I must effectively work out my mix beforehand by my mic choice and positioning so all the signals magically combine into an artistic mix."
I'm trying to keep all of this in the context of how it would be done
in a studio with "real" instruments. Where the volume level is the
volume level and if you want it louder you play harder or you turn
up your amp.
You completely lost me here. Learning about gain staging is Elementary Audio Engineering Class 2 (the one afer the "what is a signal", and "what is a transducer").
You set the level of your recording device or mixer's input depending on the item you are recording, so the natural sound of whatever your source is corresponds to some nominal level for your recorder. It doesn't just magically happen on its own.
If you're recording an instrument that doesn't put out much sound level, you use the mic preamp to boost the signal to an appropriate recording level. And if you're recording Concorde taking off, you adjust your preamp, probably turning it down or padding the signal, again so it fits the range of your recorder.
Softsynths can put out a lot of level, and many preset designers don't pay much attention to volume levels in their patches. In addition, when you play a patch polyphonically, you're mixing together multiple signals (each of the notes you are playing) so you end up with higher levels still. It's good practice to pull down the output of the synth if it's too hot, but generally speaking, and avoiding getting into any "levels in Logic" complexities here, using the fader in Logic is exactly the same process.
Faders don't bite. Use 'em.

Automation Values in Groups: Fader Drags vs. Node clicks

Thanks in advance helpful people, I'm sure this is obvious or not possible... one of the two. I'll just explain it as an example.
I have 4 drum tracks (Kik/sn/l&R) selected as a group with what I think are all the correct group settings. All four fader values are starting at different levels, and when I raise and lower a fader, all raise in relative level.
Now I put it in Automation mode. When I change automation levels via the fader (in touch or latch) as the tune plays, the levels differences stay same (Ex: track1> 1.5db up to2, track2> 2.3db up to3).
I want to be able to do this with adding a node click as well. When I click on one of the group's region with Automation enabled, all the track fader levels snap to the same db. Is this normal? I want the relative differences to stay the same, but raise all four in their relative level.
Any help would be appreciate... this along what seems to be an UNDO bug is driving me nuts. Thanks
Logic Express 8

Thanks, I guess it makes sense. However I now have another question about the bus. If you don't feel like giving me a lesson on an aux channel and wanna tell me to RTFM, great... but please tell me where;)
Here is my example: I have two GTR tracks from two different mics, I have them panned just the way I want, and the volume difference just the way I want. Your suggestion makes sense about changing both in volume... but is there a way to keep the placement in the stereo field the way I like it... cause whether the Aux channel is clicked as mono or stereo... I loose the Placement.
The reason that I need to keep the stereo placement is that it's causing the good type of phasing. Thanks... I didn't feel like a newbie until today!

Pre Fader Metering Query...

Hello to all,
I've been following a couple of threads recently and the topic of Pre Fader Metering has come up in regards to the level of the final stereo Output. I would like a little more clarification on this.
My individual track levels often times are in the "red" Pre Fader, but that seemingly never has anything to do with my final stereo output level; it's my Post Fader level of each track that affects it.
How, if at all, does the Pre Fader level affect the final stereo output? Since Logic has 32-bit floating point architecture, isn't there a ton of headroom on individual track level and its like impossible to really overload/clip?
Thanks in advance for any insight on this.
M-DAY

Yeah - sorry for the headrush, that thread was a doozy!
Yes, the same issues occur on for plugins in any audio path - if they use a fixed-point implementation, like for instance some Waves plugins do, or have low input headroom, then you can be distorting the audio through the input stage before the plugin is even doing anything, if you send in high or over-0dB values.
It is quite posible to clip the outputs slightly without really hearing much - the ear is used to small amounts of distortion, but you are damaging and changing the audio by doing so. Some people like this effect and even use it regularly.
Personally, there is a very good argument for keeping mix levels way below the 0dB point - 24-bit audio is fine for this, you don't lose resolution by turning the volume down, which is a popular misconception.
And any distortion you add into the chain, make sure it's introduced and controlled by an artistic decision, not a side-effect of not understanding what's happening...

Pre-fader vs. post-fader metering

I generally avoid any internal clipping on my virtual instruments by making use of logic's pre-fader metering option, is this really necessary?
Which is best, mix post fader and forget about internal levels of plug-ins, instruments etc. or always make sure there is no internal clipping?
What are the results really when making sure there is no post or pre fader clipping?

Chance Harper wrote:
I did a quick experiment to see what the result would be if I overloaded or pushed the internal volume of a plug-in but made sure the output channel wasn't clipping VS. a plug-in that got leveled pre and post.
I used only a drum kit from battery 3 with a simple riff. Pushed the plug-ins overall volume to +6.0dB and then made sure my post fader level wasn't clipping, both of them then got mastered using ozone 4.
Both of the tracks reached the same RMS level, neither of the two sounded louder than the other.
The one I pushed up in the plug-in sounded a bit squashed and not as clear or pure as the one that considered the pre and post fader metering. The drums sounded way more defined and clear when ensuring both pre-and post metering wasn't clipping.
It does seem that by ensuring none of your virtual stuff clips internally you get purer sound.
Of course I am sure you could still get a great sound if you internally only pushed it over by 2dBs. Still think it's best though to mix pre and post as a rule. Any comments?
Message was edited by: Chance Harper
Message was edited by: Chance Harper
Message was edited by: Chance Harper
again, i would agree with BeeJay's original reply to the original post. it's not good practice to let internal levels fly out of control and there's really no good reason to. and i would also agree that keeping levels lower result in better quality mixes.

Setup help - low signal level in Logic

I'm getting low input signal levels when recording in Logic (-17db to about -10db, on average), and am hoping someone here can point out an obvious oversight on my part.
I'm recording mic'd guitars and vocals (one track at a time), with the mic(s)running into a Mackie 1402 mixer via XLR. Signals are strong and fine when I solo on the Mackie.
The signal runs out of the Mackie via the Alt 3-4 bus into the first and second 1/4" inputs on the back of a Motu 828 mkII, then into Logic.
Even if I drive the signal to near clipping on the Mackie, I get these low levels when recording in Logic. This is true whether I'm using a condenser mic with phantom power for vocals, or a dynamic mic on a guitar amp. I've also tried swithcing XLR mic cables.
I'm running Logic Pro 7.2.3 and OS X (10.4.9) on a G5 2.5 DP.
Is my signal path in need of some tweaking, or perhaps it's a setting I'm overlooking on the Motu 828?
Any help greatly appreciated to get this rookie back on track!
G5 2.5 DP Mac OS X (10.4.9)

Hi,
You wrote:
I'm recording mic'd guitars and vocals (one track at
a time), with the mic(s)running into a Mackie 1402
mixer via XLR. Signals are strong and fine when I
solo on the Mackie.
The solo on the Mackie is probably louder,check to see if you have it AFL(after fader listen or PFL(pre fader level or "level set").
The signal runs out of the Mackie via the Alt 3-4 bus
into the first and second 1/4" inputs on the back of
a Motu 828 mkII, then into Logic.
The first thing to check is to see what kind of cables you are running into the Motu mkii.
A. Unbalanced (ie "guitar-type" with two wires)
B.Balanced (ie "stereo-type" with three wires)
The second thing is to check what your inputs on your Motu are,there are two choices: +4dBu("pro") or -10dBV("consumer")
Here's the catch:
You MUST MATCH the correct cables for the correct levels.If the Mackie is outputting -10dBV but your Motu is thinking it is +4 you see less level no matter how loud you make the Mackie outputs.
The Mackie can output AUTOMATICALLY either -10dBV or +4dBu depending on what cable is hooked up to it.
Even if I drive the signal to near clipping on the
Mackie, I get these low levels when recording in
Logic. This is true whether I'm using a condenser mic
with phantom power for vocals, or a dynamic mic on a
guitar amp. I've also tried swithcing XLR mic cables.
This is not where the problem lies.It lieas between the output of the Mackie and the input to Logic.
I'm running Logic Pro 7.2.3 and OS X (10.4.9) on a G5
2.5 DP.
Is my signal path in need of some tweaking, or
perhaps it's a setting I'm overlooking on the Motu
828?
Yes,a setting somewhere in the Motu is not set correctly.Check above for how to do that.
Any help greatly appreciated to get this rookie back
on track!
G5 2.5 DP
Mac OS X (10.4.9)
Cheers

Adjusting Cross Fade

Is there a way to adjust the cross fade level (like in itunes) so the songs are not over lapping by 10 seconds?

I have decided that if there is no way to adjust the cross fade level I will return the nano, the cross fade feature was the sole reasoning I bought the thing. The other features are great but I have 2 other cameras with video recording capabilities (that are far more better) and 2 other ipods that hold far more music and video, what was I thinking?

How to charge for the first time?

I bought myself a new iPhone and this was from the store, not from someone else, so how should I charge it for the first time? Should I wait when iPhone loads out till blank screen and the charge it to 100%?
How do you charge your iPhone by the way, sometimes I think that I should not let it load out till the blank screen, because when I put it on charge it sometimes took at least three times to begin charging - instead it loaded me the apple logo, waited for a second and then it loaded itself out, then I needed to push the sleep/wake button to turn it on and again it only showed me the apple logo for a second and loaded the iPhone out.
Do you start to charge your iPhone when it gives you the alert that 20% or 10% are remaining?

The new batteries don't need as much care as the old generations. Their lifetime is supposed to be mostly independent of how often and at what charge levels you discharge them. So feel free to charge as you wish.
If it starts showing inaccurate battery levels, calibrate it by doing a full discharge/recharge cycle.

Final Cut 7.0.2/Tascam USB-2, US-144MKII audio output intermittent

Dear folks,
Hello.
I am continuing to have problems with getting sound out of my Tascam USB 2.0 inteface box using Final Cut v 7.0.2, on a Mac Pro 2x2.66 GHz Quad Core Intel Xeon, OS10.6.4 .
The interface unit is a Tascam US-144MKII, USB 2.0 Audio/Midi Interface.
I have down loaded its driver. It works fine as the system output and playing back from Quicktime player.
In Final Cut it is fine one moment, sometimes pops and clicks then it goes silent. It is unpredictable and unstable. It is intermittent, not working most of the time. I have refreshed the AV Devices, set audio output in Audio/Video Preferences and tried Sequence settings, as well as restarting the computer.
I am having to go Firewire out to an external deck to get sound out of Final Cut onto my sound system.
Final Cut seems to be the problem.
Any ideas?
Thank you for your time.
Bests,
Peer

I've had limited success across five suites. Running FCP 7.0.3 across all rooms, however I've only been able to get one room functioning in a limited way. It sees MIDI info in the Control Panel indicator and replays some fader level info, however only when stopping and starting FCP. Have been troubleshooting the issue and have downloaded the newest Tascam driver for the FW-1884 (from May 2010). Can get FCP audio output through the monitor bussing on the Tascam, however actual moving-fader still not achieved.
Called Tascam's (LA) help line and they couldn't give me any advice at all (as they would only comment on Logic issues and were unfamiliar with using FCP!)
Any suggestions from anyone?
Thanks.
Message was edited by: Christian Bass

How do you new Mac Pro owners like your machine with Logic?

Don't mean to be a PITA but I need to get this right before I drop three to five grand on a new set of music tools. I'm trying to decide between Mac Pro and iMac for use with Logic. Seems there are a lot of posts regarding glitches with the new Mac Pro and Logic, whereas the posts from people with older G4s and G5s seem to indicate they are running rock solid. So you new Mac Pro folks or anyone else, please weigh in. Is the new Mac Pro "glitch heavy" or is it just a matter of tweaking the system to where it runs smooth? In general, how do you new Mac Pro folks like the way it works with Logic?

I'm mostly pleased with my MacPro 2.66. Almost no crashes with Logic, although I experience a few more bugs here and there than with my G4. Occasional CoreAudio errors, I have to restart CoreAudio if my external word clock is set to the wrong sample rate when I open a session, there seems to be a bug between high fader levels (above +4dB) and panning... little things like that.
Then again, compared to my G4, the FireWire bus is screaming fast--with most sessions, I can run a buffer of 128 samples at 96k with my MOTU 828mkII, while my G4 would sometimes glitch at 96k with 512 samples. At 96k, 256 samples, my MacPro/828mkII rig is rock-solid... I informally tested it by recording 12 test tracks simultaneously for 20 minutes, with the CPU nearly maxed out (which was difficult to do--took a bunch of Space Designers and Ultrabeats)--absolutely zero clicks or pops.
And of course, WAY more processing power than my G4.
I'm assuming that MacPro compatibility is a fairly high priority for Apple these days, so hopefully the bugs will get worked out soon. And as things are, Logic is definitely usable on a MacPro--the bugs I encounter rarely slow down my work.
So, far from perfect, but as far as new technology goes, I'd say Logic on the MacPro is above average.
Good luck!
James
[email protected]

Inaccurate Fader levels

Similar Messages

Maybe you are looking for