willjrock

Ticket Opened. Thanks guys!

Just to underscore the subject, Zooey is one of THE most helpful, and consistently helpful people in this forum.

Wanted to update here to clarify my topic. Ok so, the first thing is to route all the audio to the B path as follows Everything is still sounding as intended, and you can see in the next pic that the lower IR block shows IR #99, and that IS in fact, the IR that is audible at this point. Now, by dragging the top IR block as shown in the next pic The lower IR block still shows IR #99, but IR block #1 has now become audible. Audibly, the lower IR block has changed to the cab i have in my #1 slot, but visually, the lower IR block has not changed at all, while all along, no change was intended obviously. Here is the preset if you would like to try yourself. https://www.dropbox.com/s/r8sjybv799rtenr/Hi%20Gain.hlx?dl=0 You will have to go through the motions i described above.....and then after attempting with my preset, maybe attempting to build the same preset from scratch on your own system might be useful? The type of IRs (brand) have not had an impact so far. Thanks. Appreciate any interest here. Wanted to update here to clarify my topic. Ok so, the first thing is to route all the audio to the B path as follows Everything is still sounding as intended, and you can see in the next pic that the lower IR block shows IR #99, and that IS in fact, the IR that is audible at this point. Now, by dragging the top IR block as shown in the next pic The lower IR block still shows IR #99, but IR block #1 has now become audible. Audibly, the lower IR block has changed to the cab i have in my #1 slot, but visually, the lower IR block has not changed at all, while all along, no change was intended obviously. Here is the preset if you would like to try yourself. https://www.dropbox.com/s/r8sjybv799rtenr/Hi%20Gain.hlx?dl=0 You will have to go through the motions i described above.....and then after attempting with my preset, maybe attempting to build the same preset from scratch on your own system might be useful? The type of IRs (brand) have not had an impact so far. Thanks. Appreciate any interest here.

Thanks as always man, I did not download this preset from custom tone, and it most likely IS restored from an earlier firmware version. I will try building it from scratch. Firmware and editor are matched up on 2.20 (great point though - i missed this once a while back) I have never uninstalled firmware before installing new, so you very well may have something there as well. State of the split shows 100% right, i am positive about the IR block i am hearing and which is loaded, and yes when i toggle up to the next preset, it does in fact "line up" with the next in line, and then when i come back to the stored preset it is also returns to its "correct state", so the fix is easy. This i knew after i discovered the bug, but before i realized what was happening, i often had stored sounds to return to it later thinking "is that right"? Sounds like you can access the file if you have any further interest. I apologize. The last post was accidental and has thus been deleted. Ive been posting from my iphone and its been challenging to say the least. I was actually intending on posting in the "bug report" thread since the images had been updated.

that really is strange. I'll have to check it. I only have one preset with that name in there. Maybe the file ext I was forced to add had something to do with it somehow. I'll have to look.

Good question HO. Thanks for your response. The split DOES remain at 100%B path.

Thanks man. Fixed. Not sure why i suddenly need to add raw=1 at the end of my dropbox links, but i sure do.

Wanted to report my bug here, Ok so, the first thing is to route all the audio to the B path Everything is still sounding as intended, and you can see that the lower IR block shows IR #99 and that is in fact the IR that is audible. Now by dragging the top IR block as show here The lower IR block still shows that it is on IR #99, but IR block #1 has now become audible. So audibly, the lower IR block has changed to the cab i have in my #1 slot, but visually the lower IR block has not changed at all, while all along, no change was intended. Here is the preset. https://www.dropbox.com/s/r8sjybv799rtenr/Hi%20Gain.hlx?dl=0 Obviously you will have to go through the motions.....and then after attempting with my preset, maybe attempting to build the preset from scratch on your own system might be useful? I dont *think* the type of IRs should matter. I dont know yet. OS is Firmware 2.20 but this has been present for as long as i can remember. Maybe a year?

PS. the images in my 2nd post are not loading at the moment, so if this is the same for you and does not persist please let me know.

Wanted to update here to clarify my topic. Ok so, the first thing is to route all the audio to the B path as follows Everything is still sounding as intended, and you can see in the next pic that the lower IR block shows IR #99, and that IS in fact, the IR that is audible at this point. Now, by dragging the top IR block as shown in the next pic The lower IR block still shows IR #99, but IR block #1 has now become audible. Audibly, the lower IR block has changed to the cab i have in my #1 slot, but visually, the lower IR block has not changed at all, while all along, no change was intended obviously. Here is the preset if you would like to try yourself. https://www.dropbox.com/s/r8sjybv799rtenr/Hi%20Gain.hlx?dl=0 You will have to go through the motions i described above.....and then after attempting with my preset, maybe attempting to build the same preset from scratch on your own system might be useful? The type of IRs (brand) have not had an impact so far. Thanks. Appreciate any interest here.

I'll report it and i can reproduce it, but has anyone come across a bug when dragging IR blocks, it resets one of the IRs to the first IR in the bank? (only by audio, NOT visually) IR #1 I dont know the specifics because i just nailed this one down. It may only happen when using two 1024 IRs. I knew something was going on because of the tone change, but sometimes its hard to tell. Esp when you have two cabs and fx running. This bug has to have been acknowledged im sure. What do you know?

Sure there are work-a-rounds, i just hoped that it was an easy implementation. I guess you could always save a favorite block to a preset and then export that preset if you felt the need to back it up, but boy would user defaults make sense IMO.

Seems like user definable default settings, for a block inside Helix isnt atop the L6 priority list. What about an export function, so that our favorite block presets can be saved permanently? Maybe user defaults are something that is planned for the future, but in the meantime this is something that is easily implemented?

Im betting amsdenj has given you the right answer for your situation. Also comparisons made to a hardware amp may not be fair. If you need a volume boost i would just automate the amps channel volume or output block to reflect those changes. A little more hassle for sure, but adding "level" to the front end of a distorted amp isnt going to give you any more volume.

Can you not purchase the checkerboard series (and some others) by itself? Thats just silly if thats the case. Why would you turn down money?

Not necessarily. Sometimes the master volume just adds volume, sometimes it adds distortion, sometimes a combo of both, sometimes it will change the shape of the distortion entirely....and the amp channel doesnt do anything at all in that regard

Hey Z, I have replaced the files. Actually they were never moved, so i dont know if it had anything to do with a dropbox update or what. Another thing is that , when i initially linked the files, you could play the audio right here, without being redirected to dropbox, and i like that, but for whatever reason (i cant see how its anything im doing) that is no longer the case. In any case the files are there now

It was. One year on the helix, and then an additional 2 from sweetwater. Maybe you got it for a little less $$ or something? Demo maybe? Maybe theyre only willing to give a year on a demo? Maybe we just got different deals.

46 in June. Ive always kept my age attached to my sig and have often wondered why more dont. Its probably the first thing i wonder about when reading other's posts. I think it helps perspective. I dont know. Hmmm.....I was given two extra years of warranty for a total of three. Im sure thats what you meant.

It can even be an amp. As long as you keep the elements down that add distortion (drive,master) and rely more on the elements that add volume (channel volume) you can make anything work. There are no rules.

I doubt if there was any difference at all because the second he imported that 48/24 file into the Helix, it was converted to 48/16, therefore when doing his analysis he would have been comparing two identical files, and any difference in sound was most likely caused by placebo ,the positioning of his head - even an inch, or something similar..

Doesnt matter. The reamp is just used to conduct the test. Not sure what you are trying to say here. Well your memory isnt so good, so may i suggest another course of action for comparing updates. The thing was that you claimed that they were "way" better. You may be right and some of it may be my fault but i just get tired of false claims being made on the net. Thought about that... didnt test any reverbs, and as we all know they ARE different to some extent. Im sure not enough to produce audible results, but they probably may cause discrepancies in a null test. How to factor that in i have no idea.

No, i actually did the test,but the result was perfect silence, therefore the attached file is an accurate result, but the humor is in that there is no point of posting it. No offence taken, but i dont get on the internet and make claims about anything in this fashion, muchless those that are un provable. Im telling you i DID weigh the files against each other, and the result was silence, therefor the update did NOT change the sound of the Helix at ALL, in regards to the presets that are identical on 2.11 and 2.20.. Also - each person has to do the test themselvs for total accuracy. The only file i would be able to attach is the result of nulling the two files - which would be silence or very little sound, or the file used for reamping. Theres nothing else i or anyone could provide, so its either do the test for ones self or take my word for it. Probably not be all end all for tests, but FAR more than anyone starting a thread to say the update made their helix sound "way better" .

Sorry i was trying to stick it on the site player (and trying to be funny -its an empty file- which would be the result) and couldnt remember how at the moment, and am in a bit of a rush.

Here ya go :) https://www.dropbox.com/s/p83edh9igup86if/null.mp3?dl=0 I use 3 factory presets somewhat regularly. Each time an update comes out, somebody claims that "everything sounds better" so for each of the 3 presets i use (of course not all of them - but i dont think they would sonically upgrade everything except for the 3 factory presets i use :) ) what i did was A) Record a dry DI file B ) reamped it thru 2.11 C) update firmware D) reamped same DI file thru IDENTICAL preset E) played tracks at the same time with phase flipped on one track, and the result is above. Next time im going to beat everyone to the punch with a thread titled "before you go claiming the update made your helix sound better" :) Thats not true. It is provable that the sounds did not change. See above null(2).mp3