AVStoDVD Support Thread

[Reino]

Chances are that you'd see a fully-fledged error message video if you tried playing the script in Windows Media Player 6.4Why didn't I think of that?! This is what MPC-BE returns (absolutely no WMP on my computer!):
I don't know what "ruturn" means
(jdl-util.avsi, line 492)
(C:\Program Files\Media\AVStoDVD\Lib\A2DInfo.avsi, line 11)
(D:\Trouwerij\AVSInfo.avs, line 2)Wtf?! jdl-util.avsi resides in Avisynth's plugin-dir, and yes, it seems it has a typo at line 492, but although I can't see anything fishy going on in A2DInfo.avsi, does it scan my entire Avisynth's plugin-dir for syntax errors or something? :p

After correcting the typo in jdl-util.avsi:
AVS2AVI v1.39 (c) 2002-2004:
Christophe Paris, David Leatherdale, int21h, Moitah
http://www.avs2avi.org/

Source:
* Filename: "D:\Geele Bosch\Trouwerij\AVSInfo.avs"
* FourCC: YV12
* Frames: 250
* Resolution: 1920x1080
* Frame rate: 2.841 FPS
Compressor:
* No Recompression
Destination:
* Format: Null
* Pass 1/1: Finished in 00:00:37.103 (6.74 FPS)
* Frames: 250 (250 keyframes)
* Size: 741.58 MB...and AVStoDVD can open the script as well. :thanks:

@ cweb: Running Avisynth 2.6.0 Alpha 4 [130114] I encoded the wedding shots with HCenc (2-pass) without any problems.

[cweb]

@cweb

thanks for the feedback about FFmpeg/HCenc. Pls keep us informed if you get other issues with AviSynth 2.6.

;)

Bye
thanks .. I will.

[qyot27]

@qyot27

actually Avs2Avi can be easily replaced with FFmpeg for NULL output encoding. Will do.
Another option would be AVSMeter (http://forum.doom9.org/showthread.php?t=165528), as its output is roughly similar to avs2avi's. Example:
AVSMeter 1.5.2 by Groucho2004
AviSynth 2.60, build:May 16 2012 [03:31:34]
Active MT Mode: 0

Number of frames: 6681
Length (hhh:mm:ss.ms): 000:04:27.240
Frame width: 720
Frame height: 480
Framerate: 25.000 (25000/1000)
Colorspace: YV12

Frames processed: 28 (0 - 27)
FPS (min | max | average): 4.96 | 10.42 | 6.43
CPU usage (average): 93%
Thread count: 1
Physical Memory usage (peak): 95 MB
Virtual Memory usage (peak): 103 MB
Time (elapsed): 000:00:04.357

Using post-March 21st builds of FFmpeg has one glaring caveat concerning AviSynth: 2.5.8 doesn't like it one bit (http://ffmpeg.org/trac/ffmpeg/ticket/2526), and any source loading filter causes 2.5.8 to crash with the new demuxer. 2.6 and AvxSynth (the latter has no bearing on AVStoDVD) have no problems with it. This would also include the upcoming release of FFmpeg 1.3, unless the 2.5.8 issue either gets fixed in the interim or it's something further down inside of FFmpeg (or libavformat) that requires some other change to cope with it.

A way of getting around this I guess would be to query AviSynth, and if 2.5.7 or 2.5.8 is detected, fall back to an older version of FFmpeg that uses the old demuxer (point release 1.2.1 would be a good candidate, IMO). Either that or use it as an excuse to make people upgrade to 2.6, but that's mean and a little lopsided since x264 uses the same type of dynamic loading method that FFmpeg is now using, and it has no problems with 2.5.8.

[MrC]

@qyot27

thanks for pointing to AVSMeter and for the info on recent FFmpeg builds. Luckily (my laziness...) the FFmpeg package currently shipped with AVStoDVD is dated Nov 2012, prior release 1.1.

;)

Bye

[Big Vern]

Mr C.
I had to do a fresh install of windows 7 64bit ultimate. Now, when I try to use AVStoDVD 2.7.0, HCenc just sits there and does nothing for about 15 seconds, then it says its not responding. I have tried the latest versions of ffdshow and haali splitter. I even uninstalled them and AVStoDVD, rebooted, then used everything from your package, and HCenc is still hanging and not responding. I cannot for the life of me fathom out what has gone wrong? Is there a config file or something I can upload that you can look at to see if there is any conflicting software? I have not installed new from what I was using 2 days ago when AVStoDVD was working great.

Any help greatly appreciated.

Regards...

***EDIT***
Sorted, forgot to run "Win7DSFilterTweaker". All is good now :)

[manolito]

@CoRoNe

it seems you have found a nice bug in the 2.7.0 release! :)

The AviSynth script becomes red when the user changes something and it is inteded to be used instead of auto script. This feature is unfortunately broken in 2.7.0 release (it works until 2.6.0).


Any news on this?
FYI I just did a conversion using a slightly edited AviSynth script, and this edited script was in fact used for the conversion (according to the log file). So I guess this feature is at least partly working in version 2.7.0 :D


Cheers
manolito

[MrC]

Any news on this?

Half way 2.7.0 hotfix, half way 2.7.1 alpha (https://sites.google.com/site/avstodvdmain/AVStoDVD_271_Alpha_130702_exe_only.7z)

;)

Bye

[manolito]

Thanks, already doing a conversion with it...:D


Cheers
manolito

[manolito]

Originally Posted by MrC
@CoRoNe

it seems you have found a nice bug in the 2.7.0 release!

The AviSynth script becomes red when the user changes something and it is inteded to be used instead of auto script. This feature is unfortunately broken in 2.7.0 release (it works until 2.6.0).

FYI I just did a conversion using a slightly edited AviSynth script, and this edited script was in fact used for the conversion (according to the log file). So I guess this feature is at least partly working in version 2.7.0


Sorry, I spoke too soon, the current 2.7.1 alpha does not fix the issue...:eek:

The general log file for the conversion tells me that the edited AviSynth script was used, but the individual .avs files show that this is not true.

Going back to 2.6.0 for the moment...


Cheers
manolito

[MrC]

@manolito

the summer is tragic... New hotfix (https://sites.google.com/site/avstodvdmain/AVStoDVD_271_Alpha130708_exe_only.7z)

;)

Bye

[manolito]

@manolito

the summer is tragic...

Really this tragic? Are you talking just about the weather or the general political situation or the fact that all of us are spied upon by the Americans and the British? :angry:

Whatever, no need to get too depressed. The new hotfix works beautifully, the edited AviSynth script is now really executed...:D


Thanks a lot,

Cheers
manolito

[MrC]

It was a mention to a 90's dance song "The summer is magic" (http://en.wikipedia.org/wiki/The_Summer_Is_Magic).

BTW, for some personal reasons, this is a really tough period: I would deserve more time to AVStoDVD, but recently I just can give some support on the forums.

;)

Bye

[manolito]

Hi MrC,
I am very sorry to hear this. I hope you and your family are in good health. All my best wishes...

Cheers
manolito

[Sparktank]

An interesting issue I came across recently.

The Short Story:
Problem: Portable (NoInstall) will not start.
Symptom: "Run-time error '383' 'Text' property is read-only"
Solution: install A2D (of the same version that matches the portable version and then the portable version will run).

AviSynth versions:

AviSynth 2.5.8 then...
AviSynth 2.6.0 Alpha4 [Jan 14th, 2013] (IanB)
Avisynth 2.6 MT [2013.03.09] (SEt)


FFDshow version:
K-Lite Mega Codec Pack 9.9.5 [ffdshow 1.3.4513]

User Accounts:
One only, me, the Administrator (so no need to run with elevated privileges).

The LONG Story:

I had to reformat, reinstall my Windows XP machine (x86, SP3) but after doing the long-winded MS updates and getting around to reinstalling all my programs...

I went to setup the NoInstall (portable) version of AVStoDVD 2.7.0 (stable).
I've never really installed it before. I've always used the portable version and updated some of the libraries manually.
Normally, updating libraries (ffmpeg, etc) didn't cause any compatibility issues with using A2D.

But for the longest time, I've been getting a "Run-time error '383' 'Text' property is read-only" error.
I've seen several in this forum and in the comment section on the VideoHelp mirrored page commenting on the same issue.
I know it doesn't offer much in itself as to what the problem is.

Extensive google searches shows it has something to do with one of the dialogue/pop-up boxes in VB6.
I do have the VB6 control placed and registered. I even unregistered and reregistered it.

I saw one search result where you suggested to delete the registry and let itself recreate the registry key for the '383' error.
I've checked the registry for any AVStoDVD keys and made sure to delete them and let A2D rewrite them.
I did registry cleaning/defragging and deleted the manually updated components went back to the original NoInstall archive.

I tried using older portable versions: 2.6.0, 2.5.0.

I also tried to right-click on the portable program and try with different "compatibility" settings.
Nothing.

I also tried to right-click on the portable program and try running the program with different privilege settings.
"Run as..." > Current User > [no] Protect my computer...
Nothing.
"Run as..." > Current User > [yes] Protect my computer...
The splash screen showed up and then nothing.
The task manager showed the program was running at nearly 95% CPU usage.
I had to terminate the process forcibly.

I couldn't get anything to work.

Until!

Finally, I decided, as a last resort, to run the installer for A2D with the latest stable version that matches the latest stable portable version.
All extra installations were left blank due the components already being installed.
However, just for safe measure, I checked the VB6 control to make an "official" install of the VB6 control.

Success! :)

After installation, I was able to start the program and finally see the opening quick selection!
I then went into the installed program and set up all the program settings to my preference and then closed it.
I ran the portable version and it ran successfully as well!

I have no idea if uninstalling A2D will affect the portable version or not.
I'll test that after I convert some movies.
I guess the portable version wouldn't write anything to the registry? :confused:

I thought I might post this in case others with the same 383 error might get a better idea of how to go about troubleshooting their own problem.
I have no idea if it's exclusive to only portable versions or if having it previously installed has any effect.

That's all the information I can provide, too.
I don't have any debuggers or diagnostic utilities to help narrow down the cause for the 383 error.


Hope that helps and hope you're doing well.

Since I lost the usability of the front-end to A2D, I've been toying with HCenc using the .ini and some avs scripts. :devil:
'Twas a fun learning experience, lol.

On a side note, there was a few instances where I noticed the visual quality had dropped significantly and something happened between the first pass and the final encoding pass.
I'm not sure what it was, nor do I remember how my scripting was back then.
But I remember doing some 10 minute tests and used the *LOSSLESS switch in the manual HCenc encoding.
Quality was retained from the initial pass to the encoding pass.

Though, I imagine my scripting back then was very amateurish which resulted in the quality loss between the two passes.

Although, the lossless switch does take up a lot of GB in file size (not for everyone), but...

Request:
Can we get the option to use the *LOSSLESS switch in HCenc?
Maybe an option to set the lossless path as well?

Thanks, again for everything you've put into this bundle. :)

[MrC]

@Spartank

thanks for the detailed report! ;)

the "Run-time error '383' 'Text' property is read-only" VB6 message happens when the program is trying to set an invalid value to a control, i.e. a ComboBox or a TabStrip or an ItemList.

During startup AVStoDVD looks if there is the HKCU/Software/AVStoDVD registry key and try to load the preferences values written in that key.

If in the AVStoDVD registry key are stored invalid values (because of user tweaking them or due to old version preferences values no more supported), then the error msg pop out.

That's why, in case of those errors, I usually suggest to uninstall the previous versions using the uninstaller or by manually delete the reg key if the portable version is used. Moreover there is the 'Options'/'Restore Default Preferences' command that roughly delete the reg key.

About the *LOSSLESS command in HCenc, do you know that you can easily add it the the HCenc ini script by activating the 'Edit Command Parameters at runtime' option?

;)

Bye

[Sparktank]

'Edit Command Parameters at runtime'

:facepalm:

Haha, I somehow managed to completely look past that and see it only as a cosmetic design.

Thanks for the reminder. ;)

EDIT: Also, thanks for the detailed explanation. Best so far from all the google searches.

[Big Vern]

Mr. C or anyone else.
Does Cinema Craft Encoder work with this tool? I did search the thread for cinema craft encoder but got only 2 references, and no answer as to whether it does or not.

Regards...

[Sparktank]

Mr. C or anyone else.
Does Cinema Craft Encoder work with this tool? I did search the thread for cinema craft encoder but got only 2 references, and no answer as to whether it does or not.

Regards...

You actually have to search using quotes for "CCE" (as it is less than four letters).

But it was no longer supported since version 1.2.0.

@Marvel

thanks for your good opinion. About CCE, support to it has been discontinued since release 1.2.0 (November 2007) because I have chosen to support only free software, and I have no plan to reintroduce it. Sorry.

;)

Bye

[MrC]

AVStoDVD release 2.7.1 is available (https://sourceforge.net/projects/avstodvd/files/avstodvd/AVStoDVD%202.7.1/).

Change log:

- Some bugs fixed
- Added errors check just after IDX/SUB and SRT subtitles external files loading
- Added 'Fix IDX' routine for IDX/SUB subtitles
- Added assets folder free disc space check at project start up
- Added 'Full Preview' option in DVD Menu Editor
- Replaced Avs2Avi with FFmpeg for NULL encoding purposes (Avs2Avi has been actually removed from AVStoDVD package)
- Improved ReadAVSInfo routine
- Improved 'Open Project' routine (now it detects media files as wrong input and switch to 'Add Title' routine)
- Improved 'Fix SRT' routine for authored subtitles
- Improved ASS subtitles parsing routine
- Improved log activity

;)

Bye

[Big Vern]

Trying to convert to DVD9 dual-layer and keep getting this error in ImgBurn.

It happens every time I try and do a dual-layer disc, DVD5s are fine! Am I missing an option here to set the layer break in AVStoDVD?

[MrC]

@Big Vern

see Help/FAQ/Burning/Q7.2

;)

Bye

[Big Vern]

@Big Vern

see Help/FAQ/Burning/Q7.2

;)

Bye

Thank you Mr. C ;)

[Reino]

AVStoDVD release 2.7.1 is available (https://sourceforge.net/projects/avstodvd/files/avstodvd/AVStoDVD%202.7.1/)...

The custom-Avisynth-script-issue is gone now. Thank you, MrC.

[qyot27]

Using post-March 21st builds of FFmpeg has one glaring caveat concerning AviSynth: 2.5.8 doesn't like it one bit (http://ffmpeg.org/trac/ffmpeg/ticket/2526), and any source loading filter causes 2.5.8 to crash with the new demuxer. 2.6 and AvxSynth (the latter has no bearing on AVStoDVD) have no problems with it. This would also include the upcoming release of FFmpeg 1.3, unless the 2.5.8 issue either gets fixed in the interim or it's something further down inside of FFmpeg (or libavformat) that requires some other change to cope with it.
Updates.

'1.3' wasn't used as the version number; it was actually released as FFmpeg 2.0. It still has the problematic behavior with 2.5.8.

FFmpeg 2.0.1 includes a stopgap fix that prevents video from loading if 2.5 is detected and warns the user to upgrade to 2.6. Audio can still be handled through 2.5.8, just so long as the script doesn't try to hand video to FFmpeg (in other words, KillVideo() or loading audio-only files works; this is also true of 2.0, but the difference is that 2.0.1 won't crash if you accidentally try to give it video through 2.5.8).

The current git master of FFmpeg (as of 4 hours ago; as I'm typing this post it's the second-to-newest commit) contains a true fix that allows 2.5.8 to fully work properly once more. So projecting this to some future release, it'd be either a '2.0.2' or a '2.1', unless it gets a major version bump again.

[MrC]

@qyot27

thanks for the very interesting update. Hopefully the FFmpeg developers will continue to support AviSynth scripts in upcoming releases. Meanwhile I will stick to Nov 2012 version.

Keep us updated!

;)

Bye

[qyot27]

I wouldn't worry about AviSynth support being dropped, it's simply that the AviSynth demuxer received a very long overdue upgrade* this year and getting it completely back up to speed has just taken several months. Now that 2.5 works with it again, I'd say it's on an equal level to where it was before the rewrite, except with the added bonuses that it can work on Linux and OSX now (by using AvxSynth), and it outputs its error messages to FFmpeg's logging functions which displays it on stdout/stderr rather than writing an error video you have to watch in order to diagnose it. I can personally attest that using it with 2.6 seems to be rock-solid.

You'll also note that generally, the AviSynth demuxer tends to be really stable, and rarely needs fixing. There's only one page of commits that refer to AviSynth when you search on FFmpeg's git repo, only 38 commits (some of which are actually merges and a couple that only mention AviSynth but don't touch its demuxer), and a good half of them are from this year and concern the new demuxer. So that's roughly 20 commits over the 6½ years that FFmpeg used the old version. Now that the new one is more or less on equal ground, the commits on it will probably drop off like the old one's did and it'll just be about making sure it still compiles whenever libavformat's API changes.

*The old AviSynth demuxer relied on accessing scripts through Video for Windows. The new demuxer loads and uses avisynth.dll (or libavxsynth.[so|dylib]) directly. x264 underwent a similar transition from VfW to direct loading in late 2009, which is why I said that it was long overdue on FFmpeg's side.

[manolito]

Hi qyot27,

I do appreciate your helpful comments about ffmpeg compatibility with different versions of AviSynth very much, but this also triggers a real bad ranting about ffmpeg development (this is in no way directed at you)...

I come from the very old days of IBM compatible computers, and backward compatability was everything at this time. When Apple came into the game, they had a very different attitude about backward compatibility, and this was always one of the reasons I hated Apple.

Now the ffmpeg developpers release versions which only work with AviSynth 2.6 which is still Alpha. Are they crazy? Alpha means that it should not be used in productive environments.

I try to avoid ffmpeg as much as I can, but this is not always possible. I have at least 5 different ffmpeg versions on my computer, and if the version which came with a specific software actually works, I am happy. But in reality this is not always the case.

One example is WinFF. They try to use current versions of ffmpeg, but often they fail to update their templates for yet another change in the ffmpeg command line interface. I spent a lot of time to debug these things or to find a different ffmpeg version which actually worked.

ffmpeg documentation is another problem, in most cases the documentation which comes with a specific ffmpeg version is faulty and does not match the actual ffmpeg version.


My conclusion is that ffmpeg is a prime example how distributed software development should NOT be done. Pure chaos...

OK, this is OT for this thread, but I had to get this out!



Cheers
manolito

[qyot27]

Now the ffmpeg developpers release versions which only work with AviSynth 2.6 which is still Alpha. Are they crazy? Alpha means that it should not be used in productive environments.
That it only worked with 2.6 (video-wise; 2.5.8 did still work for audio) was an honest oversight. In this case I'll willingly shoulder a lot of the blame for not realizing this since I helped test the patches back in February and March and have periodically submitted follow-up patches (including the one that fixes it with 2.5.8) on a couple of the issues the new demuxer has.

As SEt notes here (http://forum.doom9.org/showthread.php?p=1564368#post1564368), though, 2.6 is not alpha as far as stability goes. There was also another quote that I can't find now where someone - I can't remember who - admitted that the 2.6 builds were being used as a sort of '2.5.9' since it's been so long since the last release (2.5.8 was released nearly 5 years ago, after all) and it resolves many of the bugs that 2.5.8 had. I'd say that assessment isn't far off from reality, even given some of the recent big changes that have occurred.

[fantasmanegro]

i was trying to encode with last avstodvd 2.7.1... but hcenc crash at second pass in 65%... no log in temp files...

any clue?

[MrC]

1. Does it crash with every input title?

2. Have you tried to use FFMpegSource instead of A2DSource?

3. Have you tried to switch to FFmpeg CBR 1-pass?

The project log file would be helpful, even the project has not ended.

;)

Bye

[fantasmanegro]

1. Does it crash with every input title?

2. Have you tried to use FFMpegSource instead of A2DSource?

3. Have you tried to switch to FFmpeg CBR 1-pass?

The project log file would be helpful, even the project has not ended.

;)

Bye

there is no log... i was using lavf as splitter and ffdshow as decoder... but yesterday i changed from a2dsource to FFMPEGSource and Lavf to Haali and there was no error...

when i was using lavf there was no error message in hcenc, but after start using haali, there was a warning in hcenc about different frames in second pass...

this is the first time i'm having "bugs" with avstodvd... not before...

it's working right now...

[MrC]

there is no log...

not possible, look in output folder, there is a .log file with the same name of your project.

Meanwhile, thanks for the report.

;)

Bye

[EpheMeroN]

AVStoDVD (latest version) works fine on my WinXP system at home. But on my Win7 x64 system it crashes every single time. See attached log. Whatever you need to figure this out I will provide! Thanks.

<10/1/2013 7:31:12 AM>
START PROCESS
<>

<10/1/2013 7:31:12 AM>
PROJECT SETTINGS

DVD Video Standard: NTSC
DVD Titles number: 1
DVD Size: 4449/4450 MB (100%)
DVD Output Setup: DVD Folder
DVD Label: DVD
DVD Menu: No Menu
Output Folder: C:\Users\user1\Videos
Delete Temp Assets Files: Yes
Delete Temp Working Files: Yes
Edit Command Parameters: No
Post Process Task: Show Progress Status window

PREFERENCES

MultiThread: 1
AVS Video Source Filter: A2DSource
AVS Audio Source Filter: A2DSource
AVS UpSize/DownSize Filter: Lanczos4Resize/Spline16Resize
Frame Adjust Strategy: 1
PAL SpeedUp: 0
Video Resolution: 0
Video BitRate Min: 2500
Video BitRate Level 1: 6500
Video Profile Level 2: 4500
Video BitRate Max: 8500
Keep DVD Compliant Video: 1
AC3 Audio Encoder: 0
Force FFmpeg for Long Audio: 1
DVD Audio Format: 0
DVD Audio BitRate: 448
Keep DVD Compliant Audio: 1
Normalize Audio: 0
Auto Delay Audio: 1
DVD Audio Language (Primary): EN - English
DVD Audio Language (Secondary): EN - English
DVD Subs Language (Primary): EN - English
DVD Subs Language (Secondary): EN - English
DVD Subs Font: Tahoma 18pt (255,255,255)
Chapters Interval: 5
Use Source Chapters: 1
DVD Burning Drive: D: TSSTcorp DVD-ROM TS-H353C D100
DVD Burning Speed: 4x
Auto Erase DVD RW: 1
Unload ActiveMovie library: 0
Adjust ffdshow at runtime: 1
Save General Settings: 0
<>

<10/1/2013 7:31:12 AM>
TITLE 1 SOURCE FILES
Video: C:\Vids\the.town.that.dreaded.sundown.mkv
Info: AVC - 5446 kbps - 1280x544 - DAR 2.353 - 23.976 fps (CFR) - Progressive - 1:29:54 hours - 129327 frames
Audio 1: C:\Vids\the.town.that.dreaded.sundown.mkv
Info: DTS - 1509 kbps - CBR - 2 ch - 48000 Hz - 24 bit - 1:29:54 hours (0 ms delay) - EN
[MediaInfoLib - v0.7.61]
<>

<10/1/2013 7:31:12 AM>
AVISYNTH SCRIPT
Import("C:\Program Files (x86)\AVStoDVD\Lib\A2DSource.avsi")

Video = A2DVideoSource("C:\Vids\the.town.that.dreaded.sundown.mkv", CacheFolder="C:\Users\user1\AppData\Local\Temp", FrameRate=23.976, VFR=false)
Audio = A2DAudioSource("C:\Vids\the.town.that.dreaded.sundown.mkv", CacheFolder="C:\Users\user1\AppData\Local\Temp")

Video = Video.ConvertToYV12()
Video = Video.AddBorders(0,88,0,88)
Video = Video.Spline16Resize(720,480)
#Using DGPulldown/HCenc to upsize FPS

AudioDub(Video, Audio)
<>

<10/1/2013 7:31:12 AM>
START VIDEO ENCODING OPERATIONS
Encoding Profile: HCenc VBR 1-pass
Target Video FileSize: 4072.9 MB
Encoding Parameters: -ini "C:\Users\user1\AppData\Local\Temp\DVD_0_the.town.that.dreaded.sundown.mkv.HCenc.ini"
HCenc ini file:
*INFILE C:\Users\mjohnson\AppData\Local\Temp\DVD_0_the.town.that.dreaded.sundown_1.avs
*AVSRELOAD
*OUTFILE C:\Users\user1\Videos\DVD_0_the.town.that.dreaded.sundown.m2v
*LOGFILE C:\Users\user1\AppData\Local\Temp\DVD_0_the.town.that.dreaded.sundown.HCenc.log
*MAXBITRATE 9000
*1PASS
*BITRATE 6334
*PROFILE BEST
*ASPECT 16:9
*PROGRESSIVE
*TFF
*PULLDOWN
*BIAS 60
*DC_PREC 10
*MATRIX MPEG
*AQ 1
*LUMGAIN 1
*SMP
*PRIORITY IDLE
*DBPATH C:\Users\user1\AppData\Local\Temp
*WAIT 2
<>

<10/1/2013 7:35:18 AM>
Process aborted during Title 1 VIDEO encoding operations.

For Video issues troubleshooting see Help/FAQ/Video section.
<>

<10/1/2013 7:35:18 AM>
Log file created by AVStoDVD Release 2.7.1
<>

[MrC]

@EpheMeroN

I assume you have installed all the required splitter and codecs (ffdshow 32bit). Then have a look at Help/FAQ/General/Q1.5

;)

Bye

[MrC]

Pre-release 2.7.2 Alpha 131004 is available to download (https://sourceforge.net/projects/avstodvd/files/avstodvd_alpha_beta/AVStoDVD%202.7.2%20Alpha%20131004/). For debug purpose only.

Change log:

- Some bugs fixed
- Added support to MicroDVD format (SUB/TXT) subtitles
- Added automated unzip of Skin icons in case of library load fault during startup
- Improved SRT->SUP subtitles vertical positioning for widescreen aspect ratio
- Improved log activity for single project and batch jobs
- Improved Video DVD compliant detection routine (max bitrate is now checked)
- Changed default subtitles font dimension from 18pt to 16pt

;)

Bye

[manolito]

Hi MrC,

it looks like the prerelease mostly fixes some subtitle issues. Since I do not use subtitles at all (I hate them to no end), is there anything you want me to test with this release?


Cheers
manolito

[MrC]

Hi manolito,

actually there are no major changes in video/audio encoding or AviSynth scripting. Some subs, errors handling and log improvements. No particular debug, just verify if there are discrepancies between project settings and output. In other words, just use it as usual... Ah, there are no new GUI objects or menu items to be translated into German.

Thanks, as always, for your help and support.

;)

Bye

[manolito]

Alright, did a couple of short test conversions (mostly Youtube clips), no problems so far...:)


Cheers
manolito

[MrC]

Alright, did a couple of short test conversions (mostly Youtube clips), no problems so far...:)

Thanks for the feedback. I'm updating the Help file, the final 2.4.2 should be out within few days.

In the next release I would add Win7/8 codecs check and selection (ffdshow instead of MS), something like Preferred Filters Tweaker. I wonder if it would be better to leave the user to decide what codecs to use or have AVStoDVD change to ffdshow automatically at runtime in a transparent, but somehow "invasive", way (coming back to original user preferred codecs setup at the end of the project).

;)

Bye

[MrC]

Release 2.7.2 final is out (https://sourceforge.net/projects/avstodvd/files/avstodvd/AVStoDVD%202.7.2/)

;)

Bye

[manolito]

Thanks very much MrC for the new version...:)

Everything works nicely here, I just found a (purely cosmetic) issue which might have been present for some time...

What I did was trying to just author and burn a fully DVD compliant MPEG2 file which was small enough to fit on one DVD. My settings are to keep compliant video and audio, so all AVStoDVD had to do was demux the source and author it using MuxMan.

After importing the source file the main window told me that the final size would be 9.5 GB (source file was 2.9 GB) and the status line was very red. A novice user might have given up at this point, but I started the process anyways, and it finished successfully.

This time it is not MediaInfo's fault, I tried three different versions.

Here's the log:
<17.10.2013 20:35:55>
START PROCESS
<>

<17.10.2013 20:35:55>
PROJECT SETTINGS

DVD Video Standard: PAL
DVD Titles number: 1
DVD Size: 9526/4450 MB (214%)
DVD Output Setup: DVD-Ordner
DVD Label: DVD
DVD Menu: No Menu
Output Folder: I:
Delete Temp Assets Files: Yes
Delete Temp Working Files: Yes
Edit Command Parameters: No
Post Process Task: Fortschrittsfenster anzeigen (Voreinstellung)

PREFERENCES

MultiThread: 1
AVS Video Source Filter: A2DSource
AVS Audio Source Filter: A2DSource
AVS UpSize/DownSize Filter: Spline36Resize/Spline36Resize
Frame Adjust Strategy: 1
PAL SpeedUp: 1
Video Resolution: 0
Video BitRate Min: 2000
Video BitRate Level 1: 6500
Video Profile Level 2: 3500
Video BitRate Max: 8500
Keep DVD Compliant Video: 1
AC3 Audio Encoder: 0
Force FFmpeg for Long Audio: 1
DVD Audio Format: 0
DVD Audio BitRate: 224
Keep DVD Compliant Audio: 1
Normalize Audio: 1 (@ 0.98)
Auto Delay Audio: 1
DVD Audio Language (Primary): DE - German
DVD Audio Language (Secondary): EN - English
DVD Subs Language (Primary): DE - German
DVD Subs Language (Secondary): EN - English
DVD Subs Font: Tahoma 16pt (255,255,255)
Chapters Interval: 6
Use Source Chapters: 1
DVD Burning Drive: H: BENQ DVD DD DW1620 B7W9
DVD Burning Speed: 8x
Auto Erase DVD RW: 0
Unload ActiveMovie library: 0
Adjust ffdshow at runtime: 1
Save General Settings: 0
<>

<17.10.2013 20:35:55>
TITLE 1 SOURCE FILES
Video: I:\test.mpg
Info: MPEG-2 Video - 2507 kbps - 720x576 - DAR 1,778 - 25 fps (CFR) - Interlaced (TFF) - 2:28:38 hours - 222966 frames
Audio 1: I:\test.mpg
Info: MPEG-1 Audio layer 2 - 192 kbps - CBR - 2 ch - 48000 Hz - 2:28:38 hours (0 ms delay)
[MediaInfoLib - v0.7.58]
<>

<17.10.2013 20:35:55>
AVISYNTH SCRIPT
Import("E:\Programme\AVStoDVD\Lib\A2DSource.avsi")

# Video is frameserved by AviSynth just for Preview and Edit purposes.
Video = A2DVideoSource("I:\test.mpg", CacheFolder="I:", FrameRate=25, VFR=false)
# Audio is frameserved by AviSynth just for Preview and Edit purposes.
Audio = A2DAudioSource("I:\test.mpg", CacheFolder="I:")

Video = Video.ConvertToYV12(interlaced=true)

AudioDub(Video, Audio)
<>

<17.10.2013 20:35:55>
START VIDEO DEMUXING OPERATIONS
Target Video FileSize: 9037,4 MB
FFmpeg Parameters: -i "I:\test.mpg" -vcodec copy "I:\DVD_0_test.m2v"
<>

<17.10.2013 20:43:11>
END VIDEO DEMUXING OPERATIONS
Created File: I:\DVD_0_test.m2v (2637,7 MB)
OUTPUT VIDEO INFO: MPEG-2 Video - 2480 kbps - 720x576 - DAR 1,778 - 25 fps (CFR) - Interlaced (TFF) - 2:28:38 hours - 222966 frames
<>

<17.10.2013 20:43:11>
START AUDIO DEMUXING OPERATIONS (Track 1)
FFmpeg Parameters: -i "I:\test.mpg" -acodec copy -map 0:1 "I:\DVD_0_test_1.ToFix.mp2"
<>

<17.10.2013 20:45:29>
END AUDIO DEMUXING OPERATIONS (Track 1)
Created File: I:\DVD_0_test_1.mp2 (204,1 MB)
OUTPUT AUDIO INFO: MPEG-1 Audio layer 2 - 192 kbps - CBR - 2 ch - 48000 Hz - 2:28:38 hours (0 ms delay)
<>

<17.10.2013 20:45:30>
START DVD AUTHORING OPERATIONS
BatchMux Parameters: -arglist "I:\DVD_0_BatchMux.ini"
BatchMux ini file:
-d "I:\DVD_0\VIDEO_TS"
-mxp "I:\DVD_0_MuxMan.mxp"
-l "I:\DVD_0_MuxMan.log"
-muxman "E:\Programme\AVStoDVD\MuxMan"
-prio LOW
-palette "I:\DVD_0_Palette.txt"
-v "I:\DVD_0_test.m2v"
-vidmode LB
-a1 "I:\DVD_0_test_1.mp2"
-a1lang de
-cellfr "I:\DVD_0_test_Chapters.txt"
-progfr "I:\DVD_0_test_Chapters.txt"
-chapfr "I:\DVD_0_test_Chapters.txt"

<>

<17.10.2013 20:58:51>
END DVD AUTHORING OPERATIONS
Created Folder: I:\DVD_0 (2926,4 MB)

CHECK DVD SIZE
DVD Folder (actual) Size: 2926,4 MB
vs Estimated Size: 9526 MB -> 69,3% undersize
vs Assets Size: 2841,9 MB -> Warning!
<>

<17.10.2013 20:58:51>
Log file created by AVStoDVD Release 2.7.2
<>

As i said, it is purely cosmetic...:D



Cheers
manolito

[MrC]

Well, not so cosmetic, at least for a less experienced user. :)

Use following hotfix (https://sites.google.com/site/avstodvdmain/AVStoDVD_272_Hotfix_131017.7z)

;)

Bye

[manolito]

Wow, this is hard to believe...


At 10 PM I report a non-critical issue for some software I use to its author.

At 11:30 PM the author sends me a working hotfix.


You would think that I must have paid good money for this software, plus I purchased priority gold support. And even then this kind of customer service would seem extraordinary.


But this just happened with AVStoDVD which happens to be free...

MrC, you are amazing...:D
Thank you so much,


Cheers
manolito

[MrC]

Wait, wait, thanks for the kind words... but actually the hotfix was already ready (http://forum.videohelp.com/threads/277852-AVStoDVD-Support-Thread?p=2274478&viewfull=1#post2274478)...

;)

Bye

[Fishman0919]

@MrC...

Any chance of seeing 2-pass ffmpeg video support?

ffmpeg ver 2.0.2 and 2.1 are pretty good.

[netmask]

Is it possible to set subtitles default ON if so how?

Thanks

[manolito]

@MrC...

Any chance of seeing 2-pass ffmpeg video support?

ffmpeg ver 2.0.2 and 2.1 are pretty good.

I just tested ffmpeg 2.1 a little bit, and I agree that it is pretty good...

First of all it does play along nicely with AviSynth 2.57 and 2.58 again (thanks qyot27 :D ). I used it within AVStoDVD for a couple of test conversions and did not run into any problems.

But I do not see any reason to include 2-pass ffmpeg support in AVStoDVD. First of all it would not be a simple matter of just changing 1 or 2 command line parameters. Instead ffmpeg would have to be called twice with different parameters.

And second I do not see any benefit. If you need 2-pass for higher quality, you already have the HC encoder. Do you believe that ffmpeg 2-pass would give you higher quality than HCenc 2-pass? Or do you think that ffmeg would be faster than HC? I doubt it in both cases.


Cheers
manolito

[Fishman0919]

I just tested ffmpeg 2.1 a little bit, and I agree that it is pretty good...

First of all it does play along nicely with AviSynth 2.57 and 2.58 again (thanks qyot27 :D ). I used it within AVStoDVD for a couple of test conversions and did not run into any problems.

But I do not see any reason to include 2-pass ffmpeg support in AVStoDVD. First of all it would not be a simple matter of just changing 1 or 2 command line parameters. Instead ffmpeg would have to be called twice with different parameters.

And second I do not see any benefit. If you need 2-pass for higher quality, you already have the HC encoder. Do you believe that ffmpeg 2-pass would give you higher quality than HCenc 2-pass? Or do you think that ffmeg would be faster than HC? I doubt it in both cases.


Cheers
manolito

I agree... somewhat.

Faster... no

Better... On most stuff I encode below 3500k, I feel Yes. Anything above 3500k, mostly No.

Calling ffmpeg for multi passes can be done with just 1 command line bat file with different settings.

ffmpeg.exe -i "####.avs" -framerate 23.976 -aspect 16:9 -dc # -g 12 -maxrate 7500k -q:v 2 -b_strategy 2 -brd_scale 2 -bf 2 -profile:v 4 -pass 1 -passlogfile ffmpeg -an -f mpeg2video pass1.m2v

ffmpeg.exe -i "####.avs" -framerate 23.976 -aspect 16:9 -dc # -g 12 -lmin 0.01 -mblmin 1 -qmin 1 -qmax 31 -maxrate 7500k -b:v ####k -bf 2 -pre_dia_size 5 -dia_size 5 -qcomp 0.7 -qblur 0 -preme 2 -me_method dia -sc_threshold 0 -sc_factor 4 -bidir_refine 4 -profile:v 4 -mbd rd -mbcmp satd -precmp satd -cmp satd -subcmp satd -skipcmp satd -pass 2 -passlogfile ffmpeg -an -f mpeg2video pass2.m2v

But this is just a thought for the back burner.

[manolito]

I agree... somewhat.

Faster... no

Better... On most stuff I encode below 3500k, I feel Yes. Anything above 3500k, mostly No.


Wow, your command line for the second pass is really impressive! Also quite slow probably...;) And still no adaptive matrix, no auto GOP adjustment. Requires extensive tests to determine which decoder has the edge at these low bitrates...

For me whenever I am not happy with low bitrate encodes, usually Procoder does the trick. Not that sharp, but very pleasant to watch.


Cheers
manolito

[Fishman0919]

Wow, your command line for the second pass is really impressive! Also quite slow probably...;) And still no adaptive matrix, no auto GOP adjustment. Requires extensive tests to determine which decoder has the edge at these low bitrates...

For me whenever I am not happy with low bitrate encodes, usually Procoder does the trick. Not that sharp, but very pleasant to watch.


Cheers
manolito

Slow... kinda Yes... about 40-45fps on my PC... where HC is about 65fps. not to bad if you remove "-mbd rd" but with somewhat of a drop in quality... about 50fps.

adaptive matrix... No... never looked into setting it.

auto GOP adjustment... Yes.

I was a Procoder fan for low bitrates, but i liked the ability to change what I wanted with ffmpeg. I believe it delivers as good of, if not better then, quality.

This was just a quick 2-pass sample that looks pretty good.