UnicodeEncodeError: 'ascii' codec can't encode character u'xf0' in position 2: ordinal not in range(128)įile “LiveControl.py”, line 282, in _add_repeater Help it doesnt work everytime i install it says an error in the įile “LiveControl.py”, line 321, in OnOscService I've stored all WiFi settings in both devices and can fire up in no time and be controlling. I really have got this running well here…. just half the channels and double their size maybe? otherwise iPad's are the only way I guess…Īnyway, you've done some superb work…. it'd be good to be able to just un-arm the channel straight after clip recording….ģ) more pages with bigger buttons…. at the moment, you have to go to another screen to arm record…then back to another screen to record a clip, then play it back…. On the iPodTouch, I do find it a little fiddly, there's always a danger of hitting the wrong parameter, and I've got a couple of suggestions that might just get me to donate if they're possible to implement in the future….ġ) There's no pads for making beats, this would be truly amazing, nine pads and an XY on the side for reverb splashes on snares etc….Ģ) Clip record and play function…. I am about to perform a sonic presentation for my degree in Music BA using TouchOSC – Livecontrol – Ableton (latest vers) I love the work you've done with livecontrol, I have no idea how you did it (I don't code…) but I think Apple sold another iPad, not because of their propaganda, but because of your LiveControl thing □ When the device is on in Ableton, the button should be red-filled, and empty when the device is off. In the device tab, the on/off button on the corner left should be a toggle button. the XY pad is … magic ! And so easy to use, I mean … just wow ! Even if it's not very easy to use on an iPod Touch, the sequencer editor is magic, I was waiting something that works this way for a long time !! the feedback on the volume faders (the green right and left levels) and in the clip launcher (position of the clip while playing). However, some points made this way more interesting: I did an extra bit of code so that the 4 bytes after the initial 0xF0 are either the hex for “NAME” (for a name change) or “COLR” (for a color change): .After some time trying to understand why it didn't work on my computer* I finally succeed !įirst of all I thought it was an emulation on µ from jazzmutant, without the need of maxforlive and obviously the lemur. I had to take somewhat a sinuous path to convert a number in Java to a 24-bit color (8bit per channel as that’s what TouchOSC accepts) There’s a rounding discrepancy between the 0…1 scale of the RGB float numbers output in the mOnColorChange function, and the 0…255 output scale: mine ends at 254. So - I wanted to do the same with Colors. Sorry there’s been a lot of edits to this answer - lots of bits that I solved during the day. OSC is not flatlining as some people thought, even here, in previous posts, and is extensively supported by some of the competition (Logic, Reaper to name a few). Nuendo has got some OSC support for position-tracking devices - proof enough that OSC support is already present in some form and does not have to be built from the grounds up OSC seems to be a good way to do that.Ĭubase Pro and Nuendo can already pass strings like the track name to Cubase iC Pro, via the SKI Remote, so it’s doable to say the least. OSC applications like TouchOSC do an amazing job as MIDI controllers, however I’d love to see the name of the “Selected Track” in my templates. I know - this is a revamp of an old topic, but there’s good ground for it, based on two points: Is it possible to have some OSC functionality implemented in the MIDI Remote Mapping Assistant? I have a request or, worst case scenario, a question for the developing team (if we didn’t scare you all away already).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |