Re: unable to play wav audio
Hi, This issue got fixed by using autoaudiosink instead of alsasink element in gstreamer pipeline. Now i can hear the sound but can someone tell me why is this behavior? why sound is not audible with alsasink? Thanks in advance. Regards, sanjay On Fri, Mar 28, 2008 at 9:05 PM, Sanjay Gupta [EMAIL PROTECTED] wrote: Hi, I am unable to hear wav audio in Hildon UI framework using the example file example_wavlaunch.c in maemo example pack. I compiled this example in scratchbox with target CHINOOK_X86 maemo sdk version is 4.0.1. I did the following to run it. 1. $Xephyr :2 -host-cursor -screen 800x480x16 -dpi 96 -ac -extension Composite empty Xephyr window will appear 2. [sbox-CHINOOK_X86] export DISPLAY=:2 3. [sbox-CHINOOK_X86] run-standalone.sh ./a.out It will display the example_wavlaunch.c ui on the top of empty Xephyr window and when file is choosen for playback, then it works I can hear the sound. Now When I start maemo GUI using the following command: [sbox-CHINOOK_X86] af-sb-init.sh start and then run the executable as given in step 3. then it does not work I can't hear audio. sometime it crashes too. Please suggest if something need to do to make it work. Thanks in advance. regards, sanjay ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Best format for SD ?
On Wed, Apr 2, 2008 at 8:45 AM, Igor Stoppa [EMAIL PROTECTED] wrote: On Tue, 2008-04-01 at 20:27 +0300, ext Marius Vollmer wrote: ext Klaus Rotter [EMAIL PROTECTED] writes: Charles Werbick wrote: [...] ARM simply cannot compete with a Pentium III CPU at 1.5 GHz and 12 watts total dissipation. I predict that the n900 series, should it reach production, will run Intel and not TI silicon. The N8xxs have a 1,5Ah x 3,7V = 5,5 Wh accu. A 12 W design will run out of power in less than half an hour. Charles is missing a dot: The chips have a thermal design power (TDP) specification in 0.6-2.5 watt range and scale to 1.8GHz [...] http://www.intel.com/pressroom/archive/releases/20080302comp.htm Anyway that's still insanely high: 0.6-2.5 watt is for a pocket stove, not an handheld device. According to Wikipedia it can idle in the 0.01 W to 0.1 W range. But this is still just for the processor core, chipset peripherals not included... Are there similar estimations for power consumption of OMAP35x processors produced in 45nm? cheers Philipp ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Best format for SD ?
On Wed, 2008-04-02 at 18:47 +0200, ext pHilipp Zabel wrote: On Wed, Apr 2, 2008 at 8:45 AM, Igor Stoppa [EMAIL PROTECTED] wrote: On Tue, 2008-04-01 at 20:27 +0300, ext Marius Vollmer wrote: ext Klaus Rotter [EMAIL PROTECTED] writes: Charles Werbick wrote: [...] ARM simply cannot compete with a Pentium III CPU at 1.5 GHz and 12 watts total dissipation. I predict that the n900 series, should it reach production, will run Intel and not TI silicon. The N8xxs have a 1,5Ah x 3,7V = 5,5 Wh accu. A 12 W design will run out of power in less than half an hour. Charles is missing a dot: The chips have a thermal design power (TDP) specification in 0.6-2.5 watt range and scale to 1.8GHz [...] http://www.intel.com/pressroom/archive/releases/20080302comp.htm Anyway that's still insanely high: 0.6-2.5 watt is for a pocket stove, not an handheld device. According to Wikipedia it can idle in the 0.01 W to 0.1 W range. But this is still just for the processor core, chipset peripherals not included... Are there similar estimations for power consumption of OMAP35x processors produced in 45nm? Sure, but i don't know how many are those that are also public. You should check the TI website. -- Cheers, Igor --- Igor Stoppa Next Generation Software Nokia Devices RD - Helsinki ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
packet storing sequence on the device..
Hi, I am interested to know the sequence in which the network packet data is stored on the device once it arrives on NIC in the device(n810). considering youtube example ,since L2 is faster, is it that packets are directly stored in L2 and video RAM , then back to L1 and then to the main memory ( for playback again) or is it that they get stored on main memory, then transferred to L1, and then to L2, video RAM for playing. I was doubting that TCP/IP suite on the device would handle this situation in a different way because of the limited memory space. Comments about the sequence of packet data movement within the memory system would be helpful for me.. Thanks for any clarification in this regard... ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Help with hildon.NumberEditor: IN PYTHON
Help please!
I am slowly learning OOP-style PyGTK code, and have recently discovered
how 'nasty' gtk.Spinbutton looks on Maemo :(
OK, so I was just going to make some quick changed to my Python code to
use 'hildon.NumberEditor' instead, but it is not as much a
'drop-in-replacement' as a newbie like me requires...
subclass the gtk.Digalog() class to create a new dialog window
class spin_window(gtk.Dialog) :
value = [0] * SPIN_BUTTON_COUNT
def hildon_set_value(self,widget,index):
self.value[index] = widget.get_value()
return
# a callback to remember the values of the spin buttons.
# the 'index' is setup when connecting the callback
def set_value(self,widget,index):
self.value[index] = widget.get_value_as_int()
return
def __init__(self,window):
# init the parent class to create the dialog
super(spin_window, self).__init__(set spin values, window,
gtk.DIALOG_DESTROY_WITH_PARENT |
gtk.DIALOG_MODAL,
(gtk.STOCK_OK, gtk.RESPONSE_OK))
number_editor = hildon.NumberEditor(-90,90)
#number_editor.connect(changed,self.set_value, 0)
#number_editor.connect(notify::value,self.set_value, 0)
number_editor.connect(notify::value,self.hildon_set_value,0)
number_editor.set_value(0)
self.vbox.pack_start(number_editor)
self.value[0] = 0
number_editor.show()
label = gtk.Label('Latitude Degrees:')
self.vbox.pack_start(label)
#label.modify_font(pango.FontDescription(sans 30))
label.show()
adjustment = gtk.Adjustment(0, -90, 90, 1, 1, 1)
spinbutton = gtk.SpinButton(adjustment,0,0)
spinbutton.connect(changed,self.set_value, 1)
self.vbox.pack_start(spinbutton)
self.value[1] = 0
spinbutton.show()
...
Notice my feeble attempts to add 'special' code for the numbereditor --
but the code above does not work:
TypeError: hildon_set_value() takes exactly 3 arguments (4 given)
So I am getting all confused! It *looks* like I am using the correct
signal value, and passing three parameters...
There are very few Python examples out on Google for me to learn the
solution with.
Thanks
Dare
___
maemo-developers mailing list
maemo-developers@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-developers
Training for Maemo Development
Does anybody know of any good training courses or seminars that are available in the United States for learning how to develop applications on the Maemo OS or geared toward developing for the Nokia Internet tablets? I guess any training on Hildon UI, GTK, or Debian Linux development might be helpful as well. We have started a project at work that is developing software for the Nokia N800/N810 and I need some good training/courses that will get me going in the right direction. Please let me know if anybody knows of anything. Thanks. MFonnesbeck ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Help with hildon.NumberEditor: IN PYTHON
On Wed, Apr 2, 2008 at 4:28 PM, Darren Enns [EMAIL PROTECTED] wrote:
Help please!
I am slowly learning OOP-style PyGTK code, and have recently discovered how
'nasty' gtk.Spinbutton looks on Maemo :(
OK, so I was just going to make some quick changed to my Python code to use
'hildon.NumberEditor' instead, but it is not as much a 'drop-in-replacement'
as a newbie like me requires...
subclass the gtk.Digalog() class to create a new dialog window
class spin_window(gtk.Dialog) :
value = [0] * SPIN_BUTTON_COUNT
def hildon_set_value(self,widget,index):
self.value[index] = widget.get_value()
return
# a callback to remember the values of the spin buttons.
# the 'index' is setup when connecting the callback
def set_value(self,widget,index):
self.value[index] = widget.get_value_as_int()
return
def __init__(self,window):
# init the parent class to create the dialog
super(spin_window, self).__init__(set spin values,
window,
gtk.DIALOG_DESTROY_WITH_PARENT |
gtk.DIALOG_MODAL,
(gtk.STOCK_OK, gtk.RESPONSE_OK))
number_editor = hildon.NumberEditor(-90,90)
#number_editor.connect(changed,self.set_value, 0)
#number_editor.connect(notify::value,self.set_value, 0)
number_editor.connect(notify::value,self.hildon_set_value,0)
number_editor.set_value(0)
self.vbox.pack_start(number_editor)
self.value[0] = 0
number_editor.show()
label = gtk.Label('Latitude Degrees:')
self.vbox.pack_start(label)
#label.modify_font(pango.FontDescription(sans 30))
label.show()
adjustment = gtk.Adjustment(0, -90, 90, 1, 1, 1)
spinbutton = gtk.SpinButton(adjustment,0,0)
spinbutton.connect(changed,self.set_value, 1)
self.vbox.pack_start(spinbutton)
self.value[1] = 0
spinbutton.show()
...
Notice my feeble attempts to add 'special' code for the numbereditor -- but
the code above does not work:
TypeError: hildon_set_value() takes exactly 3 arguments (4 given)
So I am getting all confused! It *looks* like I am using the correct
signal value, and passing three parameters...
There are very few Python examples out on Google for me to learn the
solution with.
Try replacing the argument list on the callback to
def set_value(self, widget, index, data=None)
Now data will take the extra data passed when the signal is received.
--
Lauro Moura
INdT - Instituto Nokia de Tecnologia
___
maemo-developers mailing list
maemo-developers@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Help with hildon.NumberEditor: IN PYTHON
Lauro Moura wrote:
On Wed, Apr 2, 2008 at 4:28 PM, Darren Enns [EMAIL PROTECTED] wrote:
Help please!
I am slowly learning OOP-style PyGTK code, and have recently discovered how
'nasty' gtk.Spinbutton looks on Maemo :(
OK, so I was just going to make some quick changed to my Python code to use
'hildon.NumberEditor' instead, but it is not as much a 'drop-in-replacement'
as a newbie like me requires...
subclass the gtk.Digalog() class to create a new dialog window
class spin_window(gtk.Dialog) :
value = [0] * SPIN_BUTTON_COUNT
def hildon_set_value(self,widget,index):
self.value[index] = widget.get_value()
return
# a callback to remember the values of the spin buttons.
# the 'index' is setup when connecting the callback
def set_value(self,widget,index):
self.value[index] = widget.get_value_as_int()
return
def __init__(self,window):
# init the parent class to create the dialog
super(spin_window, self).__init__(set spin values,
window,
gtk.DIALOG_DESTROY_WITH_PARENT |
gtk.DIALOG_MODAL,
(gtk.STOCK_OK, gtk.RESPONSE_OK))
number_editor = hildon.NumberEditor(-90,90)
#number_editor.connect(changed,self.set_value, 0)
#number_editor.connect(notify::value,self.set_value, 0)
number_editor.connect(notify::value,self.hildon_set_value,0)
number_editor.set_value(0)
self.vbox.pack_start(number_editor)
self.value[0] = 0
number_editor.show()
label = gtk.Label('Latitude Degrees:')
self.vbox.pack_start(label)
#label.modify_font(pango.FontDescription(sans 30))
label.show()
adjustment = gtk.Adjustment(0, -90, 90, 1, 1, 1)
spinbutton = gtk.SpinButton(adjustment,0,0)
spinbutton.connect(changed,self.set_value, 1)
self.vbox.pack_start(spinbutton)
self.value[1] = 0
spinbutton.show()
...
Notice my feeble attempts to add 'special' code for the numbereditor -- but
the code above does not work:
TypeError: hildon_set_value() takes exactly 3 arguments (4 given)
So I am getting all confused! It *looks* like I am using the correct
signal value, and passing three parameters...
There are very few Python examples out on Google for me to learn the
solution with.
Try replacing the argument list on the callback to
def set_value(self, widget, index, data=None)
Now data will take the extra data passed when the signal is received.
Thanks for the suggestion! It got me a bit further, but my parameter offsets
must be wrong. This is what my 'hildon' callback looks like now:
def hildon_set_value(self, widget, index, data=None):
When I use it that way, I get complaints that 'index' is not an integer
(which of course it is):
Traceback (most recent call last):
File mephemeris.22.py, line 2480, in hildon_set_value
self.value[index] = widget.get_value()
TypeError: list indices must be integers
This suggests to me that I have the correct number of parameters, but
not in the position I am expecting them in.
Dare
___
maemo-developers mailing list
maemo-developers@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-developers
