hmm. that's not what i've found. perhaps you're keyboard's octive is
shifted up by 2?
On 11/19/05, Antonio TARANTINO <email@hidden> wrote:
> The problemÊ was the 2 octave shift due to the difference in the Note number
> between QC and a standard (musical) keyboard controller (and, I believe, any
> standard musical MIDI software).
>
> When you play a C3 on a keyboard, well, QC actually output a C5! A bit
> confusing.
>
> Anyway, that's it.
>
> ByeÊ
>
>
>
>
>
> On Nov 19, 2005, at 8:58 PM, Antonio TARANTINO wrote:
>
> Just found 30 seconds after I sent my last e-mail!!!
>
> My fault!!!
>
> I knew I could do silly things...
>
> The output value is always 0 if the output is not connected to an
> input!!!!!!!!!
>
> This doesn't explain why it didn't work in the past days (when I was
> checking a complete composition, so the output of the controller WAS
> connected to something (which accepted the kind of value it was sending),
> but anyway, testing a new composition today, with the explained procedure,
> with some connection, well, it worked.
>
>
> Thank you all.
>
> Bye bye.
>
>
>
>
> On Nov 19, 2005, at 8:47 PM, Antonio TARANTINO wrote:
>
>
> After all kind of troubleshooting I could imagine, the result is always very
> disappointing.
>
> I checked with MIDI Monitor, but everything is working fine. The only thing
> I learned is that QC thinks a C3 key has a 36 Note number, instead of 60
> (which isÊ a C5), but this is common to other softwares and should only
> affect the way notes are displayed. Anyway, I tried to use ALL the notesÊ on
> all the available channels and for all the octaves: nothing.
>
> Just to be clear, I followed your procedure, Michael:
>
> cleaned up all physical devices, except one
> checked it with MIDI Monitor
> started QC
> crated new composition
> selected MIDI Notes controller
> selectedÊ device
> all channels were selected (gray)
> played a C3 key
> output of C3 note=0
>
> played a C1 key (just in case)
> output of C3 note=0
>
> saved and closed composition
>
> opened it again
> tried again C3 key
> output of C3 note=0
> played all other notes
> output of C3=0
>
> Then I tried any combination and test that I could possibly imagine, I even
> changed the controller (i.e. the keyboard), but the output of C3 note (and
> of all the note output that I could test) in QC was alwaysÊdesperatelyÊ=0
>
> I finally decided that QC didn't like my G5 and tried it on my iBook, but
> guess what was the result?
>
>
>
> Maybe QC doesn't receive from Firewire or USB MIDI Devices? Well, but then
> why it "sees" them? (i.e. they appear in the "observed MIDI sources" menu)
> And also, when I use a virtual midi device as a bridge, QC "sees" it as well
> but doesn't react.
>
>
> Now, I don'tÊbelieveÊit's a bug that only strikes in my flat, and I could
> have done something really silly (oh, you'd be surprised...) but anyway it
> should work just right out of the box: just opening QC, selecting the
> controller, setting the device!
>
> ÊI must admit that all this is very strange; maybe someÊvoodoo?
>
> So please, if there is some QC+MIDI guru....
>
> Bye bye
>
>
>
>
>
>
> On Nov 18, 2005, at 10:59 AM, michael markert wrote:
>
> At this point, you have to find out, where the error is.
>
> Maybe you could load a nice free midi-tool: "Midi Monitor" (just google for
> this).
> Then you use Midi Monitor to check if something is coming in. Midi Monitor
> also shows you the values of the incoming data (set the prefs to "HEX" or
> "numbers").
>
> Then (when you're absolutely sure that everything works as it should)
> start(!) QC and create a blank composition. If you select "Midi Controller",
> you shouldn't have to en/disable something at all except the source and the
> Controller-Value.
>
> If it still won't work then, save your composition with the source you want,
> then restart QC, load that composition again.
>
> If it still won't work, I don't know why :(
>
>
>
> Maybe you could test another device.
> Yesterday I had the issue that the MidiDevice on the PCI-Card just didn't
> work! I switched to my USB-Device and everything went fine. But you'd notice
> this kind of behavior when you're using Midi Monitor to check your
> transmissions.
>
>
> Good Luck!
> Michael
>
>
>
> Am 18.11.2005 um 01:35 schrieb Antonio TARANTINO:
>
>
> Thank for the try, but didn't work neither.
>
> As far as I underestand a MIDI pipe create a virtual midi outÊ (one more),
> then QC has the same behaviour with it then it has with the others.
>
> *%%´²(c)**!!Ê I'm stuck!
>
> Anto.
>
>
>
>
> maybe you could use something like midipipe to see if you could send midi to
> qc.
> just wondering how to help you debug.
>
> On 11/16/05, Antonio TARANTINO <email@hidden> wrote:
>
> Hmmm... well, I tried this, but it didn't work.
> Anyway, phisical ports should be present (and they are) anyway. But they
> don't work. Thanks anyway.
>
> I can't believe I'm the only one having this kind of problem!
>
> And concerning the channel: yes, I read about it, they are ok :
> grey=selected ;Ê white=deselected.
>
> Bye
>
> P.S.
>
> I hope I'm using the list correctly.
>
>
>
> On Nov 16, 2005, at 7:09 PM, michael markert wrote:
>
>
>
> I found that sometimes virtual ports are not recognized.
> Try opening all your musical software (with creation of virtual ports)
> first, then launch QC again Ð
>
> (sorry, if this hint won't help; for me it has been too obvious and I
> remember having clicked around for an hour untill I restarted everything and
> then it worked...)
>
>
> Also: I think the channels are all pre-selected; if you clicked on one of
> them, you might have _disabled_ the channel. I remember it has been an issue
> on this list some time ago...
>
>
> regards,
> Michael
>
>
> Am 16.11.2005 um 14:08 schrieb Antonio TARANTINO:
>
> Hi.
> I'm not a developper, I am rather a musician, but It looks like Qc is the
> ideal solution from my audio-video project. I sterted using it, but I'm
> having trouble with the MIDI controlers.
>
> TheyÊ output "0", i.e. they have no reaction.
>
> I activated the MIDI device as "source".
> I selected the channel (grey), and the octave (for MIDI note), I even tried
> to select all the midi channels and play all the notes, use all the phisical
> controller.
> The hardware is ok, the computer receives correctly, everything work fine
> with other application, but nothing happens in QC. And it's the same for all
> the MIDI devices (I have a few).
> Maybe a clue: in the inspector all the device are present, but some of them
> with the generic name (i.e. "port 1" or "Midi port") and some other with
> their specific name ("Bidule 1"). But none of them work. Is this relevant?
>
>
> Am I missing something? Is there a known issue with MIDI controlers? Is
> there a solution?
>
> Thank you and please excuse my english.
>
>
>
> _________________
>
> Antonio TARANTINO
> email@hidden
> _________________
>
>
>
> _________________
>
> Antonio TARANTINO
> email@hidden
> _________________
>
> Ê_______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Quartzcomposer-dev mailing listÊ Ê Ê
> (email@hidden)
> Help/Unsubscribe/Update your Subscription:
> http://lists.apple.com/mailman/options/quartzcomposer-dev/email@hidden
>
> This email sent to email@hidden
>
>
>
> _________________
>
>
>
>
> Antonio TARANTINO
>
> email@hidden
>
> _________________
>
>
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Quartzcomposer-dev mailing list
> (email@hidden)
> Help/Unsubscribe/Update your Subscription:
> http://lists.apple.com/mailman/options/quartzcomposer-dev/email@hidden
>
> This email sent to email@hidden
>
>
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Quartzcomposer-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/quartzcomposer-dev/email@hidden
This email sent to email@hidden
