![uninstall metropolis ark 1 uninstall metropolis ark 1](https://audiosex.pro/data/attachments/17/17240-f4e5fd6ef5ead31d2528e92d792f35ff.jpg)
- Uninstall metropolis ark 1 update#
- Uninstall metropolis ark 1 full#
- Uninstall metropolis ark 1 software#
- Uninstall metropolis ark 1 mac#
In the meantime, you've bought a new computer, changed from Mac to PC, bought a new interface, become an alcoholic (as a result of not being able to record) and are standing on a bridge somewhere, looking down at the water below.
Uninstall metropolis ark 1 software#
This is the problem with software support: it's never the fault of the software, until you see your exact problem in the list of fixes for the next release.
Uninstall metropolis ark 1 update#
Now they want me to update my bios and chipset drivers. So far they have me uninstalling and reinstalling 5.1 and UC. Having an issue where the Audio Device Controls in Console are not showing up for my Quantum. M_ELLIOTT wrote kyleguntharp wroteI just updated from Studio One 5 to 5.1. Oh, and yes I have tried turning HiDPI on and off and it's the same either way. are suddenly snappy and responsive.Īnyone else run into this? I don't remember Scratchpads being laggy like this under 5.0. TBF, I didn't yet test whether simply hiding the scratchpad and going back to the arranger would also fix the problem, but I do know for sure that simply deleting all scratchpads fixes the problem and all the same patterns, etc. And you can't even press play again right away after stopping transport you MUST wait a moment or it won't even restart playing again.ĭelete all the scratch pads and this problem instantly goes away.
Uninstall metropolis ark 1 full#
And when you stop transport, it takes a full 2-3 seconds for the channel meters to drop to -inf. Like, you press play and there's a 500-1000 ms delay for all the graphics to start up (meters, plugin window animations, playheads moving the Arranger and in the Pattern Editor, etc.). Is it just me and some misperception on my part, or is the Scratchpad much slower and more laggy under 5.1 than it was in 5.0? Recently I've noticed significant lagginess when working in a scratch pad, especially if I'm using a MIDI pattern (rather than a MIDI part). However, the quick fix is always to open the track list at the left side of the editor (the hamburger menu) and just de-select the ones you don't want to see any more. Sometimes not, and will get "stuck" as you describe. Sometimes the Select > Double-click works correctly. It *is* a little quirky and unpredictable. What if you now want to change which tracks are visible in the editor? Repeating the process with different selected events doesn't seem to work. and this means I have to then use the track list inside the editor (which is problematic when you have 300 tracks).ĮDIT: Just saw your video. There doesn't seem to be any consistency in how it works. If I exit the editor, un-select all events and then just select ONE event, and double click - I still have the same 7 tracks visible in the editor. But let's say I want to change which tracks are visible. For example, I just did it now to be able to view 7 tracks in the editor. Selecting events and then double clicking sometimes works. So I'm interested what your workflow looks like. But I don't really use the "view but no edit" feature in the editor track list.
![uninstall metropolis ark 1 uninstall metropolis ark 1](https://d29rinwu2hi5i3.cloudfront.net/article_media/7144c707-c232-4e39-835b-cda2a198259a/headline-metropolis-ark-1-review.jpg)
What I usually do is selecting the events I want to edit and double-click them to open them in the editor. I personally usually don't use the editor track list when I edit multiple tracks at the same time. I assume you're talking about the track list in the editor? Could you give some more details in terms of what you expected? Do you want the track visibility in the arrangement to be mirrored in the editor track list? Madfloyd wrote jazzundso wroteWell, let me quote my reply in the video comment: