![]() ![]() Post-production professionals rely on 5DtoRGB every day for its high-quality results, and now even novices can batch convert their clips with 5DtoRGB's user-friendly interface.ĥDtoRGB Batch offers professional controls typically unavailable in consumer-type video converters. Original MTS converted to ProRes via FFMPEG, imported to PP then exported.5DtoRGB is one of the most popular tools for converting footage from HDSLR and other cameras for editing. !38IxGQjA!WwAjaiIW7KF7lgoDkquGokrdutZqdDrvTEorl4o6dks !WgpkBZrb!RlDm6n2xeq-bGI4t4UDnhHXmiaAZKRERg_YqxvXHKIA Original GH/50F under exposed to show effect Obviously I can pre convert to prores prior to import the PP but that negates the huge advantage of native support on the PP timeline and wastes a lot of time.įiles below of 2 sec clip if you want to have a look but any ideas guys? If anyone else has come across this can you tell me how you resolved it. So this relates to some sort of comparability issue between PP (and AE I am told) and the GH2 MTS files. If I transcode the MTS via FFMBC to prores the prores files plays fine from the vert start, shows fine in PP when imported and exports fine too. Import into PP and you can see it on source and program monitor, it does not show if you set the monitors to half res. I have tried both stock 1.1 GH2 firmware and with higher bit rate set via ptools but the effect is the same even with stock firmware. If you view the original material in VLC the first second shows the effect then it disappears and you just have the normal background noise but no obvious cycling rain. The rain like effect builds up over 1 second then disappears then builds again cyclically every 1 second. I have taken some clips and you can view them with the links at the bottom of this post. The problem is rain like artifacts on GH2 MTS files when viewed and exported from PP CS6 (I haven't tried but apparently cs5.5 was the same). I got thhat information from this post and my post follows: It appears to be a problem with the Mainconcept filers used by PP which needs to be fixed. ![]() Just wanting to pitch in here as I found this post and I am having exaclty the same problems. I don't believe the hack is anything to do with this issue. My GH2 is hacked, but I have read reports where this noise is appearing on standard unhacked footage (GH2 hacked with flowmotion v2.02) ie. 5dtorgb gh2 pro#Therefore the problem appears to be Premiere Pro CS6's handling of GH2. MOV files then the media is played back in Premiere Pro 100% ok and the rain/snow/banding noise is not shown. 5dtorgb gh2 windows#If I play back using Windows media player classic then the problem appears to not exist. These snow/rain/banding noise artifacts only seem to happen on dark/underexposed areas of GH2 footage and only if played back within Premiere Pro CS6 or VLC player. Look at the lower left part of the screen (the floor in the left hand footwell of the car) and you will see the 'snow/rain/banding' artifacts flickering on playback in PP CS6 MTS media file from vimeo and load into a sequence within Premiere Pro CS6 you will see on playback some digital artifacts that look like snow/rain/banding that occur at approx 13 -14 secs onwards into the video. The vimeo transcode and playback process does not exhibit the same issues as playback within Premiere pro CS6. Please note that you cannot see these noise artifacts when playing back the video in Vimeo. It's not great footage, but I chose it as it shows the problem up quite well as a typical dark/underexposed shot where the problem typically rears it's ugly head. MTS file straight from the camera, without any processing applied, to vimeo at ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |