I have been using FlowMotion for several months and Premiere Pro CS6 exclusively for a long term project. I have shot in all kinds of lighting situations - extremely low light and intensely bright light - and have never experience this "digital rain" problem. There are so many variables involved (not just the hack and editing software), it is silly to lay blame on any one thing without researching it further. There's been so much alarm in several posts that I find quite ridiculous.

here you can find the last version, the comments section seems to indicate their using win7: http://www.videohelp.com/tools/tsMuxeR

@BurnetRhoades yeah, the .mov wouldn't load into Premiere (I think? It wouldn't play even in QT but can't remember if I tried loading it into the sequence, damn), and the Avid .avi registered as only an audio track, no video included, even tho I could watch it in a player. Could some of my issues be to do with Premiere still being in Trial mode? I've only just installed more codecs from K-Lite (changed my laptop since I was last editing video...) so that may have been part of the problem. I will try again and see if Premiere will take the clip regardless of my players being able to show me it. Cheers

@eyefi thanks for the info and links. Gonna split the file first as it is 1GB and slowing all attempts down! Edit: TSmuxer just flashes a command prompt for a millisecond & disappears (in Win7), not sure why but I can't use it.

@radikalfilm If I just download CS5.5 will that be a quick fix? I don't have loads of time on this.

@tetakpatak: Myself amongst them. I did mention at the time I'm seeing a semblance of digital rain even with stock firmware (but I only tested a well lit scene). I have trained my eyes since to see the rain in any lighting - it's still there if you know what to look for.

The problem apparently lies only indirectly with CS6 - someone else on this forum investigated and discovered it's a MainConcept decoder fault; he couldn't find a way to override DirectShow decoder weightness - so CS6 is stuck with it.

They (MainConcept) will fix it eventually and it will make its way to Adobe...it is interesting though that not ALL patches have this problem; for example Valkyrie 1.3 decodes perfectly well - I haven't tried anything else.

I can't belive how many people considered @LPowell's amazing patch Flowmotion to be a problem, but it is obviously Premiere's developing team who can be blamed for digital rain. I hope you all Premiere users guys contact their support and report the digital rain problem? It is clearly an issue to be fixed.

you can split your mts file into various segments of any predefined length, for example (see screen shot 1) 9 minutes split every 15 seconds splits your original file into 36 new files, they will be split as mt2s, but you can just rename them mts. Use tsMuxerGUI if your on a mac to do this. you can also join back sequential clips (2nd screen shot) using the same program if you need some sections to be longer than your predefined split length.

all this is easy if you preview your master clip and roughly decide what parts you'll be using. no need for huge files when up converting

I'd just transcode the whole thing and then free up the space once you're done. The tool I always use for that sort of thing doesn't read MTS directly (QTPro Player) or does with an addon so bad I finally got rid of it so that I wouldn't actually make the mistake of ever playing MTS with the QT Player again.

5DtoRGB is currently the only tool I trust to not muck up camera-raw MTS files. Sorry.

Transcode with 5DtoRGB before rendering your edit (replacing footage) or before importing to edit.

No more rain.