A follow up on the ReWire support:
Currently, Reason 6 is probably the only ReWire device software that uses the new ReWire SDK. I installed the latest Reaper version, and it still uses the older SDK version. To avoid that a large number of users will experience that ReWire does not appear to work in Podium, I’ve now included the ReWire.dll as an option in the Podium installer. I reserve the right to remove the ReWire.dll feature from the installer in the future, once the majority of third-party software have switched to the new ReWire SDK.
So, with the next Podium 3.1.0 release, you won’t need to do the file copying I described in my previous post.
@Zynewave wrote:
@mezhick wrote:
Rewire doesn’t work (win xp sp3) !! Sad
I can’t see buses in devices section and rewire soft doesn’t start in slave mode (reason 5).in version 3.01 everithing was fine…
I’ll do some testing. All I did was update to the latest Propellerheads ReWire SDK, with some minor tweaks to the Podium code. Maybe I overlooked something.
Done testing:
The new ReWire SDK (which supports both 32-bit and 64-bit) expects to find the ReWire.dll file in a different folder than the older ReWire SDK versions. The old SDK expects to find ReWire.dll in “C:WindowsSystem32”, where the new SDK expects it to be in “C:Program FilesCommon FilesPropellerhead SoftwareReWire”.
The latest Reason 6 installer will install ReWire.dll in the proper folder under Common Files, and Podium 3.0.2 will work as expected with Reason 6. If however you use Reason 5, the ReWire.dll is in the System32 folder, and Podium 3.0.2 will not be able to open ReWire.dll.
The Propellerhead ReWire SDK documentation recommends that third-party software that supports ReWire should include the ReWire.dll in their installers, but I think that is a messy solution. Whenever Propellerhead updates the ReWire.dll, there will be a large number of third-party installers that will try to install older ReWire versions. IMO a better solution would be if Propellerhead offered a free download of a dedicated ReWire.dll installer. That way third-party software developers can refer users to download the latest ReWire from the propellerhead website. Similar to how soundcard manufacturers offer downloadable driver updates.
If you are comfortable with using a file explorer, you can make Podium 3.0.2 work with Reason 5, by creating two folders and copying the ReWire.dll file:
Note that the “C:Program FilesCommon Files” folder may be different depending on your Windows OS language.
Create a new “Propellerhead Software” folder under Common Files.
Then create a new “ReWire” folder inside the Propellerhead Software folder
Copy the ReWire.dll from the folder “C:WindowsSystem32” into the “ReWire” folder you just created.
@mezhick wrote:
Rewire doesn’t work (win xp sp3) !! Sad
I can’t see buses in devices section and rewire soft doesn’t start in slave mode (reason 5).in version 3.01 everithing was fine…
I’ll do some testing. All I did was update to the latest Propellerheads ReWire SDK, with some minor tweaks to the Podium code. Maybe I overlooked something.
@rwelteroth wrote:
Hi Frits,
I sent you kind of a midi event log of a full left to right and back sweep of a pan pot on my nanokontrol2 via email.
Maybe you can use it for further optimization of the control surface support in podium.Greetings
Richard
Thanks for the MIDI log. It seems that NanoKontrol pan knobs uses a value-range of 252. I don’t know why Korg chose this range instead of the more logical 128. Perhaps it is because other DAWs expect pan values in this range. Each delta-value message from the NanoKontrol changes the value with 2, so the knob resolution is in reality only 128.
I’ve uploaded beta2. Podium will now use the pan range of 252, when the device is not a genuine MCU. The NanoKontrol is probably the most populer MCU emulation device, and with a bit of luck, other MCU emulating devices also implement pan this way. I’d appreciate if you could test beta2 and let me know if pan on NanoKontrol now works ok.
Thanks for the files. Bug is now fixed. The crash happened because there is no tempo event in your arrangement.
@rwelteroth wrote:
Hi all,
just received my korg nanokontrol2 and tried with the 3.10 beta. Played a bit around with the settings of the nanokontrol2 and now it works, using the “Live” setting (set marker/stop).
Only thing that I don’t like so far ist that the pan pots just work in an area quite close to the central position. I get to the left-/rightmost pan setting by just turning about a quarter to the left or right.
Maybe there is a way to scale the mapping of the pot.I keep on testing and provide more info as far as I find out anything new.
Many thanks for testing.
1/ Are the nanokontrol2 pan knobs endless encoders, or do they have a fixed min/max position?
2/ Does the knobs adjust the pan positions differently if you turn the knobs fast or slow?
3/ Does the range of the knobs differ if you select the other DAW modes?
Some technical info on how the MCU pan works:
On the Mackie MCU the “V-Pots” are endless encoders with no “notch” in the dial, and they use a LED light ring around the knob to indicate what the actual value is. The V-Pots transmit standard MIDI control change values to the DAW, but the values are delta-ticks, and not absolute values. Podium collects the delta-values and calculates how much pan should be adjusted. It then transmits the resulting pan position back to the MCU V-Pot light ring. The Mackie MCU furthermore adjusts the transmitted V-Pot delta-ticks according to how fast the user turns the V-Pot. Turn it fast, and you can pan from left to right with a single hand movement. Turn it slow, and you need to turn the V-Pot 360 degrees several times.
@4mica wrote:
Hi- I don’t have any MCU related equipment, but a friend of mine has an iPhone…could I test it with this?: http://itouchmidi.com/?q=node/32
If so, I’ll wait until he shows up again to test it, assuming my desktop has wireless control…
Maybe, although it seems the app hasn’t been updated since 2009, and it isn’t a full MCU emulation. It also requires that you install software on your PC. I would be surprised if it works with the latest iOS version.
The app I tried, which in its current version 1.0 fails under iOS5, is:
http://www.saitarasoftware.com/Site/AC-7_Core_Mini.html
I could not reproduce a crash. While testing, I did find and fix another bug that caused the audition to not always start. I don’t think that bug is related to your crash.
I would appreciate it if you could email me your Podium.ini file, and the project file with the empty arrangement that causes the crash.
@rwelteroth wrote:
I’d be a happy beta tester for the new functionality since I’m just also thinking about some hardware controller like the nanokontrol which is reasonably priced.
Will you post the availability of the beta version on the vip board?Greetings
Richard
Thanks. The beta is already available in the VIP download topic. I also created a 3.1.0 preview topic in the future forum. Please post your beta feedback in that topic.
Welcome Telenator,
Thanks for the story.
Frits
If you select all the notes, you can use the +/- keyboard shortcuts to coarse adjust velocities of all selected notes.
@tayfun wrote:
i’m using free version. can i use new features in free version? i am wanting to use new surfaces page in podium.
The new features will be available in Podium 3.1.0. It will eventually be available in Podium Free 3.1.0 as well, but the Podium Free releases are some months behind the full version.
I’m doing the final testing of the next Podium release, which features extended MCU support. I don’t have a Nanokontrol2 myself, so you’ll have to wait for other users to report whether it will work with the Podium update. I expect to have a beta ready for VIP users within a couple of days.
I’ll take a look at this before the next release. It sounds like a simple bug.