I finally got all 24 slots working and I made a backup of the autoload.rc
and emailed it to my other computers. Now things are set and opening my
midi files and setting the voices with the sf2 I want is almost
effortless.
I had to switch after number 13 to the Calf version of Fluidsynth. I didnt
do this in the most scientific method but in my case, it started acting
squirrelly adding more with regular (or whatever its called, no disrespect
meant) Fludisynth.
This, to me, is a triumphic moment. It is closest to the Rosegarden
version for Windows that works out_of_the_box. Please dont throw-up in
your mouth. I am just saying that when I ran the Rosegarden Windows
version it played my midi file without any setup. Ultimately, the ease of
use in the windows version is due to the lack of synth choices etc...
I know how Studio_to_Go! worked. Running Qsynth when starting jack. This
is a similar way to achieve what I wanted. But I had issues getting qsynth
to remember my settings and it didnt like when I loaded up the sf2 files (I
mean LOADED... lots... ). Others probably have this system down. Its
probably way more logical and "Linux" to do it this way. .... But I just
choose to do a more ridged setup. I printed out my list of 24 instruments
and now I dont have to read much when selecting the synth voice.
What if I found very_small_footprint sf2 files that would reside in a SVN
build. Not MEGA banks... or things like that. I have some super small sf2
that are individual instruments. (Found the sf2's from things I learned
from the Rosegarden wiki :) Would it be worth making a separate branch?
Is that crazy talk? Been there, done that? (Yes, I swear I remember this
has been tried before... and I think I remember this topic coming up before
... maybe 5 years ago?) My question is just in the interest of helping
the beginner get working faster.
Just like Studio_to_Go! used a VST and SF2 folder in the home directory and
it would scan the folders and work. Maybe that is built into RG code to
scan these locations? If you answer that, its no longer magic, so maybe I
dont need to know!
----->>OR<<------
Is this something that should be approached from a distro level? Maybe I
should ask the good people at AVLinux?
On Thu, Oct 24, 2013 at 3:35 PM, Holger Marzen <[email protected]> wrote:
> On Tue, 22 Oct 2013, Brian Clem wrote:
>
> > At least that is what I was working on. Setting my synth instruments and
> > then saving the default studio file. All synths were Fluidsynth dssi.
> 1-
> > 24. I assigned each number to a different sf2 I have saved in my dropbox
> > on every computer so the setup will be the same when working. A quick
> > start every time when working. But it failed when using all 24 spots.
> > Here is the info.
> >
> > Program terminated with signal 11, Segmentation fault.
>
> I didn't have a crash but muted voices. My solution was to increase
> FSD_CHANNEL_COUNT in fluidsynth-dssi.h to the desired number of
> instances/instruments plus 1. Don't ask me why plus 1. I often stumble
> over off-by-ones.
>
------------------------------------------------------------------------------
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60135991&iu=/4140/ostg.clktrk
_______________________________________________
Rosegarden-user mailing list
[email protected] - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-user
