zooey
Members-
Posts
1,837 -
Joined
-
Last visited
-
Days Won
15
Everything posted by zooey
-
Another huge pile 'o stuff, not specifically guitar... https://www.kvraudio.com/forum/viewtopic.php?f=43&t=494923
-
Are you sure that's the right model? Site says normal price is $76.47, and if I remember right, there are some similar stands a Helix doesn't quite fit in.
-
https://www.thegearpage.net/board/index.php?threads/2017-black-friday-software-ampsim-sales.1886552/
-
Very much yes! Take thee to yon IdeaScale henceforth and forthwith!
-
Or the other way round ;)
-
Excellent news! And what I get for posting about this update before DOING this update :)
-
And another Dr Bonkers Polytone, 12" this time. Demo clips are, uh, awkward, but I like the stuff of his I have a lot, and they certainly aren't me-too cabs you can get anywhere. Don't have either of those though. Yet, maybe.
-
Cab, not the amp, but there's this from Dr Bonkers, on sale now too :)
-
Input pad? There's no level metering so it's hard to know if you're clipping something, but that seems like the most likely culprit.
-
With the proviso that I haven't had a chance to do and explore this upgrade yet myself, I suspect a couple of cautions are in order. Full backup is essentially an extended version of the Bundle backup from previous version, which is great, but it looks like it has the same caveats... As has been discovered, and makes logical sense, restoring from a full backup after a firmware upgrade overwrites any new factory setlists or presets that came with the upgrade. For that reason, it would be great if Line 6 could provide the factory setlists as separate downloads. A corrupted preset can prevent you from being able to restore. In fact one of the biggest new features of 2.30 IMO is that it appears to detect at least some corruption when you do the export, so you know then to isolate which one and deal with it, instead of finding out when you really need to restore that your backup is unusable. I have no idea if it's actually doing any kind of on-the-fly inspection or testing, but my guess would be no, it simply tries to export, and goes off the rails if it hits something sufficiently unexpected, like software does. It's still great that it fails on export in some cases, but there may be other kinds of corruption that won't be detected until you import. For all those reasons, with prior versions I think many people did setlist and preset backups in addition to bundles. That's quite likely still wise. I don't mean to knock Line 6 or this upgrade, by all reports it seems awesome, can't wait to get there myself :)
-
I wonder what happens of you do a full reset and don't import a full backup. Is is possible to restore everything but the factory setlists from a backup? I'd say that's that the ideal pattern after an upgrade.
-
45,071 posts and counting, that's got to be the mother of huge threads that there.
-
Ok I lost interest when I saw where the decimal point goes on that price. To quote someone famous, "It can't happen here".
-
He has a point though.
-
People (including me) could tell you how they feel about the ones they've tried, but honestly, if you're happy, I don't think anything else matters.
-
I fully expect any tools like this to be obsoleted by Line 6 at some point, which would only be a good thing :)
-
Interesting strategy about the naming. Not sure how Windows file sorting compares to what I'd see from code. Might be worth investigating to lose the numbering biz. I was thinking v1.1 of my thing might well have UI to reorder, renumber and rename a set of IRs, then adjust the presets once that was settled, but you could have longer names without the numbering. At least some of the weirdness when IR metadata doesn't match a renumbered file name should go away too. It'd be great if we could keep the names like they were the original distribution, but they're often to long anyway, and quite possibly not unique across makers. Also, I like being able to control IR order as it is in Helix, like to keep a brand's stuff together. Will think on it, thanks for the ideas.
-
BIG THANKS to Line 6 for using text for the .hlx format
zooey replied to mdmayfield's topic in Helix
Cool, thanks for the info. Saw your other reply too, answered there. -
Sounds very cool. So you don't number your IRs, you just use their natural name sort order, and let your script adjust your presets for changes? Does it regen the preset file JSON from scratch, or do text replacements to update for new IR locations? Are you looking for IR usage by IR blocks only, or also in snapshots and footswitches? What language is it written in? Regardless if any of that, very cool.
-
BIG THANKS to Line 6 for using text for the .hlx format
zooey replied to mdmayfield's topic in Helix
I would think there's very little risk of incompatibility with Helix or the Helix app if all you're doing is simple text replacements. But suppose you're making more structural changes, where the best option is to deserialize the JSON data, mess with it as data (not text), and serialize it again. Has anyone tried that? The JSON format generated by the Helix app isn't what I would describe as standard, particularly its whitespace handling. The tools I'm using for my analysis app can generate JSON from a complex data structure like a preset with a simple function call, but it won't be exactly like what Helix itself does. So far, I've been concentrating on other aspects of my app that don't involve modifying presets, so I haven't tried seeing if Helix accepts that or not. Of course it's possible to write a custom serializer, but all other things being equal, I'd rather spend the time on more interesting functionality. Has anyone been down a similar road far enough to know how tolerant Helix is of whitespace differences? -
BIG THANKS to Line 6 for using text for the .hlx format
zooey replied to mdmayfield's topic in Helix
Agree that making the format human readable was a great decision. Case in point, if you haven't seen this... http://line6.com/support/topic/30287-a-few-questions-about-your-helix-backup-strategy-and-your-use-of-irs/?do=findComment&comment=233479 -
Thanks Will. I answered HO first because some of those answers apply to your less specific situation too; see that novel too. Re keeping track of IR order without manually numbering them, unfortunately, until the app can read and manipulate bundle files I can't do that. Another thing it won't do in version 1, but I hope is closer on the horizon, is to provide an interface to reorder (read - rename) IRs, delete or replace unused ones, etc, and automatically update a set of preset files to point to the new locations. But I want to ship, for once, instead of waiting to build the perfect thing. Ultimately, the real Line 6 Helix app should store IR hashes (kind of a digital fingerprint of the file contents) in each preset, rather than slot numbers, then all this renaming-reordering biz just goes away. There could even be a central online registry of every IR that any participating user had ever scanned, so the app could recognize the original source of IRs you don't even have, in a preset someone gave you. But like I want to ship, for once, instead of waiting to build the perfect thing.