duncann

It's probably nothing more than the software engineers finding a way to do something more efficiently somewhere in the firmware. Now in some cases, unknown to all of us, there's a shorter DSP distance from point A to point B. The programming instructions for a given task are reorganized in a way to get that task done with less resources, and probably with a certain elegance from the programmers point of view. Have you ever read a book where the writing style is kind of bloated? There's a lot of information that's either unnecessary, or could be condensed to convey the same information in one sentence rather than an entire paragraph of four sentences. As to what specifically might have changed, you'd have to talk to the software engineers and probably have an understanding of the programming language they use. And if there's any downsides, it would be the introduction of unwanted behavior, or bugs, because DI said none of the existing amp models have changed.

I hope I didn't misunderstand what you said, and I don't think I did because you just said it again above, "a few percent perhaps". Which is essentially what I said by saying a "possible ~4%", note the word possible and the tilde character. What I said exactly is below. But again, I'm resorting to my memory, which is for certain fallible. :)

Just so. I should say so people don't get the wrong idea about the possible extra freed DSP, that I also remember Digital_Igloo saying that none of the existing HD amp models have changed sonic character. They are all exactly the same as before. Which means the programmers likely found somewhere else other than the amp models to get the liberated DSP, or found a way to optimize the current HD amp models in a way that doesn't affect the sound.

I would say there would have to be an update to HD Edit to support the new model packs, and the new EQ.

I remember Digital_Igloo saying that the engineers were able to optimize some code while implementing the new EQ that would allow for a possible ~4% extra DSP, as compared to the firmware versions prior to 2.6. The number of HD models are probably only limited by the amount of onboard memory, however much that is.

Here's how it works in Reaper: The first event signals the pod for a bank change. The value for CC0 must be zero or it doesn't work. The second event specifies which setlist you want. In this case the value of 5 means the sixth setlist. The last event specifies which patch you want in setlist 6. Ten means patch 3C. I have to think that the setup would be very similar in Pro Tools.

In Reaper, CC0 is called Bank Select MSB. CC32 is called Bank Select LSB. Program Change is not listed in Reaper with a CC#. There's one called Program. And there's one called Bank/Program Select. So maybe look for something similar in Pro Tools. So what I understand it to be: send any value using CC0 (Bank Change/Select MSB) followed by a value of 0 to 15 using CC32 (Bank Change/Select LSB), followed by a Program Change (no CC#) for preset. I'm far from a midi expert, but it seems there are some messages in the midi protocol that aren't mapped to a CC#. Velocity, Pitch, Program, Channel Pressure, etc.

Yikes! They might be interesting, but I find them to be quite ugly. Reminds of Twiki from Buck Rogers for some reason. Bedeep bedeep bedeep! :lol:

Hold down view to access the system options and it's on the second page.

The one with the spinning gears and moving piston was pretty awesome, even though I'm not a fan of that guitar shape. Sounds good too. The one made from concrete, well, that one screwed with my sense of intuition about what a guitar is. You see it first and think, ok that's a bit strange, but when he started playing it my senses were a little short-circuited. Thanks for that. :huh: :lol: I think if these same guitars were put into the hands of less capable guitar players, the perception of the sound would be completely different.

This is from appendix B of the advanced user manual: Bank & Program Change Messages POD HD500 will respond to incoming MIDI Bank & Program Change messages as follows. • Load Set List: From your MIDI controller device, send a Bank Change CC0 (Bank MSB), CC32 (LSB) message with a value of 0 (for Setlist 1), 1 (for Setlist 2), etc., followed by a Program Change message (Value 0-63 for Preset 01A - 16D) for the desired Preset within the Set List. The Set List and Preset are loaded on POD HD500. • Load a Preset within the current Set List: Send a Program Change message (Value 0-63 for Preset 01A - 16D) for the desired Preset within the current Set List. I don't know about Pro Tools specifically, but it looks like you need to send a CC32 message to specify which setlist you want, and then a program change message to specify which patch. So it looks like you have first and last parts, but are missing the middle part or CC32 after CC0 and before a Program Change.

If you can, make sure to try what spaceatl said and measure the POD PSU output, even it's connected to the Furman. Also, if the device is out of warranty you could try and disassemble the housing if you're comfortable doing that. It could be something as simple as a bad solder joint. Or you could try the same if you don't care about the warranty.

Doesn't sound good. Does it do it for any patch or just a particular one? If it's just one that you know of, try a factory reset again. But this time don't load your custom patches. Instead rebuild the one in question from scratch and then see if it still does it. If it doesn't, try loading the rest of your patches. If it does, try it again without the usb cable attached. And if it still does it, is the unit new? Can you exchange it?

Some of the factory presets use the expression pedal for volume. If it's in the heel position you won't hear anything.

If any differences exist they would be very minor and difficult to hear. I have both an hd500 and hd500x, and I remember when I first tried the X, something seemed different. It was slightly clearer and a little less thin sounding. But it was hard to exactly nail down and the perceived difference was very very slight. A entire world of subjectiveness plays a part too, I'm sure. There is one particular thread on this forum that I remember reading about this very topic. There was an interesting post from someone, can't remember who, who might have had experience with embedded systems like the pods are. This person went into some detail about why the two might sound different simply because of more DSP, even though the base modeling is exactly the same. But if you're looking for definitive technical info about this, you probably won't find it. Although the software engineers could likely answer this, it's unlikely they would take the time to do so.

There's also a negative edge to the anxiousness. I thought I had pretty well settled on a bass tone, but with the new bass amps/cabs coming, that's likely not true anymore. I look forward to the update because they have probably learned from past mistakes and tweaked how they do their amp/cab simulations. I suspect people will generally be pleased with the new models. Hoping for too much? Maybe. Optimistic by nature. But I also dread it. It's the tediousness and time sucking process of constructing a new bass tone and then the possibility exists that I have to go over my existing songs and redo at least the bass parts.

Sorry about that Digital_Igloo. Just a little bit anxious for the update/model packs.

Nicely done. Thanks.

Don't worry. No viruses. Just wav files. But yea, there are better ways to post clips. I liked the first one better.

Here you go. Also, as pianoguyy said, if you reflash the firmware and choose not to save the presets, it will replace any custom presets with blank ones and put the all the rest back to a new/factory condition. hd500x.default.setlists.zip

Not only this, but some character of fizziness can be a component part of the tone when in a mix.

Nice song, tone, and great playing. Liked it very much.

That's a lot of songs. Resulting memory overload almost certain. Maybe that's one reason why guitar players can be like they are, whatever that might mean. :lol: Just a little bit. Do you think that's normal for that to happen? Back on topic. I tried adjusting the res to zero and 25% - and different combinations of thump and decay - for the current song I'm working on, and it sounded ok, but I much preferred the more aggressive sound and feel of a higher res, around 60-80. Anything lower and it starts to sound a little too smooth. I'm strictly a recording person, so live tones are entirely different.

Reaper is one that is able to do this. But you would also need a usb to midi interface.