bernsee.com > OSXTools.com > FAQ

Frequently Asked Questions by Product Below you can find a small section with frequently asked questions that might help identifying and solving a particular problem. <General> Will there be a Windows version of any of your products? Like the name "OSXTools" implies, our products are for MacOS X only. There will not be a Windows version of any of our products. [Top] <NUKE4ALL> In Logic, the metronome click is recorded as notes when recording NUKE automation to a track....what can i do about it? The <Nuke4All> application can receive MIDI, too (this is needed for future functionality) AND Logic's metronome defaults to MIDI-output port "all"....which means the metronome sends MIDI to the Nuke4All app, which in turn sends it to the input of the Sequencer where it is then recorded. Solution: go to "File > SongSettings > Metronome..." and set "MIDI Port" to any value except "all" or "NUKE MIDI Destination". Done. [Top] I am using Logic and when i start Logic, i see tons of MIDI I/O displayed in the Transport bar, going up and down. At some point this stops, but the data from my <Nuke> is also not recognized any longer. Probably your default Logic song loads with a MIDI track selected in the arrange-window and it's output port is set to "all". This causes a MIDI feedback to the <Nuke>, which blows up the communication. Set the port of the channel to a different value, then open the LogicPro > Preferences > Global dialog and close it again (this will reset MIDI communication)… your <Nuke>should now work as a MIDI controller. [Top] My <Nuke> is not recognized by your app… what am I doing wrong? The software running on the <Nuke> is...well...let's just say it does some weird things. There's nothing we can do about that (and we didn't write it in the first place), but you can work around this by unplugging the <Nuke> and re-plugging it while the app is running and you'll be fine.. [Top] When I rotate one of the rotary encoders (knobs), the <Nuke> sends the MIDI-cc# assigned to it plus the cc# assigned to the stick...what's wrong? The stick controller is highly sensitive, and interprets the vibrations that turning an encoder induces into the chassis as a stick-movement, and thus sends it's values. This is a hardware design flaw that we can do nothing about. [Top] I can't seem to get the cc# sent by the stick to reach certain values, why is that? There's a setting called "Mapping" in the Stick Control section of the user interface, you seem to have it set to "Inner Circle". Set it to "Outer Circle" and you'll be ok. There's a "Mouse-Over" info panel that explains what this setting does.. [Top] Why can't I change the chord the button on the <Nuke> sends? Due to a(nother) design flaw in the <Nuke>hardware, it cannot send any control data while this button is pressed, so sending note events is pretty pointless anyway (except for quick testing whether the <Nuke> does indeed transmit MIDI). In a future update this button will be put to a new, more practical use, so we figured out it's not worth the effort to make the chord editable. [Top]

Last change: 15.12.2005, ©2005 S. M. Bernsee, all rights reserved. Content subject to change without notice. Content provided 'as is', see disclaimer.