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
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
On 10/24/2013 05:42 PM, Brian Clem wrote:
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!
The
I still refer to Macs as Apple. I have Apple iie scares on the brain. I
stay far away from apples and lucky number 7's.
On Thu, Oct 24, 2013 at 6:33 PM, D. Michael McIntyre
rosegarden.trumpe...@gmail.com wrote:
On 10/24/2013 05:42 PM, Brian Clem wrote:
Just like Studio_to_Go! used a VST
Of course the trouble with running a release build to avoid all the Qt
fatal warnings problems is that you can no longer provide useful
backtraces. All the stuff in () would have been the clues to what lines
in the source code triggered what.
Since you've removed that qt-at-spi package, you
I reproduced the crash, I think. I cheated. I set up one plugin and
then copied and pasted and hand hacked the XML in the autoload, so I
wouldn't have to use the awful GTK+ file picker dialog 24 times. The
effect is having 24 plugins set up the same. Indeed, I didn't get too
far before
I was stable at 10. That is a fine compromise in the short term. I have
about 400 Christmas midi files to wade through and having a set group
of(10) quality sf2 is pretty good. Later, hopefully by Thursday's end, I
plan on adding one more until I have an accurate unstable number.
I will
