Statistics: Posted by yooha22 — 28 Sep 2011, 00:33
]]>
I really want to try Your Patch , really amazing . but the thing is im new to Osc and everywhere i go there are tutorials on osc in mac , can point me to the right direction for Win7 ,
much much appreciated .
Statistics: Posted by yooha22 — 26 Sep 2011, 23:20
]]>
http://img809.imageshack.us/img809/941/usinesquare.jpg
EDIT:never mind the skull,i got 2 monitors connected but only use my 27 inch
Statistics: Posted by ErotiCore SteNch — 02 Aug 2011, 23:23
]]>
i begin to think about something..will have more time later
Statistics: Posted by nay-seven — 02 Aug 2011, 23:22
]]>
hope you know what i mean
Statistics: Posted by ErotiCore SteNch — 02 Aug 2011, 22:45
]]>
Statistics: Posted by nay-seven — 02 Aug 2011, 22:24
]]>
Statistics: Posted by ErotiCore SteNch — 02 Aug 2011, 20:48
]]>
]]>
it's supposed to receive the audio/midi clip lenght ang warp/loop infos if there is a clip.
found it:
the LV_SELECTCLIP sendbus is based on clipsnb/selectrack/scrollx getbus,
i think it should be scroll Y.
so, here is a working solution:
replaced LV_SELECTCLIP by LV_SCROLL_Y,
added a 'pass if change' between the osc receive and the loop switch,
and linked data 1 and 2 between 'loopall' and 'loop all set' osc send.
Statistics: Posted by Fléau — 12 Jan 2011, 10:44
]]>
i prefered nearly redo all from scratch in a more clean way for v2 and i changed many adrress tags in the python files. ill do my best to provide it soon,but the full version will be avaible with next usine 5.5.
but i may have a file ready for 5.25 with only the matrix (no mixer, just clip launcher but scalable and preload) i can maybe post at the end of the week..i ll check asap
Statistics: Posted by 23fx23 — 11 Jan 2011, 21:30
]]>
but do not receive anything at all,
i'm totally newbie with osc and python, how can i resolve that?
thanks,
bérénice.
Statistics: Posted by Fléau — 11 Jan 2011, 17:20
]]>
anyway cool if no weird behaviour if triggering several!!! maybe the system i made can quick select clips one after the other and launch them, giving the impression of multitouch with quantize..
In fact all is multitouch if touch from differents part: ie can solo one track while launching a clip or setting a fader, but on the same
function, ie solos, it's not cause matrix is not multitouch yet, i don't think i can do something until matrix get multitouch.
but volume faders on V2 are based on step modules, wich i beleive is multitouch, (not buttons, faders), so should work..
about clip infos I made a completely different system on V2, wich make a brute force request of all single clips one after the
other for a total preload (a bit long at start, but then ultra fast and can be saved on reopen), so that there seems to have
no more corrupt datas in names an colors, that's the only way i found for stable results out of liveOSC. I got in touch with Ipad TouchAble guys and they went to exactly same system after long searchs, also i think there was no independant borders colors on V1 ya use, it's only on V2, wich is much more readable now.
yeah i understand it can be colorfull, that was a voluntary decision to quick identify tracks (my kick is red, HH blue, snare yelow, ect),
but I will see if i can give more controls over that, maybe a global saturation, lum fader, (still they will pick track colors),
note you can decide of track colors,( wich are also mutes and volume faders colors )via the color of first clip in the track in live, so you can make ie all them blue less satured if putting a first scene filled with blue clips... (or the color ya want)..
Statistics: Posted by 23fx23 — 30 Sep 2010, 16:50
]]>
about multitouch... its a bit weird... normal faders like master fader, effects knobs... can be controlled in multitouch.
but the main faders (what is more a hold down buttom) is not working in multitouch :/ i think its a script problem, maybe?!
the matrix seems to work here as multitouch... hehe.. maybe i am wrong, but i can press 3 4 clips at same time and it start to play.
about the clip information, on my system i got most time problems with the matrix, clip names are not shown correct, the colors are not correct and thats why i cant see the white border, which clip is playing
about colors, i am not meaning colors in clip view, that is great like it is... but i wish a thinner color design for volume meters and mute buttoms... this is sometimes so crazy color full, pink mixed with yellow and a dark grey is not so beautyful
but anyway great work!!!
regards erik
Statistics: Posted by electrixx — 30 Sep 2010, 11:50
]]>
Unfortunatly ive got no multitouch to test, but normally
They should work multitouch now. It will take me a certain amount of time to make all parts multitouch since i dont have the hardware and my base module
Matrix is not yet multitouch, but as soon as booth will be true, it will be full multitouch, with why not a pinch for zoom :;
-one color sheme what maybe is easy to change for end-user
Not easy because most colors depends from tracks colors clips, mute, solos status or volumes values inside scripts, and i use a lot bmp, wich make hard to track colors to change with the classic edit layout, but i have to think about how to get more controls.
-clip playing information inside a clip which is playing
Now playing clips have white borders, if ya mean a fader for position
Matrix dont allow this yet, and my feel is that would slow down scrolling,
So i made a compromise with some header track faders in v2.
-send faders (not from the tracks) i mean like a mixer view
You mean the return faders? Yeah i got to focus on that next week,
I have let return track a bit left..
Statistics: Posted by 23fx23 — 30 Sep 2010, 01:55
]]>
first of all:
-multi touch fader support (its not working right now)
-one color sheme what maybe is easy to change for end-user
-clip playing information inside a clip which is playing
-send faders (not from the tracks) i mean like a mixer view
thats i would love
))Statistics: Posted by electrixx — 29 Sep 2010, 14:48
]]>
how i said, i had that problem with the osc.py (32bit)..... there i got the osc message /live/tempo on a volume fader...
when i copied afterwards the osc.py (64bit) in midi remote scripts/liveosc it works perfectly, but i am not on 64bit windows, thats a bit weird.
maybe somebody can reproduce it, and then its just the readme.txt what you need to change
)i am looking forward to V2
thanks for amazing work mate
Statistics: Posted by electrixx — 28 Sep 2010, 10:37
]]>
ok so that works, cool! , indeed interesting to know! i cound't check on win32.. so you copied the OSC.py of 64bit Folder and replaced the other? mmmm may I have inverted the two files by error...if so ooops
so it may explain some others pb some users met, 32 bits users should do the same...and maybe 64 should test the other file
as well, by waiting a fresh V2..
Statistics: Posted by 23fx23 — 28 Sep 2010, 00:49
]]>
you mean the volumefaders??? indeed that's really strange, both should look like: /live/volume.
anyway im really close to provide V2 wich has been highly improved over V1, especially in data transferts.
i reduced all osctags to 1 to 3 letters, and optimized for the patch, made a total preload system for nolatency scrolling/constant requests, fixed few bugs in triggering, the clip positions are now computed locally so globally the data transferts have been reduced by 4, with much more stable results. there were also few things in liveosc script and the patch that could slow down live a lot i finally could identify and fix,
i make a last round check this week, and i should provide a beta version i hope next week. i let the extra stuff for later(midi keys/pads) but want a very stable and responsive grid/mixer fixed scalable base setup.
think start to got it only now ..atlast , was a very long figth with really lunatic liveosc, that have a high tendency to truncate datas when things could be sooo much simpler,..anyway i won a battle over the beast, it does what i want now.
Statistics: Posted by 23fx23 — 28 Sep 2010, 00:42
]]>
i am on windows 32 bit... but i copied the osc file for 64 bit os in ableton liveosc folder...
now works all!!!
hope it can help for other users too
Statistics: Posted by electrixx — 28 Sep 2010, 00:35
]]>
in my situation is a bit strange... all is working in both directions (sometimes small lags, but ok),
but no sliders from usine to live... in other direction its working.
when i trace the network, i can see following information:
1. i move in ableton a fader > i get /live/fader
2. i move in usine a fader > /live/tempo
strange isnt ?
Statistics: Posted by electrixx — 27 Sep 2010, 23:40
]]>
]]>
here the new Matrix edition:
________________________________
and little vid
http://www.youtube.com/watch?v=Hgf7nXyLGJ8
...now the hardware need to follow!
hope to finish and post asap, but need a bit of time to implement pads and keys.
Statistics: Posted by 23fx23 — 03 Sep 2010, 02:52
]]>
on open I usually press "reset' so it flush the datas, then rebuild, then the scripts are fed with datas from live and don't show errors anymore.
note the tempo can be controlled from the interface in bi directianal way normally, but not from Usine main tempo directly. one fisrt open you might need to change from tempo/vol/cross in the list on the interface and get back to the one you wanna control so it updates asking ableton, then you can change the value, it might not work on first open cause it has no value to set in memory. i will recheck but here it seems working ok, i don't see.... If you wana debug and see messages from live,
you can activate "trace OSC in" in osc preference to see messges comming from live, you can temp swich of vu_meters,
clips position ect turning down the knobs of the device to easier check datas are send. but as you receive tempo, there
should be no reasons you don't receive all in local mode, as well as if you can interact from the interface, all should work,
there are few tricky init problems like this one, sometimes need to change a track or item selection first time to feed the
memories of the script.
Anyway Ive started working a lot on a next important update 1.2 version this we, checking several scripts error like this one, and all repatching using Matrix instead of panels, (as a short coming one will allow colors and captions). I identified few trigering problems that react much better now especially scenes and clip grid, made a system with differents colors for cross A and B and other various improvements in visual feedback, using borders colors, and found a more stable way to force live reupdates correctly clips status that could be weird on senes lauch due to my script and overload,
but main big work was to replace
all independants panels by matrixes, and matrix allow ie to scale vertically the grid to display from 1 to 8 rows so they can be larger if need more precision, and move/scale much less items if need to customize/change the layout. quite cool. so got still a certain amount of work but's it's on the way for a better version, i hope posting the new version matrix powered in next 2 weeks..
let me a bit amout of time.
st8 also told me live0sc had weird parts coded if using huge livesets, i got to check with him if he founded time to check, but i
can imagine he is busy., any way my latest tests seems quite ok with actual new patch. i ll try to provide ya a beta version asap.
Statistics: Posted by 23fx23 — 04 Jul 2010, 23:37
]]>
]]>
the default liveset is only 8 tracks and this device, nothing more.
Statistics: Posted by 23fx23 — 03 Jul 2010, 23:29
]]>