HISE Logo Forum
    • Categories
    • Register
    • Login

    Default .xml Per Project

    Scheduled Pinned Locked Moved Feature Requests
    12 Posts 3 Posters 501 Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • A
      aaronventure @d.healey
      last edited by

      @d-healey I do too, that's why I would like to have the option for it to load immediately on HISE load.

      d.healeyD 1 Reply Last reply Reply Quote 0
      • d.healeyD
        d.healey @aaronventure
        last edited by

        @aaronventure aha I see, I just press enter so hadn't paid it much attention

        Free HISE Bootcamp Full Course for beginners.
        YouTube Channel - Public HISE tutorials
        My Patreon - HISE tutorials

        A 1 Reply Last reply Reply Quote 0
        • A
          aaronventure @d.healey
          last edited by

          @d-healey when launching HISE or project change? For project change, yeah, enter works, but for launching HISE it's always navigating to File > Recent Files > preset.xml , unless I'm missing something.

          d.healeyD 1 Reply Last reply Reply Quote 0
          • d.healeyD
            d.healey @aaronventure
            last edited by

            @aaronventure I think you're right

            Free HISE Bootcamp Full Course for beginners.
            YouTube Channel - Public HISE tutorials
            My Patreon - HISE tutorials

            1 Reply Last reply Reply Quote 0
            • oskarshO
              oskarsh @aaronventure
              last edited by

              @aaronventure That would be great ++

              When compiling DSP Networks having to reopen HISE makes it much more streamlined if it will load up the same .xml as before or if we can just set a default XML.

              A d.healeyD 2 Replies Last reply Reply Quote 1
              • A
                aaronventure @oskarsh
                last edited by

                @oskarsh Also the same workspace and script editor tabs but one step at a time 😃

                1 Reply Last reply Reply Quote 0
                • d.healeyD
                  d.healey @oskarsh
                  last edited by

                  @oskarsh you don't need to open the XML to compile the project's networks

                  Free HISE Bootcamp Full Course for beginners.
                  YouTube Channel - Public HISE tutorials
                  My Patreon - HISE tutorials

                  oskarshO 1 Reply Last reply Reply Quote 0
                  • oskarshO
                    oskarsh @d.healey
                    last edited by

                    @d-healey I know :)

                    But if you want to test it in context with your project you surely need to open the correct xml

                    d.healeyD 1 Reply Last reply Reply Quote 0
                    • d.healeyD
                      d.healey @oskarsh
                      last edited by d.healey

                      @oskarsh said in Default .xml Per Project:

                      the correct xml

                      You have more than one? :p

                      Most of the time I open HISE once to work on my project, and close it when I'm done. The rest of the time I want to open a blank preset for making little test projects. So a default xml thing isn't so useful to me. But maybe it would be better if when you open HISE it shows you a prompt asking if you want to reopen the last xml, then you can hit enter or esc depending on what you want to do?

                      Free HISE Bootcamp Full Course for beginners.
                      YouTube Channel - Public HISE tutorials
                      My Patreon - HISE tutorials

                      oskarshO 1 Reply Last reply Reply Quote 0
                      • oskarshO
                        oskarsh @d.healey
                        last edited by

                        @d-healey I have one main xml file named like the project and smaller stripped down versions for testing. Once a plugin reaches a certain level of complexity I like to branch out and create a new one to test complex features in isolation.

                        I often also have a Waveform, Filter, Arp combo in one xml to test the audio and the scriptfx networks. So that I can click click click to have a good sounding working setup. I mainly work with FX Plugins.

                        I think having a prompt where we can just press enter or escape would be a very good compromise. I think this already exists when changing projects.

                        1 Reply Last reply Reply Quote 1
                        • First post
                          Last post

                        21

                        Online

                        2.0k

                        Users

                        12.7k

                        Topics

                        110.1k

                        Posts