|
From: Vladimir S. <ha...@so...> - 2004-03-08 01:21:38
|
jfyi, I was able to get rid of gdb crashes by rebuilding ls with -O0. I have a total of two cores: 1) RESET after failing to load .gig file. (pInstrument was NULL when RenderAudio() was running. My understanding was that RenderAudio() should not have been called since instrument loading failed, so this should be simple to fix) 2) core when running out of voices (i think this started happening after last EG changes, looks like Stream object got corrupted when RenderAudio() was running. pRingBuffer is bad) Both cores are reproducible. I'll look into both of them next weekend, unless you guys happen to figure them out by then. Regards, Vladimir. Vladimir Senkov wrote: > Here is a patch with a few more callbacks: > GetAvailableEngines() > GetEngineInfo() > GetChannelInfo() (except for OUTPUT_CHANNEL and INPUT_CHANNEL) > I've also fixed a bug that i've previously put in --alsa_output > command line processing. > > I've noticed that ls consistenly crashes if: > 1) i try to load a gig and fail (no file found) > 2) i reset the channel > 3) i try to play something on the keyboard. > Unfortunately, i can't open the corefile . . . gdb crashes :( I'll try > to figure this out later. > > I've also noticed that output from GetBufferFill often prints out > empty lines. > > I'll keep looking into implementing other commands. This weekend was > busy and i couldn't do much but hopefully next weekend will be better. > > Regards, > Vladimir. > > > Christian Schoenebeck wrote: > >> Changes: >> >> - Implemented parser for the LinuxSampler control protocol >> (LSCP) by >> using flex / bison (where src/network/lscp.l is the input file >> for lex / >> flex and src/network/lscp.y is the input file for yacc / >> bison). Parser and >> scanner can be regenerated by 'make parser' (only necessary >> though if one >> of the two input files where modified). >> To be honest I'm not quite sure so far if this parser solution >> is a good >> choice, especially because I'm a bit disappointed about it's >> runtime >> efficiency (a main problem is that lexical analyzer and >> semantic analyzer >> are separated which is a big disadvantage for the parser >> generator in >> regards of optimization), but this lex/yacc soultion has the >> advantage >> of defining the protocol on a higher level and is thus easier >> to maintain >> in regards of a growing and possible complex protocol. We'll >> see... >> If somebody's not familiar with lex/yacc, I can give an >> introduction to the >> current LSCP implementation in a short mail if demanded. >> If somebody has a suggestion for another parser generator, let >> me know! >> >> - Implemented LSCP network server (only single threaded so far, >> thus is only >> capable to handle one connection at one time), LSCP server will >> be launched >> if LinuxSampler was started with the new "--server" flag. So far I >> implemented the following LSCP commands: >> >> * "LOAD INSTRUMENT" >> * "GET CHANNEL VOICE_COUNT" >> * "GET CHANNEL STREAM_COUNT" >> * "GET CHANNEL BUFFER_FILL" >> * "SET CHANNEL VOLUME" >> * "RESET CHANNEL" >> >> In src/network/lscpserver.cpp there already all methods which >> will be >> called in case of the respective network command. But most of them >> currently just return a "ERR:0:Not implemented yet" error >> message, so these >> methods need to be "wired" now with the engine and have to >> return a >> meaningful response message. If anybody likes to implement one >> of those >> methods I would appreciate that! (Vladimir perhaps?) >> - disk thread now started within the engine >> >> CU >> Christian >> >> P.S. It's time for a frontend... :) >> >> >> >> ------------------------------------------------------- >> This SF.Net email is sponsored by: IBM Linux Tutorials >> Free Linux tutorial presented by Daniel Robbins, President and CEO of >> GenToo technologies. Learn everything from fundamentals to system >> administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click >> _______________________________________________ >> Linuxsampler-devel mailing list >> Lin...@li... >> https://lists.sourceforge.net/lists/listinfo/linuxsampler-devel >> >> > |