linuxsampler-devel — This list is for discussing LinuxSampler development issues and ideas

Re: [Linuxsampler-devel] [linuxsampler-devel] Copying dimension region?

[Andrew C <cou...@gm...>]

Hi,

I understand I can copy the regions, but what I'm talking about is entire
dimensions:

I cannot copy a whole region's dimensions to a new region. Nothing happens
if I alt C and alt V to a newly created region (dimensions should be made
automatically?)

Of dimensions that do get copied, if dimensions exist, it appears loop
settings and sample references do not get copied.

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.

Thanks,

Andrew.

On Mon 11 Jun 2018, 11:37 Christian Schoenebeck, <
sch...@li...> wrote:

> On Sonntag, 10. Juni 2018 21:34:32 CEST Andrew C wrote:
> > How do I copy whole dimension regions to a new key/region in gigedit?
> > Referenced samples, dimension types, EG/LFO/Pitch settings, etc?
>
> 1. Select the dimension region you want top copy.
>
> 2. Hit Alt + C (or select "Copy selected dimension region" from the main
> menu).
>
> 3. The dimension region is now on the clipboard. Optionally you may now
> alter
> the copied dimension region directly on the clipboard by hitting Alt + X
> (or
> by selecting "Adjust Clipboard Conent" from the main menu).
>
> 4. Select the target dimension region(s) (which may be i.e. on another
> instrument).
>
> 5. Hit Alt + V to paste the clipboard content to the selected dimension
> region(s) (or select "Paste dimension region" from the main menu).
>
> 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
>

Re: [Linuxsampler-devel] [linuxsampler-devel] Copying dimension region?

[Christian S. <sch...@li...>]

On Sonntag, 10. Juni 2018 21:34:32 CEST Andrew C wrote:
> How do I copy whole dimension regions to a new key/region in gigedit?
> Referenced samples, dimension types, EG/LFO/Pitch settings, etc?

1. Select the dimension region you want top copy.

2. Hit Alt + C (or select "Copy selected dimension region" from the main 
menu).

3. The dimension region is now on the clipboard. Optionally you may now alter 
the copied dimension region directly on the clipboard by hitting Alt + X (or 
by selecting "Adjust Clipboard Conent" from the main menu).

4. Select the target dimension region(s) (which may be i.e. on another 
instrument).

5. Hit Alt + V to paste the clipboard content to the selected dimension 
region(s) (or select "Paste dimension region" from the main menu).

CU
Christian

[Linuxsampler-devel] [linuxsampler-devel] Copying dimension region?

[Andrew C <cou...@gm...>]

HI all,

How do I copy whole dimension regions to a new key/region in gigedit?
Referenced samples, dimension types, EG/LFO/Pitch settings, etc?

Thanks,

Andrew.

[Linuxsampler-devel] VSL Performance Set Issue

[Robert O. <rob...@gm...>]

Hello all,

Please excuse me if this is off-topic, unfortunately I am unable to register on the forums due to a visual captcha.

I am trying to make the VSL (Vienna Symphonic Library) performance set to work, with the help of some MidiScripter scripts written for Logic (http://www.3raudio.com/vsl.html <http://www.3raudio.com/vsl.html>) LinuxSampler seems to work great, though loading times could be a bit better :)

As far as I know, group 13 is used for the samples for an initial note, however in the case of some of the Legato sets, this is not true, for instance for the Solo Violin performance patches. Hitting one key on a midi keyboard does not play any note, however transitions to a second note work perfectly.

I am not sure which group is supposed to be used in this situation, thus I would appreciate any help, if anyone came across the same, or a similar issue.
I am also open for conversion, e.g. to SFZ, though I am not sure if there is a tool that could make this possible, without the loss of some mod wheel cross-fades, etc.

All the best,
Rob

Re: [Linuxsampler-devel] [linuxsampler-devel] More verbose instrument DB scanning function?

[Christian S. <sch...@li...>]

On Samstag, 26. Mai 2018 11:00:37 CEST Andrew C wrote:
> Is it possible to get more verbose InstrumentsDB scanning?
> 
> Currently there is no sign from the LS console that the operation has
> started/finished, and the only debug messages that come up are for
> Directories that already exist.

You could raise the sampler's debug level to 2 for getting more verbose output 
of what the instrument DB does when scanning your directories. The debug level 
is currently a compile time option:

	./configure --enable-debug-level=2

CU
Christian

[Linuxsampler-devel] [linuxsampler-devel] More verbose instrument DB scanning function?

[Andrew C <cou...@gm...>]

Hi all,

Is it possible to get more verbose InstrumentsDB scanning?

Currently there is no sign from the LS console that the operation has
started/finished, and the only debug messages that come up are for
Directories that already exist.

Thanks,

Andrew.

Re: [Linuxsampler-devel] Extending number of keys ?

[Christian S. <sch...@li...>]

On Freitag, 25. Mai 2018 16:53:42 CEST Hans Petter Selasky wrote:
> On 05/25/18 15:53, Christian Schoenebeck wrote:
> > so you came up with this idea, correct?
> 
> Yes, for my experiments and projects sake.
> 
> I'll see if I can use some of the described methods instead. Using up
> all the MIDI channels was just a last resort, also latency wise.

Ok, I see. I first thought you are referring to this solution since there might 
be some kind of exotic hardware organ or something that sends these messages 
already. Well under that circumstance I would definitely not use the MIDI 
channel bits for that.

In the end, you can also invent a new MIDI message like "fine tune only the 
next note on this part" (i.e. by picking an arbitrary NRPN or a short SysEx).

Latency was an issue with the old classic DIN MIDI jacks, but it is definitely 
not with todays USB and Bluetooth LE based MIDI connections anymore.

Existing controllers like the previously mentioned "Seaboard" use the 
described method of using pitchbend and MIDI channel distribution simply 
because it would work with most sound expanders and plugins out of the box.

CU
Christian

Re: [Linuxsampler-devel] Extending number of keys ?

[Hans P. S. <hp...@se...>]

On 05/25/18 15:53, Christian Schoenebeck wrote:
> so you came up with this idea, correct?

Yes, for my experiments and projects sake.

I'll see if I can use some of the described methods instead. Using up 
all the MIDI channels was just a last resort, also latency wise.

--HPS

Re: [Linuxsampler-devel] Extending number of keys ?

[Christian S. <sch...@li...>]

On Freitag, 25. Mai 2018 14:15:47 CEST you wrote:
> I didn't know there were MIDI coarse/fine tuning messages and these also
> work realtime? Do you have a reference?

There are actually several standard messages regarding tuning, for example:

1. Standard MIDI Pitchbend message.

2. Roland GS scale tuning SysEx message (tuning individual 12 notes of each 
   octave in cents).

3. MIDI RPN #1 ("fine tuning part in cents").

4. MIDI RPN #2 ("coarse tuning part in half tones").

And as I am looking at it, there are even more tuning related MIDI messages. 
The following might be a starting point for you:

	http://www.somascape.org/midi/tech/spec.html

	http://www.microtonal-synthesis.com/GS_XG.html

And I have to correct my previous email: IIRC the comman way is using actually 
pitch bend messages, not coarse/fine tuning messages (take the "Seaboard" as an 
example of a real world hardware product doing that).

Implementation status of the messages above in LinuxSampler:

1. Supported of course (real-time).

2. Supported (real-time).

3. No supported ATM.

4. Supported (but not real-time ATM, resets part ATM).

> I've made a patch for ZynaddSubFX to do this:
> 
> https://sourceforge.net/p/zynaddsubfx/code/ci/hps-subdivision-feature/tree/
> 
> The reason is that for organ sounds you don't get a phase polluted major
> unless you adjust the tones a bit.

Sound like you are resembling the Hermode Tuning algorithm, which usually uses 
Roland GS ScaleTuning (in real-time) to adjust purity of harmonies (3rd, 5th 
and 7th) in real-time.

But getting back to my actual question; as far I understand you correctly, 
there are no real-world hardware products which use the MIDI channel bits for 
the tuning purpose you described, so you came up with this idea, correct?

CU
Christian

Re: [Linuxsampler-devel] Extending number of keys ?

[Hans P. S. <hp...@se...>]

On 05/25/18 13:11, Christian Schoenebeck wrote:
> On Donnerstag, 24. Mai 2018 11:45:23 CEST Hans Petter Selasky wrote:
>> Is there any interest into extending the number of MIDI keys from 128 to
>> 128 * 16 in LinuxSampler ?
> 
> There is probably no high demand for such a feature. Are there actually any
> real devices which are doing it exactly this way (borrowing from MIDI channel
> bits that is)?
> 
> I mean there are real devices which support a more fine graded note control
> beyond the 128 notes limitation. But usually they do it like this: they send a
> regular note-on (0-127), then they send a regular coarse/fine tuning message
> pair, and if the new note would be a note nr where another note is already
> active on, then they simply send it on another MIDI channel for not changing
> the tuning of the old note.
> 
> CU
> Christian

Hi,

I didn't know there were MIDI coarse/fine tuning messages and these also 
work realtime? Do you have a reference?

I've made a patch for ZynaddSubFX to do this:

https://sourceforge.net/p/zynaddsubfx/code/ci/hps-subdivision-feature/tree/

The reason is that for organ sounds you don't get a phase polluted major 
unless you adjust the tones a bit.

Here is the math:

C-major frequencies:

C = base * pow(2.0, 0 / 12.0)
E = base * pow(2.0, 4 / 12.0)
G = base * pow(2.0, 7 / 12.0)

The base frequency is not relevant, so cancel it.

C-major frequency factors:

C = pow(2.0, 0 / 12.0)
E = pow(2.0, 4 / 12.0)
G = pow(2.0, 7 / 12.0)

Computing all the differential tones in logarithmic scale and get:

12.0 * log(G - C) / log(2) = -12.059   ... 5.9 cent over
12.0 * log(G - E) / log(2) = -24.824   ... 82.4 cent over
12.0 * log(E - C) / log(2) = -23.326   ... 67.4 cent under

12.0 means the 12'th halftone
24.0 means the 24'th halftone
osv.

Trying to rectify this with 96 tones per octave:

C = pow(2.0, 0 / 12.0)
E = pow(2.0, 3 / 12.0 + 7 / 96.0)
G = pow(2.0, 7 / 12.0)

12.0 * log(G - C) / log(2) = -12.059   ... 5.9 cent over (same as before)
12.0 * log(G - E) / log(2) = -24.177   ... 17.6 cent over
12.0 * log(E - C) / log(2) = -23.941   ... 5.9 cent under (identical 
error - cancels)

Examples with samples from Nord Electro adjusted using aduacity:

http://home.selasky.org/privat/nord/major_CEG_corrected.mp3
http://home.selasky.org/privat/nord/major_CEG_uncorrected.mp3

Summary in C-major the E shall be reduced by:
(8-7)/96*1200 = 12.5 cent

To reduce phase errors.

--HPS

Re: [Linuxsampler-devel] Extending number of keys ?

[Christian S. <sch...@li...>]

On Donnerstag, 24. Mai 2018 11:45:23 CEST Hans Petter Selasky wrote:
> Is there any interest into extending the number of MIDI keys from 128 to
> 128 * 16 in LinuxSampler ?

There is probably no high demand for such a feature. Are there actually any 
real devices which are doing it exactly this way (borrowing from MIDI channel 
bits that is)?

I mean there are real devices which support a more fine graded note control 
beyond the 128 notes limitation. But usually they do it like this: they send a 
regular note-on (0-127), then they send a regular coarse/fine tuning message 
pair, and if the new note would be a note nr where another note is already 
active on, then they simply send it on another MIDI channel for not changing 
the tuning of the old note.

CU
Christian

[Linuxsampler-devel] Extending number of keys ?

[Hans P. S. <hp...@se...>]

Hi,

Is there any interest into extending the number of MIDI keys from 128 to 
128 * 16 in LinuxSampler ?

The background for this is to have better support non-12-scale music and 
also to have organ sounds clearer especially for majors. The four 
missing bits will be stolen from the channel bits simply for standard 
MIDI, when a special parameter is given to LinuxSampler. This also 
allows to save such music into regular MIDI files and re-play them.

--HPS

Re: [Linuxsampler-devel] [linuxsampler-devel] combining .gig and .gxx files?

[Andrew C <cou...@gm...>]

Still no joy sadly, managed to get the latest version of gtkmm (upgraded to
the latest ubuntu release).

Gigedit reports samples missing when I do "save as" with the latest svn
version on the gigfile.

Andrew.

On Mon, May 7, 2018 at 4:07 PM, Christian Schoenebeck <
sch...@li...> wrote:

> On Montag, 7. Mai 2018 15:47:42 CEST Andrew C wrote:
> > My gtkmm version is 3.18, according to synaptic.
> >
> > I guess it'd be the obvious problem, but I do not have any "gdkmm"
> packages
> > in these 16.04 ubuntu repositories..
>
> It seems Ubuntu wraps both gtkmm and gdkmm into one package
> "libgtkmm-3.0-dev". Make sure you have this package installed. As you can
> see
> it contains the offending header file:
>
> https://packages.ubuntu.com/bionic/amd64/libgtkmm-3.0-dev/filelist
>
> /usr/include/gdkmm-3.0/gdkmm/seat.h
>
> 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
>

Re: [Linuxsampler-devel] Hello and a question: Running LinuxSampler on MacOS High Sierra

[Robert O. <rob...@gm...>]

On 2018. May 8., at 21:47, Christian Schoenebeck <sch...@li...> wrote:
> I think Logic is missing something else. Maybe some new AUv3 methods that are
> not implemented by our AU plugin yet.
I think the AU validation tool became quite aggressive in this regard, and this missing liblinuxsampler.5.dylib might be the issue. Validation does not continue after this, and I get:
FATAL ERROR: OpenAComponent: result: -50,0xFFFFFFCE

> And keep in mind Fantasia and QSampler actually save their sampler session as
> LSCP files as well. So you could also check what they are doing.
Now that I know that the LSCP files can be applied on the command line, they make my life a lot easier. I began working on a utility which allows loading sampler files from the clipboard, as well as display the contained instrument indices, so one can choose which one to load. The next step is to have a load/save feature based on Logic’s window title, so applying various sets of instruments can be a lot easier.

> I just added a command line switch to gigdump for this…
Thank you! I am using it now extensively.

> If you don't like the precise output, let me know. I can still tweak it easily
> for what you might need.
I think it works well. The right parenthesis and the quotes are probably not necessary, but I can parse the output easily.

All the best,
Rob

Re: [Linuxsampler-devel] polyphonic/key aftertouch support

[Christian S. <sch...@li...>]

On Montag, 7. Mai 2018 16:44:51 CEST redtide wrote:
> I would like to know if polyphonic aftertouch is supported/can be
> handled in LS in some way; it is used by some electronic drum modules
> for cymbal choking and dual/three zone cymbals.

No sorry, the SFZ engine currently ignores polyphonic key pressure. Only the 
more common channel aftertouch is supported by the engines ATM.

There are already methods in place in all engines to process polyphonic 
afterouch, but those methods are currently simply empty in all engines. The 
problem is simply that almost no manufacturer still makes keyboards with 
polyphonic aftertouch.

CU
Christian

Re: [Linuxsampler-devel] Hello and a question: Running LinuxSampler on MacOS High Sierra

[Christian S. <sch...@li...>]

On Samstag, 5. Mai 2018 14:52:10 CEST Robert O. wrote:
> Here’s the relevant log entry:
> 
> Error loading
> /Library/Audio/Plug-Ins/Components/LinuxSamplerAU.component/Contents/MacOS/
> LinuxSamplerAU: 
> dlopen(/Library/Audio/Plug-Ins/Components/LinuxSamplerAU.component/Contents
> /MacOS/LinuxSamplerAU, 262): Library not loaded:
> /home/persson/mac/x86_64/lib/linuxsampler/liblinuxsampler.5.dylib
> Referenced from:
> /Library/Audio/Plug-Ins/Components/LinuxSamplerAU.component/Contents/MacOS/
> LinuxSamplerAU Reason: image not found

Mmm, that's probably not the real issue here. Or Logic became extremely picky. 
Mac apps (and DLLs) contain an absolute path as well as a relative path for 
the DLLs they need. And this error is just on the absolute path of the 
LinuxSampler DLL, which is usually just ignored. And since you say the plugin 
is running in Logic, it found the LinuxSampler DLL using the relative path.

I think Logic is missing something else. Maybe some new AUv3 methods that are 
not implemented by our AU plugin yet.

> > commands are, which is described in a rather huge document here:
> It seems that I can easily load an instrument from here, if I know the
> index. It should be trivial to hack something together which would query
> the giga files via gigdump and pipe it to the lscp shell. This will be
> really useful when I need to load lots of instruments all at once for a
> Logic project. I’ll give this a go, thank you.

Yes, that's correct. Usually you just need some few basic LSCP commands. We 
also have some short examples on the website, so you don't necessarily need to 
read the entire, bloated LSCP specs document I gave you last time:

http://linuxsampler.org/documentation.html#example_lscp_scripts

And keep in mind Fantasia and QSampler actually save their sampler session as 
LSCP files as well. So you could also check what they are doing.

> > I am not sure how much you usually use command line applications…
> 
> A lot, daily :-)

Well, then that changes the game. :-)

> I can probably use ‘grep' or ‘sift’ to have a list of indexes, however, if
> it is not much work, it would certainly make things a lot easier. The index
> number and its name, similarly to how Fantasia displays it in its dropdown
> would be perfect.

I just added a command line switch to gigdump for this:

gigdump --instrument-names foo.gig

If you don't like the precise output, let me know. I can still tweak it easily 
for what you might need. Just download today's automatic snapshot build, run 
the installer on your Mac and you'll have that gigdump option:

http://download.linuxsampler.org/packages/osx/snapshots/

CU
Christian

Re: [Linuxsampler-devel] [linuxsampler-devel] combining .gig and .gxx files?

[Christian S. <sch...@li...>]

On Montag, 7. Mai 2018 15:47:42 CEST Andrew C wrote:
> My gtkmm version is 3.18, according to synaptic.
> 
> I guess it'd be the obvious problem, but I do not have any "gdkmm" packages
> in these 16.04 ubuntu repositories..

It seems Ubuntu wraps both gtkmm and gdkmm into one package
"libgtkmm-3.0-dev". Make sure you have this package installed. As you can see 
it contains the offending header file:

https://packages.ubuntu.com/bionic/amd64/libgtkmm-3.0-dev/filelist

/usr/include/gdkmm-3.0/gdkmm/seat.h

CU
Christian

Re: [Linuxsampler-devel] [linuxsampler-devel] combining .gig and .gxx files?

[Andrew C <cou...@gm...>]

My gtkmm version is 3.18, according to synaptic.

I guess it'd be the obvious problem, but I do not have any "gdkmm" packages
in these 16.04 ubuntu repositories..

Andrew.

On Mon, May 7, 2018 at 3:35 PM, Christian Schoenebeck <
sch...@li...> wrote:

> On Montag, 7. Mai 2018 15:05:14 CEST Andrew C wrote:
> > What version of gtkmm does the latest svn gigedit require?
>
> gigedit does not require a specific gtk(mm) version. It should compile
> with all
> Gtk(mm) 2 releases, all Gtk(mm) 3 releases, and even with latest (still in
> development) Gtk(mm) 4 git head versions.
>
> Please note that anything starting with Gtk(mm) version >= 3.23.0 and
> higher
> is *not* Gtk(mm) 3, but rather the development version of Gtk(mm) 4. If
> that
> is the case there, don't waste your time, because Gtk 4 is currently
> seriously
> broken, and I don't have the personal expectation that this would change
> anytime soon.
>
> > I'm using
> > version 3.0 and getting the error:
>
> The precise version number is always helpful on gtkmm compilation issues.
> See
> above.
>
> > regionchooser.cpp:30:25: fatal error: gdkmm/seat.h: No such file or
> > directory
> > compilation terminated.
>
> Check if you have the gdkmm header files installed (read carefully: gdkmm,
> yes
> that is a separate package along to gtkmm). That gdkmm/seat.h header file
> exists since Gtkmm release 2.99.1 up to latest Gtkmm 4.
>
> 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
>

[Linuxsampler-devel] polyphonic/key aftertouch support

[redtide <re...@gm...>]

Hi,

I would like to know if polyphonic aftertouch is supported/can be 
handled in LS in some way; it is used by some electronic drum modules 
for cymbal choking and dual/three zone cymbals.

I want to use LS with the SFZ engine.

Best Regards

Re: [Linuxsampler-devel] [linuxsampler-devel] combining .gig and .gxx files?

[Christian S. <sch...@li...>]

On Montag, 7. Mai 2018 15:05:14 CEST Andrew C wrote:
> What version of gtkmm does the latest svn gigedit require? 

gigedit does not require a specific gtk(mm) version. It should compile with all 
Gtk(mm) 2 releases, all Gtk(mm) 3 releases, and even with latest (still in 
development) Gtk(mm) 4 git head versions.

Please note that anything starting with Gtk(mm) version >= 3.23.0 and higher 
is *not* Gtk(mm) 3, but rather the development version of Gtk(mm) 4. If that 
is the case there, don't waste your time, because Gtk 4 is currently seriously 
broken, and I don't have the personal expectation that this would change 
anytime soon.

> I'm using
> version 3.0 and getting the error:

The precise version number is always helpful on gtkmm compilation issues. See 
above.

> regionchooser.cpp:30:25: fatal error: gdkmm/seat.h: No such file or
> directory
> compilation terminated.

Check if you have the gdkmm header files installed (read carefully: gdkmm, yes 
that is a separate package along to gtkmm). That gdkmm/seat.h header file 
exists since Gtkmm release 2.99.1 up to latest Gtkmm 4.

CU
Christian

Re: [Linuxsampler-devel] [linuxsampler-devel] combining .gig and .gxx files?

[Andrew C <cou...@gm...>]

Hi Christian,

What version of gtkmm does the latest svn gigedit require? I'm using
version 3.0 and getting the error:

regionchooser.cpp:30:25: fatal error: gdkmm/seat.h: No such file or
directory
compilation terminated.


Thanks,

Andrew.

On Mon, May 7, 2018 at 2:11 PM, Christian Schoenebeck <
sch...@li...> wrote:

> On Montag, 7. Mai 2018 13:53:02 CEST Andrew C wrote:
> > Hi all,
> >
> > Is it possible to combine .gig and .gx files into one big giga file?
> >
> > Whenever I try "cat thisgig.gig thisgig.gx01 > thisgigbig.gig", gigedit
> > shows there are samples missing from the resulting file, so I'm obviously
> > doing something wrong?
>
> Yes, that "cat" approach would definitely not work, because gig files are
> using
> the tree based "RIFF" format as fundamental layout. So libgig would not
> see
> anything that you manually appended to the file with cat.
>
> I haven't tried yet, but theoretically you can just open the original gig
> file
> i.e. with gigedit, then select "Save as ..." and save it with a *new* file
> name. It should then automatically store the entire bunch of gig and gx
> files
> as one new, large gig file instead. That's one of the new features in
> libgig 4.1.0, writing files larger than 4 GB. Like written in the release
> notes
> though, you won't be able to load those gig files > 4 GB with GigaStudio
> though:
>
> http://doc.linuxsampler.org/Release_Notes/LinuxSampler_2_1_0/#libgig_4_1_0
>
> 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
>

Re: [Linuxsampler-devel] [linuxsampler-devel] combining .gig and .gxx files?

[Christian S. <sch...@li...>]

On Montag, 7. Mai 2018 13:53:02 CEST Andrew C wrote:
> Hi all,
> 
> Is it possible to combine .gig and .gx files into one big giga file?
> 
> Whenever I try "cat thisgig.gig thisgig.gx01 > thisgigbig.gig", gigedit
> shows there are samples missing from the resulting file, so I'm obviously
> doing something wrong?

Yes, that "cat" approach would definitely not work, because gig files are using 
the tree based "RIFF" format as fundamental layout. So libgig would not see 
anything that you manually appended to the file with cat.

I haven't tried yet, but theoretically you can just open the original gig file 
i.e. with gigedit, then select "Save as ..." and save it with a *new* file 
name. It should then automatically store the entire bunch of gig and gx files 
as one new, large gig file instead. That's one of the new features in
libgig 4.1.0, writing files larger than 4 GB. Like written in the release notes 
though, you won't be able to load those gig files > 4 GB with GigaStudio 
though:

http://doc.linuxsampler.org/Release_Notes/LinuxSampler_2_1_0/#libgig_4_1_0

CU
Christian

[Linuxsampler-devel] [linuxsampler-devel] combining .gig and .gxx files?

[Andrew C <cou...@gm...>]

Hi all,

Is it possible to combine .gig and .gx files into one big giga file?

Whenever I try "cat thisgig.gig thisgig.gx01 > thisgigbig.gig", gigedit
shows there are samples missing from the resulting file, so I'm obviously
doing something wrong?

Andrew.

Re: [Linuxsampler-devel] Hello and a question: Running LinuxSampler on MacOS High Sierra

[Robert O. <rob...@gm...>]

On 2018. May 5., at 13:18, Christian Schoenebeck <sch...@li...> wrote:
> The Mac's "Console" utility might also give
> a clue in this case what Logic dislikes exactly about the LinuxSampler AU.
Here’s the relevant log entry:

Error loading /Library/Audio/Plug-Ins/Components/LinuxSamplerAU.component/Contents/MacOS/LinuxSamplerAU:  dlopen(/Library/Audio/Plug-Ins/Components/LinuxSamplerAU.component/Contents/MacOS/LinuxSamplerAU, 262): Library not loaded: /home/persson/mac/x86_64/lib/linuxsampler/liblinuxsampler.5.dylib
  Referenced from: /Library/Audio/Plug-Ins/Components/LinuxSamplerAU.component/Contents/MacOS/LinuxSamplerAU
  Reason: image not found
FATAL ERROR: OpenAComponent: result: -50,0xFFFFFFCE

> But there is for example the command line application “lscp”...essentially a shell…
This is exactly what I need, thank you!

> … you would still need to learn at least the basics of what those
> commands are, which is described in a rather huge document here:
It seems that I can easily load an instrument from here, if I know the index. It should be trivial to hack something together which would query the giga files via gigdump and pipe it to the lscp shell. This will be really useful when I need to load lots of instruments all at once for a Logic project. I’ll give this a go, thank you.

> I am not sure how much you usually use command line applications…
A lot, daily :-)

> I could add you a command line
> switch to gigdump such that it only prints you a list of instruments if that
> would help you.
I can probably use ‘grep' or ‘sift’ to have a list of indexes, however, if it is not much work, it would certainly make things a lot easier. The index number and its name, similarly to how Fantasia displays it in its dropdown would be perfect.

> ... the Qt
> library needs to be updated on our automatic build server. That takes a while
> because it requires us manual cross compilation and dealing with couple issues
> on our server. But I could do that somewhere next week or so.
That would be amazing, thank you. With the combination of Gigdump and the LSCP shell, plus Fantasia occasionally, I feel that this is not quite important, but it is certainly a welcome addition.
As always, your help is very much appreciated!

All the best,
Rob

Re: [Linuxsampler-devel] Hello and a question: Running LinuxSampler on MacOS High Sierra

[Christian S. <sch...@li...>]

On Freitag, 4. Mai 2018 13:42:32 CEST Robert O. wrote:
> That did it. I was able to load and play a patch from the Garritan
> Orchestra. Logic’s incompatible plugin warning shows up at every startup,
> but at least it works now. Huge thanks for your help!

The AU plugin certainly could get an update. Probably it lacks something from 
the current AU version 3 standard. The Mac's "Console" utility might also give 
a clue in this case what Logic dislikes exactly about the LinuxSampler AU.

> I am wondering, is there a way to control the engine via the command line,
> or via other means besides the two frontends? Unfortunately, choosing an
> instrument index in the loaded file in Fantasia is quite cumbersome with
> VoiceOver, as it pops up a separate window. Other parts, such as the
> directory browser are also not exposing their content properly.

There is not an Ncurses based frontent if you mean that (that is a terminal 
application which you could easily navigate with just arrow keys and enter). 
But there is for example the command line application "lscp" which is 
essentially a shell, that is you have to type text commands to the sampler 
backend with the keyboard and the shell assists you with type completion of 
those commands:

http://doc.linuxsampler.org/LSCP_Shell/

However even though this console application assists you with typing those 
commands. you would still need to learn at least the basics of what those 
commands are, which is described in a rather huge document here:

http://www.linuxsampler.org/api/draft-linuxsampler-protocol.html

> Essentially, since I have a few hundred giga files, what I would like is a
> way to print the available indexes and to load an instrument via that index
> from a .gig file. This can be through the database as well.

I am not sure how much you usually use command line applications, but you 
could use the command line application "gigdump" for this. Like the previously 
mentioned "lscp" application, these are some of a bunch of command line tools 
that are automatically installed along to the sampler. There are much more 
like command line tools for file format conversion etc. Each one is coming with 
a user manual. Type i.e. "man gigdump" on the terminal to see more.

The problem for you however is probably that "gigdump" actually dumps a load 
of information, not only the instrument names, but almost everything that is 
stored in the .gig file, like individual instrument patch parameters, all the 
samples, their loop points and so on. But I could add you a command line 
switch to gigdump such that it only prints you a list of instruments if that 
would help you.

> QSampler might work better, however, it fails to start on my system. From
> the console:
> 
> Termination Reason:    DYLD, [0x1] Library missing
> Dyld Error Message:
>   Library not loaded: /home/*/libgig.7.dylib
>   Referenced from:
> /Applications/LinuxSampler/qsampler.app/Contents/MacOS/qsampler Reason:
> image not found

Yes, QSampler would probably suit you better, because it should come with 
VoiceOver support right out of the box since it is based on the Qt UI library 
and since QSampler is not using custom UI skin features and the like, in 
contrast to Fantasia. However QSampler currently does not support the sampler 
backend's instruments DB feature yet.

The reason why QSampler is currently not running on your Mac is because the Qt 
library needs to be updated on our automatic build server. That takes a while 
because it requires us manual cross compilation and dealing with couple issues 
on our server. But I could do that somewhere next week or so.

CU
Christian