Menu
▾
▴
linuxsampler-devel
|
From: Christian S. <sch...@li...> - 2014-02-07 15:00:18
Attachments:
lscp_termsync.patch
|
On Friday 07 February 2014 08:54:53 Patrick Shirkey wrote: > It compiles fine for me on debian-7.0 64bit. However it crashes on start > and I get this backtrace: Does the attached patch fix it? CU Christian |
|
From: Christian S. <sch...@li...> - 2014-02-08 17:08:27
|
On Saturday 08 February 2014 15:23:17 raf wrote: > the sampler engine is running ok, but strangely the lscp shell complains > that the engine is too old, although they have just been compiled together > from the latest svn version... > > LinuxSampler 1.0.0.svn23 That version is from 2013 by the way. Definitely not the latest svn version. Have a look at the SVN log on the linuxsampler.org front page. You see the respective version for each commit there. Latest version is 1.0.0.svn31. CU Christian |
|
From: raf <rmo...@gm...> - 2014-02-08 17:46:11
|
> On Saturday 08 February 2014 15:23:17 raf wrote: >> the sampler engine is running ok, but strangely the lscp shell complains >> that the engine is too old, although they have just been compiled together >> from the latest svn version... >> >> LinuxSampler 1.0.0.svn23 > > That version is from 2013 by the way. Definitely not the latest svn version. > Have a look at the SVN log on the linuxsampler.org front page. You see the > respective version for each commit there. Latest version is 1.0.0.svn31. oups, you are absolutely right, the package manager didn't correctly remove the previous version... So this is all working now ! I apreciate : the colors, return message and error messages, the auto-upper case on commands, command history some enhancement for the future ? after you've gone into command history with the up arrow, you cannot come back to a blank line when you're in a command history, you have to use the delete key, you cannot use the left arrow to change some parameter on a long line. While this would be great, i'm sure it's not compatible with how the auto-completion is handled. autocompletion on command parameters display a list of available commands/sub-commands on double-tab (depending on what has previously been greened) a strange thing : lscp=# CREATE AUDIO_OUTPUT_DEVICE JACK ACTIVE=TRUE CHANNELS=2 SAMPLERATE=48000 NAME="linuxsampler"libjackBufferSizeCallback(128) after firing up this command, the libjackBufferSizeCallback(128) is added at the end. This lscp shell promises to be very useful, thank you for this great tool ! Raphaël |
|
From: Christian S. <sch...@li...> - 2014-02-08 19:24:20
|
On Saturday 08 February 2014 18:46:02 raf wrote: > some enhancement for the future ? > after you've gone into command history with the up arrow, you cannot come > back to a blank line when you're in a command history, you have to use the > delete key, you cannot use the left arrow to change some parameter on a > long line. While this would be great, i'm sure it's not compatible with > how the auto-completion is handled. autocompletion on command parameters > display a list of available commands/sub-commands on double-tab (depending > on what has previously been greened) Sure! That and more is planned. That's just a starting point for the LSCP shell for now. Not more, not less. The trickiest part was dealing with the auto generated Bison tables and the LALR(1) algorithm on top of them. But that is done now and I think the other shell features can easily be added. Those should neither be difficult nor should they take much effort. But as said, I have to work on other things for a while now. > a strange thing : > lscp=# CREATE AUDIO_OUTPUT_DEVICE JACK ACTIVE=TRUE CHANNELS=2 > SAMPLERATE=48000 NAME="linuxsampler"libjackBufferSizeCallback(128) after > firing up this command, the libjackBufferSizeCallback(128) is added at the > end. Since I couldn't reproduce this with the same command, and since I currently don't see why this should have been generated by the sampler's LSCP parser, my guess is that you compiled either JACK or the sampler with debug messages turned on, causing "libjackBufferSizeCallback(128)" to be printed on the currently active terminal when the sampler instantiates the JACK driver. CU Christian |
|
From: Christian S. <sch...@li...> - 2014-03-21 12:16:53
Attachments:
lscp_shell_1_0_0_svn37.jpg
|
On Friday 21 March 2014 10:52:41 Raphaël Mouneyres wrote: > hello, > > i've been using the LSCP shell yesterday, and it has been of a great > help, especially the command history. The LSCP shell is still work in progress. I made some progress, my planned basic features are roughly done, but I had so far no time to finish it up. There are still some minor issues to be solved. But right now I have no time for spare time projects. > >when you're in a command history, you have to use the delete key, you > >cannot use the left arrow to change some parameter on a long line. Moving the cursor position with left/right key is actually implemented in latest SVN version. Are you using the latest one (1.0.0.svn37)? > >autocompletion on command parameters display a list of available > >commands/sub-commands on double-tab (depending on what has previously > >been greened) > > as a first shot, you could display the message that is printed when > you enter an incomplete command "....expecting.....should be....." I implemented that somewhat different than other shells do: there is no need for double tab. The next token(s) are automatically shown next to your command line in different color, showing you immediately all possibilities you have while typing, without requiring you to trigger any special key (see attached screen shot). It not only lists you keywords, but also so called "non terminals" like "number", "digit" which may be required to for the current command line position, for example for "GET CHANNEL INFO <number>". Plus in latest SVN version, the relevant LSCP reference document section is automatically displayed below the command line, as soon as it is obvious which LSCP command you mean. It shows you the general syntax of the LSCP command you are currently typing, plus detailed descriptions about that specific LSCP command. However the following issues have yet to be solved for this particular feature: 1. The document section is not displayed 100% correctly. For example sometimes there is no gap between two words, and some HTML encoding of the source document (lscp.xml) is not yet transformed into normal ASCII text. 2. There is a bug, that sometimes causes the encoded document info sent by the LSCP server to be displayed by the LSCP shell directly on screen, as it was a regular response to a command the user types. 3. The document section shall actually only be displayed partly, for example it should not cover more than 25% of the current terminal height or something, if it would cover more it should be cutted and instead be scrollable with some keys, i.e. page up and page down keys. However I am not yet sure about the keys, because a Mac for example does not have page up/down keys. Preferably keys shall be defined that exist on all major systems. CU Christian |
|
From: Raphaël M. <rmo...@gm...> - 2014-03-21 13:07:32
|
> I made some progress, my planned basic features are roughly done, but I had so > far no time to finish it up. There are still some minor issues to be solved. > But right now I have no time for spare time projects. sure, i let you do it at your speed as i can not contribute to the code, but only to give some user feedback > Moving the cursor position with left/right key is actually implemented in > latest SVN version. Are you using the latest one (1.0.0.svn37)? once again, no, i hadn't updated, i'm not checking the repository that often. > I implemented that somewhat different than other shells do: there is no need > for double tab. The next token(s) are automatically shown next to your command > line in different color, showing you immediately all possibilities you have that is a good implementation ! thanks for the updated infos. In the future, would you post a quick changelog to the list when the svn is updated, or is there another way to be automatically informed when something new has been submited to the repository ? Raphaël |
|
From: Christian S. <sch...@li...> - 2014-03-21 14:54:14
|
On Friday 21 March 2014 14:07:23 you wrote: > thanks for the updated infos. > In the future, would you post a quick changelog to the list when the > svn is updated, or is there another way to be automatically informed > when something new has been submited to the repository ? Hmm... not sure about that. The jack-devel mailing list recently forwards all commit logs of JACK1 automatically to that mailing list. And I find it very annoying. So from that experience I rather don't want to forward commit change logs automatically to this list. We might establish a separate email list dedicated for commit logs and/or RSS feed, automatic Twitter tweets ... CU Christian |
|
From: raf <rmo...@gm...> - 2014-03-22 18:39:46
|
> On Friday 21 March 2014 14:07:23 you wrote: >> thanks for the updated infos. >> In the future, would you post a quick changelog to the list when the >> svn is updated, or is there another way to be automatically informed >> when something new has been submited to the repository ? > > Hmm... not sure about that. The jack-devel mailing list recently forwards all > commit logs of JACK1 automatically to that mailing list. And I find it very > annoying. So from that experience I rather don't want to forward commit change > logs automatically to this list. > > We might establish a separate email list dedicated for commit logs and/or RSS > feed, automatic Twitter tweets ... you're right, separating to another medium may be the best option. a RSS feed is easy to add to most email programs without spamming the main inbox. |
|
From: Patrick S. <psh...@bo...> - 2014-02-07 16:24:07
|
On Sat, February 8, 2014 1:01 am, Christian Schoenebeck wrote:
> On Friday 07 February 2014 08:54:53 Patrick Shirkey wrote:
>> It compiles fine for me on debian-7.0 64bit. However it crashes on start
>> and I get this backtrace:
>
> Does the attached patch fix it?
>
Moves it slightly but looks to be the same error. I'm running lscp on a
headless machine via ssh terminal in case that has any influence.
Reading symbols from /usr/bin/lscp...done.
(gdb) run
Starting program: /usr/bin/lscp
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Program received signal SIGSEGV, Segmentation fault.
0x00007ffff749449a in ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
(gdb) bt
#0 0x00007ffff749449a in ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#1 0x0000000000408ade in operator-- (this=<synthetic pointer>) at
/usr/include/c++/4.7/bits/stl_tree.h:203
#2 std::_Rb_tree<void*, std::pair<void* const, int>,
std::_Select1st<std::pair<void* const, int> >, std::less<void*>,
std::allocator<std::pair<void* const, int> > >::_M_insert_unique (
this=this@entry=0x60d420, __v=...) at
/usr/include/c++/4.7/bits/stl_tree.h:1295
#3 0x0000000000408c0b in std::_Rb_tree<void*, std::pair<void* const,
int>, std::_Select1st<std::pair<void* const, int> >, std::less<void*>,
std::allocator<std::pair<void* const, int> > >::_M_insert_unique_
(this=this@entry=0x60d420, __position=..., __v=...) at
/usr/include/c++/4.7/bits/stl_tree.h:1348
#4 0x000000000040812c in insert (__x=..., __position=..., this=0x60d420)
at /usr/include/c++/4.7/bits/stl_map.h:576
#5 operator[] (__k=<optimized out>, this=0x60d420) at
/usr/include/c++/4.7/bits/stl_map.h:458
#6 _newTermios () at TerminalCtrl.cpp:31
#7 TerminalCtrl::now () at TerminalCtrl.cpp:100
#8 0x000000000040a32f in KeyboardReader::KeyboardReader (this=0x60d100)
at KeyboardReader.cpp:16
#9 0x0000000000406caa in __static_initialization_and_destruction_0
(__initialize_p=<optimized out>, __priority=<optimized out>) at
lscp.cpp:31
#10 _GLOBAL__sub_I_main () at lscp.cpp:249
#11 0x000000000040a4ad in __libc_csu_init ()
#12 0x00007ffff69fbe40 in __libc_start_main () from
/lib/x86_64-linux-gnu/libc.so.6
#13 0x0000000000406e31 in _start ()
--
Patrick Shirkey
Boost Hardware Ltd
|
|
From: Christian S. <sch...@li...> - 2014-02-07 17:06:18
Attachments:
lscp_static_init.patch
|
On Friday 07 February 2014 17:25:27 Patrick Shirkey wrote: > On Sat, February 8, 2014 1:01 am, Christian Schoenebeck wrote: > > On Friday 07 February 2014 08:54:53 Patrick Shirkey wrote: > >> It compiles fine for me on debian-7.0 64bit. However it crashes on start > > > >> and I get this backtrace: > > Does the attached patch fix it? > > Moves it slightly but looks to be the same error. I'm running lscp on a > headless machine via ssh terminal in case that has any influence. No, that's irrelevant. It rather seems static variables of the application are initialized in a different order on your machine, but that order can be different on any system. Try the attached patch, it should fix it. CU Christian |
|
From: Patrick S. <psh...@bo...> - 2014-02-07 18:45:04
|
On Sat, February 8, 2014 3:07 am, Christian Schoenebeck wrote: > On Friday 07 February 2014 17:25:27 Patrick Shirkey wrote: >> On Sat, February 8, 2014 1:01 am, Christian Schoenebeck wrote: >> > On Friday 07 February 2014 08:54:53 Patrick Shirkey wrote: >> >> It compiles fine for me on debian-7.0 64bit. However it crashes on >> start >> > >> >> and I get this backtrace: >> > Does the attached patch fix it? >> >> Moves it slightly but looks to be the same error. I'm running lscp on a >> headless machine via ssh terminal in case that has any influence. > > No, that's irrelevant. > > It rather seems static variables of the application are initialized in a > different order on your machine, but that order can be different on any > system. Try the attached patch, it should fix it. > Yep, working now. Thanks. -- Patrick Shirkey Boost Hardware Ltd |
Thanks for helping keep SourceForge clean.
X