The weakness on understanding leads to a difficulty in memorization AFAICTĪll this stuff gets ironed out in piano lessons I'm sure but it seems to happen at a pretty late stage that isn't great for an adult beginner. Weakness on learning to play with others Weakness on developing a sense of rhythm and playing by ear Huge emphasis on reading music and playing it back even if you're not understanding it Piano is super super super biased towards classical music Nothing beats a teacher but there are some problematic things with piano teachers IME. I do think you need the music theory though, such as awareness of chords and functional harmony.Ĭonsider learning some of the classic synth basslines - they tend to have tutorials on youtube - like Material Girl or Tarzan Boy. (Of course the DX7 was played very much as a piano at times) I mean, to play the melancholy chords of "Drive" by the Cars, you need some of the skills of a pianist, but not rhythmic ones. When polysynths got common in the mid 80s, pianistic fingering of chords (but not necessarily rhythms) was used. So pianistic skills would be wasted in this context. A lot of piano technique is getting both hands working together to play rhythm and melody - but generally synths are doing one thing at a time, and cooperating with other instruments.Ī lot of classic synth lines are monophonic, aka "one-finger" lines, although to play them fluidly with one finger would be pretty hard. Definitely learn the rudiments of piano playing, up to playing block chords (triads) with either hand.īeyond that, I think they diverge too much. And on that basis, I’m sure that artists will over time become experienced as to what provides the best performance both in terms of thread allocation (be that at a Bios level or within VCV) and module choices within patches.Good question.
I’m optimistic to see multithreading implemented in VCV, but in an open source system with many third party modules there are more place for the system to encounter log-jams. It’s common sense really but it does help if you understand the under-the-hood engineering on at least a surface level as it helps you realise that multithreading isn’t a magic pill. Whilst Racks in Live are a hugely powerful multi-timbral sound design tool, it’s more efficient to work with individual instrument/effect chains placed on individual tracks/channels and common effects like saturation should be used in a limited manner on sub-group tracks rather than on each individual track. I’ve mentioned elsewhere that U-He synths such as Diva and Repro-5 are multithreaded when used polyphonically but in certain DAW’s, enabling multicore in the U-He synth will fight with the multicore capabilities of the DAW resulting in a drop in performance.Ībleton Live since Live 9 is automatically multithreaded but even here you need to build your set’s in a manner that best takes advantage of those capabilities.
But even where tasks are hyperthread friendly without loss of performance there are always trade-offs.
Over time certain tasks and setups turned out to be highly performant under hyperthreading and others less so.
SYNTORIAL FULL SCREEN CODE
Around 12 years ago when the digital content industry starting looking into parallel process enhancements to their archaic code bases (the likes of Houdini, Maya, 3ds Max etc are built on code that goes back many decades) it became a best practice to set your workstation to only use the available real cores in Bios (disabling hyperthreading). With regards to multicore vs multi-thread, things are very definitely coloured by use-case. Apologies if this seems tangential but I believe it to be relevant to the conversation.
0 kommentar(er)
