[Lmuse-developer] [ lmuse-Bugs-1334569 ] no Audio sound.

[SourceForge.net <noreply@so...>]

Bugs item #1334569, was opened at 2005-10-21 18:03
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=604222&aid=1334569&group_id=93414

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Bill Brown (wbrown338)
Assigned to: Nobody/Anonymous (nobody)
Summary: no Audio sound.

Initial Comment:
Greetings:

I cannot hear audio within muse.  I started jackd and
then muse 0.72pre2 from the command line with -D.  I
imported a wave file and tried to play it.  Here is the
debug output:

FIFO 0x8633a9c underrun...
WaveTrack::getData(Track 1) fifo underrun
fifo get error expected 1024, got 64512
fifo get error expected 2048, got 65536
fifo get error expected 3072, got 66560
fifo get error expected 4096, got 67584
...

I am running ubuntu linux (Gnome) with uname -a:
Linux ubuntu 2.6.12-9-386 #1 Mon Oct 10 13:14:36 BST
2005 i686 GNU/Linux

Have you seen this before?  Do you know how I can try
to trouble shoot this to get the sound working?  Any
help would be apreciated.  
Thanks.


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=604222&aid=1334569&group_id=93414

Re: [Lmuse-developer] Re: todo-numbering

[Mathias Lundgren <gavel@sp...>]

> Fr=E5n: ws@...
> Till: gavel@...
> Rubrik: [Lmuse-developer] Re: todo-numbering
> Datum: Fri, 21 Oct 2005 15:00:09 +0000

> On Thursday 20 October 2005 20:37, Mathias Lundgren wrote:
> > Hi, this is a question for you, Werner-mann:
> >
> > I'm just wondering what the general idea with the TODO-numbering is.
> > I've seen TODO1, TODO2 and TODO3, and I figure that it has to do with
> > priority. The question is if it has to do with order (first do TODO1.=
..)
> > or a scale of how important they are (TODO3 > TODO1 and thus TODO3 mo=
re
> > important). If I would have to bet money on it I would bet on order, =
not
> > scale.
> >
> > The other question is if you're planning to do these things yourself,=
 or
> > if you've left those messages there for people like me to dig into? :=
-D
> >
> > /Mathias
>=20
> there is nothing special with TODO-numbers. They are only simple text
> markers
> i can easy grep for.
> For example in the process of porting the code to Qt4 i commented out a=
 lot
> of=20
> functionality in order to get the whole thing compilable again.
> All commented out code is marked with "TD" so i can find and fix this
> pieces
> later on.
> TODO's without a number tend to mark real problems or missing code. And
> some
> of them are there a long time...
>=20
> If you are looking for TODO's there is plenty left in the porting proce=
ss,
> starting with simple changing all "s.latin1()" calls to
> "s.toLatin1().data()"
> or replacing all *.ui3 files with *.ui ones (the current snapshot uic3=20
> compiler
> generates bad code). Goal is to get rid of the Qt3 compatibility librar=
y.
> Other things look more complicated like how to implement list header it=
ems
> (not only separators) or how to implement multi column pulldown menus.
>=20
> I'm currently working on getting the controller editors working again.=20
> Its more complicated and time consuming than i first thought. There are
> also some issues with the qt4 lib which are fixed in the current qt
> snapshot
> (which has other problems :-( ) which costs extra time.
>=20
> /Werner
>=20

I'm just trying to port the popup menus which currently needs some change=
s when it comes to the checking behaviour (and menu title). I'm simply tr=
ying to stick to the same behaviour as previously, hope you don't have pl=
ans for any new changes here.

/Mathias

[Lmuse-developer] Re: todo-numbering

[<ws@se...>]

On Thursday 20 October 2005 20:37, Mathias Lundgren wrote:
> Hi, this is a question for you, Werner-mann:
>
> I'm just wondering what the general idea with the TODO-numbering is.
> I've seen TODO1, TODO2 and TODO3, and I figure that it has to do with
> priority. The question is if it has to do with order (first do TODO1...)
> or a scale of how important they are (TODO3 > TODO1 and thus TODO3 more
> important). If I would have to bet money on it I would bet on order, not
> scale.
>
> The other question is if you're planning to do these things yourself, or
> if you've left those messages there for people like me to dig into? :-D
>
> /Mathias

there is nothing special with TODO-numbers. They are only simple text markers
i can easy grep for.
For example in the process of porting the code to Qt4 i commented out a lot of 
functionality in order to get the whole thing compilable again.
All commented out code is marked with "TD" so i can find and fix this pieces
later on.
TODO's without a number tend to mark real problems or missing code. And some
of them are there a long time...

If you are looking for TODO's there is plenty left in the porting process,
starting with simple changing all "s.latin1()" calls to "s.toLatin1().data()"
or replacing all *.ui3 files with *.ui ones (the current snapshot uic3 
compiler
generates bad code). Goal is to get rid of the Qt3 compatibility library.
Other things look more complicated like how to implement list header items
(not only separators) or how to implement multi column pulldown menus.

I'm currently working on getting the controller editors working again. 
Its more complicated and time consuming than i first thought. There are
also some issues with the qt4 lib which are fixed in the current qt snapshot
(which has other problems :-( ) which costs extra time.

/Werner