|
From: Andrew C <cou...@gm...> - 2018-05-07 12:53:10
|
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. |
|
From: Christian S. <sch...@li...> - 2018-05-07 13:11:59
|
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 |
|
From: Andrew C <cou...@gm...> - 2018-05-07 14:05:23
|
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 > |
|
From: Christian S. <sch...@li...> - 2018-05-07 14:35:31
|
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 |
|
From: Andrew C <cou...@gm...> - 2018-05-07 14:47:50
|
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 > |
|
From: Christian S. <sch...@li...> - 2018-05-07 15:07:26
|
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 |
|
From: Andrew C <cou...@gm...> - 2018-05-09 19:56:41
|
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 > |