headers
Al Oomens | 3 Mar 2010 14:46
Picon

Ecasound still work on Cygwin?

Does Ecasound still work on Windows using Cygwin? I have used it
before, but just downloaded and tried to build the current release
using the latest Cygwin, and it gives an error when compiling. Does
anyone else have this working?

--

-- 
Al Oomens
Wheaton, IL.
aloomens <at> gmail.com
http://www.aloomens.com
http://twitter.com/aloomens

------------------------------------------------------------------------------
Download Intel&#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Ecasound-list mailing list
Ecasound-list <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ecasound-list
Permalink | Reply | 2 comments |
headers
Dubphil | 14 Mar 2010 22:40
Picon
Favicon

lot of warning with chmute

Hello,

I discovered chmute and wanted to control it by midi :

I have this minimal example :

-b:128 -r:-1 -z:intbuf -z:db,100000 -n:"test" -X -z:noxruns -z:nopsr
-z:mixmode,avg
-Md:alsaseq,
-a:j1 -f:f32_le,2,48000  -i:jack
-a:j2 -f:f32_le,2,48000  -i:jack
-a:j1 -chmute:1 -km:1.00,0.00,1.00,60.00,1.00 -chmute:2
-km:1.00,0.00,2.00,60.00,1.00
-a:j2 -chmute:1 -km:1.00,0.00,1.00,60.00,2.00 -chmute:2
-km:1.00,0.00,2.00,60.00,2.00
-a:j1,j2 -f:f32_le,2,48000  -o:jack

When I push the mute buttons of my midi controler I have this warning :

Warning: type DBC_CHECK soft-assert 'from_channel > 0' failed at
 -> audiofx_mixing.cpp:233 [(null)]

with about 6 chmute in my ecs and lot of processing, sometimes this
warning floods the screen and Ecasound seems very bad at this moment,
quite unuseable.

Best regards

Philippe
(Continue reading)

Permalink | Reply | 6 comments |
headers
Joel Roth | 15 Mar 2010 08:17
Picon
Favicon

Re: lot of warning with chmute

On Sun, Mar 14, 2010 at 10:40:25PM +0100, Dubphil wrote:
> Hello,
> 
> I discovered chmute and wanted to control it by midi :
> 
> I have this minimal example :
> 
> -b:128 -r:-1 -z:intbuf -z:db,100000 -n:"test" -X -z:noxruns -z:nopsr
> -z:mixmode,avg
> -Md:alsaseq,
> -a:j1 -f:f32_le,2,48000  -i:jack
> -a:j2 -f:f32_le,2,48000  -i:jack
> -a:j1 -chmute:1 -km:1.00,0.00,1.00,60.00,1.00 -chmute:2
> -km:1.00,0.00,2.00,60.00,1.00
> -a:j2 -chmute:1 -km:1.00,0.00,1.00,60.00,2.00 -chmute:2
> -km:1.00,0.00,2.00,60.00,2.00
> -a:j1,j2 -f:f32_le,2,48000  -o:jack
> 
> When I push the mute buttons of my midi controler I have this warning :
> 
> Warning: type DBC_CHECK soft-assert 'from_channel > 0' failed at
>  -> audiofx_mixing.cpp:233 [(null)]
> 
> with about 6 chmute in my ecs and lot of processing, sometimes this
> warning floods the screen and Ecasound seems very bad at this moment,
> quite unuseable.

Hi Philippe,

According to the docs, the -chmute parameter is a channel
(Continue reading)

Permalink | Reply | 5 comments |
headers
Dubphil | 15 Mar 2010 09:10
Picon
Favicon

Re: lot of warning with chmute

Joel Roth a écrit , Le 15/03/2010 08:17:
> Hi Philippe,
> According to the docs, the -chmute parameter is a channel
> number.
>
> Probably you are not getting the result you want if
> you are expecting -chmute to behave as an on/off function
> taking zero as an argument, which your -km range assignment
> (0,2) suggests.
>
> The warning looks right to me, since you are assigning
> zero to from_channel.
>    

Thanks Joel, what do I need to give to the km range values parameters 
then ?

-km:1.00,0.00,0.00,60.00,1.00 ?

Sorry for not seeing this obvious.

Cheers

Philippe

PS: Joel, I have tested Namma, but it is not suited to my .ecs script 
(or I did not find the way to achieve it), would you mind tell me if it 
could be done with my .ecs ? If you are ok I will send you my script.

------------------------------------------------------------------------------
(Continue reading)

Permalink | Reply | 4 comments |
headers
Joel Roth | 15 Mar 2010 10:27
Picon
Favicon

Re: lot of warning with chmute

On Mon, Mar 15, 2010 at 09:10:04AM +0100, Dubphil wrote:
> Joel Roth a écrit , Le 15/03/2010 08:17:
> > Hi Philippe,
> > According to the docs, the -chmute parameter is a channel
> > number.
> >
> > Probably you are not getting the result you want if
> > you are expecting -chmute to behave as an on/off function
> > taking zero as an argument, which your -km range assignment
> > (0,2) suggests.
> >
> > The warning looks right to me, since you are assigning
> > zero to from_channel.
> >    
> 
> Thanks Joel, what do I need to give to the km range values parameters 
> then ?
> 
> -km:1.00,0.00,0.00,60.00,1.00 ?
> 
> Sorry for not seeing this obvious.

> I have this minimal example :
> 
> -b:128 -r:-1 -z:intbuf -z:db,100000 -n:"test" -X -z:noxruns -z:nopsr
> -z:mixmode,avg
> -Md:alsaseq,
> -a:j1 -f:f32_le,2,48000  -i:jack
> -a:j2 -f:f32_le,2,48000  -i:jack
> -a:j1 -chmute:1 -km:1.00,0.00,1.00,60.00,1.00 -chmute:2
(Continue reading)

Permalink | Reply | 3 comments |
headers
Dubphil | 15 Mar 2010 12:31
Picon
Favicon

Re: lot of warning with chmute

Joel Roth a écrit , Le 15/03/2010 10:27:
> You haven't said exactly what you are trying to do.
> You seem to want to selective mute each channel
> of a stereo signal. This is how I would do it for one
> stereo signal (untested).
>
> -a:j1 -f:f32_le,2,48000 -i:jack
> -eac:1,100 -km:2,0,100,60,1     # MIDI control amplification to channel 1
> -eac:2,100 -km:2,0,100,60,2     # MIDI control amplification to channel 2
> -o:jack
>
>    

in fact a mute button is not really setting the amplification to 0,  I 
really need to mute the stereo channel by switching off the sound and 
when I switch on the sound the level must stay at the value it has 
before the switch off. That's why chmute is exactly what I need.

> Probably you understand that -f:32_le,2,4800 -i:jack creates (but
> does not connect) ports ecasound:in_1 and ecasound:in_2.
> Likewise for -o:jack, you need to use jack_connect or
> qjackctl to make the connections to the audio device.
> (For connecting directly to the soundcard, you would
> use -i:jack,system.)
>    

yes of course, but I have a patchbay setup in Qjackctrl so no problem 
about this.

> What I don't know is if your MIDI button can be programmed
(Continue reading)

Permalink | Reply | 2 comments |
headers
Joel Roth | 15 Mar 2010 19:54
Picon
Favicon

Re: lot of warning with chmute


On Mon, Mar 15, 2010 at 12:31:36PM +0100, Dubphil wrote:
> Joel Roth a �crit , Le 15/03/2010 10:27:
> > You haven't said exactly what you are trying to do.
> > You seem to want to selective mute each channel
> > of a stereo signal. This is how I would do it for one
> > stereo signal (untested).
> >
> > -a:j1 -f:f32_le,2,48000 -i:jack
> > -eac:1,100 -km:2,0,100,60,1     # MIDI control amplification to channel 1
> > -eac:2,100 -km:2,0,100,60,2     # MIDI control amplification to channel 2
> > -o:jack
> >
> >    
> 
> in fact a mute button is not really setting the amplification to 0,  I 
> really need to mute the stereo channel by switching off the sound and 
> when I switch on the sound the level must stay at the value it has 
> before the switch off. That's why chmute is exactly what I need.

Well, you can have any number of amplification operators in 
the chain! One you can toggle between 0 and 100, the other
you can set to the volume you like.

For your interest, Nama does have a mute function. It cuts
in and out gradually, and also is used at transport
start/stop so the sound tapers smoothly.

I implemented it by saving and restoring the original volume
value, however, I like this idea of using a separate -ea (or
(Continue reading)

Permalink | Reply | 1 comment |
headers
Dubphil | 15 Mar 2010 20:27
Picon
Favicon

Re: lot of warning with chmute

Le 15/03/2010 19:54, Joel Roth a écrit :
> Well, you can have any number of amplification operators in
> the chain! One you can toggle between 0 and 100, the other
> you can set to the volume you like.
>    

ok I did not think of this

> For your interest, Nama does have a mute function. It cuts
> in and out gradually, and also is used at transport
> start/stop so the sound tapers smoothly.
>
> I implemented it by saving and restoring the original volume
> value, however, I like this idea of using a separate -ea (or
> -eadb) operator for muting. It would simplify things a bit.
>
> I can look at your .ecs file. An explanation of what
> you want to accomplish might also help.
>
> There is a good chance Nama can provide the signal flow
> that you want.
>
> Nowadays, Nama has two kinds of buses: Send buses are mainly
> for instrument monitors, and sub buses for grouping signals
> together. It also has post-fader inserts for running signals
> through JACK clients or external effects boxes.  I am just
> finishing up code that will allow pre-fader inserts as well,
> although somewhat lacking what the Perl community calls
> "tuits" (as in I'll get around to it<groan>)
>
(Continue reading)

Permalink | Reply | 0 comments |
headers
Artur | 21 Mar 2010 19:29
Picon
Favicon

Bug: -i:resample and -y

Hello.

Specifying start position (option -y) when using object type 'resample' gives 
unexpected results. In the following case:

ecasound -f:s16_le,1,96000 -i:resample,44100,file.wav -y:startpos -o:out.wav

startpos must be specified as wanted_startpos*44100/96000. Otherwise if you 
specify -y:30, processing will start not 30, but 30*96000/44100=65 seconds 
from the beginning of file.wav.
Ecasound version is 2.7.1. The same happens for resample-hq and resample-lq.

Bye.
--
Artur

------------------------------------------------------------------------------
Download Intel&#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Ecasound-list mailing list
Ecasound-list <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ecasound-list
Permalink | Reply | 2 comments |
headers
Julien Claassen | 21 Mar 2010 19:42
Picon

lv2 support?

Good evening!
   I was wondering, if there are any plans to support lv2 in the near future. 
I've just recently heard about a few plugins, that aren't available as LADSPA 
and I've heard them in action and felt a greed to use them. :-)
   I'm still not completely sure about all the LV2 features, but I think in 
general, they can be used in a similar way to LADSPA plugins.
   I think the LV2 standard is now rather stable and gets more acceptance 
across several apps. So I was just wondering, if it might be considered. Kai, 
what do you think about it? Would it be manageable, feasable?
   Kindest regards
              Julien

--------
Music was my first love and it will be my last (John Miles)

======== FIND MY WEB-PROJECT AT: ========
http://ltsb.sourceforge.net
the Linux TextBased Studio guide
======= AND MY PERSONAL PAGES AT: =======
http://www.juliencoder.de

------------------------------------------------------------------------------
Download Intel&#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Ecasound-list mailing list
Ecasound-list <at> lists.sourceforge.net
(Continue reading)

Permalink | Reply | 1 comment |

Gmane