Bug 7580 - Package request qsampler (a graphical interface for linuxsampler)
Summary: Package request qsampler (a graphical interface for linuxsampler)
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: New RPM package request (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL: http://www.linuxsampler.org/
Whiteboard:
Keywords:
Depends on: 7575 7576 7579
Blocks:
  Show dependency treegraph
 
Reported: 2012-09-26 01:13 CEST by Philippe Didier
Modified: 2012-11-15 03:07 CET (History)
1 user (show)

See Also:
Source RPM: qsampler-0.2.2
CVE:
Status comment:


Attachments
spec file (adapted from Mandriva's ) (1.66 KB, text/x-rpm-spec)
2012-09-26 01:16 CEST, Philippe Didier
Details
patch file to modify the qsampler.pro (makefile to built program on qt-devel) (453 bytes, patch)
2012-09-26 01:18 CEST, Philippe Didier
Details | Diff
spec file for the last svn 2342 (1.75 KB, text/x-rpm-spec)
2012-09-30 20:16 CEST, Philippe Didier
Details
cleaner spec file for the last svn 2342 (1.65 KB, text/plain)
2012-11-13 17:27 CET, Philippe Didier
Details

Description Philippe Didier 2012-09-26 01:13:32 CEST
It was provided by Mandriva 2010.2

Graphical User Interface for Linuxsampler

I provide the spec file and patch to build on Mageia

CAUTION !!!!!

It sometimes segfault ... Known upstream bug when built with the last versions of qt4-devel and used with last Mageia2 version of KDE
Comment 1 Philippe Didier 2012-09-26 01:16:29 CEST
Created attachment 2860 [details]
spec file (adapted from Mandriva's )
Comment 2 Philippe Didier 2012-09-26 01:18:11 CEST
Created attachment 2861 [details]
patch file to modify the qsampler.pro (makefile to built program on qt-devel)
Philippe Didier 2012-09-26 01:19:18 CEST

Depends on: (none) => 7575, 7576, 7579
Source RPM: (none) => qsampler-0.2.2

Philippe Didier 2012-09-26 01:34:27 CEST

URL: (none) => http://www.linuxsampler.org/
Whiteboard: (none) => MGA2TOO

Comment 3 Philippe Didier 2012-09-30 20:16:31 CEST
Created attachment 2886 [details]
spec file for the last svn 2342

NB 
You need to download the last svn revision
Use Make -f Makefile.svn on the downloaded directory
Compress the modified directory in tar.bz format
Name it libqsampler-svn2342.tar.bz2
Then you can use the spec 
no more need to patch the source
Comment 4 Philippe Didier 2012-09-30 20:18:45 CEST
Must be built with the last svn version of linuxsampler
Philippe Didier 2012-10-02 00:31:25 CEST

Summary: Package request qsampler => Package request qsampler (a graphical interface for linuxsampler)

Comment 5 Philippe Didier 2012-11-13 17:27:18 CET
Created attachment 3089 [details]
cleaner spec file for the last svn 2342

Hi Barry

here a cleaner spec file (no mix of spaces and tabs)
(perhaps some BuildRequires still missing)

no more patch needed ...
I obsolete the old stuff

You will have to use a magic script to download and tar the source from svn
(no need to run "make -f Makefile.svn" : a Makefile.in is already provided in the trunk) 

If linuxsampler could be built, 
 this GUI the best way to use it

Thanks for your work ...

Philippe

Attachment 2860 is obsolete: 0 => 1
Attachment 2861 is obsolete: 0 => 1
Attachment 2886 is obsolete: 0 => 1

Comment 6 Barry Jackson 2012-11-14 01:17:59 CET
qsampler is now in Cauldron

Thanks Philippe.

I tried to test it by loading a .gig file, however it seems not to recognize it, so I am probably doing something wrong. It just spews out errors.
qsampler seems to be looking for "LSCP Session files" not .gig files so I have no clue at the moment :\

The GUI looks fine though ;)

Closing as fixed but please reply with how to test it - thanks.

Status: NEW => RESOLVED
CC: (none) => zen25000
Resolution: (none) => FIXED
Whiteboard: MGA2TOO => (none)

Comment 7 Philippe Didier 2012-11-14 19:26:48 CET
OK
LSCP sessions files are files containing written configurations for Qsampler (and linuxsampler)
When you have created a configuration you may save it as *.lscp file.

A) The first time you use Qsampler it's not configured at all.

1)
You must start qjackctrl first
2)
then qsampler
3)
You will see linuxsampler appearing in jack connection windows
create a connection in audio tab (from linuxsampler to audio output)
create a connection in alsa tab (or midi tab) from any keyboard to linuxsampler
(a virtual keyboard such as vkeybd provided by Mageia may used)
or from a sequencer (Rosegarden) to linuxsampler

4)In Qsampler main windows 
a)
seventh icon gives access to devices configuration
create an audio device
create a MIDI device
b)
eighth icon gives access to a channel creation for these devices
You can choose your engine (sf2 or gig) and the sample file you want to use
When it's loaded (for big files it may take 4 or 5 seconds)
Qsampler is ready

You can use it... now

You may even create several channels for your devices with different instrument in each channel

5)
If its fine you may save this Qsampler configuration (menu : file/ submenu : save => this will create a *.lscp file)


B)
next times you use Qsampler, you'll only have to open this *.lscp file (from menu : file / submenu : open ) wait a little, and ... nothing else to do than play !
You can create as much *.lscp files as you want .. depending on the sample files you want to use...



PS I found easier to inactivate PulseAudio... to directly use my soundcard (with MIDI inputs outputs, wavetables in its own memory, audio in and out ) through hard basical configuration files (automatically loading modules, soundfonts, configurating alsa and using a RT kernel )
 and qjackctrl
I had bad experiences with Mandriva and Pulseaudio... and I always apply the same thing that I did then (I know that it works fine).

But I don't know if it's OK now for Mageia with Pulseaudio and JACK ?
Comment 8 Philippe Didier 2012-11-14 19:43:03 CET
PS
Beware to properly stop Qsampler :
Menu : file / submenu : exit

It takes a little time to stop...
You are asked in a window if you want to stop the linuxsampler session : say yes !


If you quit Qsampler by only closing its window (upper right corner cross) linuxsampler will continue running !!!
and you will have to stop it through ksysguard...
Comment 9 Barry Jackson 2012-11-14 21:43:51 CET
Hmm failed at 1. I don't have qjackctl installed.

If qjackctl (I spent ages looking for qjackctrl BTW) is required then do we have a missing Requires or maybe Suggests?

I tried to follow your step by step, but I really have no idea what I am doing with this, so I think it would be better if you can get a Cauldron machine running to do some testing.
Comment 10 Philippe Didier 2012-11-14 23:45:18 CET
sorry for the typo :
it's qjackctl indeed not qjackctrl ... my bad !

qjackctl is only a GUI for jackit (jackit is already a Require for linuxsampler) 


qjackctl is not a Require, not even a Suggest for qsampler in any distribution (fedora mandriva debian...)

But I think this missing didn't appear to anyone installing Qsampler : 
qjackctl is a very useful basis for computer music and is even required by other softs (ardour for instance) so it is very often already installed when you install and use Qsampler.

You may eventually add qjackctl as a Suggest but it is not an absolute Require,
(some masochists can use a console and the command line to configure jackit, and will tell you it is not a Require...)


In a first time, (before having a Cauldron machine) I download your srpms and build rpms from them inside Mageia2... and test them ...

I don't think I can try Cauldron in a virtual machine to test Qsampler on it (I am not sure that jackit can use hardware through a virtual machine because this brings too much latency...)

Thanks again...
Comment 11 Barry Jackson 2012-11-15 01:29:14 CET
OK all understood.
Do you not have some HD space to install Cauldron in another partition?
Comment 12 Philippe Didier 2012-11-15 02:55:38 CET
OK on Mageia2 !
1)
I downloaded your srpms 
gig
liblscp
linuxsampler
qsampler
2)
built rpms and installed them one after one (the BuildRequire for uuid is OK)

everything is fine... I can play a Grand Piano gig sample with vkbrd or with an external MIDI keyboard

3)
uninstall linuxsampler and qsampler
4)
I then resolved the lv2 bug 7639 on my system (I had already built my own lv2 rpms, just have to install them)
5)
uncomment the lines in spec file of linuxsampler
build it again
install its rpm
6)
build and install qsampler rpm

everything is fine with lv2 plugin support !

Don't know yet if it's good for Cauldron ; but indeed your srpms could be backported fluently into Mageia2 and that's a good omen !

Thanks again for your patience, goodwilling and wiseness !
Regards
Comment 13 Philippe Didier 2012-11-15 03:07:10 CET
Post Scriptum (off topic)

About a Cauldron installation on a partition
I hesitate to do that on my everyday computer... (a solid tower)

I have had a very very bad experience with cooker, with damages on all file systems, long time ago (Mandriva 2006 perhaps, I don't remember well...) and promised to myself to never never use again a work in progress on my computer ! 


I only use stable and rock solid distributions  on dedicated partitions,
and before switching from an old to a new I test it for a long time...
I have 4 distributions installed which means
4 root partitions 
and sub partitions such as /home or /usr for each of them
-Mandriva 2008.1 (used until Mandriva 2010.1 is mature and quite bugless)
-Mandriva 2010.2 (used until Mageia2 is mature)
-Debian squeeze (I have tested it in parallel with Mageia when I understood that Mandriva was dying and when  Mageia1 was not mature enough )
-Mageia2 that is now my everyday distribution 

(I always added some homemade rpms until the specs or srpms that I propose are backported, or updated but I don't work no more on cooker nor cauldron )

I longly tested Mandriva 2009, 2009.1, 2010.0 and never used them, staying stuck with Mandriva 2008.1 until Mandriva 2010.1...

My Mandriva 2008.1 partitions will be erased, and used for Mageia3, stable... to be tested before being adopted...

Safety first for me ! 
That may look a little selfish ... but I try to cooperate anyway  ;)

Note You need to log in before you can comment on or make changes to this bug.