Helpful ReplyMidi - should it go or should it stay ?

Page: < 12345 > Showing page 4 of 5
Author
rabeach
Max Output Level: -48 dBFS
  • Total Posts : 2703
  • Joined: 2004/01/26 14:56:13
  • Status: offline
Re: Midi - should it go or should it stay ? 2018/03/01 22:58:43 (permalink)
Control voltage (CV and Gate) has grown on me since I started building analog synths but no way that I'm aware to interface a PC without MIDI to CV converter. MIDI is a technical standard for a communication protocol so it is here to stay.
#91
Fantasmaviajero
Max Output Level: -90 dBFS
  • Total Posts : 4
  • Joined: 2017/11/27 00:50:38
  • Status: offline
Re: Midi - should it go or should it stay ? 2018/03/01 23:16:23 (permalink)
I would like to keep midi.
#92
abacab
Max Output Level: -30.5 dBFS
  • Total Posts : 4464
  • Joined: 2014/12/31 19:34:07
  • Status: offline
Re: Midi - should it go or should it stay ? 2018/03/02 00:14:12 (permalink)
MacFurse
 
for some time I've heard nothing good about midi and Sonar, only bad. From almost every aspect, it cops a bagging.

 
Not sure who you have been listening to, but the MIDI implementation that Cakewalk has developed is easily one of the best ever seen on a PC.  There are many who have been lobbying for improvements, but definitely not bagging it!
 
Cakewalk, Cubase, and Logic are the main DAWs that earned their pedigrees as MIDI sequencers for PC and/or Mac platforms, and that later added DAW capabilities.  So they are MIDI at the core.  Other DAWs came along later that were focused exclusively on audio recording, but were forced to bolt MIDI on later.  IMHO they were late to the game and never quite "got it" as far as deep MIDI support was concerned.  But I assume that the successful ones will catch up eventually...
 

I really wanted to know whether the main users of Sonar want the new owners to push the boundaries of midi within their new platform, to take it to the forefront of DAWS. Do that, and maybe this DAW can finally make it to the 'pro' world, where it currently isn't. It needs an area to shine. This thread may help in highlighting just that.
 


I agree.  Keep pushing the boundaries! And there are a few pros using Sonar, it's just not highly publicized. 
 
Good things will come! 

DAW: CbB; Sonar Platinum, and others ... 
#93
brandonc
Max Output Level: -89 dBFS
  • Total Posts : 65
  • Joined: 2015/08/27 23:01:04
  • Status: offline
Re: Midi - should it go or should it stay ? 2018/03/02 00:25:20 (permalink)
is this topic just for fun (to be FUNNY)??? We(musicians,producers,home recording enthusiast's,etc.) have spent thousands and thousands of dollars on Drum , Synth ,Piano ,Bass , Orchestra , Choir , etc . vst's that we ( I ) use all day, Everyday!!!!  I'm a guitar player that spent the 90's recording with my electric guitar, Roland XP50( for drums and keyboard sounds ) and a Radio Shack Realistic 4 channel mixer running into a Tascam Porta 02 ,MIXED DOWN to MY BIG SISTER's TAPE DECK !! Back then I always DREAMED of what would be capable for the home musician in the future. NOW WE ( I ) HAVE IT!!! I am NOT very midi smart , I am able to do what I need to do. There is Pro's & Con's to almost everything. I am having the "TIME of MY LIFE" playing with all the tool's at my disposal !!!!! THANK YOU TECHNOLOGY!!! THANK YOU MIDI !!!
#94
iRelevant
Max Output Level: -82 dBFS
  • Total Posts : 430
  • Joined: 2017/10/25 21:14:48
  • Location: Norway
  • Status: offline
Re: Midi - should it go or should it stay ? 2018/03/02 14:54:24 (permalink)
Stay.
#95
doncolga
Max Output Level: -60 dBFS
  • Total Posts : 1519
  • Joined: 2006/01/03 17:15:48
  • Location: Statesboro, GA USA
  • Status: offline
Re: Midi - should it go or should it stay ? 2018/03/02 15:06:10 (permalink)
MacFurse
Should the owners make midi better in Sonar, or kill it off, leaving it for the DAWS that excel in that area, paving the way for better sample and loop control ?



I thought Sonar was considered as having among the very best MIDI.

HP Z220 Workstation I7 3770, 8 GB RAM, Windows 10, Sonar Platinum, RME Multiface II via PCIe, JBL 4326 w/sub, AvanTone MixCubes
#96
Midiboy
Max Output Level: -82 dBFS
  • Total Posts : 414
  • Joined: 2015/01/14 09:29:54
  • Location: Northwood
  • Status: offline
Re: Midi - should it go or should it stay ? 2018/03/02 15:57:26 (permalink)
To the OP,
 
I didn't quote you since your reply to me was on page one.  You had mentioned that I was being a little dismissive.  I do apologize, that wasn't my intention.  I was thinking you meant MIDI as a whole...when you meant more for MIDI Editing within a DAW.  Please accept my apology. 
 
I agree with the general consensus though that MIDI needs to be included in any modern daw (as with at least some sort of ability to use MIDI Editing).  

When I play out live, I actually use Sonar with it's MIDI capabilities along with Komplete Kontrol Controller Editor to get my sounds.  I Create a playlist within the Controller Editor.  I have every sound setup as a separate MIDI channel within Sonar.  For each song, I hit the "next button" on my Komplete Kontrol which then advanced the playlist in the editor, which then refers to one of the 16 tracks I have setup in Sonar for my sounds.  It can also manage splits and everything.  If I need more than 16 different sounds during a set, than that is where the playlist comes into play with Sonar as well.  

I use MIDI extensively in my recordings as well for programming my drums, and any sequencer patterns I want to create.  I often edit the MIDI (albeit simple editing) for velocity and various mods.  

Now, I do do electronic music (hehe I said do do), but I also do rock as well.  I am not a guitar player, but use Impact Soundworks Shreddage Guitar, bass and drums.  Their guitar is so stinking realistic, I have had guitar players ask me who played the guitar and be blown away when they found out it was synth.  I do a LOT of MIDI editing for guitar work as Impact Soundworks guitar is not really an easy guitar to play live as it triggers on various MIDI CCs and velocities, so you typically have to go back in and edit various things to be within the trigger points.  Some of the triggers have wide ranges, but some of the ranges in and of themselves have different articulations within the same range.  (For example, harmonics might kick in with the modwheel between 70-100, but the higher the number, the more pronounced the sound).  So yes, I do a lot of editing.  They even state that the guitar synth is not ideal for playing live, and is more for recording. With Sonar, the editing is super easy.  I also use Studio One, and while some people think there is absolutely no editing for MIDI, they would be wrong. I do find it easier in Sonar though. 

If DAWS stopped supporting MIDI, then it is likely I wouldn't be nearly as productive. 

----
Gregg
Midiboy Music
www.facebook.com/midiboygregg
 
Win10x64 (Eng), Sonar Platinum x64 (Eng w/ lifetime updates), 32GB DDR4 RAM, Intel i7 5820, nVidia 960, Alesis MultiMix 8 USB2 w/ Alesis MultiMix driver. Native Instruments Komplete Kontrol S88, Korg NanoControl.
#97
elsongs
Max Output Level: -84 dBFS
  • Total Posts : 306
  • Joined: 2010/03/02 16:16:02
  • Location: Los Angeles, CA
  • Status: offline
Re: Midi - should it go or should it stay ? 2018/03/02 16:29:07 (permalink)
If you want to use a DAW that lacks MIDI, just use Pro Tools. 

Elson Trinidad Los Angeles, CA, USA
Web: www.elsongs.com
Twitter: twitter.com/elsongs

DAWs: Cakewalk by Bandlab, Cakewalk Sonar Platinum x64, Propellerhead Reason 9, Presonus Studio One v3
OS: Windows 10 Professional 
CPU: Intel i7 3820 3.6MHz 
MB: ASRock X79 Xtreme4
RAM: Corsair Vengeance 16GB DDR3
Audio: Focusrite Scarlett 18i20 2nd Generation
MIDI: MOTU Microlite & Novation Impulse 61
#98
Jeff Evans
Max Output Level: -24 dBFS
  • Total Posts : 5139
  • Joined: 2009/04/13 18:20:16
  • Location: Ballarat, Australia
  • Status: offline
Re: Midi - should it go or should it stay ? 2018/03/02 19:26:43 (permalink)
I was put through Pro Tools Training to be a certified Avid trainer while teaching sound engineering at College.  After doing that and as someone who owns a hardware based synth system I actually found the midi in Pro Tools to be acceptable and it would have done the job had I switched.  But in the end I stayed on Studio One and happier for it.  Pro Tools don't always make it intuitive or easy.  But you are basically correct in that it is one DAW where the midi features are lesser compared to others.
 
Sonar was as far as I remember not considered the midi king back at the time.  It was Cubase and Logic.  Both of those programs handle midi real well in fact.  They were both in existence for 6 to 7 years before Cakewalk started.  I started with Steinberg Pro 24 for the Atari too.  That was pretty cool at the time.  Sonar has also had a long association with midi though for sure. 
 
If you connect certain midi hardware to either of them something else comes into play which many others don't do.  Its called LTB (Linear Time Base) with Cubase and AMT for Logic. (Active Midi transmission)  Logic is still a killer midi machine.
 
With LTB or AMT, midi notes are sent early to the interface and held up there and released in such a way as to all midi note-ons being lined up timing wise over the multiple midi out ports. (e.g. 8 midi note ons could be sent at exactly the same time, not sequentially as it normally would.  In dense passages midi note-ons would also be spread out slightly and sent a little early to keep out of the way of other notes)  Timing across all the ports is tightened up by roughly a factor of 10.  I have experienced this as well from both of those programs and it really improves things big time.  The timing for a large group of multi timbral synths parts is tightened up by a large factor.  Sonar does not have as do many others, a unique midi timing system that does this sort of thing.
 
LTB and AMT are often not well known midi features.  The timing rivals the tightness of the older CV and Gate protocol.  I had all that too with many analog synths and modular stuff.  I was using CV/Gate before midi was invented.  Especially with step sequencers.  The timing was pretty damn tight back then I can assure you.
 
But the Midi to CV/Gate converters did flow out in the mid 80's too.  I had several of them driving a bunch of instruments that only had CV/Gate inputs.  With Logic running AMT for me it worked out super well and was ultra reliable.  The converter I had also offered a third output (second CV output) for each channel and it was relative to velocity.  So velocity sensitivity could be patched into an analog synth sound rather easily. 
 
 

Specs i5-2500K 3.5 Ghz - 8 Gb RAM - Win 7 64 bit - ATI Radeon HD6900 Series - RME PCI HDSP9632 - Steinberg Midex 8 Midi interface - Faderport 8- Studio One V4 - iMac 2.5Ghz Core i5 - Sierra 10.12.6 - Focusrite Clarett thunderbolt interface 
 
Poor minds talk about people, average minds talk about events, great minds talk about ideas -Eleanor Roosevelt
#99
Thedoccal
Max Output Level: -85 dBFS
  • Total Posts : 290
  • Joined: 2014/10/12 16:43:08
  • Location: Joshua Tree, CA
  • Status: offline
Re: Midi - should it go or should it stay ? 2018/03/02 19:36:08 (permalink)
Midi won't work for online collaboration.  Audio only.
But midi works for creating what will end up being that collaborative audio file.
So midi will stay...at least in the Sonar version that Bandlab adopts for it's platform.

http://www.catastrophelounge.com
The NeckDive Strap - NEW^^
Sonar: Platinum Lifetime/Computer: i7-870, 16GB RAM, AMD R9 380 graphics, Windows 10 (Pro x64)/500gb SSD C:, Barracuda sample(3T) and projects(1T) drives/3 Display Monitors (2&3 split)/Audio Interface: Behringer UFX1604 USB/Firewire/USB Stick/MIDI: Roland A-800Pro, Keystation Pro 88, Roland UM-3G:/Hardware Synths: Korg M3, Yamaha MOX6, Roland TD-8
Midiboy
Max Output Level: -82 dBFS
  • Total Posts : 414
  • Joined: 2015/01/14 09:29:54
  • Location: Northwood
  • Status: offline
Re: Midi - should it go or should it stay ? 2018/03/02 19:40:03 (permalink)
Thedoccal
Midi won't work for online collaboration.  Audio only.
But midi works for creating what will end up being that collaborative audio file.
So midi will stay...at least in the Sonar version that Bandlab adopts for it's platform.




Depending on what you mean by online collaboration, this is not necessarily true. I have collaborated many times using MIDI.  If the person you are working with has the same MIDI instruments, not a problem at all to send them the file, then they can work on it, and send it back.  

If they do not have the same instruments, still not a problem...you just say "Track 1 = Piano, Track 2 = Bass", etc.  They can then setup something close or similar on their end, create their track and send it back.  I've done it plenty of times. 

----
Gregg
Midiboy Music
www.facebook.com/midiboygregg
 
Win10x64 (Eng), Sonar Platinum x64 (Eng w/ lifetime updates), 32GB DDR4 RAM, Intel i7 5820, nVidia 960, Alesis MultiMix 8 USB2 w/ Alesis MultiMix driver. Native Instruments Komplete Kontrol S88, Korg NanoControl.
Jeff Evans
Max Output Level: -24 dBFS
  • Total Posts : 5139
  • Joined: 2009/04/13 18:20:16
  • Location: Ballarat, Australia
  • Status: offline
Re: Midi - should it go or should it stay ? 2018/03/02 20:34:02 (permalink)
The General Midi standard was a handy invention.  It pays to have a Roland Sound Canvas lying around to play back midi files correctly.  It does work and rather well.  Selecting instruments, setting up mixes and effects.  I have collaborated this way sending GM ideas back and forth and then at the right time replacing the GM sounds with better quality sounds.  It is a good format for commercial midi files of covers.  Many midi files setup and playback perfectly. 
 
GM sounds can be edited too and dropped into the music anywhere. 
 
 

Specs i5-2500K 3.5 Ghz - 8 Gb RAM - Win 7 64 bit - ATI Radeon HD6900 Series - RME PCI HDSP9632 - Steinberg Midex 8 Midi interface - Faderport 8- Studio One V4 - iMac 2.5Ghz Core i5 - Sierra 10.12.6 - Focusrite Clarett thunderbolt interface 
 
Poor minds talk about people, average minds talk about events, great minds talk about ideas -Eleanor Roosevelt
SandlinJohn
Max Output Level: -87 dBFS
  • Total Posts : 188
  • Joined: 2016/06/14 13:56:08
  • Status: offline
Re: Midi - should it go or should it stay ? 2018/03/03 00:43:48 (permalink)
Jeff Evans
Sonar was as far as I remember not considered the midi king back at the time.  It was Cubase and Logic.  Both of those programs handle midi real well in fact.  They were both in existence for 6 to 7 years before Cakewalk started.  I started with Steinberg Pro 24 for the Atari too.  That was pretty cool at the time.  Sonar has also had a long association with midi though for sure. 


Cubase appears to have it's start in 1984 on the Commodore 64 with Pro-16 by Steinberg. The Atari ST was released in 1985 so that is the earliest for C-Lab Creator (which eventually became Logic). Cakewalk version 1.0 was in 1987 on MS-DOS machines. So at best Cubase has a three year longer history, Logic, has two years, over Cakewalk. Cakewalk and then SONAR have always had MIDI. There were other Cakewalk branded products that might have skimped on MIDI, but SONAR doesn't skimp.
 

Sonar Platinum, Windows 7 Pro 64 bit, Intel NUC micro-workstation with 5th Gen Intel i5-5250U, 16 GB RAM and 1.25 TB Storage, Yamaha MG10XU Mixer USB Interface, Yamaha HPH-MT8 Monitor Headphones, Yamaha MX-49 controller synth
abacab
Max Output Level: -30.5 dBFS
  • Total Posts : 4464
  • Joined: 2014/12/31 19:34:07
  • Status: offline
Re: Midi - should it go or should it stay ? 2018/03/03 02:50:37 (permalink)
Jeff Evans
The General Midi standard was a handy invention.  It pays to have a Roland Sound Canvas lying around to play back midi files correctly.  It does work and rather well.  Selecting instruments, setting up mixes and effects.  I have collaborated this way sending GM ideas back and forth and then at the right time replacing the GM sounds with better quality sounds.  It is a good format for commercial midi files of covers.  Many midi files setup and playback perfectly. 
 
GM sounds can be edited too and dropped into the music anywhere. 
 



I have an old Roland JV1080 rack module that can play back GM sounds. 
 
But as far as GM compatibility built into DAWs, Sonar has TTS-1, and Studio One has Presence XT.  I believe Cubase can also open GM in the included Halion Sonic, but I have not tried that.
 
I think that TTS-1 has a slight edge on Presence XT, but both definitely need some sounds replaced with better instruments.  Either way, it is handy to be able to open a file with sounds loaded, and have an idea what the orchestration should ultimately be.  The instrument names in the GM file alone are a big help in finding substitute sounds that correspond with the original composition.  If you have a multi-timbral sampler it is easy to substitute channel by channel for the GM sounds as needed.

DAW: CbB; Sonar Platinum, and others ... 
husker
Max Output Level: -90 dBFS
  • Total Posts : 35
  • Joined: 2018/01/16 02:10:34
  • Status: offline
Re: Midi - should it go or should it stay ? 2018/03/03 03:31:49 (permalink)
abacab
 Selecting instruments, setting up mixes and effects.  I have collaborated this way sending GM ideas back and forth and then at the right time replacing the GM sounds with better quality sounds.  It is a good format for commercial midi files of covers.  Many midi files setup and playback perfectly. 
 
GM sounds can be edited too and dropped into the music anywhere. 
 

I believe Cubase can also open GM in the included Halion Sonic, but I have not tried that.


Yes, that is correct.

Cubase Pro 10 / SPLAT
Homebuilt PC - Gigabyte GA-170 HD3, Intel Core i7 6700k OC 4.5 GHz, Corsair Hydro H50 Cooling, 16 MB GSkills Ripjaw DDR4-2133, SanDisk Ultra II 960 Gb, NZXT-S340 Case, LG 34UC88
Interfaces - Focusrite Scarlett 18i20 2nd Gen / MOTU Midi Express XT USB
Hardware - Roland FA08 / Moog Slim Phatty / Nord A1R / Maschine Mikro / Integra 7 / Prophet Rev2 16 Desktop
husker
Max Output Level: -90 dBFS
  • Total Posts : 35
  • Joined: 2018/01/16 02:10:34
  • Status: offline
Re: Midi - should it go or should it stay ? 2018/03/03 03:32:15 (permalink)
abacab
I believe Cubase can also open GM in the included Halion Sonic, but I have not tried that.


Yes, that is correct.

Cubase Pro 10 / SPLAT
Homebuilt PC - Gigabyte GA-170 HD3, Intel Core i7 6700k OC 4.5 GHz, Corsair Hydro H50 Cooling, 16 MB GSkills Ripjaw DDR4-2133, SanDisk Ultra II 960 Gb, NZXT-S340 Case, LG 34UC88
Interfaces - Focusrite Scarlett 18i20 2nd Gen / MOTU Midi Express XT USB
Hardware - Roland FA08 / Moog Slim Phatty / Nord A1R / Maschine Mikro / Integra 7 / Prophet Rev2 16 Desktop
tomixornot
Max Output Level: -58.5 dBFS
  • Total Posts : 1674
  • Joined: 2011/03/05 11:31:26
  • Status: offline
Re: Midi - should it go or should it stay ? 2018/03/03 04:43:58 (permalink)
Stay

Albert


i7 2600K @ 3.40GHz / MB Intel DP67BG / 16GB Ram
- ADATA 250GB SSD (Boot)
- Samsung Spinpoint F1 1TB HDD (Samples)
Audio interface : Motu 828 MK ii
 
i7 6700K @ 4.00GHz / MB Asrock Z170 / 16GB Ram
- Samsung EVO 850 120GB / 500 GB SSD

Audio interface : Roland Quad Capture
 
Win 10 Pro / Sonar Platinum
SuperG
Max Output Level: -63 dBFS
  • Total Posts : 1371
  • Joined: 2012/10/19 16:09:18
  • Location: Edgewood, NM
  • Status: offline
Re: Midi - should it go or should it stay ? 2018/03/03 07:58:58 (permalink)
Dropping midi is like asking people to stop breathing because 'second hand smoke'.
 
I admit, in my younger days when I used to smoke, I had a sticker on my dashboard that read "Thank you for holding your breath while I smoke!"...

laudem Deo
Steev
Max Output Level: -84 dBFS
  • Total Posts : 314
  • Joined: 2006/02/04 08:24:08
  • Status: offline
Re: Midi - should it go or should it stay ? 2018/03/03 10:13:22 (permalink)
  I have an original Korg MS-20, Poly 6, Poly 61, and M1, and a Yamaha DX7 all dead now.
I also have an old Roland Super JV-1080, ROMed out to the max with all expansion card slots filled. An old Juno (retired), and a PMA-5 portable 8 track sequencer Sound Canvas module that I've rocked many a solo performance with over the years. The Roland PMA-5 can store 20 songs and can run off batteries for about 12 hours of continuous use. All my old Roland's still work great. The old Juno still work but is retired because C4 key lost touch sensitivity.
 I also have an old Kawai K 11 (circa 1990) in excellent shape which is my absolute favorite very high quality sounding 32 bit GM digital hardware synth in the studio to date. It actually has two 16 bit sounds engines and 2 MIDI ports. It's still one of my go to choices for realistic piano and horns.
 But what makes the K 11 really shine is the feel and action. It's everybody's who has ever touched it favorite choice to use as keyboard controller for playing ANY synth.
 It has an extremely wide and smooth velocity range giving it a very natural feel from soft to loud, which makes it also an excellent choice for banging out and sequencing sampled drum tracks with Addictive Drums 2.
 I've been creating drum tracks on MIDI keyboards for decades. Thank God the bakers at XLN Audio has the grace and insight to included the standard GM MIDI map for drums, or I probably wouldn't have realized how good AD 2 and their sampling techniques are.
 Bye bye ToonTracks it was great and much fun while it lasted.. ;-p
 And THANKYOU Cakewalk for including Addictive Drums with SONAR Platinum
 
 I really like the Cakewalk TTS-1 DXi synth, especially being that it has such a wide list selection of varieties of Roland Sound Canvas GM/GS version libraries. Very customizable and specific to dozens of Roland synth voicings put out through the years. I've been using the TTS-1 as the center piece for all my GM collaborations since it was introduced with SONAR 4 PE, and still use it today.
 I also love the fact that it can be configured to 4 separate audio output channels giving it that much more flexibility and precise control over the sound of each voice or instruments using EQ and or any other audio FX you choose.
 I never patch more then one voice per output for optimal sound quality, no need to when I can just open another instance of the TTS-1.
 And just because you can play perform 16 different parts on a GM synth doesn't mean you should, because the more voices and parts being pumped through any synth's sound engine, be it software or hardware the more the over all sound quality degrades.
 Of course distortion has it's place in many situations, but SONAR has a host of audio FX that will nasty things up in a very musical way.
 
 The GM spec is most likely the most important key to successful MIDI collaboration that ever happened.
 Developed in collaboration with Roland, Cakewalk, Microsoft, and defined by IEEE for a standard set of 128 algorithms for program and control changes.
 It's the closest way to get all synth manufacturers on the same page by defining a specific set RPNs (registered parameter numbers), and leaving enough room with NRPNs (non registered parameter numbers) for manufacturer proprietary system exclusive information that simply gets ignored by synths that don't support or understand it.
 
And I gotta give BIG PROPS to Rapture Pro, what with being Dimension Pro and Rapture bundled up together in one Killa arse powerful GUI interface is well........... Not GM, but its ANY type of synth you want it to be. I have all the Dimension Pro expansion packs, plus several I purchased from Digital Sound Factory.
 If I was ever forced to chose between using any one synth, Rapture Pro would be the no brainer choice for the all in one Superstar.
 Now I know there are many here who would say something like; "Oh dude, you really need to try N.I.'s Kontakt!" and I know it's good just by the things I've heard from it.
 But I don't need to try it because I don't need it and I'm already familiar with what I have..

Steev on Bandlab.com
 
Custom built workstation. Windows 10 Pro x64.
 
SONAR Platinum. Cakewalk by Bandlab.
Sony Sound Forge Pro 10, ACID Pro 7, Vegas Pro 11
Pro Tools.
 
ASRock 990FX mobo, AMD FX 8370 8-Core. 16 gb DDR3 PC1866 G Skill Ripjaws X RAM. AMD FirePro V4900 1gb DDR5 accelerated graphics card. 
Behringer X Touch DAW Controller
Focusrite Scarlett 18i20 gen 2, OctoPre Mkll
Western Digital 500GB SSD bootdrive,  WD 500GB 10k rpm VelociRaptor for DAW projects . 2x1 TB WD Caviar Black SATA3 storage drives
 
Phoen1xPJ
Max Output Level: -85 dBFS
  • Total Posts : 255
  • Joined: 2016/11/03 18:14:22
  • Location: Atlanta
  • Status: offline
Re: Midi - should it go or should it stay ? 2018/03/03 10:27:43 (permalink)
Wow, Steev... thanks fer the dynamite essay that highlighted the crucial importance of MIDI... rawk on! 

Yours With a Song,
Phoen1x
 
Wayfarer Station Micro Studio including:
*new* Cakewalk by BandLab
Intel Core i5 quad core 3.10 GHz
ASUStek P8B75-M mobo
32 GB Mushkin Blackline RAM
NVidia GeForce 210 1 GB vid card
(2) 1 TB HD & (1) 500 GB HD
*new* Win 10 Pro 64 bit
Echo Layla 24 PCI audio interface (faster than USB!)
Tascam US-224 control surface (with jog/shuttle wheel, impossible to find elsewhere)
MIDIMan 2X2 MIDI interface
...not bleeding edge but vintage rockin' 
 
http://verticalalignment.rocks/
 
 
Faza_TCM
Max Output Level: -90 dBFS
  • Total Posts : 19
  • Joined: 2015/11/07 10:02:27
  • Status: offline
Re: Midi - should it go or should it stay ? 2018/03/03 14:46:58 (permalink)
The question whether MIDI should be dropped is... curious, to say the least.
 
The simple facts of the matter right now is that you pretty much can't do contemporary music production without it. Whether you're using virtual instruments, control surfaces or hardware automation, you're pretty much bound to be using MIDI for it. Any DAW that aspires towards professional use simply has to have it.
 
Now, I appreciate that these days MIDI looks more than a bit clunky and dated - mostly because of its limited resolution. Nevertheless, it's the only thing pretty much everyone is guaranteed to understand, so it's what we gotta work with.
 
Thedoccal
Midi won't work for online collaboration.  Audio only.
But midi works for creating what will end up being that collaborative audio file.
So midi will stay...at least in the Sonar version that Bandlab adopts for it's platform.



I don't mean to sound like I'm picking on you, Thedoccal, but that's not even wrong. MIDI is not only perfectly suited to online collaboration, but it facilitates certain things that you simply wouldn't be able to do otherwise. MIDI allows us to separate the composition/performance data from the actual sounds and that means the composer or performer does not have to have the best possible sound generators on hand or be proficient in getting superior audio.
 
To give an example: currently I have a couple of projects going where I get the MIDI data, transform it to suit my choice of instruments (this applies to drums especially, but I also do stuff like chart generation in order to record live guitar parts etc.) and work from there. Were I to be forced to use audio only, the results would either be inferior (being stuck with a cake I can't unbake) or I'd have a lot more work on my hands (needing to pick apart the parts I want to reprogram or re-record by ear).
 
Frankly, I can think of very few collaborative scenarios where MIDI is present and I would not want to use it. The ability to get inside the performance and to swap out tone generators for what works best in the mix is just too valuable. Even if my collaborator can provide me with excellent renders that would be used in their audio form, I still might want the MIDI data for additional layering and such.
 
The only reason I could see for dropping MIDI support is if a better global standard comes along.
abacab
Max Output Level: -30.5 dBFS
  • Total Posts : 4464
  • Joined: 2014/12/31 19:34:07
  • Status: offline
Re: Midi - should it go or should it stay ? 2018/03/03 15:14:22 (permalink)
I think of MIDI as the 'machine language' of music.  It allows you to see a performance in the way it was actually performed, note on, by note off.  Much easier to edit and move an event around than to edit audio. 
 
There was a time before all of the current audio time and pitch shifting and stretching algorithm magic was possible.  So you can do more with audio now than ever before, but you still cannot completely unbake a cake.
 
I like to be able to see music in notation view and piano roll view side by side.  I think that composers and arrangers would view MIDI as a data transmission mechanism to their 'electronic' musicians.  Write a score in a music notation program, and then export it as a MIDI file to be played back and/or edited in a DAW.

DAW: CbB; Sonar Platinum, and others ... 
CJaysMusic
Max Output Level: 0 dBFS
  • Total Posts : 30423
  • Joined: 2006/10/28 01:51:41
  • Location: Miami - Fort Lauderdale - Davie
  • Status: offline
Re: Midi - should it go or should it stay ? 2018/03/03 15:43:23 (permalink)
Re: Midi - should it go or should it stay ?
 
Why do you or why would you have you choose? 
 
Is there a reason why you seem a need to choose??

www.audio-mastering-mixing.com - A Professional Worldwide Audio Mixing & Mastering Studio, Providing Online And Attended Sessions. We also do TV commercials, Radio spots & spoken word books
Audio Blog
Jeff Evans
Max Output Level: -24 dBFS
  • Total Posts : 5139
  • Joined: 2009/04/13 18:20:16
  • Location: Ballarat, Australia
  • Status: offline
Re: Midi - should it go or should it stay ? 2018/03/03 19:49:32 (permalink)
Last year I produced a Children's CD professionally.  I worked with a married couple.  She did all the singing but he created all the midi arrangements, played guitar very well and keys for the purposes of playing data in.  We worked apart for a while using midi and the standard set of GM sounds.  Sending midi files to me once the basics of the arrangement were fleshed out.  I saw (e.g. PRV view)  and heard exactly what he was hearing which was good.  We both used a Roland Canvas as the playback machine.  The choice of presets was excellent in that it conveyed a lot about the types of sounds they were after. 
 
Midi allows extensive sound shaping and backdrops to be created and changed incredibly easily and this includes tempo alterations.  To me it is not clunky nor dated.  I think midi was invented very well to start with as it has lasted so long, it has stood the test of time, has been running excellently for decades and does not seem to be going anywhere.  They built tons of (unknown) future use into it from day one.  It is a fine example of this to be precise.  It seems to run seamlessly alongside my current DAW.  They are looking at new improved midi protocols now which is only going to get even more interesting. 
 
A midi note one only takes 1mS of latency to send.  That is super fast, even in terms with today's audio latencies.  If you only put one synth making one sound on one midi port then you are in for some pretty tight timing.  The internal resolution of programs like Studio One handle very well the capture and playback of subtle midi performances.
 
For the CD, by the time they came around to record all the vocals and guitar parts, I had all the sounds reset to high quality patches.  Some of his midi data had to re worked and improved, I added extra stuff.  We took some stuff out etc.. It was a very productive way to work.   I have not done a lot of CD's involving midi collaboration prep, but I was very pleasantly surprised at how well the use of the GM standard allowed us to do enormous amounts of work before studio sessions took place.  Everyone was super prepared.
 
A large and powerful hardware synth setup allows you to leave a lot of midi parts as midi files playing the instruments live each time you hit play on your DAW.  You need a synth mixer to do this properly.  Sounds can be changed and this is one powerful feature.  No CPU resources being used now for the purposes of making sounds. This eases the load on your computer enormously.  Of course now your virtual instruments can be added in  (you wont need as many) adding complexity and excitement to the arrangement.  Right near the end you turn everything midi into audio and then can carry on working with the music in that form.  More effects, more editing, more everything.  If you are not happy with certain parts, you can turn the midi parts back on at any time and get one or more synth parts playing live again.  Then change the part. 

Specs i5-2500K 3.5 Ghz - 8 Gb RAM - Win 7 64 bit - ATI Radeon HD6900 Series - RME PCI HDSP9632 - Steinberg Midex 8 Midi interface - Faderport 8- Studio One V4 - iMac 2.5Ghz Core i5 - Sierra 10.12.6 - Focusrite Clarett thunderbolt interface 
 
Poor minds talk about people, average minds talk about events, great minds talk about ideas -Eleanor Roosevelt
vintagevibe
Max Output Level: -51 dBFS
  • Total Posts : 2446
  • Joined: 2003/12/15 21:45:06
  • Location: Atlanta, Ga
  • Status: offline
Re: Midi - should it go or should it stay ? 2018/03/03 20:12:46 (permalink)
Why is everyone rushing in to defend MIDI as if there is any universe where MIDI would be removed or omitted from any DAW?
Zargg
Max Output Level: 0 dBFS
  • Total Posts : 10666
  • Joined: 2014/09/28 04:20:14
  • Location: Norway
  • Status: offline
Re: Midi - should it go or should it stay ? 2018/03/03 20:26:49 (permalink)
IIRC the OP stated in a later post that he meant the continuous development of MIDI, not whether or not it should be removed.
I agree that MIDI is here to stay, and is more and more relevant due to the quality of instruments available these days.
 

Ken Nilsen
Zargg
BBZ
Win 10 Pro X64, Cakewalk by Bandlab, SPlat X64, AMD AM3+ fx-8320, 16Gb RAM, RME Ucx (+ ARC), Tascam FW 1884, M-Audio Keystation 61es, *AKAI MPK Pro 25, *Softube Console1, Alesis DM6 USB, Maschine MkII
Laptop setup: Win 10 X64, i5 2.4ghz, 8gb RAM, 320gb 7200 RPM HD, Focusrite Solo, + *
 
wdaweb
Max Output Level: -90 dBFS
  • Total Posts : 9
  • Joined: 2015/02/16 14:08:40
  • Status: offline
Re: Midi - should it go or should it stay ? 2018/03/03 22:38:11 (permalink)
My opinion is that the last version of the MIDI editor in Sonar Platinum became harder to use than the way it was before. At least in the way that you were able to view tracks, and how you picked which ones you wanted to see. I saw a few complaints about this online after it was changed. Wasn't a show stopper though as you could still edit your midi tracks. Hopefully that came out right...
 
After Gibson announced it was killing off Cakewalk, I invested in Pro Tools and a lot of education to make sure I could use it to its fullest. I found that PT has excellent Midi editing features but is no where near as stable as Sonar on the PC platform. Again, my opinion is that midi editing in PT is actually better and easier to do than in Sonar. That's about the only feature that I can honestly say I use constantly where PT beats Sonar. Sonar wins at just about everything else, including it's Midi event list and how you can edit that. I don't want to sound like I'm knocking PT. It's a great program, but Sonar Platinum is much nicer to use - not to mention that its interface looks so much better.
 
As long as I don't have to sink a chunk of money into a new Bandlab/Cakewalk/Whatever It Will Be Called product, I will gladly switch back from Pro Tools. You can do some amazing things with Pro Tools, but same with Sonar Platinum and you didn't have to fight with the issues PT has on the PC platform. I think that's where cakewalk missed a marketing opportunity. It is as feature rich as PT, but no where near as buggy. Plus, Cakewalk support was a lot faster too.
Steev
Max Output Level: -84 dBFS
  • Total Posts : 314
  • Joined: 2006/02/04 08:24:08
  • Status: offline
Re: Midi - should it go or should it stay ? 2018/03/03 23:17:30 (permalink)
wdaweb
My opinion is that the last version of the MIDI editor in Sonar Platinum became harder to use than the way it was before. At least in the way that you were able to view tracks, and how you picked which ones you wanted to see. I saw a few complaints about this online after it was changed. Wasn't a show stopper though as you could still edit your midi tracks. Hopefully that came out right...
 
After Gibson announced it was killing off Cakewalk, I invested in Pro Tools and a lot of education to make sure I could use it to its fullest. I found that PT has excellent Midi editing features but is no where near as stable as Sonar on the PC platform. Again, my opinion is that midi editing in PT is actually better and easier to do than in Sonar. That's about the only feature that I can honestly say I use constantly where PT beats Sonar. Sonar wins at just about everything else, including it's Midi event list and how you can edit that. I don't want to sound like I'm knocking PT. It's a great program, but Sonar Platinum is much nicer to use - not to mention that its interface looks so much better.
 
As long as I don't have to sink a chunk of money into a new Bandlab/Cakewalk/Whatever It Will Be Called product, I will gladly switch back from Pro Tools. You can do some amazing things with Pro Tools, but same with Sonar Platinum and you didn't have to fight with the issues PT has on the PC platform. I think that's where cakewalk missed a marketing opportunity. It is as feature rich as PT, but no where near as buggy. Plus, Cakewalk support was a lot faster too.


Ummmm What??????????????

Steev on Bandlab.com
 
Custom built workstation. Windows 10 Pro x64.
 
SONAR Platinum. Cakewalk by Bandlab.
Sony Sound Forge Pro 10, ACID Pro 7, Vegas Pro 11
Pro Tools.
 
ASRock 990FX mobo, AMD FX 8370 8-Core. 16 gb DDR3 PC1866 G Skill Ripjaws X RAM. AMD FirePro V4900 1gb DDR5 accelerated graphics card. 
Behringer X Touch DAW Controller
Focusrite Scarlett 18i20 gen 2, OctoPre Mkll
Western Digital 500GB SSD bootdrive,  WD 500GB 10k rpm VelociRaptor for DAW projects . 2x1 TB WD Caviar Black SATA3 storage drives
 
Jeff Evans
Max Output Level: -24 dBFS
  • Total Posts : 5139
  • Joined: 2009/04/13 18:20:16
  • Location: Ballarat, Australia
  • Status: offline
Re: Midi - should it go or should it stay ? 2018/03/04 00:23:10 (permalink)
Interesting reading Steev's mention of the Kawai K11.  I have a Kawai K5000W which is the much later and the most powerful version of this synth.  It has both Additive and PCM based engines.  Two midi ins and two stereo outs too. Can be treated as two separate synths in one. Not many can do this.
 
The Additive side sounds amazing.  I have found many patches for it on line, probably all of them.  They are wonderful.  Not too much bottom end wither.  Many Kawai layers can be had with little build up in the low end.  The K5000 can do 6 layers per note and there are 6 effects processors too.  I have a Doepfer Pocket Dial which has 16 endless knobs on it controlling the 16 most important parameters of an additive sound.  So editing is active all the time.  
 
The PCM side is very good too loaded up with a huge sample base.  689 waveforms.  It sounds way different to the additive side.  Quite earthy and organic at times. It layers well with the additive sounds too.  There is also a built in GM sound engine with its waveforms and patches. K500W also features sequencing options. 
 
The white keys are longer than normal and have proper lead weights under mine.  The action is real nice and it is very good to play.   Most of all it has a range of sounds including lush and detailed and complex too.  It works well with the mod wheel and after touch.  It is one beautiful instrument.
 
I also have a Roland JD800 and it is completely different but also quite stunning.  That and the Kawai dance together rather beautifully. The JD can be super analog at times but super digital at other times.  It is like having two synths in one as well. Between the two of them I can get 4 distinct textures.
 
 

Specs i5-2500K 3.5 Ghz - 8 Gb RAM - Win 7 64 bit - ATI Radeon HD6900 Series - RME PCI HDSP9632 - Steinberg Midex 8 Midi interface - Faderport 8- Studio One V4 - iMac 2.5Ghz Core i5 - Sierra 10.12.6 - Focusrite Clarett thunderbolt interface 
 
Poor minds talk about people, average minds talk about events, great minds talk about ideas -Eleanor Roosevelt
jimfogle
Max Output Level: -81 dBFS
  • Total Posts : 463
  • Joined: 2007/03/14 10:08:19
  • Location: North Carolina USA
  • Status: offline
Re: Midi - should it go or should it stay ? 2018/03/04 01:33:18 (permalink)
Keep and update MIDI capability.
 
The next generation of MIDI is arriving NOW!  New specifications were released at 2018 NAMM.  The next generation is called MIDI-CI and is an addition to the original MIDI 1.0 specification.  That means anything based on MIDI-CI will be backward compatible with MIDI 1.0.  You can read more about MIDI-CI here:  https://www.midi.org/articles/midi-manufacturers-association-mma-adopts-midi-capability-inquiry-midi-ci-specification.
 
MIDI has adapted well to more than thirty years of computer evolution.  A computer built in 2018 using either the latest version of Mac or Windows can still communicate and control a MIDI keyboard or sound module built back in 1983 when MIDI was born.  MIDI has adapted to moving from transmission over dual, five wire cables to USB, Bluetooth and wi-fi.  MIDI is how most DAWs communicate with VSTs.
 
Follow the link above and read how MIDI is adapting.  The DAW that wins the MIDI battle is going to be the DAW that is able to fully utilize existing and upcoming MIDI capabilities.  Bitwing, Studio One, Ableton and Reaper demonstrated compatibility with the new standards at NAMM.  The tools presently available in Sonar are, for the most part, seriously overlooked and neglected.
 
I'd start with the MIDI effects GUIs.  Update the GUIs to reflect whatever new look the new DAW has.

Jim F
Cakewalk by Bandlab (CbB)
Sonar Home Studio V23.9.0 build 32
Music Creator 6
Band-in-a-Box, Audacity, ChordPulse
Win 7, i3 cpu, 8Gig ram, 480 Gig Dell Laptop
http://fogle622.wix.com/fogle622-audio-home
 
 
Page: < 12345 > Showing page 4 of 5
Jump to:
© 2024 APG vNext Commercial Version 5.1