Welcome to Doom9's Forum, THE in-place to be for everyone interested in DVD conversion. Before you start posting please read the forum rules. By posting to this forum you agree to abide by the rules. |
31st December 2015, 14:41 | #2881 | Link |
AVStoDVD Dev
Join Date: Apr 2006
Location: Italy
Posts: 1,302
|
AVStoDVD release 2.8.4 Alpha 151229 is available to download
Change log: - Added 'Execute AVStoDVD with Elevated Privileges' option in 'Preferences'/'Misc' - Added 'All'/'None' selection buttons to all ListBox forms - Improved parsing routine for SubRip subtitles - Removed 2nd authoring attempt if 1st fails (used new BatchMux 1.4 -bmlog flag) - Validated compatibility with Windows 10 - ColorMatrix plugin updated to release 2.5 - FFMpegSource plugin updated to release 2.21 - BatchMux updated to release 0.14 - HCenc updated to release 0.28 (16-08-2015) - AVSMeter updated to release 2.1.3 - LAV Filters updated to release 0.67 - MediaInfo updated to release 0.7.77 Bye |
1st January 2016, 04:19 | #2882 | Link |
Registered User
Join Date: Sep 2003
Location: Berlin, Germany
Posts: 3,078
|
Thanks very much for the new version, I just tested it a little bit, no problems so far...
I cannot comment on the Improved parsing routine for SubRip subtitles, I never use subs. Otherwise the only thing not working on my computer is the new ffms2 version. This version requires a CPU with SSE2 capability, and my machine only has SSE. This breaks the new version even if I do not use FFMpegSource because the A2DSource.avsi always tries to load ffms2.dll. If there are any A2D users out there using a computer without SSE2 capability, I do have a transparent workaround, just let me know... The newer BatchMux version works well with some basic menu creation tasks. Updating the A2D helper utilities is already a little behind, some apps have been updated recently: HCenc has been updated on Dec 21 fixing a critical VBV buffer bug. ffms2 has a newer version 2.22. MediaInfo is now at version 0.7.81 I tested these new versions, they all work well. The included version of ffmpeg 2.2.3 is getting a little old. The latest stable point release is version 2.8.4, and it is also working nicely (except for the bitrate limit for VCD frame sizes). I have no idea though if there are any improvements for MPEG2 encoding in the newer versions. Happy New Year! Cheers manolito Last edited by manolito; 1st January 2016 at 04:21. |
1st January 2016, 22:03 | #2884 | Link |
AVStoDVD Dev
Join Date: Apr 2006
Location: Italy
Posts: 1,302
|
@manolito
thanks for testing the new Alpha so quickly. I will add to the Readme.txt file the explicit requirement to have a SSE2 capable CPU. I will check the newer releases of HCenc, ffms2 and MediaInfo ASAP (don't know how soon in these days, actually...). I would kindly ask you to update the German.lang.ini file, line 270031. @Groucho2004 I will update. BTW, are there any improvements in the AVS info report from release 2.1.3 to 2.1.6? I apologize if I'm asking directly w/o going to read the change log... I feel so squeezed in this period. Bye |
1st January 2016, 22:45 | #2885 | Link | |
Join Date: Mar 2006
Location: Barcelona
Posts: 5,034
|
Quote:
There is comprehensive info about the installed Avisynth version in the "[General info]" section which might be useful to you (or other GUI authors). |
|
2nd January 2016, 16:24 | #2886 | Link | |
AVStoDVD Dev
Join Date: Apr 2006
Location: Italy
Posts: 1,302
|
Quote:
Bye |
|
2nd January 2016, 17:21 | #2887 | Link | |
Registered User
Join Date: Sep 2003
Location: Berlin, Germany
Posts: 3,078
|
Here are the updated 2 lines for the German language file:
Quote:
Tested the latest AVSMeter version, no problems. Quick question: I noticed that the file "ffms2.avsi" is present in the Lib folder. I think it should not be there since AVStoDVD does not call any of its functions. Am I right? Cheers manolito |
|
3rd January 2016, 17:01 | #2888 | Link |
AVStoDVD Dev
Join Date: Apr 2006
Location: Italy
Posts: 1,302
|
Thanks manolito for the translations
You are right, the ffms2.avsi is redundant in A2D scope. BTW can be useful for any curious user who wants to play with ffms2 or to learn some AviSynth scripting. Bye |
4th January 2016, 07:33 | #2889 | Link |
Registered User
Join Date: Jul 2007
Posts: 156
|
Yay new version. Thanks MrC. Going to download and use it tonight!
I have a request for you if its possible to implement without too much work. Each time you load AVStoDVD, you have to choose your output (iso, file, burn dvd) The setting is not saved. Is there some way to save the last used setting? Thanks. |
26th January 2016, 11:59 | #2895 | Link | |||
Registered User
Join Date: Sep 2003
Location: Berlin, Germany
Posts: 3,078
|
Quote:
This statement was a little premature... Some more extensive tests showed that the new BatchMux version 1.4 is not fully backward compatible. For most projects MuxMan will fail completely using the new BatchMux version. The log says that it cannot find the destination folder, but this folder does exist for sure. BatchMux INI file: Quote:
Quote:
To fix the issue it is not required to go back to the last A2D stable version. Replacing BatchMux.exe 1.4 in the new separate BatchMux subfolder with the previous version 1.3 takes care of it. Cheers manolito |
|||
26th January 2016, 13:52 | #2896 | Link | |
Registered User
Join Date: Mar 2004
Location: Italy
Posts: 953
|
Ho, oh...
Quote:
In my tests, if the folder pointed out in the -d command exists, the error about missing destination folder should be NOT produced... What about (in your testing environment) trying with a destination folder which does not end with "VIDEO_TS" ? Note that the behaviour of MuxMan about creating automatically the VIDEO_TS subfolder has changed in the release 0.16.7, and in particular it is not the same to launch manually MuxMan through its GUI or via C/L. So the need to explicitly check about the existance of the destination folder before launching the authoring session, introduced in BM 1.4 can not be avoided... The fix of using BM 1.3 as a temporary solution is very good, indeed (no more log file about the authoring session, however)... |
|
26th January 2016, 16:00 | #2897 | Link | |||
Registered User
Join Date: Sep 2003
Location: Berlin, Germany
Posts: 3,078
|
Hi SD,
Quote:
It also has nothing to do with a delay if the folder(s) are newly created. I repeated the conversion many times while these folders were already present. Quote:
Quote:
So far I think nothing has been lost, by using BatchMux 1.4 AVStoDVD has not added any new features so going back to version 1.3 is not a big deal. For using the new features of the latest BatchMux version 1.6 it will be necessary to modify AVStoDVD quite a bit, and this will take some time... Cheers manolito Last edited by manolito; 26th January 2016 at 16:03. |
|||
26th January 2016, 17:36 | #2898 | Link | ||
Registered User
Join Date: Mar 2004
Location: Italy
Posts: 953
|
Quote:
Another test, without using AVS2DVD, would be interesting: which is by launching BM from a cmd window, manually. The command to use would be something like this: I:\BatchMux.exe -arglist DVD_BatchMux.ini Quote:
Let's way for some comments on the subject from MrC. Last edited by Sir Didymus; 26th January 2016 at 17:39. |
||
29th January 2016, 17:27 | #2899 | Link | |
AVStoDVD Dev
Join Date: Apr 2006
Location: Italy
Posts: 1,302
|
SD, manolito
I have had some weeks ago an email exchange with a A2D user, having a similar problem. Unfortunately I currently do not have the time to dig deeply into this issue. I report the email exchange, if it can help... Quote:
MrC Last edited by MrC; 29th January 2016 at 17:30. |
|
29th January 2016, 20:19 | #2900 | Link |
Registered User
Join Date: Mar 2004
Location: Italy
Posts: 953
|
Ok. Just checked. The issue is in the code of BM.
There is one single line of code where the problem originates. One new function has been introduced, from the release 1.4 up to the latest 1.6, which is most possibly responsible for the reported odd behaviours. This function (in the WinApi) is the "GetFileAttributes". In the BM code it is used to check the destination folder against the constant 0x10 "FILE_ATTRIBUTE_DIRECTORY". All other results from this test currently trigger the reported BatchMux ERROR. I am quite sure (now, after deepening the matter) that encrypted directories - 0x4000 "FILE_ATTRIBUTE_ENCRYPTED", mounted volumes, network drives and possibly other legit directories in the user's file system are wrongly interpreted as invalid directories. I will do some testing during the week end and report back to you... Stay tuned, and in the meanwhile, please proceed as suggested by manolito - downgrade to BM release 1.3, or by MrC - just use a plain directory under the C: volume... Cheers, SD Last edited by Sir Didymus; 29th January 2016 at 23:08. Reason: Detailing... |
Thread Tools | Search this Thread |
Display Modes | |
|
|