News:

2box forum: accident-free since the last one.

Main Menu
Menu

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.

Show posts Menu

Messages - fishmonkey

#31
Quote from: 510man on July 02, 2015, 02:41:20 PM
the ddrum4 hihat works but does not work according to the MIDI standard. Is there a 2box MIDI note chart somewhere?

yes, the default MIDI channels and notes are in the manual. not in the 1.3 addendum, but the full 1.2x manual.

you can also change the channels and notes.
#32
Quote from: JoeMcc on July 03, 2015, 03:57:00 AM
I should have said something sooner....

indeed it would have been good to have declared your personal interest in the first post...
#34
General 2box Drumit 5 forum / Re: Recording 2Box
June 25, 2015, 06:29:51 AM
what is your budget? and how many channels do you want to record simultaneously?
#35
Quote from: Devious123 on June 17, 2015, 09:35:21 PM
Another ? there is a section in the high hat midi (unit-hped) area that refers midi "Set here the controller format for the foot controller of the hihat. you can choose between cc1 (modulation wheel) and cc4 (pedal control). Page 51. Could you enlighten me on how these two parameters effect recording/ or the drumit units hihat.

the right settings for those hi-hat MIDI parameters depends on what software (or hardware) drum sampler you are wanting to trigger with the MIDI data, and how you have it set up.

the CC setting is used to choose which MIDI Control Change number the hi-hat pedal position is being transmitted on. some CC numbers have conventional names and uses (e.g. CC1 corresponds with the modulation wheel that is usually found on a digital keyboard). CC1 or CC4 are commonly used for hi-hat pedal position messages.

after that you have two pairs of settings which do two things: firstly, they choose the polarity of the pedal height messages, i.e. whether pedal up is 0 and pedal down is 127, or vice versa. secondly, they determine if the pedal position should be sent continuously, or only in the vicinity of actual hi-hat strikes. if the drum sampler supports it, the continuous setting generally gives better hi-hat control, but at the expense of generating much more MIDI data.

note that these MIDI settings do not affect the performance of the internal drum sampler in the Drumit Five module. however they are very important if you are wanting to record the MIDI and/or use it to trigger external software or hardware...
#36
it sounds like maybe you don't know the difference between MIDI and audio...

MIDI is digital information that is used to encode and transmit musical information, it has no 'sound'. at its most basic, MIDI information describes when notes turn on and off, note values, note velocities (like a digital score). then there are various other controls and more advanced signals that it can also contain. to make actual sound from MIDI, either a software synthesiser or sampler interprets the MIDI information and creates audio.

when recording from the module you can choose to record MIDI information and/or the audio produced by the sampler inside the module. to use the MIDI recording, however, you will need to run drum sampler software inside a DAW to turn the MIDI into actual audio that you can hear.
#37
there is no harm using a separate USB-MIDI interface. just bear in mind that like anything else the quality of MIDI interfaces varies. oh, and there is no such thing as MIDI -> XLR.

if you are recording audio directly from the module, then you will want an interface that as at least 2 line inputs, for stereo left + right. having extra inputs allows you to keep more parts of the kit separate, like you would if you were miking up a real kit.
#38
Quote from: Devious123 on June 06, 2015, 10:31:03 AM
I was also wondering if the unit is always sending midi. I noticed that the unit has a option for "thru" which says it disables the onboard sound engine. Does this option need to be on to send midi out?

no, that option does not need to be on to send MIDI as well.
#39
a heads up that the XLN Audio stuff (Addictive Drums, etc.) is currently 50% off:

https://www.jrrshop.com/xln-audio?dir=asc&order=name
#40
Quote from: zorg on May 19, 2015, 01:47:35 AM
Cool cheers for that, can I ask what is BFD and do i need it for this? I have SDSE and Reaper but never heard of BFD 1 2 or 3??

Cheers Jason.

BFD is one of the best software drum samplers for acoustic drum sounds:

http://www.fxpansion.com/index.php?page=30&tab=99

BFD Eco is the cut-down version, and BFD3 is the current full-blown version.

The expansions, such as the Zildjian cymbal packs, are add-on packs of drum samples that load into the software.

when you buy BFD Eco or BFD3  you get standalone and plugin versions. when using SDSE to build DSNDs for the 2Box module, you load the plugin version inside Reaper as the DAW host.

in a nutshell, SDSE controls Reaper, triggering the drum sounds using the BFD plugin, recording the subsequent audio output from the plugin, and processing it with DSoundTool to create files that the 2Box module understands.

alternatives to BFD include Superior Drummer, Addictive Drums, etc.
#41
Quote from: tower of p on May 17, 2015, 10:55:09 PM
Hi!
Have you been looking in "username/library/application support"? this library is a hidden folder, you must make it visible first (easiest way is to use an app called "tinker tool").

otherwise I have no clue, sorry!  ;D

cheers!
Lutz

when in the Finder, hold down the Option key and click on the Go menu. your user library will then automagically appear...
#42
these new interfaces look handy for the situation you are talking about:

http://www.keithmcmillen.com/products/k-mix/
#43
Quote from: Coda on May 05, 2015, 03:19:20 PM
That's definitely a good chip (SOIC) for this kind of thing, it's got every peripheral including LCD controller and sophisticated interrupts system built in. It's not particularly fast compared to reasonable modern ARM based SIOCs (single core @190Mhz vs 4-cores @1-2ghz), but it's enough to get the job done. That SDRAM chip is 16mbit (2MByte) according to my datasheets. So definitely not useful as anything other than a cache for streaming digital audio.
One thing that disappoints me a little, and I'm sure I'll be in the minority group by saying this, that 2box didn't make use of the built-in CF interface which is tons faster than any SDCard could be (The SDCARD interface is maximum 4 bits wide, while CF is 16 bits and is IDE compatible). It might have made your 'working memory card' hunts a bit more successful.

good info, thanks.

interesting to know that using CF cards was an option with that chip. i guess they decided it was a bit cheaper to use SD cards, and the performance was sufficient for the sounds they were using. future proofing with the CF card interface would have definitely been better for us tinkerers though...
#44
Drumit Next Gen / Re: Expand the HArdware
May 01, 2015, 04:54:52 AM
i think it is very likely that the next version of the 2 Box module will have a faster processor, more RAM on board, a faster storage system, and of course a faster USB system.

i'm sure that 2Box have already hit the limits of the amount and quality of realtime processing that can be done on the sounds. the module will need more RAM and processing power to support, for example, better delays and reverbs...
#45
Quote from: Jman on April 29, 2015, 06:06:54 PM
Actually the 2Box system is different. This is from a former thread at another forum I posted in:

I think you missed just how different this module is and what the SD card does. As an example, the OS version, all kit and instrument configurations plus all your large instrument samples, everything you think would be transferred to "RAM" resides on the card. Change the card and in about 7 seconds you have everything new that is on your new card, whatever samples, OS, kit configuration, etc. etc. is all there, not transferred, residing on the card.

This is a quote from an interview, 2009 I think .... translated from Swedish:


Rik has developed a technology that lets us stream directly from the memory card so that you can access all the sounds in real time.


The latency issue some have experienced is from introducing it via the extender plus the card. That is why the right combo is absolutely essential. And also the reason 2Box hasn't provided access to the card outside the module. This has been discussed in other threads, like this one:
http://www.2box-forum.com/index.php/topic,1136.0.html

actually there is nothing unusual about streaming the sounds from the card, in fact almost all hardware and software samplers do something similar. the thing is the audio data will be streamed into a RAM buffer of some sort. all other things being equal, a larger buffer improves how much data can be reliably streamed. more RAM is always better, since accessing the data from RAM is orders of magnitude faster than reading it from disk/card. i would be surprised if the module doesn't also cache recently used samples in RAM.

also, when you boot the module, it is very likely that one of the first things that happens is that the OS is completely loaded into RAM.

an SD card extender in good condition should not affect streaming performance, however a bad cable or connection would mess things up. it is also possible that the extender might be more susceptible to electromagnetic interference.

the issue with the cards themselves is that it is impossible to know what the real-world transfer speeds and access times will be without actually testing one.

the upsides of streaming the audio are that you can change kits very quickly, and you can use kits that are too big to fit into whatever RAM is available. some downsides are that the performance of the card reading system has a critical impact on latency, and the amount of real-time processing that can be done on the sounds without causing unacceptable latency is more limited.