-
Notifications
You must be signed in to change notification settings - Fork 56
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
might off-topic: Are all the tracks share the same ogg header? #37
Comments
Not off topic. This notion may have started as some sort of geeky joke but
|
hi wxl. I'm still not sure how this trk_.h was generated. I think ogg123 decode the stream that comes from this kernel module as one ogg file. So are these tracks was encoded into one ogg file? If it is this case, how you can locate the split point and split it into trk_.h files? Thanks your time :-) |
well, honestly, i have no clue what's going on. i tried "playing" /bin/bash with ogg123 and naturally it doesn't grok it because it doesn't have the appropriate header. a hex editor provided no insight on trk_data.h. similarly, trk_.c just includes the headers as data (a struct of netcat_track netcat_cpi_trk1). netcat.h includes the netcat_track struct. in netcat.h, an array of tracks is created. beyond that, my feeble understanding of C provides no further insight on how netcat.c deals with this information, but a quick perusual doesn't make it clear that some sort of conversion is done. in any case, that's the code that does the magic. it's just a matter of finding it ;) |
The trk*.h files do not share a single header. Each on is derived from a separate ogg file. Ogg123 (and vlc, mplayer, etc) handle multiple consecutive separate files with their own header. |
hi, I plan to write a simple program that automatically generates netcat module for any existing music. your kernel module seems deal with all the tracks like one big ogg file. Is it true that tracks was originally encoded as one ogg file, and you split it into six pieces that actually share the same ogg header? If it is true , I wonder how you locate boundary between tracks in the encoded file.
The text was updated successfully, but these errors were encountered: