User Details

Username: flowstate
Website: None provided
Twitter: None provided
Soundcloud: None provided
Account Status: enabled
Member since: Nov 18 2019
About flowstate:
(report this profile)

Devices by flowstate

MIDI Morph Version 1.1
Browser Mapper Version 1.4.1
MIDI Guitar Version 1.0
Smart Search Version 1.1
Youtube Search Version 1.0
Music Maths Version 1.0
Flowpack Version 1.0

Total Downloads: 0

Comments by flowstate


Hi All,

Live 11 support has now been added.

Further updates are still underway.

Thank you for your patience and stay tuned :)


Unfortunately not, Browser Mapper is only for navigating and loading items from the Browser.

Yes this can be used without a tablet, using any MIDI Controller or even the computer keyboard.

The automap functionality for Push and Launchpad was removed as this was giving errors with the ordinary functioning of these controllers, but you can still manually map to any CC or Note as normal.

Live 11 support is underway and will be coming soon, along with an update to the device in general.

Hope this helps :)


Yeah, there have been some big changes to the scripts in Live 11, I've had a few people reach out over email asking for it to be made to work in Live 11. I WILL get round to updating the device to work in 11 as well as some other already planned updates but it won't be until some time in April. I will send out an email once the work has been done. Appologies for any inconvenience.

The bugs associated with the Mira use have been addressed, there are now two device files. One for Mira and one for other controllers. There is the option to map the navigation buttons and an added load button now also.

I am currently working on Browser Mapper 2.0 and hope this will be much more streamlined and useful. If anyone has any suggestions or requests feel free to drop them here or send me an email on the email address provided.



This should be possible - Looking into it now as well as other issues pointed out above. An email will come out when things have been resolved.

There are planned updates to this device to make navigation and mapping much more streamlined.

11strokes would probably be a good alternative to aka.keyboard object, as it works with Windows too.


Yeah, these kind of ideas are definitely on the cards - this device is designed to handle the basic piano roll functionality that is missing for the moment, but there is potential to include things like glitches, ratchets, stutters, fills, crescendo, glissando and so on.

Definitely reach out over email using the email in the receipt/manual and I will add you to the beta list for this device.

Hi - Unsure why the video link doesn't work for you, but the video is now on Gumroad as well, just follow the link.

Hi - Appologies you seem to be having issues with the device. I will look into this right away and post an update when it has been resolved.

Hi Hatyn

Thanks for your detailed report - I'll get on looking at those bugs right away,

I'm fairly sure the recent updates to remote script location installation work well now.

I will definitely take a look at your suggested features also - there are further planned updates for this device that should make it much more user friendly, the situation regarding setting up the mappings is definitely on the raddar - currently trying to find a better way of doing this.

Hi, thanks for the suggestion.

Yeah this is on the list of things to improve and should be coming as an update.

The device works best with the search and scroll buttons key/MIDI mapped, but we will be adding a floating window too at some stage.

How much latency are you experiencing? With a close to zero latency interface it should be possible to play MIDI guitar parts with ease.

MIDI Guitar should only be adding additional latency by the amount specified (15ms is recommended for most instruments).

If you would like to email the support email provided on your receipt I can explore this further with you or look at other options if you're not satisfied.

Hi, The device does add some latency, however this can be adjusted. A setting of around 15ms additional latency on the device is recommended to achieve accurate but still playable results. If you would like to email support we will try to assist you in ensuring the device is set up correctly and the best performance possible achieved.

Hi, This has not been tested with Live 9, only 10. There is no reason it shouldn't, but we will look into this and update the information.

Just to confirm - this does in fact work with the latest version of live (10.1.13). It's not recommend to try any of our devices on the Beta version of Live as correct functioning cannot be guaranteed.

It is now possible to install the script in the new location in the User Library. This will be updated in the documentation shortly.

Hi, the price is £0+ to allow for donations, if you will please email the support email provided on your receipt from the email address used in the purchase I will gladly find your order and refund you. Appologies for any confusion.

I will also look in to the issue you are describing with a white screen, this initially sounds like a common GUI issue with windows and external video windows in Live 10. Particularly on a dual GPU system. If possible please try launching Live with the integrated graphics card on your system. If the problem persists please include details in your email and I will gladly help you.

In regards to routing Audio, this has been a requested feature and is being looked in to. Currently the only way of doing this would be using an internal audio routing solution such as soundflower.

No this is running on 10.1.9.

When downloading the latest Browser Mapper update please ensure you replace the remote script with the new one also as there have been some changes to it and the old ones will not work with version 1.2.

If you would like to email me on the support email provided I could have a look at your issue in more detail and maybe video call / screen sharing session with you to see if we can get to the bottom of it.

I have checked the latest version again on Windows and Mac Ableton Live 10.1.9 with no issues.

Also please ensure you are using the latest version, 1.2 - that is available as this has had some significant updates and bugfixes.

Hi Hatyn

I'm having trouble recreating the issue your describing.

To clarify the script must be installed using the method and install location as described here:

Not in the user remote scripts folder.

There should be no need to rename or move any scripts.

Please could you send your log.txt file to the support email provided and I will have a look at this further.

Hatyn, thanks for pointing this out.

I will look into these new changes to the remote scripts and how they affect the functionality of Browser Mapper and future devices :)


Thanks for the suggestion.

It was my intention to create an iPad Lemur patch for Browser Mapper so that you can view the GUI on an iPad that way.

I agree that having it on an iPad will make it much more useful as you can see the colours and text of the buttons.

There are a few updates planned for this in the next few months so please look out for those.

I will look into adding Mira support also

Thanks :)

Yeah this was the original intention. Unfortunately the way the API and M4L are constructed and interact only allows drag and drop to be done with files. Anything with a file exension can be drag and dropped in to Max.

I am aiming to include this functionality into BrowserMapper V1.3. Drag and drop for files ONLY, not devices.

It would be possible to do this if the device was saved in a rack, and therfor had a .adg extension.

No sorry, this is just for mapping browser items such as: Instruments, Audio Effects, MIDI effects, Plug ins, Samples and so on that can be found in the Browser Menu to the left of the screen.

By looking into AU preset handling on I can see that it is not possible to load AU presets from Live's Browser.

"As they don't exist as own preset files on the hard disk, they can neither be displayed in nor loaded from Live's Browser."

Appologies for the inconvenience.

The workaround for this is to save an instrument rack with the plugin and preset you want into your user library, this can then be mapped to a button for quick launching.

Please feel free to email me regarding this as I will still be looking into it further.


Good effort on converting the 0-1 value to a dB value, not an easy task. Interested to see how you did it.

Yes you can set up the browser mapper while away from your controller, but you will need to MIDI map the controller to the buttons for it to work.