[ANN] ZynAddSubFX 2.5.4 - The “Alambradas” Release

[juhana]

Physical modeling? Someone made, at year 2000 or so, a fantastic flute physical model/demo with Csync (now under hood of Reaktor). The post should be in music-dsp archives. The flute did not sound poor digital, nor bad like sampled flutes.

The parameters should be directly controllable at the time-line in fine detail (MIDI?). Simple note-on/off control would be bad, I'm sure.

Here are some example songs which use real instruments and skilled players. Turkish instruments; flutes and lutes.

Multiple instruments in the begin:
https://www.youtube.com/watch?v=h_O0H3b5ALE

Flute at 15 seconds:
https://www.youtube.com/watch?v=Zt-x8EznEUk

I believe that physical modeling with detailed parameter curves in time-line is worth of trying. Parameter curves made by analysing the real thing and by manipulating the curves.

[dsreyes1014]

How do I get the alsa backend to work?

I keep getting:

Code: Select all

Default IO did not initialize
Defaulting to NULL backend

I'm on Gentoo with alsa-1.1.1.

[fundamental]

How do I get the alsa backend to work?

I keep getting:

Code: Select all

Default IO did not initialize
Defaulting to NULL backend

I'm on Gentoo with alsa-1.1.1.

First, I'd make sure that you're trying to run the alsa backend. Try to run with 'zynaddsubfx -I ALSA -O ALSA' . If you still get this error, then there's likely another application using the default ALSA device. You can check for this with 'lsof /dev/dsp* /dev/snd/*'.

[dsreyes1014]

First, I'd make sure that you're trying to run the alsa backend. Try to run with 'zynaddsubfx -I ALSA -O ALSA' . If you still get this error, then there's likely another application using the default ALSA device. You can check for this with 'lsof /dev/dsp* /dev/snd/*'.

Using the alsa backend still gives this error and the lsof command returns nothing.

[dsreyes1014]

I typed in the lsof command wrong. I'm getting pulse to be using everything in the /dev/snd/* folder. I guess now the question is how do I get it to let it go so Zyn can use the card?

EDIT: I got pulseaudio removed from my Enlightenment desktop and it still gives the same error.

[fundamental]

I haven't worked with pulse audio, so I do not know how to work around it.

[dsreyes1014]

Has anyone had any issues with not being able to use alsa directly? I'm still having problems with this.

[dsreyes1014]

Hey guys. Is there a manual or doc with recent osc commands for zynaddsubfx? I'm interested in created a basic layout on Android to control part volume levels.

[fundamental]

Is there a manual or doc with recent osc commands for zynaddsubfx? I'm interested in created a basic layout on Android to control part volume levels.

There's no formal manual, but there are some docs generating by reflecting on the API.
The first place to look should be: http://fundamental-code.com/zyn-ports/
I just updated that to display all the ports in the current git HEAD which have proper metadata associated with them.
If you want something more interactive than that, there is https://github.com/fundamental/oscprompt

If you can't find the specific OSC address/argument combo that you're looking for, just ask as the documentation/reflection information is incomplete (though it does cover 98% of the API).

Per the part volumes you're going to want to look at the /part*/Pvolume addresses.

[dsreyes1014]

Is there a manual or doc with recent osc commands for zynaddsubfx? I'm interested in created a basic layout on Android to control part volume levels.

There's no formal manual, but there are some docs generating by reflecting on the API.
The first place to look should be: http://fundamental-code.com/zyn-ports/
I just updated that to display all the ports in the current git HEAD which have proper metadata associated with them.
If you want something more interactive than that, there is https://github.com/fundamental/oscprompt

If you can't find the specific OSC address/argument combo that you're looking for, just ask as the documentation/reflection information is incomplete (though it does cover 98% of the API).

Per the part volumes you're going to want to look at the /part*/Pvolume addresses.

Thanks fundamental. Am I correct in assuming to get Android OSC app to communicate to Zyn I need Pd?

[fundamental]

Am I correct in assuming to get Android OSC app to communicate to Zyn I need Pd?

You should not need Pd. As long as you have some application on android which can send OSC messages via UDP Zyn should be able to receive them.

[dsreyes1014]

Am I correct in assuming to get Android OSC app to communicate to Zyn I need Pd?

You should not need Pd. As long as you have some application on android which can send OSC messages via UDP Zyn should be able to receive them.

So if I set the port via zynaddsubfx -P 1234, I just set port to 1234 on Android app?

[dsreyes1014]

For OSC assignment, I'm assigning /part0/Pvolume to first part volume of zynaddsubfx but nothing is happening on Zynaddsubfx and I'm getting

Code: Select all

Unknown address<BACKEND> '/part0/Pvolume:f'
Unknown address<BACKEND> '/part0/Pvolume:f'
Unknown address<BACKEND> '/part0/Pvolume:f'
Unknown address<BACKEND> '/part0/Pvolume:f'
Unknown address<BACKEND> '/part0/Pvolume:f'
Unknown address<BACKEND> '/part0/Pvolume:f'
Unknown address<BACKEND> '/part0/Pvolume:f'
Unknown address<BACKEND> '/part0/Pvolume:f'
Unknown address<BACKEND> '/part0/Pvolume:f'
Unknown address<BACKEND> '/part0/Pvolume:f'
Unknown address<BACKEND> '/part0/Pvolume:f'
Unknown address<BACKEND> '/part0/Pvolume:f'
Unknown address<BACKEND> '/part0/Pvolume:f'
Unknown address<BACKEND> '/part0/Pvolume:f'
Unknown address<BACKEND> '/part0/Pvolume:f'
Unknown address<BACKEND> '/part0/Pvolume:f'
Unknown address<BACKEND> '/part0/Pvolume:f'
Unknown address<BACKEND> '/part0/Pvolume:f'
Unknown address<BACKEND> '/part0/Pvolume:f'
Unknown address<BACKEND> '/part0/Pvolume:f'
Unknown address<BACKEND> '/part0/Pvolume:f'
Unknown address<BACKEND> '/part0/Pvolume:f'
Unknown address<BACKEND> '/part0/Pvolume:f'

[fundamental]

That's the right OSC path, but the wrong argument type. The majority of OSC paths in zyn accept integers (type 'i') 0..127 and not floating point values (type 'f').

[dsreyes1014]

That's the right OSC path, but the wrong argument type. The majority of OSC paths in zyn accept integers (type 'i') 0..127 and not floating point values (type 'f').

Ok understand better now. These Android apps don't seem to allow me to use integers at all.