[Mads Nybo jørgensen]

Hey James and Kouraib,

Yes, A.I. is here to stay.

And Yes, it will have an increasing impact on our industry in so many ways.

But those using A.I. for everything, might never have used a professional for their output in the first place. As they don’t want to pay for it. And, eventually we (the “consumer”) will all tire of seeing the “same” A.I. rolling over our screens.

We are already seeing the likes of Topaz releasing Bloom, that is created to make A.I. generated images look better and more realistic.

Cinema 4D, in my opinion, forgot years ago to look after their customers. This was down to a sales department thinking that they were walking on water, with the mantra “Don’t call us, we will call you” – they are laughing no more. As Cinema 4D has had to go on a purchase spree to keep their products relevant, and drop the price on their per seat subscription cost (as far as I can see, might be wrong on the price drop).

Pivot towards offering art direction and creative design input, whilst also learn Blender, Unity and Unreal + anything else that is free to use, with a big library of assets.

And, don’t forget to create a side-hustle of making your own stuff, that you are the owner of, and can monetize. Check out https://sidehustleschool.com daily podcast, plus past podcasts for inspiration.

Don’t be afraid of A.I., but do be its sceptical friend.

Just an opinion.

Atb
Mads

sidehustleschool.com

Home page

Home page

[Mads Nybo jørgensen]

Hey Florencia,

If you render out the same AE composition twice, do the glitches appear on the exact same frame(s)?

Maybe also test using different codecs for your destination master video file.

But if always at the same place, it is likely to be “rogue” key-frames, or damaged footage (if video – would need to get more information of the sources in the composition).

Less likely, but could also be a plug-in that is playing up.

Hope that this helps?

Atb
mads

[Mads Nybo jørgensen]

Hey Daniel,

Out of interest, in Media Encoder, does it switch the coded to a HD size, or a preset, that can’t do the 4K?

As weird as it may sound, this thread on Adobe might help you, also involving an NVidia GeForce card (and After Effects CC 2017):

https://community.adobe.com/t5/after-effects-discussions/after-effects-cc-2017-render-different-from-preview/m-p/9221800

Atb
Mads

community.adobe.com

After Effects CC 2017 Render different from preview?

Hi, I seem to be getting a repeating glitch when it comes to rendering after effects files in media encoder. My computer has a: NVIDIA GeForce GTX 960 graphics card with 24 Gigs of RAM 16 of which are allocated … Continue reading

[Mads Nybo jørgensen]

Sorry that there wasn’t better reply for you to get, for a camera that is sold as professional, and can record ProRes…

However, as most NLE packages will sync to audio provided that you record audio, and preferentially in track 1, or all tracks, on both cameras + you record in the exact same framerate, then it should be easy to sync. And if one camera runds out of space or battery, you can start it again, and sync that file too.

Sounds fun though, recording new talent, and see them grow if picked by the right agent.

Atb
Mads

[Mads Nybo jørgensen]

Hey Dustin,

Sorry, but there is no input for sync on the camera.
There is no clear description of using wireless (Wi-Fi), except that you can stream the image from the camera, but not necessarily remote control it or sync with other cameras of the same model.

On top-range professional cameras, you often have a BNC connector for sync (cable), but even that might not carry Timecode.

You could set your cameras up to run Time-of-Day Timecode.

Make sure that they run at the exact same frame rate.

Before start of the event, clapperboard them at the same time, or clap your hands (obviously with both cameras running and filming the clap.

The other thing to watch out for is what format you are recording. If highly compressed, the sync (Timecode) is likely to drift.

Hope that this helps you.

Atb
Mads

[Mads Nybo jørgensen]

Hey Florencia,

Adobe v25.3, certainly for Premiere Pro, is one big bug.

If you can, roll back to an earlier version like v25.0 and see what happens.

Atb
Mads

[Mads Nybo jørgensen]

Hey Roman,

Without knowing your project and the size of it, it is difficult to advice on it.

However: I recently found that Windows 11 PRO, NVidia drivers and Adobe was a lethal combination that killed my PC.

In computer terms, you are much better off, than what you had on your old PC. But not enough to make full use of AE v25.
I would like to see 64GB RAM and a fast SSD drive for starters.

In terms of rendering, the Intel 9900 chip is 5 years old – not sure about you RTX card.

Again, it depends on the size of your project and what is in the timeline.

Without breaking the bank, can you increase to 64GB memory. Hopefully that is half the problem.

Other people around here are much smarter than me and can recommend rendering and preview settings to optimize your setup.

Atb
Mads

[Mads Nybo jørgensen]

Hey Anthony,

How frustrating!
Sorry, that you have to go through this, but Adobe is currently not treating PPro with the respect that it deserves.

You didn’t tell us what file format you were shooting.

But assuming that it is MP4 LongGop, and that is why you are missing frames etc – I’ve just been through that on PPro v25.

I suggest that you as a test take the “first clip” (file) and transcode into a stable format with each frame being a full frame. Yes that will cost you space on the hard-drive + export time, but at least if it works, you know where the problem is.

ProRes is stable, there is other formats too that Adobe can offer you.

The US JVC website is not clear on whether it is 29.97P or 30P, but in theory PPro should have chosen the frame-rate that you shot it at.
If there is an XML file that came along with the video-file from the camera, it might be worth you opening that and see what it tells you?

Otherwise, in the transcode, depending on what your Tascam DR60 digital recorder fps was set to, maybe match that if you can?

Hope this helps you getting a bit closer to a solution.

Atb
Mads

[Mads Nybo jørgensen]

Hey Daniel,

Well done!

On PPro, it was Long-GOP that killed my project.
I suspect that the Adobe A.I. transcription and picture identifyng tools are tied into the timecode, and if that shifts, as it can do with Long-GOP footage then your project is toast.

If long-form Long-GOP, with many edit points. Your footage on loading could at any given point be one frame short, or worse one frame long – which should not be a big issue in A.E., but in PPro, where a neat edit has everyhing, or most, in the same Video Track, it is a dissaster…

Don’t know where your frame originated from, but it could be “rogue” video file.

Thank you for sharing your findings on that frame, just shows that it is worth reading the error logs – in my case, it was often Windows Blue Screen, so no logs.

Atb
Mads

[Mads Nybo jørgensen]

PS:

Should add that in one of my biggest crashes it turned out that alledgedly Adobe PPro was interfering with the kernel on the Geeforce card (I had a Nvidia 4090 A.I. chip in laptop).
This was found on one of the Adobe forums…

Atb
Mads