Jump to content

ibt

Member
  • Posts

    318
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

ibt's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. Dear Logic devs, in future, please let Logic send out OSC messages by default.
  2. I've got some results which might help, using the OSCulator Plugin. Once it's installed, OSCulator will receive /logic/track/level OSC messages from Logic for it's volume fader movements. Might take a bit more work to set up than in Ableton though...
  3. Looking again at your earlier screenshot and that 2nd YouTube video, I now see that those messages in OSCulator came from the M32's faders, not from Logic's. So you can ignore a lot of what I've said! The problem might be in Logic like you say... ...the OSCulator forum is your best bet.
  4. Logic is sending out OSC messages correctly in that screenshot... In OSCulator/Parameters/MIDI/MIDI Output Ports, have you selected the right port for the X32?
  5. That's positive - can you share a screenshot of those messages? You might need to use Demux (look in the OSCulator manual).
  6. When you move that fader in the DAW, does OSCulator receive any messages? In the Environment, did you cable/connect the output from that channel strip into the MIDI Instrument Object (with OSCulator's port selected) as I mentioned?
  7. Have you tried the Mackie/HUI protocols?
  8. 2 - if you want to send a MIDI signal from Logic to OSCulator, you would create a MIDI Instrument Object in the Environment, select it, and in the inspector panel on the left where it says Port, click the dropdown menu and you should see your OSCulator destinations, with their port numbers in brackets Then you need to connect/cable the stream of MIDI messages you want to send from Logic to OSCulator, to that MIDI Instrument Object. Beware of MIDI feedback if you're sending MIDI between OSCulator and Logic using the same OSCulator port... if that's a problem you could create a 2nd OSCulator document to receive the MIDI from Logic Also, I'd recommend the OSCulator forum - Camille, the developer, is v helpful
  9. ...that could add another dimension to the Environment : )
  10. Will be very interesting if it allows multitouch control, but I expect it will only allow one point of control ie cursor.
  11. ...meanwhile, somewhere else on the internet, on some other Logic Pro Help forum: User: Argh! Logic Pro is broken! It doesn't work! Other David: Did you connect the Device to the Physical Input Object? User: Eh? Other David: You have to put the Device in your mouth! It's on page one of the manual...
  12. Had to do a double take when I saw Logic Pro for sale behind the counter in a local shop: what the...? I wonder do they have a LogicProHelp forum too?
  13. Glad to hear that's the info you wanted. Controller Assignments are good (could be better... lots of threads here about that), but, you also have to 'handle with caution'! Logic does automatically save your CA changes on quitting but... it's advisable that, after you've made any significant changes in CA, you copy and save your cs preferences file - where assignments, zones, modes etc. are stored - to a 2nd location. If you have made changes worth keeping, then, after quitting Logic, visit your User Library>Preferences folder, look for the com.apple.logic.pro.cs file, copy it and save it somewhere safe (Dropbox, iCloud etc.), into lt's own, dated folder.
  14. You can... you'll need to set up two or more Modes and use 'Mode Change' ( -> 08:15 in the video)
  15. No guarantees, but you might be able to install future macOS versions even after your laptop/desktop becomes 'officially unsupported', as in: MacOS Mojave on Unsupported Macs You'll possibly miss out on some novel feature or other that a future OS introduces, and somewhere down the line, a future version of Logic (11.0?) will function sub-optimally, or not at all, on a future macOS (10.15, 10.16 etc.)... something something obsolescence... (sighs).
×
×
  • Create New...