Folks,

I need YOUR HELP to ensure the MCEBuddy continues to be developed and kept FREE. There are some FUNDAMENTAL ISSUES that need to be fixed and need your vote for it and other that are nice to have to keep the forums easy to use and functional.

---

FUNDAMENTAL ISSUES THAT NEED YOUR SUPPORT

1. VOTE FOR FFMPEG TO FIX WTV SUPPORT - WITHOUT THIS THERE WILL BE NO NEW RELEASES OF MCEBuddy SINCE IT DEPENDS UPON FFMPEG AND FFMPEG BROKE WTV SUPPORT IN DEC 2012. Post your comments here (after signing up) and lick on the Vote button (Green Arrow under the Roadmap button)
   https://ffmpeg.org/trac/ffmpeg/ticket/2227
   

---

NICE TO HAVE FEATURES
VOTE for these issues with the CodePlex website which will enhance the experience you have on this forum, takes a second: (take you picks!).

Click on the links next to the issue and click on Vote.

1. ATTACHING LOG FILES TO DISCUSSIONS - http://codeplex.codeplex.com/workitem/26583
2. USE WORD STYLE EDITOR INSTEAD OF MARK UP LANGUAGE - http://codeplex.codeplex.com/workitem/26636

---

I voted for both, although the only problem I have with the editor is it pings me to the top of the page each time I click to use a function like bold or inserting picture for example.

You may want to make the post above a bit clearer though, to me for a while it didn't make sense until i clicked on the links! :)

I just used your program and love it! Awesome job! :) Using win7 64bit and works flawlessly for wtv to wtv and remove commercials.... an in the background so I can still do other things without an issue. Very impressive. I wish I had money to donate. When I do, be sure you'll get a reward from me! ;) I love it when things just work.

Update: I wrote the praise for how the program was processing my files... when I went to play it, I got an error of unsupported codec... opened in windows live movie maker and is says it's only 7 minutes long? I used wtv to wtv and remove commercials. Failed on both a wtv and a dvr-ms file. Audio only is playing in windows media player.

With regard to the issue ffmpeg, I was reading that you want the developer to fix something that he doesn't seem to think is broken. I tried another program before finding mcebuddy and it simply got rid of the preview pics, but then all the files just had a blank pic box by the title. The program was WTVconverter and not fully compatable with win7 so slowed system down to a crawl. Also, the xmp files used to tag processed dvr-ms files were being found by my photo editing software and causing a mess, and lots of disc actitivity that put my system in a slow grind... with me heading to taskmgr to kill it, and remove it from my system (well it was Lifextender to remove commercials). My point is, mcebuddy is great, and I wanted to suggest that instead of looking for a single command string combo for ffmpeg to handle how attachments are now video streams, why not write something that evaluates the wtv file's as one that will process properly, and one that will not. Once you have this working, you can work on developing a strategy of how the program should proceed... it may be to ignore or strip the offensive component before fully converting, and the re-introduce the component ontop of the A/V file afterward?

BTW I'VE GIVEN UP ON THE FFMPEG TEAM. IF YOU'RE REALLY INTERESTED GO OUT THERE AND GET THEM TO STAND UP FOR THEIR BROKEN SOFTWARE AND FIX IT.
HERE'S THE LATEST RESPONSE FROM THEM ON TRYING TO FIX NEW BUGS:

https://ffmpeg.org/trac/ffmpeg/ticket/2433#comment:9

Hey rboy1, Thank you for the reply ;) [edit; got the wrong ticket mixed up with this one] I noticed you are using an FFmpeg version that is not noted as a stable release version, if I’m reading things correctly from the dump file you posted in the link at the beginning of this thread? It could be anyway, I just can't figure out where these versions are from...

I was wondering if you are able to use the dev build for windows using dll files and such in place of the source?
Like from this site? http://ffmpeg.zeranoe.com/builds/

Dev packages provide the headers and .lib/.dll.a files required to use the .dll files in other programs.

I use the precompiled version, unfortunately I don't hardware / resources to build ffmpeg

BTW release versions are not always teh most stable version you need test it every few days to find the most stable version. The one I had right now is the most stable one I have tested.

the ffmpeg team are difficult to deal with I admit. Where do you stand with the "patch" that Michael says should get ffmpeg to identify mjpeg as an attachment again?

Take a look here, perhaps you can merge the patch into a pre-compiled version, its beyond my knowledge, but it may help?

I've requested someone from ffmpeg dev team to build me a complied version with the patch, don't have the resources to compile ffmpeg.

Folks, I'm pretty much lost in all this technical Jargon, and I'm happy to vote, as I have already on a few of these bug reports with FFmpeg, but as far as what's actually going on, and so I'm clear on the issue (or one of the issues), I can convert videos just fine using the unprocessed profiles on the other sticky, I've tried MKV, TS, and I've also used videoredo to both remux to MKV, TS, and then recode to MKV and TS H264, while I can play the videos just fine in MCE, none of the files allow you to seek/fast forward, I can do the 30 sec skip preset.

So is this related to the ffmpeg problem? And is ffmpeg used by commercial software makers as well, like videoredo since I'm having the same issue. Or is this just a problem on my end?

yes it's ffmpeg related. some commercial software also use ffmpeg.

What issue are you facing - seeking? if so you need to vote for that ticket separately here:

https://ffmpeg.org/trac/ffmpeg/ticket/2078

Thanks for confirming, and I did vote on that one back in January as it turns out I'm scratching my head on the lack of a solution at this point, while I understand that wtv is a proprietary format, but between the dvrms and wtv, these formats have been out for at least 6 years (vista, and I believe wtv come out in a playpack on vista in 2008, and then on win7), and yet we still don't have a perfect solution.

Thanks for your continued support to get these issues resolved.