Mix print level???

[rdpar]

So as with all my projects, when I think I've got the mix right , I print a stereo track of it and then bounce to a designated "mixed" folder. So, on this particular track( I always mix down to stereo at -5db to leave room for mastering) I have to feed my print track at -8 to -10 just to keep waveform within the lines. However, even though it looks like it's clipping badly, the output of the print track is -8 to-10 db. What's up with that? This has never happened to me before. Pro Tools 2019,32gig ram Thanks for your patience:)

[JFreak]

It is clipping before you send it out.

But is there a reason for the print track? If you do the bounce anyway, then the print track seems kind of useless. I use print track when I do a live gig and want to record everything I do while mixing, kind of like sending my FOH mix to CD recorder as well. Don't see a point of bouncing that stuff later as it is.

[musicman691]

I keep things simple.
When I have a mix where I want it I record it in real time to an audio track in PT. I work at K14 metering with -1 dbFS. That's the track that gets put on a CD (I self master). It gets me consistent levels and I rarely have to raise a level when 'mastering' but more often drop levels. You see I don't play in the 'volume wars' and if it's not loud enough use the volume control on your playback device.


Why record in real time? So if I hear something I don't like I can stop transport and fix it.

[JFreak]

Originally Posted by musicman691

Why record in real time? So if I hear something I don't like I can stop transport and fix it.

You do just the same when listening to real-time bounce. So keep it simple and don't print like that, unless you have a good reason to do that like capturing real-time mixing.

[Bob Olhsson]

Just print to 32-bit float files and it probably can't clip.

There is one very good reason to print to moderate levels. You don't ever want your monitor D to A's headroom limitations influencing the choices you make.

[henningaround]

Originally Posted by JFreak

You do just the same when listening to real-time bounce. So keep it simple and don't print like that, unless you have a good reason to do that like capturing real-time mixing.

For me the reason for a print track is to be able to punch and insert at any time when I hear a mistake or something I would like to change. I hit back-and-play, punch in, immediately e.g. correct an EQ while recording. Then I hit Auto Match just to be safe. Recording goes on until the next miskate pops up. And to be honest there are always mistake popping up.
I would be bouncing instead of printing I would have to listen to the whole track again. If I here a mistake I would have to correct it, bounce againg, listen again... That's just because offline bounce aren't always sample accurate in the right place place. They often or mostly are but sometimes they are not. So one can't punch in reliably. Often or mostly it's possible.
But because there are so many things that work like 99% of the time I have to choose workflows which work 100% where it's possible.
Of course this has nothing to do with the actual problem here :) sorry

[the.engineer]

+1 for the K metering system. https://www.digido.com/ufaqs/monitor...with-k-system/

It transformed the way I mix


James Welch
Recording Engineer | Producer
Masterlink Productions

Mac Pro 5,1 (Mid 2010) | 3.46GHz Six-Core Intel Xeon | 32GB Ram | AMD Radeon R9 280X 3072 MB | 256GB Samsung SM951 SSD Blade (PCIe) System Drive | 1TB WDC Sample Drive | 4TB RAID 0 Seagate Audio Drive | UAD-2 Quad PCIe
Mojave 10.14.5 | Pro Tools Ultimate 2019.5 | HDX | Avid Omni | Avid 16x16 HD I/O x2 | Digidesign 192 | Digidesign C24

[the.engineer]

Also, have you made sure your waveform zoom is at normal?


James Welch
Recording Engineer | Producer
Masterlink Productions

Mac Pro 5,1 (Mid 2010) | 3.46GHz Six-Core Intel Xeon | 32GB Ram | AMD Radeon R9 280X 3072 MB | 256GB Samsung SM951 SSD Blade (PCIe) System Drive | 1TB WDC Sample Drive | 4TB RAID 0 Seagate Audio Drive | UAD-2 Quad PCIe
Mojave 10.14.5 | Pro Tools Ultimate 2019.5 | HDX | Avid Omni | Avid 16x16 HD I/O x2 | Digidesign 192 | Digidesign C24

[JFreak]

Originally Posted by henningaround

For me the reason for a print track is to be able to punch and insert at any time when I hear a mistake or something I would like to change. I hit back-and-play, punch in, immediately e.g. correct an EQ while recording.

You aren't using reverbs or anything random, are you?

[cwsand]

Originally Posted by henningaround

For me the reason for a print track is to be able to punch and insert at any time when I hear a mistake or something I would like to change.

What are you referring to as a "mistake"?