27 replies to this topic

[adone36]

I originally had 2.19 working fine, generating edl and mpg files for SageTV import (USA). I upgraded to 2.21 and the "No recode" option produced avi files which caused SageTV to error. In the profile, I changed file output to "mpg" and mpg files were created, but Sage again posted an exception. I went back to 2.19 because 2.21 has errors in file renaming (fixed in future versions). Now 2.19 makes the same unviewable avi files. The only thing I ever edited in profiles previously was to only generate comskip markers and not cut the files and to force edl output.

In looking at the files, they are MPEG1 (viewable on vlc, wmplyer, etc, etc,) and cause an exception in Sage. The conversion also takes much longer than before. How can I get the fast conversion to NTSC MPEG2 I had before??

[Ramit]

Please do not create MPG files with NoRecode as MPG containers typically contain MPEG-1 video. The NoRecode creates MPEG2 Video with AC3 audio.

I would suggest you create the default AVI files and then rename them to .MPG - of MEncoder or FFMPEG is used to create MPG file it can mess up the container format.

[adone36]

Thanks.

Can the extension be renamed during custom file renaming? Previously the completed process yielded an edl file and an mpg file. I did no manual manipulation, and I don't recall doing anything with respect to the extension.

[Ramit]

I haven't made any changed to the MPG code so I can't say why it isn't working, it just isn't advisable since the formats are incompatible.

I've thought about the renaming but it won't be appropriat as it'll break the format.

Doesn't SageTV play AVI files?

[adone36]

Yes it does. My major problem was when I went to 2.21. I found Sage would not play the files (avi). 2.19 was making mpgs under norecode with fast conversion and proper play. I know the only profile changes I made were for comskip and nothing about format, and the converted files were mpg. Re-installing 2.19 yielded avis also and they were unplayable (in Sage, every other player would play them). I then examined the files under detailed video info in Sage and it listed video as MPEG1 not MPEG2, which is apparently the reason for Sage throwing the exception.

[Ramit]

If it was working with 2.1.9 then reverting back to it should your problem (it is an entirely self contained package - you can do a clean installation if you'd like). However since it is not solving the problem the only logical conclusion is something else in your system configuration changed (however unlikely it may seem to you, I've seen it happen hundreds of times with users - usually an aha moment for something they installed or some other apps changed the system config).

Anyways if you'd like me to debug this you'll have to upload the original source video to the ftp server and I can see what's going on.

More likely than not it's a DirectShow filter that been messed up somehow - if I'm correct SageTV uses DirectShow filters to play back video.

[Ramit]

can you also please paste the profile that you were using (successfully). I would like to see how you had setup the option that worked for you in the past.

[adone36]

Ramit

That's my problem. When uninstalling 2.19 it removes everything. I think a future option to save settings, profiles and comskip.ini files in a save directory would be a great option. I think I may have found my culprit. Previous avi unplayable in Sage (playable in everything else) showed as video, MPEG1 720p@60 fps or MPEG2 1080i@30 fps. I made conversions of the same show with no recode and no recodeslow today and both show as avi containers with MPEG2, 1080i@30 fps. Both unplayable in Sage. I then noticed the 30fps and thought that could not be the issue because I have hundreds of avi movie files that play fine. I looked at these and the avi containers all contain mp4 video. Sage setup starts with specify NTSC or PAL and Sage has its own MPEG codec for recordings, etc. It uses SageTV Player to play mkv, mp4, etc. That is the only difference I see.

I used MC-TVconverter on the recording and it's MPEG2HQ profile yields an mpg with MPEG2 file 1080i@29.97 fps and it plays fine. MCE-Buddy is a more refined package and I just have to tweek it to do what I want. I'll test it with an mp4 profile. I used the Norecode because I don't care about the size and was more concerned with speed due to the number of recordings.

[Ramit]

Glad to know you figured out the issue.

The NoRecode profile, just as it says just copies the audio and video over into the AVI container, so it won't chnage any frame rates.

If you're looking for a fast way to get MPEG2 video, I would suggest the NoRecode SLOW profile. You can add the parameter -r 30*1000/1001 to the profile to get the exact frame rate you're looking for. You can experiment with .mpg extension and see if that works.

Regarding the settings, I've thought about it a bit, but given the changes in the programs and new features etc, I feel that is some cases it will mess up/cause unexpected output.

I figure, if you're smart/savvy enough to edit the profiles.conf file - you can also make a backup of the changes/custom profiles for future use
Often I may come up with newer profiles (e.g. NoRecode Slow), there is no way to merge the old with the custom, hence the decision not to preserve the config files. Only the HISTORY files is preserved to ensure that files are not reconverted.

Let me know if you need more help

[Ramit]

Also let me know - are the source files WTV, DVRMS or TS files?

Reason I asked, There is a new DVRMS and WTV remux engines that use frame rates while remuxing. By default they are set to auto frame rate (MCEBuddy will detect and correct) - this was done to help with conversions that FFMPEG, Mencoder fail to detect the frame rate.

If you're using DVRMS or WTV, check MCEBuddy.conf file (under the FFMPEGBackupRemux section) and you can try 2 things:
1. Change the frame rate from -r auto to -r 30*1000/1001
2. You can remove the frame rate adjustment all together, ie delete the -r auto completely

[adone36]

Thanks Ramit.

As I expected, my mp4normal played fine. The file size is 1/6 the size but the image is soft and has an occasional stutter. A 30 min show took about 30 min to process on my system.

I'll try your suggestions and I'm sure it will work out. I am using Windows 7 wtv files and the American NTSC standard.

Other issues:

In examining 3 conversions: Chelsea Lately, Fairly Legal, Common Law. All 3 say 720X400. The last two say 16:9 (1st does not), yet the 1st fills my screen and the other 2 have black bars on the sides (wider than 4:3, but not 16:9.

By the way %recordhour%%recordminute% does not work.

I use %showname%--%episodename%--%recordyear%-%recordmonth%-%recordday%-%recordhour%%recordminute% because MCE uses zap2it to provide metadata and it is very poor. Frequently channels will run 8 episodes of Mythbusters, for example, and have no episode names and a description like "Two guys do stuff" which makes duplicate files without the time. In most cases, MCEBuddy retrieves the episode title and this is outstanding. The metadata lookup is a great feature to a fine program.

[Ramit]

Can you upload one of the video files where the %recordhour% doesn't work (I'm assuming it's a WTV file). From what I have with me it's worked so I need the sample to analyze why it isn't working.

[adone36]

I just finished testing with your suggestions. When I went to modify mcebuddy.conf, I realized I had never re-installed 2.21 after going back to 2.19 and the section you mentioned was not there. I installed 2.21 and the hour and time renaming do indeed work. The file produced was 29.97 and SAGE plays it fine! The only problem is that it is MPEG1 instead of MPEG2.

[Ramit]

I tested this with 2.2.2 and it's working perfectly. the way it works is:
1. It looks for the recording date/time from the WTV/DVRMS file and uses that
2. If it cannot find a the recorded date/time in the metadata, or say the file is a mp4 or TS, it will use the File creation date/time and use that information.

In all casese it's working great nad giving me a hour and minute.

If you're still facing an issue, check the command for typo's.
Also up load the log file it will detail what the recorded minute/hour is being used by MCEBuddy and will help isolate the problem.
Make sure the log file has been set to Debug (which is default)

[adone36]

I tested this with 2.2.2 and it's working perfectly. the way it works is:
1. It looks for the recording date/time from the WTV/DVRMS file and uses that
2. If it cannot find a the recorded date/time in the metadata, or say the file is a mp4 or TS, it will use the File creation date/time and use that information.

In all casese it's working great nad giving me a hour and minute.

As I mentioned above, the hour and time ARE used in renaming with 2.21. I just discovered that the info is INCORRECT. See attached log file. The Windows file name and the metadata within the file both correctly state the record time was 23:00 ie: 11PM US Eastern Std time. MCEBuddy upon renaming the file says the record time was 1900.