Command line sound apps trouble

[yuryfdr]

Hi. I try use timidity++ for midi in pocketbook pro 603.
no problem to build, but...

I see a strange behavior when i only touch screen with stilus misic is played. It seams that PB go to sleep with no events.
Does anyone know solution?

I use wrapper timidity.app and freepats
---timidity.app------
#!/bin/sh
/mnt/ext1/system/bin/timidity $1 >/dev/null 2>&1 &
-----------------------

[rkomar]

I have no idea if this will work on the PB device, but android devices can use a wake_lock to keep from going into suspend mode. Try bracketing your call to timidity with:

echo test > /sys/power/wake_lock
timidity ...
echo test > /sys/power/wake_unlock

and see if that keeps the system from suspending.

[yuryfdr]

Originally Posted by rkomar

....
echo test > /sys/power/wake_lock
timidity ...
echo test > /sys/power/wake_unlock

and see if that keeps the system from suspending.

it helps me, in this case I lost probability to run timidity in background, but i can patch timidity.

P.S. it's pity but I have another trouble midi files with guitar bands (and some other effects) are played with unacceptable quality :-(.
(tracks with Bass,Drums and PhythmGuitar seems plays ok)
is this gcc options enough for PB 603?
gcc -O2 -march=armv6j
or maybe reason is low speed filesystem?

[rkomar]

Originally Posted by yuryfdr

it helps me, in this case I lost probability to run timidity in background, but i can patch timidity.

P.S. it's pity but I have another trouble midi files with guitar bands (and some other effects) are played with unacceptable quality :-(.
(tracks with Bass,Drums and PhythmGuitar seems plays ok)
is this gcc options enough for PB 603?
gcc -O2 -march=armv6j
or maybe reason is low speed filesystem?

MIDI files are tiny compared to mp3 files, so I doubt that it is the filesystem slowing down timidity. But if it is, maybe the '-B' option of timidity can help you. What is the problem that makes it unacceptable? There are many timidity options that you can play with. Try setting the output to ALSA (-Os). You can reduce CPU usage by setting a low sampling frequency ( say "-s 11025") and even mono output (--output-mono) to see if it is really the CPU that is limiting things. It would be good to know what is really causing the problem before trying to find the solution.

[yuryfdr]

Originally Posted by rkomar

You can reduce CPU usage by setting a low sampling frequency ( say "-s 11025") and even mono output (--output-mono)

Thanks it helps me - to use low sampling frequency.

[rkomar]

Originally Posted by yuryfdr

Thanks it helps me - to use low sampling frequency.

I see. That does look like CPU usage is a big factor. I'm not sure, but I think the floating-point arithmetic is emulated on these devices. The timidity INSTALL file describes some of the compile-time settings that can be configured in timidity.h for reduced CPU usage. Things like FLOAT_T, LOOKUP_HACK, LOOKUP_INTERPOLATION and LOOKUP_SINE can be defined to reduce some of the floating-point calculations. Also, you can disable many CPU-intensive effects on the command-line, and that may sound better than just reducing the sampling frequency.