ronin@IrishGuy wrote:
Thanks, Mike G and Ronin for the excellent tips. I will try the vst plug-ins that you suggest.
There are a lot more out there but these plugs may get you started.
@IrishGuy wrote:
Regarding the ASIO4ALL driver, is this a generic driver that works across many devices?….I will follow up in the link you’ve provided.
Yes, it is. Maybe u should check out the GNX4 manual. As far as I know it has a built-in soundcard and ASIO drivers available. You can hook that up to your computer and connect speakers to your GNX4. I have a G9.2tt that works this way….but to be honest I don’t use it as interface.
roninFor music production I still use XP Pro. The reason is the availability of related software and drivers. For any other purpose I use Linux (Fedora).
roninAs already said your laptop soundcard should work but you may achieve better results by using an ASIO driver (device). If you have problems with latency you should try the ASIO4ALL driver (http://www.asio4all.com/).
Install, Podium->Setup->Midi/Audio Interfaces-> choose ASIO devices and select ASIO4ALL.
If u need an instrument try Zynewave Nucleum (http://www.zynewave.com/files/Nucleum095.zip). Just copy that to your vstplugins folder (can be defined in podiums setup). If it is properly scanned you can select this instrument as track source.
btw. the GNX4 is an ASIO capable sound device. It can be used as external sound card.
roninAre you talking about the project tab’s background texture respectively the texture near the file,edit and view menu in the arrangement window? If yes then I’m afraid that these textures are hard-coded resources.
Sorry, I use a dark skin and the texture is not very visible. I thought it was used as arrangement background.
roninI’m sorry but a new bug has crossed my desk 🙂 Maybe you are already aware of this.
The take list (of a comp event) grows with every comp event. This means:
– the first loop had 3 takes -> comp list shows these 3 takes
– the second loop had 5 takes -> comp list shows all 8 takes
…
This was pretty confusing because firstly I didn’t saw where these mis-takes are coming from 🙂
The “rotating takes” work really nice!
ronin@Zynewave wrote:
@ronin wrote:
By the way: I think if there is no arrangement (its empty) playback should never stop with “stop playback @ end of arrangement” enabled. (It would be consistent if it never starts but there is no use case where this could be a desired behaviour 🙂 )
Is the problem that it is confusing that playback won’t start if you try to start an empty arrangement?
Yes. I’m aware of this option so its not really confusing to me but a new user might stumble accross this.
roninmaybe you can load a clean picture?…filled with a color or just a transparent plane (via project properties)?
roninI’ve found a small bug in 2.08beta4:
If “deactivate record mode if playback is stopped” is enabled a loop recording (comp track) gets disabled after the first take if the loop is at the end of the arrangement. This problem is independant from the setting “stop playback @ end of arrangement”.
Can someone confirm this?
By the way: I think if there is no arrangement (its empty) playback should never stop with “stop playback @ end of arrangement” enabled. (It would be consistent if it never starts but there is no use case where this could be a desired behaviour 🙂 )
ronin@Zynewave wrote:
@ronin wrote:
1. Is the LAST n takes feature rejected? I think its highly useful.
Nope. See the beta4 release notes.
Yeay! My personal christmas gift 🙂
@Zynewave wrote:
@ronin wrote:
2. Uncomplete takes are not detected. I gues this has reasons but it could be useful.
Only takes covering the full range of the comp event is included in the comp event take menu. I’ll consider changing this so that take events that stops before the comp event end, are also included.
No problem here. I just thought of that.
@Zynewave wrote:
@ronin wrote:
3. Is it possible to get full multiple comp events per track? Let me explain this with a small example picture.
A new take track will always be created when recording a new take. If you are running out of space as on your screenshot, you can manually move the second group of take events up on the first take tracks, and then delete the now empty bottom take tracks.
Hmm this leads to a problem with my use of comp tracks and the “delete oldest take” feature. I’d like to have a track called guitar. this track contains all e.g. clean guitar stuff and I’d like to do a multiple take record for every part of the song. As seen in the screenshot the “delete old take” feature may, while recording the right comp event, delete the first take track which contains a needed part (left side in screenshot) if the take maximum is reached. Is it possible to define this maximum as local maximum? 🙂 If the current loop has only 3 takes (whereas another comp event in the comp track has 5 and maximum is 5) then I should be able to do 2 more takes. Take deletion should then be done loop-based and not track based.
Other opinions are appreciated!
@Zynewave wrote:
@ronin wrote:
4. Another note for consistency. Personally I think moving(cutting) the comp event should move(cut) the take events. Currently it could easily lead to mistakes. This note leads to the highly appreciated group editing (like fading multiple events) 🙂
I know there are some hosts that implements multi-take this way, but I also read discussion on the net where people complained about this. They argued that they would like to be able to edit the take events as regular events and then promote these edited events to the comp track. I’m going to add some commands for this later on.
Well then its a question of taste. Group editing would be really handy but this can be done in a later update.
P.S.: The new edit-mode-less workflow is really cool. Same goes for the separated loop ranges. I’m getting used to it and its really going to make fun 🙂 Cheers for frits!
roninHi everyone,
I’ve played around with the new comp feature and noticed some things.
1. Is the LAST n takes feature rejected? I think its highly useful.
2. Uncomplete takes are not detected. I gues this has reasons but it could be useful. see
3. Is it possible to get full multiple comp events per track? Let me explain this with a small example picture.
the first event has two takes and the second three takes. After that I can’t record anything. It would be nice to have 5 takes per loop.
4. Another note for consistency. Personally I think moving(cutting) the comp event should move(cut) the take events. Currently it could easily lead to mistakes. This note leads to the highly appreciated group editing (like fading multiple events) 🙂
Thanks again for your really nice podium! I wish anyone who celebrates it a very nice x-mas 🙂
roninHi Frits,
the changes so far are cool! good work.
I have small wish: could we have an option that enables the comp track to keep the last N takes? Lets say I’d like to keep 5 takes. Currently the recording is “stopped” after 5 takes. Is it possible to change this behaviour so that while recording continues old takes are removed and always the last 5 are kept? this would be very useful for me.
roninHmm you are right…this raises the need for some other features. But I guess it would be useful if you have something like “cut audio files to events” for cleaning up the whole project. While editing the audio file the “evented” parts of the file could be highlighted and editing could be done via selection (select a part and normalize it). Unfortunately changing the loop size would result in a different beat length and this may be bad while recording. Yes, using a phantom copy would help but anyway:
I’ve I’m the only one who asks for this then you really don’t have to think about this 🙂 I can live with it. It’s not essential it just would speed some things up.
ronin@Zynewave wrote:
There’s no reason to implement the event naming for note and curve sequences, right?
I can’t think of one.
roninLooks very promising!
According to these new features I had a small idea:
Usually the first takes are not very useful and I only want to keep the last (lets say) n takes. Would it be possible to have an option to configure how much take tracks are kept?
Something like “Keep the last : N takes” or if N==0 -> keep all takes. With this option loop recording wouldn’t produce too large comp folders (tracks) and the arrangement stays cleaner.
Opinions are higly appreciated
roninNice update! Works like a charm but I can understand
@thcilnnahoj wrote:
Ohh, such a nice update for the middle mouse button. 🙁
If only my mouse (Logixxxx MX400) hadn’t such a :evil::evil::evil: of a wheel!
since my middle mouse button is integrated with the scrollwheel and it needs two chuck-norrish fingers to push it down 🙂