darktable/dtdocs — Spanish @ Weblate: Behringer BCR2000 / BCF2000

Translation

Source change

English

type: Title ##

Spanish

Needs editing

Skip

	English	Spanish	Actions
	usb 1-1: new full-speed USB device number 2 using xhci_hcd ... mc: Linux media interface: v0.10 usbcore: registered new interface driver snd-usb-audio
	Darktable uses the simple cross-platform layer PortMidi to access the underlying OS API (Alsa, Core Midi, WinMM). If you are self-compiling, make sure you have included this library.
	Starting darktable with the debug parameters `-d input` will give additional information. It should try to open up to 10 MIDI devices in the order it finds them. On the command line you might see something like this:
	[midi_open_devices] opened midi device 'Arturia BeatStep' via 'MMSystem' as midi0 [midi_open_devices] opened midi device 'BCR2000' via 'MMSystem' as midi1 [midi_open_devices] opened midi device 'X-TOUCH MINI' via 'MMSystem' as midi2
	Two issues can arise:
	a device you don't want to use might be opened anyway (and potentially cause inappropriate behavior, like starting a fireworks show prematurely -- see [this document](http://webcache.googleusercontent.com/search?q=cache:6EcEOjfjiAkJ:gmbh.pyropak.com/docs/downloads/surefire-prologic-digital-controller_rev2010.pdf+&cd=1&hl=en&ct=clnk&gl=us)); or
	devices might appear in a different order at the next startup (for example because they are plugged into a different usb port). Since configurations are stored with the device number only, reordering would cause an incorrect layout to be picked up.
	You can fix which devices to load in a specific location and which ones to skip using the configuration parameter [preferences > miscellaneous > interface > order or exclude midi devices](../preferences-settings/miscellaneous.md#interface). To skip loading the BCR2000 in the above example and to fix the other two devices into the number 0 and 2 slots, you could set this config parameter to "`BeatStep;dontuse;X-TOUCH;-BCR2000`". This would leave the BeatStep as device midi0, always leave midi1 unused and would not load the BCR2000 at all, but if any other devices are connected, they would appear as midi3, midi4 and so on. Adding "`;-`" at the end would prevent any further devices loading.
	If you just specify the configuration parameter as a single minus sign "`-`", no devices will be loaded at all.
	For devices that use relative encoding as mentioned above, you’d have to perform the slow-turn-left procedure on every start-up, or add the found encoding to the configuration string. For example "`Loupedeck:127`".
	Some MIDI controllers have keys with a light beneath them. These can be used to toggle settings and show the current position by having the light on or off. For this to work, darktable checks periodically (a few times a second) whether, say, the position of an on-screen toggle button has been changed, and sends messages to any linked MIDI device buttons to switch their light on or off. But if an unknown device has unintentionally been connected, this could be undesirable. So by default darktable waits until a "note" message is received _from_ a MIDI button before sending any "note" light on/off messages _back_ for that (and any lower numbered) button. That way no more buttons are addressed than exist on the device. If you immediately want all button lights to be used (rather than having to press the highest note once for each session) you can specify the number of buttons in the "order or exclude MIDI devices" preference, for example, "`BeatStep:63:16`".
	supported devices	formatos de fichero soportados
	The shortcut mapping system has been most extensively tested with the Behringer devices and contains custom code to deal with their specific features. All other devices are treated as "generic midi" and may or may not work (well). If you succeed in getting a MIDI device up and running that hasn't been mentioned below, it would be greatly appreciated if you would provide feedback in order to assist others, if any special steps are required. You could do this either by submitting a documentation [pull request](https://github.com/darktable-org/dtdocs/pulls) to amend this page or by [filing an issue](https://github.com/darktable-org/dtdocs/issues) containing the necessary information.
	Behringer X-touch Mini / Compact	Behringer X-touch Mini
	These devices should be in Standard Mode (not MC). Layers A & B are somewhat supported, however, since the device does not send a notification when switching between layers, and since lights (both under buttons and the pattern used around the rotors) are set based on which layer darktable believes is active, everything will only be updated completely after you press or turn something in the "new" layer. Default settings are assumed; if any have been changed they can be restored using this [X-Touch Editor](https://mediadl.musictribe.com/download/software/behringer/X-TOUCH/X-TOUCH-EDITORv1-21.zip)	El dispositivo debe estar en modo estándar (no MC). Sin embargo, las capas A y B son compatibles en cierto grado, ya que el dispositivo no envía una notificación cuando cambia de capa, y dado que las actualizaciones de rotores y luces "ocultos" (tanto debajo de los botones como el patrón utilizado alrededor de los rotores) se ignoran, todo solo se actualizará completamente después de que presione o gire algo en la capa "nueva".
	Behringer BCR2000 / BCF2000	Behringer BCR2000
	These machines are highly configurable so there are many settings that could complicate the interaction with darktable's MIDI module. The [BC Manager tool](https://mountainutilities.eu/bcmanager) (available for Windows and MacOS) can be used to configure them. The easiest thing to do is to reset all encoders and buttons to their simplest settings, which can be done (for the BCR2000) using [this file](https://github.com/dterrahe/darktable/files/6539400/bcr2000.all.buttons.and.encoders.zip). You can send it to the machine with BC Manager or (under Linux) with amidi. There's also a global setting called "Deadtime" that determines how long the BCR ignores arriving messages after sending out updates. This is to avoid feedback loops, but for darktable it means that it blocks the adjustments sent back immediately after each rotor move. So Deadtime needs to be set to 0.	Estas máquinas son altamente configurables, por lo que hay muchas configuraciones que podrían complicar la interacción con el módulo midi de darktable. La [herramienta BC Manager](https://mountainutilities.eu/bcmanager) (disponible para Windows y MacOS) se puede utilizar para configurarlos. Lo más fácil es restablecer todos los codificadores y botones a su configuración más simple, lo que se puede hacer (para el BCR2000) usando [este archivo](https://github.com/dterrahe/darktable/files/6539400/bcr2000.all.buttons.and.encoders.zip). Puede enviarlo a la máquina con BC Manager o (bajo Linux) con amidi. También hay una configuración global llamada "Deadtime" que determina cuánto tiempo el BCR ignora los mensajes que llegan después de enviar actualizaciones. Esto es para evitar bucles de retroalimentación, pero para darktable significa que bloquea los ajustes enviados inmediatamente después de cada movimiento del rotor. Entonces Deadtime debe establecerse en 0.
	Arturia Beatstep	Arturia Beatstep
	Individual rotors can be configured to send absolute (0-127) values or changes (+/- 1,2,3,... in different encodings). The recommended setting is Relative #1 for all knobs with Knob Acceleration set to Slow (Off) or Medium. Then put the string `BeatStep:63:16` in [preferences > miscellaneous > interface > order or exclude midi devices](../preferences-settings/miscellaneous.md#interface). This can be configured with [Midi Control Center](https://www.arturia.com/support/downloads&manuals), available for Windows or MacOS.
	Loupedeck / Loupedeck+	Loupedeck
	Put the string `Loupedeck:127` in "preferences > miscellaneous > interface > order or exclude midi devices".
	@jenshannoschwalm has provided a layout that can be imported in the shortcuts dialog/tab. It can be found, with documentation, here https://github.com/darktable-org/darktable/pull/12829#issuecomment-1320264833
	Korg nanoKONTROL2	Korg nanoKONTROL2
	The device should be configured first using the Korg Kontrol Editor application to be in the CC mode and every button should be set to the Note type and Momentary button behavior. To control the lights in the buttons the LED mode should be set to External. It is important to note that the Track and the Marker buttons do not have leds in them.	El dispositivo debe configurarse primero usando la aplicación Korg Kontrol Editor para estar en el modo CC y cada botón debe configurarse como tipo Nota y el comportamiento de botón como Momentáneo. Para controlar las luces de los botones, el modo LED debe establecerse en Externo. Es importante tener en cuenta que los botones Track y Marker no tienen LED.
	There is a Kontrol Editor profile available [here](https://github.com/darktable-org/darktable/files/7603658/note_buttons.zip), which can be loaded using the Windows application to directly configure all these settings to correctly work with darktable.	Hay un perfil de Kontrol Editor disponible [aquí](https://github.com/darktable-org/darktable/files/7603658/note_buttons.zip) que se puede cargar usando la aplicación de Windows para configurar directamente todas estas configuraciones para que funcionen correctamente con darktable.
	variables	variables
	darktable supports variable substitution in a number of modules and preference settings. For example:	darktable admite la sustitución de variables en varios módulos y configuraciones de preferencias. Por ejemplo:
	Defining file names in the [export](../module-reference/utility-modules/shared/export.md) module	Definición de nombres de fichero en el módulo [exportar](../module-reference/utility-modules/shared/export.md)
	Displaying image information in the darkroom's [image information line](../module-reference/utility-modules/darkroom/image-info-line.md)	Visualización de información de imagen en la [línea de información de imagen](../module-reference/utility-modules/darkroom/image-info-line.md) del cuarto oscuro
	Displaying image information in the lighttable's overlays and tooltips (see [preferences > lighttable](../preferences-settings/lighttable.md))	Visualización de la información de la imagen en las superposiciones y la información sobre herramientas de la mesa de luz (consulte [preferencias> mesa de luz](../preferences-settings/lighttable.md))
	Placing text on an image in the [_watermark_](../module-reference/processing-modules/watermark.md) processing module	Colocar texto en una imagen en el módulo de procesamiento [_watermark _](../module-reference/processing-modules/watermark.md)

Loading…

None

String updated in the repository

English

Spanish 18 characters edited Current translation Needs editing

4 months ago

None

Source string changed

4 months ago

Browse all string changes

Things to check

Trailing space

Source and translation do not both end with a space

Fix string

Reset

Glossary

English	Spanish
No related strings found in the glossary.

String information

Source string description

type: Title ##

Flags

no-wrap

Source string location

content/special-topics/midi-device-support.md

String age

4 months ago

Last updated

2 months ago

Source string age

4 months ago

Translation file

po/content.es.po, string 3979