@techpizza wait does vorbis really use a different polynomial? i remember digging deep and finding i
@techpizza wait does vorbis really use a different polynomial? i remember digging deep and finding it was the same
Ki do believe you that vorbis uses big-endian and the dotnet one doesnt though
Kthat sounds like a vorbis moment
Tturns out it's the same polynomial but reversed for the bit-reflected algorithm
Kok yeah thats what i thought
Ji love being in the silk.net discord because whenever im feeling smart i can come here to read about reversed polynomials for bit-reflected algorithms and deflate my ego right back where it needs to be
Llmao
Tdon't worry, i ended up porting assembly to c#
T
Lwhat the fuck
Tintel writing code in C challenge [impossible]
J"don't worry"
*proceeds to post the most worrying thing possible*
*proceeds to post the most worrying thing possible*
Pman cloning SilkX recursively (includes both original Silk.NET and terrafx.interop.windows as a submodule) on 4G is painful
Mwhy are all the native libs not in a submodule
Mi had to build silk buildtools locally and even though i wasn't compiling the entire project i had to pull in 600mb of stuff
Ldont worry
Li have 50GB of Silk.NET clones
Laveraging 7gb per clone
Mi hope those are on LFS
Lno
Lits commit STRAIGHT to the repo
Mi didn't know that was even allowed
Lwhat are they gonna do
Ltell us to stop
Ldid we ever figure out how native libs were gonna go in 3.0
Lif not, i have an idea
Pidk, silk has always been a monorepo and it not being a monorepo would involve us going to the dotnet gods every time we want to make a repo
Pso far it's just the same again because it works, what did you have in mind?
Lso
Mjust one repo for binaries and one repo for everything else
Lthe zig compiler lets us setup fully deterministic and fully reproducable builds relatively easily
Mthat way a non recursive clone doesn't rail the user
Land so, what we do is we setup a msbuild task magic thing to invoke the zig compiler and actually build the native libs
Lon the fly
Lwhen you build the native project
Pbelieve me that's not what bloats the repo
Lthe 3 copies of LLVM in our submodules bloat it WAY more
POH GOD WHAT HAVE I SIGNED UP TO
L--depth 1L--single-branchLor better yet
Ldont clone with submodules
Lits not needed for base Silk.NET
Chow do i only clone a single folder
Myou can't, it's not svn :)
Lbut what this would do is let us have our easy "clone and run" but without the overhead of commiting it to the repos
Myall should make buildtools a .net tool
Mit already basically is
Lno
M:(
