Standalone ALAC package

[stephen]

Hi, I'm interested in using the ALAC encoder/decoder bindings for a project I'm working on for AirTunes server support. (https://github.com/stephen/nodetunes/).

Would you be able to put your ALAC bindings into a separate npm module available for use?

[lperrin]

I'm travelling right now, but it should be easy to do. I'll see if I can
get it working in the plane.

2014-04-27 16:59 GMT-07:00 Stephen Wan [email protected]:

Hi, I'm interested in using the ALAC encoder/decoder bindings for a
project I'm working on for AirTunes server support. (
https://github.com/stephen/nodetunes/).

Would you be able to put your ALAC bindings into a separate npm module
available for use?

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/22
.

[stephen]

Thanks! Let me know if I can help. (Though unfortunately, I don't have much experience with node-gyp)

[dinomite]

@lperrin Have you had a chance to work on this? If not, any tips on where to start? I know nothing about Node packages, but would like the support for @stephen's project airsonos

[lperrin]

Hey sorry, my startup is going through Y Combinator and I don't have much
time for anything else.

I did start to work on it though. If you just need ALAC encryption, it
should be relatively easy. ALAC decryption seems a bit harder.

2014-07-09 10:31 GMT-07:00 Drew Stephens [email protected]:

@lperrin https://github.com/lperrin Have you had a chance to work on
this? If not, any tips on where to start? I know nothing about Node
packages, but would like the support for @stephen
https://github.com/stephen's project airsonos

—
Reply to this email directly or view it on GitHub
#22 (comment)
.

[ghost]

Hi All!

I am posting a new issue into this thread, so that all of you guys will receive a notification about that, hopefully.

I am interested in building an airplay-hub with a GUI for Raspberry Pi. I found this project, which uses your projects "node_airtunes" and "nodetunes" implicitly.

https://github.com/noelhibbard/node-airplayhub

This already works quite well. I detected 2 problems on the node_airtunes side:

1st problem: On songs with a very wide/intensive sound spectrum I get some debug notices of this kind: "compressed frame too big: 13340 vs. 11280". Usually this is not a problem, the playback continues. On some specific songs these messages are printed very frequently, and after a short period the process crashes:

compressed frame too big: 12020 vs. 11280
compressed frame too big: 11651 vs. 11280
compressed frame too big: 11651 vs. 11280
compressed frame too big: 11651 vs. 11280
compressed frame too big: 11374 vs. 11280
compressed frame too big: 11374 vs. 11280
compressed frame too big: 11374 vs. 11280
compressed frame too big: 11562 vs. 11280
compressed frame too big: 11562 vs. 11280
compressed frame too big: 11562 vs. 11280
compressed frame too big: 12265 vs. 11280
compressed frame too big: 12265 vs. 11280
compressed frame too big: 12265 vs. 11280
compressed frame too big: 13930 vs. 11280
compressed frame too big: 13930 vs. 11280
compressed frame too big: 13930 vs. 11280
compressed frame too big: 11441 vs. 11280
compressed frame too big: 11441 vs. 11280
compressed frame too big: 11441 vs. 11280
compressed frame too big: 11508 vs. 11280
compressed frame too big: 11508 vs. 11280
compressed frame too big: 11508 vs. 11280
compressed frame too big: 11348 vs. 11280
compressed frame too big: 11348 vs. 11280
compressed frame too big: 11348 vs. 11280
compressed frame too big: 13953 vs. 11280
compressed frame too big: 13953 vs. 11280
compressed frame too big: 13953 vs. 11280
compressed frame too big: 12090 vs. 11280
compressed frame too big: 12090 vs. 11280
compressed frame too big: 12090 vs. 11280
compressed frame too big: 12102 vs. 11280
compressed frame too big: 12102 vs. 11280
compressed frame too big: 12102 vs. 11280
compressed frame too big: 15387 vs. 11280
compressed frame too big: 15387 vs. 11280
./start_airplay_hub: line 1: 1100 Segmentation fault node-airplayhub --config=/opt/node-airplayhub/config.json

This error can be reproduced very constantly with following song:
Awolnation (Knights of Shame) - 14:58 - downloaded via Apple Music subscription
At 07:40 of this song, the process begins to print the messages.
At 11:15 the process crashes.

I figured out that the "compressed frame too big" messages are thrown from ALACEncoder.cpp. Is there a newer version available or is there any way to avoid this crash?

2nd problem: When Music is stopped for some while I cannot restart playback. This problem seems to be on the node_airtunes side, since the playback on the iOS device works (song is "running" on iPhone, so nodetunes seems to be functional), but there is no output on any target device. Is there any way to debug / get more verbose output?

Thank you!