Hercules DJControl Jogvision: First release (all MIDI mapped) #2370

perseo22 · 2019-11-25T12:19:18Z

Hercules DJControl Jogvision fully (I hope!) mapped.

https://www.mixxx.org/wiki/doku.php/hercules_dj_control_jogvision

A job mainly from DJ Phatso, with contributions by Kerrick Staley and me, David TV (aka perseo22, aka hasses1.07)

res/controllers/Hercules_DJControl_Jogvision-scripts.js

res/controllers/Hercules_DJControl_Jogvision.midi.xml

Holzhaus · 2019-11-25T21:00:59Z

Thanks for contibuting! Code looks mostly good to me except for a few small issues. I think removing redundancy could make the code drastically shorter.

Pinging @Be-ing, I'm sure he also wants to take a look at this.

Be-ing · 2019-11-26T22:43:52Z

I think removing redundancy could make the code drastically shorter.

Yes, the first thing that stands out about the code is that only half of it is needed. There's no need to have separate functions for identical features on different decks. You can determine the deck from the MIDI channel or from the "group" parameter passed to the JS function which you'd have to specify in the XML.

perseo22 · 2019-11-28T15:19:59Z

Hi all!
Working in all your comments!
Will try to upload a new commit very soon!

perseo22 · 2019-12-02T09:02:09Z

Hi all!

I just pushed a commit with all the suggested changes :)

Holzhaus

Thanks! I'm not sure why the diff is so broken, did you change the line terminators (DOS/Unix)?

In any case, I reviewed the code and didn't notice major issues. Most of my suggestions are whitespace fixes or replace == with type-safe ===. I'm not sure why you mass-set values in the init method though.

res/controllers/Hercules_DJControl_Jogvision-scripts.js

Holzhaus · 2019-12-02T19:44:24Z

res/controllers/Hercules_DJControl_Jogvision-scripts.js

+	engine.setParameter("[EffectRack1_EffectUnit1]", "mix", 0.6);
+	engine.setParameter("[EffectRack1_EffectUnit2]", "mix", 0.6);
+	engine.setParameter("[QuickEffectRack1_[Channel1]]", "super1", 0.5);
+	engine.setParameter("[QuickEffectRack1_[Channel2]]", "super1", 0.5);


Why do you mass-set these values? I think that this would cause issues if Mixxx gets MIDI hotplug support in the future. If a user accidently disconnects the controller and then reconnects it, this could cause abrupt changes in the audio output.

This was done in the original script to "work around" the limited controls available on the Jogvision (which were built out of the bundle with Serato).

Since there is only one encoder that sends 3 midi signals to control the FX amount (meaning it would affect the level of all 3 effects simultaneously), I figured I could instead configure the fx rack as auto-FX for all 3 buttons and preset the levels to an appropriate amount for each of them.

The same goes for the motion sensor "Air FX", which goes back to 0 by default. In order to use if with the Filter, it needed to be set to the middle position, and it was decided that only the lower range would be used.

There is surely a more practical and elegant ways to do all this for sure, but my coding knowledge are still limited. Any suggestions are much welcomed.

perseo22 · 2019-12-13T09:41:07Z

Hi!
A new push has been made taking into account all your suggestions ;)
Thanks!

perseo22 · 2020-01-03T08:59:08Z

Happy new year to all!!
I just pushed what I think could be the very final commit, with a couple of regression bugs fixed (VuMeter and head CUE/MIX button).
Beyond that, I don't know what else I could/should do.

Thanks a lot!!!!!

DJPhatso · 2020-01-03T14:49:28Z

Happy New year David!

Just tried the new update, and I have to say it works quite well.

The only two little things I've noticed are related to the Beat LED:

the LED will only move forward when using the jogwheel;
when the two decks are synced, the two LED are not "linked" to the same step as they are with other DJ software.

Not sure if this is a limitation of the current Mixxx state or something that can be modified in your code.

perseo22 · 2020-01-09T13:57:41Z

Hi! Happy new year! Well, regarding the beat leads not moving forward... that's weird... Please, do you best to force Mixxx to reload everyconfig change, because it works flawlessly since the very beginning of my development-- :( and for the linked state of synced decks, I simply don't know what to do (I always thought it should be your responsibility to find the beginning of the "phrases"/8ths/etc and then try to match them, which would result in a correct beat_led synchronization, from position 0).

…

On Fri, Jan 3, 2020 at 3:49 PM DJ Phatso ***@***.***> wrote: Happy New year David! Just tried the new update, and I have to say it works quite well. The only two little things I've noticed are related to the Beat LED: - the LED will only move forward when using the jogwheel; - when the two decks are synced, the two LED are not "linked" to the same step as they are with other DJ software. Not sure if this is a limitation of the current Mixxx state or something that can be modified in your code. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#2370?email_source=notifications&email_token=AAE6MGONQWCUWKEULK6WBILQ35F7TA5CNFSM4JRIB22KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEIBI46A#issuecomment-570592888>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAE6MGNGPNYAZBFUQFP54G3Q35F7TANCNFSM4JRIB22A> .

DJPhatso · 2020-01-09T14:13:09Z

Think you miss read my comment. Forward is fine. Moving backward when using the jogwheel is the problem :-)

As for the linked state, I guess we'll have to see what the Mixxx guys have to say about this. Since this is not a common feature, maybe their code just doesn't take LED feedback into consideration.

perseo22 · 2020-01-09T14:25:15Z

Wow, I just thought I missed the point once again ;) I just can't see the day this driver becomes fully integrated out of the box with Mixxx! Thanks a lot, Phatso!!!!!!!

…

On Thu, Jan 9, 2020 at 3:13 PM DJ Phatso ***@***.***> wrote: Think you miss read my comment. Forward is fine. Moving backward when using the jogwheel is the problem :-) As for the linked state, I guess we'll have to see what the Mixxx have to say about this. Since this is not a common feature, maybe their code just doesn't take LED feedback into consideration. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#2370?email_source=notifications&email_token=AAE6MGJYGHMZBZPNYXTZMBLQ44WHNA5CNFSM4JRIB22KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEIQNXGY#issuecomment-572578715>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAE6MGLF2IXWVZOEB77MFZ3Q44WHNANCNFSM4JRIB22A> .

Holzhaus

Apart from a few code-style issues this looks good to me.

res/controllers/Hercules_DJControl_Jogvision-scripts.js

Holzhaus · 2020-01-14T16:10:19Z

By the way, does this mapping use any features that aren't in 2.2? I didn't see any, so I'd suggest you rebase this on 2.2 and target that branch instead. That will allow it to go into 2.2.4.

perseo22 · 2020-01-16T09:17:06Z

Hi!
I did the suggested changes, commited, pushed, rebased against 2.2 and pushed again.

Hope you find it correct! (my knowledge on git is pretty low... :( )

Thanks!!!!
-David.

Holzhaus · 2020-01-16T11:11:20Z

I think your rebased commits were rejected, you need to use the -f flag when pushing.

res/controllers/Hercules_DJControl_Jogvision-scripts.js

Holzhaus · 2020-01-16T11:29:03Z

I think your rebased commits were rejected, you need to use the -f flag when pushing.

...or you did you forget to remove all lines containing commits that are unrelated to this PR during rebase?

perseo22 · 2020-01-16T11:29:40Z

Hi! I just pushed another (ultra-little) change: [david@ubuntu mixxx]$ git commit -a [Controller_Hercules_DJControl_Jogvision d9dc0f3] Controller: Hercules DJControl Jogvision some more log trace at shutdown 1 file changed, 2 insertions(+) [david@ubuntu mixxx]$ git push -v -f Pushing to https://github.com/perseo22/mixxx.git Counting objects: 5, done. Delta compression using up to 4 threads. Compressing objects: 100% (5/5), done. Writing objects: 100% (5/5), 512 bytes | 0 bytes/s, done. Total 5 (delta 4), reused 0 (delta 0) POST git-receive-pack (697 bytes) remote: Resolving deltas: 100% (4/4), completed with 4 local objects. To https://github.com/perseo22/mixxx.git dff8912..d9dc0f3 Controller_Hercules_DJControl_Jogvision -> Controller_Hercules_DJControl_Jogvision updating local tracking ref 'refs/remotes/origin/Controller_Hercules_DJControl_Jogvision' My current branch: [david@ubuntu mixxx]$ git branch * Controller_Hercules_DJControl_Jogvision master And this is my .git/config: [david@ubuntu mixxx]$ cat .git/config [core] repositoryformatversion = 0 filemode = true bare = false logallrefupdates = true [remote "upstream"] url = https://github.com/mixxxdj/mixxx.git fetch = +refs/heads/*:refs/remotes/upstream/* fetch = +refs/pull/*/head:refs/remotes/upstream/pr/* [remote "origin"] url = https://github.com/perseo22/mixxx.git fetch = +refs/heads/*:refs/remotes/origin/* [branch "master"] remote = origin merge = refs/heads/master [remote] pushDefault = origin [branch "Controller_Hercules_DJControl_Jogvision"] remote = origin merge = refs/heads/Controller_Hercules_DJControl_Jogvision

…

On Thu, Jan 16, 2020 at 12:11 PM Jan Holthuis ***@***.***> wrote: I think your rebase commit were rejected, you need to use the -f flag when pushing. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#2370?email_source=notifications&email_token=AAE6MGLZ75RJFFAGBHV6MXTQ6A6FRA5CNFSM4JRIB22KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEJDWEGY#issuecomment-575103515>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAE6MGK7GJSFAOY3P25F7ZTQ6A6FRANCNFSM4JRIB22A> .

perseo22 · 2020-01-16T11:40:56Z

ok ok... I guess that I " forgot to remove all lines containing commits that are unrelated to this PR during rebase" ... You know, I'm a newbie here... What should a do now? (step-by-step guide would be great... ;)

…

On Thu, Jan 16, 2020 at 12:29 PM Jan Holthuis ***@***.***> wrote: I think your rebased commits were rejected, you need to use the -f flag when pushing. ...or you did you forget to remove all lines containing commits that are unrelated to this PR during rebase? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#2370?email_source=notifications&email_token=AAE6MGKGQW4GO3WTNN5Z4EDQ6BAH7A5CNFSM4JRIB22KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEJDXTTQ#issuecomment-575109582>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAE6MGMVLORVLCZAT5WV67LQ6BAH7ANCNFSM4JRIB22A> .

Holzhaus · 2020-01-16T11:54:16Z

# First, create a backup in case something goes wrong:
$ git branch -c my-backup-branch

# Next, start an interactive rebase
$ git rebase -i 2.2

Now, a text editor opens. Delete all lines that do not belong to your PR, so that the file only contains these lines:

pick af95a70e68 Hercules DJControl Jogvision: First release (all MIDI mapped)
pick 9261e962a0 Hercules DJControl Jogvision: reduced and cleaned the size of the Javascript code
pick 940ef3fc09 Hercules DJControl Jogvision: code cleanup and added orange color to track led
pick 15ec1efaeb CONTROLLER Hercules_DJControl_Jovision: - Fixed regression not updating the VuMeters - Fixed regression not updating the CUE/MIX buttons
pick dff8912811 Controller - Hercules DJControl Jogvision: - Minor code-style changes (use caleCase, use "double quotes" and other if/else styles)
pick d9dc0f3d86 Controller: Hercules DJControl Jogvision some more log trace at shutdown

Then save the file and close the editor.

Now, push the changes to the repository:

$ git push -f origin Controller_Hercules_DJControl_Jogvision

perseo22 · 2020-01-16T12:03:40Z

No way... :( [david@ubuntu mixxx]$ git --version git version 2.7.4 [david@ubuntu mixxx]$ git branch -c my-backup-branch error: unknown switch `c' usage: git branch [<options>] [-r | -a] [--merged | --no-merged] or: git branch [<options>] [-l] [-f] <branch-name> [<start-point>] or: git branch [<options>] [-r] (-d | -D) <branch-name>... or: git branch [<options>] (-m | -M) [<old-branch>] <new-branch> or: git branch [<options>] [-r | -a] [--points-at] ... ... [david@ubuntu mixxx]$ git rebase -i 2.2 fatal: Needed a single revision invalid upstream 2.2

…

On Thu, Jan 16, 2020 at 12:54 PM Jan Holthuis ***@***.***> wrote: # First, create a backup in case something goes wrong: $ git branch -c my-backup-branch # Next, start an interactive rebase $ git rebase -i 2.2 Now, a text editor opens. Delete all lines that do not belong to your PR, so that the file only contains these lines: pick af95a70 Hercules DJControl Jogvision: First release (all MIDI mapped) pick 9261e96 Hercules DJControl Jogvision: reduced and cleaned the size of the Javascript code pick 940ef3f Hercules DJControl Jogvision: code cleanup and added orange color to track led pick 15ec1ef CONTROLLER Hercules_DJControl_Jovision: - Fixed regression not updating the VuMeters - Fixed regression not updating the CUE/MIX buttons pick dff8912 Controller - Hercules DJControl Jogvision: - Minor code-style changes (use caleCase, use "double quotes" and other if/else styles) pick d9dc0f3 Controller: Hercules DJControl Jogvision some more log trace at shutdown Now, push the changes to the repository: $ git push origin -f Controller_Hercules_DJControl_Jogvision — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#2370?email_source=notifications&email_token=AAE6MGOGPWK6N5Z27JSCJBDQ6BDGTA5CNFSM4JRIB22KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEJDZWFI#issuecomment-575118101>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAE6MGIXXDWN6FU7E4RHTDDQ6BDGTANCNFSM4JRIB22A> .

Holzhaus · 2020-01-16T12:17:46Z

@perseo22 Ok, your git version is almost 4 years old, so the first command is slightly different:

# Create backup branch
$ git checkout -b my-backup-branch

# Switch back to original branch
$ git checkout Controller_Hercules_DJControl_Jogvision

Also, it looks like you added multiple remotes to you repository, so that git doesn't know if it should use the git branch 2.2 from the origin remote or another one.
You can check which remotes are configured with:

$ git remote -v

Assuming that you have a remote origin, you can rebase via:

$ git rebase -i origin/2.2

…ascript code

track led

- Fixed regression not updating the VuMeters - Fixed regression not updating the CUE/MIX buttons

- Minor code-style changes (use caleCase, use "double quotes" and other if/else styles)

some more log trace at shutdown

Holzhaus

Ok, this looks mostly good. It's a bit unfortunate that this changes effect settings in init() because you might have multiple controllers attached, but maybe this provides better UX for users that would otherwise wonder why the effects don't work properly. Not sure.

@Be-ing Any comments?

res/controllers/Hercules_DJControl_Jogvision-scripts.js

Holzhaus · 2020-05-10T15:21:49Z

res/controllers/Hercules_DJControl_Jogvision-scripts.js

+        engine.stopTimer(ledRotationTimer);
+        ledRotationTimer = 0;
+    }
+    //Set all LED states to off


Suggested change

//Set all LED states to off

// Set all LED states to off

and added beatNax variable declaration at the beginning

- Added jogwheel outer led movement when scratch and back/forward spin

Fixed minor code standards

Fixed an ancient bug using "beatjumpSize" instead of "beatjump_size" (shame on me...)

Modified the outer jog led (spin) leds to use a better algorithm (borrowed from the 'Pioneer-DDJ-SX-scripts.js' mapping)

- Changed jogwheel outer led movement based on playposition (much better!) - Added a user variable to set or not some effects at ini - Minor code convention corrections

perseo22 · 2020-05-13T12:22:56Z

Hi all!
Just pushed a new version, with minor code changes, and a variable to allow the user decide if initialize or not some effects at startup.

…rd) and fix leads positions, what allows backward led activation!! (didn't have that working previously)

perseo22 · 2020-05-18T16:16:51Z

Hi!
Another push!

Changed beats led algorithm to match song beats (forward and backward) and fix leads positions, what allows backward led activation!! (didn't have that working previously)

perseo22 · 2020-05-19T07:31:10Z

Happy New year David!

Just tried the new update, and I have to say it works quite well.

The only two little things I've noticed are related to the Beat LED:
* the LED will only move forward when using the jogwheel;

* when the two decks are synced, the two LED are not "linked" to the same step as they are with other DJ software.
Not sure if this is a limitation of the current Mixxx state or something that can be modified in your code.

Point number 1 (the LED will only move forward when using the jogwheel) solved in v. 1.11 ;)

v1.12 Added "alternate" beat leds mode Changed "follow" beats led algorithm with a better/more elegant version

Cleanup (deletion of unused function DJCJV.beatInactive)

Added unused button combo "shift-<MULTI FX>" to do a 'beats_translate_curpos' (align deck's beat_grid to current playposition)

Added "shift"+AIRFX to do a high pass (apart from the default low pass)

Fixed a variables being declared but never used

added better beat_active matching

perseo22 · 2020-06-02T15:29:50Z

Hi @Holzhaus , everything ok?
Is there anything else I can do?
Thanks!

Reset shift-"Loop ON", to do what Hercules wanted it to be: select FX2 for given channel. Now, the loop creation is done with "MODE"+"Loop ON" combo (here, MODE key works like "SHIFT" key ;)

Holzhaus

LGTM, thank you!

Added a "beatDetection" variable to use old school one (way better beat match, but no song position relative)

perseo22 · 2020-09-10T11:17:12Z

Hi @Holzhaus !

Could you please take a look at the latest push I did to this mapping?
I sincerely think it's much better coded (prettier, and simpler), and adds a couple of nice things!

Thanks a lot in advance!!

Holzhaus · 2020-09-10T12:12:24Z

Please open a new Pull Request, then we can do a proper review.

Holzhaus requested changes Nov 25, 2019

View reviewed changes

Holzhaus requested changes Dec 2, 2019

View reviewed changes

Holzhaus added the controller mappings label Dec 5, 2019

Holzhaus requested changes Jan 14, 2020

View reviewed changes

Holzhaus requested changes Jan 16, 2020

View reviewed changes

res/controllers/Hercules_DJControl_Jogvision-scripts.js Outdated Show resolved Hide resolved

David TV added 6 commits January 16, 2020 13:53

Hercules DJControl Jogvision: First release (all MIDI mapped)

f010f37

Hercules DJControl Jogvision: reduced and cleaned the size of the Jav…

80c2b32

…ascript code

Hercules DJControl Jogvision: code cleanup and added orange color to

f978a96

track led

CONTROLLER Hercules_DJControl_Jovision:

ea6e6b9

- Fixed regression not updating the VuMeters - Fixed regression not updating the CUE/MIX buttons

Controller - Hercules DJControl Jogvision:

78a4e25

- Minor code-style changes (use caleCase, use "double quotes" and other if/else styles)

Controller: Hercules DJControl Jogvision

e4694b4

some more log trace at shutdown

Holzhaus requested changes May 10, 2020

View reviewed changes

David TV added 6 commits May 11, 2020 09:10

Controller: Hercules DJControl Jogvision - fixed some trailing space,

e95b8dd

and added beatNax variable declaration at the beginning

Controller: Hercules DJControl Jogvision

7fdd8f1

- Added jogwheel outer led movement when scratch and back/forward spin

Controller: Hercules DJControl Jogvision

0813029

Fixed minor code standards

Controller: Herculer DJControl Jogvision

8eeb41f

Fixed an ancient bug using "beatjumpSize" instead of "beatjump_size" (shame on me...)

Controller: Herculer DJControl Jogvision

22e1ba2

Modified the outer jog led (spin) leds to use a better algorithm (borrowed from the 'Pioneer-DDJ-SX-scripts.js' mapping)

Controller: Herculer DJControl Jogvision

ec3bb1d

- Changed jogwheel outer led movement based on playposition (much better!) - Added a user variable to set or not some effects at ini - Minor code convention corrections

- Changed beats led algorithm to match song beats (forward and backwa…

acb5e70

…rd) and fix leads positions, what allows backward led activation!! (didn't have that working previously)

David TV added 6 commits May 19, 2020 15:36

Controller: Hercules DJControl Jogvision

ae08776

v1.12 Added "alternate" beat leds mode Changed "follow" beats led algorithm with a better/more elegant version

Controller: Herculer DJControl Jogvision

b9d0911

Cleanup (deletion of unused function DJCJV.beatInactive)

Controller: Hercules DJControl Jogvision

dd9a81a

Added unused button combo "shift-<MULTI FX>" to do a 'beats_translate_curpos' (align deck's beat_grid to current playposition)

Controller: Hercules DJControl Jogvision

a7afb80

Added "shift"+AIRFX to do a high pass (apart from the default low pass)

Controller: Hercules DJControl Jogvision

df030f0

Fixed a variables being declared but never used

Controller: Herculer DJControl Jogvision

fdceeed

added better beat_active matching

Controller: Hercules DJControl Jogvision

1439c9b

Reset shift-"Loop ON", to do what Hercules wanted it to be: select FX2 for given channel. Now, the loop creation is done with "MODE"+"Loop ON" combo (here, MODE key works like "SHIFT" key ;)

Holzhaus approved these changes Jun 5, 2020

View reviewed changes

Controller: Hercules DJControl Jogvision

050bf48

Added a "beatDetection" variable to use old school one (way better beat match, but no song position relative)

uklotzde modified the milestones: 2.2.4, 2.2.5, 2.2.x Jun 12, 2020

Holzhaus merged commit c768ef3 into mixxxdj:2.2 Jun 12, 2020

uklotzde modified the milestones: 2.2.5, 2.3.0 May 11, 2021

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Hercules DJControl Jogvision: First release (all MIDI mapped) #2370

Hercules DJControl Jogvision: First release (all MIDI mapped) #2370

perseo22 commented Nov 25, 2019

Holzhaus commented Nov 25, 2019

Be-ing commented Nov 26, 2019 •

edited

Loading

perseo22 commented Nov 28, 2019

perseo22 commented Dec 2, 2019

Holzhaus left a comment

Holzhaus Dec 2, 2019

DJPhatso Dec 2, 2019

perseo22 commented Dec 13, 2019

perseo22 commented Jan 3, 2020

DJPhatso commented Jan 3, 2020

perseo22 commented Jan 9, 2020 via email

DJPhatso commented Jan 9, 2020 •

edited

Loading

perseo22 commented Jan 9, 2020 via email

Holzhaus left a comment

Holzhaus commented Jan 14, 2020

perseo22 commented Jan 16, 2020

Holzhaus commented Jan 16, 2020 •

edited

Loading

Holzhaus commented Jan 16, 2020

perseo22 commented Jan 16, 2020 via email

perseo22 commented Jan 16, 2020 via email

Holzhaus commented Jan 16, 2020 •

edited

Loading

perseo22 commented Jan 16, 2020 via email

Holzhaus commented Jan 16, 2020

Holzhaus left a comment

Holzhaus May 10, 2020

perseo22 commented May 13, 2020

perseo22 commented May 18, 2020

perseo22 commented May 19, 2020 •

edited

Loading

perseo22 commented Jun 2, 2020

Holzhaus left a comment

perseo22 commented Sep 10, 2020

Holzhaus commented Sep 10, 2020

Hercules DJControl Jogvision: First release (all MIDI mapped) #2370

Hercules DJControl Jogvision: First release (all MIDI mapped) #2370

Conversation

perseo22 commented Nov 25, 2019

Holzhaus commented Nov 25, 2019

Be-ing commented Nov 26, 2019 • edited Loading

perseo22 commented Nov 28, 2019

perseo22 commented Dec 2, 2019

Holzhaus left a comment

Choose a reason for hiding this comment

Holzhaus Dec 2, 2019

Choose a reason for hiding this comment

DJPhatso Dec 2, 2019

Choose a reason for hiding this comment

perseo22 commented Dec 13, 2019

perseo22 commented Jan 3, 2020

DJPhatso commented Jan 3, 2020

perseo22 commented Jan 9, 2020 via email

DJPhatso commented Jan 9, 2020 • edited Loading

perseo22 commented Jan 9, 2020 via email

Holzhaus left a comment

Choose a reason for hiding this comment

Holzhaus commented Jan 14, 2020

perseo22 commented Jan 16, 2020

Holzhaus commented Jan 16, 2020 • edited Loading

Holzhaus commented Jan 16, 2020

perseo22 commented Jan 16, 2020 via email

perseo22 commented Jan 16, 2020 via email

Holzhaus commented Jan 16, 2020 • edited Loading

perseo22 commented Jan 16, 2020 via email

Holzhaus commented Jan 16, 2020

Holzhaus left a comment

Choose a reason for hiding this comment

Holzhaus May 10, 2020

Choose a reason for hiding this comment

perseo22 commented May 13, 2020

perseo22 commented May 18, 2020

perseo22 commented May 19, 2020 • edited Loading

perseo22 commented Jun 2, 2020

Holzhaus left a comment

Choose a reason for hiding this comment

perseo22 commented Sep 10, 2020

Holzhaus commented Sep 10, 2020

Be-ing commented Nov 26, 2019 •

edited

Loading

DJPhatso commented Jan 9, 2020 •

edited

Loading

Holzhaus commented Jan 16, 2020 •

edited

Loading

Holzhaus commented Jan 16, 2020 •

edited

Loading

perseo22 commented May 19, 2020 •

edited

Loading