Intercept APC40 MIDI
Hi,
Does anyone know how I'd intercept the APC40 MIDI so I can start to make changes to it.
I've tried using a virtual MIDI cable, feeding the MIDI into PD, then into the cable: and recieving MIDI back from the cable and sending it to the APC40, but:
1: This causes a weird feedback issue: when I turn a knob Ableton gets updated and immediately sends a MIDI response, which PD sends back to the APC40. This causes slow knob response and flickering: it looks like the APC40 is getting confused by the returning MIDI signals.
The same thing does not happen when the APC40 and Ableton are connected together directly: even though there is two-way MIDI. Obviously the issue is solved somehow: but I don't know how to do it.
2: A lot of the APC functions simply doesn't work: although I've simply done midiin --> midiout with all the available MIDI interfaces. The handshake between the APC and Ableton supposedly goes through MIDI, and other people have got it working with Bome's MIDI Translator: so it's definitely possible. Any ideas on how to get it working?
Cheers,
Will.
Rumble Box
should become a kind of groove box but i guess i tinkered it to f**k. it's a damn cpu hog and it will spit out a whole list of errors to the pd window when loading.........
....BUT BESIDES ALL THAT: it sound pretty nice (in my opinon!) ....
so, if you give it a chance, tell me what you think about it.
EDIT: Note, when you open the patch (RUMBLE_BOX.pd) there will be no sound until you assigned midi in and midi out.
the sequencer sends out midi notes to the single sound generator channels, so you have to send midi out to midi in - i did this with midi ox and midi yoke, i connected "midi yoke in 1" to "midi yoke out 1" in midi ox and assigned them as midi in/out in pd.
Can't run PD 0.42-4 under OSX 10.4.11
I'm getting a similar problem on 10.5.7. I'm also getting crashes when trying to select my M-Box Micro as the output in Pd..
Process: mds [21]
Path: /System/Library/Frameworks/CoreServices.framework/Frameworks/Metadata.framework/Support/mds
Identifier: mds
Version: (???)
Code Type: X86 (Native)
Parent Process: launchd [1]
Date/Time: 2008-09-23 14:48:39.862 +1000
OS Version: Mac OS X 10.5.4 (9E17)
Report Version: 6
Exception Type: EXC_BAD_ACCESS (SIGBUS)
Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000000
Crashed Thread: 18
Application Specific Information:
/SourceCache/Spotlight/Spotlight-398.18/index/ContentIndex/CIMerging.c:1958: failed assertion 'changes->docIds[0].count==0'
(Error) IndexStore in SIStoreDirytySDBChunks:Error storing dirty sdb pages: 30
Thread 0:
0 libSystem.B.dylib 0x95fb84a6 mach_msg_trap + 10
1 libSystem.B.dylib 0x95fbfc9c mach_msg + 72
2 com.apple.CoreFoundation 0x92bda0ce CFRunLoopRunSpecific + 1790
3 com.apple.CoreFoundation 0x92bdacf8 CFRunLoopRunInMode + 88
4 mds 0x00058504 0x1000 + 357636
5 mds 0x0000e6c3 0x1000 + 54979
6 mds 0x00005956 0x1000 + 18774
Thread 1:
0 libSystem.B.dylib 0x95fb84a6 mach_msg_trap + 10
1 libSystem.B.dylib 0x95fbfc9c mach_msg + 72
2 com.apple.CoreFoundation 0x92bda0ce CFRunLoopRunSpecific + 1790
3 com.apple.CoreFoundation 0x92bdacf8 CFRunLoopRunInMode + 88
4 mds 0x00058504 0x1000 + 357636
5 mds 0x0000d61d 0x1000 + 50717
6 mds 0x000582d2 0x1000 + 357074
7 com.apple.Foundation 0x9631bf1d -[NSThread main] + 45
8 com.apple.Foundation 0x9631bac4 __NSThread__main__ + 308
9 libSystem.B.dylib 0x95fe96f5 _pthread_start + 321
10 libSystem.B.dylib 0x95fe95b2 thread_start + 34
Thread 2:
0 libSystem.B.dylib 0x95fb84a6 mach_msg_trap + 10
1 libSystem.B.dylib 0x95fbfc9c mach_msg + 72
2 com.apple.CoreFoundation 0x92bda0ce CFRunLoopRunSpecific + 1790
3 com.apple.CoreFoundation 0x92bdacf8 CFRunLoopRunInMode + 88
4 mds 0x00058504 0x1000 + 357636
5 mds 0x0000d640 0x1000 + 50752
6 mds 0x000582d2 0x1000 + 357074
7 com.apple.Foundation 0x9631bf1d -[NSThread main] + 45
8 com.apple.Foundation 0x9631bac4 __NSThread__main__ + 308
9 libSystem.B.dylib 0x95fe96f5 _pthread_start + 321
10 libSystem.B.dylib 0x95fe95b2 thread_start + 34
Thread 3:
0 libSystem.B.dylib 0x95fb84a6 mach_msg_trap + 10
1 libSystem.B.dylib 0x95fbfc9c mach_msg + 72
2 com.apple.CoreFoundation 0x92bda0ce CFRunLoopRunSpecific + 1790
3 com.apple.CoreFoundation 0x92bdacf8 CFRunLoopRunInMode + 88
4 mds 0x00058504 0x1000 + 357636
5 mds 0x0000d663 0x1000 + 50787
6 mds 0x000582d2 0x1000 + 357074
7 com.apple.Foundation 0x9631bf1d -[NSThread main] + 45
8 com.apple.Foundation 0x9631bac4 __NSThread__main__ + 308
9 libSystem.B.dylib 0x95fe96f5 _pthread_start + 321
10 libSystem.B.dylib 0x95fe95b2 thread_start + 34
Thread 4:
0 libSystem.B.dylib 0x95fb84a6 mach_msg_trap + 10
1 libSystem.B.dylib 0x95fbfc9c mach_msg + 72
2 com.apple.CoreFoundation 0x92bda0ce CFRunLoopRunSpecific + 1790
3 com.apple.CoreFoundation 0x92bdacf8 CFRunLoopRunInMode + 88
4 mds 0x00058504 0x1000 + 357636
5 mds 0x0000d686 0x1000 + 50822
6 mds 0x000582d2 0x1000 + 357074
7 com.apple.Foundation 0x9631bf1d -[NSThread main] + 45
8 com.apple.Foundation 0x9631bac4 __NSThread__main__ + 308
9 libSystem.B.dylib 0x95fe96f5 _pthread_start + 321
10 libSystem.B.dylib 0x95fe95b2 thread_start + 34
Thread 5:
0 libSystem.B.dylib 0x95fb84a6 mach_msg_trap + 10
1 libSystem.B.dylib 0x95fbfc9c mach_msg + 72
2 com.apple.CoreFoundation 0x92bda0ce CFRunLoopRunSpecific + 1790
3 com.apple.CoreFoundation 0x92bdacf8 CFRunLoopRunInMode + 88
4 mds 0x00058504 0x1000 + 357636
5 mds 0x0000d6a9 0x1000 + 50857
6 mds 0x000582d2 0x1000 + 357074
7 com.apple.Foundation 0x9631bf1d -[NSThread main] + 45
8 com.apple.Foundation 0x9631bac4 __NSThread__main__ + 308
9 libSystem.B.dylib 0x95fe96f5 _pthread_start + 321
10 libSystem.B.dylib 0x95fe95b2 thread_start + 34
Thread 6:
0 libSystem.B.dylib 0x95fbf68e __semwait_signal + 10
1 libSystem.B.dylib 0x960108e0 pthread_cond_timedwait$UNIX2003 + 72
2 mds 0x0000a3f7 0x1000 + 37879
3 libSystem.B.dylib 0x95fe96f5 _pthread_start + 321
4 libSystem.B.dylib 0x95fe95b2 thread_start + 34
Thread 7:
0 libSystem.B.dylib 0x95fdc1ba read$UNIX2003 + 10
1 libSystem.B.dylib 0x95fe96f5 _pthread_start + 321
2 libSystem.B.dylib 0x95fe95b2 thread_start + 34
Thread 8:
0 libSystem.B.dylib 0x95fe8f66 kevent + 10
1 libSystem.B.dylib 0x95fe96f5 _pthread_start + 321
2 libSystem.B.dylib 0x95fe95b2 thread_start + 34
Thread 9:
0 libSystem.B.dylib 0x95fb84a6 mach_msg_trap + 10
1 libSystem.B.dylib 0x95fbfc9c mach_msg + 72
2 com.apple.CoreFoundation 0x92bda0ce CFRunLoopRunSpecific + 1790
3 com.apple.CoreFoundation 0x92bdacf8 CFRunLoopRunInMode + 88
4 mds 0x00058504 0x1000 + 357636
5 mds 0x0008714c 0x1000 + 549196
6 mds 0x000582d2 0x1000 + 357074
7 com.apple.Foundation 0x9631bf1d -[NSThread main] + 45
8 com.apple.Foundation 0x9631bac4 __NSThread__main__ + 308
9 libSystem.B.dylib 0x95fe96f5 _pthread_start + 321
10 libSystem.B.dylib 0x95fe95b2 thread_start + 34
Thread 10:
0 libSystem.B.dylib 0x95fb84a6 mach_msg_trap + 10
1 libSystem.B.dylib 0x95fbfc9c mach_msg + 72
2 com.apple.CoreFoundation 0x92bda0ce CFRunLoopRunSpecific + 1790
3 com.apple.CoreFoundation 0x92bdacf8 CFRunLoopRunInMode + 88
4 mds 0x00058504 0x1000 + 357636
5 mds 0x00054157 0x1000 + 340311
6 mds 0x000582d2 0x1000 + 357074
7 com.apple.Foundation 0x9631bf1d -[NSThread main] + 45
8 com.apple.Foundation 0x9631bac4 __NSThread__main__ + 308
9 libSystem.B.dylib 0x95fe96f5 _pthread_start + 321
10 libSystem.B.dylib 0x95fe95b2 thread_start + 34
Thread 11:
0 libSystem.B.dylib 0x95fb84a6 mach_msg_trap + 10
1 libSystem.B.dylib 0x95fbfc9c mach_msg + 72
2 com.apple.CoreFoundation 0x92bda0ce CFRunLoopRunSpecific + 1790
3 com.apple.CoreFoundation 0x92bdacf8 CFRunLoopRunInMode + 88
4 mds 0x00058504 0x1000 + 357636
5 mds 0x00054157 0x1000 + 340311
6 mds 0x000582d2 0x1000 + 357074
7 com.apple.Foundation 0x9631bf1d -[NSThread main] + 45
8 com.apple.Foundation 0x9631bac4 __NSThread__main__ + 308
9 libSystem.B.dylib 0x95fe96f5 _pthread_start + 321
10 libSystem.B.dylib 0x95fe95b2 thread_start + 34
Thread 12:
0 libSystem.B.dylib 0x95fb84a6 mach_msg_trap + 10
1 libSystem.B.dylib 0x95fbfc9c mach_msg + 72
2 com.apple.CoreFoundation 0x92bda0ce CFRunLoopRunSpecific + 1790
3 com.apple.CoreFoundation 0x92bdacf8 CFRunLoopRunInMode + 88
4 mds 0x00058504 0x1000 + 357636
5 mds 0x00054157 0x1000 + 340311
6 mds 0x000582d2 0x1000 + 357074
7 com.apple.Foundation 0x9631bf1d -[NSThread main] + 45
8 com.apple.Foundation 0x9631bac4 __NSThread__main__ + 308
9 libSystem.B.dylib 0x95fe96f5 _pthread_start + 321
10 libSystem.B.dylib 0x95fe95b2 thread_start + 34
Thread 13:
0 libSystem.B.dylib 0x95fb84a6 mach_msg_trap + 10
1 libSystem.B.dylib 0x95fbfc9c mach_msg + 72
2 com.apple.spotlight.index 0x0022a3da _handleExceptions + 238
3 libSystem.B.dylib 0x95fe96f5 _pthread_start + 321
4 libSystem.B.dylib 0x95fe95b2 thread_start + 34
Thread 14:
0 libSystem.B.dylib 0x95fb84a6 mach_msg_trap + 10
1 libSystem.B.dylib 0x95fbfc9c mach_msg + 72
2 com.apple.CoreFoundation 0x92bda0ce CFRunLoopRunSpecific + 1790
3 com.apple.CoreFoundation 0x92bdacf8 CFRunLoopRunInMode + 88
4 mds 0x00058504 0x1000 + 357636
5 mds 0x000448f3 0x1000 + 276723
6 mds 0x000582d2 0x1000 + 357074
7 com.apple.Foundation 0x9631bf1d -[NSThread main] + 45
8 com.apple.Foundation 0x9631bac4 __NSThread__main__ + 308
9 libSystem.B.dylib 0x95fe96f5 _pthread_start + 321
10 libSystem.B.dylib 0x95fe95b2 thread_start + 34
Thread 15:
0 libSystem.B.dylib 0x95fb8506 semaphore_timedwait_signal_trap + 10
1 libSystem.B.dylib 0x95fea84f _pthread_cond_wait + 1244
2 libSystem.B.dylib 0x95fec0d3 pthread_cond_timedwait_relative_np + 47
3 com.apple.spotlight.index 0x0018b180 si_scheduler_run_waiting_timeout + 163
4 com.apple.spotlight.index 0x00176e50 runLoop + 77
5 com.apple.spotlight.index 0x00176f3c setattr_runLoop + 68
6 libSystem.B.dylib 0x95fe96f5 _pthread_start + 321
7 libSystem.B.dylib 0x95fe95b2 thread_start + 34
Thread 16:
0 libSystem.B.dylib 0x95fb8506 semaphore_timedwait_signal_trap + 10
1 libSystem.B.dylib 0x95fea84f _pthread_cond_wait + 1244
2 libSystem.B.dylib 0x95fec0d3 pthread_cond_timedwait_relative_np + 47
3 com.apple.spotlight.index 0x0018b180 si_scheduler_run_waiting_timeout + 163
4 com.apple.spotlight.index 0x00176e50 runLoop + 77
5 com.apple.spotlight.index 0x00176eaa query_runLoop + 30
6 libSystem.B.dylib 0x95fe96f5 _pthread_start + 321
7 libSystem.B.dylib 0x95fe95b2 thread_start + 34
Thread 17:
0 libSystem.B.dylib 0x95fb8506 semaphore_timedwait_signal_trap + 10
1 libSystem.B.dylib 0x95fea84f _pthread_cond_wait + 1244
2 libSystem.B.dylib 0x95fec0d3 pthread_cond_timedwait_relative_np + 47
3 com.apple.spotlight.index 0x0018b180 si_scheduler_run_waiting_timeout + 163
4 com.apple.spotlight.index 0x00176e50 runLoop + 77
5 com.apple.spotlight.index 0x0017705d flush_runLoop + 65
6 libSystem.B.dylib 0x95fe96f5 _pthread_start + 321
7 libSystem.B.dylib 0x95fe95b2 thread_start + 34
Thread 18 Crashed:
0 com.apple.spotlight.index 0x002370af _dead_beef + 11
1 com.apple.spotlight.index 0x002307c7 merge_checkAgainstUpdates + 181
2 com.apple.spotlight.index 0x00230a00 PayloadProcessDocIDRangeBitsReversed + 387
3 com.apple.spotlight.index 0x0020ef96 unpackPostingChunk + 422
4 com.apple.spotlight.index 0x0023517b mergeIndexData + 13180
5 com.apple.spotlight.index 0x001a0da6 _ContentIndexMergeIndexes + 128
6 com.apple.spotlight.index 0x001a0fe2 ContentIndexMergeIndexes + 248
7 com.apple.spotlight.index 0x0017ec59 OuterMerge + 1310
8 com.apple.spotlight.index 0x001806fe si_mergeIndex + 4007
9 com.apple.spotlight.index 0x0018aca9 si_work_queue_process + 643
10 com.apple.spotlight.index 0x0018af97 si_scheduler_once + 419
11 com.apple.spotlight.index 0x0018af97 si_scheduler_once + 419
12 com.apple.spotlight.index 0x0018b322 si_scheduler_run_waiting_timeout + 581
13 com.apple.spotlight.index 0x00176e50 runLoop + 77
14 com.apple.spotlight.index 0x00176fce compaction_runLoop + 68
15 libSystem.B.dylib 0x95fe96f5 _pthread_start + 321
16 libSystem.B.dylib 0x95fe95b2 thread_start + 34
Thread 18 crashed with X86 Thread State (32-bit):
eax: 0x00000000 ebx: 0x00230733 ecx: 0x00000000 edx: 0x00000000
edi: 0x00000000 esi: 0x00000616 ebp: 0xb0991738 esp: 0xb0991730
ss: 0x0000001f efl: 0x00010286 eip: 0x002370af cs: 0x00000017
ds: 0x0000001f es: 0x0000001f fs: 0x0000001f gs: 0x00000037
cr2: 0x00000000
Binary Images:
0x1000 - 0xb9feb mds (???) <63f8cd1f41b3382ec7d38bb5f76a20c1> /System/Library/Frameworks/CoreServices.framework/Frameworks/Metadata.framework/Support/mds
0xd7000 - 0xd8ffd com.apple.MDSChannel 1.0 (1.0) /System/Library/PrivateFrameworks/MDSChannel.framework/Versions/A/MDSChannel
0x14a000 - 0x25fff7 com.apple.spotlight.index 10.5.2 (398.18) <cc6d210e1fcd007cb427861ccd748e13> /System/Library/PrivateFrameworks/SpotlightIndex.framework/Versions/A/SpotlightIndex
0x6cf000 - 0x6d4ff7 libgermantok.dylib (???) <5608319ae54efad75bb8af543f67134f> /usr/lib/libgermantok.dylib
0x2bce000 - 0x2bceffd liblangid.dylib (???) <d1bba9ec9142b4eb33db9c24d504ac63> /usr/lib/liblangid.dylib
0x30bd000 - 0x31e4feb libmecab.1.0.0.dylib (???) <d42fb7fb40a58840dd30e4364635c245> /usr/lib/libmecab.1.0.0.dylib
0x8fe00000 - 0x8fe2da53 dyld 96.2 (???) <5013f43c4d2c33c9619011f103ec3238> /usr/lib/dyld
0x90291000 - 0x902a0ffe com.apple.DSObjCWrappers.Framework 1.2.1 (1.2.1) <43c5b91223501f917392f59fbf9d7ace> /System/Library/PrivateFrameworks/DSObjCWrappers.framework/Versions/A/DSObjCWrappers
0x90905000 - 0x9093cfff com.apple.SystemConfiguration 1.9.2 (1.9.2) <8b26ebf26a009a098484f1ed01ec499c> /System/Library/Frameworks/SystemConfiguration.framework/Versions/A/SystemConfiguration
0x9093d000 - 0x9099affb libstdc++.6.dylib (???) <6106b1f2b0b303b06ae476253dbb5f3f> /usr/lib/libstdc++.6.dylib
0x9099b000 - 0x909e1fef com.apple.Metadata 10.5.2 (398.18) <adbb3a14e8f7da444e16d2fd61862771> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Metadata.framework/Versions/A/Metadata
0x909e2000 - 0x90ac3ff7 libxml2.2.dylib (???) <1baef3d4972ee789d8fa6c1fa44da45c> /usr/lib/libxml2.2.dylib
0x90aff000 - 0x90bf3ff4 libiconv.2.dylib (???) <3f183527811098bb7332f67a1f902bfd> /usr/lib/libiconv.2.dylib
0x90bf4000 - 0x90c7ffff com.apple.framework.IOKit 1.5.1 (???) <60cfc4b175c4ef60bb8e9036716a29f4> /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit
0x92417000 - 0x9254fff7 libicucore.A.dylib (???) <5031226ea28b371d8dfdbb32acfb48b5> /usr/lib/libicucore.A.dylib
0x92551000 - 0x9256fff3 com.apple.DirectoryService.Framework 3.5.4 (3.5.4) <fe27e80e1a9e86403fd9ed16dcfe4e11> /System/Library/Frameworks/DirectoryService.framework/Versions/A/DirectoryService
0x92570000 - 0x9264ffff libobjc.A.dylib (???) <99a9ad33ca07114848fdd7580968a572> /usr/lib/libobjc.A.dylib
0x92650000 - 0x9270afe3 com.apple.CoreServices.OSServices 226.5 (226.5) <7e10d25c615a39fe1ab4d48e24a3b555> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/OSServices.framework/Versions/A/OSServices
0x92756000 - 0x92756ffa com.apple.CoreServices 32 (32) <2760719f7a81e8c2bdfd15b0939abc29> /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices
0x92b68000 - 0x92c9afff com.apple.CoreFoundation 6.5.3 (476.14) <7ef7f5db09ff6dd0135a6165872803cc> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
0x934e8000 - 0x93574ff7 com.apple.LaunchServices 289.2 (289.2) <3577886e3a6d56ee3949850c4fde76c9> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchServices.framework/Versions/A/LaunchServices
0x93de5000 - 0x93dfbfff com.apple.DictionaryServices 1.0.0 (1.0.0) <7e9ff586b5c9d02b09e2a5527d98524f> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/DictionaryServices.framework/Versions/A/DictionaryServices
0x93e13000 - 0x93e3efe7 libauto.dylib (???) <2072d673706bbe463ed2426af57a28d7> /usr/lib/libauto.dylib
0x944dc000 - 0x944e4fff com.apple.DiskArbitration 2.2.1 (2.2.1) <42908e7ecc17a83cec4afef2850ec79e> /System/Library/Frameworks/DiskArbitration.framework/Versions/A/DiskArbitration
0x94991000 - 0x94a13ff3 com.apple.CFNetwork 330.4 (330.4) <ce5b085df34a78b7f198aff9db5b52ec> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CFNetwork.framework/Versions/A/CFNetwork
0x94c22000 - 0x94df0fff com.apple.security 5.0.4 (34102) <f01d6cbd6a0f24f6c13952ed448e77d6> /System/Library/Frameworks/Security.framework/Versions/A/Security
0x950cf000 - 0x950f3fff libxslt.1.dylib (???) <59399cc446ed903fd9479526ee9f116b> /usr/lib/libxslt.1.dylib
0x955da000 - 0x95609fe3 com.apple.AE 402.2 (402.2) <d0da935e781446faa4563e7a9c587cce> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/AE.framework/Versions/A/AE
0x9563b000 - 0x956c2ff7 libsqlite3.0.dylib (???) <11311084bc4be9d4555dfac74fe7218a> /usr/lib/libsqlite3.0.dylib
0x9573a000 - 0x95741fe9 libgcc_s.1.dylib (???) <28a7cbc3a5ca2982d124668306f422d9> /usr/lib/libgcc_s.1.dylib
0x95ad9000 - 0x95ae7ffd libz.1.dylib (???) <545ca09467025f77131cfac09d8b9375> /usr/lib/libz.1.dylib
0x95e13000 - 0x95e92ff5 com.apple.SearchKit 1.2.0 (1.2.0) <5abfde5537969168b8a8743ccb9ec735> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/SearchKit.framework/Versions/A/SearchKit
0x95fb7000 - 0x96117ff3 libSystem.B.dylib (???) <a12f397abf2285077b89bd726bff5b18> /usr/lib/libSystem.B.dylib
0x96311000 - 0x9658cfe7 com.apple.Foundation 6.5.5 (677.19) <bfd4ebea1a7739dd6b523f15dca01a37> /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation
0x9662a000 - 0x9662efff libmathCommon.A.dylib (???) /usr/lib/system/libmathCommon.A.dylib
0x96bec000 - 0x96bf3ffe libbsm.dylib (???) <5582985a86ea36504cca31788bccf963> /usr/lib/libbsm.dylib
0x96bf7000 - 0x96ed1ff3 com.apple.CoreServices.CarbonCore 786.6 (786.6) <bc7c12c84fe21ae2626bdd17070aaafa> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonCore.framework/Versions/A/CarbonCore
0xfffe8000 - 0xfffebfff libobjc.A.dylib (???) /usr/lib/libobjc.A.dylib
0xffff0000 - 0xffff1780 libSystem.B.dylib (???) /usr/lib/libSystem.B.dylib
Sound appear and disapear!!
Hello I installed Pd, jackd and Alsa via apt-get i have debian 5.0(lenny)
Sometimes the sound works, when work it appear an error message:
audio I/O error history:
seconds ago error type
0.14 A/D/A sync
1.00 unknown
1.52 A/D/A sync
5.76 unknown
5.76 unknown
tried but couldn't sync A/D/A
audio I/O error history:
seconds ago error type
1.40 A/D/A sync
3.38 A/D/A sync
3.69 A/D/A sync
7.12 A/D/A sync
when don't works appear this:
couldn't open MIDI input device 0
couldn't open MIDI output device 0
opened 0 MIDI input device(s) and 0 MIDI output device(s).
audio I/O error history:
seconds ago error type
4.69 unknown
4.69 unknown
thnx
Guitar multi-effects rig
This is my live guitar effects right as of Feb 14, 2009. Please let me know if you find it useful or have any ideas for effects or other improvements. If you make some music with it, I'd love to hear it!
Once I have some more time to program it, my next effect will probably be a Vocoder.
Run effectsrig.pd to load it up. A midi expression pedal is recommended for the best experience - but it's not required.
It contains the following effects:
whammy~
Digitech whammy style pitch shifter. Allows for smooth changes to the pitch shift amount.
Based on the one posted by "kenn" on the puredata.info forums (which in turn is based on the pd example code).
shimmer~
A "shimmer" synth-like effect. This is done with a pitch shift in a feedback loop of a very short delay.
octfuzz~
Octave-up distortion like you can obtained with the classic transform and 2 diodde rectifier circuit. Basically it just full-wave rectifies the audio signal. This one really brings out the high frequencies (some times a little too much!).
leslie~
A stereo leslie (rotating speaker) simulator. This is one of my favorites. If modulation is turned all the way down it becomes tremolo. Take one of the outlets for mono use. Try it in stereo for super-swirley bliss! When using an expression pedal to control the rate, heel down will bypass the effect.
Expression pedal control is done by expression.pd. It simply reads in MIDI and scales it to a 0->1 range. You can change the midi channel used by editing this file.
The preset system is a little hack-ish, but it works for me. If anyone has any better ideas on how to do this, I'd love to hear them. When you load up the main effectsrig.pd file, you will see a bunch of message boxes. This are quick settings buttons - just click one to apply that effect. They are designed so you can click a couple in a row to quickly apply a few different settings. To start over, click the big "default" one on the left.
It can also load presets based on midi messages. I use this with my Eventide TimeFactor pedal. When I change presets on the TimeFactor, PD follows along. This is handled by the box in the top right. The symbol box is for song titles, and the number boxes show the current TimeFactor preset. Open this box to see how I've done a couple of example midi controlled presets. "pd your_love_never_fails" is a more complicated example that changes the expression pedal behavior slightly.
If you want to use a different midi channel for listening to program changes, just edit preset.pd and presetnum.pd. preset.pd outputs a bang when the preset number supplied as a parameter is chose. presetnum.pd just outputs the number of the selected preset.
Separate control of two midi devices
>>I had been hooking the sampler up to the midi out from the x-station<<
does the x-station have a midi 'thru' port too? or just in and out? because if you want to send midi to the sampler via another device, you'd probably have to have a midi thru port to do that (if i recall correctly)
if you don't have a midi through port, then i think it would be best to use the midi-usb device you have.
set the electribe to receive on midi channel 1 only. and then attach it to the the midi-usb device with a midi cable.
connect the x-station to the electribe's midi 'thru' outlet with a midi cable. set the x-station to recieve on midi channel 2 only.
then open pd and set midi output to the midi-usb device name, and then [noteout 1] should talk to the electribe only, and [noteout 2] should talk to the x-session
one more thing:
does the x-station have its own power source? if so, then disconnect the usb cable. you won't need it. but if the device needs usb for power, then maybe you can still leave it connected via usb as well, but don't select it as a device in pd, because it will be receiving midi messages via the electribe anyway.
one more thing again: really if the x-station has a midi through port, then just attach that to the electribe and all your worries should be gone.
Problem compiling external on Windows
Hey,
thanks to everyone who responded to my posts both here and in the mailing list. Since then, I've figured out how to compile externals written in C using Microsoft Visual C++ 2005. There's more to document, however, such as how to compile externals using some of the other Windows compilers (Borland, djgpp, etc.), and also how to compile externals written in C++ in Windows. But one thing at a time.
one little thing to note... steps 4 and 7 may seem a little roundabout, but they account for the fact that MSVC sometimes has trouble with spaces in directory names (eg. C://Program Files/). If anyone knows how to override this behavior, post a reply, and I'll try to simplify the steps accordingly.
Updated June 29, 2007:
use [b]C://Progra~1/[/b] instead of [b]C://Program Files/[/b],
use [b]C://Docume~1/[/b] instead of [b]C://Documents and Settings/[/b], etc.
So, without further ado...
How to compile a pd external written in C using Microsoft Visual C++ 2005:
Compared to Windows, linux offers a much more user-friendly environment for compiling pd externals. However, with a little patience, a usable environment can be set up in Windows, and the good news is that everything you need is available for free. There are several reputable Windows-compatible C/C++ compilers out there, but here I'll discuss compiling externals with Microsoft Visual C++ 2005 (MSVC for short).
1. Download and Install Microsoft Visual C++ 2005 Express Edition.
a. Click the link above, then click Go! in the Visual C++ box.
b. Run vcsetup.exe to install the program
(the setup wizard should guide you through the process).
2. Download [url=http://download.microsoft.com/download/7/7/3/7737290f-98e8-45bf-9075-85cc6ae34bf1/VS80sp1-KB9267
]Visual C++ 2005 Express Service Pack 1.
a. Click the link above to download the Service Pack.
b. Run VS80sp1-KB926748-X86-INTL.exe to install the program.
3. Create a new project:
a. Open Visual C++.
b. Open the New Project window (Ctrl+Shift+N).
c. In the Project Types pane, select Visual C++.
d. In the Templates pane, select emptyproj.
e. Enter object name (helloworld).
f. Leave Create directory for solution unchecked, and click OK.
4. Import the pd header file:
a. Get m_pd.h here, or, using pd-vanilla (not pd-extended):
1. Open Windows Explorer or My Computer.
2. Navigate to the pd/src/ directory on your system.
3. Open m_pd.h in a text editor (file type is: C/C++ header).
b. Select all (Ctrl+A).
c. Copy selection to the clipboard (Ctrl+C).
d. Back in Visual C++, open the New File window (Ctrl+N).
e. In the Categories pane, select General.
f. In the Templates pane, select Text File, and click Open.
g. Copy the contents of m_pd.h into the editor window (Ctrl+V).
h. Open the Save File As Window (Ctrl+S).
i. Save as m_pd.h.
j. From the File Menu, select Move m_pd.h into; select helloworld.
5. Write the source code for the external in C.
a. Open the New File window (Ctrl+N).
b. In the Categories pane, select General.
c. In the Templates pane, select Text File, and click Open.
d. Write your source code in the editor window.
The following example is taken from the tutorial by Johannes M. Zmoelnig.
#include "m_pd.h"
static t_class *helloworld_class;
typedef struct _helloworld {
t_object x_obj;
} t_helloworld;
void helloworld_bang(t_helloworld *x)
{
post("Hello world !!");
}
void *helloworld_new(void)
{
t_helloworld *x = (t_helloworld *)pd_new(helloworld_class);
return (void *)x;
}
void helloworld_setup(void) {
helloworld_class = class_new(gensym("helloworld"),
(t_newmethod)helloworld_new,
0, sizeof(t_helloworld),
CLASS_DEFAULT, 0);
class_addbang(helloworld_class, helloworld_bang);
}
6. Save and import the source code into the project:
a. Open the Save File As Window (Ctrl+S).
b. Save as helloworld.c.
c. From the File Menu, select Move helloworld.c into; select helloworld.
7. Access the pd library file:
a. Open Windows Explorer or My Computer.
b. Navigate to the pd/bin/ directory on your system.
c. Right-click on pd.lib (file type is: Object File Library) and select Copy.
d. Navigate to the C://TEMP/ directory on your system.
e. Paste the copy of pd.lib in the C://TEMP/ directory (right-click or Ctrl-V).
8. Set configuration properties:
a. Set configuration type to .dll:
1. Back in Visual C++, open the helloworld Property Pages window (Alt+F7).
2. In the left pane, select Configuration Properties >> General.
3. In the right pane, under Project Defaults, click on
Configuration Type, and select Dynamic Library (.dll)
(using the arrow on the right).
b. Add MSW to preprocessor definitions:
1. In the left pane, select
Configuration Properties >> C/C++ >> Preprocessor.
2. In the right pane, type MSW in the Preprocessor Definitions field.
c. Tell compiler which language to use:
1. In the left pane, select
Configuration Properties >> C/C++ >> Advanced.
2. In the right pane, select Compile As.
3. Select Compile as C Code (/TC) by clicking the arrow on the right.
d. Tell linker where to find pd.lib:
1. In the left pane, select Configuration Properties >> Linker >> Input.
2. In the right pane, select Additional Dependencies and enter
C://TEMP/pd.lib.
e. Tell linker to export the setup function:
1. In the left pane, select
Configuration Properties >> Linker >> Command Line.
2. In the right pane, type
/export:helloworld_setup in the Additional options field.
3. Click OK.
9. Compile and link:
a. Use the Build Solution command (F7).
10. Copy the new helloworld.dll file into pd.
a. Open Windows Explorer or My Computer.
b. Navigate to the
My Documents/Visual Studio 2005/Projects/helloworld/Debug/
directory on your system.
c. Right-click on helloworld.dll (file type is: Application Extension)
and select Copy.
d. Navigate to the pd/extra directory on your system.
e. Paste the copy of helloworld.dll in the pd/extra directory
(right-click or Ctrl-V).
11. Test the external in pd.
a. the external should now be a useable object in pd.
b. open a new pd patch and try to create a helloworld object.
c. add a bang to the left inlet and test it out.
d. if the main pd console window displays "Hello world !!",
the external has succeeded.
Hope this helps!
-- middlepedal
Cant get midi signals from Ground Control Pro to Puredata
Hello everyone,
I just purchased a Ground Control Pro, a midi foot pedal, from DMC. I was hoping to use it to switch between my patches in Puredata. However when I plug it in, using the factory settings=>to my Uno midi interface=>powerbook g4. I don't get any midi signals in the Test Patch in PD. I have selected the midi interface in the PD midi settings, I have also created a external in Audio|Midi OSX utility. If I switch out the GCP with my midi keyboard, PD gets the signals fine.
I am getting midi signals to the Audio/midi OSX utility because when I do a sound test in the utility i get sound response on the "\/" arrow of the midi interface(the one viewable in the patchable section of the utility)
If anyone has had any experience with the GCpro and setting it up with PD I would much apreciate some direction.
Just for you knowledge, I have tried this setup with the OSX midi utility open while PD was open(I heard that I should try that)....no luck.
Ben
Latency with midi
I'm looking for some help about a latency problem with midi processing using pd under Windows XP.
Here is the point : I'm using pd to process some midi data coming from electronic drums. These data are then sent to another software (e.g. Nuendo) thanks to virtual midi ports (MIDI Yoke). Assuming '<->' is a midi connection (virtual or physical), it looks like,
drums module <-> Sound Card (Midi Ports) <-> Pure Data <-> Midi Yoke <-> Nuendo
The problem is that pd introduces some latency... and pd is definitely responsible for that... because the following setup does not introduce latency :
drums module <-> Sound Card (Midi Ports) <-> Midi CC <-> Midi Yoke <-> Nuendo
(Midi CC allows to connect virtual ports between them)
The last point is that latency does not seem to be sensitive to the patch. I tried a simple midi thru patch and another patch with complex treatments and nothing changed...
Help
\[newbie question\] sine wave noise, A/D/A sync erro
Hi,
I'm just getting started with Pd on Fedora Core 3; installation was pretty painless thanks to the CCRMA repositories, but I've run into an issue when I first tried to make some sounds with Pd. I recreated Miller Puckette's example of a constant amplitude scaler. When I start the audio, the signal seems to take a few seconds to 'settle' into a constant frequency; I get a few seconds of static that eventually turns into the sine wave I was expecting. When I click the DIO errors button, I get a bunch of A/D/A sync errors, as follows:
audio I/O error history:
seconds ago error type
0.73 A/D/A sync
0.73 A/D/A sync
0.75 A/D/A sync
0.94 A/D/A sync
0.94 A/D/A sync
0.95 A/D/A sync
1.01 A/D/A sync
1.01 A/D/A sync
1.10 A/D/A sync
1.10 A/D/A sync
1.11 A/D/A sync
1.11 A/D/A sync
1.17 A/D/A sync
1.17 A/D/A sync
1.17 A/D/A sync
1.17 A/D/A sync
1.27 A/D/A sync
1.31 A/D/A sync
1.31 A/D/A sync
1.36 A/D/A sync
If I let the steady sine wave tone continue, eventually there's a bit of a 'hiccup' in the sound, and then I get the following errors:
audio I/O error history:
seconds ago error type
1.25 DAC blocked
1.25 data late
1.25 data late
1.25 data late
1.25 data late
1.25 data late
1.25 data late
1.25 data late
1.25 data late
1.25 data late
1.25 data late
1.25 data late
1.25 data late
1.25 data late
1.25 data late
1.25 data late
1.25 data late
1.25 data late
1.25 data late
1.25 data late
Can anyone help me out in diagnosing this problem and fixing it? Where should I start looking to fix this?
Thanks!