[Linuxsampler-devel] [linuxsampler-devel] Bug? Removing a sample from a dimension with 'all regions' selected only affects current region

[Andrew C]

Not sure if this is a bug or intended behaviour, but if I remove a sample
from a dimension and have 'all regions' selected, only that particular
region's dimension is affected.

Andrew.

[Christian Schoenebeck]

Post by Andrew C
Not sure if this is a bug or intended behaviour, but if I remove a sample
from a dimension and have 'all regions' selected, only that particular
region's dimension is affected.

Yes, that's most probably a bug, or rather I forgot to implement the "for all"
behavior for that specific feature, because assigning a null sample is not
used that often, so I never stumbled over this being still missing.

CU
Christian

[Andrew C]

Thanks for that, Christian!

On a related note, is there any relatively painless way to automatically
combine a) a multi-velocity instrument patch with b) a set of
multi-velocity release samples?
The thought of having to manually drag and drop release triggers for
multiple velocities is quite daunting to put it lightly.

Andrew.

On Sat, Jul 8, 2017 at 6:22 PM, Christian Schoenebeck <

Post by Christian Schoenebeck

Post by Andrew C
Not sure if this is a bug or intended behaviour, but if I remove a sample
from a dimension and have 'all regions' selected, only that particular
region's dimension is affected.

Yes, that's most probably a bug, or rather I forgot to implement the "for all"
behavior for that specific feature, because assigning a null sample is not
used that often, so I never stumbled over this being still missing.
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
https://lists.sourceforge.net/lists/listinfo/linuxsampler-devel

[Christian Schoenebeck]

Post by Andrew C
Thanks for that, Christian!
On a related note, is there any relatively painless way to automatically
combine a) a multi-velocity instrument patch with b) a set of
multi-velocity release samples?
The thought of having to manually drag and drop release triggers for
multiple velocities is quite daunting to put it lightly.

Sure, use the "combine" tool. Main menu of gigedit -> Tools -> Combine
Instruments. Then Ctrl click on the two instruments you want to combine,
select the release trigger dimension as the dimension to combine them and
click on Ok.

Note that the sequence of the selected instruments matters. So make sure the
instrument with the regular samples is in the instruments list before the
instrument with the release samples. If that's not the case use drag and drop
on the instruments list to correct this sequence before using the combine
tool.

Tip: if the combine tool causes any issues like samples are missing in the
combined instrument, then combine the two instruments with the "layer"
dimension first, then afterwards select the newly combined instrument, double
click any region, the region's dimension manager dialog will popup, check the
"Alll regions" checkbox and then change the layer dimension type to release
trigger dimension type.

That should do it.

CU
Christian

[Andrew C]

Thanks! That worked out perfectly for me.
I had looked at the Maestro concert grand gig file last night to try and
work out what 'order' to combine the instruments, thinking I had to do the
release trigger layer first, then the velocity and it was giving me all
kinds of headaches.

Guess I was doing it completely backwards! :)

On Sun, Jul 9, 2017 at 11:29 AM, Christian Schoenebeck <

Post by Christian Schoenebeck

Post by Andrew C
Thanks for that, Christian!
On a related note, is there any relatively painless way to automatically
combine a) a multi-velocity instrument patch with b) a set of
multi-velocity release samples?
The thought of having to manually drag and drop release triggers for
multiple velocities is quite daunting to put it lightly.

Sure, use the "combine" tool. Main menu of gigedit -> Tools -> Combine
Instruments. Then Ctrl click on the two instruments you want to combine,
select the release trigger dimension as the dimension to combine them and
click on Ok.
Note that the sequence of the selected instruments matters. So make sure the
instrument with the regular samples is in the instruments list before the
instrument with the release samples. If that's not the case use drag and drop
on the instruments list to correct this sequence before using the combine
tool.
Tip: if the combine tool causes any issues like samples are missing in the
combined instrument, then combine the two instruments with the "layer"
dimension first, then afterwards select the newly combined instrument, double
click any region, the region's dimension manager dialog will popup, check the
"Alll regions" checkbox and then change the layer dimension type to release
trigger dimension type.
That should do it.
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
https://lists.sourceforge.net/lists/listinfo/linuxsampler-devel

[Christian Schoenebeck]

Post by Andrew C
Thanks! That worked out perfectly for me.
I had looked at the Maestro concert grand gig file last night to try and
work out what 'order' to combine the instruments, thinking I had to do the
release trigger layer first, then the velocity and it was giving me all
kinds of headaches.
Guess I was doing it completely backwards! :)

Yeah, the point here is that you currently cannot change the order directly
within the combine tool dialog itself. So it does not matter for instance
which one of the instruments you select first in the combine tool dialog. So
yes, that has to be improved or at least there should be some note that you
must change the order in the instruments list first before calling the combine
dialog.

CU
Christian

[Christian Schoenebeck]

Post by Christian Schoenebeck

Post by Andrew C
Thanks! That worked out perfectly for me.
I had looked at the Maestro concert grand gig file last night to try and
work out what 'order' to combine the instruments, thinking I had to do the
release trigger layer first, then the velocity and it was giving me all
kinds of headaches.
Guess I was doing it completely backwards! :)

Yeah, the point here is that you currently cannot change the order directly
within the combine tool dialog itself. So it does not matter for instance
which one of the instruments you select first in the combine tool dialog. So
yes, that has to be improved or at least there should be some note that you
must change the order in the instruments list first before calling the
combine dialog.

I just addressed these issues. Now (gigedit 1.0.0.svn55) it is quite
convenient to combine instruments:

1. Simply select the instruments you want to combine directly from the main
window's instrument list by Ctrl clicking on them.

2. Use the new keyboard shortcut Ctrl + j (for "join"), or open the combine
tool dialog manually from the menu. Now the combine tool dialog pops up and
the instruments are already pre-selected.

3. At the bottom of the combine tool dialog there is now a new horizontal
list, showing you the currently selected items. Use drag & drop to alter
the sequence in which they are going to be combined.

4. Click "Ok". The dialog disappears and the instrument list automatically
scrolls to the newly added (combined) instrument.

CU
Christian

[Andrew C]

Great! Thank you for the fix and extended functionality. This makes it alot
easier for me!

P.S Did you get my e-mail with the lscp-to-idf script and transitionfx giga
file?

Thanks!

On Sun, Jul 9, 2017 at 7:32 PM, Christian Schoenebeck <

Post by Christian Schoenebeck

Post by Christian Schoenebeck

Post by Andrew C
Thanks! That worked out perfectly for me.
I had looked at the Maestro concert grand gig file last night to try

and

Post by Christian Schoenebeck

Post by Andrew C
work out what 'order' to combine the instruments, thinking I had to do

the

Post by Christian Schoenebeck

Post by Andrew C
release trigger layer first, then the velocity and it was giving me all
kinds of headaches.
Guess I was doing it completely backwards! :)

Yeah, the point here is that you currently cannot change the order

directly

Post by Christian Schoenebeck
within the combine tool dialog itself. So it does not matter for instance
which one of the instruments you select first in the combine tool

dialog. So

Post by Christian Schoenebeck
yes, that has to be improved or at least there should be some note that

you

Post by Christian Schoenebeck
must change the order in the instruments list first before calling the
combine dialog.

I just addressed these issues. Now (gigedit 1.0.0.svn55) it is quite
1. Simply select the instruments you want to combine directly from the main
window's instrument list by Ctrl clicking on them.
2. Use the new keyboard shortcut Ctrl + j (for "join"), or open the combine
tool dialog manually from the menu. Now the combine tool dialog pops up and
the instruments are already pre-selected.
3. At the bottom of the combine tool dialog there is now a new horizontal
list, showing you the currently selected items. Use drag & drop to alter
the sequence in which they are going to be combined.
4. Click "Ok". The dialog disappears and the instrument list automatically
scrolls to the newly added (combined) instrument.
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
https://lists.sourceforge.net/lists/listinfo/linuxsampler-devel

[Christian Schoenebeck]

Post by Andrew C
Great! Thank you for the fix and extended functionality. This makes it alot
easier for me!
P.S Did you get my e-mail with the lscp-to-idf script and transitionfx giga
file?

I admit I received it, but forgot to upload it to an appropriate place yet. I
try to do that during this week.

CU
Christian

[Christian Schoenebeck]

Post by Christian Schoenebeck

Post by Andrew C
Great! Thank you for the fix and extended functionality. This makes it alot
easier for me!
P.S Did you get my e-mail with the lscp-to-idf script and transitionfx giga
file?

I admit I received it, but forgot to upload it to an appropriate place yet.
I try to do that during this week.

Done:

http://doc.linuxsampler.org/lscp2idf/

https://www.linuxsampler.org/misc/lscp2idf/lscp2idf.tar.bz2

http://svn.linuxsampler.org/cgi-bin/viewvc.cgi/doc/docbase/lscp2idf/

Thanks!

CU
Christian