|
Avid Pro Audio CommunityHow to Join & Post • Community Terms of Use • Help Us Help YouKnowledge Base Search • Community Search • Learn & Support |
#31
|
|||
|
|||
Re: Best way to handle Punch In (PT 12)
Quote:
I do it when I have to, and it works fine (I just save a preset in the plug-in, that I can open in any session, and tweak as needed) - just bypass the plug-in if not needed, it works like a mute button. Most of the time I monitor through pro tools, so I know I captured exactly what I heard - even though I'm often using a desk on the front end. Sent from my iPhone using Tapatalk |
#32
|
|||
|
|||
Re: Best way to handle Punch In (PT 12)
Quote:
I'd like to be able to play up to 16 backing tracks, record 16 inputs, and use 8 buses at the same time (at 96kHz and 64 sample buffer). Do you think for sure it would work if I upgrade to an i7 8700k processor? Or is it a bit of a crapshoot? SiSoftware Sandra ID Host Name : StudioPC Workgroup : WORKGROUP Computer Mainboard : GigaByte Z77-DS3H BIOS : AMI (OEM) F9 09/19/2012 Intel vPro : 8.01.00.1248 Total Memory : 8GB DIMM DDR3 Processors Processor : Intel(R) Core(TM) i3-3240 CPU @ 3.40GHz (2C 4T 3.4GHz, 3.4GHz IMC, 2x 256kB L2, 3MB L3) Socket/Slot : FC LGA1155 Chipset Memory Controller : Gigabyte Core (Ivy Bridge) DRAM Controller 100MHz, 2x 4GB DIMM DDR3 1.6GHz 128-bit Memory Module(s) Memory Module : G.Skill F3-12800CL9-4GBSR 4GB DIMM DDR3 PC3-12800U DDR3-1600 (11-11-11-29 5-40-13-6) Memory Module : G.Skill F3-12800CL9-4GBSR 4GB DIMM DDR3 PC3-12800U DDR3-1600 (11-11-11-29 5-40-13-6) Video System Monitor/Panel : PLN PCT2785 (1920x1080, 27.0") Video Adapter : AMD Radeon HD 5450 (2CU 80SP SM5.0 650MHz, 512MB DDR3 1GHz 32-bit, PCIe 2.00 x16) Graphics Processor OpenCL : AMD Radeon HD 5450 (80SP 2C 650MHz, 512MB DDR3 1GHz 32-bit) D3D 11 : AMD Radeon HD 5450 (80SP 2C 650MHz, 512MB DDR3 1GHz 32-bit) OpenGL : AMD Radeon HD 5450 (80SP 2C 650MHz, 512MB DDR3 1GHz 32-bit) Pen and Touch Touch Digitiser : Integrated Multi-Touch : Yes Simultaneous Touches : 64 Pen Digitiser : External Storage Devices SanDisk SDSSDA240G (240GB, SATA600, 1.8", SSD) : 224GB (C:) Samsung SSD 850 EVO 500GB (500.1GB, SATA600, 2.5", SSD, OPAL) : 466GB (F:) Crucial_CT275MX300SSD1 (275GB, SATA300/600, 2.5", SSD, OPAL, SED) : 256GB (E:) ASUS BC-12B1ST (SATA150, BD-R, DVD+-RW, CD-RW, 2MB Cache) : N/A (D:) Logical Storage Devices StudioPC (C:) : 224GB (NTFS, 4kB) @ SanDisk SDSSDA240G (240GB, SATA600, 1.8", SSD) Files (F:) : 466GB (NTFS, 4kB) @ Samsung SSD 850 EVO 500GB (500.1GB, SATA600, 2.5", SSD, OPAL) Media Library (E:) : 256GB (NTFS, 4kB) @ Crucial_CT275MX300SSD1 (275GB, SATA300/600, 2.5", SSD, OPAL, SED) Optical Drive (D:) : N/A @ ASUS BC-12B1ST (SATA150, BD-R, DVD+-RW, CD-RW, 2MB Cache) Peripherals LPC Hub Controller #1 : Gigabyte Panther Point LPC Controller LPC Legacy Controller #1 : ITE IT8728F Audio Device : Gigabyte Panther Point High Definition Audio Controller Audio Device : Pine Technology Manhattan HDMI Audio [Mobility Radeon HD 5000 Series] Audio Codec : AMD HDMI Audio Serial Port(s) : 1 Disk Controller : Gigabyte Panther Point 6 port SATA AHCI Controller USB Controller #1 : Gigabyte Panther Point USB xHCI Host Controller USB Controller #2 : Gigabyte Panther Point USB Enhanced Host Controller #2 USB Controller #3 : Gigabyte Panther Point USB Enhanced Host Controller #1 FireWire/1394 Controller #1 : 13330 XIO2213A PCI Express to 1394b OHCI with 3-Port PHY SMBus/i2c Controller #1 : Intel ICH SMBus Printers and Faxes Printer : PDFCreator (4000x4000, Colour) Printer : PDF Architect 5 Driver (1200x1200, Colour) Network Services Network Adapter : Qualcomm Atheros AR8161/8165 PCI-E Gigabit Ethernet Controller (NDIS 6.20) (Ethernet, 1Gbps) Operating System Windows System : Microsoft Windows 7 Personal 6.01.7601 (Service Pack 1) Platform Compliance : x64 Performance Enhancing Tips Warning 2513 : TPM not detected. Some security features are unavailable. Tip 2 : Double-click tip or press Enter while a tip is selected for more information about the tip. |
#33
|
|||
|
|||
Re: Best way to handle Punch In (PT 12)
I now have my i7 8700k processor. I've built my new rig and performed all the regular optimizations, plus a few extras. I can play 16 backing tracks, record 16 inputs, and use 8 buses at the same time (at 96kHz and 64 sample buffer). I verified I'm getting a 4.5ms monitoring latency with this setup.
However, there is definitely an audible and weird comb filtering coming through the cans for the singer. It's still audible and weird at 2.2ms (direct monitoring through Apollo at 48kHz). It's no longer weird at 1.1ms (direct monitoring through Apollo at 96kHz). Moral of the story - stick with monitoring through UAD Console, even if it is a pain in the ass setting up two headphone mixes, two main mixes, using two instances of each UAD plugin (one in PT and one in Console for monitoring), and flipping back and forth with muting and unmuting etc. Last edited by chrismeraz; 04-09-2018 at 01:04 PM. |
#34
|
|||
|
|||
Re: Best way to handle Punch In (PT 12)
This is crazy!
The problem arises when doing punch-ins as the original poster said. I'm using an Apollo X16 and monitoring though the console app - this means I have the record and playback faders unlinked in PT, and I pull down the record fader so I don't hear the signal doubled. So far so good, I can record while monitoring through the UAD console. Now, it's time to punch in. I activate Quick Punch mode in PT. The problem now is that the armed tracks play back at the record fader level rather than the playback fader level even though the transport record button has not been activated. That means I don't hear them unless I turn up the record fader level which I don't want to do otherwise I'll hear a latent double. The thing that doesn't make sense here is that at this point I'm not actually recording, I've simply armed the tracks I want to punch in on. So punching in while monitoring through PT is actually impossible without either setting up either a side chain or duplicating the track and editing the clips?Duplicating tracks also creates extra work after the recording, dragging clips around, creating playlists etc... This seems like a very convoluted workflow, when in most (or even all) other DAW's you just select a preference to disable input monitoring and thats the problem solved. I just want to clarify this is actually the case in 2024 because I can't quite believe it would be this convoluted just to punch in over an existing track while monitoring though anything other than pro tools? Last edited by ralphonz; 02-27-2024 at 01:35 PM. |
#35
|
||||
|
||||
Re: Best way to handle Punch In (PT 12)
Quote:
__________________
HP Z4 workstation, Mbox Studio https://www.facebook.com/search/top/...0sound%20works The better I drink, the more I mix BTW, my name is Dave, but most people call me.........................Dave |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Quick punch.... can't hear track audio until I punch in | stainless | 003, Mbox 2, Digi 002, original Mbox, Digi 001 (Mac) | 5 | 07-31-2017 02:11 AM |
Punch In and Punch Out With no numeric pad | detroitkruk | 003, Mbox 2, Digi 002, original Mbox, Digi 001 (Mac) | 3 | 04-06-2010 11:00 AM |
Punch-in, Punch out Markers | RaySoul | 003, Mbox 2, Digi 002, original Mbox, Digi 001 (Mac) | 9 | 12-19-2008 06:10 PM |
003 Rack Punch In/Punch Out Mystery | poorman | 003, Mbox 2, Digi 002, original Mbox, Digi 001 (Mac) | 2 | 08-09-2007 06:51 PM |
Urgent! Automatic punch-in/punch-out for Mbox 7.0 | tymeless | 003, Mbox 2, Digi 002, original Mbox, Digi 001 (Mac) | 8 | 04-11-2007 04:44 PM |