Hello Adobe Community,
I'm experiencing a severe banding issue in Premiere Pro that does not occur when I play the same footage in QuickTime. So it isn't an issue with the source video files. I’m editing a project that includes footage captured using the same camera over 6 years since 2018. I have made a previous video that the footage was captured with using the same camera and also edited in Adobe Premiere which makes this banding issue even more odd. I was successfully able to Color grade it and add desired Lumetri additions on my last project. This footage is captured with a Panasonic DVX100b that used a MiniDV tape. I then used a "capture camera" that also uses a MiniDV tape (think family cameras to capture memories back in the film days) to transfer the clips from the film to make a digital file from the footage and not wear down the film heads on the camera in the process. A pretty standard recommended process. This is something i have done for years, starting with a VX1000. This was a lot of work but was all in the name of having that "aesthetic" which is quite popular in the Skate/BMX film making scene.
Here are the specifics of my setup and the problem:
System Information:
- Device: MacBook Air (2020)
- Processor: 1.1 GHz Quad-Core Intel Core i5
- Graphics: Intel Iris Plus Graphics 1536 MB
- Memory: 16 GB 3733 MHz LPDDR4X
- OS: macOS Sonoma 14.5
- Premiere Pro Version: 24.5 (Latest)
Footage Details:
DVX100b Camera Capturing on MiniDV tapes and then converted into digital '.mov' files
- Format: MPEG-4 (QuickTime) (DVCPRO)
- Resolution: 720x480 (4:3), at 29.970 FPS
- Bit Depth: 16 bits
- File Size: 33 s 834 ms, 24.4 Mb/s bitrate
Issue Description:
When playing back my footage in Premiere Pro, I experience severe banding that is not present when the footage is played back in QuickTime. The issue persists through various attempts to resolve it, including disabling hardware acceleration.
Troubleshooting Steps Taken:
- Created a New Project from Source Clip: Imported the source file directly into a new project, but the banding persisted.
- Disabled Hardware Accelerated Decoding: Went to Premiere Pro > Settings > Media, unchecked "Enable hardware accelerated decoding", restarted both Premiere Pro and my MacBook, and created a new project, but the issue remained.
- Checked Sequence Settings: Ensured that the sequence settings matched the source clip settings, including codec and frame rate.
- System Specs Confirmation: Verified that my system meets the necessary requirements for running Premiere Pro.
Screenshots and MediaInfo + Export video:
- The same clip showing banding in Premiere & not showing banding in the basic Quicktime preview
- MediaInfo software showing the source file information
- Brand new project/Sequence with Hardware Decoding Accelerated Disabled & Still Showing Banding
- All views show banding - Fit View
- All views show banding - 50%
- All views show banding - 100%
- Exported Video Showing The Current Banding Issue — If that is helpful
Additional Notes:
- The footage plays perfectly in QuickTime without any banding.
- This issue has persisted through different codec usage and files that were captured using the same camera.
- I found a very similar issue on this forum where the user says that the banding is only happening in Premiere and nowhere else, so i know that it's not just me experiencing this odd banding issue in Premiere Pro: premiere-pro-discussions/banding-on-quicktime-prores-422-10-bit-videos-in-premiere-not-elsewhere
I would appreciate any assistance or suggestions on how to resolve this issue. It’s crucial for my project, and I’m at a loss on how to proceed further. I have used Premiere for every personal project i have ever made, i don't desire learning a new piece of software like Final Cut and take my editing work that i've done in an XML file there.
I have considered that using Media Encoder may be helpful? If anyone reading this feels that would be the way to go let me know!
Here is the video that i made in 2017 using the same DVX camera and edited it using Premiere Pro:
"Tape" 4
The idea was that this was to be a follow up to this. I even downloaded this file from that link above from my Vimeo account so i could match the Media Information on the export. I've spent considerable time editing this new project so to find out that it wasn't just a display oddity that needed to be adjusted and is truly based on how Adobe is interpreting the footage is quite dissapointing. Especially since I have used the same technology successfully in the past. This footage that I have accumulated is very important to me and not being able to use it well is hard for me to accept.
Thanks in advance for any help that I may receive!
1 Correct answer
@Kevin-Monahan Found out through Reddit that it wasn't even banding.
Remedy was --> Select the clip in the Project panel and going to Clip > Modify > Interpret Footage.
When there switching from 'Lower Field First' in the project panel on the actual clips to 'No Fields (Progressive Scan)' did the trick! Not sure how the 'Lower Field First' option was on. That is odd to me. The only thing i changed was sequences attempting to troubleshoot.
24,944 frames to render!
1 Pinned Reply
Hello @JonathanSchimpf,
I'm Kevin. One of the moderators here. Thanks for filing this bug report and for the information you provided. I'm unsure what could be happening here, but hopefully, a team member will respond.
A sample clip would be helpful. Feel free to upload it to Creative Cloud or Dropbox. If you don't want it visible to the public, you can PM me the link.
My hunch is that it has to do with the media and how it was transcoded. Something may be going on with the way the media is
...
15
Replies
I've tried to upload the file to creative cloud and it is too large:
That or "Some file type not supported"
but I do have a publicly available Google drive link of an export showing the banding issue.
https://drive.google.com/file/d/1ESOc6MUDxleqQIMch2HiuuviDBwG_3BS/view
I could export a smaller video that has just the clip I've been using as a screen shot example, with the brick wall that is suffering from the banding because of the pattern. The banding is very obvious, the clip is towards the end of the video @ 13:50.
Thanks for that contact information! I will definitely be reaching out.
I really would love to upload to creative cloud but i just tried a 5-10 second snippet showing the obvious banding snippet and creative cloud would not allow it. Does creative cloud not allow .mp4 files? I thought it was the length but it said 'Some filetype not supported'..
That is the exact format that won't export from the exact sequence settings.. Not quite sure how else this can be properly diagnosed.. My bad!
At any rate here's the shortened clip:
https://drive.google.com/file/d/1Efusmp_W1Et6yxvjiFOZQU_JGUmf7mr9/view?usp=drive_link
@Kevin-Monahan
No worries, thank you for making that space and being willing to help me with this. It means alot! I have replies checked so i'll keep a lookout.
@Kevin-Monahan below is a screen recording showing that the source file of the video plays in a quicktime default player without showing banding. So there certainly be some alteration needed. It's very odd that a basic video player displays the footage correctly, but a pro tool editor does not. I must have something set up wrong. The example clip screen recording of it playing banding-free:
Screen recording showing that Quicktime does play the clip without displaying banding.
To make things easier for the developers at Adobe, here's the actual source file where the banding issue clearly shows on the brick wall:
Source file of the clearly visible banding issue on a brick wall that i've been using as an example
^ Despite that only being 34 seconds, i cannot upload to creative cloud for some reason...
CC says '"filetype not supported"
I'll gladly upload though. Just let me know!
@Kevin-Monahan Found out through Reddit that it wasn't even banding.
Remedy was --> Select the clip in the Project panel and going to Clip > Modify > Interpret Footage.
When there switching from 'Lower Field First' in the project panel on the actual clips to 'No Fields (Progressive Scan)' did the trick! Not sure how the 'Lower Field First' option was on. That is odd to me. The only thing i changed was sequences attempting to troubleshoot.
24,944 frames to render!
AdChoices