OS2 World Community Forum

OS/2, eCS & ArcaOS - Technical => Applications => Topic started by: Remy on December 30, 2015, 01:21:48 pm

Title: AVxCAT 1.4 alpha
Post by: Remy on December 30, 2015, 01:21:48 pm
Are any tester available to give a try to AVxCAT V1.4.0 ALPHA  ( compatible with ffmpeg 2.1.5 ) ?
If you are interested, please send me an email from my home site to get this alpha build or get it from here:
http://remydodin.levillage.org/outils/avxcat_140alpha.zip
 
Alpha build means that you may find problems
2 known problems
- OGV and MPEG2 not working ( about OGV, it looks to be ffmpeg but more investigation is needed )

ffmpeg to try with it   
- http://hobbes.nmsu.edu/download/pub/os2/apps/mmedia/ffmpeg-os2-r2_1_5-Fourier.zip

It has:
- latest found bugs under v1.3.x resolved
- display ffmpeg version under 'help'
- Added debug log on ffmpeg
  (warning, use it only in case conversion fails at start or the amount of messages may crash avxcat)
   to enable it: - enable axtra log, go under parameters ans mark ffmpeg debug log. At end of session, parameter is removed
- video conversion uses multi threads which speed up the conversion ( you can specify auto or the number of threads (CPU core)
  This option is enabled with ffmpeg 2.1.5 and disable under older ffmpeg ...
  note: very fast on MP4

After test, please, provide feedback using the email link on my web site and specify what was well tested or buggy.
e.g.
- audio conversion ( codec tried )
- audio to video conversion ( codec tried )
- multiple audio track with join
- video conversion
- video and mapping !
- create presentation out of videos
...   

Cheers/2
RD
Title: Re: AVxCAT 1.4 alpha
Post by: Dariusz Piatkowski on December 30, 2015, 04:31:27 pm
Hi Remy,

Wow...great news...thank you so much for continuing the work on this.

I was never able to overcome the "system freeze" with the latest previous version so I'm happy to give this a try.

-Dariusz
Title: Re: AVxCAT 1.4 alpha
Post by: Remy on December 30, 2015, 07:21:37 pm
Nice Dariusz

About this alpha build, I left some code in it to allow opening a drdialog box only in case of internal errors to get more information.

Cheers/2
RD.
Title: Re: AVxCAT 1.4 alpha
Post by: Holger Schuett on January 01, 2016, 12:10:16 pm
Hi Remi,

I just tried the alphbuild with the ffmpeg version you point to, but there seem to be files missing concerning this ffmpeg version?

By the way : Happy new year and thank you for your efforts

Holger
Title: Re: AVxCAT 1.4 alpha
Post by: Remy on January 01, 2016, 07:52:19 pm
Hi Holger,

Happy new year to you too and to all OS2WORLD users.

Yes, please read the readme file from ffmpeg. You have to get some additional dll's to make it work.

Cheers/2
Remy
Title: Re: AVxCAT 1.4 alpha
Post by: Holger Schuett on January 02, 2016, 05:12:55 pm
Hi Remy,
sorry, I did not see the readme.file the first time I tried.
I downloaded the files missing acording to the readme but I am not able to do any conversion all the same. What I noticed: When setting the ffmpeg full path in the parameters pointing to the version you recommend and then adding a file the time/file (s) line in the main window is empty. I do see the filename and the size. If I change back to another version of ffmpeg I see the filename, size and the time/file value

Holger
Title: Re: AVxCAT 1.4 alpha
Post by: Remy on January 02, 2016, 08:53:08 pm
Hi Remy,
sorry, I did not see the readme.file the first time I tried.
I downloaded the files missing acording to the readme but I am not able to do any conversion all the same. What I noticed: When setting the ffmpeg full path in the parameters pointing to the version you recommend and then adding a file the time/file (s) line in the main window is empty. I do see the filename and the size. If I change back to another version of ffmpeg I see the filename, size and the time/file value

Holger

Did you put all Dll's into a dll patth ( e.g. c:\ecs\dll ?
It looks like ffmpeg didn't find the required dll's.

I suggest you to unlock current DLL's if older version exist and rename them before copying new DLL's into the libpath.

Please use the email link on my site to provide more details about how you installed ffmpeg and avxcat and your avxcat parameters.
Best regards,
RD   
Title: Re: AVxCAT 1.4 alpha
Post by: Remy on January 11, 2016, 12:37:11 pm
Any feedback received yet  :-[ .

 
Title: Re: AVxCAT 1.4 alpha
Post by: Holger Schuett on January 11, 2016, 06:21:11 pm
Hi Remy,

shortly after my last posting I had to reinstall ECS as my machine trapped and I was not able to solve the problems.
Right now I only have ECS installed, without any programs except a Browser and I am still facing problems As soon as I have this worked out I will try again with AVxCat.

Holger
Title: Re: AVxCAT 1.4 alpha
Post by: Dariusz Piatkowski on February 14, 2016, 03:15:57 pm
Hi Remy,

...About this alpha build, I left some code in it to allow opening a drdialog box only in case of internal errors to get more information...

Sorry about the delay...alright...tested this, but the old problem remains...the minute I push the "Files" button the system goes into a SOFT freeze, meaning CTL-ALT-DEL still recovers but that leads to a shut-down.

Soo...for what it's worth, this only happens when I have all 6 CPU cores up and running...if I shut down 5 of them then it appears to work. Of course the problem this leads to is that any sort of covnersionn process takes extremely long. In my case I have massive MJPG videos from my Pentax DSLR.

Anyways, if you want me to try anything just let me know. Thanks for continuing the work on this app...
Title: Re: AVxCAT 1.4 alpha
Post by: Remy on February 16, 2016, 04:07:39 pm
Strange !
I do not see why OS2 command issued at file open time is hunging your system...
About long process, older ffmpeg was single thread only while the latest one I suggested to give it  try is multi-thread and under my system which has 4 enabled CPU core ( I also tried it using the 4 additional virtual core ), it works well and conversion is mutch faster with the latest ffmpeg suggested build.

I'll return into my code and check what could make you system not responding ...   
no other user reported this kind of problem.

Thx
RD
Title: Re: AVxCAT 1.4 alpha
Post by: Dariusz Piatkowski on February 17, 2016, 03:36:58 pm
Hi Remy,

...About long process, older ffmpeg was single thread only while the latest one I suggested to give it  try is multi-thread and under my system which has 4 enabled CPU core ( I also tried it using the 4 additional virtual core ), it works well and conversion is mutch faster with the latest ffmpeg suggested build...

Let me explain better, the long time it takes to re-encode my videos is due to several reasons:
1) MJPGs produced by my DSLR (Pentax K5) are big...we are talking on the order of 1.5-2gig for just a couple of minutes
2) since I can not use your app with multiple CPU cores enabled, I shut off all but one, then encoding happens in a "single thread" fashion since all other CPU cores are effectively disabled
3) I have previously used ffmpeg-os2-r26099, which is multi-thread enabled (it was a Dave Yeo drop)...so if I do the conversion outside of your app (command line) I am able to crunch through the data much faster as the work is done in parallel

I did download and install your recommended ffmpeg-os2-r2_1_5-Fourier version...haven't gotten a chance to try it out yet though.

Here is an idea I've been investigating to get around my app freeze situation. I could configure the application start cmd file to shut off all cores and run in a single-core mode. When the time comes to actually start the encoding operation if there was a way for your process to tie-in to a user defined "prep cmd step" I could then re-enable all the cores and really let the machine fly through the process. Since your app builds the final ffmpeg command on-the-fly I'm wondering if there is a way for me to do this?

So here is an example of what I'm talking about:

=== START ===

/* auto generated program by FFMPEGCA to execute ffmpeg in start using pipe */
Parse arg copy_metadata
ff_inputfile="I:\Movies\Family\Amelia - Baby Boots 2.MPG"
ff_inputfile='"'||ff_inputfile ||'"'
ff_outfile="G:\HOME\.ffmpegca\Amelia - Baby Boots 2.mp4"
Out_AVmap=" -map 0.1 -map 0.0"
more_map=""
ff_outfile='"'||ff_outfile||'"'
ffmpeg_prms='  -i '||ff_inputfile||' '||Out_AVmap||' -vcodec libx264 -b 1400k -r 29.97 -qmin 2 -qmax 35 -async 3'
/* --- x264 preset used : external --- */
ffmpeg_prms=ffmpeg_prms||' -vpre hq'
ffmpeg_prms=ffmpeg_prms||' -ar 44100 -acodec ac3 -ab 192k -vol 256 -ac 2'
ffmpeg_prms=ffmpeg_prms||' '||copy_metadata||' '||ff_outfile||' '||more_map

==> BEFORE ffmpeg.exe kicks off below I'd re-enable the CPU cores

'G:\util\misc\priority.exe 1 3 G:\APPS\MULTIMEDIA\ffmpeg\bin\ffmpeg.exe -y '||ffmpeg_prms||' 2>\pipe\ffmpegca_122'

==> AFTER ffmpeg.exe finishes above I'd disable the CPU cores

=== END ===

...any chance for this?
Title: Re: AVxCAT 1.4 alpha
Post by: Remy on February 18, 2016, 01:00:36 pm
thanks for your explanation.
Let me have a look and I'll add an option into an other build for test   

Note: R26099 never worked in multi thread under my system while the latest yes.
Title: Re: AVxCAT 1.4 alpha
Post by: Remy on February 18, 2016, 03:43:12 pm
Hi Dariusz,

Please give a try to this new alpha build
http://remydodin.levillage.org/outils/avxcat_140alpha2.zip

- Corrected some code when clicking on files ( a proc was called 2 times )
- Added option under parameters to see LOCAL or USED drives ( was set to USED drives by default )
- Included code to check existing of a file called "owncmd.txt' under avxcat path into which some user os2 commands could be added ( do not include single quotes because avxcat will add single quotes at start and end of each included cmd line. these commands are put/issued prior the ffmpeg exe.  e.g.   CLS

Cheers/2         
Title: Re: AVxCAT 1.4 alpha
Post by: Dariusz Piatkowski on February 19, 2016, 05:10:43 am
Hi Remy!!!

Success....but...read on please...

- Corrected some code when clicking on files ( a proc was called 2 times )
- Added option under parameters to see LOCAL or USED drives ( was set to USED drives by default )
- Included code to check existing of a file called "owncmd.txt' under avxcat path into which some user os2 commands could be added ( do not include single quotes because avxcat will add single quotes at start and end of each included cmd line. these commands are put/issued prior the ffmpeg exe.  e.g.   CLS ...

OK, so I had closed all my front-end apps before testing, in case it might freeze up...to my amazement and excillaration the Open File dialog box popped up and off I went picking files. Great...I shut-down the app, re-booted, re-tried the test to confirm the behaviour and ran straight into the same old freeze problem...why???

Well, I start up a few apps by default during system boot, one of them is PSI (IM client), through additional testing I found out that if I kill PSI before starting your app, it will open up the File dialog box fine. If on the other hand I leave PSI up and running the old behaviour persists and even the very 1st File attempt will lock things up.

Knowing this I tested further.

This time, having opened the File dialog once I wanted to rule out multiple File pick options, and here is where I ultimately got stuck. Even with PSI not running, attempting to open the File dialog for the second time will freeze the app. The LOCAL/USED drive settings did not seem to make a difference here.

One more test remains, and that is the "owncmd.txt" file approach...but as best as I can tell this only allows me to execute a "pre" command, is there a "post" command option as well? To avoid the freeze I effectively need to run in a single-core mode while using the app and only switch to all-cores when ffmpeg is actually running, then back to single-core only.
Title: Re: AVxCAT 1.4 alpha
Post by: Remy on February 19, 2016, 11:03:53 am
Thanks for your test.

Could you please provide me some information about your environnement ( ECS V? OS2 v?, number of drives etc ... )
( use my email option from my web site for confidentiality )

I'll add some debug messages in a special build

* Yes, this build has "pre" command support only. I'll add "post" cmd as well into next build ( using the same owncmd file but identifying each command by a special character ( may be: B for before and A for after ... I'll tell you as soon it is ready )

Cheers/2   
Title: Re: AVxCAT 1.4 alpha
Post by: Dave Yeo on February 19, 2016, 06:55:52 pm
This sounds like a simple smp problem and perhaps can be fixed by marking avxcat.exe as MPUNSAFE. At least it would be worth trying. I believe the syntax is
Code: [Select]
markexe MPUNSAFE avxcat.exe
Title: Re: AVxCAT 1.4 alpha
Post by: Remy on February 20, 2016, 03:58:00 am
Hi Remy!!!

Success....but...read on please...

- Corrected some code when clicking on files ( a proc was called 2 times )
- Added option under parameters to see LOCAL or USED drives ( was set to USED drives by default )
- Included code to check existing of a file called "owncmd.txt' under avxcat path into which some user os2 commands could be added ( do not include single quotes because avxcat will add single quotes at start and end of each included cmd line. these commands are put/issued prior the ffmpeg exe.  e.g.   CLS ...

OK, so I had closed all my front-end apps before testing, in case it might freeze up...to my amazement and excillaration the Open File dialog box popped up and off I went picking files. Great...I shut-down the app, re-booted, re-tried the test to confirm the behaviour and ran straight into the same old freeze problem...why???

Well, I start up a few apps by default during system boot, one of them is PSI (IM client), through additional testing I found out that if I kill PSI before starting your app, it will open up the File dialog box fine. If on the other hand I leave PSI up and running the old behaviour persists and even the very 1st File attempt will lock things up.

Knowing this I tested further.

This time, having opened the File dialog once I wanted to rule out multiple File pick options, and here is where I ultimately got stuck. Even with PSI not running, attempting to open the File dialog for the second time will freeze the app. The LOCAL/USED drive settings did not seem to make a difference here.

One more test remains, and that is the "owncmd.txt" file approach...but as best as I can tell this only allows me to execute a "pre" command, is there a "post" command option as well? To avoid the freeze I effectively need to run in a single-core mode while using the app and only switch to all-cores when ffmpeg is actually running, then back to single-core only.

How many files do you have under the path you open through internal filemanager ?
What is your path name where ?

I found a unstability issue and may rewrite several part of the code for the internal filemanager...   
Title: Re: AVxCAT 1.4 alpha
Post by: Dariusz Piatkowski on February 20, 2016, 05:17:53 am
This sounds like a simple smp problem and perhaps can be fixed by marking avxcat.exe as MPUNSAFE. At least it would be worth trying. I believe the syntax is
Code: [Select]
markexe MPUNSAFE avxcat.exe

Tried that already...same result...the only thing that seems to work is running 'setproc' utility...not sure who wrote that...but you can find it on Hobbes here => http://hobbes.nmsu.edu/download/pub/os2/util/system/setproc.zip  (http://hobbes.nmsu.edu/download/pub/os2/util/system/setproc.zip)

Here is something else I noticed. When I start up either PSI or Remy's app I see libc06b4.dll showing up in Theseus...but that is a DLL that is quite old and is "retired" now...lol...yet both apps still pull it in, my DLL details are:

 2-01-05  10:21a    562710           0  libc06b4.dll

...and here is the full list of all libcxxx DLLs:

10-27-03   5:13p    230785         124  libc04.dll
 4-14-04   4:37p    356330           0  libc05.dll
10-26-14   8:17p     48179           0  libc06.dll
10-26-14   8:17p     48179           0  libc061.dll
10-26-14   8:17p    157161           0  libc062.dll
10-26-14   8:17p    157161           0  libc063.dll
10-26-14   8:17p    157213           0  libc064.dll
 8-11-08   5:53a   1353252         124  libc064x.dll
10-26-14   8:17p    157213           0  libc065.dll
10-26-14   8:16p   1361666           0  libc066.dll
 2-01-05  10:21a    562710           0  libc06b4.dll
12-30-11  11:08a    114176           0  libcbeta
 2-01-05  10:21a    562710           0  libcbeta.dll

So maybe some sort of DLL conflict where one of these is not SMP-safe?
Title: Re: AVxCAT 1.4 alpha
Post by: Dariusz Piatkowski on February 20, 2016, 05:30:39 am
Remy,

...Could you please provide me some information about your environnement ( ECS V? OS2 v?, number of drives etc ... )...

No worries, this may be an issue that others may run into so I like to share as much of my experience with our OS/2 community as possible.

OK, so we are talking 4.52 SMP machine here. 6-core AMD Phenom II X6 CPU running on MSI 880G-E45 series motherboard. Running ACPI 3.22.08 release here.

Now the drives...oh boy (you are probably going to shake your head, but here it comes), in total I have 19 drives (volumes really across 3 physical hard-drives), 2 are not accessible (file-system not mapped), 7 are main OS/2 install, 7 are HOT/nightly backups, 3 are Samba drive mappings to other home PCs (windows boxes).

All my OS/2 drives run HPFS386, all are 60Gig in size.

I tested your "pre" user-command, works great...the conversion of my 130Meg MJPG to h264 MP4 took all of about a 30 sec with all cores chugging away (threads=4, I could have ran more given 6 CPU cores though, however that Settings spin-button only let me go to 4, if I leave on 'auto' the program runs into a problem and ffmpeg claims that the pipe was shut-down/broken, I will capture the specific details later on).

Thanks again...even with the SMP on/off manual flip this is great already!!!
Title: Re: AVxCAT 1.4 alpha
Post by: Dariusz Piatkowski on February 20, 2016, 05:40:05 am
...How many files do you have under the path you open through internal filemanager ? What is your path name where ?...
Not many files, about 6 files that match the filter extension...but about 18 files in total in that directory...the path name I've used is "G:\tmp\camtest"

From a process perspective here is what PSTAT returns:

G:\APPS\MULTIMEDIA\AVXCAT\AVXCAT.EXE   005F       2B      G:\OS2\DLL\REXXAPI.DLL
                                  G:\OS2\DLL\DOSCALL1.DLL*
                                  G:\OS2\DLL\QUECALLS.DLL*
                               G:\OS2\DLL\REXX.DLL
                                  G:\OS2\DLL\DOSCALL1.DLL*
                                  G:\OS2\DLL\REXXAPI.DLL*
                                  G:\OS2\DLL\KBDCALLS.DLL*
                                  G:\OS2\DLL\NLS.DLL*
                                  G:\OS2\DLL\SESMGR.DLL*
                                  G:\OS2\DLL\QUECALLS.DLL*
                                  G:\OS2\DLL\MSG.DLL*
                               G:\OS2\DLL\DOSCALL1.DLL*
                               G:\OS2\DLL\PMGPI.DLL*
                               G:\OS2\DLL\PMWIN.DLL*
                               G:\OS2\DLL\PMSHAPI.DLL*
                               G:\OS2\DLL\PMDRAG.DLL*
                               G:\OS2\DLL\PMCTLS.DLL*
Title: Re: AVxCAT 1.4 alpha
Post by: Remy on February 20, 2016, 08:30:59 pm
This sounds like a simple smp problem and perhaps can be fixed by marking avxcat.exe as MPUNSAFE. At least it would be worth trying. I believe the syntax is
Code: [Select]
markexe MPUNSAFE avxcat.exe

Tried that already...same result...the only thing that seems to work is running 'setproc' utility...not sure who wrote that...but you can find it on Hobbes here => http://hobbes.nmsu.edu/download/pub/os2/util/system/setproc.zip  (http://hobbes.nmsu.edu/download/pub/os2/util/system/setproc.zip)

Here is something else I noticed. When I start up either PSI or Remy's app I see libc06b4.dll showing up in Theseus...but that is a DLL that is quite old and is "retired" now...lol...yet both apps still pull it in, my DLL details are:

 2-01-05  10:21a    562710           0  libc06b4.dll

...and here is the full list of all libcxxx DLLs:

10-27-03   5:13p    230785         124  libc04.dll
 4-14-04   4:37p    356330           0  libc05.dll
10-26-14   8:17p     48179           0  libc06.dll
10-26-14   8:17p     48179           0  libc061.dll
10-26-14   8:17p    157161           0  libc062.dll
10-26-14   8:17p    157161           0  libc063.dll
10-26-14   8:17p    157213           0  libc064.dll
 8-11-08   5:53a   1353252         124  libc064x.dll
10-26-14   8:17p    157213           0  libc065.dll
10-26-14   8:16p   1361666           0  libc066.dll
 2-01-05  10:21a    562710           0  libc06b4.dll
12-30-11  11:08a    114176           0  libcbeta
 2-01-05  10:21a    562710           0  libcbeta.dll

So maybe some sort of DLL conflict where one of these is not SMP-safe?

I build the program under drdialog using rexx.
Title: Re: AVxCAT 1.4 alpha
Post by: Remy on February 20, 2016, 08:34:16 pm
...How many files do you have under the path you open through internal filemanager ? What is your path name where ?...
Not many files, about 6 files that match the filter extension...but about 18 files in total in that directory...the path name I've used is "G:\tmp\camtest"

From a process perspective here is what PSTAT returns:

G:\APPS\MULTIMEDIA\AVXCAT\AVXCAT.EXE   005F       2B      G:\OS2\DLL\REXXAPI.DLL
                                  G:\OS2\DLL\DOSCALL1.DLL*
                                  G:\OS2\DLL\QUECALLS.DLL*
                               G:\OS2\DLL\REXX.DLL
                                  G:\OS2\DLL\DOSCALL1.DLL*
                                  G:\OS2\DLL\REXXAPI.DLL*
                                  G:\OS2\DLL\KBDCALLS.DLL*
                                  G:\OS2\DLL\NLS.DLL*
                                  G:\OS2\DLL\SESMGR.DLL*
                                  G:\OS2\DLL\QUECALLS.DLL*
                                  G:\OS2\DLL\MSG.DLL*
                               G:\OS2\DLL\DOSCALL1.DLL*
                               G:\OS2\DLL\PMGPI.DLL*
                               G:\OS2\DLL\PMWIN.DLL*
                               G:\OS2\DLL\PMSHAPI.DLL*
                               G:\OS2\DLL\PMDRAG.DLL*
                               G:\OS2\DLL\PMCTLS.DLL*

Sure, not a lot of files...
Title: Re: AVxCAT 1.4 alpha
Post by: Remy on February 20, 2016, 08:44:42 pm
I'm going to increase the number of selectable CPU from max 4 to 6   ( auto should take all 6 CPUs )
Currently, I implemented the after user cmd option in addition to the pre user cmd option
I'l already working on the internal filemanager code and could reduce some processes (making it faster) but some kind of action under it always gives some unstability (but less than before)... Working more on it   
Title: Re: AVxCAT 1.4 alpha
Post by: Dave Yeo on February 20, 2016, 09:51:47 pm

Here is something else I noticed. When I start up either PSI or Remy's app I see libc06b4.dll showing up in Theseus...but that is a DLL that is quite old and is "retired" now...lol...yet both apps still pull it in, my DLL details are:

 2-01-05  10:21a    562710           0  libc06b4.dll

Isn't that loaded by ft2lib, the Innotek Font Engine? Probably other old programs as well.
Wouldn't surprise me if any of the older DLLs aren't SMP safe as it is harder to program for SMP and for the longest time no one considered it. Ideally would be to recompile all the old programs but that takes source code.
Wish I had the bandwidth to upload a new version of FFmpeg, v3 was recently released.
Title: Re: AVxCAT 1.4 alpha
Post by: Remy on February 21, 2016, 01:03:08 am
Drdialog uses an old rc.exe, I tried a newer one but this one will not work with drdialog.
Any suggestion about a newer compatible rc.exe to use with drdialog ?

FFmpeg v3 (not under os/2 yet)
Title: Re: AVxCAT 1.4 alpha
Post by: Dave Yeo on February 21, 2016, 02:45:23 am
Could try wrc from OpenWatcom. The syntax may be slightly different.
Title: Re: AVxCAT 1.4 alpha
Post by: Andreas Schnellbacher on February 21, 2016, 03:21:37 am
Have you tried the one from the ancient icc Mozilla project times?

http://os2news.warpstock.org/rcos2-5.00.007.zip (http://os2news.warpstock.org/rcos2-5.00.007.zip)

This link is still present on Steve's Warpzilla page (http://os2news.warpstock.org/Warpzilla.html).
Title: Re: AVxCAT 1.4 alpha
Post by: Dave Yeo on February 21, 2016, 06:14:50 am
Have you tried the one from the ancient icc Mozilla project times?

http://os2news.warpstock.org/rcos2-5.00.007.zip (http://os2news.warpstock.org/rcos2-5.00.007.zip)

This link is still present on Steve's Warpzilla page (http://os2news.warpstock.org/Warpzilla.html).

Ancient? It's the one I usually still use to build Mozilla :) Wrc also works and has the advantage of being opensource.
Title: Re: AVxCAT 1.4 alpha
Post by: Andi B. on February 21, 2016, 11:09:06 am
I've a program which needs an old rc version (Version 4.00.011 Oct 10 2000) to build. For other programs I sometimes switch versions during development as sometimes rc4 gives better error messages than rc5.

Usually I use this version - IBM RC (Resource Compiler) Version 5.00.007 Jan 30 2003. So it may depend on your source code/development environment which version you should use.

For new projects it's probably better to start with OpenWatcoms wrc.
Title: Re: AVxCAT 1.4 alpha
Post by: Remy on February 21, 2016, 11:20:57 pm
It looks like drdialog is only compatible with an older version...  :(
Title: Re: AVxCAT 1.4 alpha
Post by: muffetta on February 22, 2016, 10:32:05 am
It looks like drdialog is only compatible with an older version...  :(
Fortunatly this is no true: both work very well, simply rename WRC.EXE into RC.EXE, in case you prefer the Watcom resource compiler, prepending right paths accordlying to your needs.
Have nice Dialogs  ;) !
Title: Re: AVxCAT 1.4 alpha
Post by: Remy on February 22, 2016, 05:06:57 pm
Nice, I will give it a try.
Title: Re: AVxCAT 1.4 alpha
Post by: Remy on February 23, 2016, 05:49:33 pm
Hi Dariusz,

I changed several parts of the internal filemanager and corrected some other issue I found (e.g. drop down list for presets incorrect after prévious update).

http://remydodin.levillage.org/outils/avxcat_140beta1.zip

File manager should be faster and of course better ( I hope )
I no more see the unstability issue I could find previously. I hope it is fine for you too now.
( No special debug entries added )

note: I used wrc.exe this time (it's ok)


Regards.
Title: Re: AVxCAT 1.4 alpha
Post by: Remy on February 26, 2016, 09:59:09 pm
Updated to beta2    ( change beta1 by beta2 from the download link to get the update )
( same as beta1 but changed and corrected seek position under video advanced option. Now, it is very fast  ;) , optimized some code and starting video using KMP player under video advanced option will start at selected start-time )

Any feedback about beta1 test ?
Regards
 
Title: Re: AVxCAT 1.4 alpha
Post by: Dariusz Piatkowski on February 27, 2016, 01:04:59 am
Hi Remy!

Updated to beta2    ( change beta1 by beta2 from the download link to get the update )
( same as beta1 but changed and corrected seek position under video advanced option. Now, it is very fast  ;) , optimized some code and starting video using KMP player under video advanced option will start at selected start-time )

Any feedback about beta1 test ?

Well, I tested Beta1 last night...result is stil the same. Here is what I noticed though, the lock does not happen "immediately", instead I can hear the disk head seeking sounds, which tells me that whatever API is being used to retrieve HD/disk information kicks off, it is after that event that the system goes into this soft-lock.

In my particular case it takes 2 CTRL-ALT-DEL hits before the 3rd one finally reboots the system...and reboot itself is also an OS shut-down/close, followed by a power cycle, so this is the reason why I am not calling it a HARD-LOCK. Upon a re-boot I never have to do CHKDSK...so at least the disks are not flagged as 'dirty'.

I will test out Beta2 now...can I attempt to use a PRE/POST 'owncmd.txt' logic here? So far I have only tested with just the PRE owncmd.txt file, as I believe you were making some changes to enable the POST processing.

Thanks!
Title: Re: AVxCAT 1.4 alpha
Post by: Remy on February 27, 2016, 04:07:26 pm
Hi Dariuz,

New beta2 should be better due I found the unstability issue I could see sometimes. In particular situation, a process was called as mutch as you have files under the current directory instead of firering only ones (this resulted into overflow followed by AVXCAT crash). Now, this is corrected     

I just refreshed the beta2 on my server, please take the new one (some more updates - display of codecs, formats, version under help changed and simplified + thumbnail extraction when creating html for presentation is now very fast too - and now mp2 conversion works too and only ogv will not work)
Yes, you can use pre and post commands
put each command in a new line
no prefixed line or with a prefix of  'B'  (before) , it is placed as PRE command
e.g.     B @vol C:    or    @vol C:
If it is prefixed by 'A'  (after) then it is used as POST command
e.g.     A @vol C:

PS: This beta2 zip will show "beta4" under about.   

Regards 
Title: Re: AVxCAT 1.4 alpha
Post by: Remy on March 06, 2016, 03:25:34 pm
Any feedback about latest build ?
Title: Re: AVxCAT 1.4 alpha
Post by: Dariusz Piatkowski on March 13, 2016, 04:00:11 pm
Hi Remy,

Any feedback about latest build ?

Sorry...got a little behind here...away on business last week...but I will get some testing done today...

Thanks,
-Dariusz
Title: Re: AVxCAT 1.4 alpha
Post by: Dave Yeo on March 29, 2016, 01:06:06 am
I've uploaded FFmpeg v3.0 to Hobbes, http://hobbes.nmsu.edu/h-search.php?button=Search&key=ffmpeg-v3.0&dir=%2F (http://hobbes.nmsu.edu/h-search.php?button=Search&key=ffmpeg-v3.0&dir=%2F)
Remy, do you want to update AVxCAT to support it.  Also let me know if there is anything I missed as v3.0.1 will be released shortly.
Title: Re: AVxCAT 1.4 alpha
Post by: Remy on March 29, 2016, 01:05:45 pm
I've uploaded FFmpeg v3.0 to Hobbes, http://hobbes.nmsu.edu/h-search.php?button=Search&key=ffmpeg-v3.0&dir=%2F (http://hobbes.nmsu.edu/h-search.php?button=Search&key=ffmpeg-v3.0&dir=%2F)
Remy, do you want to update AVxCAT to support it.  Also let me know if there is anything I missed as v3.0.1 will be released shortly.

Thanks Dave,
I'll give it a try to check compatibility.
Title: Re: AVxCAT 1.4 alpha
Post by: muffetta on March 29, 2016, 04:48:35 pm
I'll give it a try to check compatibility.
Hi Remy and Dave, it seems quite compatible with latest releases (no tested deeply but works quite well).
Thanks for your efforts!
Regards
Title: Re: AVxCAT 1.4 alpha
Post by: Remy on March 30, 2016, 07:51:00 pm
I'll give it a try to check compatibility.
Hi Remy and Dave, it seems quite compatible with latest releases (no tested deeply but works quite well).
Thanks for your efforts!
Regards

Hi!

It is strange it works for you... 
Can you please post the result of your AVxCAT parameters dialog ?
Do you have V3.0.0 listed or v2.1.5 ?

I checked for compatibility but I could not get pipe results from any direct command issued from under drdialog with ffmpeg v3 build !
This is the first ffmpeg builf not returning messages into the pipe command issued from under AVxCAT !
Without a working pipe, conversion will not work.     

I checked my environment and installed Dlls and all are ok.
Until this issue is found and corrected, ffmpeg v3 is currently falgged as not compatible.
Title: Re: AVxCAT 1.4 alpha
Post by: muffetta on March 30, 2016, 08:36:33 pm
I'll give it a try to check compatibility.
Hi Remy and Dave, it seems quite compatible with latest releases...
Hi!

It is strange it works for you... 
Can you please post the result of your AVxCAT parameters dialog ?
Do you have V3.0.0 listed or v2.1.5 ?...
FFmpeg v.2.1.5, sorry, I badly expressed: installed/tested with appropriate instructions, both seem to work quite fine (not tested much).
Regards.
Title: Re: AVxCAT 1.4 alpha
Post by: Remy on March 30, 2016, 09:50:25 pm
Ok,

It works without using pipe fonction ( command line mode ) but not throught AVxCAT
I see that the wrong version is displaied which tells me PIPE didn't return required information out of FFMPEG.

I could read some information on FFMPEG development that they changed how pipe is working !
It would be nice having a FFMPEG V3 build with a well working (like under all prévious build) pipe function
Remember, all previous ffmpeg build up to 2.1.5 are well working with pipe under drdialog and using rxu.dll.

Hi Dave,
The problem I reported several weeks ago is always present and it is not possible to make this build compatible with AVxCAT until a well working pipe process with drdialog using RXU.dll (required).

It is very ease test, create a single drdialog, load rxutils and rxu and run ffmpeg from under drdialog using a named rxqueue (pipe) with FIFO option.

From all changes I could read under this build, resolving this issue should made it work with AVxCAT   

PS: I see a character size problem (V1, V2, Both) under this dialog I will resolve under next build.
 
Thanks
Cheers/2
Title: Re: AVxCAT 1.4 alpha
Post by: TeLLie on March 30, 2016, 11:49:40 pm
Hi Remi,

Just try AVxCat

see http://imagizer.imageshack.com/img922/9875/f8ISEQ.png

Only convert a mp4 to a wmv and that worked.
Title: Re: AVxCAT 1.4 alpha
Post by: Remy on March 31, 2016, 01:11:48 am
Hi TeLLie,

Good with ffmpeg v3.0.1  :D
Could you please provide me with this 3.0.1 build ?

( I see a bug I'll resolve - ffmpeg debug-log should be enabled and not disabled )   

Can you please tell me more about your environment ?
Thanks.


Title: Re: AVxCAT 1.4 alpha
Post by: muffetta on March 31, 2016, 07:54:40 am
Just try AVxCat

Only convert a mp4 to a wmv and that worked.
Maybe they are working on it, however syntax has changed a lot of times, release by release. My logs attempting to convert into wmv, the same you did, in this case here works right only SVN-r25157 and 2.1.5.
Regards.
Title: Re: AVxCAT 1.4 alpha
Post by: Dave Yeo on March 31, 2016, 07:57:05 am

Hi Dave,
The problem I reported several weeks ago is always present and it is not possible to make this build compatible with AVxCAT until a well working pipe process with drdialog using RXU.dll (required).

It is very ease test, create a single drdialog, load rxutils and rxu and run ffmpeg from under drdialog using a named rxqueue (pipe) with FIFO option.

From all changes I could read under this build, resolving this issue should made it work with AVxCAT   

OK, I built trunk and it worked fine with AVxCAT excepting H264 where I had some unrecognized commands. I guess something was screwed with my tree.
I'll download the 3.0.1 tarball and build and upload that.
Title: Re: AVxCAT 1.4 alpha
Post by: muffetta on March 31, 2016, 08:02:51 am
OK, I built trunk and it worked fine with AVxCAT....
As supposed, great news Dave!
Title: Re: AVxCAT 1.4 alpha
Post by: Remy on March 31, 2016, 12:34:37 pm
Just try AVxCat

Only convert a mp4 to a wmv and that worked.
Maybe they are working on it, however syntax has changed a lot of times, release by release. My logs attempting to convert into wmv, the same you did, in this case here works right only SVN-r25157 and 2.1.5.
Regards.

Note: ffmpeg 1.2.1 was not supported by AVxCAT despite the pipe function works well.

As soon, version 3.0 didn't return expected information, the correct syntax can not be generated like it is with 2.1.5
V3.0.1 seems to resolve v3.0 issue and this is a very good news  :)

 8)
Title: Re: AVxCAT 1.4 alpha
Post by: Remy on March 31, 2016, 12:43:27 pm

Hi Dave,
The problem I reported several weeks ago is always present and it is not possible to make this build compatible with AVxCAT until a well working pipe process with drdialog using RXU.dll (required).

It is very ease test, create a single drdialog, load rxutils and rxu and run ffmpeg from under drdialog using a named rxqueue (pipe) with FIFO option.

From all changes I could read under this build, resolving this issue should made it work with AVxCAT   

OK, I built trunk and it worked fine with AVxCAT excepting H264 where I had some unrecognized commands. I guess something was screwed with my tree.
I'll download the 3.0.1 tarball and build and upload that.

Great news.... thanks
Waiting on it for tests
 
 8)
Title: Re: AVxCAT 1.4 alpha
Post by: Remy on April 01, 2016, 06:36:48 pm
Hi !

A few news.
I could do a few test with a basic ffmpeg 3.0.1 build and found several things.
This build required me to install several dlls and freetyp6.dll why v3.0 build didn't request it when running it in line mode cmd.

I had some changes to do on AVxCAT for compatibility and more should be done in next days
(e.g. crop like croptop cropbottom and pad functions have changed since v3.0 and uses now -filter option)
Currently, I could well convert video files and saw v3.0.1 allowing a few more fps than 2.1.5 ( nice )

Curious, I tried again the v3.0 (refered as n3.0 after having changed dlls for 3.0.1 and n3.0 works now !
I search which dll was the culprit making no return into the pipe for drdialog and it is " freetype6.dll "  <<

As soon my code is changed and some tests could be done, I'll post a message about next available beta build
Regards 

Update: first test are promizing
Title: Re: AVxCAT 1.4 alpha
Post by: Remy on April 11, 2016, 01:55:41 am
Some news.

After a lot of changes and code re-write since last beta and many tests with some new ffmpeg 3.0.1 build, all test seems to pass now as well as added vp9 (ogg or opus) and libtheora and more available options as well.

* Thanks to Dave and Gian Filippo having worked together with me resulting into finding source of some problems and new enabled codec support ( e.g. libopus with vp9 )           
 
I hope to publish the updated AVxCAT build very soon (docs to update etc...) with new added compatibility like ffmpeg v3.0.1 r2 (hobbes) and preserving ffmpeg backlevel support ( more ffmpeg version can be available on the disk now ) 
The new comming build will be a big major update

Cheers/2
Title: Re: AVxCAT 1.4 alpha
Post by: Remy on April 12, 2016, 10:52:01 pm
After a lot of work and taking account reported problems and end user whishes,

AVxCAT V1.4.0 (major update and added compatibility with ffmpeg 1.2.1, 2.1.5, v3 up to v3.0.1 r2) is now available on my web site.  See the "changelog.Readme" under AVxCAT page.

Thanks to those having reported found issue and having done tests as well to Dave and Gian Filippo having worked hard on ffmpeg.