Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - Lustar

Pages: [1] 2 3 ... 34
1
SDSE 2.9.9 is available: download

2box DrumIt Loops fixes and improvements
Big thanks to Daniel from www.ddrum.ch for reporting issues with loops in SDSE and DrumIt Manager. Check out 2B40 if you're looking to easily make music with loops!

Alesis Strike Tip: save memory
For anyone with both a 2box DrumIt and an Alesis Strike module, here's a great trick that was found by Matt Lee: you can enjoy the same memory saving benefits as the Max Tune Up feature from the DrumIt on the Alesis Strike!
- in the new version of SDSE, set Options > Convert > Max tune up to 5
- export some instruments with SDSE and copy them to your Strike SD card
- open the Strike Editor and create your new instruments, making sure to set the 'SEMI' parameter negative to match your max tune setting (for max tune up 5 in SDSE, set SEMI to -5 in the Strike Editor)

Changelog:
  • support for GetGood Drums One Kit Wonder Aggressive Rock, One Kit Wonder Metal and One Kit Wonder Modern Fusion (all with the default Invasion mapping)
  • support for Wavesfactory Legacy Drums with GM mapping (in Legacy Drums settings, articulation control select preset: Mapping_Brush_GM, Mapping_ClassicRock_GM, Mapping_TeaTowel_GM)
  • Convert, Sort in folders: more choice for subfolder \preset, \lib, \VST
  • SSD5.5: support for SSD5.5 v1.2.4 when UI scale is set higher than 100% in the SSD5 settings. export tom rims.
  • SSD4: export HiHat foot splash for David Bendeth, Blackbird, Chris Lord-Alge and Terry Date. export tom rims for Chris Lord-Alge.
  • 2box loops: fixed issue when batch converting from .wav to loop .dsnd - big thanks to Daniel from www.ddrum.ch for reporting this!
  • Convert, 2box: it is now possible to batch convert more than 127 single zone .wav to .dsnd at a time.
  • Convert, Alesis Strike: the Max tune up can now be used with the Strike profile, to save a lot of memory on the Strike.
  • fix to export from Perfect Drums (drums and kits only, sampler is not supported)
  • SD3: better fix to export from SD3 when the sound library contains many presets, or on small screen resolutions (tested on as low as 1024x768) - thanks to Raymond for reporting this issue
  • SD3: fix to export crash bell when cymbal is loaded in a preset using several SDX or EZX - thanks to Al for reporting this
  • VSDSX: support for VSDSX 2.0.2
  • support for REAPER 6.32

2
A new version of DrumIt Manager is available.

Big thanks to Daniel from www.ddrum.ch for reporting issues with loops. Check out 2B40 if you're looking to easily make music with loops!

Changelog:
  • DKit Manager Multi-edit mode: it is now possible to change Kit settings for several kits at once even when they don't have any pads set to the same dsnd instrument - thanks to ddrummer68 for the suggestion
  • DSound Manager Create, Tune: more fixes when creating, tuning and playing Loop .dsnd
  • DSound Manager Create: the Loop check box is replaced by a "Loop" type in the drop down menu to select the type of dsnd to create.
  • DSound Manager Extract: the "restore Pitch" option can now be used to restore the original length of loop samples.
  • DKit Manager, DSound Manager: loops are now played at their original speed (for the first time, they could play a bit too fast in the 2box Editor and DSoundTool)

3
Great! although changing the Windows scale setting to 100% is apparently only needed on some computers (Microsoft Surface) or when using a version of Reaper that wasn't installed and configured by SDSE during setup. The next version will install Reaper 6.29.

4
Sorry for the delay, I didn't see this post and only heard about the issue from someone else two hours ago!
The next version will work with SSD5.5 v1.2.4. It was an issue with the newer SSD5.5 version when the UI scale is set to 125% or 150% in the SSD5 settings. It should already work when it's set to 100% in the current version.

5
Thanks for testing and for the kind words. The added step is the way to go in this case. I should have mentioned it, with the new multi-edit mode the changes are only applied if the new value is different from the default multi-edit value which is based on the first selected kit (except for the dsnd). So if some value from the current kit is already the intended setting to be applied to all the selected kits I would do it in two steps like you did, or change it to something else first before clicking Multi.

6
Hi Bobby,

Thanks for the feedback!

It's a good idea about the multi edit mode, I have sent you a test version with an improved multi edit mode :)
The Multi-edit mode could already be used to adjust the panning, balance or decay in multiple kits at once, but only as long as the pads were set to the same dsnd instrument. In the next version it will also be possible to use the Multi edit mode to change almost all of the Kit values in multiple kits even when the pads are not set to the same dsnd.

7
Thanks for all your feedback Karbonfaiba it's much appreciated. I didn't notice that your post appeared on the forum since we last exchanged mails. Just in case anyone wonders the difference turned out to be dithering noise. It happened in SDSE when using the Max Tune Up option (which is disabled by default) or when converting directly from individual .wav samples to .dsnd (without exporting from a drum VST). In DSound Manager it happened when Max Tune Up was used (disabled by default) or when Maximize wasn't used (enabled by default)



SDSE 2.9.8 is released: download

It supports the new BFD3 version from inMusic, following the migration from fxpansion.com to bfddrums.com.

  • support for more free VSTi from Alan Vista: Clavestinas, Clog Boxes, Cymbalistic, Hand Crash and Thai Gongs.
  • BFD3: support for BFD3 3.4.0.24 from inMusic/bfddrums.com
  • BFD3: support for the Crush expansion.
  • BFD3: support for the rim click articulation for the first five toms (high, mid2, mid, floor 2, floor), set Tom Rim to Rimonly in Options > Zones. mapping is full so removed Perc 11 to 15.
  • 2box Kit: when creating a .dkit file the Decay is now set to 10 by default instead of infinite to help reduce latency.
  • 2box: fixed batch converting .wav samples to Loop .dsnd (when copying .wav samples in "SDSE Sounds", clicking Convert and checking "Convert all to Loop")
  • 2box: disable .wav dithering when Max Tune Up is used or when converting from already split samples, to avoid noise when playing the dsnd when the volume is increased higher than 0 in the Kit or Unit settings - big thanks to Karbonfaiba for reporting this!
  • SD3: fixed issue that prevented exporting from SD3 v3.2.4 when too many presets were installed.
  • SD3: the Ruff articulation can now be exported (enable "Ruff" for the snare in SD3 and set Snare Rim or Snare articulations to "Drag" in the SDSE Options)
  • GetGood Drums Invasion: added Ruff as second zone of the alternate snare, fixed China L mapping and exporting Bell L, Bell R.
  • Kontakt: fix to allow exporting from unsupported sound libraries that use multiple instruments instead of a single instrument (like Core Kit from vi-elements)
  • fixed setting sort folder option to "instr" - thanks to Karbonfaiba for reporting this
  • fixed possible issue after checking REAPER.
  • fixed support for the older version of VSDSX 1.0
  • support for REAPER 6.28

8
Thanks again for making that video Anders!

A new version of DrumIt Manager is available.
  • DSound Manager: fixed Loop option.
  • DSound Manager: disable .wav dithering when Max Tune Up is used or when Maximize is not used, to avoid noise when playing the dsnd when the volume is increased higher than 0 in the Kit or Unit settings - big thanks to Karbonfaiba for reporting this

9
Sharing drum sounds - wav / aiff / rex / Re: BFD3 not working in SDSE
« on: April 23, 2021, 05:15:49 PM »
Hi Digs,

Thanks for your message, I'm afraid my previous mail got caught in the spam folder. I have released the new version with support for BFD3 3.4.024 now.

10
Thanks for reporting this, it will be set correctly to instr in the next version.

That's some interesting experimentation. The Snare Ruff articulation was already supported for SD2 and BFD3 but it wasn't enabled for SD3. The next version will allow to export it from SD3 (enable the Ruff articulation for the snare in SD3 and set Snare Rim or Snare articulations to "Drag" in the SDSE Options)

I'll send you the work in progress version with the fix and support for the Ruff/Drag in SD3.

11
In the Unit settings did you change the pad type of the tom rim to a pad type? Normally when splitting a tom input the rim should be set to a different type than "rim" so that the module treats it as a separate input. It should allow to set any different dsnd for the rim when you select the rim zone (at least on the DrumIt 5)

12
I have tried DKit Manager (the kit bank editor part of DrumIt Manager) with WINE a while ago but it was very slow. But DSound Manager (the other part of DrumIt Manager) might work good enough. I wouldn't expect SDSE to work with WINE on Linux but it should all work nicely in VMware or Virtualbox.

13
It could be more about the average sample lengths found in a kit, or possibly some pieces, rather than the total size of a kit. The hihat and cymbals are more likely to reach the limits, the hihat because it's usually the biggest dsnd file in a kit and cymbals because they can contain very long samples. I would compare the samples lengths with the pieces that worked for your setup and try to match them. You can double click on a dsnd to open it in DSound Manager (or right click on a pad button in a kit in DKit Manager and select Edit) then click on the Layers buttons for each zone on the right and check the maximum length of the zones at the bottom. I would compare the lengths of the zones you're more likely to play when you noticed the latency (for instance the closed hihat) and also the max tune (most 2box sounds use 4 but some hihats use 5, 6, 7)

14
General 2box Drumit 5 forum / Re: 2box mk2 problem
« on: March 17, 2021, 11:44:52 AM »
Hi, did you try with the same Unit settings on both modules? You could try copying your old DrumIt.dkit kit bank and kit to the new module and switch to it to see if it makes a difference. Another way would be to use my program DKit Manager to import your Unit settings to the new kit bank of the 5mk2.

It very much could be the SD card. Did you have the external SD card reader modification installed on the original DrumIt 5 and if so did you try the old SD card in the new DrumIt 5mk2?
If you didn't have the mod installed and you don't mind opening your original DrumIt 5 (it's quite safe there's a guide here) you could take its SD card and try it in your new 5mk2.

15
General 2Box Drumit 3 Forum / Re: Odd delay problem
« on: March 17, 2021, 11:34:55 AM »
The size of the sounds has to be related to how much data the module can read or process at a time. The SD card must affect how fast it can read new samples. The SD card can limit all this first if it's slower than what the module can do, and when the SD card is fast enough it looks like the module can reach a limit when processing sounds. It's not supposed to but when it was found that reducing Decay from infinite to 10 made a difference it seemed to confirm that somehow there's something about it.

That's good to know about the 1 minute dsnd. A while ago I did some tests with someone that reported the worst case of latency. We tested different versions of the same kit and it turned out that for him it wasn't the size of the individual dsnd from a kit that mattered. It would do the same even with a kit made from 1 sample per zone. It was only when reducing the length of the samples that it made a difference so it seemed to be the average length of all samples that he could play at a time. It was quite low for his setup, he could only play kits with short samples. He used acoustic triggers (home made if I remember correctly) and had to use x-talk settings due to vibrations.

It would be nice to have some test kits made from public domain samples that could be used as a benchmark. It would be a kit bank with a few test kits from long to short sample length (1 sample per zone, and another series of the same with many samples per zone). This way the results could be compared with the same kits and same Unit settings.

Pages: [1] 2 3 ... 34