Thread: [Linuxsampler-devel] import instruments from directory broken?

SourceForge Headquarters 1320 Columbia Street Suite 310 San Diego, CA 92101 +1 (858) 422-6466

I'm brand new to linuxsampler and was disappointed to find that the 
import-from-directory function for instruments doesn't seem to work.  Is 
this a known issue?  Is there a workaround?

On Tuesday, January 10, 2017 13:41:10 Andrew Dabrowski wrote:
> I'm brand new to linuxsampler and was disappointed to find that the
> import-from-directory function for instruments doesn't seem to work.  Is
> this a known issue?  Is there a workaround?

What exactly are you talking about? Do you mean the instruments DB? And what 
are you using for that attempt, Fantasia? Command line?

CU
Christian

Yes, import-from-dir into the instruments db.  I tried doing it both 
through jsampler and by telneting and using the command line.  Neither 
produced any error but neither added any instruments into the db.

On 01/11/2017 07:15 AM, Christian Schoenebeck wrote:
> On Tuesday, January 10, 2017 13:41:10 Andrew Dabrowski wrote:
>> I'm brand new to linuxsampler and was disappointed to find that the
>> import-from-directory function for instruments doesn't seem to work.  Is
>> this a known issue?  Is there a workaround?
> What exactly are you talking about? Do you mean the instruments DB? And what
> are you using for that attempt, Fantasia? Command line?
>
> CU
> Christian
>
> ------------------------------------------------------------------------------
> Developer Access Program for Intel Xeon Phi Processors
> Access to Intel Xeon Phi processor-based developer platforms.
> With one year of Intel Parallel Studio XE.
> Training and support from Colfax.
> Order your platform today. http://sdm.link/xeonphi
> _______________________________________________
> Linuxsampler-devel mailing list
> Lin...@li...
> https://lists.sourceforge.net/lists/listinfo/linuxsampler-devel

Yes, I think that's the same bug, thanks for the clue.  I'll get the 
source code and try the fix suggested.

On 01/11/2017 02:14 AM, Robert Schneider wrote:
> Hi Andrew,
>
> is that the same issue that I posted in the linuxsampler forum 
> http://bb.linuxsampler.org/viewtopic.php?f=6&t=3352&sid=94125c1e809888e5e4f69de90040fc07
>
> There is a fix for it in the reply dated 16.10.2016 16:36
> InstrumentsDb.cpp#1654:
> int res = sqlite3_bind_text(pStmt, Index, Text.c_str(), -1, 
> SQLITE_TRANSIENT);
>
> It was acknowledged to be the proper fix. Wonder that it hasn't made 
> it into the code yet.
>
> Regards
> On 10.01.2017 19:41, Andrew Dabrowski wrote:
>> I'm brand new to linuxsampler and was disappointed to find that the 
>> import-from-directory function for instruments doesn't seem to work.  
>> Is this a known issue?  Is there a workaround?
>>
>>
>> ------------------------------------------------------------------------------
>> Developer Access Program for Intel Xeon Phi Processors
>> Access to Intel Xeon Phi processor-based developer platforms.
>> With one year of Intel Parallel Studio XE.
>> Training and support from Colfax.
>> Order your platform today.http://sdm.link/xeonphi
>>
>>
>> _______________________________________________
>> Linuxsampler-devel mailing list
>> Lin...@li...
>> https://lists.sourceforge.net/lists/listinfo/linuxsampler-devel
>
>
> -- 
> Robert Schneider
> Am Rebhuhnfeld 6
> 85241 Ampermoching
> Fon: +49 8139 92850
> Mobile: +49 176 3892 7669
> Ema...@ar...

OK, I'm on Arch linux and I just replaced linuxsampler by linuxsampler-svn.

I see that that the suggested fix is in the svn code already.

But I still have the same problem, whether I use jsampler or the command 
line I can't get linuxsampler to add anything to the instruments db.

On 01/11/2017 02:14 AM, Robert Schneider wrote:
> Hi Andrew,
>
> is that the same issue that I posted in the linuxsampler forum 
> http://bb.linuxsampler.org/viewtopic.php?f=6&t=3352&sid=94125c1e809888e5e4f69de90040fc07
>
> There is a fix for it in the reply dated 16.10.2016 16:36
> InstrumentsDb.cpp#1654:
> int res = sqlite3_bind_text(pStmt, Index, Text.c_str(), -1, 
> SQLITE_TRANSIENT);
>
> It was acknowledged to be the proper fix. Wonder that it hasn't made 
> it into the code yet.
>
> Regards
> On 10.01.2017 19:41, Andrew Dabrowski wrote:
>> I'm brand new to linuxsampler and was disappointed to find that the 
>> import-from-directory function for instruments doesn't seem to work.  
>> Is this a known issue?  Is there a workaround?
>>
>>
>> ------------------------------------------------------------------------------
>> Developer Access Program for Intel Xeon Phi Processors
>> Access to Intel Xeon Phi processor-based developer platforms.
>> With one year of Intel Parallel Studio XE.
>> Training and support from Colfax.
>> Order your platform today.http://sdm.link/xeonphi
>>
>>
>> _______________________________________________
>> Linuxsampler-devel mailing list
>> Lin...@li...
>> https://lists.sourceforge.net/lists/listinfo/linuxsampler-devel
>
>
> -- 
> Robert Schneider
> Am Rebhuhnfeld 6
> 85241 Ampermoching
> Fon: +49 8139 92850
> Mobile: +49 176 3892 7669
> Ema...@ar...

On Wednesday, January 11, 2017 22:52:54 Andrew Dabrowski wrote:
> OK, I'm on Arch linux and I just replaced linuxsampler by linuxsampler-svn.
> 
> I see that that the suggested fix is in the svn code already.
> 
> But I still have the same problem, whether I use jsampler or the command
> line I can't get linuxsampler to add anything to the instruments db.

The mentioned instruments DB fix which is already applied to the SVN version, 
addressed undefined behavior when accessing the instruments data base. That 
bug caused things like corrupt database and crashes.

However I guess your issue is something else: you are trying to scan a 
directory with sfz files, right?

CU
Christian

Bingo, sfz files.  They're a problem?  I thought linuxsampler had 
advanced support for that format.

I hope I won't have to import the entire Virtual-Playing-Orchestra one 
file at a time.

On 01/12/2017 05:47 AM, Christian Schoenebeck wrote:
> On Wednesday, January 11, 2017 22:52:54 Andrew Dabrowski wrote:
>> OK, I'm on Arch linux and I just replaced linuxsampler by linuxsampler-svn.
>>
>> I see that that the suggested fix is in the svn code already.
>>
>> But I still have the same problem, whether I use jsampler or the command
>> line I can't get linuxsampler to add anything to the instruments db.
> The mentioned instruments DB fix which is already applied to the SVN version,
> addressed undefined behavior when accessing the instruments data base. That
> bug caused things like corrupt database and crashes.
>
> However I guess your issue is something else: you are trying to scan a
> directory with sfz files, right?
>
> CU
> Christian
>
> ------------------------------------------------------------------------------
> Developer Access Program for Intel Xeon Phi Processors
> Access to Intel Xeon Phi processor-based developer platforms.
> With one year of Intel Parallel Studio XE.
> Training and support from Colfax.
> Order your platform today. http://sdm.link/xeonphi
> _______________________________________________
> Linuxsampler-devel mailing list
> Lin...@li...
> https://lists.sourceforge.net/lists/listinfo/linuxsampler-devel

On Thursday, January 12, 2017 13:30:21 Andrew Dabrowski wrote:
> Bingo, sfz files.  They're a problem?  I thought linuxsampler had
> advanced support for that format.

Yeah, it's actually quite simple: sfz files are currently completely ignored 
by the instruments DB. :)

Grigor originally wrote most of the instruments DB and the sfz engine. So I 
don't know why he did not add support for scanning sfz files as well for the 
instruments DB. One reason might be that sfz does not have any way to provide 
meta information (instrument type, genre, author, engineer, copyright, 
keywords, etc.) in contrast to other formats like Giga, DLS, ...

When I find some time, I can add the missing scanner code for sfz files to the 
instruments DB feature. It just needs couple lines of code as far as I can see 
it right now.

CU
Christian

On Thursday, January 12, 2017 20:12:12 Christian Schoenebeck wrote:
> When I find some time, I can add the missing scanner code for sfz files to
> the instruments DB feature. It just needs couple lines of code as far as I
> can see it right now.

Hmm, those original "couple lines" propagated like rabbits, but it is finally 
done. Latest SVN version of LinuxSampler supports scanning .sfz and .sf2 files 
out of the box.

Give it a try!

CU
Christian

Hi,

I tried to import SFZ, GIG and SF2 with the newest build but always get errors. 
Are there any known limitations as to what can be imported and what can not. Has 
anybody already successfully imported a significant amount of SFZ, SF2 or GIG?

Regards,

Robert
On 17.01.2017 00:20, Christian Schoenebeck wrote:
> On Thursday, January 12, 2017 20:12:12 Christian Schoenebeck wrote:
>> When I find some time, I can add the missing scanner code for sfz files to
>> the instruments DB feature. It just needs couple lines of code as far as I
>> can see it right now.
> Hmm, those original "couple lines" propagated like rabbits, but it is finally
> done. Latest SVN version of LinuxSampler supports scanning .sfz and .sf2 files
> out of the box.
>
> Give it a try!
>
> 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

-- 
Robert Schneider
Am Rebhuhnfeld 6
85241 Ampermoching
Fon: +49 8139 92850
Mobile: +49 176 3892 7669
Email Rob...@ar...

On Saturday, January 21, 2017 16:53:54 lin...@ar... wrote:
> I tried to import SFZ, GIG and SF2 with the newest build but always get
> errors. Are there any known limitations as to what can be imported and what
> can not. Has anybody already successfully imported a significant amount of
> SFZ, SF2 or GIG?

The instruments DB feature was orphaned for quite a while. Accordingly there 
might still be bugs to fix. The only way to resolve this, is at least to 
describe and demonstrate the precise issues you encountered, or even better: 
providing a patch for fixing the problem.

CU
Christian