Punch-in recording

I just purchased Soundbooth CS3 with the Creative Suite and can't seem to find a way to "punch-in" when I want to replace a short section of audio. Right now, I re-record the "bad" section in a brand new file and then copy/paste to insert it back into the original Soundbooth file. But it seems Soundbooth should have a more elegant way to do this. Even the audio mixer in the older version of Premier Pro could do this! Where am I going wrong, or what is the best way to do this?
David
www.waterfordarfur.com

That kind of functionality is currently only available from Adobe within Audition - Soundbooth always records non-destructively to a new file.

Similar Messages

How do you "punch in record" in Version CS5.5

I have earlier versions of Adobe, going all the way back to Cool Edit Pro. It was very eash to highlight the section you wanted to record over. You could keep playing until you got one that you liked and select that one to replace the original. I have no idea how to do the same thing in the CS 5.5 version. Any suggestions?

Something like this? http://indesignsecrets.com/branislavs-great-ghost-technique.php

Hardware "recording in session" light with Logic punch in?

Is there any easy hardware solution for having a punch in/recording light for the vocal booth... when I am in record mode in Logic.. or other DAW?
I have a Transport Remote that gets all the signals from it, so has any company made a simple red light type of thing.
Sometimes that visual helps when doing a lot of quick punch work.
I cue the people a lot.
Sometimes not.

I just hate going back and forth from premiere and logic and all the extra time wasted exporting the files so they will work with eachother.
I just thought of something else.... Is there a way that I can get the video in premiere to play the same time I push record in logic pro and maybe sync with it?
Like if I push record in logic the video in premiere will start playing then when I push stop in logic pro it will stop in premiere or at least stay in sync with it so the timing will be right?
if anyone has any ideas throw some out there I would love to hear them.
Thanks!

Punch-In/X-Fade Issue

I hope I can explain this problem clearly...
I have a guitar part that I recorded that had a glitch in my strumming. I did a quick punch-in recording over the glitch. Now I have the Punch-in Region sitting on top of the Original Region. The Punch-in Region is one bar long.
I can adjust the length of the Punch-in Region from the left and right to make a smoother transition out of and back into the Original Region, but I still need to put a little bit of cross-fade at the beginning and end of the Punch-in Region.
When I select the X-Fade tool and click to drag left to right from the Original Region into the Punch-in Region, the Punch-in Region disappears so that I can't accurately gauge where my X-Fade will land. Naturally it's not exactly where it needs to be, but it's close enough (for rock 'n roll, as they say). However, when I try to put an X-Fade at the end of the Punch-in Region going back into the Original Region, the original X-Fade I created at the beginning of the Punch-in Region disappears and the new X-Fade I'm trying to make doesn't even appear!
Alternatively, if I try this in an opposite fashion (dragging right to left from the beginning of the Punch-In Region back into the end of the first part of the Original Region), the X-Fade seems to work; but, when I try to X-Fade from the end of the Punch-In into the beginning of the second part of the Original Region, I only get a fade-out (not a X-Fade).
To make matters worse, in either of the above cases the second part of the Original Region (the part coming out of the Punch-in Region) now doesn't have any sound even though I can see the waveform! I'm totally baffled by this. Has anyone had any similar experiences or success punching-in and applying the X-Fades?
Thanks for any help!

Thanks, David. I tried changing the editing mode to No Overlap (and also to X-Fade) with no luck changing the outcome. Also, over to the left above the channel strip, every time I try to change the Fade-Out parameter to something other than "Out" (i.e. "X" "EqP" or "X S") it keeps reverting back to "Out" automatically. Curious.
Would it be proper to deduce that when recording a punch-in, it's best to set the editing mode to No Overlap before recording?
In any case, I "solved" the problem by moving the punch-in region for a moment and slicing the original region in the area beneath it, then adjusted the two parts of the original region and placed the punch-in back in the slot between them. Fades worked fine then, but of course it was unnecessary extra work I suppose....

Punch in problem

Hi,
I'm doing a voice over session and use the punch in function to continue the recording from a point where a mistake has been made. Strangely when I press record both the old take and the live one can be heard even though I'm clearly 'going over' the old take.
It's been a while since I last did this, but I'm sure it used to be ok. I can't find any setting that might work here.
Cheers
Gerhard

Last night I found out something very odd about Logic's "Punch in on the fly" option.
When I would disable that feature (punch in on the fly) I could still punch in and out, but I would have this hiccup of playback to where it would be silent for a second even though it was still playing and recording. In other words if the artist could sing along and put up with that hiccup, the punch in recording would be okay. Which I think is normal for the software's behavior? BTW the toggle erase button on the transport was also enabled.
BUT, if I do the same with the "PIOTF" enabled it will not work. The only time it will work is if I am a good ways from the previously recorded audio region (in front or behind), and then sometimes that is unpredictable.
I would hate to think that anjamaku is right about being be forced to use input 1 all the time.
The strange thing is, this all of a sudden just started happeing. I have multitracked drums and everything and not had a problem. Then one day the kick drum track would not punch in correctly. Down hill slide since then?

Yet another nasty punch in/out bug

What is this?? Punching in before a region then punching out inside the region DELETES IT! This is in replace mode. Am I missing something here? Check it out:
http://www.youtube.com/watch?v=WqJ4hyYT1Ak

Murray Campbell wrote:
This quote from the 9.02 update page:
+- Flex Markers can align & snap to MIDI notes _Performing a punch-in recording with Replace Mode now behaves correctly_+
Isn't the problem discussed in this thread exactly the bug that 9.02 is supposed to have fixed?
This is not the problem. Replace mode was broken with the release of version 9, but was fixed in the 9.02 update.
The problem we're discussing here, is, the audio region that follows the punch out point often now disappears from the arrange page.

Cycle Record Question

- Short-story - basically I want to use the least amount of button presses during the recording process...
Typical scenario ...
Let's say I have cycle record from bars 1 through bar 4.
- Destructive editing is on
- after recording 4 bars - I decide I want to simply replace bar 3 only.
- if the in and out punch in record was set to bars 3 and 4 then when I go in on bar the three - *it also erases bar 4* ouch - which maybe I wanted to keep...
- is there a way - without resetting the punch in and out to only bar 3 - to not erased bar 4 also...?
- so I know that I could take out the destructive recording - and then manually erase the part I don't like - and then going to record... but that is also a lot of "button pressing"
- it seems as though cycle recording mixed with punch in and punch out could be easier ... maybe there is something I do not understand... any ideas?

Just to add my two cents worth - I use Autodrop all the time and it is an incredibly useful tool for re-recording very precise bits of of midi or audio.
If you are trashing bar 4 of your cycle record when you only mean to replace bar 3 then I am sure that is because the left and right auto drop locators are not set accurately.
Here is my basic methodology for using auto drop:
1 - set up a musically coherent Cycle with key commands " Set left locator" and "set right locator" ie for or 8 bars. ( Very important that you have available a key command that snaps the SPL exactly to the bar).
2 - set up within the broader Cycle and 'inner' recording zone using key commands "Set Left Auto drop" and "Set right auto drop" you can then cycle record to your heart's content in the zone that you really need to replace without messing up anything else.
Also if you choose a musically sensible 'macro cycle" then you have time to think and breath before the sequencer reaches the point that you want to actually record in.
Once you become familiar with this it takes literally seconds to re-record very precise bits of your arrangement

L9: Cycle Record Audio = many passes...(only 2 takes showing)!

Can anyone try cycle record Audio... more than 3 passes in Logic 9?
I'm only getting 2 takes I can access and are listed/showing when I click the triangle . They will show in the Bin, but you would need to flatten and reveal the file to see the other passes & work with them.
Midi seems ok.
http://www.generate-music.com/L9cycletakes_bug.mov
3 different computers have this same weirdness.
For what it's worth... we still can't "punch in record" in cycle mode... without Logic dropping us out after the first pass.
Also, when will they give us a simple "keep last full cycle only" for Audio Record settings?

If I've understood you correctly, the "countdown" you are
describing is just the visual signal to let you know when to
begin
the narration. It sounds like you are saying that you think
the recording is over when it hits "zero", but in fact, when it
hits "0", just begin speaking - and moving the mouse through the
application to create the movie.
All of that is assuming you have first connected and
calibrated your microphone, and that the hardware is working
correctly before you begin.
I disagree with your comment that there is EVER a time when
it might not be best to add audio narration after-the-fact, during
the editing stage. It is just a personal observation, but I believe
the "narration during recording" feature is the biggest mistake int
he history of this great application. It just shouldn't be done -
too much like patting your head and rubbing your stomach
simultaneously - requires coordination skills that are waaaaay
beyond those of the average bear. Create your movie complete with
actions, then during editing, add the audio to the movie. It's
quick, simple, and avoids problems with synchronization of hte
audio and the background changes in the movie ... that's just my
opinion, though ...

HT1006 why when hit the record button I lose the song on my music track for a second or so then the sound returns. I would like to be able to record on the fly while still hearing my accompanyment

guys am new to garageband. I am trying drag a non vocal track into my project, open another vocal track and and record my voice with a mic via my interface. When i hit play I hear the non vocal track, but when I hit record everything stops for a second including the non vocal track and then continue playing, and recording. why cant I record on the fly like other programs. what am I doing wrong. Help is greatly appreciated

GB doesn't offer "punch-in" recording. But you can easily set an earlier recording point, so you can listen to as much as you want from the audio track, and later cut your recorded snippet to the desired length.

Fetch data from one table and insert into two tables in desired format

I have similar to the following data in a table and it is not normalized. The groupID is being used to group two records of similar nature.
DECLARE @OldDoc TABLE (oldDocID INT, groupID INT, deptID INT)
INSERT INTO @OldDoc (oldDocID, groupID) VALUES (1, NULL, 111),(2,NULL,111),(3,1,111),(4,NULL,333),(5,1,222),(6,NULL,333),(7,2,222),(8,2,333),(9,NULL,111),(10,3,222),(11,NULL,333),(12,3,444)
I need to process the data from the above table (@OldDoc) and write into two new tables (@NewDoc and @NewDocGroup) as follows.
oldDocID should be stored as newDocID when inserting to @NewDoc table. Only records with groupID NULL and one record (first one) per group should be considered (For example, oldDocID 5 is not considered as 3 and 5 belong to the same groupID 1) for insertion.
DECLARE @NewDoc TABLE (newDocID INT)
INSERT INTO @NewDoc (newDocID) VALUES (1),(2),(3),(4),(6),(7),(9),(10),(11)
All records from @OldDoc should be considered for insertion into @NewDocGroup table. OldDocID is inserted as NewDocID and deptID is as-is. Instead of groupID, the ID of the first record in the
group should be considered as parentNewDocID (For example, 3 is considered as parentNewDocID for newDocID 5 as 3 and 5 belong to the same groupID in @OldDoc table) for the newDocID.
DECLARE @NewDocGroup (newDocID INT, parentNewDocID INT, deptID INT)
INSERT INTO @NewDocGroup (newDocID, parentNewDocID, deptID) VALUES (1,1,111),(2,2,111),(3,3,111),(4,4,333),(5,3,222),(6,6,333),(7,7,222),(8,7,333),(9,9,111),(10,10,222),(11,11,333),(12,10,444)
How do I accomplish the above using SQL ? Thanks for the help.

>> I have similar to the following data in a table and it is not normalized. The group_id is being used to group two records [sic] of similar nature. <<
Rows are not records. Tables have to have a key by definition. You do not do math with identifiers, so they should not be numeric. Let's ignore that error for now. In short, you are posting garbage. If you had followed Forum Netiquette, would you have posted
this?
CREATE TABLE Old_Documents
(old_doc_id INTEGER NOT NULL PRIMARY KEY,
group_id INTEGER,
dept_nbr INTEGER NOT NULL
REFERENCES Departments (dept_nbr));
INSERT INTO Old_Documents(old_doc_id, group_id, dept_nbr)
VALUES (1, NULL, 111),
(2, NULL, 111),
(3, 1, 111),
(4, NULL, 333),
(5, 1, 222),
(6, NULL, 333),
(7, 2, 222),
(8, 2, 333),
(9, NULL, 111),
(10, 3, 222),
(11, NULL, 333),
(12, 3, 444);
>> I need to process the data from the above table (Old_Documents) and write into two new tables (New_Documents and New_Documents_Groups) as follows. <<
Just like punch cards and mag tape data processing! Being old and being new are a status, not another kind of entity. But that is how mag tapes work. And you even use the verb "fetch" from tape files. This design flaw is called attribute splitting.
Do you have a Male_Personnel and Female_Personnel table? NO! It is just Personnel!
>> old_doc_id should be stored as new_doc_id when inserting to New_Documents table. Only records [sic] with group_id NULL and one record [sic] (first [sic; no ordering in a table] one) per group should be considered (For example, old_doc_id 5 is not considered
as 3 and 5 belong to the same group_id =1) for insertion. <<
Think about your punch card mindset. Why did you physically materialize that redundant New_Documents table? Let me answer that: this is how you work with punch cards! In SQL we use a VIEW:
CREATE VIEW New_Documents (new_doc_id)
AS
SELECT old_doc_id
FROM Old_Documents;
>> All records [sic] from Old_Documents should be considered for insertion into New_Documents_Groups table. The old_doc_id is inserted as new_doc_id and dept_nbr is as-is. Instead of group_id, the ID [sic: which identifier??] of the first [sic: tables
have no ordering like a deck of punch cards] record [sic] in the group should be considered as parent_new_doc_id (For example, 3 is considered as parent_new_doc_id for new_doc_id 5 as 3 and 5 belong to the same group_id in Old_Documents table) for the new_doc_id.
<<
Why not use 5 as the parent? My guess is that you are trying to form equivalence classes. See:
https://www.simple-talk.com/content/print.aspx?article=2020
--CELKO-- Books in Celko Series for Morgan-Kaufmann Publishing: Analytics and OLAP in SQL / Data and Databases: Concepts in Practice Data / Measurements and Standards in SQL SQL for Smarties / SQL Programming Style / SQL Puzzles and Answers / Thinking
in Sets / Trees and Hierarchies in SQL

Logic Studio on a MacBook

Hi I'm looking to purchase a MacBook to run Logic Studio. Is this a good idea from the performance point of view? If so, what is the minimum model I should be looking at? - John.

I am a Macbook user and I am running Logic Studio 9. (legit purchased copy, not pirated) I am using a presonus firestudio (firewire interface) and an external 1tb 7200 rpm firewire hardrive.
Logic studio does run on my computer. Let me say that I have just completely reformatted my hard drive with snow leopard and it is completely clean. I am still on my first mac which I bought Oct 2008. I used garageband for several months before stepping into logic. I LOVE Logic studio it is awesome.
NOTE - you should probably ask your friend why it is he wants logic studio. Garageband does a lot, and it will take you awhile to progress outside of its limits to need a program like logic studio. (garageband is also stock on macs)
While I love all my studio's capabilities, and I have a blast, I run into several performance issues. When I have a template set up with several plugins, I run into problems with latency all over. I have a presonus fader controller with a footswitch for punch-in recording, and I experience latency with it. At times my digital software mixer quits unexpectedly. I suspect that if I had a computer with a bigger processor, I wouldn't see these problems. Although, looking at even the 17" macbook pro specs, it still doesn't seem that much more powerful. My suggestion is that if you want your software to run as efficiently as possible, get the best macbook you can afford, but don't fret about it too much because all of the new ones will support it. As said here before, make sure it is equipt with firewire. I am leaning towards purchasing an iMac for at home where I do most of my stuff, and keeping my Macbook to take around and using live.

Logic Pro 9.0.1 released

This update improves overall stability and provides numerous fixes and enhancements.
Issues addressed include:
• Flex Markers can align & snap to MIDI notes
• Performing a punch-in recording with Replace Mode now behaves correctly
• The I/O plug-in adds an option for latency compensation
The update is recommended for all users of Logic Pro 9.

Logic Pro 9.0.1 Update
This update improves overall stability, provides numerous fixes and enhancements, and is recommended for all users of Logic Pro 9.
Some issues addressed include (but are not limited to):
* Replace mode now functions as expected when Punch Recording.
* Trimming a region now behaves correctly for regions whose first transient is quantized.
* Using "Paste at Original Position" in the Arrange window now works as expected.
* Using track import Replace to channel strip used on multiple tracks in the Arrange window now works as expected.
* Correct automation values are now maintained when one region is moved over another with the "Move Automation with Regions" option.
* Addresses an issue where the Save button on a Logic/Mackie Control stays lit when pressed with some projects.
* The Reassign Track shortcut menu now correctly displays the currently assigned channel strip object.
* Text Only mode for the Toolbar now remains in effect when an option is clicked on the Toolbar.
* MIDI commands can now be assigned to key commands with fixed assignments.
* Clicking solo on a channel strip no longer selects the channel strip.
* Fixes an issue where Logic would quit unexpectedly if the grid value in the Hyper Edit Convert Event definition dialog was changed.
* MIDI regions now play at the correct tempo when scrubbed with the Solo tool.
* Current project Mixer settings are now correctly maintained when importing tracks with "Send all fader values" enabled.
* EXS24 now correctly displays all parameters in Editor view for instruments created in Logic 8.
* Logic no longer quits unexpectedly in recording situations where both a MIDI and audio track are record enabled and the MIDI track is not selected.
Enhancements implemented include:
* It is now possible to measure and provide latency compensation for an external signal chain that is routed via the I/O plug-in.
* You can now snap align Flex Markers to MIDI notes within other tracks in the Arrange window.
* The Automap feature for Novation MIDI controllers now functions when using the Logic Studio plug-ins.
* Apogee's UV-22 dithering algorithm now an option when bouncing audio files.

Saving MIDI edits in GB3 - is it possible?

Don't see any obvious way via Save/Save As options. Love how easy it is to edit MIDI in GB, ashame you can't save it in anything other than proprietary GB .band or as an iTunes/iPod file... ;-( And is there a way to play an imported .mid through an external MIDI controller - ie: a Roland percussion sound module? In my book, the two most important feature requests for GB4. Any suggestions/workarounds (w/out shelling out 300 clams for Logic Express?)
Thanks!

Thanks for the reply, Christoph. Kind of what I was afraid of - sounds like I need to step up to a real sequencer app like Logic for this type of MIDI functionality. Have you worked w/ Logic Express? Can you do punch/step recording w/it? Are there are other MIDI-specific Mac apps that simply let you record, edit and playback MIDI files - that's all I really want to do.
Thanks.

Why can I not see

Recording audio in Logic Pro: Why do I not see the audio waves when recording normally? Only with punch-in recording I can see them..

Recording audio in Logic Pro: Why do I not see the audio waves when recording normally? Only with punch-in recording I can see them..

Is this feature still present?

There was a feature I ran into in Logic years ago that worked as follows:
say you launch logic and are noodling, not in record or anything, and all of a sudden you play something you love and want that on a track, so there's an option to take what you just played and open it up on a track, because Logic is always "listening" and just dumps the contents of a buffer onto the track.
I can't remember what enabled this feature then, or if it's still there now - but the event counter in the transport window seems to indicate it should still work....
Any ideas?
Thanks
Richard

You kinda can for audio, as long as you have punch in recording enabled, you can be noodling along in play (with a track record enabled of course and then hit record. It will appear to start recording at the point at which you hit rec. However, if you grab the left bottom corner of the resulting region, you will be able to drag it open, back to the point at which you hit 'play'... Cool huh?

Punch-in recording

Similar Messages

Maybe you are looking for