VAPORWAVE in VCV Rack (tutorial in english)

Поділитися
Вставка
  • Опубліковано 20 вер 2024

КОМЕНТАРІ • 11

  • @123456789tube100
    @123456789tube100 Рік тому

    You are actually making proper genre music on vcv rack

  • @GrvMUSIC4U
    @GrvMUSIC4U Рік тому +1

    Loved it awesome tutorial 🙌🙌

  • @123456789tube100
    @123456789tube100 Рік тому

    This is incredible

  • @rafaelposnik7244
    @rafaelposnik7244 Рік тому +1

    Wow, these are very good insights on building effects towards the aestetic! Congrats on this music and video!

    • @BlockOneProductions
      @BlockOneProductions  Рік тому

      Thanks! In my moogerfooger video I created another effect for vaporwave and I'm thinking about a part 2 for more generative Aesthetic what do you think?

  • @Giopiero98
    @Giopiero98 2 роки тому +1

    Keep up with the good work! I would love a video on the history of the genre 👌🏻

    • @BlockOneProductions
      @BlockOneProductions  2 роки тому +1

      Glad you liked it! Before deciding on tutorials for vcv rack, this channel *almost* was about music reviews (albums, artists and genres) it is a topic that fascinates me.

  • @daviHuggMonster
    @daviHuggMonster 2 роки тому +1

    these stutters actually had them too recently, (even with a very simple 2 sequencer patch -seq3) normally I did use the engine setting threads 6 (most modules) but that worked fine for a long time but not recently, I am testing the setting on 4 threads atm / I did try 1 and even 12 / 12 was actually worse. So maybe try that yourself, depends on your cpu

    • @BlockOneProductions
      @BlockOneProductions  2 роки тому +1

      Thanks for the suggestion! That's exactly what I did for the performance. I had to record it multiple times with different settings both on vcv rack and OBS. Sadly, I think I need a new computer, I use it mainly for music and Vjing so I can't have those stutters for live performances. The other thing I noticed was the performance meters (F3) and some modules use tons of resources! Anyways, thanks for the suggestion, I'll keep doing tests and hopefully I have them fixed for next week