You can subscribe to this list here.
2004 |
Jan
|
Feb
|
Mar
(189) |
Apr
(40) |
May
(8) |
Jun
(6) |
Jul
(5) |
Aug
|
Sep
|
Oct
|
Nov
(13) |
Dec
(10) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2005 |
Jan
(4) |
Feb
(1) |
Mar
(3) |
Apr
|
May
(7) |
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
(1) |
2006 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
(1) |
Sep
(8) |
Oct
(19) |
Nov
(19) |
Dec
(7) |
2007 |
Jan
(6) |
Feb
(6) |
Mar
(3) |
Apr
(6) |
May
(1) |
Jun
(1) |
Jul
|
Aug
(1) |
Sep
|
Oct
(1) |
Nov
(2) |
Dec
(1) |
2008 |
Jan
(19) |
Feb
(1) |
Mar
(40) |
Apr
(31) |
May
(174) |
Jun
(24) |
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
(64) |
Dec
(17) |
2009 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(14) |
Nov
|
Dec
|
2010 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
(7) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2011 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(2) |
Sep
|
Oct
|
Nov
|
Dec
|
2012 |
Jan
|
Feb
(5) |
Mar
(1) |
Apr
(1) |
May
(3) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2013 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(11) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: D.B. M. <db...@ho...> - 2008-05-15 02:14:36
|
Greetings, ---------------------------------------- > Date: Tue, 13 May 2008 21:38:17 -0700 > Subject: Re: [jazzplusplus-devel] configure.ac update -please test- > > DM = D.B. Moore > DM> Yep, no problem.... the back trace without vkeybd > DM> running but with jack/fluidsynth/qsynth running > DM> and ready to go (complete session); > >> Program received signal SIGSEGV, Segmentation fault. >> [Switching to Thread 140090596853472 (LWP 3341)] >> snd_seq_port_subscribe_set_sender (info=0x7fff6a45d310, addr=0x0) at seq.c:2432 >> 2432 memcpy(&info->sender, addr, sizeof(*addr)); >> Current language: auto; currently c >> >> (gdb) bt >> #0 snd_seq_port_subscribe_set_sender (info=0x7fff6a45d310, addr=0x0) >> at seq.c:2432 >> #1 0x0000000000426a59 in tAlsaPlayer::subscribe_inp (this=0xb68020, inp=0) >> at ../../jazz/src/AlsaPlayer.cpp:219 > > My current guess is an invalid input or output device index. Could you > update you source tree, rebuild, run again and let me know how it goes? > Same env as before..ie; vkeybd not running but with jack/fluidsynth/qsynth running and ready to go. Test build @ revision 527 (complete session); (gdb) run Starting program: /root/Jazz++/TestInstall/bin/jazz warning: no loadable sections found in added symbol-file system-supplied DSO at 0x7fff30bfe000 [Thread debugging using libthread_db enabled] [New Thread 140725286655712 (LWP 11863)] JZProject::ReadConfiguration() ConfFileNameAndPath: "/root/Jazz++/TestInstall/share/Jazz++/jazz.cfg" JZConfiguration::LoadConfig: "/root/Jazz++/TestInstall/share/Jazz++/jazz.cfg" Include synthesizer configuration file "gs.jzi" FindFile: Immediate hit on file "gs.jzi" Include file "gsdrmset.jzi" FindFile: Immediate hit on file "gsdrmset.jzi" Include file "gmdrmnam.jzi" FindFile: Immediate hit on file "gmdrmnam.jzi" Include file "gsvoices.jzi" FindFile: Immediate hit on file "gsvoices.jzi" Include file "ctrlnam.jzi" FindFile: Immediate hit on file "ctrlnam.jzi" created client:port = 131:0 Input device count: 0 INFO: input device is -1, so selecting one. no device found! Input device is: -1 INFO: output device is -1, so selecting one. //pops 'select output device' dialog window // candidates -- client 128 qjackctl | fluid synth (11837) Synth input port (11837.0) //selecting fluid synth entry, click on OK WARNING: The output device index is out of range! Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 140569115023072 (LWP 11874)] 0x0000000000426cea in tAlsaPlayer::SetSoftThru (this=0xb68010, on=1, idev=0, odev=0) at ../../jazz/src/AlsaPlayer.cpp:224 224 thru->SetSource(iaddr[ithru].client, iaddr[ithru].port); (gdb) bt #0 0x0000000000426cea in tAlsaPlayer::SetSoftThru (this=0xb68010, on=1, idev=0, odev=0) at ../../jazz/src/AlsaPlayer.cpp:224 #1 0x0000000000427ce0 in tAlsaPlayer (this=0xb68010, song=0x7fd8cc267010) at ../../jazz/src/AlsaPlayer.cpp:182 #2 0x0000000000423638 in tAlsaAudioPlayer (this=0xb68010, pSong=0x7fd8cc267010) at ../../jazz/src/AlsaDriver.cpp:127 #3 0x00000000004ba196 in JZProject (this=0x7fd8cc267010) at ../../jazz/src/Project.cpp:194 #4 0x0000000000498db0 in JZJazzPlusPlusApplication::OnInit (this=0xafe690) at ../../jazz/src/JazzPlusPlusApplication.cpp:127 #5 0x00000000004991fe in wxAppConsole::CallOnInit (this=0xafe690) at /usr/local/wx287/include/wx-2.8/wx/app.h:76 #6 0x000000000079a9ca in wxEntry () #7 0x0000000000499178 in main (argc=1, argv=0x7fffd42daae8) at ../../jazz/src/JazzPlusPlusApplication.cpp:63 Hope this helps, regards Donald B _________________________________________________________________ Are you paid what you're worth? Find out: SEEK Salary Centre http://a.ninemsn.com.au/b.aspx?URL=http%3A%2F%2Fninemsn%2Eseek%2Ecom%2Eau%2Fcareer%2Dresources%2Fsalary%2Dcentre%2F%3Ftracking%3Dsk%3Ahet%3Asc%3Anine%3A0%3Ahot%3Atext&_t=764565661&_r=OCT07_endtext_salary&_m=EXT |
From: Robert V. <vo...@ct...> - 2008-05-15 00:44:30
|
False alarm. Getting the cfg file out of my home directory changed everything. First it opened a dialog that allowed me to specify the device environment, then I was happy to see that the sequence is now working, and the metronome no longer hangs...although I can't really hear the metronome yet. Sounds good. Is the reccord button implemented ? Bob On Wed, 2008-05-14 at 06:49 +0000, D.B. Moore wrote: > > ---------------------------------------- > > Date: Tue, 13 May 2008 22:10:47 -0700 > > Subject: [jazzplusplus-devel] Debian Build and Run Attempt > > > > RV = Robert Vogel wrote me on Sun, 11 May 2008 23:14:04 -0400 > > RV> Hi Pete, > > RV> > > RV> I tried compiling Jazz++ on my Debian Etch stable system. > > RV> It looked ok throughout the build process, and it produced > > RV> an executable. When I tried opening the executable, it > <> > > > Thanks for trying this with the code in such a preliminary state. I'm > > just trying to get a MIDI file loading and playing on all platforms at > > this point. > > > > Try the suggestions above... > > > > 1. Update the code and rebuild. You can copy the new jazz binary over > > the one in TestInstall/bin. > > 2. Rename the config file in your home directory so it isn't used. > > 3. Make sure the .alsa_input_device and the .alsa_output_device entries > > in TestInstall/share/Jazz++/jazz.cfg are set to -1 so you will be > > prompted for input and output devices. > > 4. Run the version in TestInstall/bin. > > > > Let us know how it goes. > > Hmmm....one of my house-mates has a Debian Etch installation on > ix86 and it has an emu10k1 fitted to it, so I might actually try latest > against his hardware/Etch here later to compare results.... > > Regards, > > Donald B > > > _________________________________________________________________ > Search for local singles online @ Lavalife - Click here > http://a.ninemsn.com.au/b.aspx?URL=http%3A%2F%2Flavalife9%2Eninemsn%2Ecom%2Eau%2Fclickthru%2Fclickthru%2Eact%3Fid%3Dninemsn%26context%3Dan99%26locale%3Den%5FAU%26a%3D30290&_t=764581033&_r=email_taglines_Search_OCT07&_m=EXT > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > jazzplusplus-devel mailing list > jaz...@li... > https://lists.sourceforge.net/lists/listinfo/jazzplusplus-devel |
From: D.B. M. <db...@ho...> - 2008-05-14 18:55:48
|
Greetings, Pete, here's my proposal for the majority of content for the bug reports webpage. As opposed to simple editing and correcting of existing content, this is new content submitted for your approval. Please review (holding in mind certain points detailed below), and deal with it as you see fit. There are things missing/omitted from this draft that need be addressed. Exampled paths are relative to linux, as are some of the command sequences. *Add Windows and Mac paths relative to examples.as required *Include any Windows and Mac specific commands or methodology if required See attached file :- htdocs-bugreports-instructions.patch.gz **BE WARNED** -- although the formatting output looked fine here, I noticed the patch looked a little strange...almost like my CR turned itself off. Too tired to deal with that now - supplied as a patch with a warning that WYS is not nearly always WYG.... ...And of course, to everyone else here - have a look at the content, and see what you think. Anything missing? Things I shouldn't have said or ought to have said? I'm sure everyone knows the drill, and understands criticism both good and/or bad is expected and always welcome. I'll checkout a build of rev.525 in the morning. Regards, Donald B. _________________________________________________________________ Be part of history. Take part in Australia's first e-mail archive with Email Australia. http://emailaustralia.ninemsn.com.au |
From: Pete S. <pst...@gm...> - 2008-05-14 13:53:08
|
Donald, I just wanted to warn you I moved the jazz/doc directory to jazz/src/HelpFiles. Pete |
From: D.B. M. <db...@ho...> - 2008-05-14 06:49:14
|
---------------------------------------- > Date: Tue, 13 May 2008 22:10:47 -0700 > Subject: [jazzplusplus-devel] Debian Build and Run Attempt > > RV = Robert Vogel wrote me on Sun, 11 May 2008 23:14:04 -0400 > RV> Hi Pete, > RV> > RV> I tried compiling Jazz++ on my Debian Etch stable system. > RV> It looked ok throughout the build process, and it produced > RV> an executable. When I tried opening the executable, it <> > Thanks for trying this with the code in such a preliminary state. I'm > just trying to get a MIDI file loading and playing on all platforms at > this point. > > Try the suggestions above... > > 1. Update the code and rebuild. You can copy the new jazz binary over > the one in TestInstall/bin. > 2. Rename the config file in your home directory so it isn't used. > 3. Make sure the .alsa_input_device and the .alsa_output_device entries > in TestInstall/share/Jazz++/jazz.cfg are set to -1 so you will be > prompted for input and output devices. > 4. Run the version in TestInstall/bin. > > Let us know how it goes. Hmmm....one of my house-mates has a Debian Etch installation on ix86 and it has an emu10k1 fitted to it, so I might actually try latest against his hardware/Etch here later to compare results.... Regards, Donald B _________________________________________________________________ Search for local singles online @ Lavalife - Click here http://a.ninemsn.com.au/b.aspx?URL=http%3A%2F%2Flavalife9%2Eninemsn%2Ecom%2Eau%2Fclickthru%2Fclickthru%2Eact%3Fid%3Dninemsn%26context%3Dan99%26locale%3Den%5FAU%26a%3D30290&_t=764581033&_r=email_taglines_Search_OCT07&_m=EXT |
From: D.B. M. <db...@ho...> - 2008-05-14 06:01:02
|
---------------------------------------- > Date: Tue, 13 May 2008 21:53:18 -0700 > Subject: Re: [jazzplusplus-devel] Question about external link references > > DM = D.B. Moore > DM> My question is, do we wish to email such documents' > DM> authors, kindly requesting them to update their links?? > > Your call. > > DM> I primarily ask this because of jazz++'s early > DM> development stage..ie; if there were fully functional > DM>> tarballs available of any kind for jazz++ now, I > DM> wouldn't ask - I'd just send the emails to the authors > DM> concerned and report that action here. > DM> > DM> Let me know, as it's fairly easy (and convenient) for > DM> me to include such tasks in my current activities here... > > Your email to them could > > 1. indicate we are in the early stages of reviving Jazz++ > 2. point to the new web site > 3. point out that the keepers of the old site blessed this project > 4. mention the link on their site is broken so they should either remove > it or update it to point to our project. > Sounds like a plan....I'll sent about wording that up soon.. Regards, Donald B _________________________________________________________________ Be part of history. Take part in Australia's first e-mail archive with Email Australia. http://emailaustralia.ninemsn.com.au |
From: Pete S. <pst...@gm...> - 2008-05-14 05:22:51
|
>> Subject: SF.net SVN: jazzplusplus: [515] tex2rtf >> Date: Sun, 11 May 2008 23:50:54 -0700 >> >> Revision: 515 >> http://jazzplusplus.svn.sourceforge.net/jazzplusplus/?rev=515&view=rev >> Author: pstieber >> Date: 2008-05-11 23:50:53 -0700 (Sun, 11 May 2008) >> >> Log Message: >> ----------- >> Added a forked version of tex2rtf. The code has a patch applied that allows >> it to build with a version of wxWidgets that is built using stl options. >> A complete build system is not in place and will have to be added. The >> wxWidgets project is no longer using this code to build documentation >> and will not include it in post 2.8.* distributions. The fork was OKed >> on the wxWidgets developer list by Julian Smart, the original author of >> this code. >> DM = D.B. Moore DM> Do you think we should announce this on the news DM> page, and openly thank/acknowledge Julian for DM> such a kind and co-operative gesture? Keep the thought, but let's wait until I get something working. Pete |
From: Pete S. <pst...@gm...> - 2008-05-14 05:20:30
|
DM = D.B. Moore DM> This content is now in my focus, however I've only DM> done a preliminary perusal of the existing (old..) DM> documentation, for the purpose of forming a rewrite DM> stratagem. I'm hoping that raising this discussion DM> here will help form and clarify this process DM> *before* I actually start work in this area....so.... I'm going to keep a copy of the PDF generated from this old stuff on my desktop for a while. It will help me understand the original intent of the code. DM> Quite obviously, the existing documentation is quite DM> out-of-step with what the eventual release of jazz++ DM> will be - it will look different, it may have different DM> functions or do things in different ways than previous DM> releases of jazz - I have no real way of accurately DM> forecasting what these differences or changes might be DM> - this is particularly so in the linux case with the DM> current status of 'minimal functionality'. All of the builds are in roughly the same state. DM> Questions: How disparate ..functionality wise...is the DM> current Windows build compared to the Mac & Linux DM> positions? Are all the builds 'on the same page' as DM> it were? I haven't hooked the Mac version up to and device. I'm getting help with that from Leland. Leland could you introduce yourself to this list? DM> In any event and as I infer here, updates to these DM> areas of the documentation will become apparent as DM> functionality increases, and will move in concert, DM> with one area slightly behind the other. Makes sense. As I said, I'm relying on the old docs as a development guide at this point. DM> Likewise, screen-shots are bound up in here somewhere as DM> well. DM> DM> That said, other sections of jazz.tex are really dated DM> and out-of-sync with the current linux position regarding DM> audio/MIDI device options, be that real hardware DM> devices/cards, or 'pseudo' devices like the many linux DM> applicable 'softsynth' applications that exist today DM> (which weren't around when the original docs were drafted)... DM> not to mention many MIDI applications that have sprung up DM> between then and now as well. DM> DM> Seeing as we both agreed upon some form of 'how to use jazz++ DM> with 'x'' (where 'x' is one of those applications I speak DM> of above) section, I'll get to a draft of that in the coming DM> time. Remember though, interoperability and functionality DM> usually go hand in hand, and so I'm thinking everything DM> I've touched on so far will move forward at about the same DM> rate... DM> DM> Other sections, I want to fix right away....in particular, DM> references to 'OSS' sound drivers for linux. I mean...even DM> if one does want to use the old OSS API, you're going to DM> use 'snd-*-oss' modules that plugin to the alsasound API DM> ...so I think OSS is fairly redundant stuff now. DM> DM> I think what I would like to do, is remove all references DM> to the old OSS modules altogether, and instead just touch DM> upon same in a short introductory paragraph to this DM> particular section, along the lines of -- 'In the past, DM> jazz++ relied on the now deprecated 'OSS' sound drivers in DM> linux, to......' , following this up with a short paragraph DM> explaining the state of play now with linux and the alsasound DM> drivers....and beyond that, the configuration details focus DM> entirely on what's current with linux today. DM> DM> What do we think here? Comments? Thoughts? Sounds good to me. Last post of the night for me. Good night, and see you all tomorrow, Pete |
From: Pete S. <pst...@ve...> - 2008-05-14 05:10:56
|
RV = Robert Vogel wrote me on Sun, 11 May 2008 23:14:04 -0400 RV> Hi Pete, RV> RV> I tried compiling Jazz++ on my Debian Etch stable system. RV> It looked ok throughout the build process, and it produced RV> an executable. When I tried opening the executable, it RV> didn't prompt for a configuration file, but it found one RV> in my home directory. I'm not sure it is the correct RV> jazz.cfg though. (attached) Try renaming it. RV> When I execute from the TestInstall it does open a RV> window and a midi file is visible there. It doesn't RV> play though. It only makes a few low cello-like RV> sounds...about the first two bars... and then the RV> curser stops and advances no further. In another RV> window I have an alsaconnect gui...which does not RV> actually see jazz++. Could you update your source tree and try it again? RV> I connect my Yamaha ES8 keyboard to a UX16 usb RV> connector which is configured with alsaconnectgui. RV> Usually I can use the keyboard to connect with a RV> software synth or I can use Rosegarden to drive RV> using the alsa connectivity. Anyway Jazz++ doesn't RV> appear to be recognized by alsa. It doesn't show RV> up in the alsaconnect gui. RV> RV> Rosegarden complains every time I start it that the RV> 'system timer resolution is too low'. I know I need RV> to find a RT kernel, but I've been too cautious to RV> try one yet. Soon. That's why I need to be able to RV> connect to an external device or to a soft synth. RV> RV> Here are results for the menus. RV> RV> The 'preferences' on the file menu looks to be a stub. Correct. RV> I didn't get far enough along to try the edit functions. Event selection is a work in progress and isn't integrated with window scrolling, so this could be problematic. RV> The metronome causes an immediate segmentation fault RV> and a hard crash. Do you mean editing the metronome or trying to turn it on? RV> The Jazz++ harmony window looks nice. If I right click RV> on the various chord buttons they play with a guitar-like RV> sound. I have Jazz++ set up as a GM synth. I can see the RV> ux16 and click on it, but it doesn't do anything. RV> RV> The audio menu seems to be all stubs. Is that right ? That is correct. RV> Help menus are unpopulated. Probably I missed the 'make' RV> command for the documentation (?) This is not implemented, but we are working on it. RV> I'm attaching the config.log for your consideration. RV> RV> Hope this is helpful for you. If you let me know what RV> I can do to fix it, I'll try again. RV> RV> Bob Thanks for trying this with the code in such a preliminary state. I'm just trying to get a MIDI file loading and playing on all platforms at this point. Try the suggestions above... 1. Update the code and rebuild. You can copy the new jazz binary over the one in TestInstall/bin. 2. Rename the config file in your home directory so it isn't used. 3. Make sure the .alsa_input_device and the .alsa_output_device entries in TestInstall/share/Jazz++/jazz.cfg are set to -1 so you will be prompted for input and output devices. 4. Run the version in TestInstall/bin. Let us know how it goes. Pete |
From: Pete S. <pst...@gm...> - 2008-05-14 04:53:18
|
DM = D.B. Moore DM> My question is, do we wish to email such documents' DM> authors, kindly requesting them to update their links?? Your call. DM> I primarily ask this because of jazz++'s early DM> development stage..ie; if there were fully functional DM>> tarballs available of any kind for jazz++ now, I DM> wouldn't ask - I'd just send the emails to the authors DM> concerned and report that action here. DM> DM> Let me know, as it's fairly easy (and convenient) for DM> me to include such tasks in my current activities here... Your email to them could 1. indicate we are in the early stages of reviving Jazz++ 2. point to the new web site 3. point out that the keepers of the old site blessed this project 4. mention the link on their site is broken so they should either remove it or update it to point to our project. Pete |
From: Pete S. <pst...@gm...> - 2008-05-14 04:48:17
|
DM = D.B. Moore DM> I actually know about gdb, backtraces and so forth. DM> I doubt one could build a Free software based systems DM> for as long as I have without needing this 'software DM> scalpel' at some stage or another. However, I tend to DM> 'follow the book' very closely, as to expose DM> 'userland', because sometimes that's a useful strategy. DM> So we see here...the configuration switch DM> '--enable-debug' (which is part of the current svn DM> build instructions anyhow), and the quick gdb primer of DM> how to obtain useful debugging information to help DM> developers out here. DM> DM> I think somehow that for as long as a debug build is the DM> default build, these brief gdb instructions would be DM> quite pertinent for users to read somewhere on the DM> website. Test builders are a valuable resource, and so DM> I believe it might useful to include such documentation DM> on the site so users who do build jazz++ can quickly and DM> easily supply (and know how to create) useful information DM> if they find their jazz++ build crashes. If nothing else, DM> it'll save having to spell that backtrace passage out, DM> over and over again. Remember, everyone building from svn DM> is effectively a test builder at present. DM> DM> Let me know what we think here - if it sounds like a good DM> idea and we agree, I'll edit the htdocs in some appropriate DM> spot to include such instructions. I added a web directory (bugreport) and put an index.php in it for you to edit. Have at it. Pete |
From: Pete S. <pst...@gm...> - 2008-05-14 04:38:25
|
DM = D.B. Moore DM> Yep, no problem.... the back trace without vkeybd DM> running but with jack/fluidsynth/qsynth running DM> and ready to go (complete session); <Snip> > Program received signal SIGSEGV, Segmentation fault. > [Switching to Thread 140090596853472 (LWP 3341)] > snd_seq_port_subscribe_set_sender (info=0x7fff6a45d310, addr=0x0) at seq.c:2432 > 2432 memcpy(&info->sender, addr, sizeof(*addr)); > Current language: auto; currently c > > (gdb) bt > #0 snd_seq_port_subscribe_set_sender (info=0x7fff6a45d310, addr=0x0) > at seq.c:2432 > #1 0x0000000000426a59 in tAlsaPlayer::subscribe_inp (this=0xb68020, inp=0) > at ../../jazz/src/AlsaPlayer.cpp:219 My current guess is an invalid input or output device index. Could you update you source tree, rebuild, run again and let me know how it goes? Thanks, Pete |
From: D.B. M. <db...@ho...> - 2008-05-14 03:04:02
|
Greetings, As I scour the 'net looking for pertinent documentation resources, I'm coming across references to jazz++ that point back to the old jazzware website. This is unfortunate - quip; Unable to determine IP address from host name for www.jazzware.com One such document, is the 'Linux MIDI HowTo' but there are others. My question is, do we wish to email such documents' authors, kindly requesting them to update their links?? I primarily ask this because of jazz++'s early development stage..ie; if there were fully functional tarballs available of any kind for jazz++ now, I wouldn't ask - I'd just send the emails to the authors concerned and report that action here. Let me know, as it's fairly easy (and convenient) for me to include such tasks in my current activities here.... Regards, Donald B _________________________________________________________________ Never miss another e-mail with Hotmail on your mobile. http://www.livelife.ninemsn.com.au/article.aspx?id=343869 |
From: Robert V. <vo...@ct...> - 2008-05-14 00:50:25
|
I tried compiling Jazz++ on my Debian Etch stable system. It looked ok throughout the build process, and it produced an executable. When I tried opening the executable, it didn't prompt for a configuration file, but it found one in my home directory. I'm not sure it is the correct jazz.cfg though. (attached) When I execute from the TestInstall it does open a window and a midi file is visible there. It doesn't play though. It only makes a few low cello-like sounds...about the first two bars... and then the curser stops and advances no further. In another window I have an alsaconnect gui...which does not actually see jazz++. Jack doesn't know about it. I connect my Yamaha ES8 keyboard to a UX16 usb connector which is configured with alsaconnectgui. Usually I can use the keyboard to connect with a software synth or I can use Rosegarden to drive using the alsa connectivity. Anyway Jazz++ doesn't appear to be recognized by alsa. It doesn't show up in the alsaconnect gui. Rosegarden complains every time I start it that the 'system timer resolution is too low'. I know I need to find a RT kernel, but I've been too cautious to try one yet. Soon. That's why I need to be able to connect to an external device or to a soft synth. Here are results for the menus. The 'preferences' on the file menu looks to be a stub. I didn't get far enough along to try the edit functions. The metronome causes an immediate segmentation fault and a hard crash. The Jazz++ harmony window looks nice. If I right click on the various chord buttons they play the actual chords with a guitar-like sound. I have Jazz++ set up as a GM synth. I can see the ux16 and click on it, but it doesn't do anything. The audio menu seems to be all stubs. Is that right ? Help menus are unpopulated. Probably I missed the 'make' command for the documentation (?) I'm attaching the config.log for your consideration. |
From: D.B. M. <db...@ho...> - 2008-05-14 00:37:13
|
Greetings, ---------------------------------------- > Date: Tue, 13 May 2008 16:23:08 -0700 > > Subject: Re: [jazzplusplus-devel] configure.ac update -please test- > > PS = Pete Stieber > PS> I think I finally have configure.ac setup to build > PS> on a Mac and a Linux box with ALSA. I tested the > PS> Mac build with the current svn repository and it > PS> works on my Max mini. > > I just tested the current svn on a Fedora 8 box (kernel is SMP, x86_64 > version of 2.6.24.5-85.fc8). If I start jackd using qjackctl, then > start fluidsynth using qsynth, hook things up correctly, then start the > jazz binary, I am presented with the following options for output... > > Midi Through Midi Through Port-0 > Client-128 qjackctl > FLUID Synth (7569) Synth port input (7569:0) > > 7569 is the process ID for qsynth. If I select the last option, I can > here the loaded MIDI file when I hit play. > This is very much exactly the same setup sequence I followed here... > I loaded the following packages using yum to get all of this working. > > qjackctl-0.3.1a-5.fc8.x86_64 > jack-audio-connection-kit-0.103.0-5.fc8.x86_64 > qsynth-0.2.5-6.fc6.x86_64 > fluidsynth-libs-1.0.7-10.a.fc8.x86_64 > PersonalCopy-Lite-soundfont-4.1-3.fc8.noarch > ....I would need check my exact version of these things installed here for comparison - let me know if you want such. > Donald, I realize that you are having a problem with this. I'll try to > help you out by replying to your post as time permits. > Problems? Gee, I thought I was having fun!! ;-) Regards, Donald B _________________________________________________________________ Search for local singles online @ Lavalife - Click here http://a.ninemsn.com.au/b.aspx?URL=http%3A%2F%2Flavalife9%2Eninemsn%2Ecom%2Eau%2Fclickthru%2Fclickthru%2Eact%3Fid%3Dninemsn%26context%3Dan99%26locale%3Den%5FAU%26a%3D30290&_t=764581033&_r=email_taglines_Search_OCT07&_m=EXT |
From: D.B. M. <db...@ho...> - 2008-05-14 00:20:34
|
---------------------------------------- > Date: Tue, 13 May 2008 05:41:08 +0000 > Subject: Re: [jazzplusplus-devel] configure.ac update -please test- > >>> >> When you are debugging add --enable-debug to your configure line. >> >> After you finish the build, run the code using gdb... >> >> gdb jazz >> >> Then type "run" when you get a prompt. When the code crashes, generate >> a back trace using the "bt" command. Full gdb documentation can be >> found at http://sourceware.org/gdb/current/onlinedocs/gdb_toc.html >> >> Reply back with the result of the back trace. >> I actually know about gdb, backtraces and so forth. I doubt one could build a Free software based systems for as long as I have without needing this 'software scalpel' at some stage or another. However, I tend to 'follow the book' very closely, as to expose 'userland', because sometimes that's a useful strategy. So we see here...the configuration switch '--enable-debug' (which is part of the current svn build instructions anyhow), and the quick gdb primer of how to obtain useful debugging information to help developers out here. I think somehow that for as long as a debug build is the default build, these brief gdb instructions would be quite pertinent for users to read somewhere on the website. Test builders are a valuable resource, and so I believe it might useful to include such documentation on the site so users who do build jazz++ can quickly and easily supply (and know how to create) useful information if they find their jazz++ build crashes. If nothing else, it'll save having to spell that backtrace passage out, over and over again. Remember, everyone building from svn is effectively a test builder at present. Let me know what we think here - if it sounds like a good idea and we agree, I'll edit the htdocs in some appropriate spot to include such instructions. >> It will be a while before I get to it. Maybe not until this weekend. >> >> Pete >> > > Yep, no problem.... the back trace without vkeybd running but with > jack/fluidsynth/qsynth running and ready to go (complete session); > > (gdb) run > Starting program: /root/Jazz++/TestInstall/bin/jazz > Failed to read a valid object file image from memory. > [Thread debugging using libthread_db enabled] > [New Thread 140090596853472 (LWP 3341)] > JZProject::ReadConfiguration() ConfFileNameAndPath: > "/root/Jazz++/TestInstall/share/Jazz++/jazz.cfg" > JZConfiguration::LoadConfig: > "/root/Jazz++/TestInstall/share/Jazz++/jazz.cfg" > Include synthesizer configuration file "gs.jzi" > FindFile: Immediate hit on file "gs.jzi" > Include file "gsdrmset.jzi" > FindFile: Immediate hit on file "gsdrmset.jzi" > Include file "gmdrmnam.jzi" > FindFile: Immediate hit on file "gmdrmnam.jzi" > Include file "gsvoices.jzi" > FindFile: Immediate hit on file "gsvoices.jzi" > Include file "ctrlnam.jzi" > FindFile: Immediate hit on file "ctrlnam.jzi" > created client:port = 131:0 > invalid output device, so selecting one > Program received signal SIGSEGV, Segmentation fault. > [Switching to Thread 140090596853472 (LWP 3341)] > snd_seq_port_subscribe_set_sender (info=0x7fff6a45d310, addr=0x0) at seq.c:2432 > 2432 memcpy(&info->sender, addr, sizeof(*addr)); > Current language: auto; currently c > > (gdb) bt > #0 snd_seq_port_subscribe_set_sender (info=0x7fff6a45d310, addr=0x0) > at seq.c:2432 > #1 0x0000000000426a59 in tAlsaPlayer::subscribe_inp (this=0xb68020, inp=0) > at ../../jazz/src/AlsaPlayer.cpp:219 > #2 0x0000000000427793 in tAlsaPlayer (this=0xb68020, song=0x7f69623ea010) > at ../../jazz/src/AlsaPlayer.cpp:122 > #3 0x0000000000423638 in tAlsaAudioPlayer (this=0xb68020, > pSong=0x7f69623ea010) at ../../jazz/src/AlsaDriver.cpp:127 > #4 0x00000000004b9ed2 in JZProject (this=0x7f69623ea010) > at ../../jazz/src/Project.cpp:194 > #5 0x0000000000498948 in JZJazzPlusPlusApplication::OnInit (this=0xafe690) > at ../../jazz/src/JazzPlusPlusApplication.cpp:127 > #6 0x0000000000498d96 in wxAppConsole::CallOnInit (this=0xafe690) > at /usr/local/wx287/include/wx-2.8/wx/app.h:76 > #7 0x000000000079a70a in wxEntry () > #8 0x0000000000498d10 in main (argc=1, argv=0x7fff6a45dc68) > at ../../jazz/src/JazzPlusPlusApplication.cpp:63 > Just a further note on this -- as I mentioned in a previous posting, I'm keen to test out and document jazz++'s interoperability and setup with other midi based applications on linux. Last night, I got around to trying the AlsaModularSynth (AMS) application with jazz++. To use AMS without a hardware midi/synth soundcard, relies on a very similar setup to jack/fluidsynth/qsynth. One starts AMS with the --jack cmdline option, and when jazz++ is started and prompts for an output device, the user selects the AMS output device entry. Yes...it works, and curiously enough it never once spawned the above crash in a two hour session of me mucking around with things, stopping and restarting things...I could not seemingly reproduce this error above using jack/AMS and jazz++ at all. Nor did it ever steal my mouse and keyboard I hasten to add -- everything behaved itself. I'm no coder, but I thought I'd mention this here, just in case there's more to the above error than immediately meets the eye. Regards, Donald B > > > Hope this helps put some light on the issue. > > > Regards, > > Donald B > _________________________________________________________________ > Search for local singles online @ Lavalife - Click here > http://a.ninemsn.com.au/b.aspx?URL=http%3A%2F%2Flavalife9%2Eninemsn%2Ecom%2Eau%2Fclickthru%2Fclickthru%2Eact%3Fid%3Dninemsn%26context%3Dan99%26locale%3Den%5FAU%26a%3D30290&_t=764581033&_r=email_taglines_Search_OCT07&_m=EXT > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > jazzplusplus-devel mailing list > jaz...@li... > https://lists.sourceforge.net/lists/listinfo/jazzplusplus-devel _________________________________________________________________ Are you paid what you're worth? Find out: SEEK Salary Centre http://a.ninemsn.com.au/b.aspx?URL=http%3A%2F%2Fninemsn%2Eseek%2Ecom%2Eau%2Fcareer%2Dresources%2Fsalary%2Dcentre%2F%3Ftracking%3Dsk%3Ahet%3Asc%3Anine%3A0%3Ahot%3Atext&_t=764565661&_r=OCT07_endtext_salary&_m=EXT |
From: Pete S. <pst...@ve...> - 2008-05-13 23:23:36
|
PS = Pete Stieber PS> I think I finally have configure.ac setup to build PS> on a Mac and a Linux box with ALSA. I tested the PS> Mac build with the current svn repository and it PS> works on my Max mini. I just tested the current svn on a Fedora 8 box (kernel is SMP, x86_64 version of 2.6.24.5-85.fc8). If I start jackd using qjackctl, then start fluidsynth using qsynth, hook things up correctly, then start the jazz binary, I am presented with the following options for output... Midi Through Midi Through Port-0 Client-128 qjackctl FLUID Synth (7569) Synth port input (7569:0) 7569 is the process ID for qsynth. If I select the last option, I can here the loaded MIDI file when I hit play. I loaded the following packages using yum to get all of this working. qjackctl-0.3.1a-5.fc8.x86_64 jack-audio-connection-kit-0.103.0-5.fc8.x86_64 qsynth-0.2.5-6.fc6.x86_64 fluidsynth-libs-1.0.7-10.a.fc8.x86_64 PersonalCopy-Lite-soundfont-4.1-3.fc8.noarch Donald, I realize that you are having a problem with this. I'll try to help you out by replying to your post as time permits. Pete |
From: Pete S. <pst...@gm...> - 2008-05-13 14:44:13
|
DM = D.B. Moore wrote: DM> This patch corrects (hopefully) all outstanding typos, DM> spelling, and other grammatical issues in the content DM> of the following; DM> DM> web/htdocs/buildingwx/index.php DM> web/htdocs/buildingjazz/index.php Applied and moved up to the web site. Thanks Donald, Pete |
From: D.B. M. <db...@ho...> - 2008-05-13 05:41:16
|
---------------------------------------- > Date: Mon, 12 May 2008 21:48:25 -0700 > DM = D.B. Moore > DM> Just confirming that this type of error; > DM> > DM> jazz[3247]: segfault at 0 ip 7fa62e0e1b49 sp 7fff379157d0 error 4 in > libasound.so.2.0.0[7fa62e04b000+d1000] > DM> > DM> is actually emitted when jazz cannot seemingly > DM> find a valid input device, ie; I didn't have > DM> vkeybd running. Previous (elusive) reports of > DM> this I posted, were apparently related to me > DM> changing things in the qsynth connection panel > DM> 'on the fly'....sorry if that created any confusion. > DM> > DM> I did update my alsalib btw, but such made no > DM> difference here. > > Donald, > > When you are debugging add --enable-debug to your configure line. > > After you finish the build, run the code using gdb... > > gdb jazz > > Then type "run" when you get a prompt. When the code crashes, generate > a back trace using the "bt" command. Full gdb documentation can be > found at http://sourceware.org/gdb/current/onlinedocs/gdb_toc.html > > Reply back with the result of the back trace. > > It will be a while before I get to it. Maybe not until this weekend. > > Pete > Yep, no problem.... the back trace without vkeybd running but with jack/fluidsynth/qsynth running and ready to go (complete session); (gdb) run Starting program: /root/Jazz++/TestInstall/bin/jazz Failed to read a valid object file image from memory. [Thread debugging using libthread_db enabled] [New Thread 140090596853472 (LWP 3341)] JZProject::ReadConfiguration() ConfFileNameAndPath: "/root/Jazz++/TestInstall/share/Jazz++/jazz.cfg" JZConfiguration::LoadConfig: "/root/Jazz++/TestInstall/share/Jazz++/jazz.cfg" Include synthesizer configuration file "gs.jzi" FindFile: Immediate hit on file "gs.jzi" Include file "gsdrmset.jzi" FindFile: Immediate hit on file "gsdrmset.jzi" Include file "gmdrmnam.jzi" FindFile: Immediate hit on file "gmdrmnam.jzi" Include file "gsvoices.jzi" FindFile: Immediate hit on file "gsvoices.jzi" Include file "ctrlnam.jzi" FindFile: Immediate hit on file "ctrlnam.jzi" created client:port = 131:0 invalid output device, so selecting one Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 140090596853472 (LWP 3341)] snd_seq_port_subscribe_set_sender (info=0x7fff6a45d310, addr=0x0) at seq.c:2432 2432 memcpy(&info->sender, addr, sizeof(*addr)); Current language: auto; currently c (gdb) bt #0 snd_seq_port_subscribe_set_sender (info=0x7fff6a45d310, addr=0x0) at seq.c:2432 #1 0x0000000000426a59 in tAlsaPlayer::subscribe_inp (this=0xb68020, inp=0) at ../../jazz/src/AlsaPlayer.cpp:219 #2 0x0000000000427793 in tAlsaPlayer (this=0xb68020, song=0x7f69623ea010) at ../../jazz/src/AlsaPlayer.cpp:122 #3 0x0000000000423638 in tAlsaAudioPlayer (this=0xb68020, pSong=0x7f69623ea010) at ../../jazz/src/AlsaDriver.cpp:127 #4 0x00000000004b9ed2 in JZProject (this=0x7f69623ea010) at ../../jazz/src/Project.cpp:194 #5 0x0000000000498948 in JZJazzPlusPlusApplication::OnInit (this=0xafe690) at ../../jazz/src/JazzPlusPlusApplication.cpp:127 #6 0x0000000000498d96 in wxAppConsole::CallOnInit (this=0xafe690) at /usr/local/wx287/include/wx-2.8/wx/app.h:76 #7 0x000000000079a70a in wxEntry () #8 0x0000000000498d10 in main (argc=1, argv=0x7fff6a45dc68) at ../../jazz/src/JazzPlusPlusApplication.cpp:63 Hope this helps put some light on the issue. Regards, Donald B _________________________________________________________________ Search for local singles online @ Lavalife - Click here http://a.ninemsn.com.au/b.aspx?URL=http%3A%2F%2Flavalife9%2Eninemsn%2Ecom%2Eau%2Fclickthru%2Fclickthru%2Eact%3Fid%3Dninemsn%26context%3Dan99%26locale%3Den%5FAU%26a%3D30290&_t=764581033&_r=email_taglines_Search_OCT07&_m=EXT |
From: D.B. M. <db...@ho...> - 2008-05-13 05:03:47
|
Greetings, This patch corrects (hopefully) all outstanding typos, spelling, and other grammatical issues in the content of the following; web/htdocs/buildingwx/index.php web/htdocs/buildingjazz/index.php Apart from simple corrections, some wording has been slightly changed/rearranged to facilitate paragraph formatting. These are the only deviations from the content of the original texts at this time. See attached:- htdocs-20080513-fixups.patch.gz TODO: Mac OSX building instructions (awaiting input from Mac users) Regards, Donald B _________________________________________________________________ Search for local singles online @ Lavalife - Click here http://a.ninemsn.com.au/b.aspx?URL=http%3A%2F%2Flavalife9%2Eninemsn%2Ecom%2Eau%2Fclickthru%2Fclickthru%2Eact%3Fid%3Dninemsn%26context%3Dan99%26locale%3Den%5FAU%26a%3D30290&_t=764581033&_r=email_taglines_Search_OCT07&_m=EXT |
From: Pete S. <pst...@gm...> - 2008-05-13 04:48:29
|
DM = D.B. Moore DM> Just confirming that this type of error; DM> DM> jazz[3247]: segfault at 0 ip 7fa62e0e1b49 sp 7fff379157d0 error 4 in libasound.so.2.0.0[7fa62e04b000+d1000] DM> DM> is actually emitted when jazz cannot seemingly DM> find a valid input device, ie; I didn't have DM> vkeybd running. Previous (elusive) reports of DM> this I posted, were apparently related to me DM> changing things in the qsynth connection panel DM> 'on the fly'....sorry if that created any confusion. DM> DM> I did update my alsalib btw, but such made no DM> difference here. Donald, When you are debugging add --enable-debug to your configure line. After you finish the build, run the code using gdb... gdb jazz Then type "run" when you get a prompt. When the code crashes, generate a back trace using the "bt" command. Full gdb documentation can be found at http://sourceware.org/gdb/current/onlinedocs/gdb_toc.html Reply back with the result of the back trace. It will be a while before I get to it. Maybe not until this weekend. Pete |
From: D.B. M. <db...@ho...> - 2008-05-13 04:38:39
|
>> Date: Mon, 12 May 2008 09:40:48 -0700 >> Subject: Re: [jazzplusplus-devel] configure.ac update -please test- >> >> >> On 10 May 2008 at 12:31, Pete Stieber wrote: >> Just confirming that this type of error; jazz[3247]: segfault at 0 ip 7fa62e0e1b49 sp 7fff379157d0 error 4 in libasound.so.2.0.0[7fa62e04b000+d1000] is actually emitted when jazz cannot seemingly find a valid input device, ie; I didn't have vkeybd running. Previous (elusive) reports of this I posted, were apparently related to me changing things in the qsynth connection panel 'on the fly'....sorry if that created any confusion. I did update my alsalib btw, but such made no difference here. Regards, Donald B _________________________________________________________________ Search for local singles online @ Lavalife - Click here http://a.ninemsn.com.au/b.aspx?URL=http%3A%2F%2Flavalife9%2Eninemsn%2Ecom%2Eau%2Fclickthru%2Fclickthru%2Eact%3Fid%3Dninemsn%26context%3Dan99%26locale%3Den%5FAU%26a%3D30290&_t=764581033&_r=email_taglines_Search_OCT07&_m=EXT |
From: Pete S. <pst...@gm...> - 2008-05-13 04:35:26
|
DM = D.B. Moore wrote: DM> I'm just wandering through the (website) documentation DM> fixing things, and my lack of experience with Mac OSX DM> has just forced me here. DM> DM> In the 'buildingjazz++' documentation, a section DM> describing the linux build goes like this ; DM> DM> The prefix option is used so that the make install step DM> found later in these instructions, will not require root DM> privileges. It is also useful to run make install with DM> this prefix option, so that the resulting install will DM> create a copy of the jazz.cfg file that is independent DM> of the one distributed in the source tree. The DM> configuration file is modified by the Jazz++ binary. If DM> the version of the jazz.cfg file in your svn working DM> directory was altered, this could lead to update conflicts DM> when updating the code using Subversion. This may lead to DM> problems using Jazz++ as a result. DM> DM> The equivalent section in the Mac OSX instructions reads; DM> DM> The prefix option is used so that the resulting install DM> will not use the jazz.cfg file from the svn repository. DM> The configuration file is modified by the Jazz++ binary. DM> If the version in your svn working directory was altered, DM> this could lead to update conflicts when updating the DM> code. This may lead to problems using Jazz++. DM> Obviously they are quite different. My question is, are DM> the Mac OSX instructions here actually correct, or DM> should they be more akin to the linux instructions instead? I wrote them, and they work, but there are extra steps required to generate an application on Mac OS X, and I haven't had time to learn all of the details. Leland, Can you help Donald and I out by explaining the process and maybe pointing out how you go about this in the Midible branch. Donald might even be able to help document the existence of this branch in the Jazz++ web content. Donald, Go ahead and leave the Mac instructions as they are, and create a patch for the fixes you have made to the rest of the page. TIA, Pete |
From: D.B. M. <db...@ho...> - 2008-05-13 00:55:02
|
> Date: Mon, 12 May 2008 09:40:48 -0700 > Subject: Re: [jazzplusplus-devel] configure.ac update -please test- > > > On 10 May 2008 at 12:31, Pete Stieber wrote: > >> Donald and Kevin, could I get you to try the Linux build and make sure >> the jack/flsynth/qsynth is working. I don't have access to a Linux >> setup at the moment and that would really help me out. ..for some reason I didn't receive this original posting - thankfully Kevin responded to it and I was able to pick up the thread.... > > >> BTW I always seem to have a heck of a time with Mandriva. Jazz++ can >> hang it, it doesn't want to recognize my keyboard... Curious...I hadn't noticed that here myself with my initial builds, however subsequent to this call for testing....yes..there's something strange going on with input devices on linux. Here's the detail.... My svn source version here is current at rev. 518 Distcleaned my local svn, rebuilt the source and installed (completes successfully) The build-log is attached just in case there's something to see in it. Started up jack/fluidsynth/qsynth as previously configured and tested okay. Launching jazz almost immediately caused a segfault.... jazz[3277]: segfault at 1 ip 424c82 sp 7fffe79bf840 error 4 in jazz[400000+573000] jazz[3287]: segfault at 1 ip 424c82 sp 7fff0dd7b040 error 4 in jazz[400000+573000] jazz[3288]: segfault at 1 ip 424c82 sp 7fff0af091d0 error 4 in jazz[400000+573000] jazz[3299]: segfault at 1 ip 424c82 sp 7fff5cf1c1f0 error 4 in jazz[400000+573000] jazz[3300]: segfault at 1 ip 424c82 sp 7fff12a95d60 error 4 in jazz[400000+573000] jazz[3301]: segfault at 1 ip 424c82 sp 7fff8092bbf0 error 4 in jazz[400000+573000] This is me (re)starting jazz half-a-dozen times looking for clues. On the 7th attempt ; jazz[3310]: segfault at 1 ip 426cea sp 7fff8e2aa1e0 error 4 in jazz[400000+5ad000] That last one 'stole' both my mouse&keyboard completely, and left me with no X input. The system was still running though, so I moved to one of my other boxes, and ssh'd into this system to see if there were any clues...unfortunately and AFAICT there were no clues or errors to seen...in fact, everything looked fine...just X had lost input. One of the last things I saw in console that launched jazz leading up to this was ; "Invalid input device" I believe I might have recovered the situation with an simple X restart, however I decided to reboot the system to be sure of a 'clean slate'. Taking Pete's obtrusion about mouse&keyboard weirdness into account, and on a hunch thinking 'invalid input device' might be somehow related, I decided on a different approach... I downloaded Takashi Iwai's 'vkeybd' source, compiled & installed. I then started this virtual midi keyboard and check it registered in alsa midi devices -- it does, along with jack/fluidsynth/qsynth. I then restarted jazz to discover things were actually sane again. It prompted me for input device (I of course chose the vkeybd client), and output device (selected qsynth)....hey presto, it's all working again as currently expected..well...caveat ; subscribe: Operation not permitted I see this in dmesg when jazz finishes configuration dialogs and starts. Occasionally; jazz[3458]: segfault at 0 ip 7f606dd1dd39 sp 7fff77552410 error 4 in libasound.so.2.0.0[7f606dc87000+d2000] is seen in dmesg -- I'm still trying to accurately recreate this one to find the cause, but it's being elusive... I hope this helps some -- anything else/specific you want to know? >Kevin C wote; > > Hmmm. I wonder what would happen with a Linus kernel on Mandriva? > Just for the record, this account of proceedings here was using linux 2.6.25.3 I think my next move here is to double-check my alsalib installation - it's been a while since I checked what's current. Regards, Donald B _________________________________________________________________ It's simple! Sell your car for just $30 at CarPoint.com.au http://a.ninemsn.com.au/b.aspx?URL=http%3A%2F%2Fsecure%2Dau%2Eimrworldwide%2Ecom%2Fcgi%2Dbin%2Fa%2Fci%5F450304%2Fet%5F2%2Fcg%5F801459%2Fpi%5F1004813%2Fai%5F859641&_t=762955845&_r=tig_OCT07&_m=EXT |
From: Kevin C. <ke...@co...> - 2008-05-12 17:09:54
|
On 11 May 2008 at 21:38, Pete Stieber <pst...@gm...> wrote: > I do like tex2rtf's capabilities, and I do want to use it for online > HTML help. What do you all think? So long as there are instructions on where to get it and how to build it, then it seems like a good plan to me. Thx.... -- Kevin |