[Bill Celnick]

Thanks Michael – you’ve reaffirmed my thoughts exactly…once I’m a tad more comfortable with Resolve (just bought the Studio edition) I’ll end the never ending monthly payments.

It looks like there is allot of support out there for Affinity.

Best.

[Bill Celnick]

Thanks Ben – recall your name form the old WEVA forums…appreciate the feedback

[Bill Celnick]

Thanks for the good advice…I’ve used After Effects, but very sparingly, but there are other Adobe apps that I get with my license that I just don’t use…I’d say that Premiere had been the big one, and I do use Photoshop, but certainly don’t need everything it has to offer.

Once I feel a higher level of proficiency with Resolve I’ll cancel with Adobe and see what happens when they respond.

[Bill Celnick]

You could export your audio to 2 wav files, checking off “export each channel as a separate file”

Then create 2 mono tracks in your sequence and import the 2 files created above and place them there accordingly.

[Bill Celnick]

My experience with IT Departments is that if they feel a computer is fast enough for MS Office, it’s fast enough for editing video…for the most part they’re of a different mindset and not focused on video work.

[Bill Celnick]

I’m getting these errors more frequently with each new release it seems…it only seems to be an issue on rendering within the timeline for me, luckily I’m still able to export these sequences with all the effects. Sometimes I find it’s less frustrating to export a sequence to an mp4 file and proof it as a finished product then to try to deconstruct the timeline in the hope that I’ll come across the issue.

It’s incredibly frustrating that the error message can’t give us more specific info as to what the specific issue is that’s causing the problem.

[Bill Celnick]

I do this all the time…let’s say it’s a presentation where I have a main camera and two remotes – in an auditorium. My method may be more tedious then others, but it works for me.

I create my sequence in Premiere with the source footage I intend to use as my main shot on track #3, next most on track 2, and least on track one. Then I send to Plural Eyes…and it gives me back the synced sequence. Then I set my in and out points, and with my footage laid out on different tracks, I’ll do general adjustments individually on each clip / track – for example, color correct, brightness etc, then I’ll start playing the timeline and make my cuts accordingly.
If after I make cuts, I want to tweak anything further, its done piece by piece.

I use the audio clip mixer to mute the audio I won’t be using, although I keep it on hand just in case I want some ambient sounds from it, like applause.

[Bill Celnick]

I’ve been shooting weddings for over 30 years now, and I’d say that for the last 8, I’ve been shooting with a combination of traditional camcorders and DSLRs – DSLRS for the “eye candy” parts of the day such as preps, photo sessions, and camcorders for everything else.

My DSLRs have primarily been Lumix – GH4, G85, S1…I would describe my feelings towards them as “love/hate” – especially the S1 – beautiful images in low light, but you loose too much time focusing – auto focus is lacking despite several firmware updates that promised better focus among other things.

I’ve been through many camcorders over the years – bought one in August – Canon XA 50 which has become my go to camera (and I had always been partial to Sony before this). I like it much better then I expected to – and I’m using the DSLRs less and less.

[Bill Celnick]

I recently bought a new Mac with an M1 chip as a 3rd system, and with the initial install of Creative Cloud, I believe that Premiere 2022 was the only option.

Since I also edit on a PC laptop when away from home, which was running Premiere 2019, and I needed to work on a project I began in Premiere 2022 on this laptop..since projects can’t be opened in an older version retroactively, I had no choice but to install 2022 on the laptop.

Another reason would be the transcription features available on 2022 that isn’t on older versions – for some of my projects it will be very useful.

[Bill Celnick]

I tend to resist new versions until there is a compelling reason to update to the new release, but always choose the option not to uninstall the previous version.

There is just never a time (excepting the lack of work in mid 2020 due to Covid) when all my projects are complete – always something’s in the loop.