theplaydeck.com - chrome experiment

DJ Life & Community General Discussion
1

theplaydeck.com - chrome experiment

Hello

I am a software developer and a hobbyist Dj (just started few month ago).

As an experiment i have developed “Dj Player” in browser, i know there are some other better solutions :slight_smile: but it was created just for fun.

I will be more than happy to hear from you any kind of suggestions, ideas, improvements, critics… if you’ll have any

2

Thats pretty cool actually. I hope it sticks around.

3

Hey this is really well done! I had expected this page to use a boatload of CPU power but my trusty old MB 2013 handled it without any problems, I did one small mix and everything worked really well! I like the keyboard shortcuts and the interface is actually quite intuitive, keep up the great work this was a joy to use!

Edit:
Found one bug on Mac OS 10.13.15 FF 60.0.2 the loading of tracks only works the initial first time and after that the button does not trigger a reaction.

4

I’d love to see the source code.

5

Yhea me too

6

Just one question, why is it called a chrome experiment? It works just fine on Firefox?

7

Works well! The loop row should be made a little bigger comparing to other transport buttons. Also, performing a double click on mixer EQ knobs should reset value to center position.

8

I am really glad that you liked it and huge thanks to everyone who responded.

:slight_smile: idea was to submit it to Chrome Experiments - Experiments with Google, i have’t tested it fully yet in a different browsers.

Definitely will add eq reset on double click in next update, thanks!

Also what i really wanted to add is the ability to play music from cloud, via soundcloud or beatport or some other service, but can’t get their API keys yet :disappointed:

9

Yes it’s related to waveform rendering engine, CPU load jumps when waveform is zoomed and it’s scrolling.
I have some ideas how to optimize it, but do not want to waste time on it yet.

For now i just want to collect feedback if it’s useful for anyone and if it is, in which direction should i continue development.

10

I had some fun with it again today and just a couple of things:

  • The looping system slightly ruins the phase of the track which throws it of beat
  • Once a track is finished, on scrolling back the main waveform does not work (only the mini version)
  • Zooming the main waveform does not work for me unless it is the first track I load into the deck
  • Loading a new track does not work in Firefox (only empty decks can be loaded)

Any plans to open source this?