04:48:01 thuban, any progress? 11:29:12 Anyone know if there's been a mention of the MyCE forums here lately? Just checked the subdomain and it's 'disabled' atm, with a message from what looks like the host hinting there are failed payments. https://club.myce.com 11:29:42 Main site hasn't had any updates since late 2021 so wasn't sure what had occurred. 11:30:55 (it's a forum mostly dedicated to discussing blank CD/DVD/BD media and drives fwiw) 16:56:43 how is https://twitter.com/JustSolvedFmts updated? 16:58:08 Looks like IFTTT, if I were to guess, from a feed of new posts on the wiki? 16:59:18 I thought so too... I just created a page, http://fileformats.archiveteam.org/wiki/PXL-2000 and it hasn't been mentioned in the twitter feed. 17:00:56 Not that the twitter feed is why I created the page. I created the page so people who have tapes from these cameras know there may be a way to recover the video on them, even without the camera itself. 17:07:39 But it would be nice to know, so that I could make a page for the not-yet-solved .A85 files @thuban and I were talking about earlier. https://hackint.logs.kiska.pw/archiveteam-bs/20220625 17:10:32 Also kind of annoying: the IRC stuff is all happening on hackint-- but when the wiki asks you where IRC stuff takes place, you have to tell it efnet to be able to post anything. 17:11:38 Yeah, there have been issues with changing that on the fileformats wiki. 17:11:52 Not sure what the current status is, I'll poke someone about it again. 17:19:13 hahaha, why do you have two nicks? 17:22:36 Mostly because EFnet sucks and this was how I kept +o in channels there. 17:23:03 Also in case something goes wrong on my end etc. 17:24:24 oh. neat. 17:55:52 Just noticed something, I opened up the first 9 files in a hex editor and they all *end* with either (hex) 34,35, or 14 18:14:37 In fact, *all* files seem to end in either 14,15, 34, 35, 88, 89, or 00. So that's got to be some kind of magic number, right? 18:17:08 o wait ignore that 00. think that was an endianness error. 18:21:54 https://pastebin.com/NZ5vDnXs 18:24:35 So it seems that there are 6 possibilities. Here they are in binary: https://pastebin.com/XdyK0JEq 18:36:36 cogburnd02: if they are amr-wb+ files, then according to the spec (https://www.3gpp.org/ftp/Specs/archive/26_series/26.290/) those should be gain corrections--there are no footers, length data is in the frame headers 18:38:48 i haven't tried the vcproj converter / pored over a binary dump to see whether it makes sense as audio data yet (unfortunately there appear to be no magic numbers) & can't today, sorry 18:50:58 oh that's cool. no rush. Just thought it might be neat to figure out a file format. 18:52:22 wait, according to the spec, shouldn't they also have a magic number at the beginning of the file, too? 19:30:27 cogburnd02: No magic number in the latest version at https://www.3gpp.org/ftp/Specs/archive/26_series/26.290/26290-h00.zip at least. Sections 8.2 and 8.3 are the relevant one. The leading bit is a zero, as is the 11th, and that's it. But your file 0004 violates the former... 19:54:14 they're definitely not 3gp files, because those _would_ have some magic numbers 19:55:35 Yeah, and ffmpeg would certainly recognise them (even if it didn't know what to do with the contents). 19:56:32 MediaInfo doesn't recognise them either, by the way. 20:03:21 Usernam edited List of websites excluded from the Wayback Machine (+26): https://wiki.archiveteam.org/?diff=48699&oldid=48697 20:04:21 KevinArchivesThings edited WikiTeam (+165): https://wiki.archiveteam.org/?diff=48700&oldid=48481 20:20:07 rewby: while you're probably still up, can we please have a target for #glencohno ? 20:20:18 i think a single one is enough, perhaps on one of the existing machines? 20:30:03 rewby: HCross: in case one of you is online, for glencoe (see above two messages) we'd have 20:30:11 archiveteam_glencoe 20:30:17 glencoe_ 20:30:26 Archive Team Glencoe: 20:30:42 i'm hoping to have a project online today, deadline is the 30th 20:57:50 i know i said i wasn't gonna pore over binary dumps today, but i don't think the errant leading bit JAA mentioned can be explained by it being audio data that got chopped at some arbitrary byte, either: bytes 5-9 are "f9 00 00 00 00" in every single one of those files, and unless i've fucked up my grepping (possible) that's the only location that pattern appears at in any of 20:57:51 them 21:00:18 Interesting. 21:03:05 furthermore, the first byte in a 'raw' amr-wb+ file should supposedly be the frame type, but while only frame types 0-47 are valid, all but five files have a value of 50 or greater (and the different frame types indicate different stereo and bitrate settings among other things, so it would be real weird if they varied between files from a single recording at all) 21:05:50 i'm thinking that either 'raw' files actually have some kind of header structure on top of the "transport interface format" spec (reading the decoder code should elucidate this), or these are another filetype entirely... 21:22:05 (meanwhile, i tried running the decoder binary on a windows vm, just in case, but i get exactly the same output as i did through wine) 21:36:28 https://server8.kiska.pw/uploads/8b01d1afcac0cd82/image.png first time I have seen this 21:36:41 http://v4.cache.googlevideo.com/videoplayback 21:54:25 flashfire42: https://wiki.archiveteam.org/index.php/List_of_websites_excluded_from_the_Wayback_Machine 21:55:52 Sir I started that page 21:56:56 But thats a different error to the one I get for exclusion 21:58:21 I didn't know, my apologies. 21:59:22 I've seen this before, but not much. May be time for another list. Also, #internetarchive 22:00:34 (For searchability, this is the 'This URL is in our block list and cannot be captured. Please email us at "info⊙ao" if you would like to discuss this more.' error.) 23:25:40 running a local crawl now of all bugz.org.nz 23:25:46 including PDFs, images, etc. 23:25:59 (website is a pain with POSTs, all over the place) 23:26:03 JAA: FYI ^ 23:31:43 Lovely :-) 23:35:07 also here is a fun detail 23:35:45 the PDF URLs can in no way be tight to the HTML page without looking at the cookie 23:36:03 tied* sorry 23:36:08 (getting tired) 23:36:40 i'm keeping this at 1 WARC per item, and will upload like that as well. it's not a ton of items, and it make it a lot easier if some researchers want to match a PDF to a web page 23:36:42 Wonderful... But it sounds like it should be possible to index it at least. 23:37:01 yeah definitely indexable. especially when doing 1 WARC per item 23:37:05 Yeah 23:37:10 Then it's easy. :-)