Update Mixtrack (Pro) 3 mappings for Mixxx 2.1 by radusuciu · Pull Request #1180 · mixxxdj/mixxx

radusuciu · 2017-02-10T00:05:59Z

This is a WIP, not quite ready for review since I haven't had time to actually test it. Opening pull request a bit early just to move discussion from #1014. First time contributor so please let me know if I'm going against the grain!

To-do:

Load sample if none is currently loaded
Make use of focused_effect
Map sampler eject
Look at bpm tap functionality, which I either broke, or is broken

Be-ing · 2017-02-10T01:41:13Z

    // NMTP3 is a "Model A" controller for scratching, it centers on 0.
    // See http://www.mixxx.org/wiki/doku.php/midi_scripting#scratching
    // and see "Jogger" object constructor
+    this.beatJumpSize = 1;


In the future, this will be available as a ControlObject that will also be shown on skins so controller scripts won't have to keep track of this. I might implement that for Mixxx 2.2. There is a Launchpad ticket tracking it.

That would be awesome. I will not be committing code that will modify this value until the CO will be there as this controller has no way of displaying it.

You may find a beatjump size of 4 beats to be more helpful.

FYI, I just tried to install Mixxx 2.1 on Windows 10 and the installer failed. Also, I got 3 different warnings asking to confirm that I wanted to install the package; the first one saying that Windows did not recommend installing it, likely because package was not signed.

In Windows 10 you have to click "More Info" and then tell it you really mean to install it.

Please report a bug for that.

radusuciu · 2017-02-10T02:33:07Z

Will the new effects interface be used across all skins? There is currently a lot of code duplication as a result of having to support skins that have only one effect per rack. Documented here:

// Effects mode
// 1 for multi-effect mode (3 effects controlled in each EffectUnit, best used with Deere Skin)
// 2 for single effect mode (1 effect controlled in each EffectUnit, best used with skins other than Deere)
var FXmode = 1; // multi-effect mode by default

Be-ing · 2017-02-10T02:33:51Z

Will the new effects interface be used across all skins?

Yes, that's part of the point. Controller mappings having different options for different skins is a really ugly situation.

radusuciu · 2017-02-10T02:34:41Z

Awesome, thank you. 👍

Be-ing · 2017-02-10T05:28:45Z

    }

-    for (i = engine.getValue("[Master]", "num_decks"); i >= 1; i--) {
+    for (var i = engine.getValue("[Master]", "num_decks"); i >= 1; i--) {


FYI, in the old version of JS that Mixxx still uses (and in modern JS using var), variables are scoped to functions, not blocks as you might expect. You don't need to redeclare i for each loop. Just something to be aware of if you encounter puzzling bugs with one loop messing up the behavior of the next.

I'm aware that JS lacks block scoping when using var, and that variable declarations get hoisted, but I think pretty much everyone except Crockford will advocate for including var in for loops.

As an aside, the mapping in its current state is not functional since I committed stuff without having the controller on hand. I will go back and test things commit by commit though!

Okay, just pointing it out because many people who contribute mapping scripts aren't that familiar with JS.

radusuciu · 2017-02-10T21:23:37Z

@djsteph Just came across this: https://docs.google.com/spreadsheets/d/1YbLS7hBprP2uvEKizO-b0WiaRmpvml0r5NfBp4GmBVc/edit#gid=0

I'm guessing it was most useful during development but I think I'd like to use it as well. It will make a fantastic quality check for the mapping.

djsteph · 2017-02-10T22:38:30Z

You are welcome to use it...I think anyone can edit the file

…

On Fri, Feb 10, 2017 at 4:23 PM, Radu Suciu ***@***.***> wrote: @djsteph <https://github.com/djsteph> Just came across this: https://docs.google.com/spreadsheets/d/1YbLS7hBprP2uvEKizO- b0WiaRmpvml0r5NfBp4GmBVc/edit#gid=0 I'm guessing it was most useful during development but I think I'd like to use it as well. It will make a fantastic quality check for the mapping. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#1180 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AQDKyQgEOAPE4mdCerrXSVUkS_pG51EBks5rbNVcgaJpZM4L81Rl> .

radusuciu · 2017-02-14T04:25:36Z

Trying to debug things and getting a billion messages of this nature:

Note that none of the buttons on the controller are flashing, but the messages keep pouring in.

Debug [Controller]: "MixTrack Pro 3: outgoing: status 0x91 (ch 2, opcode 0x9), ctrl 0x13, val 0x20" 
Debug [Controller]: Starting one-shot timer: 184549449 
Debug [Controller]: "MixTrack Pro 3: outgoing: status 0x92 (ch 3, opcode 0x9), ctrl 0x13, val 0x20" 
Debug [Controller]: Starting one-shot timer: 268435486 
Debug [Controller]: Killing timer: 184549449 
Debug [Controller]: "MixTrack Pro 3: outgoing: status 0x91 (ch 2, opcode 0x9), ctrl 0x13, val 0x00" 
Debug [Controller]: Killing timer: 268435486 
Debug [Controller]: "MixTrack Pro 3: outgoing: status 0x92 (ch 3, opcode 0x9), ctrl 0x13, val 0x00" 

Debug [Controller]: "MixTrack Pro 3: outgoing: status 0x91 (ch 2, opcode 0x9), ctrl 0x13, val 0x20" 
Debug [Controller]: Starting one-shot timer: 1493172255 
Debug [Controller]: "MixTrack Pro 3: outgoing: status 0x92 (ch 3, opcode 0x9), ctrl 0x13, val 0x20" 
Debug [Controller]: Starting one-shot timer: 1509949470 
Debug [Controller]: Killing timer: 1493172255 
Debug [Controller]: "MixTrack Pro 3: outgoing: status 0x91 (ch 2, opcode 0x9), ctrl 0x13, val 0x00" 
Debug [Controller]: Killing timer: 1509949470 
Debug [Controller]: "MixTrack Pro 3: outgoing: status 0x92 (ch 3, opcode 0x9), ctrl 0x13, val 0x00" 

Debug [Controller]: "MixTrack Pro 3: outgoing: status 0x91 (ch 2, opcode 0x9), ctrl 0x13, val 0x20" 
Debug [Controller]: Starting one-shot timer: 805306398 
Debug [Controller]: "MixTrack Pro 3: outgoing: status 0x92 (ch 3, opcode 0x9), ctrl 0x13, val 0x20" 
Debug [Controller]: Starting one-shot timer: 922746911 

Debug [Controller]: Killing timer: 805306398 
Debug [Controller]: "MixTrack Pro 3: outgoing: status 0x91 (ch 2, opcode 0x9), ctrl 0x13, val 0x00" 
Debug [Controller]: Killing timer: 922746911 
Debug [Controller]: "MixTrack Pro 3: outgoing: status 0x92 (ch 3, opcode 0x9), ctrl 0x13, val 0x00" 
Debug [Controller]: "MixTrack Pro 3: outgoing: status 0x91 (ch 2, opcode 0x9), ctrl 0x13, val 0x20" 
Debug [Controller]: Starting one-shot timer: 1811939393 
Debug [Controller]: "MixTrack Pro 3: outgoing: status 0x92 (ch 3, opcode 0x9), ctrl 0x13, val 0x20" 
Debug [Controller]: Starting one-shot timer: 1912602654 

Debug [Controller]: Killing timer: 1811939393 
Debug [Controller]: "MixTrack Pro 3: outgoing: status 0x91 (ch 2, opcode 0x9), ctrl 0x13, val 0x00" 
Debug [Controller]: Killing timer: 1912602654 
Debug [Controller]: "MixTrack Pro 3: outgoing: status 0x92 (ch 3, opcode 0x9), ctrl 0x13, val 0x00" 
Debug [Controller]: "MixTrack Pro 3: outgoing: status 0x91 (ch 2, opcode 0x9), ctrl 0x13, val 0x20" 
Debug [Controller]: Starting one-shot timer: 1660944414

Is this normal?

Be-ing · 2017-02-14T04:32:02Z

Yes, that is normal. I added outgoing MIDI debugging messages in #1004. Is that an issue? Would you like an option to only see incoming MIDI?

radusuciu · 2017-02-14T18:47:17Z

Well, it kind of makes it difficult to debug by logging things with print statements since anything you log gets drowned out very quickly by messages from permanent timers.

Perhaps I'm doing debugging wrong? These are the options I am using:

--developer --debugLevel 2 --controllerDebug --resourcePath "%USERPROFILE%/Github/mixxx/res"

Thank you for your help!

Be-ing · 2017-02-14T19:47:46Z

--debugLevel was recently renamed to --logLevel (#1159), so that does not do anything currently, but --developer automatically sets logLevel to debug unless otherwise specified. Try running with --logLevel debug without --controllerDebug. That might hide the MIDI debugging messages but still let scripts print to the console output.

djsteph · 2017-02-15T02:54:09Z

-        contract = 0;
-    }
-
    if (shifted && value === ON) {


Just curious, you are not keeping the maximize library on the browse button push? In this code sniplet, I don't see any value set for LibraryGroup and Library command nor do I see the actual change in the code to remove the variable

That was an oversight - thanks for noticing. Will fix.

- Pressing sampler button if no sample is currently loaded will load sample from library - Shift + sampler button if sample is loaded will eject appropriate sample Fix checking if track is loaded. Make sure sample is stopped before ejecting

Be-ing

A few quick comments

Be-ing · 2017-03-08T21:15:39Z

 *                 the same tempo, and decks that also have quantize
 *                 enabled will always have their beats lined up.
- * If the Sync Loack was previously activated, it just desactivate it,
+ * If Sync Lock was previously activated, it just desactivate it,


Typo: "deactivate"

Be-ing · 2017-03-08T21:16:13Z

            } else {
-                // play sampler with Sync
                engine.setValue(group, "cue_gotoandplay", 1);
                engine.setValue(group, "beatsync", 1);


You removed the comment about playing with sync. Did you mean to remove the syncing?

No, I just thought the code is pretty clear in this case. Shift + Sampler will play the sample without sync so it's pretty easy to switch between the two.

Earlier I thought there'd be an issue with mapping Shift + Sampler to stop a sample, but there isn't one since stopping is only done on playing samples and playing without sync is only done on non-playing samples.

Be-ing · 2017-03-09T05:23:12Z

+<MixxxControllerPreset mixxxVersion="2.1.0+" schemaVersion="1">
    <info>
        <name>Numark Mixtrack (Pro) 3</name>
        <author>Stéphane Morin</author>


Feel free to mention yourself here (Keep Stéphane's name too).

Be-ing

Wow that was a lot of code changed! Thanks for the cleanup. I found a handful of other places in the diff where the code could be cleaned up a little bit plus a few UX suggestions. Looks almost ready to merge.

Be-ing · 2017-03-09T05:33:14Z

-// fastSeekEnabled: enable fast seek with Jog Wheel with Wheel Off and Shift ON 
-// Shift can be locked or not
-var fastSeekEnabled = true;
-
 //activate PFL of deck on track load
 var smartPFL = true;

 // use beatlooproll instead of beatloop
 var beatlooprollActivate = false;


This option could be removed by following the behavior of the new loopauto_toggle CO in #1187: normal loops for loops > 1 beat; rolling loops for loops <= 1 beat. That matches how the loop sizes are mapped to the pads in this. Normal loops without shift; rolling loops with shift.

I don't think those behaviours are the same, this option makes it so that all the loops set with the auto loop buttons are rolling. Also, the Shift behaviour isn't to toggle loopRoll, but rather to allow for the toggling of fractional beat loops (mapping 4 buttons to 8 loop sizes).

I understand your suggestion but I'm not quite sure if I want all of my <= 1 beat loops to be rolling. Will consider it, especially if others want the shifted behaviour you describe.

For now, I will remove the option since I can't imagine anyone wanting all of their loops to be rolling, especially without a way to toggle. Will be revisiting this when #1187 is merged.

What is the use of loops <= 1 beat that aren't rolling? Play with it, I think you'll find my suggestion makes sense.

Say instead of rolling into a drop on the same track, you bring in another track instead, and you want to leave the other track where it is instead of having it slip past when you stop the loop.

I suppose there are other ways around that though..

Be-ing · 2017-03-09T05:37:09Z

-            });
+        // permanent timer
+        this.flashTimer = engine.beginTimer(num_ms_on + num_ms_off, function() {
+            myself.flashOnceOn(false);


You can get rid of this hacky closure and use this directly since #1196 was merged.

is this:

engine.beginTimer(num_ms_on + num_ms_off, 'this.flashOnceOn(false)');

preferred over:

engine.beginTimer(num_ms_on + num_ms_off, this.flashOnceOn.bind(this, false));

I get that I don't need to bind for this but I also have an argument I'd like to curry. Most examples I've seen use the string method but I feel like the latter is better practice.

IMO the ability to pass strings instead of functions is an ugly hack that shouldn't have been implemented in the first place. I think this form would be best:

engine.beginTimer(num_ms_on + num_ms_off, function () { this.flashOnceOn(false); });

Be-ing · 2017-03-09T05:37:49Z

    if (flashCount > 1) {
        // flashcount>0 , means temporary flash, first flash already done,
        // so we don't need this part  if flashcount=1
        // temporary timer. The end of this timer stops the permanent flashing

-        this.flashTimer2 = engine.beginTimer(flashCount * (num_ms_on +
-            num_ms_off) - num_ms_off, function() {
+        this.flashTimer2 = engine.beginTimer(flashCount * (num_ms_on + num_ms_off) - num_ms_off, function() {
            myself.Stopflash(relight);


Be-ing · 2017-03-09T05:37:57Z

-            myself.flashOnceOff(relight);
-        }, true);
+    this.flashOnceTimer = engine.beginTimer(this.num_ms_on - scriptpause, function() {
+        myself.flashOnceOff(relight);


Be-ing · 2017-03-09T05:38:05Z

-                }, true);
+    if (this.ButtonTimer === 0) { // first press
+        this.ButtonTimer = engine.beginTimer(this.DoublePressTimeOut, function() {
+            myself.ButtonDecide();


Similar to my question above.

engine.beginTimer(this.DoublePressTimeOut, 'this.ButtonDecide()');

vs.

engine.beginTimer(this.DoublePressTimeOut, this.ButtonDecide);

here I assume that bind isn't necessary at all since we're not going to pass any parameters.

Be-ing · 2017-03-09T05:47:33Z

            } else {
-                // Else play/pause
-                toggleValue("[Channel" + decknum + "]", "play");
+                // else play/pause


Likewise, no explanation needed.

Be-ing · 2017-03-09T05:47:56Z

            if (!deck.TrackIsLoaded()) {
-                // If a track is not loaded, load the selected track (if any) and play
-                engine.setValue("[Channel" + decknum + "]", "LoadSelectedTrackAndPlay", true);
+                // if a track is not loaded, load the selected track (if any) and play


I think this code is self explanatory and doesn't need a comment.

Be-ing · 2017-03-09T05:59:55Z

+    } else if (deck.shiftKey && value === DOWN) {
+        // load next effect and make sure the unit is enabled
+        engine.setValue(effectGroup, "next_effect", true);
+        engine.setValue("[EffectRack1_EffectUnit" + decknum + "]", "group_[Channel" + decknum + "]_enable", true);


I still think this line should be removed. It may have made sense with the old mapping, but I don't think it makes sense to couple it to switching one effect in the chain.

Be-ing · 2017-03-09T06:02:33Z

-        for (i = 1; i <= 4; i++) {
+    var deck = NumarkMixtrack3.deckFromGroup(group);
+    // beat knobs sends 1 or 127 as value. If value = 127, turn is counterclockwise
+    var increase = (value !== 127);


I think var increase = (value === 1); would be clearer.

Be-ing · 2017-03-09T06:07:59Z

-    var decknum = script.deckFromGroup(group);
-    var deck = NumarkMixtrack3.decks["D" + decknum];
+    if (deck.loaded && TrackEndWarning) {
+        var timeremaining = duration * (1 - value);


inconsistent capitalization of variable name

Be-ing · 2017-03-10T01:15:26Z

-        }, true);
+
+        this.ButtonLongPressTimer = engine.beginTimer(
+            this.LongPressThreshold, this.ButtonAssertLongPress, true


Hmm, I think this actually would have worked in Mixxx 2.0. What #1196 fixed was using this inside the callback function. For example: fd9815d

Oh, the ButtonAssertLongPress function refers to this, so maybe it wouldn't have worked. Anyway, looks good now.

Yeah, just figured there's little point in wrapping it with a function if no arguments need to be passed.

Be-ing · 2017-03-10T01:21:21Z

    "hotCue3": 0x1d,
    "hotCue4": 0x1e,
-    "Cue": 0x03,
+    "cue": 0x03,


FYI, if you forget something in a commit and haven't added any new commits yet, git commit --amend is an easy way to overwrite the incomplete commit. It's no big deal you didn't do that here, but something to keep in mind if you are in that situation again.

Be-ing · 2017-03-10T01:26:30Z

Alright this looks good to me! 👍 Thank you! I'm glad one of the best selling controllers on the market right now will have a good mapping for the new effects UI for the 2.1 release. :)

After #1187 is merged you may want to reconsider how loops are mapped, but I've been careful to make sure that old mappings will still work with the new looping interface.

radusuciu · 2017-03-10T01:29:56Z

Thanks! I want to do a final test before merge so as to not have to open another PR just for minor fixes.

I will follow up with a PR for #1187 and #940 in the near future.

Be-ing · 2017-03-10T01:41:14Z

If you'd like to play with those before they're merged, you can checkout PRs locally and build them. I put some tips on the wiki for using git worktree to play with experimental skins and mappings.

Conflict with InstantFX

120 goes into red way too easily. 82 was juuuust right.

radusuciu · 2017-03-10T06:31:26Z

Good to go from my end with these minor fixes. Effect units definitely need to be reworked though, will try and see if I can get a build going as you described.

Thanks for review and hand-holding!

Be-ing · 2017-03-18T00:23:41Z

Could someone merge this?

I do not know if you are on the mailing list, but I just wrote a proposal for registering MIDI inputs from JS. Feedback would be appreciated.

Be-ing · 2017-03-25T15:29:29Z

@daschuer can you merge this?

daschuer · 2017-03-25T17:54:12Z

Yo! Thank your for the work.

Be-ing · 2017-06-06T19:51:18Z

@radusuciu, now that #1187 and #940 have been merged, could you update this for the new looping and beatjumping Controls? I suggest remapping the autoloop pad layer similar to the Pioneer DDJ-SB2. Users have been reporting that mapping pads that way is a little strange at first but great after getting used to it. Unlike the DDJ-SB2, because there are other parts of the controller that could be used for beatjumping, I think it would make more sense to use beatjump_1_backward/forward as the shift action for loop halve/double. You could use shift + pitch bend buttons to halve/double beatjump_size and shift + Beats encoder for beatjump_backward/forward.

Also, when I played with a DDJ-SB2, I found it was more helpful to have quick access to changing the focused effect than toggling the effect enable switches. I suggest switching these around in the Mixtrack Pro 3 mapping, so pressing the effect buttons changes the focused effect and Tap + effect button toggles the effect enable switches.

radusuciu · 2017-06-06T19:55:54Z

Yep, I will update it to make use of the new controls and will consider your mapping suggestions. I've also done a bit of playing with your components lib so can maybe bring in EffectUnit to start.

Be-ing · 2017-06-06T20:06:55Z

The EffectUnit object from the Components library is made for controllers with 4 effects knobs, so adapting it for the Mixtrack Pro 3 would probably be just as much (or maybe more) work than writing the code from scratch. However, using the Components and ComponentContainer objects to write an EffectUnit object specific to this controller would make sense if you'd like to rewrite the code you already have.

I don't recommend copying how the effects buttons work with the DDJ-SB2 in #1243. I used short versus long button presses to distinguish between switching focus and enabling effects, which is a bit clumsy because the script has to wait for the button to be released before switching the focus. There also isn't a way to show which effects are enabled on the controller. These don't need to be issues with the Mixtrack Pro 3 because the Tap button can be used to switch layers.

radusuciu force-pushed the master branch from 8149f37 to 86383de Compare February 10, 2017 00:21

Be-ing reviewed Feb 10, 2017

View reviewed changes

radusuciu force-pushed the master branch from 4141c5c to 54a86c6 Compare February 10, 2017 02:22

Be-ing reviewed Feb 10, 2017

View reviewed changes

radusuciu force-pushed the master branch 2 times, most recently from 3925289 to 38ed3f2 Compare February 14, 2017 09:55

djsteph reviewed Feb 15, 2017

View reviewed changes

radusuciu force-pushed the master branch 2 times, most recently from 8cadac0 to 84edb44 Compare February 15, 2017 17:36

radusuciu added 12 commits February 15, 2017 13:02

Load sampler if none is currently loaded.

0a20663

- Pressing sampler button if no sample is currently loaded will load sample from library - Shift + sampler button if sample is loaded will eject appropriate sample Fix checking if track is loaded. Make sure sample is stopped before ejecting

Small refactor

d623090

Add configurable beatjump size.

8d3fb42

Map loop move

c5c9b2f

Avoid code duplication for 4 deck support

a6390d5

Use new track_loaded control.

fd7004a

Remove checking for effect rack configuration

1c1ddc6

Simplify LED init

db84617

Remove softTakeover workaround

ba0f18d

Bump mininum mixxx version to 2.1

f4afa7f

Fix LED init

1a938c5

Fix TrackIsLoaded call

7e9aed2

Be-ing reviewed Mar 8, 2017

View reviewed changes

radusuciu added 2 commits March 8, 2017 14:43

Give instantfx priority over focused effect

bde2c93

Small fixes

a266753

Be-ing reviewed Mar 9, 2017

View reviewed changes

radusuciu added 9 commits March 9, 2017 12:10

Use this context directly. mixxxdj#1196

73656ab

Fix some capitalization issues

afd030f

Camelcase LEDs

76e3bf9

Finish camelcasing LED objects

98ee718

Remove effectUnit channel toggle

de3df20

Small refactor

90a0125

Remove superfluous comments

5834f75

Remove beatlooprollActivate option

478c7ec

Camelcase padindex

5d14da2

Be-ing reviewed Mar 10, 2017

View reviewed changes

radusuciu added 3 commits March 9, 2017 20:49

Misc bug fixes for beatjump/loopmove

9cd89b1

Move brake and spinback

98dbddb

Conflict with InstantFX

Adjust VUMeter multiplier

491ab27

120 goes into red way too easily. 82 was juuuust right.

daschuer merged commit e9f2d97 into mixxxdj:master Mar 25, 2017

Uh oh!

Conversation

radusuciu commented Feb 10, 2017 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

radusuciu commented Feb 10, 2017

Uh oh!

Be-ing commented Feb 10, 2017 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

radusuciu commented Feb 10, 2017

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

radusuciu commented Feb 10, 2017

Uh oh!

djsteph commented Feb 10, 2017 via email • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

radusuciu commented Feb 14, 2017 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Be-ing commented Feb 14, 2017

Uh oh!

radusuciu commented Feb 14, 2017 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Be-ing commented Feb 14, 2017

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Be-ing left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Be-ing Mar 9, 2017 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Be-ing left a comment

Choose a reason for hiding this comment

Uh oh!

Be-ing Mar 9, 2017 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Be-ing Mar 9, 2017 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

radusuciu Mar 9, 2017 • edited Loading Uh oh! There was an error while loading. Please reload this page.

radusuciu commented Feb 10, 2017 •

edited

Loading

Be-ing commented Feb 10, 2017 •

edited

Loading

djsteph commented Feb 10, 2017 via email •

edited

Loading

radusuciu commented Feb 14, 2017 •

edited

Loading

radusuciu commented Feb 14, 2017 •

edited

Loading

Be-ing Mar 9, 2017 •

edited

Loading

Be-ing Mar 9, 2017 •

edited

Loading

Be-ing Mar 9, 2017 •

edited

Loading

radusuciu Mar 9, 2017 •

edited

Loading

radusuciu Mar 9, 2017 •

edited

Loading

Be-ing Mar 10, 2017 •

edited

Loading

Be-ing Mar 10, 2017 •

edited

Loading