- Pianoteq 6 activates as plugin but not as standalone how to#
- Pianoteq 6 activates as plugin but not as standalone install#
- Pianoteq 6 activates as plugin but not as standalone software#
- Pianoteq 6 activates as plugin but not as standalone Pc#
I really have no judgement here – just use what you like.īefore the comments section gets filled up people who use Arch btw, I’ll add that the AUR has a great selection of audio software too. This way you get the low latency kernel and other audio tweaks set up by default. XFCE and MATE are two other lightweight desktop environments that you could try.Īnother option is to use a distro that is designed for audio and multimedia work, such as Ubuntu Studio. Of course it makes sense to run a lightweight desktop environment so you have more resources available for your audio software. I’m into KDE because I find it to be lightweight, fast, stable and customisable to my liking. The distro I’m using is KDE Neon which is based on Ubuntu LTS. The screenshot below is from my own machine. If you want to replicate my setup it would be easier to go with a Debian-based distro so you can use the KXStudio repository (more about KXStudio down below).
The Linux distribution you choose comes down to personal preference. I have a Zoom H4N that I sometimes use to record audio to SD card.
I skipped that part as I mostly just produce with softsynths and samples. If you want to record live audio using microphones then you’ll also want to get an audio interface. My current headphones are Audio-Technica ATH-M50x. It’s not really recommended, but you can still get a good enough sound on headphones if you use references. I actually used headphones to produce and master my last 3 albums. The acoustics in my office space are awful so I have my near-field monitors kept in storage until I eventually get a new space for music production. It’s my preferred MIDI controller I even prefer it over the axis! There’s something about the traditional 1-D style keyboard that feels natural to play. I bought a second hand M-Audio Keystation 88es from Gumtree for 50 quid. It just plugs in via USB and my system recognises it instantly as a MIDI input device. The keys are all nerdy lil hexagons, it’s cute. Isomorphic keyboards such as my C-Thru AXiS-49 work well for microtonal music because scale and chord fingerings remain the same in each key, whereas a standard MIDI keyboard requires you to learn a different fingering for each key.
Pianoteq 6 activates as plugin but not as standalone Pc#
My PC is an Entroware Ares with an Intel Core i7 processor, 16GB DDR4 RAM, one SSD and one spinning rust. You could probably get away with using a 5 year old laptop for sure. Oh and if you want to know my old workflow for making microtonal music with Ableton Live on Windows then the old article is still available. This article also discusses alternative software choices just in case your preferences differ to mine. My current setup is based on Linux, Bitwig Studio and various synth plugins. (the start command is now "C:\Programme\Adobe\Flash Builder Beta\Gumbo.exe" -clean)Īll of these should be available, as i see it.Folks often ask me how do you make microtonal music on your computer? This article explains all the essential software and hardware I used to write my most recent album. Starting FlashBuilder with -clean didn't solve the problem. HandlerActivation(commandId=.navigate.openResource, the "Configuration Details" my feature doesn't show up in the *** Features: section and my plugin doesn't show up in the *** Plugin-in Registry: section.īut they appear under Configured features and Configured plug-ins. !MESSAGE Conflict for '.navigate.openResource':
Pianoteq 6 activates as plugin but not as standalone how to#
I even have no idea how to debug this, error-log (workspace/.metadata/.log) the following message appears, (but i dont think it is related to the problem) !ENTRY .workbench 2 0 17:51:17.984 Neither of the features described above is available.
Pianoteq 6 activates as plugin but not as standalone install#
The problem now is, that the plugin never gets activated when i install it in a Flex/Flashbuilder Standalone instance.
The plugin works fine when installed in a normal Eclipse instance with Flex/Flashbuilder as plugin.
0 kommentar(er)
