[MSEide-MSEgui-talk] MSE and ./configure

classic Classic list List threaded Threaded
27 messages Options
12
Reply | Threaded
Open this post in threaded view
|

[MSEide-MSEgui-talk] MSE and ./configure

fredvs
Hello.

There is a **very** high number of different Unix distros, widget-set,
window-manager, etc,...
Same for Windows versions.

So, could it not be possible to have a king of ./configure (same idea that
used for compiling C programs) loaded at begin or before the app, that will
check all the system and give the option to adapt the default parameters for
each application?

Fre;D



--
Sent from: http://mseide-msegui-talk.13964.n8.nabble.com/

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
mseide-msegui-talk mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk
mse
Reply | Threaded
Open this post in threaded view
|

Re: [MSEide-MSEgui-talk] MSE and ./configure

mse
Administrator
On 02/20/2018 05:40 PM, fredvs wrote:

> Hello.
>
> There is a **very** high number of different Unix distros, widget-set,
> window-manager, etc,...
> Same for Windows versions.
>
> So, could it not be possible to have a king of ./configure (same idea that
> used for compiling C programs) loaded at begin or before the app, that will
> check all the system and give the option to adapt the default parameters for
> each application?
>
Which default parameters?

Martin

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
mseide-msegui-talk mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk
Reply | Threaded
Open this post in threaded view
|

Re: [MSEide-MSEgui-talk] MSE and ./configure

fredvs
Hello Martin.

OK, I suppose that mse does this "pre-configure" at loading of each
application.
I suppose too that the program check what kind of windows manager is used,
what atoms can be used, etc...

> Which default parameters?

i would like, if it is possible, to have a script or program that check the
system and all the stuff needed by MSE.
And, as result, like ./configure does for C programs, show a list with all
the features that mse can deal.

This to help the developer (and you when there are problems) to really know
what is in his system.

I ask it to you because (AFAIK) mse does that kind of check at loading and
so you could (maybe easily) give a  script for this.

Fre;D






--
Sent from: http://mseide-msegui-talk.13964.n8.nabble.com/

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
mseide-msegui-talk mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk
mse
Reply | Threaded
Open this post in threaded view
|

Re: [MSEide-MSEgui-talk] MSE and ./configure

mse
Administrator
On Wednesday 28 February 2018 13:25:52 fredvs wrote:

> Hello Martin.
>
> OK, I suppose that mse does this "pre-configure" at loading of each
> application.
> I suppose too that the program check what kind of windows manager is used,
> what atoms can be used, etc...
>
> > Which default parameters?
>
> i would like, if it is possible, to have a script or program that check the
> system and all the stuff needed by MSE.
> And, as result, like ./configure does for C programs, show a list with all
> the features that mse can deal.
>
Can you be more specific? Which features exactly? MSEgui tries to support the
features independent of the environment. In gui_init() of
lib/common/kernel/linux/mseguiintf.pas
and
lib/common/kernel/windows/mseguiintf.pas
some initialization and window property query will be done, in the
initialization section of mseguiintf.pas the loading of facultative system
libraries will be done.
MSEgui does not try to determine the active window manager, that would be
a "barrel without bottom" as one says in German.
The MSEgui command line parameters are listed in README.TXT:
"
MSEgui command line parameters
******************************
--FONTALIAS=<alias>,<fontname>[,<fontheight>[,<fontwidth>[,<options>[,<xscale>]
                              [,<ancestor>]]]]
 Change the used fonts. Example for a 16 pixel height default font:
 --FONTALIAS=stf_default,,16

--NOZEROLINES
 Use 1-width lines instead of 0-width lines. X11 only. Workaround for buggy
HW-accelerated
 X-servers which don't draw lineends exactly. Can degrade performance, see
 https://bugzilla.opensuse.org/show_bug.cgi?id=1021803

--NOZORDERHANDLING
 Do not touch Z-order of the windows.

--NORESTACKWINDOW
 Do not use the NET_RESTACK_WINDOW protocol.

--RESTACKWINDOW
 Use the NET_RESTACK_WINDOW protocol.

--NORECONFIGUREWMWINDOW
 Do not use xreconfigurewmwindow() for window stacking operation.

--RECONFIGUREWMWINDOW
 Use xreconfigurewmwindow() for window stacking operation.

--STACKMODEBELOWWORKAROUND
 Necessary for windowmanagers with buggy xreconfigurewmwindow() handling.

--NOSTACKMODEBELOWWORKAROUND
 No workaround.

--TOPLEVELRAISE
 Use the top level frame window id instead of the application client window id
 for window raise operation. Implies --NORESTACKWINDOW and
 --NORECONFIGUREWMWINDOW.

--NOSTATICGRAVITY
 Simulates staticgravity for buggy window managers.
"

Martin

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
mseide-msegui-talk mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk
Reply | Threaded
Open this post in threaded view
|

Re: [MSEide-MSEgui-talk] MSE and ./configure

fredvs
> Can you be more specific?

OK, I will try.

Here, for example the result of configure for espeak-ng:

fred@fred-Lenovo-YOGA-300-11IBY ~/espeak-ng-master $ ./configure
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking build system type... x86_64-unknown-linux-gnu
checking host system type... x86_64-unknown-linux-gnu
checking how to print strings... printf
checking for style of include used by make... GNU
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking whether gcc understands -c and -o together... yes
checking dependency style of gcc... gcc3
checking for a sed that does not truncate output... /bin/sed
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for fgrep... /bin/grep -F
checking for ld used by gcc... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
checking the name lister (/usr/bin/nm -B) interface... BSD nm
checking whether ln -s works... yes
checking the maximum length of command line arguments... 1572864
checking whether the shell understands some XSI constructs... yes
checking whether the shell understands "+="... yes
checking how to convert x86_64-unknown-linux-gnu file names to
x86_64-unknown-linux-gnu format... func_convert_file_noop
checking how to convert x86_64-unknown-linux-gnu file names to toolchain
format... func_convert_file_noop
checking for /usr/bin/ld option to reload object files... -r
checking for objdump... objdump
checking how to recognize dependent libraries... pass_all
checking for dlltool... no
checking how to associate runtime and link libraries... printf %s\n
checking for ar... ar
checking for archiver @FILE support... @
checking for strip... strip
checking for ranlib... ranlib
checking command to parse /usr/bin/nm -B output from gcc object... ok
checking for sysroot... no
checking for mt... mt
checking if mt is a manifest tool... no
checking how to run the C preprocessor... gcc -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking for dlfcn.h... yes
checking for objdir... .libs
checking if gcc supports -fno-rtti -fno-exceptions... no
checking for gcc option to produce PIC... -fPIC -DPIC
checking if gcc PIC flag -fPIC -DPIC works... yes
checking if gcc static flag -static works... yes
checking if gcc supports -c -o file.o... yes
checking if gcc supports -c -o file.o... (cached) yes
checking whether the gcc linker (/usr/bin/ld -m elf_x86_64) supports shared
libraries... yes
checking whether -lc should be explicitly linked in... no
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... yes
checking whether make supports nested variables... (cached) yes
checking whether make supports nested variables... (cached) yes
checking for gcc... (cached) gcc
checking whether we are using the GNU C compiler... (cached) yes
checking whether gcc accepts -g... (cached) yes
checking for gcc option to accept ISO C89... (cached) none needed
checking whether gcc understands -c and -o together... (cached) yes
checking dependency style of gcc... (cached) gcc3
checking whether make sets $(MAKE)... (cached) yes
checking whether ln -s works... yes
checking for ndk-build... no
checking for gradle... no
./configure: line 12518: 0: command not found
checking if gcc supports C99 without any flags... no
checking if gcc supports C99 with the -std=c99 flag... yes
checking if gcc supports C99... -std=c99
checking if targeting FreeBSD... no
checking endian.h usability... yes
checking endian.h presence... yes
checking for endian.h... yes
checking fcntl.h usability... yes
checking fcntl.h presence... yes
checking for fcntl.h... yes
checking getopt.h usability... yes
checking getopt.h presence... yes
checking for getopt.h... yes
checking locale.h usability... yes
checking locale.h presence... yes
checking for locale.h... yes
checking stddef.h usability... yes
checking stddef.h presence... yes
checking for stddef.h... yes
checking stdbool.h usability... yes
checking stdbool.h presence... yes
checking for stdbool.h... yes
checking sys/endian.h usability... no
checking sys/endian.h presence... no
checking for sys/endian.h... no
checking sys/time.h usability... yes
checking sys/time.h presence... yes
checking for sys/time.h... yes
checking wchar.h usability... yes
checking wchar.h presence... yes
checking for wchar.h... yes
checking wctype.h usability... yes
checking wctype.h presence... yes
checking for wctype.h... yes
checking for size_t... yes
checking for ssize_t... yes
checking for uint16_t... yes
checking for uint32_t... yes
checking for uint64_t... yes
checking for pid_t... yes
checking vfork.h usability... no
checking vfork.h presence... no
checking for vfork.h... no
checking for fork... yes
checking for vfork... yes
checking for working fork... yes
checking for working vfork... (cached) yes
checking for working strcoll... yes
checking for error_at_line... yes
checking for dup2... yes
checking for getopt_long... yes
checking for gettimeofday... yes
checking for malloc... yes
checking for memchr... yes
checking for memmove... yes
checking for memset... yes
checking for mkdir... yes
checking for mkstemp... yes
checking for pow... no
checking for realloc... yes
checking for setlocale... yes
checking for sqrt... no
checking for strchr... yes
checking for strdup... yes
checking for strerror... yes
checking for strrchr... yes
checking for strstr... yes
checking pcaudiolib/audio.h usability... no
checking pcaudiolib/audio.h presence... no
checking for pcaudiolib/audio.h... no
checking sonic.h usability... no
checking sonic.h presence... no
checking for sonic.h... no
checking for ronn... no
checking whether C compiler accepts -Wimplicit... yes
checking whether C compiler accepts -Wmissing-prototypes... yes
checking whether C compiler accepts -Wreturn-type... yes
checking whether C compiler accepts -Wuninitialized... yes
checking whether C compiler accepts -Wunused... yes
checking whether C compiler accepts -Wunused-parameter... yes
checking that generated files are newer than configure... done
configure: creating ./config.status
config.status: creating Makefile
config.status: creating espeak-ng.pc
config.status: creating config.h
config.status: config.h is unchanged
config.status: executing depfiles commands
config.status: executing libtool commands
configure:

    Configuration for eSpeak NG complete.

        Source code location:          .

        C99 Compiler:                  gcc
        C99 Compiler flags:            -Wunused-parameter -Wunused
-Wuninitialized -Wreturn-type -Wmissing-prototypes -Wimplicit -g -O2
-std=c99

        Sonic:                         no
        PCAudioLib:                    no

        gradle (Android):              gradle
        ndk-build (Android):          

        Klatt:                         yes
        MBROLA:                        yes
        Async:                         yes

        Extended Dictionaries:
            Russian:                   no
            Chinese (Mandarin):        no
            Chinese (Cantonese):       no
------------------------------------------------------------------------------

You see that configure has checked the system with some yes/no result and
gives at final a "Configuration for eSpeak NG".

I would like something similar that gives MSEgui features dependent of the
environment.

If users have problem, one of the question will be: "Please show us the
result of MSEconfigure".

Fre;D

PS: Nothing to do with the topic... I do not have any sound with espeak-ng
;(




--
Sent from: http://mseide-msegui-talk.13964.n8.nabble.com/

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
mseide-msegui-talk mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk
mse
Reply | Threaded
Open this post in threaded view
|

Re: [MSEide-MSEgui-talk] MSE and ./configure

mse
Administrator
On Wednesday 28 February 2018 23:04:43 fredvs wrote:

> > Can you be more specific?
>
> OK, I will try.
>
> Here, for example the result of configure for espeak-ng:
>
> fred@fred-Lenovo-YOGA-300-11IBY ~/espeak-ng-master $ ./configure
> checking for a BSD-compatible install... /usr/bin/install -c
> checking whether build environment is sane... yes
> checking for a thread-safe mkdir -p... /bin/mkdir -p
> checking for gawk... gawk
[...]
>
> You see that configure has checked the system with some yes/no result and
> gives at final a "Configuration for eSpeak NG".
>
But that is completely unrelated to Free Pascal and MSEgui? Usual Free Pascal
projects don't need a complex build environment like usual gcc projects do.

> I would like something similar that gives MSEgui features dependent of the
> environment.

I still don't know what "MSEgui features dependent of the environment" you
mean, please provide examples.

AFAIK "configure" is a part of the GNU-Build-System:
https://www.gnu.org/software/automake/manual/automake.html#GNU-Build-System

>
> PS: Nothing to do with the topic... I do not have any sound with espeak-ng
> ;(
>
In order to send wave data to audio devices "pcaudiolib" is necessary, please
read README in the espeak-ng package.

Compiled libraries of libpcaudio.so, libsonic.so and libespeak-ng with the
MSEgui extensions (libespeak-ngsync.so, libespeak-ngwo.dll) are here:
https://sourceforge.net/projects/mseuniverse/files/eSpeakNG/

Martin

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
mseide-msegui-talk mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk
Reply | Threaded
Open this post in threaded view
|

Re: [MSEide-MSEgui-talk] MSE and ./configure

fredvs
> But that is completely unrelated to Free Pascal and MSEgui? Usual Free
Pascal
> projects don't need a complex build environment like usual gcc projects
> do.

Please Martin...
Of course I know that.

The idea was to give a script or program that will check the unix system and
give a list of all the features that MSE can use.
(like some particular atom properties, transparency for some trayicon in
somewindow-manager, etc...)

But ok, forget it, I will try to do it by myself.

> README in the espeak-ng package.

Re-please Martin...
Of course I did.

But there are conflicts with espeak vs espeak-ng.
I am busy to annoy espeak people for that.

Fre;D



--
Sent from: http://mseide-msegui-talk.13964.n8.nabble.com/

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
mseide-msegui-talk mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk
mse
Reply | Threaded
Open this post in threaded view
|

Re: [MSEide-MSEgui-talk] MSE and ./configure

mse
Administrator
On Thursday 01 March 2018 10:55:46 fredvs wrote:

> > But that is completely unrelated to Free Pascal and MSEgui? Usual Free
>
> Pascal
>
> > projects don't need a complex build environment like usual gcc projects
> > do.
>
> Please Martin...
> Of course I know that.
>
> The idea was to give a script or program that will check the unix system
> and give a list of all the features that MSE can use.
> (like some particular atom properties, transparency for some trayicon in
> somewindow-manager, etc...)
>
OK, you don't want a list of MSEgui features but a list of
Unix/Linux/desktop-environment/graphical-environment - features of a given
installation. That is a big task and out of scope of MSEgui I fear. I can't
help you here.
>
> > README in the espeak-ng package.
>
> Re-please Martin...
> Of course I did.
>
Your espeak-ng ./configure shows:

>     Configuration for eSpeak NG complete.
>
>         Source code location:          .
>
>         C99 Compiler:                  gcc
>         C99 Compiler flags:            -Wunused-parameter -Wunused
> -Wuninitialized -Wreturn-type -Wmissing-prototypes -Wimplicit -g -O2
> -std=c99
>
>         Sonic:                         no
>         PCAudioLib:                    no

PCAudioLib: no -> no output to audio device possible.

From README:
"
## Linux, Mac, BSD

### Dependencies

In order to build eSpeak NG, you need:

1.  a functional autotools system (`make`, `autoconf`, `automake`, `libtool`
    and `pkg-config`);
2.  a functional c compiler that supports C99 (e.g. gcc or clang).

Optionally, you need:

1.  the [pcaudiolib](https://github.com/espeak-ng/pcaudiolib) development
library
    to enable audio output;
3.  the [sonic](https://github.com/espeak-ng/sonic) development library to
    enable sonic audio speed up support;
4.  the `ronn` man-page markdown processor to build the man pages.
"

Please build and install sonic
https://github.com/espeak-ng/sonic
and pcaudiolib
https://github.com/espeak-ng/pcaudiolib
before you run ./configure of espeak-ng and check if it returns
"
         PCAudioLib:                    yes
"

Martin

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
mseide-msegui-talk mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk
Reply | Threaded
Open this post in threaded view
|

Re: [MSEide-MSEgui-talk] MSE and ./configure

fredvs
> OK, you don't want a list of MSEgui features but a list of
> Unix/Linux/desktop-environment/graphical-environment - features of a given
> installation.

Yeeep, you get it. ;)

> That is a big task and out of scope of MSEgui I fear. I can't help you
> here.

OK, no problem, I am a warrior explorer.

> Your espeak-ng ./configure shows:

Yes.

But following:
https://www.devmanuals.net/install/ubuntu/ubuntu-17-04-lts-Zesty-Zapus/installing-espeak-ng-on-ubuntu17.04.html

sudo apt-get install espeak-ng (the "classical" way to install espeak-ng
executable) gives:
"espeak-ng package not found".

Taste and color is something very personal.

In my case, I prefer the architecture of espeak (that uses portaudio only,
without any exotic pcaudiolib or libsonic libraries).

Also for the quality of sound, my ears prefer the result of espeak vs
espeak-ng.

But, like I said earlier, it is a question of taste.
(And I prefer the original vs the copy, Coca-cola vs Pepsi-cola, Intel vs
AMD, ....)

;)

Fre;D




And the most



--
Sent from: http://mseide-msegui-talk.13964.n8.nabble.com/

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
mseide-msegui-talk mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk
mse
Reply | Threaded
Open this post in threaded view
|

Re: [MSEide-MSEgui-talk] MSE and ./configure

mse
Administrator
On Thursday 01 March 2018 13:11:09 fredvs wrote:

>
> > Your espeak-ng ./configure shows:
>
> Yes.
>
> But following:
> https://www.devmanuals.net/install/ubuntu/ubuntu-17-04-lts-Zesty-Zapus/inst
>alling-espeak-ng-on-ubuntu17.04.html
>
> sudo apt-get install espeak-ng (the "classical" way to install espeak-ng
> executable) gives:
> "espeak-ng package not found".
>
Your Ubuntu installation or your repository setup seems to be broken.
Suggestion: build and install it from source.

> Taste and color is something very personal.
>
> In my case, I prefer the architecture of espeak (that uses portaudio only,
> without any exotic pcaudiolib or libsonic libraries).
>
Espeak project is abandoned and dead, see for example the official website:
http://espeak.sourceforge.net/
last commit was in 2015.

pcaudiolib is a small library which provides cross platform audio support like
portaudio. sonic AFAIK is a FFT lib optimized for speech synthesizing
purpose. Both are parts of the espeak-ng project AFAIK.
sonic is optional, you don't need it if you don't want to benefit from it's
performance gain.

> Also for the quality of sound, my ears prefer the result of espeak vs
> espeak-ng.
>
That is strange, you should submit your findings as bug reports:
https://github.com/espeak-ng/espeak-ng/issues

> But, like I said earlier, it is a question of taste.
> (And I prefer the original vs the copy, Coca-cola vs Pepsi-cola, Intel vs
> AMD, ....)
>
That is your choice...

Martin

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
mseide-msegui-talk mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk
mse
Reply | Threaded
Open this post in threaded view
|

Re: [MSEide-MSEgui-talk] MSE and ./configure

mse
Administrator
In reply to this post by fredvs
On Thursday 01 March 2018 13:11:09 fredvs wrote:
>
> Also for the quality of sound, my ears prefer the result of espeak vs
> espeak-ng.
>
Which OS? On Windows there is a problem with not double buffered audio driver.
Please use "espeak-ngwo.dll" from here
https://sourceforge.net/projects/mseuniverse/files/eSpeakNG/
rename it to "espeak-ng.dll" and replace the file from espeak-ng Windows
package. "espeak-ngwo.dll" uses double buffered output to waveOUT API, the
project is here:
https://gitlab.com/mseide-msegui/espeak-ngsync
https://gitlab.com/mseide-msegui/pcaudiolib

Martin

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
mseide-msegui-talk mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk
Reply | Threaded
Open this post in threaded view
|

Re: [MSEide-MSEgui-talk] MSE and ./configure

fredvs
In reply to this post by mse
> Your Ubuntu installation or your repository setup seems to be broken.

Maybe ;(

Did you try with a up-to-date Debian OS ? :

sudo apt-get install espeak-ng

Does it install espeak-ng ?

> Suggestion: build and install it from source.

Yes, I did it already.  And after (lot of) tips, espeak-ng was working.
I did many test espeak vs espeak-ng (executable).
Also test using only libraries.

Now, after un-installing espeak and espeak-ng, I did try, like common user,
to install the binaries (not compiling all) on a virgin system.

And with my system (maybe broken):

sudo apt-get install espeak  -----> Ok, espeak is installed.
sudo apt-get install espeak-ng  -----> NOT Ok, espeak-ng package not found.

> Espeak project is abandoned and dead, see for example the official
> website:
> http://espeak.sourceforge.net/

Huh,  on my maybe broken system,  I get:
"http://espeak.sourceforge.net is not accessible"

Strange indeed...

> pcaudiolib is a small library which provides cross platform audio support
> like portaudio.

https://github.com/rhdunn/pcaudiolib

Hum, nice (but no comparaison with the huge number of cross-platform that
Portaudio can do).

Ok, ok, you win, I will study espeak-ng more deeply.

>> Also for the quality of sound, my ears prefer the result of espeak vs
>> espeak-ng.
> That is strange, you should submit your findings as bug reports:

;-)

Yes my ears are very strange...

Thanks Martin.

Fre;D













--
Sent from: http://mseide-msegui-talk.13964.n8.nabble.com/

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
mseide-msegui-talk mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk
Reply | Threaded
Open this post in threaded view
|

Re: [MSEide-MSEgui-talk] MSE and ./configure

fredvs
In reply to this post by mse

> Your Ubuntu installation or your repository setup seems to be broken.

Maybe ;(

Did you try with a up-to-date Debian OS ? :

sudo apt-get install espeak-ng

Does it install espeak-ng ?

> Suggestion: build and install it from source.

Yes, I did it already.  And after (lot of) tips, espeak-ng was working.
I did many test espeak vs espeak-ng (executable).
Also test using only libraries.

Now, after un-installing espeak and espeak-ng, I did try, like common user,
to install the binaries (not compiling all) on a virgin system.

And with my system (maybe broken):

sudo apt-get install espeak  -----> Ok, espeak is installed.
sudo apt-get install espeak-ng  -----> NOT Ok, espeak-ng package not found.

> Espeak project is abandoned and dead, see for example the official
> website:
> http://espeak.sourceforge.net/

Huh,  on my maybe broken system,  I get:
"http://espeak.sourceforge.net is not accessible"

Strange indeed...

> pcaudiolib is a small library which provides cross platform audio support
> like portaudio.

https://github.com/rhdunn/pcaudiolib

Hum, nice (but no comparaison with the huge number of cross-platform that
Portaudio can do).

Ok, ok, you win, I will study espeak-ng more deeply.

>> Also for the quality of sound, my ears prefer the result of espeak vs
>> espeak-ng.
> That is strange, you should submit your findings as bug reports:

;-)

Yes my ears are very strange...

Thanks Martin.

Fre;D




--
Sent from: http://mseide-msegui-talk.13964.n8.nabble.com/

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
mseide-msegui-talk mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk
Reply | Threaded
Open this post in threaded view
|

Re: [MSEide-MSEgui-talk] MSE and ./configure

fredvs
In reply to this post by mse


> Your Ubuntu installation or your repository setup seems to be broken. 

Maybe ;( 

Did you try with a up-to-date Debian OS ? : 

sudo apt-get install espeak-ng 

Does it install espeak-ng ? 

> Suggestion: build and install it from source. 

Yes, I did it already.  And after (lot of) tips, espeak-ng was working. 
I did many test espeak vs espeak-ng (executable). 
Also test using only libraries. 

Now, after un-installing espeak and espeak-ng, I did try, like common user, to install the binaries (not compiling all) on a virgin system. 

And with my system (maybe broken): 

sudo apt-get install espeak  -----> Ok, espeak is installed. 
sudo apt-get install espeak-ng  -----> NOT Ok, espeak-ng package not found. 

> Espeak project is abandoned and dead, see for example the official website: 
> http://espeak.sourceforge.net/

Huh,  on my maybe broken system,  I get: 
"http://espeak.sourceforge.net is not accessible" 

Strange indeed... 

> pcaudiolib is a small library which provides cross platform audio support like portaudio. 

https://github.com/rhdunn/pcaudiolib

Hum, nice (but no comparaison with the huge number of cross-platform that Portaudio can do). 

Ok, ok, you win, I will study espeak-ng more deeply. 

>> Also for the quality of sound, my ears prefer the result of espeak vs  espeak-ng. 
> That is strange, you should submit your findings as bug reports: 

;-) 

Yes my ears are very strange... 

Thanks Martin. 

Fre;D

PS: I did try to sent this via Nabble.com and seems not sent. If it was, sorry for the 2 X. 



------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
mseide-msegui-talk mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk
mse
Reply | Threaded
Open this post in threaded view
|

Re: [MSEide-MSEgui-talk] MSE and ./configure

mse
Administrator
On Thursday 01 March 2018 17:32:14 Fred van Stappen wrote:

> > Your Ubuntu installation or your repository setup seems to be broken.
>
> Maybe ;(
>
> Did you try with a up-to-date Debian OS ? :
>
> sudo apt-get install espeak-ng
>
> Does it install espeak-ng ?
>
I don't have Debian.

> > Suggestion: build and install it from source.
>
> Yes, I did it already.  And after (lot of) tips, espeak-ng was working.
> I did many test espeak vs espeak-ng (executable).
> Also test using only libraries.
>
> Now, after un-installing espeak and espeak-ng, I did try, like common user,
> to install the binaries (not compiling all) on a virgin system.
>
> And with my system (maybe broken):
>
> sudo apt-get install espeak  -----> Ok, espeak is installed.
> sudo apt-get install espeak-ng  -----> NOT Ok, espeak-ng package not found.
>
Maybe there is no espeak-ng Debian package or it is in an unofficial
repository or in a repository you did not add to your package configuration?

> > Espeak project is abandoned and dead, see for example the official
> > website: http://espeak.sourceforge.net/
>
> Huh,  on my maybe broken system,  I get:
> "http://espeak.sourceforge.net is not accessible"
>
> Strange indeed...
>
Exactly. AFAIK espeak-ng has been forked because the eSpeak owner could not be
contacted anymore.

> > pcaudiolib is a small library which provides cross platform audio support
> > like portaudio.
>
> https://github.com/rhdunn/pcaudiolib
>
> Hum, nice (but no comparaison with the huge number of cross-platform that
> Portaudio can do).
>
pcaudiolib supports the platforms which espeak-ng supports.

> >> Also for the quality of sound, my ears prefer the result of espeak vs
> >> espeak-ng.
> >
> > That is strange, you should submit your findings as bug reports:
>
> ;-)
>
> Yes my ears are very strange...
>
It is strange that it sounds different because espeak-ng actually is the same
codebase with a better API and some cleanup. Do you really compare the same
voices, variants and language files?

Martin

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
mseide-msegui-talk mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk
Reply | Threaded
Open this post in threaded view
|

Re: [MSEide-MSEgui-talk] MSE and ./configure

fredvs
In reply to this post by mse
Oooops, a invasion of my same message, sorry for this...

>pcaudiolib is a small library which provides cross platform audio support
like portaudio

https://github.com/espeak-ng/espeak-ng/issues/413

Fre;D



--
Sent from: http://mseide-msegui-talk.13964.n8.nabble.com/

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
mseide-msegui-talk mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk
mse
Reply | Threaded
Open this post in threaded view
|

Re: [MSEide-MSEgui-talk] MSE and ./configure

mse
Administrator
On Thursday 01 March 2018 18:19:14 fredvs wrote:
> Oooops, a invasion of my same message, sorry for this...
>
> >pcaudiolib is a small library which provides cross platform audio support
>
> like portaudio
>
> https://github.com/espeak-ng/espeak-ng/issues/413
>
pcaudiolib calls portaudio if requested. I assume the pcaudiolib author uses
pcaudiolib in different projects so he did not built in the pcaudiolib
functionality directly into espeak-ng.
I made an interface for pcaudiolib for older Windows versions which uses the
waveOUT API without the need to install another audio library.
https://gitlab.com/mseide-msegui/pcaudiolib/blob/mse/src/waveout.c
pcaudiolib will be linked statically on Windows.

Martin

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
mseide-msegui-talk mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk
Reply | Threaded
Open this post in threaded view
|

Re: [MSEide-MSEgui-talk] MSE and ./configure

fredvs
> pcaudiolib calls portaudio if requested.

What do you mean ?




--
Sent from: http://mseide-msegui-talk.13964.n8.nabble.com/

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
mseide-msegui-talk mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk
Reply | Threaded
Open this post in threaded view
|

Re: [MSEide-MSEgui-talk] MSE and ./configure

fredvs
In reply to this post by mse
> pcaudiolib calls portaudio if requested.

Are you sure ?

In README.md, line 187:

#### Audio Output Configuration

The following `configure` options control which audio interfaces to use:

| Option              | Audio Interfaces | Default |
|---------------------|------------------|---------|
| `--with-pulseaudio` | PulseAudio       | yes     |
| `--with-portaudio`  | PortAudio        | yes     |
_____________________________________________________________________

But in the script configure there is no `--with-portaudio flag !

And if you take a look at CHANGELOG.md, at line 216:

*  Removed the local portaudio header files.
*  Use the system's sonic library and header files.
_____________________________________________________________________

So, IMHO, portaudio is not ever used anymore (and README.md should be
updated).

> so he did not built in the pcaudiolib functionality directly into
> espeak-ng

Hum, once again IMHO, this is sad, a unique library/binary should be good
too.
Why not as flag in configure ? ;)

But maybe MSE will propose it...

Fre;D







--
Sent from: http://mseide-msegui-talk.13964.n8.nabble.com/

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
mseide-msegui-talk mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk
mse
Reply | Threaded
Open this post in threaded view
|

Re: [MSEide-MSEgui-talk] MSE and ./configure

mse
Administrator
In reply to this post by fredvs
On Friday 02 March 2018 00:29:49 fredvs wrote:
>
> So, IMHO, portaudio is not ever used anymore (and README.md should be
> updated).
>
You are right, pcaudiolib/source/src/audio.c:
"
struct audio_object *
create_audio_device_object(const char *device,
                           const char *application_name,
                           const char *description)
{
        struct audio_object *object;
#if defined(_WIN32) || defined(_WIN64)
#ifdef NO_XAUDIO2
        if ((object = create_waveout_object(device, application_name,
description)) != NULL)
                return object;
#else
        if ((object = create_xaudio2_object(device, application_name,
description)) != NULL)
                return object;
#endif
#else
#if defined(__APPLE__)
        if ((object = create_coreaudio_object(device, application_name,
description)) != NULL)
                return object;

#else
        if ((object = create_pulseaudio_object(device, application_name,
description)) != NULL)
                return object;
        if ((object = create_alsa_object(device, application_name, description)) !=
NULL)
                return object;
        if ((object = create_qsa_object(device, application_name, description)) !=
NULL)
                return object;
        if ((object = create_oss_object(device, application_name, description)) !=
NULL)
                return object;
#endif
#endif
        return NULL;
}
"

> > so he did not built in the pcaudiolib functionality directly into
> > espeak-ng
>
> Hum, once again IMHO, this is sad, a unique library/binary should be good
> too.

You can link pcaudiolib statically if you like. You can link all libraries in
all executables statically if you like. The disadvantage is that you need to
rebuild all applications which use a given library if the library needs to be
changed.
Assume pcaudiolib gets a new output object or a bug needs to be fixed. If
linked dynamically all applications which use pcaudiolib can use the new
pcaudiolib version without the need to recompile the applications.

Martin

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
mseide-msegui-talk mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk
12