10 Jan
2011
10 Jan
'11
3:54 p.m.
Hello I'm a user of freewheeling and I would like to ask someone with
programming skills:
freewheeling is unmaintained and it would be great to have someone
taking care of bugfixing and jackd compatibility at least. Would
anyone like to do it?
I have at least one nasty bug that doesn't allows me to use
freewheeling with my oxygen 49:
log at console:
for each time I press a key:
fluidsynth: warning: Ringbuffer full, try increasing polyphony!
fluidsynth: warning: Ringbuffer full, try increasing polyphony!
MEM: RTNew (block)- No instances available.
CONFIG: WARNING: Can't send event- RTNew() failed
Falha de segmentação
at jackd:
Mon Jan 10 15:38:36 2011: Connecting 'FreeWheeling:out_1L' to
'system:playback_1'
Mon Jan 10 15:38:36 2011: Connecting 'FreeWheeling:out_1R' to
'system:playback_2'
15:38:44.167 XRUN callback (1).
15:38:44.375 ALSA connection graph change.
15:38:44.382 JACK connection graph change.
15:38:44.428 JACK connection change.
15:38:44.429 ALSA connection change.
Mon Jan 10 15:38:44 2011: [1m [31mERROR: JackEngine::XRun: client =
FreeWheeling was not run: state = 2 [0m
Mon Jan 10 15:38:44 2011: [1m [31mERROR:
JackAudioDriver::ProcessGraphAsync: Process error [0m
Mon Jan 10 15:38:44 2011: [1m [31mERROR: JackPosixMutex::Unlock res = 1 [0m
Mon Jan 10 15:38:44 2011: [1m [31mERROR: JackPosixMutex::Unlock res = 1 [0m
Mon Jan 10 15:38:44 2011: [1m [31mERROR: JackEngine::XRun: client =
FreeWheeling was not run: state = 1 [0m
Mon Jan 10 15:38:44 2011: [1m [31mERROR:
JackAudioDriver::ProcessGraphAsync: Process error [0m
Mon Jan 10 15:38:44 2011: [1m [31mERROR: JackPosixMutex::Unlock res = 1 [0m
Mon Jan 10 15:38:44 2011: [1m [31mERROR: JackPosixMutex::Unlock res = 1 [0m
Mon Jan 10 15:38:44 2011: [1m [31mERROR: JackEngine::XRun: client =
FreeWheeling was not run: state = 1 [0m
Mon Jan 10 15:38:44 2011: [1m [31mERROR:
JackAudioDriver::ProcessGraphAsync: Process error [0m
Mon Jan 10 15:38:44 2011: [1m [31mERROR: JackPosixMutex::Unlock res = 1 [0m
Mon Jan 10 15:38:44 2011: [1m [31mERROR: JackPosixMutex::Unlock res = 1 [0m
Mon Jan 10 15:38:44 2011: [1m [31mERROR: JackEngine::XRun: client =
FreeWheeling was not run: state = 1 [0m
Mon Jan 10 15:38:44 2011: [1m [31mERROR:
JackAudioDriver::ProcessGraphAsync: Process error [0m
Mon Jan 10 15:38:44 2011: [1m [31mERROR: JackPosixMutex::Unlock res = 1 [0m
Mon Jan 10 15:38:44 2011: [1m [31mERROR: JackPosixMutex::Unlock res = 1 [0m
Mon Jan 10 15:38:44 2011: [1m [31mERROR: JackEngine::XRun: client =
FreeWheeling was not run: state = 1 [0m
Mon Jan 10 15:38:44 2011: [1m [31mERROR:
JackAudioDriver::ProcessGraphAsync: Process error [0m
Mon Jan 10 15:38:44 2011: [1m [31mERROR: JackPosixMutex::Unlock res = 1 [0m
Mon Jan 10 15:38:44 2011: [1m [31mERROR: JackPosixMutex::Unlock res = 1 [0m
Mon Jan 10 15:38:44 2011: [1m [31mERROR: JackPosixMutex::Unlock res = 1 [0m
Mon Jan 10 15:38:44 2011: [1m [31mERROR: JackPosixMutex::Unlock res = 1 [0m
Mon Jan 10 15:38:44 2011: [1m [31mERROR: JackEngine::XRun: client =
FreeWheeling was not run: state = 1 [0m
Mon Jan 10 15:38:44 2011: Disconnecting 'FreeWheeling:out_1L' from
'system:playback_1'
Mon Jan 10 15:38:44 2011: Disconnecting 'FreeWheeling:out_1R' from
'system:playback_2'
Mon Jan 10 15:38:44 2011: [1m [31mERROR: Failed to find port
'FreeWheeling:in_1' to destroy [0m
Mon Jan 10 15:38:44 2011: [1m [31mERROR: Failed to find port
'FreeWheeling:in_2' to destroy [0m
Mon Jan 10 15:38:44 2011: [1m [31mERROR: Failed to find port
'FreeWheeling:in_3L' to destroy [0m
Mon Jan 10 15:38:44 2011: [1m [31mERROR: Failed to find port
'FreeWheeling:in_3R' to destroy [0m
Mon Jan 10 15:38:44 2011: [1m [31mERROR: Failed to find port
'FreeWheeling:out_1L' to destroy [0m
Mon Jan 10 15:38:44 2011: [1m [31mERROR: Failed to find port
'FreeWheeling:out_1R' to destroy [0m
Mon Jan 10 15:38:44 2011: Client 'FreeWheeling' with PID 3514 is out
15:38:45.467 XRUN callback (5 skipped).
Could I change config file so that:
FreeWheeling library
Could it be fw-lib-date like fw-lib-201001261324? So that my loops
don't get all mix up?
Ardour
Could I record a freewheeling session directly to ardour were track is
letter were loop is:
track "a"
track "dancepad_up"
and so on...
Help Key
How do I change the help Key to the numeric keyboard pad slash? (My
keyboard is a portuguese macintosh layout...)
I think it should be at coreinterface.xml but I don't know the right
name for each key. Looking at the xml I think I better buy a us
keyboard ... I could even do freewheeling stickers
that all for now. Cheers and thanks on advance!
____________________________________________
Jorge Salgueiro
GNU/Linux: Free culture for a free society!
10 Jan
10 Jan
4:08 p.m.
On Mon, Jan 10, 2011 at 10:53 AM, Jorge Salgueiro
<jorge.salgueiro(a)gmail.com> wrote:
Hello I'm a user of freewheeling and I would like
to ask someone with
programming skills:
freewheeling is unmaintained and it would be great to have someone
taking care of bugfixing and jackd compatibility at least. Would
anyone like to do it?
just FYI, nothing in the JACK API has changed since freewheeling was
written that requires any changes to its JACK support.
4:33 p.m.
2011/1/10 Paul Davis <paul(a)linuxaudiosystems.com>om>:
On Mon, Jan 10, 2011 at 10:53 AM, Jorge Salgueiro
<jorge.salgueiro(a)gmail.com> wrote:
Yes the thruth is that my post was a little confusing:
1. freewheeling needs love. Brave coder take a step to front :D
2. I have some problems that I don't if they are from freewheeling or
from my kxstudio system. Yes I'm not a coder and I barely can
understand what happens and why it happens. If you guys what to help
me and need more info on the problems that I have just ask me.
Thanks for everybody's work!
Hello I'm a user of freewheeling and I would
like to ask someone with
programming skills:
freewheeling is unmaintained and it would be great to have someone
taking care of bugfixing and jackd compatibility at least. Would
anyone like to do it?
just FYI, nothing in the JACK API has changed since freewheeling was
written that requires any changes to its JACK support.
4:44 p.m.
On Mon, 10 Jan 2011, Jorge Salgueiro wrote:
2. I have some problems that I don't if they are
from freewheeling or
from my kxstudio system. Yes I'm not a coder and I barely can
understand what happens and why it happens. If you guys what to help
me and need more info on the problems that I have just ask me.
FW has a really cool interactive GUI. However, that GUI is
crash-prone. This is probably the problem you are having.
I have never been able to make FW work reliably on any
system I've owned.
JP Mercury pretty much wrote the GUI like a video game... so
it's not using any sort of widget kits or anything. This
means that whoever picks up the project has to either
learn a new API to maintain it, or dump it and start
fresh with some other implementation. Not fun either
way.
-gabriel
13 Jan
13 Jan
1:12 p.m.
On 01/10/2011 05:44 PM, Gabriel M. Beddingfield wrote:
On Mon, 10 Jan 2011, Jorge Salgueiro wrote:
This is a
pity indeed. But most crash-prone apps are close to useless
especially for live imho.
The same is true for the NON apps probably. Nice concept but not stable
enough atm.
Let's hope Composite will improve the state of such 'instrument' apps.
The concept looks promising...
Having great ideas and concepts is 1, but having a stable and finished
project is 2. The linuxaudio world doesn't lack great ideas, but the
problem is having stable and finished projects most of the time. Pretty
some projects fails at point 2. Freewheeling is an example of this.
\r
2. I have some problems that I don't if they
are from freewheeling or
from my kxstudio system. Yes I'm not a coder and I barely can
understand what happens and why it happens. If you guys what to help
me and need more info on the problems that I have just ask me.
FW has a really cool interactive GUI. However, that GUI is
crash-prone. This is probably the problem you are having. I have
never been able to make FW work reliably on any system I've owned. 
15 Jan
15 Jan
9:07 p.m.
Le 10/01/2011 17:33, Jorge Salgueiro a écrit :
1. freewheeling needs love. Brave coder take a step to
front :D
I love it :)
I had great moment playing with it.
After JP Mercury has left fweelin developpement I had to admit that I
needed to find another live looping app.
I tried sooperlooper, it's great! not as fun as fweelin but rock solid
and efficient.
2. I have some problems that I don't if they are
from freewheeling or
from my kxstudio system. Yes I'm not a coder and I barely can
understand what happens and why it happens. If you guys what to help
me and need more info on the problems that I have just ask me.
If you want to
continue to use freewheeling you have to Do It Yourself,
I wasn't able to use default key
bindings with non US keyboard you have to understand and modify
~/.fheelin/*.xml (look at config-help.txt for the key codes and also a
console output to see actual key code when you press a key)
It is very time consuming, but if you are a DIYer you'll have great
moment, because you
can do many things with the XML configuration.
But IMHO you should not (unless a new dev take the lead) loose to much
time on a unmaintained application, one day it will not work and linux
distro maintainers will stop packaging it :(
Yes it's sad... especially because fweelin is (one of?) the best audio
app I ever used...
nomoa.
4856
days inactive
4861
days old
linux-audio-user@lists.linuxaudio.org
5 comments
5 participants
participants (5)
-
Gabriel M. Beddingfield -
Jorge Salgueiro -
nomoa -
Paul Davis -
rosea.grammostola