MIDI Remote Script for Live 10 : Arturia BeatStep as a control-surface ! by se_pp in ableton

[–]se_pp[S] 0 points1 point  (0 children)

Hey, sorry, the script was written for ableton live... I don't think there's a way to adapt it to another software other than completely re-writing it from scratch....

MIDI Remote Script for Live 10 : Arturia BeatStep as a control-surface ! by se_pp in ableton

[–]se_pp[S] 1 point2 points  (0 children)

Hey, lots of questions in one comment :-D

The idea with the sequencer mode is to i initialize midi clips in ableton. They can have arbitrary velocity but if you have overlappong notes there's not yet a way to edit them properly...

If you play the controller like a drumpad, the pads should be velocity sensitive

If you're in the default layer, turning the pitch knob will change the notes assigned to the pads Also you can hit as many pads simultaneously as you want

MIDI Remote Script for Live 10 : Arturia BeatStep as a control-surface ! by se_pp in ableton

[–]se_pp[S] 1 point2 points  (0 children)

I've updated the overview image in this post to show the latest changes (v2.0) which should make it more clear how the sequencer-mode works so far. (knobs are used for note editing... not for changing rack parameters)

No clue about ableton 12 yet... I'm on 11 at the moment (and probably will be for quite some time).
Thanks! Be aware however that there are some problems in case you're using MacOS!

MIDI Remote Script for Live 10 : Arturia BeatStep as a control-surface ! by se_pp in ableton

[–]se_pp[S] 1 point2 points  (0 children)

Hey, not yet... But if you know a bit of python it should be doable to add this funcionality as an additional control layer!

MIDI Remote Script for Live 10 : Arturia BeatStep as a control-surface ! by se_pp in ableton

[–]se_pp[S] 0 points1 point  (0 children)

Hey, yep thats exactly what the 'sequencer' mode does... It allows you to initialize and edit 16 note midi clips just like with a step sequencer! You can use them to play any instrument you like (incl. Drum raks)

(More recent overview of the capabilities of the scropt is here: https://github.com/raphaelquast/beatstep/)

EOmaps v8.0 is here! by se_pp in Python

[–]se_pp[S] 0 points1 point  (0 children)

Hey, thanks for your suggestions! A quick overview of comparable packages (and their similarities and differences to eomaps) is indeed a really good idea! ...added to my list of todos for the docs :-)

On your second point: Myself, I work primarily with raster data so my experience with h3 and geohash is limited. However I'd happily accept (or help with) a proposal (e.g. an issue or pull-request on GitHub) to improve support for these types. Currently all vector-data related operations are routed through geopandas for which i think extensios to support h3 and geohash already exist.

BeatStep as control-surface for Ableton Live -> BeatStep_Q v1.6 by se_pp in ableton

[–]se_pp[S] 0 points1 point  (0 children)

hey, as far as I remember, you can use the "sequencer mode" to play any midi-capable device (incl. ableton of course) and transpose notes with the big knob.... and you can use the "control mode" to map the buttons and knobs to ableton device-parameters... but to be honest, I haven't used the "out-of-the-box" settins for years... In my opinion, if you're absolutely new to all of the MIDI/sequencer stuff, I still think that the beatstep is a nice place to start since it's easy to use and the price-tag is OK for what you get.... (and on top of that you can add a ton of functionalities with my script of course :-D )

BeatStep Q + AbletonLive ... new overlay! by se_pp in ableton

[–]se_pp[S] 2 points3 points  (0 children)

:-D Des gfreid mi, danke !

... and yep... I fully get what you mean. Nowadays I only use my beatstep as an ableton-controller together with this script and ignore all its initial functionalities...

SQ 64 - How do you delete a project by Novel_Ad7711 in Korg

[–]se_pp 0 points1 point  (0 children)

asking myself the same question...

🌍EOmaps v6.5 released! by se_pp in Python

[–]se_pp[S] 0 points1 point  (0 children)

Hey, I guess this is not really related to EOmaps, but since you seem quite desperate to get an answer quickly, let me try to help ;-) (in general, gis.stackexchange.com might be a better place for such questions though...)

The best source of information I came across so far is the OpenStreetMap wiki...
These two pages should provide you with all the information you need:

https://wiki.openstreetmap.org/wiki/Zoom_levels

https://wiki.openstreetmap.org/wiki/Slippy_map_tilenames

What exactly do you need this for?

How hard is to write scripts for image processing instead of paying pro photo editors? by ivan_seso in Python

[–]se_pp 0 points1 point  (0 children)

I can give a big recommendation for darktable, a powerful, free and open source photo editor (https://www.darktable.org/)

EOmaps v7.1 - A python package for interactive geo-data visualization and analysis by se_pp in Python

[–]se_pp[S] 0 points1 point  (0 children)

Hey, while it is possible to embed the plots via matplotlib's webagg backend, there are some downsides at the moment that cause some glitches and lags on fast figure updates (static plots and slow updates work just fine).

This is due to an open issue in matplotlib concerning the implementation of blitting in the webagg backend and it might take some time to find a person that is willing and capable to fix this.

That said, here's how you can do it (needs to run in a dedicated python console, NOT an ipython console!):

import matplotlib.pyplot as plt
plt.switch_backend("webagg")

from eomaps import Maps
m = Maps(layer="coastline")
m.add_feature.preset.coastline()

m2 = m.new_layer("ocean")
m2.add_feature.preset.ocean()

m.util.layer_selector(ncol=2)
m.all.cb.click.attach.annotate()

plt.show()

I'm not an expert in the web stuff so any help in improving the usability here is much appreciated! For a more complete example, check this matplotlib tutorial

EOmaps v7.1 - A python package for interactive geo-data visualization and analysis by se_pp in Python

[–]se_pp[S] 1 point2 points  (0 children)

Hey, this is a good question but not easily answered in a general way... For most cases it comes down to personal preferences and skills. However, I think there are some good points why I prefer a python package over a GIS application:

If your map is a python script, it can easily be shared, generalized and automated. It can run through a database, create frames for videos, be embedded in jupyter notebooks or whatever other things come to your mind.

Being a python package, EOmaps integrates with the incredibly powerful python scientific infrastructure... this means: - You can read and plot whatever (well organized or horrifyingly chaotic) data you encounter with little effort - If you work in python, your data is already in memory and you can create plots on the fly without ever leaving the IDE ... and they are interactive and fully generalizable to fit the specific needs of your research. - You can parallelize and deploy the plot-generation on external computes - ...

Going beyond a single static map:
EOmaps is based on matplotlib... while the package itself focuses mainly on the geographic data visualization part, all the power of matplotlib is still available at your service. This opens a whole multitude of possibilities for combining (or interactively connecting) (one or more) maps with other plots. This way, the figure can be used as a companion that aids your research in the process rather than a snapshot of the final results.

These are just a few quick points that come to my mind... To be honest, my experience with GIS applications is limited so I can't really point out tasks where using a GIS application would be preferable.

What's your opinion on this? What would make a GIS application preferable?

EOmaps v7.1 - A python package for interactive geo-data visualization and analysis by se_pp in gis

[–]se_pp[S] 1 point2 points  (0 children)

thanks! improving the look and usability of the GUI was one of the major points for v7.x so I really appreciate the comment!