Author Topic: AVxCAT 1.4 alpha  (Read 41763 times)

Remy

  • Hero Member
  • *****
  • Posts: 645
  • Karma: +9/-1
    • View Profile
Re: AVxCAT 1.4 alpha
« Reply #15 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   

Dave Yeo

  • Hero Member
  • *****
  • Posts: 4788
  • Karma: +99/-1
    • View Profile
Re: AVxCAT 1.4 alpha
« Reply #16 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

Remy

  • Hero Member
  • *****
  • Posts: 645
  • Karma: +9/-1
    • View Profile
Re: AVxCAT 1.4 alpha
« Reply #17 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...   

Dariusz Piatkowski

  • Hero Member
  • *****
  • Posts: 1317
  • Karma: +26/-0
    • View Profile
Re: AVxCAT 1.4 alpha
« Reply #18 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

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?

Dariusz Piatkowski

  • Hero Member
  • *****
  • Posts: 1317
  • Karma: +26/-0
    • View Profile
Re: AVxCAT 1.4 alpha
« Reply #19 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!!!

Dariusz Piatkowski

  • Hero Member
  • *****
  • Posts: 1317
  • Karma: +26/-0
    • View Profile
Re: AVxCAT 1.4 alpha
« Reply #20 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*

Remy

  • Hero Member
  • *****
  • Posts: 645
  • Karma: +9/-1
    • View Profile
Re: AVxCAT 1.4 alpha
« Reply #21 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

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.

Remy

  • Hero Member
  • *****
  • Posts: 645
  • Karma: +9/-1
    • View Profile
Re: AVxCAT 1.4 alpha
« Reply #22 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...

Remy

  • Hero Member
  • *****
  • Posts: 645
  • Karma: +9/-1
    • View Profile
Re: AVxCAT 1.4 alpha
« Reply #23 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   

Dave Yeo

  • Hero Member
  • *****
  • Posts: 4788
  • Karma: +99/-1
    • View Profile
Re: AVxCAT 1.4 alpha
« Reply #24 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.

Remy

  • Hero Member
  • *****
  • Posts: 645
  • Karma: +9/-1
    • View Profile
Re: AVxCAT 1.4 alpha
« Reply #25 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)
« Last Edit: February 21, 2016, 01:07:09 am by Rem »

Dave Yeo

  • Hero Member
  • *****
  • Posts: 4788
  • Karma: +99/-1
    • View Profile
Re: AVxCAT 1.4 alpha
« Reply #26 on: February 21, 2016, 02:45:23 am »
Could try wrc from OpenWatcom. The syntax may be slightly different.

Andreas Schnellbacher

  • Hero Member
  • *****
  • Posts: 827
  • Karma: +14/-0
    • View Profile
Re: AVxCAT 1.4 alpha
« Reply #27 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

This link is still present on Steve's Warpzilla page.

Dave Yeo

  • Hero Member
  • *****
  • Posts: 4788
  • Karma: +99/-1
    • View Profile
Re: AVxCAT 1.4 alpha
« Reply #28 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

This link is still present on Steve's Warpzilla page.

Ancient? It's the one I usually still use to build Mozilla :) Wrc also works and has the advantage of being opensource.

Andi B.

  • Hero Member
  • *****
  • Posts: 812
  • Karma: +11/-2
    • View Profile
Re: AVxCAT 1.4 alpha
« Reply #29 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.