Skip to content

Workshop 2015 Florida

Trond Lossuis edited this page Jul 16, 2015 · 25 revisions

When and Where?

July 19 - 26 at Stetson University

Flight arrangements can be made to the following airports: MCO, SFB, DAB

Who? (w flight info)

  • Nathan Wolek - host
  • Timothy Place - Kansas City USA
  • arrive: MCO, Jul 20, 6:12 AM via JetBlue 802
  • depart: MCO, Jul 24, 6:37 PM via JetBlue 801
  • Trond Lossius - Norway
  • arrive: MCO, Jul 18, 7:50 PM via Norwegian 7057
  • depart: MCO, Jul 27, 11:00 PM via Norwegian 7056
  • Jan Schacher - Switzerland
  • arrive: MCO, Jul 19, 7:40 PM via Delta 1110
  • depart: MCO, Jul 27, 10:30 AM via Delta 2331
  • Max Mustermann - USA
  • arrive: MCO, Jul 18, 3:30 PM via Southwest
  • depart: MCO, Jul 27, 9:05 AM via United
  • Ethan Greene - local guest

What? (main topics)

How?

Support for this workshop has been provided through the Stetson's Professional Development Committee and Office of the Provost.

Rough Schedule

  • Sun July 19 - travel day
  • Mon July 20 - work
  • Tues July 21 - work
  • Wed July 22 - work
  • 20:00: SpatDIF Skype with Chikashi
  • Thurs July 23 - work
  • Fri July 24 - work
  • Sat July 25 - sight seeing
  • Sun July 26 - travel day

Topic Notes

Please use the following sections to begin gathering details about specific issues to be addressed during the workshop.

Workflow & Testing

  • Can we finally migrate all projects to branching strategy agreed to at 04-20 BOD meeting (master instead of dev)?
  • Confirm that units tests are running in new CMake build configuration. If not, how can we ensure that this is still part of our regular release process?

Using Jamoma Core for DAW plug-in development

  • Trond and Nathan have an interest in using the Core apart in an IDE like Xcode to develop plug ins. This could be done using a framework like wdl-ol as a starting point with Jamoma Core objects doing the actual processing of samples. Wondering if Tim might be able to sit down and walk us through this process. If we get it working, we should develop tutorial for others to follow.

Path forward for Graph and AudioGraph

  • What are the next steps in this area?

Path forward for granular effects

  • LowkeyNW package is now working with Max 7 and includes basic externals to build more complex granular effects. Should these be built in LowkeyNW package so that it becomes Jamoma user library OR should they be part of Jamoma Max implementation so that it becomes Max dependency?
  • Core Issue #296 needs some discussion in order to restart work on fixing it and related issues.

Path forward for SpatDIF and spatialization

  • What are the next steps in this area?

Jamoma DSP EffectLib extension

  • Core Issue #279 port gverb~ to Jamoma
  • Trond believes that TTBalance should be refactored. This is an effect that depends on a side chain signal. Currently this is implemented in an adhoc manner on a single unit base, with the result that we are unable to use the standard wrappers for j.balance~ and j.balance= in Max. As side chains are quite common in various effects, we should rather extend EffectsLib to provide a standard implementation for effects requiring sidechains.
  • Trond believes that TTPanorama should be refactored. This is a stereo-out-only effect, but it is implemented on an adhoc basis, and consequently we are not able to use the standard wrappers for j.panorama~ and j.panorama= in Max. There might be other effects that only work with stereo inpput or output signals (such as stereo => mid-side and mid-side => stereo converters). We should rather provide a unified, standard implementation for this, so that the standard wrappers can be used.
  • Trond believes that the EffectsLib need to be extended to provide a standard attribute (or similar) for all units that provides information on the amount of delay (in samples or milliseconds) that the unit cause. For some effects such as TTMutesolo this will be 0 samples, while for others such as TTLimiter it will depend on the lookahead attribute. When used in plugin implementations this is required in order for the plugin to inform its host of what sample correction to employ.

Issues to look into