Hi,I have seen youtube films like this: =UOQGIaaYjWMThis way it takes days to write a long score. I am looking a fast way to do that.Is there any other way to play the Midi-keyboard and get your notation written on the musescore?I've heard that you might have other softwar to create the midi files and then import midi files to musescore.Could it be correct?Regards
Try this test with the very simple score [EDIT] which I have now posted below:1. Save as a MIDI file (File > Export... > Export To: MIDI)2. Close the MuseScore file3. In MuseScore open the new MIDI file with File > Open... > MIDI Files (*.mid *.midi *.kar)4. Notice how much musical information has been lost when importing the MIDI file
Another interesting format is MIDI-karaoke. You can try to look for MIDI files of popular compositions in open sources. Midi-format does not contain any information about the timbre of sound played. Midi-files consists of events (such as Note On, Note Off, Aftertouch etc). MIDI is an interface and it has been originally designed to store and transfer commands, such as when and how loud key is pressed, MIDI does not contain any complex phicysal characteristics of real-word's sounds. MIDI supposes that you use so called software-hardware complex. Playing MIDI, hardware of sotware synth uses its embedded timbres to produce sounds. You're limited by quality or a number of timbers of your synth. MIDI is strictly depends on the hardware where it was created. If you ever changed your synth, there's no warranty that you'll get a great sound on your new synth with you old midi-sources!
Hi, I'm trying to fire a cue with a midi note in ableton live through luminosus on my macbook with Eos Nomad. I add a block note in + Key button. In Ableton I see luminosus in midi preferences and enable communication, but ableton don't appear in luminosus. I tried with a midi keyboard and that works, the issue is the communication between ableton live and luminosus. Someone could help me? Thanks
summary: create event list of type network. create event of type Midi Input. enter the type of Midi string you're expecting (in your case the Midi string for the note). define what action belongs to that Midi input (in your case the cue you want to fire).
On Mar 2, 10:30 am, raymond soly wrote:> Hi Onslaught,>> to answer your question we need to know more about your set up /> interface etc.......if you just want to send midi program changes > within Qlab to LS9, then assign that message in Qlabs midi message > tab, to make sure you are sending the right message to the right port
> that will tell you what and where you are sending then troubleshoot > from there. It is unclear where the issues are unless we know more of > your system setup.>> How are is the midi getting to the yamaha, thru what interface, is the > LS9 expecting messages on a certain midi channel or all etc.. etc..>> need more info>> Ray> On 1-Mar-10, at 10:20 PM, Onslaught wrote:>>>> > Hey, i'm new to the midi world and have been playing around for a few> > hours and have had no success. I'm trying to figure out how to use> > qlab to change the scene my ls9 is in.>> > I wanted to know if anyone has done this and if so what were the> > settings used in qlab and on the ls9 to make everything work.>> > Any help would be greatly appreciated.>> > ________________________________________________________> > WHEN REPLYING, PLEASE QUOTE ONLY WHAT YOU NEED. Thanks!> > Change your preferences or unsubscribe here:> > -figure53.com>>>> ________________________________________________________> WHEN REPLYING, PLEASE QUOTE ONLY WHAT YOU NEED. Thanks!
> Ok, I have the MacPro connected to the Edirol UM-3EX Midi Usb> interface. That is connected to the Ls9 from the second out port on> the device to the input on the Ls9. The Ls9 is expecting midi files> on channel 1, i left it on the default settings. In the program> change menu on the ls9 i have 001 and 002 set as recalling scenes 1> and 2. From Qlab i can't remember how many ways i tried firing MSC> and Midi Sys-ex cues with differient combinations of numbers etc. I> read somewhere to try going up and number and down a number also for> the midi number to see if that worked, but it didnt. The Ls9 says it> is receiving midi messages because the small green midi box lights up> on the top of the screen when i try to send it a command.>>
> > is receiving midi messages because the small green midi box lights up> > on the top of the screen when i try to send it a command.>> > What else do you need to know?>> > On Mar 2, 10:30 am, raymond soly wrote:> >> Hi Onslaught,>> >> to answer your question we need to know more about your set up /> >> interface etc.......if you just want to send midi program changes
> >> tab, to make sure you are sending the right message to the right port > >> I suggest you download this little app > >> that will tell you what and where you are sending then troubleshoot > >> from there. It is unclear where the issues are unless we know more of > >> your system setup.>> >> How are is the midi getting to the yamaha, thru what interface, is the
>> >> need more info>> >> Ray> >> On 1-Mar-10, at 10:20 PM, Onslaught wrote:>> >>> Hey, i'm new to the midi world and have been playing around for a few> >>> hours and have had no success. I'm trying to figure out how to use
Akai has a long history of producing beloved hardware music controllers (most notably the MPC). They basically revolutionized hip hop with the release of the MPC60 in 1988. With that pedigree, I figured this new midi controller would be an awesome addition to my project studio.
My last big gripe with the Akai Fire is the mixer functionality. This feels like more of an afterthought than the keyboard implementation. When mixing, I typically need access to many channels at once, but the Fire only lets you control one channel strip at a time. The dedicated volume and pan faders are nice, but I have almost zero use for the pre-assigned high- and low-eq faders. I can assign effect automation to buttons and faders in a User mode, but any midi controller would let you do that.
I use alot of external hardware synths, and this tutorial was very helpful. However, my dream workflow would be to start a project in Standalone mode, and finish it in Controller mode, with MPC running as a VST in Ableton. But when I connect to my computer in Controller mode, all of my external hardware midi ports disappear, and my sequences make no sound because the ports they are routed to are grayed out. The only midi port available is called DAW. This sucks. I think the only solution is to unplug all of my hardware, connect it to my laptop, and reroute every track of every sequence to point to the hardware on the new ports in my DAW. I think this is a showstopper for my desired workflow, and there is no easy way to move from standalone to controller mode if you use external hardware.
Dorico does play but there is no blinking LED showing midi hitting the samplers.There is just no midi going between Dorico and the playback engine, none when writing or checking notes and none in playback.
Upgraded my Helix LT to the latest firmware recently. I see that with that latest version when programming in MIDI CC's or Program changes you can now put in a delay of transmission, default being 0 ms. I use my Helix to control our light show as well as it's normal use. I have Midi CC's attached to snapshots for every tune, "Verse", "Chorus, Solo" that sort of thing. Those MIDI commands are then "Caught" by a laptop running lighting software which in turn changes the light programming. In running the lights post firmware upgrade, I'm seeing random delays in light switching now. Before it was super snappy, zero lag at all, Now there's randomly up to a 500ms delay I'd say. Before I start forensically combing through software/hardware looking for the source, is this a known issue? Do I need to say, go in and recreate every command so that the midi delay data is overwritten with zero? I noticed commands I wrote pre upgrade do not display the delay option, however newly created MIDI commands do offer that option.
If the laptop is "Windows"... make sure you updated the Helix DRIVERs to make sure they match the firmware. For midi I'm not sure if it will really make a difference, but it can't hurt. Just install the latest version of HX Edit, and make sure the drivers are all checked.
Thanks for the advice. I have it connected via midi cable rather than USB. I do have the drivers updated on the laptop so...it must be something else. I'll have to hook things up and start doing some testing to see where the latency is coming from. By the responses thus far it's likely an issue with the laptop rather than the Helix. Thanks for the the help anyway guys!
It's an upgrade issue, at least in my case. Each patch has 2 commands on it. A MIDI CC command to fire the lights. and Bank/Program change to change the preset on my VE-500 vocal pedal. I'm going to have to go through the entire show and convert all of the generic post upgrade "Command" statements into actual "MIDI CC" and "Bank/Program changes" specifying 0ms wait time. I'm not sure how null data wait time is not being treated as 0. In my case anyway the firmware is producing random "wait times". I know not a ton of folks use the MIDI commands but Line 6 may want to have devs take a look. To me it was super evident because the light changes during the show were lagging significantly and I had to compensate by kicking in snapshots early so the light would change near the beat that it should. Not everyone is going to have something that blatant in their face to indicate when there's a lag. Without a light flashing in your face, a half second or second lag may not be noticed? Don't. Anyway thought I would share. I will do a full backup before I set out to manually "upgrade" all of my commands. 2b1af7f3a8