lake_eleven wrote:
Can I put this over TT 3.0 and EDO 0.7 or should I start with a
vanilla SBT? Any one tried with TT 3.0 + EDO 0.7 OR do they overlap.
They are independent. What we are doing is just preventing the samba
and wireless services from being started only
Can I put this over TT 3.0 and EDO 0.7 or should I start with a
vanilla SBT? Any one tried with TT 3.0 + EDO 0.7 OR do they overlap.
lake_eleven's Profile: http://forums.slimdevices.com/member.php?userid=48979
View
Did anyone work out how to integrate these mods into TT3.0 ? Here is one
option.
Just noticed that TT3.0 shuts down Samba, but then it is restarted in
etc/init.d/rcS file, so I have tried commenting out the lines as per
dynaudiorules instructions below.
Don't comment out the /etc/init.d/wlan
SBGK wrote:
Did anyone work out how to integrate these mods into TT3.0 ? Here is one
option.
Just noticed that TT3.0 shuts down Samba, but then it is restarted in
etc/init.d/rcS file, so I have tried commenting out the lines as per
dynaudiorules instructions below.
Don't comment out
does this mod interfere with the android squeezebox app working??? (does
the android app depend on wireless??)
it seems to.. if it doesnt, please let me know.
if it DOES...how do I revert back to the normal state with JUST THE
toolbox 3.0 mods?
thanks for any help. in a bit of a pickle..my
Thank you very much, ill try it and hope to get better results by the
impact of both.
--
Jacky
Jacky's Profile: http://forums.slimdevices.com/member.php?userid=38257
View this thread:
Jacky;671920 Wrote:
How can I best reduce buffer size from default with dynobot´s mods but
without installing Soundcheck 3.0?
Thanks
Factory reset, then install Soundcheck 2.0, change buffer size and then
reinstall dynobot's mod...
--
Midnight
Midnight;672380 Wrote:
Factory reset, then install Soundcheck 2.0, change buffer size and then
reinstall dynobot's mod...
Thanx,
Found Soundcheck 2.0 for downloading, but no describtion anymore: can
you provide me with any instructions, please?
Never did such a mod before...
Reagrds
--
Jacky;672389 Wrote:
Thanx,
Found Soundcheck 2.0 for downloading, but no describtion anymore: can
you provide me with any instructions, please?
Never did such a mod before...
Reagrds
Sure,
1. Open Squeezebox Server in Firefox.
2. Open Settings/Advanced
3. Select File Types from the pull
How can I best reduce buffer size from default with dynobot´s mods but
without installing Soundcheck 3.0?
Thanks
--
Jacky
Jacky's Profile: http://forums.slimdevices.com/member.php?userid=38257
View this thread:
First of all, sorry for my bad English.
I just want to share some of my impressions regarding SPDIF jive_alsa
value settings:
By moving back forward of those, I settled finaly to
SPDIF 45 jive_alsa 45 for best musical balance and coherence over the
whole frequency spectrum.
Suggested
Are the dynobot's mods compatible with soundcheck's SB Toolbox 3.0?
Thanks in advance.
--
Fukinagashi
Fukinagashi's Profile: http://forums.slimdevices.com/member.php?userid=42922
View this thread:
Fukinagashi;667098 Wrote:
Are the dynobot's mods compatible with soundcheck's SB Toolbox 3.0?
Thanks in advance.
in soundcheck's blog he says maybe not and suggests that one not use
both at the same time as this could be doing something unexpected. He
says he does something similar to
oops installed 3.0 while having dynobot's in place,haven't noticed
anything weird but just to be sure how does one turn off bot's mods or
do i have to do a complete factory reset and start over?
--
c-eling
c-eling's
A hard rest was recommended by Soundcheck before installing 3.0. Which
should clear Dynobots mods.
--
mjock3
mjock3's Profile: http://forums.slimdevices.com/member.php?userid=49183
View this thread:
ok thanks,I'm going to give it a few more listens,but I'm not quite sure
if it did any harm,my Talking Heads 24/96 sounds amazing
--
c-eling
c-eling's Profile: http://forums.slimdevices.com/member.php?userid=48050
View
lag0a;666565 Wrote:
Does this forum not have a PM feature?
yes, click on the poster's name.
--
garym
Location 1: Vortexbox Appliance 6TB (1.10) SbS 7.6.2 Transporter,
Touch, Boom, Radio w/Battery (all ethernet except Radio)
Location 2: Win7(64) laptop SbS 7.6.2 TouchBenchmark DAC I,
dynaudiorules, what happened to you at head-fi?
Anyways I was wondering what usb receiver your'e using in your dac that
is powered by an external power supply or powered by your dac that the
OS recognizes using only the data+ and data- lines?
--
lag0a
ncarver;665451 Wrote:
I would keep thinking I heard weird instances of high frequency noise
when using it
I was using a transparent 1.5m cable was hearing a strange distortion
in the highs, I thought it was something else in the system, or just my
system -- but along the way i switched to
Thanks for the thoughts, Ncarver and Guidof. Much appreciated.
--
cymbop
cymbop's Profile: http://forums.slimdevices.com/member.php?userid=50761
View this thread: http://forums.slimdevices.com/showthread.php?t=89359
ncarver;659227 Wrote:
For reference, I am streaming flac files from the server (SBS) via
ethernet (wired), with the Touch connected via coax into a Wyred 4
Sound DAC-1.
By comparison, I have found that most every digital cable I have tried
between the Touch and DAC-1 affects the sound
I tried other digital cables (Audioquest, Monster, Oehlbach and Apogee).
Every spdif cable sounds different, but nothing sounds as good as my
1.8m Blue Jeans with Belden 1694a and Canare plugs :)
--
praganj
praganj's
praganj;665301 Wrote:
I tried other digital cables (Audioquest, Monster, Oehlbach and Apogee).
Every spdif cable sounds different, but nothing sounds as good as my
1.8m Blue Jeans with Belden 1694a and Canare plugs :)
Well, that's reassuring! Still interested in any
description/comparison
praganj;665301 Wrote:
I tried other digital cables (Audioquest, Monster, Oehlbach and Apogee).
Every spdif cable sounds different, but nothing sounds as good as my
1.8m Blue Jeans with Belden 1694a and Canare plugs :)
You may be interested in my experience with Toslink vs. coax:
cymbop;665297 Wrote:
I'm also running a hardwired touch via coax into a W4S DAC-2. Can you
share your experiences with different coax cables or point me to a link
if you've reported on them already? I've only used my trusty Bluejeans
coax, and am really curious about the differences you
praganj;662927 Wrote:
Today i installed SB_priority script and it is a very nice improvement
:)
Thanks to everybody, who did this work !
Now i am playing around with spdif value. It looks like higher values
50 are little bright, it seems that for me something like 45-48 is the
best. My
mjock3;663916 Wrote:
His first name is Ed, goes by Dynobot.
Would you mind telling me what version of firmware you are using?
Thanks,
Mark
@1 Great thanks to Ed for this nice SBT improvement !
@2 Few days ago i used offcial 7.6.1 firmware, yesterday i upgraded SBS
to 7.7.0 -
Today i installed SB_priority script and it is a very nice improvement
:)
Thanks to everybody, who did this work !
Now i am playing around with spdif value. It looks like higher values
50 are little bright, it seems that for me something like 45-48 is the
best. My Buffalo 2 DAC is probably
Yes, I understand. But here is my problem, after doing the rcS file
change something went wrong and I had to do a factory reset. After
doing the factory reset, I reinstalled TT 2.0, then went about
plugging in the commands from Dynobot's mods. When doing this I could
not hear the differences
mjock3;662081 Wrote:
Yes, I understand. But here is my problem, after doing the rcS file
change something went wrong and I had to do a factory reset. After
doing the factory reset, I reinstalled TT 2.0, then went about
plugging in the commands from Dynobot's mods. When doing this I could
mjock3;661122 Wrote:
Is there no one willing to give me a hand on this? Could it be my
firmware updated? Is anyone using 7.6.1 r9486 and hearing changes on
the fly with the spdif settings?
Not sure what you mean by on the fly with the spdif settings. chrt
immediately changes a process
Is there no one willing to give me a hand on this? Could it be my
firmware updated? Is anyone using 7.6.1 r9486 and hearing changes on
the fly with the spdif settings?
Mark
--
mjock3
mjock3's Profile:
lintweaker;651505 Wrote:
yep, changing the prios of the IRQ stuff seems to be working when the
commands are put directly in rcS after the last command. Putting a
little sleep (10 secs) make the jive_alsa commands work too.
This is how my rcS file look now (only the last bits):
===
Finally got around to trying this mod. Created scripts to set and reset
all the relevant rtpriorities, then sat with a (Linux) laptop and
toggled the settings back and forth as desired while listening.
Results: nothing at all. Not even the slightest hint of a possibility
of there being a
ncarver;659227 Wrote:
Finally got around to trying this mod. Created scripts to set and reset
all the relevant rtpriorities, then sat with a (Linux) laptop and
toggled the settings back and forth as desired while listening.
Results: nothing at all. Not even the slightest hint of a
Thanks alec_cat
--
lake_eleven
lake_eleven's Profile: http://forums.slimdevices.com/member.php?userid=48979
View this thread: http://forums.slimdevices.com/showthread.php?t=89359
That worked nicely for me. I have settled on a value of 40 instead of 50
here:
chrt -f -p 50 367
I'm really happy with the improvements from these mods and the
Soundchek mods. I have two Touch. One feeds a PS Audio DL-III and the
other drives a Channel Islands VDA2, each via spdif. Both
Here's the bottom end of mine - works fine on 7.6.1
# Start wlan
#/etc/init.d/wlan start
# Start all 'auto' interfaces
ifup -a
# Optional local rc script
if [ -x /etc/init.d/rcS.local ]; then
echo Running rcS.local
/etc/init.d/rcS.local
fi
# Optional media scripts
for script
Pilru;656307 Wrote:
I would suggest
while ! pidof jive_alsa
do
sleep 1
done
Much better - thanks, Pilru.
bentrix
--
bentrix
__
1 x Touch with DIY linear power supply
2 x Radio
1 x Duet Receiver
Lyngdorf TDAI-2200 with RoomPerfect
Bowers Wilkins 703 speakers
DIY
Can someone post the consolidated rcs file changes - for non-tech guys
like myself. There are so many suggestions given, not sure which one to
use.
--
lake_eleven
lake_eleven's Profile:
lake_eleven;656629 Wrote:
Can someone post the consolidated rcs file changes - for non-tech guys
like myself. There are so many suggestions given, not sure which one to
use.
+1 please.
--
bluestang
SB Touch (7 Android Tablet for remote) optical SPDIF Kenwood
Sovereign VR-4700 (3x
bentrix;652658 Wrote:
In the SB_priority file you have to wait for SqueezePlay to start the
jive_alsa process. The sleep xx does this fine but a better way to do
it - especially if you should ever want to run SB_priority manually - is
to use a while loop.
Insert these lines at the top of
sckramer;652579 Wrote:
ok i'll experiment with it... fyi some info on my modified DAC-- the
coax is isolated with a pulse transformer, it also converts it to a
balanced signal
...so my DAC might be immune to noise (like toslink)
also it has very low internal jitter (the mod includes a
In the SB_priority file you have to wait for SqueezePlay to start the
jive_alsa process. The sleep xx does this fine but a better way to do
it - especially if you should ever want to run SB_priority manually - is
to use a while loop.
Insert these lines at the top of the SB_priority file:
# Wait
Hey guys, great work on the SB_priority script, before I tried the
hardwired values, but it probably was not complete because of diff
process numbers-- I played around a little bit it def manipulates the
sound!
Any theories on what is happening, are we just adjusting the noise /
jitter going
sckramer;652492 Wrote:
Hey guys, great work on the SB_priority script, before I tried the
hardwired values, but it probably was not complete because of diff
process numbers-- I played around a little bit it def manipulates the
sound!
Any theories on what is happening, are we just
Phil Leigh;652551 Wrote:
Please try using an external DAC connected (only!) by toslink... Then
see if you can hear a difference...
ok i'll experiment with it... fyi some info on my modified DAC-- the
coax is isolated with a pulse transformer, it also converts it to a
balanced signal
...so my
magiccarpetride;651974 Wrote:
No, I'm not rebooting. I thought that the change takes effect instantly,
as I'm getting an immediate feedback in the console informing me that
the FIFO is modified the moment I presse the Return key.
If I need to reboot, then I don't see why not make the
magiccarpetride;651974 Wrote:
No, I'm not rebooting. I thought that the change takes effect instantly,
as I'm getting an immediate feedback in the console informing me that
the FIFO is modified the moment I presse the Return key.
If I need to reboot, then I don't see why not make the
ah..didn't know that, I'm editing the rcS file directly, hence the need
to reboot.
Sorry Alex, giving you duff info there.
--
Gazjam
Gazjam's Profile: http://forums.slimdevices.com/member.php?userid=18604
View this
alec_cat;652051 Wrote:
Hi Dave. Mine assumes the process IDs which are constant in my setup
right now. It's not as robust as Lintweaker's longer script inspecting
the process names to obtain and then set the process priorities using
IDs as variables. In future, should firmware upgrades
I made the changes 'stick' by using a combination of lintweakers changes
to rcS and suggestions made by JohnSwenson.
1. Add the following to the basic rcS script immediately before the
call to run squeezeplay (i.e. near the end of file):
# Call file 'SB_priority' to set all audio priorities
#
Hi there
Just ran across this mod which looks well worth trying with my Touch.
Excuse the dumb question - are these mods aimed at those users who have
an external DAC only or can it be used with a standalone Touch as well.
Many thanks in advance
Mark
--
pandasharka
Gazjam;652083 Wrote:
ah..didn't know that, I'm editing the rcS file directly, hence the need
to reboot.
Sorry Alex, giving you duff info there.
No worries Gaz, these things are very, very elaborate, there's lots of
moving parts, and we cannot all be making a career in systems and
network
bobertuk;652080 Wrote:
If you enter each command manually at the touch command-line it will
take effect immediately. If you want it to survive a Touch reboot -
e.g. a firmware update - it will need to be written into the Touch rcS
file as well.
Bob
That's how I understood it from the get
bobertuk;652116 Wrote:
I made the changes 'stick' by using a combination of lintweakers changes
to rcS and suggestions made by JohnSwenson.
1. Add the following to the basic rcS script immediately before the
call to run squeezeplay (i.e. near the end of file):
# Call file
rgro;652163 Wrote:
Bobcan I correctly assume that if I've got the sound effects turned
off (per Soundcheck's mods), that it is not necessary to include the
code for both retrieving and setting the jive_alsa sound effects? Or
would omitting that code screw something up?
Rick,
The check
bobertuk;652168 Wrote:
Rick,
The check for jive_alsa 'sound effects' was just to help sort out which
was the correct jive_alsa in the first place. As long as you leave in
the code for finding and setting 'jive_alsa audio', the code for sound
effects can be left out.
Bob
Thanks for
bobertuk;652168 Wrote:
Rick,
The check for jive_alsa 'sound effects' was just to help sort out which
was the correct jive_alsa in the first place. As long as you leave in
the code for finding and setting 'jive_alsa audio', the code for sound
effects can be left out.
Bob
Possibly
rgro;652184 Wrote:
Possibly having a small problemI created the file SB_priority in the
init.d folder and copy/pasted the script into that file and saved it.
I put the other command in like this (in the rcS file)
# Start squeezeplay
/etc/init.d/SB_priority
/etc/init.d/squeezeplay
So, the end of the rcS file should look like this, instead?
# Start squeezeplay
/etc/init.d/squeezeplay start
# Call file 'SB_priority' to set all audio priorities
# by ensuring squeezeplay is fully initialised first
/etc/init.d/SB_priority
--
rgro
Rick
System information
The end of my rcS file looks like this and I get no errors...
# Start Samba
#if [ -x /etc/init.d/samba ]; then
# /etc/init.d/samba start
#fi
# Call file 'SB_priority' to set all audio priorities
# by ensuring squeezeplay is fully initialised first
/etc/init.d/SB_priority
# Start
bobertuk;652218 Wrote:
The end of my rcS file looks like this and I get no errors...
# Start Samba
#if [ -x /etc/init.d/samba ]; then
# /etc/init.d/samba start
#fi
# Call file 'SB_priority' to set all audio priorities
# by ensuring squeezeplay is fully initialised first
Hi Rick,
You only have to type the 'chmod' command once before the first reboot.
It changes the file attributes permanently.
If you type the following at the command line:
ls -l /etc/init.d/SB_priority
It should return:
-rwxr-xr-x1 root root 1311 Aug 23 12:42
bobertuk;652252 Wrote:
Hi Rick,
You only have to type the 'chmod' command once before the first reboot.
It changes the file attributes permanently.
If you type the following at the command line:
ls -l /etc/init.d/SB_priority
It should return:
-rwxr-xr-x1 root root
lake_eleven;650646 Wrote:
Resetting SPDIF priority to 40, could not take any other value due to
harshness.
I must be going deaf, because I played with spdif values yesterday, and
I could not, for the life of me, detect much difference. Regardless of
whether I set it to 59, or to 41, or to any
alec_cat;651634 Wrote:
Thanks, John and lintweaker!
This is now working great in my rcS file (hardcoded as I have all
Soundcheck's mods, only 1 jive_alsa process, and don't use external
devices)
chrt -f -p 93 11
chrt -f -p 91 5
chrt -f -p 44 367
chrt -f -p 87 407
sleep 10
jalsa=`ps
magiccarpetride;651822 Wrote:
I must be going deaf, because I played with spdif values yesterday, and
I could not, for the life of me, detect much difference. Regardless of
whether I set it to 59, or to 41, or to any other value in between,
everything continued to sound gorgeous. There were
dynaudiorules;651840 Wrote:
Hi magic,
What Dac are you using? Sounds like your Dac might not be as sensitive
to the 'tuning'...
I think he's using a Beresford Caiman...
--
Phil Leigh
You want to see the signal path BEFORE it gets onto a CD/vinyl...it
ain't what you'd call minimal...
Caiman user here...
tweaking the different SPDIF values changes the sound noticably,
particularly in bass depth and soundstage.
Settled on value of 48 for now, but doing some new diy mods to my Dac,
so will have a play again once my ears burn in with the new discreet
regulators :)
--
Gazjam
dynaudiorules;651840 Wrote:
Hi magic,
What Dac are you using? Sounds like your Dac might not be as sensitive
to the 'tuning'...
I'm using Gatorized Beresford Caiman DAC.
Stupid question: it shouldn't matter what directory on the Touch I'm in
when playing with the chrt -f -p xx 367 command?
Gazjam;651873 Wrote:
Caiman user here...
tweaking the different SPDIF values changes the sound noticably,
particularly in bass depth and soundstage.
Settled on value of 48 for now, but doing some new diy mods to my Dac,
so will have a play again once my ears burn in with the new non
magiccarpetride;651937 Wrote:
I'm using Gatorized Beresford Caiman DAC.
Stupid question: it shouldn't matter what directory on the Touch I'm in
when playing with the chrt -f -p xx 367 command? Right now I'm in the
etc/init.d directory.
naa, doesn't matter which directory Alex.
--
Gazjam;651941 Wrote:
naa, doesn't matter which directory Alex.
That's what I thought, but I reckon better ask, just in case...
--
magiccarpetride
magiccarpetride's Profile:
magiccarpetride;651947 Wrote:
That's what I thought, but I reckon better ask, just in case...
Yeah, no worries.
Hey, are you making sure your rebooting teh Touch in between every
value change?
I think you need to do that for the new values to take effect?
--
Gazjam
Have used spdif 40 and jive_alsa 55 for a day and i think its to
dark...
So now I'm running at spdif 48 (my value before changing the jive_alsa)
and still with jive_alsa at 55.
I'm using a Audiolab CDQ 8200 as DAC and can heard great diff. in
sound.
And I think that this mod should be something
Gazjam;651953 Wrote:
Yeah, no worries.
Hey, are you making sure your rebooting the Touch in between every
value change?
I think you need to do that for the new values to take effect?
No, I'm not rebooting. I thought that the change takes effect
instantly, as I'm getting an immediate
bluestang;651827 Wrote:
Thanks for the tip alec_cat. Just started reading throught this thread
this weekend...lot's of great info here.
So let's see if I have this straight. If I hardcode your code above
into the rcS file, then it will always set it for me correctly? Even
if I reboot
yep, changing the prios of the IRQ stuff seems to be working when the
commands are put directly in rcS after the last command. Putting a
little sleep (10 secs) make the jive_alsa commands work too.
This is how my rcS file look now (only the last bits):
=== start ===
# Start Samba
# JK: Do not
Works in my Touch... Thanks
--
RotelMan
RotelMan's Profile: http://forums.slimdevices.com/member.php?userid=39498
View this thread: http://forums.slimdevices.com/showthread.php?t=89359
Brilliant!
Thanks JohnS and Lintweaker.
Thats script works for me.
Although my variant sets spdif to my new preferred value: 40
Yep no change at all to spdif!
This sounds the most natural, organic and right.
And even with a spdif at 40 jive_alsa at 55 sounds better
I also keep the usual:
Thanks for sharing HumanMedia... I will try spdif 40 with jive_alsa at
55 for a day or two :-)
--
RotelMan
RotelMan's Profile: http://forums.slimdevices.com/member.php?userid=39498
View this thread:
Thanks, John and lintweaker!
This is now working great in my rcS file (hardcoded as I have all
Soundcheck's mods, only 1 jive_alsa process, and don't use external
devices)
chrt -f -p 93 11
chrt -f -p 91 5
chrt -f -p 44 367
chrt -f -p 87 407
sleep 10
jalsa=`ps -C jive_alsa -o pid=`
chrt -f -p 55
Being new to this forum, I'll try not to make a complete fool of
myself... but
I recently upgraded from SBD to SBT and noticed an improvement.
Then I found the Toolbox2 mod and applied it except the WLAN (since I
use it) and the screen parts and have only the digital out enabled.
Maybe I could
tlicht;651388 Wrote:
Being new to this forum, I'll try not to make a complete fool of
myself... but
I recently upgraded from SBD to SBT and noticed an improvement.
Then I found the Toolbox2 mod and applied it except the WLAN (since I
use it) and the screen parts and have only the digital
tlicht;651388 Wrote:
...I really cannot hear any difference...
Maybe my equipment is too poor - or too good
/Thomas
:-)
--
avr300
/avr300
avr300's Profile:
Jeff Flowerday;651240 Wrote:
Just a wild guess but maybe the jive_alsa process hasn't spawned yet
when the rcS script fires?
This is true, the last thing in the rcS starts squeezeplay (the big
program that does all the SB stuff). Squeezeplay starts the jive_alsa
processes and then goes into
Yup. I just noticed it when I went up to 51 from 44... So I'll try 48
now... ;)
/Per
--
peber
peber's Profile: http://forums.slimdevices.com/member.php?userid=31446
View this thread:
Not only the quantity but the quality also. Changing the jive_asla to 55
i.e. higher than the SPDIF, seems to bring the balance back but I found
it just sounds wrong in my system so I've changed it back and dropped
to 44.
Do you find that 41 makes enough difference to be worthwhile over the
peber;651005 Wrote:
Yup. I just noticed it when I went up to 51 from 44... So I'll try 48
now... ;)
/Per
So you guys are all findng this is an issue even with jive_alsa set to
55?
--
HumanMedia
HumanMedia's
Setting jive_alsa to 55 enhances the entire sound stage, in my system it
is a welcome change. Increasing SPDIF priority is what changes the
equation of the music. It enhances certain high frequencies, thereby
creating a sense of spaciality and darker background. But as you listen
it is fatiguing
Phil Leigh;650551 Wrote:
Is anyone with a Benchmark or Lavry DAC able to test these mods?
Do you mean a properly designed one with competently executed jitter
rejection?
--
adamdea
adamdea's Profile:
adamdea;651104 Wrote:
Do you mean a properly designed DAC with competently executed jitter
rejection?
YES...
If these DAC's demonstrate the phenomena of their sound changing
according to these mods, I'm pretty sure I know what is causing it. If
owners of these DAC's do hear differences, I'd
I have a Benchmark. I thought about trying these mods and heard a huge
difference so didn't bother.
--
JezA
JezA's Profile: http://forums.slimdevices.com/member.php?userid=21219
View this thread:
lake_eleven;651102 Wrote:
Setting jive_alsa to 55 enhances the entire sound stage, in my system it
is a welcome change. Increasing SPDIF priority is what changes the
equation of the music. It enhances certain high frequencies, thereby
creating a sense of spaciality and darker background. But
BTW, I checked both with SPDIF out to my Anthem-pre directly and also
with DACMagic in between, both exhibit similar behavior.
--
lake_eleven
lake_eleven's Profile: http://forums.slimdevices.com/member.php?userid=48979
bobertuk;650552 Wrote:
Same here :(
I've checked the code manually by entering them at the command line and
it works.
i.e.
jalsa1=`ps -eo pid,args|grep jive_alsa -d default|head -1|cut -f3 -d
`
chrt -f -p 55 $jalsa1
BUT - when included in the rcS script it doesn't work.
Ideas
lintweaker;649299 Wrote:
I've been using the tweaks on my touches with great success and decided
to contribute a bit myself.
In case the IRQ's, process numbers etc. change you can use a more
dynamic version I hacked together (It is not fool proof!):
To test it out by hand just copy and
Hi
I made the changes in command/temp fashion last night, up to jive_alsa
55 and spdif 51. Fascinating. Without changing the jive from default,
59 was shocking in the change possible but I preferred 44 - 48 looked
to have more potential.
Can I clarify a passing comment earlier in the thread? If
Last night late, I pushed the reset button on my modified Touch in my
bedroom system (http://cgi.audioasylum.com/systems/5771.html) and set
it back to factory settings to get the latest firmware (7.6.0 r9548.)
I then added Klaus' TT 2.0 w/ the buffer @ 3600 and only the analog
outs turned on.
1 - 100 of 227 matches
Mail list logo
