Пікірлер

• 
  @BB-mt5sbКүн бұрын

  very cool

• 
  @SwahaChris3 күн бұрын

  Very nice setting... and such a soothing sound. I love hang drum.

• 
  @Mandakinimusic6 күн бұрын

  Listening.... 😉 🛸🎶✨

• 
  @sternenherz6 күн бұрын

  🌞♥

• 
  @StarvedForTime7 күн бұрын

  I've been using bitwig since V1, and I can't disagree with any of this.

• 
  @juanharmon1387 күн бұрын

  Inspiring--great work

• 
  @memecoinmafia27329 күн бұрын

  nice 👍

• 
  @INKIE_MUSIC9 күн бұрын

  Looks impressive!

• 
  @Mooglala9 күн бұрын

  Mega Geil

• 
  @alexdiakov_ambient11 күн бұрын

  Wow!

• 
  @djasynchronous777717 күн бұрын

  🔥🔥🔥🔥🔥

• 
  @Maximussilentium01-mh3vd23 күн бұрын

  version 5.1.8 is out and FINALY theve done something about the horrendous stubby little vol mixer. its now resizeable in both hight and width. i love it a lot taller and slimmer

• 
  @sternenherz23 күн бұрын

  Yea, true, i loved that mixer update, too :) There are still some downsides and a lot of work to do, but it's a good development.

• 
  @BassFunMusic27 күн бұрын

  Great ☺♥♪

• 
  @stuwyattАй бұрын

  Beautiful stuff :)

• 
  @va941Ай бұрын

  Audio Damage ENSO.

• 
  @sternenherzАй бұрын

  If it has to be a VST right now i would choose Melda Productions MSuperlooper any day over ENSO. ENSO was never built with a proper looperstation in mind, but rather is based on a "frippertronics" delay pedal (paraphrasing its dev here). It doesnt even have an Undo function and doesnt offer quick and easy access to several loopers in one interface. In the future, someday, Loopy Pro will be available as VST (according to its dev). Loopy pro VST will obviously be the king to rule for many years to come. But MAC vst development took such a long time already, and windows vst development might take even longer, who knows.

• 
  @va941Ай бұрын

  @@sternenherz yeah, youre not wrong, but still, Enso looks the best out of them all, and i just have to go based on that alone. 😂

• 
  @sludgebucket3042Ай бұрын

  I love Bitwig but when I want to do heavy looping style workflow I tend to just use Ableton and import the ALS file into Bitwig for futher production. You kind of get the best of both worlds that way. Any reason you didn't consider doing it that way?

• 
  @sternenherzАй бұрын

  1. Instability of Ableton and m4l plugins 2. Worse loading time 3. Worse workflow overall 4. Worse LOOPER workflow now that i ve built my own!!! (Main point now) 5. Worse OSC implementation (i love remote control via OSC, Touch Osc) 6. I absolutely hate having to switch DAWs "for further production". I love focussing on one system without having to fiddle around with import/export and having to deal with different workflows constantly.

• 
  @DaKingofАй бұрын

  The radial menu on the touch is really bad. Amazing that it opens UNDER your finger. How are we supposed to use the menu we can't see? The menu should expand to the sides of the finger and above the finger, leaving underneath clear.

• 
  @sternenherzАй бұрын

  There's so much which could be improved about it, that i tend to just ask Bitwig to please let us deactivate it completely. How much of developers time could it take to just implement an on/off shortcut for touch UI/radial menu? I can’t imagine that could take long, especially compared to a complete overhaul of the touch UI... Still hoping for that simple on/off shortcut to happen:):) If it's a pinnable shortcut, one could use the normal mouse emulation via touch, AND if needed the radial menu, without having to dive into Bitwigs settings. One funny positive side effect i noticed about touch control recently: you can move clips without ever accidentally changing clipGain. I hate that so much with mouse control, haha! I personally never want to adjust the gain of a clip in the arranger directly, and every missclick is deeply annoying.

• 
  @BrunodeSouzaLinoАй бұрын

  As per lore, Ableton implements one user suggested feature every 10 years.

• 
  @sternenherzАй бұрын

  Hahaha yep. I hope Bitwig will always have a better rate than that!

• 
  @GeorgeLockeАй бұрын

  I love the outtro track.

• 
  @MegaPixel404Ай бұрын

  Agreed, they do need to stop focusing on new features and spend a year or 3 working on the core. I would love to get rid of that double select range thing and have all that functionality wrapped up into 1 area selection with edge grab, the white and black selection areas, the white for me stops me dead in my tracks so many times because it's not what I wanted or just need to get it out of the way. Grid line colour changes would be great to make them more defined, piano roll needs a huge amount of work, 1 that annoys the hell out of me is that the auto zoom when you click on a midi clip often has all the notes off the screen then, you double click the clip again and it may or may not bring them into view. I also hate having note selection play a preview so I always have that turned off, but when I click on the piano keys to the left they are turned off also... Come on... lol. The little things matter, they matter a lot. I do love the MSEG stuff though, when I made a feature request to them I designed UI/UX interfaces in bitwig for using them, what they did took it a step further and I do love them.

• 
  @alekjwrgnwekfgn2 ай бұрын

  Bitwig need to pay you bro- for the wizard hat.

• 
  @alekjwrgnwekfgn2 ай бұрын

  Btw do you have a link to that steel drum-thing. I saw a Czech girl busking with one (one KZread). She impressed me, but not so much for the drum.

• 
  @LabofmusicRecords2 ай бұрын

  Bitwig user since v1 here and also Cubase user since 1995... Bitwig for Ideas and fun, Cubase for serious productions... With all your Ideas, maybe switching 100% to Bitwig. Awesome Video and nice track at the end.

• 
  @ekids.bassment2 ай бұрын

  Cool, maybe you can make it work with Open Stage Control as well

• 
  @stephanearlmusic2 ай бұрын

  Does anyone know what 4-oscillator Synth VST is shown in this video at 10:42?

• 
  @sternenherz2 ай бұрын

  Reveal Sound Spire with a dark skin :)

• 
  @stephanearlmusic2 ай бұрын

  @@sternenherz That's awesome! Thanks for the response. Loved your video and the work you put into this looper. Cheers!

• 
  @TwstedTV2 ай бұрын

  I just purchased BitWig on their 10th birthday celebration sale. And when I was looking around and trying out a few things out. I started creating a few melodies and working with the midi notes. And for almost 2 hours I was searching for gridlines, only to find out 2 days later that it doesn't exist. I wanted to change from 32 to 16 and could not find it. I got frustrated and closed the DAW.

• 
  @sternenherz2 ай бұрын

  Do you mean gridlines in general or gridlines which are visible through Clips? Gridlines in general exist, and there is a slider to determine their strength in Bitwigs Interface Settings. But Gridlines cannot be seen through Clips, that's true, and it sucks :D

• 
  @AnomieDomine2 ай бұрын

  Are you developing for Android tablets? I bet a Linux/Steam deck version could be really nice

• 
  @sternenherz2 ай бұрын

  Hello, Touch OSC is running on any platform, including Linux. But i dont think the steam deck makes as much sense as bigger hardware with bigger touchscreens! The bigger the touch screen, the better the experience of control. The steamdeck has a really small screen.. So if it has to be linux, i would choose any 2-in-1 windows Laptop which can be used as Tablet Format, or just a windows based tablet, and install Linux and Touch OSC on it.

• 
  @AnomieDomine2 ай бұрын

  @@sternenherz You're not wrong, but a Steam Deck in hand is better than one in the bush...Also - it has two touch pads, two sticks, analog triggers, and buttons too.

• 
  @Joachim.Jacobs2 ай бұрын

  I hope that you posted this video in the bitwig forum or the bitwish site!

• 
  @BruceLeaak2 ай бұрын

  why u making clip.loops ? u can easy loop every track in the timeline itself with ctr +d ... and make your own horizontal timeline ' i've never used in my life this sh17 in verticals i would never make any track so : ) it's against my brain lol

• 
  @zorkertorker70202 ай бұрын

  You are the legend!!! Everything you said is absolutely needed! I have some more things you have not mentioned, but I believe they’re REALLY important for composers like me who do film scoring. 1. Ability to resize tracks like in Logic, Cubase or Studio One. When I’m working on large electro- orchestral production I need to have an ability to resize tracks just by using mouse wheel like in many other DAWs. Bitwig has a button which makes tracks tiny but this is not a solution at all. We, film composers, need to freely resize tracks in large projects with 100+ track string templates. 2. When I want to record a midi note in the current region, Bitwig just splits the region. That behaviour looks like a bug and make Bitwig totally unusable when I want to just add a midi note by playing it on my keyboard. Every time I want to edit midi I need to hit cmd +j to join midi region which is absolutely crazy to me. I wondering why nobody talks about it, but it’s absolutely true. 3. Unable to “play from playhead” in the piano roll like in Studio One. It’s really inconvenient to hit this upper panel on the piano roll to move playhead starting position. I want to just hit anywhere and then hit spacebar for playback( like in Studio One) 4. Unable to organise deactivated tracks. If there are many tracks being deactivated there are no way to organise it. You need to create a folder with audio bounce and deactivated tracks which is absolute workflow killer for all of us. 5. Unable to draw smooth automation in track view by mouse. I can do it in clip view but it getting buggy as I adding many points. 6. Video support is absolutely needed. All these things are not just small inconvenience. It’s absolute dealbreaker for me, unfortunately. I love Bitwig soo much and I hope developers will see this video and WILL FOCUS ON BASIC STUFF IN THE FUTURE DEVELOPMENT. Bitwig is already innovative product. Just give people DAW functions, please, guys! In general, if Studio One and Bitwig could be one program it seems like it would be ideal daw for 95 % on this planet So much respect to @Sternenhertz for this video!

• 
  @jbflinnla2 ай бұрын

  You are a genius! People like you remind me how happy I am to be alive. Thank you!!

• 
  @pantoniotti2 ай бұрын

  Grid lines and piano roll improvement for sure, but for me the #1 reason not to switch is : VERTICAL ZOOM ...Click and drag up/down in the tracks section is painfull and slow, and even worse if you're on a laptop with trackpad only ... the one in Ableton is good, but the one in Logic is perfect : Zoom in all direction with 2 fingers by just pressing Alt ... so fast !!!

• 
  @0lgarythm2 ай бұрын

  This is fire !!! Thank you

• 
  @delta-99693 ай бұрын

  the simple ability to use a daw as a looper and hang onto all the layers as audio tracks would be an instant buy for me.

• 
  @sternenherz3 ай бұрын

  Yea, but that’s why i built a Looper for Bitwig on my own :) (it's one of my newer videos)

• 
  @bigal246983 ай бұрын

  Really excellent but of the first 4 you propose I would say the touch controls are the least important. There is a reason Apple made a separate OS just for touch. As always Microsoft hacked it into Windows and made a mess of it. Even on a Surface Pro tablet it’s not useable which is a big hurdle for a software application to overcome. I understand why they did it but I think after all the hype dissipating they probably regret having to use resources maintaining such an ambitious feature.

• 
  @sternenherz3 ай бұрын

  Thanks :) Hmm, i have a different opinion, obviously, since touch control is really Important to me. Since i m using Touch OSC on windows everyday, i know from experience how awesome and smooth touch control on windows can work :) There is no Windows hurdle to overcome in this case :) just a few fixes necessary which are design flaws since v.1.3s release of the Bitwig touch Ui. Yes, Microsoft does a horrible job with their own OS touch control- but that has zero impact on how Bitwig handles touch control, as that's decided by Bitwigs own philosophy.

• 
  @bigal246983 ай бұрын

  @@sternenherz I agree they could sort it out 👍 thanks for getting the message out so clearly

• 
  @user-hp8it3mm6p3 ай бұрын

  MORE!!

• 
  @user-hp8it3mm6p3 ай бұрын

  Hey Brother. Have you ever been to a Gathering of the Tribes such as for example: - OZORA Festival (Hungary, happens every year) - Boom Festival (Portugal, happens once every two years) Make a note of these - they are the experience of a lifetime. Watch the official videos.

• 
  @user-hp8it3mm6p3 ай бұрын

  I love your style.

• 
  @astro_poly3 ай бұрын

  I can't find your paypal on your twitch about? Really would like to buy that looper. Looks amazing.

• 
  @sternenherz3 ай бұрын

  Heya, best thing is to hit me up on discord , link is in the description ( if you have discord) because when you dont use patreon, i gotta have to send you all the infos manually (the infos, which are part of the patreon posts for the looper). Or you just make a patreon 1 month, with immediate cancelation after ward :D

• 
  @sternenherz3 ай бұрын

  I just looked at my own twitch again: The paypal link is the huge "SPENDEN" Button ;D

• 
  @astro_poly3 ай бұрын

  @@sternenherz ah okay supeerrrb, going to make a transaction with paypal then! It works with apple too right?

• 
  @vroteg3 ай бұрын

  9 month later and they still did not address anything. Released couple of crappy devices…. What a joke. Bitwig is a shame at the moment…

• 
  @sternenherz3 ай бұрын

  I was quite happy with 5.1. They adressed the pudding-like-feeling of automation! That was a huge one for me :D Considering that this nasty automation-point-movement feeling has been with Bitwig for ages, it was a huge thing for me, that it got adressed and fixed with 5.1. Also, they've added audio-quantization, normalization, and a slider to increase/decrease gridline strength, and finally added a multi-routing-change-ability for the mixer and better mixer-track-scaling. All really helpful "basic" DAW improvements. So, i cheer them on to make the next releases all about similar stuff ;) Yes, they're still building their updates mainly around "5 new toys for this and that" , but as long as they also give basic DAW improvements, i can deal with that.

• 
  @catvision7774 ай бұрын

  und wieso gibt es keinen einfachen Mono/Side-Control button wie in FL Studio im Mixer und keine super praktische Currentspur? Für 400 Euro schwach, ich dachte, das wären absolute DAW Basics. Und die PianoRoll ist wie im Beta Modus. Hast du je eine Reaktion von Bitwig bekommen?

• 
  @modartmusic4 ай бұрын

  XDDDDDDDDDDDDDDDDDDDDDDDDDDDDDD

• 
  @JamInPeace4 ай бұрын

  :-)

• 
  @RockManDelta4 ай бұрын

  If they do a function where i could render as loop like in Live and FL Studio, i would not think two times before buying a license.

• 
  @ennes_ns4 ай бұрын

  I get the gridlines problem in arranger view but its not as big of a problem people think. In the detail editor BOOM transparent lines over the waveform. Keep the arranger for arranging sections of your song instead of waveform chopping ;^)

• 
  @sternenherz4 ай бұрын

  To each his own. I used the Cubase arranger like a semi-detail view since 2009, and i love it, and this workflow is fucking awesome, and i will ask for it till Bitwig implements it ;)

• 
  @sweeterthananything4 ай бұрын

  I was considering trying Bitwig after 15 years with Ableton (+occasionally Reaper) but this video was exactly what I needed to understand that basically all the things Ableton version 8/9+''s updates have left me disappointed with... are nearly all the same degree of neglected or even *worse* in Bitwig. I appreciate some generative music toys but deeply do not care about them if i don't have good tools for writing music WITH INTENTION first. it's making me wish these DAWs were more modular in design so I could just have FL Studio's piano roll without committing to how to handles channels/groups/etc. as it is, with all DAWs trying to both do "EVERYTHING" (in theory) AND be distinctive, it seems like *every* developer will get at least one aspect dead-wrong, and our choice of DAW comes down to deciding which thing we can accept being dead-wrong. Yeah, sodium has accumulated.

• 
  @chasewatkins30964 ай бұрын

  This was the only thing stopping me from seriously considering switching to Bitwig.

• 
  @hazmatproduction45625 ай бұрын

  After coming from cubase, Bitwig feels light years ahead for anything involving synthesis, sound design, modulation, non linear sequencing, and freedom and ease of routing. Really the only things I miss from cubase pro are ARA2, a browser like mediabay that allows editing sample metadata, and the chord track / scale assistant in the piano roll. Cubase also has much better and more accurate transient detection in beat slicing, and the ability to quantize to custom grooves created in the slicing process. Cubase is a very feature rich and long established DAW. But the caveat of this is that it suffers with a lot of bloat of legacy features from decades ago that they can’t overhaul or remove without breaking people’s old projects. Navigation is tedious and it’s still built on foundations based on audio industry standards from the 1990s. Beautiful mixing environment, and nice for working with audio, but its modulation features are so dated that I could never recommend it over Bitwig or Ableton as a sound designer’s DAW of choice. It has no capacity for any kind of FM routing at all, and doesn’t even have a native FM synth. Most of the native FX are ancient. New UIs given to the same old plugins from 20 years ago. I just kept waiting and waiting for steinberg to update modulation workflow and they never did. I can live without the thing I miss from cubase but could never choose it over Bitwig again for anything involving a lot of modulation. The FX nesting, routing options, and amazingly intuitive mod system, multiband FX racks etc. I just couldn’t go back to not having that again lol

• 
  @hahaxolotl5 ай бұрын

  i want bitwigs devices, abletons automation and browser. If they could just fuse both of them itd would be my favorite daw

• 
  @zorkertorker70205 ай бұрын

  Still can't figure out how do you automate "post record delay" with the moss script