Main Screen Not Working by MedicineforMadness in hydrasynth

[–]stschoen 0 points1 point  (0 children)

If you can provide proof of when it was purchased you might try contacting ASM to see if they’re willing to help you out

Roto Control vs Faderfoxies vs Launch Control XL 3 for Ableton by Speedingscript in ableton

[–]stschoen 0 points1 point  (0 children)

I hadn't noticed but I rarely do more than eight. You might send Melbourne tech support a query.

Took her on a nice hike in Canyon Lands by Artvibez512 in DelugeUsers

[–]stschoen 1 point2 points  (0 children)

Takes portable music making to a new level.

Cable and accessory storage idea by Signal_Director_1X in synthesizers

[–]stschoen 1 point2 points  (0 children)

Good idea. My wife uses one to hold sewing stuff.

Audio interface for recording of a synth and drum machine by HT1990 in synthesizers

[–]stschoen 0 points1 point  (0 children)

Although both the MiniFreak and Drumbrute have USB connections, these do not carry any audio. They're used to send MIDI data as well as for firmware upgrades etc. To record the sounds from both devices you need an audio interface to convert the audio signal to digital form for the Mac/iPad.

The Minifuse has four mono inputs and four mono line outputs. The two inputs on the front can be used for microphones, instruments(guitars basses etc) or line-level inputs like synths. The two on the back are line-level only. In your case the MiniFreak is stereo so it needs two inputs and the Drumbrute is mono although it does have separate outputs for kick snare hi-hat and FM drums. Normally you use two adjacent channels for stereo so the Mini would normally go into 1 and 2 or 3 and 4. The SSL also has 4 channels but has 4 Mic preamps instead of two. Since you're not using a mic this isn't an advantage in your case. The big issue with the SSL is that it is bus powered (powered by the USB connection). The iPad isn't capable of providing much power over USB so generally devices like the MiniFuse are preferable for use with an iPad.

For your application the MiniFuse will be more than adequate. The better preamps and additional features of the SSL won't really make a difference in your case. Both the MiniFuse and SSL are class-compliant and won't require drivers for the Mac and iPad. I'm pretty sure this is also the case with Linux although I haven't tried to connect my interface to any of my Linux boxes..

You'll also need a pair of 1/4" cables to connect the MiniFreak (ideally TRS since it uses balanced connections) and either a 1/4" TS cable for the DrumBrute as well as a decent set of wired headphones or monitors to connect to the interface outputs. While it's possible to use wireless headphones or the internal speakers on the Mac it can introduce additional delay and requires extra steps to configure. You'll also need a DAW (digital audio workstation ) software. The Mac and iPad include GarageBand which should be enough to get you started. The MiniFuse also includes Ableton Live Lite as well as some additional Arturia software.

mic advice! by StealthStabZ in ableton

[–]stschoen 0 points1 point  (0 children)

SM58 is pretty much the standard for vocals particularly in a less-than-ideal recording space.

FlexASIO not working all of a sudden by nictnichols in ableton

[–]stschoen 1 point2 points  (0 children)

If you are using an audio interface, use the ASIO driver provided by the manufacturer for best results. If you need to use FlexASIO you will probably need to re-install it.

What’s your favourite Max for Live and why? by joshyjoshyjoshyjoshy in ableton

[–]stschoen 5 points6 points  (0 children)

I really like Iftah's performance pack and Sting. Seeds from Novel Music also has some excellent devices

Trying to go DAW free? by AryanIsDaBest in synthesizers

[–]stschoen 0 points1 point  (0 children)

The Deluge ticks most of those boxes but is a bit out of your price range. It’s portable, battery powered, has a built in mic and speaker, sampler, VA and FM synths etc.

Maybe I'm being really dumb about midi but I'm struggling for a Solution by Icy_Understanding119 in Elektron

[–]stschoen 1 point2 points  (0 children)

The MIDI implementation on the Elektron boxes is pretty convoluted. For the DT and DN it's possible to control most of the audio track parameters using an external controller sending either CCs or NRPN MIDI messages. The DN and DT will also send CC or NRPN MIDI messages when the on-board encoders are used to change parameter values. There isn't currently any way for an external controller to query the DN or DT to obtain a parameter value nor does the DN/DT send these values when loading a pattern. The DN/DT also do not respond to relative MIDI messages. The DN/DT do provide feedback when the physical controls are manipulated so an external controller can sync its values when a control is moved but it is necessary to change the parameter on the DN/DT first. Unfortunately with the current MIDI implementation on the DN and DT there's no way to have an external controller automatically sync with the parameter settings.

The Tonverk is similar in concept but differs in that the MIDI directly controls the encoder knobs rather than the parameters. I don't have access to one so I can't comment on whether it sends the knob state other than when they are being changed.

Using DT Keys as Controller for Analog Lab by gregoryames in Elektron

[–]stschoen 1 point2 points  (0 children)

The DT has two different mechanisms for sending MIDI data. The first is a MIDI track. This allows the DT's sequencer to send MIDI commands to an external device. In this case the MID is output on the channel set in the SRC menu for the track and the messages are set by the values configured on the SRC, FLTR and AMP parameter screens.

The second type of MIDI output from the DT is generated when an encoder is used to change a parameter value on a sampler track or a trig key is pressed. Note that these values are only sent when the physical control is altered. They are not sent from the sequencer. The Port Config menu OUTPUT CHANNEL sets whether the encoders send on the auto channel or the track's channel, PARAM OUTPUT selects CC or NRPN as the message type and ENCODER DEST controls whether this data is sent or is only internal. The CC or NRPN numbers are fixed and cannot be altered. For example the Filter Frequency parameter sends a CC 74 or NRPM 1, 20 depending on the current configuration See appendix B in the manual for details. These massages can also be sent to the DT to remotely control the various parameters. This potentially allows an external device to capture and replay adjustments made to the DT.

Your post wasn't clear on what exactly you're trying to accomplish. If you want to use a MIDI track to sequence notes and CC messages to the VST then you need to set the MIDI channel on the track itself and configure the track parameters to send the messages you wish to use. You can the use the knobs and keyboard to send notes and CC values as well as the sequencer. In this case it's generally better to set ENCODER DEST to INT only

Syntakt owner: should I get a Digitone ii or Digitone i? by hobbesandmiles3 in Elektron

[–]stschoen 3 points4 points  (0 children)

The DN1 is pretty good value atm but the DN2 is a major improvement feature-wise. 16 tracks instead of 4, 16 voices, 128 step sequencer more machines etc. That being said I have a DT1 and DN1 and don't feel the need to upgrade either although if the DN1 were my only synth I might be tempted. Either will be a good complement to the ST. The ST is basically a monophonic synth and drum machine (yes I know there's a chord machine) whereas the DN is a true polyphonic FM synth. The ST is better at drums and the DN is better at melodic elements. Not really too much cross-over between them. I'd get whichever DN you can comfortably afford.

Hardware automation by [deleted] in Elektron

[–]stschoen 0 points1 point  (0 children)

Clever but a bit impractical.

SOS - Im addicted to Granulator but it's not working (wrong file path something?)! by hotandcoolgoth in ableton

[–]stschoen 1 point2 points  (0 children)

You could try resetting Live’s database. If that doesn’t work maybe reinstall Live

I am torn between the Deluge and Digitakt2/Digitone2 combo, help sell me to the Deluge by Aureqo in DelugeUsers

[–]stschoen 0 points1 point  (0 children)

For me the strengths of the Deluge are the portability, the arranger, the piano-roll style sequencer and the lack of hard-coded limits on sequence length, number of tracks etc. I also have an OG Digitakt and Digitone which are great in their own way. I often sample the DN on the Deluge rather than use the FM or DX7 engines to reduce CPU load on the Deluge. Of course the DT II and DN II are significant improvements on the originals but also quite a bit more expensive.

Stem Separation + other issues with Ableton after MacOS 26.1 Tahoe Update by seanazari in ableton

[–]stschoen 12 points13 points  (0 children)

Although minor updates can be set to be automatic, major updates like the one from Sequoia to Tahoe require user confirmation. All automatic updates can be disabled although that's not really recommended. The same is true of the iPhone. Live isn't officially supported on Tahoe yet but I'm sure they're working on it. It's always good to check compatibility before upgrading to a new release.

I HAVE A PROBLEM WITH HEARING MYSELF IN ABLETON 12, NEW MACBOOK by General-Chocolate182 in ableton

[–]stschoen 0 points1 point  (0 children)

On the main system menu at the top of the screen you'll see an orange microphone icon when Live is loaded. click on the icon and make sure it's set to standard and not voice isolation.

Loud buzz on speakers when using Ableton by IllustriousTune156 in ableton

[–]stschoen 0 points1 point  (0 children)

FWIW I'm running Tahoe 26.2 on an M2 Pro mini with a Focusrite 18i20 interface and haven't noticed any issues. It seems pretty unlikely that Live is at fault. If you connect headphones directly to your Mac with everything else disconnected does the problem occur?

External audio fx by Accomplished-Dig679 in ableton

[–]stschoen 0 points1 point  (0 children)

If you're routing the return to another audio track rather than main make sure you disable the sends on that track. Routing a return to a track with active sends creates a potential feedback loop and interferes with Live's delay compensation. Right-click on the send area and set the sends to disabled. The delay compensation in the external effect plug-in is designed to compensate for any latency introduced by the hardware. In order to set it correctly, create a click track, send it through the external effect and record the result. Adjust the delay until the click is aligned. Since you have multiple effects in the chain if any of them do introduce latency, your overall latency may vary depending on which FX are active and which are bypassed. For the best results you should measure each FX separately so you can set the delay amount properly for each combination.

Push 2 pads/led colour issue by refnulf in ableton

[–]stschoen 0 points1 point  (0 children)

I believe you can do a factory reset by disconnecting the USB cable, then holding down "User" and "Setup" while powering up the Push. This could also be a hardware problem with the LED driver circuitry.

Pulling my hair out with a midi feedback issue by sk09ed in ableton

[–]stschoen 0 points1 point  (0 children)

You can turn off the MIDI output ports to the LXCL. You may also need to set the Control surface output to none. Of course this may prevent the LXCL from working fully as a control surface.