Menu
▾
▴
linuxsampler-devel — This list is for discussing LinuxSampler development issues and ideas
You can subscribe to this list here.
| 2002 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(27) |
Nov
(120) |
Dec
(16) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2003 |
Jan
(65) |
Feb
(2) |
Mar
(53) |
Apr
(15) |
May
|
Jun
(19) |
Jul
(8) |
Aug
(35) |
Sep
(17) |
Oct
(70) |
Nov
(87) |
Dec
(94) |
| 2004 |
Jan
(133) |
Feb
(28) |
Mar
(45) |
Apr
(30) |
May
(113) |
Jun
(132) |
Jul
(33) |
Aug
(29) |
Sep
(26) |
Oct
(11) |
Nov
(21) |
Dec
(60) |
| 2005 |
Jan
(108) |
Feb
(153) |
Mar
(108) |
Apr
(44) |
May
(72) |
Jun
(90) |
Jul
(99) |
Aug
(67) |
Sep
(117) |
Oct
(38) |
Nov
(40) |
Dec
(27) |
| 2006 |
Jan
(16) |
Feb
(18) |
Mar
(21) |
Apr
(71) |
May
(26) |
Jun
(48) |
Jul
(27) |
Aug
(40) |
Sep
(20) |
Oct
(118) |
Nov
(69) |
Dec
(35) |
| 2007 |
Jan
(76) |
Feb
(98) |
Mar
(26) |
Apr
(126) |
May
(94) |
Jun
(46) |
Jul
(9) |
Aug
(89) |
Sep
(18) |
Oct
(27) |
Nov
|
Dec
(49) |
| 2008 |
Jan
(117) |
Feb
(40) |
Mar
(18) |
Apr
(30) |
May
(40) |
Jun
(10) |
Jul
(30) |
Aug
(13) |
Sep
(29) |
Oct
(23) |
Nov
(22) |
Dec
(35) |
| 2009 |
Jan
(19) |
Feb
(39) |
Mar
(17) |
Apr
(2) |
May
(6) |
Jun
(6) |
Jul
(8) |
Aug
(11) |
Sep
(1) |
Oct
(46) |
Nov
(13) |
Dec
(5) |
| 2010 |
Jan
(21) |
Feb
(3) |
Mar
(2) |
Apr
(7) |
May
(1) |
Jun
(26) |
Jul
(3) |
Aug
(10) |
Sep
(13) |
Oct
(35) |
Nov
(10) |
Dec
(17) |
| 2011 |
Jan
(26) |
Feb
(27) |
Mar
(14) |
Apr
(32) |
May
(8) |
Jun
(11) |
Jul
(4) |
Aug
(7) |
Sep
(27) |
Oct
(25) |
Nov
(7) |
Dec
(2) |
| 2012 |
Jan
(20) |
Feb
(17) |
Mar
(59) |
Apr
(31) |
May
|
Jun
(6) |
Jul
(7) |
Aug
(10) |
Sep
(11) |
Oct
(2) |
Nov
(4) |
Dec
(17) |
| 2013 |
Jan
(17) |
Feb
(2) |
Mar
(3) |
Apr
(4) |
May
(8) |
Jun
(3) |
Jul
(2) |
Aug
|
Sep
(3) |
Oct
|
Nov
|
Dec
(1) |
| 2014 |
Jan
(6) |
Feb
(26) |
Mar
(12) |
Apr
(14) |
May
(8) |
Jun
(7) |
Jul
(6) |
Aug
(6) |
Sep
(3) |
Oct
|
Nov
|
Dec
|
| 2015 |
Jan
(9) |
Feb
(5) |
Mar
(4) |
Apr
(9) |
May
(3) |
Jun
(2) |
Jul
(4) |
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
(3) |
| 2016 |
Jan
(2) |
Feb
(4) |
Mar
(5) |
Apr
(4) |
May
(14) |
Jun
(31) |
Jul
(18) |
Aug
|
Sep
(10) |
Oct
(3) |
Nov
|
Dec
|
| 2017 |
Jan
(39) |
Feb
(5) |
Mar
(2) |
Apr
|
May
(52) |
Jun
(11) |
Jul
(36) |
Aug
(1) |
Sep
(7) |
Oct
(4) |
Nov
(10) |
Dec
(8) |
| 2018 |
Jan
(3) |
Feb
(4) |
Mar
|
Apr
(8) |
May
(28) |
Jun
(11) |
Jul
(2) |
Aug
(2) |
Sep
|
Oct
(1) |
Nov
(2) |
Dec
(25) |
| 2019 |
Jan
(12) |
Feb
(50) |
Mar
(14) |
Apr
(3) |
May
(8) |
Jun
(17) |
Jul
(10) |
Aug
(2) |
Sep
(21) |
Oct
(10) |
Nov
|
Dec
(28) |
| 2020 |
Jan
(4) |
Feb
(10) |
Mar
(7) |
Apr
(16) |
May
(10) |
Jun
(7) |
Jul
(2) |
Aug
(5) |
Sep
(3) |
Oct
(3) |
Nov
(2) |
Dec
(1) |
| 2021 |
Jan
|
Feb
(5) |
Mar
(13) |
Apr
(13) |
May
(7) |
Jun
|
Jul
(1) |
Aug
(11) |
Sep
(12) |
Oct
(7) |
Nov
(26) |
Dec
(41) |
| 2022 |
Jan
(23) |
Feb
|
Mar
(8) |
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
(2) |
Sep
|
Oct
(3) |
Nov
(1) |
Dec
(1) |
| 2023 |
Jan
|
Feb
(5) |
Mar
(2) |
Apr
|
May
|
Jun
(1) |
Jul
|
Aug
(11) |
Sep
(5) |
Oct
(1) |
Nov
|
Dec
|
| 2024 |
Jan
(2) |
Feb
(4) |
Mar
(1) |
Apr
(1) |
May
(1) |
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(10) |
Dec
|
| 2025 |
Jan
|
Feb
(4) |
Mar
(1) |
Apr
(2) |
May
|
Jun
(17) |
Jul
(1) |
Aug
(4) |
Sep
(7) |
Oct
(1) |
Nov
(8) |
Dec
|
|
From: Ivan M. <iv...@ma...> - 2018-12-13 21:41:47
|
Hi Christian On 13/12/2018 13:23, Christian Schoenebeck wrote: > You think the USB dongle is the problem? I guess you are just passing through > the USB dongle for direct acess to the Virtualbox guest OS, that works usually > quite well due to its simplicity. Maybe there is rather a problem with the > GSt 4 license server on the Internet. Have you checked which server and port > the installer is trying to reach? The activation for Gigastudio 4 is different to previous versions in that it's completely offline. There is no license server and the applications depend entirely on the presence of an eLicenser with a valid license to launch. The problem I was having is that the old version of the eLicenser software included with Gigastudio 4 can't read my eLicenser anymore. The latest version of the eLicenser software from Steinberg can read my eLicenser but Gigastudio 4 doesn't seem to be able to use this software, probably due to changes to the interfaces of DLLs etc. since 2008. The good news is that I put on my grey hat yesterday evening and now have GSEdit4 running in a VM. As a result I was able to check what the maximum Sample Start Offset is - it's still 2000, it hasn't changed. This can be verified at the bottom of page 166 in the GSEdit4 User Manual available here https://tascam.com/us/product/gigastudio_4/download. I hope to get GStudio4 running soon in a similar way. > Well, chances are that GSt actually never played release triggered samples > when releasing the sustain pedal. That would explain what you are observing > there. Yes, it looks like it could be a GSt3 bug. > What we could do is adding a LS specific file format extension so that anybody > might simply pick his preferred behaviour with LS and probably revert the > default behaviour back to not playing any release samples on sustain up. So a > new option in gigedit like: > > 1. Default (no release trigger samples on sustain up) > 2. Release trigger on sustain up using 127 velocity > 3. Release trigger on sustain up using latest note-on velocity > 4. Release trigger on sustain up using continuous CC64 info ("half pedal" > support). Defaulting to no release trigger samples and giving users the option to change this sounds great. It could also be implemented as a scripting command so that users don't have to modify their gig files. Let me know if I can help with making the changes and many thanks for your time spent on this. > CU > Christian All the best, Ivan > > > _______________________________________________ > Linuxsampler-devel mailing list > Lin...@li... > https://lists.sourceforge.net/lists/listinfo/linuxsampler-devel |
|
From: Christian S. <sch...@li...> - 2018-12-13 13:23:36
|
On Mittwoch, 12. Dezember 2018 14:02:55 CET Ivan Maguidhir wrote:
> I haven't been able to get GSt4 working in a VirtualBox VM with the USB
> licenser passed through from the host so far :-( I'll keep working on
> this to find a solution. I might be able to find out the max start
> position by looking at the instrument editor in a debugger, I'll give
> this a try later today.
You think the USB dongle is the problem? I guess you are just passing through
the USB dongle for direct acess to the Virtualbox guest OS, that works usually
quite well due to its simplicity. Maybe there is rather a problem with the
GSt 4 license server on the Internet. Have you checked which server and port
the installer is trying to reach?
> I should finish it off and publish it. I gave up on it because I could
> never get the audio over Ethernet part of it working. The idea was to be
> enable the use VSTs etc. running on Windows in Linux programs like Ardour.
Yeah, that can be tricky. Sounds like a good candidate for somebody else
trying to add the missing bricks. In general I would not expect low latencies
though.
> > I wait a bit before applying your sustain patch to LS. Let's see what test
> > results you get there with GSt 4 on this issue.
>
> I didn't specify it in earlier emails but the the Sustain Release issue
> applies to GSt3 also. In fact the instrument I mentioned, PMI Emperor,
Well, chances are that GSt actually never played release triggered samples
when releasing the sustain pedal. That would explain what you are observing
there.
What we could do is adding a LS specific file format extension so that anybody
might simply pick his preferred behaviour with LS and probably revert the
default behaviour back to not playing any release samples on sustain up. So a
new option in gigedit like:
1. Default (no release trigger samples on sustain up)
2. Release trigger on sustain up using 127 velocity
3. Release trigger on sustain up using latest note-on velocity
4. Release trigger on sustain up using continuous CC64 info ("half pedal"
support).
CU
Christian
|
|
From: Jaime T <eno...@gm...> - 2018-12-13 09:19:38
|
On Sat, 8 Dec 2018 at 17:34, Ivan Maguidhir <iv...@ma...> wrote: > This was causing me a problem while playing some piano instruments like > PMI Emperor 24-bit where I would hear an unnaturally loud thump and > string noise on releasing the sustain pedal even after playing very softly. I have exactly the same problem with the original Gigapiano. I haven't had a chance to try out your fix yet, but thank you for finding this! (The problem makes linuxsampler unusable with that instrument). |
|
From: Ivan M. <iv...@ma...> - 2018-12-12 14:03:25
|
Hi Christian On 10/12/2018 14:53, Christian Schoenebeck wrote: > On Sonntag, 9. Dezember 2018 19:39:23 CET Ivan Maguidhir wrote: >>> That makes sense. What does gigdump print as global file information for a >>> gig v4 file? >> Here's a link to a zip file containing dumps of all the GSt4 instruments >> mentioned. > I applied your libgig patch to SVN and added gig::File::VERSION_4 as new > version identifier according to your dumps. Thanks! > > I also added a new option to gigedit File->Properties->File Format so that one > could explicitly store with gig v4 file format. That might help when toying > around with new gig v4 features. > Many thanks for doing this and for the mention on the website. >> Find attached a patch that >> prevents the crash by dropping notes. I didn't submit this yesterday as >> it's a bit of a hack and I'm not sure if it's correct. The SONiVOX Synth >> Pads.gig instrument still doesn't produce the sounds it's supposed to >> with this patch. I will try to investigate how GSt4 handles this >> instrument if I can get it running in a VM. > The patch prevents the crash, that's correct, but the root cause seems to be > that your gig file uses a higher sample playback start position than previously > max. allowed and expected by the engine. So obviously even with the patch you > won't be able to play the instrument correctly. > > Probably they raised that playback start position limit in v4. Since you are > one of the very few people still having a working GSt 4 installation, that > might also be valueable to see what maximum playback start position is allowed > in the GSt 4 instrument editor. > > Once we know the max. playback start position in GSt Instr. Editor 4 we can > raise that limit on LS side and that would resolve that issue correctly. I haven't been able to get GSt4 working in a VirtualBox VM with the USB licenser passed through from the host so far :-( I'll keep working on this to find a solution. I might be able to find out the max start position by looking at the instrument editor in a debugger, I'll give this a try later today. >>> Have you compared this behaviour with your GigaStudio 4 software there? Is >>> that what GSt4 does when releasing the sustain pedal? So for instance if >>> you press sustain down, then trigger a key with high velocity, then a 2nd >>> time the same key with low velocity, then release the sustain pedal, >>> would GSt then play a soft release trigger voice? >> Not yet. It's actually years since I've used GSt4. I'm going to try and >> get it working in a Windows XP VM this evening. I wrote a piece of >> software several years ago for sending MIDI from JACK on Linux to a >> driver running in a Windows VM over Ethernet. I hope I can find it >> again. Using this I should be able to test the sustain pedal behaviour. > Interesting! Might be a useful piece of software for other people as well. :-) I should finish it off and publish it. I gave up on it because I could never get the audio over Ethernet part of it working. The idea was to be enable the use VSTs etc. running on Windows in Linux programs like Ardour. > > I wait a bit before applying your sustain patch to LS. Let's see what test > results you get there with GSt 4 on this issue. I didn't specify it in earlier emails but the the Sustain Release issue applies to GSt3 also. In fact the instrument I mentioned, PMI Emperor, is actually a GSt3 instrument. As I couldn't get GSt4 working I set up a VM running GSt3 this morning. I recorded a MIDI file on my Linux host containing a loud note followed by a soft note with the sustain pedal pressed followed by the release of the sustain pedal, as you suggested. When this file is played through LinuxSampler with my patch applied I hear the notes followed by the sustain release samples played at the velocity of the last note. When the file is played through GSt3 I hear no sustain release samples at all. So it would seem that neither the current behaviour nor the behaviour with my patch applied are correct. I think the sustain release behaviour changed from version 1.0 here http://svn.linuxsampler.org/cgi-bin/viewvc.cgi?view=revision&revision=2927 > Thanks! > > CU > Christian All the best, Ivan > > > _______________________________________________ > Linuxsampler-devel mailing list > Lin...@li... > https://lists.sourceforge.net/lists/listinfo/linuxsampler-devel |
|
From: Christian S. <sch...@li...> - 2018-12-10 14:53:39
|
On Sonntag, 9. Dezember 2018 19:39:23 CET Ivan Maguidhir wrote: > > That makes sense. What does gigdump print as global file information for a > > gig v4 file? > > Here's a link to a zip file containing dumps of all the GSt4 instruments > mentioned. I applied your libgig patch to SVN and added gig::File::VERSION_4 as new version identifier according to your dumps. Thanks! I also added a new option to gigedit File->Properties->File Format so that one could explicitly store with gig v4 file format. That might help when toying around with new gig v4 features. > Find attached a patch that > prevents the crash by dropping notes. I didn't submit this yesterday as > it's a bit of a hack and I'm not sure if it's correct. The SONiVOX Synth > Pads.gig instrument still doesn't produce the sounds it's supposed to > with this patch. I will try to investigate how GSt4 handles this > instrument if I can get it running in a VM. The patch prevents the crash, that's correct, but the root cause seems to be that your gig file uses a higher sample playback start position than previously max. allowed and expected by the engine. So obviously even with the patch you won't be able to play the instrument correctly. Probably they raised that playback start position limit in v4. Since you are one of the very few people still having a working GSt 4 installation, that might also be valueable to see what maximum playback start position is allowed in the GSt 4 instrument editor. Once we know the max. playback start position in GSt Instr. Editor 4 we can raise that limit on LS side and that would resolve that issue correctly. > > Have you compared this behaviour with your GigaStudio 4 software there? Is > > that what GSt4 does when releasing the sustain pedal? So for instance if > > you press sustain down, then trigger a key with high velocity, then a 2nd > > time the same key with low velocity, then release the sustain pedal, > > would GSt then play a soft release trigger voice? > > Not yet. It's actually years since I've used GSt4. I'm going to try and > get it working in a Windows XP VM this evening. I wrote a piece of > software several years ago for sending MIDI from JACK on Linux to a > driver running in a Windows VM over Ethernet. I hope I can find it > again. Using this I should be able to test the sustain pedal behaviour. Interesting! Might be a useful piece of software for other people as well. :-) I wait a bit before applying your sustain patch to LS. Let's see what test results you get there with GSt 4 on this issue. Thanks! CU Christian |
|
From: Ivan M. <iv...@ma...> - 2018-12-09 19:39:38
|
On 09/12/2018 11:59, Christian Schoenebeck wrote: > On Samstag, 8. Dezember 2018 17:15:54 CET Ivan Maguidhir wrote: >> Hi everyone > Hi Ivan! Hi Christian. Thanks for the quick response. > >> libgig-4.1.0.svn5-load_giga4_as_giga3.patch causes GigaStudio 4 >> instruments to be loaded as if they were GigaStudio 3 instruments. They >> are currently loaded as if they were GigaStudio 2 instruments making >> them unplayable (usually the same samples on every key). I have a set of >> about 25 GigaStudio 4 instruments which were included on my GigaStudio 4 >> installation discs. There are only one or two of these instruments which >> don't behave as expected with this patch. > That makes sense. What does gigdump print as global file information for a gig > v4 file? Here's a link to a zip file containing dumps of all the GSt4 instruments mentioned. http://www.maguidhir.ie/GSt4_Dumps.zip > > Have you already checked for interesting new features in GSt4 that we might be > missing yet? Not really, but I did notice problems with some of the GSt4 instruments. Two instruments called SONiVOX Alto Saxophone.gig and SONiVOX Harmon Mute Trumpet.gig seem to have clipping or a slight crackling noise on all notes. Also, an instrument called SONiVOX Synth Pads.gig does not work as expected at all. Looking at it in gigedit it has relatively few samples and many regions share a single sample. I think it might rely on filters to generate the different patches? Anyway, it currently produces ear damaging squeaks and squawks before crashing the linuxsampler backend. When I debugged this crash I found out that it happens because linuxsampler doesn't have enough audio samples to resample to pitches that cover the entire keyboard and still have the required block size (256 in my case) to send to ALSA/JACK. Find attached a patch that prevents the crash by dropping notes. I didn't submit this yesterday as it's a bit of a hack and I'm not sure if it's correct. The SONiVOX Synth Pads.gig instrument still doesn't produce the sounds it's supposed to with this patch. I will try to investigate how GSt4 handles this instrument if I can get it running in a VM. >> linuxsampler-2.1.0.svn1-sustain_release_velocity.patch causes sustain >> release samples to be played with the latest Note On velocity of each >> key instead of the current hard-coded velocity of 127 (the highest). >> This was causing me a problem while playing some piano instruments like >> PMI Emperor 24-bit where I would hear an unnaturally loud thump and >> string noise on releasing the sustain pedal even after playing very softly. > Have you compared this behaviour with your GigaStudio 4 software there? Is > that what GSt4 does when releasing the sustain pedal? So for instance if you > press sustain down, then trigger a key with high velocity, then a 2nd time the > same key with low velocity, then release the sustain pedal, would GSt then > play a soft release trigger voice? Not yet. It's actually years since I've used GSt4. I'm going to try and get it working in a Windows XP VM this evening. I wrote a piece of software several years ago for sending MIDI from JACK on Linux to a driver running in a Windows VM over Ethernet. I hope I can find it again. Using this I should be able to test the sustain pedal behaviour. > > CU > Christian All the best, Ivan > > _______________________________________________ > Linuxsampler-devel mailing list > Lin...@li... > https://lists.sourceforge.net/lists/listinfo/linuxsampler-devel |
|
From: Edward D. <di...@um...> - 2018-12-09 13:36:08
|
I just wanted to report my own experience that recent versions of
linuxsampler greatly accentuate the release samples which is very
undesirable. I have several gigastudio pianos from Sampletekk which have
horrible buzzing sounds after every note due to this effect. My solution
has been to use old versions of LS which do not have this problem.
Another solution, less desirable, is to load a patch which does not use
release samples. This patch sounds like a good solution.
Thanks, Edward Diehl
--
Edward Diehl
Research Area Specialist Sr
367C West Hall Office: 734-936-9662
University of Michigan Fax: 734-936-6529
450 Church St Sec'y: 734-615-5811
Ann Arbor, MI 48109-1120 Email: di...@um...
|
|
From: Christian S. <sch...@li...> - 2018-12-09 12:00:04
|
On Samstag, 8. Dezember 2018 17:15:54 CET Ivan Maguidhir wrote: > Hi everyone Hi Ivan! > libgig-4.1.0.svn5-load_giga4_as_giga3.patch causes GigaStudio 4 > instruments to be loaded as if they were GigaStudio 3 instruments. They > are currently loaded as if they were GigaStudio 2 instruments making > them unplayable (usually the same samples on every key). I have a set of > about 25 GigaStudio 4 instruments which were included on my GigaStudio 4 > installation discs. There are only one or two of these instruments which > don't behave as expected with this patch. That makes sense. What does gigdump print as global file information for a gig v4 file? Have you already checked for interesting new features in GSt4 that we might be missing yet? > linuxsampler-2.1.0.svn1-sustain_release_velocity.patch causes sustain > release samples to be played with the latest Note On velocity of each > key instead of the current hard-coded velocity of 127 (the highest). > This was causing me a problem while playing some piano instruments like > PMI Emperor 24-bit where I would hear an unnaturally loud thump and > string noise on releasing the sustain pedal even after playing very softly. Have you compared this behaviour with your GigaStudio 4 software there? Is that what GSt4 does when releasing the sustain pedal? So for instance if you press sustain down, then trigger a key with high velocity, then a 2nd time the same key with low velocity, then release the sustain pedal, would GSt then play a soft release trigger voice? CU Christian |
|
From: Ivan M. <iv...@ma...> - 2018-12-08 17:34:33
|
Hi everyone I've attached two small patches that I'm using that you might also find useful. linuxsampler-2.1.0.svn1-sustain_release_velocity.patch causes sustain release samples to be played with the latest Note On velocity of each key instead of the current hard-coded velocity of 127 (the highest). This was causing me a problem while playing some piano instruments like PMI Emperor 24-bit where I would hear an unnaturally loud thump and string noise on releasing the sustain pedal even after playing very softly. libgig-4.1.0.svn5-load_giga4_as_giga3.patch causes GigaStudio 4 instruments to be loaded as if they were GigaStudio 3 instruments. They are currently loaded as if they were GigaStudio 2 instruments making them unplayable (usually the same samples on every key). I have a set of about 25 GigaStudio 4 instruments which were included on my GigaStudio 4 installation discs. There are only one or two of these instruments which don't behave as expected with this patch. Kind regards, Ivan |
|
From: Rui N. C. <rn...@rn...> - 2018-12-06 16:38:01
|
Hello again, No more excuses left: please upgrade! Qsampler 0.5.3 (end-od-autumn'18) is released! Qsampler [1] is a LinuxSampler [2] GUI front-end application written in C++ around the Qt framework using Qt Designer [3]. Website: https://qsampler.sourceforge.io http://qsampler.sourceforge.net Project page: http://sourceforge.net/projects/qsampler Downloads: http://sourceforge.net/projects/qsampler/files - source tarball: http://download.sf.net/qsampler/qsampler-0.5.3.tar.gz http://download.sf.net/qsampler/liblscp-0.6.0.tar.gz - source package (openSUSE Tumbleweed): http://download.sf.net/qsampler/qsampler-0.5.3-27.rncbc.suse.src.rpm http://download.sf.net/qsampler/liblscp-0.6.0-24.rncbc.suse.src.rpm - binary package (openSUSE Tumbleweed): http://download.sf.net/qsampler/qsampler-0.5.3-27.rncbc.suse.x86_64.rpm http://download.sf.net/qsampler/liblscp6-0.6.0-24.rncbc.suse.x86_64.rpm http://download.sf.net/qsampler/liblscp-devel-0.6.0-24.rncbc.suse.x86_64.rpm - AppImage [6] package: http://download.sf.net/qsampler/qsampler-0.5.3-4.x86_64.AppImage Git repos: https://git.code.sf.net/p/qsampler/code https://github.com/rncbc/qsampler.git https://gitlab.com/rncbc/qsampler.git https://bitbucket.com/rncbc/qsampler.git Change-log: - Avoid saving plug-in sampler channels and related devices to regular LSCP (*.lscp) session files. - Fixed MIDI and Audio device selection on the common sampler channel settings dialog. - Old deprecated Qt4 build support is no more. - AppStream metadata updated to be the most compliant with latest freedesktop.org specification and recommendation. License: Qsampler [1] is free, open-source Linux Audio [4] software, distributed under the terms of the GNU General Public License (GPL) version 2 or later [5]. See also: http://www.rncbc.org/drupal/node/1957 References: [1] Qsampler - A LinuxSampler Qt GUI Interface http://qsampler.sourceforge.net [2] LinuxSampler - The Linux Sampler Project A modular, streaming capable, realtime audio sampler http://www.linuxsampler.org [3] Qt framework, C++ class library and tools for cross-platform application and UI development http://qt.io/ [4] Linux Audio consortium of libre software for audio-related work http://linuxaudio.org [5] GPL - GNU General Public License http://www.gnu.org/copyleft/gpl.html [6] AppImage, Linux apps that run anywhere http://appimage.org/ Enjoy && have (lots of) fun! -- rncbc aka Rui Nuno Capela |
|
From: Christian S. <sch...@li...> - 2018-11-27 16:05:51
|
On Freitag, 23. November 2018 20:54:58 CET Thomas Howe wrote: > Is there a way to set the voice stealing to kill only the oldest voices > across the instrument? There are currently two voice stealing algorithms available as compile time option. Which is either: ./configure --enable-voice-steal-algo=oldestvoiceonkey or ./configure --enable-voice-steal-algo=oldestkey or to disable voice stealing entirely: ./configure --enable-voice-steal-algo=none You probably want "oldestkey". See ./configure --help for details. CU Christian |
|
From: Thomas H. <tho...@gm...> - 2018-11-23 20:55:18
|
Hi all, I've got a problem where if I've run out of voices and hit the same note twice, the second-most-recent hit of the note will be killed. Here is a simple MIDI file I made to show the problem: https://drive.google.com/open?id=1M1rVtVG2ACOySVtrPl9bN_pTRRC8cjos Here is my digital piano's rendition: https://drive.google.com/open?id=1k2nTYRMrpQjXJjfBGlSwcJZ5EmQHsRiP Here is LinuxSampler's rendition: https://drive.google.com/open?id=1absbQBn8CQoA0Kw1XAS1P_0GVU3UyPpb Is there a way to set the voice stealing to kill only the oldest voices across the instrument? Many thanks, Tom |
|
From: <MAX...@li...> - 2018-10-11 09:21:04
|
Hello, this is my first attempt to provide support for aarch64 (ARMv8a). At the moment the only arm patch available is for ARMv7. Is anybody else working on this issue at the moment? NOTE: my patch apply and linuxsampler compiles fine for aarch64, but when the add ENGINE command is sent the server (linuxsampler) crashes with [error 1]+ Illegal instruction I don't know how to proper debug the issue (printf before atomic instructions?) so I'm asking some support to finish the job. Thanks |
|
From: Christian S. <sch...@li...> - 2018-08-14 13:00:10
|
On Dienstag, 14. August 2018 08:51:21 CEST Christoph Kuhr wrote: > lscp.y: In function ‘bool _isRuleTerminalSymbol(int)’: > lscp.y:1386:18: error: ‘yyprhs’ was not declared in this scope > for (int i = yyprhs[rule]; yyrhs[i] != -1; ++i) > ^~~~~~ https://sourceforge.net/p/linuxsampler/mailman/message/34965251/ CU Christian |
|
From: Christoph K. <chr...@we...> - 2018-08-14 06:51:32
|
<html><head></head><body><div style="font-family: Verdana;font-size: 12.0px;"><div>Hi *,</div>
<div> </div>
<div>I tried compiling the new version of Linuxsampler yesterday.</div>
<div> </div>
<div>Make exited with the error:</div>
<div> </div>
<div>
<div style="margin-left: 40px;">In file included from lscpparser.h:45:0,<br/>
from lscp.y:34:<br/>
../drivers/midi/MidiInstrumentMapper.h:146:120: warning: dynamic exception specifications are deprecated in C++11 [-Wdeprecated]<br/>
static void AddOrReplaceEntry(int Map, midi_prog_index_t Index, entry_t Entry, bool bInBackground = false) throw (Exception);<br/>
^~~~~<br/>
../drivers/midi/MidiInstrumentMapper.h:179:73: warning: dynamic exception specifications are deprecated in C++11 [-Wdeprecated]<br/>
static std::map<midi_prog_index_t,entry_t> Entries(int Map) throw (Exception);<br/>
^~~~~<br/>
../drivers/midi/MidiInstrumentMapper.h:195:52: warning: dynamic exception specifications are deprecated in C++11 [-Wdeprecated]<br/>
static int AddMap(String MapName = "") throw (Exception) ;<br/>
^~~~~<br/>
../drivers/midi/MidiInstrumentMapper.h:203:44: warning: dynamic exception specifications are deprecated in C++11 [-Wdeprecated]<br/>
static String MapName(int Map) throw (Exception);<br/>
^~~~~<br/>
../drivers/midi/MidiInstrumentMapper.h:213:60: warning: dynamic exception specifications are deprecated in C++11 [-Wdeprecated]<br/>
static void RenameMap(int Map, String NewName) throw (Exception);<br/>
^~~~~<br/>
lscp.y: In function ‘bool _isRuleTerminalSymbol(int)’:<br/>
lscp.y:1386:18: error: ‘yyprhs’ was not declared in this scope<br/>
for (int i = yyprhs[rule]; yyrhs[i] != -1; ++i)<br/>
^~~~~~<br/>
lscp.y:1386:18: note: suggested alternative: ‘yyr2’<br/>
for (int i = yyprhs[rule]; yyrhs[i] != -1; ++i)<br/>
^~~~~~<br/>
yyr2<br/>
lscp.y:1386:32: error: ‘yyrhs’ was not declared in this scope<br/>
for (int i = yyprhs[rule]; yyrhs[i] != -1; ++i)<br/>
^~~~~<br/>
lscp.y:1386:32: note: suggested alternative: ‘yyr2’<br/>
for (int i = yyprhs[rule]; yyrhs[i] != -1; ++i)<br/>
^~~~~<br/>
yyr2<br/>
Makefile:448: recipe for target 'lscpparser.lo' failed</div>
<div> </div>
<div> </div>
<div>Here is the ./configure output as well:</div>
<div> </div>
<div>
<div style="margin-left: 40px;">christoph@workstation:~/Desktop/project_linuxsampler/linuxsampler-2.1.0$ ./configure --prefix=/usr/local --disable-alsa-driver --disable-arts-driver --disable-artstest --disable-asio-driver --disable-midishare-driver --disable-coremidi-driver --disable-coreaudio-driver --disable-mmemidi-driver --disable-instruments-db --enable-rt-exceptions --enable-debug-level=1 --enable-preload-samples=16777216 --enable-eg-bottom=0.0005 --enable-eg-min-release-time=0.001 --enable-max-pitch=6 --enable-filter-cutoff-min=20.0 --enable-filter-cutoff-max=16000.0<br/>
checking for a BSD-compatible install... /usr/bin/install -c<br/>
checking whether build environment is sane... yes<br/>
checking for a thread-safe mkdir -p... /bin/mkdir -p<br/>
checking for gawk... gawk<br/>
checking whether make sets $(MAKE)... yes<br/>
checking whether make supports nested variables... yes<br/>
checking for gcc... gcc<br/>
checking whether the C compiler works... yes<br/>
checking for C compiler default output file name... a.out<br/>
checking for suffix of executables...<br/>
checking whether we are cross compiling... no<br/>
checking for suffix of object files... o<br/>
checking whether we are using the GNU C compiler... yes<br/>
checking whether gcc accepts -g... yes<br/>
checking for gcc option to accept ISO C89... none needed<br/>
checking whether gcc understands -c and -o together... yes<br/>
checking for style of include used by make... GNU<br/>
checking dependency style of gcc... gcc3<br/>
checking for g++... g++<br/>
checking whether we are using the GNU C++ compiler... yes<br/>
checking whether g++ accepts -g... yes<br/>
checking dependency style of g++... gcc3<br/>
checking build system type... x86_64-pc-linux-gnu<br/>
checking host system type... x86_64-pc-linux-gnu<br/>
checking how to print strings... printf<br/>
checking for a sed that does not truncate output... /bin/sed<br/>
checking for grep that handles long lines and -e... /bin/grep<br/>
checking for egrep... /bin/grep -E<br/>
checking for fgrep... /bin/grep -F<br/>
checking for ld used by gcc... /usr/bin/x86_64-linux-gnu-ld<br/>
checking if the linker (/usr/bin/x86_64-linux-gnu-ld) is GNU ld... yes<br/>
checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B<br/>
checking the name lister (/usr/bin/nm -B) interface... BSD nm<br/>
checking whether ln -s works... yes<br/>
checking the maximum length of command line arguments... 1572864<br/>
checking how to convert x86_64-pc-linux-gnu file names to x86_64-pc-linux-gnu format... func_convert_file_noop<br/>
checking how to convert x86_64-pc-linux-gnu file names to toolchain format... func_convert_file_noop<br/>
checking for /usr/bin/x86_64-linux-gnu-ld option to reload object files... -r<br/>
checking for objdump... objdump<br/>
checking how to recognize dependent libraries... pass_all<br/>
checking for dlltool... dlltool<br/>
checking how to associate runtime and link libraries... printf %s\n<br/>
checking for ar... ar<br/>
checking for archiver @FILE support... @<br/>
checking for strip... strip<br/>
checking for ranlib... ranlib<br/>
checking command to parse /usr/bin/nm -B output from gcc object... ok<br/>
checking for sysroot... no<br/>
checking for a working dd... /bin/dd<br/>
checking how to truncate binary pipes... /bin/dd bs=4096 count=1<br/>
checking for mt... mt<br/>
checking if mt is a manifest tool... no<br/>
checking how to run the C preprocessor... gcc -E<br/>
checking for ANSI C header files... yes<br/>
checking for sys/types.h... yes<br/>
checking for sys/stat.h... yes<br/>
checking for stdlib.h... yes<br/>
checking for string.h... yes<br/>
checking for memory.h... yes<br/>
checking for strings.h... yes<br/>
checking for inttypes.h... yes<br/>
checking for stdint.h... yes<br/>
checking for unistd.h... yes<br/>
checking for dlfcn.h... yes<br/>
checking for objdir... .libs<br/>
checking if gcc supports -fno-rtti -fno-exceptions... no<br/>
checking for gcc option to produce PIC... -fPIC -DPIC<br/>
checking if gcc PIC flag -fPIC -DPIC works... yes<br/>
checking if gcc static flag -static works... yes<br/>
checking if gcc supports -c -o file.o... yes<br/>
checking if gcc supports -c -o file.o... (cached) yes<br/>
checking whether the gcc linker (/usr/bin/x86_64-linux-gnu-ld -m elf_x86_64) supports shared libraries... yes<br/>
checking whether -lc should be explicitly linked in... no<br/>
checking dynamic linker characteristics... GNU/Linux ld.so<br/>
checking how to hardcode library paths into programs... immediate<br/>
checking whether stripping libraries is possible... yes<br/>
checking if libtool supports shared libraries... yes<br/>
checking whether to build shared libraries... yes<br/>
checking whether to build static libraries... yes<br/>
checking how to run the C++ preprocessor... g++ -E<br/>
checking for ld used by g++... /usr/bin/x86_64-linux-gnu-ld -m elf_x86_64<br/>
checking if the linker (/usr/bin/x86_64-linux-gnu-ld -m elf_x86_64) is GNU ld... yes<br/>
checking whether the g++ linker (/usr/bin/x86_64-linux-gnu-ld -m elf_x86_64) supports shared libraries... yes<br/>
checking for g++ option to produce PIC... -fPIC -DPIC<br/>
checking if g++ PIC flag -fPIC -DPIC works... yes<br/>
checking if g++ static flag -static works... yes<br/>
checking if g++ supports -c -o file.o... yes<br/>
checking if g++ supports -c -o file.o... (cached) yes<br/>
checking whether the g++ linker (/usr/bin/x86_64-linux-gnu-ld -m elf_x86_64) supports shared libraries... yes<br/>
checking dynamic linker characteristics... (cached) GNU/Linux ld.so<br/>
checking how to hardcode library paths into programs... immediate<br/>
checking for flex... no<br/>
checking for lex... no<br/>
checking for bison... no<br/>
checking for byacc... no<br/>
checking whether byte ordering is bigendian... no<br/>
checking for pkg-config... /usr/bin/pkg-config<br/>
checking pkg-config is at least version 0.9.0... yes<br/>
checking whether x86 architecture... yes<br/>
checking for mmsystem.h... no<br/>
checking whether UNIX98 compatible... yes<br/>
checking features.h usability... yes<br/>
checking features.h presence... yes<br/>
checking for features.h... yes<br/>
checking for the pthreads library -lpthreads... no<br/>
checking whether pthreads work without any flags... no<br/>
checking whether pthreads work with -Kthread... no<br/>
checking whether pthreads work with -kthread... no<br/>
checking for the pthreads library -llthread... no<br/>
checking whether pthreads work with -pthread... yes<br/>
checking for joinable pthread attribute... PTHREAD_CREATE_JOINABLE<br/>
checking if more special flags are required for pthreads... no<br/>
checking for compiler's pragma diagnostics... no<br/>
checking for NPTL bug... no<br/>
ALSA support disabled by configure script parameter<br/>
checking for JACK... yes<br/>
checking for jack_client_name_size... yes<br/>
checking for jack_client_open... yes<br/>
checking for jack_on_info_shutdown... yes<br/>
checking jack/midiport.h usability... yes<br/>
checking jack/midiport.h presence... yes<br/>
checking for jack/midiport.h... yes<br/>
checking for jack_midi_get_event_count... yes<br/>
ARTS support disabled by configure script parameter<br/>
Windows ASIO support disabled by configure script parameter<br/>
MidiShare support disabled by configure script parameter<br/>
CoreMIDI support disabled by configure script parameter<br/>
CoreAudio support disabled by configure script parameter<br/>
MME MIDI support disabled by configure script parameter<br/>
checking dssi.h usability... yes<br/>
checking dssi.h presence... yes<br/>
checking for dssi.h... yes<br/>
checking for LV2... yes<br/>
checking AudioUnit/AudioUnit.h usability... no<br/>
checking AudioUnit/AudioUnit.h presence... no<br/>
checking for AudioUnit/AudioUnit.h... no<br/>
checking for GIG... yes<br/>
yes, found libgig 4.1.0<br/>
checking for SNDFILE... yes<br/>
yes, found libsndfile 1.0<br/>
checking whether SF_FORMAT_VORBIS is declared... yes<br/>
checking whether SF_FORMAT_FLAC is declared... yes<br/>
checking for SF_INSTRUMENT.loops... yes<br/>
Instruments DB feature disabled by configure script parameter<br/>
benchmarking for the best (signed) triangular oscillator algorithm... integer math using abs()<br/>
benchmarking for the best (unsigned) triangular oscillator algorithm... integer math using abs()<br/>
checking for stdlib.h... (cached) yes<br/>
checking that generated files are newer than configure... done<br/>
configure: creating ./config.status<br/>
config.status: creating Makefile<br/>
config.status: creating man/Makefile<br/>
config.status: creating man/linuxsampler.1<br/>
config.status: creating man/lscp.1<br/>
config.status: creating src/Makefile<br/>
config.status: creating src/db/Makefile<br/>
config.status: creating src/network/Makefile<br/>
config.status: creating src/engines/Makefile<br/>
config.status: creating src/engines/gig/Makefile<br/>
config.status: creating src/engines/sf2/Makefile<br/>
config.status: creating src/engines/sfz/Makefile<br/>
config.status: creating src/engines/common/Makefile<br/>
config.status: creating src/effects/Makefile<br/>
config.status: creating src/common/Makefile<br/>
config.status: creating src/testcases/Makefile<br/>
config.status: creating src/drivers/Makefile<br/>
config.status: creating src/drivers/audio/Makefile<br/>
config.status: creating src/drivers/midi/Makefile<br/>
config.status: creating src/plugins/Makefile<br/>
config.status: creating src/hostplugins/Makefile<br/>
config.status: creating src/hostplugins/dssi/Makefile<br/>
config.status: creating src/hostplugins/lv2/Makefile<br/>
config.status: creating src/hostplugins/lv2/manifest.ttl<br/>
config.status: creating src/hostplugins/vst/Makefile<br/>
config.status: creating src/hostplugins/au/Makefile<br/>
config.status: creating src/scriptvm/Makefile<br/>
config.status: creating src/scriptvm/editor/Makefile<br/>
config.status: creating src/shell/Makefile<br/>
config.status: creating linuxsampler.spec<br/>
config.status: creating debian/Makefile<br/>
config.status: creating Artwork/Makefile<br/>
config.status: creating scripts/Makefile<br/>
config.status: creating osx/Makefile<br/>
config.status: creating osx/linuxsampler.xcodeproj/Makefile<br/>
config.status: creating Documentation/Makefile<br/>
config.status: creating Documentation/Engines/Makefile<br/>
config.status: creating Documentation/Engines/gig/Makefile<br/>
config.status: creating linuxsampler.pc<br/>
config.status: creating Doxyfile<br/>
config.status: creating config.h<br/>
config.status: config.h is unchanged<br/>
config.status: executing depfiles commands<br/>
config.status: executing libtool commands</div>
<div style="margin-left: 40px;">#####################################################################<br/>
# LinuxSampler Configuration #<br/>
#-------------------------------------------------------------------#<br/>
# Release Version: 2.1.0<br/>
# LSCP Version: 1.7<br/>
#-------------------------------------------------------------------<br/>
# Assembly Optimizations: yes<br/>
# Development Mode: no<br/>
# Debug Level: 1<br/>
# Use Exceptions in RT Context: yes<br/>
# Preload Samples: 16777216<br/>
# Maximum Pitch: 6 (octaves)<br/>
# Maximum Events: 1024<br/>
# Envelope Bottom Level: 0.0005 (linear)<br/>
# Envelope Minimum Release Time: 0.001 s<br/>
# Streams to be refilled per Disk Thread Cycle: 4<br/>
# Minimum Stream Refill Size: 1024<br/>
# Maximum Stream Refill Size: 65536<br/>
# Stream Size: 262144<br/>
# Default Maximum Disk Streams: 90<br/>
# Default Maximum Voices: 64<br/>
# Default Subfragment Size: 32<br/>
# Default Global Volume Attenuation: 0.35<br/>
# Voice Stealing Algorithm: oldestvoiceonkey<br/>
# Signed Triangular Oscillator Algorithm: intmathabs<br/>
# Unsigned Triangular Oscillator Algorithm: intmathabs<br/>
# SysEx Buffer Size: 2048 Byte<br/>
# Min. Portamento Time: 0.1 s<br/>
# Max. Portamento Time: 32 s<br/>
# Default Portamento Time: 1 s<br/>
# Force Filter Usage: no<br/>
# Filter Cutoff Minimum: 20.0 Hz<br/>
# Filter Cutoff Maximum: 16000.0 Hz<br/>
# Override Filter Cutoff Controller: no<br/>
# Override Filter Resonance Controller: no<br/>
# Override Filter Type: no<br/>
# Assert GS SysEx Checksum: no<br/>
# Process Muted Channels: no<br/>
# Process All-Notes-Off MIDI message: yes<br/>
# Apply global volume SysEx by MIDI port: no<br/>
# Interpolate Volume: yes<br/>
# Instruments database support: no<br/>
# Plugin Path: /usr/local/lib/linuxsampler/plugins<br/>
#-------------------------------------------------------------------<br/>
# MIDI Input Drivers:<br/>
# ALSA: no, JACK: yes, CoreMIDI: no, MME: no, MidiShare: no<br/>
#-------------------------------------------------------------------<br/>
# Audio Output Drivers:<br/>
# ALSA: no, JACK: yes, ARTS: no, CoreAudio: no, ASIO: no<br/>
#-------------------------------------------------------------------<br/>
# Sampler Engines:<br/>
# GIG: yes, SF2: yes, SFZ: yes<br/>
#-------------------------------------------------------------------<br/>
# Effect plugin systems for internal effects:<br/>
# LADSPA: yes<br/>
#-------------------------------------------------------------------<br/>
# Building sampler as plugin for following host standards:<br/>
# DSSI: yes, LV2: yes, VST: no, AU: no<br/>
#-------------------------------------------------------------------#<br/>
# Read './configure --help' or file 'configure.in' for details. #<br/>
#####################################################################</div>
<div style="margin-left: 40px;">Good. Now type 'make' to compile, followed by 'make install' as root.</div>
<div style="margin-left: 40px;">christoph@workstation:~/Desktop/project_linuxsampler/linuxsampler-2.1.0$ make<br/>
make all-recursive<br/>
make[1]: Entering directory '/home/christoph/Desktop/project_linuxsampler/linuxsampler-2.1.0'<br/>
Making all in man<br/>
make[2]: Entering directory '/home/christoph/Desktop/project_linuxsampler/linuxsampler-2.1.0/man'<br/>
make[2]: Nothing to be done for 'all'.<br/>
make[2]: Leaving directory '/home/christoph/Desktop/project_linuxsampler/linuxsampler-2.1.0/man'<br/>
Making all in src<br/>
make[2]: Entering directory '/home/christoph/Desktop/project_linuxsampler/linuxsampler-2.1.0/src'<br/>
Making all in scriptvm<br/>
make[3]: Entering directory '/home/christoph/Desktop/project_linuxsampler/linuxsampler-2.1.0/src/scriptvm'<br/>
make all-recursive<br/>
make[4]: Entering directory '/home/christoph/Desktop/project_linuxsampler/linuxsampler-2.1.0/src/scriptvm'<br/>
Making all in editor<br/>
make[5]: Entering directory '/home/christoph/Desktop/project_linuxsampler/linuxsampler-2.1.0/src/scriptvm/editor'<br/>
make[5]: Nothing to be done for 'all'.<br/>
make[5]: Leaving directory '/home/christoph/Desktop/project_linuxsampler/linuxsampler-2.1.0/src/scriptvm/editor'<br/>
make[5]: Entering directory '/home/christoph/Desktop/project_linuxsampler/linuxsampler-2.1.0/src/scriptvm'<br/>
make[5]: Nothing to be done for 'all-am'.<br/>
make[5]: Leaving directory '/home/christoph/Desktop/project_linuxsampler/linuxsampler-2.1.0/src/scriptvm'<br/>
make[4]: Leaving directory '/home/christoph/Desktop/project_linuxsampler/linuxsampler-2.1.0/src/scriptvm'<br/>
make[3]: Leaving directory '/home/christoph/Desktop/project_linuxsampler/linuxsampler-2.1.0/src/scriptvm'<br/>
Making all in db<br/>
make[3]: Entering directory '/home/christoph/Desktop/project_linuxsampler/linuxsampler-2.1.0/src/db'<br/>
make[3]: Nothing to be done for 'all'.<br/>
make[3]: Leaving directory '/home/christoph/Desktop/project_linuxsampler/linuxsampler-2.1.0/src/db'<br/>
Making all in network<br/>
make[3]: Entering directory '/home/christoph/Desktop/project_linuxsampler/linuxsampler-2.1.0/src/network'<br/>
depbase=`echo lscpparser.lo | sed 's|[^/]*$|.deps/&|;s|\.lo$||'`;\<br/>
/bin/bash ../../libtool --tag=CXX --mode=compile g++ -DHAVE_CONFIG_H -I. -I../.. -I/usr/local/include/libgig -Wreturn-type -ffast-math -g -O2 -pthread -MT lscpparser.lo -MD -MP -MF $depbase.Tpo -c -o lscpparser.lo lscpparser.cpp &&\<br/>
mv -f $depbase.Tpo $depbase.Plo<br/>
libtool: compile: g++ -DHAVE_CONFIG_H -I. -I../.. -I/usr/local/include/libgig -Wreturn-type -ffast-math -g -O2 -pthread -MT lscpparser.lo -MD -MP -MF .deps/lscpparser.Tpo -c lscpparser.cpp -fPIC -DPIC -o .libs/lscpparser.o<br/>
In file included from lscpparser.h:41:0,<br/>
from lscp.y:34:<br/>
../common/global_private.h:95:40: warning: dynamic exception specifications are deprecated in C++11 [-Wdeprecated]<br/>
inline int ToInt(const std::string& s) throw(LinuxSampler::Exception) {<br/>
^~~~~<br/>
../common/global_private.h:102:44: warning: dynamic exception specifications are deprecated in C++11 [-Wdeprecated]<br/>
inline float ToFloat(const std::string& s) throw(LinuxSampler::Exception) {<br/>
^~~~~<br/>
In file included from ../engines/../drivers/audio/../DeviceParameter.h:31:0,<br/>
from ../engines/../drivers/audio/AudioOutputDevice.h:35,<br/>
from ../engines/EngineChannel.h:25,<br/>
from ../Sampler.h:32,<br/>
from lscpevent.h:30,<br/>
from lscpparser.h:43,<br/>
from lscp.y:34:<br/>
../engines/../drivers/audio/../../common/optional.h:73:34: warning: dynamic exception specifications are deprecated in C++11 [-Wdeprecated]<br/>
const T& get() const throw (Exception) {<br/>
^~~~~<br/>
../engines/../drivers/audio/../../common/optional.h:78:22: warning: dynamic exception specifications are deprecated in C++11 [-Wdeprecated]<br/>
T& get() throw (Exception) {<br/>
^~~~~<br/>
../engines/../drivers/audio/../../common/optional.h:95:41: warning: dynamic exception specifications are deprecated in C++11 [-Wdeprecated]<br/>
const T& operator *() const throw (Exception) { return get(); }<br/>
^~~~~<br/>
../engines/../drivers/audio/../../common/optional.h:96:41: warning: dynamic exception specifications are deprecated in C++11 [-Wdeprecated]<br/>
T& operator *() throw (Exception) { return get(); }<br/>
^~~~~<br/>
../engines/../drivers/audio/../../common/optional.h:98:42: warning: dynamic exception specifications are deprecated in C++11 [-Wdeprecated]<br/>
const T* operator ->() const throw (Exception) {<br/>
^~~~~<br/>
../engines/../drivers/audio/../../common/optional.h:103:30: warning: dynamic exception specifications are deprecated in C++11 [-Wdeprecated]<br/>
T* operator ->() throw (Exception) {<br/>
^~~~~<br/>
In file included from ../engines/../drivers/audio/AudioOutputDevice.h:35:0,<br/>
from ../engines/EngineChannel.h:25,<br/>
from ../Sampler.h:32,<br/>
from lscpevent.h:30,<br/>
from lscpparser.h:43,<br/>
from lscp.y:34:<br/>
../engines/../drivers/audio/../DeviceParameter.h:181:47: warning: dynamic exception specifications are deprecated in C++11 [-Wdeprecated]<br/>
virtual void SetValue(String val) throw (Exception) = 0;<br/>
^~~~~<br/>
../engines/../drivers/audio/../DeviceParameter.h:224:59: warning: dynamic exception specifications are deprecated in C++11 [-Wdeprecated]<br/>
virtual void SetValue(String val) throw (Exception) OVERRIDE;<br/>
^~~~~<br/>
../engines/../drivers/audio/../DeviceParameter.h:231:43: warning: dynamic exception specifications are deprecated in C++11 [-Wdeprecated]<br/>
virtual void SetValue(bool b) throw (Exception);<br/>
^~~~~<br/>
../engines/../drivers/audio/../DeviceParameter.h:246:45: warning: dynamic exception specifications are deprecated in C++11 [-Wdeprecated]<br/>
virtual void OnSetValue(bool b) throw (Exception) = 0;<br/>
^~~~~<br/>
../engines/../drivers/audio/../DeviceParameter.h:283:59: warning: dynamic exception specifications are deprecated in C++11 [-Wdeprecated]<br/>
virtual void SetValue(String val) throw (Exception) OVERRIDE;<br/>
^~~~~<br/>
../engines/../drivers/audio/../DeviceParameter.h:290:42: warning: dynamic exception specifications are deprecated in C++11 [-Wdeprecated]<br/>
virtual void SetValue(int i) throw (Exception);<br/>
^~~~~<br/>
../engines/../drivers/audio/../DeviceParameter.h:329:44: warning: dynamic exception specifications are deprecated in C++11 [-Wdeprecated]<br/>
virtual void OnSetValue(int i) throw (Exception) = 0;<br/>
^~~~~<br/>
../engines/../drivers/audio/../DeviceParameter.h:367:59: warning: dynamic exception specifications are deprecated in C++11 [-Wdeprecated]<br/>
virtual void SetValue(String val) throw (Exception) OVERRIDE;<br/>
^~~~~<br/>
../engines/../drivers/audio/../DeviceParameter.h:374:45: warning: dynamic exception specifications are deprecated in C++11 [-Wdeprecated]<br/>
virtual void SetValue(float f) throw (Exception);<br/>
^~~~~<br/>
../engines/../drivers/audio/../DeviceParameter.h:453:59: warning: dynamic exception specifications are deprecated in C++11 [-Wdeprecated]<br/>
virtual void SetValue(String val) throw (Exception) OVERRIDE;<br/>
^~~~~<br/>
../engines/../drivers/audio/../DeviceParameter.h:460:55: warning: dynamic exception specifications are deprecated in C++11 [-Wdeprecated]<br/>
virtual void SetValueAsString(String s) throw (Exception);<br/>
^~~~~<br/>
../engines/../drivers/audio/../DeviceParameter.h:523:59: warning: dynamic exception specifications are deprecated in C++11 [-Wdeprecated]<br/>
virtual void SetValue(String val) throw (Exception) OVERRIDE;<br/>
^~~~~<br/>
../engines/../drivers/audio/../DeviceParameter.h:530:74: warning: dynamic exception specifications are deprecated in C++11 [-Wdeprecated]<br/>
virtual void SetValue(std::vector<String> vS) throw (Exception);<br/>
^~~~~<br/>
../engines/../drivers/audio/../DeviceParameter.h:771:53: warning: dynamic exception specifications are deprecated in C++11 [-Wdeprecated]<br/>
DeviceCreationParameterBool(String val) throw (Exception);<br/>
^~~~~<br/>
../engines/../drivers/audio/../DeviceParameter.h:779:49: warning: dynamic exception specifications are deprecated in C++11 [-Wdeprecated]<br/>
virtual void SetValue(String val) throw (Exception) OVERRIDE;<br/>
^~~~~<br/>
../engines/../drivers/audio/../DeviceParameter.h:782:43: warning: dynamic exception specifications are deprecated in C++11 [-Wdeprecated]<br/>
virtual void SetValue(bool b) throw (Exception);<br/>
^~~~~<br/>
../engines/../drivers/audio/../DeviceParameter.h:785:45: warning: dynamic exception specifications are deprecated in C++11 [-Wdeprecated]<br/>
virtual void OnSetValue(bool b) throw (Exception) = 0;<br/>
^~~~~<br/>
../engines/../drivers/audio/../DeviceParameter.h:808:52: warning: dynamic exception specifications are deprecated in C++11 [-Wdeprecated]<br/>
DeviceCreationParameterInt(String val) throw (Exception);<br/>
^~~~~<br/>
../engines/../drivers/audio/../DeviceParameter.h:816:49: warning: dynamic exception specifications are deprecated in C++11 [-Wdeprecated]<br/>
virtual void SetValue(String val) throw (Exception) OVERRIDE;<br/>
^~~~~<br/>
../engines/../drivers/audio/../DeviceParameter.h:819:42: warning: dynamic exception specifications are deprecated in C++11 [-Wdeprecated]<br/>
virtual void SetValue(int i) throw (Exception);<br/>
^~~~~<br/>
../engines/../drivers/audio/../DeviceParameter.h:825:56: warning: dynamic exception specifications are deprecated in C++11 [-Wdeprecated]<br/>
virtual void OnSetValue(int i) throw (Exception) = 0;<br/>
^~~~~<br/>
../engines/../drivers/audio/../DeviceParameter.h:848:54: warning: dynamic exception specifications are deprecated in C++11 [-Wdeprecated]<br/>
DeviceCreationParameterFloat(String val) throw (Exception);<br/>
^~~~~<br/>
../engines/../drivers/audio/../DeviceParameter.h:856:49: warning: dynamic exception specifications are deprecated in C++11 [-Wdeprecated]<br/>
virtual void SetValue(String val) throw (Exception) OVERRIDE;<br/>
^~~~~<br/>
../engines/../drivers/audio/../DeviceParameter.h:859:45: warning: dynamic exception specifications are deprecated in C++11 [-Wdeprecated]<br/>
virtual void SetValue(float f) throw (Exception);<br/>
^~~~~<br/>
../engines/../drivers/audio/../DeviceParameter.h:865:46: warning: dynamic exception specifications are deprecated in C++11 [-Wdeprecated]<br/>
virtual void OnSetValue(float f) throw (Exception) = 0;<br/>
^~~~~<br/>
../engines/../drivers/audio/../DeviceParameter.h:895:49: warning: dynamic exception specifications are deprecated in C++11 [-Wdeprecated]<br/>
virtual void SetValue(String val) throw (Exception) OVERRIDE;<br/>
^~~~~<br/>
../engines/../drivers/audio/../DeviceParameter.h:898:55: warning: dynamic exception specifications are deprecated in C++11 [-Wdeprecated]<br/>
virtual void SetValueAsString(String s) throw (Exception);<br/>
^~~~~<br/>
../engines/../drivers/audio/../DeviceParameter.h:902:47: warning: dynamic exception specifications are deprecated in C++11 [-Wdeprecated]<br/>
virtual void OnSetValue(String s) throw (Exception) = 0;<br/>
^~~~~<br/>
../engines/../drivers/audio/../DeviceParameter.h:926:56: warning: dynamic exception specifications are deprecated in C++11 [-Wdeprecated]<br/>
DeviceCreationParameterStrings(String val) throw (Exception);<br/>
^~~~~<br/>
../engines/../drivers/audio/../DeviceParameter.h:935:49: warning: dynamic exception specifications are deprecated in C++11 [-Wdeprecated]<br/>
virtual void SetValue(String val) throw (Exception) OVERRIDE;<br/>
^~~~~<br/>
../engines/../drivers/audio/../DeviceParameter.h:938:74: warning: dynamic exception specifications are deprecated in C++11 [-Wdeprecated]<br/>
virtual void SetValue(std::vector<String> vS) throw (Exception);<br/>
^~~~~<br/>
../engines/../drivers/audio/../DeviceParameter.h:942:61: warning: dynamic exception specifications are deprecated in C++11 [-Wdeprecated]<br/>
virtual void OnSetValue(std::vector<String> vS) throw (Exception) = 0;<br/>
^~~~~<br/>
In file included from ../engines/../drivers/audio/../../engines/Engine.h:28:0,<br/>
from ../engines/../drivers/audio/AudioOutputDevice.h:36,<br/>
from ../engines/EngineChannel.h:25,<br/>
from ../Sampler.h:32,<br/>
from lscpevent.h:30,<br/>
from lscpparser.h:43,<br/>
from lscp.y:34:<br/>
../engines/../drivers/audio/../../engines/InstrumentManager.h:190:137: warning: dynamic exception specifications are deprecated in C++11 [-Wdeprecated]<br/>
virtual InstrumentEditor* LaunchInstrumentEditor(EngineChannel* pEngineChannel, instrument_id_t ID, void* pUserData = NULL) throw (InstrumentManagerException) = 0;<br/>
^~~~~<br/>
../engines/../drivers/audio/../../engines/InstrumentManager.h:199:88: warning: dynamic exception specifications are deprecated in C++11 [-Wdeprecated]<br/>
virtual std::vector<instrument_id_t> GetInstrumentFileContent(String File) throw (InstrumentManagerException) = 0;<br/>
^~~~~<br/>
../engines/../drivers/audio/../../engines/InstrumentManager.h:207:77: warning: dynamic exception specifications are deprecated in C++11 [-Wdeprecated]<br/>
virtual instrument_info_t GetInstrumentInfo(instrument_id_t ID) throw (InstrumentManagerException) = 0;<br/>
^~~~~<br/>
In file included from ../engines/../drivers/audio/AudioOutputDevice.h:36:0,<br/>
from ../engines/EngineChannel.h:25,<br/>
from ../Sampler.h:32,<br/>
from lscpevent.h:30,<br/>
from lscpparser.h:43,<br/>
from lscp.y:34:<br/>
../engines/../drivers/audio/../../engines/Engine.h:56:54: warning: dynamic exception specifications are deprecated in C++11 [-Wdeprecated]<br/>
virtual void SetMaxVoices(int iVoices) throw (Exception) = 0;<br/>
^~~~~<br/>
../engines/../drivers/audio/../../engines/Engine.h:61:60: warning: dynamic exception specifications are deprecated in C++11 [-Wdeprecated]<br/>
virtual void SetMaxDiskStreams(int iStreams) throw (Exception) = 0;<br/>
^~~~~<br/>
In file included from ../engines/../drivers/audio/AudioOutputDevice.h:37:0,<br/>
from ../engines/EngineChannel.h:25,<br/>
from ../Sampler.h:32,<br/>
from lscpevent.h:30,<br/>
from lscpparser.h:43,<br/>
from lscp.y:34:<br/>
../engines/../drivers/audio/AudioChannel.h:72:55: warning: dynamic exception specifications are deprecated in C++11 [-Wdeprecated]<br/>
virtual void OnSetValue(bool b) throw (Exception) OVERRIDE { /* cannot happen, as parameter is fix */ }<br/>
^~~~~<br/>
../engines/../drivers/audio/AudioChannel.h:83:64: warning: dynamic exception specifications are deprecated in C++11 [-Wdeprecated]<br/>
virtual void OnSetValue(int i) throw (Exception) OVERRIDE { /*TODO: needs to be implemented */ }<br/>
^~~~~<br/>
In file included from ../engines/../drivers/audio/../../effects/Effect.h:27:0,<br/>
from ../engines/../drivers/audio/../../effects/EffectChain.h:24,<br/>
from ../engines/../drivers/audio/AudioOutputDevice.h:39,<br/>
from ../engines/EngineChannel.h:25,<br/>
from ../Sampler.h:32,<br/>
from lscpevent.h:30,<br/>
from lscpparser.h:43,<br/>
from lscp.y:34:<br/>
../engines/../drivers/audio/../../effects/EffectControl.h:32:38: warning: dynamic exception specifications are deprecated in C++11 [-Wdeprecated]<br/>
virtual void SetValue(float val) throw (Exception);<br/>
^~~~~<br/>
In file included from ../engines/../drivers/audio/../../effects/EffectChain.h:24:0,<br/>
from ../engines/../drivers/audio/AudioOutputDevice.h:39,<br/>
from ../engines/EngineChannel.h:25,<br/>
from ../Sampler.h:32,<br/>
from lscpevent.h:30,<br/>
from lscpparser.h:43,<br/>
from lscp.y:34:<br/>
../engines/../drivers/audio/../../effects/Effect.h:77:57: warning: dynamic exception specifications are deprecated in C++11 [-Wdeprecated]<br/>
virtual void InitEffect(AudioOutputDevice* pDevice) throw (Exception);<br/>
^~~~~<br/>
In file included from ../engines/../drivers/audio/AudioOutputDevice.h:39:0,<br/>
from ../engines/EngineChannel.h:25,<br/>
from ../Sampler.h:32,<br/>
from lscpevent.h:30,<br/>
from lscpparser.h:43,<br/>
from lscp.y:34:<br/>
../engines/../drivers/audio/../../effects/EffectChain.h:60:55: warning: dynamic exception specifications are deprecated in C++11 [-Wdeprecated]<br/>
void InsertEffect(Effect* pEffect, int iChainPos) throw (Exception);<br/>
&n...
[truncated message content] |
|
From: Edgar A. <ed...@ao...> - 2018-07-24 13:21:51
|
Hello, I'm a long time linux audio user and also maintain a bunch of rpm packages for openSUSE. In an attempt to get falkTX's carla into the official openSUSE distribution, I also currently maintain ligig and other packages carla depends on. Yesterday (and today again) I received ten mails regarding bug issues from some automated security checks, and as I'm not a programmer and don't have the knowledge to resolve any of these, I want to point you towards these. They all are marked minor severity, but nevertheless I hope you can make sense of these, and possibly fix them upstream. Below I post links to the opensuse bugzilla entries, each has a comment near the bottom linking to other pages with more detailed test results, gdb and other logs: http://bugzilla.opensuse.org/show_bug.cgi?id=1102164 http://bugzilla.opensuse.org/show_bug.cgi?id=1102165 http://bugzilla.opensuse.org/show_bug.cgi?id=1102167 http://bugzilla.opensuse.org/show_bug.cgi?id=1102168 http://bugzilla.opensuse.org/show_bug.cgi?id=1102169 http://bugzilla.opensuse.org/show_bug.cgi?id=1102170 http://bugzilla.opensuse.org/show_bug.cgi?id=1102173 http://bugzilla.opensuse.org/show_bug.cgi?id=1102174 http://bugzilla.opensuse.org/show_bug.cgi?id=1102176 http://bugzilla.opensuse.org/show_bug.cgi?id=1102177 Thank you, Edgar |
|
From: Nathan B. <nat...@th...> - 2018-07-05 18:03:45
|
Hello, I'm compiling Linux Sampler on a Gemini PDA with a Mediatek Helio *X27* processor, but I received this error in RTMath.cpp: "Sorry, LinuxSampler lacks time stamp code for your system." "Please report this error and the CPU you are using to the LinuxSampler developers mailing list!" Thus I'm reporting to the e-mail list. It's a 10-core processor with two ARM-A72 cores and 8 ARM-A53 cores. I'm compiling natively not cross-compiling. Let me know if I need to run anything. Here's cat /proc/cpuinfo Processor : AArch64 Processor rev 4 (aarch64) processor : 0 model name : AArch64 Processor rev 4 (aarch64) BogoMIPS : 26.00 BogoMIPS : 26.00 Features : fp asimd evtstrm aes pmull sha1 sha2 crc32 CPU implementer : 0x41 CPU architecture: 8 CPU variant : 0x0 CPU part : 0xd03 CPU revision : 4 Hardware : MT6797X Thanks! - Nathan |
|
From: Christian S. <sch...@li...> - 2018-06-27 11:32:10
|
On Montag, 25. Juni 2018 12:45:38 CEST Andrew C wrote:
> Would it be possible from a gigedit/engine POV to break the 256 dimension
> limit?
It is of course possible. However if the actual question is whether this would
be a one line change, then I have to disappoint you. At the moment this limit
of max. 256 dimension regions is hard coded at many places in libgig and in
LinuxSampler's gig engine and in gigedit. So in the source code in all of them
you currently find many places like i.e.:
for (int dr = 0; dr < 256; ++dr) {
...
}
So raising that limit would require reviewing and manually adjusting a
substantial amount of code. Automatic refactoring tools would not help in this
case. Not a hard work of course, because in the end you just have to look at
occurences of such 256 numbers in the code (and checking whether the
respective 256 number is actually about dimension regions or something else),
but it takes time and patience.
> In this glorious 64-bit age, could this be upped to 1024 or 768 (though, I
> am aware this would break giga compatibility with the original gigastudio)?
Giga compatibility is not the main issue here. I mean I already extended the
GigaStudio format at several places for adding useful enhancements, always
with the same usage pattern: if the user user decides to use format extension
X than he gets a warning in gigedit that the gig file won't load with
GigaStudio. If he later removes feature X it would load with GigaStudio again.
Well, if you want that 256 limit change to happen, then you could start by
reviewing the code and replacing the occurences of those 256 number literals
by calls to a libgig member variable or method call which would return the
current limit for the gig file. So that overall change would not happen over
night, but rather be a step by step effort.
CU
Christian
|
|
From: Andrew C <cou...@gm...> - 2018-06-25 11:45:46
|
Hi all, Would it be possible from a gigedit/engine POV to break the 256 dimension limit? I'm wanting to layer together a bunch of crossfaded(2 instruments, 4 layers each) and velocity sensitive instruments (3 instruments, 4-5 layers), but gigedit is telling me it would exceed the 256 dimension limit. In this glorious 64-bit age, could this be upped to 1024 or 768 (though, I am aware this would break giga compatibility with the original gigastudio)? Thanks, Andrew. |
|
From: Andrew C <cou...@gm...> - 2018-06-22 16:23:18
|
Hi all, I'm wanting to embark on a mini-project to create 'large' keyswitched instruments for a 'customised' string library. Will gigedit choke/mess up if I have say, modwheel xfade layers + velocity for one keyswitch, then just velocity layers for staccato and pizzicato keyswitches? Thanks, Andrew. |
|
From: Andrew C <cou...@gm...> - 2018-06-21 22:28:42
|
Many thanks, that worked out just as well! Andrew. On Mon 11 Jun 2018, 15:08 Christian Schoenebeck, < sch...@li...> wrote: > On Montag, 11. Juni 2018 14:13:47 CEST Andrew C wrote: > > What I'm trying to achieve to just simply copy the whole C2 region > (samples > > and all) over to the B2 region (whether I have to outright delete it or > > not), with all dimensionsj and samples referenced intact and without > having > > to manually remap those samples. > > Then if I am not missing anything, what you probably want to do in this > case > instead is: > > 1. Select region B2. > > 2. Delete region B2. > > 3. Drag the boundary of region C2 horizontally such that region C2 would > cover > the old B2 region. > > That way you don't have to copy anything. You just enlarge C2's key span. > > CU > Christian > > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Linuxsampler-devel mailing list > Lin...@li... > https://lists.sourceforge.net/lists/listinfo/linuxsampler-devel > |
|
From: Andrew C <cou...@gm...> - 2018-06-21 18:35:36
|
HI all, I'm merging large gigs together and they seem to take a long time to merge and finish saving. Trying to merge 1st and 2nd violins legato gigs(each around 600MB) and while the sample size increases instantly to 1.2GB or so, gigedit seems to "lag" behind with recreating the Instruments + settings? Should it take as long as 30 minutes? htop shows minimal CPU usage from gigedit. Thanks, Andrew. |
|
From: Christian S. <sch...@li...> - 2018-06-11 14:07:36
|
On Montag, 11. Juni 2018 14:13:47 CEST Andrew C wrote: > What I'm trying to achieve to just simply copy the whole C2 region (samples > and all) over to the B2 region (whether I have to outright delete it or > not), with all dimensionsj and samples referenced intact and without having > to manually remap those samples. Then if I am not missing anything, what you probably want to do in this case instead is: 1. Select region B2. 2. Delete region B2. 3. Drag the boundary of region C2 horizontally such that region C2 would cover the old B2 region. That way you don't have to copy anything. You just enlarge C2's key span. CU Christian |
|
From: Andrew C <cou...@gm...> - 2018-06-11 13:13:56
|
I've used a sample conversion program to convert the already mapped kontakt samples to gigastudio. Samples are mapped such that you have two keys for each drum type (B2 and C2 are hard mallets - exact same samples). The issue I've encountered is that despite the C2 region being mapped perfectly (sample channels, velocity), the B2 has an (unintended) layer dimension with the velocities mapped very oddly over the two layers present in the B2 region. What I'm trying to achieve to just simply copy the whole C2 region (samples and all) over to the B2 region (whether I have to outright delete it or not), with all dimensionsj and samples referenced intact and without having to manually remap those samples. (odd thing is, only the b2 is acting strangely. The soft mallets, flams and rolls in the same instrument do not have any conversion pecularities!) Andrew. On Mon, Jun 11, 2018 at 1:09 PM, Christian Schoenebeck < sch...@li...> wrote: > On Montag, 11. Juni 2018 12:35:35 CEST Andrew C wrote: > > Of dimensions that do get copied, if dimensions exist, it appears loop > > settings and sample references do not get copied. > > That's currently the expected behavior. It intentionally omits the > dimension > type, sample reference, sample tuning and sample loop points. > > The reason is because the common requirement is to leave exactly those > untouched. > > > Could this be changed at some point? Trying to convert Auddict's Drums Of > > The Deep to Gig format, just need a few QOL UX changes on the gigedit > side. > > Maybe you could elaborate what exactly you are trying to achieve, in the > sense > what you want to achieve, not how you want to achieve that. Because maybe > there is some alternative way already to achieve what you want to do. > > CU > Christian > > ------------------------------------------------------------ > ------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Linuxsampler-devel mailing list > Lin...@li... > https://lists.sourceforge.net/lists/listinfo/linuxsampler-devel > |
|
From: Christian S. <sch...@li...> - 2018-06-11 12:09:55
|
On Montag, 11. Juni 2018 12:35:35 CEST Andrew C wrote: > Of dimensions that do get copied, if dimensions exist, it appears loop > settings and sample references do not get copied. That's currently the expected behavior. It intentionally omits the dimension type, sample reference, sample tuning and sample loop points. The reason is because the common requirement is to leave exactly those untouched. > Could this be changed at some point? Trying to convert Auddict's Drums Of > The Deep to Gig format, just need a few QOL UX changes on the gigedit side. Maybe you could elaborate what exactly you are trying to achieve, in the sense what you want to achieve, not how you want to achieve that. Because maybe there is some alternative way already to achieve what you want to do. CU Christian |
161 messages has been excluded from this view by a project administrator.
