[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: KPSK v.1.0rc1 released (PSK31 for KDE 3.x)



One other thing...should have rolled this into the other message:  With the 
settings previously reported (start artsd at startup, autosuspend after 30 
secs, do not run realtime priority) ARts Control Tool reported "The aRts 
sound daemon is suspended. Legacy applications can use the sound card now."

So, it looks like if an application is using the soundcard while arts is 
suspended, like KPSK, arts will not unsuspend until that application gives up 
control....this is a good thing, I think!  :)

Ernie

On Friday 06 September 2002 10:58 pm, w9ya wrote:
> Um, I won't be able to do that anytime soon, as I am not set up to test
> actual audio out.
>
> I was compiling this for my distro (sorcerer) as I am nominally in charge
> of the ham programs and such.
>
> Anyways, I *would* like to hear how the unsuspend works in your testing.
>
> (I *DO* plan on using psk31 soon though!)
>
> Bob
> w9ya
>
> On Friday 06 September 2002 10:27 pm, Ernest Stracener wrote:
> > Great!  I will try testing it here in just a few minutes...maybe we can
> > each try to cause artsd to unsuspend while kpsk is running...don't know
> > how, but maybe monkey with different stuff to see if we can crash it.
> > Yahoo!
> >
> > I'll let you know how my test goes...
> >
> > Ernie
> >
> > On Friday 06 September 2002 10:31 pm, w9ya wrote:
> > > Yes apparently this will take care of bringing up the program. Although
> > > I am not sure this will not be an issue because of the auto un-suspend
> > > deal. That may well affect smooth operation. Dunno. Perhaps you can
> > > test this?
> > >
> > > BTW the default setting for this is 60 secs. Although it seems much
> > > shorter now that I test it.
> > >
> > > Anyways, thanxs for all the help to you and Joop !
> > >
> > > Bob
> > > w9ya
> > >
> > > On Friday 06 September 2002 10:00 pm, Ernest Stracener wrote:
> > > > I did some searching and found a few references to it.  Apparently
> > > > this is a common problem & appears to be due to the way that artsd
> > > > locks up the soundcard.  From the KDE soundserver documentation:
> > > >
> > > > (option)"Autosuspend if idle for.  Normally aRts locks the sound card
> > > > device, so that other applications cannot use it. If you enable this
> > > > option, then if aRts has been idle for the amount of time you set, it
> > > > will suspend itself, allowing any application access to the sound
> > > > hardware. If aRts receives another request, it will unsuspend, and
> > > > continue as normal. Enabling this option may cause a small delay when
> > > > you start an aRts application."
> > > >
> > > > Perhaps turning off the system sounds notifications would allow artsd
> > > > to suspend and allow other applications to use the sound device?
> > > >
> > > > Ernie
> > > >
> > > > On Friday 06 September 2002 09:21 pm, w9ya wrote:
> > > > > Well, o.k...that's what I thought it might be.
> > > > >
> > > > > So I assume this will not be a "wholy" kde3 compatable program
> > > > > then. i.e. having to turn off arts and etc. Is that right?
> > > > >
> > > > > Bob
> > > > > w9ya
> > > > >
> > > > > On Friday 06 September 2002 07:26 pm, Ernest Stracener wrote:
> > > > > > Hello Bob!
> > > > > >
> > > > > > That's an easy one! Joop was right on the money.
> > > > > >
> > > > > > You need to turn off the ARtsD soundserver:
> > > > > > kcmshell arts
> > > > > > Uncheck the "Start ARtsD soundserver at startup" box, OK & exit.
> > > > > > Restart KPSK.
> > > > > >
> > > > > > To transmit, you will need to have write permissions for
> > > > > > /dev/ttyS0 (or your port)...most easily achieved by adding your
> > > > > > username to the group that owns the ports (e.g. ls -al
> > > > > > /dev/ttyS0, get into that group--for redhat it is group 'uucp')
> > > > > >
> > > > > > Thanks for giving it a shot...let me know how it goes.  I am now
> > > > > > subscribed to Debian Hams, so a post to the list will get to me.
> > > > > > Otherwise there is a kpsk-user list at the sourceforge project
> > > > > > page.
> > > > > >
> > > > > > Good luck & I hope to see you on the waterfall soon!
> > > > > >
> > > > > > 73-
> > > > > > Ernie
> > > > > >
> > > > > > On Friday 06 September 2002 07:04 pm, w9ya wrote:
> > > > > > > On Friday 06 September 2002 03:03 pm, Ernest Stracener wrote:
> > > > > > > > KPSK is a PSK31 application for KDE 3.x and Qt 3.x.
> > > > > > > >
> > > > > > > > A new release candidate of KPSK has been released for testing
> > > > > > > > and bugspotting/squashing.
> > > > > > >
> > > > > > > O.K. here's a quick report.
> > > > > > >
> > > > > > > I use the default kde3 stuff for audio, which for me is 3.0.2
> > > > > > > on top of qt 3.0.5. Anyways, all the stuff for audio works fine
> > > > > > > , xine (dvd's), mouse and keyboard mistake beeps, watching tee
> > > > > > > wee with xawtv, adn probably other stuff I am missing.
> > > > > > >
> > > > > > > KPSK wants something more than this, probably a soundcard
> > > > > > > deally not doubt, but it is complaining about "device or
> > > > > > > resource busy" on /dev/audio, which for me is not a symlink and
> > > > > > > is 660. I changed it to 777 and still "no go" with the same
> > > > > > > complaints.
> > > > > > >
> > > > > > > I haven't read the fine manual yet, so please forgive this if
> > > > > > > that info is in it, just was hoping if it was a kde3 style app
> > > > > > > that wouldn't be necessary somehow. i.e. that the audio would
> > > > > > > just "happen" so to speak.
> > > > > > >
> > > > > > > Thanxs for your time, and vy 73;
> > > > > > >
> > > > > > > bob
> > > > > > > w9ya
> > > > > > >
> > > > > > > > Full details, documentation, packages and screenshots are
> > > > > > > > available at http://1409.org/projects/kpsk . Packages are
> > > > > > > > also on the project's development page is at
> > > > > > > > http://sf.net/projects/kpsk .
> > > > > > > >
> > > > > > > > 73-
> > > > > > > > Ernie
> > > > > > > > KG9NI
> > > > > > > >
> > > > > > > > (I am not currently subscribed to debian-hams, so if you have
> > > > > > > > any questions, please contact me directly)



Reply to: