PS Did you set the Octave name display offset? Perhaps you can post screenshots here showing the differences. If you have any examples of different playable ranges for the same bass in both products, I'd be interested to see them. Typically, the range is based on the naturally playable range of the sampled / modelled bass. In both products the playable note range for each instrument is decided by the sounds developer. MODO BASS isn’t a sample-based instrument, but rather a completely new technology where sound is generated by recreating the physical properties of a real instrument - everything that makes an instrument create sound is physically modelled and sound is synthesized in real time. You see, traditional virtual instruments are sample-based, meaning that sound is produced by triggering recorded samples of instruments. I mean for goodness sake, I just want to play midi files that play fine in other DAWS!ĭoes anyone know of any reference for "MIDI" settings that will make Reaper do what the others do without having to jump through hoops?Įvery component that contributes to the unique tonal properties of a bass player playing an instrument has been modelled, and the effects of each component on the other ones - the interactions between each tone variable - has been recreated to give you a dynamic, living breathing and ever-changing performance. I love Reaper and prefer it for recording, but every time I turn around it seems like I'm fighting with it to do something simple that Studio One or Cakewalk does without any effort, which is important with a limited amount of time. What setting would cause "this" behavior in Reaper? The notes and instrument do play perfectly if I play them manually on the keyboard, it's just the playing back of a standard midi file that is giving me fits. I'm afraid I don't know enough about midi editing to check the individual note volume, etc., however it does play perfectly in Studio One. Every note above D2 sounds fine, but notes below D2 do not play. When I import a midi file, only the "top half" of the track will sound the notes. However, I have another issue with Midi in Reaper. Maybe someone can suggest a good method to clean up an existing project.Well, I'm still not sure why, but when I use the 16 channel out version of Kontakt instead of the 8 out, it works. I am dealing with apple on this as well and I will post my findings but if anyone can suggest any workarounds or suggestions (maybe its a UTM bug, reset pref's, etc). I've been a logic user since 3.5 and I've never seen a bug like this so I am really worried. Someone posted about a bug that seems somehow related to my experience with midi and incorrect track assignment and he posted a video here (however he says 9.1.1 fixed his issue). It thought it may be related to the size of my projects but even on new "default empty" projects I am getting strange channel strip behavior in which the VU meter wont show any activity until I "reset" it to no output and back to Stereo Output. The video at the link below shows the issue. I am not clear on what exactly it is doing as it appears to be random. However on playback it plays something else. If I drag over the midi I hear the instrument I played. But it plays back some other instrument in my arrangement instead on playback. The above is strange but the worse issue is that on some of my songs (songs with a lot of instruments) when I play and record midi on a track for, say Instrument 30 on any midi channel (1, 2, 3, etc.) it seems to record fine. Now I can make the Instrument channel strip for midi channel 2 move again as expected by first assigning its output to no output and then back to stereo output. The stereo out and the plugin itself recognize the signal passing through. I create a software instrument and assign it to a Kontakt 4/Omnisphere, instance and assign it to midi channel 1 and then add another midi channel of that same instrument (say channel 2.now its a multi-timbral instrument), and I can play and hear the instrument as expected but the VU meter for that new channel is not moving, it is frozen (if there was a sustained sound being triggered from channel 1). I installed the update hoping it would fix it but no luck.īasically it seems like an environment related issue: I only noticed the issues this week ironically hours prior to installing the 9.1.1 update. I am running a clean SL install and experiencing some serious bugs in relation to creating software instruments and recording midi with them in Logic.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |