How can i connect my DN2s to my Mac Sequoia ?
Midi Connection via:
I’ve tried renaming via Midi Center it does not work because after re-connect the assignment is random.
Audio Connetion via USB:
If the second Dn2 is connected the first connection breaks and audio stops.
Have the DNs no unique ID or is that a special issue with Mac Os?
Hi, how are you trying to use them within the Mac, through the standalone app or via a DAW? I thought I remember someone saying that if it’s ableton you need to create a second named device profile? I don’t know, that may be incorrect, I don’t use ableton for recording.
Also, Ableton (from what I understand) has a 16 track limit so if you have all 16 tracks piped in from 1 device, then I would think it makes sense that the connection is broken as you’re essentially selecting to move all available resources to the second device. I read that this is an Ableton limitation, but since I don’t know what you’re using I can’t be much more specific.
If you add some more details about what you’re doing after you plug the DN2 pair into your Mac maybe someone will have better advice.
I’d probably just file a ticket with Elektron in your elektron.se account and ask them, might be faster.
Connected to the System via USB. Its not working so currently no need to connect it to a DAW or something. i can use the Transfer App with one unit connected. Maybe overbridge could help in the future. I made a support request.
I see. And you already did something like this to create an aggregate device for your mac audio?
I don’t know how it works because I don’t use mac, but I do read a lot of posts here and this seems to be something that people talk about. I’m assuming you’ve already done it, but only mentioning because you don’t explicitly state that you’ve made one.
If you run lsusb, do they share the exact id?
Bus 036 Device 003: ID 04e8:6860 Samsung Electronics Co., Ltd. SAMSUNG_Android Serial: 323062d3f6738057
Bus 036 Device 002: ID 05ac:8507 Apple Inc. Built-in iSight Serial: 8J97P2KF16V13A00
Bus 038 Device 003: ID 1a40:0101 TERMINUS TECHNOLOGY INC. USB 2.0 Hub [MTT]
Bus 038 Device 004: ID 0403:6001 Future Technology Devices International Limited FT232R USB UART Serial: A601EFG9
Bus 038 Device 005: ID 12d1:1038 Huawei Technologies Co., Ltd. Android Adapter Serial: 509F2735096D
Bus 038 Device 002: ID 05ac:8403 Apple Inc. Internal Memory Card Reader Serial: 000000009833
Bus 004 Device 003: ID 05ac:8242 Apple Inc. IR Receiver
Bus 004 Device 002: ID 05ac:0236 Apple Inc. Apple Internal Keyboard / Trackpad
Bus 006 Device 002: ID 0a5c:4500 Broadcom Corp. BRCM2046 Hub
Bus 006 Device 003: ID 05ac:8213 Apple Inc. Bluetooth USB Host Controller Serial: 002608CCAC6F
Bus 036 Device 001: ID 05ac:8006 Apple Inc. EHCI Root Hub Simulation
Bus 038 Device 001: ID 05ac:8006 Apple Inc. EHCI Root Hub Simulation
Bus 004 Device 001: ID 05ac:8005 Apple Inc. OHCI Root Hub Simulation
Bus 006 Device 001: ID 05ac:8005 Apple Inc. OHCI Root Hub Simulation
Yes, that was my first move to separate them. Doesn’t help.
Looks like the same id. And now sending back for repair?
Bus 002 Device 008: ID 1935:1034 1935 Elektron Digitone II Serial: 000000000001
…
Bus 001 Device 006: ID 1935:1034 1935 Elektron Digitone II Serial: 000000000001
Same vendor ID and product ID is expected. What’s weird is that they have the same serial. Mine does as well. I can only hope that now with all the overbridge testing this has been caught and fixed?
Thanks for help,! It’s so bad, my old FM Love (I have 2 of them) is addressable via an ID on the same midi channel and port, and my new FM Love 40 Year later can’t do that. Hmm
No I D no cry, Nooo I D no cray… Ahhhhhhhhhhhhh
That’s really weird. As an embedded developer who loves to write code but hate to test it myself, I would at the very least check that the serial was unique per device.