<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
  <title>nashNET Forums - Getting Started</title>
  <link>http://forum.nash.audio</link>
  <description>nashNET Forums - Getting Started</description>
  <atom:link href="http://forum.nash.audio/forums/thread-rss.asp?fid=31" rel="self" type="application/rss+xml" />
  <item>
     <title>New user</title>
     <link>https://forum.nash.audio/forums/thread-view.asp?tid=3318&amp;posts=1&amp;mid=16455#M16455</link>
     <guid>https://forum.nash.audio/forums/thread-view.asp?tid=3318&amp;posts=1&amp;mid=16455#M16455</guid>
     <description><![CDATA[Hi, just passing by to say hello :-) Tried the free version and registered a few weeks ago. Thanks for keeping the &quot;Scream Tracker&quot; way of tracking alive.]]></description>
     <category>Getting Started</category>
     <pubDate>Mon, 25 Jan 2016 02:17:28 GMT</pubDate>
     <dc:creator>Debvgger</dc:creator>
  </item>
  <item>
     <title>Re: tempo in standalone version</title>
     <link>https://forum.nash.audio/forums/thread-view.asp?tid=3295&amp;posts=3&amp;mid=15384#M15384</link>
     <guid>https://forum.nash.audio/forums/thread-view.asp?tid=3295&amp;posts=3&amp;mid=15384#M15384</guid>
     <description><![CDATA[Hi Maksim,<br /><br />Yeah, the built-in documentation is usually a few .x versions behind. :( <br /><br />It&#39;s always a good fall-back to look at the changelog (in readme.txt) and then look up the .x version&#39;s announcement - which usually explains any new features added.<br /><br />For those stumbling across this thread later: the answer to Maksim&#39;s question is to use the @xx effect to set the tempo (where xx is the tempo, in bpm, specified in hex).<br /><br />Best,<br />Chris]]></description>
     <category>Getting Started</category>
     <pubDate>Tue, 13 Nov 2012 18:43:02 GMT</pubDate>
     <dc:creator>chrisnash</dc:creator>
  </item>
  <item>
     <title>Re: tempo in standalone version</title>
     <link>https://forum.nash.audio/forums/thread-view.asp?tid=3295&amp;posts=3&amp;mid=15383#M15383</link>
     <guid>https://forum.nash.audio/forums/thread-view.asp?tid=3295&amp;posts=3&amp;mid=15383#M15383</guid>
     <description><![CDATA[ok guys! i dig into the posts and find the answers ;) no problems!<br /><br />peace<br />maksim]]></description>
     <category>Getting Started</category>
     <pubDate>Tue, 13 Nov 2012 08:58:53 GMT</pubDate>
     <dc:creator>kcdp</dc:creator>
  </item>
  <item>
     <title>tempo in standalone version</title>
     <link>https://forum.nash.audio/forums/thread-view.asp?tid=3295&amp;posts=3&amp;mid=15382#M15382</link>
     <guid>https://forum.nash.audio/forums/thread-view.asp?tid=3295&amp;posts=3&amp;mid=15382#M15382</guid>
     <description><![CDATA[hi guys and thanx to chris for this good software!<br /><br />there is one stupid question: how i can change song tempo (bpm) in standalone version (of course free edition)? i can&#39;t find it in preferences or command list...<br /><br />sorry for my bad english!<br />take care<br />maksim]]></description>
     <category>Getting Started</category>
     <pubDate>Tue, 13 Nov 2012 03:25:00 GMT</pubDate>
     <dc:creator>kcdp</dc:creator>
  </item>
  <item>
     <title>Re: REAPER and ReViSiT MIDI Output Conflicts?</title>
     <link>https://forum.nash.audio/forums/thread-view.asp?tid=3292&amp;posts=5&amp;mid=15379#M15379</link>
     <guid>https://forum.nash.audio/forums/thread-view.asp?tid=3292&amp;posts=5&amp;mid=15379#M15379</guid>
     <description><![CDATA[Works perfectly! The MIDI interface that was locked before is now greyed out in ReVisit, so for my interface I didn&#39;t have to use the new INI setting.<br />However, after loading if I tried to enable another interface (LoopBe), I still got the error. After applying the INI fix, this problem went away, so both issues are fixed.<br /><br />Everything looks good to me, thanks for putting the time in to fix this :)]]></description>
     <category>Getting Started</category>
     <pubDate>Sat, 27 Oct 2012 21:25:33 GMT</pubDate>
     <dc:creator>jamesh</dc:creator>
  </item>
  <item>
     <title>RE: REAPER and ReViSiT MIDI Output Conflicts?</title>
     <link>https://forum.nash.audio/forums/thread-view.asp?tid=3292&amp;posts=5&amp;mid=15378#M15378</link>
     <guid>https://forum.nash.audio/forums/thread-view.asp?tid=3292&amp;posts=5&amp;mid=15378#M15378</guid>
     <description><![CDATA[<br /> Hi James, <br /> <br />I was unable to replicate the issue on my system - using REAPER 4.261 32-bit / LoopBe1 / Win7 64-bit.<br /> However, I have made a couple of changes that should allow you (and other REAPER users) to work around the issue:<br /> Adding disablemidi=&quot;1&quot; to the reViSiT.ini file (explore &quot;c:\%LOCALAPPDATA%\reViSiT\&quot;) will prevent reViSiT trying to open MIDI devices at all. <br /> <br />&amp;lt;preferences ... disablemidi=&quot;1&quot; ... /&amp;gt; <br /> <br />(&quot;VST Host&quot; will still be available for passing MIDI messages from reViSiT to the host, though you will obviously be limited to 16 channels.)<br />  <br /> Any MIDI device that is disabled (or already in use) will be grayed out in the MIDI Device lists in the Instrument List (F4).<br /> I&#39;ll email you the new build (1.7.1.2) to try out - let me know how you get on. If all looks good, I&#39;ll schedule a wider release as 1.7.2.<br /> Best, <br />Chris]]></description>
     <category>Getting Started</category>
     <pubDate>Sat, 27 Oct 2012 11:51:13 GMT</pubDate>
     <dc:creator>chrisnash</dc:creator>
  </item>
  <item>
     <title>RE: REAPER and ReViSiT MIDI Output Conflicts?</title>
     <link>https://forum.nash.audio/forums/thread-view.asp?tid=3292&amp;posts=5&amp;mid=15377#M15377</link>
     <guid>https://forum.nash.audio/forums/thread-view.asp?tid=3292&amp;posts=5&amp;mid=15377#M15377</guid>
     <description><![CDATA[<br />Some MIDI drivers are single-client, meaning that any software that uses them will &quot;lock&quot; the MIDI device for exclusive use, preventing other applications from successfully opening the port. Because not every host supports the built-in VST mechanism for passing &quot;MIDI&quot; messages to the host, reViSiT additionally offers direct access to MIDI drivers. Obviously, this creates a potential conflict between the host&#39;s and plugin&#39;s attempt to use the driver. It seems reasonable that reViSiT&#39;s claim should be subordinate to the host, which is how it usually works - the host claims the MIDI driver, then when reViSiT loads, it is no longer available.<br /><br />Unfortunately, it sounds like REAPER is a little random about the way it starts up. A host often part-loads it&#39;s plugins during loading, and normally this is done after it has the basic systems like MIDI and audio already initialised. However, I think REAPER tries to do both these things at once (in separate threads), such that it becomes a race as to who gets to grab MIDI devices first. REAPER does load a lot quicker than other hosts, and this could be the price.<br /><br />Aha, makes sense.<br /><br />Anyway, I have PM&#39;d you the requested info. Let me know if you need anything more. Hope you can figure something out! :)<br /><br />Perhaps just an INI flag or something to completely disable Midi Driver loading would work?]]></description>
     <category>Getting Started</category>
     <pubDate>Fri, 26 Oct 2012 11:18:00 GMT</pubDate>
     <dc:creator>jamesh</dc:creator>
  </item>
  <item>
     <title>RE: REAPER and ReViSiT MIDI Output Conflicts?</title>
     <link>https://forum.nash.audio/forums/thread-view.asp?tid=3292&amp;posts=5&amp;mid=15376#M15376</link>
     <guid>https://forum.nash.audio/forums/thread-view.asp?tid=3292&amp;posts=5&amp;mid=15376#M15376</guid>
     <description><![CDATA[Hi James,<br /><br />Welcome to the forum! It sounds like you have encountered a rare, but perfect storm of MIDI - a collision of specific drivers, host and plugin.<br /><br />Some MIDI drivers are single-client, meaning that any software that uses them will &quot;lock&quot; the MIDI device for exclusive use, preventing other applications from successfully opening the port. Because not every host supports the built-in VST mechanism for passing &quot;MIDI&quot; messages to the host, reViSiT additionally offers direct access to MIDI drivers. Obviously, this creates a potential conflict between the host&#39;s and plugin&#39;s attempt to use the driver. It seems reasonable that reViSiT&#39;s claim should be subordinate to the host, which is how it usually works - the host claims the MIDI driver, then when reViSiT loads, it is no longer available.<br /><br />Unfortunately, it sounds like REAPER is a little random about the way it starts up. A host often part-loads it&#39;s plugins during loading, and normally this is done after it has the basic systems like MIDI and audio already initialised. However, I think REAPER tries to do both these things at once (in separate threads), such that it becomes a race as to who gets to grab MIDI devices first. REAPER does load a lot quicker than other hosts, and this could be the price.<br /><br />I&#39;ve not had reports of similar errors in the past, which presumably means most drivers are multi-client, or other hosts are more careful with their startup. For example, in Cubase, I seem able to use MIDI devices in both the plugin and the host, without conflict - though it&#39;s possible Cubase has more advanced / flexible MIDI support. Things might have also improved in more recent versions of Windows (it would be sensible for the OS to lock the device, then itself accept, mediate, and merge MIDI requests from multiple applications).<br /><br />Let me know about your host (version and whether 32-bit or 64-bit), your MIDI interface (make and model) and OS (version and whether 32-bit or 64-bit), and I&#39;ll see if I can code some kind of workaround. This might be a setting disabling reViSiT external MIDI support (possibly, initially, requiring an edit to the config file), or maybe a method to detect when reViSiT is &quot;part-loaded&quot;, so that it doesn&#39;t try to initialise MIDI support before REAPER does. It may also be possible to defer initialising MIDI devices until they are actually used in a song, though I&#39;m not sure how feasible this is in the current codebase.<br /><br />All the best,<br />Chris<br /><br />]]></description>
     <category>Getting Started</category>
     <pubDate>Fri, 26 Oct 2012 05:54:15 GMT</pubDate>
     <dc:creator>chrisnash</dc:creator>
  </item>
  <item>
     <title>REAPER and ReViSiT MIDI Output Conflicts?</title>
     <link>https://forum.nash.audio/forums/thread-view.asp?tid=3292&amp;posts=5&amp;mid=15375#M15375</link>
     <guid>https://forum.nash.audio/forums/thread-view.asp?tid=3292&amp;posts=5&amp;mid=15375#M15375</guid>
     <description><![CDATA[Hi all,<br /><br />I&#39;m having some strange problems using Revisit as a plugin in REAPER with the MIDI-out functionality. Sometimes - around 50% of the time - when I close and reopen a project with a Revisit instance, REAPER pops up a message saying it cannot open the midi output to my synth, and then the track no longer outputs midi since the device no longer shows as a selectable option. Once I remove the revisit instance, the device is available again. Revisit is somehow locking the MIDI device but I can&#39;t find any settings to make revisit ONLY use the 00: VST Host option and not ping for other devices. Does such a setting exist?<br /><br />Additionally, if I have revisit in a project open, and I go to the REAPER settings and try to enable a midi device, I get the same warning message.<br /><br />Are there any solutions to this?<br /><br />Thanks!]]></description>
     <category>Getting Started</category>
     <pubDate>Thu, 25 Oct 2012 16:56:05 GMT</pubDate>
     <dc:creator>jamesh</dc:creator>
  </item>
  <item>
     <title>RE: Yet another &quot;reViSiT and VST instruments&quot; question</title>
     <link>https://forum.nash.audio/forums/thread-view.asp?tid=3213&amp;posts=2&amp;mid=15088#M15088</link>
     <guid>https://forum.nash.audio/forums/thread-view.asp?tid=3213&amp;posts=2&amp;mid=15088#M15088</guid>
     <description><![CDATA[<br /> Hi game_0ver,<br /> reViSiT can connect to other VSTi instruments that are hosted in the parent program (i.e. Nuendo).  <br />In the reViSiT Help, there are two pages detailing how this can be done:<br /> Working with the Host &amp;gt; Connecting Instruments <br />Working with the Host &amp;gt; Example Setups &amp;gt; Steinberg Cubase SX<br /> You should find the Example Setup useful, as Cubase and Nuendo are very similar.<br /> &#39;Hope this helps, <br />Chris]]></description>
     <category>Getting Started</category>
     <pubDate>Tue, 27 Apr 2010 16:07:26 GMT</pubDate>
     <dc:creator>chrisnash</dc:creator>
  </item>
  <item>
     <title>Yet another &quot;reViSiT and VST instruments&quot; question</title>
     <link>https://forum.nash.audio/forums/thread-view.asp?tid=3213&amp;posts=2&amp;mid=15087#M15087</link>
     <guid>https://forum.nash.audio/forums/thread-view.asp?tid=3213&amp;posts=2&amp;mid=15087#M15087</guid>
     <description><![CDATA[The only thing I&#39;m more or less good at is OpenMPT (aka ModPlug Tracker) but finding good sample sets is very hard and it won&#39;t allow me to use audio editing at the same time. Plus, OpenMPT lacks some really neat features.<br /><br />So I decided to try my hand at Nuendo, EDIROL Orchestral (VST with great orchestral sounds) and reViSiT.<br /><br />Is there anyone who can explain me in an &quot;I&#39;m an idiot, I need handholding&quot; way, step-by-step, how do I get instruments from EDIROL Orchestral to use them in reViSiT?<br /><br />P.S. Yes, I know I could try to use VST instruments in OpenMPT but... still no audio editing and no cool features from Nuendo...]]></description>
     <category>Getting Started</category>
     <pubDate>Tue, 27 Apr 2010 15:23:21 GMT</pubDate>
     <dc:creator>game_0ver</dc:creator>
  </item>
  <item>
     <title>Re: reViSiT help not working (it seems)</title>
     <link>https://forum.nash.audio/forums/thread-view.asp?tid=3201&amp;posts=10&amp;mid=15063#M15063</link>
     <guid>https://forum.nash.audio/forums/thread-view.asp?tid=3201&amp;posts=10&amp;mid=15063#M15063</guid>
     <description><![CDATA[Thanks for that information. I traced the problem to UAC (User Access Control) in Vista/7, which prevents applications that aren&#39;t running with Administrator privileges writing anything to the Program Files directory.<br /><br />With the new release (1.3.3), I now include these two files in the initial setup program, rather than rely on reViSiT extracting them later. It means a bigger download, but I guess that&#39;s the price of Vista/7 support. Also, because of the more complicated install process, I&#39;m no longer distributing the zip archive version - though people should be able to open the .exe in any program that supports WinRAR compression.<br /><br />Best,<br />Chris]]></description>
     <category>Getting Started</category>
     <pubDate>Fri, 12 Feb 2010 18:27:06 GMT</pubDate>
     <dc:creator>chrisnash</dc:creator>
  </item>
  <item>
     <title>Re: reViSiT help not working (it seems)</title>
     <link>https://forum.nash.audio/forums/thread-view.asp?tid=3201&amp;posts=10&amp;mid=15052#M15052</link>
     <guid>https://forum.nash.audio/forums/thread-view.asp?tid=3201&amp;posts=10&amp;mid=15052#M15052</guid>
     <description><![CDATA[AHA.<br /><br />I went into the X86 Program Files folder and looked at the attributes for the vst folder and found (lo and behold) it was set to read only. I&#39;m not sure why this was the case, but perhaps it has something to do with FL Studio since I&#39;m assuming it is the program which created to folder in the first place.<br /><br />Anyway, everything seems to be working fine. Now I can get to it in earnest.<br /><br />M]]></description>
     <category>Getting Started</category>
     <pubDate>Thu, 4 Feb 2010 14:31:07 GMT</pubDate>
     <dc:creator>mpalmer28</dc:creator>
  </item>
  <item>
     <title>Re: reViSiT help not working (it seems)</title>
     <link>https://forum.nash.audio/forums/thread-view.asp?tid=3201&amp;posts=10&amp;mid=15051#M15051</link>
     <guid>https://forum.nash.audio/forums/thread-view.asp?tid=3201&amp;posts=10&amp;mid=15051#M15051</guid>
     <description><![CDATA[You&#39;re quite right. I have the standard Windows font instead of the ones you just showed me.<br /><br />Hmmm... Hope that helps.<br /><br />M]]></description>
     <category>Getting Started</category>
     <pubDate>Thu, 4 Feb 2010 04:19:38 GMT</pubDate>
     <dc:creator>mpalmer28</dc:creator>
  </item>
  <item>
     <title>RE: yet another tempo-related question...</title>
     <link>https://forum.nash.audio/forums/thread-view.asp?tid=3204&amp;posts=3&amp;mid=15050#M15050</link>
     <guid>https://forum.nash.audio/forums/thread-view.asp?tid=3204&amp;posts=3&amp;mid=15050#M15050</guid>
     <description><![CDATA[Hi Chris,<br /><br />There are no plans at the moment to have independent tempo features in reViSiT, largely because of the added-confusion it could cause. However, reMASTER, a side project I&#39;ll be working on this summer (to create a dedicated host just for reViSiT - i.e. creating a standalone option) will encourage me to think more on the subject (tempo will need to be controlled somehow!). Similarly, I&#39;m going to be investigating the possibility of reViSiT sending MIDI timecode, so that it might drive the host, which will require similar considerations.<br /><br />Thanks for your reply! The possibility of reViSiT driving the host sounds like a very desirable feature - in many ways this would enable the same workflow and convenience as doing things with Impulse Tracker.  A standalone version would also be cool (I can definitely see it directly competing with things like Renoise).<br />: )<br />Hope these features do wind up in reViSiT someday.  In the meanwhile I guess I could get the hang of it, even try out different hosts and see what&#39;s most convenient.  (Actually, I wonder which hosts offer the nicest/most convenient interfaces, especially from the standpoint of musicians who &quot;grew up&quot; with trackers - but that&#39;s probably a topic for a different thread...)<br /><br />Cheers,<br />AK]]></description>
     <category>Getting Started</category>
     <pubDate>Wed, 3 Feb 2010 20:39:56 GMT</pubDate>
     <dc:creator>akeren</dc:creator>
  </item>
  <item>
     <title>RE: yet another tempo-related question...</title>
     <link>https://forum.nash.audio/forums/thread-view.asp?tid=3204&amp;posts=3&amp;mid=15049#M15049</link>
     <guid>https://forum.nash.audio/forums/thread-view.asp?tid=3204&amp;posts=3&amp;mid=15049#M15049</guid>
     <description><![CDATA[Hi akeren,<br /><br />Welcome back!<br /><br />As you&#39;ve correctly surmised, reViSiT gets all its tempo info from the host, so the ease of trying out new tempos in reViSiT is tantamount to doing the same in the host, and some hosts are better than others - Cubase lets you change the tempo using the transport bar, and allows you to toggle between a single tempo or using a more complicated tempo track. Saying that, demoing tempo changes is still a little cumbersome.<br /><br />There are no plans at the moment to have independent tempo features in reViSiT, largely because of the added-confusion it could cause. However, reMASTER, a side project I&#39;ll be working on this summer (to create a dedicated host just for reViSiT - i.e. creating a standalone option) will encourage me to think more on the subject (tempo will need to be controlled somehow!). Similarly, I&#39;m going to be investigating the possibility of reViSiT sending MIDI timecode, so that it might drive the host, which will require similar considerations.<br /><br />&#39;Hope this helps,<br />Chris<br />]]></description>
     <category>Getting Started</category>
     <pubDate>Wed, 3 Feb 2010 17:56:13 GMT</pubDate>
     <dc:creator>chrisnash</dc:creator>
  </item>
  <item>
     <title>yet another tempo-related question...</title>
     <link>https://forum.nash.audio/forums/thread-view.asp?tid=3204&amp;posts=3&amp;mid=15048#M15048</link>
     <guid>https://forum.nash.audio/forums/thread-view.asp?tid=3204&amp;posts=3&amp;mid=15048#M15048</guid>
     <description><![CDATA[First of all, I have to say I majorly appreciate this project and its continued development!  I am back with reViSiT after a couple years of not having touched it - the old version I was testing had some problems with my host of choice (Sonar), but I just downloaded v1.3.2 and everything works like a charm... keyboard is flawless, and no crashes anymore.  Great work Chris!<br /><br />To my question:  After playing a bit with the program, testing a few .IT files, and looking around on the forums - I get the basic idea regarding tempo (i.e.. the host rules all).<br /><br />This does make sense when playing the full composition from the host, with reViSiT playing alongside all my other tracks.  But how about just playing one pattern (F6) or even the full song (F5) from reViSiT itself, to see how it sounds at a particular tempo, or with tempo changes?   Is there any way to set an &quot;internal&quot; reViSiT tempo for this purpose (which the host itself would just ignore when playing the full project)?<br /><br />Currently I find that whenever I want to play a pattern at a particular tempo, I need to go back to beginning of the song&#39;s timeline (in the host) to change the project&#39;s default BPM (the current tempo at any other point doesn&#39;t seem to matter).... and if I want tempo changes throughout the pattern itself - well, I can&#39;t hear that without actually going and applying them from the host.<br /><br />This isn&#39;t a major complaint or anything like that... I simply find it much easier to do most of my work within the tracker, so having to do all of this is just kind of cumbersome. Then again, I&#39;m only starting out all over again, maybe this is just &#39;birth pangs&#39; so to speak....]]></description>
     <category>Getting Started</category>
     <pubDate>Wed, 3 Feb 2010 04:37:29 GMT</pubDate>
     <dc:creator>akeren</dc:creator>
  </item>
  <item>
     <title>Re: reViSiT help not working (it seems)</title>
     <link>https://forum.nash.audio/forums/thread-view.asp?tid=3201&amp;posts=10&amp;mid=15045#M15045</link>
     <guid>https://forum.nash.audio/forums/thread-view.asp?tid=3201&amp;posts=10&amp;mid=15045#M15045</guid>
     <description><![CDATA[<br /> Hi Matt, <br /> <br />I&#39;ve just tested reViSiT with Windows 7 64-bit, and the help worked perfectly, so I&#39;ve no idea what&#39;s wrong.  <br /> <br />One question: does the font in the pattern look like the reViSiT font? For example:<br /> http://www.nashnet.co.uk/english/revisit/revisit09011.jpg  <br />or http://www.nashnet.co.uk/english/revisit/revisit12001.jpg<br /> Or just a standard Windows font? For example:<br /> http://www.nashnet.co.uk/english/revisit/revisit08951.gif<br /> Both the font file and the help file are extracted in the same manner, so you might not have the font either.<br /> Cheers, <br />Chris]]></description>
     <category>Getting Started</category>
     <pubDate>Tue, 2 Feb 2010 18:12:29 GMT</pubDate>
     <dc:creator>chrisnash</dc:creator>
  </item>
  <item>
     <title>Re: reViSiT help not working (it seems)</title>
     <link>https://forum.nash.audio/forums/thread-view.asp?tid=3201&amp;posts=10&amp;mid=15041#M15041</link>
     <guid>https://forum.nash.audio/forums/thread-view.asp?tid=3201&amp;posts=10&amp;mid=15041#M15041</guid>
     <description><![CDATA[Works great. Thanks.<br /><br />M]]></description>
     <category>Getting Started</category>
     <pubDate>Sun, 31 Jan 2010 02:08:10 GMT</pubDate>
     <dc:creator>mpalmer28</dc:creator>
  </item>
  <item>
     <title>Re: MIDI notes/volumes/effects</title>
     <link>https://forum.nash.audio/forums/thread-view.asp?tid=3125&amp;posts=6&amp;mid=15039#M15039</link>
     <guid>https://forum.nash.audio/forums/thread-view.asp?tid=3125&amp;posts=6&amp;mid=15039#M15039</guid>
     <description><![CDATA[The volume column for a note in reViSiT is used as the MIDI velocity, for MIDI instruments - but note that the MIDI spec does not allow you to change the volume of a note after it has started. Instead, subsequent volume changes for that note in reViSiT will be sent as MIDI Channel volume, not velocity.]]></description>
     <category>Getting Started</category>
     <pubDate>Sat, 30 Jan 2010 13:30:57 GMT</pubDate>
     <dc:creator>chrisnash</dc:creator>
  </item>

</channel>
</rss>
