Isaac Halasima
Forum Replies Created
-
I’m pretty sure there is a way to do it because I think I’ve done it a couple times on accident. Holding “Shift” while adjusting a Video track, does all video tracks, and adjusting audio does the same… but that’s too much for me.
I like it tight and clean though, so for me I kind of have this little deal I do, which involves creating a hot key. I always have them collapsed. To expand quick, if you double click to the right of the “S” button on audio tracks or the eye on video tracks, it’ll open them up to whatever predetermined size the adobe peeps decided was enough for us to see everything we need. You can change how big they pop open to in preferences.
But to close it all fast, I made a hot-key for the “Minimize All Tracks”option in the “Keyboard Layout” window. It’s not a hot-key that comes with Premiere, so you come up with your own combo (I use “option+tab”). But that way I can open tracks I want quick with some double clicks, and close it down with one swipe on the keyboard. Just nice to keep it looking as clean as I possibly can as I cut.
T. Isaac Halasima
isaachalasima.com -
Yeah, I’ve definitely had that one happen quite a few times.
When I’m in a hurry and feel like gambling, I throw a filter on the audio clip and zero out the adjustments. Your justifying to force Premiere into completely rendering audio (which it doesn’t like to do) and dump whatever glitchy render file, or what not, has jacked it up.
If you have more time, kill the render files of the entire sequence, the most effective for me has been when I lifted the entire edit off the sequence and pasted it on a new fresh one (weird how often that one works). But remember to match how many tracks there are, and turn on all the blue “Track Targeting” buttons, on top of the tracks numbers. Otherwise you may not recognize what lands on your sequence after you paste.
The best thing to do though, is look for any audio that isn’t a WAV, convert it, then replace the spot on the sequence. If you have automation you can just “paste Attributes” to retain the settings. But really cleaning up the edit and how many clips may overlap each other, is how I’ve eliminated the problem. Sometimes it’s not possible, but if you can get to no more than 3 audio files overlapping at once, it usually won’t do that. And yeah, it it isn’t all WAV or AIF those problems seem to sneak up pretty consistently, Especially if there’s a bunch of clips on the sequence.
Audio used to beat up FCP 7 too. I’ve crashed them all. The only one that haven’t crashed with a direct connection to audio was Avid. But I still prefer Premiere in the end.
T. Isaac Halasima
https://www.vimeo.com/user1134661/videos -
Mine just started doing that too… and it’s around the cruddy compressed audio clips go figure (why do people still give me mp3 files?… not like we still use floppy disks). Audio has beat the snot out of me in Premiere, more than I think it should. But I still remember audio glitches being way more devastating in FCP 7.
The hard drives play into it too. Granted, knowing I’m on a mac, I know with a bushel of HD’s running a project my computer would seem to go out of it’s way to try and rest drives, causing all kinds of havoc. Which includes the phantom starting points on the sequence after pushing play, and one of my favorites… the complete freeze on the monitor and computer while the audio still finishes the sequence. It gives you a moment to wonder how long it’s been since you saved. Making the moment you finally hit “Force Quit” so painful.
On my mac, that system preference has been turned off for years and I’d delete that option if I could. I just haven’t touched windows since Bush beat Gore, and have no idea what kind of energy savers it might have.. But everybody’s right to point to audio, right off the bat. If it isn’t a WAV, you can almost count on something strange eventually happening. That’s how I got the the quick finger action for Command+S, as a weird and constant nervous twitch.
Isaac Halasima
OS X El Capitan
iMac (Retina 5k, 27-inch, Late 2015)
4GHz Intel Core i7
64 GB 1867 MHz DDR3
AMD Radeon R9 M395X 4096 MBisaachalasima.com
-
Warning… I’m on day 4 of no sleep or sun while editing a long narrative… so I may get wordy. But have you checked your RAM? And are the hard drives that you’re cutting from spinning all right? Or if they’re solid state are they hot? I know it probably sounds crazy and not what a lot of people want to think of, but I just survived a nightmare because of RAM that had gone bad. Luckily I didn’t loose my entire computer to RAM slowly destroying my computer, like one of my friends just dealt with as his souped up iMac died slowly in front of him one day.
— Sorry, just looked at what I wrote, and I’m definitely deeper into “cutting a narrative,” and storyteller mode, than I realized —
But I ran into a very similar problem with a monster ad campaign I was finishing up a couple months ago. After 3 all-nighters I just exported to a drive and headed to deliver. I got lucky when I was randomly given extra time and had to wait, so I figured, might as well watch before handing it to my client. And… I mean, I’ve lost audio randomly while watching sections of sequences during edits, only to have it come back when I played again… no surprise… but after an export, from a sequence I knew was rendered correctly before final export? I was getting horrifying audio drops maybe a second long at the most, but all while our most expensive actor was on camera. During the last days of cutting, one thing I did notice was I’d get weird audio activity and glitches around any music that wasn’t recompressed to a WAV or AIF. Sometimes giving the loudest possible pops and screeches, that I was sure blew the speakers when I’d be scrubbing the timeline. I also had random glitches in sections where i had done a lot of clean up on the audio, or tons of it stacked (right now I’ve got 60 audio tracks on this movie I’m trying to survive).
Blah, blah, blah, the glitches and drops were inconsistent enough that I figured it had to be the temporary memory. Like I said, my good friend had his entire system go down for good because of cheap RAM, and it nearly killed him, so I’m always thinking RAM. Since I was under the gun to deliver, and was feeling pretty solid on my theory of RAM (he and I had buy RAM from the same place). I changed the memory setting, to max what I could out of the 32 GB’s, but, 3 straight times, it would quit exporting the file after about 30 minutes of pretending like I was going to work. Luckily I’m OCD when I cut because. I keep dialogue, b-roll sound, audio FX, and music patched into separate submixes at all times. And I figured I had to strip the sequence. So I exported the submixes separately, laid them on a new timeline, and exported with “Use Previews” turned off. And 6 hours after I thought I was delivering, I finally handed the drive off… client was ticked, but after 6 months of working on it and way way way more money spent than I would make in the next 3 years, I figured 6 hours was worth it.
Anyway, after all that high stress, I ripped out that RAM from my iMac and gave it a fiery Viking funeral. Then immediately bit the bullet and maxed my computer with 64 GB’s of whatever cost a lot (not smart… but I was still shell-shocked). And now, considering this flick I’m finishing is the biggest sequence I’ve ever cut on (a total of 60 tracks on a 2 hour sequence, with 16 TB’s of RED Raw and Lexa footage (granted, that blessed footage is in computer lovin’ ProRes), all spread out on 4 daisy-chained hard drives… I feel like I’ve thrown the computer back into a mine field while it plays a game of Russian roulette by itself… but the thing runs smoother than it ever has, and no more glitches (well an Mp3 just screeched at me, so I’m recompressing it). Thank heavens that the peeps at Apple made it surprisingly easy to replace… well… the only think you can replace on an iMac. I’m fully convinced it was the RAM that started all that for me. And I hate to say it, but I just take the high-priced kick in the crotch from Apple now on RAM… just as long as I don’t have to do that again.. brutal. Well, not blue-collar, working in a steel plant, nearly dying while melting rocks into metal brutal… like my Dad will remind me… but rough.
Yep… got wordy… I need to go to bed.
Isaac Halasima
OS X El Capitan
iMac (Retina 5k, 27-inch, late 2015)
4 GHz Intel Core i7
AMD Radeon R9 M395X 4096 MBisaachalaisma.com