xwax

I used to do this but it hides the toolbar and the battery applet too,
this led to my computer running out of battery without me realising
and hibernating mid mix. Oops, haha! :P

Louis

On 21 September 2012 09:49, ewan colsell <ewanuno@...> wrote:
> I use devilspie to maximize the xwax-devel window to fullscreen when it
> loads. That way the only way to close it is to use alt-tab to switch to the
> terminal window where I started xwax and press ctrl-c,  I never manged to do
> this by accident.
>
> Ewan.
>
> On Sep 20, 2012 9:39 PM, "Louis Adam" <louispopinjay@...> wrote:
>>
>> Hello!
>>
>> I was playing around with Mixxx the other day and they had a simple
>> feature that I thought might be good for xwax: if you attempt to close
>> the window while decks are playing it asks if you are sure you want to
>> do that. I've not yet accidentally closed xwax mid mix (touch wood)
>> but something like this could save someone some future embarrassment.
>> Just a little idea!
>>
>> Regards,
>> Louis
>>
>>
>> ------------------------------------------------------------------------------
>> Everyone hates slow websites. So do we.
>> Make your web apps faster with AppDynamics
>> Download AppDynamics Lite for free today:
>> http://ad.doubleclick.net/clk;258768047;13503038;j?
>> http://info.appdynamics.com/FreeJavaPerformanceDownload.html
>>
>> --
>> xwax-devel mailing list
>>
>> Please don't start a new thread by replying and changing the subject.
>> Instead, send a new mail to xwax-devel@...

On Fri, 21 Sep 2012, Louis Adam wrote:

> I used to do this but it hides the toolbar and the battery applet too,
> this led to my computer running out of battery without me realising
> and hibernating mid mix. Oops, haha! :P

Yeah, I'm a full-screen person too. Just remember to plug in.

Coding it would be tricky. xwax isn't really a GUI application, only an 
SDL application much like a game. So it can't open extra windows etc.

You could tweak your window manager to remove the close button on xwax 
windows, then the only way to kill it would be from the shell. That is 
easy to do in fvwm, I don't know about the others.

> On 21 September 2012 09:49, ewan colsell <ewanuno@...> wrote:
> > I use devilspie to maximize the xwax-devel window to fullscreen when it
> > loads. That way the only way to close it is to use alt-tab to switch to the
> > terminal window where I started xwax and press ctrl-c,  I never manged to do
> > this by accident.
> >
> > Ewan.

-- 
Mark

Never mind then, it can just be an idea for anyone planning to make a
new frontend for xwax in the future.

Louis

On 21 September 2012 12:06, Mark Hills <mark@...> wrote:
> On Fri, 21 Sep 2012, Louis Adam wrote:
>
>> I used to do this but it hides the toolbar and the battery applet too,
>> this led to my computer running out of battery without me realising
>> and hibernating mid mix. Oops, haha! :P
>
> Yeah, I'm a full-screen person too. Just remember to plug in.
>
> Coding it would be tricky. xwax isn't really a GUI application, only an
> SDL application much like a game. So it can't open extra windows etc.
>
> You could tweak your window manager to remove the close button on xwax
> windows, then the only way to kill it would be from the shell. That is
> easy to do in fvwm, I don't know about the others.
>
>> On 21 September 2012 09:49, ewan colsell <ewanuno@...> wrote:
>> > I use devilspie to maximize the xwax-devel window to fullscreen when it
>> > loads. That way the only way to close it is to use alt-tab to switch to the
>> > terminal window where I started xwax and press ctrl-c,  I never manged to do
>> > this by accident.
>> >
>> > Ewan.
>
> --
> Mark

On Mon, 17 Sep 2012, Jakub Lauda wrote:

> as a newbie I am running in some issues trying to get xwax running on
> MacBook Pro 8.1, with ubuntu 12.04 and stanton scratchamp first version.
> 
[...]
> in kern.log I get the message:
> Sep 17 01:03:56 vitabook kernel: [  936.552675] hub 1-1.3:1.0: USB hub found
> Sep 17 01:03:56 vitabook kernel: [  936.553516] hub 1-1.3:1.0: 4 ports
> detected
> Sep 17 01:03:56 vitabook kernel: [  936.855625] usb 1-1.3.1: new full-speed
> USB device number 10 using ehci_hcd
> Sep 17 01:03:57 vitabook kernel: [  937.283140] usb 1-1.3.2: new full-speed
> USB device number 11 using ehci_hcd
> Sep 17 01:05:14 vitabook kernel: [ 1014.843844] cannot submit datapipe for
> urb 0, error -28: not enough bandwidth
> 
> Probably some issue with the snd_usb_audio driver. But googling around
> didn't get me any further.

If I recall, the ScratchAmp v1 declares itself as a USB 1 device, but to 
stream 2x 44100Hz stereo audio channels requires just slightly more than 
the available bandwidth. Thus it made a small abuse of the standard in 
order to actually do the task in hand. Maybe ehci_hcd and other Linux USB 
drivers have tightened up to this.

This feels familiar, like it has been asked before. Perhaps search the 
archives of this list, or alsa-devel.

Does it work with only a single deck?

It may be worth taking this to the alsa-devel mailing list. Technical 
correctness is very welcome, but then the device used to work on Linux -- 
this is definitely a regression. The ScratchAmp is definitely capable of 
achieving the required bandwidth, maybe some kind of workaround is needed.

Unfortuntely, I no longer have my ScratchAmp v1 to test.

It would be good to see this working again. It may be an old device, but 
it works very well with the right kernel.

-- 
Mark

Hi Mark. 
Thanks for the feedback.
With single deck everything works ok.
I will try to search the archives as suggested.

Jakub

19. 9. 2012 v 0:48, Mark Hills <mark@...>:

> On Mon, 17 Sep 2012, Jakub Lauda wrote:
> 
>> as a newbie I am running in some issues trying to get xwax running on
>> MacBook Pro 8.1, with ubuntu 12.04 and stanton scratchamp first version.
>> 
> [...]
>> in kern.log I get the message:
>> Sep 17 01:03:56 vitabook kernel: [  936.552675] hub 1-1.3:1.0: USB hub found
>> Sep 17 01:03:56 vitabook kernel: [  936.553516] hub 1-1.3:1.0: 4 ports
>> detected
>> Sep 17 01:03:56 vitabook kernel: [  936.855625] usb 1-1.3.1: new full-speed
>> USB device number 10 using ehci_hcd
>> Sep 17 01:03:57 vitabook kernel: [  937.283140] usb 1-1.3.2: new full-speed
>> USB device number 11 using ehci_hcd
>> Sep 17 01:05:14 vitabook kernel: [ 1014.843844] cannot submit datapipe for
>> urb 0, error -28: not enough bandwidth
>> 
>> Probably some issue with the snd_usb_audio driver. But googling around
>> didn't get me any further.
> 
> If I recall, the ScratchAmp v1 declares itself as a USB 1 device, but to 
> stream 2x 44100Hz stereo audio channels requires just slightly more than 
> the available bandwidth. Thus it made a small abuse of the standard in 
> order to actually do the task in hand. Maybe ehci_hcd and other Linux USB 
> drivers have tightened up to this.
> 
> This feels familiar, like it has been asked before. Perhaps search the 
> archives of this list, or alsa-devel.
> 
> Does it work with only a single deck?
> 
> It may be worth taking this to the alsa-devel mailing list. Technical 
> correctness is very welcome, but then the device used to work on Linux -- 
> this is definitely a regression. The ScratchAmp is definitely capable of 
> achieving the required bandwidth, maybe some kind of workaround is needed.
> 
> Unfortuntely, I no longer have my ScratchAmp v1 to test.
> 
> It would be good to see this working again. It may be an old device, but 
> it works very well with the right kernel.
> 
> -- 
> Mark

On Sat, 15 Sep 2012, Joonas Henriksson wrote:

> Hi,
> 
> I'm working on getting traktor scratch mk2 vinyls to work with xwax.
> So far I've got it playing in correct speed by switching the
> resolution to 2400hz from 2000hz on old traktor disks, but the
> playback sounds "jittery" and i'm not getting clean circles in the
> timecode scope.
> 
> Here's a picture of the odd-looking tracking scope:
> http://postimage.org/image/5lt32zlwd/
> 
> I don't fully understand how timecoded vinyls are working, and have
> run out of ideas, so any help would be appreciated :)

You're right, it s a completely different timecode design.

If you can get a stable signal, you might see the pattern emerge. If you 
have a CD, you could test with that instead.

But in general I've voiced my scepticism that the timecode could be 
superior to the others such as Serato, and is also likely to be harder to 
implement and less robust. I'm open to suggestions -- but this is why I 
haven't done anything more than taken a brief look at the mk2 timecode 
some time ago.

-- 
Mark

On Wed, 5 Sep 2012 18:24:52 -0500, Brian Jackson wrote:

> Here are some local changes I've been playing with for handling my 
> music
> collection.
>
> I'm sure something would have to be tweaked a little before anything 
> like
> this
> is committed to git, but here's what I'm working with presently to 
> help
> with big
> playlists:
>
> First, a little alteration to the scan script in the xwax 
> distribution:
>
> diff --git a/scan b/scan
> index 976948a..3e39bd5 100755
> --- a/scan
> +++ b/scan
> @@ -12,6 +12,10 @@
>
> PATHNAME="$1"
>
> +if [ `echo "$PATHNAME" | grep -q '.xwaxpls' ; echo $?` -eq 0 ] ; 
> then
> + cat "$PATHNAME"
> + exit
> +fi
> +
> if [ -d "$PATHNAME" ]; then
> find -L "$PATHNAME" -type f |
> grep -iE '.(ogg|oga|aac|cdaudio|mp3|flac|wav|aif|aiff|m4a|wma)$'
>
> Then the actual script that generates my "xwaxpls" files. It requires 
> a
> utility
> called mediainfo. It was in the Debian/Ubuntu repo's. It also assumes
> your
> music is properly tagged.
>
> #!/bin/bash
>
> # generate an "xwax" playlist
>
> #BPM_UTIL="/stuff/src/bpm-tools/bpm"
> #BPM_MIN="165"
> #BPM_MAX="180"
>
> if [ ! $# -eq 2 ] ; then
> echo "$0 "
> fi
>
> OUTFILE=$1
> SCANPATH=$2
>
> oIFS=$IFS
> IFS="
> "
>
> for file in `find ${SCANPATH} -type f | grep -iE '.(mp3|m4a|flac)$'` 
> ; do
> # tt[t]n
>
> IFS=$oIFS
>
> echo "analyzing ${file}"
>
> artist=`mediainfo "${file}"| grep '^Performer[[:space:]]*:' | cut -f2
> -d: | sed 's/^[[:space:]]//'`
> title=`mediainfo "${file}"| grep '^Track name[[:space:]]*:' | cut -f2
> -d: | sed 's/^[[:space:]]//'`
> #bpm=`sox "${file}" -t raw -r 44100 -e float -c 1 - | ${BPM_UTIL} -f
> '%.0f' -m ${BPM_MIN} -x ${BPM_MAX}`
> # I have added the BPM tag to all my music using a little script I
> # wrote that uses bpm-tools
> # An alternate way would be uncomment the line above and uncomment 
> the
> # BPM* vars at the beginning of this script
> bpm=`mediainfo "${file}"| grep '^BPM[[:space:]]*:' | cut -f2 -d: | 
> sed
> 's/^[[:space:]]//'`
>
> echo -e "${file}t${artist}t${title}t${bpm}"
> echo -e "${file}t${artist}t${title}t${bpm}" >> $OUTFILE
> done
>
> I'd be interested in hearing how others are dealing with their music.
> Specifically with very large music collections. Are you using some 
> other
> util
> to maintain your library and then somehow dumping that to an xwax
> friendly
> format? Something else?
>
> I'm also tying to think of ways to make the crate columns a little 
> more
> dynamic.
> Polyrhythmic and I were talking in IRC about maybe a header row from 
> the
> scan script
> being able to setup the fields.
>
> p.s. Sorry, the above is rough and c&p'ed from a ssh session back 
> home.
> I'll try to have future posts a little more neat and orderly, but I'm 
> at
> work and
> bored.
>
> --Brian (Iggy) Jackson


I like the concept, I haven't tried it yet, but I'm curious to know, 
where did u get that bpm tool? What formats does it work on?

---
Marc DM

On 09/05/2012 11:40 PM, Marc D. Murray wrote:
> 
> I like the concept, I haven't tried it yet, but I'm curious to know, 
> where did u get that bpm tool? What formats does it work on?

It might be this one:
http://www.pogo.org.uk/~mark/bpm-tools/

-- 
John Brier, RHCA, RHCVA, RHCX
Quality Assurance Engineer - NA
gpg: 1024D/251D9FF9 6F7B 242A 9375 F4CC BC6D  F453 60D8 35FF 251D 9FF9

http://opensource.com - Where Open Source Multiplies

On Wed, 5 Sep 2012, Marc D. Murray wrote:

> On Wed, 5 Sep 2012 18:24:52 -0500, Brian Jackson wrote:
> 
> > Here are some local changes I've been playing with for handling my 
> > music collection.
[...]
> I like the concept, I haven't tried it yet, but I'm curious to know, 
> where did u get that bpm tool? What formats does it work on?

Probably from here:

  http://www.pogo.org.uk/~mark/bpm-tools/

Feedback welcome :) If you do try these tools I'd be pleased to hear 
whether they are working for you.

Thanks

-- 
Mark

On Wed, 5 Sep 2012, Brian Jackson wrote:

> Here are some local changes I've been playing with for handling my music 
> collection.
> 
> I'm sure something would have to be tweaked a little before anything 
> like this is committed to git, but here's what I'm working with 
> presently to help with big playlists:
> 
> 
> First, a little alteration to the scan script in the xwax distribution:
> 
> diff --git a/scan b/scan
> index 976948a..3e39bd5 100755
> --- a/scan
> +++ b/scan
> @@ -12,6 +12,10 @@
>  
>  PATHNAME="$1"
>  
> +if [ `echo "$PATHNAME" | grep -q '.xwaxpls' ; echo $?` -eq 0 ] ; then
> +       cat "$PATHNAME"
> +       exit      
> +fi
> +
>  if [ -d "$PATHNAME" ]; then
>         find -L "$PATHNAME" -type f |
>                 grep -iE '\.(ogg|oga|aac|cdaudio|mp3|flac|wav|aif|aiff|m4a|wma)$'
> 
> 
> 
> Then the actual script that generates my "xwaxpls" files. It requires a 
> utility called mediainfo. It was in the Debian/Ubuntu repo's. It also 
> assumes your music is properly tagged.
> 
> 
> #!/bin/bash
> 
> # generate an "xwax" playlist
> 
> #BPM_UTIL="/stuff/src/bpm-tools/bpm"
> #BPM_MIN="165"
> #BPM_MAX="180"
> 
> if [ ! $# -eq 2 ] ; then
>         echo "$0 <output file> <path to scan>"
> fi
> 
> OUTFILE=$1
> SCANPATH=$2
> 
> oIFS=$IFS
> IFS="
> "
> 
> for file in `find ${SCANPATH} -type f | grep -iE '\.(mp3|m4a|flac)$'` ; do
>         #   <pathname>\t<artist>\t<title>[\t<bpm>]\n
> 
>         IFS=$oIFS
> 
>         echo "analyzing ${file}"
> 
>         artist=`mediainfo "${file}"| grep '^Performer[[:space:]]*:' | cut -f2 -d: | sed 's/^[[:space:]]//'`
>         title=`mediainfo "${file}"| grep '^Track name[[:space:]]*:' | cut -f2 -d: | sed 's/^[[:space:]]//'`
>         #bpm=`sox "${file}" -t raw -r 44100 -e float -c 1 - | ${BPM_UTIL} -f '%.0f' -m ${BPM_MIN} -x ${BPM_MAX}`
>         # I have added the BPM tag to all my music using a little script I 
>         # wrote that uses bpm-tools 
>         # An alternate way would be uncomment the line above and uncomment the 
>         # BPM* vars at the beginning of this script
>         bpm=`mediainfo "${file}"| grep '^BPM[[:space:]]*:' | cut -f2 -d: | sed 's/^[[:space:]]//'`
> 
>         echo -e "${file}\t${artist}\t${title}\t${bpm}"
>         echo -e "${file}\t${artist}\t${title}\t${bpm}" >> $OUTFILE
> done
> 
> 
> 
> 
> I'd be interested in hearing how others are dealing with their music. 
> Specifically with very large music collections. Are you using some other 
> util to maintain your library and then somehow dumping that to an xwax 
> friendly format? Something else?

I have something pretty similar; my xwax-scan script checks for a cache 
file, and if there isn't one it calls the comprehensive scan script, which 
is like yours above.

Thanks for sharing this. This is kinda what I intended for people to do in 
terms of customisation. I don't think there's really one true way to do 
this that would suit everybody.
 
> I'm also tying to think of ways to make the crate columns a little more 
> dynamic. Polyrhythmic and I were talking in IRC about maybe a header row 
> from the scan script being able to setup the fields.

Yes, nice to try this. Shouldn't be too hard (you possibly don't need the 
headers either)

It might be that extra fields are only really useful if they have a 
special meaning, like BPM is used for ordering, or for searching, pathname 
to album art etc..

Thanks for this. I'd be interested to hear from others too.

-- 
Mark

On Thursday, September 06, 2012 04:35:33 PM Mark Hills wrote:
> On Wed, 5 Sep 2012, Marc D. Murray wrote:
> > On Wed, 5 Sep 2012 18:24:52 -0500, Brian Jackson wrote:
> > > Here are some local changes I've been playing with for handling my
> > > music collection.
> 
> [...]
> 
> > I like the concept, I haven't tried it yet, but I'm curious to know,
> > where did u get that bpm tool? What formats does it work on?
> 
> Probably from here:
> 
>   http://www.pogo.org.uk/~mark/bpm-tools/
> 
> Feedback welcome :) If you do try these tools I'd be pleased to hear
> whether they are working for you.

Yes, those are the ones.

I ran against about 1000 Drum & Bass tracks and it got them all right. I set a 
min of 160 and a max of 185 iirc. Before setting the min and max it obviously 
didn't do very well since the default max is 146bpm. I haven't tried any of my 
other music yet. I'm trying to work out my workflow a little better with a 
smaller subset of my music.



> 
> Thanks