Added “Refresh file list” button to the file browser toolbar.
I like it, few times I’ve missed it.
From the manual, device panel chapter:
The device list can be updated with the **Devices** menu and the list right-click menu.
List right click menu? I don’t see nothing in that menu :S
@LiquidProj3ct wrote:
From the manual, device panel chapter:
The device list can be updated with the **Devices** menu and the list right-click menu.
List right click menu? I don’t see nothing in that menu :S
http://www.zynewave.com/wiki/doku.php?id=guide:project_start_page#devices_list_menu
@Zynewave wrote:
@LiquidProj3ct wrote:
From the manual, device panel chapter:
The device list can be updated with the **Devices** menu and the list right-click menu.
List right click menu? I don’t see nothing in that menu :S
http://www.zynewave.com/wiki/doku.php?id=guide:project_start_page#devices_list_menu
Yes, but you cannot update the device list from that menu (I think)
@LiquidProj3ct wrote:
Yes, but you cannot update the device list from that menu (I think)
When I write “update” I mean that the list can be edited, organized, etc.
What did you think I meant by “updated”?
Something like “refresh devices” or something like the option “update plugin database (with new devices that aren’t added yet)”. But you’re using the word update like ‘manage’, which I don’t know if that’s right
@LiquidProj3ct wrote:
Something like “refresh devices” or something like the option “update plugin database (with new devices that aren’t added yet)”. But you’re using the word update like ‘manage’, which I don’t know if that’s right
Point taken. I’ve updated the text, so that it now uses “maintain” instead of “update”. I could also have used “manage”.
Thanks Frits—
Getting started–>Mixing–>Last paragraph:
The bus send sliders will control the level of the “wet” signal that is sent to the busses. The gain fader on the track will control the level of the “dry” signal going out of the track.
I think it should be:
the level of the “dry” signal that is sent to the busses
or
the level of the “wet” signal that is come back from the busses
or delete the words “wet” and “dry” and everything will have sense:
@fixed wrote:
he bus send sliders will control the level of the signal that is sent to the busses. The gain fader on the track will control the level of the signal going out of the track.
@LiquidProj3ct wrote:
Getting started–>Mixing–>Last paragraph:
The bus send sliders will control the level of the “wet” signal that is sent to the busses. The gain fader on the track will control the level of the “dry” signal going out of the track.
I think it should be:
the level of the “dry” signal that is sent to the busses
or
the level of the “wet” signal that is come back from the busses
or delete the words “wet” and “dry” and everything will have sense:
@fixed wrote:
he bus send sliders will control the level of the signal that is sent to the busses. The gain fader on the track will control the level of the signal going out of the track.
I did not swap dry/wet by mistake, but I can see why the description can be confusing. I’ve changed the text, and removed dry/wet references.
Frits, there is an small conflict deleting files from file explorer, if the file is playing (browser preview) and you try to delete it you get the tipical windows error that file is in use. Maybe you can change this behavior in two minutes, stoping the playback once you select ‘Delete’ 🙂
@LiquidProj3ct wrote:
Frits, there is an small conflict deleting files from file explorer, if the file is playing (browser preview) and you try to delete it you get the tipical windows error that file is in use. Maybe you can change this behavior in two minutes, stoping the playback once you select ‘Delete’ 🙂
Fixed.
Noticed something peculiar yesterday:
I wanted to transform a series of points into a curve, but Podium won’t let me transform only those points that are selected. Because of this, I had to transform the points before and after this section separately.
An even simpler experiment: if you select any two points, and use any of the transform commands, all points inbetween those two will also be transformed.
I guess this is intentional? It seems a little strange to me, though, if it’s like in the picture example.
@thcilnnahoj wrote:
I guess this is intentional? It seems a little strange to me, though, if it’s like in the picture example.
Sort of intentional. Originally you could only transform a segment selection to a spline curve. When I extended it to also include event selections, the code would only search for the first and last selected event, and then transform that time range. I’ve now changed it so that Podium will divide it into smaller segments if there are “holes” in the selected events.
Thanks.