thread starter this problem is solved, but a new problem knocked my door. look at the bottom of this page if you wan't to see.
Recent blogs: tinnitus (hearing noise within your ears)
Replies
FINALLY! i discoverd the problem: the subpatch i made for ducking when samplestarttime is changed caused a delay of a few milliseconds.
problem now is i don't know how to make a system for doing that without causing delay.
Recent blogs: tinnitus (hearing noise within your ears)
Glad you figured it out! (looking at isolated problems is fine but the idea of trying to debug other people's complex patches gives me the creeps)
if you could describe the problem in more detail (or post a patch that I could open in max 4 - won't be possible if you're using sync objects...) i'd be happy to lend a hand.
as cbit says, it'd be way easier if you can demonstrate the problem in a simpler patch. I've never done any live sampling so i'd love to take a look at what you're doing tho. the problem i posted about @ is fixed. i have a big problem with making my patch sample accurate know. it seems like msp~ is inaccurate while i have pretty good gear(unibody 2,4ghz MBP and i focusrite saffire pro10 soundcard). if you could try and help me/know what could cause this that would be great. look her for more info: link
(@ flies: the core of what i use for live sampling is a record~ object recording to a buffer~ and a play~ object driven with phasor~ playing that. you could maybe more easily do this with groove~ if you don't care that much about sampleaccuracy)
Recent blogs: tinnitus (hearing noise within your ears)
ssb0 said: "if you could try and help me/know what could cause this that would be great. look her for more info: link" what those guys are saying is correct. you need to trigger your recording with signals if you want precision down to the sample, which means using something other than record~, which is triggered by a message. i would suggest poke~ or tapin/out. (tapin/out can be very effective for many tasks. you can even granulate by scrubbing the tapout~ object.) commands are definitely not signal accurate. signals are. peter castine's suggestion of lowering your sample vector size may work, but bringing it all the way down to 4 is probably impractical. ps it's pretty amazing how often castine mentions his (not free) bundle when offering 'assistance'....
the problem is not being record but a simple patch like this:
----------begin_max5_patcher---------- 432.3ocyUF0aCBBDG+Y8SAgmsMfsV0k8x9brzrfJskEELJl0sl1O6SfZa2xl ilZ57EHdbd2+6GGvNWGXhXKsFBd.7LvwYmqii1jxfywucfEjso4jZsavU4Bd SAzyrTIQltgwW+REMUZBi+BzTjGvOVOsXtZDGMEAVd7eXY5.IRdchOF0EoUB tjSJn50dphQx6VoMcLdNUpyO9rQQiryp+EAol8gNHXU9MlMdJeujZjnpHHRn G.lP3qgfkJ2165pF7rjCb5asUPmFkzs5xGJYEzJKnSndZ1rdoCJ5Joi+vRmA kLzr0zC8QFeCYlaHSb+jI7eouQ2tbSsMIMRofaAFLMH9mF+YLDbEEKt2pZH2 pe7.XBZZfEUoYZte+a13A4X.9J2rqYq4sIXHASFMWRr4P.xbHHpetLLWdNB3 R4FRsn5..+2nAGomBB5CM333QSKiVevbF+6uypqQk8uxqZQSUZW.O8L.3bcl QqkLNQxZuG4BuTOkdgWaXYYTsCcpsfkUJXb4QY7K6e1qpPaTkV63QopFerJ3 NqJrUpJ7NqJjUpBeWUk9BEKT0sbFr8i8teR55i5R -----------end_max5_patcher----------- @ 1hz timer gives an interval between 9998 and 1002 ms with a vector size of 64, overdriveon and sceduler in audiointerrupt.
Recent blogs: tinnitus (hearing noise within your ears)
fyi i cant open patches formatted that way cuz i'm max 4. there's an option to copy/paste in a more verbose format, i think.
maybe you can copy this into a patcher?
{ "boxes" : [ { "box" : { "maxclass" : "flonum", "patching_rect" : [ 260.0, 290.0, 64.0, 18.0 ], "id" : "obj-210", "fontname" : "Arial", "numinlets" : 1, "numoutlets" : 2, "fontsize" : 10.0, "outlettype" : [ "float", "bang" ] } } , { "box" : { "maxclass" : "newobj", "text" : "timer", "patching_rect" : [ 260.0, 270.0, 33.0, 18.0 ], "id" : "obj-208", "fontname" : "Arial", "numinlets" : 2, "numoutlets" : 2, "fontsize" : 10.0, "outlettype" : [ "float", "" ] } } , { "box" : { "maxclass" : "newobj", "text" : "edge~", "patching_rect" : [ 220.0, 240.0, 39.0, 18.0 ], "id" : "obj-207", "fontname" : "Arial", "numinlets" : 1, "numoutlets" : 2, "fontsize" : 10.0, "outlettype" : [ "bang", "bang" ] } } , { "box" : { "maxclass" : "button", "patching_rect" : [ 220.0, 270.0, 20.0, 20.0 ], "id" : "obj-205", "numinlets" : 1, "numoutlets" : 1, "outlettype" : [ "bang" ] } } , { "box" : { "maxclass" : "newobj", "text" : "<~ -0.5", "patching_rect" : [ 220.0, 220.0, 42.0, 18.0 ], "id" : "obj-201", "fontname" : "Arial", "numinlets" : 2, "numoutlets" : 1, "fontsize" : 10.0, "outlettype" : [ "signal" ] } } , { "box" : { "maxclass" : "newobj", "text" : "delta~", "patching_rect" : [ 220.0, 200.0, 38.0, 18.0 ], "id" : "obj-200", "fontname" : "Arial", "numinlets" : 1, "numoutlets" : 1, "fontsize" : 10.0, "outlettype" : [ "signal" ] } } , { "box" : { "maxclass" : "newobj", "text" : "phasor~ 1", "patching_rect" : [ 220.0, 180.0, 55.0, 18.0 ], "id" : "obj-199", "fontname" : "Arial", "numinlets" : 2, "numoutlets" : 1, "fontsize" : 10.0, "outlettype" : [ "signal" ] } } ], "lines" : [ { "patchline" : { "source" : [ "obj-199", 0 ], "destination" : [ "obj-200", 0 ], "hidden" : 0, "midpoints" : [ ] } } , { "patchline" : { "source" : [ "obj-200", 0 ], "destination" : [ "obj-201", 0 ], "hidden" : 0, "midpoints" : [ ] } } , { "patchline" : { "source" : [ "obj-201", 0 ], "destination" : [ "obj-207", 0 ], "hidden" : 0, "midpoints" : [ ] } } , { "patchline" : { "source" : [ "obj-207", 0 ], "destination" : [ "obj-205", 0 ], "hidden" : 0, "midpoints" : [ ] } } , { "patchline" : { "source" : [ "obj-207", 0 ], "destination" : [ "obj-208", 0 ], "hidden" : 0, "midpoints" : [ ] } } , { "patchline" : { "source" : [ "obj-207", 0 ], "destination" : [ "obj-208", 1 ], "hidden" : 0, "midpoints" : [ ] } } , { "patchline" : { "source" : [ "obj-208", 0 ], "destination" : [ "obj-210", 0 ], "hidden" : 0, "midpoints" : [ ] } } ] }
Recent blogs: tinnitus (hearing noise within your ears)
as i posted on the cycling '74 forum:
normally i use a signal vectorsize of 64 (and an I/O size of 256 but i don't thinks that matters?). i thought that was pretty small but even with a phasor of 1 hz it causes inaccuaracy of @ highest 2 ms. does it time that way with that vector size on your computers too? when i use a signal vector size of 16 an a phasor of 1Hz the intervalls are rock solid but when i calcute in example 145bpm wich makes phasor go at 2.41667Hz the intervalls switch beteen 413.666656 an 414 ms. even with a vector size of 2 the timed intervalls sporadicly switch from 413.791656 to 413.83334 wich is a vector size i think i couldn't affort. is this normal or is it only my computer? i tried using the internal souncard but this gives me even more inaccuracy on all these settings i tried with my other soundcard, wich as a 'focusrite saffire pro10'. i also can't find any background processes wich use ramrkable much cpu or memory. strange thing is that when i use a metro at a vector size of 64 at whaterver floating point interval(tried 4n with 145bpm, 414.75689 ms, and just 100 ms) it is rock rock solid.
Recent blogs: tinnitus (hearing noise within your ears)
just out of curiosity, what sampling rate are you running at? 64 samples at 44.1khz is 1.45 ms.
i'll try and load the patch when i have a chance (unfortunatlye probably not today) Signup to comment
|