Skip to content
This repository has been archived by the owner on Dec 7, 2019. It is now read-only.

This ambitious project aims to provide a single API for MIDI control pedal ANY multi-effect

Notifications You must be signed in to change notification settings

PedalController/MidiPedalController

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

10 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

MidiPedalController

This ambitious project aims to provide a single API for MIDI control pedal ANY multi-effect

Test:

This code provides an API for projects implementation.

Currently the projects that uses MidiPedalController are:

  • EasyEditShare: Simple Zoom Edit&Share implementation for view the effects in the current patch (bank);
  • PiPedalController: A project for extends the Zoom G3 guitar pedal controller.

To control/detect what?

To detect:

  • CommonCause.TO_PATCH : Patch changed to specific patch
  • CommonCause.PATCH_NUMBER : Details of a patch number
  • CommonCause.PATCH_VOLUME : Details of a patch volume
  • CommonCause.PATCH_NAME : Details of a patch name
  • CommonCause.EFFECT_ACTIVE : Specific effect actived
  • CommonCause.EFFECT_DISABLE : Specific effect disabled
  • CommonCause.EFFECT_TYPE : Specific effect type
  • CommonCause.PARAM_VALUE : Specific param of effect actived

To control:

  • Patch
  • PedalController.nextPatch()
  • PedalController.beforePatch()
  • PedalController.toPatch(int index)
  • Current patch
  • PedalController.toogleEffect(int idEffect)
  • PedalController.hasActived(int idEffect)
  • PedalController.activeEffect(int idEffect)
  • PedalController.disableEffect(int idEffect)
  • PedalController.setEffectParam(int idEffect, int idParam, int value)
  • PedalController.getAmountEffects()
  • All the multistomp options
  • PedalController.multistomp(): PedalController is a façade for the multistomp.

Support:

  • PedalCompany.ZoomCorp
  • PedalType.G2Nu (basic, but not tested)
  • PedalType.G3
PedalType CommonCause Detects pedal change? Request changes to pedal?
PedalType.G3 TO_PATCH (x) (x)
PedalType.G3 PATCH_NUMBER ( ) * TO_PATCH equivalent
PedalType.G3 PATCH_VOLUME ( ) ( )
PedalType.G3 PATCH_NAME (x) ( )
PedalType.G3 EFFECT_ACTIVE (x) (x)
PedalType.G3 EFFECT_DISABLE (x) (x)
PedalType.G3 EFFECT_TYPE ( ) * ( )
PedalType.G3 PARAM_VALUE (x) (x)
  • Only by ZoomGSeriesMessages.REQUEST_SPECIFIC_PATCH_DETAILS(idPatch). It inform
  • PATCH_NUMBER
  • PATCH_NAME
  • EFFECT_ACTIVE
  • EFFECT_DISABLE
  • EFFECT_TYPE

How to use:

Changing

// Throws DeviceNotFoundException if not found
PedalController multistomp = PedalControllerFactory.generateControllerFor(ZoomG3Type.class);

// Init the system (not your pedal)
// Throws MidiUnavailableException
multistomp.on();

// TO ZOOM G2Nu
// 0 to 7: Comp to Reverb
// 8 Mute
// 9 Bypass

multistomp.activeEffect(0);
multistomp.disableEffect(1);

// TO ZOOM G3
// 0 to 5 (6 Pedals)
// ...

// Set Patch
multistomp.beforePatch();
multistomp.nextPatch();
multistomp.toPatch(99);

System.out.println(multistomp);

// Turn down the system, not your pedal :P
multistomp.off();

Detect changes

You can receive notifications directly from your pedal

PedalController multistomp = PedalControllerFactory.searchPedal();

pedal.addListener(messages -> {
	messages.getBy(CommonCause.ACTIVE_EFFECT)
			.forEach(message -> System.out.println(message.details().effect));
	messages.getBy(CommonCause.DISABLE_EFFECT)
			.forEach(message -> System.out.println(message.details().effect));

	messages.getBy(CommonCause.TO_PATCH)
			.forEach(message -> System.out.println(message.details().patch));

	messages.getBy(CommonCause.PATCH_NAME)
			.forEach(message -> System.out.println((String) message.details().value));

	messages.getBy(CommonCause.SET_PARAM)
			.forEach(message -> System.out.println(pedal));
});

How to Collabore

Understand the structure:

  • Archicheture: The utils and exceptions of the system;
  • Controller: It offers a simple API to use;
    • MultistompChanger: Filter: MidiMessage parsed -> Changes in Multistomp object
  • Domain: The multistomp structure and message structure;
  • Connection: The connection with Real Multistomp and this lib;
  • Multistomp: Specific implementation for pedals;
  • Test: Unit tests;
  • Main: User demonstrations.

Implement!

  1. Create a "Source Folder" that corresponds the real Pedal Company; zoom/
  2. Create a package like: com.yourcompany.multistomp.pedalcompany; br.com.srmourasilva.multistomp.zoom
  3. Create a PedalType implementation. This will use @Pedal annotation; ZoomG3Type
  4. Create the MessageEncoder and MessageDecoder implementations; ZoomGSeriesEncoder and ZoomGSeriesEncoder
  5. Use the MidiConnection or implements the specific pedal Connection.

Thanks for:

About

This ambitious project aims to provide a single API for MIDI control pedal ANY multi-effect

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages