5Once the blank document appears I click "Document Setup" to check that the settings are correct it shows "Print" as the type and "Custom" as the page preset. When I change this to "Presets" as the type and choose my named preset as the page preset, as it should show, it changes the document settings back to what they were when the New Document panel opened.
It seems like as soon as you name the custom preset it saves whatever settings are already populated in the panel from the last document that was opened. I figured out that I need to change my settings first then make a custom preset and name it for the settings to stick. The way you have the panel laid out it makes sense to work from top to bottom and clicking ok to would save all these changes. Is this a bug?
What I want to do is create the mainline connection (a point snapping to the watermain), the hydrant service line (line) and the hydrant (point snapping to the end of the service line) using a 'Preset Template from Selected Features'. Following the instructions above, I am using an existing feature, select all of the features in the order of digitizing, and then go to 'New' - 'Preset Template from Selected Features' but that option is grayed out. The only option available to me is 'Group Template' which doesn't seem to do what I want.
So it appears that using the "Group Template" feature will do what I want. The process of creating the template is a bit finicky, but I was able finally create a Hydrant with a lateral line and a service connection, which I can snap to an existing watermain, and orient it in anyway I want. A much better solution than the 'Preset Template from Selected Features'
OK, well I kind of have this working. I'm not sure what I did differently, but I again selected all of the features and now the 'Preset Template from Selected Features' is enabled, so I was able to to create a template that basically creates what I want, but with some issues. Here are the main problems:
1. When I click on the new template the feature created is EXACTLY the same as the one I 'cloned'. In reality the distance between the connection and the hydrant would never be the same, nor would the bearing from the hydrant to the connection. Basically all I can do with this new template is recreate what I had previously selected when making the template. Is there a way to just click where I want the connection (1st point), click where I want the hydrant (2nd point), then have everything just draw in?? That is what my .NET tool does. I was hoping the templates could do this for me.
1. Preset templates represent the features at the time of capture. They are in fixed positions that cant be dynamically altered. Once created, the features are not associated with each other in terms of moving them.
In the future, 'attribute rules' may be able to help by creating other features in response to a feature you create. e.g. create a hydrant line and then automatically create all the other stuff in between.
Thanks Sean. I do remember that at previous ESRI Conferences, seminars, etc. that doing what I want to do is possible. Is this sort of functionality doable through another ESRI product....ArcFM maybe is what I am thinking of??
Hi Brian, It looks like you are on the Group layer node in Manage Templates, if you click on WAT_Hydrant layer, and then open the menu, you should be able to access the command to create new preset template.
I was able to create the 'Preset Template from Selected Features', but it isn't totally working the way I expected. Please check back and read my comment. Hopefully you have some ideas for me to get this working the way I want.
Also, I may have overexplained. Basically, if I click preset A, I want it to not only turn on everything I have saved for that preset, but I want it to turn off everything on the last preset I had on. Maybe that is a better explanation of what I mean.
I make changes to an existing factory preset, but when I try to create a new preset in the menu, the option is greyed out. I know this has worked before, but just recently I reinstalled FXSound and noticed this issue right away. Anyone else experienced this? Thanks!
More info here: Blink only the last engaged Preset
The article is written with the MC3/6/8 using the blink feature (preset blinks when in toggle position 2, while the MC6 PRO just displays a different color scheme and name), but the logic is the same.
Edit oreset by right clikking it and deactivate matricks from there. Or just selfix that preset and then deactivate matricks and store merge/update that preset. Not on console right now so hope these work
Had my QC for 2 days now and have raced to set up a suite of presets ready for its first gig tonight. Had amazing results so far and really pleased with tones I am getting. Only issue is that the lag when changing presets is really noticeable (will probably be less noticeable when the rest of the band is playing). I know I could get around this with Scenes but we have very quick song and sound changes and Presets will just work better for me.
Presets will always have a little lag because every block has to be loaded. When the QC was released the lag was much more noticeable than it is now, so I can imagine that it might improve over time. But it will always be there.
You can can load multiple amps, cabs, and/or effects into one preset and bypass/activate/change them when needed in scene mode. That should cover all of your needs I guess
Thanks for the reply. Yeah I think I will start looking in to this a bit more. I have an expression pedal hooked up too which allows for even more options. Just need the time to be able to have a full on play around with it.
I get the issue of changing presets for a quick seamless change of songs. The only way I get around this is trying to change to the next preset and to a similar sounds and switch between chords so there is t just a big ringing chord with half a second gap in it.
Hi Fellas,
I have just seen the Youtube video where Kiko reveals his automated Megadeth live setup. He has been using PRESET CHANGE for every different parts of songs. This is done via computer automation. My question is: How could he manage that obvious lag between preset changes?
Within a Babel config, if the preset is on npm, you can pass in the name of the preset and Babel will check that it's installed in node_modules already. This is added to the presets config option, which takes an array.
As of Babel 7, we've decided to deprecate the Stage-X presets and stop publishing them. Because these proposals are inherently subject to change, it seems better to ask users to specify individual proposals as plugins vs. a catch all preset that you would need to check up on anyway. Check out our blog for more context.
I just created the proxy preset (using Adobe Media Encoder) that I need to use with my footage, but when I select the footage -> proxy -> create proxies I am unable to select the proxy that is saved on my desktop. When I do so, the above error message flashes on my screen.
Could anyone help with what I am missing here please, I'm very new to this and still learning everything so would appreciate the help greatly.
I have made the encoding preset already. Can you please further explain the next steps you mentioned:
"Then you make a proxy preset 'based on' that encoding preset. Then you export that proxy preset to the folder that PrPro looks in for such things."
One allows you to make a new thing ... as I recall, same icon to make the original encoding preset, but this time take the option to create a proxy preset. For which encoding preset it will be based on, choose the encoding preset you made.
Then Export the proxy preset. You kinda hafta dig to find where the proxy presets are stored in PrPro. It should know where they are and just put them there, but you do have to navigate to the right folder.
First Step: in Media Encoder > Preset Browser > Plus Icon > Create Encoding Preset > Name, Format, Based on Preset, Basic Video Settings, Effects > Name Overlay > Format: Prefix and Suffix Only. Prefix: Proxy.
I am finding in version 23.1.0 that creating Ingest presets based on the steps in this thread that Premiere Pro is not recognizing Inget presets as ingest presets. I get the mismatch error dialog. This is not making any sense and I'm surprised no one else is seeing this.
First ... never assume that just because you are getting X behavior, all other users are. I found out long ago in computer work that this assumption is often wrong. It might be correct, but until you know, assume you're getting a unique situation. And check.
I can't replicate on my PC, just created a proxy preset a few days ago. Make sure that Premiere and MediaEncoder are both showing identical numbers for versions. Close projects, dump the cache files, or ... when launching, before selecting a project to open, go directly to Pr's menu ... Preferences/Cache files, dump all cache files. Then open the project.
Thanks for the feedback but I didn't assume one single thing. I meticulously replicated the steps illustrated in this post and got the error message 100% of the time. Is that assumption? Absolutely not.
Can you please breakdown how you created your proxy preset a few days ago. Some UI elements have been changed or moved in more recent versions of both PP and Media Encoder and things aren't matching up with previous tutorials scattered across the Internet. When I open ME and choose "Create Ingest Preset" from Preset menu I see what is in the screenshot attached. Curiously, there is no "Based on Preset" option like what was seen in previous version of ME so something is different and I can't see what it is. Another strange thing I see (which is in the screenshot) is that in the bootom right corner there is a "Save A Copy" option but not "OK". There's no original preset that I've created so why default to saving a copy?
3a8082e126