14 Oct
2008
14 Oct
'08
12:31 p.m.
My suggestion about the filebrowser made me think about another feature
which would makes this app more easy to use for beginning home studio
recording musicians....
Easy access to instruments like fluidsynth/ whysynth using dssi etc.
and maybe the (experimental) plugin for Linuxsampler?
14 Oct
14 Oct
2:16 p.m.
Grammostola Rosea wrote:
My suggestion about the filebrowser made me think
about another feature
which would makes this app more easy to use for beginning home studio
recording musicians....
Easy access to instruments like fluidsynth/ whysynth using dssi etc.
and maybe the (experimental) plugin for Linuxsampler?
(dssi) instrument access is already supported to some extent in
qtractor. after you insert a dssi plugin into a midi track you get
access to its instruments (aka midi programs) in the track properties
dialog.
try and tell me whether you have something else better in mind :)
byee
--
rncbc aka Rui Nuno Capela
rncbc(a)rncbc.org
9:43 p.m.
Rui Nuno Capela wrote:
Grammostola Rosea wrote:
Uh....maybe somthing like Rosegarden has it?
My suggestion about the filebrowser made me think
about another
feature which would makes this app more easy to use for beginning
home studio recording musicians....
Easy access to instruments like fluidsynth/ whysynth using dssi
etc. and maybe the (experimental) plugin for Linuxsampler?
(dssi) instrument access is already supported to some extent in
qtractor. after you insert a dssi plugin into a midi track you get
access to its instruments (aka midi programs) in the track properties
dialog.
try and tell me whether you have something else better in mind :)
15 Oct
15 Oct
6:17 a.m.
Grammostola Rosea wrote:
Rui Nuno Capela wrote:
and what do you think is wrong with qtractor's?
under qtractor, dssi plugins are treated as any other plugin (ladspa,
vst). however as an instrument plugin (dssi, vsti) it only makes sense
when inserted in a midi track, of course.
additionally, you can chain the instrument audio audio output through
other fx plugins in-place. that's why you get to insert audio plugins
(ladspa, vst) in a midi track. ah, you can even have multiple instrument
plugins in a midi track, but remember that only the last active one will
have an audible audio output ;)
as said, you can select the midi program/instrument while in the track
properties dialog where you can choose which to assign from a drop-down
list. this is provided even without you firing up the plugins gui, which
will work as well btw :)
maybe i'm missing your point, you tell me
--
rncbc aka Rui Nuno Capela
rncbc(a)rncbc.org
Grammostola Rosea wrote:
Uh....maybe somthing like Rosegarden has it?
My suggestion about the filebrowser made me think
about another
feature which would makes this app more easy to use for beginning
home studio recording musicians....
Easy access to instruments like fluidsynth/ whysynth using dssi
etc. and maybe the (experimental) plugin for Linuxsampler?
(dssi) instrument access is already supported to some extent in
qtractor. after you insert a dssi plugin into a midi track you get
access to its instruments (aka midi programs) in the track properties
dialog.
try and tell me whether you have something else better in mind :)
7:23 a.m.
Rui Nuno Capela wrote:
Grammostola Rosea wrote:
When I start Hexter for example on
the normal way (not as plugin) I see
what instrument belongs to what program no. . That's also the case in
Rosegarden. I doesn't see that as I open it in qtractor...
Maybe that's my point and maybe giving the program no names will improve
things..(?)
BTW. are you planning to support LASH with your great apps?
Rui Nuno Capela wrote:
and what do you think is wrong with qtractor's?
under qtractor, dssi plugins are treated as any other plugin (ladspa,
vst). however as an instrument plugin (dssi, vsti) it only makes sense
when inserted in a midi track, of course.
additionally, you can chain the instrument audio audio output through
other fx plugins in-place. that's why you get to insert audio plugins
(ladspa, vst) in a midi track. ah, you can even have multiple
instrument plugins in a midi track, but remember that only the last
active one will have an audible audio output ;)
as said, you can select the midi program/instrument while in the track
properties dialog where you can choose which to assign from a
drop-down list. this is provided even without you firing up the
plugins gui, which will work as well btw :)
maybe i'm missing your point, you tell me Grammostola Rosea wrote:
Uh....maybe somthing like Rosegarden has it?
My suggestion about the filebrowser made me think
about another
feature which would makes this app more easy to use for beginning
home studio recording musicians....
Easy access to instruments like fluidsynth/ whysynth using dssi
etc. and maybe the (experimental) plugin for Linuxsampler?
(dssi) instrument access is already supported to some extent in
qtractor. after you insert a dssi plugin into a midi track you get
access to its instruments (aka midi programs) in the track
properties dialog.
try and tell me whether you have something else better in mind :)
7:54 a.m.
Grammostola Rosea wrote:
Rui Nuno Capela wrote:
when you open/insert a plugin in qtractor you'll see the generic
plugin form. plugins that implement their own gui most certainly will
have this generic form empty, that is, with no sliders to tweak plugin
parameters. if then you wish to launch the plugin dedicated gui (if one
is provided) you'll have to go through the "Edit" button or respective
context menu item. there you'll see some particular option to
select instrument programs and that should be the case for hexter as
well, probably (i'm not sure, can't confirm atm.)
again in qtractor, you can select the instrument/program without going
through the gui editor. while in track properties you can do that
exactly as you would do for any other midi instrument (eg. outboard
hardware) for which you have a cakewalk instrument definition file
setup. otoh, instrument plugins provide its own midi program map, no
need for a .ins definition file ;)
Grammostola Rosea wrote:
When I start Hexter for example on
the normal way (not as plugin) I see
what instrument belongs to what program no. . That's also the case in
Rosegarden. I doesn't see that as I open it in qtractor... Rui Nuno Capela wrote:
and what do you think is wrong with qtractor's?
under qtractor, dssi plugins are treated as any other plugin (ladspa,
vst). however as an instrument plugin (dssi, vsti) it only makes sense
when inserted in a midi track, of course.
additionally, you can chain the instrument audio audio output through
other fx plugins in-place. that's why you get to insert audio plugins
(ladspa, vst) in a midi track. ah, you can even have multiple
instrument plugins in a midi track, but remember that only the last
active one will have an audible audio output ;)
as said, you can select the midi program/instrument while in the track
properties dialog where you can choose which to assign from a
drop-down list. this is provided even without you firing up the
plugins gui, which will work as well btw :)
maybe i'm missing your point, you tell me Grammostola Rosea wrote:
> My suggestion about the filebrowser made me think about another
> feature which would makes this app more easy to use for beginning
> home studio recording musicians....
>
> Easy access to instruments like fluidsynth/ whysynth using dssi
> etc. and maybe the (experimental) plugin for Linuxsampler?
>
(dssi) instrument access is already supported to some extent in
qtractor. after you insert a dssi plugin into a midi track you get
access to its instruments (aka midi programs) in the track
properties dialog.
try and tell me whether you have something else better in mind :)
Uh....maybe somthing like Rosegarden has it?
Maybe that's my point and maybe giving the program
no names will improve
things..(?)
no names? now i've missed it, again :/
BTW. are you planning to support LASH with your great apps?
yes, i have that plan in some dusty shelf. still waiting for this new
lash generation :P
cheers
--
rncbc aka Rui Nuno Capela
rncbc(a)rncbc.org
8:31 a.m.
Rui Nuno Capela wrote:
Would be great!
Another little gui thing I have with your latest version.
The names in the menu: file, Edit, Track, View etc. are not displayed
totally. I've Fil , Edi , Trac , Viev ,
The last letters of the names are displayed half...
Grammostola Rosea wrote:
Sorry, vague language. I mean program
numbers > names of instruments
But it is solved now. When I have selected a dssi in the tab 'plugin'
and I go to the tab 'track', at that point only the program numbers are
displayed!!!
But when I mouse click on 'Hexter ...' below Midi/ instrument (on the
right of 'channel') I see the instrument names...
This is somewhat vague cause the name of Hexter seems already
selected... (it is strange for me that I have to mouse click it before I
see the instruments instead of just numbers)...
Rui Nuno Capela wrote:
when you open/insert a plugin in qtractor you'll see the generic
plugin form. plugins that implement their own gui most certainly will
have this generic form empty, that is, with no sliders to tweak plugin
parameters. if then you wish to launch the plugin dedicated gui (if
one is provided) you'll have to go through the "Edit" button or
respective
context menu item. there you'll see some particular option to
select instrument programs and that should be the case for hexter as
well, probably (i'm not sure, can't confirm atm.)
again in qtractor, you can select the instrument/program without going
through the gui editor. while in track properties you can do that
exactly as you would do for any other midi instrument (eg. outboard
hardware) for which you have a cakewalk instrument definition file
setup. otoh, instrument plugins provide its own midi program map, no
need for a .ins definition file ;)
Grammostola Rosea wrote:
When I start Hexter for example on
the normal way (not as plugin) I
see what instrument belongs to what program no. . That's also the
case in Rosegarden. I doesn't see that as I open it in qtractor... Rui Nuno Capela wrote:
> Grammostola Rosea wrote:
>> My suggestion about the filebrowser made me think about another
>> feature which would makes this app more easy to use for
>> beginning home studio recording musicians....
>>
>> Easy access to instruments like fluidsynth/ whysynth using dssi
>> etc. and maybe the (experimental) plugin for Linuxsampler?
>>
> (dssi) instrument access is already supported to some extent in
> qtractor. after you insert a dssi plugin into a midi track you get
> access to its instruments (aka midi programs) in the track
> properties dialog.
>
> try and tell me whether you have something else better in mind :)
>
>
Uh....maybe somthing like Rosegarden has it?
and what do you think is wrong with qtractor's?
under qtractor, dssi plugins are treated as any other plugin
(ladspa, vst). however as an instrument plugin (dssi, vsti) it only
makes sense when inserted in a midi track, of course.
additionally, you can chain the instrument audio audio output
through other fx plugins in-place. that's why you get to insert
audio plugins (ladspa, vst) in a midi track. ah, you can even have
multiple instrument plugins in a midi track, but remember that only
the last active one will have an audible audio output ;)
as said, you can select the midi program/instrument while in the
track properties dialog where you can choose which to assign from a
drop-down list. this is provided even without you firing up the
plugins gui, which will work as well btw :)
maybe i'm missing your point, you tell me Maybe that's my point and maybe giving the
program no names will
improve things..(?)
no names? now i've missed it, again :/
BTW. are you planning to support LASH with your great apps?
yes, i have that plan in some dusty shelf. still waiting for this new
lash generation :P
11:22 a.m.
Grammostola Rosea wrote:
But it is solved now. When I have selected a dssi in the tab 'plugin'
and I go to the tab 'track', at that point only the program numbers are
displayed!!!
But when I mouse click on 'Hexter ...' below Midi/ instrument (on the
right of 'channel') I see the instrument names...
good grief :)
This is somewhat vague cause the name of Hexter seems
already
selected... (it is strange for me that I have to mouse click it before I
see the instruments instead of just numbers)...
you have to select something before it gets actually assigned ;)
Another little gui thing I have with your latest version.
The names in the menu: file, Edit, Track, View etc. are not displayed
totally. I've Fil , Edi , Trac , Viev ,
The last letters of the names are displayed half...
that's a very (well?) known issue due on Qt >= 4.4
try changing the base font size in View/Options.../Display/Options/Base
font size, to something else than "(default)" that is
cheers
--
rncbc aka Rui Nuno Capela
rncbc(a)rncbc.org
11:27 a.m.
Rui Nuno Capela wrote:
Ok, I'll try that.
Thanks :)
Grammostola Rosea wrote:
If it could
without that mouse-click it would be more intuitive and user
friendly IMHO
But it is solved now. When I have selected a dssi in the tab 'plugin'
and I go to the tab 'track', at that point only the program numbers
are displayed!!!
But when I mouse click on 'Hexter ...' below Midi/ instrument (on the
right of 'channel') I see the instrument names...
good grief :)
This is somewhat vague cause the name of Hexter
seems already
selected... (it is strange for me that I have to mouse click it
before I see the instruments instead of just numbers)...
you have to select something before it gets actually assigned ;)
Another little gui thing I have with your latest version.
The names in the menu: file, Edit, Track, View etc. are not displayed
totally. I've Fil , Edi , Trac , Viev ,
The last letters of the names are displayed half...
that's a very (well?) known issue due on Qt >= 4.4
try changing the base font size in
View/Options.../Display/Options/Base font size, to something else than
"(default)" that is
5884
days inactive
5885
days old
linux-audio-user@lists.linuxaudio.org
8 comments
2 participants
participants (2)
-
Grammostola Rosea -
Rui Nuno Capela