GPearce10
Explorer
GPearce10
Explorer
Activity
‎May 05, 2024
03:14 PM
😀
... View more
‎Mar 04, 2022
04:20 AM
Thanks for the tip on global sfx removal. That will be a big help next time. Meanwhile, I did export the audio, process it (using Reaper) and re-import it to get the job done.
... View more
‎Feb 26, 2022
09:55 AM
I'll look into that, thanks. I started NLE on Avid (the first 'real' NLE for broadcast). When I went freelance, I got to 'experience' a few others that seemed disappointing... but a good share of that was they were just different, and I had to reorient my thinking to see their way of doing things. But there was also a fair amount of 'how do I do this? You can't. How do I to that? You can't'. Premiere Pro was very Avid-like, on purpose I'm sure, and probably because Adobe hired a bunch of Avid programmers. Version 1.5 was fairly terrible, but I produced some shows (eventually) on it. I don't even remember the last version number I upgraded to, but it was getting very good. So I've always been reluctant to try Brand X editors, and also "I'm not gonna pay a lot for this muffler". I probalby would have continued upgrading Pro as a 'you own it' standalone, but the subscription isn't affordable without income. Off to 'solve' my audio issue. I will (tediously) remove the Dynamic effect from each of a couple hundred clips, one at a time. Then I'll export the audio, run it through a DAW called Reaper to compress and balance it, and re-import it. At least that's the plan. I was tempted to see if there was a different dynamics effect, but then I realized that ALL of the audio effects were going offline, not just Dynamics. Back to work. Thanks for your interest! - Gary
... View more
‎Feb 25, 2022
06:12 PM
First... my workaround failed. All the edits seemed to have the effect applied, but when I rendered it out and played the rendered file in VLC, the compression was missing from maybe half of the edited clips. And when I looked at them back in Elements, sure enough they were offline. And this was with my magic 1080 clip in both the Project Assets and in the timeline. So back to square one on that. I have been around the block enough times to know that it's impossible to make bug-free software (at least complex software), and the wide variety of configurations of Windows machines means some incompatabilites are inevitable and can't be fixed because no company can afford to investigate and solve problems at that individual machine level. And I get that a problem forum will collect dozens to hundreds of users with what is apparently the same problem, but that is still a tiny percentage of users. That is cold comfort when you as an individual user are experiencing 100% of a problem that is a game-stopper on a project with a deadline. The project I'm working on is a freebie that I can just give up on, but across my career I've pulled many all-nighters finding solutions and then redoing hours of work once I did, for clients who were paying big bucks with tight deadlines. The memories remain bitter. And I'm left with the notion that I'm runing the same hardware that ran Pro pretty darn well, but Elements has thrown me curve after curve, either with glitches or limited design. Your question about 'too many clicks': Here's an edit in my timeline: You can see that the video is offset from the audio by a half second or so. To achieve that edit in Pro, I would need to hold the ALT key down (to temporarily separate the audio from the video), and use the 'double roller' tool (selected by hitting one key) to slide the edit left or right. Nothing ripples. An added benefit is that the monitor window 'doubles' to show what video is at the edit point on both sides of the edit. In Elements, I have to Alt+Click the video on one side of the edit (again to temporarily separate the audio from the video), then Shift+Click and drag that one side of the edit so it doesn't ripple. That leaves a hole in the timeline that Elements tries desparately to fill by rippling, but for the Shift+Click and drag. Then I have to Alt+Click on the video on the other side of the edit (to temporarily separate audio/video), and Shift+Click and drag that video to close up the gap. So to summarize in Pro, it's Alt+Click and drag. In Elements it's Alt+Click, Shift+Click and drag, Alt+Click, Shift+Click and drag. Here's another issue I haven't described: My goal is to cut a few seconds out of a clip. In Pro, it's Mark In, Mark Out, Lift, all with specialized keyboard functions. In Elements, there is no Mark In / Mark Out, so I find my 'In' point and click on the little sissor icon in the timeline to split the clip. I can then do the same at the 'Out' point, and delete the piece I want to cut out. Now I do want a ripple, so the Backspace key will do that. Not to hard, and it works. What doesn't always work is the other way to do this: split a clip at just the In point, then click and drag the 'handle' across the footage I want to delete until I reach the spot I want to keep. After I've been editing a while, that click and drag stops working. A brown outline of the area to be deleted jumps around. It's probably not random, but it seems like it. The Escape key doesn't clear this outline. A few mouse clicks seems to clear it, but it may take a random piece of footage with it, requiring an Undo to repair the damage. The process to split clips at the 'In' and 'Out' points works efficiently enough for fairly gross edits, but the click and slide method is much better for fine trims of a few frames. When it works. And it's slightly more efficient for edits covering several seconds. So, tomorrow I try to rescue my project before I give up on it. If Elements has a method to delete effects in multiple selected clips (or all of them), experimenting would be easier. I have a hundred or more edited clips, and some have good effects and some have 'offline' effects, and unless I'm missing something, I have to delete them one clip at a time. There is a way to copy and effect and apply it to multiple clips. And none of this would be an issue if I could apply an effect to a track instead of individual clips. But then feature by feature, we are turning Elements into Pro, something Adobe surely doesn't want to do.
... View more
‎Feb 25, 2022
11:49 AM
Thanks for the reply. Adobe 'removed' this particular audio compressor from Pro a few years ago, but it remained in a 'legacy' folder. I always found it to the the easiest to use, giving the most clear feedback on what the adjustments were doing (the little bar at the top that shows how much an audio peak was being compressed). So I continued to live dangerously and use it. My best guess is that it was a licensing issue rather than someone thinking they had a better tool, but who the people who know aren't talking... or at least I haven't heard them. As for being 'crappy' - that comes from my long history of using fairly early versions of editing software (Media Composer, Premiere 1.5) that crashed a lot, or had features that wouldn't work reliably. Some of it was bad user interface or bad implementation of things that otherwise did work but were hard to use, or obviously needed features that were missing. And over time, things stabilized, features were improved, and crashes were rare. (Although I have noted that some software seemed to 'get better' the more I used it and understood it.) Also, while things may be working pretty well for me, there are plenty of people who are still having problems, filing bug reports and filling up the forums. As for Elements, I'm having the 'stops randomly while playing' issue that a forum thread on that topic has been going for 5 years. I'm hoping this 'effect offline' issue is a one-off. My main gripe with the way it's designed is that it is way too aggressive in rippling the timeline when I adjust a clip. It takes way to many clicks to trim a video edit a few frames one way or the other without rippling the timeline. You'll find the 'double roller' option in Pro a very useful tool. I expect the 'it gets better the more I use it' experience to apply to Elements over time, but some things ought to work better now.
... View more
‎Feb 25, 2022
10:09 AM
Workaround Solution: I added a video clip from another project (a 1080p camera video clip) to the Project Assets of my test and original project. After Saving, Closing and Opening the project, the 'offline' audio effects all became 'online' again. Read below for a play-by-play of my troubleshooting steps: The next morning (and we're now in Play by Play Troubleshooting mode) The source video I've been using came from a Zoom cloud recording. It's a 720p .mp4 file. A test I did a few minutes before starting today's log indicates that may be key, but I don't see why (yet?). I started another new project (Offline Effect Test 2), but this time with different footage from a video camera, 1080p. I added the audio effect, closed and re-opened Elements. The effect was still present in the timeline. It had not 'gone offline'. I added the video from my Zoom meeting to that new project, and tagged it to the end of the timeline. Then I added the audio effect to that clip. Close, re-open... the effect is still there! On the 'bad' video clip. Now we're getting into 'workaround' territory, at least. I start a third new project (Offline Effect Test 3). First, I just bring in my Zoom meeting footage, and apply the audio effect. Close (Save), Open, Effect Offline. I bring that 1080p camera footage into this project.. add it to the end of the timeline add the audio effect so far, the audio effect on the Zoom clip is still offline Close (Save), Open.... drumroll.... The effect is still there on both clips! definately in workaround territory. I re-run this test as Offline Effect Test 4. Same result - the effect has not gone offline. Curious, I delete the 1080 footage from the timeline and the Project Assets. Close (Save), Open, and the effect is still there. Risking all, I make a few edits, just to manipulate the timeline some. Close, Open, Weirdness: I edited the footage into three clips. The effect is offline on two of the clips and online (present) on the third clip. I add back a 1080 clip. I do not add an audio effect to that clip Close, Open, and the effect is present on all three Zoom clips. I delete the 1080 clip from the timeline and Project Assets box again. Close, Open, still there in the Zoom media, all three edits. Add another edit (1080 media still out of the project). Close, Open, effect is present in clips 1, 2 and 4, but missing from 3. Next, added a 1080 clip to the Project Assets, but not the timeline. Close, Open... effect is present in all edited clips!!! I think we have a workaround. Holding breath, opening original project... I had made a few dozen edits to the original, single Zoom 720 media file. Some still had offline effects, and some still had online effects. Most had no effect, but I don't really remember the quick screwing around that I had done while still in WTF mode. So I deleted the offline and online effects in all but the first few edits (tediously, clip by clip). I left the (offline) effects in the first few clips to see what happened when I added a 1080p clip to the project. Close, Open, and all the offline effects I had left in the first few edits came back to life. To review: Audio effects clips went 'offline' when I closed and re-opened a project with footage saved and downloaded from the Zoom cloud. Other Elements projects, including one with a different Zoom cloud video clip, continue to work properly. Adding a 'good' clip to the project (a 1080p clip from a video camera) fixed whatever was glitching in the program. After adding that 1080 clip to the Project Assets - and not necessarily to the timeline... ... then closing and re-opening the project... ... restored all the 'offline' audio effects. So, back to work. Finally.
... View more
‎Feb 24, 2022
07:32 PM
Premiere Elements 2021 version 19.0 running on Windows 10, running in Expert mode. Beginning a new project, I applied an audio effect (a compressor) to a 30 minute clip, then began editing the clip to remove pauses, 'uhs', etc. I disconnected my network connection because I was having a problem with playback stopping by itself frequently enough to be irritating. A forum post suggested trying that. It seemed to help, at least after a few minutes. I closed the project to take a break. When I reopened the project (internet still disconnected), the audio sounded low. I checked for the compressor, and under 'Applied Effects', the box where the compressor effect should be read Offline (filter unavailable) Hmmm, OK the internet was disconnected. Was this effect looking for a network connection for some reason? I reconnected the network cable, half expecting the effect to magically reappear. It didn't. I closed the project, reopened it... still Offline (effect unavailable) I rebooted the PC. No help. I searched the forum for the keywords "Applied Effects" "Offline (filter unavailable)". I didn't find anything specifically germane, but one post mentioned something about that issue, and noted that the user reapplied an effect, but when they closed the project and reopened it, the effect was Offline again. I deleted that 'effect' with the trash icon, and reapplied the effect. I closed the project, and reopened it. The effect was Offline again for me, too. I opened an early version of the project from the Auto-Save folder. This version was very early, after I had applied the compressor effect to the long clip, and before I began editing it. The effect was Offline here, too. Next, I created a completely new project. I applied my compressor effect I closed the project, and reopened it The effect was Offline!! I applied a video effect (a blur) Close, reopen.. the blur is still there It occured to me that I was using a 'My Presets' saved effect. So I deleted the 'offline' effect (I'm still in the 'new' project) and applied the 'original' version of the effect from the FX panel Close, reopen the project (close Premiere Elements completely, not just reselecting a project) The 'new' effect was Offline!! (OK, that surprised me) I deleted the Offline compressor, and applied a lowpass filter, just to try a different effect. confidence level: low Offline!! (low confidence justified) Opened an 'old' project (from a week ago) that used the same compressor effect (ALL my projects use that compressor effect, if they have any audio in them) You're guessing 'Offline', but nope, the compressor was there! 10:30 PM. Wife wants me to come watch TV. So over to you guys.... I'll get back to beating my head against this tomorrow. (BTW, and for the record, I'm a retired video editor with 45 years experience, with nonlinear editing starting with Avid Media Composer (I mistyped 'Composter' at first and almost left it) in 1995, and Premiere Pro since 2005, so I know what crappy, buggy software is and does. Premiere Pro started getting pretty reliable, but I can't do the monthly subscription for simple home/free projects. I was hoping Elements would be a good product (because 2021), but it's turning out to be pretty crappy. I don't think Adobe cares much about it.
... View more
‎Jun 14, 2021
08:49 AM
1 Upvote
Using the scroll bar has some limits. I've zoomed in tight for some fine audio editing, and using that bar sends my timeline flying. A more granular method is to click on an empty track (if there is one), then drag off the edge of the screen. That scrolls the timeline in a more controlled manner. That said, count me among those who would like the scroll wheel (with a modifier key) to scroll horizontally, and, with a different modifier key, to zoom in and out. I've recently 'downgraded' from Pro, which I used for years. I've retired, and while I'd like the full capability of Pro, I can't justify the expense. I work on mosly 'home movie' projects now. And I don't expect Elements to do it all. But timeline scrolling and zooming seems basic enough. I will add a bit of a rant about too much handholding in 'expert' mode. I haven't figured out how to stop all the rippling when I move a clip along the timeline. But that's a complaint for a different thread.
... View more
‎Nov 18, 2017
12:03 PM
My problem / symptoms are similar, but I'll note the differences here: I'm scanning from an Epson XP-830. If I use only the Adobe tools to scan, it works every time. But the scanner's interface has more granular control of the parameters of the scan. So I prefer to use that. If I select Scan Using / My Custom Settings (show scanner's user interface) it becomes intermittent. Sometimes it works, sometimes it fails. When it fails, it always completes running the mechanics. Then: sometimes it hangs with the Enhance Scans tab up until I manually 'crash' it with Task Manager. Sometimes it crashes to something like the scanner has stopped working and closes itself. Scans using the Epson scan software also always work. Then I get the granular control of the scan, but more than half the time I want to add pages to an existing PDF document. That function isn't available from the Epson scan softwere so there are extra steps to merge the new scan with the original PDF. SYSTEM INFO: The Epson drivers are current. The Acrobat program is updated to 18.009.20044. The operating system is a current Windows 10 PRO version 1703
... View more
‎Nov 08, 2017
02:32 PM
Memory problem? All the RAM got gobbled up after a few minutes. I installed 2018 (Windows 10), upgraded the project I was working on and started editing. Within a few minutes, it bogged down, then froze... not just Premiere Pro, but the whole PC. Cursor frozen, keyboard frozen, mouse (new Wacom tablet) frozen... had to do a hard reset of the PC. Tried again, froze again, but then I noticed that every 10 or 15 seconds, something jumped. The cursor, or an open window, or something even in Premiere. I checked to see if I had slipped back to Windows 95. Another hard reboot, and I opened the Task Manager and launched Premiere. Was the CPU maxed? Nope... but I watched memory usage climb until my 24 GB of memory was gone, and everything stalled again (no kidding). Reboot (hard punch out again) and relaunch Premiere, and checked that Memory was set for 16 GB limit. It climbed through that while I watched, and I shut it down before it could stall the PC again. So I went back to the Cloud manager and reinstalled CC 2017. That's working (and I'm working). RAM use is between 8 and 10 GB again. One last comment on all the VR stuff. I know Adobe has to go there, but it'll never (never say never? Well, not my small biz) use it. Kinda wish they'd developed a separate app - PremiereVR - for that. Of course, I don't know how feasible that would have been, but I'm hoping I'm not paying a lot (in $ and bloat) for it.
... View more
‎Oct 17, 2017
10:43 AM
Your comment showed up below a longer quote, so I didn't see it until I'd already sent my comment. And my dog ate my homework.
... View more
‎Oct 17, 2017
09:44 AM
Make sure 'continuous scrolling' is turned off. Page scrolling is OK. My recently updated CC2017 continues to lock up in 'play' (not necessarily Fast Play) if I have continuous scrolling on. Note that the setting has moved to Edit/Preferences/Timeline in the newest update.
... View more
‎Sep 29, 2017
06:19 PM
I get the idea of being able to move projects to Audition, and with the 'obsolete' effects, the editor can't do that. I don't use Audition. I do all my audio in Premiere Pro, and it does everything I need. If I did use Audition, I'd still want it to have all the audio metering that audio engineers have relied on for decades. Or perhaps someone can point me to a good tutorial on setting threshold levels without being able to see the effect on the amount of compression being applied. Again.. old dog.
... View more
‎Sep 29, 2017
06:11 PM
Similar issue, but my problem seems to happen mostly when I'm adding a scan to an existing PDF. Changing to different user worked, and the scan completed quickly (it seems to take several seconds to complete if it completes without crashing on the original user account). So what steps should I take to get it to work on the account I use daily?
... View more
‎Jul 22, 2017
05:35 PM
Turning off scrolling fixes it for me.
... View more
‎Apr 22, 2017
07:58 AM
Here's how I competed the Feature/Bug form: How would you like the feature to work? I'd like it to work just as it always did... just not be on the chopping block. Why is this feature important to you? First: I need meters. Especially the Compressor and Expander meters that help me set the threshold for the effect. And overall level meter doesn't provide that feedback. Second: this tool puts the four audio tools I rely on daily (Gate, Compressor, Expander, Limiter) in one, easy to adjust panel. They all affect each other. Yes, I rely on my ear to ultimately judge the result of the settings. The metering gets me there faster. When I looked at the new dynamics tools, my first reaction was "Where are the meters?". I assumed I wasn't looking in the right place. But I never found them. I'm not opposed to learning new things, but I've got work to do. Is there a good reason to drop the "obsolete" tools? Is there a good tutorial to teach this old dog a new trick?
... View more
‎Feb 01, 2017
09:57 AM
Turning off Smooth Scrolling worked for me. I'm answering this all the way in February 2017, running CC 2017.0.2. If I had Smooth Scrolling on, I'd lose control within seconds. Turning audio waveforms off brought me back to 'sluggish' control - Multicam switching happened a second or three after I pressed the button, as did stopping. So betterish, but really still useless. I can still use Page Scrolling - with audio waveforms on - so the timeline at least keeps up, and things work OK.
... View more
‎Dec 04, 2016
10:11 AM
3 Upvotes
I started running into this when I upgraded to CC. Never had it in CS6. I just found a fix for me. I'll offer it as something to try. I have a closing sequence that I put on the end of all my shows. Here's an example on YouTube. It'll just take a few seconds to watch. It's not complex, but it does take two nested sequences, and I dissolve into the final composite. The render error started hitting the last frame of the dissolve. The fix was to just make that dissolve one frame longer. Here's a simple look at my timeline. First, the render failed at the end of the dissolve (note the green/red transition). Make the dissolve one frame longer, and the render succeeds: TROUBLESHOOTING TECHNIQUE: I first found the failure at the end of a 90 minute render in Adobe Media Encoder (AME). That created a log file with the time code of the error. So I zoomed into that spot and experimented by setting the Work Area bar around the problem spot and doing a Sequence/Render entire work area. Something else that worked was to render up to the error, then set the Work area bar a few frames after the error and render another second or two. Then I moved the Work area bar into the unrendered spot, made it one frame long, and rendered one frame at a time. For some reason that worked, and if I did my output with "Use Previews" checked, the final render worked. I'd say there's still something wrong with Premiere Pro causing this error. Nothing in my timeline was that unusual or complex. So I wonder when it'll bite me again.
... View more