Puppy Linux Discussion Forum Forum Index Puppy Linux Discussion Forum
Puppy HOME page : puppylinux.com
"THE" alternative forum : puppylinux.info
 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

The time now is Fri 24 May 2019, 07:13
All times are UTC - 4
 Forum index » Advanced Topics » Puppy Projects
DebianDog64 - 64 bit DebianDog-Jessie
Moderators: Flash, JohnMurga
Post new topic   Reply to topic View previous topic :: View next topic
Page 10 of 38 [560 Posts]   Goto page: Previous 1, 2, 3, ..., 8, 9, 10, 11, 12, ..., 36, 37, 38 Next
Author Message
fredx181


Joined: 11 Dec 2013
Posts: 3919
Location: holland

PostPosted: Thu 04 Feb 2016, 15:40    Post subject:  

Save as UTF-8 maybe?
Back to top
View user's profile Send private message 
stemsee

Joined: 27 Jun 2013
Posts: 2342
Location: In The Way

PostPosted: Fri 05 Feb 2016, 03:47    Post subject:  

Hi Fredx181

I want to be able to play DogRadio over bluetooth speaker. This is the command I use to play a media playlist file. It is the same for a single media file just remove -playlist section and supply path to *.mp3 etc
Code:
mplayer -ao alsa:device=btheadset -playlist /tmp/list-"$filext".m3u &


How can I apply this to DogRadio?
Back to top
View user's profile Send private message MSN Messenger 
fredx181


Joined: 11 Dec 2013
Posts: 3919
Location: holland

PostPosted: Fri 05 Feb 2016, 08:06    Post subject:  

stemsee wrote:
Hi Fredx181

I want to be able to play DogRadio over bluetooth speaker. This is the command I use to play a media playlist file. It is the same for a single media file just remove -playlist section and supply path to *.mp3 etc
Code:
mplayer -ao alsa:device=btheadset -playlist /tmp/list-"$filext".m3u &


How can I apply this to DogRadio?


Hi Stemsee,

Adding this on top of $HOME/.dogradio/data/func should work (doesn't work adding to /usr/local/bin/dogradio):

Code:
#!/bin/bash

shopt -s expand_aliases
alias mplayer='mplayer -ao alsa:device=btheadset "$@"'

......
......


Another way possibly to make new script named mplayer and put it in first PATH env
For me /root/bin
Code:
#!/bin/bash

## USE FULL PATH OF EXISTING MPLAYER BINARY
/opt/bin/mplayer -ao alsa:device=btheadset "$@";

My PATH is:
Code:
root@jessie:~# echo $PATH
/root/bin:/opt/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games:/usr/local/sbin:/usr/sbin:/sbin

So /root/bin is first in PATH

Fred
Back to top
View user's profile Send private message 
rcrsn51


Joined: 05 Sep 2006
Posts: 12627
Location: Stratford, Ontario

PostPosted: Fri 05 Feb 2016, 09:39    Post subject:  

@stemsee: Assuming that DogRadio plays to the default ALSA device, try this /root/.asoundrc:

Code:
pcm.builtin {type hw; card 0;}
ctl.builtin {type hw; card 0;}

pcm.btheadset {
   type plug
   slave {
       pcm {
           type bluetooth
           device XX:XX:XX:XX:XX:XX
           profile "auto"
       }
   }
   hint {
       show on
       description "BT Headset"
   }
}
ctl.btheadset {
  type bluetooth
}

#pcm.!default pcm.builtin
#ctl.!default ctl.builtin

pcm.!default pcm.btheadset
ctl.!default ctl.btheadset


You can switch between your bluetooth audio device and the built-in speakers by changing the commented lines at the bottom.
Back to top
View user's profile Send private message 
stemsee

Joined: 27 Jun 2013
Posts: 2342
Location: In The Way

PostPosted: Fri 05 Feb 2016, 10:36    Post subject:  

Thanks @fredx181 @ rcrsn51

I will test them both, a specific solutioin and a global solution.

stemsee

post script
One request for DogRadio gui if possible. After clicking the stop button it would be great if it changed colour ( the stop button) and behaved as a pause so that pressing it again resumed the same station; and then changed to red after starting a station or resuming.
Back to top
View user's profile Send private message MSN Messenger 
fredx181


Joined: 11 Dec 2013
Posts: 3919
Location: holland

PostPosted: Sun 07 Feb 2016, 14:58    Post subject:  

Hi All,

Fix for loading encrypted save file, added to the Changes and fixes list

9) Fix for loading encrypted save file when using porteus-boot (using live-boot-3 works well)
Problem is with USB keyboard. Not possible to type the password as the module hid_generic is not loaded at this point (keyboard not enabled)
Fixed with new initrd1.xz, download:
https://dl.dropboxusercontent.com/u/36279550/DebDog64-Jessie/Temp/initrd1.xz
Replace it in the "live" folder

Fred

Last edited by fredx181 on Sun 07 Feb 2016, 15:29; edited 2 times in total
Back to top
View user's profile Send private message 
fredx181


Joined: 11 Dec 2013
Posts: 3919
Location: holland

PostPosted: Sun 07 Feb 2016, 15:12    Post subject:  

Hi All,

I decided to remove the link to DebianDog64 - Stretch version on the first post.
Mainly because:
- There are some problems found with it that I can't solve.
- I don't have enough time to maintain it (e.g. fixes, new packages)

So I'll focus on DebDog64 Jessie only now.

Fred
Back to top
View user's profile Send private message 
fredx181


Joined: 11 Dec 2013
Posts: 3919
Location: holland

PostPosted: Sun 07 Feb 2016, 16:56    Post subject:  

*** LZ4 compression boot support ***

In the 32 bit Debiandog Jessie thread, rufwoof explained some advantages using LZ4 compressed modules.
See more about LZ4 here:
http://cyan4973.github.io/lz4/

Full support for it will be included in next DD64 ISO

For now, to have full LZ4 support for DebianDog64-Jessie, download and extract in the "live" folder this archive:

https://dl.dropboxusercontent.com/u/36381953/DebDog64-Jessie/Extra-Modules/3.16-64-kernel-squashfs-lz4-support.tar.gz?dl=1

Or Download with SFS-get from the Menu (Accessories > SFS-get)

From the ReadMe inside:
Quote:
Supports mounting, creating, extracting and activating (sfs-load) LZ4 compressed .squashfs modules.

Place these files in the "live" folder:
initrd1-lz4.xz
initrd1-lz4.img
initrd-lz4.img
316-squashfs-lz4-support64.squashfs
and
vmlinuz1-lz4 (added here for completeness, in fact it's the same as vmlinuz1 from DebianDog pae ISO, kernel 3.16.0-4-686-pae)


Make new entry in menu.list according to the path/names of the files, e.g:

# Porteus-boot:

title DebianDog 64 with LZ4-squashfs-support - porteus-boot sysvinit
root (hd0,2)
kernel /live/vmlinuz1-lz4 from=/ noauto changes=EXIT:/live/
initrd /live/initrd1-lz4.xz

# Live-boot-3:

title DebianDog 64 with LZ4-squashfs-support - live3 persistence sysvinit
root (hd0,2)
kernel /live/vmlinuz1-lz4 boot=live persistence config swapon quickreboot noprompt autologin
initrd /live/initrd-lz4.img

Reboot

See for more info in the ReadMe.

Fred
Back to top
View user's profile Send private message 
rcrsn51


Joined: 05 Sep 2006
Posts: 12627
Location: Stratford, Ontario

PostPosted: Tue 09 Feb 2016, 10:27    Post subject:  

stemsee wrote:
I will test them both, a specific solutioin and a global solution.

Whatever happened with this issue?
Back to top
View user's profile Send private message 
stemsee

Joined: 27 Jun 2013
Posts: 2342
Location: In The Way

PostPosted: Mon 15 Feb 2016, 11:46    Post subject:  

well I don't want to distract from the thread but I didn't implement either cleanly because before I did I implemented this loop to ~.asoundrc

Code:
# ------------------------------------------------------
# hardware 0,0 : used for ALSA playback
pcm.loophw00 {
  type hw
  card Loopback
  device 0
  subdevice 0
  format S32_LE
  rate 48000
}

# ------------------------------------------------------
# playback PCM device: using loopback subdevice 0,0
# Don't use a buffer size that is too small. Some apps
# won't like it and it will sound crappy

pcm.amix {
  type dmix
  ipc_key 219345
  slave {
    pcm loophw00
    period_size 2048
    periods 2
  }
}

# ------------------------------------------------------
# software volume
pcm.asoftvol {
  type softvol
  slave.pcm "amix"

  control { name PCM }

  min_dB -51.0
  max_dB   0.0
}

# ------------------------------------------------------
# for jack alsa_in: looped-back signal at other ends
pcm.cloop {
  type hw
  card Loopback
  device 1
  subdevice 0
  format S32_LE
  rate 48000
}

# ======================================================
# ------------------------------------------------------
# hardware 0,1 : used for ALSA capture
pcm.loophw01 {
  type hw
  card Loopback
  device 0
  subdevice 1
  format S32_LE
  rate 48000
}

# ------------------------------------------------------
# for jack alsa_out: looped-back signal at other end
pcm.ploop {
  type hw
  card Loopback
  device 1
  subdevice 1
  format S32_LE
  rate 48000
}

# ======================================================
# ------------------------------------------------------
# duplex device combining our PCM devices defined above
pcm.aduplex {
  type asym
  playback.pcm "asoftvol"
  capture.pcm "loophw01"
}

# ------------------------------------------------------
# default device
pcm.!default {
  type plug
  slave.pcm aduplex

  hint {
       show on
       description "Duplex Loopback"
  }
}
Back to top
View user's profile Send private message MSN Messenger 
oui

Joined: 20 May 2005
Posts: 3379
Location: near Woof (Germany) :-) - 3 PC's: DELL SX280 750 MB Pentium4, Acer emachines 2 GB AMD64. DELL XPS15

PostPosted: Tue 16 Feb 2016, 19:58    Post subject:  

Hi
How to install skype?
Kind regards
Back to top
View user's profile Send private message 
fredx181


Joined: 11 Dec 2013
Posts: 3919
Location: holland

PostPosted: Wed 17 Feb 2016, 14:24    Post subject:  

oui wrote:
Hi
How to install skype?
Kind regards


Currently it's not possible, the .deb from the skype website is i386 .
There are some problems using multiarch on DD 64, see here:
http://murga-linux.com/puppy/viewtopic.php?p=881963#881963

I'll look at some possible workaround when I have time.

Fred
Back to top
View user's profile Send private message 
oui

Joined: 20 May 2005
Posts: 3379
Location: near Woof (Germany) :-) - 3 PC's: DELL SX280 750 MB Pentium4, Acer emachines 2 GB AMD64. DELL XPS15

PostPosted: Thu 18 Feb 2016, 04:07    Post subject:  

Thank you very much Fred

Next detail:

Modern browsers and flash plugins are so, that immediately the sound started, else if you only touch only a really little bit the window of the terrible advertising videos placed by the friend of humanity on the most internet pages.

at normal «master» and «speaker» are at range 60 % («headphone1» at 43 % but «headphone2» at terrible 100 %) in the default values having given to DebianDog64, those videos are a terrible inconvenient if you use the PC in the environment of your asleep partner or baby etc. and microphone is not on. if you use a voice system (ekiga etc.) you have always to turn it on and to open and increase the sound.

how to change the default values before remastering so, that they stay as entered by you after remastering? from which file are the default values coming from?

how far can the thematic of following recent message help here:

stemsee wrote:
well I don't want to distract from the thread but I didn't implement either cleanly because before I did I implemented this loop to ~.asoundrc

Code:
# ------------------------------------------------------
# hardware 0,0 : used for ALSA playback
pcm.loophw00 {
  type hw
  card Loopback
  device 0
  subdevice 0
  format S32_LE
  rate 48000
}

# ------------------------------------------------------
# playback PCM device: using loopback subdevice 0,0
# Don't use a buffer size that is too small. Some apps
# won't like it and it will sound crappy

pcm.amix {
  type dmix
  ipc_key 219345
  slave {
    pcm loophw00
    period_size 2048
    periods 2
  }
}

# ------------------------------------------------------
# software volume
pcm.asoftvol {
  type softvol
  slave.pcm "amix"

  control { name PCM }

  min_dB -51.0
  max_dB   0.0
}

# ------------------------------------------------------
# for jack alsa_in: looped-back signal at other ends
pcm.cloop {
  type hw
  card Loopback
  device 1
  subdevice 0
  format S32_LE
  rate 48000
}

# ======================================================
# ------------------------------------------------------
# hardware 0,1 : used for ALSA capture
pcm.loophw01 {
  type hw
  card Loopback
  device 0
  subdevice 1
  format S32_LE
  rate 48000
}

# ------------------------------------------------------
# for jack alsa_out: looped-back signal at other end
pcm.ploop {
  type hw
  card Loopback
  device 1
  subdevice 1
  format S32_LE
  rate 48000
}

# ======================================================
# ------------------------------------------------------
# duplex device combining our PCM devices defined above
pcm.aduplex {
  type asym
  playback.pcm "asoftvol"
  capture.pcm "loophw01"
}

# ------------------------------------------------------
# default device
pcm.!default {
  type plug
  slave.pcm aduplex

  hint {
       show on
       description "Duplex Loopback"
  }
}



Question

kind regards
Back to top
View user's profile Send private message 
fredx181


Joined: 11 Dec 2013
Posts: 3919
Location: holland

PostPosted: Thu 18 Feb 2016, 06:38    Post subject:  

Hi oui,

The file is '/var/lib/alsa/asound.state' where the mixer values are stored.
Comment this line in remasterdog to not remove it:
Code:
rm -f "$WORK"/var/lib/alsa/asound.state


To reflect the changes made in alsamixer directly during a session;
Code:
alsactl store 0


Quote:
how far can the thematic of following recent message help here:


I think none, it's not for mixer values stored

Fred
Back to top
View user's profile Send private message 
stemsee

Joined: 27 Jun 2013
Posts: 2342
Location: In The Way

PostPosted: Thu 18 Feb 2016, 08:50    Post subject:  

fredx181 wrote:
Adding this on top of $HOME/.dogradio/data/func should work (doesn't work adding to /usr/local/bin/dogradio):

Code:
#!/bin/bash

shopt -s expand_aliases
alias mplayer='mplayer -ao alsa:device=btheadset "$@"'

......
......


This worked great on top of what I alreay have set up as regards loop-back on alsa for jack audio!
Back to top
View user's profile Send private message MSN Messenger 
Display posts from previous:   Sort by:   
Page 10 of 38 [560 Posts]   Goto page: Previous 1, 2, 3, ..., 8, 9, 10, 11, 12, ..., 36, 37, 38 Next
Post new topic   Reply to topic View previous topic :: View next topic
 Forum index » Advanced Topics » Puppy Projects
Jump to:  

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You can download files in this forum


Powered by phpBB © 2001, 2005 phpBB Group
[ Time: 0.0733s ][ Queries: 13 (0.0231s) ][ GZIP on ]