[Brett Nelson]

Nevermind. I answered my own question. The Ripple Tool has no problem with transitions. I had a specific clip issue.

[Brett Nelson]

After more digging, I found what was probably where I should have started…if I had known/remembered. I cleared my media cache by renaming my Adobe Common folder: https://forums.adobe.com/thread/2152942

Before this, I had already created a new media cache folder, but that did not solve the problem. I had also tried renaming my media folder and that also did not solve the problem. Renaming my Adobe Common folder and forcing PPro to create a new Common was the golden ticket.

Brett

[Brett Nelson]

I’m having the same issue. I’ve seen threads with previous versions of PPro but I personally only started having the problem with PPro 2018. Deleting the cache files did not resolve the problem. It seems like making the clips offline and then re-linking them should solve the problem but it doesn’t. Or maybe there could be a reset attributes option that forced importing the clip without changing the sequence. I’m not sure if this makes sense but this seems like a bug.

I count on my projects to be backwards compatible. I will go back a number of years to grab old footage. To simply not be able to re-link those assets is a big problem.

Brett

[Brett Nelson]

Thanks, Alex. I’m going to look further and see if I can find a solution.

It seems like there should at least be a choice of whether to look for original bins or create a new one. This something that was great about FCP 7. It was very simple to share sequences.

This probably my biggest frustration with PPro. I work with multiple editors and am often exchanging sequences. Adding a bin everytime means adding many extra bins and sequence links I don’t want. I was very excited about Adobe Anywhere until I learned it is not intended for mere mortals. I don’t know why they even advertise it. How many PPro users will ever use it? It’s cost prohibitive. Hopefully that will change.

Anyway, thanks to all for the input. I’ll report back if I find anything.

Brett

[Brett Nelson]

Alex,
I had high hopes it would…but it’s the same results. It creates duplicate bins. When I import a sequence from a copied project on the same system, I do not get extra bins. Only when I cross over from one computer to another.

I’m wondering if I should have my Media Cache in my project folder rather than on my system drive? I know this is not recommended. The problem with that is my Cache then needs to be changed manually with each change of project.

thanks,

Brett

[Brett Nelson]

Hmmm. I must be missing something in my process. Bear with me, and let me see if I understand. You start with Computer 1. You create a project called Project A and create Bin A. You import media into Bin A. You create Sequence A. You use clips from Bin A in Sequence A. You save Project A.

You copy Project A with media to Computer 2. You open Project A on Computer 2. You open Project A on Computer 2. You duplicate Sequence A and start editing on Sequence A Duplicate. You save Project A on Computer 2 as Project B. You copy Project B to Computer 1. You then open Project A on Computer 1 and choose Import. You choose Project B from the Open screen. That brings up a dialogue that says Import Project. You choose Import Selected Sequences. You choose Sequence A Duplicate. It opens in Project A and only brings in a single sequence. No new bin. Is this right?

When I do the above, I get my Sequence A Duplicate but also a new bin called Bin A 01 It contains all the clips in Sequence A Duplicate. The actual media is unchanged and no re-conforming happens but I don’t want that new bin. Also, the clips in Sequence A Duplicate now reference to Bin A 01 rather than Bin A.

Am I doing something wrong?

thanks!

Brett

[Brett Nelson]

Thanks for the test. I don’t import any new footage or media, but the new sequence does create a new bin that contains the clips from the sequence. Links to actual media are not an issue.

When you bring in a sequence, does it only import the sequence and nothing else into your project? That’s what I would like instead of adding a bin. When I open my new sequence, click on a clip and choose Reveal in Project currently it takes me to the new bin it created rather than its original bin.

thanks,

Brett

[Brett Nelson]

This is one of those times I really appreciate the Cow! The slight Gaussian blur on a suit jacket saved me in a last-minute crisis…an executive’s greeting that had to go out within a couple of hours. I didn’t see the problem until it went to YouTube. I duped the layer and did a garbage matte around the suit (It was green screen, so I could cut the matte fast and loose). Below the neck was a slight bit soft, but the face was sharp and the clip looked good.

Thank you!

Brett

[Brett Nelson]

Steve,
I checked the clip with Mediainfo and nothing jumps out as unusual. It’s Sony DV codec, 720x480i, YUV. I just tried a JPEG AVI created from a still camera. That does not import either. Maybe my DV AVIs aren’t the problem after all.
I must have an app on the MacBook that reads AVIs which CC is using. I’ve tried to isolate which it might be. QT 7, MPEG Streamclip, VLC, DivX, Squeeze are all current versions on both systems. Again, I don’t have trouble viewing these AVIs with any program other than the ones in the CC suite.

Brett

[Brett Nelson]

Tero,
Yes. I did try, but that did not solve it. I decided to take what should have been the obvious option, I transcoded. I used MPEG Streamclip and made DV QTs. I resisted doing this because it’s hours of footage, but it works. Also, I’m now suspecting that these are not mere mortal DV-AVIs. I am remembering that they were created 3 years ago by someone using Premiere Elements. They well may have had some strangeness wrapped in them that for some reason was viewable by other programs but not CC on this system.

Thanks for the input.

Brett